Manual Monitoring Cisco UCS Manager

Monitoring the Cisco UCS Manager

eG Enterprise v6

Restricted Rights Legend

The information contained in this document is confidential and subject to change without notice. No

part of this document may be reproduced or disclosed to others without the prior permission of eG

Innovations Inc. eG Innovations Inc. makes no warranty of any kind with regard to the software and

documentation, including, but not limited to, the implied warranties of merchantability and fitness for

a particular purpose.

Trademarks

Microsoft Windows, Windows NT, Windows 2000, Windows 2003 and Windows 2008 are either

registered trademarks or trademarks of Microsoft Corporation in United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their

respective owners.

Copyright

Table of Contents

MONITORING THE CISCO UCS MANAGER...........................................................................................................................................1

1.1 UCS CHASSIS LAYER .......................................................................................................................................................................... 4

1.1.1 Chassis IO Modules Test ........................................................................................................................................................ 6

1.1.2 Chassis Fans Test ................................................................................................................................................................ 19

1.1.3 Chassis Details Test ............................................................................................................................................................. 30

1.1.4 Chassis Fan Modules Test .................................................................................................................................................... 42

1.1.5 Chassis IO Module Backplane Ports Test .............................................................................................................................. 51

1.1.6 Chassis PSUs Test ............................................................................................................................................................... 53

1.1.7 Chassis IO Module Fabric PortsTest..................................................................................................................................... 66

1.2 THE NETWORK LAYER ...................................................................................................................................................................... 70

1.3 THE FABRIC INTERCONNECTS LAYER................................................................................................................................................. 70

1.3.1 Fabric Interconnect PSUs Test ............................................................................................................................................. 71

1.3.2 Fabric Interconnect Ethernet Ports Test ................................................................................................................................ 82

1.3.3 Fabric Interconnect Fans Test .............................................................................................................................................. 90

1.3.4 Fabric Interconnect FC Ports Test ...................................................................................................................................... 101

1.3.5 Fabric Interconnect Details Test ......................................................................................................................................... 109

1.3.6 LAN Cloud Port Channels Test ........................................................................................................................................... 113

1.3.7 LAN Cloud PC Ethernet Ports ............................................................................................................................................ 118

1.4 THE BLADES LAYER ....................................................................................................................................................................... 121

1.4.1 Blade Overview Test .......................................................................................................................................................... 122

1.4.2 Blade Processors Test ........................................................................................................................................................ 133

1.4.3 Blade Motherboard Test ..................................................................................................................................................... 134

1.4.4 Blade Memory Arrays Test ................................................................................................................................................. 136

1.4.5 Blade NICs Test ................................................................................................................................................................. 137

CONCLUSION ......................................................................................................................................................................................... 147

x

Table of Figures

Figure 1: The architecture of the Cisco UCS .....................................................................................................................................................2

Figure 2: Layer model of the Cisco UCS Manager ............................................................................................................................................3

Figure 3: The tests mapped to the UCS Chassis layer ........................................................................................................................................6

sFigure 4: The detailed diagnosis of the Configuration state measure of the Chassis I/O Modules Test .............................................................. 19

Figure 5: The detailed diagnosis of the Overall status measure of the Chassis Fans test ..................................................................................... 30

Figure 6: A Cisco UCS Blade Server Chassis ................................................................................................................................................. 31

Figure 7: The detailed diagnosis of the Administrative state measure of the Chassis Details test ........................................................................ 42

Figure 8: The detailed diagnosis of the Overall status measure of the Chassis Fan Modules test ........................................................................ 51

Figure 9: The detailed diagnosis of the Overall status measure of the Chassis PSUs test ................................................................................... 65

Figure 10: The detailed diagnosis of the Overall status measure of the Chassis I/O Module Fabric Ports Test .................................................... 70

Figure 11: The tests mapped to the Network layer........................................................................................................................................... 70

Figure 12: The tests mapped to the Fabric Interconnects layer ......................................................................................................................... 71

Figure 13: The detailed diagnosis of the Overall status measure of the Fabric Interconnect PSUs test ................................................................ 82

Figure 14: The detailed diagnosis of the Overall status measure of the Fabric Interconnect Uplink Ethernet Ports test ........................................ 90

