This post is more than 5 years old

31 Posts

5815

November 18th, 2014 12:00

Querying Isilon Cluster via SNMP For Node Model

Does anyone know how to query an Isilon cluster in order to identify the node model?

See the output below which ONLY provides the version of OneFS:

asdfasdf@asdfasdf:~$ snmpget -v 2c -c aasdfasdf -m SNMPv2-MIB asdfasdf sysName.0 sysDescr.0 sysObjectID.0

SNMPv2-MIB::sysName.0 = STRING: isilon

SNMPv2-MIB::sysDescr.0 = STRING: Isilon OneFS Isilon-1 v7.0.2.4 Isilon OneFS v7.0.2.4 B_7_0_2_184(RELEASE) amd64

SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.12124.1

TIA,

Amir

3 Apprentice

 • 

622 Posts

November 18th, 2014 13:00

Isilon SNMP.PNG.png

Use the "ISILON-MIB.txt". There's a "chassisModel" name in there. See also this thread for explanation of MIBs:

https://community.emc.com/thread/177288

1 Attachment

3 Apprentice

 • 

622 Posts

November 18th, 2014 14:00

Sorry, no idea. Someone else may know.

31 Posts

November 18th, 2014 14:00

100% correct. Thank you.  Do you know of a way, via SNMP, to acquire the "cluster IP" address from a node?

++++++++++++++++++++++++++++++++++++

$ snmptable -v 2c -c XXXXXX -O0b -Cfil ----- -Ln -m ISILON-MIB X.X.X.X chassisTable | sed -E 's/,//g' | sed -E 's/-----/,/g' | sed -E 's/,+$//g'

SNMP table: ISILON-MIB::chassisTable

index,chassisNumber,chassisConfigNumber,chassisSerialNumber,chassisModel,chassisUnitIDLEDOn

1,1,400-0034-03,SX200-XXXXX,X200-2U-Single-12GB-2x1GE-2x10GE SFP+-12TB,na

++++++++++++++++++++++++++++++++++++

31 Posts

November 18th, 2014 15:00

I have a cluster with an IP address of X.X.X.100.  If I walk a node with an IP address of X.X.X.101 - I get the following output and you can see that the X.X.X.100 cluster address in the SNMP output.  But I can't figure out how to query directly for it -instead of doing the entire snmpwalk:

$ snmpwalk -v 2c -c XXXXX -Ln -m ISILON-MIB X.X.X.101

SNMPv2-SMI::mib-2.1.1.0 = STRING: "Isilon OneFS C-1 v7.0.2.4 Isilon OneFS v7.0.2.4 B_7_0_2_184(RELEASE) amd64"

SNMPv2-SMI::mib-2.1.2.0 = OID: ISILON-MIB::cluster

SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (1332886052) 154 days, 6:27:40.52

SNMPv2-SMI::mib-2.1.4.0 = STRING:

SNMPv2-SMI::mib-2.1.5.0 = STRING: "isilon-c-1"

SNMPv2-SMI::mib-2.1.6.0 = STRING: "XXXX"

SNMPv2-SMI::mib-2.1.7.0 = INTEGER: 12

SNMPv2-SMI::mib-2.1.8.0 = Timeticks: (19) 0:00:00.19

SNMPv2-SMI::mib-2.1.9.1.2.1 = OID: SNMPv2-SMI::snmpModules.10.3.1.1

SNMPv2-SMI::mib-2.1.9.1.2.2 = OID: SNMPv2-SMI::snmpModules.11.3.1.1

SNMPv2-SMI::mib-2.1.9.1.2.3 = OID: SNMPv2-SMI::snmpModules.15.2.1.1

<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>

SNMPv2-SMI::mib-2.4.20.1.1.X.X.X.100 = IpAddress: X.X.X.100

SNMPv2-SMI::mib-2.4.20.1.1.X.X.X.101 = IpAddress: X.X.X.101

3 Apprentice

 • 

622 Posts

November 20th, 2014 15:00

I was going to suggest that, but you wanted to know if SNMP does it or not and I wasn't sure.

Phil

31 Posts

November 20th, 2014 15:00

Answering my own question here - it appears that you cannot SNMP query for the SmartConnect address.  However, the following CLI syntax will provide that information.  See the SC Service Address field below:

# isi networks list subnets -v

