17.1 Global Properties

You can set global properties from the Console Props button in the Console Properties window. You display the Console properties window by ensuring no glyphs are selected in the Console window (click SELECT anywhere in the Console window that is not a glyph), then clicking SELECT on the Props button as illustrated in Figure 17-1.

Figure 17-1

Clicking on the Props button brings up the window shown in Figure 17-2.

Figure 17-2

The Console Properties window has a Category abbreviated menu button that provides the window categories shown in Figure 17-3.

Figure 17-3

These categories are described in the following subsections. When you choose a category from the menu, the name to the right of the abbreviated menu button changes to reflect the new category, and the property window displays a pane with the settings for the selected category.

After you have entered in all the changes in a window, click SELECT on the Apply button to apply the new settings and dismiss the Console Properties window. Click SELECT on the Reset button to return to the previous settings. Click SELECT on the pushpin in the upper right corner to unpin, and thereby dismiss, the Console Properties window.

Most changes to window settings take effect during your current Console session, although you may not see the change immediately. For instance, if you change the window title, you will not see the change until you change views or the currently-displayed Console window is changed. A few changes to window settings do not take effect until you restart the Console--these settings are noted in the descriptions in Section 17.2, "Windows."

17.2 Windows

The settings in the Windows category define the properties of the main windows of the Console and Console tools. The items in the Console Properties window for the Window category are as follows:

Icon Font: Specifies the font used by the Console to display the labels under the glyphs. The default is "lucida-10." You can enter a font that is available on your server--use the xlsfonts command to see available fonts.

---

Note - You must restart the Console in order for changes to the Icon Font setting to take effect.

---

Window Title: Specifies the text that appears in the title bar of all of the Console's windows. The default is "SunNet Manager Console." The text can be up to 80 characters (no quotation marks are required). If the text is too long for the size of a window, only a view name is displayed.

Display Username in Title: Specifies whether or not the value of the environment variable SNM_USER (or USER if SNM_USER is not set) is displayed in the title bar in parentheses just after the value of Window Title. A check mark in the box indicates that the user name is to be displayed in the title bar--click SELECT on the box to toggle the check mark on or off. By default, this is off (no user name is displayed).

Maximum Colors: Specifies the number of user colormap entries the Console uses. This value is the maximum number of unique colors which can be supported in a given view. The default is 32. To change the value, either type in a new number or click SELECT on the down arrow. The range of possible values is 16 to 255.

---

Note - You must restart the Console in order for changes to the Maximum Colors setting to take effect.

---

Horizontal Scrolling: Specifies the number of pixels to move whenever you click SELECT on the left or right arrows of the horizontal scroll bar of a Console window. The default is 16. To change the value, either type in a new number or click SELECT on the up or down arrows. The range of possible values is 1 to 99.

Vertical Scrolling: Specifies the number of pixels to move whenever you click SELECT on up or down arrows of the vertical scroll bar of a Console window. The default is 16. To change the value, either type in a new number or click SELECT on the up or down arrows. The range of possible values is 1 to 99.

17.3 Requests

The settings in the Requests category define certain Data and Event Request properties. The Requests category is shown in Figure 17-4, "Console Properties Requests Category."

Figure 17-4

Restart Request upon Agent Failure: Specifies the default value of the Restart field in the Request Properties window. A check mark in the box specifies that whenever a new Request Properties window is displayed, the Restart field in the Request Properties window is on (a check mark appears next to the Restart field). The default value can be overwritten in the Request Properties window for individual

requests. Click SELECT on the box to toggle the check mark on or off. By default, this field is off (the Restart field is off in the Request Properties window).

Request Timeout: Specifies the time (in seconds) that the Console waits for a response from an agent when starting or stopping requests. The default value is 20. The range of possible values is 10 to 300 (5 minutes).

Maximum Restart Timeout: Specifies the maximum interval between attempts to start a failed request. If a request fails to start, the Console retries the request after 60 seconds. If the request fails again, it is retried again after 120 seconds. The interval between failed requests and the re-sending of the request is doubled for each restart attempt. If the maximum restart timeout value is reached before the agent responds to the request, the maximum restart timeout value becomes the interval between resent requests. The default value is 1800 seconds (30 minutes). The range of possible values is 120 to 3600 (1 hour).

17.4 Automatic Management

