Change IP addressing via CLI after cluster move

Question

Our cluster was moved on very short notice which meant a lack of planning.  Upon arriving at the new destination I've taken the opportunity to try to change the addressing as it was inexplicably configured with 192.168.X.X address space.  Obviously I can't use the wizard as the nodes are already configured nor the GUI because the network it was on doesn't exist at this location.  I've managed to piece together how to configure the new subnet and pool as well as add the interfaces to the pool.  Everything looks right to me but I'm getting 'no carrier' statuses on the 10gb interfaces both using a Cisco QSFP-4X10G-AOC1 as well as direct 10GB links on 50nm OM3 cable.  On my Cisco Nexus switch the ports show connected.  They are configured as simple access ports at this point, no trunk, no port-channel and I have 'green' link LED indicators on the Isilon shelves. So my question is, am I missing some step to write the config to the interfaces or something along those lines?  It doesn't seem to me like I should given that this is running a flavor of Linux.  When I run an ifconfig -a on the shelf to which I'm connected with a serial cable the interface is showing 'no carrier' there as well.  I tried bringing the ports up with the ifconfig command but no change.  Ifconfig doesn't show the ip address unless I manually configure it. I feel like I'm missing something simple but don't know this equipment at all (I'm the network engineer) and I'm working my way through what I can find online as best as I'm able. studio01-4# isi network list subnet --verbose subnet0Address Family: IPv4Netmask: 255.255.248.0Subnet: 10.120.208.0Gateway 10.120.208.1, Priority 1MTU: 1500SC Service Address: 10.120.208.100VLAN Tagging: EnabledVLAN ID: 208DSR Addresses: 0Pools: 1pool0 studio01-4# isi network list pool --verbose subnet0:pool0In Subnet: subnet0Allocation: StaticRanges: 110.120.208.101-10.120.208.106Pool Membership: 61:10gige-1 (no carrier)2:10gige-1 (no carrier)3:10gige-1 (no carrier)4:10gige-1 (no carrier)5:10gige-1 (no carrier)6:10gige-1 (no carrier)Aggregation Mode: Link Aggregation Control Protocol (LACP)Access Zone: 1SmartConnect:Suspended Nodes : NoneAuto Unsuspend ... 0Zone : N/ATime to Live : 0Service Subnet : subnet0Connection Policy: Network ThroughputFailover Policy : Round RobinRebalance Policy : Automatic Failback   studio01-4# isi networks list interfaceInterface Status Membership Addresses--------------- ----------- ------------------------- ------------------------------1:10gige-1 no carrier subnet0:pool0 10.120.208.1011:10gige-2 no carrier1:ext-1 no carrier1:ext-2 no carrier2:10gige-1 no carrier subnet0:pool0 10.120.208.1022:10gige-2 no carrier2:ext-1 no carrier2:ext-2 no carrier3:10gige-1 no carrier subnet0:pool0 10.120.208.1033:10gige-2 no carrier3:ext-1 no carrier3:ext-2 no carrier4:10gige-1 no carrier subnet0:pool0 10.120.208.1044:10gige-2 no carrier4:ext-1 no carrier4:ext-2 no carrier5:10gige-1 no carrier subnet0:pool0 10.120.208.1055:10gige-2 no carrier5:ext-1 no carrier5:ext-2 no carrier6:10gige-1 no carrier subnet0:pool0 10.120.208.1066:10gige-2 no carrier6:ext-1 no carrier6:ext-2 no carrier Thanks in advance.

Phil.Lam · Answer

Coupe2112, Try re-seating the QSFPs. Your network config looks correct.

Isilon

Was this post helpful?