IBM Brocade Data Collection Best Practices
seb_ 060000QVK2 Comments (2) Visits (13117)
My friend and colleague here in IBM L2 SAN Support, Serge Monney prepared a "little-helper" article for our clients. It's intended to help you with the Brocade SAN switch data collection in case of a problem. Maybe you even got the link to this article within a case. This is it:
Be prepared to send good logs to your support
Brocade SAN switch have the particularity to have logs with timestamps and logs without timestamps. The logs without timestamps are counters that tell you what is going on or what is going wrong with your frame entering or leaving your switch. To be able to trust the counters we need to set a baseline by clearing the statistics.
Most of the time support needs the following to perform troubleshooting:
How to take a supportsave
(You can download a free version of the Network Advisor after you created an account for mybrocade.com)
Your FTP server will receive multiple files. Please compress them and give the resulting archive file a meaningful name. For example:
(Collecting data using the web interface will not help , you need to collect supportsave with Network advisor or CLI )
And to IBM...
To upload the package, please make use of our Secure Upload web frontend:
Just use your PMR (preferred), RCMS, or CROSS case number for your upload to let the system even notify the support engineer with an update to the case. It's also possible to upload data on the plain Machine Type / Serial Number, but then there won't be any direct correlation to the case. In the field "Upload is for:" always choose "Hardware" when you upload SAN data collections. The email address is optional but it will send you a short notice as soon as the upload completed successfully and the support engineer will be able to contact you via mail if needed. After clicking on "Continue" you can drag and drop the archive file containing the supportsave to upload it. That's it!
Short link for this article: http