Logic that is being used to generate Cisco CallProcessor BackupActivated events

Products

• VMware Smart Assurance
• Network Observability

Issue/Introduction

This article addresses the following questions: 

• How does Smarts IP generate the BackupActivated Event for Cisco CallProcessor?
• What OIDs does Smarts IP use to determine whether to generate the BackupActivated Event for CallProcessor?
• How can I confirm that SRST is active?

Environment

All Supported Smarts releases

Resolution

Smarts IP considers the following factors when determining whether to generate a BackupActivated event. These factors are based on the results from the constant polling of the CSRST state on OID 1.3.6.1.4.1.9.9.441.1.2.1 and OID 1.3.6.1.4.1.9.9.441.1.3.1 as defined in the Smarts IP polling cycle. The factors considered are:

• Whether Cisco SRST support is enabled or disabled as returned from csrstEnabled OID (1.3.6.1.4.1.9.9.441.1.2.1)
• Current state of Cisco SRST feature on the router based on the return from the csrstState OID (1.3.6.1.4.1.9.9.441.1.3.1):
  • Active - At least one IP or SIP phone is registered
  • Inactive - Cisco SRST has no IP or SIP phones registered
• Status of SRST csrstFailNotif based on listening to SRST Trap OID (1.3.6.1.4.1.9.9.441.0.2).

Smarts IP will generate the BackupActivated event when ALL of the following conditions exist:

• csrstEnabled is true
• csrstState is active
• csrstFailNotif is not notified of any error