6.2 Discovery Error Messages

NetExplorer: Warning: The available disk space on volume volname is only ’x’ byte(s)

Source: ZENworks 7 Server Management; Management and Monitoring Services; netxplor.nlm
Severity: Warning
Explanation: The volume where the Management Site Server is installed does not have sufficient memory.
Action: Delete unnecessary files to free up memory.

NetExplorer: Warning: The available disk space on volume volname is less than 2 blocks

Source: ZENworks 7 Server Management; Management and Monitoring Services; netxplor.nlm
Severity: Warning
Explanation: The volume where the site server is installed does not have sufficient memory.
Action: Delete unnecessary files to free up memory.

Unable to remove files: datfilename with path. You need to manually remove the files from the directory. Restart discovery

Source: ZENworks 7 Server Management; Management and Monitoring Services; netxplor.nlm
Severity: Critical
Explanation: The NetExplorer™ server was unable to remove the .dat files created during the early cycles of discovery.
Possible Cause: ZENworks Server Management services were started using the sloader.ncf command before starting discovery NLM™ software (netxplor.ncf).
Possible Cause: Discovery was stopped and started without stopping the ZENworks Server Management services.
Action: Perform the following tasks:

  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 completely stopped.

  2. Start NetExplorer.

  3. Start the discovery services.

    To start the discovery services, enter startdis.ncf.

Unable to remove NetExplorer .dat files in zfs_install_volume:\zfs_install_folder\zenworks\mms\mwserver\nmdisk\dat

Source: ZENworks Server Management; Management and Monitoring Services; netxplor.nlm
Severity: Critical
Explanation: The NetExplorer server was unable to remove the .dat files created during the early cycles of discovery.
Possible Cause: ZENworks Server Management services were started using the sloader.ncf command before starting discovery NLM software (netxplor.ncf).
Possible Cause: Discovery was stopped and started without stopping the ZENworks Server Management services.
Action: Perform the following tasks:

  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 completely stopped.

  2. Start NetExplorer.

  3. Start the discovery services.

    To start the discovery services, enter startdis.ncf.

The server does not contain an IP or IPX address. You need to specify an IP or an IPX address. Restart discovery

Source: ZENworks Server Management; Management and Monitoring Services; NetExplorer
Severity: Critical
Explanation: Discovery was unable to obtain a valid IP/IPX™ binding on the local host.
Possible Cause: The IP/IPX address is not bound to any interfaces of the machine.
Action: Verify that the TCP/IP and SPX™/IPX stacks are configured correctly. Ensure that the IP or IPX address is bound to an interface.

Unable to load the nxpip.nlm file. An IP address is not bound to any of the interfaces. Specify an IP address and restart discovery

Source: ZENworks Server Management; Management and Monitoring Services; nxpip.nlm
Severity: Critical
Explanation: The nxpip.nlm was unable to obtain the IP address of the local host.
Possible Cause: An IP address is not bound on this machine. TCP/IP is not configured on this machine.
Action: Verify that a valid IP address is bound to an interface and TCP/IP is configured correctly.

Waiting for netxplor.nlm to load

Source: ZENworks Server Management; Management and Monitoring Services; nxpip.nlm, nxplanz.nlm
Severity: Critical
Explanation: The NetExplorer server is unable remove the .dat files created by earlier cycles of discovery.
Possible Cause: Unable to initialize the NetExplorer server.
Action: Perform the following tasks:

  1. Stop the discovery services.

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

  2. Start NetExplorer.

  3. Start the discovery services.

    To start the discovery services, enter startdis.ncf.

Unable to open IPCache. Please check to see if the following .ddf files exist on the server: attrib.ddf, field.ddf, file.ddf, ndex.ddf

Source: ZENworks Server Management; Management and Monitoring Services; ipgroper.nlm, nxplanz.nlm
Severity: Critical
Explanation: An error occurred while opening IPCACHE. The discovery NLM programs were loaded in the wrong sequence. In netxplor.ncf, the nxpip.nlm must be loaded before ipgroper.nlm and nxplanz.nlm.
Possible Cause: Netxplor.ncf has been manually edited.
Action: Perform the following tasks:

  1. Copy the netxplor.ncf and nxp.ini files 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 set the value of [IPCACHE] PATH to ZENworks_installation_directory\zenworks\mms\ mwserver\ipcache.

  3. Restart discovery.

Possible Cause: The nxp.ini file is corrupted and does not have the [IPCACHE]section.
Action: Perform the following tasks:

  1. Copy the nxp.ini file from the ZENWorks 7 Server Management product CD into ZENworks_installation_directory\zenworks\mms\ mwserver\nmdisk.

  2. Edit the nxp.ini file to set the value of [IPCACHE] PATH to ZENworks_installation_directory\zenworks\mms\mwserver\nmdisk\ipcache.

  3. Restart discovery.

