ViPR Controller: What information should a customer provide for ViPR Controller issues?

For ViPR Controller issues, we need the information detailed below for further investigation. Attach the information below to the SR.

• What is the ViPR Controller version (from System > Dashboard > Version & License, vipr-xxxx)?

• What is the ViPR Controller Virtual Machines configuration: 2+1 (3 nodes) or 3+2 (5 nodes)?

• What are the steps / changes made to the environment that preceded the issue? If an error is displayed, attach a screenshot of the error or the failed order (including the failed order number and expanded Logs & Execution Steps sections) if the error occurred in an order.

• Is ViPR Controller installed in a lab environment or in a production environment?

• Is a VPLEX discovered in this ViPR Controller instance? If so, what is the VPLEX version? 

• Is the System > Dashboard - System Health Controller Status stable and is the System > Health Status green for all ViPR nodes? Attach screenshots showing that information for each of the 3 or 5 ViPR nodes.

Collect ViPR Controller system logs including the orders as detailed below.

1. Select System > Logs > Download.

2. Set Node: to All Nodes.

3. Set Services: to All.

4. Set Log Level: to DEBUG.
   Note: Although Log Level is set to DEBUG, logs will actually be collected at INFO level unless the ViPR Controller configuration is also modified to enable DEBUG logging per KB30464 (000008413). The modification to enable debug logging should not be used for initial ViPR Controller log collection and should only be used when specifically requested by ViPR Controller Technical Support due to DEBUG Log Level's verbose content.

5. Set Start Time: so that the logs/alerts for the time period of interest are captured, usually about a day before the issue occurred.

6. Set End Time: to current.

7. Set Orders: to All Orders

8. Select the Download button.

9. A logs archive (.zip) file called logs-<date>-<time>.zip is downloaded.

10. This logs archive contains all log, system configuration, and order information.

Attach the zip file to the Service Request.
 

Column Family Information

For ViPR Controller version 3.6.x and higher:
A new  diagutils  tool to collect ViPR Controller information is built-in to ViPR Controller as of version 3.6.x and higher. The diagutils tool can collect the column family information previously collected by the  slither  tool, but it does not require a separate download as with slither. Since slither is deprecated and will not be updated, diagutils (which includes the slither functionality) should be used as of version 3.6.x and higher to collect column family information.

The diagutils tool has the capability to send data directly to an FTP server if available without an intermediate transfer using the diagutils -ftp option as shown in the example below:
./diagutils -min_cfs -ftp ftp://ftp.emc.com -u username -p password 

If a subdirectory exists on the ftp server, diagutils can be used to copy data to the subdirectory as shown in the example below:
./diagutils -all_cfs -properties -health -zk -ftp ftp://ftp.emc.com/subdirectoryname -u username -p password 

A DellEMC ftp site can be provided through a request to ViPR Controller Technical Support. Note: DellEMC ftp temp accounts expire after 7 days to the hour at which time the account and any data are automatically deleted. 

Collect the ViPR Controller column family, properties, health, and zookeeper data as detailed below:
      1. Log in to one of the ViPR Controller nodes as root using Putty or equivalent

      3. Run diagutils using the options:
          ./diagutils -all_cfs -properties -health -zk
          as shown below:

For ViPR Controller version 3.5.x and lower:
Collect a slither 1.4 output as detailed below or a diagutils output (preferred) as detailed above. Diagtutils is compatible with ViPR Controller starting with version 2.4. Diagutils is available for download at 
https://support.emc.com/downloads/32034_ViPR-Controller > Product Tool > Diagutils data collection utility for ViPR Controller 
or 
https://download.emc.com/downloads/DL84052_Diagutils-data-collection-utility-for-ViPR-Controller.zip

• What are the array types & versions?

• For the arrays above what are the corresponding SE / SMI-S versions?

• If any SMI-S errors are displayed please include the SE / SMI-S logs from the relevant SE / SMI-S host(s) as detailed below:

• Brocade / CMCNE switches

• Cisco switches

501341 - ViPR Controller: How to use the Diagutils to collect ViPR data