|
|
This appendix describes the error messages you may encounter when using the TrafficDirector application.
Explanation The SwitchProbe agent is not responding to TrafficDirector queries. The community string configured at the SwitchProbe device may be invalid. The failure can also be caused by a variety of physical connectivity or other agent configuration problems.
Recommended Action Perform a ping to the agent, or perform an Agent Test to make sure the agent is alive on the network. If the ping request is successful, check the agent SNMP community strings.
Explanation The print to file feature failed.
Recommended Action Check the pathname and access privileges for the <filename>.
Explanation The Windows TCP/IP stack on the PC running the TrafficDirector software has a problem.
Recommended Action Check for insufficient resources, such as socket descriptors.
Explanation Occurs while using Configuration Manager. Host name could not be resolved while adding an entry.
Recommended Action Supply a valid host name.
Explanation The print command failed.
Recommended Action Check your printer device for possible problems or a misconfiguration.
Explanation Occurs while using either the Protocol Zoom application. The domain configuration file could not be opened.
Recommended Action Copy domtree.inf from the samples directory to the $NSHOME/usr directory.
Explanation Occurs while using the Protocol Monitor or Application Monitor applications. The domain configuration file could not be opened.
Recommended Action Copy protogrp.cfg from the samples directory to the $NSHOME/usr directory.
Explanation Occurs while using the Data Capture application. The agent name you entered was invalid.
Recommended Action Enter a valid agent name.
Explanation Occurs while using the Host Zoom application.
Recommended Action Enter a valid agent name.
Explanation The application executable may not be available.
Recommended Action Verify that the application executable file is present in the $NSHOME/bin directory.
Explanation The path where the TrafficDirector software is installed cannot be found by the system.
Recommended Action Set the NSHOME environment variable to the directory path where the TrafficDirector software is installed.
Explanation The pathname where the TrafficDirector software is installed exceeds 64 characters in length.
Recommended Action Rename the installation directory, or install the TrafficDirector software into a another directory at a level closer to your root directory.
Explanation The TrafficDirector software cannot connect to the agent, the specified domain is not installed on the agent, or history is not enabled on the agent.
Recommended Action Verify that the agent is reachable using Test Agent. Check the agent IP address, interface number, and SNMP community strings. Ping the agent to verify that the agent is alive on the network. Make sure the specified domain is installed on the agent. If you are trying to run a history application, verify that the history group is enabled on the agent or switch port.
Explanation Occurs while using the Conversation History application. The TrafficDirector software cannot connect to the agent, and the specified domain with the Conversations group enabled is not installed.
Recommended Action Enable and install the domain with the Conversations enabled in the agent properties file. Reinstall the properties file on the SwitchProbe agent.
Explanation The TrafficDirector software cannot connect to the agent, and the specified domain is not installed on the agent.
Recommended Action Enable and install the domain in the agent properties file. Reinstall the properties file on the probe agent.
Explanation Occurs while using the Host Zoom application. The TrafficDirector software cannot connect to the agent, and the specified domain with the Host and Conversations groups properly enabled is not installed on the agent.
Recommended Action Ping the host and verify that it is alive; enable and install the domain in the agent properties file with Host and Conversations enabled. Reinstall the properties file on the SwitchProbe agent.
Explanation Either the specified domain is not installed on the agent, or the statistics group is not enabled for the domain.
Recommended Action Enable the statistics group for the specified domain in the agent properties file. Reinstall the properties file on the SwitchProbe agent.
Explanation The specified domain is not installed on the agent in the appropriate agent group.
Recommended Action Enable and install the domain for the agent group in the agent properties file. Reinstall the properties file on the SwitchProbe agent.
Explanation Occurs while using the Host Zoom application. The specified Conversation group for <domain> is not installed on the agent.
Recommended Action Enable and install the Conversation group for the <domain> on <agent> in the agent properties file. Reinstall the properties file on the SwitchProbe agent.
Explanation Occurs while using the Configuration Manager. The admin entry could not be created.
Recommended Action Verify that enough memory is available on the SwitchProbe device and that the write community is valid.
Explanation Occurs while using the Protocol Zoom application. The DLCI configuration might be faulty.
Recommended Action Examine the DLCI configuration in Configuration Manager.
Explanation Occurs while using the Configuration Manager. The admin entries for target hosts that are supposed to receive trap messages could not be learned from the SwitchProbe device. An nql timeout occurred when a command was issued to learn the admin entries.
Recommended Action Retry the command to learn the admin entries again.
Explanation While running functions from the command line, an incorrect agent name was entered, or the agent was deleted from Configuration Manager.
Recommended Action Check the Configuration Manager window or the $NSHOME/usr/agent.lst file for the correct spelling of the agent name. If the agent name is not listed, it was deleted. Redefine the agent if necessary.
Explanation While running functions from the command line, indicates the specified domain name is incorrect.
Recommended Action Check the domain name as it appears in Domain Editor and try the function again.
Explanation Occurs while using Configuration Manager. An invalid domain name was encountered during the parsing of the properties files.
Recommended Action Check the domain name entry in the file and verify that the domain is listed in the domain.lst file.
Explanation Occurs while using Configuration Manager. Field validation failed for the properties file. Either the properties file is corrupted, or some invalid filed entry exists.
Recommended Action Either delete the file or edit the entry in the properties file.
Explanation While running functions from the command line, you entered an invalid switch name, or the switch was deleted from Configuration Manager.
Recommended Action Check the Configuration Manager window or the $NSHOME/usr/switch.lst file for the correct spelling of the agent name. If the switch name is not listed, it was deleted. Redefine the switch if necessary.
Explanation The maximum number of agents allowed per TrafficDirector license has been reached. The Microsoft Windows version supports 100 agents; the UNIX version supports 500 agents.
Recommended Action Use fewer agents.
Explanation The particular application you requested from the RMON manager cannot be started with the selected agent because the topology does not match.
Recommended Action Select an appropriate agent for the specified topology.
Explanation Occurs while using the All Talkers application.
Recommended Action Verify the host name.
Explanation Occurs while using the Protocol Zoom application. Each domain group must have at least one associated child.
Recommended Action Edit the domtree.inf file so each domain group has at least one child.
Explanation Occurs while using either the Protocol Monitor or Application Monitor applications. Each domain group must have at least one associated child.
Recommended Action Edit the protogrp.cfg file so each domain has at least one child.
Explanation Occurs while using the Protocol Zoom application. The domains you specified are not installed on any agent.
Recommended Action Verify that at least one of the domains specified in domtree.inf is installed on an agent.
Explanation Occurs while using either the Protocol Monitor or Application Monitor applications. The domains you specified are not installed on any agent.
Recommended Action Verify that at least one of the protocols specified in protogrp.cfg is installed on an agent.
Explanation You did not provide a file name while trying to use the print to file feature.
Recommended Action Enter the name of the file you want to print.
Explanation Occurs while using the Protocol Zoom application.
Recommended Action Ensure that the domain has at least one grandchild.
Explanation Virtual memory is exhausted. There is no memory available to run the application. Most often occurs on Microsoft Windows platforms.
Recommended Action Restart the RMON manager application after closing some open applications.
Explanation The agent has run out of resources to handle the number of tasks specified.
Explanation The agent has insufficient resources to handle a request.
Recommended Action See the console window for additional information.
Explanation You started the TrafficDirector with an invalid agent, port, VLAN, or DLCI.
Recommended Action Specify a valid agent, port, VLAN, or DLCI.
Explanation You cannot start the TrafficDirector application with the domain you specified.
Recommended Action Select an appropriate domain.
Explanation You cannot start the TrafficDirector application with the domain group you specified.
Recommended Action Select the appropriate domain group first.
Explanation Occurs while attempting to use the SMON Monitor application. The SMON option at the SwitchProbe device is not enabled, or is not present because of license restrictions.
Recommended Action Enable the option at the device, or use an application other than SMON Monitor.
Explanation Occurs while using the Protocol Zoom application. The domain group has too many children specified for its definition.
Recommended Action Edit the domtree.inf file and verify that each domain group has no more than 19 children.
Explanation Occurs while using either the Protocol Monitor or Application Monitor applications. The domain group has too many children specified for its definition.
Recommended Action Edit the protogrp.cfg file and verify that each domain group has no more than 19 children.
Explanation The SNMP communication request cannot be properly handled.
Recommended Action See the console window for additional information.
Explanation The memory allocation for log storage is exhausted. Fewer logging snapshots are required to ensure there is adequate space to store the logged data.
Recommended Action Increase the logging interval in the agent properties file, then reinstall the properties file on the SwitchProbe agent.
Explanation The Extraction Daemon cannot continue logging all the requested data.
Recommended Action Use a text editor to add the following line to the sqldb.dvp file:
num_interval_for_skipping_logs: 5 (maximum 10 intervals)
For example, to change the default interval from 5 to 8, use this syntax: num_interval_for_skipping_logs:8
Explanation The SQL server cannot continue logging all the requested data.
Recommended Action Add the following line to the sqldb.dvp file:
num_interval_for_skipping_logs: 5 (maximum 10 intervals)
For example, to change the default interval from 5 to 8, use this syntax: num_interval_for_skipping_logs:8
Explanation Occurs while using the Protocol Zoom application.
Recommended Action Verify that the agent is reachable by performing a ping to the agent or using Test Agent.
Explanation Occurs while using the Protocol Zoom application. The protocol has no children.
Recommended Action Restart the application.
Explanation Occurs while using the Protocol Zoom application. The protocol has no parent.
Recommended Action Restart the application.
Explanation Occurs while using the Protocol Zoom application. The domtree.inf file was modified while the application was running.
Recommended Action Restart the application.
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon Apr 5 13:18:49 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.