Chapter 4 Troubleshooting

This chapter provides a list of error messages and problems you might encounter while installing the Sun N1 System Manager, and procedures for resolving the errors. The following topics are discussed:

• General Information

• Error Messages

• Problems

• Management Server Configuration

• Provisionable Server Firmware

General Information

This section provides information concerning N1 System Manager operational processes.

N1 System Manager Cannot Be Used to Manage System Management Servers

Do not use the N1 System Manager to manage servers that have system management software installed on them such as Sun Management Server, Sun Control Station, and any other system management applications including the N1 System Manager.

Discovery of Servers in the Factory Default State

If discovery is attempted on a provisionable server that is in the factory default state, the N1 System Manager discovery process will automatically attempt to configure the SSH and IPMI accounts on the provisionable server as part of discovery as shown in the following tables.

The discovery process will configure credentials as follows:

Table 4–1 SPARC Architecture Provisionable Server Default Credentials

Type	Telnet Login	Telnet Password
Netra 240 and 440	admin	admin
Sun Fire V210, V240, and V440	admin	admin
Sun Fire T1000 and T2000	admin	admin

Table 4–2 x86 Architecture Provisionable Server Default Credentials

Type	SSH Login	SSH Password	IPMI Login	IPMI Password	SNMP Read Community String
Sun Fire V20z and V40z	admin	admin	-	admin	public
Sun Fire X2100	-	-	Admin	admin	-
Sun Fire X4100 and X4200	root	changeme	root	changeme	public

If you have specified the SSH and IPMI login accounts and passwords, the discovery process will configure the provisionable server using the user-specified credentials. If only one credential is specified, the missing credential will be configured with one of the defaults specified above.

If you want to disable auto configuration, add the following line to the file /etc/opt/sun/n1gc/domain.properties before you run discovery:

com.sun.hss.domain.internal.discovery.initializeDevice=false

The N1 System Manager must be restarted for auto configuration disabling to take effect. Note that once auto configuration is disabled, any servers in factory default state cannot be discovered until their SSH and IPMI accounts are configured. For further information, see Setting Up Provisionable Servers in Sun N1 System Manager 1.2 Site Preparation Guide.

DHCP Service Conflict With N1 Grid Service Provisioning System

If you are using both the N1 System Manager and the N1 Grid Service Provisioning System with the ISP plug-in, you must choose which product you want to use for OS deployment for a given target set of servers. Based on the product chosen for OS deployment, you must ensure that the DHCP service supplied by the other product is manually shut down (as the root user) using operating system commands. Failure to shut the service down might result in unreliable behavior of OS deployment operations as well as potential network related problems.

Error Messages

This section lists the error messages and resolutions for problems that might occur while installing the Sun N1 System Manager.

[alert] httpd: Could not determine the server's fully qualified domain name, using 129.123.111.12 for ServerName scs-httpd: Fri Nov 19 12:47:34 PST 2004 : Daemon started (pid=1473 1485 1486..

Cause:

The system cannot determine the server's fully qualified domain name because the system file /etc/resolv.conf is not configured correctly.

Solution:

Update the /etc/resolv.conf file as directed by To Update the /etc/resolv.conf File.

Error waiting for SPS to start.

Cause:

Incorrect entry in the /etc/hosts file.

Solution:

Update the /etc/hosts as directed by To Update the /etc/hosts File.

An exception occurred trying to update SP-IPaddress. Please refer to the log file for more information.

Cause:

Firmware versions 2.2 and above for the Sun Fire V20z servers do not support the PIC firmware upgrade. The upgrade of PIC firmware will fail, and the job step will show the above error message.

Solution:

Do not load PIC firmware to the Sun Fire V20z servers.

Connect to management server url:443 failed (Connection refused)

Description:

When entering the Sun N1 System Manager server URL using the format https://servername, where servername is the name of the management server, the above error message is displayed.

Cause:

The system file /etc/resolv.conf is not configured correctly.

Solution:

Update the /etc/resolv.conf as directed by To Update the /etc/resolv.conf File.

Fatal error: Command failed for target `Makefile'

Example:

Writing Makefile for Locale::gettextMakefile out-of-date with respect to/usr/perl5/5.8.4/lib/i86pc-solaris-64int/Config.pm/usr/perl5/5.8.4/lib/i86pc-solaris-64int/CORE/config.hCleaning current config before rebuilding Makefile... make -f Makefile.old clean > /dev/null 2>&1 || /bin/sh -c true/usr/bin/perl Makefile.PLWriting Makefile for Locale::gettext ==> Your Makefile has been rebuilt. <== ==> Please rerun the make command. <==false *** Error code 255make: Fatal error: Command failed for target `Makefile'

Cause:

The system date is incorrect.

Solution:

Set the system date.

Starting dhcpd: [Failed]

Description:

dhcpd fails to start during system boot. This message is normal if Sun N1 System Manager configuration has not been performed.

Solution:

Configure the N1 System Manager system as described in Configuring the N1 System Manager System.

Problems

Cannot discover a provisionable server.

