8 Replies Latest reply: Nov 6, 2013 7:21 AM by JLundfelt RSS

How to REIP a Netapp's primary interface without any downtime?

JLundfelt Sprinter
Currently Being Moderated

Hello.,

 

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-

 

 

TypeControllerInterfaceNetwork AddressNetwork MaskTypeStatusIn/SecOut/SecProtocols
Active/Active Controllerirv-gdc-san1a.corp.myco.comvif1-9610.1.96.100255.255.255.0VIFUp6947801745400CIFS
Active/Active Controllerirv-gdc-san1a.corp.myco.comlosk127.0.20.1255.0.0.0UnknownUp01LOOPBACK
Active/Active Controllerirv-gdc-san1a.corp.myco.comvif2-23010.1.230.50255.255.255.0VIFUp5209970023208100iSCSI
Active/Active Controllerirv-gdc-san1a.corp.myco.comvif2-23110.1.231.50255.255.255.0VIFUp20998801475370NFS
Active/Active Controllerirv-gdc-san1a.corp.myco.comvif2-23210.1.232.50255.255.255.0VIFUp756796013NFS

 

 

Routing tables

 

Internet:

Destination      Gateway            Flags     Refs     Use  Interface

default          10.1.96.1          UGS        33 3318967135  vif1-96

10.1.96/24       link#14            UC          0        0  vif1-96

10.1.96.1        c4:7d:4f:b1:35:40  UHL         1        0  vif1-96

irv-gdc-san1a-vi 2:a0:98:12:e8:ac   UHL         0      443  lo

10.1.96.255      ff:ff:ff:ff:ff:ff  UHL         0   317283  vif1-96


The A record points to 10.1.96.100, and the tentative plan was 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
  • Change A record(s)
  • Confirm network traffic [netstat -I vif1-96 -w 1 –x]
  • Change default route
  • Confirm network traffic [netstat -I vif1-26 -w 1 –x]
  • Remove existing vif1-96 VLAN

 

Attached are our hosts, and RC file

  • Re: How to REIP a Netapp's primary interface without any downtime?
    billshaffer Kart Racer
    Currently Being Moderated

    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?

     

    Bill

    • Re: How to REIP a Netapp's primary interface without any downtime?
      JLundfelt Sprinter
      Currently Being Moderated

      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-

       

       

      ControllerInterfaceNetwork AddressNetwork MaskProtocols
      irv-gdc-san1a.corp.myco.comvif1-9610.1.96.100255.255.255.0CIFS
      irv-gdc-san1a.corp.myco.comlosk127.0.20.1255.0.0.0LOOPBACK
      irv-gdc-san1a.corp.myco.comvif2-23010.1.230.50255.255.255.0iSCSI
      irv-gdc-san1a.corp.myco.comvif2-23110.1.231.50255.255.255.0NFS
      irv-gdc-san1a.corp.myco.comvif2-23210.1.232.50255.255.255.0NFS

       

      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
      • Change A record(s)
      • Confirm network traffic [netstat -I vif1-96 -w 1 –x]
      • Change default route  add new route with lower metric [route add host 10.228.26.100 10.228.26.1 10]
      • Confirm network traffic [netstat -I vif1-26 -w 1 –x]
      • Remove existing vif1-96 VLAN

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points