Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[everflow] Active Monitor Port is not updated when the active monitor port which is a member of L3 Portchannel is shutdown #1499

Open
ashfakg opened this issue Nov 11, 2020 · 1 comment · May be fixed by #1846
Open

[everflow] Active Monitor Port is not updated when the active monitor port which is a member of L3 Portchannel is shutdown #1499

ashfakg opened this issue Nov 11, 2020 · 1 comment · May be fixed by #1846

Comments

@ashfakg
Copy link

ashfakg commented Nov 11, 2020

Description:
When we create a mirror session with DIP reachable via next hop of L3 Portchannel interface, the mirror session takes one of the portchannel member as Active monitor port.
Now when the active monitor port which is a member of Portchannel is shutdown, monitor port doesn't switch to another member of the portchannel. And the mirror packet forwarding through the L3 portchannel interface fails.

Log1

Now shutdown the active monitor port which is the member of L3 portchannel.
Log2

Log3
@anshuv-mfst
Copy link

@abdosi - could you please look into the issue, thanks.

@wendani wendani linked a pull request Aug 1, 2021 that will close this issue
Open
EdenGri pushed a commit to EdenGri/sonic-swss that referenced this issue Feb 28, 2022
@yozhao101
[config] Disable/enable container monitoring when stopping/starting s…
4a0c010 
…ervices (sonic-net#1499)

Signed-off-by: Yong Zhao yozhao@microsoft.com

What I did
When we ran the commands sudo config reload or sudo config load_minigraph, the containers swss, snmp, lldp, teamd, syncd, snmp, bgp, radv, pmon, dhcp_relay, telemetry, mgmt-framework and restapi would be stopped and then restarted. The script container_checker ran by Monit will generate false alerting messages into syslog to indicate some containers were not running during such stopping and restarting process. So this PR aims to prevent Monit from generating false alarm messages.

How I did it
Before stopping services, we disable Monit to monitor the running status of containers. After restarting services, we enable Monit to monitor the running status of containers again.

How to verify it
I deliberately reduce the monitoring interval of Monit from 60 seconds to 10 seconds to ensure the alerting messages from the script container_checker was generated during sudo config reload and sudo config load_minigraph. After this change was added into _stop_services() and _restart_services() , I checked that the alerting messages from container_checker did not appear in the syslog.

I verified this change on the virtual switch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[mirror] Observe lag member status change wendani/sonic-swss
2 participants
@anshuv-mfst @ashfakg