Nortel Networks NN46110-602 manual RFC 2787-VRRP MIB, RFC 2737-Entity MIB

Appendix A MIB support 133

RFC 2787—VRRP MIB

The VPN Router supports RFC 2787, Definitions of Managed Objects for the Virtual Router Redundancy Protocol. As stated in the introduction, RFC 2787 “defines an extension to the Management Information Base (MIB) for use with SNMP-based network management. In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol (VRRP).”

RFC 2737—Entity MIB

This MIB contains five tables two or which are partially implemented.

*entPhysicalTable entLogicalTable entLPMappingTable *entAliasMappingTable entPhysicalContainsTable

The entPhysicalTable provides a listing of the hardware elements that are present in the system. For example, each slot is listed and if there is a card in the slot, then the card and any ports on the card are listed. The exception to this is the hardware accelerator, which does not appear in the table. The listing shows element relationships through the columns entPhysicalContainedIn and entPhysicalParentRelPos. The only columns that are implemented are:

entPhysicalIndex

entPhysicalDescr (although the value is not strictly what the MIB specifies)

entPhysicalContainedIn entPhysicalClass entPhysicalParentRelPos entPhysicalName entPhysicalIsFRU

All other columns return an appropriate default value for the object.

The entAliasMappingTable provides a mapping from entPhysicalIndex to ifTable.ifIndex. By walking this table, a management station can deter the ifIndex associated with a physical port.

Nortel VPN Router Troubleshooting