DC-ISIS-MIB: View SNMP OID List / Download MIB

The MIB module for management of the DC-ISIS product. This is closely based on the draft standard MIB draft-ietf-isis-wg-mib-16.

The set of instances of the Integrated IS-IS protocol existing on the system.

Each row defines information specific to a single instance of the IS-IS protocol existing on the system.

The unique identifier of the Integrated IS-IS instance to which this row corresponds. This object follows the index behavior.

The version number of the IS-IS protocol that is implemented. Enumeration: 'unknown': 0, 'one': 1.

At which levels is the Intermediate System running? This object follows the replaceOnlyWhileDisabled behavior. Enumeration: 'level2IS': 2, 'level1L2IS': 3, 'reserved': 0, 'level1IS': 1.

The ID for this instance of the Integrated IS-IS protocol. 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. For the DC-ISIS implementation, this field is set through the MIB. This object follows the replaceOnlyWhileDisabled behavior.

Maximum number of paths with equal routing metric value which it is permitted to split between. Note that, when IGP shortcut interfaces are in use, this maximum applies individually to IGP shortcut paths and non-IGP shortcut paths. That is, there may be a total of 2 * isisSysMaxPathSplits paths for a single route. This object follows the replaceOnlyWhileDisabled behavior.

Maximum interval, in seconds, between generated LSPs by this instance of the protocol. This object follows the resettingTimer behavior. The value must be greater than any value configured for isisSysLevelMinLSPGenInt, and should be at least 300 seconds less than isisSysMaxAge. Note that this value is specified in seconds whereas isisSysLevelMinLSPGenInt is specified in milliseconds.

The value, in seconds, to be used for the suggested ES configuration timer in ISH PDUs when soliciting the ES configuration.

Number of seconds to delay in waiting state before entering on state. This object follows the resettingTimer behavior.

The administrative state of this instance of the Integrated IS-IS protocol. Setting this object to the value 'on' when its current value is 'off' enables operation of this instance of the Integrated IS-IS protocol.

If true, allow the router to leak L2 routes into L1.

Value to place in RemainingLifeTime field of the LSPs we generate. This should be at least 300 seconds greater than isisSysMaxLSPGenInt.

Size of the largest Buffer we are designed or configured to store. This should be at least as big as the maximum isisSysOrigLSPBuffSize supported by the system. If resources allow, we will store and flood LSPs larger than isisSysReceiveLSPBufferSize, as this can help avoid problems in networks with different values for isisSysOrigLSPBuffSize.

The state of the IS-IS router. Turning this to state 'destroy' forces the router to forget all the current configuration. Setting the state to 'notInService' stops protocol processing, but retains the configuration.

The current operational status of this instance of the Protocol Manager component of DC-ISIS. Note that DC-ISIS can only activate if there is at least one active entry in the isisManAreaAddrTable.

If 'true' then add IP addresses received from the I3 stub to the isisCircIPAddrTable with admin state 'on'. If 'false' then add them with admin state 'off'. This field follows the replaceOnlyWhileDisabled behavior.

The maximum delay before the Routing Table is recalculated following a change to the Link State Database. (Recalculation is delayed to reduce the frequency of recalculations of the Routing Table). This parameter has units of milliseconds. A value of 0 indicates that a routing calculation will immediately follow an update to the database.

This parameter can be used to override the routing calculation delay indicated by the isisSysCalcMaxDelay parameter when the number of updates to the Link State Database reaches a threshold value. This parameter specifies the threshold number of updates that can be made to the Link State Database such that any subsequent update to the database causes a full routing calculation to start immediately. - 0 indicates that a routing calculation will immediately follow an update to the database. - 0xFFFFFFFF indicates that this threshold is infinite, and hence the timing of a routing calculation is determined solely by the configured calculation delay.

This parameter can be used to interrupt a full routing calculation when the number of pending updates to the Link State Database has reached a threshold value. This parameter specifies the threshold number of updates that can be made to the Link State Database such that any subsequent update to the database causes the current routing calculation to be interrupted, and a new calculation to start using an up to date Link State Database. - 0 indicates that an update to the Link State Database will cause any current routing calculation to be interrupted and a new one to start. - 0xFFFFFFFF indicates that this threshold is infinite, and hence no number of pending updates to the database will cause a routing calculation to be interrupted.

This parameter limits the number of consecutive times a routing calculation can be interrupted by new updates. This guarantees that the routing calculation will actually complete. - 1 indicates that once a calculation has been interrupted once, it will not be interrupted again. - 0xFFFFFFFF indicates that the calculation can always be interrupted.

This value determines how regularly a Routing Calculation is paused. It is measured in points. The points scale roughly maps to a time scale, so that the larger this value is, the longer the Routing Calculation runs before pausing. See the DC-ISIS Configuration and Management Interface Specification for more information on how to set this parameter. - 0 indicates that the routing calculation is paused after every calculation step. - 0xFFFFFFFF indicates that the Routing Calculation is never paused.

This value determines how often the checksums of LSPs in the Link State Database are checked. If 0, no checksums in the database are checked.

This is the minimum amount of time in seconds for which the header of an expired LSP shall be retained after it has been flooded with zero Remaining Lifetime. All that is required is that the header be retained until the zero Remaining Lifetime LSP has been safely propagated to all the neighbors.

The number of updates that are pending addition to the Link State Database.

The number of updates that have been merged into the Link State Database since the last routing calculation.

The number of LSPs in the Link State Database which are now due to have their checksum checked.

The Traffic Engineering metric is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of the TE metric that causes a new LSP to be originated.

The maximum bandwidth on an interface is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of maximum bandwidth that causes a new LSP to be originated.

The maximum reservable bandwidth on an interface is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of maximum reservable bandwidth that causes a new LSP to be originated.

The unreserved bandwidth on an interface is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of unreserved bandwidth that causes a new LSP to be originated.

The maximum LSP bandwidth for the various switching descriptors on an interface is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of maximum LSP bandwidth that causes a new LSP to be originated.

The minimum LSP bandwidth for the various switching descriptors on an interface is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of minmimum LSP bandwidth that causes a new LSP to be originated.

The Maximum Transmission Unit size for the various switching descriptors on an interface is updated in real-time by the I3 Stub. In order to increase performance and reduce network traffic, this parameter determines the minimal percentage change of the Maximum Transmission Unit that causes a new LSP to be originated.

The Local IPv4 TE Router ID. This is a single stable IPv4 address that can always be referenced in a path that will be reachable from multiple hops away, regardless of the state of the node's interfaces. This object must be set if isisSysLevelTEEnabled is 'true' at either level, but is otherwise ignored.

The Local IPv6 TE Router ID. This is a single stable IPv6 global address that can always be referenced in a path that will be reachable from multiple hops away, regardless of the state of the node's interfaces. This object must be set if isisSysLevelIPv6TEEnabled is 'true' at level 1, but is otherwise ignored.

The maximum number of static routes and routes redistributed from other protocols that DC-ISIS will accept. The action that DC-ISIS will take when the maximum is exceeded is controlled by isisSysMaxExternalRoutesAction. 0xFFFFFFFF is a special value indicating that the threshold is infinite.

The action that DC-ISIS will take when the number of external routes exceeds isisSysMaxExternalRoutes. If set to 'log', DC-ISIS will alert the administrator by logging that the limit has been exceeded. If set to 'suppressExternal', DC-ISIS will remove all external routes from the local LSP (at all active levels) in addition to logging the problem. In both cases, the administrator is responsible for correcting the configuration in each Address Family Manager (for example, DC-RTM), to reduce the number of redistributed external routes. In the 'suppressExternal' case, the Address Family Manager is responsible for resynchronizing the set of routes with DC-ISIS. Enumeration: 'suppressExternal': 2, 'log': 1.

