| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Since the DECmcc SNMP AM V1.2 is going to support 6 types of traps.
How many kind of trap messages (and what are they) can our FDDI concentrator
and Bridges sent out.
Will they be able to sent all 6 types of traps?
Is there some online document somewhere which describes all types of traps
that can be generated?
Also posted in MOUSE::FDDI
Raj
ACT Singapore
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1411.1 | Some answers... | ALLZS::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Wed Aug 28 1991 11:54 | 33 |
> How many kind of trap messages (and what are they) can our FDDI concentrator > and Bridges sent out. > > Will they be able to sent all 6 types of traps? I'll defer on this question to the people writing the SNMP Agents for the DECbridge 5xx/6xx and DECconcentrator 5xx (I have forwarded the baase note to people in the LANBU who should be able to supply the details). > Is there some online document somewhere which describes all types of traps > that can be generated? The six generic traps are well known (and well documented) elsewhere in this conference. You might want to take a look at: The Simple Book An Introduction to MANAGEMENT of TCP/IP - based internets by Marshall T. Rose Pages 156-158 have a nice description of Traps in general. Note that there are generic traps (which TCP/IP SNMP AM V1.2 will be supporting) and enterpriseSpecific traps (which will most likely not be in V1.2). Each vendor invents their own enterpriseSpecific Traps, which are documented in their Enterprise Specific MIB definition(s). Hope this helps... Chris | |||||
| 1411.2 | some of them | QUIVER::GALLAGHER | Wed Aug 28 1991 12:41 | 35 | |
Trap Current Next Current Next
Concentrator Concentrator Bridge Bridge
-------------------------------------------------------------------
coldStart Yes Yes Yes Yes
warmStart No No No No
linkDown No No No Yes
linkUp Yes Yes No Yes
authenFailure No Yes No Yes
egp No No No No
enterprise No No No Probably
The current release of the fddi bridge and concentrator generate coldStart
traps. The concentrator also generates LinkUp traps.
They don't generate WarmStart because the they don't partially initialize.
(When they initialize, everything is initialized. The volatile MIB objects
[like counters] are all zeroed.)
The concentrator doesn't generate linkDown because it only has one MAC
(kind of like having one link). Sending a linkDown trap on a link that
is down is pretty pointless. (Although some have suggested that we claim
to send linkDown traps that just don't make it to the wire ;-)
egpNeighborLoss trap aren't sent because neither product implement EGPs.
(Neither is a gateways.)
In the next release of the concentrator, authenticationFailure traps will
be sent. (The next release enters field test 30-Aug.)
The next release of the bridge will also implement authenticationFailure
traps. linkDown traps will be flooded to all other ports which are up.
Additional enterpriseSpecific traps may be generated because of bridge mib
events. (The next release is 3-6 months out.)
-Shawn
| |||||