Install the EFOS software

Contributors netapp-yvonneo netapp-martyh

You can use this procedure to install the EFOS software on the BES-53248 cluster switch. You can download the applicable Broadcom EFOS software for your cluster switches from the Broadcom Ethernet Switch Support site.

About this task

Note the following:

  • When upgrading from EFOS 3.4.x.x to EFOS 3.7.x.x or later, the switch must be running EFOS 3.4.4.6 (or later 3.4.x.x release). If you are running a release prior to that, then upgrade the switch to EFOS 3.4.4.6 (or later 3.4.x.x release) first, then upgrade the switch to EFOS 3.7.x.x or later.

  • The configuration for EFOS 3.4.x.x and 3.7.x.x or later are different. Changing the EFOS version from 3.4.x.x to 3.7.x.x or later, or vice versa, requires the switch to be reset to factory defaults and the RCF files for the corresponding EFOS version to be (re)applied. This procedure requires access through the serial console port.

  • Beginning with EFOS version 3.7.x.x or later, a non-FIPS compliant and a FIPS compliant version is available. Different steps apply when moving to from a non-FIPS compliant to a FIPS compliant version or vice versa. Changing EFOS from a non-FIPS compliant to a FIPS compliant version or vice versa will reset the switch to factory defaults. This procedure requires access through the serial console port.

Procedure

Current EFOS version

New EFOS version

High level steps

Steps to upgrade EFOS between two (non) FIPS compliant versions

3.4.x.x

3.4.x.x

Install the new EFOS image using method 1) The configuration and license information is retained

3.4.4.6 (or later 3.4.x.x)

3.7.x.x or later non-FIPS compliant

Upgrade EFOS using method 1. Reset the switch to factory defaults and apply the RCF file for EFOS 3.7.x.x or later

3.7.x.x or later non-FIPS compliant

3.4.4.6 (or later 3.4.x.x)

Downgrade EFOS using method 1. Reset the switch to factory defaults and apply the RCF file for EFOS 3.4.x.x

3.7.x.x or later non-FIPS compliant

Install the new EFOS image using method 1. The configuration and license information is retained

3.7.x.x or later FIPS compliant

3.7.x.x or later FIPS compliant

Install the new EFOS image using method 1. The configuration and license information is retained

Steps to upgrade to/from a FIPS compliant EFOS version

Non-FIPS compliant

FIPS compliant

Installation of the EFOS image using method 2. The switch configuration and license information will be lost.

FIPS compliant

Non-FIPS compliant

