ViPR SRM 3.6 – SolutionPack for Cisco UCS Summary Sheet

Table of Contents

Overview

Learn 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.

SolutionPack for Cisco UCS

SolutionPack for Cisco UCS

Back to Top

Technical specifications

Data collection methods

UCS XML API

Main reports

Power Consumption over Time

Fabric Interconnects

Chassis

System Statistics, Fans, PSU, Interfaces

Events

Supported collection interfaces

For information about supported collection interfaces, refer to the ViPR SRM Support Matrix.

Back to Top

Where to find the latest SolutionPack software

Install the latest core software update for your product suite. SolutionPacks distributed with core software have a 30-day free evaluation period. If you plan to use the software longer than 30 days, you must install a SolutionPack license before the trial period ends.

This 30-day free evaluation only applies to new installations and is not available for upgraded installations. If you upgrade the core software and want to try a new SolutionPack, you must request a license for that SolutionPack.

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. Click Administration.
  2. Click Centralized Management.
  3. Click SolutionPacks.
  4. Click SolutionPack Center.
  5. Select the SolutionPack in the Browse and Install SolutionPacks window.
  6. Click Install.
  7. Type the instance name.
  8. Assign a server for each component.
    In a typical four server deployment, the recommended servers are selected automatically.
  9. Click Next.
    The window displays pre-configured alert details.
  10. From the Alerting on data collection drop-down menu, select existing settings that have been specified for other components, or select Add a new alerting data collection.
    If you select Add a new alerting on data collection, type information about the alerting configuration. In Alerting Backend hostname or IP address, specify the Primary Backend host.
  11. Click Next.
    The window displays data collection details.
  12. From the Data collection drop-down menu, select existing settings that have been specified for other components, or select Add a new data collection.
    If you select Add a new data collection, type information about the data collection. In Hostname or IP address to send data to, use localhost on port 2020, which is the Collector host where the Load Balancer Connector is installed.
  13. From the Frontend Web service drop-down menu, select existing settings that have been specified for other components, or select Add a new Frontend Web service.
    If you select Add a new Frontend Web service, type information about the Frontend Web service.
  14. Select the Enable events collection checkbox.
  15. In the Event server hostname or IP address field, select the Backend host where the events server runs. The default port is 52007.
  16. In the Even server port number field, enter a port number for events collection.
  17. Select Configure advanced settings to configure polling settings.
  18. Click Next.
    The window displays event settings.
  19. 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.
  20. Click Next.
    The window displays reports settings.
  21. In Administration Web-Service Instance, select an existing instance or create a custom instance.
  22. Click Install.
  23. Click Ok when the installation is complete.
  24. Click Discovery Center > Devices Management.
  25. Click Cisco UCS.
  26. Click Add new device.
  27. Specify the details of the Cisco UCS configuration.
    1. In the Device location section, select the server and instance where you want to store the configuration details for this device.
    2. In the UCS type field, select UCS Manager (Blade Chassis) or UCS C-Series (Server).
    3. In Hostname or IP address type the UCS management host.
    4. In the Username and Password fields, type the credentials for the management server.
    5. Select Enable secure connection, if desired.
    6. In the Communication port field, type the port number for the management server.
  28. Click Test to validate the credentials.
  29. Click OK.
  30. Click Save.

After you finish

If you want to discover the Cisco UCS Fabric Interconnects in your environment via SNMP, you must install the Cisco MDS /Nexus SolutionPack in your environment to provide full SNMP masks and capabilities for the SNMP discovery.

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

Confirming report creation

After you install a SolutionPack, you can view its reports.

To view the reports:

Procedure

  1. Go to User Interface > Report Library.
  2. Click the SolutionPack to view its reports.

Results

It may take up to an hour to display all relevant information in these reports.

Back to Top

Troubleshooting

Report display problems

Back to Top

What to do if data does not appear in any reports

Procedure

  1. After the completion of at least three collection cycles, verify if data is populating into the reports. If there is still no data in the reports, continue to the next step.
  2. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to the next step.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Running a scheduled task to import data into reports

After you push a new configuration into a collector, a scheduled task runs and populates the reports with new data. You can manually run the scheduled task to import the data more quickly.

Before you begin

Allow at least three polling cycles to pass before manually running the scheduled task.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Scheduled Tasks.
  4. Click Database.
  5. Select the import-properties-Default task.
  6. Click Run Now.
  7. Confirm success in running the task in the Last Result and Last Result Time columns.
Back to Top

What to do if data does not appear in some reports

Procedure

  1. Run the scheduled task to import data into reports. If there is still no data in the reports, continue to step 2.
  2. Search for the metric in the database.
  3. To view the log files for errors, go to Centralized Management and click Collecting > Collector-Manager::<instance name> > Log Files.
Back to Top

Searching for metrics in the database

You can verify that a metric is being collected and used for reporting when you search and find the metric in the database.

Procedure

  1. Go to the Administration page.
  2. Under Modules, click Management of Database Modules.
  3. On the Metric Selection page, create the filter, type the number of results, and select the properties to display for the metric.
    For example, to list up to 100 results of the SignalWait Time metric with the properties of device and IP, type name=='SignalWaitTime' in the Filter field, 100 in the Maximum results field, and select device and IP for the Properties to show.
  4. Click Query.
    A list of the metric results appears. If nothing displays, the metric is not being collected.
Back to Top

Viewing collector errors in the Collector-Manager log files

Review the Collector-Manager log files to troubleshoot problems with data collection.

Procedure

  1. Click Administration.
  2. Click Centralized Management.
  3. Expand Collecting.
  4. Click the Collector-Manager for your collector instance.
    Collector-Manager::<Collector-Manager instance> - <physical_host_ID>
  5. Expand Log Files and click the View File icon to review the configuration error messages.
Back to Top