OPCD-CONNECTORS-MIB-V2: View SNMP OID List / Download MIB

VENDOR: OPENCODE SYSTEMS LTD


 Home MIB: OPCD-CONNECTORS-MIB-V2
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC, OPCD-SUPPORT-MIB-V2

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 occonnectors 1.3.6.1.4.1.30374.16
       occonnectors_traps 1.3.6.1.4.1.30374.16.1
           definitions 1.3.6.1.4.1.30374.16.1.0
               occonectors_LdapConnector 1.3.6.1.4.1.30374.16.1.0.2
LDAP Connector is down!
               occonectors_LdapConnector_Canceled 1.3.6.1.4.1.30374.16.1.0.3
LDAP Connector is down-Canceled
               occonectors_MmlConnector 1.3.6.1.4.1.30374.16.1.0.4
MML Connector is down!
               occonectors_MmlConnector_Canceled 1.3.6.1.4.1.30374.16.1.0.5
MML Connector is down-Canceled
               occonectors_UcpConnector 1.3.6.1.4.1.30374.16.1.0.6
UCP Connector is down!
               occonectors_UcpConnector_Canceled 1.3.6.1.4.1.30374.16.1.0.7
UCP Connector is down-Canceled
               occonectors_UcipConnector 1.3.6.1.4.1.30374.16.1.0.8
UCIP Connector is down!
               occonectors_UcipConnector_Canceled 1.3.6.1.4.1.30374.16.1.0.9
UCIP Connector is down-Canceled
               occonectors_CaiConnector 1.3.6.1.4.1.30374.16.1.0.10
CAI Connector is down!
               occonectors_CaiConnector_Canceled 1.3.6.1.4.1.30374.16.1.0.11
CAI Connector is down-Canceled
               occonectors_SoapConnectorTimeout 1.3.6.1.4.1.30374.16.1.0.12
SOAP connector timeout.
               occonectors_SoapConnectorTimeout_Canceled 1.3.6.1.4.1.30374.16.1.0.13
SOAP connector timeout-Canceled
               occonectors_SoapConnectorLimit 1.3.6.1.4.1.30374.16.1.0.14
SOAP connector session limit is exceeded.
               occonectors_SoapConnectorLimit_Canceled 1.3.6.1.4.1.30374.16.1.0.15
SOAP connector session limit is exceeded-Canceled
               occonectors_CorbaSib 1.3.6.1.4.1.30374.16.1.0.16
Cannot connect to CORBA-CIB server.
               occonectors_CorbaSib_Canceled 1.3.6.1.4.1.30374.16.1.0.17
Cannot connect to CORBA-CIB server-Canceled
               occonectors_CorbaSmaf 1.3.6.1.4.1.30374.16.1.0.18
Cannot connect to CORBA-SMAF server.
               occonectors_CorbaSmaf_Canceled 1.3.6.1.4.1.30374.16.1.0.19
Cannot connect to CORBA-SMAF server-Canceled
               occonectors_CorbaSih 1.3.6.1.4.1.30374.16.1.0.20
Cannot connect to CORBA-SIH server.
               occonectors_CorbaSih_Canceled 1.3.6.1.4.1.30374.16.1.0.21
Cannot connect to CORBA-SIH server-Canceled
               occonectors_XMLConnectorTimeout 1.3.6.1.4.1.30374.16.1.0.22
XML connector timeout.
               occonectors_XMLConnectorTimeout_Canceled 1.3.6.1.4.1.30374.16.1.0.23
XML connector timeout-Canceled
               occonectors_XMLConnectorLimit 1.3.6.1.4.1.30374.16.1.0.24
XML connector session limit is exceeded.
               occonectors_XMLConnectorLimit_Canceled 1.3.6.1.4.1.30374.16.1.0.25
XML connector session limit is exceeded-Canceled
               occonectors_ORACLEConnector 1.3.6.1.4.1.30374.16.1.0.26
