T.R | Title | User | Personal Name | Date | Lines |
---|
1570.1 | Here's everything... | SLINK::HOOD | I'd rather be at the Penobscot | Thu Oct 13 1994 13:53 | 70 |
| Info available on the DECbridge 900MX / DECswitch 900EF / PEswitch 900TX FDDI
port from HUBwatch:
(a) From the bridge/switch port window (HUBwatch V3.1):
switch/bridge info:
sysDescr
sysName
dot1dStpTimeSinceTopologyChange
dot1dStpRootPort
ebrCurrNVForwardingDBEntries
ebrCurrNVProtocolDBEntries
esysPowerups
esysMgmtResets
esysUnsolicitedResets
interface info:
ifType
ifPhysAddress
ifLastChange
ifInOctets
ifInUcastPkts
ifInNUcastPkts
ifInDiscards
ifInErrors
ifOutOctets
ifOutUcastPkts
ifOutNUcastPkts
ifOutDiscards
ifOutErrors
dot1dBasePortDelayExceededDiscards
dot1dStpPortState
dot1dStpPortDesignatedBridge
dot1dStpPortDesignatedPort
dot1dStpPortForwardTransitions
ebrRateLimitAddressFrames
ebrRateLimitProtocolFrames
ebrIfPortRestarts
ebrIfUnknownDAReceived
ebrIfBadHelloLimitExceeded
ebrPEAddressActives [PEswitch only]
ebrPEAddressDiscards [PEswitch only]
FDDI ports only:
eMACFrameAlignmentErrors
eifBadFramesReceived
ebrIfFddiIpDatagramsFragmented
ebrIfFddiIpDontFragment
Ethernet ports only:
dot3StatsAlignmentErrors
dot3StatsFCSErrors
dot3StatsSingleCollisionFrames
dot3StatsMultipleCollisionFrames
dot3StatsDeferredTransmissions
dot3StatsExcessiveCollisions
dot3StatsCarrierSenseErrors
(b) From the bridge/switch summary window:
ifType
ifPhysAddress
ifDescr
dot1dStpPortState
dot1dStpPortEnable
dot1dStpPortPathCost
ifOperStatus
ebrIfEthPhysicalMediumType (Ethernet ports only)
ePORTPMDType (FDDI ports only)
dot1dTpPortInFrames (HUBwatch calculates frames/second)
dot1dTpPortOutFrames (HUBwatch calculates frames/second)
dot1dTpPortInDiscards (HUBwatch displays percent discards)
|
1570.2 | Thanks for the quick response | STROP::LAYLAND | The good die young, the wealthy stay healthy. | Fri Oct 14 1994 05:25 | 0 |
1570.3 | ...and WANrouter and DECbrouter 90's, too. | SLINK::HOOD | I'd rather be at the Penobscot | Fri Oct 14 1994 11:24 | 44 |
| Hmmm, I only gave the bridge/switch info in .1
HUBwatch does not support the WANrouter 90's (other than front panel).
They support only MIB-II GET's.
For the DECbrouter 90's, the following are used by HUBwatch:
Module info:
sysName snmpInPkts snmpInTooBigs
sysLocation snmpOutPkts snmpInNoSuchNames
sysContact snmpInGetRequests snmpInBadValues
sysDescr snmpInGetNexts snmpInReadOnlys
sysUpTime snmpInSetRequests snmpInGenErrs
ifNumber snmpOutTraps snmpOutTooBigs
bufferElFree snmpInBadVersions snmpOutNoSuchNames
bufferElMiss snmpInBadCommunityNames snmpOutBadValues
bufferElHit snmpInBadCommunityUses snmpOutReadOnlys
freeMem snmpInASNParseErrors snmpOutGenErrs
avgBusy5 snmpInBadTypes
Port info:
ifOperStatus locIfInPktsSec
ifAdminStatus locIfOutPktsSec
ifDescr ifPhysAddress [Ethernet port only]
locIfDescr ifInErrors
ifType ifOutErrors
For the following protocols, in and out packets, and
in and out octets per port:
Apollo MOP
Appletalk Novell
ARP PUP
bridge stp (bridging)
chaosnet srb
CLNS stun
DECnet vines
IP xns
For the DECbrouters, if a variable isn't MIB-II, it's from the Cisco
MIB extensions.
- Tom Hood
HUBwatch
|
1570.4 | MIB variables for polling bridge ports | NETCAD::SLAWRENCE | | Mon Oct 17 1994 11:21 | 8 |
|
All the 900 series switches support MIB-II and the IETF Bridge MIB (rfc
1493). You can poll ifOperStatus - another one to look at is
dot1dStpPortState, which will tell you the state of the spanning tree
on each port.
For the FDDI port, I also poll fddimibPORTConnectState.
|