OPCD-CONNECTORS-MIB-V2 :: occonectors_CORBA_CX_connector_CONNECT_Canceled

MIB Reference — IPNetwork Monitor

All MIBsOPCD-CONNECTORS-MIB-V2occonectors_CORBA_CX_connector_CONNECT_Canceled

occonectors_CORBA_CX_connector_CONNECT_Canceled

Module: OPCD-CONNECTORS-MIB-V2

OID (symbolic): OPCD-CONNECTORS-MIB-V2::occonectors_CORBA_CX_connector_CONNECT_Canceled

OID (numeric): 1.3.6.1.4.1.30374.16.1.0.39

Node type: NOTIFICATION-TYPE

Description:

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

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' OPCD-CONNECTORS-MIB-V2::occonectors_CORBA_CX_connector_CONNECT_Canceled
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.30374.16.1.0.39

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:59527->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (500283015) 57 days, 21:40:30.15
  SNMPv2-MIB::snmpTrapOID.0 = OID: OPCD-CONNECTORS-MIB-V2::occonectors_CORBA_CX_connector_CONNECT_Canceled

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.30374opencode_systemsOPCD-SUPPORT-MIB-V2
1.3.6.1.4.1.30374.16occonnectorsOPCD-CONNECTORS-MIB-V2
1.3.6.1.4.1.30374.16.1occonnectors_trapsOPCD-CONNECTORS-MIB-V2
1.3.6.1.4.1.30374.16.1.0definitionsOPCD-CONNECTORS-MIB-V2
1.3.6.1.4.1.30374.16.1.0.39occonectors_CORBA_CX_connector_CONNECT_CanceledOPCD-CONNECTORS-MIB-V2