test

Sun N1 System Manager 1.3.2 Release Notes

Issues with Sun Fire X2100 M2 or Sun Fire X2200 M2 Servers

This section describes known issues with Sun Fire X2100 M2 or Sun Fire X2200 M2 servers.

Provisioning Solaris 10 6/06 on a Sun Fire X2100 M2 Server

To provision Solaris 10 6/06 on a Sun Fire X2100 M2 server, you must perform the following steps to modify the default OS profile and specify bge0 for networkdevice in the load command. This example uses an OS profile named s10u2_x86.


N1-ok> remove osprofile s10u2_x86 partition swap
N1-ok> remove osprofile s10u2_x86 partition /
N1-ok> add osprofile s10u2_x86 partition swap device=c0d0s1 size=2048 type=swap sizeoption=fixed
N1-ok> add osprofile s10u2_x86 partition / device=c0d0s0 type=ufs sizeoption=free
N1-ok> load server ipaddress osprofile s10u2_x86 networktype=static ip=ipaddress
       console=ttyb consolebaud=9600 networkdevice=bge0
Note –

You must use the Broadcom network port (net0).

Provisioning Solaris 10 6/06 on a Sun Fire X2200 M2 Server

To provision Solaris 10 6/06 on a Sun Fire X2200 M2 server, you must perform the following steps to modify the default OS profile and specify bge0 for networkdevice in the load command. This example uses an OS profile named s10u2_x86.


N1-ok> remove osprofile s10u2_x86 partition swap
N1-ok> remove osprofile s10u2_x86 partition /
N1-ok> add osprofile s10u2_x86 partition swap device=c1d0s1 size=2048 type=swap sizeoption=fixed
N1-ok> add osprofile s10u2_x86 partition / device=c1d0s0 type=ufs sizeoption=free
N1-ok> load server ipaddress osprofile s10u2_x86 networktype=static ip=ipaddress
       console=ttyb consolebaud=9600 networkdevice=bge0
Note –

You must use the Broadcom network port (net0).

Provisioning Red Hat Enterprise Linux 3.0 AS Update 8 on a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server

To provision Red Hat Enterprise Linux 3.0 AS Update 8 on a Sun Fire X2100 M2 or Sun Fire X2200 M2 server, you must use the Broadcom network port (net0). You must also use the appropriate console and bootnetworkdevice settings to view the console output through the connect server command. Refer to the server documentation to determine which physical port is net0.

The following example is a sample command to deploy the default OS profile on a Sun Fire X2200 M2 server.


N1-ok> load server ipaddress osprofile RHEL3-U8 bootip=ipaddress networktype=static ip=ipaddress 
       bootnetworkdevice=eth2 console=ttyS1 consolebaud=115200

Provisioning SUSE Linux Enterprise Server 9 SP3 on a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server

To provision SUSE Linux Enterprise Server 9 SP3 on a Sun Fire X2100 M2 or Sun Fire X2200 M2 server, you must use the Nvidia network ports (net2 and net3). The bootnetworkdevice value must be eth1 for net2 or eth0 for net3. You must also use the appropriate console and consolebaud settings to view the console output through the connect server command.

The following example is a sample command to deploy the default profile on a Sun Fire X2200 M2 server.


N1-ok> load server ipaddress osprofile SUSE9SP3 bootip=ipaddress networktype=static ip=ipaddress 
       bootnetworkdevice=eth1 console=ttyS1 consolebaud=115200

Serial Console Is Not Available During Solaris OS Provisioning on a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server (6480994)

Workaround: View the console through the system's Web GUI during installation.

SUSE Linux Enterprise Server 9 SP3, 64–Bit OS Deployment Fails on a Sun Fire X2100 Server (6416190)

The deployment fails with the message “Reread of the partition table failed.”

Workaround: Specify hde for the device attribute value in the server's OS profile.

Rediscovery of Sun Fire X2100 M2 Systems Fail (6489463)

If you delete an existing Sun Fire X2100 server from N1 System Manager and try to rediscover it, the discovery might fail with the following error message in the job details: “Cannot set alert destination to N1 SM. Maximum destination count has reached.”

Workaround: You need to manually clear the alert destination on the managed node and run the discovery command again:

  1. Log in as root on the management server.

  2. Change directory to the ipmitool location.

    # cd /opt/ipmitool/bin/ipmitool

  3. Manually clear the alert destination on the managed node. You must know the root password of the managed node's SP.


    # ./ipmitool -H sp-ip -U root -I lan lan alert set 1 1 ipaddr 0.0.0.0

  4. Rediscover the server using the discover command.

Provisioning Firmware on a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server

You need to download the “tools and drivers iso” file for the firmware and then extract the firmware file by mounting the ISO image. After mounting the ISO image, the firmware is located in the remoteflash subdirectory and has a name similar to X2100-190_3A06.

