7.1 Troubleshooting NetExplorer

My routers are not discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The NXPIP module is not running.
Action: Check the status of NXPIP through NXPCON. If the NXPIP status is not set to run, set the status of NXPIP to run. For information, see Choosing Which Discovery Modules to Load in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.
Possible Cause: The SNMP community string of the router is not configured in NetExplorer™.
Possible Cause: The router access control prevents the NetExplorer server from retrieving information about using SNMP.
Action: Validate the SNMP configuration issue or the access control issue:

  1. In ConsoleOne®, launch the MIB Browser.

  2. Specify the IP address of the router.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    The results are displayed if you have configured correctly.

If the results are not displayed, you need to configure to discover IP routers.

Possible Cause: The scope is set in such a way that the router cannot be reached from the Management and Monitoring Services site server.
Action: You need to set the scope. For more information, see Changing the Discovery Scope in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.
Possible Cause: The Management and Monitoring Services site server is unable to reach the network where the router is present. For example, there might be a VPN connection between the site server and the router.
Action: If the router cannot be reached from the site server directly:

  1. Specify the IP addresses of the routers in the additional IP router list using NXPCON. For more information, see Specifying a Seed Router and Additional IP Routers in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

My router is discovered as an IP workstation

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The NXPIP module is not running.
Action: Check the status of NXPIP through NXPCON. If the NXPIP status is not set to run, set the status of NXPIP to run.
Possible Cause: The SNMP community string of the router is not configured in NetExplorer.
Possible Cause: The router access control prevents the NetExplorer server from retrieving information about using SNMP.
Action: To validate if there is any SNMP configuration issue or access control issue, you need to perform the following tasks:

  1. In ConsoleOne, launch the MIB Browser.

  2. Enter the IP address of the router.

  3. Enter the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    The results are displayed if you have configured correctly.

If the results are not displayed you need to configure to discover IP routers.

Possible Cause: The scope is set in such a way that the router cannot be reached from the Management and Monitoring Services site server.
Action: You need to set the scope.
Possible Cause: The Management and Monitoring Services site server is unable to reach the network where the router is present. For example, there might be a VPN connection between the site server and the router.
Action: If the router cannot be reached from the site server directly, enter the IP addresses of the routers in the additional IP router list using NXPCON.

My servers are not discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The IPGROPER module is not running.
Action: Check if IPGROPER is running in the NetExplorer IP host discovery. If IPGROPER module is not running, set the module to run. For information, see Choosing Which Discovery Modules to Load in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.
Possible Cause: The SNMP community string of the server is not configured for discovery.
Action: To validate your SNMP configuration:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the server.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    The results are displayed if you have configured correctly.

If the results are not displayed, you need to configure to discover IP routers.

Possible Cause: The scope set for discovery does not contain the address of the server.
Action: You need specify the address of the server in the scope.
Possible Cause: There is a problem with the address information of the server returned by SNMP.
Action: To validate your SNMP configuration:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the server.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II ipAddrTable in the IP group (iso.org.dod.internet.mgmt.mib-2.ip.ipAddrTable.ipAddrentry.ipAdEntAddr).

  5. Click Tree Walk.

    Check if the IP address appears in the list. Specify the correct IP address of the server. You need to wait until the next cycle of discovery for this address to be discovered.

Possible Cause: The network in which the server is present is not discovered because the router connecting the network to the site server is not discovered.
Action: If the machines that are in the same network as the server are not discovered, then check if the router that is connected to the network is discovered. For more information, see My server is discovered as an IP workstation.

If the network is very large, NetExplorer takes longer to discover the information about the server.

Possible Cause: Discovery has not run for a sufficient time.
Action: If the SNMP information is correct, you can use file-based discovery to immediately obtain information about the machine discovered, without waiting for discovery to reach the network in the normal cycles.

My server is discovered as an IP workstation

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The IPGROPER module is not running.
Action: Check if the IPGROPER module is running in the NetExplorer IP host discovery. If the IPGROPER module is not running, set the module to run.
Possible Cause: The SNMP community string of the server is not configured for discovery.
Action: To validate your SNMP configuration:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the server.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    The results are displayed if you have configured correctly.

If the results are not displayed, you need to configure to discover IP routers.

Possible Cause: The scope set for discovery does not contain the address of the server.
Action: You need to set the scope.
Possible Cause: There is a problem with the address information of the server returned by SNMP.
Action: To validate your SNMP configuration:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the server.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II ipAddrTable in the IP group (iso.org.dod.internet.mgmt.mib-2.ip.ipAddrTable.ipAddrentry.ipAdEntAddr).

  5. Click Tree Walk.

    Check if the IP address appears in the list. Specify the correct IP address of the server. You need to wait until the next cycle of discovery for this address to be discovered.

Possible Cause: The network where the server is present is not discovered because the router connecting the network to the site server is not discovered.
Action: If the machines that are in the same network as the server are not discovered, then check if the router that is connected to the network is discovered. For more information, see My router is discovered as an IP workstation.

If the network is very large, NetExplorer will take longer to discover the information about the server.

Possible Cause: Discovery has not run for a sufficient time.
Action: If the SNMP information is correct, you can use file-based discovery to immediately obtain information about the machine discovered, without waiting for discovery to reach the network in the normal cycles.

A network segment is not discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The router connecting the network segment is not discovered.
Action: Check if the router connecting the segment is discovered. For more information, see My router is discovered as an IP workstation.
Possible Cause: The scope is set in such a way that the network segment cannot be discovered.
Action: You need to set the scope.
Possible Cause: Discovery has not run for a sufficient time.
Action: If the network is very large, NetExplorer takes longer to discover the information about the segment. You can use file-based discovery to obtain information about the machine discovered .
Action: To discover the segment, install the Traffic Analysis Agent on the network segment and configure the agent in NXPCON. For more information, seeSpecifying Traffic Analysis Agents to Be Queried by NXPLANZ in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

My segments are displayed under Islands

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The router connecting to the segments is not discovered.
Action: Check if the router connecting the segments is discovered. For more information, see My router is discovered as an IP workstation.

The DNS names of my machines are not displayed

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The IPGROPER module is not running.
Action: Check if IPGROPER is running in the NetExplorer IP host discovery. If IPGROPER is not running, configure the module to run.
Possible Cause: The DNS server information is not configured in the site server.
Action: If IPGROPER is running, check if the resolv.cfg file in the sys:\etc\ directory has the information about the DNS server that contains the DNS information. If the file does not have the information, configure DNS on a NetWare® server, which in turn updates this file.

My switches are not discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
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.
Possible Cause: The bridge discovery is not running.
Action: Check if the bridge discovery is running:

  1. Check the log files generated in the ZENworks_installation_directory\zenworks\mms\ logfiles\sloader directory.

  2. Select the sloader-bignumber.txt file, which contains the latest modified time stamp.

  3. Search for the string, Service Bridge Discovery started successfully. If this string does not exist, start the services.

Possible Cause: The SNMP community string of the switch is not configured in NetExplorer.
Action: Configure the SNMP community string:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the switch.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    If the configuration is correct, the results are displayed. If the results are not displayed, you need to configure SNMP to discover SNMP devices.

Possible Cause: The SNMP information about the switch is incorrect or inadequate for ZENworks Server Management to discover it as a switch.
Action: If you have verified the SNMP configuration, check for the following SNMP information for the switch:

  1. In ConsoleOne, launch the MIB Browser.

  2. Use the MIB Browser again to select the dot1dBridge FDB table specified by the OID: 1.3.6.1.2.1.17.4.3

  3. Click Tree Walk.

    If no results are displayed, ZENworks Server Management cannot 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 a sufficient time.
Action: If the network is very large, it might take time to NetExplorer to discover the information about the segment. If the router is not discovered or if discovery is taking a longer time to discover the router, use the file-based discovery to obtain information about the machine.

My switch is discovered as an IP workstation

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
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.
Possible Cause: The bridge discovery is not running.
Action: Check if the bridge discovery is running:

  1. Check the log files generated in the ZENworks_installation_directory\zenworks\mms\ logfiles\sloader directory.

  2. Select the sloader-bignumber.txt file, which contains the latest modified time stamp.

  3. Search for the string, Service Bridge Discovery started successfully. If this string does not exist, start the services.

Possible Cause: The SNMP community string of the switch is not configured in NetExplorer.
Action: Configure the SNMP community string:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the switch.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    If the configuration is correct, the results are displayed. If the results are not displayed, you need to configure SNMP to discover SNMP devices.

Possible Cause: The SNMP information about the switch is incorrect or inadequate for ZENworks Server Management to discover it as a switch.
Action: If you have verified the SNMP configuration, check for the following SNMP information for the switch:

  1. In ConsoleOne, launch the MIB Browser.

  2. Use the MIB Browser again to select the dot1dBridge FDB table specified by the OID: 1.3.6.1.2.1.17.4.3

  3. Click Tree Walk.

    If no results are displayed, ZENworks Server Management 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.

