Smarts NPM: Devices using ISIS MIB RFC4444 (1.3.6.1.2.1.138) are not discovered by Smarts NPM; Is the ISIS MIB RFC4444 supported? What Smarts NPM version is required?

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

This article explains the requirements for Smarts Network Protocol Manager (Smarts NPM) discovery of ISIS objects on devices using the ISIS MIB RFC4444 (1.3.6.1.2.1.138) version that supersedes ISIS MIB 1.3.6.1.3.37.1.5.

Devices using the new  ISIS MIB RFC4444 (1.3.6.1.2.1.138) are not being discovered by Smarts NPM

Environment

VMware Smart Assurance - SMARTS

Cause

Failure to discover devices using the ISIS MIB RFC4444 (1.3.6.1.2.1.138) is because the Smarts NPM version installed in the environment does not support that version of the ISIS MIB.

Resolution

Smarts NPM 9.2.1 or later is required to discover and support devices using ISIS MIB RFC4444 (1.3.6.1.2.1.138) according to the specifications and restrictions described in the following section.

ISIS MIB RFC4444 device support and restrictions
Smarts NPM v9.2.1 and later Smarts NPM versions fully support RFC 4444 devices with the ISIS IPv6 MIB, regardless of device vendor (Cisco or Juniper). Discovery and monitoring support is complete and the ISIS NPM domain manager is able to stitch topologies discovered using RFC -4444 MIBs. However, Smarts NPM support for ISIS RFC 4444 MIB  is only verified and validated for devices with IPv6 configured. For IPv4-only devices using the RFC 4444 ISIS-MIB, the devices will be discovered by the Smarts IP Manager, but will not be listed as part of ISIS_TopologyCollection, so the Smarts NPM ISIS server will not discover the devices.