Contained Within
Find More DocumentationFeatured Support Resources |  Scarica il manuale in formato PDF (632 KB)
Chapter 2 Sun N1 System Manager System and Network PreparationThis chapter provides the Sun N1 System Manager hardware and software requirements, reference architectures, and procedures for preparing your N1 System Manager components. The tasks provided in this chapter can be performed in parallel with the Microsoft Windows Remote Installation Services (RIS) server setup and with the management server preparation as described in the following sections: Note – Do not run discovery or use the N1 System Manager system until all manageable servers have been configured as described in the following sections. This chapter discusses the following topics: Sun N1 System Manager Hardware and OS RequirementsThe information in this section will help you determine what operating system, hardware, and storage resources must be allocated or acquired to implement the N1 System Manager system. This section discusses the following topics: Management Server RequirementsN1 System Manager management server hardware and operating software minimum requirements are listed in the following table. See Table 2–9 for specific management server sizing information based on the number of servers that are to be managed.  Caution – Dedicate the N1 System Manager management server only to the N1 System Manager software. Do not install other applications on the management server. The management server must not be managed by any system management software such as N1 System Manager, Sun Management Center, Sun Control Station, or any other management system. Table 2–1 Management Server Disk Space and RAM Requirements
Table 2–2 SPARC-based Management Server Supported Hardware and Operating Systems
Table 2–3 X86 and X64–based Management Server Supported Hardware and Operating Systems
A minimum of 3.0 Gbytes should be allocated for each OS distribution you plan to provision.
Note – If the server you have chosen for the management server has only two network interfaces, consider installing a third 10/100 or 10/100/1000 NIC in the N1 System Manager. A third NIC enables you to assign the management, provisioning, and data networks to separate network interfaces, and simplifies administrative tasks. The example diagrams and configurations in this document assume that an additional NIC has been installed in the management server. Manageable Server RequirementsN1 System Manager manageable server hardware and operating software requirements are listed in the following tables. Table 2–4 Manageable Server Disk Space and RAM Requirements
Table 2–5 SPARC-Based Manageable Server Supported Hardware and Operating Systems
Table 2–6 X86 and X64 Based Manageable Server Supported Hardware and Operating Systems
Note – OS discovery, OS monitoring, and software update management are not supported for managed servers running the Windows operating system. For further information about OS discovery, see Chapter 4, Discovering Manageable Servers, in Sun N1 System Manager 1.3 Discovery and Administration Guide. For further information about OS monitoring, see Chapter 6, Monitoring Servers and Server Groups, in Sun N1 System Manager 1.3 Discovery and Administration Guide. Manageable Server Firmware RequirementsThe following tables list the supported manageable server firmware versions by machine type. Refer to each server's hardware documentation for firmware verification and upgrade procedures. Note – You can also verify a managed server's firmware version as described in To List the Firmware Updates Installed on a Managed Server in Sun N1 System Manager 1.3 Operating System Provisioning Guide. This requires that Sun N1 System Manager 1.3 has been installed and configured, and the server has been discovered. Table 2–7 SPARC-based Manageable Server Firmware Requirements
Table 2–8 x86-based Manageable Server Firmware Requirements
Managed Server LimitationsThis section lists managed server hardware and network configuration limitations.
Microsoft Windows Image Server RequirementsIf you plan to provision a Windows operating system to one or more managed servers, you must install and configure a Windows Remote Installation Services (RIS) server. The Windows RIS server must be running one of the following operating systems:
For information about installing and configuring a Windows RIS server, see Setting Up a Windows Remote Installation Services Server. Recommended Switch ConfigurationYou can use a single VLAN-programmable switch to provide the management, provisioning, and data network infrastructure. However, for ease of management, you should install one VLAN-programmable switch for the management network, and a second VLAN-programmable switch for the provisioning and data network. Each management, provisioning, and data network should be assigned to separate subnets and VLANs. Note – In order to support firmware updates for the Sun Fire V20z and V40z servers, the management network switch should be configured to auto-negotiate link speed. Ethernet connectivity recommendations
Considerations:
Sun N1 System Manager Connection InformationThis section provides the connectivity requirements for the Sun N1 System Manager servers. Management Server ConnectionsA SPARC or x86 based server can be used as the management server. Each server provides at least one 10/100/1000 (1-Gbit) network interface port, but adding additional Gbit network interface cards to the management server increases ease of management and physical separation of the corporate and provisioning networks. If you do not install additional NICs in your management server, you can configure your network to route the corporate and provisioning networks through a single 1-Gbit port as illustrated by the diagrams in Reference Configurations. Each server also provides one or two system management ports depending on server architecture, labeled Net Mgmt (Network Management), ALOM (Advanced Lights Out Manager port), ILOM (Integrated Lights Out Manager port) on single management port manageable servers, and labeled SP0 and SP1 (Service Processor 1 and 2) on dual management port manageable servers. The management server requires only a single management port to provide connectivity with the corporate network. In this document, the management port is always shown as MGMT. Note – Depending on the system architecture and the operating system installed, the operating system refers to the Ethernet ports by different names. For example, the first Ethernet port on a machine is referred to as ETH0, HME0, or BGE0 depending on the operating system. This document refers to the lowest order Ethernet port on a machine as ETH0, the next port as ETH1 and so on regardless of architecture and operating system. The following illustration provides the logical diagram for a management server with three 1-Gbyte NICs, and is used in subsequent sections to illustrate the reference architecture diagrams.
Manageable Server ConnectionsA SPARC or x86–based server can be used as a manageable server as described in Management Server Requirements. Each server provides one or two 10/100/1000 network interface ports. Each server also provides one or two system management ports depending on server architecture, labeled ALOM or ILOM on single management port manageable servers, and labeled SP0 and SP1 on dual management port manageable servers. In this document, the management port is always shown as MGMT. The following illustration provides the logical diagram for a manageable server with two 1-Gbyte NICs, and is used in subsequent sections to illustrate the reference architecture diagrams.
Reference ConfigurationsThis section provides reference configuration diagrams and connectivity information that will assist you in designing and connecting your N1 System Manager equipment. Other configurations are possible, such as using separate switches for each network. You can implement your network using any combination of VLANs and switches. Each network, whether management, provisioning or data, should be assigned to separate VLANs. Note – In each of the following reference configurations, corporate access is shown as a connection to the management server. Alternatively, corporate access to the N1 System Manager can be provided through a switch instead of the management server. Separate Management, Provisioning, and Data NetworksThis section provides reference configuration diagrams and connectivity information that will assist you in designing and connecting your N1 System Manager equipment. Figure 2–1 Separate Management, Provisioning, and Data Networks
When designing a network, keep the following information in mind:
The following list summarizes the connectivity requirements for the separate management, provisioning, and data networks configuration.
Combined Management and Provisioning Network, and a Separate Data NetworkFigure 2–2 Combined Management and Provisioning Networks, and a Separate Data Network
For this configuration:
Caution – The statically-assigned management IP addresses and the dynamically assigned IP addresses used during OS provisioning are part of the same network. The N1 System Manager does not manage IP addresses. You must ensure that the IP addresses used during provisioning do not conflict with the management network IP addresses. The following list summarizes the connectivity requirements for the combined management and provisioning network and the separate data network configuration.
Combined Provisioning and Data Network, and a Separate Management NetworkFigure 2–3 Combined Provisioning and Data Network, and a Separate Management Network
For this configuration:
Caution – The N1 System Manager DHCP service must be the only DHCP service on the data network. The following list summarizes the connectivity requirements for the combined data and provisioning network and the separate management network configuration.
Combined Provisioning, Data, and Management NetworkFigure 2–4 Combined Provisioning , Data, and Management Network
For this configuration:
Caution – The N1 System Manager DHCP service must be the only DHCP service on the data network. The following list summarizes the connectivity requirements for the combined management, provisioning, and data networks configuration.
Restricted Mode: Management Network OnlyFigure 2–5 Restricted Mode: Management Network Only
For this configuration:
Restricted Mode: Provisioning Network OnlyFigure 2–6 Restricted Mode: Provisioning Network Only
For this configuration:
The following list summarizes the connectivity requirements for the management network only configuration.
Site PlanningThis section provides guidelines for determining your management server and switch needs. The following topics are discussed: Management Server ConsiderationsHard drive capacity and the number of manageable servers to be managed are the primary considerations for your management server.
The following table provides sizing guidelines for the management server. Table 2–9 Management Server Hardware Sizing Guidelines
Switch ConsiderationsSwitch requirements are determined by the following factors:
The following worksheet can assist you in determining the total number of switch ports by type that you will need on your switch or switches. Table 2–10 Switch Port Requirements Worksheet
Use the above totals to determine your switch requirements, and then connect the servers and switches according to your site plan. Setting Up Manageable ServersBefore you can use the N1 System Manager to discover manageable servers, each manageable server must be set up as follows:
Discovery of a manageable server will fail if the server's management port has not been configured. SPARC Architecture Manageable Server CredentialsIf you do not specify the management server management port credentials when running discovery, the discovery process will use the default credentials shown in the following table. Table 2–11 SPARC Architecture Manageable Server Default Credentials
To manage RSC-based manageable servers, you must first configure the RSC credentials and the Online Boot Prom (OBP) as described in Preparing RSC-based Manageable Servers. x86 Architecture Manageable Server CredentialsIf you do not specify the management server management port credentials when running discovery, the discovery process will use the default credentials shown in the following table. Table 2–12 x86 Architecture Manageable Server Default Credentials
If only one credential is specified during discovery for x86 architecture manageable servers, the missing credential is configured with one of the defaults specified above. Automatic configuration of credentials during discovery is supported for Sun Fire V20z and V40z servers if they are in the factory default state. If you do specify the login accounts and passwords for discovery of a Sun Fire V20z or V40z, the discovery process configures the Sun Fire V20z or V40z using the credentials you provide. Although the Sun Fire X2100 does not support SNMP, the X2100 does support IPMI platform event trap (PET), which generates SNMP V1 traps for IPMI events. The N1 System Manager listens for the X2100 IPMI events. Preparing RSC-based Manageable ServersThe Sun Fire V490 and V890 RSC IP address and credentials, are configured by running configuration utilities from the Solaris root command line prompt on the server. The servers are shipped with Solaris pre-installed. Configuration of the Online Boot Prom (OBP) is done using a telnet session to the RSC. Preparation of an RSC-based manageable server is comprised of the following tasks:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
# pkgadd -d . SUNWrsc
The following files are already installed on the system and are being
used by another package:
/usr <attribute change only>
Do you want to install these conflicting files [y,n,?,q] y
## Checking for setuid/setgid programs
Installing Remote System Control as <SUNWrsc>
.
.
.
Installation of <SUNWrsc> was successful
# pkgadd -d . SUNWrscd
Processing package instance <SUNWrscd>
.
.
.
Installation of <SUNWrscd> was successful
# pkgadd -d . SUNWrscj
Processing package instance <SUNWrscj>
.
.
.
Installation of <SUNWrscj> was successful
|
Next Steps
Configure the server's RSC as described in the next procedure.
To Configure the RSC IP Address and Credentials
The Sun Fire V490 and V890 RSC credentials are configured by running configuration utilities from the Solaris root command line prompt on the server. The servers are shipped with Solaris pre-installed.
This procedure describes only the information required by the N1 System Manager. For detailed information about the RSC configuration utility, see the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12 and the Sun Remote System Control (RSC) 2.2.3 Release Notes at http://docs.sun.com/source/819–2022.
Before You Begin
RSC Configuration Utilities version 2.3.3 must be installed on the server as described in To Download and Update the RSC Utilities
Steps
-
Log in as root on the RSC-based manageable server.
-
Run the RSC configuration utility.
-
If you are configuring a V490 server, type /usr/platform/SUNW,Sun-Fire-V490/rsc/rsc-config.
-
If you are configuring a V890 server, type /usr/platform/SUNW,Sun-Fire-V890/rsc/rsc-config.
Respond to each prompt according to the requirements of your network, except for the RSC user account prompts:
-
When prompted for the RSC user account, type admin.
-
When prompted for the RSC user account password, type n1smadmin.
-
When prompted for the RSC user privileges, type cuar.
-
Next Steps
Redirect the server console to the RSC, and configure the Online Boot Prom (OBP) settings.
To Redirect the Server's Console to the RSC and Configure
the OBP
The Sun Fire V490 and V890 RSC credentials are configured by running configuration utilities from the Solaris root command line prompt on the server. The servers are shipped with Solaris pre-installed.
This procedure describes only the information required by the N1 System Manager. For detailed information about console redirection on an RSC-based server and OBP configuration, see the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12 and the Sun Remote System Control (RSC) 2.2.3 Release Notes at http://docs.sun.com/source/819–2022.
Before You Begin
-
RSC Configuration Utilities version 2.3.3 must be installed on the server as described in To Download and Update the RSC Utilities.
-
The RSC must be configured as described in To Configure the RSC IP Address and Credentials.
Steps
-
Log on to the manageable server's RSC using the command telnet IP address where IP address is the address you assigned to the RSC.
-
Redirect the server's console to the RSC as described in the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12.
-
Configure the server's OBP as described in the Sun Remote System Control (RSC) 2.2 User's Guide at http://docs.sun.com/source/816–3314–12.
Ensure the following environment variables are set to the values shown:
OBP Environment Variable
Value
local-mac-address?
true
output-device
rsc-console
input-device
rsc-console
diag-device
disk
diag-script
none
diag-level
off
diag-switch?
false
For example:
> setenv local-mac-address? true > setenv output-device rsc-console
To verify the settings, type printenv.
Setting Up a Windows Remote Installation Services Server
The N1 System Manager OS provisioning process uses the Microsoft Remote Installation Services (RIS) technology to provision Windows operating systems to manageable servers from a RIS server. To provision Windows operating systems to manageable servers, you must set up a RIS server that is accessible to the N1 System Manager as described in the following sections. For more information about RIS, see the Microsoft RIS documentation at http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/c62e5951-5eb9-42f1-95ae-490e5d7a5551.mspx.
Setting up the Windows RIS server consists of the following tasks:
To Set Up the Windows RIS Server
Steps
-
Install Windows 2003 Enterprise Edition operating system for 32–bit systems with Service Pack 1 on the Windows RIS server.
Create a separate NTFS partition that contains 800 Mbytes for each Windows operating system image that you want to provision. The Windows OS image partition should be on a drive or logical partition other than the C: drive. You will prompted for the partition information when you configure the N1 System Manager.
Note –If you already have a machine that is running Windows 2003 Server 32-bit Enterprise edition without Service Pack 1, you can install just the Windows 2003 Service Pack 1 on the server See Microsoft Knowledge Base Article #891128.
-
Install and configure Active Directory Server on the RIS server.
During installation of Active Directory Server software on your RIS server, identify your RIS server as a domain controller. For information about Active Directory Server, see Microsoft Knowledge Base Article 324753
-
Install and configure the RIS server software on the RIS server.
For more information, see Microsoft Knowledge Base Article 325862.
Note –While installing RIS server, add a Windows 2003 x64 Risetup.exe image or the Windows 2003-Service Pack 1 x86 Risetup.exe image on the RIS server.
If the Windows Server 2003 SP1 RISETUP image is the first image to be uploaded to the RIS server, the new OS chooser screen (x8664.osc ) is copied to the RIS server by default.
If there are existing Windows OS images on the RIS server at the time the first Windows Server 2003 SP1 image is added, you must choose whether to overwrite (or backup and overwrite) the OS chooser screens during the installation to get the new screen. See Microsoft Knowledge Base Article #891128.
-
Install Cygwin© on the RIS Server and configure Open Secure Shell Service (OpenSsh service) for Windows 2003 on the RIS server as n1smssh user.
For more information, see the Cygwin Home Page and the Open Ssh Windows Install Instructions. For information about removing existing Cygwin packages, see http://cygwin.com/faq/faq_2.html#SEC20.
The Cygwin install source is located in the install media Windows directory.
To Set Up a Windows Image on the Windows RIS Server
Steps
-
Log onto the Windows RIS server using the administrator account or an account with administrator privileges.
-
Copy the Windows distribution from a CD or Network Share to the RIS server CIFS.
On the RIS server, copy the windows distribution either from a CD or Network Share using the RiSetup.exe utility with the -add option onto the RIS Server Common Internet File System (CIFS) share.
Note –Make sure you select the option “Keep the old existing OSC files” in the risetup wizard while creating RIS images.
When you copy a Windows distribution to the RIS server, the appropriate Windows drivers are copied automatically. To add other drivers into the distribution, copy the drivers into the scripts directory on the RIS server.
Do not use the Microsoft Developers Network (MSDN) Combination CDs to create a RIS Image. RIS image creation will fail, and you will get an error message that is described in the Microsoft Knowledge Base Article #300556. To resolve this issue, use a retail version of the OS image being created.
To create a RIS image of a Windows distribution integrated with service packs, follow the procedures described in the following articles:
-
How to create a RIS image with the service pack bundled is explained in Service Pack 3 Installation and Deployment Guide for Windows 2000 Server edition. Similar guides can be found in Microsoft documentation for other OS version service packs as well.
-
How to obtain the latest Windows 2000 service pack is explained in Microsoft Knowledge Base Article #260910
Choose “Network installation” option for Windows Service Pack Express/Network Installation for downloading a service pack to create a RIS image. Windows 2000 Service pack 3 download process is explained in http://www.microsoft.com/Windows2000/downloads/servicepacks/sp3/download.aspx. Similar download pages can be found in Microsoft documentation for other OS version service packs as well.
-
-
(Optional) To provision non-English versions of the Windows OS, you need to do some additional configuration when you set up the image on the RIS server.
Basically, the RIS server assumes that you have files in an English path. To resolve this issue, copy the other language's files to the English path.
-
Go to the directory in which the OS Chooser files live.
For example:
% cd RemoteInstall\OSChooser
-
Copy the files from the language directory to an English directory.
For example:
% copy -r Japanese English
This creates a directory RemoteInstall\OSChooser\English that contains the install screens in the native language. When the RIS software looks into the default English path, it will display the non-English OS Chooser screens during install.
-
To Set the BIOS Boot Order on a Manageable Server
Before You Begin
Ensure that the Windows operating system is supported on each target manageable server. For a list of manageable servers that support the Windows operating system, see Table 2–6.
Steps
-
Set the BIOS Settings on the target host in the following order:
-
Identify the target host's primary NIC MAC address for a PXE network boot and the Globally Unique Identifier (GUID) value.
You can obtain the GUID from the target host's BIOS settings or from any of the following other sources:
-
A label on the side of the computer case.
-
A label within the computer case.
-
The basic input/output system (BIOS) of the client computer.
-
Network traffic from the client computer. You can use a network utility to sniff the network traffic and locate the DHCPDiscover packet. That field will contain the 128-bit, 16-byte GUID or a 128 bit Universally Unique IDentifier (UUID).
Note –The GUID must be in the form {dddddddd-dddd-dddd-dddd-dddddddddddd}, where d is a hexadecimal text digit. For example, {921FB974-ED42-11BE-BACD-00AA0057B223}. Valid entries for the client GUID are restricted to the numbers 0 through 9, lowercase alphabetical characters, uppercase alphabetical characters, and a dash.
Caution – Spaces, underscores, and other special symbols are not permitted in a GUID nor in a UUID.
-