Documentation, Support, and Training
Evaluating Product Compatibility
Form-Factor Physical Characteristics
Warranty and Technical Support
System Requirements and Options
Installing Optional Components
Preparing to Install the Blade Server
Power and Thermal Distribution
Required Cooling and Blade Impedance Curve
Local Network IP Addresses and Host Names
Connect the External I/O Cables
Connect Cables to a System Console Running the Oracle Solaris OS
Connect Cables to a System Console Not Running Oracle Solaris OS
Insert and Latch the Blade Server
Software and Firmware Upgrades
Software and Firmware Upgrades
Firmware and Blade Server Management
Creating a Boot Disk Server and Adding Clients
Create a Boot Server for Diskless Clients
Compact Flash Formatting for the Oracle Solaris OS
Advanced Rear Transition Module Connectors (Zone 3)
Locate Base MAC Address on Blade Server
Configuring and Using Serial Over LAN
Shut Down OS and Deactivate the Blade Server
Power Off and Remove the Blade Server
A MUX controller and ShMM configuration is available for use on the Netra SPARC T3-1BA blade server to multiplex 10GbE NIU ports to Zone 2 (midplane) and/or to Zone 3 (ARTM).
MUX control configurations take effect during the blade activation following the configuration change.
Both NIU ports are independently configurable.
MUX configuration is persistent across reboots, resets, and hotswaps.
MUX configuration remains persistent for the slot, so that if a blade is replaced with another Netra SPARC T3-1BA blade server, the new blade assumes the previous configuration.
Note - The host must be configured to match the MUX configuration.
If you are using blade servers in a Sun Netra CT900 ATCA chassis, a complete end-to-end solution is provided. The MUX feature is implemented through the ShMM firmware and IPMI commands on the IPMC. These commands extend MUX configuration access to the management software so that during blade server hot-swaps, the MUX configuration is persistent across blade server activations and deactivations.
If you are using the Netra SPARC T3-1BA blade server in a third-party chassis (which does not have the Sun Netra CT900 ATCA chassis ShMM management software implemented), you can save MUX configurations in a configuration file or in persistent storage managed by system management software. When the system management software detects blade server activation, it sends the command to set MUX to the programmed state. Because management software sends the command during every blade server activation, the configuration is persistent across blade server deactivation and activation.
Be aware of the following possibilities when multiplexing zones:
MUX and payload driver configuration could go out of sync, requiring a system administrator to make sure they are set to the same configuration.
Midplane FRUID record could be corrupted when updating with the MUX configuration.
Third-party shelf management software might block updates to the midplane FRUID.
To multiplex blade servers, refer to the following documentation:
For ShMM commands, refer to the Sun Netra CT900 Server Administration and Reference Manual.
For IPMI commands, refer to the Sun Netra CT900 Server Software Developer’s Guide.