2015-04-10 06:36 AM
I need to change the management IP addresses of our CDOT system; the new addresses are in a different network. Since we're currently using port e0a for management, I also want to switch back to e0M. Since there are quite some steps to achieve all this, I made a list of steps I have to perform:
1. Change IP-Address of SP on each node: system node service-processor network modify ...
2. Create routing groups for the new network for cluster and both node Vservers: network routing-groups create ...
3. Add e0M to the failover groups for cluster and node management: network interface failover-groups create ...
4. Change the network settings for cluster and node management: network interface modify ...
5. Remove e0a from the failover groups for cluster and node management: network interface failober-groups delete ...
Did I miss anything?
Solved! SEE THE SOLUTION
2015-04-10 05:51 PM
6. Updating DNS with the appropriate A & PTR records (And CName aliases if you have them configured)
7. Updating any firewall rules in your environment
2016-10-18 08:09 AM
No, really. Back in the days of 7mode you just hand edited a few config files and rebooted. But cDOT is database driven, and the best way to get there depends on your situation, how many lifs need to be re-addressed, can you connect to the old subnet and the new subnet at the same time, and are you on a release from before or after the introduction of broadcast domains.
At a high level I'd suggest configuring ports with connectivity to the new network, creating new lifs, etc on those ports for node mgmt and cluster mgmt, and then decommisioning the old lifs/ports. It's likely non-disruptive if planned correctly, but the steps to get there will vary from one situation to the next.
2016-10-19 04:11 AM
This is a 2254, so connectivity is limited, the LIFs etc are the ones the installation wizard creates.
I think I can find away to do it by temporarily designating an unused 10GB port on each head as a node management one, deleting the e0M lifs and create new ones in the right subnet.
Really this post is about NetApp inability to offer a solution to what can't be that unusual a question. Last time I had a similar one they ended up recommending to wipe the filer and start again, Which I did as there wasn't really any other set-up it.
Crux of the matter is CDot may be a great product, but it may be so complex now that NetApp's staff can't really support properly.
2016-11-22 05:17 PM
For cDOT 8.3. I had some issues finding the correct command with NetApp documentation (annoying). You can change the e0M network interface IP/subnet with the following command (Run this from console connection)
CLUSTER::> network interface show -curr-port e0M
displays entries that can be modified for the e0M management port for proper command syntax
CLUSTER::> set advance
advance command structure - approve
CLUSTER::> network interface modify -vserver VSERVER -lif LIFNAME -home-node HOMENODE -home-port e0M -address IPADDRESS -netmask NETMASK
you may have to include -force-subnet-assocation
The subnet should be created prior to moving IPs from my experience.