Figure 15: The detailed diagnosis of the Overall status measure of the Fabric Interconnect Fans test ............................................................... 100

Figure 16: The detailed diagnosis of the Fabric Interconnect Uplink FC Ports test .......................................................................................... 109

Figure 17: The detailed diagnosis of the Overall status measure of the Fabric Interconnect Details test ............................................................ 113

Figure 18: The detailed diagnosis of the Overall status measure of the LAN Cloud Port Channels Test ........................................................... 118

Figure 19: The detailed diagnosis of the Overall Status measure of the LAN Cloud PC Ethernet Ports test ...................................................... 121

Figure 20: The tests mapped to the Blades layer ........................................................................................................................................... 122

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

1

Monitoring the Cisco UCS Manager

The Cisco Unified Computing System (UCS) is a data center computing solution composed of

computing hardware, virtualization software, switching fabric, and management software. The idea

behind the system is to reduce total cost of ownership and improve scalability by integrating the

different components into a cohesive platform that can be managed as a single unit. Just-In-Time

deployment of resources and 1:N redundancy are also possible with a system of this type.

Figure 1 depicts the architecture of Cisco UCS.

Chapter

1

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

2

Figure 1: The architecture of the Cisco UCS

The computing component of the UCS is available in two versions; the B-Series (a modular package

consisting of a powered chassis and full or half slot blade servers), and the C-series rackmount servers

(that can be used with or without UCS, or mixed with blade UCS systems). Both form factors utilize

the same standard components seen throughout the industry, including Intel Nehalem processors and

DIMM memory. The servers are distinctive for supporting Converged Network Adapters ( CNAs), Port

Virtualization, and in some models the Catalina chipset (ASICs that expand the number of memory

sockets than can be connected to a single memory bus).

Besides the blade servers and chassis, the other core components of the Cisco UCS are as follows:

 UCS manager: Cisco UCS Manager implements policy-based management of the server and

network resources. Network, storage, and server administrators all create service profiles,

allowing the manager to configure the servers, adapters, and fabric extenders and appropriate

isolation, quality of service (QoS), and uplink connectivity. It also provides APIs for integration

with existing data center systems management tools. An XML interface allows the system to

be monitored or configured by upper-level systems management tools.

 UCS fabric interconnect: Networking and management for attached blades and chassis with

10 GigE and FCoE. All attached blades are part of a single management domain. Deployed in

redundant pairs, the 20-port and the 40-port offer centralized management with Cisco UCS

Manager software and virtual machine optimized services with the support for VN-Link.

 Cisco Fabric Manager: manages storage networking across all Cisco SAN and unified fabrics

with control of FC and FCoE. Offers unified discovery of all Cisco Data Center 3.0 devices aa

well as task automation and reporting. Enables IT to optimize for the quality-of-service (QoS)

levels, performance monitoring, federated reporting, troubleshooting tools, discovery and

configuration automation.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

3

 Fabric extenders: connect the fabric to the blade server enclosure, with 10 Gigabit Ethernet

connections and simplifying diagnostics, cabling, and management. The fabric extender is

similar to a distributed line card and also manages the chassis environment (the power supply,

fans and blades) so separate chassis management modules are not required. Each UCS

chassis can support up to two fabric extenders for redundancy.

The health of the Cisco UCS platform hence largely relies on how the blade chassis, the blade servers,

the fabric interconnects and extenders are functioning. This implies that issues in the availablity /

operability of one/more of these components, or the unexpected power/thermal/voltage failures they

may encounter can degrade the overall performance of the Cisco UCS. In order to avoid this, the

health and operational efficiency of the integral components of the platform should be continuously

monitored, and issues proactively reported.

eG Enterprise provides a 100%, web-based Cisco UCS Manager monitoring model that periodically

monitors the Cisco UCS manager, discovers the chassis, I/O modules, blades, and fabric interconnects

managed by the UCS manager, and determines the current status of each of these components.

Figure 2: Layer model of the Cisco UCS Manager

Each layer of Figure 2 is mapped to a series of tests that instantly capture current/potential

abnormalities in the state and functioning of the core components managed by the Cisco UCS

manager, and alerts administrators to the same. With the help of the metrics collected by these tests,

administrators can find quick and accurate answers for the following queries:

 Are all I/O modules (i.e., fabric extenders) operating normally? Is any I/O module in a

