During the startup of most NetVisualyzer tools, a connection must be established between the Display Station tool and the local or remote Data Station Snoop daemon, snoopd(1M) (see “Snooping” in Chapter 1). This section lists problem messages and their remedies in the sequence that they are typically encountered during the connection process.

DataStation name not recognized. 
Check that DataStation is a valid name and is entered in the appropriate data base. See Appendix A of the NetVisualyzer User's Guide for detailed help. 

By default NetVisualyzer uses entries in /etc/hosts to resolve Data Station names into their IP addresses. The name provided was not found in this file or the entry was invalid.

If the Data Station name was entered as an Internet address in the standard dot notation (for example, 191.26.45.75), that IP address was not reachable on the network. The address may have been keyed in error or a route to the host may not be known.

If the –y option was specified on the command line when the tool was started, name resolution will use the network hosts databases, NIS and BIND, if the hostresorder resource includes NIS and BIND. This request failed; check with your system administrator to verify that this node is known to the network's name server.

See also gethostbyname(3N), resolver(4), and ypbind(1M).

Could not connect to snoopd on DataStation: Program not registered.
Check that snoopd is installed and configured correctly on the Data Station. See Appendix A of the NetVisualyzer User's Guide for detailed help.

For NetVisualyzer to snoop on a Data Station, it must establish an RPC connection with the Snoop daemon, snoopd, on that node. Normally, following the directions in “Enabling Network Snooping” in Chapter 1 is sufficient. This error message indicates that the connection wasn't made. To diagnose the problem, verify the following:

To protect the tools from illegal users, NetVisualyzer allows the superuser to define which users and hosts have permission to use the tools on each Data Station.

You must have been granted authorization in the file /usr/etc/rpc.snoopd.auth to snoop on a Data Station. See “Authorizing NetVisualyzer Users for Snooping” in Chapter 1 for more information.

Could not find a valid NetVisualyzer license

NetVisualyzer requires the user to purchase a license for the total number of concurrent Data Stations that are to accessed from the Display Station. The license is checked by the Display Station software as each tool is invoked. Possible reasons for this message are:

Examine the license file and make sure that the correct password from your software license appears. It may be necessary for the superuser to re-enter the password string.

NetVisualyzer license limit reached

The Display Station has attempted to connect to more concurrent Data Stations than it is authorized for. You can either retry later when demand has lessened or consider upgrading the license to permit a larger number of simultaneous users.

Contact lost with Data Station DataStation. Check network connection and remote node. See Appendix A of the NetVisualyzer User's Guide for detailed help. 

Typically, this error message results from a problem with either the network or the Data Station node. Either software or hardware failure is possible:

A first, simple test is to ping the node to determine whether the node responds and if the link is congested.

The following messages can occur when you are using Analyzer:

Could not snoop from filename: errmsg.

Cannot open the specified file for reading.

No captured data available.

No snoop data available for searching. Capture some data before using the Search button.

Could not write to filename: errmsg.

An error occurred when writing to the file.

Unresolved String: filter

Cannot interpret the filter expression.

Snoop length error.

Length of data packet to capture is not acceptable.

Cannot keep n packets because only m packets to stop at. Can keep only m.

The value in the Stop At entry field is less than the value specified to keep for decoding. Only the smaller number of packets can be decoded.

Value too big. Only n packets are kept.

The number of packets specified to keep for decoding is too big. The bigger default value is used.

analyzer: Could not start NetFilters: errmsg.

NetFilters is not installed or some other error occurred that is described in errmsg.

Could not write to .analyzerrc. 
Could not write to user_input_rcfilename.

No permission to write or the directory does not exist.

Could not read .analyzerrc. 
Could not read user_input_rcfilename.

No permission to read or the file does not exist.

Could not transfer filter expression to a non-filter field.

A filter expression can only be transferred to the Trigger On, Filter, or Stop On entry fields.

Could not open help file filename: errmsg.

Cannot open the help file listed in the error message.

The following messages can occur when you are using Browser:

