TIMETRA-PIM-NG-MIB :: vRtrPimNgInvalidIPmsiTunnel

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsTIMETRA-PIM-NG-MIBvRtrPimNgInvalidIPmsiTunnel

vRtrPimNgInvalidIPmsiTunnel

Module: TIMETRA-PIM-NG-MIB

OID (symbolic): TIMETRA-PIM-NG-MIB::vRtrPimNgInvalidIPmsiTunnel

OID (numeric): 1.3.6.1.4.1.6527.3.1.3.50.0.14

Node type: NOTIFICATION-TYPE

Description: [CAUSE1] The vRtrPimNgInvalidIPmsiTunnel event is generated when an invalid default core group address specified by vRtrPimNgWrongMdtDefGrpAddr of the Multicast Distribution Tree(MDT) is received in PIM message from vRtrPimNgNotifySourceIp, instead of the expected addresss specified by vRtrPimNgAFGenMdtDefGrpAddress. It is considered to be a misconfiguration and the message will be dropped. This trap is intended to help network operators recognize the misconfiguration and adjust their configurations accordingly.

[CAUSE2] This event is also generated when the tunnel type specified by vRtrPimNgWrongPmsiType is received in PIM message from vRtrPimNgNotifySourceIp which is different from the configured tunnel type.

[EFFECT] The PMSI received in the PIM message from vRtrPimNgNotifySourceIp is not processed by PIM.

[RECOVERY]: Operator needs to look and adjust the configuration of vRtrPimNgNotifySourceIp in the VPRN specified by vRtrPimNgWrongVprnId.

The objects vRtrPimNgWrongPmsiP2mpId, vRtrPimNgWrongPmsiTunnelId and vRtrPimNgWrongPmsiExtTunlAddr in the event vRtrPimNgInvalidIPmsiTunnel are valid only when vRtrPimNgWrongPmsiType is 'rsvp (2)'.

The objects vRtrPimNgWrongMdtDefGrpAddrType and vRtrPimNgWrongMdtDefGrpAddr in the event vRtrPimNgInvalidIPmsiTunnel are valid only when vRtrPimNgWrongPmsiType is either 'pimSsm (0)' or 'pimSm (1)'.

The objects vRtrPimNgWrongPmsiLdpLspId, vRtrPimNgWrongPmsiSenderAdrTyp and vRtrPimNgWrongPmsiSenderAddr in the event vRtrPimNgInvalidIPmsiTunnel are valid only when vRtrPimNgWrongPmsiType is 'ldp (3)'.

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> '' TIMETRA-PIM-NG-MIB::vRtrPimNgInvalidIPmsiTunnel
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.6527.3.1.3.50.0.14

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]:50789->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (211752037) 24 days, 12:12:00.37
  SNMPv2-MIB::snmpTrapOID.0 = OID: TIMETRA-PIM-NG-MIB::vRtrPimNgInvalidIPmsiTunnel

Start monitoring Nokia/Alcatel-Lucent 7750/7450 SROS routers, multicast-enabled (PIM admin/oper/ECMP-rebalance status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TIMETRA-PIM-NG-MIB::vRtrPimNgInvalidIPmsiTunnel OID value, configure state conditions and alerts, and monitor any Nokia/Alcatel-Lucent 7750/7450 SROS routers, multicast-enabled (PIM admin/oper/ECMP-rebalance status) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.3tmnxSRNotifyPrefixALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.3.50vRtrPimNgNotifyPrefixTIMETRA-PIM-NG-MIB
1.3.6.1.4.1.6527.3.1.3.50.0vRtrPimNgNotificationsTIMETRA-PIM-NG-MIB
1.3.6.1.4.1.6527.3.1.3.50.0.14vRtrPimNgInvalidIPmsiTunnelTIMETRA-PIM-NG-MIB