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].
4. Definition of IS-IS MIB
ISIS-MIB DEFINITIONS ::= BEGIN
IMPORTS
TEXTUAL-CONVENTION, RowStatus, TruthValue, TimeStamp
FROM SNMPv2-TC -- RFC2579
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Unsigned32, Counter32, mib-2
FROM SNMPv2-SMI -- RFC2578
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC2580
SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC2571
IndexInteger, IndexIntegerNextFree
FROM DIFFSERV-MIB -- RFC3289
InterfaceIndex
FROM IF-MIB -- RFC2863
InetAddressType, InetAddress, InetAddressPrefixLength
FROM INET-ADDRESS-MIB; -- RFC3291
isisMIB MODULE-IDENTITY
LAST-UPDATED "200604040000Z" -- April 4, 2006, midnight
ORGANIZATION "IETF IS-IS for IP Internets Working Group"
CONTACT-INFO
"IS-IS for IP Internets working Group
http://www.ietf.org/html.charters/isis-charter.html
isis-wg@ietf.org
Jeff Parker
Department of Computer Science
Middlebury College,
Middlebury, Vermont 05753
jeffp at middlbury dot edu"
DESCRIPTION
"This document describes a management information base for
the IS-IS Routing protocol, as described in ISO 10589,
when it is used to construct routing tables for IP
networks, as described in RFC 1195.
This document is based on a 1994 IETF document by Chris
Gunner. This version has been modified to include
current syntax, to exclude portions of the protocol that
are not relevant to IP, and to add management support for
current practice.
Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC 4444; see the RFC
itself for full legal notices."
REVISION "200604040000Z" -- April 4, 2006, midnight
DESCRIPTION
"Initial version, published as RFC 4444."
::= { mib-2 138 }
-- Top-level structure of the MIB
isisNotifications OBJECT IDENTIFIER ::= { isisMIB 0 }
isisObjects OBJECT IDENTIFIER ::= { isisMIB 1 }
isisConformance OBJECT IDENTIFIER ::= { isisMIB 2 }
-- OBJECT IDENTIFIER definitions
-- System wide attributes.
isisSystem OBJECT IDENTIFIER ::= { isisObjects 1 }
-- Attributes associated with the domain or with the area.
isisSysLevel OBJECT IDENTIFIER ::= { isisObjects 2 }
-- Attributes associated with one Circuit
isisCirc OBJECT IDENTIFIER ::= { isisObjects 3 }
-- Attributes associated with area or domain relevant within a Circuit.
isisCircLevelValues OBJECT IDENTIFIER ::= { isisObjects 4 }
-- System and circuit counters.
isisCounters OBJECT IDENTIFIER ::= { isisObjects 5 }
-- Attributes associated with an adjacent Protocol Peer.
isisISAdj OBJECT IDENTIFIER ::= { isisObjects 6 }
-- Attributes associated with a configured address.
isisReachAddr OBJECT IDENTIFIER ::= { isisObjects 7 }
-- Attributes associated with IP routes learned by
-- configuration or through another protocol.
isisIPReachAddr OBJECT IDENTIFIER ::= { isisObjects 8 }
-- The collection of Link State PDUs known to the Intermediate System
isisLSPDataBase OBJECT IDENTIFIER ::= { isisObjects 9 }
-- Objects included in Notifications.
isisNotification OBJECT IDENTIFIER ::= { isisObjects 10 }
-- Type definitions
IsisOSINSAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"OSI Network Service Address, e.g., NSAP, SNPA, or Network
Entity Title"
SYNTAX OCTET STRING (SIZE(0..20))
IsisSystemID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The ID for an Intermediate System. This should
be unique within a network, and is included
in all PDUs originated by an Intermediate System.
The protocol does not place any meanings upon
the bits, other than using ordering to break
ties in electing a Designated IS on a LAN."
REFERENCE "{ISIS.aoi systemId (119)}"
SYNTAX OCTET STRING (SIZE(6))
IsisLinkStatePDUID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The 8-byte Link State PDU (LSP) ID,
consisting of the 6-byte SystemID of the
originating IS; a one-byte PseudoNode ID,
which is 0 unless the LSP represents the
topology of a LAN; and a one-byte LSP
fragment number that is issued in sequence,
starting with 0. Non-zero PseudoNode IDs
need to be unique to the IS but need not
match the IfIndex."
REFERENCE "{See section 9.8 of ISO 10589}"
SYNTAX OCTET STRING (SIZE(8))
IsisAdminState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Type used in enabling and disabling a row."
SYNTAX INTEGER
{
on(1),
off(2)
}
IsisLSPBuffSize ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Integer sub-range for maximum LSP size."
SYNTAX Unsigned32 (512..16000)
IsisLevelState ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"States of the IS-IS protocol."
SYNTAX INTEGER
{
off (1),
on (2),
waiting (3),
overloaded(4)
}
IsisSupportedProtocol ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Types of network protocol supported by Integrated IS-IS.
The values for ISO8473 and IP are those registered for
these protocols in ISO TR9577."
REFERENCE "{See section 5.3.1 of RFC 1195}"
SYNTAX INTEGER
{
iso8473(129),
ipV6(142),
ip(204)
}
IsisDefaultMetric ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Integer sub-range for default metric for single hop.
ISO 10589 provides for 4 types of metric. Only the
’default’ metric is used in practice."
REFERENCE "{See section 7.2.2 of ISO 10589}"
SYNTAX Unsigned32 (0..63)
IsisWideMetric ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Wide metric for IS Neighbors. ISO 10589 provides a
6-bit metric. Traffic Engineering extensions provide
24-bit metrics."
REFERENCE "{See section 3 of RFC 3784}"
SYNTAX Unsigned32 (0..16777215)
IsisFullMetric ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Full metric for IP Routes. Traffic Engineering extensions
provide 32-bit metrics."
REFERENCE "{See section 4 of RFC 3784}"
SYNTAX Unsigned32
IsisMetricType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Is this an Internal or External Metric?"
REFERENCE "{See section 7.2.2 of ISO 10589}"
SYNTAX INTEGER
{
internal(1),
external(2)
}
IsisMetricStyle ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Do we use RFC 1195 style metrics or wide metrics?"
REFERENCE "{See section 5 of RFC 3787}"
SYNTAX INTEGER
{
narrow(1),
wide(2),
both(3)
}
IsisISLevel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies a level."
REFERENCE "{See definitions 3.6.1 and 3.6.11 of ISO 10589}"
SYNTAX INTEGER
{
area(1), -- L1
domain(2) -- L2
}
IsisLevel ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Identifies one or more levels."
REFERENCE "{See definitions 3.6.1 and 3.6.11 of ISO 10589}"
SYNTAX INTEGER
{
level1(1),
level2(2),
level1and2(3)
}
IsisPDUHeader ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"A block to contain the header from a PDU."
SYNTAX OCTET STRING (SIZE(0..64))
IsisCircuitID ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"ID for a circuit."
REFERENCE "{See section 7.2.7 of ISO 10589}"
SYNTAX OCTET STRING (SIZE(0|7))
IsisISPriority ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"Integer sub-range for IS-IS priority."
REFERENCE "{See section 9.5 of ISO 10589}"
SYNTAX Unsigned32 (0..127)
IsisUnsigned16TC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An Unsigned32 further restricted to 16 bits. Note that
the ASN.1 BER encoding may still require 24 bits for
some values."
SYNTAX Unsigned32 (0..65535)
IsisUnsigned8TC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
"An Unsigned32 further restricted to 8 bits. Note that
the ASN.1 BER encoding may still require 16 bits for
some values."
SYNTAX Unsigned32 (0..255)
-- Behavior Definitions
-- ResettingTimer behavior definition
--
-- "This behavior applies to objects that specify the interval
-- between events in the operation of the protocol state machine.
-- If the value of such an object is set to a new value while
-- the protocol state machine is in operation, the implementation
-- shall take the necessary steps to ensure that for any time
-- interval that was in progress when the value of the
-- corresponding object was changed, the next expiration of that
-- interval takes place the specified time after the original
-- start of that interval, or immediately, whichever is later.
-- The precision with which this time shall be implemented shall
-- be the same as that associated with the basic operation of
-- the timer object."
-- ReplaceOnlyWhileDisabled behavior definition
-- "This behavior applies to objects that may not be modified
-- while the corresponding table row’s variable of type
-- IsisAdminState is in state on."
-- ManualOrAutomatic behavior definition
-- "This behavior applies to objects that are read-write
-- if the object was created manually. Objects that were
-- created automatically that have this behavior are
-- read-only.
isisSysObject OBJECT IDENTIFIER ::= { isisSystem 1 }
isisSysVersion OBJECT-TYPE
SYNTAX INTEGER
{
unknown(0),
one(1)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The version number of the IS-IS protocol that
is implemented."
REFERENCE "{ISIS.aoi version (1)}"
DEFVAL { one }
::= { isisSysObject 1 }
isisSysLevelType OBJECT-TYPE
SYNTAX IsisLevel
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"At which levels is the Intermediate System
running? This object may not be modified when
the isisSysAdminState variable is in state ’on’
for this Intermediate System.
Configured values MUST survive an agent reboot."
REFERENCE "{ISIS.aoi iSType (2)}"
DEFVAL { level1and2 }
::= { isisSysObject 2 }
isisSysID OBJECT-TYPE
SYNTAX IsisSystemID
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The ID for this Intermediate System.
This value is appended to each of the
area addresses to form the Network Entity Titles.
The derivation of a value for this object is
implementation specific. Some implementations may
automatically assign values and not permit an
SNMP write, while others may require the value
to be set manually.