Table of Contents
Advertisement
132 Appendix A MIB support
RFC 1724—RIP Version 2 MIB Extension
The VPN Router supports RFC 1724, RIP Version 2 MIB Extension. As stated in
the introduction to the RFC, the RFC "defines a portion of the Management
Information Base (MIB) for use with network management protocols in TCP/
IP-based internets. In particular, it defines the objects for managing RIP Version
2."
RFC 1213—Network Management of TCP/IP-Based Internets
MIB
The VPN Router supports RFC 1213, Management Information Base for Network
Management of TCP/IP-based Internets: MIB II. This RFC provides the
architecture and system for managing TCP/IP-based internets. With the exception
of the EGP Group (Section 6.10) and the Transmission Group (Section 6.11), the
VPN Router provides full support for the RFC.
SNMP interface index (IfIndex) numbers, as defined in RFC 1213, are numbers
that third-party network management systems (NMS) rely on to monitor and
gather statistics for devices through SNMP. The physical and virtual interfaces on
the VPN Router are assigned these locally significant numbers and the NMS can
use them to associate statistics with the devices.
Prior to Release 7.0, an IfIndex number was dynamically assigned to a branch
office tunnel (BOT) when the BOT came up. Only up tunnels were reported. This
enhancement does the following:
•
•
RFC 2667—IP Tunnel MIB
The VPN Router supports RFC 2667, IP Tunnel MIB. As stated in the
introduction to the RFC, it "describes a Management Information Base (MIB)
used for managing tunnels of any type over IPv4 networks, including GRE
[16,17], IP-in-IP [18], Minimal Encapsulation [19], L2TP [20], PPTP [21], L2F
[25], UDP (e.g., [26]), ATMP [22], and IPv6-in-IPv4 [27] tunnels."
NN46110-602
assigns a static number to each branch office tunnel
reports all branch office tunnels, whether they are up or down, in an SNMP
query
Advertisement
Table of Contents
Troubleshooting
