Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1012402.1
Update Date:2013-11-06
Keywords:

Solution Type  Troubleshooting Sure

Solution  1012402.1 :   Sun StorEdge[TM] 2G switch troubleshooting using log commands  


Related Items
  • QLogic SANbox 5600 Switch
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Switch>SN-DK: Qlogic switch
  •  

PreviouslyPublishedAs
217101


Applies to:

QLogic SANbox 5600 Switch - Version Not Applicable and later
All Platforms

Purpose

 
Occasionally, it may be necessary to inspect the protocol exchange between a device and a Sun/Qlogic 2G Fibre Channel Switch to assist in diagnosing an issue.

The Qlogic/Sun Sanbox2 2G switch has a good set of log commands that can assist in troubleshooting a fibre channel issue. (These are not present on the 1G device.)
By default, the switch is set to log only critical events, but if a problem is currently occurring, then setting the log level to info (informational) can produce a large amount of diagnostic information.

Troubleshooting Steps


To identify and change the current log level and components being logged, connect to the Command Line Interface (CLI) using telnet and issue the following commands:

show log level
by default this is 'Critical'
show log component
by default includes all the following logical components within the
switch:- NameServer MgmtServer Zoning Switch Chassis Blade Port
Eport Snmp Other CimServer
To change either the level or component entries, first enter 'admin' mode.
admin start
To increase the level of log to informational level (highest)
set log level info
To include all components to be logged (initial suggestion)
set log component all
It is also possible to specific a space separated list of components, for instance
set log component NameServer Port
Enable/Start logging with the newly-specified parameters
set log start
The amended level of logging will be effective until the switch is rebooted
or the logging level is lowered manually.
To restore to the original level
set log stop
set log restore
set log start
If you wish to retain the amended setting across switch reboots, issue the command
set log save
When completed exit from 'admin' mode within the CLI
admin end
It is not recommended to leave the log level at info unless there is a specific
need to do so.
Collecting/clearing the logs
----------------------------
The resulting logs at 'info level can be long. Drop any current telnet/CLI
session and start a script or session capture before reconnecting.
To see complete log
show log
To clear log (requires you to enter 'admin' mode)
set log clear
Analyzing the log
-----------------
The log will collect information from the 'component' list that recorded changes. Understanding the details will require some degree of Fibre Channel protocol knowledge. 

It will also be beneficial to collect any messages/logs from the host and storage, bearing in mind that their clocks may be set differently and you will have to adjust event times in 1 or more sets of logs. 



Remember that looking at other switch outputs such as 'show port' and 'show ns' will mean that you do not necessarily need to analyze the switch log. The log will record changes, the show commands will detail current state.



sanbox, switch, log, troubleshooting, san
Previously Published As
78485

Change History
Date: 2004-10-15
User Name: 25440
Action: Approved
Comment: Spellchecked. Made varying use of "admin mode" and "admin level" into "'admin' mode" throughout for consistency. Publishing.
Version: 3
Date: 2004-10-15
User Name: 25440
Action: Accept
Comment:
Version: 0
Date: 2004-10-15
User Name: 102104
Action: Approved
Comment: Very useful document.
Version: 0
Product_uuid
5a28f26e-146b-11d7-8eef-e1eae48719f5|Sun StorageTek 2 Gb 8-Port Switch
3476195a-2994-11d7-83a1-cceb9f78f141|Sun StorageTek 2 Gb 64-Port Switch
0a594ba7-d43c-11d8-ab52-080020a9ed93|Sun StorageTek Network 1 Gb FC Switch-16


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback