Deployment and Sizing Information
Deployment Scenarios on Trusted Boundry
- Single Machine Deployment of Monitoring Service
  - Single Machine Deployment of Monitoring Service-Alternate Method
- Multiple Machine Deployment of Monitoring Service
  - Multiple Machine Deployment of Monitoring Service-Alternate Method
Deployment Scenarios on Untrusted Boundary
- Multiple Machine Deployment of Monitoring Service-Alternate Method

Deployment and Sizing Information

This chapter contains the following sections:

Deployment Scenarios on Trusted Boundry

Single Machine Deployment of Monitoring Service

Before you begin

The necessary Management Packs must be imported in the Management Group.

Procedure

Step 1

Add an Agent Managed Computer (AM)

Step 2

Run the installer on the AM and install the Monitoring Service

Step 3

While adding the UCS instances or IMC Group instances from the Operations Manager console, select the AM as the Service Machine.

The following tables displays the sizing information for the above approach:

Table 1. UCS Manager Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored
AM	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~140 with default private bytes ~200 with private bytes value ~1.5 GB

Table 2. Cisco IMC Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored
AM	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~500

Table 3. Cisco UCS Central Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored
AM	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~200 with private bytes value ~1.5 GB

Single Machine Deployment of Monitoring Service-Alternate Method

Before you begin

The necessary Management Packs must be imported in the Management Group.

Procedure

Step 1

Run the installer on a Management Server, and install the Monitoring Service.

Step 2

While adding the UCS instances or IMC Group instances from the Operations Manager console, select the Management Server (MS) as the Service Machine.

Table 4. UCS Manager Sizing Details
Management Server	Hardware Specification	Number of blades Monitored
MS	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~500

Table 5. Cisco IMC Sizing Details
Management Server	Hardware Specification	Number of blades Monitored
MS	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~1100

Table 6. Cisco UCS Central Sizing Details
Management Server	Hardware Specification	Number of blades Monitored
MS	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~600 with default private bytes ~1000 with private bytes value ~2.5 GB

Multiple Machine Deployment of Monitoring Service

Before you begin

The necessary Management Packs must be imported in the Management Group.

Procedure

Step 1

Add Agent Managed Computer (AM).

You can add more than one agent managed computer. For example, AM1, AM2, AM3.

Step 2

Run the installer on all the added agent managed computers and install the Monitoring Service.

Step 3

While adding the UCS instances or IMC Group instances from the Operations Manager console, select the AM from which you want to monitor the instances as the Service Machine.

The following tables displays the sizing information for the above approach:

Table 7. UCS Manager Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored per Server
AM1 AM2 AM3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~140 with default private bytes ~200 with private bytes value ~1.5 GB

Table 8. Cisco IMC Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored per Server
AM1 AM2 AM3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~500

Table 9. Cisco UCS Central Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored per Server
AM1 AM2 AM3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~140 with default private bytes ~200 with private bytes value ~1.5 GB

Multiple Machine Deployment of Monitoring Service-Alternate Method

Before you begin

The necessary Management Packs must be imported in the Management Group.

Procedure

Step 1

Run the installer on a Management Server, and install the Monitoring Service.

You can add more than one Management Servers. For example, MS1, MS2, MS3.

Step 2

While adding the UCS instances or IMC Group instances from the Operations Manager console, select a Management Server (MS) as the Service Machine.

Table 10. UCS Manager Sizing Details
Management Server	Hardware Specification	Number of blades Monitored per Server
MS1 MS2 MS3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~500 with default private bytes

Table 11. Cisco IMC Sizing Details
Management Server	Hardware Specification	Number of blades Monitored per Server
MS1 MS2 MS3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~1100

Table 12. Cisco UCS Central Sizing Details
Management Server	Hardware Specification	Number of blades Monitored per Server
MS1 MS2 MS3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~600 with default private bytes ~1000 with private bytes value ~2.5 GB

Deployment Scenarios on Untrusted Boundary

Distributed deployment of Operations Manager can consists of Gateway Servers which are installed on a different un-trusted boundary to the Management Group. These Gateway servers monitor the Agent Managed Computers locally and send the monitoring information to the connected Management Server.

The Management Group (MG) has two management servers; MS1 and MS2. Gateway Server (GW) is connected to MS1. GW belongs to a different Active Directory than MS1 or MS2. Assuming that there are multiple instances to be monitored, few instances are on same network as MS1 or MS2, and the rest belongs to the same network as GW.

Before you begin

The necessary Management Packs must be imported in the Management Group.

Procedure

Step 1

Add an Agent Managed Computer to Management Server, either MS1 or MS2.

Step 2

Add an Agent Managed Computer AM2 to GW1.

You can add one or more Agent Managed Computers.

Step 3

Run the installer on AM1 and install the Cisco UCS Monitoring Service.

Step 4

Run the installer on AM2 and install the Cisco UCS Monitoring Service.

Run the installer for additional Agent Managed Computer.

Step 5

While adding Cisco UCS or IMC Group instances from the Operations Manager Console select AM1 as the Service Machine.

Alternatively, Agent Managed Computer added in Step 3 can also be selected as Service Machine from Add Monitoring Wizard.

The following tables display the sizing information for the above approach:

Table 13. Cisco UCS Manager Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored per Server
AM1 AM2 AM3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~140 with default private bytes ~200 with private bytes value ~1.5 GB

Table 14. Cisco IMC Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored per Server
AM1 AM2 AM3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~500

Table 15. Cisco UCS Central Sizing Details
Agent Managed Computer	Hardware Specification	Number of blades Monitored per Server
AM1 AM2 AM3	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~140 with default private bytes ~200 with private bytes value ~1.5 GB

Multiple Machine Deployment of Monitoring Service-Alternate Method

Before you begin

The necessary Management Packs must be imported in the Management Group.

Procedure

Step 1

Run the installer on either MS1 or MS2, and install the Monitoring Service.

You can add more than one Management Servers. For example, MS1, MS2, MS3.

Step 2

Run the installer on GW1, and install the Monitoring Service.

Step 3

While adding the UCS instances or IMC Group instances from the Operations Manager console, select either MS1 or MS2 as the Service Machine to monitor the instances which belong to the same network.

Step 4

While adding UCS or IMC Group instances from the Operations Manager Console select GW1 as the Service Machine for monitoring the instances which belongs to the same network as GW1.

Table 16. UCS Manager Sizing Details
Management Server	Hardware Specification	Number of blades Monitored per Server
MS1 GW1	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	MS1—~500 servers with default private bytes GW1—~500 servers with default private bytes

Table 17. Cisco IMC Sizing Details
Management Server	Hardware Specification	Number of blades Monitored per Server
MS1 GW1	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	MS1—~1100 servers GW1—~1100 servers

Table 18. Cisco UCS Central Sizing Details
Management Server	Hardware Specification	Number of blades Monitored per Server
MS1 GW1	Intel® Xeon® CPU E5-4640 0@ 2.40 G Hz (2 processors) RAM 12.0 GB 64-bit Operating system	~600 with default private bytes ~1000 with private bytes value ~2.5 GB

Cisco UCS Management Pack Suite Installation and Deployment Guide, Release 4.x For Microsoft System Center Operations Manager

Bias-Free Language

Book Title

Cisco UCS Management Pack Suite Installation and Deployment Guide, Release 4.x For Microsoft System Center Operations Manager

Chapter Title