4.1 Configuring the Cooperative Consoles Receiver

If you select the Receiver button from the CC Configuration main menu, the Receiver Configuration window appears, as shown in Figure 4-3.

Figure 4-3

The Receiver Configuration window allows you to build the registration list that determines the remote management stations that the local Receiver process will attempt to register with when it is launched. You can also specify the manner of automatic synchronization of the receiving station with remote sending stations.

4.1.1 Adding a New Entry to the Registration List

To add a new entry to the Registration List, you need to enter the appropriate information in the three fields at the bottom of the list window:

• Sender Hostname -- This name is the host name of a remote Site/SunNet/Domain Manager console machine where a Sender daemon has been installed.
• Database Name -- This name is the instance name of the runtime database on the remote machine that the Receiver requests access to when it registers with the Sender daemon on the remote machine. For example, if the database file is named db.localnet, then the name that should be entered in this field is localnet.
• Filter File -- This field requests the filter file name on the sender station used to select event, trap, and topology information for forwarding. By default, filter_none.ccf is listed.
• Delete Permission -- This toggle allows you to control deletion of elements in response to deletions of element instances on remote sending stations. If Delete Permission is set to Source, the Receiver deletes an element in response to a delete trap from a remote station only if that connection was the source of the local element instance (as indicated by the Created by cc field on the local element's properties sheet). If Delete Permission is set to All, then a delete trap received from a remote station results in the deletion of that element on the local Console even if that connection was not the source of the local instance of that element.
• Startup -- This toggle determines whether the Receiver automatically executes a synchronization with the selected sending station whenever the Receiver is started.
• Sync Frequency -- This option allows you to enable automatic synchronization of the selected connection at scheduled intervals. Automatic synchronization can be scheduled to occur either Daily or Weekly. If None is selected, scheduled synchronization is disabled.
• Day of Week -- A pulldown menu enables you to select the day of week for scheduled automatic synchronization. This selection takes effect only if you have selected Weekly for Sync Frequency.
• Sync Time -- A pulldown menu enables you to select the time of day for scheduled automatic synchronization. This selection takes effect only if you have selected Daily or Weekly for Sync Frequency.

After you have added this information, click SELECT on the Add button to add the new entry to the Registration List. A sample Registration List is shown in Figure 4-4.

Figure 4-4

4.1.2 Modifying an Entry in the Registration List

If you want to change one of the existing entries in the Registration list, do the following:

1. Click SELECT on the entry that you want to change. The entry should now be highlighted.

2. The values for the three fields in the selected entry should now be displayed in the Sender Hostname, Database Name, and Filter File fields at the bottom of the screen. Edit these fields to make your desired changes.

3. Click SELECT on the Change button for your changes to take effect.

4.1.3 Deleting an Entry from the Registration List

To delete one of the entries from the Registration List, click SELECT on the entry to highlight it, then click SELECT on the Delete button.

4.1.4 Saving the Registration List

After you have finished adding or modifying entries in the Registration List, be sure to click SELECT on the Apply button to save your changes.

4.1.5 Abandoning Changes to the Registration List

If you want to abandon the changes you have made to the Registration List and revert to the previously saved version of the Registration List, click SELECT on the Reset button.

4.2 Configuring the Sender Daemon

If you select the Sender button from the CC Configuration main menu, the Sender Configuration window appears, as shown in Figure 4-5.

Figure 4-5

If you press the MENU button over the Category button, as shown in Figure 4-6, a menu appears with the following options:

Figure 4-6

• Database Template -- Select this Category if you want to define the topology information that the Sender daemon is to forward to specified Receiver processes. Multiple Database Templates can be defined.
• Trap Selection Template -- Select this Category if you want to define the types of SNMP traps that the Sender daemon is to forward to specified Receiver processes. Multiple Trap Templates can be defined.
• Authorization List -- Select this Category if you want to define the list of remote receiving stations authorized to register with the local Sender and the database instances they are authorized to access.
• Filter Table -- Select this category if you want to define the selection criteria to use when forwarding SNMP traps, Glyph traps, SNM events, and database (topology) traps to receiving stations. Multiple filter tables can be defined.

4.2.1 Setting Up the Authorization List

---

Note - Refer to Section 4.2.3, "Specifying Topology Information for Forwarding" for information on how to set up the Database Template and Section 4.2.4, "Setting Up the Trap Selection Template" for Trap Selection Template discussions.

---

As shown in Figure 4-7, the local Sender's authorization table contains two columns: Remote Receiver Host and Local Database Name.

Figure 4-7

• Remote Receiver Host -- Names of Domain Manager host machines that are authorized to register with this Sender
• Local Database Name -- A database name that the remote Domain Manager host is authorized to use in accessing the runtime management database on the local machine

Two fields at the bottom of the window enable you to create and modify rows in the Authorization List.

• Remote Receiver Host
• Local Database Name

4.2.1.1 Adding a Remote Host to the Authorization List

If you want to enter a new row in this list, type in the host name of the receiving station in the Remote Receiver Host field. Also type a database name in the Local Database Name field. For example, if you want to authorize a remote host to access a database named db.localnet, you enter localnet in the Local Database Name field.

When you have entered the information that you want to specify for the receiving station, click SELECT on the Add button to add the specified host to the authorization list.

You can make multiple entries in the authorization list for the same remote host if that host is authorized to access more than one database, as shown in Figure 4-8.

Figure 4-8

For the example above, the machine netmgr1.Japan.Sun.Com has access to all three regions, db.john, db.central, and db.west.

4.2.1.2 Changing an Entry in the Authorization List

If you want to modify one of the entries (rows) in the authorization table, click SELECT on that row to highlight it. The information for that host is now displayed in the Remote Receiver Host and Local Database Name fields at the bottom of the window. After you have changed these values, click SELECT on the Change button to enter the changes into the table.

4.2.1.3 Removing a Remote Host from the Authorization List

If you want to delete one of the entries (rows) in the authorization list, click SELECT on that row to highlight it, then click SELECT on the Delete button.

4.2.1.4 Saving the Authorization List

After you have added new entries or made other changes in the Authorization List, click SELECT on the Apply button to save your changes.

4.2.1.5 Abandoning Changes to the Authorization List

If you want to abandon the changes you have made to the Authorization List and revert to the previously saved version, click SELECT on the Reset button.

4.2.2 Setting Up the Filter Table

The selection criteria used by the local Sender in forwarding SNMP traps, Glyph traps, SNM events, and topology information to registered receiving stations is contained in one or more filter files. The entries in each filter file constitute a single Filter Table. When you first select Filter Table from the Sender Configuration Category menu, the Filter Table properties sheet are blank, as shown in Figure 4-9.

---

Note - Filtering is the most powerful and complex part of Cooperative Consoles. Please read and understand Section 3.4.2.2, "Filtering Events and Traps for Forwarding" before you attempt to configure the Filter Table.

---

Figure 4-9

4.2.2.1 Loading a Filter

You can either load an existing filter file or define a new filter table. To load an existing filter file, click SELECT on the Load button. You see a load window, as shown in Figure 4-10.

Figure 4-10

The CC product provides several sample filter files as listed in the File List scroll menu. For example, to load the Infrastructure.ccf filter file, select Infrastructure.ccf from the file list, then click SELECT on the Open button.

These sample filter files are located in the following directory:

• /var/adm/snm/cc_files on Solaris 1.x environments
• /var/opt/SUNWconn/snm/cc_files on Solaris 2.x environments

A sample Filter Table is shown in Figure 4-11.

Figure 4-11

Each row in the table is a filter that defines selection criteria and action to be taken if the events or traps match the selection criteria. Events and traps are checked against the filters in the table. See Section 4.2.2.2, "Adding a New Filter" for explanations of the different filter types.

4.2.2.2 Adding a New Filter

To add a new filter to a Filter Table, select the filter type. The filter types are listed if you press MENU on the Filter Type button, as shown in Figure 4-12.

Figure 4-12

• Filter Type -- This selection determines the primary selection criterion for processing a trap or event. The following values are possible: Hostname, Component, View Name, View Type, or Default.

  · Hostname -- When you select Hostname as the filter type, the filter selects events or traps on the basis of host name match. For example, you might want to use a Hostname type filter to select critical nodes by name in order to forward events or traps relating to those devices.

  · Component -- When you select Component as the filter type, the component type name is used to select events and traps. For example, you might want to use a Component type filter to forward events or traps pertaining to all devices of a certain type such as router.

  · View Name -- When you select View Name as the filter type, the filter selects events or traps on the basis of view name match.

  · View Type -- When you select View Type as the filter type, the filter selects events or traps on the basis of view type match.

  · Default -- If the event or trap is not selected by any of the filters in the table, the action specified by the Default filter is taken. For example, if only one hostname entry is present, and Default (Drop) is absent, then all information is passed. Note that a Filter Table should have one and only one Default entry.

• Host Name -- This field changes depending on the filter type selected. The following values are possible: Host Name, Component, View Name, and View Type. The default setting is Host Name.

  · If the Type is Hostname, this field value must be either an IP address or the host name of a glyph in the SNM database. The user must enter in this field value.

  · If the Type is Component, a list of component types is provided. From this list, select a component type (for example, component.router). The selected component type is then displayed for this field value as shown in Figure 4-13.

  · If the Type is View Name, this field value must be a view name. For example, if the view type is named mpk16(view.subnet), then the name to enter in this field is mpk16.

  · If the Type is View Type, a list of view types is provided. From this list, select a view type (for example, building, bus, and campus are all view types). The selected view type is then displayed for this field value as shown in Figure 4-14.

Figure 4-13

Figure 4-14

• Events/Traps -- The Events/Traps field allows you to further discriminate the filtering process. To select the options for this field, press MENU on the Events/Traps button, as shown in Figure 4-15.

Figure 4-15

The following values are possible: All, Events Only, Traps Only, Glyphs Only, Events & Traps, Events & Glyphs, and Traps & Glyphs.

• All-- Selects SNMP Traps, Glyph Traps, and SNM Events. Note that database (topology) traps are not included.
• Events Only-- Selects the SNM Events only. SNM Events are generated as a result of the SNM event request from the Site/SunNet/Domain Manager console.
• Traps Only-- Selects the SNMP Traps only. These traps can be Standard or Enterprise specific SNMP traps.

• Glyphs Only-- Selects the Glyph Traps only. Glyph Traps are originated when the glyph state is changed manually on the Console. The glyph state can also be changed by the forwarding of SNMP Traps and SNM Events.
• Events & Traps-- Selects SNM Events and SNMP Traps.
• Events & Glyphs-- Selects SNM Events and Glyph Traps.
• Traps & Glyphs-- Selects SNMP Traps and Glyph Traps.

• Trap Template -- The Trap Template field specifies the file name to be used in selecting the types of SNMP traps and trap numbers for filtering. If this field is left blank, the trap filtering is based on the selection of the Events/Traps field only. The role of the Trap Template is discussed in Section 4.2.4, "Setting Up the Trap Selection Template."
• Priority -- The priority fields apply to SNMP Traps and SNM Events only. This field specifies the priority of the SNMP Traps and SNM Events for filtering. For example, if you select High for this field, then only high priority events and traps are selected for filtering. If you select Medium, then both medium and high priority events and traps are selected. If you select Low, then Low, Medium, and High priority events and traps are selected. For backward compatibility, the None button exists but it has the same functionality as the Low button.

  All SNMP Traps or SNM Events with a priority less than the priority selected in the Priority field are not selected. For example, if Medium is selected, then all traps and events with a lower priority than Medium are not selected.

• New Priority -- If a value is specified here, this becomes the new priority of the forwarded trap or event. When traps or events are forwarded, their priority is changed to a value specified in this field. If you want to change all events selected by this filter to be forwarded as low priority traps, click SELECT on Low. If you select the As Is button, the priority of a selected trap or event when forwarded remain the same.
• Action -- This field applies to SNMP Traps, Glyph Traps, and SNM Events only. The Action field specifies that the event or trap is to be forwarded or dropped. Click SELECT to highlight the appropriate action in the Action field.

• DB Template -- This field applies to database traps only. The DB Template field specifies the file name used in selecting the topology information to be forwarded or dropped when SNM Database Traps match the filter's Name field. The role of the Database Template is discussed in Section 4.2.3, "Specifying Topology Information for Forwarding."

After you have made all your selections for a single filter, click SELECT on the Add button if you want your selections to define a new filter (row) in the table.

Refer to Chapter 5, "Cooperative Consoles Examples" for the different filter entries examples.

4.2.2.3 Changing a Filter

To change the values of an existing filter in the filter table, do the following:

1. Click SELECT on the filter you want to change in the table.

2. Enter or select the values in the Filter Type, Name, Events/Traps, Trap Template, Priority, New Priority, Action, and DB Template fields.

3. Click SELECT on the Change button to modify the values of the selected filter.

4.2.2.4 Deleting a Filter

To delete a filter in the Filter Table, click SELECT on the filter to be deleted and click SELECT on the Delete button.

4.2.2.5 Saving the Filter File

After you are finished adding new filters, deleting or modifying existing filters in the Filter Table, click SELECT on the Save button to save your changes to this filter file. For changes to existing filter files, select the filter file name from the file list scroll menu (for example, infrastructure.ccf) and click SELECT on the Save button, as shown in Figure 4-16.

Figure 4-16

4.2.2.6 Abandoning Changes to the Filter File

If you want to abandon the changes you have made to the Filter Table and revert to the previously saved version of this filter file, click SELECT on the Reset button, as shown in Figure 4-11.

4.2.3 Specifying Topology Information for Forwarding

The Site/SunNet/Domain Manager Console generates database traps in response to changes in the runtime database. When an SNM database trap is generated, the Sender daemon uses a filter table specified by a remote Receiver process to determine whether the trap should be forwarded to that Receiver process. Within the filter table, a Database Template file is specified to determine the topology information to be forwarded or dropped.

The Database Template files used for selecting topology information to be forwarded/dropped depend on the filter file requested by the Receiver at the time it registered with the local Sender daemon.

Each filter entry in the filter file can specify a DB Template file to be used for elements that match the selection criteria of that filter. The element is selected by the criteria as mentioned under Section 3.4.2.2, "Filtering Events and Traps for Forwarding."

Database Template files are only accessed in response to SNM database traps.

4.2.3.1 Setting Up the Database Template

To configure a Database Template file, select Database Template from the Sender Configuration Category menu. When initially selected, the Database Template window is blank, as shown in Figure 4-17.

Figure 4-17

4.2.3.2 Loading a Database Template File

You can either load an existing Database Template file or create a new Database Template. To load an existing Database Template file, click SELECT on the Load button. A Database Template Load window appears, as shown in Figure 4-18.

Figure 4-18

The CC product provides several sample database template files as listed in the File List scroll menu. For example, to load the passall.cct database template file, select passall.cct from the file list, then click SELECT on the Open button.

These sample database template files are located in the following directories:

• /var/adm/snm/cc_files on Solaris 1.x environments
• /var/opt/SUNWconn/snm/cc_files on Solaris 2.x environments

The passall.cct sample Database Template is shown in Figure 4-19.

Figure 4-19

4.2.3.3 Adding a Database Trap Type Entry

To add an entry for one of the SNM database trap types, press MENU over the Trap Type button, as shown in Figure 4-20, and select one of the available trap types.

Figure 4-20

A Database Template can contain six entries (rows). Each entry corresponds to one of the following types of SNM database trap:

• Add -- Generated when a new element is added by the database Application Programmatic Interface.
• Background -- Generated when a background image is added to a view.

---

Note - Due to the design limitation, Background is not supported at this release.

---

• Change -- Generated when attributes of the element (such as the agents list or the screen coordinates) are changed.
• Create -- Generated when a new element is created via the Site/SunNet/Domain Manager console.
• Delete -- Generated when an element is deleted from the database.

---

Note - Due to the design limitation, the Delete trap cannot be dropped.

---

• Load -- Generated when a new management database is loaded.

To specify the type of action to be taken for one of these SNM database trap types, an entry for that type must be in the template. If no entry is specified for a database trap type in the template, then that particular trap type is dropped.

The following table outlines the types of topology information that can be passed for each database trap type:

Table 4-1

Trap Type	Keywords (one or more can be specified)
Add	membership, color, agents, attributes, connections, drop
Background	drop
Change	membership, color, agents, attributes, connections, drop
Create	membership, color, agents, attributes, connections, drop
Delete	drop
Load	membership, color, agents, attributes, connections, drop

The keywords used determine the forwarded content for each of the available trap types. The keywords have the following interpretation:

• Agents -- If selected, a list of the agents checked off on the properties sheet is forwarded, along with the proxy system name for proxy agents.
• Attributes -- If selected, the attributes of the element (such as, IP address or contact name) as defined in the element's schema are forwarded.

• Color -- If selected, the element's RGB values are forwarded.
• Connections -- If selected, information about simple connections between the selected element and other elements is forwarded.
• Drop -- Select this button if you want the selected database trap type to be ignored (not forwarded). If this button is selected, the other buttons are ignored.
• Membership -- If selected, the Viewname of each view the element belongs to is forwarded as is the screen position (coordinates) of the element within that view.

Each of these buttons is a toggle -- click SELECT on the button to turn it off or on. The button is on when it is highlighted.

After you have selected the desired combination of values for these six toggles, click SELECT on the Add button to add an entry for this trap type to the template.

If no information (for example, Color) is selected for a trap type in the database template, then the information (in this case, color) is not passed.

---

Note - Agents, Attributes, Color, and Connections buttons have no effect for database traps of types Background or Delete.

---

4.2.3.4 Changing the Forwarding Specified for a Trap Type

If you want to modify the topology information specified for a trap type in the Database Template, do the following:

1. Click SELECT on the trap type entry you want to change.

   The six buttons along the bottom of the window should be highlighted to indicate the selected values for that trap type.

2. Make the desired changes in the forwarding action for this trap type.

   Click SELECT on the Agents, Attributes, Color, Connections, Drop, or Membership buttons.

3. Click SELECT on the Change button to apply your selections to the Database Template entry.

4.2.3.5 Deleting a Database Trap Type Entry

You can delete the existing entry in the Database Template for a particular trap type if you click SELECT on that entry, then click SELECT on the Delete button.

4.2.3.6 Saving the Database Template

After you have added new trap type entries, or deleted or modified existing trap type entries in the Database Template, click SELECT on the Save button to save your changes to this Database Template file. For changes to existing database template files, select the database template file name from the file list scroll menu (for example, views-only.cct) and click SELECT on the Save button, as shown in Figure 4-21.

Figure 4-21

4.2.3.7 Abandoning Changes to the Database Template

If you want to abandon the changes you have made to the Database Template and revert to the previously saved version of this Database Template file, click SELECT on the Reset button.

4.2.4 Setting Up the Trap Selection Template

To configure a Trap Selection Template file, select Trap Selection Template from the Sender Configuration Category menu. This template allows the user to filter only SNMP traps based on the trap type (Standard/Enterprise) and trap numbers. When initially selected, the Trap Selection Template window displays the available Enterprise traps names, as shown in Figure 4-22.

Figure 4-22

4.2.4.1 Loading a Trap Selection Template File

You can either load an existing Trap Template file or create a new Trap Template. If you want to load an existing Trap Template file, click SELECT on the Load button. A Trap Template Load window appears, as shown in Figure 4-23.

Figure 4-23

You are prompted to enter the trap selection template file name. If you want to load an existing trap selection template file, select this file name from the File List scroll menu, then click SELECT on the Open button.

As shown in Figure 4-22, the Sender's Trap Selection Template contains these columns:

• Enterprise Name -- This column lists the Enterprise names whose traps are to be forwarded or dropped. Any SNMP Traps that match the Enterprise names in this list are selected. Standard Traps and/or All Enterprise Traps can also be selected from this list.
• Trap No. List -- This field allows users to select the SNMP trap numbers to be filtered. The numbers can be specified as single numbers or as ranges separated by commas, for example, 1, 2-5, 10.

To create and modify rows in the Trap Selection Template, use the Enterprise Name table and the Trap number list field at the bottom of the window.

4.2.4.2 Adding a Trap Type Entry

If you want to enter a new row in this list, follow these steps:

1. Click SELECT on the enterprise names provided in the Enterprise Name field.

   These names are sorted alphabetically (except for the first two items).

2. Enter a list of trap numbers by typing the numbers or ranges separated by commas in the Trap No. List field.

   If this field is left blank, then all traps for the selected enterprise are specified.

After you have entered the information, click SELECT on the Add button to add the specified Enterprise names and trap numbers to the trap template file.

4.2.4.3 Changing a Trap Type Entry

If you want to modify one of the entries (rows) in the trap selection template, click SELECT on that row to highlight it. The information for that trap is now highlighted in the Enterprise Name table. From this table, scroll up or down to select a new enterprise name. Also, enter the desired trap numbers in the Trap No. List field then click SELECT on the Change button to enter the changes into the template.

4.2.4.4 Deleting a Trap Type Entry

To delete a trap type in the Trap Selection Template, click SELECT on the trap to be deleted, then click SELECT on the Delete button.

4.2.4.5 Saving the Trap Type File

After you have finished adding new trap type entries, or deleting or modifying existing trap type entries in the Trap Selection Template, click SELECT on the Save button to save your changes to this Trap Selection Template file. You are prompted to enter the name of the Trap Selection Template file. If you are saving changes to an existing trap selection template file, select it from the file list scroll menu, then click SELECT on the Save button, as shown in Figure 4-24.

Figure 4-24

4.2.4.6 Abandoning Changes to the Trap Selection Template

If you want to abandon the changes you have made to the Trap Selection Template and revert to the previously saved version of this template file, click SELECT on the Reset button.

4.3 Configuring Cooperative Consoles for

Internationalization

The default locale for cc_sender is C (C locale). However, whatever locale a particular SNM database is created in, that same locale should be used for the cc_sender. The cc_sender can be instructed to use the locale for particular databases with the following file:

/var/opt/SUNWconn/snm/cc_files/cc_sender.lang

The format of this file is as follows:

<database_name1> <locale_name1> <database_name2> <locale_name2> <database_name3> <locale_name3>

For example, to set the database mydb in Japanese (ja) locale and the database yourdb in C locale, you would configure the cc_sender.lang file as follows:

mydb      ja
yourdb C