You can enable Automatic Management to automatically monitor the health of your network. You do this by sending an event request to each managed device to determined the state of the device. This feature also allows predefined Event Requests to start automatically for elements that are added to the management database. The Automatic Management category in the Console Properties windows in shown in Figure 17-5.

Figure 17-5

By default, the automatic node management feature is disabled. If you enable this feature, you can also define the reporting characteristics and signal options of automatic requests. Before you enable automatic node management, read the following section, which describes how it works.

If you enable automatic node management, you can specify that predefined Event Requests not be sent for elements that are created in certain views or buses. This is done with the Auto Manage Off option in the bus or view's Glyph menu. Refer to Section 14.10.12, "Auto Manage Off," on page 14-32 for more information about this option.

If you enable automatic node management and then load an ASCII database file, the Console will attempt to start a predefined Event Request for every element defined in the database that supports one of the proxy agents listed above. You can disable automatic node management for certain views. This is done with the Auto Manage Off option of the element's Glyph menu (refer to Section 14.10.12, "Auto Manage Off," on page 14-32 for more information). You can kill launched Event Requests at the same time by using the Requests Summary window. Once you have killed these requests, re-save the database to an ASCII file. The next time the file is loaded, no predefined Event Requests will be started.

You can use automatic management in one of two modes: default or custom. Choose the mode (behavior) by selecting the appropriate value in the management behavior field as shown in Figure 17-5.

If you choose Default mode, SunNet Manager will send predefined requests as explained in Section 17.4.1, "The Default Option."

17.4.1 The Default Option

If automatic node management is enabled with the default option, a predefined Event Request is automatically started for new elements that support at least one of the following proxy agents:

• SNMP
• hostperf
• ICMP ping

The event specification for each default proxy agent is described below.

If the element supports more than one of the proxy agents in default mode, the predefined Event Request that is actually sent is determined in the following order:

1. If you have specified that the new element can be managed with a Sun-supplied SNMP schema, the following is defined as the event for the element:

   ifOperStatus Not Equal To 1

   which specifies the condition where a device is not up.

   If the element can be managed with multiple Sun-supplied SNMP schemas, the Console uses the following order of schema files:

   a. snmp.schema (MIB I)

   b. snmp-mibII.schema (MIB II)

   c. sun-snmp.schema (MIB II with Sun enterprise-specific extensions for Sun workstation support)

   For example, if an element supports MIB I as well as the Sun workstation MIB, the Console uses the schema file associated with MIB I (snmp.schema) for the auto request. Note that if the element supports SNMP but does not support the ifOperStatus attribute, an error is

returned to the Console. If this happens, the request is stopped. If the element supports the hostperf proxy agent, the predefined Event Request that is associated with the hostperf proxy agent is sent. Otherwise, if the element supports the ping proxy agent, the predefined Event Request that is associated with the ping proxy agent is sent.

2. If you have specified that the new element can be managed with the hostperf agent, the following is defined as the event for the element:

   uptime increased by less than <number>

   where <number> is the value of the Polling Interval setting in the Console Properties Automatic Management category minus 2 minutes. By default, the value of <number> is 8 minutes.

3. If you have specified that the new element can be managed with the ping agent, the following is automatically defined as the event for the element:

   reachable equal to 'false'

Once started, an automatic Event Request can be modified like any other request. The window for the Automatic Management category is shown in Figure 17-5 on page 17-8, with the automatic node management feature enabled (checked off). If you disable the automatic node management feature, the rest of the items in the window are grayed-out.

The items in the Automatic Management category window are described below:

Automatic Management: Specifies whether the automatic node management feature is enabled. A check mark in the box indicates that the feature is enabled--click SELECT on the box to toggle the check mark on or off. When this field is off (automatic node management is disabled), the remaining items in the window are dimmed. If automatic node management is not enabled (check box is empty and you click SELECT on Apply), the Auto Manage option in the element Glyph menus is not available. Note that if you enable automatic node management then later disable it, all active automatic requests are killed.

Polling Interval: Specifies the interval (in seconds) for the agent to send reports. By default, the reporting frequency for automatic requests is set to '600' (10 minutes). To change the value, either type in a number on the line or click SELECT on the up or down arrows. The range of possible values is 1 to 9999 (seconds).

---

Caution - If you decrease this number substantially, you can cause network traffic problems.

---