The map is consolidating and displaying the network segments

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: One or more machines in the network are assigned more than one IP address and are bound to the same MAC address. ZENworks Server Management assumes that the two networks are running on the same segment.
Action: Check the properties of the machines in ConsoleOne to see if machines having more than one IP address are connected to a single MAC address. You need to reconfigure the machines correctly and run discovery again with an empty database.

WARNING:The configuration information about alarms, health reports, etc., is lost If you copy an empty database.

Possible Cause: The data (*.btv) files in the ZENworks_installation_directory\zenworks\mms\nmdisk\ipcache directory are corrupted. The *.btv files are temporary files, which are possibly corrupted because of a server abend.
Action: Perform the following tasks:

  1. Stop NetExplorer.

  2. Delete all the *.btv files.

  3. Restart NetExplorer.

Possible Cause: NXPIP discovery is not running. The status is displayed as Not Loaded in NXPCON.

None of my discovery modules are running, although I did type netxplor. The status is displayed as Waiting in NXPCON

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: NetExplorer was starting using netexplor after sloader. The following message is displayed:

Unable to remove files dat filename with path. You need to manually remove the files from the directory. Restart discovery.

Action: Perform the following tasks:

  1. Stop the discovery services.

    To stop the discovery services, enter stopdis.ncf at the Management server prompt.

    The Consolidator, SN3 discovery, and Bridge discovery services stop.

    Wait until these services are completely stopped.

  2. Start NetExplorer.

    To start NetExplorer, enter netxplor.

  3. Start the discovery services.

    To start discovery services, enter startdis.ncf.

My server name is displayed as an IP address

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: DNS server information has not been configured on the site server.
Possible Cause: SNMP information has not been discovered.
Possible Cause: The System name of the server has not been set.
Action: Perform the following tasks:

  1. Specify the IP address of the server.

  2. Specify the SNMP READ/GET community string.

  3. Select the MIB-II variable sysName in the system group (iso.org.dod.internet.mgmt.mib-2.system.sysName).

  4. Click Tree Walk.

    If the name here is NULL or something incorrect, set the correct name and wait for discovery to refresh the information in its next cycle

For more information see The DNS names of my machines are not displayed and My workstations are not discovered.

I have reset the scope and restarted discovery. The machines that do not belong to the scope are still displayed in the Atlas

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The services were restarted. However, the database that was populated by prior rounds of discovery was used while restarting the services

The machines that have already discovered during the previous cycles of discovery are not removed if ZENworks Server Management services are restarted with a changed scope without resetting.

Action: Copy the empty database and restart the services with the new scope.

WARNING:If you copy the empty database, the configuration information about alarms, health reports, etc., is lost.

Discovery is trying to query machines that I do not want to be discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The machines are reachable from the ZENworks Server Management site server and therefore discovery can access them.
Action: If you want to prevent whole networks from being queried, set a discovery scope to avoid discovery finding out these machines. For more information, see Changing the Discovery Scope in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

If you want exclude certain machines from being discovered, use the SNMP No Access feature as described below:

  1. Launch NXPCON.

  2. Select Configuration Options > SNMP > Edit IP Exclusion List.

  3. Specify the IP addresses of machines that you do not want to discover.

  4. Save the configuration.

  5. Select Activate Changes.

My machines are displayed under the wrong segment

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: Because of over consolidation, several segments are combined into a single segment.
Action: Check the properties of the machines in ConsoleOne to see if machines having more than one IP address are connected to a single MAC address. You need to reconfigure the machines correctly and run discovery again with an empty database.

WARNING:The configuration information about alarms, health reports, etc., is lost If you copy an empty database.

Possible Cause: The subnet masks in the network are incorrectly configured.
Action: Check in your network if there is any machine that has been configured with an incorrect subnet mask and correct that machine. Wait for discovery to refresh the information in the next cycle.
Possible Cause: Incorrect subnet mask or incorrect default mask was specified for the machines discovered using file-based discovery.
Action: If the machines were discovered by file-based discovery, use the correct subnet mask and run file- based discovery again.