The set of routes (if any) that will be removed from the local LSP by DC-ISIS when the local LSP becomes full at either level. When set to 'external', all static routes and routes redistributed from other protocols will be removed from the local LSP (at all active levels) when the local LSP is full. If set to 'none', DC-ISIS will be unable to accept any additional configuration that may increase the size of the local LSP. The system administrator should modify the system configuration to reduce the local LSP size - for example, by reducing the number of addresses redistributed from other routing protocols, or by deleting circuit configuration. Once this has been done, if isisSysLspFullSuppress is set to 'external', the Address Family Manager is responsible for resynchronizing the set of routes with DC-ISIS. Enumeration: 'none': 2, 'external': 1.

If set to 'true', DC-ISIS will set the database overload flag in the local LSP (at all active levels) when the local LSP becomes full (at either level). The administrator can clear the database overload flag for a level by setting isisSysLevelSetOverload to 'false' for that level.

Indicates whether DC-ISIS implements the procedures defined in the IS-IS restart RFC (3847) for helping a peer to restart. Note that this object has no effect on the local restart behavior, and so may be set independently of isisSysRestartActivationType and isisSysRestartAutoResetType.

This object is only used when DC-ISIS is manually activated or deactivated (in other words, enters or leaves the state with row status 'active' and admin status 'on'), and indicates which restart procedures (if any) are followed. During the activation period, DC-ISIS will use the value that was configured at the start of activation. The value may be changed at any time, but the new value will only take effect the next time that manual activation takes place. During deactivation, DC-ISIS will purge the local LSP from remote nodes if this object is set to 'none' or 'start'. Setting the object to 'restart' before deactivation will prevent the local LSP from being purged. A planned restart may be initiated by setting isisSysAdminState to 'off' and later to 'on'. Graceful restart procedures will only function correctly if the local LSP has not been purged, and so to initiate a planned restart, isisSysRestartActivationType should be set to 'restart' before deactivation.

There are cases where the IS-IS protocol requires the local node to automatically deactivate and later reactivate. This object indicates which restart procedures (if any) are followed during such an automatic reset. During the activation period, DC-ISIS will use the value that was configured at the start of activation. The value may be changed at any time, but the new value will only take effect the next time that automatic re-activation takes place.

This object is only used when DC-ISIS activates with the activation type (isisSysRestartActivationType or isisSysRestartAutoResetType) set to 'start' or 'restart'. It defines how long DC-ISIS will wait to establish adjacencies before completing the start/restart. This object follows the resettingTimer behavior.

This object is only used when DC-ISIS activates with the activation type (isisSysRestartActivationType or isisSysRestartAutoResetType) set to 'restart'. It defines the maximum time that DC-ISIS will take before completing restart procedures. The value specified puts an upper bound on the duration of the T3 timer described in the IS-IS restart RFC (3847). The actual duration of the timer is the minimum of the value specified and the minimum remaining holding time received on an adjacency. This object follows the resettingTimer behavior.

Set to 'true' to clear all system statistics, including the isisSystemCounter and isisPacketCounter tables. Note that isisSysStatsLSPCount is not reset by this object. Reading the value of this field has no meaning.

If DC-ISIS is operating at both level 1 and level 2, this field indicates how DC-ISIS should decide whether to set the attached bit in its level 1 LSP. - 'attachNoOverlapOrRedist' indicates that the attached bit should be set if either of the following are true. - The IS can reach at least one other area (the IS is adjacent with a L2 router whose area addresses do not overlap with the area addresses we know about at L1). - The IS is redistributing one or more external routes into the AS. - 'attachNoOverlapOnly' indicates that the attached bit should be set only if the IS can reach at least one other area. - 'attachSet' indicates that the attached bit should always be set. - 'attachClear' indicates that the attached bit should never be set. Enumeration: 'attachSet': 3, 'attachNoOverlapOrRedist': 1, 'attachClear': 4, 'attachNoOverlapOnly': 2.

This attribute contains the set of protocols supported by this Intermediate System.

This object only affects IPv4 broadcast circuits. If this is set to 'true', DC-ISIS will only form adjacencies with intermediate systems that are on the same subnet as the local circuit. This object only has effect when the I3 Stub is used to determine subnet addresses and is ignored otherwise.

The string that this instance of IS-IS will use as the local hostname. This is advertised to other Intermediate Systems in the Dynamic Hostname TLV.

Set this object to 'true' to minimize the delay before triggering a routing calculation that includes any relevant circuit change. This means a change to the local neighbors (including pseudonodes), or to the reachable addresses received from the I3 stub. There are two aspects to minimizing the delay. - DC-ISIS overrides the setting of the isisSysLevelMinLSPGenInt object when such a change occurs, and usually regenerates the local LSP(s) immediately. The only exception is when DC-ISIS is performing restart procedures as defined in RFC3847. This RFC specifies when DC-ISIS can update the local LSP during a restart. - DC-ISIS overrides all of the objects that affect the scheduling of routing calculations, with the exception of the isisSysCalcThrshRestartLimit object. It ensures that a routing calculation including the updated LSPs takes place as soon as possible. It abandons an existing route calculation if necessary, unless more than isisSysCalcThrshRestartLimit successive calculations would have been interrupted.

This attribute contains the set of notifications generated by this Intermediate System. The notifications that may be enabled are the isisCircIndTable, isisDatabaseOverload, isisManualAddressDrops, isisIDLenMismatch, isisMaxAreaAddressesMismatch, isisOwnLSPPurge, isisAreaMismatch, isisRejectedAdjacency, isisAdjacencyChange, isisLSPErrorDetected, isisAttemptToExceedMaxSequence, isisSequenceNumberSkip, isisDisChange, isisOperStateChange, isisLspAuthFailure, isisHelloAuthFailure, isisExtPassCircuitInd and isisAttachStateChange notifications. Bits: 'lspAuthFailure': 15, 'manualAreaAddressDrops': 2, 'sequenceNumberSkip': 11, 'maxAreaAddressMismatch': 4, 'circuitIndication': 0, 'areaMismatch': 6, 'rejectedAdjacency': 7, 'attemptToExceedMaxSequence': 10, 'extPassCircuitInd': 12, 'helloAuthFailure': 16, 'lspErrorDetected': 9, 'idLengthMismatch': 3, 'operStateChange': 13, 'databaseOverload': 1, 'disChange': 14, 'attachStateChange': 17, 'adjacencyChange': 8, 'ownLspPurge': 5.

Set isisSysEnableIgpShortcut to 'true' to enable IS-IS routing over IGP shortcut interfaces. Set isisSysEnableIgpShortcut to 'false' to disable IS-IS routing over IGP shortcut interfaces. IS-IS will ignore any interface that is identified as an IGP shortcut.

Identifies the I3 stub instance to which this IS-IS instance should join. The status of the join is given by the row in the isisPmMjTable with isisPmMjInterface equal to ifInterfaceInfo. Note that IS-IS will not become active unless the join to the specified I3 stub is activated successfully. This field follows the replaceOnlyWhileDisabled behavior.

This object defines the maximum time that DC-ISIS will wait when a Routing Table Manager (such as DC-RTM) fails before purging routes. In some systems, the Routing Table Manager may restart independently of DC-ISIS. For example, it may be administratively deactivated and reactivated, or may be distributed to a separate process that can restart independently of the DC-ISIS process. If such a restart does not affect the forwarding table, then DC-ISIS should continue to advertise routes that it has learnt from the Routing Table Manager. This is achieved by setting isisSysRtmPurgeTime to a value that gives the Routing Table Manager sufficient time to restart. A value of zero indicates that routes will be purged as soon as the join to RTM fails. Any change to the configured timer value will take effect when the timer is next started. RTM purge timers that are already running will not be affected by the change.

