Type
  • Best Practice
Description
  • This article explains how to monitor a Cisco UCS B-Series Blade Chassis with Hardware Sentry KM.
Additional Keywords
  • Cisco, Cisco UCS, B-Series, Blade Chassis

Related Topics

Knowledge Base

Monitoring a Cisco UCS B-Series Blade Chassis

KB1059 - Dec 09, 2010 - Last reviewed on Jan 10, 2018

Principle

The Cisco UCS B-Series infrastructure consists of:

  • A main chassis (UCS 5100) with the blade servers (B-Series)
  • A couple of Fabric Interconnect Switches.

The switches are responsible for linking the blade servers to the LAN and to a SAN (optional). The switch is capable of handling both traffics on the same backplane (actually everything is 10 Gb/s Ethernet, and SAN traffic is encapsulated into Ethernet frames).

The switch is also responsible for the management of the entire platform. UCS Manager, the Cisco built-in administration tool, is actually a Web application running on the switch itself. It gives visibility on the health of the main chassis (temperature, cooling, powering), the health of the interconnect switches (temperature, cooling, powering, connectivity) and an overall status of each blade server.

In order to cover the entire UCS B-Series platform, Hardware Sentry KM connects to the switch (through Cisco’s native UCS XML API) to gather all metrics related to the main chassis and the switch.

The KM also needs to connect to each blade server individually to gather internal metrics that are not available through UCS Manager: storage subsystem, network traffic, a few environmental parameters.

Prerequisites

A user account with operator privileges is required to connect to the UCS Manager.
  1. Connect to the Cisco UCS Manager from the server on which the PATROL Agent is running.
  2. Enter the credentials that you will also use to configure the monitoring of your Cisco UCS in the TrueSight console.

Monitoring from a PATROL console

  1. In the PATROL Console, [right-click] on the hardware icon › [KM Commands] › [Add a Remote System or an External Device]
  2. Accept the End User License Agreement and click [Next].
  3. Enter the Interconnects DNS Name.  Select System or Device Type “Management Card/Chip, Blade Chassis, ESXi” and click [Next]
  4. Select Manually choose which connectors to use and click [Next]
  5. Select Cisco UCS Manager (Fabric Interconnect Switch) Connector and click [Next]
  6. Enter valid UCS Manager Credentials for the Interconnect Switch. If you are using a LDAP account, strictly follow the LDAP account syntax (e.g.: ucs-local\sam).

    Note: If you are using a LDAP account and if the PATROL agent is running on UNIX/Linux systems, you will have to use a second backlash to protect the first one in the shell command (e.g.: ucs-local\\sam)

  7. Click [Next].
  8. Click [Finish].

Monitoring from a TrueSight console

Configuring TrueSight – Hardware Sentry

  1. Log on to the TrueSight console.
  2. In the navigation pane, expand Configuration and select Infrastructure Policies.
  3. In the Infrastructure Policies page, ensure that the Monitoring tab is selected and click Create Policy.
  4. In the Create Monitoring Policy page, specify the monitoring policy properties:
    1. Enter the Internal ID of the Cisco UCS you wish to monitor (ucs-manager in our example). This ID will be used as a label to identify the device in the TrueSight console.
    2. Enter the actual hostname or IP address of the Cisco UCS (ucs-manager in our example).
    3. From the Device Type list, select "Management Card/Chip, Blade Chassis, ESXi".
    4. (Optional) Enter the FQDN to associate the system to another device in TrueSight. The FQDN uniquely distinguishes a device from any other system and ensures that a device monitored via their management cards or through controllers, for example, is properly identified.
  5. Scroll down to the Cisco UCS section.
  6. Select the "Enable Cisco UCS" option.
  7. Enter the same credentials as used above to establish the connection to the UCS Manager's URL.
  8. By default, the encryption is enabled to enable the SSL Encryption for UCS login (HTTPS).
  9. Scroll down to the Device Advanced Settings section and expand the Connectors panel
  10. From the Connector Selection list, select "Use Specified Connectors"
  11. In the Connector File Names, enter the name of the connector you wish to use, that is MS_HW_CiscoUCSBlade.hdf for Cisco UCS.
  12. Click OK twice to save your settings.
  13. After a few minutes, the newly discovered devices is displayed in the Devices view: