Smarts IP: Replaced server is not discovered with the right DNS name; How to force Smarts IP to use specific IP address when discovering device

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:




Problem Description: Devices are being discovered with the wrong DNS name.

In our troubleshooting we found:
The servers can be seen using NSLOOKUP with these names;

• device1 10.2.130.28
• device2 10.2.130.218

When we attempted to discover them, through the Smarts IP domain,  they grab these floating IP names:

• device1-vip.domain.com 10.2.130.13
• device2-vip.domain.com 10.2.130.14

We were using this text in the seed file attempt to force the names through a seed file failed as well:

NAMEORIP=device1 NAMEFORMAT=TM_USESEEDNAME COMMUNITY=xxx ACCESSMODE=ICMPSNMP
NAMEORIP=device2 NAMEFORMAT=TM_USESEEDNAME COMMUNITY=xxx ACCESSMODE=ICMPSNMP

Environment

VMware Smart Assurance - SMARTS

Cause

The IP domain is giving an incorrect, or undesired device names from it's 'getaddr' call.

Resolution

To force Smarts to use a specific IP address and DNS name, add this extra  text in the seedfile- NAMEORIP=10.2.130.28.
Here's an example:

NAMEORIP=10.2.130.28 SEEDNAME=device1 NAMEFORMAT=TM_USESEEDNAME COMMUNITY=xxx ACCESSMODE=ICMPSNMP

NAMEORIP=10.2.130.218 SEEDNAME=device2 NAMEFORMAT=TM_USESEEDNAME COMMUNITY=xxx ACCESSMODE=ICMPSNMP

NOTE: For detailed instructions on how to use the seed file for discovery, see https://support.emc.com/docu46037_Smarts_IP_Manager_9.2_User_Guide.pdf?language=en_US