The 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:
N1 System Manager management server hardware and operating software minimum requirements are listed in the following table. See Table 2–5 for specific management server sizing information based on the number of provisionable servers to be managed.
Dedicate the management server only to N1 System Manager software. Do not install other applications on the management server.
Type |
Management Port Type |
Operating System |
Disk Space |
RAM |
---|---|---|---|---|
NetraTM 240, 440 |
ALOM |
Solaris 10 GA and later |
72 Gbytes minimum |
4 Gbytes minimum |
Sun FireTM V210, V240, V440 |
ALOM |
Solaris 10 GA and later |
||
Sun Fire T1000 and T2000 |
ALOM |
Solaris 10 HW2 and later |
Table 2–2 X86–Based Management Server Hardware and Operating System Requirements
Type |
Management Port Type |
Operating System |
Disk Space |
RAM |
---|---|---|---|---|
Sun Fire X2100 with the 8081A IPMI 1.5 Remote Management Card: Part Number: 371-0743 |
SP |
Solaris x86 Version 10 HW1 and later Red Hat Enterprise Linux 3.0 AS Updates 2 through 5, 32–bit and 64–bit |
72 Gbytes minimum |
4 Gbytes minimum |
Sun Fire X4100 and X4200 |
ILOM |
Solaris x86 Version 10 HW1 and later Red Hat Enterprise Linux 3.0 AS Update 5, 32–bit and 64–bit |
||
Sun Fire V20z and V40z |
SP |
Solaris x86 Version 10 and later Red Hat Enterprise Linux 3.0 AS Updates 2 through 5, 32–bit and 64–bit |
A minimum of 3.0 Gbytes should be allocated for each OS distribution you plan to provision.
On a Solaris-based management server, OS distributions are stored as follows:
Linux OS distributions are stored in /var/opt/SUNWscs/share/allstart
Solaris OS distributions are stored in /var/js
On a Linux-based management server, OS distributions are stored as follows:
Linux OS distributions are stored in /var/opt/sun/scs/share/allstart/
Solaris OS distributions are stored in /var/opt/sun/scs/share/allstart/jumpstart/
If the server you have chosen for the management server has only two network interfaces, consider installing a third 10/100 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.
N1 System Manager provisionable server hardware and operating software requirements are listed in the following tables.
Table 2–3 SPARC-Based Provisionable Server Hardware and Operating System Requirements
Type |
Management Port Type |
Provisionable OS |
Disk Space Requirements |
RAM Requirements |
---|---|---|---|---|
Sun Netra 240 and 440 |
ALOM |
Solaris 10 GA and later Solaris 9 Update 7 and Update 8 |
12 Gbytes minimum for all provisionable servers |
512 Mbytes minimum, 1-Gbyte recommended for all provisionable servers |
Sun Fire V210, V240, and V440 |
ALOM |
Solaris 10 GA and later Solaris 9 Update 7 and Update 8 |
||
Sun Fire T1000 and T2000 |
ALOM |
Solaris 10 HW2 and later |
Table 2–4 X86–Based Provisionable Server Hardware and Operating System Requirements
Type |
Management Port Type |
Provisionable OS |
Disk Space Requirements |
RAM Requirements |
---|---|---|---|---|
Sun Fire X2100 with the 8081A IPMI 1.5 Remote Management Card: Part Number: 371-0743 |
SP |
Solaris x86 Version 10 HW1 and later Red Hat Enterprise Linux 3.0 WS, ES, and AS Update 5, 32–bit and 64–bit Red Hat Enterprise Linux 4.0 WS, ES, and AS update 1, 32–bit and 64–bit SUSE Linux Professional 9.2, 64–bit only SUSE Linux Professional 9.3, 64–bit only |
12 Gbytes minimum for all |
512 Mbytes minimum, 1-Gbyte recommended |
Sun Fire X4100 and X4200 |
ILOM |
Solaris x86 Version 10 HW1 and later Red Hat Enterprise Linux 3.0 WS, ES, and AS Update 5, 32–bit and 64–bit Red Hat Enterprise Linux 4.0 WS, ES, and AS update 1, 64–bit only SUSE Linux Enterprise Server 9 SP1, 64–bit only |
||
Sun Fire V20z and V40z |
SP |
Solaris x86 Version 10 and later Solaris x86 Version 9 update 7 and update 8 Red Hat Enterprise Linux 3.0 WS, ES, and AS, Updates 1 through 5 for 32–bit only Red Hat Enterprise Linux 3.0 WS, ES, and AS, Updates 3 through 5, 64-bit only Red Hat Enterprise Linux 4.0 WS, ES, and AS, 64-bit only Red Hat Enterprise Linux 4.0 WS, ES, and AS update 1, 32–bit and 64-bit SUSE Linux Enterprise Server 9, 32–bit and 64–bit SUSE Linux Enterprise Server 9 SP1, 32–bit and 64–bit SUSE Linux Professional 9.2 , 32–bit and 64–bit SUSE Linux Professional 9.3, 32–bit and 64–bit |
You 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.
In order to support firmware updates for the Sun Fire V20z and V40z provisionable servers, the management network switch should be configured to auto-negotiate link speed.
The management switch and the provisioning and data network switch should support the following Ethernet connectivity.
10/100-megabit per second connectivity from the management server to the management switch to provide connectivity to each provisionable server's management port
10/100-megabit per second connectivity from each provisionable server's management port to the management switch
The management network should be on a private subnet, and must provide connectivity to a management port on each provisionable server
Provisioning and Data Network Switch
1 gigabit per second connectivity from the management server ETH1 port to the provisioning and data switch
1 gigabit per second connectivity from each provisionable server ETH0 port to the provisioning and data switch
1 gigabit per second connectivity from each provisionable server ETH1 port to the provisioning and data switch
1 gigabit per second connectivity from the provisioning and data switch to the corporate network
Considerations:
The provisioning network should be on a private subnet.
The data network should be on a public subnet accessible by the management server, provisionable servers, and the corporate network.
Due to the use of the DHCP protocol and the bandwidth requirements for OS provisioning, isolating the data network from the provisioning network might be required.
OS provisioning of Linux might fail if a delay occurs in the transmission of data between the management server and the provisionable server. A long delay can result if the spanning tree option is enabled for the switch port connected to the ETH0 port of the provisionable server. To address this issue, you can disable the spanning tree option for the switch or for the switch ports connected to the provisionable servers. Refer to your switch documentation for instructions about how to disable the spanning tree feature on your switch.