The IP/IPX/MAC address information for my machine is incorrect

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The addresses changed after discovery was complete, so discovery has not discovered these machines.
Action: If the addresses have changed after the first cycle of discovery is completed, it might take time to discover the changed information again, depending on the size of the network. Use file-based discovery to refresh the information immediately.
Possible Cause: The addresses have been changed after discovery. The old and new addresses are displayed together.
Action: ZENworks Server Management occasionally displays both the old and new addresses of the machine. Use Database Object Editor to delete the previous address of the machine.
Possible Cause: Outdated information about the machines was received from sources like a Traffic Analysis Agent or a router.
Action: If the machine is not SNMP-configured, it was possibly discovered because of a Traffic Analysis Agent. Try unloading and reloading the agent on the segment where the machine was placed previously. Reloading the agent deletes the old address and enables discovery to retrieve the new address.
Possible Cause: The SNMP information of the machine is displayed incorrectly.
Action: If the machine is SNMP-configured, check the SNMP information of the machine by performing the following tasks:

  1. Launch the MIB Browser from the ZENworks Server Management console.

  2. Specify the IP address of the machine.

  3. Select the MIB-II ipAddrTable in the IP group (iso.org.dod.internet.mgmt.mib-2.ip.ipAddrTable.ipAddrentry.ipAdEntAddr).

  4. Specify the SNMP READ/GET community string.

  5. Click Tree Walk.

    If you get any results at this stage, check if the IP address of the server appears in the list. If it does not, correct the IP address of the server and wait for the address to be discovered in the next cycle.

NOTE:You can use the Database Object Editor to edit the information. Select Prevent Deletion by NetExplorer to retain the information in the database .

My switch has been discovered with empty address information and a name as ’Switch on x.x.x.x’

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The IPGROPER module is not running.
Action: Check if IPGROPER is running in the NetExplorer IP host discovery. If IPGROPER is not running, configure it to run.
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:

  1. Check the log files generated in the ZENworks_installation_directory\zenworks\mms\ logfiles\sloader directory.

  2. Select the sloader-bignumber.txt file, which contains the latest modified time stamp.

  3. Search for the strin,g Service Bridge Discovery started successfully. If this string does not exist, you need to start the services.

Possible Cause: The SNMP community string of the switch is not configured in NetExplorer.
Action: Configure the SNMP community string:

  1. In ConsoleOne, launch the MIB Browser.

  2. Specify the IP address of the switch.

  3. Specify the SNMP READ/GET community string.

  4. Select the MIB-II system group (iso.org.dod.internet.mgmt.mib-2.system).

  5. Click Tree Walk.

    If the configuration is correct, the results are displayed. If the results are not displayed, you need to configure SNMP for discovering SNMP devices. For more information see Starting Discovery in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

Possible Cause: The SNMP information about the switch is incorrect or inadequate for ZENworks Server Management to discover it as a switch.
Action: If you have verified the SNMP configuration, check for the following SNMP information for the switch:

  1. In ConsoleOne, launch the MIB Browser.

  2. Use the MIB Browser again to select the dot1dBridge FDB table specified by the OID: 1.3.6.1.2.1.17.4.3

  3. Click Tree Walk.

    If no results are displayed, ZENworks Server Management cannot 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 a 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 file-based discovery to obtain information about the machine.

My workstations are not discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: There is no Traffic Analysis Agent or router to provide information about the workstations.
Action: Install the Traffic Analysis Agent on the network segment and configure the agent in NXPCON.
Possible Cause: Discovery is not able to reach the segment with the workstations.
Action: For more information, see A network segment is not discovered.

Discovery is running for a long time (many hours). The Atlas contains WAN pages and Islands and both are empty

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The nxp.ini file is corrupted and NetExplorer is unable to discover any components.
Action: Compare the nxp.ini file in ZENworks_installation_directory\zenworks\mms\ mwserver\nmdisk with the nxp.ini file on the ZENworks 7 Server Management product CD. If the nxp.ini file in the installation location does not contain information that is present in the nxp.ini file in the ZENworks 7 Server Management product CD, then you need to perform the following tasks:

  1. Copy the nxp.ini file from the ZENworks 7 Server Management product CD to the ZENworks_installation_directory\zenworks\mms\ mwserver\nmdisk directory.

  2. Edit the nxp.ini file to contain the following section and its corresponding entry: 

    [IPCACHE] PATH = ZENworks_installation_directory\zenworks\mms\mwserver\nmdisk\ipcache\

  3. Restart discovery.

Possible Cause: The server running Management and Monitoring Services is configured as an end node and no other routers are configured in the Seed Router/Additional IP Routers.
Action: By default, discovery requires certain routers to be accessible to start discovering the network. Configure the NetWare server running Management and Monitoring Services as a router and not as an end node. Alternatively, you can configure additional routers.
Action: Install the Traffic Analysis Agent on the network where you want the segment to be discovered and configure the agent in NXPCON.

