3.1 Console

3.1.1 Can't run multiple sessions

Another user with the same user ID is already running a Console session.

The following message is displayed:

snm already running: started <date> on <host> (pid <pid>) by <user> on display <displayname>

Multiple Console sessions can be run from a single user ID. For each session, specify a different name by setting the environment variable SNM_NAME:

host% setenv SNM_NAME "Jack Netman"

The name does not need to be a UNIX login name; however, it should not include characters such as '/', '.', or '..'.

While multiple Console sessions are supported, it is not the recommended way to use SNM.

3.1.2 Incorrect glyph positions

• Glyph positions are not correct.

  In the discover function's properties window, make sure the Add Object Coordinates item is set to yes.

3.1.3 Can't change the glyph for the element instance

Glyphs are associated with element types, not element instances. See the Administration Guide for more information.

3.1.4 Empty views are displayed

By default, the Console allows you to go to empty views. You can specify that the Console not display empty views; this is configured in the Miscellaneous category of the Console Properties window. See the Administration Guide for more information.

3.1.5 Can't get traps to work

3.1.5.1 Traps are not being received by the Console.

Check the value of the na.snmp-trap.rendez keyword in the /etc/snm.conf file (Solaris 1.x) or the /etc/opt/SUNWconn/snm.conf file (Solaris 2.x) on the system that the trap daemon resides. Add the keyword if it does not exist. Make sure the host name of the Console system is defined correctly. Multiple host names should be separated by colons (:).

3.1.5.2 Traps are not being signaled in the Console.

The Console can be configured to signal, send mail, or fork a program when a trap report is received. If trap reports are being displayed in the Event/Trap Reports window, but the Console is not signaling the receipt of the trap report, check the settings for Trap Information in the Events and Traps category of the Console Properties window. If a glyph effect is being propagated, make sure that glyph state propagation has been enabled for the Console view that is being displayed.

3.1.6 Incorrect schema file on the proxy system

The proxy agent cannot find the schema or group specified in the request.

If the SNMP proxy agent cannot find the schema file for the target system or the schema file on the proxy system is not the same as the one loaded in the Console, the following message appears:

Error(Get): Invalid object group: <gro>

This can happen if you are attempting to use a schema file that is not a "standard" schema file supplied by Sun (the schema file has been supplied by another vendor, or you have created your own schema file). Make sure that the schema file on the SNMP proxy system is located in a directory specified by the na.snmp.schemas keyword in the /etc/snm.conf file (Solaris 1.x) or the /etc/opt/SUNWconn/snm.conf file (Solaris 2.x) on the proxy system. If you change the keyword value while the SNMP proxy agent is running, you need to kill the proxy agent for the change to take effect. Make sure that the schema file on the proxy system is the same as the schema file on the Console.

3.1.7 Can't load background image

• The background file cannot be found.

  An image file you specified in the Add Background file menu does not exist or is not in the directory you specified.

  If you added a background by editing the ASCII file that contains the runtime database and the Console cannot locate the background image file you specified in the viewBackground instance, the following message appears:

Cannot find icon/rasterfile <file>

If the icon path name begins with a slash (/), it is treated as an absolute path. Otherwise, the path name is relative to the directories specified by the Icon Directories setting in the Console Properties Locations category. See the Administration Guide for more information.

• The background image file is not in the correct format.

  If the background image file is not in rasterfile format, the following message appears:

Bad rasterfile: <file>

Icon format is supported if the file ends with the extension.icon.

• The background image file is a color file, but the Console is currently running on a black and white monitor.

If the following message appears, the background image file can only be loaded on color systems.

Cannot load color rasterfile on B&W monitor

• Too many icons and rasterfiles are already loaded into the runtime database.

  If the following message appears, you need to reduce the number of icons or rasterfiles in the runtime database.

Cannot load more than 1024 icons/rasterfiles

• The view instance cannot be found.

  If you added a background by editing the ASCII file that contains the runtime database and the view instance for the background image is not defined, the following message is displayed:

Unknown <viewname>

Make sure that the view instance definition exists and that it is loaded before the viewBackground instance.

3.1.8 Can't load schema file

The schema file you created does not load.

If the following message appears, make sure that the schema file is readable.

Cannot open <file> - load failed

If loading the schema file fails because of a syntax error in the schema file, a message like the following appears in the Error Reports window:

line x: syntax error

Check the line indicated in the.schema file. Make sure that record entries have beginning and ending paragraph braces (). The field names in the element definition must not contain blanks--use underscores instead. The underscores will be displayed as blanks in the Properties window for the element.

The schema file may fail to load if the specified icon cannot be found. If the icon path name begins with a slash (/), it is treated as an absolute path. Otherwise, the path name is relative to the directories specified in the Console Properties window. See the Administration Guide for more information.

3.1.9 Can't find the icon file

If the Console cannot locate the icon file you specified in the viewBackground instance, the following message appears:

Cannot find icon/rasterfile <file>

If the icon path name begins with a slash (/), it is treated as an absolute path. Otherwise, the path name is relative to the directories specified in the Console Properties window. See the Administration Guide for more information.

3.1.10 Didn't get a value returned

• No value is returned for an attribute.

  If the message "(No value retrieved)" appears under the Current Value column for an attribute, either the value is not available at the time the get request is made or an error occurred. (Refer to the error message at the bottom of the screen.)

3.1.11 Request didn't change

• Modifications to the request did not take effect.

  Make sure that you have clicked SELECT on the Apply button after modifying an attribute display.

