5 - Cooperative Consoles Examples

Table 5-1 indicates that by default, the action is to pass all events, SNMP traps and glyph traps. No priorities are set. The DB Template field indicates to forward or drop database traps as specified by the file passall.cct .

Table  5-1 All Events and Traps with no Priority Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
default		all	-	-	-	pass	passall.cct

Table 5-2 indicates that by default, the action is to pass all events, SNMP traps and glyph traps that are of priority medium or high. All low priority events, SNMP traps, and glyph traps are dropped. The DB Template field indicates to forward or drop database traps as specified by the file passall.cct .

Table  5-2 All Events and Traps with Medium Priority Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
default		all	-	med	-	pass	passall.cct

Table 5-3 indicates that by default, the action is to pass all events, SNMP traps and glyph traps that are of priority medium or high. After these events and traps are forwarded, the new priority will be set to high. All low priority events, SNMP traps, and glyph traps are dropped. The DB Template field indicates to forward or drop database traps as specified by the file passall.cct .

Table  5-3 All Events and Traps with Medium/High Priority Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
default		all	-	med	high	pass	passall.cct

Table 5-4 indicates that by default, the action is to pass all events that are of priority medium or high. After these events and traps are forwarded, the new priority will be set to high. All low priority events, SNMP traps, and glyph traps are dropped. The DB Template field indicates to forward or drop database traps as specified by the file passall.cct.

Table  5-4 Events Only with Medium/High Priority Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
default		events	-	med	high	pass	passall.cct

Table 5-5 indicates that by default, the action is to pass all events and SNMP traps listed in the trap selection template file stdtraps.cce with priority medium or high. Convert the priority of these SNMP traps to high. Drop all other SNMP traps. All low priority events and SNMP traps are dropped. The DB Template field indicates to forward or drop database traps as specified by the file passall.cct.

Table  5-5 Events and SNMP Traps with Medium/High Priority Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
default		events, traps	stdtraps.cce	med	high	pass	passall.cct

Table 5-6 indicates to pass all events, SNMP traps and glyph traps that are from host venus. Pass or drop the database traps that are from host venus as specified in DB Template file passall.cct . By default, drop all other events, SNMP traps and glyph traps that are not from venus. Pass or drop all other database traps (that are not from venus) as specified by the DB Template file firewall.cct .

Table  5-6 Hostname With All Events and Traps Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
hostname	venus	all	-	-	-	pass	passall.cct
default	-	-	-	-	-	drop	firewall.cct

Table 5-7 indicates to pass all events, SNMP traps and glyph traps that are from any component of type component.router. Pass or drop the database traps that are from component of type component.router as specified in
DB Template file passall.cct. By default, drop all other events, SNMP traps and glyph traps that are not from element of type component.router . Pass or drop all other database traps (that are not from component.router ) as specified by the DB Template file firewall.cct.

Table  5-7 Component Router Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
component	component.router	all	-	-	-	pass	passall.cct
default	-	-	-	-	-	drop	firewall.cct

Table 5-8 indicates to pass all events, SNMP traps and glyph traps that are from any element in the view or subview of big-cloud. Pass or drop the database traps that are from any element in the view big-cloud or any subviews of it as specified in DB Template file passall.cct . By default, drop all other events, SNMP traps and glyph traps. Pass or drop all other database traps (that are not from big-cloud) as specified by the DB Template file firewall.cct.

Table  5-8 Viewname With all Events and Traps Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
viewname	big-cloud	all	-	-	-	pass	passall.cct
default	-	-	-	-	-	drop	firewall.cct

Table 5-9 indicates to pass all events, SNMP traps and glyph traps that are from any element in view or subview of type campus. Pass or drop the database traps that are from any element in view of type campus or any subviews of it as specified in DB Template file passall.cct . By default, drop all other events, SNMP traps and glyph traps. Pass or drop all other database traps (that are not from campus) as specified by the DB Template file firewall.cct.

Table  5-9 Viewtype With all Events and Traps Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
viewtype	campus	all	-	-	-	pass	passall.cct
default	-	-	-	-	-	drop	firewall.cct

Table 5-10 indicates to drop all events, SNMP traps and glyph traps that are from host venus. Pass or drop the database traps that are from host venus as specified in DB Template file passall.cct . By default, pass all other events, SNMP traps and glyph traps. Pass or drop all other database traps (that are not from venus) as specified by the DB Template file firewall.cct.

Table  5-10 Hostname Drop all Events and Traps Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
hostname	venus	all	-	-	-	drop	passall.cct
default	-	-	-	-	-	pass	firewall.cct

Table 5-11 indicates to pass all events, SNMP traps and glyph traps that are from the host venus. Pass or drop the database traps that are from host venus as specified in DB Template file passall.cct . Also, pass all events, SNMP traps and glyph traps that are from the host splendid. Pass or drop the database traps that are from host splendid as specified in DB Template file maypass.cct. By default, drop all other events, SNMP traps and glyph traps. Pass or drop all other database traps (in this case, that are neither from venus nor splendid) depending on the DB Template file firewall.cct .

