Hi ronanb2,

You should be able to see all of the IP addresses it is using with

isi config

status advanced

interface

Let us know if you have any additional questions.

Hello,

I only see the internal IP ranges. 

I dont see any IP address for the primary or secondary internal switch:

Information for int-a interface:
Netmask : 255.255.255.0
MTU : 9000 (shared)
IP Ranges : 128.221.252.1-128.221.252.254
Flags : Enabled

Information for int-b interface:
Netmask : 255.255.255.0
MTU : 9000 (shared)
IP Ranges : 128.221.253.1-128.221.253.254
Failover IPs : 128.221.254.1-128.221.254.254
Flags : Cluster Traffic, Failover, Enabled

Rgds

Ronan

@ronanb,

Run ifconfig on each node, the mlx0/mlx1 or ib0/ib1 internal interface.

EXAMPLE:

ib0: flags=8843 metric 0 mtu 2044
options=80018
lladdr 0.0.4.4.fe.80.0.0.0.0.0.0.0.15.1b.0.10.bd.3a.a
nd6 options=29
media: Infiniband autoselect
status: inactive
ib1: flags=1008843 metric 0 mtu 2044
options=80018
lladdr 0.0.4.5.fe.80.0.0.0.0.0.0.0.15.1b.0.10.bd.3a.b
inet 128.221.252.2 netmask 0xffffff00 broadcast 128.221.252.255 zone 1
nd6 options=29
media: Infiniband autoselect
status: active

Thanks for your reply but that just shows me the internal IP's for each Isilon node.

I want to know if i can obtain the IP address of each internal Isilon switch.

Additionally, does anyone know if the internal Isilon switches are poll-able by SNMP  (can they be discovered by SNMP)?

@ronanb,

The backend switch is unmanaged. So you can't really connect and manage it.

The back end networks are still considered private to the cluster, even when using Ethernet instead of InfiniBand. The back end Ethernet switches are configured with IPv6 addresses that OneFS uses to monitor the switches, especially in a leaf/spine configuration. There is no support for direct end-user SNMP (or other) access to the back end switches at this time.

On the Dell ethernet switches that we purchased with our new H500's, you are able to connect with this:

ssh admin@fdfe:9042:c53d::5eff:fe00:101
ssh admin@fda7:e6ee:2e09::5eff:fe00:102

default pass is admin

Assume this is self-explanatory, but that needs to be ran from your cluster nodes.

Thanks desismus - it has worked for me!

Just remember BE switches can't be manipulated by customers.

Best Regards