MITEL-IperaVoiceLAN-MIB

Monitored by Observium
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Graphs Status
Explore Observium network monitoring
Source file
MITEL-IperaVoiceLAN-MIB
Last revised
Not declared
Objects (42)
6 directly used by Observium
.1.3.6.1.4.1.1027.4.1.1.2
.1.3.6.1.4.1.1027.4.1.1.2.1
.1.3.6.1.4.1.1027.4.1.1.2.1.2
.1.3.6.1.4.1.1027.4.1.1.2.1.2.1
mitelIpera3000IPUsrLicUsed OBS ✓ mandatory
.1.3.6.1.4.1.1027.4.1.1.2.1.2.2
.1.3.6.1.4.1.1027.4.1.1.2.1.2.3
mitelIpera3000IPDevLicUsed OBS ✓ mandatory
.1.3.6.1.4.1.1027.4.1.1.2.1.2.4
mitelIpera3000CEID mandatory
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.1.3
mitelIpera3000PNI mandatory
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.1.4
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.1.5
.1.3.6.1.4.1.1027.4.1.1.2.2
mitelIpera3000AlmLevel OBS ✓ mandatory
.1.3.6.1.4.1.1027.4.1.1.2.2.1
.1.3.6.1.4.1.1027.4.1.1.2.2.2
.1.3.6.1.4.1.1027.4.1.1.2.2.3
.1.3.6.1.4.1.1027.4.1.1.2.2.4
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1
Integer32
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.1
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.2
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.3
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.4
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.5
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.6
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.7
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.2.4.1.8
.1.3.6.1.4.1.1027.4.1.1.2.2.5
.1.3.6.1.4.1.1027.4.1.1.2.2.6
.1.3.6.1.4.1.1027.4.1.1.2.2.7
.1.3.6.1.4.1.1027.4.1.1.2.2.8
.1.3.6.1.4.1.1027.4.1.1.2.3
.1.3.6.1.4.1.1027.4.1.1.2.4
.1.3.6.1.4.1.1027.4.1.1.2.4.1
.1.3.6.1.4.1.1027.4.1.1.2.4.1.1
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.4.1.1.1
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.4.1.1.2
OctetString
.1.3.6.1.4.1.1027.4.1.1.2.4.1.1.3
.1.3.6.1.4.1.1027.4.1.1.2.4.1.1.4
Enumeration
.1.3.6.1.4.1.1027.4.1.1.2.4.1.1.5
.1.3.6.1.4.1.1027.4.1.1.2.5
.1.3.6.1.4.1.1027.5.1.4
.1.3.6.1.4.1.1027.5.2.4.1
.1.3.6.1.4.1.1027.5.2.4.2
.1.3.6.1.4.1.1027.5.3.3
Dependencies (11) 4 direct · 7 transitive 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
Type Definitions (4)
OctetString range: 8range: 11
Enumeration
almClear(1)
almMinor(2)
almMajor(3)
almCritical(4)
Enumeration
pushButtonReset(1)
softwareInitiatedReset(2)
powerOnReset(3)
systemFaultReset(4)
uknownReset(5)
Enumeration
resourcesLowReboot(1)
softwareFailureReboot(2)
hardwareFailureReboot(3)
softwareUpgradedReboot(4)
databaseRestoreReboot(5)
intermediateReboot(6)
l2SwitchFailureReboot(7)
remoteAlarmButtonReboot(8)
programmedReboot(9)
maintenanceCommandReboot(10)
maintenanceCommandShutdown(11)
shutdownCauseNotReported(12)
Notifications / Traps (6)
NameOIDDescription
.1.3.6.1.4.1.1027.1.2.3.0.301
This notification is generated whenever
an alarm condition is detected or cleared. The
manager is expected to retrieve the corresponding
alarm and category table information.
.1.3.6.1.4.1.1027.1.2.3.0.302
This notification is generated whenever
the system can detect a shutdown of the system.
.1.3.6.1.4.1.1027.1.2.3.0.303
This notification is generated whenever
the system has completed booting and is now
opperational. The Reset Cause can give a
post mortum reason for the startup.
.1.3.6.1.4.1.1027.1.2.3.0.501
This notification is generated when the
first set fails-over from a primary to
secondary node.
.1.3.6.1.4.1.1027.1.2.3.0.502
This notification is generated
when the primary ICP has now
recovered. This means that the
primary ICP has passed a system
health check as determined by the
resiliency application on this
node.
.1.3.6.1.4.1.1027.1.2.3.0.503
This notification is generated
when all phones, from a particular
primary ICP, that had failed
over to this node have completed
handoff back to the primary ICP.