CISCO-LATITUDE-MIB.mib object view, vendor Latitude-Communications
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2024 can import MIB file CISCO-LATITUDE-MIB and use it to monitor vendor specific OID's.
CISCO-LATITUDE-MIB file content
Object view of CISCO-LATITUDE-MIB:
Scalar Object |
mpExCode |
.1.3.6.1.4.1.7185.3.1.3.1 |
MeetingPlace Exception Code.
This is the primary code associated with each
MeetingPlace exception condition.
The mpAlarmDesc OID will provide a textual description
of the exception code. Refer to the MeetingPlace
System Managers Guide for more details.
|
mpSysUnit |
.1.3.6.1.4.1.7185.3.1.3.2 |
MeetingPlace Server Unit Number.
This is the unit (server) number of the server that
reported the exception.
|
mpHwDev |
.1.3.6.1.4.1.7185.3.1.3.3 |
MeetingPlace Hardware Device Code.
This defines the class of device that generated a
hardware fault.
'mpTemperature' - Temperature Sensor
'mpPowerSupply' - Power Supply
'mpSerialPort' - Serial Port
'mpTapeDrive' - Tape Drive
'mpHardDrive' - Hard Drive
'mpDisketteDrive' - Diskette Drive
'mpEthernet' - Ethernet Port
'mpModem' - Modem Port
'mpSystemMisc' - System Misc
'mpDSPMSC' - Master Switch Controller
'mpDSPPRC' - Port Resource Card
'mpT1Blade' - T1 Blade
'mpAnalogBlade' - Analog Blade
'mpT1Network' - T1 Network Interface
'mpSystemIntegrityCard' - System Integrity Card
'mpMainMemory' - Main Memory
'mpE1Blade' - E1 Blade
'mpE1Network' - E1 Network Interface
'mpVoIPBlade' - VoIP Blade
|
mpHwUnit |
.1.3.6.1.4.1.7185.3.1.3.4 |
MeetingPlace Hardware Device Unit Number.
This is the unit number of the hardware device that
generated a fault. For a disk this would be the SCSI
ID. For a blade this would the the logical card number
as defined in the system configuration.
|
mpHwSlot |
.1.3.6.1.4.1.7185.3.1.3.5 |
MeetingPlace Hardware Device Slot Number.
This is the location of the hardware device that
generated a fault. For a blade this would be the slot
number.
|
mpHwPort |
.1.3.6.1.4.1.7185.3.1.3.6 |
MeetingPlace Hardware Device Port Number.
This is the logical port number associated with a
hardware fault. For a T1 alarm, this is the logical
span number.
|
mpAlarmDesc |
.1.3.6.1.4.1.7185.3.1.3.7 |
MeetingPlace Alarm Description.
This is a one-line text description of the exception
condition. It comprises a string indexed by the
exception code filled in with context-specific values.
|
Trap |
mpT1Down |
.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.
|
mpGWSimAlarm |
.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
|
mpMajHwAlarm |
.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.
|
mpMinHwAlarm |
.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.
|
mpMajSwAlarm |
.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.
|
mpMinSwAlarm |
.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.
|
Object Identifier |
latitudeComm |
.1.3.6.1.4.1.7185 |
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.
|
latitudeReg |
.1.3.6.1.4.1.7185.1 |
latitudeModules |
.1.3.6.1.4.1.7185.1.1 |
latitudeGeneric |
.1.3.6.1.4.1.7185.2 |
latitudeProducts |
.1.3.6.1.4.1.7185.3 |
meetingplace |
.1.3.6.1.4.1.7185.3.1 |
meetingplaceConfs |
.1.3.6.1.4.1.7185.3.1.1 |
meetingplaceObjs |
.1.3.6.1.4.1.7185.3.1.2 |
meetingplaceEvents |
.1.3.6.1.4.1.7185.3.1.3 |
meetingplaceEventsV2 |
.1.3.6.1.4.1.7185.3.1.3.0 |
ciscoLatitudeMIBCompliances |
.1.3.6.1.4.1.7185.3.1.1.1 |
ciscoLatitudeMIBGroups |
.1.3.6.1.4.1.7185.3.1.1.2 |
Group |
ciscoLatitudeAlarmGroupRev1 |
.1.3.6.1.4.1.7185.3.1.1.2.1 |
Alarms objects within MeetingPlace.
|
ciscoLatitudeNotifsGroupRev1 |
.1.3.6.1.4.1.7185.3.1.1.2.2 |
Notifications applicable to meetingplace.
|