Preview Tool

Cisco Bug: CSCte37117 - Syslog not generated for server status change from non-monitored to aliv

Last Modified

Mar 29, 2015

Products (1)

  • Cisco Data Center Network Manager

Known Affected Releases


Description (partial)

RADIUS/TACACS+ server status shown in DCNM and in the switch are not in sync.

When a RADIUS or TACACS+ server is created in the switch without idle or deat time, they will be in non-monitored state. So, DCNM will also so the status of the corresponding server as "non-monitored". But, if user configures the idle-time or dead-time for that server on the switch, the switch will start monitoring the server. So, as soon as user configures idle-time or dead-time for that server, the server status will move to non-monitored state to Alive state. But, since there will be no syslog generated for this status change, DCNM will not aware of this status change, so it will continue to show the status as non-monitored.

Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.