Header Only - DO NOT REMOVE - Extreme Networks

EXOS hardware detection, wrong sysObjectID for X690, X770, X870 or any switch in stack


Hello all,

As commented in other posts, the correct way to get the hardware type of an EXOS device using snmp, is with sysObjectID.

Doing that for X690, X770, X870, it always return:

:~$ snmpget -v2c -c public sparex690 1.3.6.1.2.1.1.2.0
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.1916.2.93
SNMPv2-MIB::sysObjectID.0 = OID: EXTREME-BASE-MIB::summitVer2Stack[/code]
Looking the MIBs definitions it said (ExtremeXOS-22.4.1.4-MIB):

summitVer2Stack OBJECT IDENTIFIER ::= { extremeProduct 93 }
-- A stacked version of the EXOS Summit X450's, X250's[/code]
But non of the requested device are X450 nor X250.

If I do the same snmp request to another device:

:~$ snmpget -v2c -c public sparebd8806 1.3.6.1.2.1.1.2.0
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.1916.2.74
SNMPv2-MIB::sysObjectID.0 = OID: EXTREME-BASE-MIB::bd8806[/code]
It returns correctly the product as stated in the MIB:

bd8806 OBJECT IDENTIFIER ::= { extremeProduct 74 }
-- Black Diamond 8800 6 slot chassis[/code]
The MIB has the definition product for X690, X770, X870:

.1.3.6.1.4.1.1916.2.194 = Summit X770-32q
.1.3.6.1.4.1.1916.2.237(238) = Summit X870-32C
.1.3.6.1.4.1.1916.2.247(248) = X690[/code]
So, the questions,
1. Why is returning the wrong sysObjectID?
2. Is it because the devices have the stacking enabled? If is because of that, then;
3. How correctly get the Extreme Product using stacking?

Thanks.

3 replies

Hi

I also found this problem
Userlevel 5
On a standalone switch the SysObjectId will respond with the individual product ID but as soon it is a stack it will respond with “1.3.6.1.4.1.1916.2.93” meaning that this is a EXOS summit stack.

As a stack can consist of multiple platforms that is what you get from the stack master. The only problem is that the MIB definition is created at the time there were only stacks of X450 and/or X250

The actual stack members are visible through another OID:

1.3.6.1.4.1.1916.1.33.2.1.2 (extremeStackMemberType)

The switch is doing what it supposed to do, It say “this is a stack” and then you need to examine the stack members to see what types they are.

Whatever combination of EXOS units you have in your stack the result will always “1.3.6.1.4.1.1916.2.93” (summitVer2Stack)
Ron Huygens wrote:

On a standalone switch the SysObjectId will respond with the individual product ID but as soon it is a stack it will respond with “1.3.6.1.4.1.1916.2.93” meaning that this is a EXOS summit stack.

As a stack can consist of multiple platforms that is what you get from the stack master. The only problem is that the MIB definition is created at the time there were only stacks of X450 and/or X250

The actual stack members are visible through another OID:

1.3.6.1.4.1.1916.1.33.2.1.2 (extremeStackMemberType)

The switch is doing what it supposed to do, It say “this is a stack” and then you need to examine the stack members to see what types they are.

Whatever combination of EXOS units you have in your stack the result will always “1.3.6.1.4.1.1916.2.93” (summitVer2Stack)

Hello Ron, thank you very much for the reply.

That explains everything.

Reply