|C H A P T E R 5|
This chapter contains the following sections:
To support Sun Fire B200x blades in a Sun Fire B1600 blade system chassis, you must be running System Controller firmware version 1.2. To perform the upgrade of the System Controller firmware, follow the instructions in the Sun Fire B1600 Blade System Chassis Administration Guide (Chapter 10).
There is a method described in Chapter 9 of the Sun Fire B1600 Blade System Chassis Administration Guide (on the Documentation CD) for regaining access to the System Controller if you have forgotten your password.
If you lose your password to the System Controller, the correct procedure for regaining access to the device is as follows:
1. Remove and then re-insert one of the power supplies.
2. Within five minutes of re-inserting the power supply, set up a serial connection to the SSC containing the active System Controller and log in as user admin.
For information about setting up a serial connection to the SSC, see the Sun Fire B1600 Blade System Chassis Hardware Installation Guide.
To log in, type the default user name admin and when prompted for a password, press [ENTER].:
3. At the sc> prompt, set a new password for the default user (admin).
To set a new password for user admin, type:
The password you specify can be up to eight characters long. It must begin with an alphabetic character, and it must contain at least one lower-case alphabetic character. You can use any of the following characters in the password:
4. Set up a new user name and password for yourself.
To do this, follow the instructions in Chapter 3 of the Sun Fire B1600 Blade System Chassis Administration Guide.
The following known problems apply to the current release of the System Controller firmware for this product:
where xxxxxxxx is the hexadecimal representation of an IP address. If you see an error message like this, it will be followed by a reset of the System Controller (if you are operating the chassis with a single System Controller) or a failover to the standby System Controller (if you are operating a chassis containing a redundant System Controller).
To avoid this problem make sure you configure the System Controller with a netmask that is valid for your network. If you are using DHCP to allocate IP addresses, make sure your DHCP server is configured to provide a netmask that is valid for your network.
The following known problems applied to release 1.1 of the System Controller firmware (they are fixed in release 1.2):
This problem can occur if the System Controller is reset immediately after an event has been reported on the serial console. In other words, it happens if the System Controller has not completed writing the information to its event logs when the reset is performed.
To avoid the problem, if you see an event reported on your serial console, wait at least 30 seconds before executing the resetsc or setfailover command.
The syntax of the above command is correct, but the software does not process it correctly. The consequence, if you type the command in this way, is that all FRUs in the chassis will be reset.
To avoid this problem, when you perform an externally initiated reset on a blade (by using the -x option) and you specifically do not want to receive the confirmation prompt (the -y option), make sure you separate the arguments as follows when you type the command:
where n is the number of the slot containing the blade you want to reset.
The following known problems applied to release 1.0 of the System Controller firmware (they are fixed in release 1.1):
However, when the underlying fault is removed (in other words, when the blade causing the problem is removed from the chassis), the System Controller will not report the recovery of this rail and will continue to light the service required LED on the affected PSU and on the chassis (even though service is not in fact required).
When the component causing the underlying problem has been replaced, the showplatform and showenvironment commands will correctly report that there are no faults on the system. However, the service LED on the PSU will still remain lit. To turn it off after replacing the component that caused the underlying problem, type the following commands from the System Controller's sc> prompt:
where n is either 0 or 1 depending on the Power Supply Unit involved. (You do not need to remove the Power Supply Unit.)
Note - Executing the removefru command prepares the PSU for removal but does not stop the PSU from providing power to the chassis. However, it does prevent environmental monitoring of the PSU by the System Controller. This is restored when you run the poweron psn command. Therefore, when you do this, the service LED will be reset.