Smarts NCM: Model is not getting updated under Physical Hardware in few Cisco IOS device properties
Article ID: 331010
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
Symptoms:
Model is not getting updated under Physical Hardware properties for few devices. Due to this missing model properties under Chassis/Physical Hardware, these devices are not getting fetched in the Device Detail Report.
Device Properties -> General
Model is available.
Device Properties -> Configuration -> Hardware -> Physical Hardware
Model is not available under Chassis information.
Model is not getting updated under Physical Hardware properties for few devices. Due to this missing model properties under Chassis/Physical Hardware, these devices are not getting fetched in the Device Detail Report.
Device Properties -> General
Model is available.
Device Properties -> Configuration -> Hardware -> Physical Hardware
Model is not available under Chassis information.
Environment
VMware Smart Assurance - NCM
Cause
Devices are discovered with both SNMP and SSH credentials.
When SNMP & SSH credentials are provided during device discovery, NCM gives precedence to SNMP for hardware data pull. If only SSH details are provided, then SSH is used.
When we check commmgr.log captured during device hardware pull, below errors are seen, hence the retrieved partial information is only updated on NCM:
Nov 16 09:44:11 1304389376/pull(21702398)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.2.1.47.1.1.1.1.13.1) (syntax:129) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Nov 16 09:44:11 1304389376/pull(21702398)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.9.9.92.1.1.1.3.1) (syntax:128) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Nov 16 09:44:12 1304389376/pull(21702398)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.9.3.6.11.1.1.1) (syntax:129) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
These OIDs are not present/not authorized for snmp get, so the Model name information under Chassis cannot be obtained by NCM.
Below are details of these OIDs, they are of 3 MIBs. These MIBs contain Physical Hardware information on Cisco IOS devices.
1) ENTITY-MIB/entPhysicalTable - .1.3.6.1.2.1.47.1.1.1
entPhysicalModelName - .1.3.6.1.2.1.47.1.1.1.1.13.X
2) ciscoEntityAssetMIB - .1.3.6.1.4.1.9.9.92
ceAssetOrderablePartNumber - .1.3.6.1.4.1.9.9.92.1.1.1.3.x
3) OLD-CISCO-CHASSIS-MIB/cardTableEntry - 1.3.6.1.4.1.9.3.6.11.1
cardIndex - .1.3.6.1.4.1.9.3.6.11.1.1.x
Contact your local network administrator for configuration of these MIBs on the device.
When SNMP & SSH credentials are provided during device discovery, NCM gives precedence to SNMP for hardware data pull. If only SSH details are provided, then SSH is used.
When we check commmgr.log captured during device hardware pull, below errors are seen, hence the retrieved partial information is only updated on NCM:
Nov 16 09:44:11 1304389376/pull(21702398)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.2.1.47.1.1.1.1.13.1) (syntax:129) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Nov 16 09:44:11 1304389376/pull(21702398)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.9.9.92.1.1.1.3.1) (syntax:128) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
Nov 16 09:44:12 1304389376/pull(21702398)#1: Error in validating Oid: RTSNMPVar::getDASLValueFromVb: Can't read OID(1.3.6.1.4.1.9.3.6.11.1.1.1) (syntax:129) -- NOSUCHOBJECT/NOSUCHINSTANCE/ENDOFMIBVIEW (TSNOTE) (RTSNMPVar.cpp#640)
These OIDs are not present/not authorized for snmp get, so the Model name information under Chassis cannot be obtained by NCM.
Below are details of these OIDs, they are of 3 MIBs. These MIBs contain Physical Hardware information on Cisco IOS devices.
1) ENTITY-MIB/entPhysicalTable - .1.3.6.1.2.1.47.1.1.1
entPhysicalModelName - .1.3.6.1.2.1.47.1.1.1.1.13.X
2) ciscoEntityAssetMIB - .1.3.6.1.4.1.9.9.92
ceAssetOrderablePartNumber - .1.3.6.1.4.1.9.9.92.1.1.1.3.x
3) OLD-CISCO-CHASSIS-MIB/cardTableEntry - 1.3.6.1.4.1.9.3.6.11.1
cardIndex - .1.3.6.1.4.1.9.3.6.11.1.1.x
Contact your local network administrator for configuration of these MIBs on the device.
Resolution
As a workaround till the SNMP MIB issue is fixed, SSH can be used for pull hardware details, by disabling SNMP.
To Disable SNMP on a device in NCM:
In the Device Properties, Communication => Update Credentials => In-Band:
In "SNMP Credentials" section, for "SNMP v1/v2/v3" fields, select SNMP Disabled from dragdown and click Save Only.
Execute Pull hardware job on the device. Now NCM will make use of SSH to pull hardware details.
Model information is now updated in Chassis details:
To Disable SNMP on a device in NCM:
In the Device Properties, Communication => Update Credentials => In-Band:
In "SNMP Credentials" section, for "SNMP v1/v2/v3" fields, select SNMP Disabled from dragdown and click Save Only.
Execute Pull hardware job on the device. Now NCM will make use of SSH to pull hardware details.
Model information is now updated in Chassis details:
Feedback
Yes
No
Powered by
