Skip to main content
Cluster and storage switches

Install a Reference Configuration File on a CN1610 switch

Contributors netapp-jsnyder netapp-jolieg netapp-yvonneo
PDFs

Follow this procedure to install a Reference Configuration File (RCF).

Before installing an RCF, you must first migrate the cluster LIFs away from switch cs2. After the RCF is installed and validated, the LIFs can be migrated back.

Review requirements

What you'll need

  • A current backup of the switch configuration.

  • A fully functioning cluster (no errors in the logs and no defective cluster network interface cards (NICs) or similar issues).

  • Fully functional port connections on the cluster switch.

  • All cluster ports set up.

  • All cluster logical interfaces (LIFs) set up.

  • A successful communication path: The ONTAP (privilege: advanced) cluster ping-cluster -node node1 command must indicate that larger than PMTU communication is successful on all paths.

  • A supported version of RCF and ONTAP.

    Make sure you consult the switch compatibility table on the NetApp CN1601 and CN1610 Switches page for the supported RCF and ONTAP versions.

Install the RCF

The following procedure uses the clustered Data ONTAP 8.2 syntax. As a result, the cluster Vserver, LIF names, and CLI output are different than those in Data ONTAP 8.3.

There can be command dependencies between command syntax in the RCF and FASTPATH versions.

Note In RCF version 1.2, support for Telnet has been explicitly disabled because of security concerns. To avoid connectivity issues while installing RCF 1.2, verify that Secure Shell (SSH) is enabled. The NetApp CN1610 Switch Administrator's Guide has more information about SSH.
About the examples

The examples in this procedure use the following switch and node nomenclature:

  • The two NetApp switches are cs1 and cs2.

  • The two cluster LIFs are clus1 and clus2.

  • The Vservers are vs1 and vs2.

  • The cluster::*> prompt indicates the name of the cluster.

  • The cluster ports on each node are named e1a and e2a.

    Hardware Universe has more information about the actual cluster ports that are supported on your platform.

  • The supported Inter-Switch Links (ISLs) are ports 0/13 through 0/16.

  • The supported node connections are ports 0/1 through 0/12.

  • A supported version of FASTPATH, RCF, and ONTAP.

    Make sure you consult the switch compatibility table on the NetApp CN1601 and CN1610 Switches page for the supported FASTPATH, RCF, and ONTAP versions.

Step 1: Migrate cluster

  1. Save your current switch configuration information:

    write memory

    Show example

    The following example shows the current switch configuration being saved to the startup configuration (startup-config) file on switch cs2:

    (cs2) # write memory
This operation may take a few minutes.
Management interfaces will not be available during this time.

Are you sure you want to save? (y/n) y

Config file 'startup-config' created successfully.

Configuration Saved!

  2. On the console of each node, migrate clus2 to port e1a:

    network interface migrate

    Show example 
    cluster::*> network interface migrate -vserver vs1 -lif clus2 -source-node node1 -destnode node1 -dest-port e1a

cluster::*> network interface migrate -vserver vs2 -lif clus2 -source-node node2 -destnode node2 -dest-port e1a

  3. On the console of each node, verify that the migration occurred:

    network interface show -role cluster

    Show example

    The following example shows that clus2 has migrated to port e1a on both nodes:

    cluster::*> network port show -role cluster
         clus1      up/up      10.10.10.1/16   node2    e1a     true
         clus2      up/up      10.10.10.2/16   node2    e1a     false

  4. Shut down port e2a on both nodes:

    network port modify

    Show example

    The following example shows port e2a being shut down on both nodes:

    cluster::*> network port modify -node node1 -port e2a -up-admin false
cluster::*> network port modify -node node2 -port e2a -up-admin false

  5. Verify that port e2a is shut down on both nodes:

    network port show

    Show example 
    cluster::*> network port show -role cluster

                                  Auto-Negot  Duplex      Speed (Mbps)
Node   Port   Role     Link MTU   Admin/Oper  Admin/Oper  Admin/Oper
------ ------ -------- ---- ----- ----------- ----------  -----------
node1
       e1a    cluster  up   9000  true/true   full/full   auto/10000
       e2a    cluster  down 9000  true/true   full/full   auto/10000
node2
       e1a    cluster  up   9000  true/true   full/full   auto/10000
       e2a    cluster  down 9000  true/true   full/full   auto/10000

  6. Shut down the ISL ports on cs1, the active NetApp switch.

    Show example 
    (cs1) # configure
(cs1) (config) # interface 0/13-0/16
(cs1) (interface 0/13-0/16) # shutdown
(cs1) (interface 0/13-0/16) # exit
(cs1) (config) # exit

Step 2: Install RCF

  1. Copy the RCF to the switch.

    Note You must set the .scr extension as part of the file name before invoking the script. This extension is the extension for the FASTPATH operating system.

    The switch will validate the script automatically as it is downloaded to the switch, and the output will go to the console.

    Show example 
    (cs2) # copy tftp://10.10.0.1/CN1610_CS_RCF_v1.1.txt nvram:script CN1610_CS_RCF_v1.1.scr

[the script is now displayed line by line]
Configuration script validated.
File transfer operation completed successfully.

  2. Verify that the script was downloaded and saved with the file name that you gave it.

    Show example 
    (cs2) # script list