The set of manual area addresses configured on this Intermediate System.

Each entry contains one area address manually configured on this system

A manually configured area address for this system. This object follows the index behavior. Note: an index for the entry {1, {49.0001} active} in this table would be the ordered pair (1, (0x03 0x49 0x00 0x01)), as the length of an Octet string is part of the OID. For the DC-ISIS implementation, the area address must have a non-zero length.

The state of the isisManAreaAddrEntry. This object follows the Row Status behavior. If the isisSysAdminState for this instance of the IS-IS protocol is 'on', and an attempt is made to set this object to the value 'destroy' or 'notInService' when this is the only isisManAreaAddrEntry in state 'active' for this instance of the IS-IS protocol should return inconsistentValue.

The union of the sets of area addresses reported in all Level 1 LSPs with segment number zero received by this instance of the protocol from Intermediate Systems which are reachable via Level 1 routing.

Each entry contains one area address reported in a Level 1 LSP received by this instance of the IS-IS protocol. The DC-ISIS implementation ignores received area addresses with a length of zero.

An area address reported in a Level 1 LSP received by this instance of the IS-IS protocol. The DC-ISIS implementation ignores received area addresses with a length of zero.

Following ISO10589 section 7.1.5, we advertise the three numerically lowest level 1 area addresses in the level 2 LSP fragment zero. If 'true', then this area address is one of the three numerically lowest area addresses, and if this router is active at level 2, it is therefore one of those area addresses advertised in the level 2 LSP fragment 0.

The set of IP summary addresses to use in forming summary TLVs originated by this Intermediate System. An administrator may use a summary address to combine and modify IP Reachability announcements. If the Intermediate system can reach any subset of the summary address, the summary address will be announced instead, at the configured metric.

Each entry contains one IP summary address.

The Type of IP address for this summary address. This object follows the index behavior.

The IP Address value for this summary address. This object follows the index behavior. The address must not contain any set host bits (bits set after the address prefix determined by isisSummAddrPrefixLen).

The Length of the IP NetMask for this summary address.

The existence state of this summary address. This object follows the row status behavior.

The metric value to announce this summary address with in LSPs generated by this system.

The wide metric value to announce this summary address with in LSPs generated by this system.

The topology that this summary address applies to. This should be set to zero if multi-topology IS-IS is not enabled. This object follows the index behavior.

This table provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table will be announced at L1 by routers when isisSysL2toL1Leaking is enabled. Routes that fall into the ranges specified are announced as is, without being summarized. Routes that do not match a summary mask are not announced.

Each entry contains one IP summary address to manage leaking L2 addresses into L1.

The Type of IP address for this summary address. This object follows the index behavior.

The IP Address value for this summary address. This object follows the index behavior. The address must not contain any set host bits (bits set after the address prefix determined by isisRedistributeAddrPrefixLen).

The Length of the IP NetMask for this summary address.

The existence state of this summary address. This object follows the row status behavior.

The topology that this redistribution address applies to. This should be set to zero if multi-topology IS-IS is not enabled. This object follows the index behavior.

The set of hostnames and router ID.

Each entry tracks information about one peer at one level.

The System ID of the Router Peer.

The level of this Intermediate System.

The hostname listed in LSP, or NULL if none.

The Router ID of the Peer found in LSP, or NULL if none.

The IPv6 TE Router ID found in the LSP, if any.

A row in this table represents the level of support for a topology on this instance of the Integrated IS-IS protocol. This table is only used when multi-topology IS-IS is supported.

Each row defines information specific to a single topology on a single instance of the IS-IS protocol existing on the system.

The topology that this row represents.

The state of the MIB row. Turning this to state 'destroy' forces the router to forget all the current topology configuration. Setting the state to 'notInService' stops protocol processing for this topology, but retains the configuration. For multi-topology ID zero (the base topology), this field is read only. The row for the base topology is automatically created and destroyed along with the corresponding isisSysTable row.

The desired operational state of this topology on this instance of the Integrated IS-IS protocol. Setting this object to the value 'on' when its current value is 'off' enables operation of this topology for this instance of the Integrated IS-IS protocol.

The current operational status of this topology on this instance of the Integrated IS-IS protocol. If this is 'down' then the topology is not supported.

This attribute contains the set of protocols supported by this topology on this Intermediate System. Note that RFC 5120 assigns certain topologies to serve pre-determined purposes (MT IDs 0 - 5). This limits the set of allowed values this field should take.

When set to 'true', corresponding rows in the isisMtCircStatusTable have oper status 'up', unless a corresponding row exists in the isisMtCircManConfigTable. When set to 'false', corresponding rows in the isisMtCircStatusTable have oper status 'down', unless a corresponding row exists in the isisMtCircManConfigTable.

Level specific information about an instance of IS-IS.

Describe variables defined for Area or Domain.

The level that this entry describes. Enumeration: 'none': 0, 'level2IS': 2, 'level1IS': 1.

The maximum size of LSPs and SNPs originated by this Intermediate System at this level. This object follows the replaceOnlyWhileDisabled behavior.

Minimum interval, in milliseconds, between successive generation of LSPs with the same LSPID at this level by this instance of the protocol. This object follows the resettingTimer behavior.

The Overload state of the database at this level. The value 'overloaded' indicates a database that is low on an essential resource, such as memory. The administrator may indirectly force the state to 'waiting' when the router is initializing by setting the object isisSysLevelSetOverload. If the state is waiting or overloaded, we originate LSPs with the Overload bit set.

Administratively set the overload bit for the level. The overload bit will continue to be set if the implementation runs out of memory, independent of this variable.

If set, the overload bit should be set, and cleared after sysUpTime exceeds this value.

Which style of Metric do we generate in our LSPs at this level?

Which style of Metric do we consider in our SPF computation at this level?

Do we do Traffic Engineering for IPv4 at this level? If Traffic Engineering is enabled, isisSysLevelMetricStyle must be set to 'wide' or 'both' for this level, and a value must be configured for isisSysTERouterID. When Traffic Engineering is enabled for IPv4, this IS will advertise the IPv4 TE router ID in the local LSP, and will advertise traffic engineering parameters (where available) for links configured to support IPv4. This object is ignored if the 'ipv4' bit is not set in the value of isisSysProtSupported.

Do we do Traffic Engineering for IPv6 at this level? DC-ISIS only supports Traffic Engineering for IPv6 at level 1. If Traffic Engineering is enabled, a value must be configured for isisSysIPv6TERouterID. When Traffic Engineering is enabled for IPv6, this IS will advertise the IPv6 TE router ID in the local LSP, and will advertise traffic engineering parameters (where available) for links configured to support IPv6. This object is ignored if the 'ipv6' bit is not set in the value of isisSysProtSupported.

This object is only used when DC-ISIS activates with the activation type (isisSysRestartActivationType or isisSysRestartAutoResetType) set to 'start' or 'restart'. It defines how long DC-ISIS will wait to complete database synchronization at this level before completing the start/restart. This object follows the resettingTimer behavior.

Authentication user data for area/domain level authentication. This data is passed opaquely to the Metaswitch authentication interface where it can be used to assist with authentication decisions.

The table of circuits used by each instance of Integrated IS-IS on this system.

An isisCircEntry exists for each circuit used by Integrated IS-IS on this system.

