HP Comware 5 Debug Manual Vol 2

debugging fc name-service
Use debugging fc name-service to enable debugging for the FC name service.
Use undo debugging fc name-service to disable debugging for the FC name service.
Syntax
debugging fc name-service { all | error | event | packet } [ vsan vsan-id ]
undo debugging fc name-service { all | error | event | packet } [ vsan vsan-id ]
Default
Debugging is disabled for the FC name service.
Views
User view
Default command level
1: Monitor level
Parameters
all: All types of debugging.
error: Error debugging.
event: Event debugging.
packet: Packet debugging.
vsan vsan-id: Enables debugging for the specified VSAN. The vsan-id argument ranges from 1 to 3839.
If you do not specify a VSAN, this command enables debugging for all VSANs.
Examples
# Enable error debugging for the FC name service in all VSANs. Output similar to the following example
is generated when the payload length of received CT packets is shorter than the basic CT header length:
<Sysname> debugging fc name-service error
* Feb 22 11:23:23:145 2010 Sysname FCGS/7/ERROR: (VSAN 1): Payload of the CT frame was
not long enough.
// Payload of the CT frames was not long enough.
# Enable event debugging for the FC name service in all VSANs. Output similar to the following example
is generated when the ESS negotiation succeeds:
<Sysname> debugging fc name-service event
<Sysname> system-view
[Sysname] vsan 1
[Sysname-vsan1] domain restart disruptive
Warning: The command may cause traffic interruption. Continue? [Y/N]:y
*Apr 19 17:22:58:265 2010 Sysname FCGS/7/EVENT: (VSAN 2): Received domain ID change
event..
// FCGS received domain ID change event.
*Apr 19 17:23:09:750 2010 Sysname FCGS/7/EVENT: (VSAN 2): Succeeded in creating ESS tim
er of domain 2.
// FCGS created the ESS timer successfully.
*Apr 19 17:23:15:515 2010 Sysname FCGS/7/EVENT: (VSAN 2): ESS negotiation with doma
33