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

The MIB module for management of the IS-IS protocol.

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.

The existence state (RowStatus) of the IS-IS router. Setting 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 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: 'level1IS': 1, 'level2IS': 2, 'level1L2IS': 3.

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. This value is a 6 byte MAC address. This object follows the ReplaceOnlyWhileDisabled behavior.

Maximum number of paths with equal routing metric value which it is permitted to split between. 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 prvtIsisSysLevelxMinLSPGenInt, and should be at least 300 seconds less than prvtIsisSysMaxAge.

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 state 'waiting' before entering the state 'on'. This object follows the ResettingTimer behavior.

The administrative state of this instance of the Integrated IS-IS protocol. Setting this object to the value 'false' when its current value is 'true' 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 prvtIsisSysMaxLSPGenInt.

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

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

If 'true' then add IP addresses received from the I3 stub to the prvtIsisCircIPAddrTable 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 prvtIsisSysCalcMaxDelay 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. - 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 field is ignored if prvtIsisSysLevelxTEEnabled is 'false'.

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 field is ignored if prvtIsisSysLevelxIPv6TEEnabled is 'false'.

The maximum number of static routes and routes redistributed from other protocols that will be accepted. The action that will be taken when the maximum is exceeded is controlled by prvtIsisSysMaxExternalRoutesAct. 0xFFFFFFFF is a special value indicating that the threshold is infinite.

The action that will be take whenn the number of external routes exceeds prvtIsisSysMaxExternalRoutes. If set to 'log', IS-IS will alert the administrator by logging that the limit has been exceeded. If set to 'suppressExternal', IS-IS 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 to reduce the number of redistributed external routes. In the 'suppressExternal' case, the system is responsible for resynchronizing the set of routes with IS-IS. Enumeration: 'suppressExternal': 2, 'log': 1.

The set of routes (if any) that will be removed from the local LSP 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', IS-IS 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 prvtIsisSysLspFullSuppress is set to 'external', the system is responsible for resynchronizing the set of routes with ISIS. Enumeration: 'none': 2, 'external': 1.

If set to 'true', the database overload flag will be set 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 prvtIsisSysLevelxSetOverload to 'false' for that level.

Indicates if the procedures defined in the IS-IS restart RFC (3847) for helping a peer to restart is implemented. Note that this object has no effect on the local restart behavior, and so may be set independently of prvtIsisSysRestartActivationType and prvtIsisSysRestartAutoResetType.

This object is only used when IS-IS 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, IS-IS 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, IS-IS 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 prvtIsisSysShutdown to 'true' and later to 'false'. Graceful restart procedures will only function correctly if the local LSP has not been purged, and so to initiate a planned restart, prvtIsisSysRestartActivationType 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, IS-IS 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 IS-IS activates with the activation type (prvtIsisSysRestartActivationType or prvtIsisSysRestartAutoResetType) set to 'start' or 'restart'. It defines how long IS-IS will wait to establish adjacencies before completing the start/restart. This object follows the ResettingTimer behavior.

This object is only used when IS-IS activates with the activation type (prvtIsisSysRestartActivationType or prvtIsisSysRestartAutoResetType) set to 'restart'. It defines the maximum time that IS-IS 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 prvtIsisSystemCounter and prvtIsisPacketCounter tables. Note that prvtIsisSysStatsLSPCount is not reset by this object. Reading the value of this field has no meaning.

If IS-IS is operating at both level 1 and level 2, this field indicates how IS-IS 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. Bits: 'reserved': 0, 'ipv4': 1, 'ipv6': 2.

This object only affects IPv4 broadcast circuits. If this is set to 'true', IS-IS 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. - IS-IS overrides the setting of the prvtIsisSysLevelMinLSPGenInt object when such a change occurs, and usually regenerates the local LSP(s) immediately. The only exception is when IS-IS is performing restart procedures as defined in RFC3847. This RFC specifies when IS-IS can update the local LSP during a restart. - IS-IS overrides all of the objects that affect the scheduling of routing calculations, with the exception of the prvtIsisSysCalcThrshRestartLimit 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 prvtIsisSysCalcThrshRestartLimit 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 prvtIsisCircIndTable, prvtIsisDatabaseOverload, prvtIsisManualAddressDrops, prvtIsisIDLenMismatch, prvtIsisMaxAreaAddressesMismatch, prvtIsisOwnLSPPurge, prvtIsisAreaMismatch, prvtIsisRejectedAdjacency, prvtIsisAdjacencyChange and prvtIsisLSPErrorDetected notifications. Bits: 'manualAreaAddressDrops': 2, 'maxAreaAddressMismatch': 4, 'circuitIndication': 0, 'areaMismatch': 6, 'rejectedAdjacency': 7, 'lspErrorDetected': 9, 'idLengthMismatch': 3, 'databaseOverload': 1, 'adjacencyChange': 8, 'ownLspPurge': 5.

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

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

