Description

For Juniper Networks Junos OS, some SNMP traps defined in the MIBs for SNMPv2 are not compatible with SNMPv1.

Symptoms

Juniper enterprise MIBs support SNMPv1 and SNMPv2.

However, some SNMP traps defined in the MIBs for SNMPv2 are not compatible with SNMPv1.


Successful Trap Translation (jnxVpnIfDown )

In the example below:

  • The "Specific Type" is 2.
 
  • The SNMP trap service, snmptrapd , translates the specific type to a proper trapname, jnxVpnIfDown .


2000-01-01 00:00:00 10.0.0.1(via UDP: [10.0.0.1]:60639->[10.0.0.2]) TRAP, SNMP v1, community juniper

jnxVpnMIB Enterprise Specific Trap ( jnxVpnIfDown ) Uptime: 01:00:00:00.0
jnxVpnIfVpnType.bgpAtmVpn."abcdefghijklmnopqrst".2147483647 bgpAtmVpn
jnxVpnIfVpnName.bgpAtmVpn."abcdefghijklmnopqrst".2147483647 "abcdefghijklmnopqrst"
jnxVpnIfIndex.bgpAtmVpn."abcdefghijklmnopqrst".2147483647 2147483647


Unsuccessful Trap Translation ( jnxPowerSupplyFailure )

In the example below:

  • The "Specific Type" is 1.
 
  • The SNMP trap service, snmptrapd , does not translate the specific type to the proper trapname, jnxPowerSupplyFailure .

2000-01-01 00:00:00 10.0.0.1(via UDP: [10.0.0.1]:60639->[10.0.0.2]) TRAP, SNMP v1, community juniper
jnxChassisTraps Enterprise Specific Trap ( 1 ) Uptime: 01:00:00:00.0
jnxContentsContainerIndex.1073741824.1073741823.1073741823.1073741823 1073741824
jnxContentsL1Index.1073741824.1073741823.1073741823.1073741823 1073741823
jnxContentsL2Index.1073741824.1073741823.1073741823.1073741823 1073741823
jnxContentsL3Index.1073741824.1073741823.1073741823.1073741823 1073741823
jnxContentsDescr.1073741824.1073741823.1073741823.1073741823 abcdefghijklmnopqrst
jnxOperatingState.1073741824.1073741823.1073741823.1073741823 standby

Solution

Some SNMP traps in the MIBs are defined for SNMPv2 but are not compatible with SNMPv1.

These traps cannot be translated to a trapname by the SNMP manager.

This is a limitation of the Juniper Enterprise MIB.

Use SNMPv2 instead of SNMPv1.

Note: If SNMPv1 is required, modify the SNMP manager so that the traps can be translated.

The table below lists the traps that cannot be translated to a trapname.


Traps that cannot be translated to a trapname:

Enterprise MIB

MIB file name

Trap

Chassis MIB
(JUNIPER-MIB)		jnx-chassis.mibjnxPowerSupplyFailure  
jnxFanFailure  
jnxOverTemperature  
jnxRedundancySwitchover  
jnxFruRemoval  
jnxFruInsertion  
jnxFruPowerOff  
jnxFruPowerOn  
jnxFruFailed  
jnxFruOffline  
jnxFruOnline  
jnxFruCheck  
jnxFEBSwitchover  
jnxHardDiskFailed
jnxHardDiskMissing  
jnxBootFromBackup  
jnxFmLinkErr  
jnxFmCellDropErr  
jnxExtSrcLockLost  
jnxPlaneOffline  
jnxPlaneOnline  
jnxPlaneCheck  
jnxPlaneFault  
jnxPowerSupplyOK  
jnxFanOK  
jnxTemperatureOK  
jnxFruOK  
jnxExtSrcLockAcquired  
Fabric Chassis MIB
(JUNIPER-FABRIC-CHASSIS)		mib-jnx-fabric-chassis.txtjnxFabricPowerSupplyFailure
jnxFabricFanFailure  
jnxFabricOverTemperature  
jnxFabricRedundancySwitch
jnxFabricFruRemoval  
jnxFabricFruInsertion  
jnxFabricFruPowerOff  
jnxFabricFruPowerOn  
jnxFabricFruFailed  
jnxFabricFruOffline  
jnxFabricFruOnline  
jnxFabricFruCheck  
jnxFabricFEBSwitchover  
jnxFabricHardDiskFailed  
jnxFabricHardDiskMissing  
jnxFabricBootFromBackup  
jnxFabricPowerSupplyOK  
jnxFabricFanOK  
jnxFabricTemperatureOK  
jnxFabricFruOK  
FRU management for OTN Equipments
(JUNIPER-FRU-MIB)		jnx-fru.mibjnxFruNotifMismatch  
jnxFruNotifAdminStatus  
jnxFruNotifOperStatus  
DHCP MIB
(JUNIPER-JDHCP-MIB)		mib-jnx-jdhcp.txtjnxJdhcpLocalServerDuplicateClient   
jnxJdhcpLocalServerInterfaceLimitExceeded   
jnxJdhcpLocalServerInterfaceLimitAbated   
jnxJdhcpLocalServerHealth  
jnxJdhcpRelayInterfaceLimitExceeded   
jnxJdhcpRelayInterfaceLimitAbated   
DHCPv6 MIB
(JUNIPER-JDHCP-MIB)		mib-jnx-jdhcpv6.txtjnxJdhcpv6LocalServerInterfaceLimitExceeded   
jnxJdhcpv6LocalServerInterfaceLimitAbated   
jnxJdhcpv6LocalServerHealth  
GGSN MIBggsn.mibggsnTrapNew
ggsnTrapChanged
ggsnTrapCleared

Modification History

2022-09-28: Article reviewed for accuracy. It is still relevant and valid.