The identifier of this circuit, unique within the instance of the IS-IS protocol. This object follows the index behavior. This is for SNMP Indexing purposes only and need not have any relation to any protocol value. In DC-ISIS this is always equal to the circuit ifIndex.

The value of ifIndex for the interface to which this circuit corresponds. This object cannot be modified after creation. In DC-ISIS this is also used as the 3-way circuit ID on point-to-point circuits, and must equal isisCircIndex. The default value is the same as isisCircIndex. A create request using any other value will fail.

A specifier for the part of the interface ifIndex to which this circuit corresponds, such as a DLCI or VPI/VCI. This object cannot be modified after creation. In DC-ISIS this field is ignored.

The administrative state of the circuit. This object follows the AdminState behavior. In DC-ISIS the default admin state for a new automatic circuit is 'on' if the isisSysAllowAutoI3Config field is 'true', otherwise the default admin state is 'off'.

The existence state of this circuit. This object follows the Row Status behavior. Setting the state to 'notInService' halts the generation and processing of IS-IS protocol PDUs on this circuit. Setting the state to destroy will also erase any configuration associated with the circuit. In DC-ISIS, automatic circuits from the I3 stub appear as passive circuits with existence state 'active'. These circuits can be configured via the MIB like manual circuits, except that they will survive a Destroy request, with all fields reset to their automatic values. MIB configuration overrides automatic configuration.

The type of the circuit. This object follows the replaceOnlyWhileDisabled behavior. The type specified must be compatible with the type of the interface defined by the value of isisCircIfIndex. In DC-ISIS only 'broadcast' and 'ptToPt' circuits are supported. An automatic circuit can have type 'unknown' until the correct MIB type is defined. Enumeration: 'staticOut': 4, 'unknown': 0, 'dA': 5, 'broadcast': 1, 'staticIn': 3, 'ptToPt': 2.

If true, suppress normal transmission of and interpretation of Intra-domain IS-IS PDUs on this circuit.

Indicates which type of packets will be sent and accepted on this circuit. The values used will be modified by the settings of isisSysType. This object follows the replaceOnlyWhileDisabled behavior. Enumeration: 'level1': 1, 'level2': 2, 'reserved': 0, 'level1L2': 3.

Should we include this interface in LSPs, even if it is not running the IS-IS Protocol? In DC-ISIS, circuits with isisCircExtDomain 'true' will only be included in LSPs if this field is also 'true', and the circuit is active.

Is this port a member of a mesh group, or blocked? Circuits in the same mesh group act as a virtual multiaccess network. LSPs seen on one circuit in a mesh group will not be flooded to another circuit in the same mesh group. Enumeration: 'inactive': 1, 'set': 3, 'blocked': 2.

Circuits in the same mesh group act as a virtual multiaccess network. LSPs seen on one circuit in a mesh group will not be flooded to another circuit in the same mesh group. If isisCircMeshGroupEnabled is inactive or blocked, this value is ignored.

Can we send unpadded hellos on LAN circuits? False means LAN Hellos must be padded. Implementations should allow the administrator to read this value. An implementation need not be able to support unpadded hellos to be conformant. DC-ISIS does support unpadded hellos.

If the circuit is enabled, the value of sysUpTime when isisCircAdminState most recently entered the state on. If the circuit is not on, the value of sysUpTime when the circuit last entered state on, 0 if the circuit has never been on.

Is this circuit enabled to run 3Way handshake? DC-ISIS will always run the 3-way handshake on point to point circuits, and so this object is read-only.

The value to be used as the extended circuit ID in 3Way handshake. This value is only used if isisCirc3WayEnabled is true, and must be unique across all circuits on this IS. DC-ISIS uses the value for isisCircIndex as the extended circuit ID, and so this object is read-only.

The operational state of this circuit.

Identifies the SDC entity which will handle this circuit. This object must be specified before the circuit can run the IS-IS protocol. It cannot be changed after it has been specified.

Capacity of the buffer pool used by the DL stub to send data signals to the SDC. This object follows the replaceOnlyWhileDisabled behavior.

Capacity of the buffer pool into which SDC transfers data signals from the DL Stub. This object follows the replaceOnlyWhileDisabled behavior.

Capacity of the buffer pool used by SDC to send indications to PM. This object follows the replaceOnlyWhileDisabled behavior.

Maximum size of PDU that can be sent or received over this circuit (MTU). This object follows the replaceOnlyWhileDisabled behavior.

The physical address of the network interface (for example a MAC address on an Ethernet card). This value is only relevant to a broadcast circuit and is ignored on a point-to-point circuit. It needs to be specified in the MIB if the information is not obtained from the I3 stub. This object follows the replaceOnlyWhileDisabled behavior.

Has this circuit been configured by MIB (manual), I3 information (automatic) or both? MIB configuration overrides I3 configuration. Automatic circuits cannot be destroyed. Destroying a manual circuit removes all configuration from that circuit from DC-ISIS. Destroying a circuit in state 'both' destroys any MIB configuration and returns the circuit to automatic state. Enumeration: 'automatic': 2, 'manual': 1, 'both': 3.

Is the T1 timer running on this circuit? This object is only valid on a circuit that is currently running the IS-IS protocol (isisCircExtDomain is 'false' and isisCircOperState is 'operStatusUp'). When set to 'true', this indicates that the local node is running starting or restarting node procedures.

Which protocols are supported on this circuit? Note that the configured value is used in conjunction with the value of isisSysProtSupported. In particular: - IPv4 is supported on the circuit if both isisSysProtSupported and this object have the 'ipv4' bit set - IPv6 is supported on the circuit if both isisSysProtSupported and this object have the 'ipv6' bit set.

Allows a broadcast circuit to be configured to operate point-to-point over LAN procedures. This is used in conjunction with the isisCircType object as follows. - If isisCircType = 'ptToPt', the circuit is a standard point-point circuit, and isisCircPtToPtOverLAN is ignored. - If isisCircType = 'broadcast' and isisCircPtToPtOverLAN is 'false', the circuit is used as a normal LAN. - If isisCircType = 'broadcast' and isisCircPtToPtOverLAN is 'true', point-point over LAN procedures are followed. Point-to-point over LAN procedures should only be configured when there are just two Intermediate Systems operating on the LAN. This object follows the replaceOnlyWhileDisabled behavior.

Indicates the protocols running on this circuit for which Bidirectional Forwarding Detection (BFD) is desired. If isisCircProtBfdDesired is clear for an address type, then BFD sessions are not established to peers for that address type. If isisCircProtBfdDesired is set for an address type, then a BFD session is established to each peer that supports BFD for that address type. The object isisISAdjProtSuppBfdStatus provides BFD status for each address type. This object can be modified at any time.

This table contains the set of IP Addresses configured on all circuits.

Each entry contains one IP Address configured on a circuit.

The type of IP address. Those of type manual are created by the network manager. Those of type automatic are created through propagation of interface information from the I3 stub. This object cannot be modified after creation, and follows the manualOrAutomatic behavior. Enumeration: 'automatic': 2, 'manual': 1, 'both': 3.

An index to this table which identifies the IP addresss to which this entry belongs. This object follows the manualOrAutomatic behavior.

The existence state of this IP address. This object follows the RowStatus and manualOrAutomatic behaviors.

Administrative state of this IP address. This object follows the AdminState and manualOrAutomatic behaviors. The system level isisSysAllowAutoI3Config field defines the initial administrative state for IP addresses that are configured automatically from the I3 stub. If isisSysAllowAutoI3Config is 'true' then automatic addresses initially have administrative state 'on'; otherwise they initially have administrative state 'off'.

