Home/Catalog/OPCD-CONNECTORS-MIB-V2

OPCD-CONNECTORS-MIB-V2

Detailed view of the defined objects, syntax rules, and hierarchical paths.

93
Objects
Active
Status
3
Dependencies

Imported Objects

SNMPv2-SMI
SNMPv2-TC
OPCD-SUPPORT-MIB-V2

Objects

93 total
Object Name
occonnectors
OBJECT IDENTIFIER
.1.3.6.1.4.1.30374.16
occonnectors_traps
OBJECT IDENTIFIER
.1.3.6.1.4.1.30374.16.1
definitions
OBJECT IDENTIFIER
.1.3.6.1.4.1.30374.16.1.0
occonectors_LdapConnectorLDAP Connector is down!
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.2
occonectors_LdapConnector_CanceledLDAP Connector is down-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.3
occonectors_MmlConnectorMML Connector is down!
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.4
occonectors_MmlConnector_CanceledMML Connector is down-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.5
occonectors_UcpConnectorUCP Connector is down!
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.6
occonectors_UcpConnector_CanceledUCP Connector is down-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.7
occonectors_UcipConnectorUCIP Connector is down!
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.8
occonectors_UcipConnector_CanceledUCIP Connector is down-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.9
occonectors_CaiConnectorCAI Connector is down!
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.10
occonectors_CaiConnector_CanceledCAI Connector is down-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.11
occonectors_SoapConnectorTimeoutSOAP connector timeout.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.12
occonectors_SoapConnectorTimeout_CanceledSOAP connector timeout-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.13
occonectors_SoapConnectorLimitSOAP connector session limit is exceeded.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.14
occonectors_SoapConnectorLimit_CanceledSOAP connector session limit is exceeded-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.15
occonectors_CorbaSibCannot connect to CORBA-CIB server.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.16
occonectors_CorbaSib_CanceledCannot connect to CORBA-CIB server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.17
occonectors_CorbaSmafCannot connect to CORBA-SMAF server.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.18
occonectors_CorbaSmaf_CanceledCannot connect to CORBA-SMAF server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.19
occonectors_CorbaSihCannot connect to CORBA-SIH server.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.20
occonectors_CorbaSih_CanceledCannot connect to CORBA-SIH server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.21
occonectors_XMLConnectorTimeoutXML connector timeout.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.22
occonectors_XMLConnectorTimeout_CanceledXML connector timeout-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.23
occonectors_XMLConnectorLimitXML connector session limit is exceeded.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.24
occonectors_XMLConnectorLimit_CanceledXML connector session limit is exceeded-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.25
occonectors_ORACLEConnectorOracle connector is down
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.26
occonectors_ORACLEConnector_CanceledOracle connector is down-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.27
occonectors_MYSQL_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.28
occonectors_MYSQL_connector_CONNECT_CanceledNo connection to MYSQL server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.29
occonectors_SMPP_SERVER_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.30
occonectors_SMPP_SERVER_connector_CONNECT_CanceledNo connection to SMPP server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.31
occonectors_TELNET_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.32
occonectors_TELNET_connector_CONNECT_CanceledNo connection to TELNET server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.33
occonectors_CORBA_SMAF_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.34
occonectors_CORBA_SMAF_connector_CONNECT_CanceledNo connection to CORBA SMAF server - Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.35
occonectors_CORBA_SIH_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.36
occonectors_CORBA_SIH_connector_CONNECT_CanceledNo connection to CORBA SIH server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.37
occonectors_CORBA_CX_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.38
occonectors_CORBA_CX_connector_CONNECT_CanceledNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.39
occonectors_CORBA_CIB_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.40
occonectors_CORBA_CIB_connector_CONNECT_CanceledNo connection to CORBA CIB server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.41
occonectors_CORBA_ALCATEL_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.42
occonectors_CORBA_ALCATEL_connector_CONNECT_CanceledNo connection to CORBA(Alcatel) server -Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.43
occonectors_CAI_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.44
occonectors_CAI_connector_CONNECT_CanceledNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.45
occonectors_BROADCAST_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.46
occonectors_BROADCAST_connector_CONNECT_CanceledNo connection to MYSQL server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.47
occonectors_LDAP_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.48
occonectors_LDAP_connector_CONNECT_CanceledNo connection to LDAP server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.49
occonectors_DIAMETER_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.50
occonectors_DIAMETER_connector_CONNECT_CanceledNo connection to DIAMETER server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.51
occonectors_HTTPCLIENT_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.52
occonectors_HTTPCLIENT_connector_CONNECT_CanceledNo connection to HTTP server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.53
occonectors_BOOKMARK_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.54
occonectors_BOOKMARK_connector_CONNECT_CanceledNo connection to MYSQL server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.55
occonectors_CORBA_INPAYMENT_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.56
occonectors_CORBA_INPAYMENT_connector_CONNECT_CanceledNo connection to IN(Payment) server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.57
occonectors_CORBA_PPSERVER_connector_CONNECTNo 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.58
occonectors_CORBA_PPSERVER_connector_CONNECT_CanceledNo connection to CORBA PP server-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.59
occonectors_ecm_CONNECTOR_CRASHEDConnector monitored by ECM crashed
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.60
occonectors_ecm_CONNECTOR_CRASHED_CanceledConnector monitored by ECM crashed-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.61
occonectors_ecm_CONNECTOR_DISABLEDConnector disabled.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.62
occonectors_ecm_CONNECTOR_DISABLED_CanceledConnector disabled-Canceled
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.63
occonectors_MMLAUC_connector_CONNECTNo connection to MML server
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.64
occonectors_MMLAUC_connector_CONNECT_CanceledNo connection to MML server
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.65
occonectors_ecm_CONNECTOR_PROBLEMThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.66
occonectors_ecm_CONNECTOR_PROBLEM_CanceledThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.67
mcr_HTTP_SERVER_connector_CONNECTThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.68
mcr_HTTP_SERVER_connector_CONNECT_CanceledThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.69
mcr_SPEECHLAB_TTS_connector_CONNECTThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.70
mcr_SPEECHLAB_TTS_connector_CONNECT_CanceledThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.71
mcr_CIMD2_connector_CONNECTThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.72
mcr_CIMD2_connector_CONNECT_CanceledThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.73
mcr_SOAP_CLIENT_connector_CONNECTThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.74
mcr_SOAP_CLIENT_connector_CONNECT_CanceledThe 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
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.75
mcr_BLRATING_connector_CONNECTAlarm 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.76
mcr_BLRATING_connector_CONNECT_CanceledAlarm 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.77
mcr_DMS_CLIENT_connector_CONNECTAlarm 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.78
mcr_DMS_CLIENT_connector_CONNECT_CanceledAlarm 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.79
mcr_SMPP_EX_connector_CONNECT- All sessions for all configured clients are broken. - The connector exited unexpectedly. - The connector is disabled by ECM.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.80
mcr_SMPP_EX_connector_CONNECT_Canceled- The connector has at least one connected session.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.81
mcr_SMPP_EX_connector_CLIENT_SESS- One configured SMPP session is broken.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.82
mcr_SMPP_EX_connector_CLIENT_SESS_Canceled- All configured SMPP sessions are connected.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.83
mcr_SMPP_EX_connector_CLIENT_CONN- All sessions for one configured client are broken.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.84
mcr_SMPP_EX_connector_CLIENT_CONN_Canceled- At least one session is connected for this client.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.85
mcr_SMPP_EX_connector_SERVER_CONN- Server cannot be started.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.86
mcr_SMPP_EX_connector_SERVER_CONN_Canceled- Server is started.
NOTIFICATION-TYPE
.1.3.6.1.4.1.30374.16.1.0.87
vars
OBJECT IDENTIFIER
.1.3.6.1.4.1.30374.16.1.1
mcr_HostString containing hostname of fault node.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.30374.16.1.1.1
mcr_SeverityAlarm severity.ro
Enumeration
.1.3.6.1.4.1.30374.16.1.1.2
mcr_TextString containing text of the alarm.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.30374.16.1.1.3
OPCD-CONNECTORS-MIB-V2 - SNMP MIB Reference | MIBs Explorer