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)

Known Problems

The following table describes known problems with the switch.

Setting an alert rule to ipmipet sometimes does not work.
There is no impact to the InfiniBand fabric.

Workaround: After setting the alert rule to ipmipet, set the level to disable, and then set the level to the desired value.

Time zone setting is not preserved.
When upgrading from or downgrading to the 1.1.3 firmware version, the time zone setting is lost.

Workaround: Reconfigure the time zone setting after the firmware upgrade or downgrade. Refer to Switch Administration Guide, setting the time.

IP addresses within the Subnet Manager nodes file does not match those assigned by DHCP.
By default, the DHCP server is not assured to assign a consistent IP address to a Subnet Manager node upon reboot.

Workaround: Manually configure the DHCP server to assign a specific and unique IP address to each Subnet Manager node.

No way to set Fabric Monitor console timeout.
The Fabric Monitor will timeout after 15 minutes of idle time.

Workaround: You must login to the web interface and launch the Fabric Monitor again.

Fabric Monitor does not support Internet Explorer.
Though the Oracle ILOM web interface supports Internet Explorer, the Fabric Monitor does not.

Workaround: Use Mozilla Firefox 3.0 or 3.6.

Oracle ILOM web interface not compatible with Mozilla Firefox 6.0.
Using the Mozilla Firefox 6.0 browser, only navigational control is possible with the Oracle ILOM web interface. No informational output is displayed.

Workaround: Use Mozilla Firefox 3.0 or 3.6.

smpartition start command gives unclear message if the Subnet Manager is disabled.
If the Subnet Manager is disabled before starting a partition configuration session using the smpartition start command, confusing messages are displayed upon issuing the command.

Workaround: Ensure that the Subnet Manager is enabled before starting a partition configuration session.

checkguidfilesftree is displayed with the help all command, but is not supported.
Using the help all command within the Oracle ILOM /SYS/Fabric_Mgmt target displays the checkguidfilesftree command. This command has been deprecated and is not available.
fdconfig command is unavailable from the /SYS/Fabric_Mgmt target.
The fdconfig command is required for configuring the FabricMIB and should be available from the Oracle ILOM /SYS/Fabric_Mgmt target. The command is not available.

Workaround: Log in as the root user, where the fdconfig command is available.

Need tool to display InfiniBand topology with physical InfiniBand entities.
At present, no command provides InfiniBand fabric GUIDs, LIDs, and IB ports relationship to eachother in a simplified manner.

Workaround: Use the ibnetdiscover command.

Stopping or starting the envd daemon initiates a segmentation fault for the FabricMIB.
Stopping or starting the environment daemon on a switch running as a fabric manager or monitored by a fabric manager changes the FabricMIB configuration due to the new status of that fabric element. Should an snmpwalk of the FabricMIB be issued at the same time the FabricMIB library reloads the updated configuration, internal file pointers might be mishandled, initiating a segmentation fault.

There is no workaround at this time.

Fabric Monitor might fail to load.
During a firmware upgrade or downgrade, certain symbolic links might not be created or become lost. Consequently, the Fabric Monitor will fail to load when requested.

Workaround: Reperform the upgrade or downgrade, using the -force option.