ViPR SRM 3.6 – SolutionPack for Brocade FC Switch Summary Sheet

Table of Contents

Overview

Learn how to install and configure the SolutionPack for Brocade FC Switch. The SolutionPack for Brocade FC Switch accesses performance data information that was automatically collected and interpreted (using resource grouping and mathematical calculations) from across multiple fabrics.

SolutionPack for Brocade FC Switch

SolutionPack for Brocade FC Switch

Alerts are consolidated from Brocade FC Switches and shown on the All Alerts Console.

Back to Top

Technical specifications

Data collection methods

Note Image
Choose one of the options below. Do not use both options simultaneously.

SMI-S Only
Discover switch topology, performance and zoning details through SMI-S.
SNMP + SMI-S (Zoning only through SMI-S)
Discover switch topology and performance metrics through SNMP. SNMP does not support zoning discovery. Restrict SMI-S discovery to zoning details only.

Main reports

FC Switches Summary
Overviews the FC switches, including key indicators such as name, IP addresses, firmware version, and operational status.
# FC Ports with Errors
Reports the FC ports with errors, such as invalid CRCs, signal losses, or link failures.
Fabrics Overall Health
Reports the current operational status of the switch.
Inventory & Performance
Reports Inter-Switch-Link (ISL) trunking resource usage. ISL monitoring helps administrators determine the sources of traffic on ISLs and identify potential points of congestion in the SAN fabric.
Throughput by Switches (/s)
Reports the Throughput by switches. Typically, this is the sum of throughput for all FC ports belonging to a switch.
Throughput by Port Type (/s)
Reports the Throughput by port type. Typically, this is the sum of throughput of all FC ports of each port type on the switches.
Traffic by Domains (/s)
Reports the Throughput by domains. Typically, this is the sum of throughput for all FC ports belonging to switches regarding the domain id.
Situation To Watch
Highlights risk situations such as FC ports errors.
Virtual Fabrics
Reports the virtual Fabrics configured on all switches available in the environment

Recommendations on using SolutionPack for Brocade FC Switch

The recommended discovery approach is to use SMI-S only data collection (in both fresh deployment of ViPR SRM 3.6 and upgrade from previous versions to 3.6).

SNMP + SMI-S (Zoning only through SMI-S) data collection is supported for backward compatibility with previous versions and will be deprecated in a future release.

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

Brocade switch and SMI agent configuration

You must configure Brocade switches and SMI agents for discovery and alert consolidation in ViPR SRM.

Back to Top

Configuring Brocade SMI Agents

Install and configure Brocade SMI agent for complete switch discovery (if you choose SMI-S Only discovery option) or zoning discovery only (if you choose the SNMP+SMI-S discovery option).

Procedure

  1. Install Brocade SMI agent in one of the following modes:
    Installation mode Description
    Integrated Brocade SMI Agent The Brocade SMI agent is integrated with CMCNE, BNA, CMDCE, DCFM and gets installed when you install any of these products.
    Brocade SMI Agent only (headless installation) Headless installation (silent mode installation) does not need a license and installs the SMI agent only.
    Refer to the CMCNE/CMDCE installation guide for more details on installation and configuration of Brocade SMI agent.
Back to Top

Configuring Brocade switches for alert consolidation

Use the snmpConfig command to forward SNMP v1 traps from Brocade switches to ViPR SRM.

Trap-based alerts for Brocade switches are supported through SNMP regardless of the discovery option you choose. In other words, even if you choose the SMI-S Only discovery approach, configure the switches for SNMP trap forwarding.

Use the snmpConfig command to forward SNMP v1 traps from Brocade switches to ViPR SRM.

Procedure

  1. Log into the Brocade FC switch as the administrator.
  2. Type snmpConfig ––set snmpv1 , and press Enter.
  3. Type the following details, when prompted:
    Option Input
    Community [public]
    Trap recipient's IP address The ViPR SRM trap recipient IP which, in a single vApp installation is the ViPR SRM IP, and in a distributed environment, is the Backend server's IP.
    Trap recipient severity level (0..5)
    Trap recipient port 2041, which is the ViPR SRM trap listening port.
  4. If you have multiple Brocade FC switches in your storage environment, repeat this procedure on each switch.
