How to Create/Upload Diagnostic Log File Bundle for an Oracle Fabric Interconnect (Formerly Xsigo)

Asset ID:	1-71-1517366.1
Update Date:	2017-08-01
Keywords:

Solution Type Technical Instruction Sure

Solution 1517366.1 : How to Create/Upload Diagnostic Log File Bundle for an Oracle Fabric Interconnect (Formerly Xsigo)

Applies to:

Oracle Fabric Interconnect F1-4 - Version All Versions to All Versions [Release All Releases]
Oracle Fabric Interconnect F1-15 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Goal

How to Create and Upload Diagnostic Log Bundles for an Oracle Fabric Interconnect

Solution

How to Create

To create/generate Oracle Fabric Interconnect diagnostic log files, log in to the Oracle Fabric Interconnect CLI and output the 'get-log-file -all' command to a file:

NOTE: Remove the <> carets from the command when directing the 'get-log-files -all' command output to a file.

Sample 'get-log-files -all' command output:

*** output file is 3-12312312-iodir1-logs.tar.gz (1003.60K)

It is recommended for any issue where an IO Module or process has crashed, to generate the Fabric Interconnect diagnostic log bundle with the '-cores' option instead of the '-all' option so that the process core files or IO Module 'diag' files can be sent over for analysis.

get-log-files -cores <SR#-Chassisname>-logs.tar

To generate an SR#, login to MOS and open an SR, or call the Oracle Support Hotline in your Global Region.

If uploading multiple Oracle Fabric Interconnect log bundles for the Oracle Virtual Networking Support Group to analyze, download all individual diagnostic log bundles to a local system by using an FTP/SCP client and connect to the Oracle Fabric Interconnect as user ‘root.　After logging in as user ‘root’ traverse to the '/var/fsroot/admin' folder.　Once in the '/var/fsroot/admin' folder, locate the log bundle just created and copy the Oracle Fabric Interconnect diagnostic log bundle off to the local system. May also use the ‘file copy’ command to copy the Fabric Interconnect diagnostic log bundles to another Linux/ESX system for storing or to combine multiple files into one tar archival bundle prior to uploading them to an existing SR at MOS .

Example using the ‘file copy’ Fabric Interconnect CLI command to copy the Oracle Fabric Interconnect diagnostic log bundle off to another system:

# file copy 12312312-iodir1-logs.tar.gz scp://<username>@<hostname or IP>:/path

For ease of use, it is recommended to take the individual diagnostic log bundles from multiple Oracle Fabric Interconnects, host diagnostic log bundles, and Oracle Fabric Manager diagnostic logs and archive them into one combined archive bundle. 　Name the combined diagnostic archive bundle as your SR# (Service Request) # that was assigned when you opened a Service Request through MOS (My Oracle Support) or by calling the Oracle Support Hotline.　File uploads via MOS (My Oracle Support) can handle up to 2GB file sizes.　

How to Upload

Upload the diagnostic log archive for Oracle Virtual Networking Group to analyze by using the methods in the following My Oracle Support Knowledge Document:

"How to Upload Data to Oracle Such as Explorer and Core Files" [ID 10201991.1]

NOTE: The legacy 'file upload'Xsigo Fabric Director CLI command as of February 18, 2013 no longer functions and will fail with the following error message:　

admin@iodir1[xsigo] file upload 3-12312312-iodir1-logs.tar.gz

connect: No route to host

Upload of /opt/xsigo/xsigos/xsigos-3.9.0-XGOS/fsroot/home/admin/f15-sca11-c-logs.tar.gz failed (Failed to connect to FTP server ftp.xsigo.com )

This error occurs because the former Xsigo FTP server is no longer available and the FTP target is hard-coded into the firmware. A bug in BugDB has been created to track resolution to this. Until this is resolved, please use the standard Oracle upload methods described above.

References

<NOTE:1020199.1> - How to Upload Support Files to Oracle Such as Explorer and Crash Dumps

Attachments

This solution has no attachment