degraded/powered-off/inoperable state currently? If so, which one is it?

 Is any I/O module experiencing any critical performance issues now?

 How is the power/voltage/thermal states of the I/O modules?

 Is any I/O module missing?

 Is the temperature of all I/O modules normal? Is any I/O module experiencing abnormal

temperatures?

 Is any fan inoperable? In which chassis, does this fan exist?

 Does any fan operate at abnormal speeds?

 Is any fan experiencing any performance failures?

 Have non-recoverable problems occurred in the power/thermal /voltage states of any fan?

 How is the overall health of the chassis? Is any chassis in an inoperable state currently?

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

4

 Is any chassis license-insufficient?

 Are the power/thermal/voltage states of all chassis normal?

 Is any chassis receiving / transmitting more power than it can handle?

 Which fan module is currently in an inoperable state?

 Which fan module is behaving abnormally?

 Are all backplane ports healthy?

 Have any operational/performance issues been detected in any of the PSUs in the chassis?

 Which PSU is receiving voltage over 210 volts and emitting voltage over 12 volts?

 Are the fabric interconnects operating normally?

 Do the fabric interconnects have enough CPU and memory resources at their disposal? Is any

fabric interconnect experiencing a CPU/memory contention?

 Are the PSUs of the fabric interconnects operating normally?

 Is the power/voltage input and output of the PSUs within acceptable limits?

 Have any uplink ethernet ports failed?

 Which uplink ethernet port is seeing very high traffic?

 Are the fans of all fabric interconnects operating normally?

 Is any uplink fibre channel port in an abnormal state?

 Are there any disabled uplink fibre channel ports?

 Is any fibre channel port seeing very high traffic?

 Is any fibre channel port experiencing too many errors in transmission?

 Are the blade servers in a chassis healthy?

 Is any blade server unavailable?

 Is the power state/slot state of the blade servers OK?

 Are the blade servers utilizing memory optimally? If any blade server over-utilizing the

memory?

 Is the motherboard of any blade server consuming power/current excessively?

 Is the temperature of the motherboard normal? If not, then which side of the motherboard is

experiencing abnormal temperatures - the front or the rear?

 Is the temperature of any memory array of any blade server very high?

The sections that follow will discuss each layer of Figure 2 of this document.

1.1 UCS Chassis Layer

The Cisco UCS server chassis and its components are part of the Cisco Unified Computing System.

The Cisco UCS server chassis system consists of the following components:

 Cisco UCS server chassis

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

5

 Cisco UCS blade servers-up to eight half-width or four full-width blade servers, each

containing two CPUs and holding up to two hard drives

 Cisco UCS I/O Module—up to two I/O modules, each providing four ports of 10-Gb Ethernet,

Cisco Data Center Ethernet, and Fibre Channel over Ethernet (FCoE) connection to the fabric

interconnect

 A number of SFP+ choices from copper to fiber

 Power supplies—up to four 2500 Watt hot-swapable power supplies

 Power Distribution Unit

 Fan modules—eight hot-swapable fan modules

As a problem in the chassis system can affect the overall performance of the Cisco UCS platform, you

need to shield the chassis and its integral components from permanent physical or operational

damage. To achieve this, you need proactive updates of probable threats to the health of the chassis

system; these updates will enable you to initiate corrective measures before it is too late. The tests

mapped to this layer provide you with such problem updates.

With the help of these tests, you can keep an eye on the status of each chassis managed by the Cisco

UCS manager and also its core components such as the fabric extemders, fan modules, power

supplies, etc., and quickly detect abnormalities.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

6

Figure 3: The tests mapped to the UCS Chassis layer

1.1.1 Chassis IO Modules Test

The Cisco UCS chassis contains I/O Modules or Fabric Extenders that allow the blade servers in the

chassis to communicate with Cisco UCS Fabric Interconnects. The chassis supports up to two I/O

Modules, each with four I/O ports.

The Cisco UCS Fabric Extenders bring the unified fabric into the blade server enclosure, providing 10

Gigabit Ethernet connections between blade servers and the fabric interconnect, simplifying

diagnostics, cabling, and management.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

7

The Cisco UCS Fabric Extenders extend the I/O fabric between the Cisco UCS Fabric Interconnects and

