Quantcast
Viewing all articles
Browse latest Browse all 251313

VMNIC alarming

Hello all,

     I have a need to raise alerts when a vmnic fails but I'm having trouble understanding the logic behind existing vmnic alerting. Below are examples of the logic I have seen but I would greatly appreciate some pointers/direction to solving my problem.

 

 

vSS with single vmnic

  • vmnic nic failure causes the alarm "Network Connectivity Lost"

 

vSS with two vmnics

  • single vmnic nic failure triggers the alarm "Network uplink redundancy lost"
  • two vmnic failures cause the alarm "Network Connectivity Lost"

 

vSS with three vmnics

  • one vmnic nic failure triggers the alarm "Network uplink redundancy degraded"
  • two vmnic nic failures triggers the alarm "Network uplink redundancy lost"
  • three vmnic failuires triggers the alarm "Network Connectivity Lost"

 

vSS with four vmnics

  • one vmnic nic failure triggers the alarm "Network uplink redundancy degraded"
  • two vmnic nic failures triggers no new alarm to be presented
  • three vmnic nic failures triggers the alarm "Network uplink redundancy lost"
  • four vmnic failuires triggers the alarm "Network Connectivity Lost"

 

All of this seems normal to me with the exception that I never get an alarm for each individual vmnic failure. To take it a bit further. If I had a vSS with 5 vmnics and two failed that would only be one alarm and if a single vmnic recovered while one is still down the alarm would clear even though there is still a problem! (Network uplink redundancy degraded).

 

I can go into some tweaking I did with the degraded alarm to present for each vmnic but I guess I would have expected the "Network Connectivity Lost" to actually present for each vmnic failure and not only when all vmnics for a vSS are down.

 

Please help to clear my confusion and thanks for taking the time to review and respond!

 

Woody


Viewing all articles
Browse latest Browse all 251313

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>