CISCO-LATITUDE-MIB

        The MIB module for the managment of Cisco Latitude MeetingPlace
conferencing solution.
        
MeetignPlace MIB traps are generated under the following 
conditions.
        
    - T1 status
    - Gateway System Integrity
    - Major hardware alarm
    - Minor hardware alarm
    - Major software alarm
    - Minor software alarm
        
Each major and minor hardware and software notification
includes an integer alarm code that indicates which software
module and server reported the alarm.  For hardware alarms,
four additional codes identify the device type, the device
address, slot number, and port number.
    
Source file
CISCO-LATITUDE-MIB
Last revised
Identity
latitudeComm
Base OID
1.3.6.1.4.1.7185
Imported Objects
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI enterprises Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC DisplayString
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-LATITUDE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-LATITUDE-MIB::latitudeComm'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-LATITUDE-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-LATITUDE-MIB::latitudeComm'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (19)
.1.3.6.1.4.1.7185
.1.3.6.1.4.1.7185.1
.1.3.6.1.4.1.7185.1.1
.1.3.6.1.4.1.7185.2
.1.3.6.1.4.1.7185.3
.1.3.6.1.4.1.7185.3.1
.1.3.6.1.4.1.7185.3.1.1
.1.3.6.1.4.1.7185.3.1.1.1
.1.3.6.1.4.1.7185.3.1.1.2
.1.3.6.1.4.1.7185.3.1.2
.1.3.6.1.4.1.7185.3.1.3
.1.3.6.1.4.1.7185.3.1.3.0
Integer32
.1.3.6.1.4.1.7185.3.1.3.1
Integer32
.1.3.6.1.4.1.7185.3.1.3.2
Enumeration
.1.3.6.1.4.1.7185.3.1.3.3
Integer32
.1.3.6.1.4.1.7185.3.1.3.4
Integer32
.1.3.6.1.4.1.7185.3.1.3.5
Integer32
.1.3.6.1.4.1.7185.3.1.3.6
OctetString
.1.3.6.1.4.1.7185.3.1.3.7
Dependencies (3) 3 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. SNMPv2-CONFrfc
  3. SNMPv2-TCrfc
  4. CISCO-LATITUDE-MIBciscoselected
Conformance Groups (2)
Alarms objects within MeetingPlace.
.1.3.6.1.4.1.7185.3.1.1.2.1
Notifications applicable to meetingplace.
.1.3.6.1.4.1.7185.3.1.1.2.2
Compliance Statements (1)

OID .1.3.6.1.4.1.7185.3.1.1.1.1
The compliance statement for entities which implement the
MeetingPlace MIB.
Required groups
Notifications / Traps (6)
NameOIDDescription
.1.3.6.1.4.1.7185.3.1.3.0.1
MeetingPlace T1 Down Alarm.
This indicates generically there is a problem with a
telephony port. There are several possible alarm
conditions that will generate this trap. This is from
Release 4.3.
.1.3.6.1.4.1.7185.3.1.3.0.2
MeetingPlace Gateway Alarm.
This indicates an alarm generated by a MeetingPlace
gateway. There are several alarms that will generate
this trap. This is from Release 4.3
.1.3.6.1.4.1.7185.3.1.3.0.3
MeetingPlace Major Hardware Alarm.
This is generated any time MeetingPlace reports a major
hardware alarm.
.1.3.6.1.4.1.7185.3.1.3.0.4
MeetingPlace Minor Hardware Alarm.
This is generated any time MeetingPlace reports
a minor hardware alarm.
.1.3.6.1.4.1.7185.3.1.3.0.5
MeetingPlace Major Software Alarm.
This is generated any time MeetingPlace reports a major
software alarm.
.1.3.6.1.4.1.7185.3.1.3.0.6
MeetingPlace Minor Software Alarm.
This is generated any time MeetingPlace reports
a minor hardware alarm.