CISCO-VOICE-APPS-MIB

        The MIB Module for the management of Cisco Voice
Applications.  This MIB is designed to work in 
conjunction with the SYSAPPL-MIB to provide status
monitoring, provisioning and notification.
    
Source file
CISCO-VOICE-APPS-MIB
Last revised
Identity
ciscoVoiceAppsMIB
Base OID
1.3.6.1.4.1.9.9.190
Imported Objects
CISCO-SMI ciscoMgmt
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DisplayString TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-VOICE-APPS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-VOICE-APPS-MIB::ciscoVoiceAppsMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-VOICE-APPS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-VOICE-APPS-MIB::ciscoVoiceAppsMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (24)
.1.3.6.1.4.1.9.9.190
.1.3.6.1.4.1.9.9.190.1
.1.3.6.1.4.1.9.9.190.1.1
.1.3.6.1.4.1.9.9.190.1.1.1
.1.3.6.1.4.1.9.9.190.1.1.1.1
.1.3.6.1.4.1.9.9.190.1.1.1.1.1
OctetString
.1.3.6.1.4.1.9.9.190.1.1.1.1.2
OctetString
.1.3.6.1.4.1.9.9.190.1.1.1.1.3
OctetString
.1.3.6.1.4.1.9.9.190.1.1.1.1.4
.1.3.6.1.4.1.9.9.190.1.1.1.1.5
.1.3.6.1.4.1.9.9.190.1.1.3
.1.3.6.1.4.1.9.9.190.1.2
Enumeration
.1.3.6.1.4.1.9.9.190.1.2.1
OctetString
.1.3.6.1.4.1.9.9.190.1.2.2
.1.3.6.1.4.1.9.9.190.1.2.3
OctetString
.1.3.6.1.4.1.9.9.190.1.2.4
Enumeration
.1.3.6.1.4.1.9.9.190.1.2.5
OctetString
.1.3.6.1.4.1.9.9.190.1.2.6
Enumeration
.1.3.6.1.4.1.9.9.190.1.2.7
.1.3.6.1.4.1.9.9.190.2
.1.3.6.1.4.1.9.9.190.2.0
.1.3.6.1.4.1.9.9.190.3
.1.3.6.1.4.1.9.9.190.3.1
.1.3.6.1.4.1.9.9.190.3.2
Dependencies (5) 5 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-CONFrfc
  4. SNMPv2-TCrfc
  5. SNMP-FRAMEWORK-MIBrfc
  6. CISCO-VOICE-APPS-MIBciscoselected
Conformance Groups (3)
A collection of objects which provide info about the
application. It comprises of all the modules and servers
associated with the application.
.1.3.6.1.4.1.9.9.190.3.2.1
A collection of notification objects which provide info
about the application notification.
.1.3.6.1.4.1.9.9.190.3.2.2
A collection of notifications.
.1.3.6.1.4.1.9.9.190.3.2.3
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.190.3.1.1
The compliance statement for entities which implement
the CISCO APPLICATION MIB.
Required groups
mandatory cvaModuleInfoGroup
mandatory cvaNotificationInfoGroup
optional cvaNotificationGroup Support for these notifications is optional.
Notifications / Traps (5)
NameOIDDescription
.1.3.6.1.4.1.9.9.190.2.0.1
A cvaModuleStart notification signifies that an
application module or subsystem has successfully
started and transitioned into in-service state.
This notification is working in conjunction with
the cvaModuleStop notification to notify the start
and stop status of a particular application module.
.1.3.6.1.4.1.9.9.190.2.0.2
A cvaModuleStop notification signifies that an
application module or subsystem has stopped. This
notification is working in conjunction with the
cvaModuleStart notification to notify the start
and stop status of a particular application module.
If failure cause is known then it will be specified
in the cvaModuleFailureCause variable. Additional
failure information associated with cvaModuleFailureCause
can be specified in the cvaModuleFailureCauseMessage.
.1.3.6.1.4.1.9.9.190.2.0.3
A cvaModuleRunTimeFailure notification signifies that a run
time failure has occurred. If failure cause is known then it
will be specified in the cvaModuleRunTimeFailureCause
variable. Additional failure information associated with
cvaModuleRunTimeFailureCause can be specified in the
cvaModuleFailureCauseMessage.
.1.3.6.1.4.1.9.9.190.2.0.4
A cvaProcessStart notification signifies that a process has
just started. This notification is intended to work in
conjunction with the caProcessStop notification to notify
the start and stop status of a particular process.
.1.3.6.1.4.1.9.9.190.2.0.5
A cvaProcessStop notification signifies that a process has
just stopped. This notification is intended to work in
conjunction with the cvaProcessStart notification to notify
the start and stop status of a particular process.