The Inet type of this IP Address. This object follows the manualOrAutomatic behavior.

One IP Address configured on this circuit. This field must be present on row creation and cannot be modified after creation. This address must be unique among all manual IP addresses configured on this circuit. If a manual address matches an automatic IP address on this circuit then the manual address takes precedence, and the automatic address is not used by DC-ISIS. This address is guaranteed to be unique among all automatic addresses on this circuit.

Is this IP address advertised in TLV 132 in LSPs sent out by this intermediate system? This object follows the manualOrAutomatic behavior.

A row in this table represents the manual configuration of support for a topology on this circuit. Rows in this table are created and destroyed by an administrator to provide per-circuit multi-topology configuration. Note that the presence of a row in this table overrides the default multi-topology settings for the given circuit and topology.

An isisMtCircManConfigEntry is created to provide multi-topology specifc circuit configuration.

The topology that this row represents.

The state of the MIB row. Turning this to state 'destroy' forces the router to forget the manually configured multi-topology configuration for this circuit. Setting the state to 'notInService' stops the manual multi-topology configuration being used, but retains the configuration.

The desired operational state for the manual configuration of this topology on this circuit. Setting this object to the value 'on' when its current value is 'off' enables use of the manual configuration for this topology on this circuit.

The current operational status of the manual configuration for this topology on this circuit.

The level 1 wide metric value of this circuit for this topology. Note that topologies other than MT ID 0 always use wide metrics. For multi-topology ID zero (the base topology), this field is read only. The level 1 metric for the base topology is configured using the isisCircLevelWideMetric field in the isisCircLevelTable.

The level 2 wide metric value of this circuit for this topology. Note that topologies other than MT ID 0 always use wide metrics. For multi-topology ID zero (the base topology), this field is read only. The level 2 metric for the base topology is configured using the isisCircLevelWideMetric field in the isisCircLevelTable.

A row in this table represents the current support for a topology on this circuit. A row exists in this table for every row in the isisCircTable and every row in the isisMtSysTable.

An isisMtCircStatusEntry details the status of a topology on a circuit.

The topology that this row represents.

The current operational state of this topology on this circuit. If no corresponding row exists in the isisMtCircManConfigTable then this is derived from the isisMtSysDefaultActive field in the isisMtSysTable row. Otherwise, this is derived from a combination of the isisMtSysOperState field in the isisMtSysTable and the isisMtCircManOperState field in the isisMtCircManConfigTable row.

The level 1 wide metric value of this circuit for this topology. Note that topologies other than MT ID 0 always use wide metrics. If no corresponding row exists in the isisMtCircManConfigTable then this is derived from the isisCircLevelWideMetric field in the level 1 isisCircLevelTable. Otherwise, this is derived from the isisMtCircManL1WideMetric field in the isisMtCircManConfigTable row.

The level 2 wide metric value of this circuit for this topology. Note that topologies other than MT ID 0 always use wide metrics. If no corresponding row exists in the isisMtCircManConfigTable then this is derived from the isisCircLevelWideMetric field in the level 2 isisCircLevelTable. Otherwise, this is derived from the isisMtCircManL2WideMetric field in the isisMtCircManConfigTable row.

Level specific information about circuits used by IS-IS.

An isisCircLevelEntry exists for each level on each circuit used by Integrated IS-IS on this system.

The level that this entry describes. Enumeration: 'none': 0, 'level2IS': 2, 'level1IS': 1.

The metric value of this circuit for this level.

The wide metric value of this circuit for this level.

The priority for becoming LAN Designated Intermediate System at this level.

A one byte identifier for the circuit selected by the Intermediate System. On point-to-point circuits, the value is used as the Local Circuit ID in point-to-point IIH PDUs transmitted on this circuit. In this case, values of isisCircLevelIDOctet do not need to be unique. For broadcast circuits, the value is used to generate the LAN ID that will be used if this Intermediate System is elected as the Designated IS on this circuit. The value is required to differ on LANs where the Intermediate System is the Designated Intermediate System.

On a point to point circuit with a fully initialized adjacency to a peer IS, the value of this object is the circuit ID negotiated during adjacency initialization. On a point to point circuit without such an adjacency, the value is the concatenation of the local system ID and the one byte isisCircLevelIDOctet for this circuit i.e. the value that would be proposed for the circuit ID. On other circuit types, the value returned is the zero length OCTET STRING.

The ID of the LAN Designated Intermediate System on this circuit at this level. If, for any reason, this system is not partaking in the relevant Designated Intermediate System election process, then the value returned is the zero length OCTET STRING.

This value is multiplied by the corresponding HelloTimer and the result in seconds (rounded up) is used as the holding time in transmitted hellos, to be used by receivers of hello packets from this IS.

Maximum period, in milliseconds, between IIH PDUs on multiaccess networks at this level for LANs. The value at L1 is used as the period between Hellos on L1L2 point to point circuits. Setting this value at level 2 on an L1L2 point to point circuit will result in an error of InconsistentValue. This object follows the resettingTimer behavior.

Period, in milliseconds, between Hello PDUs on multiaccess networks when this IS is the Designated Intermediate System. This object follows the resettingTimer behavior.

Minimal interval of time, in milliseconds, between transmissions of LSPs on an interface at this level.

Minimum interval, in milliseconds, between re-transmission of an LSP at this level. This object follows the resettingTimer behavior. Note that isisCircLevelLSPThrottle controls how fast we send back to back LSPs. This variable controls how fast we re-send the same LSP.

Interval of time, in seconds, between periodic transmission of a complete set of CSNPs on multiaccess networks if this router is the designated router at this level. This object follows the resettingTimer behavior.

Minimum interval in seconds between sending Partial Sequence Number PDUs at this level. This object follows the resettingTimer behavior.

Boost to add to the priority of this router (up to the maximum permitted value) when it becomes DIS at this level to make it more likely to remain DIS.

Authentication user data for this level's authentication. This data is passed opaquely to the Metaswitch authentication interface where it can be used to assist with authentication decisions.

The hostname corresponding to the system ID part of the isisCircLevelID object. This is the null string if the isisCircLevelID object is null, or if no hostname is known.

The hostname corresponding to the system ID part of the isisCircLevelDesIS object. This is the null string if the isisCircLevelDesIS object is null, or if no hostname is known.

The minimum interval between reception of new instances of a particular LSP. LSP instances received at higher frequencies are discarded. If set to zero then no check is made on the frequency of LSP reception. This object follows the resettingTimer behavior.

System wide counters for one instance of the IS-IS protocol on the system.

System-wide IS-IS counters.

The level that this entry describes. Enumeration: 'none': 0, 'level2IS': 2, 'level1IS': 1.

Number of corrupted in-memory LSPs detected. LSPs received from the wire with a bad checksum are silently dropped and not counted. LSPs received from the wire with parse errors are counted by isisSysStatLSPError.

The number of authentication type mismatches recognized by this instance of the protocol.

The number of authentication failures recognized by this instance of the protocol.

Number of times the LSP database has become overloaded.

Number of times a manual address has been dropped from the area.

Number of times the IS has attempted to exceed the maximum sequence number.

Number of times a sequence number skip has occurred.

Number of times a zero-aged copy of the system's own LSP is received from some other node.

Number of times a PDU is received with a different value for ID field length to that of the receiving system.

Partition changes.

Number of times we ran SPF at this level.

The count of badly formed LSPs discarded by the PM component of DC-ISIS.

The count of badly formed CSNPs discarded by the PM component of DC-ISIS.

The count of badly formed PSNPs discarded by the PM component of DC-ISIS.