the Cisco Blade Server Chassis, enabling a lossless and deterministic Fibre Channel over Ethernet

(FCoE) fabric to connect all blades and chassis together. Since the fabric extender is similar to a

distributed line card, it does not do any switching and is managed as an extension of the fabric

interconnects. This approach removes switching from the chassis, reducing overall infrastructure

complexity and enabling the Cisco Unified Computing System to scale to many chassis without

multiplying the number of switches needed, reducing TCO and allowing all chassis to be managed as a

single, highly available management domain.

The Cisco UCS Fabric Extenders also manages the chassis environment (the power supply and fans as

well as the blades) in conjunction with the Fabric Interconnects. Therefore, separate chassis

management modules are not required.

Cisco UCS Fabric Extenders fit into the back of the Cisco UCS Chassis. Each Cisco UCS Chassis can

support up to two Fabric Extenders, enabling increased capacity as well as redundancy.

This test monitors the overall health of each of the I/O Modules present in every chassis managed by

the Cisco UCS manager, and in the process, promptly alerts you to abnormalities in the power,

thermal, voltage states of the modules and sudden spikes in the ambient/ASIC temperature of the

modules. This way, defective I/O modules come to light.

Purpose

Monitors the overall health of each of the I/O Modules present in every chassis of

managed by the Cisco UCS manager, and in the process, promptly alerts you to

abnormalities in the power, thermal, voltage states of the modules, or a sudden

increase in the ambient/ASIC temperature of the modules

Target of the

test

A Cisco UCS manager

Agent

deploying the

test

A remote agent

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

8

Configurable

parameters for

the test

1. TESTPERIOD – How often should the test be executed

1. HOST – The IP address of the host for which the test is being configured.

2. PORT – The port at which the specified HOST listens. By default, this is NULL.

3. UCS USER and UCS PASSWORD – Provide the credentials of a user with at least

read-only privileges to the target Cisco UCS manager.

4. CONFIRM PASSWORD- Confirm the password by retyping it here.

5. SSL - By default, the Cisco UCS manager is SSL-enabled. Accordingly, the SSL

flag is set to Yes by default.

6. WEB PORT- By default, in most virtualized environments, Cisco UCS manager

listens on port 80 (if not SSL-enabeld) or on port 443 (if SSL-enabled) only. This

implies that while monitoring Cisco UCS manager, the eG agent, by default,

connects to port 80 or 443, depending upon the SSL-enabled status of Cisco

UCS manager - i.e., if Cisco UCS manager is not SSL-enabled (i.e., if the SSL

flag above is set to No), then the eG agent connects to Cisco UCS manager

using port 80 by default, and if Cisco UCS manager is SSL-enabled (i.e., if the

SSL flag is set to Yes), then the agent-Cisco UCS manager communication

occurs via port 443 by default. Accordingly, the WEBPORT parameter is set to

default by default.

In some environments however, the default ports 80 or 443 might not apply. In

such a case, against the WEBPORT parameter, you can specify the exact port at

which the Cisco UCS manager in your environment listens, so that the eG agent

communicates with that port for collecting metrics from the Cisco UCS manager.

7. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG

Enterprise suite embeds an optional detailed diagnostic capability. With this

capability, the eG agents can be configured to run detailed, more elaborate tests

as and when specific problems are detected. To enable the detailed diagnosis

capability of this test for a particular server, choose the On option. To disable

the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be

available only if the following conditions are fulfilled:

 The eG manager license should allow the detailed diagnosis capability

 Both the normal and abnormal frequencies configured for the detailed

diagnosis measures should not be 0.

Outputs of the

test

One set of results for each I/O module in each chassis managed by the Cisco UCS

manager being monitored

Measurements

made by the

Measurement

Unit

Interpretation

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

9

test

Configuration

state:

Indicates the

ccurrent

onfiguration status

of this I/O module

present in this

chassis.

The States reported by this measure and

their corresponding numeric equivalents are

described in the table below:

Numeric Value

State

0

Un-initialized

1

Un-acknowledged

2

Unsupported-

connectivity

3

Ok

4

Removing

Note:

By default, this measure reports the above-

mentioned States while indicating the

configuration status of the I/O module in

this chassis. However, in the graph of this

measure, states will be represented using

the corresponding numeric equivalents i.e.,