Event Priority: Specifies the priority of an event from an automatic node management request. The default is High. To change the setting, click SELECT on the appropriate rectangle.

Glyph Effect: Specifies a visible indicator when an event is reported from an automatic node management request. Only one glyph effect option can be chosen. The default is Color by Priority. To change the setting, click SELECT on the appropriate rectangle.

Audio Effect: Specifies an audible indicator when an event is reported from an automatic node management request. Only one audio effect option can be chosen. The default is None (no audible indicator). To change the setting, click SELECT on the appropriate rectangle.

Audio File: Defines the audio file to be played when an event is reported from an automatic node management request. (The option Play Audio File must be specified in the Audio Effect field for this setting to be enabled.) Type in the path name of the audio file. The audio file will be played at the currently-set audio level.

---

Note - The Console must be running (not merely displaying) on a machine with an audio port. If you are running the Console on a server but displaying the Console windows on a local workstation, the Console will attempt to play the audio file on the server.

---

Send Mail To: Defines one or more mail recipients to whom an Event Report is sent when an event is reported from an automatic node management request. Type in a list of mail recipients. If there is more than one recipient, use a space or comma between each entry.

Send To Program: Defines a program or shell script to be run when an event is reported from an automatic node management request. Include the directory path, if necessary. A new copy of the program or shell script is forked for each event report. The event report is passed to the standard input of the program or shell script. For example, if the value were cat > /tmp/trap.rpt, it would cause the cat program to receive the event report and write it to the file /tmp/trap.rpt.

17.4.1.1 The Custom Option

Starting with version 2.3, SunNet Manager provides a powerful addition to Automatic Management called customized auto management. This feature allows you to selectively perform auto management on a particular class of devices.

If the default action does not meet your requirement, you can create a predefined request by selecting the Custom option in the management behavior field as shown in Figure 17-5. Your predefined requests will be attached with the type of node against which you want to run the request. Click SELECT on Customize to see the Customize Automatic Management window as shown in Figure 17-6.

Figure 17-6

The Component list on the left side of the screen will list the components in your runtime database that were identified during initialization from the elements.schema file. The Predefined Request list is read from the SNMpredefined file in your home directory.

A predefined request can be attached to a component type using the following steps. Refer to Figure 17-7 for examples of the fields explained in the steps below.

Figure 17-7

1. Use the mouse to select a component from the component list.

2. Use the mouse to select a request from the predefined request list.

   To create a predefined request, click SELECT on Create Predefined and see Chapter 5, "Specifying Event Requests" for information on creating predefined event requests.

3. Click SELECT on the Add button.

The component/request pair appear in the Customized Automatic Management Request list.

You can detach a predefined request from the component type using the following steps:

1. Use the mouse the select the desired entry from the Customized Automatic Management Request list.

2. Click SELECT on Delete.

You can also detach a predefined request from a component and attach a new predefined request using the following steps:

1. Use the mouse to select the desired entry from the Customized Automatic Management list.

   The corresponding component/predefined requests are automatically selected.

2. Use the mouse to select a new predefined request from the Predefined Request list.

3. Click SELECT on the Change button.

4. Click SELECT on Apply to submit changes.

Note that if an element or component supports more than one agent, only one predefined Event Request is sent.

The changes are saved to .SNMautomanagement in your home directory and the request(s) is launched.

You can combine customized automatic managed with default automatic management. This means you can choose to run predefined requests for a specific component type (such as a router), and at the same time run default automanagement for the rest of the nodes. To combine the features:

1. Select a component from the component list.

2. Select a predefined request from the Predefined Request list.

3. Click SELECT on the Add button.

4. Click SELECT on the checkbox at the top of the customized window as shown in Figure 17-6.

5. Click SELECT on Apply.

SunNet Manager will run your predefined request for the component you selected and will run default automatic management for the rest of the components.

To run only customized requests, do not click the checkbox at the top of the customized window.

17.5 Events and Traps

The settings in the Events and Traps category allow you to define Console operations for events and traps. You can also specify signal options for trap reports.

---

Note - Trap report signal options are effective for all trap reports the Console receives.

---

The window for the Events and Traps category is shown in Figure 17-8.

Figure 17-8

Open on Event or Trap: Specifies whether the Console window should be opened if it is closed to an icon when an event or trap report is received. A check mark in the box indicates that Console should be opened--click SELECT on the box to toggle the check mark on or off. By default, this is off (Console window is not opened).

