Scribd
Upload
71 views2 pages

When XMPP Between Active VSD and VSC Drops, VSC Sends Degraded State Causing Openflow Mastership Flip On Vswitches

When the XMPP connection between an active VSD and VSC drops, the VSC will send a degraded state message to its vswitches, potentially causing them to flip mastership. This occurs because the VSC loses its connection to the VSD. It is recommended to shut down the VSD ejabberd service of the VSD connected to the most VSCs last during maintenance to minimize openflow switchovers.

Uploaded by

touaiti2009
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
71 views2 pages

When XMPP Between Active VSD and VSC Drops, VSC Sends Degraded State Causing Openflow Mastership Flip On Vswitches

When the XMPP connection between an active VSD and VSC drops, the VSC will send a degraded state message to its vswitches, potentially causing them to flip mastership. This occurs because the VSC loses its connection to the VSD. It is recommended to shut down the VSD ejabberd service of the VSD connected to the most VSCs last during maintenance to minimize openflow switchovers.

Uploaded by

touaiti2009
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

21-0176 When XMPP between active VSD and VSC drops, VSC sends Degraded state causing Openflow

mastership flip on
vswitches

Type: Informational
Urgency: Medium
Publish Date: 4 Mar 2021
Region: ALL
Expiration: N/A
Product category: IP Networking
Product line: Multiservice Core Switching Products
Product family: Nuage Portfolio
Product: Nuage Virtualized Services Platform (VSP)
Version: ALL
Product category: IP Networking
Product line: Multiservice Core Switching Products
Product family: Nuage Portfolio
Product: Nuage Virtualized Network Services (VNS)
Version: ALL

Overview:
If VSDs ejabberd service is shut down or disconnected, any VSC that is connected to that VSD over ejabberd/XMPP port 5222 will send an
openflow DEGRADED message to its vswitches (VRS/AVRS/VRS-G/NSG) causing a VSC switchover.

Impact:
Normally the VSC switchover will not be service impacting but in rare cases there may be some traffic impact.

Context:
This affects all VCS and VNS deployments on 5.3.2, 5.4, 6.0, 20.5 and 20.10 deployments.

Cause:
When a VSC loses connection to a VSD that it has an ejabberd/XMPP connection to, the VSC sends the openflow DEGRADED message to
its vswitches so they switchover to the standby VSC. This is in case the previously standby VSC still has an ejabberd/XMPP connection to a
VSD.

This behaviour might be unwanted during a maintenance window when ejabberd will be shut down on one VSD in a cluster, but the other
VSDs are still up and operational. In these cases, even though the downtime between VSC losing connection to one VSD and reconnecting
to a different VSD is very small, the VSC still sends the DEGRADED openflow message to its vswitches.

Please note there are some other cases which can cause the VSC to lose connection to a VSD and a DEGRADED state message to get
sent towards its vswitches.

• Due to any network events between VSD and VSC that breaks the XMPP/ejabberd connection over TCP port 5222
• The "xmpp-server" configuration is removed/altered on VSC
• Deactivation of VSD in Active-Standby VSD cluster switchover

Action To Be Taken:
In times of maintenance on VSD, be aware of the VSDs that each VSC is connected to over ejabberd/XMPP port 5222. The VSD with the
most VSC connections should have its ejabberd service shut down last, in order to minimize the amount of openflow switchovers at the

21-0176 Nokia - Proprietary Page 1 of 2


vswitches.

To check what VSCs are connected to each VSD perform:

VSD side:

[root@vsd01b ~]# netstat -anp | grep "5222 " | grep -v "127.0.0.1" | grep ESTABLISHED
tcp 0 0 192.168.0.31:5222 192.168.0.35:50360 ESTABLISHED 5958/beam.smp
tcp 0 0 192.168.0.31:5222 192.168.0.33:53371 ESTABLISHED 5958/beam.smp
tcp 0 0 192.168.0.31:5222 192.168.0.43:62561 ESTABLISHED 5958/beam.smp
tcp 0 0 192.168.0.31:5222 192.168.0.34:49548 ESTABLISHED 5958/beam.smp

Where 192.168.0.33, 192.168.0.34, 192.168.0.35 and 192.168.0.43 are all VSCs

VSC side:

*A:VSC1# show system connections port 5222

===============================================================================
Connections
===============================================================================
Prot RecvQ TxmtQ Local Address State
MSS Remote Address vRtrID
-------------------------------------------------------------------------------
TCP 0 0 192.168.0.33.53371 ESTABLISH
1460 192.168.0.31.5222 4095
-------------------------------------------------------------------------------

Solution Availability:
TBA

Contact:
Nokia Technical Support
Please contact the technical support team for your country. If you are unsure of who that is, you can locate the correct number by using our
Technical Support phone number look-up tool.

21-0176 Nokia - Proprietary Page 2 of 2

You might also like