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.
Disable any web browser popup blockers during the log collection procedure and file upload.
You can get logs from the following parts in the chassis:
getconfig
getconfig
supportconfig -l
sosreport
getconfig
Refer to the solution: Brocade VDX Log Collection.
Collecting log through LAN connection:
[en]
, and then press [Enter].
[copy tech-support ftp]
in [#]
prompt, and then press [Enter]
.[MGT]
when [Port type ["DATA"/"MGT"]:]
is prompted, and then press [Enter]
.[IP address]
of the maintenance PC in [Address or name of remote host:]
prompt, and then press [Enter]
.[file name]
in [Destination file name:]
prompt, and then press [Enter]
.[upload]
in [User name:]
prompt, and then press [Enter]
.[password]
in [Password:]
prompt, and then press [Enter]
.[tsdmp successfully ftp'd to xxx.xxx.xxx.xxx:entered file name]
is indicated and [#]
prompt is indicated again.[exit]
in [#]
prompt, and then press [Enter]
.
Tags: CB2500,CB2500 Dump logs,How to collect CB2500 logs,Compute Blade 2500 log collection,Compute data collection,Chassis dump logs
PageID: 11831