6.8 Traffic Analysis Error Messages
Unable to add the protocol
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
This error is displayed if the addition of a protocol to the Protocol Directory fails.
Possible Cause:
The agent might not allow certain protocols to be added.
Action:
Add only the protocols that the agent allows you to add.
Possible Cause:
An internal error occurred at the agent.
Action:
If this error occurs multiple times, unload and reload the agent.
Possible Cause:
The ZENworks Server Management is not responding.
Action:
Restart the ZENworks Server Management.
Unable to reach the agent
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
This message displays if the management server is down or if the connection between the agent and the management server is down.
Action:
Ensure that the management server is up and running and check the connection between the agent and the server.
Unable to turn to promiscuous mode
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Traffic Analysis Agent requires promiscuous mode to function appropriately.
Possible Cause:
The Traffic Analysis Agent software failed to turn on the promiscuous mode for the interface.
Possible Cause:
The board or the driver is not functioning.
Possible Cause:
The server where the traffic analysis agent is installed is running out of resources.
Action:
Try unloading the promiscuous mode driver and reloading it. If that does not solve the problem, see the driver's documentation for details.
Console views display abnormal values for segment bandwidth utilization.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
One of the parameters in calculating the bandwidth utilization is the interface speed (ifSpeed in MIB-2 RFC1158). On some NICs, the ifSpeed might not reflect the actual value because of some problem in querying the driver. The following drivers have this problem:
3Com* EtherLink* PCI (NT server)3Com Fast EtherLink 3C59X (NetWare server)
Action:
Upgrade to the latest drivers.
Constraints in addition of new protocols
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The agent does not allow the user to add new protocols over certain encapsulations like ETHER2, ETHER2.IP, ETHER2.IPX.NCP. However, new protocols can be added over ETHER2.IP.UDP, ETHER.IP.TCP or ETHER2.IPX.
Action:
None.
You do not have rights to modify the protocol attributes
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
You do not have the rights to perform operations on the Protocol directory.
Action:
Contact your system administrator regarding granting of rights.
The interface driver is not loaded
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Traffic Analysis Agent requires an interface driver to start monitoring segments, nodes, or devices on your network.
Action:
Load the interface driver at the agent.
Possible Cause:
The appropriate driver is not loaded or the driver is not loaded properly.
Action:
Load the appropriate driver or check to make sure that the driver has been loaded successfully.
The interface is not found
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The management console is unable to find a particular interface on the server where the monitoring agent is loaded.
Possible Cause:
The LAN driver for the adapter related to this interface is not loaded.
Action:
If the LAN driver is not loaded, load it. You can use the Remote Console utility in the management console to access the server console session. Refer to the vendor documentation for information about what command to enter to load the driver.
Possible Cause:
The network board was removed from the server where the monitoring agent is loaded or exchanged for a new one.
Action:
If you removed or changed a network board, wait until NetExplorer completes its next cycle and NetExplorer Manager runs on the management console. NetExplorer detects that a network board is removed or changed and updates the ZENworks Server Management database accordingly.
Possible Cause:
A new server was added to the network on which the monitoring agent is loaded, and it is assigned an IPX or IP address that has been used previously.
Action:
If you assigned a previously used IP or IPX address to a new server, reassign an IP or IPX address that was not assigned previously and run NetExplorer and NetExplorer Manager.
Action:
Update the relevant Network Interface card information using the Database Object Editor. Edit the existing Network Interface card information and add the Network Interface card information again:
-
In ConsoleOne, select the node that has the Network Interface card problem.
-
Click > >.
-
Select the tab.
-
From the Interface Summary list, select the row that contains the interface information that needs to be modified, then click .
-
Change the information for Network Interface card
-
Click to add the new Network Interface card information.
-
Click .
The interface is not licensed
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The installed driver is not licensed.
Action:
Load a licensed driver.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
An unknown error occurred when the management console tried to obtain information from the server where the monitoring agent is loaded.
This error does not occur under typical conditions.
Action:
If other management consoles on the segment are able to communicate with the monitoring agent, this indicates that the agent is functioning. Try to free memory on the management console.
If no other management console can communicate with the agent, try to free memory on the agent by restarting the management console.
Possible Cause:
You are using the VPN address of the Traffic Analysis Agent.
Action:
Use any address other than the VPN address of the Traffic Analysis Agent.
Multiple refreshes to some views during early cycles of discovery
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Possible Cause:
During early cycles of discovery, many new nodes are discovered and nodes are moved from one segment to another. Because of this, there might be multiple refreshes to some views.
Action:
Wait for the discovery to stabilize and then launch the view.
The site server is not responding
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Management server needs sufficient memory to respond to requests from the management console.
Possible Cause:
The server is down.
Action:
Ensure that the server is up and running.
Possible Cause:
The server is out of memory.
Action:
Restart the server if it is out of memory.
Possible Cause:
There is a network error in communicating with the Management server.
Action:
Check the network connections and try again.
The media is not supported
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The selected media is not supported by the monitoring agent.
Action:
Use an adapter of the supported media type.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
MIB-2 is the information base where the RMON agent resides.
Action:
Reload the agent.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The machine is not on the network.
Action:
Try to ping to some other hosts from Windows NT. If they do not respond, contact your system administrator.
Explanation:
SNMP does not respond if the SNMP service for Windows NT is not running.
Action:
Start the SNMP service. At the Management server prompt, enter net start snmp.
Explanation:
The SNMP service on Windows NT is not configured.
Action:
Check the community string of SNMP for READ/WRITE access.
Explanation:
The NetWare servers with default settings for SNMP Set operations do not respond to the community string PUBLIC, although the same is not true for SNMP Get operations. As a result, the LSM operations that involve setting SNMP entries, like Stations, Dashboard (top n), and Capture packets, display no SNMP response.
Action:
Set the community string to PUBLIC.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Possible Cause:
The monitoring agent is not running on the segment. The interface cannot be monitored because the driver is not supported.
Possible Cause:
You disabled monitoring on the agent.
Possible Cause:
You deleted the statistics entry on the agent.
Action:
If you are running the Traffic Analysis Agent for NetWare 1.0/1.1/1.2, upgrade to version 1.3, which is available as part of ZENworks Server Management or on the Novell Support Web page.
Install a promiscuous mode driver for the interface on the server. The driver must also support the raw send feature. Check the Web page for information regarding availability of the latest promiscuous mode drivers. You might need to contact your adapter vendor for the appropriate driver.
If a promiscuous driver already exists, try unloading the driver and reloading it.
This is not a promiscuous driver
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Traffic Analysis Agent requires promiscuous mode to function properly.
Possible Cause:
The driver is not a promiscuous mode driver.
Action:
Install a promiscuous mode driver on the server. Check the Novell Support web page for information regarding availability of the latest promiscuous mode drivers. You might need to contact your adapter vendor for the appropriate driver.
This is not a raw send driver
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Traffic Analysis Agent requires an adapter driver that supports the raw send feature.
Possible Cause:
The driver does not support the raw send feature.
Action:
On the server, install an adapter driver that supports the raw send feature. Check the Novell Support Web page for information regarding availability of the latest promiscuous mode drivers that support the raw send feature. You might need to contact your adapter vendor for the appropriate driver.
This is not a non-pipelined adapter
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The Traffic Analysis Agent supports non-pipelined adapters.
Possible Cause:
The adapter is a pipelined adapter.
Action:
If the adapter allows you to switch from pipelined mode to non-pipelined mode, do so. If the adapter cannot switch modes, replace the adapter with an adapter of the supported media type for Traffic Analysis Agent operations.
Unable to remove the protocol
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
This error is displayed if deletion of a protocol from the \protocol directory failed.
Possible Cause:
The agent does not allow certain protocols to be deleted.
Action:
Remove only those protocols that the agent allows you to remove.
Possible Cause:
An internal error occurred at the agent.
Action:
If this error occurs multiple times, unload and reload the agent.
Possible Cause:
The ZENworks Server Management server is not responding.
Action:
Restart the ZENworks Server Management server.
RMON is not present on the switch
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The RMON groups are not found on the switch.
Possible Cause:
The RMON groups are not loaded.
Action:
Load the RMON groups.
Possible Cause:
The switch does not support RMON.
Action:
None.
The RMON2 service is not available on this node
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The RMON2 group is not available at the agent.
Possible Cause:
Discovery has not yet discovered sufficient information about the agent.
Action:
Ensure that the discovery component is up and running. Allow it to run for a sufficient time to enable it to discover objects in your network.
Possible Cause:
The agent does not implement the RMON2 group.
Action:
Use database object editor to add RMON2 service.
SNMP / Console error displayed by LSM
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Possible Cause:
If the SNMP communication to the primary agent is over NCP™, it requires the user to log into this server. If the authentication is not done, LSM reports an SNMP error.
Action:
Select the primary agent and click the Probe Manageability button to force the user to authenticate to the server. LSM also works after this authentication.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
This message displays if an internal error occurs at the agent.
Action:
If this message displays multiple times, unload and reload the agent.
The switch is not responding
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The switch is not responding to the SNMP requests or the switch might not be configured to accept SNMP requests from the selected host.
Action:
Enable SNMP on the switch.
Action:
Use the community string accepted by the switch.
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
You cannot view tables for an interface if the agent is not loaded.
Action:
Ensure that the agent is loaded. If you are still unable to view the required information, ensure that the table is implemented by the agent that is used for monitoring.
This segment does not have an RMON Agent connected to it
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Explanation:
The segment is not an Ethernet, token ring, or FDDI ring segment, or an RMON agent is not installed on the segment.
“Segment Not Monitored” has the same meaning as this message.
Action:
If you want the Ethernet, token ring, or FDDI ring segment to be monitored, install the Traffic Analysis Agent for NetWare or the Traffic Analysis Agent for Windows NT on a server on the segment.
The Host table is not present on the primary agent
Source:
ZENworks Server Management; Management and Monitoring Services; Traffic Analysis
Severity:
Important
Possible Cause:
The Host table or the MIB-2 is not implemented by the agent or the agent is not loaded.
Action:
Reload the agent.