Cause:

The provisionable server firmware might be too old.

Solution:

Verify the firmware version and, if necessary, update the firmware as described in Provisionable Server Firmware.

Firmware update for Sun Fire V20z or Sun Fire V40z fails.

Cause:

Auto-negotiate link speed has not been enabled on the management network switch.

Solution:

Enable auto-negotiate link speed on the management network switch for all management network connections.

management server IP address resolves to 127.0.0.1 instead of a real IP address

Cause:

/etc/hosts does not contain an IP address and server name assignment for the management server.

Solution:

Update the /etc/hosts file as described in To Update the /etc/hosts File.

Unable to log onto a provisionable server management processor.

Cause:

The service processor account and password are not known.

Solution:

Reset the service processor accounts to the factory defaults as described by the hardware documentation

Management Server Configuration

This section provides the procedures for resolving problems with the management server configuration files.

To Update the /etc/hosts File

Step

Edit /etc/hosts and ensure that the entries are similar to the following example:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1           localhost
111.222.333.44     machine-name loghost

where 111.222.333.44 is the IP address of the N1 System Manager server, and machine-name is the name of the N1 System Manager management server.

For example, if the machine name is n1manager, and the assigned IP address for eth0 is 129.123.111.12, then the /etc/hosts file should contain the following settings:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1          localhost.localdomain localhost
129.123.111.12     n1manager loghost

You must reboot the system after updating the /etc/hosts file.

To Update the /etc/resolv.conf File

Step

Edit /etc/resolv.conf and ensure that the entries are similar to the following:

nameserver server 1 IP address
nameserver name server 2 IP address
nameserver name server 3 IP address
domain your-domain-name
search your-domain-name

For example, assume the IP address of the first DNS server is 129.123.111.12, the second DNS server is 129.123.111.24, and the third DNS server is 129.123.111.36. If your company domain name is mydomain.com, then the /etc/resolv.conf file would contain the following lines.

nameserver 129.123.111.12
nameserver name 129.123.111.24
nameserver name 129.123.111.36
domain mydomain.com
search mydomain.com

To Disable Provisionable Server Automatic Configuration

The following procedure disables the automatic configuration of provisionable servers during discovery.

Step

Edit the /etc/opt/sun/n1gc/domain.properties file and add the following line to the file:

com.sun.hss.domain.internal.discovery.initializeDevice=false

The N1 System Manager system must be restarted for auto configuration disabling to take effect. Note that once auto configuration is disabled, any servers in a factory default state cannot be discovered until their SSH and IPMI accounts are configured. For further information, see Setting Up Provisionable Servers in Sun N1 System Manager 1.2 Site Preparation Guide.

Provisionable Server Firmware

This section provides the list of supported provisionable server firmware versions, and procedures for verifying, downloading, and updating the provisionable server firmware.

The following table lists supported firmware versions by machine type.

Provisionable Server   Type	Minimum	Best Practice
Netra 240 and 440 ALOM	1.4	1.5.3
Sun Fire T1000 ALOM	6.1.0	6.1.0
Sun Fire T2000 ALOM	6.0.1	6.0.1
Sun Fire V20z and V40z SP	Service Processor: 2.1.0.5	Service Processor: 2.3.0.11
Sun Fire V20z BIOS	1.27.4	1.33.5.2
Sun Fire V40z BIOS	1.27.4	2.33.5.2
Sun Fire V210, V240, and V440 ALOM	1.4	1.5.3
Sun Fire X2100 SP	4.0.9	4.11
Sun Fire X2100 BIOS	1.0.0	1.0.3
Sun Fire X4100 and X4200	1.0	1.0

To verify a provisionable server's firmware version, proceed as described in To List the Firmware Updates Installed on a Provisionable Server in Sun N1 System Manager 1.2 Administration Guide.

If the firmware version cannot be reported by the N1 System Manager, one or all of the following situations might be the cause:

• The IP address of the provisionable server's management processor has not been set, and thus the server cannot be discovered.

  Check whether the management processor IP address has been set and, if it has been set, whether it is accessible by the N1 System Manager.

  If the management processor IP address is not correct, assign an IP address to the processor as directed by the hardware documentation.

  If the IP address is correct, go to the next item in this list.

• The provisionable server's management processor account credentials (login account and password) are not recognized by the N1 System Manager. Check the credentials used by the N1 System Manager, and then try accessing the provisionable server's management processor account. For information about the processor accounts, see Discovery of Servers in the Factory Default State.

  If you cannot access the management processor, reset the provisionable server to the factory defaults as directed by the hardware documentation, and reassign an IP address to the provisionable server's management processor. When you have completed resetting the provisionable server, run discovery on the server as described in Discovering Servers in Sun N1 System Manager 1.2 Administration Guide.

  If discovery is successful, verify the firmware version as described in To List the Firmware Updates Installed on a Provisionable Server in Sun N1 System Manager 1.2 Administration Guide. If the firmware version still cannot be reported by the N1 System Manager, update the firmware to a supported version as directed by the hardware documentation.