Snmp; Src Software And Sdx Software - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - RELEASE NOTES 2010-11-09 Release Note

JunosE 11.3.0 Release Notes

SNMP

Trap Name
junidApsEventSwitchover
junidApsEventModeMismatch
junidApsEventChannelMismatch
junidApsEventPSBF
junidApsEventFEPLF
juniAddressPoolHighAddrUtil
juniAddressPoolAbatedAddrUtil
juniAddressPoolNoAddresses
juniDhcpLocalServerPoolHighAddrUtil
juniDhcpLocalServerPoolAbatedAddrUtil
juniDhcpLocalServerPoolNoAddresses
pimNeighborLoss

SRC Software and SDX Software

36 Known Behavior
SNMP MIBs

Information about all the SNMP MIBs (both standard and proprietary) that the router
supports in this release is available in the MIB directory in the SW_Image_CD-2 folder
of the JunosE Software image bundle, which you downloaded from the Juniper
Networks website, that contains the release file for E120 and E320 routers.
Some Juniper Networks SNMPv1-formatted traps contain an incorrect object

identifier (OID) in the SNMPv1-Trap-PDU enterprise field. An SNMPv2 trap is typically
identified by an OID that ends in the form ...x.y.z.0.n. This OID appears, in full, as the
value of the snmpTrapOID.0 object in the varbind list of an SNMPv2-formatted trap.
In the corresponding SNMPv1-formatted trap, this OID is broken down into
subcomponents that fill the SNMPv1-Trap-PDU enterprise field (...x.y.z) and specific
trap number field (n); the zero is unused.
The SNMPv1-formatted versions of the following Juniper Networks traps incorrectly
contain ...x.y.z.0 in the SNMPv1-Trap-PDU enterprise field. That is, a zero is
mistakenly appended to the correct enterprise OID value.
Expected Enterprise OID
.1.3.6.1.4.1.4874.3.2.2.1.2
.1.3.6.1.4.1.4874.3.2.2.1.2
.1.3.6.1.4.1.4874.3.2.2.1.2
.1.3.6.1.4.1.4874.3.2.2.1.2
.1.3.6.1.4.1.4874.3.2.2.1.2
.1.3.6.1.4.1.4874.2.2.21.3
.1.3.6.1.4.1.4874.2.2.21.3
.1.3.6.1.4.1.4874.2.2.21.3
.1.3.6.1.4.1.4874.2.2.22.3
.1.3.6.1.4.1.4874.2.2.22.3
.1.3.6.1.4.1.4874.2.2.22.3
.1.3.6.1.3.61.1
Work-around: Use the OIDs that the SNMP agent sends.
When you configure the router with an address pool that has two IP address ranges,

only the range that you configured first is available via the MIB.
The SRC client does not prevent you from changing the name of the router while the

client is connected to the SAE, resulting in SAE issues such as lost IP addresses and
stale users.
Work-around: To change the router name while the SRC client is connected to the
SAE, shut down the SRC client, change the name, then re-enable the SRC client.
Enterprise OID Sent by SNMP Agent
.1.3.6.1.4.1.4874.3.2.2.1.2.0
.1.3.6.1.4.1.4874.3.2.2.1.2.0
.1.3.6.1.4.1.4874.3.2.2.1.2.0
.1.3.6.1.4.1.4874.3.2.2.1.2.0
.1.3.6.1.4.1.4874.3.2.2.1.2.0
.1.3.6.1.4.1.4874.2.2.21.3.0
.1.3.6.1.4.1.4874.2.2.21.3.0
.1.3.6.1.4.1.4874.2.2.21.3.0
.1.3.6.1.4.1.4874.2.2.22.3.0
.1.3.6.1.4.1.4874.2.2.22.3.0
.1.3.6.1.4.1.4874.2.2.22.3.0
.1.3.6.1.3.61.1.0
Copyright © 2010, Juniper Networks, Inc.