In this case, when an event, SNMP trap, glyph trap or database trap is received by the CC Sender program, it is checked to see whether or not it satisfies the criteria mentioned for hostname venus . If the criteria is satisfied, then the pass action will be performed. If not, the criteria for hostname splendid is checked. If this criteria is met, then the action pass will be performed. Otherwise, the action drop mentioned for the default case will be performed.

Table  5-11 Multiple Hostnames with All Events and Traps Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
hostname	venus	all	-	-	-	pass	passall.cct
hostname	splendid	all	-	-	-	pass	maypass.cct
default	-	-	-	-	-	drop	firewall.cct

Table 5-12 indicates to pass all events, SNMP traps and glyph traps that are from the host splendid. Pass or drop the database traps that are from host splendid as specified in DB Template file maypass.cct . Also, pass all SNMP traps that are from the view or subview of eternal . Pass or drop the database traps that are from view eternal or its subviews as specified in DB Template file passnone.cct. By default, drop all other events, SNMP traps and glyph traps. Pass or drop all other database traps depending on the DB Template file firewall.cct .

Since only SNMP traps are passed from the view eternal , the events and glyph traps that come from the view eternal will satisfy the third line for default and will be dropped.

Interchanging lines 1 and 2 in this filter file will have no effect on the outcome of the filter process. The reason is that the filtering mechanism follows a predefined set of precedences. The precedence will be given on the value of the type field. The lines with type hostname will take the highest precedence and the line with default will be given the least. The following list indicates the decreasing order of precedence.

• Hostname
• Component
• View Name
• View Type
• Default

One of the special cases is when the same event/trap is capable of satisfying more than one filter lines. For example, consider the following filter file in Table 5-13 .

Assume that host splendid appears in the view or subview eternal. If an SNMP trap comes from host splendid , then according to the first line, it should be passed. But according to the second line, it should be dropped. In that case, the `first come first served' rule is adopted. Since the condition for host splendid is met first, (even if the lines are interchanged) the SNMP trap will be forwarded.

Table  5-13 Hostname and Viewname (Drop) Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
hostname	splendid	all	-	-	-	pass	maypass.cct
viewname	eternal	traps	-	-	-	drop	passnone.cct
default	-	-	-	-	-	drop	firewall.cct

One can specify multiple filter lines for the same host, view or component. For example, consider the following filter file in Table 5-14 .

The filtering process will undergo the following steps. All the Database traps that are coming from host nethound will be forwarded or dropped as specified in the database template file maypass.cct . As a result of the first filter line, all the events and glyph traps from the host nethound will be dropped.

As a result of the second filter line, all the SNMP traps that are specified in the trap selection template stdtraps.cce and that are from the host nethound will be dropped. The SNMP Traps from host nethound that are not mentioned in stdtraps.cce will be considered for subsequent filtering.

As a result of the third filter line, all the SNMP traps that are specified in the trap selection template suntraps.cce and that are from the host nethound will be forwarded. The SNMP traps from host nethound that are not mentioned in suntraps.cce (as well as stdtraps.cce) will be considered for subsequent filtering.

As a result of the fourth filter line, all the SNMP traps that are specified in the trap selection template enterprise.cce and that are from the host nethound will be dropped. The SNMP Traps from host nethound that are not mentioned in enterprise.cce (as well as stdtraps.cce and suntraps.cce) will be processed by the fifth filter line for the default case. In addition, all the events, glyph traps and SNMP traps from all other elements will be processed by the fifth filter line.

As a result of the last filter line, the SNMP traps that are mentioned in the file enterprise.cce will be forwarded. The events and glyph traps will be forwarded. All the database traps will be forwarded or dropped per DB Template file firewall.cct.

Table  5-14 Same Hostname Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
hostname	nethound	events,glyphs	-	-	-	pass	maypass.cct
hostname	nethound	traps	stdtraps.cce	-	-	drop	maypass.cct
hostname	nethound	traps	suntraps.cce	-	-	pass	maypass.cct
hostname	nethound	traps	enterprise.cce	-	-	drop	maypass.cct
default	-	glyphs,traps	enterprise.cce	-	-	pass	firewall.cct

Table 5-15 indicates to pass all events and glyph traps that are from any component of type component.router. Pass the SNMP traps that are specified in the the trap selection template stdcisco.cce. Pass or drop the database traps that are from component of type component.router as specified in DB Template file passall.cct. By default, drop all other events, SNMP traps and glyph traps that are not from element of type component.router. Pass or drop all other database traps depending on the DB Template file firewall.cct.

Table  5-15 Component Trap Template Example

Type	Name	Events/Traps	Trap Template	Priority	New Priority	Action	DB Template
component	component.router	all	stdcisco.cce	-	-	pass	passall.cct
default	-	-	-	-	-	drop	firewall.cct

Copyright 1996 Sun Microsystems, Inc., 2550 Garcia Ave., Mtn. View, CA 94043-1100 USA. All Rights Reserved