0 to 4.

The detailed diagnosis of this measure

provides the Time, ID, PID, Side, Chassis

ID, Fabric ID, Revision, Serial Number and

Vendor attributes for each I/O module.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

10

Overall status:

Indicates the overall

status of this I/O

module present in

this chassis.

The States reported by this measure and

their corresponding numeric equivalents are

described in the table below:

Numeric Value

State

0

Unknown

1

Operable

2

Inoperable

3

Degraded

4

Powered-off

5

Power-problem

6

Removed

7

Voltage-

problem

8

Thermal-

problem

9

Performance-

problem

10

Accessibility-

problem

11

Identity-

unestablishable

12

Bios-post-

timeout

13

Disabled

51

Fabric-conn-

problem

52

Fabric-

unsupported-

conn

81

Config

82

Equipment-

problem

83

Decommissioni

ng

.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

11

84

Chassis-limit-

exceeded

100

Not-supported

101

Discovery

102

Discovery-

failed

103

Identify

104

Post-failure

105

Upgrade-

problem

106

Peer-comm-

problem

107

Auto-upgrade

Note:

By default, this measure reports the above-

mentioned States while indicating the status

of the I/O module in this chassis. However,

in the graph of this measure, states will be

represented using the corresponding

numeric equivalents only.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

12

Operability:

Indicates the

current operating

state of this I/O

module present in

this chassis.

The States reported by this measure and

their corresponding numeric equivalents are

described in the table below:

Numeric Value

State

0

Unknown

1

Operable

2

Inoperable

3

Degraded

4

Powered-off

5

Power-

problem

6

Removed

7

Voltage-

problem

8

Thermal-

problem

9

Performance-

problem

10

Accessibility-

problem

11

Identity-

unestablisha

ble

12

Bios-post-

timeout

13

Disabled

51

Fabric-conn-

problem

52

Fabric-

unsupported-

conn

81

Config

82

Equipment-

problem

83

Decommissio

ning

84

Chassis-limit-

exceeded

100

Not-

supported

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

13

101

Discovery

102

Discovery-

failed

103

Identify

104

Post-failure

105

Upgrade-

problem

106

Peer-comm-

problem

107

Auto-upgrade

Note:

By default, this measure reports the above-

mentioned States while indicating the

operability of an I/O module in this chassis.

However, in the graph of this measure,

states will be represented using their

corresponding numeric equivalents only.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

14

Performance

state:

Indicates the

current

performance status

of this I/O module

present in this

chassis.

The States reported by this measure and

their corresponding numeric equivalents are

described in the table below:

Numeric Value

State

0

Unknown

1

Ok

2

Upper-non-

recoverable

3

Upper-critical

4

Upper-non-

critical

5

Lower-non-

critical

6

Lower-critical

7

Lower non-

recoverable

100

Not-supported

Note:

By default, this measure reports the above-

mentioned States while indicating the

performance state of an I/O module.

However, in the graph of this measure,

states will be represented using the

corresponding numeric equivalents.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

15

Power state:

Indicates the

current power

status of this I/O

module in this

chassis.

The State values reported by this measure

and their corresponding numeric

equivalents are described in the table

below:

Note:

By default, this measure reports the above-

mentioned States while indicating the power

state of an I/O module. However, in the

graph of this measure, states will be

represented using their corresponding

numeric equivalents only.

Numeric Value

State

0

Unknown

1

On

2

Test

3

Off

4

Online

5

Offline

6

Offduty

7

Degraded

8

Power-save

9

Error

10

Not-

supported

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

16

Presence state:

Indicates the

current state of this

I/O module in this

chassis.

The State values reported by this measure

and their corresponding numeric

equivalents are described in the table

below:

Note:

By default, this measure reports the above-

mentioned States while indicating the

current state of the I/O module in this

chassis. However, in the graph of this

measure, states will be represented using

their corresponding numeric equivalents

only.

Numeric Value

State

0

Unknown

1

Empty

10

Equipped

11

Missing

12

Mismatch

13

Equipped-

not-primary

20

Equipped-

identity-

unestablisha

ble

30

Inaccessible

40

Unauthorize

d

100

Not-

supported

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

17

Thermal state:

Indicates the

current thermal

state of this I/O

module present in

this chassis.

The State values reported by this measure

