Network Working Group J. Parker, Ed. Request for Comments: 4444 Axiowave Networks Category: Standards Track April 2006 Management Information Base for Intermediate System to Intermediate System (IS-IS) Status of This Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2006).Abstract
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. Specifically, this document describes a MIB for the Intermediate System to Intermediate System (IS-IS) Routing protocol when it is used to construct routing tables for IP networks.Table of Contents
1. The Internet-Standard Management Framework . . . . . . . . . . 2 2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Definition of IS-IS MIB. . . . . . . . . . . . . . . . . . . . 6 5. IANA Considerations. . . . . . . . . . . . . . . . . . . . . . 96 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 96 7. Security Considerations. . . . . . . . . . . . . . . . . . . . 96 8. Normative References . . . . . . . . . . . . . . . . . . . . . 101 9. Informative References . . . . . . . . . . . . . . . . . . . . 102
1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].2. Overview
This document describes a management information base for the Intermediate System to Intermediate System (IS-IS) Routing protocol, as described in ISO 10589 [ISO10589], when it is used to construct routing tables for IP networks, as described in RFC 1195 [RFC1195]. The objects are mainly derived from the Guidelines for Definition of Managed Objects (GDMO) definitions in ISO 10589 and from the GDMO definitions in ISO 10733 [ISO10733]. There are also additional objects for managing the IP-specific functionality of Integrated IS- IS operation. This MIB imports definitions from SNMPv2-TC [RFC2579], SNMPv2-SMI [RFC2578], SNMPv2-CONF [RFC2580], SNMP-FRAMEWORK-MIB [RFC3411], DIFFSERV-MIB [RFC3289], IF-MIB [RFC2863], and INET-ADDRESS-MIB [RFC4001]. See the imports section of the MIB for the specific items imported. This MIB defines some objects to manage Mesh Groups, described in [RFC2973], and a three-way handshake for point-to-point adjacencies, described in [RFC3373]. The IS-IS MIB defines the following objects: System-Wide Attributes - isisSystem This table contains information specific to a single instance of the IS-IS protocol running on a router.
- isisManAreaAddr This table includes area addresses that are manually configured, which are used to control the associations formed between Level 1 Intermediate Systems. - isisAreaAddr This table includes area addresses reported in relevant L1 LSPs. - isisSummAddr This table holds summary addresses configured for each Level 2 instance of the IS-IS protocol running on a router. - isisRedistributeAddr This table provides criteria to decide whether a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. - isisRouter This table holds the hostname and router ID for Intermediate Systems in the network. - isisSysLevel This table contains information specific to a domain (Level 2) or an area (Level 1) of the IS-IS protocol. - isisNextCircIndex This scalar is used to provide a unique circuit index. Circuit-specific Attributes - isisCirc This table contains information specific to a point-to-point or a broadcast interface in the system. - isisCircLevel This table contains information specific to Level 1 or Level 2 of an interface.
Counters - isisSystemCounter Counters in the System table, such as number of times we have wrapped a sequence counter on one of our Link State PDUs. - isisCircuitCounter Counters of events particular to a circuit, such as PDUs with an illegal value of the System ID field length. - isisPacketCounter Counts of IS-IS Protocol PDUs broken down into packet type. Attributes associated with an Adjacency - isisISAdj This table contains information about adjacencies to routers maintained by the protocol. Entries in this table cannot be created by management action: they are established through the Hello protocol. - isisISAdjAreaAddr This table contains the set of Area Addresses of neighboring Intermediate Systems, as reported in IIH PDUs. - isisISAdjIPAddr This table contains the set of IP Addresses of neighboring Intermediate Systems, as reported in received IIH PDUs. - isisISAdjProtSupp This table contains the set of protocols supported by neighboring Intermediate Systems, as reported in received IIH PDUs.
Attributes Associated with Addresses - isisRA The Reachable Address Table. This table contains information about an address prefix manually configured on the system or learned through another protocol. - isisIPRA The IP Reachable Address Table. This table contains information about an IP reachable address manually configured on this system or learned from another protocol. Attributes Associated with Link State PDU Table - isisLSPSummaryTable The Link State PDU Summary Table. This table contains information contained in the headers of Link State PDUs stored by the system. - isisLSPTLVTable The Link State PDU TLV Table. This table holds the sequence of TLVs that make up an LSP fragment. Attributes Associated with a Notification - isisNotification This table defines attributes that will be included when reporting IS-IS notifications.3. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL", when they appear in this document, are to be interpreted as described in BCP 14, RFC 2119 [RFC2119].