ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Pingable model recreated after modeling the snmp model in Spectrum

book

Article ID: 187877

calendar_today

Updated On:

Products

CA Spectrum CA eHealth

Issue/Introduction

Pingable model recreated after modeling the snmp model in Spectrum

After modeling the UCS AIM in Spectrum, the Fabric Interconnect (FI) is modeled as a Pingable model as expected.

After manually adding the FI as an SNMP device, the Pingable model is automatically deleted as expected. However, after a few minutes the Pingable model is recreated and a duplicate model alarm is asserted on the SNMP and Pingable models.

Cause

The SNMP and Pingable model do not have the same value for the Serial_Number attribute id 0x10030.

The underlying discovery code checks for a current model with the serial number from the UCS Aim. If no model exists with that serial number, then a Pingable model is created ad the Serial_Number attribute 0x10030 is populated with the serial number from the UCS Aim.

Environment

Release : 10.4

Component : Spectrum Core / SpectroSERVER

Resolution

Update the Serial_Number attribute id 0x10030 on the SNMP model with the value of the value of the Serial_Number attribute id 0x10030 from the Pingable model. 

1. Log into OneClick as an ADMIN user

2. Find and select the Pingable model

3. Click on the Attributes tab, filter for the Serial_Number attribute id 0x10030 and note the value

4. Find and select the SNMP model

5. Click on the Attributes tab, filter for the Serial_Number attribute id 0x10030 and update the value from value of the Pingable model 

6. Delete the Pingable model