OXO-CALL-HANDLING-MIB
140 objects
This is ALE Communication implementation of enterprise specific MIB for the OmniPCX Office Call Handling.
Imported Objects
| OXO-MIB | EventSeverity oxoMIB |
| SNMPv2-SMI | Integer32 MODULE-IDENTITY NOTIFICATION-TYPE OBJECT-TYPE TimeTicks |
| SNMPv2-TC | DateAndTime DisplayString TEXTUAL-CONVENTION |
| OID | Name | Access | Status | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.6486.64.4200.1.2 | IdentityoxoCallHandlingMIB | This is ALE Communication implementation of enterprise specific MIB for the OmniPCX Office Call Handling. | ||
| 1.3.6.1.4.1.6486.64.4200.1.2.1 | NodeochmObjects | |||
| 1.3.6.1.4.1.6486.64.4200.1.2.1.1 | ScalarochmStatus | read-only | current | Global status of the OmniOfficePCX Call handling. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2 | TableochmAlarmTable | not-accessible | current | Alarm table. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1 | RowochmAlarmEntry | not-accessible | current | Each entry contains the description of one alarm. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.0 | ColumnochmAlarmTypeINDEX | read-only | current | To identify the related alarm table. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.1 | ColumnochmAlarmTableType | read-only | current | To identify the related alarm table. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.2 | ColumnochmAlarmIndex | read-only | current | Index into alarmTable. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.3 | ColumnochmAlarmSystTime | read-only | current | The value of sysUpTime when the alarm occurs. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.4 | ColumnochmAlarmDateTime | read-only | current | The local date and time when the alarm occurs. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.5 | ColumnochmAlarmEvent | read-only | current | An integer that acts as an alarm Id NMC to uniquely identify each alarm.(Different than OXO Id Event) |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.6 | ColumnochmAlarmSubEvent | read-only | current | An integer used to give a particular |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.7 | ColumnochmAlarmCabinetSlot | read-only | current | Cabinet slot to identify the board related to the alarm. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.8 | ColumnochmAlarmBoardSlot | read-only | current | Board slot to identify the access related to the alarm. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.9 | ColumnochmAlarmHalfBoard | read-only | current | Half board to identify the half board related to the alarm. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.10 | ColumnochmAlarmInfo1 | read-only | current | First additionnal information byte. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.11 | ColumnochmAlarmInfo2 | read-only | current | Second additionnal information byte. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.12 | ColumnochmAlarmInfo3 | read-only | current | Third additionnal information byte. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.13 | ColumnochmAlarmInfo4 | read-only | current | Fourth additionnal information byte. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.14 | ColumnochmAlarmType | read-only | current | The event Type values. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.15 | ColumnochmAlarmSeverity | read-only | current | Perceived severity values. |
| 1.3.6.1.4.1.6486.64.4200.1.2.2.1.16 | ColumnochmAlarmCause | read-only | current | Probable cause values for the alarms. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3 | NodeochmNotificationPrefix | |||
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0 | NodeochmNotifications | |||
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.1 | NotificationochmSystemRestart | current | The call handling has started running. Correlation: =========== ochmSystemRestart and ochmSystemRestarted can be correlated when the variable ProblemId has the… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.2 | NotificationochmSystemRestarted | current | The call handling has finished its start. Correlation: =========== ochmSystemRestart and ochmSystemRestarted can be correlated when the variable ProblemId has … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.3 | NotificationochmCabinetUnplugged | current | A cabinet has been plugged out. Correlation: =========== ochmCabinetUnplugged and ochmCabinetOperational can be correlated when the variable ProblemId has the … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.4 | NotificationochmCabinetOperational | current | A cabinet is now operational. Correlation: =========== ochmCabinetUnplugged and ochmCabinetOperational can be correlated when the variable ProblemId has the sa… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.5 | NotificationochmBoardFailure | current | A board has been plugged out. Correlation: =========== 1/ First correlation ochmBoardFailure and ochmBoardCleared can be correlated when the variable ProblemId… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.6 | NotificationochmBoardCleared | current | A permanent reset has been performed on a board. Correlation: =========== ochmBoardFailure and ochmBoardCleared can be correlated when the variable ProblemId h… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.7 | NotificationochmBoardOperational | current | A board is now operational. Correlation: =========== ochmBoardFailure and ochmBoardOperational can be correlated when the variable ProblemId has the same value… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.8 | NotificationochmPowerSupplyFailure | current | The main power supply went down. Correlation: =========== ochmPowerSupplyFailure and ochmPowerSupplyOperational can be correlated when the variable ProblemId h… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.9 | NotificationochmPowerSupplyOperational | current | The main power supply is back in service. Correlation: =========== ochmPowerSupplyFailure and ochmPowerSupplyOperational can be correlated when the variable Pr… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.10 | NotificationochmFanFailure | current | Fan status anomaly. Correlation: =========== ochmFanFailure and ochmFanOperational can be correlated when the variable ProblemId has the same value ochmFanFail… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.11 | NotificationochmFanOperational | current | Fan status is operational. Correlation: =========== ochmFanFailure and ochmFanOperational can be correlated when the variable ProblemId has the same value ochm… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.12 | NotificationochmIsdnFailure | current | A T2 access is out of service. Correlation: =========== ochmIsdnFailure and ochmIsdnOperational can be correlated when the variable ProblemId has the same valu… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.13 | NotificationochmIsdnOperational | current | A T2 access is back in service. Correlation: =========== ochmIsdnFailure and ochmIsdnOperational can be correlated when the variable ProblemId has the same val… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.14 | NotificationochmVoipLinkDown | current | Ethernet interface of an IP-LAN board is down. Correlation: =========== ochmVoipLinkDown and ochmVoipLinkUp can be correlated when the variable ProblemId has t… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.15 | NotificationochmVoipLinkUp | current | Ethernet interface of an IP-LAN board is up. Correlation: =========== ochmVoipLinkDown and ochmVoipLinkUp can be correlated when the variable ProblemId has the… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.16 | NotificationochmIbsSynchroDown | current | IBS has lost synchronization on UA link: the link is down. Correlation: =========== ochmIbsSynchroDown and ochmIbsSynchroUp can be correlated when the variable… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.17 | NotificationochmIbsSynchroUp | current | IBS has lost synchronization on UA link: the link is up. Correlation: =========== ochmIbsSynchroDown and ochmIbsSynchroUp can be correlated when the variable P… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.18 | NotificationochmNotifUnknownIncident | current | A trap that notify a PABX incident with UNKNOWN severity | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.19 | NotificationochmNotifCriticalIncident | current | A trap that notify a PABX incident with CRITICAL severity | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.20 | NotificationochmNotifMajorIncident | current | A trap that notify a PABX incident with MAJOR severity | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.21 | NotificationochmNotifMinorIncident | current | A trap that notify a PABX incident with MINOR severity | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.22 | NotificationochmNotifWarningIncident | current | A trap that notify a PABX incident with WARNING severity | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.23 | NotificationochmNotifIndeterminateIncident | current | A trap that notify a PABX incident with INDETERMINATE severity | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.24 | NotificationochmNotifState | current | A trap that notify a problem state change | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.25 | NotificationochmAnoRegisterReject | current | SIP Registration rejected on OXO | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.26 | NotificationochmRemoteAccessMbxLocked | current | :the remote access to voice mail box is currently locked Correlation: =========== ochmRemoteAccessMbxLocked and ochmRemoteAccessMbxUnlocked can be correlated w… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.27 | NotificationochmRemoteAccessMbxUnlocked | current | the remote access to voice mail box is currently unlocked Correlation: =========== ochmRemoteAccessMbxLocked and ochmRemoteAccessMbxUnlocked can be correlated … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.28 | NotificationochmRemoteAccessWsapiLocked | current | the remote access to web services API is currently locked Correlation: =========== ochmRemoteAccessWsapiLocked and ochmRemoteAccessWsapiUnlocked can be correla… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.29 | NotificationochmRemoteAccessWsapiUnlocked | current | the remote access to web services API is currently unlocked Correlation: =========== ochmRemoteAccessWsapiLocked and ochmRemoteAccessWsapiUnlocked can be corre… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.30 | NotificationochmArpSpoofInfo | current | ARP spoofing detected. Multiple ARP reply received within lock-time period | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.31 | NotificationochmDefaultPasswordFound | current | Default passwords found in Management/ SIP Phone Administrator passwords | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.32 | NotificationochmEasyPasswordFound | current | Easy passwords found in Management/ User passwords | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.33 | NotificationochmDhcpServerExited | current | Server exited due to bad configuration or option definition error or IP address not in subnet or restart failed | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.34 | NotificationochmDhcpServerStatus | current | Server status changed | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.35 | NotificationochmAnoQuarantineAlert | current | An IP address is added in quarantine | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.36 | NotificationochmMgtsrvLock | current | Access to system management is locked due to 6 consecutive authentication failures with in 5 minutes | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.37 | NotificationochmMgtsrvUnlock | current | Access to system management is unlocked after 6 consecutive authentication failures in 5 minutes | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.38 | NotificationochmUnsupportedRamSize | current | Power CPU EE does not support RAM less than 512 MB | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.39 | NotificationochmMsdbHealthStatus | current | : eMMC in MSDB is approaching its end of life due to increase in block erase count / bad blocks | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.40 | NotificationochmAnoPrinterFault | current | Default TRAPThis error is reported by the Formatter every N unsuccessful attempts to print. Report of anomaly depends on the value attached to the nothworthly … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.41 | NotificationochmAnoMemoryAvail | current | There is not enough memory to start an application (mailing, custo, ...). When this problem occurs, there is less than 15% of free memory | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.42 | NotificationochmTermRebootOrResetOfUserData | current | Reboot of IP terminal or reset of user data. | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.43 | NotificationochmBoardTempReset | current | A temporary reset has been performed on a board (selective maintenance). The reset reason is either a hardware anomaly, or the board is not responding anymore.… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.44 | NotificationochmThresholdHardwareTBL | current | The critical threshold of the hardware anomaly table is reached (80% full). | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.45 | NotificationochmThresholdHistoryTBL | current | The critical threshold of the history events table is reached (80% full). | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.46 | NotificationochmThresholdMeteringTBL | current | The critical threshold of the metering table is reached (80% full). | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.47 | NotificationochmThresholdUrgentTBL | current | The critical threshold of the urgent alarm table is reached (80% full). | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.48 | NotificationochmNmcMeteringTblFull | current | The metering table is full (100%) | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.49 | NotificationochmAnoNoeDLDFail | current | This event is sent when a NOE TDM terminal downloading fails | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.50 | NotificationochmAnoPraAlarm | current | An alarm has been detected on a primary rate access | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.51 | NotificationohcmPasswordAuthenticationLocked | current | User password authentication is locked | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.52 | NotificationohcmPasswordAuthenticationUnlocked | current | User password authentication is unlocked | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.53 | NotificationochmLocalMgtPwdReset | current | All the management passwords have been locally reset to a random value. These management passwords MUST be modified within the limited time frame (in minute) i… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.54 | NotificationochmLocalMgtPwdOperational | current | All the management passwords are now operationals. The sub-event information given in ochmAlarmEvent field indicates the action which solves this problem: 2 - … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.55 | NotificationochmAnoCCStatusConnectionSuccess | current | Change in the CC connection state: CC connection success Byte 1: Cause 0x00: No cause 0x01: First OXO startup 0x02: OXO startup 0x03: CC Agent startup 0x04: FT… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.56 | NotificationochmAnoCCStatusDisconnectionSuccess | current | Change in the CC connection state: CC disconnection success Byte 1: Cause 00: No cause 0x01: First OXO startup 0x02: OXO startup 0x03: CC Agent startup 0x04: F… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.57 | NotificationochmAnoCCStatusFTRDone | current | Change in the CC connection state: FTR Done Byte 1: Cause 00: No cause 0x01: First OXO startup 0x02: OXO startup 0x03: CC Agent startup 0x04: FTR done 0x05: CC… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.58 | NotificationochmAnoCCFailureConnectionFailed | current | Failure on CC connection CC connection failed Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication required 0x… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.59 | NotificationochmAnoCCFailureIntAgentError | current | Failure on CC connection Internal CC Agent error Byte 1: Cause 0x00: No cause 0x0A: Stream version error 0x09: Stream close 0x0B: Proxy authentication required… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.60 | NotificationochmAnoCCFailureConnectionLost | current | Failure on CC connection CC connection lost Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication required 0x0C… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.61 | NotificationochmAnoCCFailureBadCredential | current | Failure on CC connection Bad credential Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication required 0x0C: Pr… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.62 | NotificationochmAnoCCFailureServUnreachable | current | Failure on CC connection Service unreachable Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication required 0x0… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.63 | NotificationochmAnoCCFailureFinalAccountGetting | current | Failure on CC connection Final account getting Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication required 0… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.64 | NotificationochmAnoCCFailureFinalAccountACK | current | Failure on CC connection Final account acknowledgement Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication re… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.65 | NotificationochmAnoCCFailureInconsistentRecData | current | Failure on CC connection Inconsistent received data Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication requi… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.66 | NotificationochmAnoCCFailureEventNodeError | current | Failure on CC connection Event node error Byte 1: Cause 0x00: No cause 0x09: Stream version error 0x0A: Stream close 0x0B: Proxy authentication required 0x0C: … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.67 | NotificationochmAnoCCVPNStatus | current | Change in VPN connection state Byte 1: Request 0x01: start 0x02: stop 0x03: all stopall Byte 2: Cause 0x00: Undefined 0x01: User request 0x02: CC disabled 0x03… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.68 | NotificationochmAnoCCVPNFailure | current | A remote user initiated a request to start or stop a VPN. The request failed. Byte 1: Request 0x01: Start 0x02: Stop 0x03: Stop all Byte 2: Cause 0x00: Undefin… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.69 | NotificationochmAnoEmergencyConfig | current | No device configured to receive emergency call notification | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.70 | NotificationochmSystemAutoProvision | current | Auto Provisioning is Activated/Deactivated | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.72 | NotificationochmAnoRBStatusConnectionSuccess | current | Change in the RB connection state: RB connection success Byte 1: Cause 0x00: No cause 0x01: First OXO startup 0x02: OXO startup 0x03: RB Agent startup 0x04: RB… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.73 | NotificationochmAnoRBStatusDisconnectionSuccess | current | Change in the RB connection state: RB disconnection success Byte 1: Cause 00: No cause 0x01: First OXO startup 0x02: OXO startup 0x03: RB Agent startup 0x04: R… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.74 | NotificationochmAnoRBFailureConnectionFailed | current | Failure on RB connection RB connection failed Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required 0x… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.75 | NotificationochmAnoRBFailureIntAgentError | current | Failure on RB connection Internal RB Agent error Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.76 | NotificationochmAnoRBFailureConnectionLost | current | Failure on RB connection RB connection lost Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required 0x04… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.77 | NotificationochmAnoRBFailureBadCredential | current | Failure on RB connection Bad credential Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required 0x04: Pr… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.78 | NotificationochmAnoRBFailureServUnreachable | current | Failure on RB connection Service unreachable Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required 0x0… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.79 | NotificationochmAnoRBFailureFinalAccountGetting | current | Failure on RB connection Final account getting Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required 0… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.80 | NotificationochmAnoRBFailureFinalAccountACK | current | Failure on RB connection Final account acknowledgement Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication re… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.81 | NotificationochmAnoRBFailureInconsistentRecData | current | Failure on RB connection Inconsistent received data Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication requi… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.82 | NotificationochmAnoRBFailureEventNodeError | current | Failure on RB connection Event node error Byte 1: Cause 0x00: No cause 0x01: Stream version error 0x02: Stream close 0x03: Proxy authentication required 0x04: … | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.83 | NotificationochmAnoTempMax | current | Max temperature reached. Byte 1: temperature | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.84 | NotificationochmDectSyncTreeKo | current | Impossible to build the synchronization tree of xBS: the master is ko. The DECT site is given by the board parameter. Correlation: =========== 1/ First correla… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.85 | NotificationochmDectSyncTreeOk | current | Impossible to build the synchronization tree of xBS: the master is ok. The DECT site is given by the board parameter. Correlation: =========== ochmDectSyncTree… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.86 | NotificationochmDectSyncManual | current | Synchronization mode for xBS: manual. The DECT site is given by the board parameter. | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.87 | NotificationochmDectSyncAutomatic | current | Synchronization mode for xBS: automatic. The DECT site is given by the board parameter. Correlation: =========== ochmDectSyncTreeKo and ochmDectSyncAutomatic c… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.0.88 | NotificationochmDectSyncIslandsChanged | current | The number of islands in the synchronization tree has changed. The DECT site is given by the board parameter. The number of islands is given by the byte 1. The… | |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1 | NodeochmNotificationObjects | |||
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.1 | ScalarochmProblemId | accessible-for-notify | current | The value of this object identifies the equipment for correlation purpose. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.2 | ScalarochmCabinetIndex | accessible-for-notify | current | Index to access the cabinet in the OXO hardware MIB. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.3 | ScalarochmBoardIndex | accessible-for-notify | current | Index to access the board in the OXO hardware MIB. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.4 | ScalarochmFanId | accessible-for-notify | current | Identifier of the fan in the OXO cabinet. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.5 | ScalarochmAccessIndex | accessible-for-notify | current | Index of the access on an OxO board. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.6 | ScalarochmInterfaceNumber | accessible-for-notify | current | Number of the interface on an IP-LAN board. |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.7 | ScalarochmSenderType | accessible-for-notify | current | Type of notification sender |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.8 | ScalarochmNotifFaultId | accessible-for-notify | current | Fault Id sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.9 | ScalarochmNotifProblemState | accessible-for-notify | current | Problem state sent into a state notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.10 | ScalarochmNotifPbxIncidentNumber | accessible-for-notify | current | Incident Id from the PABX sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.11 | ScalarochmNotifAlarmId | accessible-for-notify | current | Incident Id from the Fault Manager sent into an incident ochmNotification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.12 | ScalarochmNotifEventType | accessible-for-notify | current | OSI Type sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.13 | ScalarochmNotifManagedObject | accessible-for-notify | current | Managed object sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.14 | ScalarochmNotifProbableCause | accessible-for-notify | current | Cause of alarm sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.15 | ScalarochmNotifCorrelation | accessible-for-notify | current | Correlation sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.16 | ScalarochmNotifPbxReceptionTime | accessible-for-notify | current | Time of reception of an incident from a PABX sent into an incident notification |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.17 | ScalarochmNmcTicketNumber | accessible-for-notify | current | Number of NMC Alarm value |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.18 | ScalarochmAlarmTime | accessible-for-notify | current | Date of Alarm Ticket |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.19 | ScalarochmAlarmNumberEvent | accessible-for-notify | current | Number of Alarm Event and Sub Event |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.20 | ScalarochmEquipementInfo | accessible-for-notify | current | Information about Board, Half-board and Slot |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.21 | ScalarochmComplementInfo | accessible-for-notify | current | Complement information of Alarm Ticket |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.22 | ScalarochmEventType | accessible-for-notify | current | Type of Event |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.23 | ScalarochmProbableCause | accessible-for-notify | current | Probable cause of incident |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.24 | ScalarochmSeverity | accessible-for-notify | current | Severity of incident |
| 1.3.6.1.4.1.6486.64.4200.1.2.3.1.25 | ScalarochmAlarmName | accessible-for-notify | current | Alarm name incident |
Type Definitions
| Name | Syntax | Status | Description |
|---|---|---|---|
| AlarmEventType | INTEGER { unknown (0), change-Value (1), communication-Alarm (2), environmental-Alarm (3), equipment-Alarm (4), object-Creation (6), object-Deletion (7), processing-Error-Alarm (10), quality-Of-Service-Alarm (11), change-State (14) } | current | The event Type values. |
| AlarmProbableCause | INTEGER { unknown (0), adapter-Error (1), application-Subsystem-Failure (2), band-Width-Reduced (3), call-Establishment-Error (4), communications-Protocol-Error (5), communications-Subsystem-Failure (6), configuration-Or-Customization-Error (7), congestion (8), corrupt-Data (9), cpu-Cycles-Limit-Exceeded (10), data-Set-Or-Modem-Error (11), degraded-Signal (12), dte-Dce-Interface-Error (13), enclosure-Door-Open (14), equipment-Mal-Function (15), excessive-Vibration (16), file-Error (17), fire-Detected (18), flood-Detected (19), framing-Error (20), heating-Ventilation-Cooling-System-Problem (21), humidity-Unacceptable (22), input-Output-Device-Error (23), input-Device-Error (24), lAN-Error (25), leak-Detected (26), local-Node-Transmission-Error (27), loss-Of-Frame (28), loss-Of-Signal (29), material-Supply-Exhausted (30), multiplexer-Problem (31), out-Of-Memory (32), output-Device-Error (33), performance-Degraded (34), power-Problem (35), pressure-Unacceptable (36), processor-Problem (37), pump-Failure (38), queue-Size-Exceeded (39), receive-Failure (40), receiver-Failure (41), remote-Node-Transmission-Failure (42), resource-At-Or-Nearing-Capacity (43), response-Time-Excessive (44), retransmission-Rate-Excessive (45), softwar-eError (46), software-Program-Ab-normally-Terminated (47), software-Program-Error (48), storage-Capacity-Problem (49), temperature-Unacceptable (50), threshold-Crossed (51), timing-Problem (52), toxic-Leak-Detected (53), transmit-Failure (54), transmitter-Failure (55), underlying-Resource-Unavailable (56), version-Mismatch (57) } | current | Probable cause values for the alarms. |
| AlarmTypeList | INTEGER { urgent (1), hardware (2), history (3) } | current | The type of Alarm Event. |