The MIB Module for the management of the Cisco Unified SIP Proxy (CUSP) service. CUSP is a Session Initiation Protocol (SIP) proxy server that helps enterprises aggregate their SIP elements into a centralized architecture in order to simplify and improve the flexibility of their network. MIB has OID's to monitor CUSP specific info like Server Group, Calls Per Second (CPS), Total Calls, Failed Calls, Dropped Calls, License, Up time CPU and Memory info and also traps on Server group elements, CPU and Memory threshold exceed, License exceed, Back up , process going down, Extensive logging and connection. |
ciscoMgmt | CISCO-SMI |
MODULE-COMPLIANCE, NOTIFICATION-GROUP, OBJECT-GROUP | SNMPv2-CONF |
MODULE-IDENTITY, OBJECT-TYPE, Counter32, NOTIFICATION-TYPE, Unsigned32, Integer32 | SNMPv2-SMI |
TruthValue, TimeStamp, DateAndTime | SNMPv2-TC |
![]() | .1.3.6.1.4.1.9.9.827 | |
![]() | .1.3.6.1.4.1.9.9.827.0 | |
![]() | .1.3.6.1.4.1.9.9.827.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.10 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.11 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.12 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.3 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.4 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.5 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.6 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.7 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.8 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.10.9 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.11 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.11.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.11.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.12 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.12.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.12.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.3 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.4 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.5 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.6 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.7 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.8 | |
![]() | .1.3.6.1.4.1.9.9.827.1.1.9 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1.3 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1.4 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1.5 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.1.1.6 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.3 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.4 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.5 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.6 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.7 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.8 | |
![]() | .1.3.6.1.4.1.9.9.827.1.2.2.1.9 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.1 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.10 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.11 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.12 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.13 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.2 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.3 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.4 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.5 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.6 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.7 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.8 | |
![]() | .1.3.6.1.4.1.9.9.827.1.3.9 | |
![]() | .1.3.6.1.4.1.9.9.827.2 | |
![]() | .1.3.6.1.4.1.9.9.827.2.1 | |
![]() | .1.3.6.1.4.1.9.9.827.2.2 |
Name | OID | Description |
---|---|---|
.1.3.6.1.4.1.9.9.827.0.1 | This notification is generated when the CUSP system goes up/down. This notification can be enabled/disabled by setting cuspSystemStateAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.10 | This notification is generated when a connection exception occurs. This notification can be enabled/disabled by setting cuspConnectionExceptionAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.11 | This notification is generated when CUSP system queues gets full. Queue full indicates CUSP is either over loaded or encountering network issues. This notification can be enabled/disabled by setting cuspSipMessageQueueOverflowAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.2 | This notification is generated when server group element status changes. This notification can be enabled/disabled by setting cuspServerGroupElementAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.3 | This notification is generated when all the elements in the server group goes down or when any one element in the server group comes up after all the elements in the group were down. This notification can be enabled/disabled by setting cuspServerGroupAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.4 | This notification is generated when CUSP memory usage exceeds the cuspMemoryThresholdValue. This notification can be enabled/disabled by setting cuspMemoryThresholdAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.5 | This notification is generated when average CPS exceeds cuspLicenseLimit. This notification can be enabled/disabled by setting cuspLicenseExceededAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.6 | This notification is generated when CUSP license state changes. This notification can be enabled/disabled by setting cuspLicenseStateAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.7 | This notification is generated when extensive debug level logging is enabled in CUSP. Extensive logging might impact the performance and system stability. This notification can be enabled/disabled by setting cuspExtensiveLoggingAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.8 | This notification is generated when the CUSP Disk usage exceeds the cuspDiskSpaceThresholdValue. This notification can be enabled/disabled by setting cuspDiskSpaceThresholdAlertEnable. | |
.1.3.6.1.4.1.9.9.827.0.9 | This notification is generated when back up process fails. This notification can be enabled/disabled by setting cuspBackupProcessFailAlertEnable. |