|
Andrew,
most of the answers to your questions are in the installation manual and the
firmware release notes.
Look at the variable esysFddiPortTrapSwitch in the ELAN_vendor_mib_v30 (or V29)
You setup traps using the module specific option in the setup port.
Shawn will correct me if I am wrong 8-)
Manuel.
Traps supported
----------------
Generic Trap 0 1 2 3 4 5 6
DECconcen900MX/TH Y N Y Y Y N Y (3)
(3) The DECconcentrator900 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".
The port traps is disabled by default. It may be enabled by
the setup port module specific options (enable/disable SNMP Port Traps)
Or by using an NMS to set esysFddiPortTrapSwitch.
The installation and Configuration Manual describes also the traps
supported.
- From V3.2 release notes:
-------------------------
The DECconcentrator 900MX module supports the following MIBs and RFCs:
o Built-in SNMP agent supports the following management information
bases (MIBs):
- MIB II, RFC 1213
- FDDI MIB, RFC 1512
- Digital Extended MIB V3.0
- PCOM MIB, June 1995
o Support for SMT 7.3 Station Management (X3.229-1994)
o Port State Trap Not Saved If Set Via the Setup Port
In firmware version V3.1, if port traps were enabled via the setup port,
their state was not saved in non-volatile random access memory (NVRAM).
Therefore, if a DECconcentrator MX were reset,
port traps were reset to the default state of disabled. However, if port
traps were enabled via an network management station (NMS) by setting the
Vendor management information base (MIB) object
esysFDDIPortTrapSwitch, the new state was stored in NVRAM and retained
across resets.
In firmware version V3.2, the port trap state is retained in NVRAM when
it is set via the setup port or from an NMS.
|
|
> I browse
> the dec_elan_vendor_mib_v30 mib from digital ftp server, it seems there
> is nothing about enterprise specific traps sent from DC900MX).
A TRAP-TYPE definition will be put into the next version of the ELAN
MIB describing this trap. The definition will look a lot like this:
portTrap TRAP-TYPE
ENTERPRISE <oid of the concentrator>
VARIABLES { fddimibPORTConnectState }
DESCRIPTION
"Indicates that a concentrator port underwent a state change."
::= 1
> Secondly, will DC900MX send out trap when M-port become standny or
> switch from standby to active when connecting to dual-home DAS FDDI
> device?
I dunno. Does the port state change when this happens? If it does,
then yes, a trap will be sent.
>What is the lates FDDI mib supported by DC900MX?
rfc1512.
Sorry for the delay,
-Shawn
|