When module rootnames are loaded, ScanEngine Explorer will display MIBs by modulename with a relative module OID as a suffix. For example, by loading the module root 220.127.116.11.2 for the standard mgmt module, a message containing 2 objects (ifInOctets.1 and ifOutOctets.1) would display as shown.
mgmt.18.104.22.168.10 is the OID for ifInOctets, and mgmt.22.214.171.124.16 is the OID for ifOutOctets. ScanEngine Explorer displays them as OIDs in the mgmt module but one would only know the unique identity by checking an on-line OID definition resource for the mgmt module.
While loading the module name as a root is an improvement, loading the MIB definition file for the MIBs module is the best. This alternative is described in the next section.