topic Re: ICX 7250 OIDS in ICX Switches

ICX 7250 OIDS

Assiamour_ — Fri, 24 May 2024 19:17:31 GMT

Hello, I'm trying to monitor my switch's CPU load, memory util, and temperature through a third party network monitoring tool (PRTG). I have been looking everywhere for the snmp OIDs to do so but can't find them anywhere. My switch's version is 08.0.95mT211.

Re: ICX 7250 OIDS

Chandini — Mon, 27 May 2024 10:35:26 GMT

Hi Assiamour_

Thank you for reaching us

You can refer the below link for the OID's you are looking for.

Thanks

Re: ICX 7250 OIDS

nolanm — Mon, 27 May 2024 11:37:41 GMT

I've tried those and they do not work. The MIB doesn't have the OID's for the cpu load or memory util and the OID's from your post return an error when trying to set up sensors through PRTG.

Re: ICX 7250 OIDS

inphobia — Tue, 28 May 2024 04:33:18 GMT

not running 8.x but

FOUNDRY-SN-AGENT-MIB::snAgImgVer.0 = STRING: "10.0.10cT233"
FOUNDRY-SN-AGENT-MIB::snAgFlashImgVer.0 = STRING: "10.0.10cT233"

and still need to add it to prtg (using that as well), but for cpu this should work:

FOUNDRY-SN-AGENT-MIB::snAgGblCpuUtil1SecAvg.0 = Gauge32: 2
FOUNDRY-SN-AGENT-MIB::snAgGblCpuUtil5SecAvg.0 = Gauge32: 2
FOUNDRY-SN-AGENT-MIB::snAgGblCpuUtil1MinAvg.0 = Gauge32: 2

memory:

FOUNDRY-SN-AGENT-MIB::snAgGblDynMemUtil.0 = Gauge32: 28
FOUNDRY-SN-AGENT-MIB::snAgGblDynMemTotal.0 = Gauge32: 4099227648
FOUNDRY-SN-AGENT-MIB::snAgGblDynMemFree.0 = Gauge32: 2946719744

temperature:

FOUNDRY-SN-AGENT-MIB::snChasActualTemperature.0 = INTEGER: 54
FOUNDRY-SN-AGENT-MIB::snChasWarningTemperature.0 = INTEGER: 118
FOUNDRY-SN-AGENT-MIB::snChasShutdownTemperature.0 = INTEGER: 124
FOUNDRY-SN-AGENT-MIB::snChasEnableTempWarnTrap.0 = INTEGER: enabled(1)
FOUNDRY-SN-AGENT-MIB::snChasGlobalIgnoreShutdownTemperature.0 = INTEGER: disabled(0)
FOUNDRY-SN-AGENT-MIB::snChasUnitActualTemperature.1 = INTEGER: 54
FOUNDRY-SN-AGENT-MIB::snChasUnitWarningTemperature.1 = INTEGER: 118
FOUNDRY-SN-AGENT-MIB::snChasUnitShutdownTemperature.1 = INTEGER: 124
FOUNDRY-SN-AGENT-MIB::snChasUnitIgnoreShutdownTemperature.1 = INTEGER: disabled(0)
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.1 = STRING: "Sensor 1 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.2 = STRING: "Sensor 2 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.3 = STRING: "Sensor 3 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.4 = STRING: "Sensor 4 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.5 = STRING: "Sensor 5 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.6 = STRING: "Sensor 6 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.7 = STRING: "Sensor 7 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempSensorDescr.1.8 = STRING: "Sensor 8 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.1 = INTEGER: 49
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.2 = INTEGER: 59
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.3 = INTEGER: 72
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.4 = INTEGER: 54
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.5 = INTEGER: 58
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.6 = INTEGER: 54
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.7 = INTEGER: 59
FOUNDRY-SN-AGENT-MIB::snAgentTempValue.1.8 = INTEGER: 103
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.1 = STRING: "Sensor 1 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.2 = STRING: "Sensor 2 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.3 = STRING: "Sensor 3 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.4 = STRING: "Sensor 4 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.5 = STRING: "Sensor 5 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.6 = STRING: "Sensor 6 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.7 = STRING: "Sensor 7 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2SensorDescr.1.1.8 = STRING: "Sensor 8 Temperature"
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.1 = INTEGER: 49
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.2 = INTEGER: 59
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.3 = INTEGER: 72
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.4 = INTEGER: 54
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.5 = INTEGER: 58
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.6 = INTEGER: 54
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.7 = INTEGER: 59
FOUNDRY-SN-AGENT-MIB::snAgentTemp2Value.1.1.8 = INTEGER: 103
FOUNDRY-SN-AGENT-MIB::snAgentTempThreshold2LowValue.1.1 = INTEGER: 34
FOUNDRY-SN-AGENT-MIB::snAgentTempThreshold2HighValue.1.1 = INTEGER: 42
FOUNDRY-SN-AGENT-MIB::snAgentTempThreshold2ShutdownValue.1.1 = INTEGER: 62

Re: ICX 7250 OIDS

inphobia — Tue, 28 May 2024 04:41:59 GMT

you'll most likely want to use "Absolute (unsigned integer)" in prtg for the custom mib tables

https://gitlab.com/PRTG/Device-Templates/Brocade could be an option, but if it's just for mem/cpu/temp a custom table should be pretty easy to make.

Re: ICX 7250 OIDS

inphobia — Wed, 29 May 2024 03:16:31 GMT

a sensor of type "SNMP Custom Advanced" with these settings should do the trick

however it seems there's a bug in prtg where only the first channel works....

you can work around this by making "SNMP Custom" sensors for each oid like this:

i'll open a case with paessler

Re: ICX 7250 OIDS

Assiamour_ — Wed, 29 May 2024 12:38:10 GMT

Hey Inphobia, thank you very much for your answers. I ended up finding an oid that returns a table for the CPU utilization which works perfectly. The memory used sensor OID you provided in your screenshot is outdated I believe because the value returned is always <0.01Gb, the Dram total sensor works and the Dram Used OID you provided seems to actually be the DRAM free but it works. The problem is, I have a stack of three ICX 7250's at the IP that I'm monitoring but the sensor only monitors one of the switches.

Re: ICX 7250 OIDS

Assiamour_ — Wed, 29 May 2024 12:51:54 GMT

This is the screenshot from PRTG

Re: ICX 7250 OIDS

inphobia — Wed, 29 May 2024 19:39:46 GMT

"The memory used sensor OID you provided in your screenshot is outdated I believe because the value returned is always <0.01Gb"

just grepped through a full snmpwalk to find possible options. for the memused however, if the mib is correct it should report percentage used. i think you might have set that to "memorybytes" instead of "percent" in the sensor config.

after having a closer look it seems like my stack's output shows only stats for the master cpu & memory as well. regretfully don't have a lot of time to dig through the mibs & figure out where & how they've hidden that info.

2 notes:
* i'm running 10.0.20, so the mib table you referenced there from 8.0.95 might not apply
* stopped looking after i clicked on "system dram" and which explained how to get temperature & license info instead.
https://docs.commscope.com/bundle/fastiron-10020-mibref/page/GUID-9EEF8E57-330A-4C1C-AA33-8741FA46A91E.html

i've been giving ruckus a hard time on the documentation (particularly for 10.x) but stuff like the "system dram" mentioned above does not inspire confidence.

sometimes they do make you smile, like when you pay for a license and find out they didn't even bother to run a spell checker on the cli command:

SSH@campus-core1#license
...
set Set seriral number for a specified software license

now where do i find a "seriral" number 😄

Re: ICX 7250 OIDS

nolanm — Fri, 31 May 2024 18:16:17 GMT

You're absolutely right. I can't thank you enough for all of your help. I added the memory used as a percentage this time, it gave me the same result as when I calculate the percentage myself using the values returned from the dynamic memory total and used. I will be replacing the dynamic memory sensors with that one for sure. I opened a case with RUCKUS to see if there is a way to monitor all of the switches in a stack, if ever they get back to me with a way to do it I'll be sure to post it here.