Troubleshooting Traffic Analysis

The ZENworks for Servers 3 traffic analysis system can be an extremely useful tool when debugging LAN-related issues. But there is a possibility for problems with the traffic analysis system itself. The following sections discuss steps to take if you are experiencing problems with the traffic analysis system.

Verifying LAN Traffic Agents Are Loaded on Devices

The first step you should take is to check the servers and other devices that have LAN traffic analysis agents on them. Make certain that the agents are loaded (NetWare servers) or started (Windows NT/2000 Servers) properly.

Verifying RMON Agent Settings

After you verify that the traffic analysis agents are loaded properly, you should check the RMON agent's settings for the device in ConsoleOne. You should verify that the RMON agent is enabled for the nodes you are trying to analyze. You should also verify that you have the correct preferred agent set. (See Chapter 10, "Using ZENworks for Servers Traffic Analysis," for more information about setting up the RMON agent.)

Verifying Settings in the LANZ.NCF File

After you verify the RMON agent, you should verify that the settings in the LANZ.NCF files for your NetWare servers are correct. You can also enable the LANZ control screen that can help you understand the current state of the agents. (See Chapter 10 for more information about setting up the LANZ.NCF file.)

Verifying Settings in the LANZCON Utility

After you verify the settings in the LANZ.NCF files for your NetWare servers, you should verify that the settings in the LANZCON utility for your Windows NT/2000 Servers are correct. (See Chapter 10 for more information about setting up the LANZ.NCF File.)

Additional Debugging Tips

The following sections discuss some possible problems in the traffic analysis system and agents and how to resolve them.

LANalyzer Error Ethernet Adapter <address> Is Not Monitored Because the Driver Does Not Support Promiscuous Mode

A promiscuous-mode driver receives all packets and errors on the network. This is required for the ZENworks for Servers 3 traffic analysis agents. The driver currently loaded does not support promiscuous mode; therefore, you need to update your driver for the traffic analysis agents to work.

No SNMP Response

No SNMP service is currently started on the Windows NT/2000 Server, or the agent is not configured to receive SNMP requests. Start the SNMP server on the NT server and verify that the IP address of the selected host is included in the trap destination address list. This problem could also be caused if you have some community string settings wrong or SNMP parameters set wrong on the servers.

RMON Tables Are Not Listed

Adapter monitoring is not enabled in the LANZCON utility or the RMON tables have been deleted. You should enable adapter monitoring in the LANZCON utility.

False Duplicate IP Address Alarm Generated in DHCP

The DHCPRELEASE packet from the client has not reached the server, resulting in a false duplicate IP address. Use the LANZCON utility to disable the generation of duplicate IP address alarms.

No Response Message on Management Console

The most common cause is that adapter monitoring is not enabled. Use the LANZCON utility in Windows NT/2000 or the LANZ configuration utility in NetWare to enable adapter monitoring.

MIB-2 Not Found

MIB-2 refers to the information base in which the RMON agents are located. You should reload the agent on the device.

No Statistics Are Reported

The monitoring agent is not running on the segment, the interface cannot be monitored because the driver is not supported or is disabled, or the statistics entry has been deleted. You should enable monitoring on the agent, update the driver to a promiscuous mode driver, and/or reload the agent.

This Segment Does Not Have an RMON Agent Connected to It

The segment does not have a supported topology, the RMON agent is not configured or installed correctly, or insufficient memory is on the management server to run the RMON agent. You should first verify that your topology is supported. Second, you should install or configure the RMON agent. Verify that the server has plenty of memory. Then unload and reload the RMON agent.

Interface Not Found

The management console is not able to find the interface on the server to contact the monitoring agent.

The LAN adapter may not be loaded on the server. You should load the LAN driver for the adapter on the server.

The network card for the server was removed and replaced with a new one. Simply wait until NetExplorer discovers the new card and removes the old one.

You installed or reinstalled a new server on the network, but used an IP or IPX address that has been previously assigned. Change the address and run NetExplorer.

Management Server Is Not Responding

The server is down, out of memory, or has a communication problem. If you're experiencing this sort of problem, first verify that the server is up and running. Next verify that the server has plenty of memory. Then check the connectivity status of all services to the management server by using the connectivity test utility.