Network Protocol Manager for IS-IS sends SNMP requests to Juniper devices to discover routing topology objects and their relationships. It supports SNMPv1, v2c, and v3 access to the IS-IS MIB objects that are defined in RFC 1195.

Because the IS-IS MIB is used by Juniper devices but not by Cisco devices, Network Protocol Manager for IS-IS uses SNMP discovery and SNMP polling to discover and monitor the IS-IS topology for Juniper devices, and uses CLI discovery and CLI polling to discover and monitor the IS-IS topology for Cisco devices. The CLI commands that are invoked for IS-IS discovery are identified in “CLI commands for IS-IS discovery” on page 111, and the CLI commands that are invoked for IS-IS monitoring are identified in the VMware Smart Assurance Network Protocol Manager Configuration Guide .

For Juniper devices, Network Protocol Manager for IS-IS reads the IS-IS MIB objects that are identified in this section to discover the following routing topology objects and their relationships:

  • IS-IS areas

  • IS-IS services

  • IS-IS networks

  • IS-IS interfaces

  • IS-IS neighbor endpoints

  • IS-IS adjacencies

    After discovering and creating the IS-IS topology objects in its repository, Network Protocol Manager for IS-IS monitors the status of the IS-IS objects by periodically establishing SNMP sessions to the managed devices and polling the IS-IS MIB objects that are identified in the VMware Smart Assurance Network Protocol Manager Configuration Guide .

    MIB objects accessed for IS-IS discovery lists the discovery IS-IS MIB objects that are accessed by Network Protocol Manager for IS-IS.

Table 1. MIB objects accessed for IS-IS discovery

MIB object

OID

Description

Module

isisISAdjIPAddress

.1.3.6.1.3.37.1.5.3.1.3

One IP Address as reported in IS-IS Hello (IIH) protocol data units (PDUs) that are received from the neighbor.

IS-IS MIB

isisISAdjAreaAddress

.1.3.6.1.3.37.1.5.2.1.2

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

IS-IS MIB

isisISAdjNeighSysID

.1.3.6.1.3.37.1.5.1.1.5

System ID and 4-byte circuit ID of the neighboring Intermediate System set from the source ID field of the Three-Way-Handshake information from the neighbor’s IIH PDUs.

IS-IS MIB

isisISAdjNeighSysType

.1.3.6.1.3.37.1.5.1.1.4

Type of the neighboring system:

1 (l1IntermediateSystem)

2 (l2IntermediateSystem)

3 (l1l2IntermediateSystem)

4 (Unknown)

IS-IS MIB

isisISAdjNeighPriority

.1.3.6.1.3.37.1.5.1.1.8

Priority of the neighboring Intermediate System for becoming the:

  • LAN Level-1 (L1) Designated Intermediate System (DIS) if the value of isisISAdjNeighSysType is l1IntermediateSystem.

  • LAN Level-2 (L2) DIS if the value of isisISAdjNeighSysType is l2IntermediateSystem.

  • LAN L1L2 DIS if the value of isisISAdjNeighSysType is l1l2IntermediateSystem.

IS-IS MIB

IS-IS object creation shows the mapping between the discovery MIB objects and the creation of the IS-IS objects.

  1. Discovered MIB Objects

  2. isisISAdjIPAddress

  3. Created IS-IS Objects

  4. ISISArea

  5. Created IS-IS Objects

  6. ISISService

  7. isisISAdjAreaAddress

  8. ISISInterface

  9. ISISNeighborEndpoint

  10. isisISAdjNeighSysID

  11. ISISAdjacency

  12. ISISNetwork

  13. (Created from AM-created IPNetwork object)

Figure 1. IS-IS object creation