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/sarray
41: hrFSMountPoint.41 (InternationalDisplayString) /emc/wuj6
42: hrFSMountPoint.42 (InternationalDisplayString) /disks/smrtsupport
43: 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.