UNSOLVED

Mithrilhall

updated

20 years ago

M

Mithrilhall

2 Intern

128 Posts

0

14682

April 28th, 2006 11:00

SNMP (Determine type of switches in stack)

I'm trying to determine the type of switches in my stack via SNMP.

I've looked at the sysObjectID but the only thing that turns up is 'dellLan.3003'.


Any suggestions?

Message Edited by Mithrilhall on 04-28-200609:38 AM

  • Mithrilhall

    2 Intern

    128 Posts

    248

    0

    Posted April 28th, 2006 14:00

    Cuong...

    This is what I'm trying to do.

    I have a stack of 2 switches (1 3348 & 1 3324).

    I want to determine what type of switches make up the stack. The sysObjectID only shows the first switch of the stack. Is there a way to determine what type the other switches in the stack are?
  • DELL-Cuong N.

    1017 Posts

    248

    0

    Posted April 28th, 2006 14:00

    I answered this before here:

    http://forums.us.dell.com/supportforums/board/message?board.id=pc_managed&message.id=5476&query.id=0#M5476

    Perhaps you are having some other issue?  The 3003 at the end indicates that it is a 3348.

    Cuong.

  • DELL-Cuong N.

    1017 Posts

    248

    0

    Posted April 28th, 2006 19:00

    Try look at the rlPhysDescription.mib file.  Look at the rlPhdModuleTable.  There is a field in there call rlPhdModuleType.  It returns the type of chipset used for the unit.  The translation for the 34xx switches are as follows:

    • 3424 = gemstone 24F+4G (42)
    • 3448 = gemstone 48F+4G (43)
    • 3424P = gemstone 24F+4G with PoE (47)
    • 3448P = gemstone 48F+4G with PoE (48)

    Cuong.

  • Mithrilhall

    2 Intern

    128 Posts

    248

    0

    Posted April 28th, 2006 20:00

    Thank you....I'll take a look at that.
  • mljames

    4 Posts

    248

    0

    Posted July 17th, 2007 15:00

    Do you have similar values for the PowerConnect 5300 series (or any other PowerConnects)?  Is this still the best field to use for 5300 series switches in order to determine which switches are included in the stack?
     
    Thanks,
    Matt