The count of received LSPs that are queued internally in the PM component of DC-ISIS, awaiting processing.

Number of LSP fragments that the local system has generated.

Number of LSPs that have been retransmitted.

Number of LSPs that have been regenerated. An LSP is regenerated when it is nearing the end of its lifetime and it has not changed.

Number of LSP purges that have been initiated by this instance of IS-IS.

The number of LSPs in the database at this level.

Number of LSP purges initiated by this instance of IS-IS, of LSPs that were originated locally. This field behaves like an SNMP counter. It only increases, never decreases, and is subject to wrap. The absolute value of an SNMP counter has no meaning. Applications use the difference between counter values at different times to display count changes. The absolute value of this counter does have meaning, until it first wraps.

Number of LSP purges initiated by this instance of IS-IS, of LSPs that were originated remotely. This field behaves like an SNMP counter. It only increases, never decreases, and is subject to wrap. The absolute value of an SNMP counter has no meaning. Applications use the difference between counter values at different times to display count changes. The absolute value of this counter does have meaning, until it first wraps.

Number of LSP purges initiated by this instance of IS-IS, of LSPs that were originated remotely, due to receiving a SNP. This field behaves like an SNMP counter. It only increases, never decreases, and is subject to wrap. The absolute value of an SNMP counter has no meaning. Applications use the difference between counter values at different times to display count changes. The absolute value of this counter does have meaning, until it first wraps.

Number of LSP purges initiated by this instance of IS-IS, of LSPs that were originated remotely, because they have expired. This field behaves like an SNMP counter. It only increases, never decreases, and is subject to wrap. The absolute value of an SNMP counter has no meaning. Applications use the difference between counter values at different times to display count changes. The absolute value of this counter does have meaning, until it first wraps.

Number of LSP purges initiated by this instance of IS-IS, of LSPs that were originated remotely, due to peer restart. This field behaves like an SNMP counter. It only increases, never decreases, and is subject to wrap. The absolute value of an SNMP counter has no meaning. Applications use the difference between counter values at different times to display count changes. The absolute value of this counter does have meaning, until it first wraps.

Circuit specific counters for this Intermediate System.

An isisCircuitCounterEntry exists for each circuit used by Integrated IS-IS on this system.

What type of circuit saw these counts? The point to point Hello PDU includes both L1 and L2, and ISs form a single adjacency on point to point links. Thus we combine counts on point to point links into one group. Enumeration: 'lanlevel2': 2, 'lanlevel1': 1, 'p2pcircuit': 3.

The number of times an adjacency state change has occurred on this circuit.

The number of adjacencies on this circuit.

The number of times initialization of this circuit has failed. This counts events such as PPP NCP failures. Failures to form an adjacency are counted by isisCircRejAdjs.

The number of times an adjacency has been rejected on this circuit.

The number of times an IS-IS control PDU with an ID field length different to that for this system has been received.

The number of times an IS-IS control PDU with a max area address field different to that for this system has been received.

The number of times an IS-IS control PDU with an auth type field different to that for this system has been received.

The number of times an IS-IS control PDU with the correct auth type has failed to pass authentication validation.

The number of times the Designated IS has changed on this circuit at this level. If the circuit is point to point, this count is zero.

Information about IS-IS protocol traffic at one level on one circuit in one direction.

Information about IS-IS protocol traffic at one level on one circuit in one direction

The level at which these PDU counts have been collected. Enumeration: 'level1': 1, 'none': 0, 'level2': 2.

Were we sending or receiving these PDUs? Enumeration: 'sending': 1, 'receiving': 2.

The number of IS-IS Hello PDUs seen in this direction at this level. Point-to-Point IIH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.

The number of ES-IS Hello PDUs seen in this direction. ISH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.

The number of ES Hello PDUs seen in this direction. ESH PDUs are counted at the lowest enabled level: at L1 on L1 or L1L2 circuits, and at L2 otherwise.

The number of IS-IS LSPs seen in this direction at this level.

The number of IS-IS CSNPs seen in this direction at this level.

The number of IS-IS PSNPs seen in this direction at this level.

The number of unknown IS-IS PDUs seen at this level.

The number of IIH PDUs that have been discarded. This field is always zero for outgoing PDUs.

The number of LSP PDUs that have been discarded by the SDC component of DC-ISIS. This field is always zero for outgoing PDUs.

The number of CSNP PDUs that have been discarded by the SDC component of DC-ISIS. This field is always zero for outgoing PDUs.

The number of PSNP PDUs that have been discarded by the SDC component of DC-ISIS. This field is always zero for outgoing PDUs.

The table of adjacencies to Intermediate Systems.

Each entry corresponds to one adjacency to an Intermediate System on this system.

A unique value identifying the IS adjacency from all other such adjacencies on this circuit. This value is automatically assigned by the system when the adjacency is created.

The state of the adjacency. Enumeration: 'down': 1, 'failed': 4, 'up': 3, 'initializing': 2.

The 3Way state of the adjacency. These are picked to match the historical on-the-wire representation of the 3Way state, and are not intended to match isisISAdjState. Enumeration: 'down': 2, 'failed': 3, 'up': 0, 'initializing': 1.

The SNPA address of the neighboring system.

The type of the neighboring system. Enumeration: 'l1IntermediateSystem': 1, 'l1L2IntermediateSystem': 3, 'l2IntermediateSystem': 2, 'unknown': 4.

The system ID of the neighboring Intermediate System.

The 4 byte Extended Circuit ID learned from the Neighbor during 3-way handshake, or 0.

How is the adjacency used? On a point-to-point link, this might be level1and2, but on a LAN, the usage will be level1 on the adjacency between peers at L1, and level2 for the adjacency between peers at L2. Enumeration: 'level1': 1, 'level2': 2, 'reserved': 0, 'level1and2': 3.

The holding time in seconds for this adjacency. This value is based on received IIH PDUs and the elapsed time since receipt.

Priority of the neighboring Intermediate System for becoming the Designated Intermediate System.

If the isisISAdjState is in state 'up', the value of sysUpTime when the adjacency most recently entered the state 'up', or 0 if it has never been in state 'up'.

Does the neighbor support restart signalling? This object is set to 'true' if the peer includes the restart TLV in IIH PDUs.

Is the peer currently restarting? Set to 'notRestarting' if the neighbor is not restarting (is not including a restart TLV in the IIH, or is not setting the RR bit). Set to 'restartingNoHelp' if the neighbor is restarting (is including a restart TLV with the RR bit in IIH PDUs), but the local node is not helping the restart. Set to 'helpingRestart' if the neighbor is restarting and the local node is helping the restart. Enumeration: 'helpingRestart': 3, 'notRestarting': 1, 'restartingNoHelp': 2.

Has the peer requested that the adjacency be suppressed? If set to 'true', the adjacency will not be added to the local LSP. This object is set to 'true' if the peer sets the SA bit in the restart TLV in IIH PDUs.

On a broadcast circuit, the LAN ID reported by the neighbor for the Designated Intermediate System on this circuit at this level. For a non-broadcast circuit, or if, for any reason, the neighbor is not partaking in the relevant Designated Intermediate System election process, then the value returned is the zero length OCTET STRING.

The hostname corresponding to isisISAdjNeighSysID. This is the null string if isisSdEntMapHostnames is 'false' or if no hostname is known.

The hostname corresponding to the system ID part of the isisISAdjNeighLanID object. This is the null string if the isisISAdjNeighLanID object is null, if isisSdEntMapHostnames is 'false', or if no hostname is known.

This table contains the set of Area Addresses of neighboring Intermediate Systems as reported in received IIH PDUs.

