Re: Trap customization question

I don't think you understand this process.  It is not NetView which
determines how the trap is sent, only how it is displayed.  Obviously, the
combination of enterprise id and generic and specific trap id is unique,
and can have only one definition.  Cisco will have to tll you what it will
send and then you can change trapd.conf accordingly.  But we do not know
what the agent will do.  Clearly one of the traps you are trying to define
is a mistake.  Which one?  Only Cisco can tell you.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Adriana Gomes <agomes AT VE.IBM DOT COM> on 09/30/98 11:19:55 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView et alia <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  Re: Trap customization question





To:   nv-l AT ucsbvm.ucsb DOT edu
cc:

From:




Hello again!

As you recommend me, due to create specific events for Cisco Catalyst 1924
switches when NetView is receiving specific traps, I created a script file,
which contain addtrap commands for adding all these traps. Although, there
is a conflict between newRoot specific trap number (1) and switch
Diagnostic specific trap number (1), because they are originally from
different enterprise trap groups (newRoot came from Bridge trap
definitions, and switchDiagnostic came from series2000 trap definitions).
Then, NetView doesn't let me add the source trap nodes from map in
switchDiagnostic, and shows the follow error message:

"Trying to modify to use a source already defined by event format
newRoot_1924"

Can I modify the switchDiagnostic specific trap number for another, like 6,
for example, without avoid the recognition from NetView if the agent send
to NetView a switch Diagnostic trap?. How can I solve this error without
affecting getting and recognition all traps I want to get from Cisco
Catalyst 1924 switches?

The traps defined in the new enterprise trap group I created, called
Catalyst_1924 (1.3.6.1.4.1.24), is shown as follow:

coldStart_1924        Cold Start  Cleared  Default 34.3.171.250 ...
warmStart_1924        Warm Start  Cleared  Default 34.3.171.250 ...
LinkDown_1924         Link Down   Major    Default 34.3.171.250 ...
LinkUp_1924           Link Up     Cleared  Default 34.3.171.250 ...
logonIntruder_1924    Specific 0  Critical Default 34.3.171.250 ...
newRoot_1924          Specific 1  Critical Default 34.3.171.250 ...
switchDiagnostic_1924 Specific 1  Critical Default   topologyChange_1924
Specific 2  Minor    Default 34.3.171.250 ...
addressViolation_1924 Specific 3  Critical Default 34.3.171.250 ...
broadcastStorm_1924   Specific 4  Critical Default 34.3.171.250 ...
rpsFailed_1924        Specific 5  Major    Default 34.3.171.250 ...

Thanks in advance,

Adriana Gomes N.
Phone: (582) 9088615.   Tie-line: 777-8615
Address: Av. Ernesto Blohm, Ed. IBM. Chuao. Caracas, Venezuela.
e-mail: agomes AT ve.ibm DOT com