Important Note that after upgrading BES-53248 cluster switches from EFOS 3.3.x.x or 3.4.x.x to EFOS 3.7.0.4 or 3.8.0.2, Inter-Switch Links (ISLs) and port channels are marked in the Down state. See this KB article for further details.
Steps
  1. Connect the BES-53248 cluster switch to the management network.

  2. Use the ping command to verify connectivity to the server hosting EFOS, licenses, and the RCF file.

    This example verifies that the switch is connected to the server at IP address 172.19.2.1:

    (cs2)# ping 172.19.2.1
    Pinging 172.19.2.1 with 0 bytes of data:
    
    Reply From 172.19.2.1: icmp_seq = 0. time= 5910 usec.
  3. Back up the current active image on cs2:

    show bootvar

    (cs2) # show bootvar
    
     Image Descriptions
    
     active :
     backup :
    
    
     Images currently available on Flash
    
    --------------------------------------------------------------------
     unit      active      backup        current-active    next-active
    --------------------------------------------------------------------
    
        1      3.4.3.3     Q.10.22.1     3.4.3.3           3.4.3.3
    (cs2) # copy active backup
    Copying active to backup
    Management access will be blocked for the duration of the operation
    Copy operation successful
    
    (cs2) # show bootvar
    
    Image Descriptions
    
     active :
     backup :
    
    
     Images currently available on Flash
    
    --------------------------------------------------------------------
     unit      active      backup      current-active    next-active
    --------------------------------------------------------------------
    
        1      3.4.3.3     3.4.3.3     3.4.3.3           3.4.3.3
    (cs2) #
  4. Verify the running version of the EFOS software:

    show version

    (cs2) # show version
    
    Switch: 1
    
    System Description............................. Quanta IX8-B 48x25GB SFP 8x100GB QSFP, 3.4.3.3, Linux 4.4.117-ceeeb99d, 2016.05.00.04
    Machine Type................................... Quanta IX8-B 48x25GB SFP 8x100GB QSFP
    Machine Model.................................. IX8-B
    Serial Number.................................. QTFCU38260014
    Maintenance Level.............................. A
    Manufacturer................................... 0xbc00
    Burned In MAC Address.......................... D8:C4:97:71:12:3D
    Software Version............................... 3.4.3.3
    Operating System............................... Linux 4.4.117-ceeeb99d
    Network Processing Device...................... BCM56873_A0
    CPLD Version................................... 0xff040c03
    
    Additional Packages............................ BGP-4
    ...............................................	QOS
    ...............................................	Multicast
    ............................................... IPv6
    ............................................... Routing
    ............................................... Data Center
    ............................................... OpEN API
    ............................................... Prototype Open API
  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 EFOS version. The previous image remains available as a backup.

    (cs2)# *copy sftp://root@172.19.2.1//tmp/EFOS-3.4.4.6.stk active*
    Remote Password:********
    
    Mode........................................... SFTP
    Set Server IP.................................. 172.19.2.1
    Path........................................... //tmp/
    Filename....................................... EFOS-3.4.4.6.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*
    SFTP Code transfer starting...
    
    
    File transfer operation completed successfully.
  6. Display the boot images for the active and backup configuration:

    show bootvar

    (cs2) # show bootvar
    
    Image Descriptions
    
     active :
     backup :
    
    
     Images currently available on Flash
    
    --------------------------------------------------------------------
     unit      active      backup     current-active        next-active
    --------------------------------------------------------------------
    
        1     3.4.3.3     3.4.3.3            3.4.3.3            3.4.4.6
  7. Reboot the switch:

    reload

    (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!
  8. Log in again and verify the new version of the EFOS software:

    show version

    (cs2) # show version
    
    Switch: 1
    
    System Description............................. x86_64-quanta_common_rglbmc-r0, 3.4.4.6, Linux 4.4.211-28a6fe76, 2016.05.00.04
    Machine Type................................... x86_64-quanta_common_rglbmc-r0
    Machine Model.................................. BES-53248
    Serial Number.................................. QTFCU38260023
    Maintenance Level.............................. A
    Manufacturer................................... 0xbc00
    Burned In MAC Address.......................... D8:C4:97:71:0F:40
    Software Version............................... 3.4.4.6
    Operating System............................... Linux 4.4.211-28a6fe76
    Network Processing Device...................... BCM56873_A0
    CPLD Version................................... 0xff040c03
    
    Additional Packages............................ BGP-4
    ...............................................	QOS
    ...............................................	Multicast
    ............................................... IPv6
    ............................................... Routing
    ............................................... Data Center
    ............................................... OpEN API
    ............................................... Prototype Open API

Upgrade EFOS using the ONIE OS installation

You can perform the following steps if one EFOS version is FIPS compliant and the other EFOS version is non-FIPS compliant. These steps can be used to install the non-FIPS or FIPS compliant EFOS 3.7.x.x image from ONIE if the switch fails to boot.

Note This functionality is only available for EFOS 3.7.x.x or later non-FIPS compliant.
Steps
  1. Boot the switch into ONIE installation mode.

    During boot, select ONIE when the following screen appears:

    +--------------------------------------------------------------------+
    |EFOS                                                                |
    |*ONIE                                                               |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    +--------------------------------------------------------------------+

    After selecting ONIE", the switch will then load and present you with the following choices:

    +--------------------------------------------------------------------+
    |*ONIE: Install OS                                                   |
    | ONIE: Rescue                                                       |
    | ONIE: Uninstall OS                                                 |
    | ONIE: Update ONIE                                                  |
    | ONIE: Embed ONIE                                                   |
    | DIAG: Diagnostic Mode                                              |
    | DIAG: Burn-In Mode                                                 |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    |                                                                    |
    +--------------------------------------------------------------------+

    The switch now will boot into ONIE installation mode.

  2. Stop the ONIE discovery and configure the Ethernet interface.

    Once the following message appears press <Enter> to invoke the ONIE console:

    Please press Enter to activate this console. Info: eth0:  Checking link... up.
     ONIE:/ #
    Note The ONIE discovery will continue and messages will be printed to the console.
    Stop the ONIE discovery
    ONIE:/ # onie-discovery-stop
    discover: installer mode detected.
    Stopping: discover... done.
    ONIE:/ #
  3. Configure the Ethernet interface and add the route using ifconfig eth0 <ipAddress> netmask <netmask> up and route add default gw <gatewayAddress>

    ONIE:/ # ifconfig eth0 10.10.10.10 netmask 255.255.255.0 up
    ONIE:/ # route add default gw 10.10.10.1
  4. Verify that the server hosting the ONIE installation file is reachable:

    ONIE:/ # ping 50.50.50.50
    PING 50.50.50.50 (50.50.50.50): 56 data bytes
    64 bytes from 50.50.50.50: seq=0 ttl=255 time=0.429 ms
    64 bytes from 50.50.50.50: seq=1 ttl=255 time=0.595 ms
    64 bytes from 50.50.50.50: seq=2 ttl=255 time=0.369 ms
    ^C
    --- 50.50.50.50 ping statistics ---
    3 packets transmitted, 3 packets received, 0% packet loss
    round-trip min/avg/max = 0.369/0.464/0.595 ms
    ONIE:/ #
  5. Install the new switch software:

    ONIE:/ # onie-nos-install http:// 50.50.50.50/Software/onie-installer-x86_64
    discover: installer mode detected.
    Stopping: discover... done.
    Info: Fetching http:// 50.50.50.50/Software/onie-installer-3.7.0.4 ...
    Connecting to 50.50.50.50 (50.50.50.50:80)
    installer            100% |*******************************| 48841k  0:00:00 ETA
    ONIE: Executing installer: http:// 50.50.50.50/Software/onie-installer-3.7.0.4
    Verifying image checksum ... OK.
    Preparing image archive ... OK.

    The software will install and then reboot the switch. Let the switch reboot normally into the new EFOS version.

  6. Verify that the new switch software is installed: show bootvar

    (cs2) # show bootvar
    Image Descriptions
    active :
    backup :
    Images currently available on Flash
    ---- 	----------- -------- --------------- ------------
    unit 	active 	    backup   current-active  next-active
    ---- 	----------- -------- --------------- ------------
    1 	  3.7.0.4     3.7.0.4  3.7.0.4         3.7.0.4
    (cs2) #
  7. Complete the installation.

    The switch will reboot with no configuration applied and reset to factory defaults.

Related information