When importing Sun Fire X2100 M2 or Sun Fire X2200 M2 firmware into N1 System Manager, there is an eight character limitation on the firmware name. N1 System Manager will allow longer names to be specified. However, any attempt to load the firmware onto a managed node will be rejected. To avoid having to recreate the firmware image later on, the best practice is to use a shorter name at the time of firmware creation.

Firmware Update May Timeout for a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server (6493791)

If the management network is slow between a managed server's SP and the N1 SM management server, the firmware update process may take longer than the default timeout (10 minutes) to complete and the firmware update job will error out.

Workaround: You need to increase the speed of the management network or increase the timeout value.

  1. Verify that the firmware update actually failed. The update might have actually completed. To verify this, perform steps 4-9 described in the workaround for Upgrading Firmware Version 1.0a/1.1 to 1.2 Is Not Supported on a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server (6492583). If the firmware has not been updated, proceed to the next step.

  2. Log in as root on the N1 SM management server.

  3. Make a new directory in the /opt/sun/n1gc/dvrs directory.


    # mkdir /opt/sun/n1gc/drvrs/resources

  4. Create a file named taurus.properties in the resources directory with the following contents. Note the value of the firmwareUpdateTimeout property, which is set to 40 minutes.

    ipmi.lan.channel=1
consoleProtocol=ssh
nicFruPattern=(.*NIC0.*)|(.*NIC1.*)
supportedModels=X2100M2,X2200M2
firmwareUpdateTimeout=2400
firmwareUpdateFinishedPattern=Update Successful
firmwareUpdateFailedPattern=fail|error
ipmi.factory_default_user_name=root
ipmi.factory_default_password=changeme

  5. Restart the N1 SM management server.


    # /etc/init.d/n1sminit stop
# /etc/init.d/n1sminit start

  6. Retry the firmware update.

Upgrading Firmware Version 1.0a/1.1 to 1.2 Is Not Supported on a Sun Fire X2100 M2 or Sun Fire X2200 M2 Server (6492583)

N1 System Manager does not fully support upgrading firmware version 1.0a/1.1 to 1.2 on the Sun Fire X2100 M2 and Sun Fire X2200 M2 servers. Though the update will actually complete successfully in all cases, N1 System Manager may report the operation as a failure depending on the server type and the firmware version being updated. Also, the CMOS checksum will be invalid and must be manually cleared to allow the system to boot properly.

Workaround: Use the following procedure to update the firmware. This procedure assumes you have already imported the firmware image into N1 System Manager using the create firmware command.

  1. Log in as root on the management server.

  2. Update the firmware on the managed server to version 1.2.


    # n1sh stop server server-name force=true
# n1sh load server server-name firmware firmware1.2-name

  3. Wait for the firmware update job to finish.

    Depending on the following upgrade path, the job may either succeed or fail.

    • 1.0a to 1.2 will fail

    • 1.1 to 1.2 will fail for the Sun Fire X2200 M2 server

  4. Connect to the console of the managed server being updated:


    # n1sh connect server servername

  5. In a different N1 SM terminal window, power off and on the managed server.


    # n1sh stop server server-name force=true
# n1sh start server server-name

    After the managed server powers on, the console window will display the BIOS POST output, which will report an invalid CMOS checksum.

  6. In the console window, press F2 to restore the defaults and allow the POST to complete.

    Note –

    If the basemanagement or osmonitor features have been enabled on the server, wait until the system fully boots up before proceeding.

  7. Exit the console window for the managed server.

  8. Refresh the system information for the managed server.


    # n1sh set server server-name refresh

  9. Verify that the firmware has been updated to version 1.2 on the managed server.


    # n1sh show server server-name | egrep 'SP|BIOS'

    The SP and BIOS versions should be updated to the latest versions.

Upgrading BIOS to Future Versions of Firmware on Sun Fire X2100 M2 or Sun Fire X2200 M2 Servers May Overwrite User Specified BIOS Settings

To update BIOS firmware, N1 System Manager uses the default native firmware update mechanism provided by the platform service processor. For some rare upgrade paths, this default behavior may result in BIOS settings reverting to optimized defaults. Depending on the operating system and platform configuration, this may require the user to manually re-apply these settings. Refer to the server documentation for additional details on which configurations are affected.

Sun Fire X2100 M2 or Sun Fire X2200 M2 Server “Unreachable” After Firmware Upgrade (6489473)

After you upgrade the firmware to version 1.2 on a Sun Fire X2100 M2 or Sun Fire X2200 M2 server, the server may occasionally change to “Unreachable” state within 5 minutes.

Workaround: You must reset the server's service processor (SP):

  1. Log in to the server's SP.


    # ssh -l sp-user sp-ip

  2. Reset the SP.


    -> reset

  3. On the management server, refresh the server's monitoring information.


    n1-ok> set server server-name refresh