Multiple machines with the same name are displayed

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: If the DNS names are being duplicated, the DNS server might return the same names for more than one machine.
Action: From ConsoleOne, check if the IP addresses of the machines have the same names. Check if the DNS server is returning the same DNS names for the different IP addresses using NSLOOKUP. Correct the configuration in the DNS server.
Possible Cause: If you have used Imaging to install NetWare servers, the same names are displayed even if the server names have subsequently changed.
Action: Perform the following tasks:

  1. Specify the IP address of the server.

  2. Specify the SNMP READ/GET community string.

  3. Select the MIB-II variable sysName in the system group (iso.org.dod.internet.mgmt.mib-2.system.sysName).

  4. Click Tree Walk.

    If the same name is displayed for all the servers, set the correct name using the MIB Browser for each server and wait for discovery to refresh the information during the next cycle.

My Traffic Analysis Agent is not discovered

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The agent is not loaded on the servers.
Action: Ensure that the agent is loaded on the servers.
Possible Cause: The agents are in a network other than the network where the Management and Monitoring Services site server is running. The SLP and SAP multicasts and broadcasts are stopped on the routers connecting the networks, so ZENworks Server Management is unable to discover them.
Action: If your routers are disabled so they cannot forward multicasts or broadcasts, you need to manually enter the agent in the discovery system.
Possible Cause: The server running the LANZ agent is not discovered.
Action: For information on this scenario, see My server is discovered as an IP workstation.

My Traffic Analysis Agent is discovered as an IP workstation

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: The agent is not loaded on the servers.
Action: Ensure that the agent is loaded on the servers.
Possible Cause: The agents are in a network other than the network where the Management and Monitoring Services site server is running. The SLP and SAP multicasts and broadcasts are stopped on the routers connecting the networks, so ZENworks Server Management is unable to discover them.
Action: If your routers are disabled so they cannot forward multicasts or broadcasts, you need to manually enter the agent in the discovery system.
Possible Cause: The server running the LANZ agent is not discovered.
Action: The server running the LANZ agent might not be discovered. For more information, see My server is discovered as an IP workstation.

There are machines deleted from my network, but I still view them in the Atlas

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: ZENworks Server Management does not delete machines that have been removed from the network.
Action: Use the Database Object Editor to manually delete these machines.

NetExplorer does not have access to any of the routers in my network

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: If NetExplorer does not have access to all the routers in your network, the servers and workstations are not automatically discovered.
Action: In order to discover and manage your servers, use file-based discovery to obtain information about all the machines you want to manage. For more information, see File-Based Discovery in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

The routers in my network are managed by some other company

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Possible Cause: If NetExplorer does not have access to all the routers in your network, the servers and workstations are not automatically discovered.
Action: In order to discover and manage your servers, use file-based discovery to retrieve information about all the machines you want to manage. For more information, see File-Based Discovery in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

NetExplorer is successfully discovering the machines, but the map does not display the discovered machines

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Explanation: This occurs on ZENworks for Servers 3 SP1 or previous versions of ZENworks for Servers 3 installed on NetWare 6 SP2 and above.
Possible Cause: The ZENworks for Servers services were started using the sloader.ncf command before starting the discovery NLM software (netxplor.ncf)
Possible Cause: Discovery was stopped and started without stopping the ZENworks for Servers services. On NetWare 6 SP2 or later, it is possible to restart NetExplorer while SLOADER is still running. Although NetExplorer is successfully discovering the machines, the database is not updated with the information of these discovered machines.
Action: Do the following:

  1. Stop the Discovery services.

    Enter stopdis.ncf at the Management server prompt to stop the Consolidator, SN3 Discovery, and Bridge Discovery services.

    Wait until these services are stopped completely.

  2. Start NetExplorer

  3. Start the Discovery services.

    To start the discovery services, enter startdis.ncf at the Management server prompt.

Unable to add a new node in an unnumbered link segment using the Database Object Editor

Severity: ZENworks 7 Server Management; Management and Monitoring Services; NetExplorer
Explanation: While adding a node to an unnumbered link segment using the Database Object Editor, the following error message is displayed:

The network number of at least one interface must match with the network number of the segment

Possible Cause: ZENworks 7 Server Management does not support adding a node to an unnumbered link segment using the Database Object Editor.