Can't find what you need?


• Ask the Community
• Create a Case
Reset Search
 

 

Article

Cluster Member SPB Adjacencies Dropped and Stopped Forwarding Packets Following VMware Host Placed In Maintenance Mode

« Go Back

Information

 
TitleCluster Member SPB Adjacencies Dropped and Stopped Forwarding Packets Following VMware Host Placed In Maintenance Mode
Symptoms
  • VMware ESX host connected to VSP-1 was put into maintenance mode
  • VSP-1 (part of cluster) lost all SPB/IS-IS adjacencies and stopped forwarding packets with nothing in log file other than adjacencies going down
  • Cluster peer (VSP-2) also had no indication of why adjacencies went down
VSP-1
[03/24/19 17:04:35.223:EST] 0x00004726 00000000 GlobalRouter SNMP INFO SPBM detected adj DOWN on Port2/2 , neighbor 1111.0a00.1500 (7254aa1) 
[03/24/19 17:04:36.222:EST] 0x00004726 00000000 GlobalRouter SNMP INFO SPBM detected adj DOWN on Port2/1 , neighbor 1111.0a00.1800 (7254cc2) 
[03/24/19 17:04:39.189:EST] 0x00004726 00000000 GlobalRouter SNMP INFO SPBM detected adj DOWN on Port1/48, neighbor 1111.0a00.0500 (8404dd) 

VSP-2
CP1  [03/24/19 17:04:39.283:EST] 0x00004726 00000000 GlobalRouter SNMP INFO SPBM detected adj DOWN on Port2/1 , neighbor 1111.0a00.1700 (7254bb1)
CP1  [03/24/19 17:04:39.323:EST] 0x001dc60e 00000000 GlobalRouter ISIS INFO SPBM smlt peer down 11:11:0a:00:17:00
  • VSP-1 was rebooted and SPB/IS-IS adjacencies re-established and switch began processing packets again
Environment
  • VSP 7200
  • Release 6.1.2
Cause
Root cause undetermined
Resolution
  • Upgrade to release 7.1.2.0 or 6.1.6.0 for fixes that could be linked to symptoms noted
Additional notes
Fixed in 6.1.3 and later:
  • VSP4000-200: High CPU Utilization lasting 2-3 min on multiple VSP nodes because ISIS packets sent to wrong priority internal queue. VSP4000 specific issue
  • NOTE: Not necessarily specific to VSP 4000

Fixed in 6.1.5 and higher
  • VSP8000-329: All VLACP interfaces timed out on the box due to buffer exhaustion
  • NOTE: Not necessarily specific to VLACP, but more-so the buffer exhaustion hits the more sensitive protocols such as VLACP first.

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255