Oracle connector is down
               occonectors_ORACLEConnector_Canceled 1.3.6.1.4.1.30374.16.1.0.27
Oracle connector is down-Canceled
               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
               occonectors_MYSQL_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.29
No connection to MYSQL server-Canceled
               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
               occonectors_SMPP_SERVER_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.31
No connection to SMPP server-Canceled
               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
               occonectors_TELNET_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.33
No connection to TELNET server-Canceled
               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
               occonectors_CORBA_SMAF_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.35
No connection to CORBA SMAF server - Canceled
               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
               occonectors_CORBA_SIH_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.37
No connection to CORBA SIH server-Canceled
               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
               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
               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
               occonectors_CORBA_CIB_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.41
No connection to CORBA CIB server-Canceled
               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
               occonectors_CORBA_ALCATEL_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.43
No connection to CORBA(Alcatel) server -Canceled
               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
               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
               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
               occonectors_BROADCAST_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.47
No connection to MYSQL server-Canceled
               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
               occonectors_LDAP_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.49
No connection to LDAP server-Canceled
               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
               occonectors_DIAMETER_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.51
No connection to DIAMETER server-Canceled
               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
               occonectors_HTTPCLIENT_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.53
No connection to HTTP server-Canceled
               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
               occonectors_BOOKMARK_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.55
No connection to MYSQL server-Canceled
               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
               occonectors_CORBA_INPAYMENT_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.57
No connection to IN(Payment) server-Canceled
               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
               occonectors_CORBA_PPSERVER_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.59
No connection to CORBA PP server-Canceled
               occonectors_ecm_CONNECTOR_CRASHED 1.3.6.1.4.1.30374.16.1.0.60
Connector monitored by ECM crashed
               occonectors_ecm_CONNECTOR_CRASHED_Canceled 1.3.6.1.4.1.30374.16.1.0.61
Connector monitored by ECM crashed-Canceled
               occonectors_ecm_CONNECTOR_DISABLED 1.3.6.1.4.1.30374.16.1.0.62
Connector disabled.
               occonectors_ecm_CONNECTOR_DISABLED_Canceled 1.3.6.1.4.1.30374.16.1.0.63
Connector disabled-Canceled
               occonectors_MMLAUC_connector_CONNECT 1.3.6.1.4.1.30374.16.1.0.64
No connection to MML server
               occonectors_MMLAUC_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.65
No connection to MML server
               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
               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
               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
               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
               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
               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
               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
               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
               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
               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
               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.
               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.
               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.
               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.
               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.
               mcr_SMPP_EX_connector_CONNECT_Canceled 1.3.6.1.4.1.30374.16.1.0.81
- The connector has at least one connected session.
               mcr_SMPP_EX_connector_CLIENT_SESS 1.3.6.1.4.1.30374.16.1.0.82
- One configured SMPP session is broken.
               mcr_SMPP_EX_connector_CLIENT_SESS_Canceled 1.3.6.1.4.1.30374.16.1.0.83
- All configured SMPP sessions are connected.
               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.
               mcr_SMPP_EX_connector_CLIENT_CONN_Canceled 1.3.6.1.4.1.30374.16.1.0.85
- At least one session is connected for this client.
               mcr_SMPP_EX_connector_SERVER_CONN 1.3.6.1.4.1.30374.16.1.0.86
- Server cannot be started.
               mcr_SMPP_EX_connector_SERVER_CONN_Canceled 1.3.6.1.4.1.30374.16.1.0.87
- Server is started.
           vars 1.3.6.1.4.1.30374.16.1.1
               mcr_Host 1.3.6.1.4.1.30374.16.1.1.1 displaystring no-access
String containing hostname of fault node.
               mcr_Severity 1.3.6.1.4.1.30374.16.1.1.2 integer no-access
Alarm severity. Enumeration: 'major': 2, 'critical': 1, 'warning': 5, 'minor': 3, 'normal': 4.
               mcr_Text 1.3.6.1.4.1.30374.16.1.1.3 displaystring no-access
String containing text of the alarm.