3.1.12 Edit menu doesn't have element type

The elements.schema file defines element types that are available from the Edit menu. The elements.schema file is normally located in the struct directory. The default path for the struct directory is:

• /usr/snm/struct on Solaris 1.x machines
• /opt/SUNWconn/snm/struct on Solaris 2.x machines

See the Administration Guide for information on creating new element types.

3.1.13 Properties menu doesn't have agent schema

• Desired agent schema is not listed in element Properties window.

  The agent schemas that are listed in the Properties window are those files with the.schema extension that are located in the directories specified in the Console Properties window. By default, these directories are:

  · /usr/snm/agents and /usr/snm/struct on Solaris 1.x machines

  · /opt/SUNWconn/snm/agents and /opt/SUNWconn/snm/struct on Solaris 2.x machines

  Agent schema files are provided with agent software. If you are using an agent that is not supplied with the SNM package, make sure that the agent schema file is located in a directory specified in the Console Properties window. See the Administration Guide for information on Schema Directories setting.

  Certain agents, such as the SNMP proxy agent, can use multiple schema files for a single element. These schema files can be Sun-supplied SNMP schema files or schema files created from an enterprise-specific SNMP Management Information Base (MIB) file used to manage a specific device. See the Administration Guide for more information.

3.1.14 Can't use Quick Dump

• Quick Dump option is not available from the Glyph menu.

  If there are no readable attributes for any agent on the target system, the Quick Dump item in the Glyph menu is dimmed.

3.1.15 Can't find data report

If you have a large number of incoming data reports, it is not unusual for the maximum number (1000) of data reports in the Data Reports window to be reached. When this happens, the total number of entries in the Data Reports window will not increment, although new reports are added. You can change the maximum number of entries by modifying the Maximum Data Reports setting in the Miscellaneous category of the Console Properties window. See the Administration Guide for more information.

3.1.16 snm -i exits with an error

snm -i exits with the error, "Runtime database does not contain 'viewBackground' record definition."

Verify that the definitions file has the correct version and restart the product application. Your SNMHOME environment variable may not be set correctly. If you have installed the product application in a non-default directory (not /opt), then you have to set SNMHOME pointing to the installed directory.

In csh:

setenv SNMHOME <your directory>/SUNWconn/snm

If you have installed the product application in the default directory, do the following:

unsetenv SNMHOME

3.2 Elements

3.2.1 Can't delete elements

The element you tried to delete has an active request, or the element contains another element in its view.

If you attempt to delete an element that has an active agent request associated with it or that contains another element in its view, the following message appears in the Console footer:

Cannot cut or delete objects with non-empty subviews. 0 element(s) deleted.

You need to kill the agent requests for the element or delete the elements in its view.

3.2.2 Incorrect element type

Element types are not correct.

Discovered devices are classified as either routers, workstations, or servers. See the Administration Guide for information on changing an element type.

3.2.3 Can't drop or paste element

• If the following error message appears:

Attempt(s) to Drop or Paste into a request.

You attempted to paste an element into a request view.

• No agents were specified in the Properties window of the target element.

  The following message indicates that agent software has not been installed on the target system.

Attempt(s) to Drop or Paste to an element accepting no requests

Run the getagents program on the target system.

• The agent in the copied request is not associated with the target element.

The following message indicates that the agent specified in the copied request is not associated with the target element.

Attempt(s) to Drop or Paste a request unknown to an element

Check that the agent is appropriate for the target element and install the agent software on the target system, if necessary.

• You cannot paste requests into the Home view.

  The following message indicates that you tried to copy a request to the Home view.

Attempt(s) to inappropriately Drop or Paste into Home

You can only copy a request to an element subview.

3.3 Tools

3.3.1 No data stream from Browser

If you see the following message in the footer of the Results Browser window, you need to select the report streams to be graphed before you can send data to the Grapher.

No Streams Selected

See Administration Guide for information about selecting report streams.

3.3.2 Can't graph attribute

Attribute is not graphable.

Only attributes of data types integer, float, counter, gauge, timestamp, or UNIX time can be graphed.

3.3.3 Bad data scale of graph

By default, the vertical axis of a graph is plotted using Absolute values. The minimum and maximum values of the vertical axis are the smallest and greatest values among all the data sets that are being graphed. If you graph different attributes on the same graph, data sets can sometimes virtually disappear in the graph display.

You should probably change the graph display to use Relative data scale values. The maximum and minimum values of the graph will then vary according to the maximum and minimum values of each data set. See the Administration Guide for information on changing the graph display.

3.3.4 Bad time scale of graph

By default, the horizontal (time) axis of a graph is plotted using Absolute values. The minimum and maximum values of the horizontal axis are the earliest and latest times among all the data sets that are being graphed. If you graph different time periods on the same graph, data sets can sometimes virtually disappear in the graph display. You should probably change the graph display to use Relative time scale values. The maximum and minimum values of the graph will then vary according to the maximum and minimum values of each data set. See the Administration Guide for information modifying the graph display.

3.3.5 Can't print graph

Graph does not print or the graph does not print in color.

Check the printer options in the Snapshot window to make sure that they match the characteristics of the printer.

3.3.6 Can't discover networks beyond local network

To allow discovery for networks beyond your local network:

1. Make sure the local router has SNMP running.

2. Make sure the correct read community string is entered.

3. Make sure that the hop cound is greater than zero (0).

4. Start Discover.