Back to Top

Configuring Brocade switches for SNMP

Brocade switches have to be configured with SNMP v1/v2c/v3 credentials if you choose SNMP+SMI-S (zoning only through SMI-S) discovery option.

Procedure

  1. Launch a command line interface for the Brocade switch and log in with Administrator credentials.
  2. Perform the following steps to configure the switch for SNMPv1/v2c:
    1. Type snmpConfig --show snmpv1
      The community strings will be listed.
    2. If you wish to change a community string, type snmpConfig --set snmpv1
    3. Enter the new community string and proceed.
  3. Perform the following steps to configure the switch for SNMPv3:
    1. Type snmpConfig --show snmpv3.
      The configuration parameters will be listed.
    2. If you wish to change the parameters, type snmpConfig --set snmpv3
    3. Enter the parameters and proceed.
  4. Repeat these steps for each Brocade switch in your storage environment.
Back to Top

Installing the SolutionPack

Before you begin

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 a note about Alert Consolidation.
  10. Click Next.
    The window displays pre-configured alert details.
  11. 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, choose an alerting web-service instance.
  12. Click Next.
    The window displays data collection details.
  13. 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.
  14. Leave Enable Topology Backend on data collected checked.
  15. From the Topology Service drop-down menu, select existing settings that have been specified for other components, or select Add a new Topology Service.
    If you select Add a new Topology service, provide information about the topology service and the web service. In Topology Service hostname or IP address, specify the Primary Backend.
    From the Web-Service Gateway drop-down menu, select existing settings that have been specified for other components, or select Add new gateway. If you select Add new gateway, provide information about the web-service gateway where the topology service resides.
  16. 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.
  17. (For SRM 3.5.1 and higher) From the SMI-S Discovery Configuration option drop-down menu, select existing settings that have been specified for other components, or add a new configuration. If desired, select Restrict SMI-S to zoning discovery only.
    If the option is selected, SMI-S will be used to discover zoning details only. If unselected, SMI-S will be used to discover switch and zoning details completely.
  18. From the Passive Host Discovery Specific Configuration drop-down menu, select existing settings that have been specified for other components, or add a new configuration. If desired, select Enable Passive Host Discovery.
  19. Optionally, select Configure advanced settings to configure polling settings.
  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 Next.
    The window displays a note about SNMP masks.
  23. Click Install.
  24. Click Ok when the installation is complete.
  25. Click Discovery Center > Devices Management.
  26. Click Brocade SMI Provider.
  27. Click Add new device.
  28. Specify the details of the Brocade SMI Provider 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 SMI Provider IP Address or Host Name field, type the Brocade SMI Provider host.
    3. Enter the access credentials.
    4. If desired, select Enable Secure Connection (SSL).
    5. Type the port number. The default ports are 5988 for non-SSL and 5989 for SSL.
  29. Click Test to validate the credentials.
  30. Click OK.
  31. Click Save.
Back to Top

Passive host discovery configuration options

Enable passive host discovery to see end-to-end topology from hosts to arrays, and identify chargeback on SAN enabled hosts without active host discovery.

You can passively resolve hosts, discovered through the SolutionPack for Brocade FC Switch, from zoning records.

The default zone naming patterns in ViPR SRM are:

z_%h%

z_%h%_*

z_%h%_*_*

%h%_*

After you have enabled passive host discovery, there are two options for passive host configuration.

You can enable passive host discovery while installing the SolutionPack, or you can enable it by reconfiguring the SMI Data Collection component of an existing instance of the SolutionPack.

To enable and add/edit customized zone naming patterns:

Procedure

  1. Select the Enable Passive Host Discovery checkbox.
  2. Select the Customized zone naming patterns checkbox.
    The system displays the four default zone naming templates.
  3. Click the Add button (plus icon) to view the zone naming pattern and host position for a template. Edit the pattern or position if desired.
    Only Java-based zone naming patterns are supported.
    Only plain numbers can be used for the position. Special characters (like $) are not required.

    For more information on writing Java's regular expression refer to http://docs.oracle.com/javase/tutorial/essential/regex/

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