I cannot answer your specific question about 2210 system levels and the traps
they send.
However, addtrap will not replace nor update an existing trap in your
trapd.conf. So if you already have an old definition for the same enterprise id
and specific trap id, it will not be changed. All you will be doing is adding
the new, additional definitions. If you want add tap to replace your old ones
you would have to use xnmtrap to delete them first.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Juan Echevarria <echevarria@ES.IBM.COM> on 09/20/99 03:24:46 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: addtraps.2210 script
Hi all,
some time ago I run a script to add Cisco traps to my NetView. Last week I
found some scripts in IBM Networking web pages called addtraps.2210. Those
scripts define the 2210 traps in NetView systems. My question is: there are
different scripts depending on MRS version (v3.1, v3.2 and v3.3): are any kind
of incompatibility between them? My managed network has different MRS code
levels starting in MRS2.2 (for which I didn't find a addtraps script). Has
anybody tried this? Do you think it can harm my traps definition file to execute
the addtraps.2210 script for the higher level?
Thanks, Juan.
Juan Echevarr
ía López
AT&T Global Network Services
|