Cluster rename

[Jeff Cleverley]

Greetings,

Has anyone renamed a cluster?  If so what are the steps?

My main issue is the cluster name was generated in capital letters instead of lower case.  We have a bunch of common scripts used at multiple sites that expect lower case.  Windows doesn't care, but nfs/unix being case sensitive does.  I'd rather rename the cluster than start modifying a bunch of script and try to make sure all future ones adapt to the anomaly. 

The cluster isn't in production yet so renaming is still an option.  I have the same thing to do with a NL cluster.

Thanks,

Jeff

--

Jeff Cleverley
IT Engineer

4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611

[Jeff Cleverley]

I forgot to mention it is currently running 7.1.1.1.

Thanks,

Jeff

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Monty Bolinger]

Jeff,

Is this what you are looking for?

# isi config
>>> name "new name"
>>> commit

The only thing is that this won't really change how the cluster is accessed.  That mapping is done from DNS.
If you change the cnames in DNS you should be able to call it whatever you want there.

MB

[Monty Bolinger]

Here is a more official response.

16583 : OneFS: How to change the cluster name            
https://support.emc.com/kb/16583

MB

On 1/30/2015 4:01 PM, Jeff Cleverley wrote:

[Jeff Cleverley]

Monty,

This isn't what I'm after.  The current name shows up as DILBERT but we want it to be dilbert.  When I try and change the command through the web or CLI like above, it fails saying the name is the same.  This means I have to rename it catbert and then back to dilbert. This case difference doesn't affect dns or anything like that.  

The problem is when scripts run a host command or something similar, it comes back upper case.  This causes things like nfs paths created by the scripts to require users to go to /ifs/DILBERT/data/* or to fail because the scripts have the names loaded in lower case.  We unix users really hate upper case :-)

As mentioned, I could modify current scripts, but future scripts pushed by different people to all the sites might not be modified correctly.  I just don't want to keep tripping on this issue for the next few years.

If you rename a linux system, there are generally 4 or 5 locations you have to modify files in.  I'm assuming the web or CLI would modify all of them, but EMC has said re-naming has sometimes lead to issues.  I just saw your email with the link to the howto.  

I've got 1G connections we use for management access so I shouldn't have to change dns after the reboot.

Thanks,

Jeff

[Peter Serocka]

Hi Jeff

why not trying out a OneFS virtual node/simulator to see
how you can achieve the desired effect (which still
hasn’t become clear to me, sorry ;).

Some bits which might help connecting the dots:

Using host/dig/nslookup always goes to DNS,
wether ran on the cluster or some client.

The hostname command on the cluster returns the nodename
which is derived from the clustername as clustername-#.

ping nodename
finds actual nodenames in /etc/hosts and thus
doesn’t consult DNS (for nodenames!).

hth

— Peter

[Jeff Cleverley]

On Sat, Jan 31, 2015 at 12:57 AM, Peter Serocka <pser...@picb.ac.cn> wrote:

Hi Jeff

why not trying out a OneFS virtual node/simulator to see
how you can achieve the desired effect (which still
hasn’t become clear to me, sorry ;).

The desired effect is to see the host name at the prompts in lower case and not upper case.  The concern is EMC has said there were some problems in the past.  I'm hearing it was more in the 6.5 class.  I could test the base change which I expect will work, I just can't test future config issues :-)  I was wondering if anyone had done this.

Some bits which might help connecting the dots:

Using host/dig/nslookup always goes to DNS,
wether ran on the cluster or some client.

The hostname command on the cluster returns the nodename
which is derived from the clustername as clustername-#.

ping nodename
finds actual nodenames in /etc/hosts and thus
doesn’t consult DNS (for nodenames!).

In this case some of the scripts are running "isi status |grep "Cluster Name".  The name returned is upper case and it really should be lower case.  

Thanks,

Jeff

[Peter Serocka]

Some caveats with cluster renaming are documented in 

KB articles -- are you saying that support suggests 

there might be issues beyond those?

On 2015 Feb 3. md, at 13:45 st, Jeff Cleverley wrote:

On Sat, Jan 31, 2015 at 12:57 AM, Peter Serocka <pser...@picb.ac.cn> wrote:

Hi Jeff

why not trying out a OneFS virtual node/simulator to see
how you can achieve the desired effect (which still
hasn’t become clear to me, sorry ;).

The desired effect is to see the host name at the prompts in lower case and not upper case.  The concern is EMC has said there were some problems in the past.  I'm hearing it was more in the 6.5 class.  I could test the base change which I expect will work, I just can't test future config issues :-)  I was wondering if anyone had done this.

Some bits which might help connecting the dots:

Using host/dig/nslookup always goes to DNS,
wether ran on the cluster or some client.

The hostname command on the cluster returns the nodename
which is derived from the clustername as clustername-#.

ping nodename
finds actual nodenames in /etc/hosts and thus
doesn’t consult DNS (for nodenames!).

In this case some of the scripts are running "isi status |grep "Cluster Name".  The name returned is upper case and it really should be lower case.  

Thanks,

Jeff

Peter Serocka

CAS-MPG Partner Institute for Computational Biology (PICB)

Shanghai Institutes for Biological Sciences (SIBS)

Chinese Academy of Sciences (CAS)

320 Yue Yang Rd, Shanghai 200031, China

pser...@picb.ac.cn

[Jeff Cleverley]

That is what I was told.  There were no specific cases or details given to me, but they said it was mostly the 6.5 OneFS range.  I expected there could be issues with the caveats such as the name length, but those would not affect this.

I never found a stand alone file like /etc/hosts that had that name in it so I expect it is buried in a database file somewhere.  I'm going to try the rename and hope the future doesn't make me regret it :-)

Jeff

--
You received this message because you are subscribed to the Google Groups "Isilon Technical User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isilon-user-gr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bnajera10]

Question: What was the experience renaming the cluster? Any regrets?

Thanks,

Ben

[Jeff Cleverley]

Ben,

Ultimately things worked out fine.  There wasn't much data on the cluster when we did it so there were not too many disruptions to it.  We ended up changing the path for the SyncIQ to match the lower case.  I believe that did require a new baseline because the path changed, but again, not that much data.

The unix people made some changes and everything else seemed to be happy.  I don't recall there being any issues with CIFS/AD configurations.

Thanks,

Jeff

** Please note my email address has changed to jeff.cl...@broadcom.com

Jeff Cleverley
IT Engineer

4380 Ziegler Road

Building 1, Dock 1