JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Sun Datacenter InfiniBand Switch 36

Product Notes for Firmware Version 2.0

search filter icon
search icon

Document Information

Using This Documentation

1.  Sun Datacenter InfiniBand Switch 36 Product Notes

Known Problems

Hardware Information and Issues

Service an Undervoltage Condition

Supported Fan Configuration

Software Information and Issues

Main Board, Management Controller, and Chassis Serial Numbers

Firmware Version Numbers

Time Zone Support

Firmware Update Considerations

High Availability in Partitions

Email Alert Rules

Commands Available to Restricted Linux Shells

Documentation Information and Issues

smpartition Command Guidelines

Declaration of Conformity

SNMP V3 Protocol Passwords

Upgrading the Switch Firmware

Acquire the Switch Firmware Package (CLI)

Upgrade the Switch Firmware (CLI)

Documentation Information and Issues

smpartition Command Guidelines

When partitioning the InfiniBand fabric with the smpartition command, consider these guidelines during the configuration session:

Declaration of Conformity

To receive a copy of the latest Declaration of Conformity for the switch, either contact your local Oracle sales representative or create an online request at the following URL:

SNMP V3 Protocol Passwords

In sections of Switch Remote Management, authentication and privacy passwords are described for SNMP service user accounts and SNMP V3 protocol commands. For the user accounts and commands, the MD5 and SHA authentication passwords are 8 to 12 characters in length, and the DES privacy password must be exactly 8 characters long.

Upgrading the Switch Firmware

In Switch Remote Management, firmware version numbers are provided as x.y, x.y.z, and x.y.z-w. Currently, these numbers are 2.0, 2.0.8, and 2.0.8-1 respectively. The following two procedures describe how to acquire and upgrade the firmware through the Oracle ILOM CLI.

Note - The switch must have atleast version 1.1.3 firmware installed before the two following procedures can be used. Refer to Switch Remote Management, installing the firmware, for more information.

Acquire the Switch Firmware Package (CLI)

  1. Open a web browser on a host that is on the same Ethernet network as the management controller to receive the firmware update.
  2. Go to this URL.

    Oracle's My Oracle Support page is displayed.

  3. Sign in if you already have an account.

    The dashboard page is displayed.

    Note - If you do not have an account, you must register.

  4. Click the Patches & Updates tab.

    The Patches and Updates page is displayed.

  5. In the Patch Search window, click the Search tab.

    The Patch Search window updates.

  6. Click the Product or Family (Advance) link.

    The Patch Search window updates.

  7. In the Product Is drop-down menu, select Sun Datacenter InfiniBand Switch 36.
  8. In the Release Is drop-down menu, select Sun Datacenter InfiniBand Switch 36 x.y.z.

    Where x.y.z is the version number of the firmware package to be acquired. For example, 2.0.8.

  9. Click outside of the drop-down menu.
  10. Click Search.

    The Patch Search window expands with the search results.

  11. In the Patch Name column, click the respective patch number link.

    For example, 16294964. The Patch Search window reformats.

  12. Click Read Me to display the README file.
  13. Click Download.

    The File Download window opens.

  14. Click the link to initiate the download.

    For example,

  15. Indicate where the file should be saved.

    The file is downloaded and saved.

  16. In your receiving directory, decompress the file.

    The firmware is in the SUN_DCS_36p_x.y.z.tar.gz file.

    The README file contains the latest information about the firmware release.

  17. Unpack the .gz file.
    $ gtar -zxvf SUN_DCS_36p_x.y.z.tar.gz

    The extracted files are displayed.

  18. Move the switch firmware package (filename.pkg) to a directory on a host that is accessible by Oracle ILOM.
  19. Upgrade the switch firmware.

    See Upgrade the Switch Firmware (CLI).

Upgrade the Switch Firmware (CLI)

