shaffer@hamlet.ctd.anl.gov (04/12/91)
Does anyone know if the enterprise specific traps for cisco products are documented anywhere (that is where users can get at it)? We have both routers and terminal servers here and I am building a system that will need to be able to interpret these traps. In the mean time what does an enterprise:1 trap from a terminal server mean? mike shaffer@achilles.ctd.anl.gov Argonne National Labs Argonne IL 708-972-8181
snyder@cisco.com (Robert Snyder) (04/12/91)
>>Does anyone know if the enterprise specific traps for cisco products are >>documented anywhere (that is where users can get at it)? Well they will be documented in the new version of mib.txt when it appears. I will send mail to this list when that is a reality. In the mean time there are only 2 enterprise specific traps 0 == reload command 1 == a tcp connection close Robert cisco
thille@cisco.com (Nick Thille) (04/13/91)
Hi,
Yes, we know what the traps are, and we plan to document them in an
upcoming MIB.TXT document available from ftp.cisco.com. Exactly when this
will be finished, I don't know.
For now, the cisco enterprize specific traps are:
trap #0: SNMP RELOAD. This trap is triggered when the router is reloaded via
the reload command. It is not triggered when the router is
reloaded due to a power interruption or other cause.
trap #1: SNMP TTY. This trap is triggered when a TCP connection is closed.
These are the two cisco specific traps currently implemented.
I hope this helps.
Regards,
Nick Thille
Customer Engineer
cisco Systemsthille@cisco.com (Nick Thille) (04/13/91)
Yes, Andrew, you're right. There are many more than 2 traps defined. However, there are only 2 cisco Enterprise Specific Traps, the two that I explained in the previous message: reload, and TCP connection close. All of your other traps are not specific to cisco. Regards, -Nick