Time expired. Agent did not respond. Check whether the agent is running on the node; check whether the community name that you entered in the main window corresponds to what the agent expects and also whether your host is authorized for the service you requested on the remote host

This message can occur when Browser fails to establish a connection with the SNMP agent on the node you want to browse. Some possible causes are networking problems, incorrect community string, and your host is not authorized to browse on this node.

Send Error: Unable to communicate with the remote node

The remote node is down or the communication link to that node is down. Check whether the node is up by issuing ping(1M) command.

MIB tree was not created

The MIB database was not created because there was a problem with reading and compiling the MIB specifications in the /usr/lib/netvis/mibs directory.

No such name

The specified variable is not found in the MIB. Check whether you are entering the correct object identifier or name for the variable. This error is also caused by trying to write to a read-only object. If you are entering the right name (or object id) and that object has read-write permissions, then that variable is not implemented by the agent.

Bad value

The requested operation contained incorrect syntax or an incorrect value when trying to modify a variable.

SNMP protocol error

The SNMP agent's response did not conform to the SNMP protocol specification.

Nothing to set in this table yet, do a Get first

When a table window comes up, it displays only the columns of the table. To set a particular value in the table, you have to do a Get so that the entry fields for the table appear on the screen.

SNMP Generic error

Got genErr from the agent.

Variable is a Table

You probably want to get a value for a variable in this table. Specify the object identifier and an instance for the variable.

Variable is a Group

You probably want to get a value for a variable in this group. Specify the object identifier and instance for the variable.

Variable is in a Table. It requires an instance

You have to specify the instance for this variable.

Variable name not in the MIB tree

You are trying to specify a name for a variable that is not known to the Browser database. Specify the object identifier for the variable.

The following messages can occur when you are using NetAccount:

usage: netaccount [-p proto] [-tvy] [-r nrank] [-s nsumm] file

Bad arguments given.

netaccount: Could not find a valid NetVisualyzer license.

No license found.

netaccount: NetVisualyzer license limit reached.

Maximum number of data stations active.

netaccount: unknown protocol.

A bad value for protocol passed with –p.

netaccount: invalid rank count.

A bad value for rank passed with –r.

netaccount: invalid summarize count.

A bad value for summarize passed with –s.

netaccount: error reading filename: message.

Error occured reading the file.

The following messages can occur when you are using NetCollect:

usage: netcollect [-h hashsize] [-i interface] [-p path] [-t interval]

Displayed when a bad argument is given.

netcollect: couldn't get hostname: message.

The name of the host NetCollect is running on could not be obtained.

netcollect: interval must be > 0 and < 1440.

A bad value for interval was given.

netcollect: error getting host information for hostname: message.

The host name passed through a –i option could not be found.

netcollect: interface: Invalid argument.

A bad value was passed for interface.

netcollect: error in open: message.

Could not open a socket.

netcollect: error in subscribe: snoopd on hostname: message.

Could not connect to snoopd.

netcollect: error in setsnooplen: message.

Could not set the length of packets to capture.

netcollect: error in getaddr: message.

Could not get the address or netmask of the interface being snooped on.

netcollect: error in compile: message.

Could not compile filter.

netcollect: error creating data directory: message.

Could not create the directory to store data files.

netcollect: error in start: message.

Could not turn on snooping.

netcollect: error in read: message.

Error while reading from snoopd.

netcollect: error in write: message.

Could not write data file.

netcollect: snoopd on hostname: Error in subscribe: message.

The Snoop daemon on hostname rejected the subscribe.

The following messages can occur when you are using NetFilters:

Couldn't load file filename.

Error in reading the filters file. The directory or file doesn't exist.

No current file name. Use the "Save As" command.

There is no filters file in use currently. Use the “Save As” menu choice to specify a file name.

Couldn't save file filename.

Error in writing the filters to filename. You do not have permission to write to the directory or it doesn't exist.

The following messages can occur when you are using NetGraph:

Could not start snooping
Error in snoop read

