Open leoli-nps opened 5 years ago
This is a known issue that may happen during bootup. It is supposed to be fixed as part of https://github.com/Azure/sonic-buildimage/pull/2829. Can you check if you have this fix?
@prsunny Thank you for your reply. I checked it, we have not merged this fix yet. However, I made the corresponding changes directly on the device, as follows:
admin@sonic:~$ cat /etc/systemd/system/teamd.service
[Unit]
Description=TEAMD container
Requires=updategraph.service
After=updategraph.service swss.service
Before=ntp-config.service
[Service]
User=admin
ExecStartPre=/usr/bin/teamd.sh start
ExecStart=/usr/bin/teamd.sh wait
ExecStop=/usr/bin/teamd.sh stop
[Install]
WantedBy=multi-user.target
admin@sonic:~$
Then execute warm-reboot, but the phenomenon is still the same as described above. I think they should be two different issues.
Further, I checked the code of teamsyncd. When executing warm-reboot, the lag information from the kernel will be written to m_tempViewState instead of APP_DB. After 70 seconds (DEFAULT_WR_PENDING_TIMEOUT), execute applyState(). But currently, the information that needs to be synchronized from the kernel is only admin_status and oper_status, no mtu, I think the problem may be here. Hope to help.
@prsunny , @leoli-nps I am also observing the above issue with SONiC image - April 2020/201911 branch. Can you please confirn if this is fixed. After warm-reboot the MTU for LAG rif Interface is getting changed to default 1492 from 9100. APP_DB - Before and After warm reboot Before: "LAG_TABLE:PortChannel101": { "type": "hash", "value": { "admin_status": "up", "mtu": "9100", "oper_status": "up" } }, "LAG_TABLE:PortChannel201": { "type": "hash", "value": { "admin_status": "up", "mtu": "9100", "oper_status": "up" } }, After: "LAG_TABLE:PortChannel101": { "type": "hash", "value": { "admin_status": "up", "oper_status": "up" } }, "LAG_TABLE:PortChannel201": { "type": "hash", "value": { "admin_status": "up", "oper_status": "up" } }, Config_DB: "PORTCHANNEL|PortChannel101": { "type": "hash", "value": { "admin_status": "up", "members@": "Ethernet68", "min_links": "1", "mtu": "9100" } },
"PORTCHANNEL|PortChannel201": {
"type": "hash",
"value": {
"admin_status": "up",
"members@": "Ethernet252",
"min_links": "1",
"mtu": "9100"
}
},
SONiC Software Version: SONiC.201911.470-dirty-20200413.175026 Distribution: Debian 9.12 Kernel: 4.9.0-11-2-amd64 Build commit: d09fba37 Build date: Tue Apr 14 02:45:44 UTC 2020 Built by: nd@mavtest2-bxdsw
Platform: x86_64-accton_wedge100bf_65x-r0 HwSKU: mavericks ASIC: barefoot Serial Number: AH47011410 Uptime: 19:07:37 up 21:04, 4 users, load average: 2.35, 2.30, 2.28
Docker images: REPOSITORY TAG IMAGE ID SIZE docker-syncd-bfn 201911.470-dirty-20200413.175026 67693f0ec154 807MB docker-syncd-bfn latest 67693f0ec154 807MB docker-router-advertiser 201911.470-dirty-20200413.175026 aacf0c7bbe7d 283MB docker-router-advertiser latest aacf0c7bbe7d 283MB docker-platform-monitor 201911.470-dirty-20200413.175026 9d05be095518 334MB docker-platform-monitor latest 9d05be095518 334MB docker-fpm-frr 201911.470-dirty-20200413.175026 9b20037b8a53 327MB docker-fpm-frr latest 9b20037b8a53 327MB docker-sflow 201911.470-dirty-20200413.175026 988e7952291f 307MB docker-sflow latest 988e7952291f 307MB docker-lldp-sv2 201911.470-dirty-20200413.175026 18da217cfad7 304MB docker-lldp-sv2 latest 18da217cfad7 304MB docker-dhcp-relay 201911.470-dirty-20200413.175026 84bf3d863621 293MB docker-dhcp-relay latest 84bf3d863621 293MB docker-database 201911.470-dirty-20200413.175026 b05010a9876e 283MB docker-database latest b05010a9876e 283MB docker-snmp-sv2 201911.470-dirty-20200413.175026 eadb4ac374ca 340MB docker-snmp-sv2 latest eadb4ac374ca 340MB docker-orchagent 201911.470-dirty-20200413.175026 9cacaacdf877 325MB docker-orchagent latest 9cacaacdf877 325MB docker-teamd 201911.470-dirty-20200413.175026 787bee61d7db 307MB docker-teamd latest 787bee61d7db 307MB docker-nat 201911.470-dirty-20200413.175026 bc381c4411a4 309MB docker-nat latest bc381c4411a4 309MB