How to Collect Logs from CB2000
Content

Environment

  • Compute Blade 2000 (CB2000).

Procedure

Note: You may need more than one log set type for a case. For example, if the customer had a spontaneous reboot of a Windows host, we would need a getconfig and SVP logs. If the customer had an HVM Virtual Server crash, then we would need a getconfig of that host type when it comes back up, and the HVM dump (which would come with an SVP dump). Please use your best judgment for which log gathering procedures apply for the case.

All procedures can be run with the customer's credentials.

Please disable any web browser popup blockers during the log collection procedure and file upload. 

Operating System:

 

IP Switches:

  • Telnet to the switch
  • Enable log capture for Putty, TeraTerm or any other telnet application you might be using.
  • Run "show tech-support"
  • Save the output of the text to a log file

 

FC Switches:

Refer to the solution: Brocade Data Collection.

Chassis Data Collection:

The easiest way to gather logs from the SVP is through its web interface.

  1. Like the AMS, use a web browser and the IP Address to get to the SVP Web interface.
    090240412003621.png

  2. Navigate to SVP Web interface → Maintenance Tab → Log → Dump Log
  3. On the dropdown menu select "All management modules and partitions".
  4. Click "Download".
    090240412003622.png

  5. A pop-up window may appear, asking to save the file, the resulting file will have the extion ".dmp".

 

Chassis Data Collection - Alternate Method:

This alternate method of getting the logs from the SVP is via the CLI. This may be faster for the customer depending on the situation, or necessary if they are unable to access the web interface.

  1. Telnet/SSH to the SVP IP address.
  2. Type S to enter the SVP
  3. Type DL for Download Logs
  4. Type D for dump logs to file.
    Use EX Command to return to Main Menu.

    Use HE Command to get a list of available commands

    4601RZ0 00003(1)SVP>DL

    (S,E,D,P,M,A,F,I,C,[Q]) : D

    Select module (P=Partition,M=Management module,A=All,[Q=Quit]) : A

    WARNING : If confirm, it will take a few minutes to dump the log to the file.

    Confirm? (Y,[N]) :
  5. Once completed, the logs can be found on the SVP. You will need to connect to the SVP via FTP to obtain the logs, using an FTP application such as FileZilla.
  6. Upload the file to TUF.

 

HVM Log Collection:

Collect the LPAR manager dump into and from SVP on the LP screen:

  1. Connect to the SVP and enter the type P.
  2. Enter the partition number that is running HVM.
  3. If the blade is running HVM then you will be shown the main window.
    090240412003624.png

    090240412003625.png
     
  4. Select "LP Options" on the LP screen.
    090240412003626.png

  5. Pressing the [Enter] key for "Execute" of "Take LP Dump" displays the subscreen. Select "Yes."
    090240412003627.png

  6. Make sure that "Completed. Please check LP System Logs screen" has appeared.
    090240412003628.png
     
  7. In the above operation, it takes two or three minutes until the LPAR manager dump is stored in SVP.
  8. Press the [Esc] key to return to the LP screen.
  9. Select "LP System Logs."
    090240412003629.png

  10. Press the [Enter] key for the level selection portion in the upper right of the screen.
    090240412048782.png
     
  11. The subscreen appears. Select "Error/Warn./Info."
    090240412003632.png

  12. Make sure that the level selection indicates "All Level."
    090240412048783.png

  13. Make sure that two "LP dump transfer succeeded." events are obtained around the time when the LP dump was obtained. If no events are displayed, contact the support section.
    090240412003633.png

  14. According to the Dump Collection (Case 1) procedure, obtain the LP dump stored in SVP.
    Note: To obtain two or more dumps, repeat steps (1) to (10).
  15. When the HVM dump is complete, then you must go back and follow STEP 1 of the "Chassis Data Collection".
Attachments
CXone Metadata

Tags: CB2000,Chassis dump logs,CB2000 dump,CB2000 Dump logs

PageID: 11823