Possible Cause: The IPGROPER module is not running.
Action: Check if IPGROPER is running in NetExplorer IP host discovery. If IPGROPER is not running, configure it to run. For more information, see "Choosing Which Discovery Modules to Load" in "Understanding Network Discovery and Atlas Management" in the Administration guide.
Possible Cause: The bridge discovery is not running.
Action: Check if the bridge discovery is running. To check, you need to perform the following tasks:
Check the log files generated in the following directory: installvolume:\installdirectory\ZENWORKS\MMS\LOGFILES\SLOADER.
Select the SLOADER-bignumber.TXT file which contains the latest modified time stamp.
Search for the string Service Bridge Discovery started successfully. If this string does not exist, start the services.
Possible Cause: The SNMPcommunity string of the switch is not configured in NetExplorer.
Action: You need to configure the SNMP community string. To configure, perform the following tasks:
From ConsoleOne, launch the MIB Browser.
Enter the IP address of the switch.
Enter the SNMP READ/GET community string.
Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).
Click Tree Walk.
If the configuration is correct, the results will be displayed. If the results are not displayed, you need to configure SNMP to discover SNMP devices. For more information see "Starting Discovery" in "Understanding Network Discovery and Atlas Management" in the Administration guide.
Possible Cause: The SNMP information about the switch is incorrect or inadequate for ZfS to discover it as a switch.
Action: If you have verified the SNMP configuration, check for the following SNMP information for the switch.
From ConsoleOne, launch the MIB Browser.
Use the MIB Browser again to select the dot1dBridge FDB table specified by the OID: 1.3.6.1.2.1.17.4.3
Click Tree Walk.
If no results are displayed, ZfS will not be able to recognize this as a switch. Check with the vendor of the switch to resolve the issue. Repeat Step 3 with the dot1dBridge STP table specified by the OID: 1.3.6.1.2.1.17.2.
Possible Cause: Discovery has not run for sufficient time.
Action: If the network is very large, it might take time for NetExplorer to discover the information about the segment. If the router is not discovered or if discovery is taking a long time to discover the router, use the file-based discovery to obtain information about the machine discovered . For information, see "File-Based Discovery" in "Understanding Network Discovery and Atlas Management" in the Administration guide.