SolutionPack for Cisco UCS

Table of Contents

Overview

This article explains how to install and configure the SolutionPack for Cisco UCS. The SolutionPack for Cisco UCS generates reports that encompass compute, network, and storage access components of the unified fabric. The SolutionPack generates uptime reports for the UCS Managers and enables you to see into the solution as managed by the unified management domain. In addition, the SolutionPack for Cisco UCS obtains real-time and historical data through various reports that indicate events and faults in the system.

This article applies to EMC ViPR SRM version 3.5.1.

reports screen

SolutionPack for Cisco UCS

Back to Top

Technical specifications

SolutionPack version

Compatible ViPR SRM version

Data collection methods

Main reports

Back to Top

Configuring the UCS Manager

Enable XML API for the Cisco UCS Manager.

Before you begin

Procedure

  1. Log in to the Cisco UCS Manager web console.
  2. Navigate to Admin > Communication Management > Communication Services.
  3. Verify that the HTTP & CIM XML services are enabled.
    If the Redirect HTTP to HTTPS option is enabled, you will need to use secure communication when configuring your SolutionPack block.
  4. If you want to use secure communications between the collector and the UCS Manager:
    • Choose the secure communication option when adding the UCS Manager.
    • Configure HTTPS on the Communication Services page of UCS Manager.

After you finish

EMC recommends that you create a new dedicated service account for SolutionPack integration. Role-read-only role is sufficient for the SolutionPack to work properly.

Back to Top

Installing the SolutionPack

Before you begin

ViPR SRM core modules must be up-to-date in all servers because not all module dependencies are validated during the SolutionPack installation or update process.

Procedure

  1. Log in.
  2. Click Administration.
  3. Click Centralized Management.
  4. Click SolutionPacks.
  5. Select SolutionPack Center.
  6. Select the SolutionPack for Cisco UCS in the Browse and Install SolutionPacks screen.
  7. Click Install.
    The remaining steps assume a typical four VM deployment.
  8. In the Pre-configured alerts field in the Select the components to install window, select the Primary Backend host.
  9. In the Data Collection field, select the Collector host.
  10. In the Events field, select the Backend host.
  11. In the Reports field, select the Frontend host.
  12. Click Next.
  13. In the Alerting on data collection field of the Pre-configured alerts window, you can select a different destination for alerts: select Add a new Alerting on data collection, and select a Primary Backend host as the Alerting Web Service Instance.
  14. In the Recipient for email alerts field, type an email address that will be sent alerts.
  15. Click Next.
  16. In the Data Collection window, make a selection in the Data Collection field.
  17. If you select Add a new Data collection, enter information for the new data collection. In the Hostname or IP address to send data field, type the Primary Backend host.
  18. Leave Enable alerting on data collected selected.
  19. Make a selection in the Alerting on data collection field.
    If you select Add a new Alerting on data collection, type information for the new alerting destination. In Alerting Backend the hostname or IP address field, select the Primary Backend host.
  20. Make a selection in the Property Store configuration field to identify the APG property store. If you select Add a new Property Store configuration, type information for the new property store.
  21. Type information for the Cisco UCS configuration.
    1. In the UCS type field, select UCS Manager (Blade Chassis) or UCS C-Series (Server).
    2. In Hostname or IP address type the UCS management host.
    3. In the Username and Password fields, type the credentials for the management server.
    4. Select Enable secure connection, if desired.
    5. In the Communication port field, type the port number for the management server.
  22. Select the Enable events collection checkbox.
  23. In the Event server hostname or IP address field, select the Backend host where the events server runs. The default port is 52007.
  24. In the Server port number field, enter a port number for events collection.
  25. Select Use advanced settings to configure polling settings.
  26. Click Next.
  27. In the Events window, select an Event database. If you select Add a new Events database, type information for the new events database. Type the database information for the events database that runs on the Primary Backend host. The default Database port is 53306. The default Event server port number is 52007.
  28. Click Next.
  29. In the Administration Web-Service Instance field on the Reports window, select the Frontend host.
  30. Click Install.
    The SolutionPack installation begins.
  31. Click Ok once installation is complete.
    Performance data will displayed in about an hour.
Back to Top

Importing the new database schema

Before you begin

Starting with Watch4net 6.2u4, schema are preloaded. If you installed from an earlier version, import the new database schema.

Procedure

  1. Load the events block file Event-Processing/Generic-Live-Writer/cisco-ucs/ddl/my-ucs_live.sql.
  2. Run mysql-client.sh (mysql-client.cmd on Windows).
  3. Type username, database name, and password.
  4. Copy the contents of the /my-ucs_live.sql file and paste it into the mysql client at the mysql> prompt.
    This creates the ucs_live table.
  5. Start the event processing manager service.
  6. To enable events reporting from the frontend:
    1. Edit the Web-Application configuration file Web-Servers/Tomcat/Default/conf/Catalina/localhost/APG.xml.
    2. If the cisco-ucs-events section is present, uncomment it.
    3. If the cisco-ucs-events section is missing, add the following lines:
      <!-- cisco-ucs-events --> 
      <ResourceLink name="jdbc/FLOW-UCS-LIVE:{ mapping=FLOW-UCS.xml, table=ucs_live
       }" global="jdbc/FLOW-EVENTS" type="javax.sql.DataSource" />
  7. Restart the tomcat service.
Back to Top