User`s guide

XSR User’s Guide 93
Chapter 5 IETF MIBs Supported
Configuring IP
When the actual IP address owner of the Virtual IP address releases the
master state of the VR, it will no longer be able to receive any IP packet
destined for that address even though the actual interface is still up. This may
cause routing packets to not reach this interface and cause this interface to be
considered down by other routers. To avoid this situation, when Interface
Monitoring is used, be sure that you configure Virtual IP addresses different
than the actual IP addresses of the interfaces.
Physical Interface and Physical IP Address Change on a VRRP Router
The VR will change to the initialize state regardless of the interface state, if you
configure a VR before configuring the physical IP address, and there will be a
conflict between the physical IP and VR IP address.
The VR will change to the initialize state regardless of the interface state, if you
change the physical IP address on that interface, and this change will also
create a conflict between the physical IP and VR IP address.
IETF MIBs Supported
The XSR supports the following standard MIB-II managed objects:
 MIB-II RFC-1213: System, Interfaces, IP, ICMP, TCP, UDP, and SNMP
groups
 RFC-1471: PPP LCP MIB (pppLqrExtnsTable and pppTests not
supported)
 RFC-1473: PPP IP NCP MIB
 RFC-1573: IfStackTable only
 RFC-1724: RIPv2 MIB
 RFC-1850: OSPF MIB
 RFC-2115: Frame Relay DTE MIB
 RFC-2667: Tunnel MIB
 RFC-2737, Entity MIB Version 2: EntPhysicalTable