An error was returned by snoopd. It may have lost contact with the Data Station.

Could not add promiscuous snoop filter

snoopd did not accept a promiscuous snoop filter, so NetGraph couldn't run.

Cannot continue -- too many errors

The content of the NetGraph user interface configuration file (.netgraphrc) has more than 10 errors. See “NetGraph User Interface Configuration File” in Appendix D for the correct format, or start NetGraph without a .netgraphrc file.

Illegal graph specification token

An illegal keyword was given in the specification for a graph. Valid keywords include line, bar, packets, noalarm, and so on. See “NetGraph User Interface Configuration File” in Appendix D for the correct keyword.

Error in opening history file, so can not save history

Bad directory name or no permission to write to that directory.

Error in opening history file, so can not play back history

The file you specified as a history file doesn't exist, isn't a valid NetGraph history file, or is read-protected.

History file cannot be specified here

You can start NetGraph with the –i history_file option, but you cannot specify a history file as the interface after NetGraph is already running.

When playing back history, cannot simultaneously record history

The data being displayed are coming from a history file; it is not necessary to save it again.

Could not open alarm log file, so alarms will go to standard output

The log file specified does not exist or permission denied.

ControlsFile has too many lines. It probably isn't in the correct format

A correct user interface configuration file has one line per graph desired, plus a few extra lines. The file you specified has so many lines that it probably isn't a valid user interface configuration file.

netgraph: Could not start NetFilters: errmsg.

NetFilters is not installed or some other error occurred that is described in errmsg.

This section lists messages displayed by NetLook. “Messages Common to Analyzer, NetGraph, NetLook, and NetTop” in this chapter lists additional messages from NetLook.

Starting NetLook...

Buffer size must be greater than zero.

Interval size must be greater than zero.

Could not get this host's name.

Could not get this host's entry.

Could not open socket.

Could not get interface configuration.

Could not create node node.

Could not start snooping on node: errmsg.

Could not stop snooping on node: errmsg.

Could not change filter on the following DataStations:

node: errmsg

object is hidden.

Could not find object.

object is already hidden.

object is not hidden.

Could not start ping: errmsg.

Could not start traceroute: errmsg.

netlook: Could not start NetFilters: errmsg.

Could not open datafile: errmsg.

Could not read datafile: errmsg.

datafile is not a NetLook data file.

datafile: line line: parse_error.

Could not write datafile: errmsg.

No object to hide.

No hidden objects.

Save data to datafile before quitting?

Are you sure that you want to delete object?

The following messages can occur when you are using NetPack:

usage: netpack [-p path] [-rv] file1 file2 ...

Bad arguments given.

netpack: could not read filename: message.

Error occurred reading the file.

netpack: could not unlink filename: message.

Error occurred removing a file.

netpack: could not get current directory: message.

Could not find the current directory.

netpack: could not create data directory: message.

Could not create the directory to store data files.

netpack: could not save filename: message.

Error occurred writing the file.

The following messages can occur when you are using NetSnoop:

netsnoop: interface_or_filename: No such file or directory. 

An invalid interface was specified using the –i option. NetSnoop expects a valid interface name, such as ec0, or the name of a snoop file with the full path if it is not in the current directory.

netsnoop: cannot snoop to tracefile filename: Cannot write to the named file. 

Bad directory name or no permission to write to that file.

netsnoop: cannot snoop on default interface: Permission denied.

You must be superuser to run NetSnoop when snooping from a network interface.

netsnoop: cannot snoop on interface: Not enough space.

Not enough memory left to buffer snoop data.

The following messages can occur when you are using NetTop:

Error in snoop read
Could not delete snoop filter
Could not start snooping
Could not stop snooping
Could not set snooping interval
Error in snoop unsubscribe

An error was returned by snoopd. Contact with the Data Station may have been lost.

Error in snoop read - wrong number of bins

NetTop couldn't run any more because snoopd returned bad data.

nettop: Could not start NetFilters: errmsg.

NetFilters is not installed or some other error occurred that is described in errmsg.