OS Provisioning Issues
This section describes the known OS provisioning (deployment) issues.
Setting Baud Rate for the BIOS Console Makes OS Deployment Fail on Sun Fire V20z and V40z Servers (6322295)
The baud rate for the BIOS console must be set to 9600 (default) or OS deployment to a Sun Fire V20z or V40z server will fail. This means that you cannot change the consolebaudrate value in the load server command or the Load OS wizard in the browser interface.
Note –
If the SP console baud rate is set to something other than 9600, the OS deployment will succeed but the console through the connect server command will display garbage characters.
Workaround: You must change the baud rate for the BIOS console manually after an OS deployment. To do this, reboot the target server and enter the BIOS setup screen during the boot sequence. Consult the server's user manual to see how to change its BIOS settings.
The Same SUSE OS Profile Cannot Be Used on Sun Fire V20z/V40z Servers and Sun Fire X4000 Series Servers (6344382)
Once you load a SUSE OS profile on a Sun Fire X4000 series server, that same OS profile and associated OS distribution cannot be used on Sun Fire V20z and V40z servers. Loading a SUSE OS profile on a Sun Fire X4000 series server actually modifies the associated SUSE OS distribution, which makes that OS distribution unusable by Sun Fire V20z and V40z servers.
Note –
This issue applies to the SUSE Linux Enterprise Server 9 Base and SP1 releases. It is not a problem for SUSE Linux Enterprise Server 9 SP3 release.
Workaround: You must create separate SUSE OS distributions and OS profiles for Sun Fire V20z/V40z servers and Sun Fire X4000 series servers.
Provisioning IP Address is Not Assigned Properly When Deploying the Windows OS Using DHCP (6381141)
When you deploy a Windows OS with the networktype=dhcp attribute, the IP address assigned to the managed server after Windows is installed is the IP address specified by the bootip attribute. The IP address should be automatically assigned by the DHCP service.
Workaround: After the installation completes, reboot the managed server. The server's provisioning IP address will be correctly reassigned from the DHCP server.
OS Deployment Job Status is Incorrect (6382570)
There are situations, such as a bad disk on the managed server, when an OS deployment job status is shown as completed when the system has failed to install and is not running.
Workaround: Verify that the managed server is installed and running properly by using the serial console feature.
Creating Windows OS Distribution Fails Due to Missing RIS Host Key (6392700)
The create os command will fail for Windows if the RIS server's host key does not exist in the management server's ./ssh/known_hosts file.
Workaround: Make sure the RIS server's host key exists in the management server's ./ssh/known_hosts file. Manually logging into the RIS server from the management server using the ssh command will automatically create a host key.
Creating OS Distributions with Same Name Not Supported (6393802)
The create os command allows you to create OS distributions with the same name. Although this is allowed, it is not recommended and it will cause naming collisions.
Workaround: Always make OS distribution names unique. If you end up having the same name for multiple OS distributions, you should delete the OS distributions and copy them again with unique names. You may have to delete all the corresponding OS profiles used by both OS distributions in order to delete them.
Creating OS Profiles with Same Name Not Supported (6404428)
The create osprofile command allows you to create OS profiles with the same name. Although this is allowed, it is not recommended and it will cause naming collisions.
Workaround: Always make OS profile names unique. If you end up having the same name for multiple OS profiles, you should delete the OS profiles and create them again with unique names.
Creating Windows OS Distribution Fails Due to Upgrade Problem (6405983)
If you upgrade from N1SM version 1.2 to 1.3, the create os command will fail for Windows with the following error message:
Error 1: Description: INFO : Info: 2003SE : windows : x86 INFO : Info 2: DBD::Pg::db do failed: ERROR: Relation "as_distro" has no column "ris_id" at /opt/sun/scs/lib/perl5/SCSDB.pm line 241. INFO : ERROR creating distro win2k3se32sp1 INFO : Creating windows distrobution failed |
Workaround: You must perform the following procedure on the management server and try the create os command again:
-
Become root on the management server.
-
Start the N1SM database program:
-
For Linux management server:
# /opt/sun/scs/sbin/db_tool.pl psql
-
For Solaris management server:
# /opt/SUNWscs/sbin/db_tool psql
-
-
Add a missing column to the as_distro table:
Welcome to psql 7.3.9-RH, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help on internal slash commands \g or terminate with semicolon to execute query \q to quit mgmt=> alter table as_distro add column ris_id integer; ALTER TABLE mgmt-> \q -
Create a new directory:
# mkdir /var/opt/sun/scs/share/allstart/config/subnet
Blank Error Messages Displayed for OS Deployments Due to Exceeding Job or Job Step Timeout Value (6405994)
When deploying an OS on a large number of managed servers, the OS deployments may fail due the OS deployment jobs exceeding the job or job step timeout value. When this situation occurs, the job indicates the error but the error description is blank and the install may have actually succeeded. An example follows:
bash-3.00# n1sh show job 12 Job ID: 12 Date: 2006-03-29T01:06:53+0000 Type: Load OS Status: Error (2006-03-29T03:07:00+0000) Command: load group sparc-srvrs osprofile sol-sparc networktype=static ip=10.0.108.81-10.0.108.90 Owner: root Errors: 10 Warnings: 0 Steps ID Type Start Completion Result 1 Acquire Host 2006-03-29T01:06:54+0000 2006-03-29T01:06:54+0000 Completed 2 Acquire Host 2006-03-29T01:06:54+0000 2006-03-29T01:06:54+0000 Completed . . Servers 3 through 28 . 29 Acquire Host 2006-03-29T01:06:56+0000 2006-03-29T01:06:57+0000 Completed 30 Acquire Host 2006-03-29T01:06:56+0000 2006-03-29T01:06:57+0000 Completed 31 Execute Java 2006-03-29T01:06:56+0000 2006-03-29T03:06:58+0000 Error 1 32 Execute Java 2006-03-29T01:06:56+0000 2006-03-29T03:06:58+0000 Error 2 33 Execute Java 2006-03-29T01:06:56+0000 2006-03-29T03:06:58+0000 Error 3 34 Execute Java 2006-03-29T01:06:56+0000 2006-03-29T03:06:58+0000 Error 4 35 Execute Java 2006-03-29T01:06:56+0000 2006-03-29T03:06:58+0000 Error 5 36 Execute Java 2006-03-29T01:06:56+0000 2006-03-29T03:06:58+0000 Error 6 37 Execute Java 2006-03-29T01:06:57+0000 2006-03-29T03:06:58+0000 Error 7 38 Execute Java 2006-03-29T01:06:57+0000 2006-03-29T03:06:58+0000 Error 8 39 Execute Java 2006-03-29T01:06:57+0000 2006-03-29T03:06:58+0000 Error 9 40 Execute Java 2006-03-29T01:06:57+0000 2006-03-29T03:06:58+0000 Error 10 Errors Error 1: Description: Error 2: Description: . . Blank error messages 3 through 8 . Error 9: Description: Error 10: Description: |
Workaround: Increase the job timeout value using n1smconfig or try to reduce the reasons for exceeding the existing timeout value, for example, network latency problems. Also, it may be possible that some of the OS deployments did succeed. You can verify whether a server installed properly by viewing the OS Usage column in the All Servers page or by using the Serial Console to log into the server.
OS Deployments Fail on Newer Sun Fire V20z Servers When Specifying bge1 Device Path for bootpath Attribute (6346563)
As documented in the N1SM product documentation, the bge1 device path for Sun Fire V20z servers is /pci@0,0/pci1022,7450@a/pci17c2,10@3. However, when specifying the bge1 device path for the bootpath attribute, the OS deployments will fail on newer Sun Fire V20z servers because the bge1 device path has changed.
Workaround: On newer Sun Fire V20z servers, use the following bge1 device path for the bootpath attribute: /pci@0,0/pci1022,7450@a/pci17c2,10@2,1
- © 2010, Oracle Corporation and/or its affiliates