We observed few devices which changed their system name as same as description.
Release : 3.7
Component : IM Reporting / Admin / Configuration
There was an error requesting sysUpTime during discovery.
Looking at the Vendor Certifications (VCs) in the "System" Metric family:
1) The isKey OIDs for "System Statistics":
<Attribute external="true" name="sysUpTime" type="Long">
<IsKey>true</IsKey>
<Source>1.3.6.1.2.1.1.3.0</Source>
<NeedsDelta>true</NeedsDelta>
</Attribute>
<Attribute external="true" name="sysObjectID" type="ObjectID">
<IsKey>true</IsKey>
<Source>1.3.6.1.2.1.1.2.0</Source>
</Attribute>
All isKey OIDs must be present. So if sysUpTime could not be polled successfully, it moves to the next in the VC priority list.
Looking at the next in the list Checkpoint System Statistics, the isKey OID there is 1.3.6.1.4.1.2620.1.5.6.0, which is
a Checkpoint specific OID which is not supported on the devices:
<Attribute name="haState" external="true" type="OctetString">
<Documentation />
<IsKey>true</IsKey>
<Source>1.3.6.1.4.1.2620.1.5.6.0</Source>
</Attribute>
The third in the list is "Cisco Meraki System Statistics" the isKey OIDs are:
<Attribute name="sysDescr" external="true" type="OctetString">
<Documentation/>
<IsKey>true</IsKey>
<Source>1.3.6.1.2.1.1.1.0</Source>
</Attribute>
<Attribute external="true" name="sysObjectID" type="ObjectID">
<IsKey>true</IsKey>
<Source>1.3.6.1.2.1.1.2.0</Source>
</Attribute>
<Attribute name="sysORUpTime" external="true" type="ObjectID">
<Source>1.3.6.1.2.1.1.9.1.4</Source>
<IsKey>true</IsKey>
<IsIndex>true</IsIndex>
</Attribute>
Which are available and caused a temprary flip to use "Cisco Meraki System Statistics" which used sysDescr for both the name and description:
<Expression destAttr="SystemDescription">sysDescr</Expression>
<Expression destAttr="SystemName">sysDescr</Expression>
The next discovery where sysUpTime is responsive, now the "System Statistics" VC can be supported again, which fixed the name.