As part of an organization change we need to change the IP address of everything in our environment, to a new corporate network range. I was wondering if our plan to REIP the primary routable interface on each of our NetApp’s was solid. Here is the typical controller-
This looks like it will work - as far as changing the controller IP. But I think you're still going to run into CIFS/NFS disconnects. I'm pretty sure that NFS filehandles won't move to the new IP, and you'd have to do a remount on the clients. CIFS will certainly complain when the existing interface is taken offline.
You will also need to consider your NFS exports - if the network changes are happening on the client side as well, then the entire /etc/exports file becomes deprecated as soon as you make the switch.
I'm not completely clear on how CIFS registers with AD, or whether the same machine on a different IP will confuse AD or not, but that is another thing to consider.
You could test this - create your new vlan, and create another A record to point to the existing one. Mount a couple shares on a test box pointing to that new A record, change the A record, as see what happens.... You'd have to do something with the routing on the new vlan - a static host route to your test box, maybe?
Yeah. I am scheduled to test tomorrow. The good news is only CIFS, and MGMT (DFM / SSH / SNMP / ETC) run over the primary interface. iSCSI and NFS have their own interfaces as I was illustrating above-
The first interface is the primary, and the one we will be changing. I am not worried how thie will impact AD / Kerberos so much, as I am how I can have two routes simultaneously while I wait for the DNS record to update, and workstations and servers to start using the new interface. Wouldn't I need to change my plan to-
Add new VLAN to existing VIF1 interface. [vlan create vif1 26]
Add new IP Address (10.228.26.100) to new VLAN [Ifconfig Vif1-26 10.228.26.100 netmask 255.255.255.0]
Verify connectivity by testing CIFS / RPC to new IP address
For the test, at least, you don't have to worry much about the multiple routes - a host route will take precedent over a default route. The man page for na_route says "metric" has to be 0 if the destination is on a directly attached network; not sure if it would let you put a non-zero metric for a destination on the same network.
For the actual cutover, I do see your dilemma - if the client addresses aren't changing, how do you satisfy incoming traffic from both vlans? Like I said though, CIFS is going to be a problem anyways because it is connection oriented. I don't see any way around refreshing the CIFS share on the clients to get them to recognize the new IP. And in addition to having to wait for DNS to propagate, you need to worry about the DNS cache on the windows boxes. I've seen plenty of occasions when I had to flush the cache in order to get windows to see a new IP.