| > SNMP TRAP : vendor specific from 19.59.48.20
> enterprise : [1.3.6.1.4.1.36.2.15.5.4.1]
> specific : [1]
> varbind 1: 1.3.6.1.2.1.10.15.73.5.2.1.20.1.4 = 4
Not a dumb question at all.....as you'll soon see ;-)
Briefly, this is a DECconcentrator "port" trap. It indicates that port 4's
connect state is now 'active. (A station just attached to port 4.)
You can expect a similar trap when the connect state changes.
In gory detail... The "enterprise" is the sysObjectID for the
DECconcentrator900MX. "specific" indicates the enterprise specific
trap number which, in this case, is "1". (There is only one enterprise
specific trap for the DECconcentrator900MX.)
The var-bind is the object identifier for fddimibPORTConnectState.
That's:
<blah>.fddi(15).fddimib(73).fddimibPORT(5).fddimibPORTTable(2).
fddimibPORTEntry(1).fddimibPORTConnectState(20)
with an instance (index) of fddimibPORTSMTIndex(1) and fddimibPORTIndex(4).
The fddimibPORTIndex of 4 is what indicates that the trap concerns port 4.
The value of 4 indicates that the connect state is now active, as shown
below (from the FDDI MIB, aka rfc1512).
> fddimibPORTConnectState OBJECT-TYPE
> SYNTAX INTEGER {
> disabled(1),
> connecting(2),
> standby(3),
> active(4)
> }
> ACCESS read-only
> STATUS mandatory
> DESCRIPTION
> "An indication of the connect state of this PORT
> and is equal to the value of Connect_State (refer
> to ANSI 9.4.1)"
> REFERENCE
> "ANSI { fddiPORT 61 }"
> ::= { fddimibPORTEntry 20 }
These traps have to be enabled. I don't recall what vendor MIB object is used
to enable/disable this trap. If you're interested, let me know and I'll look
it up.
And I don't recall where this is documented. If you're interested, let me
know and I'll look it up.
-Shawn
|
|
for receiving and decoding traps , you need
an SNMP manager like :
- Manageworks/SNMP for PC/windows environment : 1 K$
- Polycenter Netview for Alpha UNIX : 20 K $
Hubwatch integrates well in both softwares , so
either with Manageworks or Netview ,
you will have a map of the IP network ,
be able to distinguish dechubs with appropriate icons ,
received traps from dechubs ,
poll dechubs modules ,
launch hubwatch per dechub icon
as basic functions
what you really need is more memory that cpu for each
platform ( PC or Alpha ) : 16 M for manageworks , 128 M for Netview
|