Pingable models name fail to be updated in Spectrum

book

Article ID: 49145

calendar_today

Updated On:

Products

CA Spectrum

Issue/Introduction

After discovering and modeling many Pingable models and then running the 'Reevaluate All Model Names' function, the Pingable models names are not changed.

Environment

Release: Any
Component: SPCDIS

Resolution

Pingable, or non-SNMP managed, device models are defined in Spectrum as devices capable only of communication through Ping.

The Model Naming configuration that controls how Spectrum determines the names of models it creates is found on the VNM model for each Landscape. It is found in the VNM models Information tab, in the SpectroSERVER Control section.

The primary two configurations that impact model naming are:

Use Fully Qualified Host Name
Model Naming Order

User Fully Qualified Host Name has a Yes or No setting. If a devices name is device.company.com, if that is set to Yes, it will be named with:

device.company.com

If that is set to No, it will be named with:

device

The default setting is No.

Model Naming Order default settings are:

SysName
IP Address
Name Service

SysName is obtained from the MIB Object of the device that lists its SysName value
IP Address is the IP Address of the device
Name Service is the DNS name of the device, also found through the 'nslookup <IP_Address> command.

The default Spectrum Naming configuration for determining Model Names noted above will result in Pingable models being named with IP Addresses.

If that order is changed after the Pingable models are created, they will be ignored when the 'Reevaluate All Model Names' function is launched and will not be renamed.

There are two other methods of creating Pingable models. The first, the 'Model by Type' option from the Topology tab will also ignore those naming configurations and will create a model named with IP address if the devices name is not specified when setting up the 'Model by Type' option.

The second, Discovery Configurations launched from the Auto Discovery UI, does honor the Model Naming configuration settings. Some examples of model names when using the Discovery configurations are as follows using the example of the device with Fully Qualified Host Name of 'device.company.com':

Model Naming configuration settings:
Use Fully Qualified Host Name = No
Model Naming Order set to:

IP Address
Naming Service
SysName

Pingable model will be created with IP Address as the models name.

Model Naming configuration settings:
Use Fully Qualified Host Name = No
Model Naming Order set to:

Naming Service
SysName
IP Address

Pingable model will be created with 'device' as the models name.

Model Naming configuration settings:
Use Fully Qualified Host Name = Yes
Model Naming Order set to:

Naming Service
IP Address
SysName

Pingable model will be created with 'device.company.com' as the models name.

If you have already discovered the Pingable models prior to properly configuring the Model Naming configuration options and they need to be changed, we are left with two options:

  1. Delete and rediscover the Pingable models through a Discovery Configuration in the Auto Discovery UI
  2. Manually rename the Pingable models