System Requirements for Unicenter 3.0

Last Updated: September 27, 2006

SQL 6.5, 7.0 or 2000 is required for the repository on Windows. Ingres is required for the repository on UNIX.

Please see the Release notes for other installation considerations.

R3.1 :

Hardware Requirements (Windows Only)

• CPU-PIII-550 minimum, PIII-800 and higher recommended
• RAM-256 MB minimum, 512 MB or higher recommended
• Hard drive-4 GB minimum, 6 GB recommended
• Video-32 MB DirectX-True Color, TNT2 (for 3d) recommended
• Monitor-17" @1024x768 minimum, 21"@1600x1200 recommended

Note: These minimums assume a wide cross-selection of installed components. If you install only a few components or agents, the minimum hardware requirements can be substantially less.

Hardware Requirements (UNIX/Linux Only)

5.1 Disk Requirements for a Unicenter NSM 3.1 Manager

• 1 GB of available disk space
• 1 GB of swap space

5.2 Disk Requirements for a Unicenter NSM 3.1 Client (Unicenter Explorer Only)

• 256 MB of available disk space
• 512 MB of swap space
• 200 MB of additional swap space for each instance of the Unicenter Explorer

5.3 Memory Requirements

• 512 MB for a Unicenter NSM 3.1 Manager computer (contains any or all of the above Unicenter Managers)
• 256 MB for a Unicenter NSM 3.1 Client (Unicenter Explorer only)

R11 :

Enterprise Manager Configuration

An Enterprise Manager Configuration consists of all management components including a local MDB.

Infrastructure Server Configuration

An Infrastructure Server consists of all management components with a remote MDB.

Managed Node Configuration

A Managed Node consists of the System, Performance and Event Agents.

Management Command Center Configuration

A Management Command Center consists of the main GUI client interface to an Infrastructure Server or an Enterprise Server.

GUI Configurations

Any local GUI configurations require the following hardware:

Note: We recommend letting the Windows operating system manage virtual memory, rather than specifying an absolute value. If you decide to specify an absolute value, we recommend that value be at least 1.5 times the physical amount of real memory (RAM) on the computer. Virtual memory must not be less than 2 GB if installing the Ingres Server, and should be substantially more if the system has many other applications running.

Note: You may see messages stating that one or more other CA services have failed to start if the computer does not have the minimum necessary resources to support the installed components. In many cases the services may in fact be operational shortly after the error message, while in other cases they may fail due to insufficient resource availability, causing other cascading failures. The overall stability of your system may be affected if you install this product on systems with insufficient resources.

Note: Ingres preallocates most of the resources it requires. It often uses hundreds of megabytes of virtual memory and several hundred thousand handles. The exact use of resources depends upon the number and sizes of the page caches used. The default medium MDB config provided with r11 products uses about 1 GB of virtual memory and approximately 350,000-500,000 handles.

R11.1 :

Hardware Requirements

You may see messages stating that one or more other CA services have failed to start if the computer does not have the minimum necessary resources to support the installed components. In some cases, even computers that meet or exceed the necessary hardware requirements may experience this behavior if the combination of software products installed cause a temporary shortage of resources during startup. The services may in fact be operational shortly after the errors. Should this occur, it may become necessary to delay the startup of CA services to allow other critical services time to completely initialize. In cases where there are simply insufficient resources available, CA services and other services may fail causing other cascading failures. The overall stability of your system may be affected if you install this product on systems with insufficient resources.

We recommend letting the Windows operating system manage virtual memory, rather than specifying an absolute value. If you decide to specify an absolute value, we recommend that value be at least 1.5 times the physical amount of real memory (RAM) on the computer.

A pointing device, (for example, a mouse) is required to install and use this product.

Enterprise Manager Configuration

An Enterprise Manager Configuration consists of all management components including a local MDB.

Infrastructure Server Configuration

An Infrastructure Server consists of all management components with a remote MDB.

Managed Node Configuration

A Managed Node consists of the System, Performance and Event Agents.

Management Command Center Configuration

A Management Command Center consists of the main GUI client interface to an Infrastructure Server or an Enterprise Server.

GUI Configurations

Any local GUI configurations require the following hardware:

Database Requirements

Unicenter NSM for Windows requires Microsoft SQL Server 2000 Enterprise or Standard Edition (32-bit) with a minimum of Service Pack 4 or any later maintenance, or Microsoft SQL Server 2005 Enterprise or Standard Edition (32-bit) optionally with Service Pack 1 or any later maintenance.

Note: The MDB creation uses Windows Authentication and must be run by an operating system user that is a member of the System Administrators server role.

• Mixed-mode authentication is required.
• A dictionary sort order of case-sensitive or case-insensitive is required.
• You can use the English version of Microsoft SQL Server, with a code page/character set of 1252, on any of the Windows language versions that we document as certified.
• You can use localized versions of Microsoft SQL Server other than English on any of their respective and matching Windows language versions that we document as certified, with the default code page/character set, or with 1252 if you will not be using specific localized character data for that region, even though you are installing on a localized system of that region. You must use the default code page/character set if you plan to use specific localized characters.
• You cannot use a Microsoft SQL Server alias that matches the local computer name, but really points to a remote Microsoft SQL Server (whether in another resource group on the same physical node of a cluster, or truly on a different computer).

Note: In Unicenter NSM r11, the database tool used for the MDB is Ingres for both Windows and UNIX/Linux. In Unicenter NSM r11.1, however, the database tool used for the MDB is Microsoft SQL Server. The documentation for Unicenter NSM r11.1 has information for both Ingres databases and Microsoft SQL Server databases, so be aware that some of it may not apply, depending on the Unicenter NSM version you are running.