The Overload state of the database at level 1. 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 prvtIsisSysLvl1SetOverload. 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 level 1 ?

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

Do we do Traffic Engineering for IPv4 at level 1 ? Currently only Traffic Engineering at L1 is supported. If Traffic Engineering is enabled, prvtIsisSysLvl1MetricStyle must be set to 'wide' or 'both', and a value must be configured for prvtIsisSysTERouterID. 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 prvtIsisSysProtSupported.

Do we do Traffic Engineering for IPv6 at level 1 ? Currently only Traffic Engineering at L1 is supported. If Traffic Engineering is enabled, a value must be configured for prvtIsisSysIPv6TERouterID. 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 prvtIsisSysProtSupported.

This object is only used when IS-IS activates with the activation type (prvtIsisSysRestartActivationType or prvtIsisSysRestartAutoResetType) set to 'start' or 'restart'. It defines how long IS-IS will wait to complete database synchronization at level 1 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 authentication interface where it can be used to assist with authentication decisions.

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

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

The Overload state of the database at level 2. 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 prvtIsisSysLvl2SetOverload. 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 level 2 ?

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

Do we do Traffic Engineering for IPv4 at level 2 ? Currently only Traffic Engineering at L1 is supported. If Traffic Engineering is enabled, prvtIsisSysLvl2MetricStyle must be set to 'wide' or 'both', and a value must be configured for prvtIsisSysTERouterID. 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 prvtIsisSysProtSupported.

Do we do Traffic Engineering for IPv6 at level 2 ? Currently only Traffic Engineering at L1 is supported. If Traffic Engineering is enabled, a value must be configured for prvtIsisSysIPv6TERouterID. 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 prvtIsisSysProtSupported.

This object is only used when IS-IS activates with the activation type (prvtIsisSysRestartActivationType or prvtIsisSysRestartAutoResetType) set to 'start' or 'restart'. It defines how long IS-IS will wait to complete database synchronization at level 2 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 authentication interface where it can be used to assist with authentication decisions.

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. The area address must have a non-zero length.

The existence state (RowStatus) of the prvtIsisManAreaAddrEntry

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. Received area addresses with a length of zero are ignored.

An area address reported in a Level 1 LSP received by this instance of the IS-IS protocol. Received area addresses with a length of zero are ignored.

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 IP address and prefix length value for this summary address.

The existence state (RowStatus) of this summary address.

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

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

The table represents the routing protocols redistributed into the IS-IS routing domain. Creation of conceptual row in the table starts the redistribution of the specified protocol, which would lead to the injection of routing information from that protocol into IS-IS. Deletion of conceptual row would stop the redistribution of that protocol into the IS-IS.

An entry into the prvtIsisRedistributeTable.

The specific routes redistributed into IS-IS. Enumeration: 'default': 17, 'kernel': 2, 'static': 4, 'connect': 3.

Indicates the status of the row. Setting of this field to active enables the redistribution of the protocol. Setting this field to destroy disables the redistribution of the protocol.

The IS-IS level at which this row applies to. Enumeration: 'level1': 1, 'level2': 2.

The IS-IS protocol metric to assign to the redistributed route.

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

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

The value of ifIndex for the interface to which this circuit corresponds. This object cannot be modified after creation. This is also used as the 3-way circuit ID on point-to-point circuits.

The existence state (RowStatus) of this circuit. 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. 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.

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. This field is currently ignored.

The administrative state of the circuit.

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 prvtIsisCircIfIndex. Only 'broadcast' and 'ptToPt' circuits are currently 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 prvtIsisSysType. This object follows the ReplaceOnlyWhileDisabled behavior. Enumeration: 'level1': 1, 'level2': 2, 'level1L2': 3.

Should we include this interface in LSPs, even if it is not running the IS-IS Protocol? Circuits with prvtIsisCircExtDomain '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 prvtIsisCircMeshGroupEnabled is inactive or blocked, this value is ignored.

Can we send unpadded hellos on LAN circuits? False means LAN Hellos must be padded. Currently only unpadded hellos are supported.

