Skip to main content
Cluster and storage switches

Install FASTPATH software

Contributors netapp-jsnyder netapp-jolieg
PDFs

When you install the FASTPATH software on your NetApp switches, you must begin the upgrade with the second switch, cs2.

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 (must not have been migrated).

  • 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 FASTPATH and ONTAP.

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

Install FASTPATH

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.

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.

Step 1: Migrate cluster

  1. If AutoSupport is enabled on this cluster, suppress automatic case creation by invoking an AutoSupport message:

    system node autosupport invoke -node * -type all - message MAINT=xh

    x is the duration of the maintenance window in hours.

    Note The AutoSupport message notifies technical support of this maintenance task so that automatic case creation is suppressed during the maintenance window.

  2. Log into the switch as admin. There is no password by default. At the (cs2) # prompt, enter the enable command. Again, there is no password by default. This gives you access to Privileged EXEC mode, which allows you to configure the network interface.

    Show example 
    (cs2) # enable
Password (Enter)
(cs2) #

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

    network interface migrate

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

  4. On the console of each node, verify that the migration took place:

    network interface show

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

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

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

Step 2: Install FASTPATH software

  1. Shut down cluster 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

  2. 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

  3. Shut down the Inter-Switch Link (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

  4. Back up the current active image on cs2.

    Show example 
    (cs2) # show bootvar

 Image Descriptions   .

  active:
  backup:

 Images currently available on Flash

----------------------------------------------------------------------
 unit        active       backup     current-active       next-active
----------------------------------------------------------------------

    1        1.1.0.3      1.1.0.1          1.1.0.3           1.1.0.3

(cs2) # copy active backup
Copying active to backup
Copy operation successful

(cs2) #

  5. Download the image file to the switch.

    Copying the image file to the active image means that when you reboot, that image establishes the running FASTPATH version. The previous image remains available as a backup.

    Show example 
    (cs2) # copy tftp://10.0.0.1/NetApp_CN1610_1.1.0.5.stk active


Mode...................................... TFTP
Set Server IP............................. 10.0.0.1
Path...................................... ./
Filename.................................. NetApp_CN1610_1.1.0.5.stk
Data Type................................. Code
Destination Filename...................... active

Management access will be blocked for the duration of the transfer
Are you sure you want to start? (y/n) y
TFTP Code transfer starting...


File transfer operation completed successfully.

  6. Verify the running version of the FASTPATH software.

    show version

    Show example 
    (cs2) # show version

Switch: 1

System Description.................. Broadcom Scorpion 56820
                                     Development System - 16 TENGIG,
                                     1.1.0.3, Linux 2.6.21.7
Machine Type........................ Broadcom Scorpion 56820
                                     Development System - 16TENGIG
Machine Model....................... BCM-56820
Serial Number....................... 10611100004
FRU Number..........................
Part Number......................... BCM56820
Maintenance Level................... A
Manufacturer........................ 0xbc00
Burned In MAC Address............... 00:A0:98:4B:A9:AA
Software Version.................... 1.1.0.3
Operating System.................... Linux 2.6.21.7
Network Processing Device........... BCM56820_B0
Additional Packages................. FASTPATH QOS
                                     FASTPATH IPv6 Management

  7. View the boot images for the active and backup configuration.

    show bootvar

    Show example 
    (cs2) # show bootvar

Image Descriptions

 active :
 backup :

 Images currently available on Flash

----------------------------------------------------------------------
 unit        active       backup     current-active       next-active
----------------------------------------------------------------------

    1        1.1.0.3      1.1.0.3          1.1.0.3           1.1.0.5

  8. Reboot the switch.

    reload

    Show example 
    (cs2) # reload

Are you sure you would like to reset the system? (y/n)  y

System will now restart!

Step 3: Validate installation

  1. Log in again, and verify the new version of the FASTPATH software.

    show version

    Show example 
    (cs2) # show version

Switch: 1

System Description................... Broadcom Scorpion 56820
                                      Development System - 16 TENGIG,
                                      1.1.0.5, Linux 2.6.21.7
Machine Type......................... Broadcom Scorpion 56820
                                      Development System - 16TENGIG
Machine Model........................ BCM-56820
Serial Number........................ 10611100004
FRU Number...........................
Part Number.......................... BCM56820
Maintenance Level.................... A
Manufacturer......................... 0xbc00
Burned In MAC Address................ 00:A0:98:4B:A9:AA
Software Version..................... 1.1.0.5
Operating System..................... Linux 2.6.21.7
Network Processing Device............ BCM56820_B0
Additional Packages.................. FASTPATH QOS
                                      FASTPATH IPv6 Management

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

    configure

    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

  3. 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

  4. 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!

  5. Enable the second cluster port, e2a, on each node:

    network port modify

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

  6. Revert clus2 that is associated with port e2a:

    network interface revert

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

    Show example 
    cluster::*> network interface revert -vserver Cluster -lif n1_clus2
cluster::*> network interface revert -vserver Cluster -lif n2_clus2

  7. 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

  8. View the status of the nodes:

    cluster show

    Show example 
    cluster::> cluster show

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

  9. Repeat the previous steps to install the FASTPATH software on the other switch, cs1.

  10. If you suppressed automatic case creation, re-enable it by invoking an AutoSupport message:

    system node autosupport invoke -node * -type all -message MAINT=END