subnet0 - Default ext-1 subnet

     Address Family: IPv4

            Netmask: 255.255.255.0

             Subnet: 10.160.54.0

             Gateway 10.160.54.1, Priority 1

                MTU: 1500

SC Service Address: 10.160.54.100

       VLAN Tagging: Disabled

            VLAN ID: 0

      DSR Addresses: 0

              Pools: 1

                     pool0 - Default ext-1 pool

31 Posts

December 1st, 2014 08:00

The Isilon platform supports RFC1213-MIB.  That MIB can be used, as shown below, to acquire the SmartConnect IP address for the cluster.  Since the SmartConnect IP address lives on the first node added to the cluster, we see, in the output below, the SmartConnect IP address 10.160.54.100 associated with the first node with IP address 10.160.54.101.  Unlike nodes 2 and 3, the first node shows two IP addresses with ipAdEntIfIndex = 8  - that is because the SmartConnect address lives on the first node.

For each node in the cluster query the ipAddrTable from the RFC1213-MIB

snmptable -v 2c -c XXXXXXXX -m RFC1213-MIB 10.160.54.101 ipAddrTable

SNMP table: RFC1213-MIB::ipAddrTable

   ipAdEntAddr ipAdEntIfIndex ipAdEntNetMask ipAdEntBcastAddr ipAdEntReasmMaxSize

10.160.54.100              8  255.255.255.0                1                  -1

10.160.54.101              8  255.255.255.0                1                  -1

     127.0.0.1              5      255.0.0.0                1                  -1

128.221.252.1              7  255.255.255.0                1                  -1

128.221.253.1              6  255.255.255.0                1                  -1

128.221.254.1              5  255.255.255.0                1                  -1

snmptable -v 2c -c XXXXXXXXX -m RFC1213-MIB 10.160.54.102 ipAddrTable

SNMP table: RFC1213-MIB::ipAddrTable

   ipAdEntAddr ipAdEntIfIndex ipAdEntNetMask ipAdEntBcastAddr ipAdEntReasmMaxSize

10.160.54.102              8  255.255.255.0                1                  -1

     127.0.0.1              5      255.0.0.0                1                  -1

128.221.252.2              7  255.255.255.0                1                  -1

128.221.253.2              6  255.255.255.0                1                  -1

128.221.254.2              5  255.255.255.0                0                  -1

snmptable -v 2c -c XXXXXXXXXX -m RFC1213-MIB 10.160.54.103 ipAddrTable

SNMP table: RFC1213-MIB::ipAddrTable

   ipAdEntAddr ipAdEntIfIndex ipAdEntNetMask ipAdEntBcastAddr ipAdEntReasmMaxSize

10.160.54.103              8  255.255.255.0                1                  -1

     127.0.0.1              5      255.0.0.0                1                  -1

128.221.252.3              7  255.255.255.0                1                  -1

128.221.253.3              6  255.255.255.0                1                  -1

128.221.254.3              5  255.255.255.0                1                  -1

1 Message

April 6th, 2017 07:00

This is some years after the original question was posed, but there is a simpler way, on a RHEL 6 server with netsnmp-utils.

The limiting issue is most people only configure a single SmartConnect zone with all of their nodes in it, which doesn't help if you have multiple node types as you don't know which node you will connect to.

We configure additional SmartConnect zones, one per node (nodeX.isilon.example.com), each containing ext-1 for that node as well as a range of only a single IP. These are then addressable in DNS, so you can connect to each specific node.

Then you can do:

  1. Download the ISILON-MIB.txt file from your cluster
  2. Put it in /usr/share/snmp/mibs/ISILON-MIB.txt
  3. Ensure /etc/snmp/snmp.conf has "mibs +all" in it (it's the only line in our file)
  4. Run the following:

# snmpget -v2c -c community-string node1.isilon.example.com ISILON-MIB::chassisModel.1 SNMPv2-MIB::sysDescr.0 ISILON-MIB::diskStatus.3

ISILON-MIB::chassisModel.1 = STRING: X410-4U-Dual-128GB-2x1GE-2x10GE SFP+-102TB-1638GB SSD

SNMPv2-MIB::sysDescr.0 = STRING: isilon-1 1491349860 Isilon OneFS v8.0.0.4

ISILON-MIB::diskStatus.3 = STRING: REPLACE

Hope this helps someone in the future!

No Events found!

Top