Smarts IP: Interfaces without configured IP address are not discovered.

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:


Interfaces without IP addresses configured are not discovered by Smarts IP.

Environment

VMware Smart Assurance - SMARTS

Cause

As per design for Routers, Smarts discovers all Interfaces regardless of whether an IP address is configured for the interface or not. 

For Switches, Smarts verifies if the interface has an IP address configured on it and will then proceed to create the Interface.

This is the basic design of Smarts and is considered well within the generic standards of networking.

Resolution

The IFDescrPatternIFExt parameter in tpmgr-param.conf can be used to force Smarts to discover interface(s) without an IP address configured.

The below example is based on the Juniper EX3300-24T certification which utilizes the Juniper-EX-Series containment driver for discovery of interface with "ge-0/1/0" in the description:

# Juniper EX3300-24t
.1.3.6.1.4.1.2636.1.1.1.2.76 {
     TYPE = Switch
     VENDOR = Juniper
     MODEL = EX3300-24t
     CERTIFICATION = CERTIFIED
     CONT = Juniper-EX-Series
....

1. Add IFDescrPatternIFExt.1.3.6.1.4.1.2636.1.1.1.2.76 *ge-0/1/0* in tpmgr-param.conf (sm_edit conf/discovery/tpmgr-param.conf)
2. Modify Juniper-EX-Series containment driver (sm_edit conf/discovery/DISCOVERY_JUNIPER.import) as per below:

GA_CompoundDriver::Containment-Juniper-EX-Series-Driver {
drivers = {
{"Containment-Create-Interface-Driver", 10},
{"Containment-IfMIB-Stack-Driver", 15},
{"Containment-Create-Interface-Ext-Driver", 20},
{"Juniper-Port-Creation-Driver", 25},
{"DOT3-Duplex-Driver",30},
{"Containment-IfTable-Driver", 35},
{"Juniper-Card-Rel-Driver", 40}
}
waitForCompletion = TRUE
}

Containment-Create-Interface-Ext-Driver was added.

3. Restart domain, then delete and discover the device.