Configuration Script Name        Size(Bytes)
-------------------------------- -----------
running-config.scr               6960
CN1610_CS_RCF_v1.1.scr           2199

2 configuration script(s) found.
6038 Kbytes free.

  3. Validate the script.

    Note The script is validated during the download to verify that each line is a valid switch command line.
    Show example 
    (cs2) # script validate CN1610_CS_RCF_v1.1.scr
[the script is now displayed line by line]
Configuration script 'CN1610_CS_RCF_v1.1.scr' validated.

  4. Apply the script to the switch.

    Show example 
    (cs2) #script apply CN1610_CS_RCF_v1.1.scr

Are you sure you want to apply the configuration script? (y/n) y
[the script is now displayed line by line]...

Configuration script 'CN1610_CS_RCF_v1.1.scr' applied.

  5. Verify that your changes have been implemented on the switch.

    (cs2) # show running-config

    The example displays the running-config file on the switch. You must compare the file to the RCF to verify that the parameters that you set are as you expect.

  6. Save the changes.

  7. Set the running-config file to be the standard one.

    Show example 
    (cs2) # write memory
This operation may take a few minutes.
Management interfaces will not be available during this time.

Are you sure you want to save? (y/n) y

Config file 'startup-config' created successfully.

  8. Reboot the switch and verify that the running-config file is correct.

    After the reboot completes, you must log in, view the running-config file, and then look for the description on interface 3/64, which is the version label for the RCF.

    Show example 
    (cs2) # reload

The system has unsaved changes.
Would you like to save them now? (y/n) y


Config file 'startup-config' created successfully.
Configuration Saved!
System will now restart!

  9. Bring up the ISL ports on cs1, the active switch.

    Show example 
    (cs1) # configure
(cs1) (config)# interface 0/13-0/16
(cs1) (Interface 0/13-0/16)# no shutdown
(cs1) (Interface 0/13-0/16)# exit
(cs1) (config)# exit

  10. Verify that the ISLs are operational:

    show port-channel 3/1

    The Link State field should indicate Up.

    Show example 
    (cs2) # show port-channel 3/1

Local Interface................................ 3/1
Channel Name................................... ISL-LAG
Link State..................................... Up
Admin Mode..................................... Enabled
Type........................................... Static
Load Balance Option............................ 7
(Enhanced hashing mode)

Mbr    Device/       Port      Port
Ports  Timeout       Speed     Active
------ ------------- --------- -------
0/13   actor/long    10G Full  True
       partner/long
0/14   actor/long    10G Full  True
       partner/long
0/15   actor/long    10G Full  True
       partner/long
0/16   actor/long    10G Full  True
       partner/long

  11. Bring up cluster port e2a on both nodes:

    network port modify

    Show example

    The following example shows port e2a being brought up on node1 and node2:

    cluster::*> network port modify -node node1 -port e2a -up-admin true
cluster::*> network port modify -node node2 -port e2a -up-admin true

Step 3: Validate installation

  1. Verify that port e2a is up on both nodes:

    network port show -role cluster

    Show example 
    cluster::*> network port show -role cluster

                                Auto-Negot  Duplex      Speed (Mbps)
Node   Port Role     Link MTU   Admin/Oper  Admin/Oper  Admin/Oper
------ ---- -------- ---- ----  ----------- ----------  ------------
node1
       e1a  cluster  up   9000  true/true   full/full   auto/10000
       e2a  cluster  up   9000  true/true   full/full   auto/10000
node2
       e1a  cluster  up   9000  true/true   full/full   auto/10000
       e2a  cluster  up   9000  true/true   full/full   auto/10000

  2. On both nodes, revert clus2 that is associated with port e2a:

    network interface revert

    The LIF might revert automatically, depending on your version of ONTAP.

    Show example 
    cluster::*> network interface revert -vserver node1 -lif clus2
cluster::*> network interface revert -vserver node2 -lif clus2

  3. Verify that the LIF is now home (true) on both nodes:

    network interface show -role cluster

    Show example 
    cluster::*> network interface show -role cluster

        Logical    Status     Network        Current  Current Is
Vserver Interface  Admin/Oper Address/Mask   Node     Port    Home
------- ---------- ---------- -------------- -------- ------- ----
vs1
        clus1      up/up      10.10.10.1/24  node1    e1a     true
        clus2      up/up      10.10.10.2/24  node1    e2a     true
vs2
        clus1      up/up      10.10.10.1/24  node2    e1a     true
        clus2      up/up      10.10.10.2/24  node2    e2a     true

  4. View the status of the node members:

    cluster show

    Show example 
    cluster::> cluster show

Node           Health  Eligibility
-------------- ------- ------------
node1
               true    true
node2
               true    true

  5. Copy the running-config file to the startup-config file when you are satisfied with the software versions and switch settings.

    Show example 
    (cs2) # write memory
This operation may take a few minutes.
Management interfaces will not be available during this time.

Are you sure you want to save? (y/n) y

Config file 'startup-config' created successfully.

Configuration Saved!

  6. Repeat the previous steps to install the RCF on the other switch, cs1.

What's next?

Configure switch health monitoring