and their corresponding numeric

equivalents are described in the table

below:

Numeric Value

State

0

Unknown

1

Ok

2

Upper-non-

recoverable

3

Upper-critical

4

Upper-non-

critical

5

Lower-non-

critical

6

Lower-critical

7

Lower non-

recoverable

100

Not-supported

Note:

By default, this measure reports the above-

mentioned States while indicating the

thermal state of the I/O modules in this

chassis. However, in the graph of this

measure, states will be represented using

the corresponding numeric equivalents

only.

Nu

mer

ic

Val

ue

Stat

e

0

Unk

now

n

1

Ok

2

Upp

er-

non

-

rec

ove

rabl

e

3

Upp

er-

criti

cal

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

18

Voltage state:

Indicates the

current voltage

state of this I/O

module present in

this chassis.

The State values reported by this measure

and their corresponding numeric

equivalents are described in the table

below:

Note:

By default, this measure reports the above-

mentioned States while indicating the

voltage state of the I/O module in this

chassis. However, in the graph of this

measure, states will be represented using

their corresponding numeric equivalents

only.

Numeric

Value

State

0

Unknown

1

Ok

2

Upper-non-

recoverable

3

Upper-critical

4

Upper-non-

critical

5

Lower-non-

critical

6

Lower-critical

7

Lower non-

recoverable

100

Not-supported

Ambient

temperature:

Indicates the

current ambient

temperature of this

I/O module present

in this chassis.

Celcius

An abnormal temperature may cause

severe damage to the I/O modules.

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

19

ASIC

temperature:

Indicates the

current temperature

of the ASIC

(Application-Specific

Integrated Circuit)

in this I/O module

present in this

chassis.

Celcius

An application-specific integrated circuit

(ASIC) is an integrated circuit (IC)

customized for a particular use, rather than

intended for general-purpose use.

If an ASIC registers an abnormal

temperature, it may severely affect the

operations of the I/O module in which that

ASIC operates.

The detailed diagnosis of Configuration state measure provides the Time, ID, PID, Side, Chassis ID,

Fabric ID, Revision, Serial Number and Vendor attributes for each I/O module.

sFigure 4: The detailed diagnosis of the Configuration state measure of the Chassis I/O Modules Test

1.1.2 Chassis Fans Test

A Cisco Blade Server Chassis contains the following components:

 Cisco UCS Fabric Extenders—Up to two fabric extenders (FEX), each FEX provides four ports of

10-Gigabit Ethernet, Cisco Data Center Ethernet, and Fibre Channel over Ethernet (FCoE)

 SFP+ transceiver choices that include copper and fiber optic

 Power supply units—Up to four 2500 W hot-swappable power supply units

 Fan modules—Eight hot-swappable fan modules

 Cisco UCS Blade Servers —Up to eight half-wide blade servers or four full-width blade servers,

each holding RAID capable hard drives

This test monitors the overall health of each fan present in each chassis managed by the Cisco UCS

manager, and proactively alerts users to the following:

 Fans that are in an abnormal operational state;

 Fans that are in a critical performance/thermal/voltage state;

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

20

 Fans in a degraded/errored power state;

 Fans operating at abnormal speeds.

Purpose

Monitors the overall health of each fan module present in each chassis managed by

the Cisco UCS manager, and proactively alerts users to the following:

 Fans that are in an abnormal operational state;

 Fans that are in a critical performance/thermal/voltage state;

 Fans in a degraded/errored power state;

 Fans operating at abnormal speeds.

Target of the

test

A Cisco UCS manager

Agent

deploying the

test

A remote agent

M o n i t o r i n g t h e C i s c o U C S M a n a g e r

21

Configurable

parameters for

the test

1. TESTPERIOD – How often should the test be executed

2. HOST – The IP address of the host for which the test is being configured.

3. PORT – The port at which the specified HOST listens. By default, this is NULL.

4. UCS USER and UCS PASSWORD – Provide the credentials of a user with at least

read-only privileges to the target Cisco UCS manager.

5. CONFIRM PASSWORD- Confirm the password by retyping it here.

6. SSL - By default, the Cisco UCS manager is SSL-enabled. Accordingly, the SSL

flag is set to Yes by default.

7. WEB PORT- By default, in most virtualized environments, Cisco UCS manager