| I can't speak for the DEChub 900, but the DECagent 90 V2.0 supports the
following:
--
-- DECagent 90 Trap Definitions
--
-- The following SNMP generic traps are supported by the DECagent 90:
--
-- coldStart(0)
-- warmStart(1)
-- authenticationFailure(4)
--
-- The DECagent 90 also generates the enterpriseSpecific(6) traps defined
-- below.
--
consolePasswordFailure TRAP-TYPE
ENTERPRISE decagent90v1
DESCRIPTION
"There have been three consecutive failures to enter a correct password
when attempting to log into the DECagent 90 console port."
::= 1
nonVolatileRamError TRAP-TYPE
ENTERPRISE decagent90v1
DESCRIPTION
"An error in the non-volatile storage on the DECagent 90 has occurred.
Some configuration information may have been lost."
::= 2
configurationExceeded TRAP-TYPE
ENTERPRISE decagent90v1
DESCRIPTION
"An attempt was made to exceed the maximum configuration supported by
the DECagent 90. The request to create the additional community or to
add the additional module has been rejected."
::= 3
populationChange TRAP-TYPE
ENTERPRISE decagent90v1
VARIABLES { da90CommunityIndex, dh90SlotIndex, dh90SlotObjectID }
DESCRIPTION
"A module has been added or discovered, or has been deleted or
undiscovered. The objects dh90PopulationChange and
dh90PopulationLastChange have been updated to reflect this change.
The community index, slot index, and module object id are included in
the trap PDU."
::= 4
moduleStatusChange TRAP-TYPE
ENTERPRISE decagent90v1
VARIABLES { da90CommunityIndex, dh90SlotIndex, dh90SlotObjectID,
dh90SlotProxyStatus }
DESCRIPTION
"A module has become reachable or unreachable. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id and
proxy status are included in the trap PDU."
::= 5
rptrPortStatusChange TRAP-TYPE
ENTERPRISE decagent90v1
VARIABLES { da90CommunityIndex, dh90SlotIndex, dh90SlotObjectID,
drpt90PortIndex, drpt90PortState }
DESCRIPTION
"The port status has changed on a repeater module. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id, port
index and port state are included in the trap PDU."
::= 6
srvrPortStatusChange TRAP-TYPE
ENTERPRISE decagent90v1
VARIABLES { da90CommunityIndex, dh90SlotIndex, dh90SlotObjectID,
charPortIndex, charPortOperStatus }
DESCRIPTION
"The port status has changed on a terminal server module. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id, port
index and port operational status are included in the trap PDU."
::= 7
brdgPortStatusChange TRAP-TYPE
ENTERPRISE decagent90v1
VARIABLES { da90CommunityIndex, dh90SlotIndex, dh90SlotObjectID,
ifIndex, ifOperStatus }
DESCRIPTION
"The port status has changed on a bridge module. The objects
dh90StatusChange and dh90StatusLastChange have been updated to reflect
this change. The community index, slot index, module object id, port
index and port operational status are included in the trap PDU."
::= 8
|
| I've been asked to produce a document describing just that: all traps
generated by the DEChub 900 and it's line cards. I hope to begin the
document at the end of this week.
The short answer, by the way, is that all modules generate the standard
traps (coldStart, warmStart, linkUp, linkDown, and authFailure) both
when inserted into the DEChub900 and when standalone. In addition,
the concentrator generates "enterprise specific" port traps the repeater
generates some repeaters mib traps, and the bridge generates some bridge
MIB traps. Other traps are planned for the June/July release.
Watch this space for more details.
-Shawn
|
| re .2
Would there be traps related to Power Supply? eg, a Power Supply unit
has failed, a Power Supply unit has been added, a module has been power
off due to insufficient Power Supply, etc...
Faraday
|
| > Would there be traps related to Power Supply? eg, a Power Supply unit
> has failed, a Power Supply unit has been added, a module has been power
> off due to insufficient Power Supply, etc...
No, not for this release. There are no "enterprise-specific" traps supported
in the next release. There are no "module insertion", "module removal",
"power supply insertion", etc., traps supported in the April release.
However, you can poll objects in the chassis mib to determine when modules
and power supplies come and go. Traps augment polling schemes and are not
needed for effective network management.
We hope to have RMON Alarm and Event support in the following release
(June/July?). Our MIBs allow RMON A&E to be used to trap on your first two
examples, but I don't think we have the MIB object(s) to trap when a module
has been powered off due to insufficient power.
Note 580.2 describes some of the capabilities of RMON A&E. (580.2 was
entered when I thought we'd support RMON A&E on the MAM in the April release.
It just didn't work out that way.)
-Shawn
|
| The following table shows which generic (aka "standard") traps are
supported by which DEChub900 MAX modules by the April-94 release:
+-----------------+--------+--------+-------+-------+-------+
| | Bridge | Concen | Rprtr | Srvr | Mgmt |
| Trap Type | 900MX | 900MX | 900TM | 900TM | Agent |
+-----------------+--------+--------+-------+-------+-------|
| ColdStart | x | x | x | x | x |
| WarmStart | | x | | | |
| LinkUp | | x | | x | x |
| LinkDown | | x | | x | x |
| AuthenFailure | x | x | x | x | x |
| EGPNeighbor | | | | | |
+-----------------+--------+--------+-------+-------+-------+
This table shows what traps will be supported by the Summer-94 release:
+-----------------+--------+--------+-------+-------+-------+
| | Bridge | Concen | Rprtr | Srvr | Mgmt |
| Trap Type | 900MX | 900MX | 900TM | 900TM | Agent |
+-----------------+--------+--------+-------+-------+-------|
| ColdStart | x | x | x | x | x |
| WarmStart | | x | | | |
| LinkUp | x | x | x | x | x |
| LinkDown | x | x | x | x | x |
| AuthenFailure | x | x | x | x | x |
| EGPNeighbor | | | | | |
+-----------------+--------+--------+-------+-------+-------+
In addition to the generic traps shown above:
- The DECrepeater900TM (and the "next wave" repeaters) support
the following repeater MIB traps:
o rptrResetEvent - sent when the repeater's state machine
is reset, and
o rptrHealthTrap - sent when the value of rptrOperStatus
changes, or upon completion of a non-disruptive test.
(RFC1516 provides further detail about these traps.)
- The DECconcentrator900MX supports an "Enterprise Specific" port
trap. "Enterprise Specific" traps are non-standard traps.
The port trap conveys information about the change of an FDDI
port's state. For example, a "disconnecting" port causes a
port trap to be sent. Another trap is sent when the port is
"connecting". Other state changes also cause port traps.
The port traps is disabled by default. It may be enabled by
setting the esysFddiPortTrapSwitch. The release notes for the
DECconcentrator900MX provide additional detail.
Also of note:
- Most products don't have the capability of warm-starting.
When reset they re-initialize completely. WarmStart traps
need only be supported if warm-start capability is supported.
- None of the products listed are routers which support the
Exterior Gateway Protocol (EGP). Therefore, none of the
products support the EGP Neighbor Loss trap.
-Shawn
|