Note - If you are going to downgrade the firmware to a version earlier than 2.0, you must remove user partitions and depopulate the Subnet Manager nodes list. Refer to Switch Administration, removing partitions for firmware downgrade.

  1. Open an SSH session as user root and connect to the management controller by specifying the controller's host name.

    For example:

    % ssh -l root switch_name
    root@switch_name's password: password

    where switch_name is the host name of the management controller. Initially, the password is changeme.

  2. If the Subnet Manager is running on the management controller, disable the Subnet Manager with the disablesm command.
    # disablesm
    Stopping partitiond daemon.                                [  OK  ]
    Stopping IB Subnet Manager..                               [  OK  ]
  3. Verify that there is at least 80 MB available in the / filesystem.
    # df -h /
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/hda2             471M  276M  172M  62% /

    In this example, there are 172 MB available. If not enough space is available, you must delete or move files from the / filesystem.

  4. Verify that there is at least 120 MB available in the /tmp directory.
    # df -h /tmp
    Filesystem            Size  Used Avail Use% Mounted on
    tmpfs                 250M  240K 249M 1% /tmp

    In this example, there are 249 MB available. If not enough space is available, you must delete files from the /tmp directory.

  5. Verify that there is at least 120 MB free memory available.
    # free -m
                     total       used       free     shared    buffers     cached
    Mem:           498        104        393          0         12         47
    -/+ buffers/cache:         45        453
    Swap:            0          0          0

    In the -/+ buffers/cache: row of the free column, there should be at least 120 MB free memory. In this example, there are 453 MB available. If not enough memory is available, you must exit nonessential applications that are running.

  6. Start the Oracle ILOM shell.
    # spsh
    Oracle(R) Integrated Lights Out Manager
    Version ILOM 3.0 r47111
    Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.

    You are now in the Oracle ILOM shell.

    You can use the exit command to return to the Linux shell.

  7. Begin the upgrade process.
    -> load -source URI/pkgname


    • URI is the uniform resource indicator for the host where the switch firmware package is located. The FTP and HTTP protocols are supported.

    • pkgname is the name of the firmware package in the transfer directory.

    For example, using the FTP protocol:

    -> load -source ftp://root:changeme@
    Downloading firmware image. This will take a few minutes.

    Note - If you are upgrading from firmware version 2.0.X, you can use the -force option to disable version number checking, and force the upgrade.

    The firmware is downloaded. The upgrade begins. A caution is displayed, and you are asked to commit to the upgrade.

    NOTE: Firmware upgrade will upgrade firmware on SUN DCS 36p firmware.
             ILOM will enter a special mode to load new firmware. No other tasks 
             should be performed in ILOM until the firmware upgrade is complete. 
    Are you sure you want to load the specified file (y/n)?
  8. Answer y to the prompt to commit to the upgrade.

    The upgrade begins.

    Setting up environment for firmware upgrade. This will take few minutes.
    Starting SUN DCS 36p FW update
    Performing operation: I4 A
    I4 fw upgrade from 7.3.0(INI:4) to 7.4.1010(INI:4):
    Upgrade started...
    Upgrade completed.
    INFO: I4 fw upgrade from 7.3.0(INI:4) to 7.4.1010(INI:4) succeeded
    Summary of Firmware update 
    I4 status                :  FW UPDATE - SUCCESS
    I4 update succeeded on   :  A
    I4 already up-to-date on :  none
    I4 update failed on      :  none
    Performing operation: SUN DCS 36p firmware update
    SUN DCS 36p upgrade from 1.3.3-2 to 2.0.8-1:
    Upgrade started...
    Upgrade completed.
    INFO: SUN DCS 36p upgrade from 1.3.3-2 to 2.0.8-1 succeeded
    Firmware update is complete.
    ILOM will be restarted and will take 2 minutes to come up.
    You will need to reconnect to Integrated Lights Out Manager.
    Stopping any already executing ILOM daemons
    Starting event manager
    Starting log manager
    Starting ILOM IPMI stack
    Started ILOM IPMI stack
    Starting lumain
    Starting luproxy
    Starting ealertd
    Starting web server
    Starting SNMP
  9. Reboot the switch to enable the new firmware.

    Refer to Switch Administration, restarting the entire switch.

    Note - The restart process takes between 4 to 5 minutes to complete. The Oracle ILOM stack requires at least 2 minutes to become operational after a reboot.

  10. If the Subnet Manager was previously disabled, log in as the root user and enable the Subnet Manager.
    % ssh -l ilom-admin switch_name
    ilom-admin@switch_name's password: password
    -> show /SP/Fabric_Mgmt
    NOTE: show on Fabric_Mgmt will launch a restricted Linux shell. 
             User can execute switch diagnosis, SM Configuration and IB
             monitoring commands in the shell. To view the list of commands,
             use "help" at rsh prompt. 
             Use exit command at rsh prompt to revert back to
             ILOM shell.
    Starting IB Subnet Manager.                                [  OK  ]
    Starting partitiond daemon.                                [  OK  ]
  11. Verify the firmware version.
    SUN DCS 36p version: 2.0.8-1
    Build time: Feb  6 2013 09:09:09
    SP board info:
    Manufacturing Date: 2009.12.08
    Serial Number: "NCD4I0133"
    Hardware Revision: 0x0006
    Firmware Revision: 0x0102
    BIOS version: NOW1R112
    BIOS date: 04/24/2009

    In the first line of the output is SUN DCS 36p version x.y.z-w, where x.y.z-w is the version of the firmware upgraded (or downgraded). For example, 2.0.8-1.

  12. Verify the firmware integrity.
    Checking all present packages:
    ........................................................................... OK
    Checking if any packages are missing:
    ........................................................................... OK
    Verifying installed files:
    ........................................................................... OK