If the circuit is enabled, the value of sysUpTime when prvtIsisCircShutdown 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? Currently the 3-way handshake on point to point circuits is always run.

The value to be used as the extended circuit ID in 3Way handshake. This value is only used if prvtIsisCirc3WayEnabled is true, and must be unique across all circuits on this IS. Currently the value for prvtIsisCircIfIndex is used as the extended circuit ID.

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 for that circuit. Destroying a circuit in state 'both' destroys any MIB configuration and returns the circuit to automatic state. Enumeration: 'manual': 1, 'automatic': 2, '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 (prvtIsisCircExtDomain is 'false' and prvtIsisCircOperState 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 prvtIsisSysProtSupported. In particular: - IPv4 is supported on the circuit if both prvtIsisSysProtSupported and this object have the 'ipv4' bit set. - IPv6 is supported on the circuit if both prvtIsisSysProtSupported and this object have the 'ipv6' bit set. Bits: 'reserved': 0, 'ipv4': 1, 'ipv6': 2.

Allows a broadcast circuit to be configured to operate point-to-point over LAN procedures. This is used in conjunction with the prvtIsisCircType object as follows. - If prvtIsisCircType = 'ptToPt', the circuit is a standard point-point circuit, and prvtIsisCircPtToPtOverLAN is ignored. - If prvtIsisCircType = 'broadcast' and prvtIsisCircPtToPtOverLAN is 'false', the circuit is used as a normal LAN. - If prvtIsisCircType = 'broadcast' and prvtIsisCircPtToPtOverLAN 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.

The metric value of this circuit for level 1.

The wide metric value of this circuit for level 1.

The priority for becoming the LAN-Designated Intermediate System at level 1.

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 prvtIsisCircLvl1IDOctet 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 prvtIsisCircLvl1IDOctet 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 level 1. 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 level 1 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 level 1.

Minimum interval, in seconds, between re-transmission of an LSP at level 1. This object follows the ResettingTimer behavior. Note that prvtIsisCircLvl1LSPThrottle 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 level 1. This object follows the ResettingTimer behavior.

Minimum interval in seconds between sending Partial Sequence Number PDUs at level 1. 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 level 1 to make it more likely to remain DIS.

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

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

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

The metric value of this circuit for level 2.

The wide metric value of this circuit for level 2.

The priority for becoming the LAN-Designated Intermediate System at level 2.

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 prvtIsisCircLvl2IDOctet 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 prvtIsisCircLvl2IDOctet 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 level 2. 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 level 2 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 level 2.

Minimum interval, in seconds, between re-transmission of an LSP at level 2. This object follows the ResettingTimer behavior. Note that prvtIsisCircLvl2LSPThrottle 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 level 2. This object follows the ResettingTimer behavior.

Minimum interval in seconds between sending Partial Sequence Number PDUs at level 2. 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 level 2 to make it more likely to remain DIS.

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

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

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 prvtIsisISAdjState. 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, '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 prvtIsisISAdjState 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 prvtIsisISAdjNeighSysID. This is the null string if prvtIsisSdEntMapHostnames is 'false' or if no hostname is known.

The hostname corresponding to the system ID part of the prvtIsisISAdjNeighLanID object. This is the null string if the prvtIsisISAdjNeighLanID object is null, if prvtIsisSdEntMapHostnames 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 prvtIsisSysRstrctLanAdjsToSubnet object in prvtIsisSysTable 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. The type of this address is determined by the value of the prvtIsisISAdjIPAddrType object.

The table of IP Reachable Addresses to networks, subnetworks or hosts, learned automatically. This table is read-only. Manual addition of entries using this table is not supported.

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 type of this address is determined by the value of the prvtIsisIPRADestType object.

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.

The IP next hop to this destination. The type of this address is determined by the value of the prvtIsisIPRANextHopType object.

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. Currently only automatic entries in this table are supported. Enumeration: 'manual': 1, 'automatic': 2.

The administrative state of the IP Reachable Address.

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. This field is currently not supported.

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 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 for this LSP.

The remaining lifetime in seconds for this LSP. For a current LSP (prvtIsisLSPZeroLife is 'false'), this indicates the time remaining before the LSP will expire. For an LSP being purged from the system (prvtIsisLSPZeroLife 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 prvtIsisLSPID object. This is the null string if no hostname is known.

The table of LSPs in the database.

Each entry describes a TLV within an LSP currently 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 for this LSP.

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 prvtIsisLSPID object. This is the null string if no hostname is known.