Operational Defect Database

BugZero updated this defect 58 days ago.

VMware | 471953

Smarts IP: Containment showing duplicate entry on FileSytem for Solairs 10 hosts

Last update date:

3/22/2024

Affected products:

Smart Assurance - SMARTS

Affected releases:

No affected releases provided.

Fixed releases:

No fixed releases provided.

Description:

Symptoms

Duplicate entry on FileSytem for Solairs 10 hostsContainment showing duplicate entry on FileSytem for Solairs 10 hosts

Cause

Bug in Solaris 10 MIB on hrFSMountPoint index and hrStorageDescr index

Resolution

The containment view for FileSystem is based on RootName and not on DisplayName.The RootName for diskIndex is obtained from the hrFSMountPoint and those index which are not listed in the hrFSMountPoint MIB will be obtained from the hrStoreageDescr MIB. Example: Fusion had a total of 43 entries in the hrFSMountPoint MIB where SMARTS relied on the hrFSMountPoint for obtaining the RootName.40: hrFSMountPoint.40 (InternationalDisplayString) /emc/sarray41: hrFSMountPoint.41 (InternationalDisplayString) /emc/wuj642: hrFSMountPoint.42 (InternationalDisplayString) /disks/smrtsupport43: hrFSMountPoint.43 (InternationalDisplayString) /emc/tumman***** SNMP QUERY FINISHED *****40: hrStorageDescr.41 (DisplayString) /emc/mensha/cuda1 [2F.65.6D.63.2F.6D.65.6E.73.68.61.2F.63.75.64.61.31 (hex)]41: hrStorageDescr.42 (DisplayString) /emc/kachak [2F.65.6D.63.2F.6B.61.63.68.61.6B (hex)]42: hrStorageDescr.43 (DisplayString) /emc/sarray [2F.65.6D.63.2F.73.61.72.72.61.79 (hex)]43: hrStorageDescr.44 (DisplayString) /emc/wuj6 [2F.65.6D.63.2F.77.75.6A.36 (hex)]44: hrStorageDescr.45 (DisplayString) /disks/smrtsupport [2F.64.69.73.6B.73.2F.73.6D.72.74.73.75.70.70.6F.72.74 (hex)]45: hrStorageDescr.46 (DisplayString) /emc/tumman [2F.65.6D.63.2F.74.75.6D.6D.61.6E (hex)]***** SNMP QUERY FINISHED *****For the diskIndex 44 and 45, the RootName is obtained from the hrStorageDescr MIB. While looking in the containment view, there will duplicate entries for 44 and 45.If the index mapping were correct in the MIB, then the identical RootNames for all the FileSystem instances would not cause such issue.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Unavailable

Learn More

Search:

...