Chapter 3 Discovery Problems

This chapter lists Sun N1 System Manager problems that can occur during discovery of manageable servers, their causes, and the solution for each problem. The following topics are discussed:

• Cannot Discover a Manageable Server

• Unable to Log In to a Managed Server Management Processor

Cannot Discover a Manageable Server

Failure to discover a manageable server can be caused by many different issues. This section provides guidelines and references to help you resolve each issue.

The following topics are discussed:

• Incorrect Firmware Is Installed on the Managed Server

• Maximum Number of SNMP Destinations Has Been Exceeded

• RSC Servers Must Be Powered Off for Discovery to Succeed

• V20z or V40z Discovery Fails With Error Cannot Open IPMI Session

Incorrect Firmware Is Installed on the Managed Server

The managed server firmware version might be less than the minimum supported version.

Verify the firmware version and, if necessary, update the firmware. For a list of qualified firmware versions, see Manageable Server Firmware Requirements in Sun N1 System Manager 1.3 Site Preparation Guide.

Maximum Number of SNMP Destinations Has Been Exceeded

The service processor of the Sun Fire V20z and V40z servers has a limit of three SNMP destinations. If there are more than three SNMP destinations for a V20z or a V40z server, discovery will fail. The failure occurs because the N1 System Manager adds another SNMP destination to the service processor during discovery.

The SNMP destinations can be configured in a service processor by N1 System Manager or some other management software. You can delete entries from the SNMP destinations if you know that the SNMP destination entry is no longer needed.

Perform the following steps to view the service processor SNMP destinations and then delete at least one SNMP destination:

1. Log into the V20z or V40z service processor admin account using SSH.

2. To display the server's current SNMP destinations, type the command sp get snmp-destinations.

   The SNMP destinations appear in the output.

   If there are more than three SNMP destinations, you must delete SNMP destinations until there are no more than three SNMP destinations.

3. To delete an SNMP destination on the service processor, use the command sp delete snmp-destination where snmp-destination is the SNMP destination to be deleted..

   Use the delete command with caution because some other management software might need the entry for monitoring. A manageable server's SNMP destination is deleted, however, when the server is deleted from the N1 System Manager using the delete server command. Always use the delete server command when removing a manageable server.

RSC Servers Must Be Powered Off for Discovery to Succeed

Manageable servers based on the Remote System Control (RSC) technology, such as Sun Fire V490 and V890 series servers, must be powered off before they can be discovered by N1 System Manager. RSC-based servers must remain powered off until discovery is complete and discovery has been confirmed by using the show server command.

The first time the show server command is used to identify a newly discovered RSC server, the command can take up to 5 minutes to complete.

The console of an RSC server must not be in use when being discovered. These servers must also be bench configured prior to discovery. For details on bench configuration of RSC servers, see Preparing RSC-based Manageable Servers in Sun N1 System Manager 1.3 Site Preparation Guide.

If the RSC manageable server was not powered off before being discovered by N1 System Manager, the server MAC address cannot be detected. Subsequent attempts to load an OS on the server fail with the following message:

Operation failed

In this case, stop the managed server:

N1-ok> stop server server force true

Refresh the managed server to retrieve the server's MAC address:

N1-ok> set server server refresh

This command can take up to 5 minutes to complete. Once complete, an OS can be provisioned on to the RSC server using N1 System Manager.

V20z or V40z Discovery Fails With Error Cannot Open IPMI Session

Discovery cannot open an IPMI session to a Sun Fire V20z or a V40z server if the IPMI password on the V20z or V40z is missing or has been reset.

To reset the IPMI password and then discover the server, proceed as follows:

1. Open a terminal window and log in to the V20z or V40z service processor admin account using SSH.

2. Type the command ipmi get channels followed by the command ipmi reset -a to reset the IPMI password. You are prompted to confirm the new password.

   For example, assume the server management processor IP address is 10.0.5.3, and that the default ssh account name admin and the default password admin have not been changed:

   bash-3.00# ssh -l admin 10.0.5.3 admin@10.0.5.3's password: Sun Microsystems IPMI v2.0 Service Processor Version: V2.4.0.6 localhost $ localhost $ ipmi get channels Channel Status lan enabled sms enabled localhost $ ipmi reset -a localhost $ localhost $ ipmi enable channel lan Password: example Confirm password: example

3. Rerun discovery from the N1 System Manager commandline interface for the V20z or V40z, using the IPMI password you specified.

For example:

N1-ok > discover 10.0.5.3 ssh=admin/admin ipmi=/example

Unable to Log In to a Managed Server Management Processor

If the service processor account and password are not known, reset the service processor accounts to the factory defaults as described by the hardware documentation.