The size of the trap will depend upon whose it is. Some vendors send variables,
some don't.
One way you can tell the size of the trap is to turn on the "hex dump of all
packets" for trapd (so that he runs with the -x option) and then toggle the
trace on at the command line by issuing trapd -T . This causes a hex dump of
each trap to be written to
the trapd.trace file and you can match that with trapd.log to find whatever trap
you are looking for. Note, however that this gives you the raw trap size, not
the size of the netwrok packet with all its headers, as well. To get that you
would need a sniffer or an iptrace, but those are harder to decipher into which
is the trap you are looking for.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Leslie Clark <lclark@US.IBM.COM> on 12/01/99 07:30:26 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: Size of Authentication Failure trap
I don't know, Niko, but probably someone on the listserver does.. Anybody?
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Hello,
I'd like to know how big is the trap (in terms of bytes) of
"authetication
failure" send by router to NetView. Do you have made any calculation in
order
to find this number ?.
Thanks a lot.
Best Regards,
Niko Kaniadakis
|