Upon Opening: The Open on Event or Trap setting described above must be checked for this setting to be enabled. Upon Opening specifies the view to be displayed when the Console window is opened and an event or trap report has been received. Press MENU in the Upon Opening abbreviated menu button to receive the menu in Figure 17-9.

Figure 17-9

The default is Stay in Current View (the Console displays the same view it displayed before the Console window was closed to an icon). To change the setting, press MENU on the abbreviated menu button and release on the desired option. Go to Home View causes the Console to always display the Home view while Go to View Containing Element causes the Console to display the view that contains the element for which an event or trap report is received.

Propagate Event Effect: Specifies whether the glyph effect options of events are propagated to all parent views of the affected element. A check mark in the box indicates that propagation is enabled--click SELECT on the box to toggle the check mark on or off. By default, this is on (events' effects are propagated through the view hierarchy).

---

Note - You can disable glyph state propagation for a view by setting the Glyph State field in the view's Property window to "Not Inherited."

---

If a glyph is contained in more than one view, its state is propagated through its multiple view hierarchies. When the Console is closed to an icon, glyph state changes reflected in the Home view cause the SNM Console icon to display question marks.

If there are different glyph states propagating to the same view glyph, the view glyph assumes the state of the highest-priority member glyph state. The following list defines glyph-state priority from highest to lowest:

a. Color set by the priority of the event. By default, high, medium, and low priority events are red, orange, and yellow, respectively.

b. Dimmed

c. Blinking

You can explicitly change the state of a glyph by using the Glyph State option in the Glyph menu for the element. There are two important points to remember when using this option to change glyph state:

• When you change the state of a glyph, the new glyph state is propagated as though an event had occurred to change the glyph state. For example, if you change the glyph state of an element from normal to blinking, the glyph state (blinking) propagates as if an event had occurred.
• If you have multiple glyph states propagating into a single view, and you change the glyph state for the view to normal, the member glyph states are also reset to normal. For example, if you change the glyph state of a view from blinking to normal, the effects of the event that caused a member element to blink are cleared. This allows you to clear multiple events by resetting the glyph state of a view.

Starting with version 2.3, you can specify pending mode for a glyph state, (press MENU over the target glyph; release MENU over Pending On/Off). The glyph object is dimmed and outstanding traps/events are cleared. New traps/events do not change the glyph state or propagate the effect of the trap/event to the parent object. If a parent object is in pending state, a state change for any child object has no affect on the parent. See Chapter 5, "Specifying Event Requests," for more information about glyph pending state.

Event Effect Overlap Time: Specifies the amount of time (in seconds) beyond the reporting interval that an event's glyph effect options remain in effect. If another event does not occur within this overlap time, the Console cancels the current signal option. The default is 10 seconds. To change the value, either type in a number on the line or click SELECT on the up or down arrows. The range of possible values is 0 (no overlap) to 86400 (24 hours).

---

Note - If the reporting interval is not specified in the event report, the Console assumes the reporting interval to be 60 seconds.

---

The following fields pertain to traps only.

Glyph Effect:

Specifies a visible indicator when a trap is reported. The default is Color by Priority. Starting with version 2.3, you can customize the color of the glyph to indicate Low, Medium or High priority by clicking on Props >> Custom Colors on the Console menu as shown in Figure 17-10.

Figure 17-10

When you receive the Custom Colors window in Figure 17-11, use the mouse to slide the indicators to the color you wish for each priority level.

Figure 17-11

Note that the Console can receive high, medium, and low priority traps. (Low priority traps are generated when the SNM database API functions are used to add, change, or delete elements in the database.) If you keep the default Color by Priority option, high priority traps cause the element's glyph to turn red and low priority traps cause the glyph to turn yellow. If both high and low priority traps are received for an element, high priority is used. In association with the Color by Priority option is the decay feature. The decay feature pertains to traps that have been reported and for which the Effect Decay Time period has expired. In response to these conditions, the glyph for the affected element turns blue (the default), or to a color you have customized. Once a glyph shows the decay color, the trap report must be acknowledged in order for the glyph to return to its original color. To get a glyph to return to its original color, you can either:

• Select the Console's View >> Event Summary option
• Highlight the name of the glyph
• Press the Drop from List button.

  Or

• From the Glyph Menu for the specific element, pull right over the Glyph State >> Normal option.

Propagate Effect: Specifies whether the glyph effect options of traps are propagated to all parent views of the affected element. A check mark in the box indicates that propagation is enabled--click SELECT on the box to toggle the check mark on or off. By default, this is on (trap's effects are propagated through the view hierarchy).

Glyph state changes that result from traps propagate in the Console's view hierarchy in the same manner as with glyph state changes that result from events. See the description of the Propagate Event Effect setting for more information about propagation of glyph state changes.

Effect Decay Time: Specifies the amount of time (in seconds) during which a trap's glyph effect option remains in effect. After the specified time, the effect caused by the trap is automatically cleared and the glyph's state is returned to "Normal" or decayed to blue. The latter only occurs when the Color by Priority option is in effect as described above under Glyph Effect. The default is 0 (glyph effects caused by a trap are not automatically cleared). To change the value, either type in a number on the line or click SELECT on the up or down arrows. The range of possible values is 0 to 86400 (24 hours).

Audio Effect: Specifies an audible indicator when a trap is reported. Only one audio effect option can be chosen. The default is None (no audible indicator). To change the setting, click SELECT on the appropriate rectangle.

Audio File: Defines the audio file to be played when a trap is reported. (The option Play Audio File must be specified in the Audio Effect field for this setting to be enabled.) Type in the path name of the audio file. The audio file will be played at the currently-set audio level.

---

Note - The Console must be running (not merely displaying) on a machine with an audio port. If you are running the Console on a server but displaying the Console windows on a local workstation, the Console will attempt to play the audio file on the server.

---

Send Mail To: Defines one or more mail recipients to whom a trap report is sent when a trap is reported. Type in a list of mail recipients. If there is more than one recipient, use a space or comma between each entry.

Send To Program: Defines a program or shell script to be run when a trap is reported. Include the directory path, if necessary. A new copy of the program or shell script is forked for each trap report. The trap report is passed to the standard input of the program or shell script. For example, if the value were cat > /tmp/trap.rpt, it would cause the cat program to receive the trap report and write it to the file /tmp/trap.rpt.

Ignore Database Traps: Defines whether the traps generated when changes are made in the database are displayed by the Console. Low priority traps are generated when elements are added, changed, or deleted in the database, or if a new database file is loaded. A check mark in the box indicates that these traps are ignored by the Console -- click SELECT on the box to toggle the check mark on or off.

---

Note - With the Ignore Database Traps option turned off, when you create an element, the trap report for that element says that the element was "created." An analogous operation using the database API returns the word "added" rather than "created."

---

17.6 Errors

The settings in the Errors category allow you to specify signal options for errors that the Console receives from agents. Note that the only type of errors that cause glyph state changes are errors received from agents; glyph state changes do not occur as a result of local Console errors. The window for the Errors category is shown in Figure 17-12, "Console Properties Errors Category."

Figure 17-12

Signal On: Specifies whether signal options are in effect for all errors received from agents or only fatal errors. The default is Fatal Errors. To change the setting, click SELECT on All Errors.

Glyph Effect: Specifies a visible indicator when an agent error is reported. Only one glyph effect option can be chosen. The default is Dim. To change the setting, click SELECT on the appropriate rectangle. Note that agent errors can be either high or low priority errors. If you choose the Color by Priority option, high priority errors (generic errors and agent-specific fatal errors) cause the element's glyph to turn red and low priority errors (agent-specific warnings) cause the glyph to turn to the default color of yellow. If both high and low priority errors are received for an element, high priority is used.

Propagate Effect: Specifies whether the glyph effect options of errors are propagated to all parent views of the affected element. A check mark in the box indicates that propagation is enabled--click SELECT on the box to toggle the check mark on or off. By default, this is off (error's effects are not propagated).

Glyph state changes that result from errors propagate in the Console's view hierarchy in the same manner as with glyph state changes that result from events. See the description of the Propagate Event Effect setting in the Events and Traps category for more information about propagation of glyph state changes.

Effect Decay Time: Specifies the amount of time (in seconds) during which an error's glyph effect option remains in effect. After the specified time, the effect caused by the error is automatically cleared and the glyph's state is returned to "Normal." The default is 0 (glyph effects caused by an error are not automatically cleared). To change the value, either type in a number on the line or click SELECT on the up or down arrows. The range of possible values is 0 to 86400 (24 hours).

Audio Effect: Specifies an audible indicator when an error is reported. Only one audio effect option can be chosen. The default is None (no audible indicator). To change the setting, click SELECT on the appropriate rectangle.

Audio File: Defines the audio file to be played when an error is reported. (The option Play Audio File must be specified in the Audio Effect field for this setting to be enabled.) Type in the path name of the audio file. The audio file will be played at the currently-set audio level.

---

Note - The Console must be running (not merely displaying) on a machine with an audio port. If you are running the Console on a server but displaying the Console windows on a local workstation, the Console will attempt to play the audio file on the server.

---

Send Mail To: Defines one or more mail recipients to whom an error report is sent when a error is reported. Type in a list of mail recipients. If there is more than one recipient, use a space or comma between each entry.

Send To Program: Defines a program or shell script to be run when an error is reported. Include the directory path, if necessary. A new copy of the program or shell script is forked for each error report. The error report is passed to the standard input of the program or shell script. For example, if the value were cat > /tmp/trap.rpt, it would cause the cat program to receive the error report and write it to the file /tmp/trap.rpt.

17.7 Locations

The settings in the Locations category allow you to define the directories where the schema and icon files used by the Console are found. The Locations category is shown in Figure 17-13, "Console Properties Locations Category."

Figure 17-13

---

Note - You must restart the Console in order for changes to the Locations settings to take effect.

---

Schema Directories: Specifies one or more directories that contain agent and element schema files. The Console searches these directories from left to right, loading any files ending in.schema. Multiple directories are separated by colons (:). The directories must be absolute path names (start with /) and cannot contain environment variables.

Icon Directories: Specifies one or more directories that contain icon and icon mask files. The Console searches these directories from left to right, loading any files ending in .icon and .iconmask. Multiple directories are separated by colons (:). The directories must be absolute path names (start with /) and cannot contain environment variables.

17.8 Miscellaneous

The settings in the Miscellaneous category allow you to define Console parameters not covered in the other categories. The window for the Miscellaneous category is shown in Figure 17-14, "Console Properties Miscellaneous Category."

Figure 17-14

Different Windows for Load & Save: Specifies whether different windows are displayed for Load and Save operations. A check mark in the box indicates that different windows are displayed--click SELECT on the box to toggle the check mark on or off. By default, this is off (the same window is used for Load or Save operations).

Verify Quit: Specifies the verification prompt, if any, displayed by the Console whenever you choose to quit a Console session. The default is If Requests are Active (a verification prompt is displayed only if there are active requests; the verification prompt asks if you want the active requests automatically killed before the Console is exited). To change the setting, click SELECT on the appropriate rectangle: Never causes no verification prompt to be displayed, Always causes a verification prompt to be displayed even if there are no active requests.

SELECTing Goto Button Means: Specifies the view that is displayed whenever you click SELECT on the Goto menu button. The default is Last Visited View. To change the setting, click SELECT on Home View (the Home view is displayed whenever you click SELECT on the Goto menu button).

Goto Empty Views: Specifies whether or not the Console displays an empty view. A check mark in the box indicates that the Console can display empty views. Click SELECT on the box to toggle the check mark on or off. By default, this is on (Console can display empty views). If the box is not checked, the Console does not display empty views and an error message appears in the Console's footer. However, an empty view can still be selected if the user clicks SELECT twice on the empty view.

Read-Only Mode In read-only mode, you can run your applications and manage requests. However, the following menu items are dimmed: Edit, Create Predefined Requests, and Change Type. See Chapter 14, "Console" for more information regarding Read-Only mode.

Maximum Data Reports: Defines the maximum number of data reports that can be displayed in the Data Reports window. The default is 1000. The range of possible values is 10 to 99999.

Maximum Error Reports: Defines the maximum number of error reports that can be displayed in the Error Reports window. The default is 100. The range of possible values is 10 to 99999.

Maximum Event Reports: Defines the maximum number of event reports that can be displayed in the Event/Trap Reports window. The default is 1000. The range of possible values is 10 to 99999.

Maximum Trap Reports: Defines the maximum number of trap reports that can be displayed in the Event/Trap Reports window. The default is 1000. The range of possible values is 10 to 99999.

17.9 Custom Colors

Starting with version 2.3, you can customize trap priority colors by selecting Props >> Category >> Custom Colors. You receive the screen in Figure 17-15.

Figure 17-15

See Section 17.5, "Events and Traps," on page 17-16 for a description of the Custom Colors function.

When you click SELECT on Apply after selecting the color(s) you wish, the changes are saved to the .SNMdefaults file. If the colors are different from the previous values, the glyph state colors for the target objects are recalculated and displayed.

17.10 Other Configuration

When you apply a setting in the SunNet Manager Console Properties window (under Props, when no glyphs are selected), the information is stored in the $HOME/.SNMdefaults file. The $HOME/.SNMdefaults file is intended to contain per-user configuration information.

Per-product defaults can be placed in $SNMHOME/defaults. This allows you to set up site-wide Console resources and definitions so that everyone who uses the product uses those defaults. If the user has their own $HOME/.SNMdefaults file, the information in the $HOME/.SNMdefaults overrides the information in $SNMHOME. Users can also set the environment

variable SNMDEFAULTS to have the Console read another file instead of $HOME/.SNMdefaults. If SNMDEFAULTS is not set, the Console reads $HOME/.SNMdefaults.

---

Note - The Console also supports X11 resources configurations, however settings in $HOME/.SNMdefaults take priority.

---

There are a few optional definitions you can specify to further customize the operation of the Console. You can add these definitions into one of the files described above.

17.10.1 Forking Programs For Element Types

You can specify a program that is forked for an element type when an instance of the element type is created or modified. To do this, use the following definitions:

snm.console.<element-category>.<element-type>.createProg: <program1> snm.consolecomponent.<element-category>.<element-type>.modifyProg: <program2>

where <program1> and <program2> are forked whenever the <element-type> is created or modified, respectively. Note that you can specify * for <element-category> or <element-type>. If you want programs to be forked for any creation or modification of an element, use the following definitions:

snm.console.*.*.createProg: <program1> snm.console.*.*.modifyProg: <program2>

If you want a program to be forked whenever any view is created, use the following definition:

snm.console.view*createProg: < program>

If you want a program to be forked whenever an ethernet element type (bus.ethernet, view.ethernet, etc.) is created, use the following definition:

snm.console*ethernet.createProg: <program>

The process that is forked when an element is created has the following parameters:

<program1> -c -v <viewname> -t <object_type>

where <viewname> is the current view, and <object_type> is the type of the object created.

The process that is forked when an element is modified has the following parameters:

<program2> -m -v <viewname> -n <object_name>

where <viewname> is the current view, and <object_name> is the name of the object being modified.

17.10.2 Redirecting SNMP Requests

You can have SNMP requests from the Console redirected to another vendor's SNMP proxy. To do this, use the following definition:

snm.console.snmpRedirect: true snm.console.snmpRedirectItem: <label> snm.console.snmpRedirectAgent: <agent>

where <label> appears in the bottom left panel of the Data and Event Request Properties window and <agent> is the name of the SNMP proxy agent to which the requests will be redirected. In the Request Properties window, a box appears next to <label>--click SELECT in the box to toggle a check mark on or off. A check mark causes the request to be redirected.

---

Note - The Console does not kill redirected requests when it starts or exits. You must explicitly kill these requests with the snm_kill(1) command. This feature is intended for vendor-supplied SNMP proxies that do not return reports to the Console.

---

17.10.3 Activating Console Database Manager Traps for File Loads

The Console can be configured to issue a trap to inform other applications when a new runtime database is loaded. Such a trap contains the names of the elements that have been loaded.

To activate this feature, the .SNMdefaults file needs to be modified to set the value of snm.console.DBMgrTrapAlways to true. By default, this property is set to false.

17.11 Custom Colors

Starting with version 2.3, you can customize colors of event and trap priority levels. The default colors continue to be Low=yellow, Medium=orange, High=Red, and decay=blue. By choosing the Custom Colors category, you receive the window in Figure 17-16.

Figure 17-16

You can determine the current RGB value of a color for particular objects by choosing the checkbox corresponding to the priority state or the decay state of the element. Customize the color by sliding the color indicator(s) to the desired position. If the colors are different from the previous values, the glyph state colors for the objects are recalculated and displayed.

Click SELECT on Apply to save the new color to the .SNMdefaults configuration file.