Sun N1 System Manager 1.3.1 What's New

Chapter 4 Other Changes to N1 System Manager

This chapter details changes and modifications to N1 System Manager functionality and documentation beyond those additions that support the Sun Blade 8000 Modular System.

The online help has not been updated for this release of N1 System Manager. This chapter also details the minor changes to the functionality described in the online help.

Supported Hardware and Operating Systems

This section details the supported hardware for this release of N1 System Manager.

Management Server Requirements

N1 System Manager management server hardware and operating software minimum requirements are listed in the following table.


Caution – 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 4–1 Management Server Disk Space and RAM Requirements

Disk Space 

RAM 

72 Gbytes minimum for all management servers 

4 Gbytes minimum for all management servers 

Table 4–2 SPARC-based Management Server Supported Hardware and Operating Systems

Type 

Operating System 

NetraTM 240, 440

Solaris Version 10, 64-bit 

Solaris Version 10 Update 1, 64-bit 

Sun FireTM T1000, T2000

Solaris Version 10 HW2, 64-bit 

Solaris Version 10 Update 1, 64-bit 

Sun Fire V210, V240, V440 

Solaris Version 10, 64-bit 

Solaris Version 10 Update 1, 64-bit 

Sun Fire V490 

Solaris Version 10, 64-bit 

Solaris Version 10 Update 1, 64-bit 

Table 4–3 X86 and X64–based Management Server Supported Hardware and Operating Systems

Type 

Operating System 

Sun Fire X2100 

Solaris Version 10 HW1, 32-bit and 64-bit 

Solaris Version 10 Update 1, 32-bit and 64-bit 

Solaris Version 10 Update 2, 32-bit and 64-bit 

Red Hat Enterprise Linux 3.0 AS Update 6, 32-bit and 64-bit 

Red Hat Enterprise Linux 4.0 AS Update 2, 32-bit and 64-bit 

Sun Fire X4100 and X4200 

Solaris x64 Version 10 HW1, 64-bit 

Solaris x64 Version 10 Update 1, 64-bit 

Solaris x64 Version 10 Update 2, 64-bit 

Red Hat Enterprise Linux 3.0 AS Update 5, 32–bit and 64–bit 

Red Hat Enterprise Linux 4.0 AS Update 1 and Update 3, 64–bit 

Sun Fire V20z and V40z 

Solaris x64 Version 10 HW1, 64-bit 

Solaris x64 Version 10 Update 1 and Update 2, 64-bit 

Red Hat Enterprise Linux 3.0 AS Updates 2 through 4, 32-bit and 64-bit, single core only 

Red Hat Enterprise Linux 3.0 AS Update 5, 32-bit and 64-bit 

Red Hat Enterprise Linux 4.0 AS Update 1, 32-bit and 64-bit 

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 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 Requirements

N1 System Manager manageable server hardware and operating software requirements are listed in the following tables.

Table 4–4 Manageable Server Disk Space and RAM Requirements

Disk Space 

RAM 

12 Gbytes minimum for all manageable servers 

512 Mbytes minimum, 1 Gbyte recommended for all manageable servers 

Table 4–5 SPARC-Based Manageable Server Supported Hardware and Operating Systems

Type 

Provisionable OS 

Sun Netra 240 and 440 

Solaris 10 GA and later 

Solaris 9 Update 7 and Update 8 

Sun Fire V210, V240, and V440 

Solaris 10 GA and later 

Solaris 9 Update 7 and Update 8 

Sun Fire V490 

Solaris 9 9/05 

Solaris 10 3/05 

Sun Fire V890 

Solaris 9 9/05 

Solaris 10 3/05 

Sun Fire T1000 and T2000 

Solaris 10 HW2 and later 

Table 4–6 X86 and X64 Based Manageable Server Supported Hardware and Operating Systems

Type 

Provisionable OS 

Sun Blade X8400 Server Module 

Solaris x64 Version 10 Update 2, 64-bit 

Red Hat Enterprise 4 AS, Update 3 

SUSE Linux Enterprise Server 9 SP3, 64-bit 

Windows 2003 SE, 2003 EE 64-bit 

Windows 2003 SE, 2003 EE, SP1 32-bit 

Sun Fire V20z and V40z 

Solaris x64 Version 10 HW1, 64-bit 

Solaris x64 Version 10 Update 1, 64-bit 

Solaris 9 04/05 32-bit 

Solaris 9 09/05 HW 32-bit 

Solaris 9 09/05 32-bit 

Red Hat Enterprise Linux 3.0 WS, ES, and AS, Updates 1 through 4, 32-bit and 64-bit, single core only 

Red Hat Enterprise Linux 3.0 WS, ES, and AS, Updates 5 through 6, 32-bit and 64-bit 

