-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shutdown the portchannel,but the portchannel member'Oper status is not down #5319
Comments
This is an expected behavior. |
When a physical port is added to a portchannel member port, if the portchannel is shut down, the physical port should also be shut down and cannot communicate normally. This meets the expectations of the portchannel member port。But in fact, the portchannel is shut down, and the physical port can still communicate normally |
So are you saying the portchannel member must be "admin" down when the portchannel itself is shutdown? The description says you are expecting "oper" down. Can you please clarify? |
What I expect is that when the portchannel is shut down, the state of the member port that belongs to it is also shut down, and the member port cannot communicate normally until the portchannel is up or it is removed from the portchannel。 |
Got it, so that's a feature request that needs to be planned. |
Description
shutdown the portchannel,but the portchannel member'Oper status is not down
Steps to reproduce the issue:
1.config a new portchannel
2.add portchannel member
3.shutdown the portchannel
4.View port status
Describe the results you received:
portchannel member (portchannel member) Oper status is not down
Describe the results you expected:
portchannel member (portchannel member) Oper status is down
Additional information you deem important (e.g. issue happens only occasionally):
Sep 1 17:16:13.229631 sonic ERR monit[555]: 'sflowmgrd' process is not running
root@sonic:/home/admin# show version
SONiC Software Version: SONiC.master.399-07b9d7f4
Distribution: Debian 10.5
Kernel: 4.19.0-9-2-amd64
Build commit: 07b9d7f
Build date: Sun Aug 30 07:41:30 UTC 2020
Built by: johnar@jenkins-worker-8
Platform: x86_64-ruijie_b6510-48vs8cq-r0
HwSKU: B6510-48VS8CQ
ASIC: broadcom
Serial Number: G1W10072
Uptime: 17:26:38 up 2:51, 1 user, load average: 0.46, 0.37, 0.29
Docker images:
REPOSITORY TAG IMAGE ID SIZE
docker-teamd latest 0da13af040db 386MB
docker-teamd master.399-07b9d7f4 0da13af040db 386MB
docker-sonic-mgmt-framework latest b3309c50c848 481MB
docker-sonic-mgmt-framework master.399-07b9d7f4 b3309c50c848 481MB
docker-router-advertiser latest 81563660196e 355MB
docker-router-advertiser master.399-07b9d7f4 81563660196e 355MB
docker-platform-monitor latest bfc946290aa4 429MB
docker-platform-monitor master.399-07b9d7f4 bfc946290aa4 429MB
docker-lldp latest 17607fd34cc8 383MB
docker-lldp master.399-07b9d7f4 17607fd34cc8 383MB
docker-dhcp-relay latest 57d5a7e2d58d 362MB
docker-dhcp-relay master.399-07b9d7f4 57d5a7e2d58d 362MB
docker-database latest ddb145fe6d62 355MB
docker-database master.399-07b9d7f4 ddb145fe6d62 355MB
docker-orchagent latest 2b0a4c92794f 400MB
docker-orchagent master.399-07b9d7f4 2b0a4c92794f 400MB
docker-nat latest eb5c6b6736c2 389MB
docker-nat master.399-07b9d7f4 eb5c6b6736c2 389MB
docker-sonic-telemetry latest 6c4292e948fd 425MB
docker-sonic-telemetry master.399-07b9d7f4 6c4292e948fd 425MB
docker-fpm-frr latest 076744e3f438 402MB
docker-fpm-frr master.399-07b9d7f4 076744e3f438 402MB
docker-sflow latest 1046ede2b365 390MB
docker-sflow master.399-07b9d7f4 1046ede2b365 390MB
docker-snmp latest ffbf20d1540a 395MB
docker-snmp master.399-07b9d7f4 ffbf20d1540a 395MB
docker-syncd-brcm latest d62f6c218ce2 447MB
docker-syncd-brcm master.399-07b9d7f4 d62f6c218ce2 447MB
root@sonic:/home/admin#
```
The text was updated successfully, but these errors were encountered: