Re: [tkined] Monitoring a 3Com SuperStack II 3300 switch

From: oliver hemming (Oliver.Hemming@jet.uk)
Date: Wed Feb 02 2000 - 11:05:03 MET


George Ross wrote:
>
> > I'm new to SNMP MIB network monitoring. I know that, to monitor a
> > particular hardware, I must download the specific mib-file. For example
> > to monitor a "3Com SuperStack II 3300 switch" I must take its specific
> > mib, but I don't know what's the specific mib-file (and what's the
> > variables that can be monitored). I've gone to
> > ftp://ftp.3com.com/PUB/mibs/ but there is a very large set of mibs
> > and... the readme files don't explain very well.
>
> Indeed! The only thing I've found on 3com's site that's been of any
> use in monitoring 3300s is the vlan mib from the 9300 collection.
> There's clearly a lot of other stuff accessible under "enterprises",
> but so far I've not found how to decode it. If anyone has any pointers
> I would be interested in hearing too.

Over the years we have picked up the following mib files for Lanplex,
Linkswitch and Superstack II:
 3com0004.mib 3com0014.mib 3com0023.mib 3com0027.mib 3com0049.mib
 3com0007.mib 3com0017.mib 3com0024.mib 3com0028.mib
 3com0008.mib 3com0019.mib 3com0025.mib 3com0029.mib
 3com0012.mib 3com0021.mib 3com0026.mib 3com0045.mib

File 3com0004.mib gives the following generic definitions, and we have
commented the use of the
other files that we know of:

> A3COM0004-GENERIC DEFINITIONS ::= BEGIN
>
> IMPORTS
> generic FROM A3COM-PRODUCTS-MIB
> OBJECT-TYPE FROM RFC-1212
> ;
>
> -- *** SNMP-REPEATER-MIB
> -- *** see also <<< A3COM0023-RPTR-EXTENSIONS >>>
> -- *** 3COM-MIBS
> -- *** SUPERSTACK-II UNIT TYPE DEFINITIONS
> -- *** see <<< A3COM0025-STACK-UNIT-TYPES >>>
>
> setup OBJECT IDENTIFIER ::= {generic 2}
> sysLoader OBJECT IDENTIFIER ::= {generic 3}
> -- *** see <<< A3COM0007-SYSLOADER >>>
>
> security OBJECT IDENTIFIER ::= {generic 4}
> -- *** see <<< A3COM0008-SECURITY >>>
>
> gauges OBJECT IDENTIFIER ::= {generic 5}
> asciiAgent OBJECT IDENTIFIER ::= {generic 6}
> serialIf OBJECT IDENTIFIER ::= {generic 7}
> repeaterMgmt OBJECT IDENTIFIER ::= {generic 8}
> endStation OBJECT IDENTIFIER ::= {generic 9}
> localSnmp OBJECT IDENTIFIER ::= {generic 10}
> -- *** see <<< A3COM0012-TRAPTABLE2 >>> (upgrade!!!)
>
> manager OBJECT IDENTIFIER ::= {generic 11}
> unusedGeneric12 OBJECT IDENTIFIER ::= {generic 12}
> chassis OBJECT IDENTIFIER ::= {generic 14}
> mrmResilience OBJECT IDENTIFIER ::= {generic 15}
> -- *** see <<< A3COM0014-RESILIENTLINKS >>>
>
> tokenRing OBJECT IDENTIFIER ::= {generic 16}
> multiRepeater OBJECT IDENTIFIER ::= {generic 17}
> bridgeMgmt OBJECT IDENTIFIER ::= {generic 18}
> fault OBJECT IDENTIFIER ::= {generic 19}
> poll OBJECT IDENTIFIER ::= {generic 20}
> powerSupply OBJECT IDENTIFIER ::= {generic 21}
> securePort OBJECT IDENTIFIER ::= {generic 22}
> -- *** see <<< A3COM0021-PORT-SECURITY >>>
>
> alertLed OBJECT IDENTIFIER ::= {generic 23}
> remoteControl OBJECT IDENTIFIER ::= {generic 24}
> rmonExtensions OBJECT IDENTIFIER ::= {generic 25}
> -- *** see <<< A3COM0019-RMON-REMOTE-POLL >>>
> -- *** and <<< A3COM0024-EVENT-EXTENSION >>>
> -- *** and <<< A3COM0027-RMON-EXTENSIONS >>>
> -- *** and <<< A3COM0028-ALARM-PEAK >>>
> -- *** and <<< A3COM0029-HOST-LOCATION >>>
>
> rfc1516extensions OBJECT IDENTIFIER ::= {generic 26}
> superStackIIconfig OBJECT IDENTIFIER ::= {generic 27}
> -- *** see <<< A3COM0017-STACK-CONFIG >>>
>
> extendedIfInfo OBJECT IDENTIFIER ::= {generic 28}
> -- *** see <<< A3COM0026-IF-EXTENSIONS >>>
>
> a3ComVlan OBJECT IDENTIFIER ::= {generic 29}
> vlanServerClient OBJECT IDENTIFIER ::= {generic 30}
> segmentLoadBalancing OBJECT IDENTIFIER ::= {generic 31}
> virtualFileSystem OBJECT IDENTIFIER ::= {generic 32}
> autosensingCableQuality OBJECT IDENTIFIER ::= {generic 33}
> brasica2 OBJECT IDENTIFIER ::= {generic 34}

Let me know if you need any of these: I don't think there is any problem
with passing them around.

> What I do have is a fairly rudimentary 1100/3300/3300XM monitoring and
> configuration tool, using expect to change things and Tnm 3.0 (99.08.12
> snapshot) to query the devices' states. It needs tidied up a little,
> and there's minimal documentation, but if you're interested I could
> make it available.

I would also be interested to see this.
One thing I have always wanted to do is set up Port Mirroring (Roving
Analysis Port) via SNMP, but I've never managed to find out how to do
it. Fortunately the CLI is now much better in version 2.30, and allows
to do most things.

> Dr George D M Ross, Division of Informatics, University of Edinburgh
> Kings Buildings, Mayfield Road, Edinburgh, Scotland, EH9 3JZ
> Mail: gdmr@dcs.ed.ac.uk Voice: +44 131 650 5147 Fax: +44 131 667 7209
> PGP: 1024/B74A4F7D 14 E8 B3 00 20 04 68 F8 95 40 CB 36 A4 D4 FA 90
>

Regards
Oliver

-- 
+-----------------------------------------------------------+ 
| Oliver Hemming                                            |
| UKAEA Fusion                E-mail: Oliver.Hemming@jet.uk |
| Culham Science Centre       Voice: (++44)1235 46-4437     |
| Abingdon, Oxon.             Fax:   (++44)1235 46-4404     |
| OX14 3EA                                                  |
| UnitedKingdom.                                            |
+-----------------------------------------------------------+
--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.



This archive was generated by hypermail 2b29 : Mon Jan 08 2001 - 15:27:33 MET