Each entry contains one Area Address reported by a neighboring Intermediate System in its IIH PDUs.

An index for the areas associated with one neighbor. This provides a simple way to walk the table.

One Area Address as reported in IIH PDUs received from the neighbor.

This table contains the set of IP Addresses of neighboring Intermediate Systems as reported in received IIH PDUs. If the isisSysRestrictLanAdjsToSubnet object in isisSysTable is set to 'true' then for an IPv4 broadcast circuit, only IP addresses on the same subnet as the local circuit are included in this table.

Each entry contains one IP Address reported by a neighboring Intermediate System in its IIH PDUs.

An index to this table which identifies the IP addresss to which this entry belongs.

The type of one IP Address as reported in IIH PDUs received from the neighbor.

One IP Address as reported in IIH PDUs received from the neighbor.

This table contains the set of protocols supported by neighboring Intermediate Systems as reported in received IIH PDUs.

Each entry contains one protocol supported by a neighboring Intermediate System as reported in its IIH PDUs.

One supported protocol as reported in IIH PDUs received from the neighbor.

Whether local configuration allows use of this protocol to this neighbor. The value 'false' indicates that the protocol is unusable.

BFD session state for this protocol. The state inactive(2) indicates that the protocol is unusable for forwarding because a BFD session cannot be established or has failed. Enumeration: 'active': 1, 'adminDown': 3, 'noContact': 4, 'inactive': 2, 'notRequired': 0.

This table contains the set of topologies supported by neighboring Intermediate Systems as reported in received IIH PDUs.

Each entry contains one topology reported by a neighboring Intermediate System in its IIH PDUs.

A topology that is supported on this adjacency.

Whether this topology is also supported locally on this circuit. The value is 'true' if there is a corresponding row in the isisMtCircStatusTable with isisMtCircStatusOperState set to 'operStatusUp'. In this case, IS-IS will advertise reachability to this neighbor in this topology.

The table of IP Reachable Addresses to networks, subnetworks or hosts, learned automatically. DC-ISIS does not support the manual addition of entries using this table. This table is read-only. In order to specify reachable addresses manually, configure a static route in the Address Family Manager, and configure the AFM to pass the static route into DC-ISIS. In DC-RTM, this can be done using the static routes table (rtmStaticRtTable), and the redistribution table (rtmRedistTable).

Each entry defines an IP Reachable Address to a network, subnetwork or host. Each IP Reachable Address may have multiple entries in the table, one for each equal cost path to the reachable address.

The type of this IP Reachable Address.

The destination of this IP Reachable Address. This is either a network address, subnetwork address or host address.

The length of the IP Netmask for Reachability Address.

Index of next hop. Used when there are multiple Equal Cost Multipath alternatives for the same destination.

The type of the IP next hop address. For the DC-ISIS implementation, this field is not stored and is therefore not returned in GETs for this MIB.

The IP next hop to this destination. For the DC-ISIS implementation, this field is not stored and is therefore not returned in GETs for this MIB.

The type of this IP Reachable Address. Those of type manual are created by the network manager. Those of type automatic are created through propagation of routing information from another routing protocol. DC-ISIS only supports automatic entries in this table. These are learnt from an Address Family Manager (for example, DC-RTM), or from the I3 stub. Enumeration: 'automatic': 2, 'manual': 1, 'both': 3.

The state of this IP Reachable Address. This object follows the ExistenceState behavior.

The administrative state of the IP Reachable Address. This object follows the AdminState behavior.

The metric value for reaching the specified destination over this circuit.

Indicates whether the metric is internal or external.

The wide metric value for reaching the specified destination over this circuit.

The SNPA Address to which a PDU may be forwarded in order to reach a destination which matches this IP Reachable Address. DC-ISIS does not support this field.

The origin of this route. Enumeration: 'isis': 5, 'igrp': 7, 'direct': 2, 'rip': 6, 'ospfv3': 4, 'bgp': 9, 'eigrp': 8, 'other': 10, 'static': 1, 'ospfv2': 3.

The topology that this reachable address is in.

The table of LSP Headers.

Each entry provides a summary describing an LSP currently stored in the system.

At which level does this LSP appear?

The 8 byte LSP ID, consisting of the SystemID, Circuit ID, and Fragment Number.

The sequence number for this LSP.

Is this LSP being purged by this System?

The 16 bit Fletcher Checksum.

The remaining lifetime in seconds for this LSP. For a current LSP (isisLSPZeroLife is 'false'), this indicates the time remaining before the LSP will expire. For an LSP being purged from the system (isisLSPZeroLife is 'true'), the LSP remains in the database for ZeroAgeLifetime, and this will indicate the time remaining before final deletion of the LSP.

The length of this LSP.

Flags carried by the LSP.

The hostname corresponding to the system ID part of the isisLSPID object. This is the null string if no hostname is known.

The contents of each LSP.

Each entry describes an LSP current stored in the system.

The index of this TLV in the LSP. The first TLV has index 1 and the Nth TLV has an index of N.

The sequence number for this LSP.

The 16 bit Fletcher Checksum.

The type of this TLV.

The length of this TLV.

The value of this TLV.

The hostname corresponding to the system ID part of the isisLSPID object. This is the null string if no hostname is known.

An Octet String that uniquely identifies a Link State PDU.

Holds up to 64 initial bytes of a PDU that triggered the notification.

Holds the System ID length reported in PDU we received.

Holds the Max Area Addresses reported in a PDU we received.

The current state of an adjacency. Enumeration: 'down': 1, 'failed': 4, 'up': 3, 'initializing': 2.

An offset to a problem in a PDU. If the problem is a malformed TLV, this points to the begining of the TLV. If the problem is in the header, this points to the byte that is suspicious.

The type for a malformed TLV.

The unique identifier of the Integrated IS-IS instance for this notification.

The system level for this notification.

An Area Address.

A unique value identifying the IS adjacency from all other such adjacencies on this circuit.

The current state of the DIS. Enumeration: 'remote': 2, 'none': 3, 'local': 1.

The current state of attachment. Enumeration: 'notAttached': 2, 'attached': 1.

The system ID of the neighboring Intermediate System.

The topology for which the IS-IS instance is entering or leaving attached state.

This table contains information on joins on which the Protocol Manager acts as a slave. Each row in this table represents one slave join in the Protocol Manager.

Represents a join for which the Protocol Manager is slave.

Identifies the interface provided on this slave join.

Index which uniquely identifies the master entity among other entities of the same component within this instance of DC-ISIS.

The status of the slave join.

This table controls which entities the Protocol Manager should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row. Only routing protocol joins may be configured in this MIB. Rows in this table for other join types are read only.

Represents a join for which the Protocol Manager is master.

Identifies the interface required of this master join. This object follows the index behavior.

Identifies the slave entity to join with. This index is used in the join user data, to enable FTI-specific code within System Manager to select a suitable slave entity. This object follows the index behavior.

Identifies the slave entity to join with. This is used along with the isisPmMjSlaveEntity (with address subtype 'none') in the join user data on an RPI join, to enable FTI-specific code within System Manager to select a suitable slave entity. The value is 'none' if isisPmMjInterface is not ifRtProtoInput. This object follows the index behavior.

The row status for this master join, used to create and destroy table entries.

The administrative status of this master join, used to start and stop the join.

The current operational status of this master join.

The status of the master join.

The topology that this join is for. Note that this only applies to RPI joins. If multi-topology IS-IS is not supported then this field should be set to zero. This object follows the index behavior.

Identifies the sub address family this join is for. Note that this only applies to RPI joins. The value is ignored if isisPmMjInterface is not ifRtProtoInput.

