Nokia update sonic platform 202205 #19210

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

(cherry picked from commit 350e528dc2afb1d3ce5192729931010f04755f97)

ndk 22.9.13

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically * 8cf9817 - (HEAD -> 202205, origin/202205) Merge pull request sonic-net#26 from jfeng-arista/202205-clear-fabric-counters (8 hours ago) [gechiang] * 4c91f77 - Clear fabric counters queue/port (4 weeks ago) [Jie Feng]

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

ndk 22.9.14

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically * ceced56 - (HEAD -> 202205, origin/202205) Merge pull request sonic-net#30 from alpeshspatel/alpeshspatel/util.msft.202205.mmuconfig (30 hours ago) [abdosi] |\ | * 44dbfde - mmuconfig to set threshold for profiles master#2775 (2 days ago) [Alpesh S Patel] |/ * 75030e0 - Merge pull request sonic-net#29 from mssonicbld/sonicbld/202205-merge (3 days ago) [mssonicbld] * 7df1c6b - Merge branch '202205' of https://github.com/sonic-net/sonic-utilities into 202205 (3 days ago) [Sonic Automation] * d9bc820 - Handle NotImplementedError exception while changing optoe write max (sonic-net#2985) (3 days ago) [mihirpat1] * 4bf29fe - [sonic-package-manager] Increate timeout for sonic-package-manager migrate (sonic-net#2973) (3 days ago) [Yaqiang Zhu]

…atically

Update cisco-8000.ini to 202205.3.2.1 drop

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically * c4dcb32 - (HEAD -> 202205, origin/202205) Merge pull request sonic-net#31 from mssonicbld/sonicbld/202205-merge (3 days ago) [mssonicbld] * bb5123d - Merge branch '202205' of https://github.com/sonic-net/sonic-utilities into 202205 (3 days ago) [Sonic Automation] * ff8a064 - [202205][acl-loader] Identity ICMP v4/v6 based on IP_PROTOCOL for custom ACL table types (sonic-net#3003) (3 days ago) [Zhijian Li]

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically * b97d75e - (HEAD -> 202205, origin/202205) Merge pull request sonic-net#32 from mssonicbld/sonicbld/202205-merge (3 days ago) [mssonicbld] * 27cea9f - Merge branch '202205' of https://github.com/sonic-net/sonic-utilities into 202205 (3 days ago) [Sonic Automation] * 0ad458c - Include /var/log.tmpfs in techsupport (sonic-net#2979) (3 days ago) [mihirpat1]

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

Update cisco-8000.ini to 202205.3.2.2 drop

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

ndk 22.9.16

Update cisco-8000.ini Updated platform version to 202205.3.2.3. Release content for Cisco 8808 platform: * Fixed syncd crash due to 40G link configuration * Fixed load_minigraph failure due to 40G configuration * HBM route scale enablement for Vanguard Lancer * Fixed port handling of empty ecmp group to drop packets (MIGSMSFT-333 / SR 696141124)

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically * 189ea52 - (HEAD -> 202205, origin/202205) Merge pull request sonic-net#33 from mssonicbld/sonicbld/202205-merge (13 days ago) [mssonicbld] * d61c2a3 - Merge branch '202205' of https://github.com/sonic-net/sonic-utilities into 202205 (13 days ago) [Sonic Automation] * 5d3c563 - [dualtor_neighbor_check] Adjust zero-mac check condition (sonic-net#3034) (2 weeks ago) [Longxiang Lyu]

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

Signed-off-by: Anand Mehra anamehra@cisco.com

Update cisco-8000.ini to 202205.3.2.4

