Add new platform m2-w6510-48V #17899
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…low]ERR sflow#hsflowd: device Loopback0 Get SIOCGIFFLAGS failed : No such device sonic-net#13407 (sonic-net#15362) Signed-off-by: Gokulnath-Raja <[email protected]> Co-authored-by: mohanapriya-meganathan <[email protected]>
…net#16625) - Why I did it Because the Spectrum4 devices don't support mlxtrace utility. - How I did it Edit sai.profile and remove mlxtrace_spectrum4_itrace_*.cfg.ext files Signed-off-by: vadymhlushko-mlnx <[email protected]> Co-authored-by: Vadym Hlushko <[email protected]>
…d format (sonic-net#16388) (sonic-net#16626) * Change the CAK key length check in config plugin, macsec test profile changes * Fix the format in add_profile api The changes needed in various macsec unit tests and config plugin when we move to accept the type 7 encoded key format for macsec. This goes along with PR : sonic-net/sonic-swss#2892 raised earlier. Co-authored-by: judyjoseph <[email protected]>
…c-net#16490) (sonic-net#16628) In sonic-net#15080, there was a command added to re-add 127.0.0.1/8 to the lo interface when the networking configuration is being brought down. However, the trigger for that command is `down`, which, looking at ifupdown2 configuration files, runs immediately after 127.0.0.1/16 is removed. This means there may be a period of time where there are no loopback addresses assigned to the lo interface, and redis commands will fail. Fix this by changing this to pre-down, which should run well before 127.0.0.1/16 is removed, and should always leave lo with a loopback address. Signed-off-by: Saikrishna Arcot <[email protected]> Co-authored-by: Saikrishna Arcot <[email protected]>
sonic-net#16527) Signed-off-by: anamehra [email protected] Added a check for DEVICE_METADATA before accessing the data. This prevents the j2 failure when var is not available.
Add new easy bringup (EZB) files for new SAI 1.12.0
…onic-net#16603) Stop installing development packages from telemetry docker images to avoid unnecessary space usage. ### Why I did it From 202305, libswsscommon-dev and the Boost headers were brought in telemetry docker image incorrectly, which result in unnecessary space usage. ##### Work item tracking - Microsoft ADO **(number only)**:25176224 #### How I did it Remove libswsscommon-dev accordingly. #### How to verify it Image building.
… (sonic-net#16644) * [swss] Chassis db clean up optimization and bug fixes This commit includes the following changes: - Fix for regression failure due to error in finding CHASSIS_APP_DB in pizzabox (#PR 16451) - After attempting to delete the system neighbor entries from chassis db, before starting clearing the system interface entries, wait for sometime only if some system neighbors were deleted. If there are no system neighbors entries deleted for the asic coming up, no need to wait. - Similar changes for system lag delete. Before deleting the system lag, wait for some time only if some system lag memebers were deleted. If there are no system lag members deleted no need to wait. - Flush the SYSTEM_NEIGH_TABLE from the local STATE_DB. While asic is coming up, when system neigh entries are deleted from chassis ap db (as part of chassis db clean up), there is no orchs/process running to process the delete messages from chassis redis. Because of this, stale system neigh are entries present in the local STATE_DB. The stale entries result in creation of orphan (no corresponding data path/asic db entry) kernel neigh entries during STATE_DB:SYSTEM_NEIGH_TABLE entries processing by nbrmgr (after the swss serive came up). This is avoided by flushing the SYSTEM_NEIGH_TABLE from the local STATE_DB when sevice comes up. Signed-off-by: vedganes <[email protected]> * [swss] Chassis db clean up bug fixes review comment fix - 1 Debug logs added for deletion of other tables (SYSTEM_INTERFACE and SYSTEM_LAG_TABLE) Signed-off-by: vedganes <[email protected]> --------- Signed-off-by: vedganes <[email protected]> (cherry picked from commit b13b41f)
…4.6.1062/2012.1062/SAIBuild2211.25.1.4 (sonic-net#16478) - Why I did it SAI bug Fixes 1. When creating an ACL rule with SAI_ACL_ENTRY_ATTR_FIELD_SRC_IP/SAI_ACL_ENTRY_ATTR_FIELD_DST_IP enabled, and then disabling the field by setting enable=false, a match on L3_type=IPv4 will remain programmed for the rule Issue resolved after the fix 2. Allow the max scale of virtual routers to be configure for SPC-1, SPC-2, SPC-3 which is 255 when fastboot enable and 511 when fastboot disable 3. Remove default hash key of SRC_MAC, DST_MAC and ETH_TYPE SAI features 1. Port init profile 2. Dual ToR Active-Standby | Additional MAC support SDK/FW bug fixes 1. When preforming fast boot from an old SDK version (currently installed) to a newer one (target version), and the system was initially loaded with a new SDK version (past version), and the system has not been wiped, under specific conditions, the fast boot would use the past version's data and may fail. - How I did it Update SAI version to SAIBuild2211.25.1.4 Update SDK/FW version to 4.6.1062/2012.1062
…lly (sonic-net#16642) #### Why I did it src/sonic-swss ``` * 0584d35b - (HEAD -> 202305, origin/202305) Revert "Support type7 encoded CAK key for macsec in config_db (sonic-net#2892)" (3 minutes ago) [stormliang] * 7097cf2b - Revert "[teamd]: Clean teamd process if LAG creation fails (sonic-net#2888)" (3 days ago) [stormliang] * a0eb0d07 - Support type7 encoded CAK key for macsec in config_db (sonic-net#2892) (4 days ago) [judyjoseph] * c7e5f10e - [teamd]: Clean teamd process if LAG creation fails (sonic-net#2888) (4 days ago) [Lawrence Lee] * f30b6107 - [CodeQL]: Use dependencies with relevant versions in azp template. (sonic-net#2845) (4 days ago) [Nazarii Hnydyn] ``` #### How I did it #### How to verify it #### Description for the changelog
Fixing the following build issue
[2023-09-20T04:42:00.004Z] [ FAIL LOG START ] [ target/python-wheels/bullseye/sonic_bgpcfgd-1.0-py3-none-any.whl ]
[2023-09-20T04:42:00.004Z] Build start time: Wed Sep 20 04:41:54 UTC 2023
[2023-09-20T04:42:00.004Z] [ REASON ] : target/python-wheels/bullseye/sonic_bgpcfgd-1.0-py3-none-any.whl does not exist NON-EXISTENT PREREQUISITES: target/python-wheels/bullseye/sonic_config_engine-1.0-py3-none-any.whl-install target/python-wheels/bullseye/sonic_yang_mgmt-1.0-py3-none-any.whl-install target/python-wheels/bullseye/sonic_yang_models-1.0-py3-none-any.whl-install target/debs/bullseye/libyang_1.0.73_amd64.deb-install target/debs/bullseye/libyang-cpp_1.0.73_amd64.deb-install target/debs/bullseye/python3-yang_1.0.73_amd64.deb-install target/debs/bullseye/python3-swsscommon_1.0.0_amd64.deb-install
[2023-09-20T04:42:00.004Z] [ FLAGS FILE ] : []
[2023-09-20T04:42:00.005Z] [ FLAGS DEPENDS ] : [mellanox amd64 bullseye]
[2023-09-20T04:42:00.005Z] [ FLAGS DIFF ] : [mellanox amd64 bullseye ]
[2023-09-20T04:42:00.005Z] /sonic/src/sonic-bgpcfgd /sonic
[2023-09-20T04:42:00.005Z] running pytest
[2023-09-20T04:42:00.005Z] Searching for netaddr==0.8.0
[2023-09-20T04:42:00.005Z] Best match: netaddr 0.8.0
[2023-09-20T04:42:00.005Z]
[2023-09-20T04:42:00.005Z] Using /var/sw-r2d2-bot/.local/lib/python3.9/site-packages
[2023-09-20T04:42:00.005Z] running egg_info
[2023-09-20T04:42:00.005Z] writing sonic_bgpcfgd.egg-info/PKG-INFO
[2023-09-20T04:42:00.005Z] writing dependency_links to sonic_bgpcfgd.egg-info/dependency_links.txt
[2023-09-20T04:42:00.005Z] writing entry points to sonic_bgpcfgd.egg-info/entry_points.txt
[2023-09-20T04:42:00.005Z] writing requirements to sonic_bgpcfgd.egg-info/requires.txt
[2023-09-20T04:42:00.005Z] writing top-level names to sonic_bgpcfgd.egg-info/top_level.txt
[2023-09-20T04:42:00.005Z] reading manifest file 'sonic_bgpcfgd.egg-info/SOURCES.txt'
[2023-09-20T04:42:00.005Z] writing manifest file 'sonic_bgpcfgd.egg-info/SOURCES.txt'
[2023-09-20T04:42:00.005Z] running build_ext
[2023-09-20T04:42:00.005Z] Traceback (most recent call last):
[2023-09-20T04:42:00.005Z] File "/sonic/src/sonic-bgpcfgd/setup.py", line 3, in <module>
[2023-09-20T04:42:00.005Z] setuptools.setup(
[2023-09-20T04:42:00.005Z] File "/usr/local/lib/python3.9/dist-packages/setuptools/__init__.py", line 163, in setup
[2023-09-20T04:42:00.005Z] return distutils.core.setup(**attrs)
[2023-09-20T04:42:00.005Z] File "/usr/lib/python3.9/distutils/core.py", line 148, in setup
[2023-09-20T04:42:00.005Z] dist.run_commands()
[2023-09-20T04:42:00.006Z] File "/usr/lib/python3.9/distutils/dist.py", line 966, in run_commands
[2023-09-20T04:42:00.006Z] self.run_command(cmd)
[2023-09-20T04:42:00.006Z] File "/usr/lib/python3.9/distutils/dist.py", line 985, in run_command
[2023-09-20T04:42:00.006Z] cmd_obj.run()
[2023-09-20T04:42:00.006Z] File "/usr/local/lib/python3.9/dist-packages/ptr.py", line 208, in run
[2023-09-20T04:42:00.006Z] with self.project_on_sys_path():
[2023-09-20T04:42:00.006Z] File "/usr/lib/python3.9/contextlib.py", line 117, in __enter__
[2023-09-20T04:42:00.006Z] return next(self.gen)
[2023-09-20T04:42:00.006Z] File "/usr/local/lib/python3.9/dist-packages/setuptools/command/test.py", line 168, in project_on_sys_path
[2023-09-20T04:42:00.006Z] require('%s==%s' % (ei_cmd.egg_name, ei_cmd.egg_version))
[2023-09-20T04:42:00.006Z] File "/usr/local/lib/python3.9/dist-packages/pkg_resources/__init__.py", line 899, in require
[2023-09-20T04:42:00.006Z] needed = self.resolve(parse_requirements(requirements))
[2023-09-20T04:42:00.006Z] File "/usr/local/lib/python3.9/dist-packages/pkg_resources/__init__.py", line 790, in resolve
[2023-09-20T04:42:00.006Z] raise VersionConflict(dist, req).with_context(dependent_req)
[2023-09-20T04:42:00.006Z] pkg_resources.ContextualVersionConflict: (netaddr 0.9.0 (/var/sw-r2d2-bot/.local/lib/python3.9/site-packages), Requirement.parse('netaddr==0.8.0'), {'sonic-bgpcfgd'})
[2023-09-20T04:42:00.007Z] [ FAIL LOG END ] [ target/python-wheels/bullseye/sonic_bgpcfgd-1.0-py3-none-any.whl ]
[2023-09-20T04:42:00.007Z] make: *** [slave.mk:881: target/python-wheels/bullseye/sonic_bgpcfgd-1.0-py3-none-any.whl] Error 1
[2023-09-20T04:42:00.007Z] make: *** Waiting for unfinished jobs....
…lly (sonic-net#16694) #### Why I did it src/sonic-swss ``` * 8934b62b - (HEAD -> 202305, origin/202305) [202305][CodeQL]: Use dependencies with relevant versions in azp template. (sonic-net#2906) (3 hours ago) [Nazarii Hnydyn] ``` #### How I did it #### How to verify it #### Description for the changelog
…et#16545) Sfp api can now be called from the host which doesn't have the python_sdk_api installed. Also, sfp api has been migrated to use sysfs instead of sdk handle. Signed-off-by: Vivek Reddy Karri <[email protected]>
* [Ci] Change the package upgrade PR title * Change the branchname variable, and change the body
…t fast-reboot from older images (sonic-net#16733) (sonic-net#16753)
Why I did it SONiC service determine-reboot-cause might run before driver creating reset cause files. In that case, the reset cause will be "Unknown". This PR introduces a wait mechanism to wait for reset cause sysfs files ready. How I did it /run/hw-management/config/reset_attr_ready is the file to indicate all reset cause files are ready. In chassis.get_reboot_cause function, it waits /run/hw-management/config/reset_attr_ready for up to 45 seconds. How to verify it Manual test on master/202211/202205
…upport for CMIS CDB operations (sonic-net#16572) (sonic-net#16796)
…00C/SN4700. (sonic-net#16761) BACKPORT: sonic-net#16781 Why I did it To enable Store-And-Forward switching mode for SN2700/SN3800/SN4600C/SN4700 Work item tracking N/A How I did it Added vendor SAI config options How to verify it make configure PLATFORM=mellanox make target/sonic-mellanox.bin
Why I did it First SONIC 202305 based release Includes all fixes so far up to latest 202205 based 8111 drop (Code drop 111: 202205.main.0.13) Work item tracking Microsoft ADO (number only): How I did it update to 202305.main.0.1 release How to verify it
…ic-net#17650) Signed-off-by: Nazarii Hnydyn [email protected] Why I did it Improved switch init time Work item tracking N/A How I did it Replaced: sonic-cfggen -> sonic-db-cli Aggregated template list for sonic-cfggen How to verify it Run warm-reboot
sonic-net#17731) #### Why I did it src/linkmgrd ``` * 2f5971f - (HEAD -> 202305, origin/202305) [warmboot] use config_db connector to update mux mode config instead of CLI (sonic-net#223) (4 hours ago) [Jing Zhang] ``` #### How I did it #### How to verify it #### Description for the changelog
…et#17649) Signed-off-by: Nazarii Hnydyn [email protected] This improvement does not bring any warm-reboot degradation, since the database availability (tcp/ip access over the loopback interface) was fixed by these PRs: Re-add 127.0.0.1/8 when bringing down the interfaces sonic-net#15080 Fix potentially not having any loopback address on lo interface sonic-net#16490 Why I did it Removed dependency on interfaces-config.service to speed up the boot, because interfaces-config.service takes a lot of time on init Work item tracking N/A How I did it Changed service files for swss/syncd How to verify it Boot and check swss/syncd start time comparing to interfaces-config
Signed-off-by: Lawrence Lee <[email protected]>
…atically (sonic-net#17757) #### Why I did it src/sonic-utilities ``` * 651a80b1 - (HEAD -> 202305, origin/202305) Modify teamd retry count script to base BGP status on default BGP status (sonic-net#3069) (22 hours ago) [Saikrishna Arcot] ``` #### How I did it #### How to verify it #### Description for the changelog
Why I did it For some devices with small memory, after upgrading to the latest image, the available memory is not enough. Work item tracking Microsoft ADO (number only): 26324242 How I did it Disable restapi feature for LeafRouter which with slim image. How to verify it verified on 7050qx T1 (slim image), restapi disabled verified on 7050qx T0 (slim image), restapi enabled verified on 7260 T1 (normal image), restapi enabled
### Why I did it Fix ENABLE_DIALOUT flag issue. ##### Work item tracking - Microsoft ADO **(number only)**: 21326000 #### How I did it Update Makefile.work and add debug string. #### How to verify it 
… unreliable los settings (sonic-net#17768) For 40G optics there is SAI handling of T0 facing ports to be set with SR4 type and unreliable los set for a fixed set of ports. For this property to be invoked the requirement is set phy_unlos_msft=1 in config.bcm. This change is to meet the requirement and once this property is set, the los/interface type settings is applied by SAI on the required ports. Why I did it For Arista-7060CX-32S-Q32 T1, 40G ports RX_ERR minimalization during connected device reboot can be achieved by turning on Unreliable LOS and SR4 media_type for all ports which are connected to T0. The property phy_unlos_msft=1 is to exclusively enable this property. Microsoft ADO: 25941176 How I did it Changes in SAI and turning on property How to verify it Ran the changes on a testbed and verified configurations are as intended. with property admin@sonic2:~$ bcmcmd "phy diag xe8 dsc config" | grep -C 2 "LOS" Brdfe_on = 0 Media Type = 2 Unreliable LOS = 1 Scrambling Disable = 0 Lane Config from PCS = 0 without property admin@sonic:~$ bcmcmd "phy diag xe8 dsc config" | grep -C 2 "LOS" Brdfe_on = 0 Media Type = 0 Unreliable LOS = 0 Scrambling Disable = 0 Lane Config from PCS = 0 Signed-off-by: vaibhav-dahiya <[email protected]>
…7761) Why I did it Fix a bug that sometimes the script runs in sh not bash. Work item tracking Microsoft ADO (number only): 26297955 How I did it
…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 <[email protected]>
…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
…r non-secured (sonic-net#16191) What I did: Added flag in sonic_version.yml to see if compiled image is secured or non-secured. This is done using build/compile time environmental variable SECURE_UPGRADE_MODE as define in HLD: https://github.com/sonic-net/SONiC/blob/master/doc/secure_boot/hld_secure_boot.md This flag does not provide the runtime status of whether the image has booted securely or not. It's possible that compile time signed image (secured image) can boot on non secure platform. Why I did: Flag can be used for manual check or by the test case. ADO: 24319390 How I verify: Manual Verification --- build_version: 'master-16191.346262-cdc5e72a3' debian_version: '11.7' kernel_version: '5.10.0-18-2-amd64' asic_type: broadcom asic_subtype: 'broadcom' commit_id: 'cdc5e72a3' branch: 'master-16191' release: 'none' build_date: Fri Aug 25 03:15:45 UTC 2023 build_number: 346262 built_by: AzDevOps@vmss-soni001UR5 libswsscommon: 1.0.0 sonic_utilities: 1.2 sonic_os_version: 11 secure_boot_image: 'no' Signed-off-by: Abhishek Dosi <[email protected]>
*What I did: Enable BFD for Static Route for chassis-packet. This will trigger the use of the feature as defined in here: sonic-net#13789 Signed-off-by: Abhishek Dosi <[email protected]>
…lly (sonic-net#17821) #### Why I did it src/sonic-swss ``` * ac94f0b7 - (HEAD -> 202305, origin/202305) [202305][routeorch] Fixing bug with multiple routes pointing to nhg (sonic-net#3002) (2 hours ago) [Nikola Dancejic] ``` #### How I did it #### How to verify it #### Description for the changelog
… amd64. (sonic-net#17182) (sonic-net#17828) Fix sonic-net#16204 Microsoft ADO (number only): 25746782 How I did it multiarch/debian-debootstrap:arm64-bullseye is too old. It needs to add some gpg keys before 'apt-get update'
Why I did it When we disable telemetry.service, sonic-hostservice will not start. And root cause is sonic-hostservice is only wanted by telemetry.service. Work item tracking Microsoft ADO (number only): How I did it Add dependency for gnmi.service. How to verify it Disable telemetry.service and build new image, and then check sonic-hostservice with new image.
…c-net#17549) Why I did it double commit PR-16450 because of cherry pick conflict for PR#202305 Work item tracking Microsoft ADO (number only): How I did it How to verify it
…-BGP peers in TSA mode (sonic-net#16714) (sonic-net#17837) 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 <[email protected]>
Why I did it Upgrade the xgs SAI version to 8.4.39.2 to include the following fix: 8.4.36.0: [submodule upgrade] [SAI_BRANCH rel_ocp_sai_8_4] SID: SDK-381039 Cosq control dynamic type changes 8.4.37.0: SID: MMU cosq control configuration with Dynamic Type Check 8.4.38.0: [sbumodule upgrade] [CSP 0001232212][SAI_BRANCH rel_ocp_sai_8_4]back-porting SONIC-82415 to SAI 8.4 8.4.39.0: [CSP CS00012320979] Port SONIC-81867 sai spec compliance for get SAI_SWITCH_ATTR_SWITCH_HARDWARE_INFO 8.4.39.1: changes for phy-re-init of 40G ports for TH platforms CS00012327470 8.4.39.2: fix capability for Hostif queue by change SET operation of SAI_HOSTIF_ATTR_QUEUE to be true Work item tracking Microsoft ADO (number only): 26491005 How I did it Upgrade xgs SAI version in sai.mk file. How to verify it Run basic SONiC test using SAI release pipeline, all cases passed. https://dev.azure.com/mssonic/internal/_build/results?buildId=457869&view=results
…atically (sonic-net#17855) #### Why I did it src/sonic-utilities ``` * 93c42272 - (HEAD -> 202305, origin/202305) [chassis]: Support show ip bgp summary to display without error when no external neighbors are configured on chassis LC (sonic-net#3099) (22 hours ago) [Arvindsrinivasan Lakshmi Narasimhan] ``` #### How I did it #### How to verify it #### Description for the changelog
sonic-net#17851) #### Why I did it src/linkmgrd ``` * f5e9b54 - (HEAD -> 202305, origin/202305) [CodeQL] fix unmet build dependency (sonic-net#222) (10 hours ago) [Jing Zhang] * 2282cc5 - [active-standby] Probe the link in suspend timeout (sonic-net#235) (22 hours ago) [Longxiang Lyu] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (sonic-net#17853) #### Why I did it src/sonic-snmpagent ``` * b0a4bcc - (HEAD -> 202305, origin/202305) Set the execute bit on sysDescr_pass.py (sonic-net#306) (22 hours ago) [Andre Kostur] ``` #### How I did it #### How to verify it #### Description for the changelog
…-net#17797) (sonic-net#17840) Currently, whenever isc-dhcp-relay forwards a packet upstream, internally, it will try to send it on a "fallback" interface. My understanding is that this isn't meant to be a real interface, but instead is basically saying to use Linux's regular routing stack to route the packet appropriately (rather than having isc-dhcp-relay specify specifically which interface to use). The problem is that on systems with a weak CPU, a large number of interfaces, and many upstream servers specified, this can introduce a noticeable delay in packets getting sent. The delay comes from trying to get the ifindex of the fallback interface. In one test case, it got to the point that only 2 packets could be processed per second. Because of this, dhcrelay will easily get backlogged and likely get to a point where packets get dropped in the kernel. Fix this by adding a check saying if we're using the fallback interface, then don't try to get the ifindex of this interface. We're never going to have an interface named this in SONiC. Signed-off-by: Saikrishna Arcot <[email protected]>
…atically (sonic-net#17859) #### Why I did it src/sonic-snmpagent ``` * 2efaf2e - (HEAD -> 202305, origin/202305) Revert "[action] [PR:303] Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303)" (sonic-net#308) (4 minutes ago) [StormLiangMS] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (sonic-net#17863) #### Why I did it src/sonic-snmpagent ``` * 6f59d29 - (HEAD -> 202305, origin/202305) Fix SNMP dropping some of the queue counter when create_only_config_db_buffers is set to true (sonic-net#303) (sonic-net#309) (33 minutes ago) [mssonicbld] ``` #### How I did it #### How to verify it #### Description for the changelog
…atically (sonic-net#17868) #### Why I did it src/sonic-utilities ``` * 83a548de - (HEAD -> 202305, origin/202305) Disable Key Validation feature during sonic-installation for Cisco Platforms (sonic-net#3115) (22 hours ago) [selvipal] ``` #### How I did it #### How to verify it #### Description for the changelog
…D automatically (sonic-net#17891) #### Why I did it src/sonic-platform-daemons ``` * 824c20a - (HEAD -> 202305, origin/202305) Support 800G ifname in xcvrd (sonic-net#420) (20 hours ago) [Anoop Kamath] ``` #### How I did it #### How to verify it #### Description for the changelog
Signed-off-by: philo <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why I did it
Work item tracking
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Tested branch (Please provide the tested image version)
Description for the changelog
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)