Input file discnodes.txt not found. To use File-Based Discovery, you can create a new input file

Source: ZENworks Server Management; Management and Monitoring Services; ipgroper.nlm
Severity: Informational
Explanation: File-based discovery has been configured to run without specifying an input file.
Possible Cause: The input file has not been configured.
Action: If you want to discover hosts using file-based discovery, create the discnodes.txt input file in the ZENworks_installation_directory\mwserver\nmdisk directory. For more information, see File-Based Discovery in Understanding Network Discovery and Atlas Management in the Novell ZENworks 7 Server Management Administration Guide.

Unable to find the DNS name server information in the resolv.cfg file. Ensure that the DNS server is configured correctly

Source: ZENworks Server Management; Management and Monitoring Services; ipgroper.nlm
Severity: Important
Explanation: The sys:\etc\resolv.cfg file does not contain the information on the DNS server to be queried to retrieve the DNS names.
Possible Cause: The server has not been configured with any DNS server to resolve names.
Action: Configure the NetWare® server to query a DNS server.
Action: You can also manually edit the resolv.cfg file to create an entry for the DNS server. For example: domain domainname nameserver IP address of the DNS server.

Unable to update the NetExplorer configuration file

Source: ZENworks Server Management; Management and Monitoring Services; nxpcon.nlm
Severity: Critical
Explanation: The configuration that needs to be updated in the nxp.ini configuration file in the ZENworks_installation_directory\zenworks\mms\ mwserver\nmdisk directory could not be performed.
Possible Cause: The nxp.ini file is corrupted or does not exist.
Action: Perform the following tasks:

  1. Stop NetExplorer by entering unxp at the Management server prompt.

  2. If sloader is started, stop the Java discovery processes.

    To stop the discovery processes, enter stopdis.

    Wait for all the Java discovery processes to stop.

  3. Copy the nxp.ini file from the ZENworks Server Management product CD into the following directory: ZENworks_installation_directory\zenworks\mms\ mwserver\nmdisk.

  4. Edit the nxp.ini file to set the value of [IPCACHE] PATH to ZENworks_installation_directory\zenworks\mms\ mwserver\nmdisk\ipcache.

  5. Start NetExplorer by entering netxplor at the Management server prompt.

  6. Start the Java discovery processes by entering startdis.

    Use NXPCON to configure NetExplorer.

Insufficient memory. Exit NetExplorer and try later

Source: ZENworks Server Management; Management and Monitoring Services; nxpcon.nlm
Severity: Critical
Explanation: The program was unable to allocate sufficient memory.
Possible Cause: The server is running low on memory.
Action: Check and unload unnecessary processes to free up the memory and try again.

Changes cannot be activated from here. Reload NetExplorer to activate the changes in the following: changelist

Source: ZENworks Server Management; Management and Monitoring Services; nxpcon.nlm
Severity: Informational
Explanation: You have changed certain configuration parameters like the IP discovery scope, which require the NetExplorer system to be restarted. These changes cannot be updated within the NetExplorer system while the other modules are running.
Possible Cause: You have made the changes to suboptions other than SNMP using Configuration Options.
Action: Perform the following tasks:

  1. Stop NetExplorer by entering unxp at the Management server prompt.

  2. If sloader has been started, stop the Java discovery processes by entering stopdis.

    Wait for all the Java discovery processes to stop.

  3. Start NetExplorer by entering netxplor.

  4. Start the discovery processes by entering startdis.

Error starting Naming Service. Naming Service already running on port portnumber

Source: ZENworks Server Management; Management and Monitoring Services; Naming Server
Severity: Informational
Explanation: A prior instance of the Naming Server Java process is already running and an attempt was made to start it again.
Possible Cause: You have entered mwserver twice at the command prompt.
Possible Cause: You have attempted to restart the services without killing the Naming Server Java process.
Action: Perform the following tasks:

  1. Stop the Naming Server Java process by entering mmsNaming -exit at the server prompt.

  2. Restart the Naming Server Java process by entering mwserver at the server prompt.

Error starting Naming Service. The address is already in use

Source: ZENworks Server Management; Management and Monitoring Services; Naming Server
Severity: Important
Explanation: The NetWare server has not released the port associated with a prior instance of the Naming Server Java process. Therefore, a subsequent attempt to restart the Naming Server on the same port failed.
Possible Cause: An attempt to stop and start the Naming Server Java process was made too quickly.
Action: Wait for a longer time interval (at least a minute) before restarting the Naming Server Java process.

NXPLANZ: Internal error in finding server MAC address

Source: ZENworks Server Management; Management and Monitoring Services; ipgroper.nlm
Severity: Informational
Possible Cause: You are trying an unsupported load balancing configuration.
Action: Ensure that only one network interface card (Ethernet Card) is the primary interface for only one network.