This post is more than 5 years old
1 Rookie
•
16 Posts
3
14561
June 28th, 2013 07:00
How do I re-number Isilon nodes in a cluster?
As Isilon clusters grow over time, and nodes are Smartfailed out, you may be left with a cluster that does not have contiguous node numbers. If that ever happens, it is easy to change a node number to be what you need it to be. The LNN is the Logical Node number and the lnnset command in isi config is used to change these LNN's.
To change node #8 to be node #6 in an Isilon cluster, you would issue the following commands:
# isi config
>>> lnnset 8 6
>>> commit
No Events found!
DevinLucas
1 Rookie
•
16 Posts
0
June 28th, 2013 08:00
Thanks Devin!
DevinLucas
1 Rookie
•
16 Posts
0
August 26th, 2014 05:00
Yes it is non-disruptive.
crklosterman
450 Posts
1
August 28th, 2014 08:00
Also, be aware that this only changes the LNN (logical node number), not the actual device ID on the cluster. What's the difference you may ask?
Type:
isi config
status advanced
The last table in the output will show you a map of ID to LNN. ID will never change, but you usually won't see it in any cluster output. All that you will typically see is the LNN. Just be aware that both do exist. ID is incremented every time a new node is added to the cluster.
~Chris Klosterman
Senior Solution Architect
EMC Isilon Offer and Enablement Team
Twitter: @croaking
Email: chris.Klosterman@emc.com
Peter_Sero
6 Operator
•
1.2K Posts
0
September 2nd, 2014 08:00
Chris
that's an important difference for sure, and the next twist is that for drives
it is the "logical number" (Lnum) which gets incremented and therefore is unique (within a node).
Nodes: LOGICAL=arbitrary,settable ID=incremented,unique
Drives: LOGICAL=incremented,unique
-- Peter
Brian_Coulombe_
1 Rookie
•
107 Posts
0
September 15th, 2015 09:00
Reopening this for a question. Renumbered the nodes to this:
CLUSTERNAME >>> lnnset
LNN Device ID Cluster IP
----------------------------------------
1 1 128.221.254.1
2 2 128.221.254.2
3 3 128.221.254.3
4 4 128.221.254.4
5 5 128.221.254.5
6 6 128.221.254.6
7 7 128.221.254.7
8 9 128.221.254.9
9 8 128.221.254.8
I know DEVID and LNN won't match but the front panels on both Node 8 and 9 say Node 9. How do I fix that?
Peter_Sero
6 Operator
•
1.2K Posts
0
September 15th, 2015 21:00
# isi config
>>> lnnset 8 9
>>> lnnset 9 8
>>> commit
Before the final commit, all lnnsets comprise the overall change plan in plain form "old -> new".
-- Peter
Brian_Coulombe_
1 Rookie
•
107 Posts
0
September 16th, 2015 04:00
Thanks Peter. I should have closed this out the other day as I figured it out. I'm impatient and didn't realize it takes time for this to occur. On the down side, Node 8 and node 9 both say node 9 so I was told to reboot node 8 so I will be doing that later this afternoon.
ID's remain the same, LNNs change so good deal
ladkins1
2 Posts
0
May 16th, 2016 07:00
So at the dashboard where node IDs are listed are we seeing the ID or the LNN
Peter_Sero
6 Operator
•
1.2K Posts
0
May 16th, 2016 09:00
The platform API mostly uses node IDs (as "devid") for statistics...
And the dashboard labels the column "ID" where it actually shows the LNNs...
fwiw
-- Peter
addisdaddy20
65 Posts
0
May 16th, 2016 09:00
Hello ladkins,
you are viewing the nodes LNN. Actual node ID's are never reused so its important to understand this if you have to for any reason replace a node. You do not want to use the device ID but the LNN for any scripting you may do.
D_Tracy