Servers discovered manually are not automatically monitored for hardware health, as indicated in Table 4–1.
Before you discover a new hardware component, read Chapter 2, Sun N1 System Manager System and Network Preparation, in Sun N1 System Manager 1.3 Site Preparation Guide for details on setting up a managed server for discovery.
The N1 System Manager can provision an OS on a managed server that was discovered by OS-based discovery, only if that managed server and target OS combination is supported by the N1 System Manager.
Manual discovery of diskless clients is not supported.
The manageable server must be powered on before being discovered.
When using the N1 System Manager to load an OS on managed servers that were discovered manually, the manualnetboot feature must be turned on. For more information, see Sun N1 System Manager 1.3 Operating System Provisioning Guide.
Use the discover command to discover a server manually.
N1-ok> discover file format file [group group] |
The file must be a fully qualified path to an XML file, containing the manageable server's MAC address. To manually discover a group of manageable servers with one command, their MAC addresses must be specified in the same XML file.
This command makes the servers part of the same group.
See discover in Sun N1 System Manager 1.3 Command Line Reference Manual for more details about the syntax used in the discover command.
After successful completion of the Discovery job, a managed server is identified by its management name. This name is the name you provided in the XML file. You can rename discovered servers at any time.
The following example of the discover command shows how to discover manageable servers manually. The servers have the following MAC addresses: 00:11:22:33:44:55 and 00:11:22:33:44:77.
N1-ok> discover /net/machine1.brasil/XMLfiles/manual_disco.xml format file group group1 Job 1 started. |
The XML file contains the machine names and MAC addresses for manual discovery.
<?xml version='1.0' encoding='utf-8'?> <servers> <server name="galaxy1" model="X4100" guid="01234567-89ab-cdef-0123-456789abcdff"> <ethernetPort name="GB_0" mac="00:11:22:33:44:55"/> <ethernetPort name="GB_1" mac="00:11:22:33:44:56"/> </server> <server name="galaxy2" model="X4100" guid="01234567-89ab-cdef-0123-456789abcdee"> <ethernetPort name="GB_0" mac="00:11:22:33:44:77"/> <ethernetPort name="GB_1" mac="00:11:22:33:44:76"/> </server> </servers> |
The guid attribute is optional.
The group subcommand adds the successfully discovered servers into a server group called group1.
The following example command shows how to view the Discovery job and the job status.
N1-ok> show job all Job ID Date Type Status Owner 3 2005-06-28T06:53:53-0700 Discovery Completed root |
The following example command shows how to verify that the discovered servers were added to the server group.
N1-ok> show group all Name us Jobs Servers Spare group1 2 |
Some commands are not supported for managed servers that were discovered manually. See Capability of Managed Servers Based on Discovery for details about which features are not available for managed servers that were discovered manually. Unsupported commands generate the following error:
Unsupported operation
This error is displayed either in the job status or immediately in the command line interface.
Discovery can fail with the following error message:
Check the Standard Output field for possible reasons for this failure
To see the Standard Output field, check the job details in the browser interface or by using the show job command with the job number of the discovery job that failed.
Discovery might fail due to a firmware version problem with drivers. See Cannot Discover a Manageable Server in Sun N1 System Manager 1.3 Troubleshooting Guide for details.
Sun N1 System Manager 1.3 Site Preparation Guide and Troubleshooting Discovery
Open the server's serial console. To view information about accessing a server's serial console, in the Sun N1 System Manager Online Help, find the topic `To Open the Serial Console for a Server'.