Red Hat Enterprise Linux 4.0 WS, ES, and AS, 32-bit, single core only 

Red Hat Enterprise Linux 4.0 WS, ES, and AS, update 1, 32-bit and 64-bit 

SUSE Linux Enterprise Server 9 SP1 and SP2, 64-bit 

 

MS Windows 2003 SE, 2003 EE, 2003 WE 32-bit only 

Windows 2003 SE, 2003 EE 64- bit only 

Windows 2000S, 2000AS 32-bit only 

Sun Fire X2100 with the 8081A IPMI 1.5 Remote Management Card: Part Number: 371-0743 

Solaris Version 10 HW1. 32-bit and 64-bit 

Solaris Version 10 Update 1, 32-bit and 64-bit 

Red Hat Enterprise Linux 3.0 WS, ES, and AS Update 6 or greater, 32-bit and 64-bit 

Red Hat Enterprise Linux 4.0 WS, ES, and AS Update 2, 32-bit and 64-bit 

SUSE Linux Professional 9 SP3 or greater, 32-bit and 64-bit 

Windows 2003 SE, 2003 EE, 64-bit 

Windows 2003 SE, 2003 EE, SP1, 32-bit 

Sun Fire X4100 and X4200 including Sun Fire X4100 M2 and Sun Fire X4200 M2 

Solaris x64 Version 10 HW1, 64-bit 

Solaris x64 Version 10 Update 1, 64-bit 

Red Hat Enterprise Linux 3.0 WS, ES, and AS, Update 5 and Update 6, 32-bit and 64-bit 

Red Hat Enterprise Linux 4.0 WS, ES, and AS Update 1 and Update 2, 64-bit 

SUSE Linux Enterprise Server 9 SP1 through SP3, 64-bit 

Windows 2003 SE, 2003 EE 64-bit 

Windows 2003 SE, 2003 EE, SP1 32-bit 

Sun Fire X4500 

Solaris 10 Update 1, 64-bit 

Sun Fire X4600 and Sun Fire X4600 M2 

Solaris 10 Update 1, 64-bit, 

Red Hat Enterprise Linux 4.0 WS, ES, and AS Update 3, 64-bit, 

Windows 2003 SE, SP1, 32-bit 


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.


Upgrading From N1 System Manager 1.3

The upgrade procedure to N1 System Manager 1.3.1 from N1 System Manager 1.3 is identical to the upgrade procedure to N1 System Manager 1.3 from N1 System Manager 1.2. See Upgrading to Sun N1 System Manager 1.3 in Sun N1 System Manager 1.3 Installation and Configuration Guide for details.

Updates to the N1 System Manager 1.3 Documentation

This section details any updates or corrections to the N1 System Manager documentation that already existed for the last release of the product, and that accompanies this release of the product.

Provisioning the Solaris 10 OS on to N1 Grid Engine Hosts

After you have deployed the Solaris 10 OS to the managed servers that are designated N1 Grid Engine compute hosts, if the N1 Grid Engine master server is running a supported distribution of Red Hat Linux version 4, follow the procedure described below.

This workaround is necessary no matter what operating system is running on the management server.

ProcedureTo Provision the Solaris 10 OS on to N1 Grid Engine Hosts

  1. Follow the standard provisioning process described in Chapter 2, Provisioning UNIX Operating Systems, in Sun N1 System Manager 1.3 Operating System Provisioning Guide and in Chapter 1, N1SM for N1 Grid Engine Online Help, in Sun N1 System Manager 1.3 Grid Engine Monitoring Help.

  2. On the server designated as a compute host, on which you have provisioned the Solaris 10 OS, edit the /etc/default/nfs file as follows.

    Ensure that the NFS_CLIENT_VERSMAX is set to 2 and not 4.


    NFS_CLIENT_VERSMAX=2
  3. Restart NFS using the following command.


    # svcadm restart svc:/network/nfs/client:default
    

Updates and Amendments to the Online Help

The online help has not been updated for this release of the N1 System Manager. This section details some minor additions to the functionality that is described in the online help, since these additions have not been made to the online help for this release.

The valid hardware model name in N1 System Manager for Sun Blade X8400 Server Module is X8400.

The valid hardware model names in N1 System Manager for the Sun Fire X4000 series servers are as follows:

X4100M2

Sun Fire X4100 M2 server

X4200M2

Sun Fire X4200 M2 server

X4600M2

Sun Fire X4600 M2 server

X4500

Sun Fire X4500 server

The provisioning of Sun Blade X8400 Server Modules is now possible. This is not detailed in the online help. See Chapter 3, Provisioning Sun Blade X8400 Server Modules in the Sun Blade 8000 Chassis for details.