The table of IGP shortcut tunnel interfaces known to DC-ISIS.

Each entry corresponds to one IGP shortcut tunnel interface known to DC-ISIS on this system.

The value of ifIndex for the IGP shortcut tunnel interface.

The Type of IP address for this remote address.

The IP Address value for this remote address.

The type of metric value assigned to this IGP shortcut. The type of metric value can be one of the following. - 'metricTypeAbsolute'; the metric defined by isisShortcutMetricValue is used as the cost of the IGP shortcut. - 'metricTypeRelative'; the metric value defined by isisShortcutMetricValue is added to the IGP-calculated cost of reaching the egress of the shortcut to determine the cost of the IGP shortcut. Note that, in this case, the metric value may be zero, positive or negative. Note also that a minimum value of 1 is defined for the result of the sum of the IGP-calculated cost and a relative metric value.

The metric assigned to this IGP shortcut. If isisShortcutMetricType is set to 'metricTypeAbsolute' then this field takes a value in the range of 1 - 16777215. If isisShortcutMetricType is set to 'metricTypeRelative' then this field takes a value in the range of -16777214 to 16777215.

The operational status of the IGP shortcut interface. The IGP shortcut interface is only usable by DC-ISIS if isisShortcutOperStatus is set to 'up'.

If 'true' then the IGP shortcut interface has been deleted but has not yet been removed from DC-ISIS because it might still be in use as a TE-tunnel next hop.

Each entry in this table represents an SDC entity.

Each entry represents an SDC entity.

Non-zero index which identifies an SDC entity.

The row status for this SDC Entity Table entry, used to create and destroy table entries.

The administrative status of this SDC entity, used to activate and deactivate SDC.

The current operational status of this SDC entity.

Should SDC map system IDs to hostnames? If 'true', SDC will fill in the isisISAdjNeighHostname and isisISAdjNeighLanIDHostname objects (if a hostname is known), and will map system IDs to hostnames in PD logs. Setting this object to 'true' will cause a small occupancy increase, because SDC will set up a database of mappings between the system IDs and the corresponding hostnames.

Should SDC authenticate SNP packets? If 'false', SDC will not check the authentication on SNP packets. If 'true' then it will. Setting this field is sometimes required for interoperability with other routers.

The entity index for the Bidirectional Forwarding Detection (BFD) provider to which this SDC entity should join. Zero indicates that no BFD provider is available, or that SDC should not join to any BFD provider. This field follows the replaceOnlyWhileDisabled behavior.

Flag indicating whether this SDC should prevent an adjacency forming to a neighbor with the same System ID but a different SNPA address as an existing neighbor over the same circuit and level. This field can be changed while SDC is active. Doing so will not affect existing adjacencies, but will affect whether further adjacencies form.

This table controls which entities an SDC entity should join to as master. Each join is represented by a row in this table. The status of each join is represented by a read-only object within each row.

Represents a join for which this SDC entity is master.

Identifies the interface required of this master join. Since an SDC only has a single join on any of its interfaces, this serves with the SDC entity index in uniquely identifying the join. This field follows the replaceOnlyWhileDisabled behavior.

The row status for this master join, used to create and destroy table entries.

The administrative status of this master join, used to start and stop the join.

The current operational status of this master join.

Identifies the slave entity to join with. This index (possibly along with isisSdMjEntityType - see below) is used in the join user data, to enable FTI-specific code within System Manager to select a suitable slave entity. This field follows the replaceOnlyWhileDisabled behavior.

If isisSdMjInterface is ifSubnetDependent, this field indicates the type of entity to join with. This index along with isisSdMjEntityType is used in the join user data to enable FTI-specific code within System Manager to select a suitable slave entity. This field follows the replaceOnlyWhileDisabled behavior.

The status of the master join.

This notification is generated when the system enters or leaves the Overload state. The number of times this has been generated and cleared is kept track of by isisSysStatLSPDbaseOloads.

This notification is generated when one of the manual areaAddresses assigned to this system is ignored when computing routes. The object isisNotificationAreaAddress describes the area that has been dropped. The number of times this event has been generated is counted by isisSysManAddrDropFromAreas. This notification is edge triggered, and should not be regenerated until an address that was used in the previous computation has been dropped.

A notification sent when we receive a PDU with a different value of the System ID Length. This notification includes an index to identify the circuit where we saw the PDU and the header of the PDU which may help a network manager identify the source of the confusion. This should be an edge-triggered notification. We should not send a second notification about PDUs received on the same circuit.

A notification sent when we receive a PDU with a different value of the Maximum Area Addresses. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edge-triggered notification. We should not send a second notification about PDUs received from the same circuit.

A notification sent when we receive a PDU with our systemID and zero age. This notification includes the circuit Index and router ID from the LSP, if available, which may help a network manager identify the source of the confusion.

A notification sent when we receive a Hello PDU from an IS which does not share any area address. This notification includes the header of the packet, which may help a network manager identify the source of the confusion. This should be an edge-triggered notification. We should not send a second notification about PDUs received from the same circuit.

A notification sent when we receive a Hello PDU from an IS, but do not establish an adjacency for some reason. This should be an edge-triggered notification. We should not send a second notification about PDUs received from the circuit.

A notification sent when an adjacency changes state, entering or leaving state up. The first 6 bytes of the isisPduLspId are the SystemID of the adjacent IS. The isisAdjState is the new state of the adjacency.

This notification is generated when we receive an LSP with a parse error. The isisCircIfIndex holds in index of the circuit on which the PDU arrived. The isisPduFragment holds start of the LSP, and the isisErrorOffset points to the problem. If the problem is a malformed TLV, isisErrorOffset points to start of the TLV and isisErrorTLVType holds the value of the type. If the problem is with the LSP header, isisErrorOffset points to the suspicious byte. The number of such LSPs is accumulated in isisSysStatLSPErrors.

When the sequence number on an LSP we generate wraps the 32-bit sequence counter, we purge and wait to re-announce this information. This notification describes that event. Since these should not be generated rapidly, we generate an event each time this happens. While the first 6 bytes of the LSPID are ours, the other two contain useful information.

When we receive an LSP with our System ID and different contents, we may need to reissue the LSP with a higher sequence number. We send this notification if we need to increase the sequence number by more than one. If two Intermediate Systems are configured with the same System ID, this notification will fire.

A notification sent when the value of isisCircOperState for a circuit changes to operStatusUp, operStatusDown or operStatusActFailed.

A notification sent when the value of isisCircOperState for a circuit not configured to run the IS-IS protocol (such as an external, TE-only or passive circuit) changes to operStatusUp, operStatusDown or operStatusActFailed.

This notification is generated when the IS-IS system changes operational state to operStatusUp, operStatusDown or operStatusActFailed.

An IS-IS instance sends this notification if a received LSP has failed to authenticate.

An IS-IS instance sends this notification if a received Hello has failed to authenticate.

This notification is generated when the Attached state for a topology changes and the topology is operationally up.

An IS-IS instance sends this notification if the DIS changes at level 1 or level 2.

The collections of objects used to manage an IS-IS router.

The collection of objects used to describe an IS-IS Circuit.

The collections of objects used to manage an IS-IS Adjacency.

The objects used to record notification parameters.

The collections of notifications sent by an IS.

The collections of objects used to count protocol PDUs.

The collections of objects used to manage configured IP addresses.

The collections of objects used to observe the LSP Data Base.

The collection of Data Connection additions to the MIB.

The compliance statement for agents that support the IS-IS MIB

The advanced compliance statement for agents that support the IS-IS MIB