HP Comware 5 Debug Manual Vol 2

Table 109 Output from the debugging ipc event ack command
Field
Description
Process ACK from node node1, queue type: type1,
queue ID:id1, ACK: sqn1.
The node received an acknowledgement from node1.
The queue type is type1, queue number is id1, and
packet sequence number is sqn1, where:
Values for the queue type include unicast, multicast,
and mixcast.
Table 4 describes output fields and messages for the debugging ipc event flow-control command.
Table 110 Output from the debugging ipc event flow-control command
Field
Description
IPC procedure eventId1 event, node node1, queue
type type1, queue ID id1.
A node processed an event.
• node1—Node ID.
• eventId1—Event ID. The value is flow-control for a
flow control event.
• type1—Queue type of the event. Its value is always
mixcast.
• id1—Queue number.
Received flow control request from node node1,
queue type: type1, queue ID: id1.
The type1 argument represents the queue type. Its
value is always mixcast.
The send queue (node ID: node1, queue type: type1,
queue ID: id1) was freed from flow control.
Flow control was removed on a send queue.
• node1—Destination node ID. For a unicast, it is the
peer node ID. For a multicast, it is the multicast
group number.
• type1—Queue type. Its value is always mixcast.
Table 5 describes output fields and messages for the debugging ipc event inner command.
Table 111 Output from the debugging ipc event inner command
Field
Description
Quick link transfer is detected between Node node1
and peer node node2.
One node (node1) detects that a quick link transfer
exists on the link to another node (node2).
IPC detected event event1, node node1, queue type
type1, queue ID id1.
The IPC module detected an internal processing event.
The event ID is event1, the node number is node1, the
queue type is type1, and the queue number is id1.
Values for the queue type include unicast, multicast,
and mixcast.
NOTE:
No output is available for the application, assemble, driver, or resend keyword.
Examples
# Enable IPC flow control debugging for the local node and node 5. When flow control starts or ends,
output similar to the following example is generated:
<Sysname> terminal debugging
144