OPCD-CONNECTORS-MIB-V2
File:
OPCD-CONNECTORS-MIB-V2.mib (43191 bytes)
Imported modules
Imported symbols
Defined Values
| vars |
1.3.6.1.4.1.30374.16.1.1 |
| OBJECT IDENTIFIER |
|
|
|
| mcr-Host |
1.3.6.1.4.1.30374.16.1.1.1 |
| String containing hostname of fault node. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..255) |
|
| mcr-Severity |
1.3.6.1.4.1.30374.16.1.1.2 |
| Alarm severity. |
| Status: mandatory |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
critical(1), major(2), minor(3), normal(4), warning(5) |
|
| mcr-Text |
1.3.6.1.4.1.30374.16.1.1.3 |
| String containing text of the alarm. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..255) |
|
| occonectors-LdapConnector |
1.3.6.1.4.1.30374.16.1.0.2 |
| LDAP Connector is down! |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-MmlConnector |
1.3.6.1.4.1.30374.16.1.0.4 |
| MML Connector is down! |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-UcpConnector |
1.3.6.1.4.1.30374.16.1.0.6 |
| UCP Connector is down! |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-UcipConnector |
1.3.6.1.4.1.30374.16.1.0.8 |
| UCIP Connector is down! |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CaiConnector |
1.3.6.1.4.1.30374.16.1.0.10 |
| CAI Connector is down! |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-SoapConnectorLimit |
1.3.6.1.4.1.30374.16.1.0.14 |
| SOAP connector session limit is exceeded. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CorbaSib |
1.3.6.1.4.1.30374.16.1.0.16 |
| Cannot connect to CORBA-CIB server. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CorbaSib-Canceled |
1.3.6.1.4.1.30374.16.1.0.17 |
| Cannot connect to CORBA-CIB server-Canceled |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CorbaSmaf |
1.3.6.1.4.1.30374.16.1.0.18 |
| Cannot connect to CORBA-SMAF server. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CorbaSmaf-Canceled |
1.3.6.1.4.1.30374.16.1.0.19 |
| Cannot connect to CORBA-SMAF server-Canceled |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CorbaSih |
1.3.6.1.4.1.30374.16.1.0.20 |
| Cannot connect to CORBA-SIH server. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CorbaSih-Canceled |
1.3.6.1.4.1.30374.16.1.0.21 |
| Cannot connect to CORBA-SIH server-Canceled |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-XMLConnectorLimit |
1.3.6.1.4.1.30374.16.1.0.24 |
| XML connector session limit is exceeded. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-ORACLEConnector |
1.3.6.1.4.1.30374.16.1.0.26 |
| Oracle connector is down |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-MYSQL-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.28 |
| No connection to MYSQL server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to MySQL server.
3.Check MySQL logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-SMPP-SERVER-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.30 |
| No connection to SMPP server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to SMPP server.
3.Check SMPP server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-TELNET-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.32 |
| No connection to TELNET server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to TELNET server.
3.Check TELNET server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-SMAF-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.34 |
| No connection to CORBA SMAF server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA SMAF server.
3.Check CORBA SMAF server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-SIH-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.36 |
| No connection to CORBA SIH server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA SIH server.
3.Check CORBA SIH server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-CX-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.38 |
| No connection to CORBA CX server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA CX server.
3.Check CORBA CX server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-CX-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.39 |
| No connection to CORBA CX server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA CX server.
3.Check CORBA CX server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-CIB-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.40 |
| No connection to CORBA CIB server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA CIB server.
3.Check CORBA CIB server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-ALCATEL-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.42 |
| No connection to CORBA(Alcatel) server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA(Alcatel) server.
3.Check CORBA(Alcatel) server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CAI-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.44 |
| No connection to CAI server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CAI server.
3.Check CAI server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CAI-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.45 |
| No connection to CAI server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CAI server.
3.Check CAI server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-BROADCAST-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.46 |
| No connection to MYSQL server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to MySQL server.
3.Check MySQL logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-LDAP-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.48 |
| No connection to LDAP server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to LDAP server.
3.Check LDAP logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-DIAMETER-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.50 |
| No connection to DIAMETER server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to DIAMETER server.
3.Check DIAMTER server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-HTTPCLIENT-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.52 |
| No connection to HTTP server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to HTTP server.
3.Check HTTP server logs for the possible reason for refusing connections from the connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-BOOKMARK-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.54 |
| No connection to MYSQL server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to MySQL server.
3.Check MySQL logs for the possible reason for refusing connections from the
connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-INPAYMENT-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.56 |
| No connection to IN(Payment) server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to IN server.
3.Check IN logs for the possible reason for refusing connections from the
connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-CORBA-PPSERVER-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.58 |
| No connection to CORBA PP server
1.Check the connector's log file in order to find the reason for this alarm.
2.Check if there is ping to CORBA server.
3.Check CORBA logs for the possible reason for refusing connections from the
connector |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-ecm-CONNECTOR-PROBLEM |
1.3.6.1.4.1.30374.16.1.0.66 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| occonectors-ecm-CONNECTOR-PROBLEM-Canceled |
1.3.6.1.4.1.30374.16.1.0.67 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-HTTP-SERVER-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.68 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-HTTP-SERVER-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.69 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SPEECHLAB-TTS-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.70 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SPEECHLAB-TTS-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.71 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-CIMD2-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.72 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-CIMD2-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.73 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SOAP-CLIENT-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.74 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SOAP-CLIENT-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.75 |
| The alarm is turned ON if any connector is not working properly:
1.all subconnectos or all IPC connections are not working
2.it exited unexpectedly
3.it is disabled by ECM because of too much retries to start |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-BLRATING-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.76 |
| Alarm of type 'CONNECT' is ON when connector can't
connect to MySQL server or when connected to it and lost connection later. This
alarm is set OFF when connection is restored. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-BLRATING-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.77 |
| Alarm of type 'CONNECT' is ON when connector can't
connect to MySQL server or when connected to it and lost connection later. This
alarm is set OFF when connection is restored. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-DMS-CLIENT-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.78 |
| Alarm of type 'CONNECT' is ON when connector can't
connect to HTTP server or when connected to it and lost connection later. This alarm is
set OFF when connection is restored. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-DMS-CLIENT-connector-CONNECT-Canceled |
1.3.6.1.4.1.30374.16.1.0.79 |
| Alarm of type 'CONNECT' is ON when connector can't
connect to HTTP server or when connected to it and lost connection later. This alarm is
set OFF when connection is restored. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SMPP-EX-connector-CONNECT |
1.3.6.1.4.1.30374.16.1.0.80 |
| - All sessions for all configured clients are broken.
- The connector exited unexpectedly.
- The connector is disabled by ECM. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SMPP-EX-connector-CLIENT-SESS |
1.3.6.1.4.1.30374.16.1.0.82 |
| - One configured SMPP session is broken. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| mcr-SMPP-EX-connector-CLIENT-CONN |
1.3.6.1.4.1.30374.16.1.0.84 |
| - All sessions for one configured client are broken. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|