…-BGP peers in TSA mode (sonic-net#16714) What I did: In Chassis TSA mode Loopback0 Ip's of each LC's should be advertise through e-BGP peers of each remote LC's How I did: - Route-map policy to Advertise own/self Loopback IP to other internal iBGP peers with a community internal_community as define in constants.yml - Route-map policy to match on above internal_community when route is received from internal iBGP peers and set a internal tag as define in constants.yml and also delete the internal_community so we don't send to any of e-BGP peers - In TSA new route-map match on above internal tag and permit the route (Loopback0 IP's of remote LC's) and set the community to traffic_shift_community. - In TSB delete the above new route-map. How I verify: Manual Verification UT updated. sonic-mgmt PR: sonic-net/sonic-mgmt#10239 Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>

[masft-202205] Support advertisement of Loopback0 of all LC's across all e-BGP peers in TSA mode

sonic-net#16732) What I did: Added support when TSA is done on Line Card make sure it's completely isolated from all e-BGP peer devices from this LC or remote LC Why I did: Currently when TSA is executed on LC routes are withdrawn from it's connected e-BGP peers only. e-BGP peers on remote LC can/will (via i-BGP) still have route pointing/attracting traffic towards this isolated LC. How I did: When TSA is applied on LC all the routes that are advertised via i-BGP are set with community tag of no-export so that when remote LC received these routes it does not send over to it's connected e-BGP peers. Also once we receive the route with no-export over iBGP match on it and and set the local preference of that route to lower value (80) so that we remove that route from the forwarding database. Below scenario explains why we do this: - LC1 advertise R1 to LC3 - LC2 advertise R1 to LC3 - On LC3 we have multi-path/ECMP over both LC1 and LC2 - On LC3 R1 received from LC1 is consider best route over R1 over received from LC2 and is send to LC3 e-BGP peers - Now we do TSA on LC2 - LC3 will receive R1 from LC2 with community no-export and from LC1 same as earlier (no change) - LC3 will still get traffic for R1 since it is still advertised to e-BGP peers (since R1 from LC1 is best route) - LC3 will forward to both LC1 and LC2 (ecmp) and this causes issue as LC2 is in TSA mode and should not receive traffic To fix above scenario we change the preference to lower value of R1 received from LC2 so that it is removed from Multi-path/ECMP group. How I verfiy: UT has been added to make sure Template generation is correct Manual Verification of the functionality sonic-mgmt test case will be updated accordingly. Please note this PR is on top of this :sonic-net#16714 which needs to be merged first. Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>

[msft-202205] Added support of isolating given LC in Chassis with TSA mode Cherry-pick of PR: sonic-net#16732

Manual Merge public 202205 to resolve conflict introduced by [202205] Update Linux kernel to 5.10.179 sonic-net#17569

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

(cherry picked from commit e9dec4615dbdca5a9db51ae5a15fc4d368bb43a1)

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

ndk 22.9.21

…ice data (sonic-net#17378) These changes, in conjunction with NDK version >= 22.9.17 address the thermal logging issues discussed at Nokia-ION/ndk#27. While the changes contained at this PR do not require coupling to NDK version >= 22.9.17, thermal logging enhancements will not be available without updated NDK >= 22.9.17. Thus, coupling with NDK >=22.9.17 is preferred and recommended. Why I did it To address thermal logging deficiencies. Work item tracking Microsoft ADO (number only): 26365734 How I did it The following changes are included: Threshold configuration values are provided in the associated device data .json files. There is also a change included to better handle the condition where an SFP module read fails. Modify the module.py reboot to support reboot linecard from Supervisor - Modify reboot to call _reboot_imm for single IMM card reboot - Add log to the ndk_cmd to log the operation of "reboot-linecard" and "shutdown/satrtup the sfm" Add new nokia_cmd set command and modify show ndk-status output - Add a new function reboot_imm() to nokia_common.py to support reboot a single IMM slot from CPM - Added new command: nokia_cmd set reboot-linecard <slot> [forece] for CPM - Append a new column "RebootStatus" at the end of output of "nokia_cmd show ndk-status" - Provide ability for IMM to disable all transceiver module TX at reboot time - Remove defunct xcvr-resync service

…API reboot and Disable all SFPs (sonic-net#17483) Why I did it When Supervisor card is rebooted by using PMON API, it takes about 90 seconds to trigger the shutdown in down path. At this time linecards have been up. This delays linecards database initialization which is trying to PING/PONG the database-chassis. To address this issue, we modified the NDK to use the system call with "sudo reboot" when the request is from PMON API on Supervisor case. The NDK version is 22.9.20 and greater. This new NDK requires this modifcaiton of platform_reboot to work with. Work item tracking Microsoft ADO (number only): 26365734 How I did it Modify the platform_reboot In Supervisor not to reboot all IMMs since it has been done in the function reboot() in module.py. Also handle the reboot-cause.txt for on the Supervisor when the reboot is request from PMON API. Modify the Nokia platform specific platform_reboot in linecard to disable all SPFs. This PR works with NDK version 22.9.20 and above Signed-off-by: mlok <marty.lok@nokia.com>

Cherry-pick 17483 and 17378 from public master to msft/202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…es up, start a timer to configure TSB and configure TSB when the timer expires Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>

1) Reused the existing Python functions 2) Modified the function names to use snake case 3) Changed the print to logger.log_info 4) Fixed the indentation 5) Modified it to work for both single and multi asic 6) Reset the env variable 7) When user issues TSB when the service is running, stop the service Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…rvice (sonic-net#17836) * Update service_checker.py Signed-off-by: Abhishek Dosi <abdosi@microsoft.com>

[chassis] update service_checker module to handle database-chassis service (sonic-net#17836)

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

ndk 22.9.23

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…t ids (sonic-net#18066) Update/Add the sai_postinit_cmd.soc with the interrupt-ids Microsoft ADO 26730061: How to verify it Verify on the Chassis LCs

…E platform (thermal logging thresholds) (sonic-net#18063) These changes adjust Nokia IXR7250 thermal sensor logging thresholds. Why I did it To modify the thermal sensor logging thresholds used on LC and Supervisor. How I did it Modified the JSON based thermal logging thresholds used to determine when to log current high sensor temperature and hottest sensor margin fluctuations. How to verify it Verify that syslog messages indicating current (high) temperature and margin values are only logged when these respective values fluctuate by at least 5 degrees.

202205 manual cherry pick PRs: [chassis][voq] update the sai_post_init soc file with interrupt ids sonic-net#18066 and [Nokia-IXR7250E][Devicedata] Update the device data for Nokia IXR7250… sonic-net#18063

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

ndk 22.9.25

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…et#18420 9302b28 [SFM] Fixed the SFM empty serail when SFM is hot inserte

[Nokia][sonic-platform] Update Nokia sonic-platform submodule sonic-net#18420 …

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…17836 (sonic-net#18109) PR sonic-net#17836 added the container checking for database-chassis for Supervisor. But the related container_feature_dict[] is missing for the database-chassis. This causes the exception failure shows on Supervisor Signed-off-by: mlok <marty.lok@nokia.com>

[service-checker] Fix the service-checker issue which is caused by PR…

…sa-tsb Added code to start a new service to configure TSA as soon as Linecard comes up, start a timer to configure TSB and configure TSB when the timer expires

Replace char* and C string functions with C++ strings.

…-cstr [202205][ssg]: Use C++ strings for text handling

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…onic-net#18092) HW Lane for Inband and Rec ports were conflicting with front panel ports Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>

[Nokia-IXR7250E][Devicedata] Update HW Lane for Inband and Rec ports …

… bringing up BGP (sonic-net#18556) Why I did it Ensure BGP peer bring-up and route advertisements are done only after checking TSA status during reload Work item tracking Microsoft ADO (number only): 27171112 How I did it Add dependency on tsa_enabled flag before peer configuration How to verify it Validate that the BGP session bring up is not complete until tsa_enabled flag is populated. Ensure no traffic is drawn to the device when in TSA and reboot with BGP unshut.

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

[202205] Port the yang-models for sonic-console.yang and sonic-restapi.yang

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

- Remove bcmcmd show pvt ASIC thermal sensor polling

Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>

ndk 22.9.26

…sa-tsb Fix for Bug in tsa-tsb script

Add dependency for tsa_enabled flag before populating peer config and…

Add YANG model for SYSTEM_PORT. Resolves sonic-net#12458 YANG model for SYSTEM_PORT in CONFIG_DB was missing. Added new YANG model and associated unit tests. Passing unit tests

[yang-models] Add YANG model for SYSTEM_PORT (sonic-net#12689)

…re valid in CONIFG_DB before starting chassis-db-cleanup (sonic-net#17962) This PR fixes the issue reported in Issu sonic-net#17945 We noticed that chassis db clean up is skipped sometimes when the CHASSIS_APP_DB PING fails. Also if host_name and asic_name are not written to CONIG_DB, it could pass the empty strings to CHASSIS_APP_DB EVAL commands. The service hostname-config.service is restarted whenever the config-reload or load-minigraph is done and this services renames the file /etc/hosts to updates it with the new file. This interferes with swss@.service and when swss.sh script CHASSIS_APP_DPP when the /etc/hosts file is renamed, the error "Unable to connect to redis: Cannot assign requested address" is seen and the CHASSIS_APP_DB EVAL command fails. This causes the chassis db entries not getting cleaned up and causes orchagent crash in remote LC's. --------- Signed-off-by: saksarav <sakthivadivu.saravanaraj@nokia.com>

Wait till CHASIS_APP_DB PING is successful, host_name and asic_name …

…wn a SFM. (sonic-net#18393) On a Supervisor card of a VOQ chassis, when remove or shutdown a Fabric card, swss.sh shows Stacktrace for all related empty SFM slots in the syslog file. This PR fixes sonic-net#18384 How I did it In the asic_status.py, all empty SFM slots related swss.sh is in the waiting state to wait for the presence event of SFM -- SET operation. The subscriber event handler also includes the "DEL" operation when a SFM is shutdown/removal. When a SFM is shutdown, all empty slot's swss.sh also get the "DEL" event although it is not for them. In the "DEL" operation, the current implementation doesn't check if this "DEL" operation for them, and then they exit the wait state and proceed to docker-wait-any with wrong operation in the wrong slot. docker-wait0any raise the backtarce. How to verify it In a chassis which has some empty SMF slot, remove or shutdown a SFM. There should not be related stacktrace shown in syslog Signed-off-by: mlok <marty.lok@nokia.com>

[supervisor][sfm]Fix the issue of swss.sh shows backtrace when shutdo…

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…t2-voq-support-new T2-VOQ: VS Support

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

sonic-net#18444) ### Why I did it In Multi ASIC scenario, 1. PORT configuration table requires `coreId`, `corePortId` and `numVoq`: ```json { "PORT": { "Ethernet0": { "index": "0", "lanes": "101,102", "description": "fortyGigE1/1/1", "mtu": "9100", "alias": "fortyGigE1/1/1", "speed": "40000", "link_training": "off", "laser_freq": "191300", "tx_power": "-27.3", "dom_polling": "enabled", "coreId": "1", "corePortId": "1", "numVoq": "8" }, "Ethernet1": { "index": "1", "lanes": "103,104", "description": "fortyGigE1/1/2", "mtu": "9100", "alias": "fortyGigE1/1/2", "admin_status": "up", "speed": "40000", "link_training": "on", "laser_freq": "191300", "tx_power": "-27.3", "dom_polling": "enabled", "coreId": "0", "corePortId": "14", "numVoq": "8" }, "Ethernet63": { "index": "63", "lanes": "87,88", "description": "fortyGigE1/4/16", "mtu": "9100", "alias": "fortyGigE1/4/16", "speed": "40000", "laser_freq": "191300", "tx_power": "-27.3", "dom_polling": "disabled", "coreId": "0", "corePortId": "15", "numVoq": "8" } } } ``` 2. DEVICE_METADATA configuration table requires `asic_id`: ```json { "DEVICE_METADATA": { "localhost": { "asic_id": "06:00.0", "asic_name": "asic0", "hwsku": "Force10-S6100", "default_bgp_status": "up", "docker_routing_config_mode": "unified", "hostname": "sonic-s6100-01", "platform": "x86_64-dell_s6100_c2538-r0", "mac": "4c:76:25:f4:70:82", "default_pfcwd_status": "disable", "bgp_asn": "65100", "deployment_id": "1", "type": "ToRRouter", "bgp_adv_lo_prefix_as_128" : "true", "buffer_model": "traditional", "yang_config_validation": "disable", "rack_mgmt_map": "dummy_value", "timezome": "Europe/Kiev" } } } ``` ##### Work item tracking - Microsoft ADO **(number only)**: 27252814, 27253157 #### How I did it 1. Added `coreId`, `corePortId` and `numVoq` field to CONFIG_DB PORT table. 2. Added `asic_id` and `asic_name` field to CONFIG_DB DEVICE_METADATA table.

### Why I did it Consolidate the `numvoq`, `coreid`, `coreportid` to be lower case which matches other leaf node convention. ### How I did it Rename to lower case. #### How to verify it No need to verify.

…k-18444-and-18704 [YANG]: Add Yang model support for Multi ASIC port and device_metadata

…oot to allow SUP to log expected/unepected midplane/module connectivity msg (sonic-net#18805) Why I did it For Linecard expected and unexpected reboot, Supervisor needs to log a expected and unexpected lost connectivity message. After the new mechanism has been introduced by PRs. For Nokia-IXR7250E-36x600G linecard, it requires to handle missing heartbeat reboot is unexpected reboot for SUP. Issue sonic-net#18540 Work item tracking Microsoft ADO (number only): How I did it On Nokia-IXR7250E-36x400G platform, missing heartbeat reboot also call the "sudo reboot" which creates a CHASSIS_MODULE_REBOOT_INFO_TABLE entry expected reboot on SUP. Since heartbeat reboot is unexpected reboot, it requires to modify the platform_reboot check if it is missing heart reboot, then remove the CHASSIS_MODULE_REBOOT_INFO_TABLE entry on the SUP. So that, SUP can log the unexpected log. How to verify it Simulated the missing heartbeat reboot on the linecard, then, verify the log message on SUP as below Apr 25 19:50:19.286081 ixre-cpm-chassis7 WARNING pmon#chassisd: Module LINE-CARD0 went off-line! Apr 25 19:50:22.549416 ixre-cpm-chassis7 WARNING pmon#chassisd: Unexpected: Module LINE-CARD0 lost midplane connectivity. Signed-off-by: mlok <marty.lok@nokia.com>

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…into 202205

[code sync] Merge code from sonic-net/sonic-buildimage:202205 to 202205

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

[Nokia][chassis] modify Nokia-IXR7250E-36x400G platform specified reb…

…t#18956)

[yang]: adding Buffer pool enum type both for sonic chassis (sonic-net#18956)

…t.yang (sonic-net#18855) Microsoft ADO 27934751: Fixes sonic-net#18854 Update the sonic-system-port.yang to remove the check to have ifname as leafref in the port table The system-port config table will have all the ports in the chassis not only to one linecard, so in case of the chassis with different linecards sku with different number of ports this leafref will not work.

[chassis][voq] Remove the leaf ref for the ifname in sonic-system-por…

…is (sonic-net#18875) Why I did it The configuration for QUEUE and BUFFER_QUEUE differs between a VOQ device and a Non-VOQ devices. For the Voq device: The queue and buffer queue is applied on the system port. The system port is a representation of every port in a chassis, the key for systemport consists of Linecard Name , Asic Name and portname On a Non voq device: the queue and buffer queue configuration is applied on the front panel port. Due to this differences the yang models sonic-queue.yang and sonic-buffer-queue.yang does not work for Voq devices This is address in this PR Microsoft ADO (27252773 and 27252696): How I did it Update the yang model to have different CONFIG_LIST with different keys based on the following condition when the switch_type is not present or switch_type is not voq, the yang LIST will have key of port and queue_index when the switch_type is present and switch_type is voqhe yang LIST will have key of Linecard name, asi name, port and queue_index How to verify it UT and incremental config push on chassis

…atically

…ic-utilities [submodule][202205] Update submodule sonic-utilities to the latest HEAD automatically

[Chassis][Voq]Update sonic-buffer-queue and sonic-queue for Voq Chass…

… for Nokia-IXR7250E platform (sonic-net#18862) This PR add the platform specified linecard_reboot_timeout value to the platform_evn.conf. It works PR sonic-net/sonic-platform-daemons#480 and sonic-net/sonic-utilities#3292 to address issue sonic-net#18540 Signed-off-by: mlok <marty.lok@nokia.com>

[Nokia][supervisor] add linecard_reboot_timeout value to platform_env…

Signed-off-by: mlok <marty.lok@nokia.com>

Commits on Oct 23, 2023

ndk 22.9.16

jon-nokia committed Oct 23, 2023

Configuration menu

View commit details

Copy full SHA for 023ff74

Browse repository at this point

Copy the full SHA

023ff74 View commit details

Browse the repository at this point in the history

Commits on Jan 18, 2024

ndk 22.9.23

jon-nokia committed Jan 18, 2024

Configuration menu

View commit details

Copy full SHA for 491b182

Browse repository at this point

Copy the full SHA

491b182 View commit details

Browse the repository at this point in the history

Nokia update sonic platform 202205 #19210

Nokia update sonic platform 202205 #19210

Commits on Sep 24, 2023

Commits on Sep 25, 2023

Commits on Sep 26, 2023

Commits on Sep 27, 2023

Commits on Sep 29, 2023

Commits on Sep 30, 2023

Commits on Oct 3, 2023

Commits on Oct 4, 2023

Commits on Oct 5, 2023

Commits on Oct 6, 2023

Commits on Oct 10, 2023

Commits on Oct 11, 2023

Commits on Oct 12, 2023

Commits on Oct 14, 2023

Commits on Oct 15, 2023

Commits on Oct 17, 2023

Commits on Oct 18, 2023

Commits on Oct 20, 2023

Commits on Oct 21, 2023

Commits on Oct 23, 2023

Commits on Oct 24, 2023

Commits on Oct 26, 2023

Commits on Oct 27, 2023

Commits on Oct 28, 2023

Commits on Oct 31, 2023

Commits on Nov 3, 2023

Commits on Nov 7, 2023

Commits on Nov 8, 2023

Commits on Nov 9, 2023

Commits on Nov 16, 2023

Commits on Nov 18, 2023

Commits on Nov 21, 2023

Commits on Nov 22, 2023

Commits on Nov 28, 2023

Commits on Nov 30, 2023

Commits on Dec 1, 2023

Commits on Dec 5, 2023

Commits on Dec 7, 2023

Commits on Dec 11, 2023

Commits on Dec 12, 2023

Commits on Dec 13, 2023

Commits on Dec 19, 2023

Commits on Jan 5, 2024

Commits on Jan 6, 2024

Commits on Jan 7, 2024

Commits on Jan 8, 2024

Commits on Jan 9, 2024

Commits on Jan 10, 2024

Commits on Jan 11, 2024

Commits on Jan 12, 2024

Commits on Jan 18, 2024

Commits on Jan 23, 2024

Commits on Jan 24, 2024

Commits on Jan 25, 2024

Commits on Jan 26, 2024

Commits on Jan 27, 2024

Commits on Jan 30, 2024

Commits on Feb 5, 2024

Commits on Feb 6, 2024

Commits on Feb 8, 2024

Commits on Feb 10, 2024

Commits on Feb 20, 2024

Commits on Feb 23, 2024

Commits on Feb 29, 2024

Commits on Mar 8, 2024

Commits on Mar 9, 2024

Commits on Mar 13, 2024

Commits on Mar 14, 2024

Commits on Mar 19, 2024

Commits on Mar 25, 2024

Commits on Mar 26, 2024

Commits on Apr 3, 2024

Commits on Apr 5, 2024

Commits on Apr 9, 2024

Commits on Apr 14, 2024

Commits on Apr 15, 2024

Commits on Apr 17, 2024

Commits on Apr 18, 2024