HP Comware 5 - HPE Support Center

HP Comware 5 - HPE Support Center
HP Comware 5
Comware 5 Debug Manual
Volume 3
Part number: 5998-5838
Legal and notice information
© Copyright 2014 Hewlett-Packard Development Company, L.P.
No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.
Contents
MAC authentication debugging commands ················································································································· 1
debugging mac-authentication································································································································ 1
MAC-in-MAC debugging commands ···························································································································· 6
debugging minm ······················································································································································ 6
MBGP debugging commands ······································································································································13
debugging bgp update ipv4 multicast ················································································································ 13
MFF debugging commands ··········································································································································16
debugging mac-forced-forwarding ······················································································································ 16
MLD debugging commands ··········································································································································22
debugging mld ······················································································································································ 22
debugging mld proxying ······································································································································ 27
MLD snooping debugging commands·························································································································31
debugging mld-snooping······································································································································ 31
Modem debugging commands ····································································································································36
debugging modem ················································································································································ 36
Monitor Link debugging commands ····························································································································40
debugging monitor-link ········································································································································· 40
MPLS L2VPN debugging commands ···························································································································41
debugging mpls l2vpn ·········································································································································· 41
MPLS L3VPN debugging commands ···························································································································50
debugging l3vpn ··················································································································································· 50
MPLS OAM debugging commands ·····························································································································55
debugging mpls oam ············································································································································ 55
MPLS TE debugging commands ···································································································································62
debugging isis traffic-eng ····································································································································· 62
debugging mpls moam packet ···························································································································· 62
debugging mpls rsvp-te········································································································································· 63
debugging mpls te cspf ········································································································································ 69
debugging mpls te management ························································································································· 75
debugging mpls te protect-switch ························································································································ 78
debugging ospf mpls-te········································································································································· 79
MSDP debugging commands ·······································································································································81
debugging msdp ··················································································································································· 81
MTR debugging commands ··········································································································································84
debugging multiple-topology event ····················································································································· 84
debugging multiple-topology hsb ························································································································ 84
Multicast routing and forwarding debugging commands ·························································································86
debugging mfib ····················································································································································· 86
debugging mrm ····················································································································································· 94
debugging mtracert ··············································································································································· 96
i
Multicast VPN debugging commands ·························································································································98
debugging md ······················································································································································· 98
debugging mtunnel ············································································································································· 101
MVRP debugging commands ···································································································································· 107
debugging mvrp error········································································································································· 107
debugging mvrp event ········································································································································ 107
debugging mvrp packet······································································································································ 108
debugging mvrp state ········································································································································· 109
NAT debugging commands ······································································································································ 113
debugging nat ····················································································································································· 113
debugging userlog nat········································································································································ 116
NAT-PT debugging commands ·································································································································· 118
debugging natpt ·················································································································································· 118
ND attack defense debugging commands ·············································································································· 121
debugging ipv6 nd detection packet ················································································································ 121
NetStream debugging commands ···························································································································· 123
debugging ip netstream event ··························································································································· 123
debugging ip netstream packet ························································································································· 128
NQA debugging commands ····································································································································· 130
debugging nqa ···················································································································································· 130
NTP debugging commands ······································································································································· 133
debugging ntp-service········································································································································· 133
OAA debugging command ······································································································································· 139
debugging oaa remote-interface ······················································································································· 139
OSPF debugging commands ····································································································································· 140
debugging ospf event ········································································································································· 140
debugging ospf hot-standby······························································································································· 143
debugging ospf lsa ············································································································································· 145
debugging ospf mpls-te······································································································································· 149
debugging ospf non-stop-routing ······················································································································· 152
debugging ospf packet ······································································································································· 155
debugging ospf spf ············································································································································· 160
debugging ospf timer ·········································································································································· 176
OSPFv3 debugging commands································································································································· 178
debugging ospfv3 event ····································································································································· 178
debugging ospfv3 graceful-restart ····················································································································· 179
debugging ospfv3 ifsm ······································································································································· 182
debugging ospfv3 lsa ········································································································································· 184
debugging ospfv3 nfsm ······································································································································ 187
debugging ospfv3 packet··································································································································· 190
debugging ospfv3 route ····································································································································· 192
PIM debugging commands ········································································································································ 196
debugging pim ···················································································································································· 196
PKI debugging commands ········································································································································· 208
debugging pki ····················································································································································· 208
Policy-based routing debugging commands ············································································································ 222
debugging ip policy-based-route ······················································································································· 222
ii
Port security debugging commands ·························································································································· 224
debugging port-security ······································································································································ 224
Portal debugging commands ····································································································································· 230
debugging portal················································································································································· 230
debugging portal server ····································································································································· 239
POS terminal access debugging commands ··········································································································· 244
debugging posa all ············································································································································· 244
debugging posa event ········································································································································ 245
debugging posa error ········································································································································· 246
debugging posa packet······································································································································ 248
PPP debugging commands ········································································································································ 250
PPP debugging commands ·········································································································································· 250
debugging ppp ···················································································································································· 250
PPPoE debugging commands ····································································································································· 253
debugging pppoe-client······································································································································ 253
debugging pppoe-server ···································································································································· 257
PTP debugging commands········································································································································· 260
debugging ptp ····················································································································································· 260
QoS debugging commands······································································································································· 262
debugging dar····················································································································································· 262
debugging p2p···················································································································································· 263
debugging qos all ··············································································································································· 265
debugging qos car ·············································································································································· 266
debugging qos cbq ············································································································································· 266
debugging qos error ··········································································································································· 268
debugging qos event ·········································································································································· 269
debugging qos gts ·············································································································································· 270
debugging qos match ········································································································································· 270
debugging qos remark ······································································································································· 271
Voice RADIUS debugging commands ······················································································································ 273
debugging voice radius ······································································································································ 273
RIP debugging commands ········································································································································· 288
debugging rip ······················································································································································ 288
debugging rip brief ············································································································································· 288
debugging rip event ············································································································································ 289
debugging rip packet ········································································································································· 291
debugging rip receive ········································································································································ 293
debugging rip send············································································································································· 295
debugging rip timer ············································································································································ 297
RIPng debugging commands ····································································································································· 298
debugging ripng·················································································································································· 298
debugging ripng brief ········································································································································ 298
debugging ripng event ······································································································································· 299
debugging ripng packet ····································································································································· 300
debugging ripng receive ···································································································································· 301
debugging ripng send ········································································································································ 302
debugging ripng timer ········································································································································ 302
RMON debugging commands ·································································································································· 304
debugging rmon ·················································································································································· 304
iii
RPR debugging commands ········································································································································ 308
debugging rpr error ············································································································································ 308
debugging rpr event ··········································································································································· 309
debugging rpr fsm ··············································································································································· 312
debugging rpr packet ········································································································································· 314
debugging rpr timer ············································································································································ 316
RRPP debugging commands ······································································································································ 318
debugging rrpp ··················································································································································· 318
RSH debugging commands ······································································································································· 326
debugging rsh······················································································································································ 326
Service loopback group debugging commands ····································································································· 327
debugging service-loopback ······························································································································ 327
Session management debugging commands ·········································································································· 328
debugging session aging-process ····················································································································· 328
debugging session engine·································································································································· 329
debugging session ext-info ································································································································· 332
debugging session packet-process ···················································································································· 334
debugging session relation ································································································································ 334
debugging session session-table ························································································································ 336
debugging session log proc ······························································································································· 337
debugging session log active-flow ···················································································································· 339
SIP debugging commands ········································································································································· 341
debugging voice sip ··········································································································································· 341
debugging voice ssm call ··································································································································· 353
debugging voice ssm lsm ··································································································································· 363
debugging voice ssm probe ······························································································································· 364
debugging voice ssm reg ··································································································································· 367
debugging voice ssm stack ································································································································ 370
debugging voice ssm sub ··································································································································· 377
debugging voice ssm ucm ·································································································································· 384
debugging voice srtp ·········································································································································· 385
Smart Link debugging commands ····························································································································· 387
debugging smart-link··········································································································································· 387
SNMP debugging commands ··································································································································· 391
debugging snmp agent packet ·························································································································· 391
debugging snmp agent process························································································································· 395
debugging snmp trap packet ····························································································································· 397
debugging snmp trap process ··························································································································· 399
Spanning tree debugging commands ······················································································································ 402
debugging stp all ················································································································································ 402
debugging stp event············································································································································ 402
debugging stp fsm ··············································································································································· 403
debugging stp global-error································································································································· 405
debugging stp global-event ································································································································ 407
debugging stp packet ········································································································································· 408
debugging stp roles ············································································································································ 411
debugging stp tc ·················································································································································· 412
SSH debugging commands ······································································································································· 414
debugging ssh server ·········································································································································· 414
iv
debugging ssh client ··········································································································································· 419
SSL debugging commands ········································································································································ 424
debugging ssl ······················································································································································ 424
SSL VPN debugging commands ······························································································································· 431
debugging ssl-vpn ··············································································································································· 431
Stateful failover debugging commands ···················································································································· 433
debugging dhbk ·················································································································································· 433
debugging dhbk service ····································································································································· 435
Terminal access debugging commands ··················································································································· 442
debugging rta error ············································································································································ 442
debugging rta event ············································································································································ 443
debugging rta packet ········································································································································· 444
Track debugging commands ····································································································································· 447
debugging track ·················································································································································· 447
Tunneling debugging commands ······························································································································ 450
debugging ipv4-tunnel ········································································································································ 450
debugging ipv6-tunnel ········································································································································ 454
debugging tunnel ················································································································································ 457
UDP helper debugging commands ··························································································································· 459
debugging udp-helper ········································································································································ 459
URPF debugging commands ······································································································································ 462
debugging ip urpf discards ································································································································ 462
VLAN termination debugging commands ················································································································ 463
debugging vlan ··················································································································································· 463
VoFR debugging commands ······································································································································ 467
debugging voice vofr ·········································································································································· 467
Voice subscriber line debugging commands ··········································································································· 488
debugging voice cmc ········································································································································· 488
debugging voice em ··········································································································································· 494
debugging voice ipp ··········································································································································· 501
debugging voice lgs············································································································································ 501
debugging voice r2············································································································································· 510
debugging voice statistics ·································································································································· 513
VRRP debugging commands ······································································································································ 515
IPv4 VRRP debugging commands ······························································································································ 515
debugging vrrp error ·········································································································································· 515
debugging vrrp event·········································································································································· 516
debugging vrrp packet ······································································································································· 518
debugging vrrp state ··········································································································································· 520
IPv6 VRRP debugging commands ······························································································································ 523
debugging vrrp ipv6 error ································································································································· 523
debugging vrrp ipv6 event ································································································································· 524
debugging vrrp ipv6 packet ······························································································································ 527
debugging vrrp ipv6 state ·································································································································· 529
WEB filtering debugging commands ························································································································ 533
debugging firewall http url-filter host ················································································································· 533
debugging firewall http url-filter parameter ······································································································ 533
v
debugging firewall http java-blocking ·············································································································· 534
debugging firewall http activex-blocking ·········································································································· 535
vi
MAC authentication debugging commands
The MAC authentication module name is identified as "MACAUTH" in debugging messages.
Some information in this chapter is device type specific. Devices in this chapter are categorized
depending on their IRF capability and support for interface cards that use independent processors for
forwarding traffic, as shown in Table 1.
Table 1 Device types
Device type
Distributed devices
Interface cards with
on-card processors
IRF capability
Examples
No
HP 6600 routers (except
for 6602)
Yes
Yes (in standalone mode)
Distributed IRF devices
Yes
Yes (in IRF mode)
Centralized devices
No
No
Centralized IRF devices
No
Yes
HP 12500 switches
HP 10500 switches
HP 12500 switches
HP 10500 switches
HP MSR routers
HP 6602 router
HP 5800 switches
HP 5500 switches
The output description tables in this document only contain fields and messages that require an
explanation.
debugging mac-authentication
Use debugging mac-authentication to enable MAC authentication debugging.
Use undo debugging mac-authentication to disable MAC authentication debugging.
Syntax
Centralized devices:
debugging mac-authentication event
undo debugging mac-authentication event
Distributed devices/centralized IRF devices:
debugging mac-authentication event [ slot slot-number ]
undo debugging mac-authentication event [ slot slot-number ]
Distributed IRF devices:
debugging mac-authentication event [ chassis chassis-number slot slot-number ]
undo debugging mac-authentication event [ chassis chassis-number slot slot-number ]
1
Default
MAC authentication debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
event: Specifies MAC authentication event debugging.
slot slot-number: Specifies a card by its slot number. (Distributed device—In standalone mode.)
slot slot-mumber: Specifies an IRF member device by its member ID. (Centralized IRF devices.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number
argument represents the ID of the IRF member device. The slot-number argument represents the slot
number of the card. (Distributed devices—In IRF mode.)
Usage guidelines
Table 2 describes output fields and messages for the debugging mac-authentication event command.
Table 2 Output from the debugging mac-authentication event command
Field
Description
IfIndex : IfIndex
Interface index.
cmd = CmdType
Command.
Processing node CONNECTING...
The MAC authentication module is processing the
node in Connecting state.
Processing node SUCCESS...
The MAC authentication module is processing the
node in Success state.
Processing node FAILURE...
The MAC authentication module is processing the
node in FAILURE state.
Processing node LOGOFF...
The MAC authentication module is processing the
node in LOGOFF state.
Warning:MACAuth Que is almost full, CUT user msg
is dropped
MAC authentication message queue is to be full. The
cut user connection messages will be dropped.
new mac address MacAddress
The MAC authentication module received unknown
MAC address from the underlayer.
PortIndex is invalid .
Invalid port index.
error mac address MacAddress
Invalid MAC address.
Send new mac event to queue failed .
The MAC authentication module failed to send new
MAC messages to the message queue.
write new mac event failed
The MAC authentication module failed to write new
MAC addresses.
MAC_AddressLearn rcv a multicast MAC addr , will
not authenticate...
The device received a multicast MAC address. MAC
authentication does not authenticate the multicast
address.
2
Field
Description
MacAuth is configuring or already disabled ,can't
add src drop mac .
MAC authentication is under configuration or has
been disabled. The device cannot add the MAC
address to the MAC address table that contains
blocked MAC addresses.
Broadcast send a MAC address syn add msg
The device broadcast the synchronization message
for a new MAC.
Broadcast send a new slot inserted notify msg ,new
slot is :SlotID
The device broadcast the message to notify the
insertion of a new card. (Distributed
devices/distributed IRF devices.)
The device broadcast the message to notify the
insertion of a new subordinate device. (Centralized
IRF devices.)
Receive broadcast kickoff preUser IPC request.
The MAC authentication module received broadcast
IPC request to remove duplicated MAC authentication
users.
find auth by index fail...
The device failed to find MAC authentication
resources based on the user index.
NOT FOUND MacAddress, Vlan:VlanID in
MACAUTH blocked List.
The MAC authentication module failed to find the
MAC address of the specified VLAN in the quiet MAC
address table.
FOUND MacAddress, Vlan: VlanID in MACAUTH
blocked List.
The MAC authentication module found the MAC
addresses of the specified VLAN in the quiet MAC
address table.
Send request to driver to get port PortSec info for
IfIndex =IfIndex,cmd = CmdType
The MAC authentication module sent a request to the
driver. The module requested port security information
of a port.
Get Port Portsec info for IfIndex =IfIndex, cmd =
CmdType, return code = ErrCode
The MAC authentication module received port
security information of the port.
IPCMsg: Sync Slot Insert Information msg: recv data is
null!
IPCMsg: Sync Slot Insert Information msg: recv data
length is wrong!
3
Card insertion synchronization message. The
received data is null. (Distributed devices/distributed
IRF devices.)
Member device insertion synchronization message.
The received data is null. (Centralized IRF devices.)
Card insertion synchronization message. The
received data length is incorrect. (Distributed
devices.)
Member device insertion synchronization message.
The received data length is incorrect. (Centralized IRF
devices.)
Field
Description
When a new card was inserted, port security was not
enabled and MAC authentication was enabled on the
card. After the insertion, MAC authentication is
enabled on the new card. (Distributed devices.)
SlotInsert, Portsec not enabled, macauth
enabled ,enable macauth on new slot!
When a new member device was inserted, port
security was not enabled and MAC authentication
was enabled on the device. After the insertion, MAC
authentication is enabled on the new member device.
(Centralized IRF devices.)
When a new card was inserted, port security was
enabled or MAC authentication was not enabled on
the card. After the insertion, MAC authentication is
enabled on the new card. (Distributed devices.)
SlotInsert, Portsec enabled or macauth not
enabled ,enable macauth on new slot!
When a new member device was inserted, port
security was enabled or MAC authentication was not
enabled on the device. After the insertion, MAC
authentication is enabled on the new member device.
(Centralized IRF devices.)
Fail to enable mac_auth for driver's err
The system failed to enable MAC authentication
because of driver error.
Fail to disable mac_auth for driver's err
The system failed to disable MAC authentication
because of driver error.
Receive reset drv msg .
The MAC authentication module received a message
to reset the driver.
Receive clear drv msg
The MAC authentication module received a message
to clear the driver.
waiting users off-line.
The MAC authentication module is waiting for users to
go offline.
clear mac-auth drv .
The MAC authentication module cleared the MAC
authentication driver.
Port leave from Vlan, but user is leaving GuestVLAN,
need NOT cut user!!!
The interface has left the guest VLAN, and the user is
being removed from the guest VLAN. In this case, it is
not required to force the user to go offline.
Port leave from Vlan, cut user!!!
The interface has left guest VLAN. The user went
offline forcibly.
An MGV entry for MAC authentication was added:
Added an MACAUTH MGV entry for MacAddress:
IfIndex =IfIndex Guest-Vlan=VlanID
• MacAddress—MAC address added to the MGV
entry.
• IfIndex—Port index.
• Guest-Vlan—Guest VLAN ID.
MGV traffic timer triggered MAC authentication.
• MAC—MAC address that triggered the MAC
MGV traffic timer triggered MAC authentication:
MAC= MacAddress , IfIndex =IfIndex ,
Guest-Vlan=VlanID, InitVlan = InitVlan
authentication.
• IfIndex—Port index.
• Guest-Vlan—Guest VLAN ID.
• InitVlan—Initial VLAN to which the port was
assigned before it was added to the guest VLAN.
4
Field
Description
An MGV entry has had no packets matching it and
therefore needs to be deleted.
No packets match the MGV entry. The MGV entry will
be deleted.
Failed to process MGV for the same MGV entry.
The MAC authentication module failed to process
MGV because the same MGV entry already exists.
Examples
# Enable MAC authentication event debugging. Output similar to the following example is generated
under the following conditions:
•
MAC authentication is enabled globally and on GigabitEthernet 1/1.
•
A user passes MAC authentication on GigabitEthernet 1/1.
•
The network cable connected to GigabitEthernet 1/1 is removed.
<Sysname> debugging mac-authentication event
<Sysname> Sysname-view
[Sysname] interface gigabitethernet 1/1
[Sysname-GigabitEthernet1/1] mac-authentication
*Apr 30 12:14:27:357 2000 Sysname MACAUTH/7/EVENT:Port:GigabitEthernet1/1,send request
to driver to Get Port Portsec info for IfIndex = 900002,cmd = 8460f01
*Apr 30 12:14:27:369 2000 Sysname MACAUTH/7/EVENT:Port:GigabitEthernet1/1, get Port
Portsec info for IfIndex = 900002,cmd = 8460f01,return code = 0
Mac-auth is enabled on port GigabitEthernet1/1.
// The MAC authentication module sent a request to the driver. The request obtained port security
information on GigabitEthernet 1/1 and enabled MAC authentication on the port.
*Apr 30 12:19:05:199 2000 Sysname MACAUTH/7/EVENT:Port:GigabitEthernet1/1, new mac
address 0015-e947-e45b
*Apr 30 12:19:05:209 2000 Sysname MACAUTH/7/EVENT:Auth:193,Processing node CONNECTING...
*Apr 30 12:19:05:230 2000 Sysname MACAUTH/7/EVENT:Auth:193,Processing node SUCCESS...
// GigabitEthernet 1/1 received the authentication request from the user, and the MAC authentication
module authenticated the new MAC address.
*Apr 30 12:24:48:600 2000 Sysname MACAUTH/7/EVENT:Port:GigabitEthernet1/1,
Auth:0,IF_IFMSG_DOWN
*Apr 30 12:24:48:632 2000 Sysname MACAUTH/7/EVENT:Auth:194,Processing node LOGOFF...
*Apr 30 12:24:48:640 2000 Sysname MACAUTH/7/EVENT:Auth:194,Processing node FAILURE...
// MAC authentication on the port failed after you unplugged the network cable connected to the port.
5
MAC-in-MAC debugging commands
The MAC-in-MAC module name is identified as "MINM" in debugging messages.
The output description tables in this document only contain fields and messages that require an
explanation.
debugging minm
Use debugging minm to enable debugging for MAC-in-MAC.
Use undo debugging minm to disable debugging for MAC-in-MAC.
Syntax
debugging minm { all | error | event | packet }
undo debugging minm { all | error | event | packet }
Default
Debugging for MAC-in-MAC is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: All types of debugging for MAC-in-MAC.
error: MAC-in-MAC error debugging.
event: MAC-in-MAC event debugging.
packet: MAC-in-MAC frame debugging.
Usage guidelines
Table 1 describes the output fields and messages for the debugging minm error command.
Table 3 Output from the debugging minm error command
a. Field
b. Description
c. The ISID of this packet is
d. The I-SID of the MAC-in-MAC frame is
not configured
not as configured.
f.
e. Failed to set driver
g. Failed to process BMAC
h. MINM failed to age the B-MAC entry.
aging event
i.
MINM failed to issue the configuration
to the driver.
j.
Failed to create VSI, when
processing slot in
6
MINM failed to create a VSI when a
board was plugged.
a. Field
b. Description
k. Failed to set driver type:
l.
MINM_DEL
m. Interface type is not
MINM failed to issue MINM_DEL to the
driver.
n. This type of interface does not support
supported
MAC-in-MAC.
o. Failed to broadcast
p. MINM failed to broadcast the IPC
message by VPLS IPC
message through VPLS.
Table 2 describes the output fields and messages for the debugging minm event command.
7
Table 4 Output from the debugging minm event command
a. Field
b. Description
8
a. Field
b. Description
d. MINM succeeded in
processing IPC
messages X. X
indicates the IPC
message type:
• 0—Invalid operation type.
• 1—Adding VSI.
• 2—Deleting VSI.
• 3—Configuring B-VLAN.
• 4—Adding B-VLAN to the driver.
• 5—Deleting B-VLAN to the driver.
• 6—Deleting uplink port to the driver.
• 7—Adding uplink port to the driver.
• 8—Deleting uplink port.
• 9—Deleting an uplink port by the port
number.
• 10—Adding uplink port.
• 11—Enabling re-encapsulation.
• 12—Disabling re-encapsulation.
• 13—Adding B-MAC.
• 14—Modifying B-MAC.
• 15—Deleting all B-MACs.
c. Succeeded in processing IPC message: X
• 16—Deleting B-MACs of the specified
VSI.
• 17—Deleting B-MACs of the specified VSI
and link ID.
• 18—Deleting B-MACs of the specified
VLAN.
• 19—Deleting B-MACs of the specified
port.
• 20—Deleting B-MACs of the specified
VLAN and port.
• 21—Deleting B-MAC by MAC.
• 22—Aging B-MACs of the specified VSI.
• 23—Aging B-MACs of the specified link
ID.
• 24—Debugging.
• 25—Setting board boot.
• 26—Setting state for all boards.
• 27—Setting state for the VSI.
• 28—Processing B-MAC information
according to the B-MAC state.
• 29—Displaying data.
• 30—Configuring VSI when a board was
9
plugged.
• 31—Configuring uplink port when a
board was plugged.
a. Field
b. Description
f.
e. Succeeded in sending IPC to slot n,
message type: X
MINM succeeded in
sending IPC message X
to the board in slot n. n
indicates the slot
number of the board. X
indicates the IPC
message type.
h. MINM succeeded in
processing event Y on
port n. n indicates the
number of the port. Y
indicates the event
type:
g. Succeeded in processing interface n, Event:
Y
• 2—Deleting a port.
• 8—Unplugging a port.
• 64—Port down.
j.
i.
Succeeded in processing VSI event: Y
MINM succeeded in
processing VSI event Y.
Y indicates the event
type:
• 0—Creating VSI.
• 1—Deleting VSI.
• 2—Shutting down VSI.
• 3—Bringing up VSI.
l.
MINM succeeded in
processing VLAN event
Y, with the start address
a, end address b, and
data c. Y indicates the
event type:
• 4—Static VLAN deleting detection.
k. Succeeded in processing event: Y.
ulStartIndex = a, ulEndIndex = b, ulData = c
• 2048—Deleting an access port from the
VLAN.
• 8192—Deleting a trunk port from the
VLAN.
• 32768—Deleting a multi port from the
VLAN.
• 2097152—Deleting ports in batch from
the VLAN.
• 8388608—Deleting a port from multiple
VLANs in batch.
n. MINM succeeded in
m. Succeeded in processing slot n event:
SLOT_IN
10
processing the event of
plugging a board into
slot n. n is the slot
number of the board.
a. Field
b. Description
p. Configuring the uplink
o. pfDRV_MINM_SetUplink is NULL
port is not supported.
r. Configuring the
re-encapsulation
information is not
supported.
q. pfDRV_MINM_SetReEncapsulation is NULL
Table 3 describes the output fields and messages for the debugging minm packet command.
Table 5 Output from the debugging minm packet command
a. Field
b. Description
c. Receive MAC-in-MAC
d. MINM received MAC-in-MAC frames
frame from IFname
on port IFname.
e. B-DA
f.
g. B-SA
h. Source B-MAC address.
i.
j.
BTAG type, which is fixed to 0x88a8.
k. ITAG TPID
l.
ITAG type, which is fixed to 0x88e7.
m. C-DA
n. Destination C-MAC address.
o. C-SA
p. Source C-MAC address.
BTAG TPID
Destination B-MAC address.
Examples
# Enable MAC-in-MAC error debugging. Output similar to the following example is generated when you
configure the uplink port and downlink port for MAC-in-MAC.
<Sysname> debugging minm error
*Oct 24 14:23:58:531 2009 Sysname MINM/7/Error:
1.
*Oct 24 14:23:58:531 2009 Sysname MINM/7/Error:
This packet is not received from BVLAN
Failed to learn BMAC.
// An uplink port in B-VLAN 1 received MAC-in-MAC frames from B-VLAN 20, and B-MAC learning
failed.
*Oct 24 14:27:16:968 2009 Sysname MINM/7/Error: The ISID of this packet is not configured
*Oct 24 14:27:16:968 2009 Sysname MINM/7/Error:
Failed to learn BMAC.
// The I-SID of the MAC-in-MAC frame received was not as configured, and B-MAC learning failed.
# Enable MAC-in-MAC event debugging. Output similar to the following example is generated when
you configure the uplink port and downlink port for MAC-in-MAC.
<Sysname> debugging minm event
*Oct 24 14:34:02:828 2009 Sysname MINM/7/Event: Succeeded in sending IPC to slot ffffffff,
message type: 13.
// MINM succeeded in sending IPC message 13 (adding B-MAC) to the board in slot ffffffff.
*Oct 24 14:34:27:515 2009 Quidway MINM/7/Event: Succeeded in processing BMAC aging event
// MINM succeeded in aging the B-MAC entry.
*Oct 24 14:36:35:312 2009 Quidway MINM/7/Event:
Succeeded in processing VSI event: 2
// MINM succeeded in processing VSI event 2 (shutting down VSI).
11
*Oct 24 14:50:31:875 2009 Quidway MINM/7/Event:
BMAC already learned.
// MINM already learned the B-MAC.
# Enable MAC-in-MAC packet debugging. Output similar to the following example is generated when
you configure the uplink port and downlink port for MAC-in-MAC.
<Sysname> debugging minm packet
*Oct 24 11:20:41:453 2009 Sysname MINM/7/Packet:
Receive MAC-in-MAC frame from Ethernet1/1
B-DA: 0102-0304-0506
B-SA: 0605-0403-0206
BTAG TPID: 0x88a8
BVLAN: 20
ITAG TPID: 0x88e7
I-SID: 111
C-DA: 0101-0101-0101
C-SA: 0202-0202-0202
// Content of the MAC-in-MAC frame received from port Ethernet 1/1.
12
MBGP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging bgp update ipv4 multicast
Use debugging bgp update ipv4 multicast to enable BGP update debugging for IPv4-MBGP address
family.
Use undo debugging bgp update ipv4 to disable BGP update debugging for IPv4-MBGP address family.
Syntax
debugging bgp update ipv4 multicast [ peer { ip-address | group-name } ] [ receive | send ] [ verbose ]
undo debugging bgp update ipv4 multicast [ peer { ip-address | group-name } ] [ receive | send ]
[ verbose ]
Default
BGP update debugging for IPv4-MBGP address family is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
ip-address: Specifies the IP address of the peer entity.
group-name: Specifies the peer group, which is a string of 1 to 47 characters.
receive: Specifies debugging for received BGP updates.
send: Specifies debugging for sent BGP updates.
verbose: Displays detailed debugging information.
Usage guidelines
IMPORTANT:
Enabling debugging might affect system performance. Use this command only when necessary and
disable debugging when the debugging operation is complete.
Table 1 describes the output fields and messages for the debugging bgp update ipv4 multicast
command.
Table 6 Output from the debugging bgp update ipv4 multicast command
Field
Description
BGP.xxx
Name of the current instance.
Recv UPDATE from x.x.x.x
BGP received an update from BGP neighbor x.x.x.x.
13
Field
Description
Recv UPDATE(Withdraw) from x.x.x.x
BGP received an update withdraw from BGP
neighbor x.x.x.x.
Error identified while receiving UPDATE message from
the peer x.x.x.x and ignored
Error was found in the received update message from
neighbor x.x.x.x, and the message was ignored.
Err/SubEr
Error code/sub-error code.
Errdata:
Error data.
Send UPDATE to x.x.x.x
BGP sent an update message to BGP neighbor
x.x.x.x.
Send UPDATE(Withdraw) to peer x.x.x.x
BGP sent an update withdraw message to BGP
neighbor x.x.x.x.
x.x.x.x/xx
Destination IP address/mask.
INBOUND
Inbound policy.
LocRemCross:Export Policy Check Failed
BGP exported policy check error when importing
routes to VRF routing table.
LocRemCross:Import Policy Check Error
BGP imported policy check error when importing
routes to VRF routing table.
in-label
Incoming label.
out-label
Outgoing label.
tnl id
Tunnel ID.
Create ILM Success
BGP succeeded to create the ILM.
Delete ILM Success
BGP succeeded to delete the ILM.
Create NHLFE success
BGP succeeded to create the NHLFE.
Delete NHLFE success
BGP succeeded to delete the NHLFE.
afi = 196(l2vpn) safi = 128(l2vpn)
The address family was 196, and the sub-address
family was 128(L2VPN).
Origin
Origin of BGP.
AS Path
AS Path of BGP.
Next Hop
Next Hop of BGP.
Local Pref
Local Preference of BGP.
MED
MED attribute of BGP.
afi = 155(vpls) safi = 128(vpls)
The address family was 155, and the sub-address
family was 128(VPLS).
Create ILM6 Success
BGP succeeded to create the ILM6.
Delete ILM6 Success
BGP succeeded to delete the ILM6.
BGP Recv Label Route : Tunnel Waiting , BGP LSP isn't
created
BGP received a labeled route, but the tunnel was still
waiting, and the BGP LSP had not been established.
RouteDistinguisher:X:X
RD value.
label offset:X
Label offset.
label base:XXX
Label start position.
14
Examples
# Enable BGP update debugging for IPv4-MBGP address family.
<Sysname> debugging bgp update ipv4 multicast packet
*Apr
2 17:46:55:830 2007 Sysname-Comware RM/6/RMDEBUG:
BGP_MBGP.: Recv UPDATE from 12.1.1.1 with following destinations :
Update message length : 67
Local Pref
: 100
MED
: 0
Origin
: Incomplete
AS Path
:
Next Hop
: 12.1.1.1
1.2.3.4/32
15
MFF debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging mac-forced-forwarding
Use debugging mac-forced-forwarding to enable MFF debugging.
Use undo debugging mac-forced-forwarding to disable MFF debugging.
Syntax
debugging mac-forced-forwarding { all | error | event | info | packet }
undo debugging mac-forced-forwarding { all | error | event | info | packet }
Default
MFF debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
all: Specifies all types of debugging for MFF.
error: Specifies error debugging.
event: Specifies error debugging.
info: Specifies information debugging.
packet: Specifies packet debugging.
Usage guidelines
Table 1 describes output fields and messages for the debugging mac-forced-forwarding error
command.
Table 7 Output from the debugging mac-forced-forwarding error command
Field
Description
Failed to fill vlan tag
MFF failed to fill the VLAN tag when constructing an ARP packet.
Failed to cut vlan tag
MFF failed to remove the VLAN tag when constructing an ARP
packet.
Failed to set gateway
MFF failed to update the gateway MAC address.
Failed to get gateway
MFF failed to find the user's gateway in the VLAN.
CFA send failed
MFF failed to send IPC broadcast.
Replace buildrun failed
MFF failed to replace buildrun.
16
Field
Description
Process event of slot-insert failed
MFF failed to process a card insertion event.
Create interface control block failed
MFF failed to create an interface control block.
Delete interface control block failed
MFF failed to delete an interface control block.
Table 3 describes output fields and messages for the debugging mac-forced-forwarding event
command.
Table 8 Output from the debugging mac-forced-forwarding event command
Field
Description
Deal MAC change
The driver notified MFF of a MAC address change.
Notify MCM ACL rule
MFF notified MCM to apply or delete the ACL.
Interface name: ifName
Name of the interface to which the ACL applies, action for the
ACL (add or delete), and the returned result.
Option type: optionType Return Value: n
Notify DHSP ACL rule
Interface name: ifName,
portType,
Port type:
Option type: optionType,
Return Value: n
Notify DRV ACL rule
Interface name: ifName
MFF notified DHCP snooping to apply or delete the ACL.
Name of the interface to which the ACL applies, action for the
ACL (add or delete), and the returned result.
MFF notified driver to apply or delete the ACL.
VlanId: vlanId
Port type: portType
type: optionType
Option
Rule type: ruleType,
Return Value: n
Notify ISG ACL rule
Interface name: ifName
VlanId: vlanId
Option type: optionType Gateway IP: x.x.x.x
Gateway MAC: xxxx-xxxx-xxxx Return
Value: n
Name of the interface to which the ACL applies, and VLAN ID
of the interface.
Interface type, and action for the ACL (add or delete).
ACL type, and returned result.
MFF notified IP source guard to apply or delete the ACL.
Name of the interface to which the ACL applies.
VLAN ID of the interface.
Action for the ACL (add or delete), and gateway IP address.
Gateway MAC address, and returned result.
Table 3 describes output fields and messages for the debugging mac-forced-forwarding info command.
Table 9 Output from the debugging mac-forced-forwarding info command
Field
Description
Notify other application MFF is enabled
MFF notified other modules that MFF was enabled.
Notify other application MFF is disabled
MFF notified other modules that MFF was disabled.
No gateway in VLAN n
No gateway was found for the ARP request received by MFF.
Destination port index can't found
No outbound interface was not found when MFF sent packets.
Transmit request from gateway
After the network port received an ARP request for an unknown
host from the gateway, MFF forwarded the request.
Transmit request from server
After the network port received an ARP request for an unknown
host from the server, MFF forwarded the request.
17
Field
Description
Transmit request from client
After the user port received an ARP request from a host and the
MAC address of the gateway was not obtained, MFF
forwarded the request.
Refresh gateway information by packet
MFF updated the MAC address of the gateway and the
upstream network port marked by the gateway.
Self ip address
The MFF device did not process the packet with the destination
IP address as that of a virtual interface on itself.
Examples
# Enable MFF event debugging on an MFF enabled device.
<Sysname> debugging mac-forced-forwarding event
<Sysname> terminal debugging
% Current terminal debugging is on
// Event debugging was enabled.
*Apr 26 16:30:21:435 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify DHCP ACL rule:
Interface name: Ethernet1/3,
Option type: ADD,
Port type: USER,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified the DHCP module to apply an
ACL to user port Ethernet 1/3 to permit packets from DHCP clients. The apply operation was successful.
*Apr 26 16:30:21:441 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify DRV ACL rule:
Interface name: Ethernet1/3,
Port type: USER,
VlanId: 100,
Option type: ADD,
Rule type: ALL DENY,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified the driver to apply an ACL to
user port Ethernet 1/3 to deny all packets. The apply operation was successful.
*Apr 26 16:30:21:451 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify DRV ACL rule:
Interface name: Ethernet1/3,
Port type: USER,
VlanId: 100,
Option type: ADD,
Rule type: MULTICAST PERMIT,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified the driver to apply an ACL to
user port Ethernet 1/3 to permit multicast packets. The apply operation was successful.
*Apr 26 16:30:21:461 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify ISG ACL rule:
Interface name: Ethernet1/3,
VlanId: 100,
Option type: ENABLE,
Gateway IP: N/A,
Gateway MAC: N/A
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified ISG to apply an ACL to enable
user port Ethernet 1/3, and the result was successful.
18
*Apr 26 16:30:21:471 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify MCM ACL rule:
Interface name: Ethernet1/3,
Option type: ADD,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified MCM to apply an ACL to user
port Ethernet 1/3 to deliver ARP packets to the CPU. The apply operation was successful.
*Apr 26 16:30:21:582 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify DHSP ACL rule:
Interface name: Ethernet1/2,
Option type: ADD,
Port type: NETWORK,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified DHCP to apply an ACL to
network port Ethernet 1/2 to permit DHCP packets. The apply operation was successful.
*Apr 26 16:30:21:592 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify DRV ACL rule:
Interface name: Ethernet1/2,
Port type: NETWORK,
VlanId: 100,
Option type: ADD,
Rule type: BROADCAST DENY,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified the driver to apply an ACL to
network port Ethernet 1/2 to deny multicast packets. The apply operation was successful.
*Apr 26 16:30:21:602 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify DRV ACL rule:
Interface name: Ethernet1/2,
Port type: NETWORK,
VlanId: 100,
Option type: ADD,
Rule type: MULTICAST PERMIT,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified the driver to apply an ACL to
network port Ethernet 1/2 to permit multicast packets. The apply operation was successful.
*Apr 26 16:30:21:612 2000 Sysname MFF/7/Debug_MFF_Event:
MFF Event:
Notify MCM ACL rule:
Interface name: Ethernet1/2,
Option type: ADD,
Return Value: 0
// After automatic mode MFF was enabled for VLAN 100, MFF notified MCM to apply an ACL to
network port Ethernet 1/2 to deliver ARP packets to the CPU. The apply operation was successful.
# Enable MFF error debugging on an MFF enabled device.
<Sysname> debugging mac-forced-forwarding error
<Sysname> terminal debugging
% Current terminal debugging is on
// MFF error debugging was enabled.
Error: MAC-forced forwarding is not enabled in the VLAN.
// Periodic gateway MAC probe cannot be enabled because MFF was not enabled.
# Enable MFF information debugging on an MFF enabled device.
19
<Sysname> debugging mac-forced-forwarding info
<Sysname> terminal debugging
% Current terminal debugging is on
// MFF information debugging was enabled.
*Apr 26 17:00:25:371 2000 Sysname MFF/7/Debug_MFF_Info:
MFF Info:
Get client info from DHCP:
Client MAC: 000d-5619-f7bc,
Gateway IP: 100.1.1.100,
Client IP: 100.1.1.1,
Client VLAN: 100,
Port: Ethernet1/3
// After automatic mode MFF was enabled, MFF obtained a client entry from the DHCP server.
# Enable MFF packet debugging on an MFF enabled device.
<Sysname> debugging mac-forced-forwarding packet
<Sysname> terminal debugging
% Current terminal debugging is on
// MFF packet debugging was enabled.
*Apr 26 12:12:59:465 2000 Sysname MFF/7/Debug_MFF_Recv_Pkt:
Receiving MFF packet:
Src Interface : Ethernet1/2
Dst Interface :
N/A
InterfaceType :NETWORK
Vlan ID :100
SrcMac :00e0-fc00-3102
SrcIp :
100.1.1.100
DstMac :0000-0000-0000
DstIp :
100.1.1.1
PacketType :REQUEST
// Network port Ethernet1/2 received an ARP request for the MAC address of host 100.1.1.1 from the
gateway with IP address 100.1.1.100 and MAC address 00e0-fc00-3102.
*Apr 26 12:12:59:465 2000 Sysname MFF/7/Debug_MFF_Recv_Pkt:
Receiving MFF packet:
Src Interface : Ethernet1/3
Dst Interface :
N/A
InterfaceType :USER
Vlan ID :100
SrcMac :000d-5619-f7bc
SrcIp :
100.1.1.1
DstMac :0000-0000-0000
DstIp :
100.1.1.1
PacketType :GRATUITOUS
// User port Ethernet1/3 received a gratuitous ARP packet from the host with IP address 100.1.1.1 and
MAC address 000d-5619-f7bc.
*Apr 26 12:12:59:509 2000 Sysname MFF/7/Debug_MFF_Recv_Pkt:
Receiving MFF packet:
Src Interface : Ethernet1/3
Dst Interface :
N/A
InterfaceType :USER
Vlan ID :100
SrcMac :000d-5619-f7bc
SrcIp :
100.1.1.1
DstMac :0000-0000-0000
DstIp :
100.1.1.100
PacketType :REQUEST
// User port Ethernet1/3 received an ARP request from the host with IP address 100.1.1.1 and MAC
address 100.1.1.1 to the gateway at 100.1.1.100.
*Apr 26 12:12:59:523 2000 Sysname MFF/7/Debug_MFF_Send_Pkt:
20
Sending MFF packet:
Src Interface :
N/A
Dst Interface : Ethernet1/2
InterfaceType :NETWORK
Vlan ID :100
SrcMac :000d-5619-f7bc
SrcIp :
100.1.1.1
DstMac :0000-0000-0000
DstIp :
100.1.1.100
PacketType :REQUEST
// Network port Ethernet1/2 received an ARP request from the host with IP address 100.1.1.1 and MAC
address 000d-5619-f7bc to the gateway at 100.1.1.100.
*Apr 26 12:12:59:534 2000 Sysname MFF/7/Debug_MFF_Recv_Pkt:
Receiving MFF packet:
Src Interface : Ethernet1/2
Dst Interface :
N/A
InterfaceType :NETWORK
Vlan ID :100
SrcMac :00e0-fc00-3102
SrcIp :
100.1.1.100
DstMac :000d-5619-f7bc
DstIp :
100.1.1.1
PacketType :REPLY
// Network port Ethernet1/2 received an ARP response from the gateway with IP address 100.1.1.100
and MAC address 00e0-fc00-3102 to the host with IP address 100.1.1.1 and MAC address
000d-5619-f7bc.
*Apr 26 12:12:59:553 2000 Sysname MFF/7/Debug_MFF_Send_Pkt:
Sending MFF packet:
Src Interface : Ethernet1/2
Dst Interface :
N/A
InterfaceType :USER
Vlan ID :100
SrcMac :00e0-fc00-3102
SrcIp :
100.1.1.100
DstMac :0000-0000-0000
DstIp :
100.1.1.100
// Network port Ethernet1/2 received a gratuitous ARP packet from the gateway with IP address
100.1.1.100 and MAC address 00e0-fc00-3102.
21
MLD debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging mld
Use debugging mld to enable MLD debugging.
Use undo debugging mld to disable MLD debugging.
Syntax
debugging mld { all | done [ basic-acl6-number ] | event | query [ advanced-acl6-number ] [ receive |
send ] | report [ advanced-acl6-number ] | ssm-mapping [ advanced-acl6-number ] | timer }
undo debugging mld { all | done | event | query [ receive | send ] | report | ssm-mapping | timer }
Default
MLD debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of MLD debugging.
done: Specifies MLD done message debugging.
basic-acl6-number: Specifies an IPv6 basic ACL by its number in the range of 2000 to 2999.
event: Specifies MLD event debugging.
query: Specifies MLD query message debugging.
advanced-acl6-number: Specifies an IPv6 advanced ACL by its number, in the range of 3000 to 3999.
receive: Specifies debugging for received MLD query messages.
send: Specifies debugging for sent MLD query messages.
report: Specifies MLD report debugging.
ssm-mapping: Specifies MLD SSM mapping debugging.
timer: Specifies MLD timer debugging.
Usage guidelines
Table 1 describes output fields and messages for the debugging mld done command.
22
Table 10 Output from the debugging mld done command
Field
Description
DONE
MLD done message.
Interfacename(ifadd)
Interface that received the MLD done message
(interface address).
group gadd
IPv6 group address in the MLD done message.
Ignoring
This MLD done message was ignored.
Table 2 describes output fields and messages for the debugging mld event command.
Table 11 Output from the debugging mld event command
Field
Description
Creating/creation/created
Event types:
Elected/ Un-elected
•
•
•
•
•
•
Interface interfacename(ifadd)
Interface that responded to events (interface address).
(sadd, gadd)
(S, G) entry.
(*, gadd)
(*, G) entry.
Group limit reached on interface interfacename, failed
to create group(gadd)
MLD failed to create a table entry for the group
because the number of IPv6 multicast groups has
reached the specified threshold.
aux join/aux prune
adding/deleting downstream interface
deleting/unregister/deleted
Enqueue/Dequeing
Creating/creation/created
Aux join/aux prune
Adding/deleting downstream interface
Deleting/unregister/deleted
Enqueue/Dequeing
Elected/ Un-elected
Table 3 describes output fields and messages for the debugging mld query receive command.
Table 12 Output from the debugging mld query receive command
Field
Description
version <1-2>
Version of the MLD query.
Interfacename(ifadd)
Interface that sent/received this message (interface
address).
Ignoring
The MLD query message was ignored.
Received
The MLD query message was received.
Group gadd
IPv6 group address to be queried.
Table 4 describes output fields and messages for the debugging mld report command.
Table 13 Output from the debugging mld report command
Field
Description
Ignoring
This MLD report was ignored.
23
Field
Description
Record types of MLDv2 membership reports:
•
•
•
•
•
•
IS_IN/IS_EX/TO_IN/TO_EX/ALLOW/BLOCK
IS_IN
IS_EX
TO_IN
TO_EX
ALLOW
BLOCK
Group gadd
Reported IPv6 group address.
(sadd, gadd)
(S, G) entry.
v1/v2
Version of MLD membership report.
Interfacename(ifadd)
Interface that sent/received this message (interface
address).
Table 5 describes output fields and messages for the debugging mld query send command.
Table 14 Output from the debugging mld query send command
Field
Description
version <1-2>
Version of the MLD query.
Interfacename(ifadd)
Interface that sent/received this message (interface
address).
Ignoring
This MLD query message was ignored.
Send
The MLD query message was sent.
With/without s-bit
Whether S flag bit was set in the MLD query message.
Group gadd
IPv6 group address to be queried.
Table 6 describes output fields and messages for the debugging mld ssm-mapping command.
Table 15 Output from the debugging mld ssm-mapping command
Field
Description
ssm-mapping notify
MLD reported SSM mapping multicast group
information to the upper-layer routing protocol.
ssm-mapping group
SSM mapping multicast group.
Compatibility
Group compatibility mode.
Lmqi timer
Last-listener query timer.
ssm-mapping policy table
SSM mapping rule table.
Table 7 describes output fields and messages for the debugging mld timer command.
Table 16 Output from the debugging mld timer command
Field
Description
Lmqi timeout for group
The last-listener query timer timed out.
24
Field
Description
Other querier present timeout
The MLD other querier present interval timer timed out.
Interfacename(ifadd)
Interface that sent/received this message. The
interface address is displayed in the brackets.
Deleting v1 host timer
The MLDv1 host timer timed out.
Setting v1 host timer
MLDv1 host present timer was configured.
Examples
# Enable MLD done message debugging. When MLD is enabled, output similar to the following
example is generated:
<Sysname> debugging mld done
*0.1678546 Sysname MLD/7/DONE:Received DONE for group(FF0E::101:101) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M053692)
// MLD received an MLD done message on Ethernet 1/1 with the group address FF0E::101:101.
*0.1826210 Sysname MLD/7/DONE:Ignoring DONE received for group(FF0E::101:101) on
interface Ethernet1/1(FE80::200:5EFF:FE01:6C00). Already sending last listener queries
(M053683)
// Because a done message was received on Ethernet 1/1, this done message was ignored and a
multicast-address-specific query was sent.
*0.1671115 Sysname MLD/7/DONE:Ignoring DONE received for non-member group(FF0E::101:101)
on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00). (M053660)
// The done message was ignored, because this interface did not join the group.
# Enable MLD event debugging. When MLD is enabled, output similar to the following example is
generated:
<Sysname> debugging mld event
*0.852518 Sysname MLD/7/EVENT:Elected querier on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G10297)
// Ethernet 1/1 became the MLD querier.
*0.813059 Sysname MLD/7/EVENT:Un-elected querier on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G10456)
// Ethernet 1/1 became a non-querier.
*0.886956 Sysname MLD/7/EVENT:MLDV2 (*, FF0E::101:101) aux join received on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G01600)
*0.886956 Sysname MLD/7/EVENT:(*, FF0E::101:101) entry created in global MRT (G01609)
*0.886956 Sysname MLD/7/EVENT:Adding interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) to
downstream IN tree for (*, FF0E::101:101) (G01629)
*0.886956 Sysname MLD/7/EVENT:Creating group(FF0E::101:101) for interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G013082)
// MLD received a join message on Ethernet 1/1 and added an entry for the group FF0E::101:101 with
Ethernet 1/0 as the outgoing interface.
*0.886956 Sysname MLD/7/EVENT:Enqueue group(FF0E::101:101) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) in group_calq. (G014076)
// MLD put the group in the aging queue.
*0.1223796 Sysname MLD/7/EVENT:Dequeing group(FF0E::101:101) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) from group_calq. (G014028)
25
*0.1223796 Sysname MLD/7/EVENT:Enqueue group(FF0E::101:101) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) in group_calq. (G014076)
// MLD received an MLD done message on Ethernet 1/1 and reset the group aging timer.
*0.1224808 Sysname MLD/7/EVENT:Lmqi timeout for group(FF0E::101:101), sending last
listener query on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00). (G013428)
*0.1224808 Sysname MLD/7/EVENT:Enqueue group(FF0E::101:101) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) in group_calq. (G014076)
// The last-listener query timer timed out. MLD sent out a multicast-address-specific query.
*0.1225820 Sysname MLD/7/EVENT:Group(FF0E::101:101) expired and sources empty. Deleting
this group on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00). (G013318)
// No more join messages with the group address FF0E::101:101 were received on Ethernet 1/1. This
entry timed out.
*0.1225820 Sysname MLD/7/EVENT:Deleting group(FF0E::101:101) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G014170)
*0.1225820 Sysname MLD/7/EVENT:Group(FF0E::101:101) deleted (G01805)
// IGMP deleted the entry for group FF0E::101:101.
# Enable debugging for received MLD query messages. When MLD is enabled, output similar to the
following example is generated:
<Sysname> debugging mld query receive
*0.2607914 Sysname MLD/7/QUERY:Received MLDv2 query message on
Ethernet1/1(FE80::200:5EFF:FE01:6C00) from FE80::1 (M04430)
// MLD received an MLDv2 query on Ethernet 1/1.
*0.2607914 Sysname MLD/7/QUERY:Adopted querier's robustness(2), query interval(10) on
interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M04984)
// MLD set the number of times to 2 and interval of sending multicast-address-specific queries to 10
seconds.
# Enable MLD membership report debugging. When MLD is enabled, output similar to the following
example is generated:
<Sysname> debugging mld report
*0.1988093 Sysname MLD/7/REPORT:Received IS_IN for group(FF1E::3) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M05704)
// MLD received an MLDv2 membership report for group FF1E::3 on Ethernet 1/1, with the record type
of IS_IN.
*0.2103721 Sysname MLD/7/REPORT:Received IS_EX for group(FF1E::3) on interface
Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M05755)
// MLD received an MLDv2 membership report for group FF1E::3 on Ethernet 1/1, with the record type
of IS_EX.
# Enable debugging for sent MLD query messages. When MLD is enabled, output similar to the
following example is generated:
<Sysname> debugging mld query send
*0.2237184 Sysname MLD/7/QUERY:Send version 2 general query on
Ethernet1/1(FE80::200:5EFF:FE01:6C00) to destination(FF02::1) (M04791)
// MLD sent an MLDv2 general query message out of Ethernet 1/1
# Enable MLD SSM mapping debugging on the public network. When MLD SSM mapping is enabled,
output similar to the following example is generated:
<Sysname> debugging mld ssm-mapping
26
*0.20301209 Sysname MLD/7/SSM-MAPPING:(public net):Receive ssm-mapping report for group
FF34::1 on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M053895)
// MLD received an MLDv1 membership report with the multicast group address FF34::1 on Ethernet 1/1.
The multicast group address is in the MLD SSM mapping rule range.
*0.20301209 Sysname MLD/7/SSM-MAPPING:(public net):Creating ssm-mapping group
(FF34::1)for interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G015470)
// MLD created an SSM mapping multicast group FF34::1 on Ethernet 1/1 after source addresses were
mapped with the MLD SSM mapping rule.
*0.20320402 Sysname MLD/7/SSM-MAPPING:(public net):Receive ssm-mapping LEAVE for group
FF34::1 on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M054112)
// MLD received an MLDv1 done message with the multicast group address of FF34::1 on Ethernet 1/1.
The multicast group address is in the MLD SSM mapping rule range.
*0.20320402 Sysname MLD/7/SSM-MAPPING:(public net):Ssm-mapping LEAVE received for group
FF34::1 is immediately processed on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00)
(M054185)
// The MLD SSM snooping multicast group was directly deleted because fast-leave processing has been
enabled.
*0.20320402 Sysname MLD/7/SSM-MAPPING:(public net):Deleting ssm-mapping group (FF34::1)
on interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) (G015835)
// MLD deleted the MLD SSM mapping multicast group on Ethernet 1/1.
# Enable MLD timer debugging. When MLD is enabled, output similar to the following example is
generated:
<Sysname> debugging mld timer
*0.2955218 Sysname MLD/7/TIMER:Deleting v1host timer for group(FF0E::101:101) (M053388)
// The MLDv1 host timer timed out.
*0.3023658 Sysname MLD/7/TIMER:Deleting source lmqi timer for group(FF0E::101:101) on
interface Ethernet1/1(FE80::200:5EFF:FE01:6C00) (M053493)
// The last-listener query timer timed out.
*0.20447221 Sysname MLD/7/TIMER:(public net):Setting source expiry timer for source
FE90::200:5EFF:FE01:6C00 of group FF34::1 on Ethernet1/1(FE80::6C00) to 260 (M054026)
// MLD received an MLDv1 membership report with the multicast group address FF34::1 on Ethernet 1/1.
The multicast group address is in the MLD SSM mapping rule range. After the MLD SSM mapping
multicast group was created, an aging timer was set for the group per IPv6 multicast source.
*0.40447221 Sysname MLD/7/TIMER:(public net):Lmqi timeout for group FF34::1, sending last
member query on Ethernet1/1(FE80::6C00) (G016089)
// MLD received an MLDv1 done message with the multicast group address of FF34::1 on Ethernet 1/1.
The multicast group address is in the MLD SSM mapping rule range. After the last-listener query timer of
the MLD SSM mapping multicast group timed out, a multicast-address-specific query was sent.
*0.70447221 Sysname MLD/7/TIMER:(public net):Deleting lmqi timer for ssm-mapping group
FF34::1 on Ethernet1/1(FE80::6C00) (G016110)
// MLD sent out queries. No report was received, so the last-listener query timer was deleted.
debugging mld proxying
Use debugging mld proxying to enable MLD proxy debugging.
Use undo debugging mld proxying to disable MLD proxy debugging.
27
Syntax
debugging mld proxying { event | packet | routing-table } advanced-acl6-number
undo debugging mld proxying { event | packet | routing-table }
Default
MLD proxy debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
event: Specifies MLD proxy event debugging.
packet: Specifies MLD proxy packet debugging.
routing table: Specifies MLD proxy routing table debugging.
advanced-acl6-number: Specifies an IPv6 advanced ACL by its number, in the range of 3000 to 3999.
Usage guidelines
Table 8 describes output fields and messages for the debugging mld proxying event command.
Table 17 Output from the debugging mld proxying event command
Field
Description
enqueued
The multicast group was enqueued.
dequeued
The multicast group was dequeued.
proxy_calq
MLD proxy CALQ queue.
proxy cache
MLD proxy cache.
proxy database
Group membership database maintained by the MLD
proxy device.
Number of joins
Number of joined sources.
Table 9 describes output fields and messages for the debugging mld proxying packet command.
Table 18 Output from the debugging mld proxying packet command
Field
Description
proxying interface
MLD proxy interface.
query
MLD query message.
report
MLD report message.
record
Group record.
28
Field
Description
type 1
Group record types:
•
•
•
•
•
•
•
•
type 2
type 3
type 4
type 5
type 6
type 7
type 8
Type 1—IS_IN.
Type 2—IS_EX.
Type 3—TO_IN.
Type 4—TO_EX.
Type 5—ALLOW.
Type 6—BLOCK.
Type 7—JOIN.
Type 8—LEAVE.
Table 10 describes output fields and messages for the debugging mld proxying routing-table command.
Table 19 Output from the debugging mld proxying routing-table command
Field
Description
(sadd, gad)
(S, G) entry.
Recovery of route
The route was recovered.
Loss of route
The route was lost.
Examples
# Enable MLD proxy event debugging. When MLD proxy is enabled on the interface, output similar to
the following example is generated:
<Sysname> debugging mld proxying event
*0.1631452 Sysname MLD/7/PRY_EVT:(public net): Group FF0E::101:101 added in proxy cache.
(G363219)
// MLD received a join message for group FF0E::101:101 on a downstream interface and added this
multicast group into the MLD proxy cache.
*0.1631831 Sysname MLD/7/PRY_EVT:(public net): EXCLUDE group FF0E::101:101 added in proxy
database.
// MLD added an entry for the multicast group in the EXCLUDE mode to the group membership
database in the MLD proxy device.
*0.1632021 Sysname MLD/7/PRY_EVT:(public net): Number of joins increased to 2 for group
FF0E::101:101 in proxy database.
// MLD received a join message for the multicast group FF0E::101:101 on another downstream interface.
The number of records for the same group in the database increased to two.
*0.1678546 Sysname MLD/7/PRY_EVT: Group FF0E::101:101 enqueued in proxy_calq. (M363784)
// Upon receiving a query message for group FF0E::101:101, the upstream interface started the delay
timer and put this group in the CALQ queue.
*0.1714536 Sysname MLD/7/PRY_EVT: Group FF0E::101:101 dequeued from proxy_calq. (G363833)
// When the upstream interface went down, it removed the group from the CALQ queue.
*0.5532846 Sysname MLD/7/PRY_EVT:(public net): Group record created for group
FF0E::101:101 at delay timer timeout.
// The delay timer timed out, and a group record was created for the multicast group FF0E::101:101.
29
# Enable MLD proxy packet debugging on the public network. When MLD proxy is enabled on the
interface, output similar to the following example is generated:
<Sysname> debugging mld proxying packet
*0.1726142 Sysname MLD/7/PRY_EVT: Received MLDv1 query for group FF0E::101:101 on version
1 proxying interface Ethernet1/1(FE80::200:6C00). (G362885)
// MLD received an MLDv1 query message for group FF0E::101:101 on the upstream interface Ethernet
1/1.
*0.1754567 Sysname MLD/7/PRY_EVT: MLDv1 report for group FF0E::101:101 sent out
Ethernet1/1(FE80::200:6C00). (G363449)
// After the entry for group FF0E::101:101 was added, the proxy device sent an MLD report for group
FF0E::101:101 on Ethernet 1/1.
*0.1752533 Sysname MLD/7/PRY_EVT: Type 3 record added for group FF0E::101:101. (G363564)
// When an MLD report was sent as a result of a change in the membership for the multicast group
FF0E::101:101, a TO-IN group record for the group was added.
*0.1783136 Sysname MLD/7/PRY_EVT: Source 100::10 added to group record. (G363647)
// The source 100::10 was added into the group record.
*0.1790527 Sysname MLD/7/PRY_EVT: MLDv2 report sent. (G363662)
// When the membership for the group changed, an MLDv2 report was sent to the upstream device.
# Enable MLD proxy route debugging. When MLD proxy is enabled on the interface, output similar to
the following example is generated:
<Sysname> debugging mld proxying routing-table
*0.57932162 Sysname MLD/7/PRY_RT:(public net): Entry (100::1, FF3E::1) created in IPv6
multicast routing table. (G01597)
// MLD received an (S, G) join with the group address in the SSM group range on a downstream
interface and created a forwarding entry.
*0.58934175 Sysname MLD/7/PRY_RT:(public net): Entries for group FF3E::1 removed upon
change of SSM group range. (G36139)
// MLD detected a change in the SSM group policy and removed entries for the group FF3E::1.
*0.59833187 Sysname MLD/7/PRY_RT: Loss of route for (100::1, FF3E::1) detected, (S,G) entry
removed. (G361460)
// MLD detected that the route was lost and removed the associated forwarding entry.
*0.58034165 Sysname MLD/7/PRY_RT:(public net): Recovery of route for (100::1, FF3E::1)
detected, (S,G) entry created. (G361460)
// MLD detected that the route was recovered and created the associated forwarding entry.
30
MLD snooping debugging commands
The MCS module name is identified as "multicast" in debugging messages.
The output description tables in this document only contain fields and messages that require an
explanation.
Some information in this chapter is device type-specific. Devices in this chapter are categorized
depending on their IRF capability and support for interface cards that use independent processors for
forwarding traffic, as shown in Table 1.
Table 20 Device types
Device type
Distributed devices
Interface cards with
on-card processors
IRF capability
Examples
No
HP 6600 routers (except
for 6602)
Yes
Yes (in standalone mode)
Distributed IRF devices
Yes
Yes (in IRF mode)
Centralized devices
No
No
Centralized IRF devices
No
Yes
HP 12500 switches
HP 10500 switches
HP 12500 switches
HP 10500 switches
HP MSR routers
HP 6602 router
HP 5800 switches
HP 5500 switches
debugging mld-snooping
Use debugging mld-snooping to enable MLD snooping debugging.
Use undo debugging mld-snooping to disable MLD snooping debugging.
Syntax
Centralized devices:
debugging mld-snooping { abnormal | all | driver | event | group | packet [ vlan vlan-id ] [ port
interface-type interface-number ] | timer }
undo debugging mld-snooping { abnormal | all | driver | event | group | packet | timer }
Distributed devices/centralized IRF devices/distributed IRF devices:
debugging mld-snooping { abnormal | all | driver | event | group | ipc { receive | send } | packet
[ vlan vlan-id ] [ port interface-type interface-number ] | timer }
undo debugging mld-snooping { abnormal | all | driver | event | group | ipc { receive | send } |
packet | timer }
Default
MLD snooping debugging is disabled.
31
Views
User view
Default command level
1: Monitor level
Parameters
abnormal: Specifies MLD snooping exception debugging.
all: Specifies all types of MLD snooping debugging.
driver: Specifies MLD snooping interface driver debugging.
event: Specifies MLD snooping event debugging.
group: Specifies MLD snooping multicast group debugging.
ipc { receive | send }: Specifies inbound/outbound IPC packet debugging.
packet: Specifies MLD snooping packet debugging.
vlan vlan-id: Specifies the VLAN to which an Ethernet port belongs. The value range for the vlan-id
argument is 1 to 4094.
port interface-type interface-number: Specifies an Ethernet port.
timer: Specifies debugging for MLD snooping timers.
Usage guidelines
Table 2 describes output fields and messages for the debugging mld-snooping driver command.
Table 21 Output from the debugging mld-snooping driver command
Field
Description
Add/Delete multicast vlan OIF to/from driver
A multicast VLAN outgoing interface was added to or
deleted from the driver.
Add/Delete Level2 IP entry to/from driver
A Layer 2 IP entry was added to or deleted from the
driver.
Add/Delete Unit/Board for multicast vlan to/from
driver
A unit or board for the multicast VLAN was added to
or deleted from the driver.
Add/Delete Unit/Board for Level2 IP entry to/from
driver
A unit or board for the Layer 2 IP entry was added to
or removed from the driver.
Add/Delete Port for multicast vlan OIF to/from driver
A port was added to or deleted from the multicast
VLAN outgoing interface list on the driver.
Add/Delete Port for Level2 IP entry to/from driver
A port was added to or deleted from the Layer 2 IP
entry on the driver.
Add/Delete multicast vlan IP entry to/from driver
A multicast VLAN IP entry was added to or deleted
from the driver.
Add/Delete Level2 MAC entry to/from driver
A Layer 2 MAC entry was added to or deleted from
the driver.
mask boardmask
The destination board mask of an entry was added to
or deleted from the driver.
(saddr, gaddr)
(S, G) entry.
32
Table 3 describes output fields and messages for the debugging mld-snooping event command.
Table 22 Output from the debugging mld-snooping event command
Field
Description
Succeed to enable/disable MLD snooping globally
MLD snooping was globally enabled or disabled.
Succeed to enable/disable MLD snooping
drop-unknown globally
The function of dropping unknown multicast packets
was globally enabled or disabled.
Succeed to enable/disable MLD snooping proxying
on vlan vlanid
MLD snooping proxy was enabled or disabled in a
VLAN.
Received chassis/slot/interface event
An IRF member device, card, or VLAN interface event
was received.
Table 4 describes output fields and messages for the debugging mld-snooping group command.
Table 23 Output from the debugging mld-snooping group command
Field
Description
Create L2 IP Source entry
MLD snooping created a Layer 2 IP entry.
Deleted IP and MAC entry
MLD snooping deleted the IP and MAC entries.
(saddr, gaddr)
(S, G) entry.
on vlan vlanid
VLAN to which the (S, G) belongs.
Group number exceeds the max number
The number of multicast groups exceeded the
maximum number.
Table 5 describes output fields and messages for the debugging mld-snooping ipc command.
Table 24 Output from the debugging mld-snooping ipc command
Field
Description
Inform other boards/units: event
MLD snooping informed the other boards/units about
the event.
Successful to send ipc information to ipc queue
MLD snooping sent IPC packets to the IPC queue
successfully.
Received an IPC packet and insert it into queue
MLD snooping received an IPC packet and
successfully inserted it into the IPC queue.
Received an IPC packet, but failed to insert it into
queue
MLD snooping received an IPC packet but failed to
insert it into the IPC queue.
Table 6 describes output fields and messages for the debugging mld-snooping packet command.
Table 25 Output from the debugging mld-snooping packet command
Field
Description
port portname
Port that processed the message.
on vlan vlanid
ID of the VLAN to which the port belongs.
source address addr
Source address of the packet.
destination address addr
Destination address of the message.
33
Table 7 describes output fields and messages for the debugging mld-snooping timer command.
Table 26 Output from the debugging mld-snooping timer command
Field
Description
Create/Set
MLD snooping created or set a timer.
MLD snooping timers:
host port aging timer/time
•
•
•
•
•
•
router port aging timer/time
aggregation host port aging timer/time
aggregation router port aging timer/time
querier timer/interval
query respond timer
Host port aging timer/time
Router port aging timer/time
Aggregation host port aging timer/time
Aggregation router port aging timer/time
Querier timer/interval
Query respond timer
Examples
# Enable MLD snooping interface driver debugging. When MLD snooping is enabled on the device,
output similar to the following example is generated:
<Sysname> debugging mld-snooping driver
*Nov 7 09:32:30:738 2006 Sysname MCS/7/driver:Add Level2 IP entry to driver: vlan:2,
S,G(2002::2,FF08::8), port num:1. (G08758)
// An IP entry (2002::2, FF08::8) was added to the driver in VLAN 2.
# Enable MLD snooping event debugging. When MLD snooping is on the device and MLD snooping
proxy is enabled in VLAN 2, output similar to the following example is generated:
<Sysname> debugging mld-snooping event
*Nov 7 17:22:24:532 2006 Sysname MCS/7/event:Succeed to enable MLD snooping globally.
(G083769)
// MLD snooping was enabled globally.
*Nov 7 17:23:21:742 2006 Sysname MCS/7/event:Succeed to enable MLD snooping proxying on
vlan 2. (G202463)
// MLD snooping proxy was enabled in VLAN 2.
# Enable MLD snooping multicast group debugging. When MLD snooping is enabled on the device,
output similar to the following example is generated:
<Sysname> debugging mld-snooping group
*Nov 7 09:34:59:488 2006 Sysname MCS/7/groups:Deleted IP and MAC entry of
(S,G)(2002::2,FF08::8) on vlan 2. (G142433)
// The IP and MAC entry was deleted.
# Enable inbound IPC packet debugging. When MLD snooping is enabled on the device, output similar
to the following example is generated:
<Sysname> debugging mld-snooping ipc receive
*Nov 7 18:07:02:726 2006 Sysname MCS/7/ipcrecv:Slot=1;Received an IPC packet and insert
it into queue. (G18955)
// MLD snooping received an IPC packet and inserted it into the IPC queue.
# Enable outbound IPC packet debugging. When MLD snooping is enabled on the device, output similar
to the following example is generated:
<Sysname> debugging mld-snooping ipc send
34
*Nov 7 17:06:08:412 2006 Sysname MCS/7/ipcsend:Inform other boards: this board is a new
router board. (G143331)
// MLD snooping sent an IPC packet.
# Enable MLD snooping packet debugging. When MLD snooping is enabled on the device, output
similar to the following example is generated:
<Sysname> debugging mld-snooping packet
*Nov 7 09:37:21:174 2006 Sysname MCS/7/packet:Received MLDv2 report packet for destination
address FF02::16 from port Eth1/1 on vlan 2. (G213068)
// MLD snooping received an MLD report on Ethernet 1/1 in VLAN 2.
*Nov 7 09:37:54:174 2006 Sysname MCS/7/packet:Send the packet to port Eth1/1 of vlan
2,which source address is FE80::1 and destination address is FF02::16. (G261104)
// MLD snooping sent an MLD message with the source address FE80::1 and the destination address
FF02::16 out of Ethernet 1/1 in VLAN 2.
# Enable MLD snooping timer debugging. When MLD snooping is enabled on the device, output similar
to the following example is generated:
<Sysname> debugging mld-snooping timer
*Nov 7 17:06:08:412 2006 Sysname MCS/7/timer:Create router port aging timer, 260 seconds,
for port: Eth1/1, vlan: 2. (G141414)
// MLD snooping created a router port aging timer on Ethernet 1/1 in VLAN 2 and set the aging timer
to 260 seconds.
*Nov 7 17:06:54:712 2006 Sysname MCS/7/timer:Create query respond timer of group FF02::16,
2000 milliseconds. (G153777)\
// MLD snooping created a query response timer for the IPv6 multicast group FF02::16 and set the time
interval to 2 seconds.
35
Modem debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging modem
Use debugging modem to enable modem debugging.
Use undo debugging modem to disable modem debugging.
Syntax
debugging modem [ interface interface-type interface-number ]
undo debugging modem [ interface interface-type interface-number ]
Views
User view
Default command level
1: Monitor level
Parameters
interface-type interface-number: Interface type and interface number.
Usage guidelines
Table 1 describes output fields and messages for the debugging modem command.
Table 27 Output from the debugging modem command
Field
Description
AT
AT command.
OK
Connection was established successfully.
ATDT
AT command used to dial a number.
ATA
AT command used to answer a call without waiting
for a ring.
+++
Quit command.
IDLE
Idle state.
CONNECT
Connected state.
ACTIVE
Active state.
DISCONNECT
Disconnect state.
BUSY
Line busy.
NO CARRIER
No carrier signal was detected.
MDM_LINE_MODEM_NO
Both answering calls and placing calls were disabled.
MDM_LINE_MODEM_IN
Answering calls was enabled.
36
Field
Description
MDM_LINE_MODEM_OUT
Placing calls was enabled.
MDM_LINE_MODEM_INOUT
Both answering calls and placing calls were enabled.
MDM_LINE_DISCONNECT
Modem was disconnected.
MDM_LINE_CALLBACK
Modem callback.
MDM_DDR_CONN_REQ
DDR connection request was received.
MDM_DDR_CONN_RES
DDR connection acknowledgement was received.
MDM_DDR_DISC_REQ
DDR disconnect request was received.
MDM_DDR_DISC_RES
DDR disconnect acknowledgement was received.
MDM_PHY_SHUT
SHUT command was issued.
MDM_PHY_NO_SHUT
No SHUT command was issued.
MDM_PHY_TO_AT
Modem changed to the AT command mode.
MDM_PHY_CD_DOWN
CD signal went invalid.
MDM_PHY_CD_UP
CD signal went valid.
Examples
Output in the following example was created under the following conditions:
•
Router A and Router B are connected through a PBX.
•
Router A has the following configuration:
#
dialer-rule 1 ip permit
#
interface Analogmodem5/1
async mode protocol
link-protocol ppp
ip address 51.0.0.1 255.255.255.0
dialer enable-circular
dialer-group 1
dialer number 105
#
user-interface tty 177
modem both
#
•
Router B has the following configuration:
#
dialer-rule 1 ip permit
#
interface Analogmodem5/1
async mode protocol
link-protocol ppp
ip address 51.0.0.2 255.255.255.0
dialer enable-circular
dialer-group 1
37
dialer number 106
#
user-interface tty 177
modem both
#
# Enable modem debugging on Router A, and then ping Router B from Router A.
<Sysname> debugging modem interface Analogmodem 5/1
<Sysname> ping -c 1 51.0.0.2
*Mar 31 12:13:00:352 2006 Sysname MODEM/7/debug_CTRL:
Analogmodem5/1 Modem received information: MDM_DDR_CONN_REQ
// Analogmodem 5/1 received a connection request.
*Mar 31 12:13:00:352 2006 Sysname MODEM/7/debug_AT_Send:
Analogmodem5/1
Data of AT is sent: ATDT105
// Analogmodem 5/1 sent the number to be called.
*Mar 31 12:13:00:352 2006 Sysname MODEM/7/debug_ModemState:
Analogmodem5/1
The modem state is changed: from IDLE to CONNECT
// Analogmodem 5/1 turned from idle state to connected state.
*Mar 31 12:13:00:379 2006 Sysname MODEM/7/debug_AT_Recv:
Analogmodem5/1
Data of AT is received: ATDT105
// Analogmodem 5/1 received an AT command: ATDT105.
*Mar 31 12:13:22:875 2006 Sysname MODEM/7/debug_AT_Recv:
Analogmodem5/1
Data of AT is received: CONNECT 57600
// Analogmodem 5/1 received an AT command: connect 57600.
*Mar 31 12:13:25:780 2006 Sysname MODEM/7/debug_CTRL:
Analogmodem5/1 Modem received information: MDM_PHY_CD_UP
// Analogmodem 5/1 received a message that the CD signal was valid.
*Mar 31 12:13:25:886 2006 Sysname MODEM/7/debug_ModemState:
Analogmodem5/1
The modem state is changed: from CONNECT to ACTIVE
// Analogmodem 5/1 changed from connected state to active state.
*Mar 31 12:13:33:630 2006 Sysname MODEM/7/debug_CTRL:
Analogmodem5/1 Modem received information: MDM_DDR_DISC_REQ
// Analogmodem 5/1 received a disconnect request. This message is displayed when the dialer
disconnect command is executed to disconnect the modem.
*Mar 31 12:13:33:738 2006 Sysname MODEM/7/debug_ModemState:
Analogmodem5/1
The modem state is changed: from ACTIVE to DISCONNECT
// Analogmodem 5/1 changed from active state to disconnect state.
*Mar 31 12:13:33:738 2006 Sysname MODEM/7/debug_AT_Send:
Analogmodem5/1
Data of AT is sent: +++
// Analogmodem 5/1 issued a command to terminate the connection.
*Mar 31 12:13:34:583 2006 Sysname MODEM/7/debug_AT_Recv:
Analogmodem5/1
Data of AT is received: NO CARRIER
// Analogmodem 5/1 received a no-carrier AT data command.
*Mar 31 12:13:35:750 2006 Sysname MODEM/7/debug_ModemState:
Analogmodem5/1
The modem state is changed: from DISCONNECT to IDLE
38
// Analogmodem 5/1 changed from disconnect state to idle state.
*Mar 31 12:13:35:750 2006 Sysname MODEM/7/debug_ModemState:
Analogmodem5/1
The modem state is changed: from IDLE to DISCONNECT
// Analogmodem 5/1 changed from idle state to disconnect state.
*Mar 31 12:13:35:750 2006 Sysname MODEM/7/debug_AT_Send:
Analogmodem5/1
Data of AT is sent: +++
// Analogmodem 5/1 issued a command to terminate the connection.
*Mar 31 12:13:35:751 2006 Sysname MODEM/7/debug_ModemState:
Analogmodem5/1
The modem state is changed: from DISCONNECT to IDLE
// Analogmodem 5/1 changed from disconnect state to idle state.
39
Monitor Link debugging commands
The Monitor Link module name is identified as "MTLK" in debugging messages.
debugging monitor-link
Use debugging monitor-link to enable Monitor Link debugging.
Use undo debugging monitor-link to disable Monitor Link debugging.
Syntax
debugging monitor-link [ group group-id ] { all | error | event }
undo debugging monitor-link [ group group-id ] { all | error | event }
Default
Monitor link debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
group group-id: Specifies a monitor link group by its ID. If no group ID is specified, this command
enables or disables monitor link debugging for all monitor link groups.
all: Specifies all types of monitor link group debugging.
error: Specifies monitor link group error debugging.
event: Specifies monitor link group event debugging.
Examples
# Enable event debugging for monitor link group 1.
<Sysname> debugging monitor-link group 1 event
*Dec 28 19:37:47:543 2007 Sysname MTLK/7/GROUPSTATE:
Monitor link group 1 is down
// Monitor link group 1 went down.
40
MPLS L2VPN debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging mpls l2vpn
Use debugging mpls l2vpn to enable debugging for MPLS L2VPN.
Use undo debugging mpls l2vpn to disable debugging for MPLS L2VPN.
Syntax
debugging mpls l2vpn { advertisement | all | connections | error | event | hsb }
undo debugging mpls l2vpn { advertisement | all | connections | error | event | hsb }
Default
Debugging for MPLS L2VPN is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
advertisement: Specifies debugging for advertisement events.
all: Specifies debugging for all events.
connections: Specifies debugging for connection events.
error: Specifies debugging for error events.
event: Specifies debugging for bottom layer events.
hsb: Specifies debugging for hot standby events.
Usage guidelines
Table 1 describes output fields and messages for the debugging mpls l2vpn advertisement command.
Table 28 Output from the debugging mpls l2vpn advertisement command
Field
Description
peer pe ip address
IP address of the specified peer PE.
fec element type
FEC type. The value is 128.
c-Bit
Control bit. 1 means enabled, and 0 means not
enabled.
group id
Used to remove VC information with the same group
ID in batch.
vsi type
VSI access type.
41
Field
Description
MP_REACH_NLRI
Network layer reachable message.
MP_UNREACH_NLRI
Network layer unreachable message.
Table 2 describes output fields and messages for the debugging mpls l2vpn event command.
Table 29 Output from the debugging mpls l2vpn event command
Field
Description
g_ulL2vpnMsg2MFWCounter
L2VPN advertised counter to MFW.
g_ulL2vpnMsg2BGPCounter
L2VPN advertised counter to BGP.
g_ulL2vpnMsg2LDPCounter
L2VPN advertised counter to LDP.
intf Up event receive&process
L2VPN received and processed interface up event.
intf Notify Msg to IFNET process
Interface notified IFNET process of a message.
Table 3 describes output fields and messages for the debugging mpls l2vpn hsb command.
Table 30 Output from the debugging mpls l2vpn hsb command
Field
Description
L2VPN CCCEncapIntf RealTime Backup Modify
IfState....entered
L2VPN interface encapsulation state change realtime
backup began.
L2VPN CCCEncapIntf RealTime Backup Modify
IfState....leaving
L2VPN interface encapsulation state change realtime
backup finished.
L2VPN LocalLdp Realtime backup Modify
VCState....entered
L2VPN local LDP information realtime backup began.
L2VPN LocalLdp Realtime backup Modify
VCState....leaving
L2VPN local LDP information realtime backup
finished.
L2VPN Restore Scheduler....entered
L2VPN restore began.
L2VPN Restore Buffer....entered
L2VPN restore buffer began.
L2VPN Parse Restore Buffer....entered
L2VPN parse restore buffer began.
L2VPN CCCEncapIntfDLL Restore....entered
L2VPN interface encapsulation restore began.
L2VPN CCCEncapIntfDLL Restore....leaving
L2VPN interface encapsulation restore finished.
L2VPN Parse Restore Buffer....leaving
L2VPN parse restore buffer finished.
L2VPN Restore Buffer....leaving
L2VPN restore buffer finished.
L2VPN Restore Scheduler....leaving
L2VPN restore began.
L2VPN BGPVC Batch Backup....entered
L2VPN BGP VC batch backup began.
L2VPN BGPVC Batch Backup....leaving
L2VPN BGP VC batch backup finished.
Table 4 describes output fields and messages for the debugging mpls l2vpn connection command.
42
Table 31 Output from the debugging mpls l2vpn connection command
Field
Description
RmtCEID
Remote CE identifier.
vcid
VC identifier.
vctype
VC type.
dest
Destination LSR address.
Table 5 describes output fields and messages for the debugging mpls l2vpn error command.
Table 32 Output from the debugging mpls l2vpn error command
Field
Description
Invalid Remote interface - not able to get the outifindex
Invalid remote interface. Not able to get the outgoing
interface index.
Examples
# Enable debugging for MPLS L2VPN advertisement. Output similar to the following example is
generated when these tasks are performed:
•
Connect three routers that are directly connected.
•
Configure MPLS, MPLS LDP, and Martini settings on each router, and establish a Martini connection
between two routers.
•
Execute the debugging mpls l2vpn advertisement command on one PE router.
•
Shut down the Martini-enabled interface that is connected to the private network.
<PE1> debuggiing mpls l2vpn advertisement
<PE1> terminal monitor
<PE1> terminal debugging
<PE1> system-view
[PE1] interface vlan-interface 80
[PE1-Vlan-interface80] display this
#
interface Vlan-interface80
ip address 100.5.1.2 255.255.255.0
mpls l2vc 33.33.33.33 100
#
return
[PE1-Vlan-interface80]
[PE1-Vlan-interface80]
[PE1-Vlan-interface80] shutdown
[PE1-Vlan-interface80]
%Jul
6 17:56:30:172 2006 PE1 IFNET/5/LINK UPDOWN:
Vlan-interface80: link status is DOWN
*0.3799203 PE1 L2V/8/DBG:
! [L2VPN-LDP]Info :
sent label withdraw message.
context of message as follow:
-----------------------------
43
peer pe ip address is:
33.33.33.33
request_id is:
0
label is:
1024
status_code is:
0x0
fec element type is:
128
c-Bit is:
0
vc type is:
ethernet
vc info length is:
4
group id is:
0
vc id is:
100
length of vc_fec_tlv is:
12
context of vc_fec_tlv is:
80 00 05 04 00 00 00 00 00 00 00 64
*0.3799203 PE1 L2V/8/DBG:
! L2VPN LDP - Send LABEL WITHDRAW to ldp success
// L2VPN sent a label withdraw message to LDP successfully.
*0.3799375 PE1 L2V/8/DBG:
! [L2VPN-LDP]Info :
received label release message.
context of message as follow:
----------------------------peer pe ip address is:
33.33.33.33
request_id is:
0
label is:
1024
status_code is:
0x0
fec element type is:
128
c-Bit is:
0
vc type is:
ethernet
vc info length is:
4
group id is:
0
vc id is:
100
length of vc_fec_tlv is:
12
context of vc_fec_tlv is:
80 00 05 04 00 00 00 00 00 00 00 64
// L2VPN received a label release message.
*0.3799375 PE1 L2V/8/DBG:
! [L2VPN-VSI]Info :
VSI: received label release message.
context of message as follow:
----------------------------peer pe ip address is:
33.33.33.33
request_id is:
0
label is:
1024
status_code is:
0x0
fec element type is:
128
c-Bit is:
0
vsi type is:
ethernet
vsi info length is:
4
44
group id is:
0
vsi id is:
100
length of vc_fec_tlv is:
12
context of vc_fec_tlv is:
80 00 05 04 00 00 00 00 00 00 00 64
// The VSI at the private network side received the label release message.
*0.3799422 PE1 L2V/8/DBG:
! L2VPN LDP
no corresponding local vc
// L2VPN LDP had no corresponding local VC.
*0.3799422 PE1 L2V/8/DBG:
! L2VPN VSI no local ldp peer found.
// L2VPN VSI had no local LDP peer found.
# Enable debugging for MPLS L2VPN connections. Output similar to the following example is generated
when these tasks are performed:
•
Connect three routers that are directly connected.
•
Configure MPLS, MPLS LDP and Martini settings on each router, and establish a Martini connection
between two routers.
•
Execute the debugging mpls l2vpn connection command on one PE router.
•
Shut down the Martini-enabled interface that is connected to the private network.
<PE1> debuggiing mpls l2vpn connection
<PE1> terminal monitor
<PE1> terminal debugging
<PE1> system-view
[PE1] interface vlan-interface 80
[PE1-Vlan-interface80] shutdown
[PE1-Vlan-interface80]
%Jul
7 08:57:01:609 2006 PE1 IFNET/5/LINK UPDOWN:
Vlan-interface80: link status is DOWN
*0.57830687 PE1 L2V/8/DBG:
! L2VPN LDP VC state DOWN:(vcid=100,vctype=5,dest=33.33.33.33)
// L2VPN LDP VC was in DOWN state.
[PE1-Vlan-interface80] display debug
MPLS L2VPN connection debugging is on
[PE1-Vlan-interface80]
# Enable debugging for MPLS L2VPN errors. Output similar to the following example is generated when
these tasks are performed:
•
Connect three routers that are directly connected.
•
Configure MPLS, MPLS LDP and CCC settings on each router, and establish a remote CCC
connection between two PE routers.
•
Execute the debugging mpls l2vpn error command on one PE router.
•
Disable the MPLS function on the interface that is connected to the public network.
[PE1-Vlan-interface80]
[PE1-Vlan-interface80] display debugging
MPLS L2VPN error debugging is on
[PE1-Vlan-interface80] undo shutdown
[PE1-Vlan-interface80]
45
%Jul
6 17:31:42:812 2006 PE1 IFNET/5/LINK UPDOWN:
Vlan-interface80: link status is UP
[PE1-Vlan-interface80]
[PE1-Vlan-interface80]
[PE1-Vlan-interface80]
[PE1-Vlan-interface80]
[PE1-Vlan-interface80] interface vlan-interface 10
[PE1-Vlan-interface10] display this
#
interface Vlan-interface10
ip address 100.1.1.1 255.255.255.0
mpls
mpls ldp
#
return
[PE1-Vlan-interface10] undo mpls
[PE1-Vlan-interface10]
#Jul 6 17:32:16:469 2006 PE1 LDP/5/SessionDown: Session(22.22.22.22:0. public Instance)'s
state change to Down
*0.2345547 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
*0.2345547 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
*0.2345766 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
*0.2345984 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
*0.2346203 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
*0.2346422 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
*0.2346641 PE1 L2V/8/DBG:
! L2VPN CCC :Invalid Remote interface - not able to get the outifindex
// Invalid remote interface was not able to get the outgoing interface index.
# Enable debugging for MPLS L2VPN events. Output similar to the following example is generated when
these tasks are performed:
•
Connect three routers that are directly connected.
•
Configure MPLS, MPLS LDP and Martini settings on each router, and establish a Martini connection
between two PE routers.
•
Execute the debugging mpls l2vpn event command on one PE router.
•
Disable the MPLS function on the interface that is connected to the private network.
[PE1]
[PE1] display mpls l2vc
total ldp vc : 1
1 up
0 down
Transport
Client
VC
Local
Remote
Tunnel
VC ID
Intf
State
VC Label
VC Label
Policy
46
100
Vlan-interface80
up
1024
1024
default
[PE1]dis debug
MPLS L2VPN event debugging is on
[PE1] interface vlan-interface 80
[PE1-Vlan-interface80] shutdown
[PE1-Vlan-interface80]
%Jul 10 10:01:54:640 2006 PE1 IFNET/5/LINK UPDOWN:
Vlan-interface80: link status is DOWN
*0.1196640 PE1 L2V/8/DBG:
! L2VPN - interface status change event received: interface Vlan-interface80 down
// L2VPN received interface status change event that interface VLAN-interface 80 was down.
*0.1196640 PE1 L2V/8/DBG:
! notify Final Status, IFINDEX = 120717391, ulslot = 0,ulSeqNo = -2147483613
// L2VPN notified the final status that interface index was 120717391, slot number was 0, and sequence
number was -2147483613.
*0.1196703 PE1 L2V/8/DBG:
!L2VPN LDP-Downloaded FIB to MFW: Event = 2, Entry Type = 1 :
// L2VPN LDP downloaded FIB to MFW. Event 2 was deleting forwarding entries, and entry type 1
indicates that the entry was received by a remote connection.
*0.1196703 PE1 L2V/8/DBG:
!L2VPN LDP-Downloaded FIB to MFW: Event = 2, Entry Type = 3 :
// L2VPN LDP downloaded FIB to MFW. Event 2 was deleting forwarding entries, and entry type 3
indicates that the entry was sent from a remote connection.
*0.1196703 PE1 L2V/8/DBG:
! L2VPN - intf down: ldp intf down
// L2VPN received the interface down event indicating that the interface enabled with LDP went down.
*0.1196703 PE1 L2V/8/DBG:
! L2VPN - intf Down event receive&process
// L2VPN received and processed the interface down event.
*0.1196703 PE1 L2V/8/DBG:
! L2VPN - intf Notify Msg to IFNET process
// L2VPN notified IFNET process of the message.
*0.1196718 PE1 L2V/8/DBG:
g_ulL2vpnMsg2MFWCounter:2
// Layer 2 forwarding entry counter was 2.
*0.1196718 PE1 L2V/8/DBG:
g_ulL2vpnMsg2LDPCounter:1
// L2VPN to LDP message counter is 1.
[PE1-Vlan-interface80]
# Enable debugging for MPLS L2VPN hot standby. Output similar to the following example is generated
when these tasks are performed:
•
Connect three routers that are directly connected.
•
Configure MPLS, MPLS LDP and Martini settings on each router, and establish a Martini connection
between two PE routers.
47
•
Execute the debugging mpls l2vpn event command on one PE router.
•
Shut down the interface that is connected to the private network.
[PE1] interface vlan-interface 80
[PE1-Vlan-interface80]
[PE1-Vlan-interface80]
[PE1-Vlan-interface80] display this
#
interface Vlan-interface80
shutdown
ip address 100.5.1.2 255.255.255.0
mpls l2vc 33.33.33.33 100
#
return
[PE1-Vlan-interface80] shutdown
Interface Vlan-interface80 has already been shut down
[PE1-Vlan-interface80] undo shutdown
[PE1-Vlan-interface80]
%Jul 10 10:10:10:687 2006 PE1 IFNET/5/LINK UPDOWN:
Vlan-interface80: link status is UP
*0.1686718 PE1 L2V/8/DBG:
L2VPN CCCEncapIntf RealTime Backup Modify IfState....entered
// L2VPN interface encapsulation state change realtime backup began.
*0.1686718 PE1 L2V/8/DBG:
L2VPN CCCEncapIntf RealTime Backup Modify IfState....leaving
// L2VPN interface encapsulation state change realtime backup finished.
*0.1686718 PE1 L2V/8/DBG:
L2VPN LocalLdp Realtime backup Modify VCState....entered
// L2VPN local LDP information realtime backup began.
*0.1686734 PE1 L2V/8/DBG:
L2VPN LocalLdp Realtime backup Modify VCState....leaving
// L2VPN local LDP information realtime backup finished.
*0.1686906 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Scheduler....entered
// L2VPN restore began.
*0.1686906 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Buffer....entered
// L2VPN restore buffer began.
*0.1686906 PE1 L2V/8/DBG:Slot=7;
L2VPN Parse Restore Buffer....entered
// L2VPN parse restore buffer began.
*0.1686906 PE1 L2V/8/DBG:Slot=7;
L2VPN CCCEncapIntfDLL Restore....entered
// L2VPN interface encapsulation restore began.
*0.1686906 PE1 L2V/8/DBG:Slot=7;
L2VPN CCCEncapIntfDLL Restore....leaving
48
// L2VPN interface encapsulation restore finished.
*0.1686906 PE1 L2V/8/DBG:Slot=7;
L2VPN Parse Restore Buffer....leaving
// L2VPN parse restore buffer finished.
*0.1686922 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Buffer....leaving
// L2VPN restore buffer finished.
*0.1686922 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Scheduler....leaving
// L2VPN restore buffer finished.
*0.1686922 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Scheduler....entered
// L2VPN restore began.
*0.1686922 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Buffer....entered
// L2VPN restore buffer began.
*0.1686937 PE1 L2V/8/DBG:Slot=7;
L2VPN Parse Restore Buffer....entered
// L2VPN parse restore buffer began.
*0.1686937 PE1 L2V/8/DBG:Slot=7;
L2VPN LocalLdp Restore....entered
// L2VPN local LDP information restore began.
*0.1686937 PE1 L2V/8/DBG:Slot=7;
L2VPN LocalLdp Restore....leaving
// L2VPN local LDP information restore finished.
*0.1686937 PE1 L2V/8/DBG:Slot=7;
L2VPN Parse Restore Buffer....leaving
// L2VPN parse restore buffer finished.
*0.1686937 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Buffer....leaving
// L2VPN restore buffer finished.
*0.1686937 PE1 L2V/8/DBG:Slot=7;
L2VPN Restore Scheduler....leaving
// L2VPN restore finished.
49
MPLS L3VPN debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging l3vpn
Use debugging l3vpn to enable debugging for L3VPN.
Use undo debugging l3vpn to disable debugging for L3VPN.
Syntax
debugging l3vpn { all | hsb | cfgmsg }
undo debugging l3vpn { all | hsb | cfgmsg }
Default
The debugging for L3VPN is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for L3VPN.
hsb: Specifies debugging for L3VPN hot standby.
cfgmsg: Specifies debugging for L3VPN configuration message processing.
Usage guidelines
Table 1 describes the output fields and messages for the debugging l3vpn command.
Table 33 Output from the debugging l3vpn command
Field
Description
L3VPN VRFMGM VrfCreate....entered
L3VPN began to create VPN instances.
L3VPN VRFMGM VrfCreate....leaving
L3VPN finished creating VPN instances.
L3VPN VRFMGM RdAssign....entered
L3VPN began to assign a route distinguisher.
L3VPN VRFMGM RdAssign....leaving
L3VPN finished assigning a route distinguisher.
L3VPN VRFMGM RtList Assign....entered
L3VPN began to assign VPN targets.
L3VPN VRFMGM RtList Assign....leaving
L3VPN finished assigning VPN targets.
L3VPN VRFMGM CreateDesc....entered
L3VPN began to create a description for the current
VPN instance.
L3VPN VRFMGM CreateDesc....leaving
L3VPN created a description for the current VPN
instance.
50
Field
Description
L3VPN VRFMGM DeleteDesc....entered
L3VPN began to delete the description of the current
VPN instance.
L3VPN VRFMGM DeleteDesc....leaving
L3VPN deleted the description of the current VPN
instance.
L3VPN VRFMGM Import Route Policy
Assign....entered
L3VPN began to assign an import route policy.
L3VPN VRFMGM Import Route Policy
Assign....leaving
L3VPN finished assigning an import route policy.
L3VPN VRFMGM MaxRoute....entered
L3VPN started the limit on the maximum number of VPN
routes.
L3VPN VRFMGM MaxRoute....leaving
L3VPN ended the limit on the maximum number of VPN
routes.
L3VPN VRFMGM Tunnel Policy Assign....entered
L3VPN began to assign a tunnel policy.
L3VPN VRFMGM Tunnel Policy Assign....leaving
L3VPN finished assigning a tunnel policy.
L3VPN VRFMGM Export Route Policy
Assign....entered
L3VPN began to assign an export route policy.
L3VPN VRFMGM Export Route Policy
Assign....leaving
L3VPN finished assigning an export route policy.
L3VPN VRFMGM Import Route Policy
Delete....entered
L3VPN began to delete an import route policy.
L3VPN VRFMGM Import Route Policy
Delete....leaving
L3VPN finished deleting an import route policy.
L3VPN VRFMGM Export Route Policy
Delete....entered
L3VPN began to delete an export route policy.
L3VPN VRFMGM Export Route Policy
Delete....leaving
L3VPN finished deleting an export route policy.
L3VPN VRFMGM Tunnel Policy Delete....entered
L3VPN began to delete a tunnel policy.
L3VPN VRFMGM Tunnel Policy Delete....leaving
L3VPN finished deleting a tunnel policy.
L3VPN VRFMGM RtDelete....entered
L3VPN began to delete a VPN-Target.
L3VPN VRFMGM RtDelete....leaving
L3VPN finished deleting a VPN-Target.
L3VPN VRFMGM RtDelete All....entered
L3VPN began to delete a route distinguisher.
L3VPN VRFMGM RtDelete All....leaving
L3VPN finished deleting a route distinguisher.
L3VPN VRFMGM IfAssociate....entered
L3VPN began to associate a VPN with an interface.
L3VPN VRFMGM IfAssociate....leaving
L3VPN finished associating a VPN with an interface.
L3VPN VRFMGM IfDisassociate....entered
L3VPN began to disassociate a VPN from an interface.
L3VPN VRFMGM IfDisassociate....leaving
L3VPN finished disassociating a VPN from an interface.
L3VPN VRFMGM VrfDelete....entered
L3VPN began to delete a VPN.
L3VPN VRFMGM VrfDelete....leaving
L3VPN finished deleting a VPN.
IntfDelete Notify....entered
L3VPN began to delete an interface (logical).
IntfDelete Notify....leaving
L3VPN finished deleting an interface (logical).
51
Field
Description
L3VPN CORE Get Batch BackUp Data....entered
L3VPN began to get batch backup data.
L3VPN CORE Get Batch BackUp Data....leaving
L3VPN finished getting batch backup data.
PackOneBatchVrf....entered
L3VPN began to get a batch of VRFs.
PackOneBatchVrf....leaving
L3VPN finished getting a batch of VRFs.
PackOneVrf....entered
L3VPN began to get one VRF.
PackOneVrf....leaving
L3VPN finished getting one VRF.
Vrf: VrfId bind Interface: IfIndex success
L3VPN bound a VRF with an interface successfully.
Vrf: VrfId unbind Interface: IfIndex success
L3VPN unbound a VRF from an interface successfully.
Vrf: VrfId bind Interface: IfIndex failure
L3VPN failed to bind a VRF with an interface.
Vrf: VrfId unbind Interface: IfIndex failure
L3VPN failed to unbind a VRF from an interface.
Receive (chassis chassisID, slot slotID) Plug In Notify
L3VPN received the card (in chassis chassisID, slot
slotID) plug-in notify message.
Examples
# Enable all types of debugging for L3VPN. Output similar to the following example is generated when
these tasks are performed in order:
•
Create a VPN instance.
•
Configure an RD and VPN target.
•
Configure a description for the VPN instance and delete it.
•
Configure an import route policy.
•
Configure a VPN route number limit.
•
Bind the VPN instance to an interface.
<Sysname> debugging l3vpn all
[Sysname] ip vpn-instance vpna
*0.1362469 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM VrfCreate....entered
// L3VPN began to create a VPN instance.
*0.1362469 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM VrfCreate....leaving
// L3VPN finished creating the VPN instance.
[Sysname-vpn-instance-vpna] route-distinguisher 100:1
*0.1538078 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM RdAssign....entered
// L3VPN began to assign an RD.
*0.1538078 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM RdAssign....leaving
// L3VPN finished assigning the RD.
[Sysname-vpn-instance-vpna] vpn-target 111:1
IVT Assignment result:
VPN-Target assignment is successful
EVT Assignment result:
52
VPN-Target assignment is successful
*0.1669656 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM RtList Assign....entered
// L3VPN began to assign VPN targets.
*0.1669656 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM RtList Assign....leaving
// L3VPN finished assigning VPN targets.
*0.1669656 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM RtList Assign....entered
// L3VPN began to assign VPN target.
*0.1669656 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM RtList Assign....leaving
// L3VPN finished assigning VPN target.
[Sysname-vpn-instance-vpna]description this is orange's vpn
*0.1912719 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM CreateDesc....entered
// L3VPN began to create a description for the current VPN instance.
*0.1912719 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM CreateDesc....leaving
// L3VPN created a description for the current VPN instance.
[Sysname-vpn-instance-vpna]undo description
*0.3361156 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM DeleteDesc....entered
// L3VPN began to delete the description of the current VPN instance.
*0.3361156 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM DeleteDesc....leaving
// L3VPN deleted the description of the current VPN instance.
[Sysname-vpn-instance-vpna]import route-policy irp1
Policy configuration is successful, but needs to be created
*0.2217297 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM Import Route Policy Assign....entered
// L3VPN began to assign import route policy.
*0.2217297 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM Import Route Policy Assign....leaving
// L3VPN finished assigning import route policy.
[Sysname-vpn-instance-vpna]routing-table limit 1000 100
*0.2413234 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM MaxRoute....entered
// L3VPN started the limit on the maximum number of VPN routes.
*0.2413234 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM MaxRoute....leaving
// L3VPN ended the limit on the maximum number of VPN routes.
[Sysname-vpn-instance-vpna]tnl-policy tp1
Policy configuration is successful, but needs to be created
53
*0.2806641 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM Tunnel Policy Assign....entered
// L3VPN began to assign tunnel policy.
*0.2806641 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM Tunnel Policy Assign....leaving
// L3VPN finished assigning tunnel policy.
[Sysname-vpn-instance-vpna]export route-policy erp1
Policy configuration is successful, but needs to be created
*0.2118578 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM Export Route Policy Assign....entered
// L3VPN began to assign export route policy.
*0.2118578 Sysname L3VPN/8/L3VPNDBG:
L3VPN VRFMGM Export Route Policy Assign....leaving
// L3VPN finished assigning export route policy.
[Sysname-Vlan-interface1]ip binding vpn-instance vpna
Source File: l3v_core_if.c , Line No: 184
Vrf: 1 bind Interface: 120717312 success
// L3VPN bound the VRF to the interface.
[Sysname-Vlan-interface1]undo ip binding vpn-instance vpna
Source File: l3v_core_if.c , Line No: 302
Vrf: 1 unbind Interface: 120717312 success
// L3VPN unbound the VRF from the interface.
54
MPLS OAM debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging mpls oam
CAUTION:
Executing this debugging command might affect sending and receiving of MPLS OAM protocol packets.
Use this command only when necessary.
Use debugging mpls oam to enable one or all types of debugging for MPLS OAM.
Use undo debugging mpls oam to disable MPLS OAM debugging.
Syntax
debugging mpls oam { all | bdi | cv | decode | defect-detect | error | fdi | ffd |
fsm | hsb | main | packet | process | timer }
undo debugging mpls oam { all | bdi | cv | decode | defect-detect | error | fdi |
ffd | fsm | hsb | main | packet | process | timer }
Default
No debugging is enabled for MPLS OAM.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging.
bdi: Specifies debugging for backward defect indication (BDI) messages.
cv: Specifies debugging for connectivity verification (CV) messages.
decode: Specifies debugging for encoding and decoding.
defect-detect: Specifies debugging for defect detection.
error: Specifies debugging for errors.
fdi: Specifies debugging for forward defect indication (FDI) messages.
ffd: Specifies debugging for fast fault detection.
fsm: Specifies debugging for finite state machine (FSM).
hsb: Specifies debugging for hot standby (HSB).
main: Specifies the main debugging.
55
packet: Specifies debugging for packets.
process: Specifies debugging for processing.
timer: Specifies debugging for timers.
Usage guidelines
Table 1 describes the output fields and messages for the debugging mpls oam bdi command.
Table 34 Output from the debugging mpls oam bdi command
Field
Description
OAM Index
OAM instance index.
OAM DD
OAM defect detection.
Table 2 describes the output fields and messages for the debugging mpls oam cv command.
Table 35 Output from the debugging mpls oam cv command
Field
Description
OAM Index
OAM instance index.
OAM DD
OAM defect detection.
Table 3 describes the output fields and messages for the debugging mpls oam decode command.
Table 36 Output from the debugging mpls oam decode command
Field
Description
OAM Index
OAM instance index.
BIP16
BIP16 check.
Frequency
Frequency of OAM packets.
padding
Packet payload.
defect location
Number of the Autonomous System (AS) where the
defect is located.
lsr id
LSR ID in the TTSI.
tunnel id
Tunnel ID in the TTSI.
Out Label
Outgoing label.
processing board
Main processing board.
InLabel
Incoming label.
BoardId
Number of the main processing board.
Table 4 describes the output fields and messages for the debugging mpls oam defect-detect command.
Table 37 Output from the debugging mpls oam defect-detect command
Field
Description
OAM Index
OAM instance index.
lsr id
LSR ID in the TTSI.
56
Field
Description
tunnel id
Tunnel ID in the TTSI.
ASM
OAM state machine.
ext-bdi
Extended BDI, used for RLSN.
available
available state of the state machine.
unavailable
unavailable state of the state machine.
RLSN
Remote link status notification.
Table 5 describes the output fields and messages for the debugging mpls oam error command.
Table 38 Output from the debugging mpls oam error command
Field
Description
OAM Index
OAM instance index.
ava2unava
OAM state machine changes from available to
unavailable.
OAM DD
OAM defect detection.
PS
Protection switching.
HA
High availability.
BoardId
Number of the main processing board.
Table 6 describes the output fields and messages for the debugging mpls oam fdi command.
Table 39 Output from the debugging mpls oam fdi command
Field
Description
OAM Index
OAM instance index.
Table 7 describes the output fields and messages for the debugging mpls oam ffd command.
Table 40 Output from the debugging mpls oam ffd command
Field
Description
OAM Index
OAM instance index.
OAM DD
OAM defect detection.
Table 8 describes the output fields and messages for the debugging mpls oam fsm command.
Table 41 Output from the debugging mpls oam fsm command
Field
Description
OAM Index
OAM instance index.
ASM
OAM defect detect.
ava2unava
OAM state machine changes from available to
unavailable.
Unava
unavailable state of the OAM state machine.
57
Table 9 describes the output fields and messages for the debugging mpls oam hsb command.
Table 42 Output from the debugging mpls oam hsb command
Field
Description
OAM Index
OAM instance index.
status
HA state.
ha type
Type of the HA event.
Table 10 describes the output fields and messages for the debugging mpls oam main command.
Table 43 Output from the debugging mpls oam main command
Field
Description
OAM Index
OAM instance index.
MPLS OAM MN
Main debugging of MPLS OAM.
ha type
Type of the HA event.
InLabel
Incoming label.
BoardId
Number of the main processing board.
tunnel id
Tunnel ID of the ingress.
Lsp Id
LSP ID of the CRLSP.
InLabel
Incoming label of the static LSP.
TnlIfindex
Tunnel interface index.
Lsp Status
Status of the CRLSP.
IfIndex
Interface index.
MsgType
Interface message.
rev lsp
Backward LSP.
pdt
Product.
Table 11 describes the output fields and messages for the debugging mpls oam packet command.
Table 44 Output from the debugging mpls oam packet command
Field
Description
OAM Index
OAM instance index.
Processing Board
Number of the main processing board.
TTSI-Lsrid
LSR ID in the TTSI.
TTSI-Tunnelid
Tunnel ID in the TTSI.
Table 12 describes the output fields and messages for the debugging mpls oam process command.
58
Table 45 Output from the debugging mpls oam process command
Field
Description
OAM Index
OAM instance index.
release oam
OAM sent the OAM instance to the main processing
board.
update entry config
OAM updated the OAM instance configuration.
Table 13 describes the output fields and messages for the debugging mpls oam timer command.
Table 46 Output from the debugging mpls oam timer command
Field
Description
ASM ava2unava timer
available state timer of the OAM state machine.
ASM unava2ava timer
unavailable state timer of the OAM state machine.
Rlsn timer
Timer for sending extended BDI messages.
release timer
OAM released the OAM instance timer.
Examples
# Enable MPLS OAM processing debugging. Output similar to the following example is generated when
these tasks are performed:
•
Configure a TE tunnel between two routers.
•
Execute the debugging mpls oam process command on the tunnel ingress router.
•
Configure an OAM instance on the router.
<PE1> debugging mpls oam process
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:6571: begin to find oam by detect tunnel
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:6581: find oam by tunnel ifindex at ingress
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:6618: find oam from detect tunnel hash table
// OAM was finding the OAM instance by the detected tunnel.
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:6632: have not find oam from detect tunnel hash table
// OAM instance was not found.
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:4473: begin to add oam entry.
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:4498: Success to alloc oam entry from gads.
// OAM started to add the OAM instance.
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:4544: Begin to fill oam entry.
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:5757: begin to add detect tunnel hash node
// OAM filled information into the OAM instance.
59
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:4881: Begin to release oam!
// OAM started to send the OAM instance to the main processing board.
*Nov 29 16:01:18:125 2006 PE1 OAM/7/PROCESS:
17:9258: GetProcBoard:begin to select process board
*Nov 29 16:01:18:146 2006 PE1 OAM/7/PROCESS:
17:9474: SelAgtBoard process start
// OAM started to select the main processing board.
*Nov 29 16:01:18:162 2006 PE1 OAM/7/PROCESS:
17:13233: GetBoardByArp: ulVrfIndex = 0, ulNextHop = c010102, ulIfIndex = 120717313
// OAM was obtaining the board where the outgoing interface resides according to the ARP
information.
*Nov 29 16:01:18:162 2006 PE1 OAM/7/PROCESS:
17:13291: GetBoardByArp:
ulBoard = 1
*Nov 29 16:01:18:162 2006 PE1 OAM/7/PROCESS:
17:9517: OAM PROC: SelAgtBoard
get arp board
(1)
*Nov 29 16:01:18:162 2006 PE1 OAM/7/PROCESS:
17:9543: OAM PROC: SelAgtBoard
get main board
(1)
*Nov 29 16:01:18:365 2006 PE1 OAM/7/PROCESS:
17:9405: OAM PROC: GetProcBoard
vlan get board
(1)
*Nov 29 16:01:18:365 2006 PE1 OAM/7/PROCESS:
17:9762: begin to add board dll
// Board 1 was obtained.
*Nov 29 16:01:18:365 2006 PE1 OAM/7/PROCESS:
17:2649: begin to add search node
*Nov 29 16:01:18:365 2006 PE1 OAM/7/PROCESS:
17:2671: begin to select which search node to add
*Nov 29 16:01:18:365 2006 PE1 OAM/7/PROCESS:
17:2694: oam proc:Add ttsi node at ingressmpl
*Nov 29 16:01:18:831 2006 PE1 OAM/7/PROCESS:
17:2897: begin to add ttsi node
*Nov 29 16:01:18:831 2006 PE1 OAM/7/PROCESS:
17:2916: sucess to memory alloc for ttsi node
*Nov 29 16:01:18:831 2006 PE1 OAM/7/PROCESS:
17:2947: add ttsi node at ingress table
*Nov 29 16:01:18:831 2006 PE1 OAM/7/PROCESS:
17:3046: finish to add ttsi node
*Nov 29 16:01:18:831 2006 PE1 OAM/7/PROCESS:
17:2785: finish to add search node
*Nov 29 16:01:18:831 2006 PE1 OAM/7/PROCESS:
17:4717: OAM_SetEntryStatRecord: ulIgrReleaseEntryNumLowFreq add 1
// OAM added the search table.
*Nov 29 16:01:18:847 2006 PE1 OAM/7/PROCESS:Slot=1;
17:1580:
IPC Msg Type: 4
// The interface board received a message of type 4 (search table).
60
*Nov 29 16:01:18:847 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2649: begin to add search node
*Nov 29 16:01:18:847 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2671: begin to select which search node to add
*Nov 29 16:01:18:847 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2694: oam proc:Add ttsi node at ingress
*Nov 29 16:01:18:864 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2897: begin to add ttsi node
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2916: sucess to memory alloc for ttsi node
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2947: add ttsi node at ingress table
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:3046: finish to add ttsi node
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:2785: finish to add search node
// OAM added a search node.
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:1580:
IPC Msg Type: 1
// The interface board received a message of type 1 (add instance).
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0060: begin to set entry
*Nov 29 16:01:18:879 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0072: seccess to alloc gads node
*Nov 29 16:01:18:895 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0121: MPLS OAM SetEntryIO: start to mallo the space for oam packet
*Nov 29 16:01:18:895 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0140: MPLS OAM SetEntryIO: Start to fill the CV FFD Packet s
*Nov 29 16:01:18:908 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0153: MPLS OAM SetEntryIO: End to fill the CV FFD Packet
// The interface board started to add an OAM instance.
*Nov 29 16:01:18:908 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0188: MPLS OAM SetEntryIO: sucess to malloc the space for oam packet and fill the packet
// The OAM instance was added successfully.
*Nov 29 16:01:18:908 2006 PE1 OAM/7/PROCESS:Slot=1;
17:0221: finish to add entry on io board oam ingress enable Tunnel1
// OAM finished adding the OAM instance.
61
MPLS TE debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging isis traffic-eng
Use debugging isis traffic-eng to enable debugging for IS-IS traffic engineering.
Use undo debugging isis traffic-eng to disable debugging for IS-IS traffic engineering.
Syntax
debugging isis traffic-eng { advertisement | event } [ process-id | vpn-instance vpn-instance-name ]
undo debugging isis traffic-eng { advertisement | event } [ process-id
vpn-instance-name ]
| vpn-instance
Default
Debugging for IS-IS traffic engineering is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
advertisement: Specifies debugging for IS-IS advertisements.
event: Specifies debugging for IS-IS traffic engineering events.
process-id: Specifies debugging for an IS-IS process. The process-id argument represents the IS-IS
process ID in the range of 1 to 65535.
vpn-instance vpn-instance-name: Specifies debugging for an MPLS L3VPN instance. The
vpn-instance-name argument represents the VPN instance name, a case-sensitive string of 1 to 31
characters.
Examples
# Enable debugging for IS-IS traffic engineering events.
<Sysname> debugging isis traffic-eng event
debugging mpls moam packet
Use debugging mpls moam packet to enable debugging for MPLS TP OAM (MOAM).
Use undo debugging mpls moam packet to disable debugging for MOAM.
Syntax
debugging mpls moam packet
undo debugging mpls moam packet
62
Default
Debugging for MOAM is disabled.
Views
User view
Default command level
1: Monitor level
Examples
# Enable debugging for MOAM packets. Use the moam lm command to detect the packet loss rates for
a bidirectional MPLS TE tunnel on the device.
<Sysname> debugging mpls moam packet
<Sysname> moam lm -c 1 te tunnel 2
Loss measurement for Tunnel 2, press CTRL_C to break
*Jan 30 16:46:36:781 2011 Sysname MOAM/7/Packet:
>>>>Send LM query msg.
Sequence number: 0
// MOAM sent an LM request message. The sequence number of the message is 0.
*Jan 30 16:46:37:062 2011 Sysname MOAM/7/Packet:
>>>>Send LM query msg.
Sequence number: 1
// MOAM sent an LM request message. The sequence number of the message is 1.
1. TxLoss = 1 (100.00% loss), Rxloss = 1 (100.00% loss)
*Jan 30 16:46:37:094 2011 Sysname MOAM/7/Packet:
Received LM packet: C1: 0, C2: 0, C3: 0, C4: 0
*Jan 30 16:46:37:125 2011 Sysname MOAM/7/Packet:
Calculate send packet loss
Ingress send
: 1
Egress
receive: 0
Txloss
: 1
// One sent packet was lost.
*Jan 30 16:46:37:125 2011 Sysname MOAM/7/Packet:
Calculate receive packet loss
Egress
send
: 1
Ingress receive: 0
Rxloss
: 1
// One packet failed to be received.
--- Loss measurement statistics for Tunnel 2 --TxLoss/TxTotal = 1/1 (100.00% loss)
RxLoss/RxTotal = 1/1 (100.00% loss)
debugging mpls rsvp-te
Use debugging mpls rsvp-te to enable debugging for MPLS RSVP-TE.
Use undo debugging mpls rsvp-te to disable debugging for MPLS RSVP-TE.
63
Syntax
debugging mpls rsvp-te { all | authentication | bundle | encdec | error | hello | hsb | main | msg-hex
| path | perr | ptear | rconf | rerr | resv | rtear | socket | srefresh | timer | tool | traffic-control |
tunnel-id { tunnel-id | all } }
undo debugging mpls rsvp-te { all | authentication | bundle | encdec | error | hello | hsb | main |
msg-hex | path | perr | ptear | rconf | rerr | resv | rtear | socket | srefresh | timer | tool |
traffic-control | tunnel-id { tunnel-id | all } }
Default
Debugging for MPLS RSVP-TE is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging.
authentication: Specifies debugging for authentication.
bundle: Specifies debugging for bundle.
encdec: Specifies debugging for encoding and decoding.
error: Specifies debugging for errors.
hello: Specifies debugging for hello.
hsb: Specifies debugging for hot standby backup.
main: Specifies debugging for main.
msg-hex: Specifies debugging for message hex format.
path: Specifies debugging for paths.
perr: Specifies debugging for path errors.
ptear: Specifies debugging for path tearing down.
rconf: Specifies debugging for reservation confirmation.
rerr: Specifies debugging for reservation errors.
resv: Specifies debugging for reservation message.
rtear: Specifies debugging for reservation tearing down.
socket: Specifies debugging for socket.
srefresh: Specifies debugging for Srefresh.
timer: Specifies debugging for timer.
tool: Specifies debugging for tools.
traffic-control: Specifies debugging for traffic control.
tunnel-id: Specifies tunnel debugging. The tunnel-id argument specifies a single tunnel by ID, which is in
the range of 0 to 2048. The all keyword specifies all tunnels.
64
Usage guidelines
For the completeness of debugging information, H3C recommends that you enable debugging mpls
rsvp-te tunnel-id for each type of RSVP-TE debugging except for debugging mpls rsvp-te all.
Table 1 describes output fields and messages for the debugging mpls rsvp authentication command.
Table 47 Output from the debugging mpls rsvp authentication command
Field
Description
Local IfEntry number is x.
The local RSVP-TE interface sequence number is X.
Table 2 describes output fields and messages for the debugging mpls rsvp error command.
Table 48 Output from the debugging mpls rsvp error command
Field
Description
Invalid IfIndex
Invalid interface index.
IF Not Enbale Authenticate
Authentication is not enabled on the interface.
Table 3 describes output fields and messages for the debugging mpls rsvp hello command.
Table 49 Output from the debugging mpls rsvp hello command
Field
Description
Nbr is lost, process Frr Nbr lost
Neighbor was lost. Frr processed neighbor loss.
Table 4 describes output fields and messages for the debugging mpls rsvp hsb command.
Table 50 Output from the debugging mpls rsvp hsb command
Field
Description
AMB: Backup Global Data and send to HAC
Active MPU: Backed up the global data and sent it to
HAC.
SMB: Restore Global Data
Standby MPU: Restored the global data.
SMB: RealTime Restore TCSB Data
Standby MPU: Restored the traffic control state block
(TCSB) data.
Table 5 describes output fields and messages for the debugging mpls rsvp main command.
Table 51 Output from the debugging mpls rsvp main command
Field
Description
RSVP GR process: RSVP NBR x.x.x.x restarting.
RSVP GR process: RSVP neighbor xxx is restarting.
Table 6 describes output fields and messages for the debugging mpls rsvp path command.
Table 52 Output from the debugging mpls rsvp path command
Field
Description
Path mesg Received with Lih xxx for IfAddr xxx
MPLS TE received a path message with the logical
interface handle (LIH) of xxx from interface xxx.
65
Field
Description
Unable to add PSB in IfEntry link
MPLS TE was unable to add PSB to the RSVP-TE
interface information.
Table 7 describes output fields and messages for the debugging mpls rsvp ptear command.
Table 53 Output from the debugging mpls rsvp ptear command
Field
Description
TearRSB by OutIf filter is Null, Send PathTear Msg
When processing TearRSB by outbound interface,
MPLS TE found the filter is null and sent a PathTear
message.
Table 8 describes output fields and messages for the debugging mpls rsvp resv command.
Table 54 Output from the debugging mpls rsvp resv command
Field
Description
Can't get IncIF
MPLS TE failed to get the inbound interface.
Resv mesg Received with Lih xxx for IfAdd xxx
Resv message received with logical interface handle
xxx for interface address xxx.
Table 9 describes output fields and messages for the debugging mpls rsvp traffic-control command.
Table 55 Output from the debugging mpls rsvp traffic-control command
Field
Description
Start update Tc process
MPLS TE started update traffic processing.
Examples
The following examples are based on the scenario in which two directly-connected devices have been
enabled with MPLS basic capability, MPLS TE basic capability, and MPLS RESV-TE capability.
# Enable RSVP-TE authentication on the interfaces between the two devices. Execute the debugging mpls
rsvp-te authentication and debugging mpls rsvp-te tunnel-id all commands. Then the two devices
establish an MPLS TE tunnel.
<Sysname> debugging mpls rsvp-te authentication
<Sysname> debugging mpls rsvp-te tunnel-id all
*Nov 13 10:29:32:884 2006 Sysname RSVP/7/AUTH:
04:0138: Sending Sequence number is 1163413641 2.
// RSVP sent a sequence number 1163413641 2.
*Nov 13 10:29:41:444 2006 Sysname RSVP/7/AUTH:
04:0278: Local IfEntry
number is 1163413640 2.
// The sequence number of the local RSVP-TE interface is 1163413640 2.
*Nov 13 10:29:41:444 2006 Sysname RSVP/7/AUTH:
04:0281: Receiving Sequence number is 1163413640 3.
// RSVP received a sequence number 1163413640 3.
66
# Enable the RSVP-TE Hello function in MPLS view and interface view. Execute both the debugging mpls
rsvp-te hello and debugging mpls rsvp-te tunnel-id all commands. Then the two devices establish an
MPLS TE tunnel.
<Sysname> debugging mpls rsvp-te hello
<Sysname> debugging mpls rsvp-te tunnel-id all
*Nov 13 10:39:00:618 2006 Sysname RSVP/7/HELLO:
10:0353: Receiving Hello REQ Message form 80.1.1.2:
// RSVP received a Hello REQ message from 80.1.1.2.
*Nov 13 10:39:00:618 2006 Sysname RSVP/7/HELLO:
10:0359: Src_Instance : 0x1d1
Dst_Instance : 0x1ce
// The source instance is 0x1d1, and the destination instance is 0x1ce.
*Nov 13 10:39:00:634 2006 Sysname RSVP/7/HELLO:
10:0506: Sending Hello ACK Message:
// RSVP sent a Hello ACK message.
*Nov 13 10:39:00:634 2006 Sysname RSVP/7/HELLO:
10:0511: Src_Instance : 0x1ce
Dst_Instance : 0x1d1
// The source instance is 0x1ce, and the destination instance is 0x1d1.
# Execute both the debugging mpls rsvp-te path and debugging mpls rsvp-te tunnel-id all commands.
Then the two devices establish an MPLS TE tunnel.
<Sysname> debugging mpls rsvp-te path
<Sysname> debugging mpls rsvp-te tunnel-id all
*Nov 13 10:46:19:130 2006 Sysname RSVP/7/PATH:
13:2566: Form and Send Path Msg!
// RSVP formed and sent a PATH message.
*Nov 13 10:46:19:145 2006 Sysname RSVP/7/PATH:
13:2808: Path mesg sent with Lih 2818064 for IfAdd 50010101
// RSVP sent a PATH message from interface 50010101, with the LIH of 2818064.
*Nov 13 10:46:19:145 2006 Sysname RSVP/7/PATH:
13:5017: Successfully send path refresh message...
// RSVP sent a PATH refresh message.
*Nov 13 10:46:19:145 2006 Sysname RSVP/7/PATH:
13:5023: Tunnel address = 88.2.2.2, Tunnel ID =1, next hop = 80.1.1.2
// The tunnel's destination address is 88.2.2.2, the tunnel ID is 1, and the next hop is 80.1.1.2.
*Nov 13 10:46:19:145 2006 Sysname RSVP/7/PATH:
13:5028: Timer interval configured=30000 : Timer interval used =29100
// The refresh timer setting is 30000 milliseconds, and the actual timer value is 29100 milliseconds.
*Nov 13 10:46:19:145 2006 Sysname RSVP/7/PATH:
13:5031: PATH msg MsgId = 0x2
// The MsgId of the PATH message is 0x2.
# Configure FRR so that when the PLR node detects a need for FRR switchover, it will send a path error
message to notify the upstream node of the FRR switchover. Execute both the debugging mpls rsvp-te
perr and debugging mpls rsvp-te tunnel-id all commands.
<Sysname> debugging mpls rsvp-te perr
<Sysname> debugging mpls rsvp-te tunnel-id all
67
*Nov 13 11:39:19:146 2006 Sysname RSVP/7/PERR:
06:0581: Start PathErr message processing...
// RSVP started to send a PathErr message.
*Nov 13 11:39:19:146 2006 Sysname RSVP/7/PERR:
06:0583: End PathErr message process.
// RSVP finished sending the PathErr message.
# Execute both the debugging mpls rsvp-te ptear and debugging mpls rsvp-te tunnel-id all commands,
and then delete the tunnel.
<Sysname> debugging mpls rsvp-te ptear
<Sysname> debugging mpls rsvp-te tunnel-id all
*Nov 13 11:43:44:179 2006 Sysname RSVP/7/PTEAR:
15:1086: LSPM delete lsp, Send PathTear Msg
// LSPM deleted the LSP and is preparing to send a PathTear message.
*Nov 13 11:43:44:195 2006 Sysname RSVP/7/PTEAR:
16:0263: Form and Send PathTear Msg
// RSVP constructed and sent the PathTear message.
*Nov 13 11:43:44:195 2006 Sysname RSVP/7/PTEAR:
16:0336: Delete FilteSpec In Rsb.
// RSVP deleted the FilteSpec in RSB.
*Nov 13 11:43:44:195 2006 Sysname RSVP/7/PTEAR:
16:0430: Delete Psb
// RSVP deleted PSB.
# Execute both the debugging mpls rsvp-te resv and debugging mpls rsvp-te tunnel-id all commands.
Then the two devices establish an MPLS TE tunnel.
<Sysname> debugging mpls rsvp-te resv
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
06:0593: Start Resv message processing...
// RSVP started RESV message processing.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0138: Resv mesg Received with Lih 2818064 for IfAdd 50030101
// RSVP received from address 50030101 a RESV message with Lih 2818064.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0141: Session: 88.1.1.1:6
// The session is 88.1.1.1:6.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0252: Reservation Style is SE
// The reservation style is SE.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0410: Process Current Flow Descriptor Begin:
// RSVP started to process the current flow descriptor.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0680: Matching RSB Exists
// RSVP found a matching PSB.
68
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0727: Update Old RSB!
// RSVP updated the old RSB.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0764: message bandwidth: 0
// The bandwidth request carried by the message is 0.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0778: LSPID: 6
// The LSP ID is 6.
*Nov 13 11:55:29:990 2006 Sysname RSVP/7/RESV:
19:0783: end display LSP ID
// RSVP finished displaying LSP ID.
*Nov 13 11:55:30:00 2006 Sysname RSVP/7/RESV:
19:0805: Get corresponding PSB for FilterSpec.
// RSVP got the PSB for FilteSpec.
*Nov 13 11:55:30:00 2006 Sysname RSVP/7/RESV:
19:0857: LSPID: 6
RRO in RSB: 80.3.1.1
Label in RSB: 1037
RRO in RSB: 88.3.3.3
RRO in RSB: 80.2.1.2
RRO in RSB: 80.2.1.1
Label in RSB: 1033
RRO in RSB: 88.2.2.2
RRO in RSB: 80.1.1.2
RRO in RSB: 80.1.1.1
Label in RSB: 3
RRO in RSB: 88.1.1.1
*Nov 13 11:55:30:00 2006 Sysname RSVP/7/RESV:
19:0863: RESV msg MsgID = 0x0
// The Msg ID of the RESV message is 0x0.
*Nov 13 11:55:30:00 2006 Sysname RSVP/7/RESV:
19:0984: Delete Message ID
// RSVP deleted the message ID.
*Nov 13 11:55:30:00 2006 Sysname RSVP/7/RESV:
19:0414: Process Current Flow Descriptor End
// RSVP finished processing the current flow descriptor.
*Nov 13 11:55:30:16 2006 Sysname RSVP/7/RESV:
06:0595: End Resv message process.
// RSVP finished processing the RESV message.
debugging mpls te cspf
Use debugging mpls te cspf to enable debugging for CSPF.
Use undo debugging mpls te cspf to disable debugging for CSPF.
69
Syntax
debugging mpls te cspf { all | computation | errors | events | tedb }
undo debugging mpls te cspf { all | computation | errors | events | tedb }
Default
Debugging for CSPF is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for MPLS TE CSPF.
computation: Specifies debugging for CSPF calculation.
error: Specifies debugging for errors.
event: Specifies debugging for events.
tedb: Specifies debugging for traffic engineering database (TEDB).
Usage guidelines
Table 10 describes output fields and messages for the debugging mpls te cspf computation command.
Table 56 Output from the debugging mpls te cspf computation command
Field
Description
Beginning pre-process and the next-hop number is
×××.
Preprocessing begins. Number of hops included in the
display path is ×××.
Table 11 describes output fields and messages for debugging mpls te cspf errors command.
Table 57 Output from the debugging mpls te cspf errors command
Field
Description
Others address has been configured to include hop on
this node.
Other addresses on this node have been configured in
the include hop.
Examples
# Configure MPLS basic capability and MPLS TE basic capability on two directly-connected devices.
Execute the debugging mpls te cspf computation command. Configure CSPF.
<Sysname> debugging mpls te cspf computation
*Sep 22 02:20:19:989 2003 Sysname CSPF/7/COMPUTE:
01:7252: Begining CSPF computation.The LspId: 9, IngressLsrId: b0b0b0b, EgressLsrId:
38010101 .
// CSPF computation started. The LSP ID is 9, ingress LSR ID is b0b0b0b, and egress LSR ID is 38010101.
*Sep 22 02:20:20:167 2003 Sysname CSPF/7/COMPUTE:
01:7262: The TE-class number is 7.
// The TE class number is 7.
*Sep 22 02:20:20:267 2003 Sysname CSPF/7/COMPUTE:
70
01:7278: The resource reserve policy is LSPM_RANDOM_FILL.
// The resource reservation policy is LSPM_RANDOM_FILL.
*Sep 22 02:20:20:397 2003 Sysname CSPF/7/COMPUTE:
01:6670: Beginning the first segment computation.
// The first segment computation started.
*Sep 22 02:20:20:517 2003 Sysname CSPF/7/COMPUTE:
01:6710: The current IGP is OSPF and the process id is 1.
// The current IGP protocol is OSPF, and the process ID is 1.
*Sep 22 02:20:20:647 2003 Sysname CSPF/7/COMPUTE:
01:3757: Beginning pre-process and the next-hop number is 0.
// The pre-process started. The number of hops in the display path is 0.
*Sep 22 02:20:20:787 2003 Sysname CSPF/7/COMPUTE:
01:3838: The start hop is 11.11.11.11 in current segment.
// The start hop in the current segment is 11.11.11.11.
*Sep 22 02:20:20:917 2003 Sysname CSPF/7/COMPUTE:
01:3994: The current end hop is same as egress id 56.1.1.1.
// The current end hop is the same as egress ID 56.1.1.1.
*Sep 22 02:20:21:58 2003 Sysname CSPF/7/COMPUTE:
01:6736: The current outgoing flag is 0, incoming flag is 0.
// The current outgoing flag is 0, and the incoming flag is also 0.
*Sep 22 02:20:21:197 2003 Sysname CSPF/7/COMPUTE:
01:7008: The current computation is loose.
// The current computation is loose computation.
*Sep 22 02:20:21:547 2003 Sysname CSPF/7/COMPUTE:
01:7139: The node with router id 56.1.1.1 is selected.
// The node with router ID 56.1.1.1 is selected.
*Sep 22 02:20:21:677 2003 Sysname CSPF/7/COMPUTE:
01:7197: The current segment computation is success and the final result is:
*Sep 22 02:20:21:837 2003 Sysname CSPF/7/COMPUTE:
01:2307: 0: 87.1.1.1
1: 87.1.1.2
//The current segment's computation is successful, and the final result is: 0: 87.1.1.1
*Sep 22 02:20:21:957 2003 Sysname CSPF/7/COMPUTE:
01:6754: The first segment computation is success.
// The first segment's computation is successful.
*Sep 22 02:20:22:77 2003 Sysname CSPF/7/COMPUTE:
01:7476: The CSPF path computation is success!
// The CSPF path computation is successful.
*Sep 22 02:20:22:197 2003 Sysname CSPF/7/COMPUTE:
01:7477: The final result is:
*Sep 22 02:20:22:297 2003 Sysname CSPF/7/COMPUTE:
01:2307: 0: 87.1.1.1
1: 87.1.1.2
*Sep 22 02:20:22:417 2003 Sysname CSPF/7/COMPUTE:
01:7482: The total metrics is: 1
// The total cost is 1.
71
1: 87.1.1.2.
*Sep 22 02:20:22:517 2003 Sysname CSPF/7/COMPUTE:
01:7493: The computation of path to egress is finished.
// Computation of the path to the egress has been finished.
# Configure MPLS basic capability and MPLS TE basic capability on two directly-connected devices.
Execute the debugging mpls te cspf events command. Establish OSPF neighbor relationship between the
two devices, and configure CSPF.
<Sysname> debugging mpls te cspf events
*Sep 22 02:31:58:656 2003 Sysname CSPF/7/EVENT:
05:0600: Received 87.1.1.1 link event: ADD.
// CSPF received an add event of link 87.1.1.1.
*Sep 22 02:31:58:765 2003 Sysname CSPF/7/EVENT:
05:0600: Received 87.1.1.2 link event: DELETE.
// CSPF received a delete event of link 87.1.1.2.
*Sep 22 02:31:58:885 2003 Sysname CSPF/7/EVENT:
05:0757: Received network LSA event: MODIFY.
// CSPF received a modify event of network LSA.
*Sep 22 02:31:58:995 2003 Sysname CSPF/7/EVENT:
05:0600: Received 87.1.1.2 link event: ADD.
// CSPF received an add event of link 87.1.1.2.
*Sep 22 02:31:59:105 2003 Sysname CSPF/7/EVENT:
05:0757: Received network LSA event: MODIFY.
// CSPF received a modify event of network LSA.
*Sep 22 02:31:59:215 2003 Sysname CSPF/7/EVENT:
05:0600: Received 87.1.1.2 link event: DELETE.
// CSPF received a delete event of link 87.1.1.2.
*Sep 22 02:31:59:335 2003 Sysname CSPF/7/EVENT:
05:0757: Received network LSA event: MODIFY.
// CSPF received a network LSA modify event.
*Sep 22 02:31:59:445 2003 Sysname CSPF/7/EVENT:
05:0600: Received 87.1.1.2 link event: ADD.
// CSPF received an add event of link 87.1.1.2.
*Sep 22 02:31:59:555 2003 Sysname CSPF/7/EVENT:
05:0757: Received network LSA event: MODIFY.
// CSPF received a network LSA modify event.
*Sep 22 02:32:00:284 2003 Sysname CSPF/7/EVENT:
05:0757: Received network LSA event: DELETE.
// CSPF received a network LSA delete event.
# Configure MPLS basic capability and MPLS TE basic capability on two directly-connected devices.
Execute the debugging mpls te cspf tedb command. Establish OSPF neighbor relationship between the
two devices, and configure CSPF.
<Sysname> debugging mpls te cspf tedb
*Sep 22 02:37:58:655 2003 Sysname CSPF/7/TEDB:
02:0170: Router node index added successfully to node hash table.
// CSPF added the Router node index to the node hash table.
72
*Sep 22 02:37:58:794 2003 Sysname CSPF/7/TEDB:
02:1872: Router Node for 11.11.11.11 has been added successfully.
// CSPF added the router node 11.11.11.11.
*Sep 22 02:37:58:934 2003 Sysname CSPF/7/TEDB:
02:1042: Area Id 0 added successfully to area id list of router node.
// CSPF added area ID 0 to the area ID list of the router node.
*Sep 22 02:37:59:74 2003 Sysname CSPF/7/TEDB:
02:1089: Link Index added successfully to Link Index list of router node.
// CSPF added the link Index to the Link Index list of the router node.
*Sep 22 02:37:59:224 2003 Sysname CSPF/7/TEDB:
02:0170: Router node index added successfully to node hash table.
// CSPF added the router node index to the node's hash table.
*Sep 22 02:37:59:364 2003 Sysname CSPF/7/TEDB:
02:2749: 87.1.1.1 has been added successfully to link table.
// CSPF added link 87.1.1.1 to the link table.
*Sep 22 02:37:59:494 2003 Sysname CSPF/7/TEDB:
02:3701: IGP received link info has been processed successfully.
// CSPF processed the IGP link information successfully.
*Sep 22 02:37:59:634 2003 Sysname CSPF/7/TEDB:
02:0273: Hash index deleted successfully from node hash table.
// CSPF deleted the hash index from node hash table.
*Sep 22 02:37:59:774 2003 Sysname CSPF/7/TEDB:
02:1138: Area Id 0 deleted successfully to area id list of router node.
// CSPF deleted area ID 0 from the area ID list of the router node.
*Sep 22 02:37:59:924 2003 Sysname CSPF/7/TEDB:
02:1184: Link Index deleted
successfully from Link Index list of router node.
// CSPF deleted the link Index from the Link Index list of the router node.
*Sep 22 02:38:00:94 2003 Sysname CSPF/7/TEDB:
02:3040: 87.1.1.2 link has been deleted successfully.
// CSPF deleted link 87.1.1.2.
*Sep 22 02:38:00:214 2003 Sysname CSPF/7/TEDB:
02:3701: IGP received link info has been processed successfully.
// CSPF processed the IGP link information successfully.
*Sep 22 02:38:00:354 2003 Sysname CSPF/7/TEDB:
02:3284: Network LSA for 87.1.1.2 has been modified successfully.
// CSPF modified the network LSA for 87.1.1.2.
*Sep 22 02:38:00:494 2003 Sysname CSPF/7/TEDB:
02:3799: IGP received network LSA has been processed successfully.
// CSPF processed the IGP network LSA successfully.
*Sep 22 02:38:00:634 2003 Sysname CSPF/7/TEDB:
02:1089: Link Index added successfully to Link Index list of router node.
// CSPF added the link index to the Link Index list of the router node.
*Sep 22 02:38:00:784 2003 Sysname CSPF/7/TEDB:
73
02:0170: Router node index added successfully to node hash table.
// CSPF added the router node index to the node's hash table.
*Sep 22 02:38:00:924 2003 Sysname CSPF/7/TEDB:
02:2749: 87.1.1.2 has been added successfully to link table.
// CSPF added link 87.1.1.2 to the link table.
*Sep 22 02:38:01:55 2003 Sysname CSPF/7/TEDB:
02:3701: IGP received link info has been processed successfully.
// CSPF processed the IGP link information successfully.
*Sep 22 02:38:01:194 2003 Sysname CSPF/7/TEDB:
02:3284: Network LSA for 87.1.1.2 has been modified successfully.
// CSPF modified the network LSA for 87.1.1.2.
*Sep 22 02:38:01:334 2003 Sysname CSPF/7/TEDB:
02:3799: IGP received network LSA has been processed successfully.
// CSPF processed the IGP network LSA successfully.
*Sep 22 02:38:01:484 2003 Sysname CSPF/7/TEDB:
02:0273: Hash index deleted successfully from node hash table.
// CSPF deleted the hash index from the node's hash table.
*Sep 22 02:38:01:624 2003 Sysname CSPF/7/TEDB:
02:1138: Area Id 0 deleted successfully to area id list of router node.
// CSPF deleted area ID 0 from the area ID list of the router node.
*Sep 22 02:38:01:774 2003 Sysname CSPF/7/TEDB:
02:1184: Link Index deleted
successfully from Link Index list of router node.
// CSPF deleted the link index from the Link Index list of the router node.
*Sep 22 02:38:01:934 2003 Sysname CSPF/7/TEDB:
02:3040: 87.1.1.2 link has been deleted successfully.
// CSPF deleted link 87.1.1.2.
*Sep 22 02:38:02:55 2003 Sysname CSPF/7/TEDB:
02:3701: IGP received link info has been processed successfully.
// CSPF processed the IGP link information successfully.
*Sep 22 02:38:02:194 2003 Sysname CSPF/7/TEDB:
02:3284: Network LSA for 87.1.1.2 has been modified successfully.
// CSPF modified the network LSA for 87.1.1.2.
*Sep 22 02:38:02:334 2003 Sysname CSPF/7/TEDB:
02:3799: IGP received network LSA has been processed successfully.
// CSPF processed the IGP network LSA.
*Sep 22 02:38:02:474 2003 Sysname CSPF/7/TEDB:
02:1089: Link Index added successfully to Link Index list of router node.
// CSPF added the link index to the Link Index list of the router node.
*Sep 22 02:38:02:624 2003 Sysname CSPF/7/TEDB:
02:0170: Router node index added successfully to node hash table.
// CSPF added the router node index to the node's hash table.
*Sep 22 02:38:02:764 2003 Sysname CSPF/7/TEDB:
02:2749: 87.1.1.2 has been added successfully to link table.
74
// CSPF added link 87.1.1.2 to the link table.
*Sep 22 02:38:02:904 2003 Sysname CSPF/7/TEDB:
02:3701: IGP received link info has been processed successfully.
// CSPF processed the IGP link information successfully.
*Sep 22 02:38:03:44 2003 Sysname CSPF/7/TEDB:
02:3284: Network LSA for 87.1.1.2 has been modified successfully.
// CSPF modified the network LSA for 87.1.1.2.
*Sep 22 02:38:03:184 2003 Sysname CSPF/7/TEDB:
02:3799: IGP received network LSA has been processed successfully.
// CSPF processed the IGP network LSA successfully.
*Sep 22 02:38:03:487 2003 Sysname CSPF/7/TEDB:
02:0326: Hash index deleted successfully from Network LSA hash table.
// CSPF deleted the hash index from the network LSA hash table.
*Sep 22 02:38:03:624 2003 Sysname CSPF/7/TEDB:
02:3378: Network LSA for 87.1.1.2 has been deleted successfully.
// CSPF deleted the network LSA for 87.1.1.2.
*Sep 22 02:38:03:764 2003 Sysname CSPF/7/TEDB:
02:3799: IGP received network LSA has been processed successfully.
// CSPF processed the IGP network LSA successfully.
*Sep 22 02:38:04:465 2003 Sysname CSPF/7/TEDB:
02:0219: Network LSA index added successfully to network LSA hash table.
// CSPF added the network LSA index to the network LSA hash table.
*Sep 22 02:38:04:614 2003 Sysname CSPF/7/TEDB:
02:3168: Network LSA for 87.1.1.2 has been added successfully.
// CSPF added the network LSA for 87.1.1.2.
*Sep 22 02:38:04:754 2003 Sysname CSPF/7/TEDB:
02:3799: IGP received network LSA has been processed successfully.
// CSPF processed the IGP network LSA successfully.
debugging mpls te management
Use debugging mpls te management to enable debugging for MPLS TE management.
Use undo debugging mpls te management to disable debugging for MPLS TE management.
Syntax
debugging mpls te management { all | auto-bandwidth-adjustment | events | fast-reroute |
link-administration | reoptimization | states }
undo debugging mpls te management { all | auto-bandwidth-adjustment | events | fast-reroute |
link-administration | reoptimization | states }
Default
Debugging for MPLS TE management is disabled.
Views
User view
75
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for MPLS TE management.
auto-bandwidth-adjustment: Specifies debugging for auto-bandwidth-adjustment of MPLS TE
management.
events: Specifies debugging for MPLS TE management events.
fast-reroute: Specifies debugging for fast reroute of MPLS TE management.
link-administration: Specifies debugging for link administration of MPLS TE management.
reoptimization: Specifies debugging for reoptimization of MPLS TE management.
states: Specifies debugging for MPLS TE management states.
Examples
The following examples are based on the scenario in which two directly-connected devices have been
enabled with MPLS basic capability, MPLS TE basic capability, and MPLS RESV-TE capability.
# Execute the debugging mpls te management auto-bandwidth-adjustment command. Then the two
devices establish an RSVP-TE tunnel.
<Sysname> debugging mpls te management auto-bandwidth-adjustment
*Nov 13 14:20:04:832 2006 Sysname LSPM/7/LSPM
TE AUTOBW:
Received Global AutoBw enable event.
// MPLS TE management received a global automatic bandwidth adjustment enable event.
*Nov 13 14:20:04:832 2006 Sysname LSPM/7/LSPM
TE AUTOBW:
AutoBw timer created for Tunnel : Tunnel0.
// MPLS TE management created an automatic bandwidth adjustment timer for Tunnel 0.
*Nov 13 14:20:05:740 2006 Sysname LSPM/7/LSPM
TE AUTOBW:
AutoBw Timer expired for Tunnel : Tunnel0.
// Automatic bandwidth adjustment timer for Tunnel 0 has expired.
*Nov 13 14:20:05:740 2006 Sysname LSPM/7/LSPM
TE AUTOBW:
Lsp Agt triggered to collect sample for Tunnel Tunnel0.
// LSP agent has been triggered to collect samples for Tunnel 0.
*Nov 13 14:20:05:740 2006 Sysname LSPM/7/LSPM
TE AUTOBW:
Sample collected for Tunnel : Tunnel0.
// Sample has been collected for Tunnel 0.
# Execute the debugging mpls te management events command. Then the two devices establish an
RSVP-TE tunnel.
<Sysname> debugging mpls te management events
*Nov 13 14:24:56:141 2006 Sysname LSPM/7/LSPM TE EVENTS:
Received Tunnel create event.
// MPLS TE management received a tunnel create event.
*Nov 13 14:24:56:255 2006 Sysname LSPM/7/LSPM TE EVENTS:
Cspf calculated path for Tunnel : Tunnel0 is received.
// MPLS TE management received the path calculated by CSPF for Tunnel 0.
76
*Nov 13 14:24:56:848 2006 Sysname LSPM/7/LSPM TE EVENTS:
Main Crlsp is Up for Tunnel : Tunnel0.
// The main CR-LSP for Tunnel 0 is up.
# Execute the debugging mpls te management fast-reroute command. Then the two devices establish an
RSVP-TE tunnel.
<Sysname> debugging mpls te management fast-reroute
*Nov 13 14:28:10:424 2006 Sysname LSPM/7/LSPM TE FRR:
The interface has been added for bypass tunnel (Tunnel1) to protect.
// The interface has been successfully added and is to be protected by the bypass tunnel.
# Execute the debugging mpls te management reoptimization command. Then the two devices establish
an RSVP-TE tunnel.
<Sysname> debugging mpls te management reoptimization
*Nov 13 14:31:11:674 2006 Sysname LSPM/7/LSPM TE REOPT:
Reoptimization timer created for Tunnel : Tunnel1.
// MPLS TE management created a reoptimization timer for Tunnel 1.
*Nov 13 14:31:15:586 2006 Sysname LSPM/7/LSPM TE REOPT:
Reoptimization Timer expired for Tunnel : Tunnel1.
// Reoptimization timer for Tunnel 1 has expired.
*Nov 13 14:31:15:586 2006 Sysname LSPM/7/LSPM TE REOPT:
Reoptimizing Crlsp for Tunnel : Tunnel1.
// MPLS TE management is re-optimizing CR-LSP for Tunnel 1.
*Nov 13 14:31:15:602 2006 Sysname LSPM/7/LSPM TE REOPT:
Reoptimization triggered successfully for Tunnel : Tunnel1.
// Reoptimization has been triggered successfully for Tunnel 1.
*Nov 13 14:31:15:782 2006 Sysname LSPM/7/LSPM TE REOPT:
Reoptimization timer created for Tunnel : Tunnel1.
// MPLS TE management created a reoptimization timer for Tunnel 1.
*Nov 13 14:31:15:782 2006 Sysname LSPM/7/LSPM TE REOPT:
Cspf calculated Path for reoptimization for Tunnel : Tunnel1, is not optimal.
// Path calculated by CSPF for reoptimization of Tunnel 1 is not optimal.
# Execute the debugging mpls te management states command. Then the two devices establish an
RSVP-TE tunnel.
<Sysname> debugging mpls te management states
*Nov 13 14:42:34:586 2006 Sysname LSPM/7/LSPM TE STATES:
State Change :Tunnel Tunnel1 enters USINGIDLE state.
// State change: Tunnel 1 entered the USINGIDLE state.
*Nov 13 14:42:34:586 2006 Sysname LSPM/7/LSPM TE STATES:
State Change :Tunnel Tunnel1 enters WAITFORCSPF state from a USINGIDLE state.
// State change: Tunnel 1 entered the WAITFORCSPF state from the USINGIDLE state.
*Nov 13 14:42:34:728 2006 Sysname LSPM/7/LSPM TE STATES:
State Change :Tunnel Tunnel1 enters SETUPING state from WAITFORCSPF state.
// State change: Tunnel 1 entered the SETUPING state from the WAITFORCSPF state.
[Sysname-Tunnel1]
77
*Nov 13 14:42:35:130 2006 Sysname LSPM/7/LSPM TE STATES:
State Change :Tunnel Tunnel1 enters READY state from SETUPING state.
// State change: Tunnel 1 entered the READY state from the SETUPING state.
debugging mpls te protect-switch
Use debugging mpls te protect-switch to enable debugging for protection switching.
Use undo debugging mpls te protect-switch to disable debugging for protection switching.
Syntax
debugging mpls te protect-switch { all | error | process | timer }
undo debugging mpls te protect-switch { all | error | process | timer }
Default
No protection switching debugging is enabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging.
error: Specifies debugging for errors.
process: Specifies debugging for processing.
timer: Specifies debugging for timers.
Examples
# Configure MPLS TE tunnels between two routers. Execute the debugging mpls te protect-switch all
command on the ingress router of the tunnel, and then configure a protection group. The ingress router
outputs the following debugging information:
<PE1> debugging mpls te protect-switch all
*Feb 22 16:52:53:953 2011 PE1 PSC/7/PROC: Create a PG in PSC: Instance 0, ProtectType 1,
ResvertiveModeFlag 1,SwitchMode 1, HoldOff 0, WTR 120.
// Protection switching started to create a protection group.
*Feb 22 16:52:53:953 2011 PE1 PSC/7/PROC: Real-time backup: PG 1, WTnlId 4294967295, PTnlId
4294967295, Action 0.
// Protection switching performed real-time backup for the protection group.
*Feb 22 16:52:53:953 2011 PE1 PSC/7/PROC: Add a path to PSC: Instance 0, PG 1, PathType
0, PContext 79101954.
// Protection switching added a path to the protection group.
*Feb 22 16:52:53:969 2011 PE1 PSC/7/PROC:
input event : PSC_LOCAL_EVENT_CSFW
--------before processing------------Instance: 0
PG ID: 1
State: UNAVAILABLE
78
Old event:
Working path flag: 1
Protection path flag: 1
Switch result: 0
Message: 0x0(0,0)
--------before processing-------------
// The protection group was enabled to process the event. This is the protection group's status before
processing.
*Feb 22 16:52:53:969 2011 PE1 PSC/7/PROC: Real-time back up: PG 1, WTnlId 79101954, PTnlId
4294967295, Action 1.
// Status changed. The device performed real-time backup for the protection group.
*Feb 22 16:52:53:985 2011 PE1 PSC/7/PROC:
--------after processing------------Instance: 0
PG ID: 1
State: UNAVAILABLE
Old event:
Working path flag: 0
Protection path flag: 1
Switch result: 0
Message: 0x0(0,0)
--------after processing-------------
debugging ospf mpls-te
Use debugging ospf mpls-te to enable OSPF TE debugging.
Use undo debugging ospf mpls-te to disable OSPF TE debugging.
Syntax
debugging ospf [ process-id ] mpls-te
undo debugging ospf [ process-id ] mpls-te
Default
OSPF TE debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
Usage guidelines
OSPF TE debugging displays TE LSA receiving, forming, proliferation, and update events.
If no OSPF process number is specified, TE debugging information for all OSPF processes will be output.
79
Examples
# Enable OSPF TE debugging.
<Sysname> debugging ospf mpls-te
80
MSDP debugging commands
Support for VPN instances depends on your device model.
The output description tables in this document only contain fields and messages that require an
explanation.
debugging msdp
Use debugging msdp to enable MSDP debugging.
Use undo debugging msdp to disable MSDP debugging.
Syntax
debugging msdp [ all-instance | vpn-instance vpn-instance-name ] { all | connect | event | packet |
source-active }
undo debugging msdp [ all-instance | vpn-instance vpn-instance-name ] { all | connect | event | packet
| source-active }
Default
MSDP debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all-instance: Specifies all MPLS L3VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance. The VPN instance name must be a
case-sensitive string of 1 to 31 characters and must not contain any spaces.
all: Specifies all types of MSDP debugging.
connect: Specifies debugging for MSDP peer connection resets.
event: Specifies MSDP event debugging.
packet: Specifies MSDP packet debugging.
source-active: Specifies debugging for active sources of MSDP.
Usage guidelines
If neither all-instance nor vpn-instance is specified, this command enables MSDP debugging on the
public network.
Table 1 describes output fields and messages for the debugging msdp event command.
81
Table 58 Output from the debugging msdp event command

Field

Description

(sadd, gadd)

(S, G) entry.

static RPF peer

RPF neighbor types:

E-MBGP peer

I-MBGP peer

NOT BGP peer

NOT MBGP peer
•
•
•
•
•
Static RPF peer
E-MBGP peer
I-MBGP peer
NOT BGP peer
NOT MBGP peer
Table 2 describes output fields and messages for the debugging msdp packet command.
Table 59 Output from the debugging msdp packet command

Field

SA-TLV

SA-Request TLV

SA-Response TLV

KeepAlive TLV

Notification TLV


•
•
•
•
•
Description
TLV for different types of
messages:
SA-TLV
SA-Request TLV
SA-Response TLV
KeepAlive TLV
Notification TLV
Table 3 describes output fields and messages for the debugging msdp source-active command.
Table 60 Output from the debugging msdp source-active command

Field

Description

Only one peer

Conditions for RPF check:

Peer is original RP

Peer belongs mesh-group

Static RPF peer

MSDP Peer is E-MBGP peer

Peer's AS is the next-AS to RP

MSDP Peer is I-MBGP peer

Peer is the next-hop to RP
•
•
•
•
•
•
•
•
Only one peer.
Peer is original RP.
Peer belongs mesh-group.
Static RPF peer.
MSDP Peer is E-MBGP peer.
Peer's AS is the next-AS to RP.
MSDP Peer is I-MBGP peer.
Peer is the next-hop to RP.
Examples
# Enable debugging for MSDP events on the public network. When MSDP is enabled, output similar to
the following example is generated:
<Sysname> debugging msdp event
*Aug 25 09:33:13:130 2006 ar2 MSDP/7/EVENT:
(public net):11.11.11.11: TCP listening (H12726)
// The server 11.11.11.11 started TCP listening.
*Aug 25 09:35:45:790 2006 ar2 MSDP/7/EVENT:
(public net):11.11.11.11: Connection accepted (H12850)
82
*Aug 25 09:35:45:790 2006 ar2 MSDP/7/EVENT:
(public net):11.11.11.11: TCP connection established (H12854)
// A TCP connection was established.
*Aug 25 09:35:45:790 2006 ar2 MSDP/7/EVENT:
(public net):11.11.11.11: Sending message to peer: keepalive (H101045)
// The device sent keepalive messages to the MSDP peer.
*Aug 25 09:35:45:790 2006 ar2 MSDP/7/EVENT:
(public net):11.11.11.11: Originating SA message for peer (H10859)
// The device sent SA messages (if any) to the MSDP peer.
# Enable debugging for MSDP messages on the public network. When MSDP is enabled, output similar
to the following example is generated:
<Sysname> debugging msdp packet
*Aug 25 09:39:07:162 2006 ar2 MSDP/7/PACKET:
(public net):11.11.11.11: Sending a 3-bytes message to peer (H17119)
// The device sent a three-byte message to the MSDP peer.
*Aug 25 09:39:07:162 2006 ar2 MSDP/7/PACKET:
(public net):11.11.11.11: Sending to peer success, 3-bytes sent (H17143)
// The device succeeded in sending the message to the MSDP peer.
*Aug 25 09:39:07:162 2006 ar2 MSDP/7/PACKET:
(public net):11.11.11.11: Received 3-bytes message 1 from peer (H13471)
// The MSDP peer received the three-byte message.
*Aug 25 09:39:07:162 2006 ar2 MSDP/7/PACKET:
(public net):11.11.11.11: KeepAlive TLV (H131441)
// This message is a keepalive message.
# Enable debugging for active sources of MSDP on the public network. When MSDP is enabled, output
similar to the following example is generated:
<Sysname> debugging msdp source-active
*Aug 25 09:52:08:924 2006 ar2 MSDP/7/SOURCE-ACTIVE:
(public net):11.11.11.11: Only one peer, passed RPF check (H132426)
// The SA message was received. The RPF check succeeded because only one MSDP peer exists.
83
MTR debugging commands
Enabling any debugging command in this chapter might affect system performance, especially when the
system is busy. Disable debugging after the debugging operation is complete.
debugging multiple-topology event
Use debugging multiple-topology event to enable topology event debugging.
Use undo debugging multiple-topology event to disable topology event debugging.
Syntax
debugging multiple-topology event
undo debugging multiple-topology event
Default
Topology event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Examples
# Enable topology event debugging. When you create topology voice, output similar to the following
example is generated:
<Sysname> debugging multiple-topology event
[Sysname-address-family ipv4] multiple-topology voice
*Jul 20 11:44:17:282 2009 Sysname MT/7/MTDBG: Create topol:voice
debugging multiple-topology hsb
Use debugging multiple-topology hsb to enable topology hot backup debugging.
Use undo debugging multiple-topology hsb to disable topology hot backup debugging
Syntax
debugging multiple-topology hsb
undo debugging multiple-topology hsb
Default
Topology hot backup debugging is disabled.
Views
User view
Default command level
1: Monitor level
84
Examples
# Enable topology hot backup debugging. When you create topology voice, output similar to the
following example is generated:
<Sysname> debugging multiple-topology hsb
[Sysname-address-family ipv4] multiple-topology voice
*Jul 20 11:44:17:282 2009 Sysname MT/7/MTDBG: rtbkup:send type:1's data
// MTR sent information with a backup type of create to the standby card.
85
Multicast routing and forwarding debugging
commands
Support for VPN instances depends on your device model.
The output description tables in this document only contain fields and messages that require an
explanation.
Some information in this chapter is device type specific. Devices in this chapter are categorized
depending on their IRF capability and support for interface cards that use independent processors for
forwarding traffic, as shown in Table 1.
Table 61 Device types
Device type
Distributed devices
Interface cards with
on-card processors
IRF capability
Examples
No
HP 6600 routers (except
for 6602)
Yes
Yes (in standalone mode)
Distributed IRF devices
Yes
Yes (in IRF mode)
Centralized devices
No
No
Centralized IRF devices
No
Yes
HP 12500 switches
HP 10500 switches
HP 12500 switches
HP 10500 switches
HP MSR routers
HP 6602 router
HP 5800 switches
HP 5500 switches
debugging mfib
Use debugging mfib to enable multicast forwarding information base (MFIB) debugging.
Use undo debugging mfib to disable MFIB debugging.
Syntax
Centralized devices:
debugging mfib [ all-instance | vpn-instance vpn-instance-name ] { all | { driver | no-cache | packet |
register | route | sync | upcall | wrong-iif } [ advanced-acl-number ] }
undo debugging mfib [ all-instance | vpn-instance vpn-instance-name ] { all | { driver | no-cache |
packet | register | route | sync | upcall | wrong-iif } [ advanced-acl-number ] }
Distributed devices/centralized IRF devices:
debugging mfib [ all-instance | vpn-instance vpn-instance-name ] { all | { driver | no-cache | packet |
register | route | sync | upcall | wrong-iif } [ advanced-acl-number ] } [ slot slot-number ]
86
undo debugging mfib [ all-instance | vpn-instance vpn-instance-name ] { all | { driver | no-cache |
packet | register | route | sync | upcall | wrong-iif } [ advanced-acl-number ] } [ slot slot-number ]
Distributed IRF devices:
debugging mfib [ all-instance | vpn-instance vpn-instance-name ] { all | { driver | no-cache | packet |
register | route | sync | upcall | wrong-iif } [ advanced-acl-number ] } [ chassis chassis-number slot
slot-number ]
undo debugging mfib [ all-instance | vpn-instance vpn-instance-name ] { all | { driver | no-cache |
packet | register | route | sync | upcall | wrong-iif } [ advanced-acl-number ] } [ chassis chassis-number
slot slot-number ]
Default
MFIB debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all-instance: Specifies all the MPLS L3VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name. The VPN instance
name must be a case-sensitive string of 1 to 31 characters and must not contain any spaces.
all: Specifies all types of debugging for MFIB.
driver: Specifies MFIB debugging for interface drivers.
no-cache: Specifies MFIB debugging for unknown multicast packets.
packet: Specifies MFIB packet debugging.
register: Specifies MFIB debugging for register messages.
route: Specifies MFIB route debugging.
sync: Specifies MFIB debugging for synchronization messages.
upcall: Specifies debugging for messages that MFIB reported to MRM.
wrong-iif: Specifies MFIB debugging for incoming interface (IIF) errors.
advanced-acl-number: Specifies an advanced ACL number in the range of 3000 to 3999.
slot slot-number: Specifies a card by its slot number. (Distributed devices.)
slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number
argument specifies the IRF member device ID. The slot-number argument specifies the number of the slot
where the card resides. (Distributed IRF devices.)
Usage guidelines
If neither all-instance nor vpn-instance is specified, this command enables MFIB debugging for the
public network.
Table 2 describes output fields and messages for the debugging mfib driver command.
87
Table 62 Output from the debugging mfib driver command
Field
Description
call driver
The MFIB called the driver.
Do not add to driver
The MFIB did not add the multicast forwarding entries
to the driver.
downloaded to driver Failed
The MFIB failed to issue configurations to the driver.
(sadd, gadd)
(S, G) entry.
set unknown packet to CPU
The MFIB sent unknown packets to the CPU for
process.
Table 3 describes output fields and messages for the debugging mfib no-cache command.
Table 63 Output from the debugging mfib no-cache command
Field
Description
Receive no cache report
The MFIB received an unknown multicast data packet.
No MFIB entry matches
The MFIB failed to find the matching entry.
(sadd, gadd)
(S, G) entry.
Cache the packet
The MFIB cached multicast data packets.
Table 4 describes output fields and messages for the debugging mfib packet command.
Table 64 Output from the debugging mfib packet command
Field
Description
Receive/Drop packet
The MFIB received or dropped multicast data packets.
(sadd, gadd)
(S, G) entry.
IIF
Incoming interface.
OIF
Outgoing interface.
TTL
TTL value of the message.
InPktVrf
Index number of the VPN to which the received packet
belongs.
Forward multicast packet
The MFIB forwarded multicast data packets.
DP
Data plane (supported only by multi-core devices).
control plane
Control plane (supported only by multi-core devices).
Send packet to control plane
The data plane sent multicast packets to the control
plane (supported only by multi-core devices).
Drop packet because unknown packet to cpu function
is closed
The MFIB dropped unknown packets because the
function for sending unknown packets to CPU was
disabled (supported only by multi-core devices).
Search entry in DP MFIB
The MFIB searched the data plane MFIB for correct
entries (supported only by multi-core devices).
Table 5 describes output fields and messages for the debugging mfib register command.
88
Table 65 Output from the debugging mfib register command
Field
Description
Send register
The MFIB sent a register message.
(sadd, gadd)
(S, G) entry.
Dropping received register packet
The MFIB dropped error register messages.
Table 6 describes output fields and messages for the debugging mfib route command.
Table 66 Output from the debugging mfib route command
Field
Description
add-entry message
The MFIB received an add-entry message from the
multicast routing module (MRM).
del-entry message
The MFIB received a del-entry message from MRM.
set-IIF message
The MFIB received a set-IIF message from MRM.
del-OIF message
The MFIB received a del-OIF message from MRM.
add-OIF message
The MFIB received an add-OIF message from MRM.
MRM
Multicast routing module.
The Following OIFs are added
The following outgoing interfaces were added.
(sadd, gadd)
(S, G) entry.
Add/Delete entry successfully
The data plane successfully added or deleted an entry
(supported only by multi-core devices).
Add/Delete num OIF(s)
The data plane entry successfully added or deleted
outgoing interfaces, the number of which is specified
by num (supported only by multi-core devices).
Set Switch-Group successfully
The data plane entry successfully configured
switch-group (supported only by multi-core devices).
Table 7 describes output fields and messages for the debugging mfib sync command.
Table 67 Output from the debugging mfib sync command
Field
Description
added to updated list
The MFIB added an entry to the updated list.
deleted from updated list
The MFIB deleted an entry from the updated list.
Encoded the ADD/DEL/MOD message
The MFIB encapsulated a message to
add/delete/modify an entry.
(sadd, gadd)
(S, G) entry.
Table 8 describes output fields and messages for the debugging mfib upcall command.
Table 68 Output from the debugging mfib upcall command
Field
Description
Send No cache up call
The MFIB sent a message to MRM.
89
Field
Description
(sadd, gadd)
(S, G) entry.
Table 9 describes output fields and messages for the debugging mfib wrong-iif command.
Table 69 Output from the debugging mfib wrong-iif command
Field
Description
WRONG_IF packet
The MFIB received a multicast data packet on a wrong
incoming interface.
(sadd, gadd)
(S, G) entry.
Examples
•
On multi-core devices:
# Enable MFIB packet debugging for the public network. When PIM-DM is enabled on interfaces,
output similar to the following example is generated:
<Sysname> debugging mfib packet
*Nov 12 17:25:58:202 2007 Sysname DP_MFIB/7/PACKET:
(IPv4
0): (3.4.5.6, 226.1.1.1) Receive packet from interface Ethernet1/1 in vcpu
7. (D45208)
// The MFIB received a multicast packet (3.4.5.6, 226.1.1.1) from Ethernet 1/1 on VCPU 7.
*Nov 12 17:25:58:204 2007 Sysname DP_MFIB/7/PACKET:
(IPv4
0): (3.4.5.6, 226.1.1.1) Search entry in DP MFIB. (D45263)
// The MFIB searched the data plane MFIB for the forwarding entry for the multicast packet
(3.4.5.6, 226.1.1.1).
*Nov 12 17:25:58:204 2007 Sysname DP_MFIB/7/PACKET:
(IPv4
0): (3.4.5.6, 226.1.1.1) Send packet to control plane. (D45314)
// The data plane sent the multicast packet (3.4.5.6, 226.1.1.1) to the control plane.
*Nov 12 17:25:58:204 2007 Sysname MFIB/7/MFIB PACKET:
(public net):Receive packet (3.4.5.6, 226.1.1.1), iif = Ethernet1/1, TTL = 128,
InPktVrf = 0(A08238)
// The MFIB received a public network multicast packet (3.4.5.6, 226.1.1.1) with the TTL value
of 128.
*Nov 12 17:25:58:205 2007 Sysname MFIB/7/MFIB PACKET:
(public net):No MFIB entry matches (3.4.5.6, 226.1.1.1)(A08351)
// No matching multicast forwarding entry was found.
*Nov 12 17:25:58:206 2007 Sysname MFIB/7/MFIB PACKET:
(public net):Cache the packet for (3.4.5.6, 226.1.1.1)(A082126)
// The MFIB cached the multicast packet (3.4.5.6, 226.1.1.1).
*Nov 12 17:25:58:207 2007 Sysname MFIB/7/MFIB PACKET:
(public net):Forward multicast packet (3.4.5.6, 226.1.1.1) Ethernet1/1 (A081013)
*Nov 12 17:25:58:207 2007 Sysname MFIB/7/MFIB PACKET:
(public net): Forward multicast packet (3.4.5.6, 226.1.1.1) on local
Ethernet1/1(A084106)
//The MFIB forwarded the multicast packet (3.4.5.6, 226.1.1.1) out of Ethernet 1/1.
90
# Enable MFIB route debugging for the public network. When PIM-DM is enabled on interfaces,
output similar to the following example is generated:
<Sysname> debugging mfib route
*Nov 12 17:43:01:491 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):Receive no cache report,add dummy entry (3.4.5.6, 226.1.1.1)(A07109)
*Nov 12 17:43:01:492 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):Entry (3.4.5.6, 226.1.1.1) is added to dummy list(A063866)
*Nov 12 17:43:01:492 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):The Dummy entry (3.4.5.6, 226.1.1.1) is added(A061861)
// The control plane received a multicast packet (3.4.5.6, 226.1.1.1). No forwarding entry for
the packet was found. The control plane created a dummy entry for it.
*Nov 12 17:43:01:492 2007 Sysname DP_MFIB/7/ROUTE:
(IPv4
0): (3.4.5.6, 226.1.1.1) Add entry successfully! (D44157)
// The data plane also created an entry for the multicast packet (3.4.5.6, 226.1.1.1).
*Nov 12 17:43:01:495 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):Receive add-entry message of entry (3.4.5.6, 226.1.1.1) from MRM, OIF
num is 1.(A112135)
// An add-entry message was received from the MRM for adding an entry for (3.4.5.6,
226.1.1.1) with the outgoing interface number of 1.
*Nov 12 17:43:01:495 2007 Sysname DP_MFIB/7/ROUTE:
(IPv4
0): (3.4.5.6, 226.1.1.1) Delete entry successfully! (D44246)
*Nov 12 17:43:01:496 2007 Sysname DP_MFIB/7/ROUTE:
(IPv4
0): (3.4.5.6, 226.1.1.1) Add entry successfully! (D44157)
*Nov 12 17:43:01:496 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):Entry (3.4.5.6, 226.1.1.1) is deleted from dummy list(A063908)
*Nov 12 17:43:01:497 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):The dummy entry (3.4.5.6, 226.1.1.1) is replaced by actual entry(A07407)
*Nov 12 17:43:01:497 2007 Sysname MFIB/7/MFIB ROUTE:
(public net):The entry (3.4.5.6, 226.1.1.1) is added(A0669)
// The MFIB deleted the dummy entry for (3.4.5.6, 226.1.1.1) from the data plane table and
created a forwarding entry for (3.4.5.6, 226.1.1.1).
•
On single-core devices:
# Enable MFIB driver debugging for the public network. When PIM-DM is enabled on interfaces,
output similar to the following example is generated:
<Sysname> debugging mfib driver
*Apr 26 12:53:18:967 2000 Sysname MFIB/7/MFIB DRIVER:
(public net):Succeed to set IPMC 0x0 on interface Vlan-interface20(A082415)
// Multicast routing was enabled on VLAN-interface 20.
*Apr 26 12:53:18:979 2000 Sysname MFIB/7/MFIB DRIVER:
(public net):Succeed to set unknown packet to CPU 0x3 on interface
Vlan-interface20(A082520)
// VLAN-interface 20 was configured to send unknown data packets to the CPU.
91
NOTE:
A router does not output interface driver debugging information about MFIB.
# Enable MFIB unknown packet debugging for the public network. When PIM-DM is enabled on
interfaces, output similar to the following example is generated:
<Sysname> debugging mfib no-cache
*Apr 26 12:43:19:09 2000 Sysname MFIB/7/MFIB NO-CACHE:
(public net):No MFIB entry matches (3.4.5.6, 226.1.1.1)(A08303)
*Apr 26 12:43:19:17 2000 Sysname MFIB/7/MFIB NO-CACHE:
(public net):Receive no cache report,add dummy entry (3.4.5.6, 226.1.1.1)(A07120)
*Apr 26 12:43:19:27 2000 Sysname MFIB/7/MFIB NO-CACHE:
(public net):Cache the packet for (3.4.5.6, 226.1.1.1)(A082099)
//The MFIB received a multicast packet (3.4.5.6, 226.1.1.1). No forwarding entry was found for
the packet. The MFIB created a dummy forwarding entry and cached the multicast packet.
# Enable MFIB packet debugging for the public network. When PIM-DM is enabled on interfaces,
output similar to the following example is generated:
<Sysname> debugging mfib packet
*Apr 26 12:28:50:578 2000 Sysname MFIB/7/MFIB PACKET:
(public net):Receive packet (3.4.5.6, 226.1.1.1), iif = Vlan-interface20, TTL =
128(A08204)
// The MFIB received a multicast packet (3.4.5.6, 226.1.1.1) with a TTL value of 128 on
VLAN-interface 20.
*Apr 26 12:28:50:586 2000 Sysname MFIB/7/MFIB PACKET:
(public net):No MFIB entry matches (3.4.5.6, 226.1.1.1)(A08303)
// The MFIB failed to find a matching multicast forwarding entry.
*Apr 26 12:28:50:605 2000 Sysname MFIB/7/MFIB PACKET:
(public net):Cache the packet for (3.4.5.6, 226.1.1.1)(A082099)
// The MFIB cached the multicast packet (3.4.5.6, 226.1.1.1).
*Apr 26 12:28:50:615 2000 Sysname MFIB/7/MFIB PACKET:
(public net):Forward multicast packet (3.4.5.6, 226.1.1.1) on
Vlan-interface10(A08945)
// The MFIB forwarded the multicast packet (3.4.5.6, 226.1.1.1) to VLAN-interface 10.
*Apr 26 12:28:50:625 2000 Sysname MFIB/7/MFIB PACKET:
(public net):Forward multicast packet (3.4.5.6, 226.1.1.1) at port Ethernet1/0
(A083551)
// The MFIB forwarded the multicast packet (3.4.5.6, 226.1.1.1) out of Ethernet 1/1.
# Enable MFIB debugging for register messages for the public network. The output in this example
was created when the following conditions exist:

PIM-SM is enabled on the two devices.

The RP and the BSR are configured.
<Sysname> debugging mfib register
92
*Apr 26 13:29:33:753 2000 Sysname MFIB/7/MFIB REGISTER:
(public net):Received register packet from 22.1.1.1 to 10.1.1.1, with data packet:
(22.1.1.10, 226.1.1.1)(A086218)
// The MFIB received a register message (22.1.1.1, 10.1.1.1) with the encapsulated multicast
packet (22.1.1.10, 226.1.1.1).
*Apr 26 13:29:33:763 2000 Sysname MFIB/7/MFIB REGISTER:
(public net):Send register-stop packet to 22.1.1.1 for (22.1.1.10,
226.1.1.1).(A085970)
// The MFIB sent a register-stop message for (22.1.1.10, 226.1.1.1) to 22.1.1.1.
# Enable MFIB route debugging for the public network. When PIM-DM is enabled on interfaces,
output similar to the following example is generated:
<Sysname> debugging mfib route
*Apr 26 12:39:59:272 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):Receive no cache report,add dummy entry (3.4.5.6, 226.1.1.1)(A07120)
*Apr 26 12:39:59:277 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):Entry (3.4.5.6, 226.1.1.1) is added to dummy list(A063785)
*Apr 26 12:39:59:287 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):The Dummy entry (3.4.5.6, 226.1.1.1) is added(A061784)
// The MFIB received a multicast packet (3.4.5.6, 226.1.1.1). No forwarding entry for the packet
was found. The MFIB created a dummy forwarding entry.
*Apr 26 12:39:59:297 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):Receive add-entry message of entry (3.4.5.6, 226.1.1.1) from MRM, OIF
num is 1.(A112030)
// The MFIB received an add-entry message from MRM for adding (3.4.5.6, 226.1.1.1) entry
with the outgoing interface number of 1.
*Apr 26 12:39:59:317 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):Entry (3.4.5.6, 226.1.1.1) is deleted from dummy list(A063827)
*Apr 26 12:39:59:327 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):The dummy entry (3.4.5.6, 226.1.1.1) is replaced by actual entry(A07391)
*Apr 26 12:39:59:337 2000 Sysname MFIB/7/MFIB ROUTE:
(public net):The entry (3.4.5.6, 226.1.1.1) is added(A06630)
// The MFIB deleted the dummy forwarding entry for (3.4.5.6, 226.1.1.1) and created a
forwarding entry for (3.4.5.6, 226.1.1.1).
# Enable MFIB synchronization message debugging for the public network. When PIM-DM is
enabled on interfaces, output similar to the following example is generated:
<Sysname> debugging mfib sync
*Sep
7 21:10:08:156 2006 Sysname MFIB/7/MFIB SYNC:
(public net):Entry (3.4.5.6, 226.1.1.1) is added to updated list(A063552)
// The MFIB added an entry for (3.4.5.6, 226.1.1.1) to the updated list.
# Enable debugging for packets that the MFIB reported to MRM for the public network. When
PIM-DM is enabled on interfaces, output similar to the following example is generated:
<Sysname> debugging mfib upcall
*Sep
7 21:10:08:130 2006 Sysname MFIB/7/MFIB UPCALL:
(public net):Send No cache up call (3.4.5.6, 226.1.1.1) to MRM.(A14624)
//The MFIB reported MRM about an unknown multicast packet (3.4.5.6, 226.1.1.1).
# Enable MFIB debugging for incoming interface errors for the public network. The output in this
example was created when the following conditions exist:
93


PIM-DM is enabled on VLAN-interface 40 and VLAN-interface 60.
Packets with the same multicast source address and multicast group address are sent to the two
interfaces.
<Sysname> debugging mfib wrong-iif
*Jan 24 04:36:52:990 2003 Sysname MFIB/7/MFIB WRONG-IIF:
(public net):Slot=3;WRONG_IF packet (10.11.113.168, 226.1.1.1) received on
Vlan-interface60, should from Vlan-interface40(A08734)
// The MFIB received a multicast packet (10.11.113.168, 226.1.1.1) on an incorrect incoming
interface (VLAN-interface 60). The correct incoming interface is VLAN-interface 40.
debugging mrm
Use debugging mrm to enable MRM debugging.
Use undo debugging mrm to disable MRM debugging.
Syntax
debugging mrm [ all-instance | vpn-instance vpn-instance-name ] { all | event | packet
[ advanced-acl-number ] | route [ advanced-acl-number ] }
undo debugging mrm [ all-instance | vpn-instance vpn-instance-name ] { all | event | packet | route }
Default
MRM debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
all-instance: Specifies all the MPLS L3VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name. The VPN instance
name must be a case-sensitive string of 1 to 31 characters and must not contain any spaces.
all: Specifies all types of debugging for MRM.
event: Specifies MRM event debugging.
packet: Specifies MRM packet debugging.
route: Specifies MRM route debugging.
advanced-acl-number: Specifies an advanced ACL number in the range of 3000 to 3999.
Usage guidelines
If neither all-instance nor vpn-instance is specified, this command enables MRM debugging for the
public network.
Table 10 describes output fields and messages for the debugging mrm event command.
94
Table 70 Output from the debugging mrm event command
Field
Description
(sadd, gadd)
(S, G) entry.
failed
Operation failed.
Table 11 describes output fields and messages for the debugging mrm packet command.
Table 71 Output from the debugging mrm packet command
Field
Description
Received
Received packets.
MFIB information(NOCACHE)
Types of received packets:
MFIB information(WRONGIF)
packet (protocol = 2)
•
•
•
•
•
•
•
•
•
(sadd, gadd)
(S, G) entry.
MFIB information(ACTIVE)
MFIB information(INACTIVE)
MFIB information(SPT)
MFIB information(CLEAR)
MFIB information(REG-Timeout)
Pim
MFIB information(NOCACHE)
MFIB information(WRONGIF)
MFIB information(ACTIVE)
MFIB information(INACTIVE)
MFIB information(SPT)
MFIB information(CLEAR)
MFIB information(REG-Timeout)
Pim
packet (protocol = 2)
Table 12 describes output fields and messages for the debugging mrm route command.
Table 72 Output from the debugging mrm route command
Field
Description
lost the route
A route was deleted.
a new route
A new route was added.
(sadd, gadd)
(S, G) entry.
Examples
The output in the following examples was created when PIM-SM is enabled:
# Enable MRM event debugging for the public network.
<Sysname> debugging mrm event
*0.1433697 85 MRM/7/EVENT:
(public net):Task(IGMPV3) register interest in (*,235.1.1.1)(C153622)
// An IGMP join message was received and IGMPv3 created a (*, 235.1.1.1) entry.
*0.1434697 85 MRM/7/EVENT:
(public net):Task(IGMPV3) unregistered interest in (*,235.1.1.1)(C153522)
// IGMPv3 deleted the (*, 235.1.1.1) entry 130 seconds after the host stopped sending IGMP join
messages.
# Enable MRM packet debugging on the public network.
<Sysname> debugging mrm packet
95
*0.21838588 Sysname MRM/7/PACKET:
(public net):Received MFIB information(NOCACHE) for (1.1.1.108, 235.1.1.1) with incoming
interface index 0x30f0188(C22380)
// The MRM received a multicast packet (1.1.1.108, 235.1.1.1) for an unknown group address from the
MFIB on the interface with the index number of 0x30F0188.
*0.22048588 Sysname MRM/7/PACKET:
(public net):Received MFIB information(INACTIVE) for (1.1.1.108, 235.1.1.1) (C22502)
// The multicast forwarding entry of (1.1.1.108, 235.1.1.1) transited to INACTIVE state 210 seconds after
the multicast source stopped sending data stream.
# Enable MRM route debugging on the public network.
<Sysname> debugging mrm route
*0.703622 Sysname MRM/7/ROUTE:
(public net):SG_INCLUDE: get a new route for (3.3.3.156, 225.0.0.1)(C155414)
// The MRM found a new route for the entry (3.3.3.156, 225.0.0.1).
*0.703622 Sysname MRM/7/ROUTE:
(public net):SG_INCLUDE: 100.1.1.1 is reachable, move (3.3.3.156, 225.0.0.1) include
interest from null list(C155426)
// The route to 100.1.1.1 is reachable and the record for the entry (3.3.3.156, 225.0.0.1) was moved from
the null list.
*0.21838588 Sysname MRM/7/ROUTE:
Received a creation alert for (3.3.3.156, 225.0.0.1)(C181103)
// The MRM received a creation alert for multicast forwarding entry (3.3.3.156, 225.0.0.1).
debugging mtracert
Use debugging mtracert to enable multicast traceroute debugging.
Use undo debugging mtracert to disable multicast traceroute debugging.
Syntax
debugging mtracert { all | event | packet }
undo debugging mtracert { all | event | packet }
Default
Multicast traceroute debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
all: Specifies all types of multicast traceroute debugging.
event: Specifies multicast traceroute event debugging.
packet: Specifies multicast traceroute packet debugging.
96
Usage guidelines
Table 13 describes output fields and messages for the debugging mtracert event command.
Table 73 Output from the debugging mtracert event command
Field
Description
task send buffer
Buffer for sending task.
Maxhops
Maximum number of hops.
Rttl
TTL value of the multicast traceroute packet header.
Multicast-enabled
Enable IP multicast routing.
Responder
Address of the responder.
Ip_chPr
Protocol field in the IP packet header.
Appointed response
Response address designated by the trace command.
Table 13 describes output fields and messages for the debugging mtracert packet command.
Table 74 Output from the debugging mtracert packet command
Field
Description
Error hops
Incorrect hop count (the number of hops in the IGMP
message header)
Response block number
Number of response blocks.
Examples
The output in the following examples was created when you use the mtracert command to trace the
multicast packet path on an IP multicast routing enabled device:
# Enable debugging for multicast traceroute events.
<Sysname> debugging mtracert event
*Jan 31 17:40:01:522 2007 Sysname MTRACE/7/event: Can't locate upstream neighbor for
(10.10.10.8, 225.2.1.1) in multicast routing table (FWD Code: NO_ROUTE) (M07520)
// The multicast traceroute was unable to locate the upstream neighbor for (10.10.10.8, 225.2.1.1).
# Enable debugging for multicast traceroute packets.
<Sysname> debugging mtracert packet
*Jan 31 17:36:06:221 2007 Sysname MTRACE/7/packet: Receive mtrace response packet from
7.7.7.2 (M12480)
// The multicast traceroute received a response packet from 7.7.7.2.
97
Multicast VPN debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging md
Use debugging md to enable multicast domain (MD) debugging.
Use undo debugging md to disable MD debugging.
Syntax
debugging md [ all-instance | vpn-instance vpn-instance-name ] { all | event [ advanced-acl-number ] |
packet | timer }
undo debugging md [ all-instance | vpn-instance vpn-instance-name ] { all | event | packet | timer }
Default
MD debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all-instance: Specifies all MPLS L3VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name. The VPN instance
name must be a case-sensitive string of 1 to 31 characters and must not contain any spaces.
all: Specifies all types of MD debugging.
event: Specifies MD event debugging.
advanced-acl-number: Specifies an advanced ACL number in the range of 3000 to 3999.
packet: Specifies MD packet debugging.
timer: Specifies MD timer debugging.
Usage guidelines
If neither all-instance nor vpn-instance is specified, this command enables MD debugging on the public
network.
If a debugging option is enabled for all VPN instances, that debugging option is automatically enabled
for VPN instances created afterwards.
Table 1 describes output fields and messages for the debugging md event command.
98
Table 75 Output from the debugging md event command
Field
Description
local MDT info
Local MDT route information.
sender
Sender of the MDT switching notification.
source list
List of senders of MDT switching notifications.
Pending node
Node with a pending join.
Join Pending Job
Job that processes a pending join.
switch receive table
Table was created after a switching notification message was
received. The table is used for storing switch-group addresses and
information about switching notification senders, including the
switch group and initiator addresses.
Join Notification
A join notification.
SR
Switch receive module.
Source-MDT
The Source-MDT is the same as the switch-MDT.
UP/DOWN event
Above-threshold/below-threshold event.
SS walk
All (S, G) entries in the specified instance are examined in the
switch-MDT switching threshold and ACL rule configuration.
PD
Public MD module.
SD_QueryShareGroup
Share-group query function.
PD_JoinGroup
Group join function.
Resume Source-MDT state
MD reset the switch-MDT state.
Allocate Switch-Group
MD allocated a switch-group address.
Recycle Switch-Group
MD recycled the switch-group address. After this operation, traffic
will not be forwarded by using the switch-MDT. The switch-group
configuration remains the same.
Release Switch-Group
MD released the switch-group and deleted the switch-group
configuration.
SS_SWITCH_INITIAL
This (S, G) entry has just been created.
SS_SWITCH_DELAY
This (S, G) entry is in switch-delay state.
SS_SWITCH_HOLDDOWN
This (S, G) entry is in switch-holddown state.
SS_SWITCH_NORMAL
This (S, G) entry is in switch-normal state.
SS_HOLDOWNBYCLEAR
This (S, G) entry is in switch-holddown state because the reset
command was executed.
SS_UNKNOWN
This (S, G) entry is in unknown state.
Switch-Send timer
Timer for sending MDT switching notification.
Switch-Delay state
The traffic was being forwarded by using the share-MDT. When the
MDT switching conditions were met, the traffic switched to the
switch-MDT.
Switch-Holdown state
The traffic was being forwarded by using the switch-MDT. If the MDT
switching conditions were no longer met, the traffic switched back to
the share-MDT.
99
Field
Description
SwitchReceiverTimer
Timer for receiving MDT switching notification.
IFC_ADD event
Interface adding event.
IFC_UP event
Interface up event.
IFC_DELETE event
Interface deletion event.
Table 2 describes output fields and messages for the debugging md packet command.
Table 76 Output from the debugging md packet command
Field
Description
Switch notification message
MDT switching notification message.
Table 3 describes output fields and messages for the debugging md timer command.
Table 77 Output from the debugging md timer command
Field
Description
Query-MTI-Address timer
MTI address query timer.
BGP Addr
Obtained BGP address. The MTI address is consistent
with this address.
Examples
# Enable MD event debugging for VPN instance mvpn. Output similar to the following example is
generated under the following conditions:
•
A share-group with the group address of 225.1.2.3 is created.
•
MTI0 is associated with the VPN instance mvpn.
<Sysname> debugging md vpn-instance mvpn event
*Jun 16 08:09:24:452 2008 Sysname MD/7/MD:(mvpn): MD Task created successfuly for
InstanceID 1(M04790)
*Jun 16 08:09:24:453 2008 Sysname MD/7/MD:(mvpn): IFC_ADD event is received for
MTunnel0(M041115)
// An MD task was successfully created and an IFC_ADD event for MTI interface 0 was received.
*Jun 16 08:09:24:472 2008 Sysname MD/7/MD:(mvpn): Share-Group 225.1.2.3 is added
successfully for Instance mvpn(M04177)
*Jun 16 08:09:24:472 2008 Sysname MD/7/MD:(mvpn): Notifying MD enable for Instance 1 to
BGP(M04253)
*Jun 16 08:09:24:512 2008 Sysname MD/7/MD:(mvpn): Interface MTunnel0 is added successfuly
in Instance mvpn(M041194)
// MD successfully created the share-group in VPN instance mvpn and bound the MTI to the VPN
instance. The VPN instance sent a notification that MD was enabled in the VPN instance to BGP.
*Jun 16 08:09:24:512 2008 Sysname MD/7/MD:(mvpn): IFC_ADD event is received for MTunnel0
for Instance 1(M041261)
*Jun 16 08:09:24:573 2008 Sysname MD/7/MD:(mvpn): IFC_UP event is received for MTunnel0
for Instance 1(M041299)
*Jun 16 08:09:24:574 2008 Sysname MD/7/MD:(mvpn): Notifying add local MDT info (225.1.2.3,
12.34.56.78) for Instance 1 to BGP(M041319)
100
// After MTI got up, an up event was received. BGP was informed to add local MDT routing information.
*Jun 16 08:21:50:706 2008 Sysname MD/7/MD:(mvpn): Send Join Group 225.1.2.3 to PD for
InstanceID 1(M04882)
*Jun 16 08:21:50:706 2008 Sysname MD/7/MD:(mvpn): Socket initialization is successful for
MTunnel0(12.34.56.78)(M04661)
*Jun 16 08:21:50:707 2008 Sysname MD/7/MD:(mvpn): PIM Initialization on MTI is done
successfuly for Instance 1(M04922)
// PIM-enabled interfaces exist in the VPN instance. The VPN instance sent a join notification to the
public network for joining the share-group, and the same PIM mode was initialized on all the MTI
interfaces.
# Enable MD packet debugging for VPN instance mvpn. When a remote PE device initiates an MDT
switchover, output similar to the following example is generated:
<Sysname> debugging md vpn-instance mvpn packet
*Mar 12 17:28:21:709 2007 Sysname MD/7/MD:(mvpn): Number of MD TLV received is 1(M03197)
*Mar 12 17:28:21:814 2007 Sysname MD/7/MD:(mvpn): (10.21.21.3, 235.4.5.6) entry exists
in the PIM MRT (M03443)
*Mar 12 17:28:21:953 2007 Sysname MD/7/MD:(mvpn): Refresh Time for 226.4.5.0 switch group
& sender 22.22.22.22(M03562)
*Mar 12 17:28:22:103 2007 Sysname MD/7/MD:(mvpn): Switch message processed
successfully(M03644)
// MD received a MDT switching notification message from a remote PE. The locally attached PE
received the packet (10.21.21.3, 235.4.5.6), and the local device refreshed the switching receiving timer.
# Enable MD timer debugging for VPN instance mvpn. When the MTI address query timer expires,
output similar to the following example is generated:
<Sysname> debugging md vpn-instance mvpn timer
*Mar 12 17:29:50:428 2007 Sysname MD/7/MD:Query-MTI-Address timer expires(M042864)
*Mar 12 17:29:50:524 2007 Sysname MD/7/MD:Result: 0, BGP Addr: 11.11.11.11(M042881)
*Mar 12 17:29:55:428 2007 Sysname MD/7/MD:Query-MTI-Address timer expires(M042864)
*Mar 12 17:29:55:524 2007 Sysname MD/7/MD:Result: 0, BGP Addr: 11.11.11.11(M042881)
// When the MTI address query timer (set to 5 seconds) expired, the MTI address was automatically
refreshed to keep consistent with the obtained BGP address.
debugging mtunnel
Use debugging mtunnel to enable multicast tunnel debugging.
Use undo debugging mtunnel to disable multicast tunnel debugging.
Syntax
debugging mtunnel { all | error | event | ipc | management | packet }
undo debugging mtunnel { all | error | event | ipc | management | packet }
Default
Multicast tunnel debugging is disabled.
Views
User view
101
Default command level
1: Monitor level
Parameters
all: Specifies all types of multicast tunnel debugging.
error: Specifies multicast tunnel error debugging.
event: Specifies multicast tunnel event debugging.
ipc: Specifies multicast tunnel IPC message debugging.
management: Specifies multicast tunnel management debugging.
packet: Specifies multicast tunnel packet debugging.
Usage guidelines
Table 4 describes output fields and messages for the debugging mtunnel error command.
Table 78 Output from the debugging mtunnel error command
Field
Description
The interface index is invalid
The MTI index is invalid.
Get-LinkCB is failed
The multicast tunnel failed to obtain the MT link-layer control
block.
pstMTunnel is NULL
The link-layer control block pointer obtained through the MTI
index is null.
pData is NULL
The function input parameter pointer is null.
pPhyInfo is NULL
The physical statistics memory pointer of MT is null.
The PhyInfo is too large
The amount of statistics data to be output exceeded the buffer
size.
The parameter is NULL
The set interface parameter pointer is null.
The pulDrvContext is NULL
The memory address for obtaining the DrvContext value is null.
prepare Drv-block is failed
The multicast tunnel failed to request memory for driver data.
send to DRV is failed
The multicast tunnel failed to deliver driver.
MTunnel_ReceivePacket is NULL
Packet pointer received by the MT is null.
Preparing MTunnelCB is failed
The multicast tunnel failed to request memory for MTI link-layer
data blocks.
Preparing PhyInfo-block is failed
The multicast tunnel failed to request memory for MTI physical
statistics data blocks.
Get default Mtunnel mode is failed
The multicast tunnel failed to obtain the MT default mode.
Init MtunnelCB is failed
The multicast tunnel failed to initialize the MT link-layer data
block.
The packet is NULL
The packet pointer is null.
Can't get MTunnel PhyInfo Ptr
The multicast tunnel failed to obtain the MT physical statistics data
block.
Table 5 describes output fields and messages for the debugging mtunnel event command.
102
Table 79 Output from the debugging mtunnel event command
Field
Description
The block chain is NULL
The global chain of MT data block is null.
SplImp is failed
The multicast tunnel failed to disable interruption.
the DrvContext[0] is 0x
DrvContext[0] value of the MPU.
the DrvContext[1] is 0x
DrvContext[1] value of the MPU.
the DrvContext[0] from DRV is 0x
DrvContext[0] value the MPU obtained from the
driver.
the DrvContext[1] from DRV is 0x
DrvContext[1] value the MPU obtained from the
driver.
the IO-DrvContext[0] from mainboard is 0x
DrvContext[0] value the IO card obtained from the
MPU.
the IO-DrvContext[1] from mainboard is 0x
DrvContext[1] value the IO card obtained from the
MPU.
the IO-DrvContext[0] from IOboard is 0x
DrvContext[0] value of the IO card.
the IO-DrvContext[1] from IOboard is 0x
DrvContext[1] value of the IO card.
the IO-DrvContext[0] from DRV is 0x
DrvContext[0] value the IO card obtained from the
driver.
the IO-DrvContext[1] from DRV is 0x
DrvContext[1] value the IO card obtained from the
driver.
Deleted link CB(if index = 0x%X)
The MT link-layer control block was successfully
deleted. (MTI index = 0x%X)
The MTunnel is not found
The MTI to be deleted was not found.
the MsgRPC_CMD, send to No.1 board, is 0x%X
Value of the RPC message sent to IO card 1.
the MsgRPC_CMD, Broadcast to IO board, is 0x%X
Value of the RPC message broadcast to all IO cards.
No.1 board, the Recive-MsgRPC_CMD is 0x%X
Value of the RPC message received on IO card 1.
No.1 board , the IO-Drv-CMD from mainboard is
0x%X
Value of driver context that IO card 1 received from
the MPU.
Table 6 describes output fields and messages for the debugging mtunnel ipc command.
Table 80 Output from the debugging mtunnel ipc command
Field
Description
Recive-Msg is NULL
The received IPC message is null.
The length of receive-Msg is wrong
The size of the received IPC message is incorrect.
the MsgRPC_CMD, Send to No.1 Failed(Revlen
error), is 0x%X
RPC communication with board 1 failed (incorrect
length received). The command word is 0x%X.
the MsgRPC_CMD, Send to No.1 timeout, is 0x%X
RPC communication with board 1 failed (command
timed out). The command word is 0x%X.
Alloc IPC_RPC_MSG error
RPC communication failed (memory allocation error).
Table 7 describes output fields and messages for the debugging mtunnel management command.
103
Table 81 Output from the debugging mtunnel management command
Field
Description
Can't get MTunnel src addr
The MTI source address cannot be obtained.
MTunnel src addr is invalid
The obtained MTI source address is invalid (0).
Can't get MTunnel dest address
The group IP address of the MTI cannot be obtained.
MTunnel dest addr is invalid
The obtained group IP address of the MTI is invalid (0).
The MTunnel has been
MT state: Up or down.
MTunnel Src addr
MTI source address.
Set MTunnel Src addr
A MTI source address was set.
Set MTunnel group addr
A MTI group address was set.
Table 8 describes output fields and messages for the debugging mtunnel packet command.
Table 82 Output from the debugging mtunnel packet command
Field
Description
The packet length is too short
Insufficient packet length.
Memory-continous is failed
The multicast tunnel failed to defragment data in the
MBUF.
pIp is NULL
The packet IP header address is null.
pstMGRE-Head is NULL
The packet GRE header address is null.
resv0 field error
The reserved 0 field of the GRE header is not 0.
check-sum error
Packet checksum result error.
version field error
The version field of the packet GRE header is not 0.
protocol field known
The packet payload is non-IPv4.
Decapsulate successfully
Packet was successfully de-encapsulated.
Payload is IP data
The VPN packet payload is IP data.
Payload is not IP data
The VPN packet payload is not IP data.
ADD GRE-head is failed
The multicast tunnel failed to add GRE header to
packet.
ADD IP-head is failed
The multicast tunnel failed to add IP header to packet.
Can't get mtunnel source address
The MTI source address cannot be obtained.
Src addr
MTI source address for packet was successfully
encapsulated.
Can't get mtunnel destination address
The MTI group IP address cannot be obtained.
Grp addr
The default group IP address of the MTI is being used.
Switch-Grp addr
The switch-group address of the MTI is being used.
MTunnel is not up
The MT to forward packets is not up.
The MTunnelMode-LLCoutput is NULL
The transmission function corresponding to the MT
mode to forward the multicast packet is null.
104
Examples
A multicast tunnel interface (MTI) is a global interface. Unless otherwise stated, all examples in this
section are based on centralized devices.
# Enable multicast tunnel error debugging. Output similar to the following example is generated when
an IPv4 packet of another multicast tunnel is sent under the following conditions:
•
A multicast tunnel is created between two PE devices.
•
The tunnel parameters are configured at both ends to bring the tunnel interface up.
<Sysname> debugging mtunnel error
*Jan 23 16:30:17:06 2007 Sysname MTUNNEL/7/debug:
mtunnel_error: Can't get MTunnel PhyInfo Ptr.
// The multicast tunnel failed to obtain the physical statistics data block of the multicast tunnel interface.
# Enable multicast tunnel event debugging. Output similar to the following example is generated when
a multicast tunnel is removed under the following conditions:
•
The multicast tunnel is created between two PE devices
•
Interrupts fail to be disabled when the multicast tunnel is removed.
<Sysname> debugging mtunnel event
*Jan 23 16:30:17:06 2007 Sysname MTUNNEL/7/debug:
mtunnel_event: SplImp is failed..
// The multicast tunnel failed to disable interrupts.
# Enable multicast tunnel management debugging. Output similar to the following example is generated
under the following conditions:
•
A multicast tunnel interface is created.
•
The multicast tunnel group address is set to 235.0.0.1.
<Sysname> debugging mtunnel management
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mtunnel_management: Set MTunnel group addr=235.0.0.1.
// The multicast tunnel set the multicast tunnel interface group address to 235.0.0.1.
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mtunnel_management: Set MTunnel Src addr=11.11.11.11.
// The multicast tunnel set the multicast tunnel interface source address to 11.11.11.11.
*Jan 23 15:52:55:18 2007 DUT1 MTUNNEL/7/debug:
mtunnel_management: The MTunnel has been UP, no change.
// The link state of the multicast tunnel interface was up without any change.
# Enable multicast tunnel packet debugging. Output similar to the following example is generated under
the following conditions:
•
A multicast tunnel interface is created, with the default group address 235.0.0.1 and the source
address 11.11.11.11.
•
The MD is configured.
•
The MD protocol is enabled to start protocol packet exchange.
<Sysname> debugging mtunnel packet
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mgre_encapsulate: Payload is IP data.
// The packet that entered the multicast tunnel is an IP packet.
105
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mgre_encapsulate: Src addr 11.11.11.11.
// The multicast tunnel source address 11.11.11.11 is used for packet encapsulation.
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mgre_encapsulate: Grp addr 235.0.0.1.
// The default group IP address 235.0.0.1 of the multicast tunnel is used for packet encapsulation.
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mgre_encapsulate: Encapsulate successfully.
// The packet was successfully encapsulated.
*Jan 23 15:52:15:02 2007 Sysname MTUNNEL/7/debug:
mgre_Decaps: Decapsulate successfully.
// The packet was successfully decapsulated.
# Enable multicast tunnel IPC message debugging. When a multicast tunnel is created between two
distributed PE devices, output similar to the following example is generated:
<Sysname> debugging mtunnel ipc
*Apr 10 14:25:04:106 2007 PE1 MTUNNEL/7/debug:
mtunnel_ipc: No.1 board, the Recive-Msg length of recive-Msg is wrong.
// The RPC message received from interface board 1 has an incorrect length.
106
MVRP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging mvrp error
Use debugging mvrp error to enable MVRP error debugging.
Use undo debugging mvrp error to disable MVRP debugging.
Syntax
debugging mvrp error
undo debugging mvrp error
Default
MVRP error debugging is disabled.
Views
Use view
Default command level
1: Monitor level
Examples
# Enable MVRP error debugging.
<Sysname> debugging mvrp error
*Mar 30 14:22:21:15 2011 Sysname MVRP/7/MVRP_DEBUG:
ERROR: Failed to send IPC message to slot ID 0x1.
// MVRP failed to send IPC messages to slot 1.
debugging mvrp event
Use debugging mvrp event to enable MVRP event debugging.
Use undo debugging mvrp event to disable MVRP event debugging.
Syntax
debugging mvrp event
undo debugging mvrp event
Default
MVRP event debugging is disabled.
Views
User view
Default command level
1: Monitor level
107
Examples
# Enable MVRP event debugging.
<Sysname> debugging mvrp event
*Mar 31 17:49:26:219 2011 Sysname MVRP/7/MVRP_DEBUG: EVENT:
VLAN list successfully created when the OP timed out.
*Mar 31 17:49:26:219 2011 Sysname MVRP/7/MVRP_DEBUG: EVENT:
VLAN list added to the trunk port.
// Creating VLAN 10 on the remote interface triggered the process of adding the VLAN list on the local
interface to the trunk port.
debugging mvrp packet
Use debugging mvrp packet to enable MVRP packet debugging on an interface.
Use undo debugging mvrp packet to disable MVRP packet debugging on an interface.
Syntax
debugging mvrp packet { send | receive } interface interface-type interface-number
undo debugging mvrp packet { send | receive } interface interface-type interface-number
Default
MVRP packet debugging is disabled on an interface.
Views
User view
Default command level
1: Monitor level
Parameters
send: Specifies debugging for sent MVRP packets.
receive: Specifies debugging for received MVRP packets.
interface interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 1 describes output fields and messages for the debugging mvrp packet command.
Table 83 Output from the debugging mvrp packet command
Field
Description
VLAN state:
•
•
•
•
•
VLAN Attribute
New—Declared and maybe not registered.
JoinIn—Declared and registered.
In—Not declared but registered.
JoinEmpty—Declared but not registered.
Empty—Not declared or registered.
VLAN ID in the range of the minimum VLAN ID to the
maximum VLAN ID that the system supports.
VLAN ID
108
Examples
# Enable debugging for sent MVRP packets on Ethernet 1/1.
<Sysname> debugging mvrp packet send interface ethernet 1/1
*Mar 31 17:23:59:860 2011 Sysname MVRP/7/MVRP_DEBUG: PACKET.Ethernet1/1.TX:
// MVRP sent packets through Ethernet 1/1.
VLAN Attribute = JoinIn, VLAN ID = 1.
// The VLAN ID was 1 and the attribute value was JoinIn.
debugging mvrp state
Use debugging mvrp state interface to enable MVRP state debugging for a VLAN on an interface.
Use undo debugging mvrp state to restore the default.
Syntax
debugging mvrp state interface interface-type interface-number vlan vlan-id
undo debugging mvrp state interface interface-type interface-number vlan vlan-id
Default
MVRP state debugging is disabled on an interface.
Views
User view
Default command level
1: Monitor level
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 2 describes output fields and messages for the debugging mvrp state command.
Table 84 Output from the debugging mvrp state command
Field
Description
AtrID
VLAN attribute ID, in the range of the minimum VLAN
ID to the maximum VLAN ID that the system supports.
109
Field
Description
Application state machine, which indicates the state of
the attribute that the local participant declares to the
remote participant. The state can be VO, VP, VN, AN,
AA, QA, LA, AO, QO, AP, QP, or LO. Each state
consists of two letters.
The first letter indicates the state:
•
•
•
•
APP
V—Very anxious.
A—Anxious.
Q—Quiet.
L—Leaving.
The second letter indicates the membership state:
•
•
•
•
A—Active member.
P—Passive member.
O—Observer.
N—New.
For example, VP indicates "Very anxious, Passive
member."
Registration state machine of the attribute declared by
remote participants on the local participant. The state
can be:
• IN—Registered.
• LV—Previously registered, but now being
Reg
unregistered.
• MT—Not registered.
110
Field
Description
Event that triggers state machine transitions.
The application state machines include:
• Begin!—The state machine is initialized.
• New!—MRP requests the local participant to
declare this attribute, and the tcDetected timer of
the instance on the local participant is not 0.
• Join!—MRP requests the local participant to
declare this attribute.
• Lv!—MRP requests the local participant to
deregister this attribute.
• rNew!—The local participant receives a New
message.
• rJoinIn!—The local participant receives a JoinIn
message that the peer participant has registered.
• rIn!—The local participant receives an In message
that the peer participant has registered, but not
declared.
• rJoinMt!—The local participant receives a JoinMt
message that the peer participant has not
registered.
• rMt!—The local participant receives an Mt
message that the peer participant has not
registered or declared.
• rLv!—The local participant receives a Leave
message.
• rLA!—The local participant receives a LeaveAll
message.
• Re-declare!—When the MSTP port changes from a
Desi port to a Root or Alte port, the process of
re-declaring all MVRP attributes is triggered.
• periodic!—The Periodic timer expires.
• tx!—A packet ending timing is generated, and no
Event
LeaveAll event exists.
• txLA!—A packet sending timing is generated, and
the LeaveAll flag is set.
• txLAF!—A packet sending timing is generated, the
LeaveAll flag is set, and the PDU message is full.
The registration state machines include:
• Begin!—The state machine is initialized.
• rNew!—The local participant receives a New
message.
• rJoinIn!—The local participant receives a JoinIn
message that the peer participant has registered.
• rJoinMt!—The local participant receives a JoinMt
message that the peer participant has not
registered.
• rLv!—The local participant receives a Leave
message.
• rLA!—The local participant receives a LeaveAll
message.
111
• txLA!—A packet sending timing is generated, and
the LeaveAll flag is set.
• Re-declare!—When the MSTP port changes from a
Desi port to a Root or Alte port, the process of
re-declaring all MVRP attributes is triggered.
Field
Description
LeaveAll
LeaveAll flag. This field is displayed only when the flag
is true.
Examples
# Enable MVRP state debugging for VLAN 2 on Ethernet 1/1.
<Sysname> debugging mvrp state interface ethernet 1/1 vlan 2
*Mar 31 17:52:58:875 2011 Sysname MVRP/7/MVRP_DEBUG: FSM:
Ethernet1/1: AtrID = 2: APP = VO Reg = IN, Event = rJoinMt!.
// The application state machine was VO, the registration state machine was IN, and the event was
rJoinMt!.
*Mar 31 17:52:58:938 2011 Sysname MVRP/7/MVRP_DEBUG: FSM:
Ethernet1/1: AtrID = 2: APP = LO Reg = LV, Event = rLA!, LeaveAll = TRUE.
// The application state machine was LO, the registration state machine was LV, the event was rLA!, and
the LeaveAll flag was TRUE.
112
NAT debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging nat
Use debugging nat to enable NAT debugging.
Use undo debugging nat to disable NAT debugging.
Syntax
debugging nat { alg | event | packet } [ interface interface-type interface-number ]
undo debugging nat { alg | event | packet } [ interface interface-type interface-number ]
Default
NAT debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
alg: Specifies ALG debugging. Support for this keyword depends on the device model.
event: Specifies event debugging.
packet: Specifies packet debugging.
interface interface-type interface-number: Specifies NAT packet debugging for a specified interface.
Usage guidelines
Table 1 describes output fields and messages for the debugging nat alg command.
Table 85 Output from the debugging nat alg command
Field
Description
Ftp Packet To Svr
NAT ALG processes FTP packets sent to the server.
(interface-type interface-number-out :)
The outbound packet is serviced by NAT on interface
interface-type interface-number.
Find a Normal Ftp CMD
ALG received a normal FTP command.
Ftp Packet To Client
NAT ALG processes FTP packets sent to the client.
(interface-type interface-number-in :)
The inbound packet is serviced by NAT on interface
interface-type interface-number.
113
Field
Description
The IP address in the type A DNS reply has been translated.
DNS A answer is translated successfully by
dns-map(address1 -> address2).
• address1—The IP address before translation.
• address2—The IP address after translation.
Table 2 describes output fields and messages for the debugging nat event command.
Table 86 Output from the debugging nat event command
Field
Description
The packet can't translate by static.
Static address translation failed.
(interface-index-out)
The outbound packet is serviced by NAT on interface
interface-index.
(interface-index-in)
The inbound packet is serviced by NAT on interface
interface-index.
Ftp Packet To Svr
Processes FTP packets sent to the server using NAT ALG.
Translate Ftp PORT CMD fail
FTP port address translation failed.
Table 3 describes output fields and messages for the debugging nat packet command.
Table 87 Output from the debugging nat packet command
Field
Description
from VPN : vpn index
VPN index of the outbound packet (not displayed if no VPN
exists).
is from NAT static
The outbound packet is translated by using static NAT.
Before address translation:
( inside-source-ip: port1 global-destination-ip: port2) ------>
•
•
•
•
inside-source-ip—Source IP address.
port1—Source port number.
global-destination-ip—Public destination IP address.
port2—Destination port number.
After address translation:
(
global-source-ip: port1 global-destination-ip: port2)
•
•
•
•
global-source-ip—Source IP address.
port1—Source port number.
global-destination-ip—Public destination IP address.
port2—Destination port number.
to VPN : vpn index
VPN index of the inbound packet (not displayed if no VPN
exists).
is to NAT server
The inbound packet is translated by using the NAT Server
feature.
is to NAT static
The inbound packet is translated by using static NAT.
114
Field
Description
Before address translation:
•
•
•
•
( global-source-ip: port1 global-destination-ip: port2) ------>
global-source-ip—Source IP address.
port1—Source port number.
global-destination-ip—Public destination IP address.
port2—Destination port number.
After address translation:
•
•
•
•
(
global-source-ip: port1 inside-destination-ip: port2)
global-source-ip—Source IP address.
port1—Source port number.
inside-destination-ip—Destination IP address.
port2—Destination port number.
Examples
# Enable NAT ALG debugging on the NAT device. When internal host 192.168.0.210 uses FTP to access
public host 2.2.2.2, output similar to the following example is generated:
<Sysname> debugging nat alg
*Apr 26 12:05:36:881 2010 Sysname NAT/7/debug:Ftp Packet To Svr (Ethernet1/1-out :) Find
a Normal Ftp CMD
// NAT used ALG to translate the address in the outgoing FTP packet sent to the server on Ethernet 1/1.
*Apr 26 12:05:36:952 2010 Sysname NAT/7/debug: Ftp Packet To Client
(Ethernet1/1-in :)
Find a Normal Ftp CMD
// NAT used ALG to translate the address in the incoming FTP packet sent to the client on Ethernet 1/1.
# Enable NAT event debugging on the NAT device. Output similar to the following example is generated
when internal host 192.168.0.210 sends a packet to public host 2.2.2.2 under the condition that no
matching static NAT entry exists:
<Sysname> debugging nat event
*Apr 26 12:05:37:33 2010 Sysname NAT/7/debug: "NAT_EVENT:(0x00001234-out)The packet can't
translate by static.
// NAT failed to perform static address translation for the packet on interface 0x00001234.
# Enable NAT packet debugging on the NAT device. Output similar to the following example is
generated when internal host 192.168.0.210 in VPN 10 pings public host 2.2.2.2 under the condition
that a matching static NAT entry is configured:
<Sysname> debugging nat packet
*Apr 26 12:04:37:134 2010 Sysname NAT/7/debug:
(Ethernet1/1-out :) from VPN : 10 Pro : ICMP is from NAT static
(
(
192.168.0.210:
--- -
2.2.2.10:--- -
2.2.2.2:
2.2.2.2:
---) ------>
---)
// NAT translated the source IP address of the outgoing packet on Ethernet 1/1 by using the static NAT
entry.
*Apr 26 12:04:37:134 2010 Sysname NAT/7/debug:
(Ethernet1/1-in
:)Pro : ICMP is to NAT static
(
2.2.2.2:
--- -
(
2.2.2.2:
--- -
2.2.2.10:---) ------>
192.168.0.210:
---)
// NAT translated the destination IP address of the incoming packet on Ethernet 1/1 by using the static
NAT entry.
115
debugging userlog nat
Use debugging userlog nat to enable NAT logging debugging.
Use undo debugging userlog nat to disabled NAT logging debugging.
Syntax
debugging userlog nat
undo debugging userlog nat
Default
NAT logging debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
NOTE:
Support for this command depends on the device model.
Table 4 describes output fields and messages for the debugging userlog nat command.
Table 88 Output from the debugging userlog nat command
Field
Description
The NAT logging function does not function correctly
because either of the following reasons:
• No log server is specified on the device.
• The device is not configured to send logs to the
Export-host address or syslog not configured.
information center.
The log information is output in UDP packets.
The system is forced to output a certain number of NAT
logs when the number of NAT logs exceeds 250000.
Forced to output NAT logs.
Examples
# Enable NAT logging debugging on the NAT device. When NAT logging is enabled but no log server
is specified on the device, output similar to the following example is generated:
<Sysname> debugging userlog nat
*Dec 6 15:36:38:956 2010 Sysname S8505 USERLOG/8/NAT:Slot=3;
Export-host address or syslog is not configured.
// No log server is configured or the device is not configured to send logs to the information center.
# Enable NAT logging debugging on the NAT device. Output similar to the following example is
generated under the conditions that NAT logging is enabled and a log server is specified:
<Sysname> debugging userlog nat
*Dec 6 15:36:39:03 2010 Sysname S8505 USERLOG/8/NAT:Slot=3;
Exporting a UDP packet with 2 logs from slot 3.
116
// NAT logs were output in UDP packets from slot 3 to the log server. One UDP packet carried two NAT
logs.
*Dec 6 15:36:39:54 2010 Sysname S8505 USERLOG/8/NAT:Slot=3;
Forced to output NAT logs.
// The system was forced to output NAT logs because the NAT log buffer was full.
117
NAT-PT debugging commands
debugging natpt
Use debugging natpt to enable NAT-PT debugging.
Use undo debugging natpt to disable NAT-PT debugging.
Syntax
debugging natpt { alg | all | event | packet } [ interface interface-type interface-number ]
undo debugging natpt { alg | all | event | packet } [ interface interface-type interface-number ]
Default
NAT-PT debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
alg: Specifies the application layer gateway (ALG) debugging.
all: Specifies all types of debugging.
event: Specifies the event debugging.
packet: Specifies the packet debugging.
interface interface-type interface-number: Specifies an interface by its type and number.
Examples
Figure 1 Network diagram
natpt address-group 1 5.1.1.1 5.1.1.20
natpt prefix 1001::
natpt v6bound dynamic prefix 1001:: address-group 1 no-pat
interface Ethernet1/2
ip address 3.3.3.2 255.255.255.0
natpt enable
interface Ethernet1/1
ipv6 address 1000::2 64
natpt enable
IPv4 network
Eth1/1
1000::2/64
Eth1/2
3.3.3.2/24
IPv4 host
IPv6 host
Device
3.3.3.1/24
•
IPv6 network
1000::1/64
On single-core devices:
118
# Enable NAT-PT packet debugging on the NAT-PT device. When the IPv6 host uses FTP to access
the IPv4 host, output similar to the following example is generated:
<Sysname> debugging natpt packet
*0.1150141 Sysname NATPT/7/debug:
Pro : TCP
TTL : 127
V6 Pkt Translated to V4 Pkt
(1000::0001 :
(5.1.1.1 :
1041 - 1001::0303:0301 :
1041 - 3.3.3.1 :
21)
21)
// NAT-PT translated the source and destination IPv6 addresses in the received IPv6 TCP packet
into IPv4 addresses.
*0.1150141 Sysname NATPT/7/debug:
Pro : TCP
TTL : 254
V4 Pkt Translated to V6 Pkt
(3.3.3.1 :
21 - 5.1.1.1 :
(1001::0303:0301 :
1041)
21 - 1000::0001 :
1041)
// NAT-PT translated the source and destination IPv4 addresses in the received IPv4 TCP packet
into IPv6 addresses.
# Enable NAT-PT event debugging on the NAT-PT device. When the device receives an IPv4
packet, but no matching NAT-PT entry exists for the destination IPv4 address, output similar to the
following example is generated:
<Sysname> debugging natpt event
*0.478281 Sysname NATPT/7/debug:
Mapping does not exist for the v4 destination address 111.255.255.255
// NAT-PT found no NAT-PT entry for IP address 111.255.255.255.
*0.478281 Sysname NATPT/7/debug:
The v4 pkt is not intended for NATPT. Returning the pkt back to V4 stack
// NAT-PT sent the IPv4 packet back to the IPv4 protocol stack because the packet was not
intended for NAT-PT.
# Enable NAT-PT event debugging on the NAT-PT device. When the device receives an IPv6
packet, but no matching IPv6 prefix exists for the destination IPv6 address, output similar to the
following example is generated:
<Sysname> debugging natpt event
*0.825484 Sysname NATPT/7/debug:
V6 dest addr does not contain configured prefix
// NAT-PT did not find a matching prefix for the destination address of the IPv6 packet.
*0.825484 Sysname NATPT/7/debug:
The v6 pkt is not intended for NATPT. Returning the pkt back to V6 stack
// NAT-PT sent the IPv6 packet back to the IPv6 protocol stack because it was not intended for
NAT-PT.
•
On multi-core devices:
# Enable NAT-PT packet debugging on the NAT-PT device. When the IPv6 host uses FTP to access
the IPv4 host, output similar to the following example is generated:
<Sysname> debugging natpt packet
*Mar 10 14:28:16:62 2008 Sysname DPNATPT/7/PACKET:
Pro : TCP
119
TTL : 127
IPv6 packet is translated to IPv4 packet.
(1000::0001 :
(5.1.1.1 :
1041 - 1001::0303:0301 :
1041 - 3.3.3.1 :
21)
21)
// NAT-PT translated the source and destination IPv6 addresses in the received IPv6 TCP packet
into IPv4 addresses.
*Mar 10 14:28:16:62 2008 Sysname DPNATPT/7/PACKET:
Pro : TCP
TTL : 254
IPv4 packet is translated to IPv6 packet.
(3.3.3.1 :
21 - 5.1.1.1 :
(1001::0303:0301 :
1041)
21 - 1000::0001 :
1041)
// NAT-PT translated the source and destination IPv4 addresses in the received IPv4 TCP packet
into IPv6 addresses.
# Enable NAT-PT event debugging. Output similar to the following example is generated when the
IPv6 host uses FTP to access the IPv4 host under the condition that NAT-PT is disabled on Ethernet
1/1:
<Sysname> debugging natpt event
*Mar 10 14:34:02:547 2008 Sysname DPNATPT/7/EVENT: The outgoing interface is disabled,
dropping packet.
// NAT-PT discarded the packets because NAT-PT was disabled on the outgoing interface.
# Enable NAT-PT event debugging on the NAT-PT device. Output similar to the following example
is generated when the IPv6 host uses FTP to access the IPv4 host under the condition that dynamic
IPv6 NAT-PT mappings are deleted:
<Sysname> debugging natpt event
*Mar 10 14:45:10:562 2008 Sysname DPNATPT/7/EVENT: Cannot get mapped IPv4 source
address, dropping packet.
// NAT-PT discarded the packet because no IPv6 NAT-PT mappings were available.
# Enable NAT-PT ALG debugging on the NAT-PT device. Output similar to the following example
is generated when the IPv6 host uses PORT to access the IPv4 host under the following conditions:

The IPv6 host has successfully accessed the IPv4 host by using FTP.

The sessions on the NAT-PT device have been deleted by using the reset session command.

The IPv6 NAT-PT dynamic mappings have been deleted.
<Sysname> debugging natpt alg
*Mar 10 14:45:10:562 2008 Sysname DPNATPT/7/ALG: Failed to process command EPRT.
// Because FTP control sessions and IPv6 dynamic NAT-PT mappings were removed from Device,
Device could not translate addresses in the PORT commands sent from the IPv6 host.
120
ND attack defense debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ipv6 nd detection packet
Use debugging ipv6 nd detection packet to enable ND packet debugging for ND detection.
Use undo debugging ipv6 nd detection packet to disable ND packet debugging for ND detection.
Syntax
debugging ipv6 nd detection packet
undo debugging ipv6 nd detection packet
Default
ND packet debugging of ND detection is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 1 describes the output fields and messages for the debugging ipv6 nd detection packet command.
Table 89 debugging ipv6 nd detection packet command output
Field
Description
Received: Port
Port that received an ND packet.
VLAN
VLAN that received the packet.
DstMACInEth
Destination MAC address in the Ethernet frame header of the
packet.
SrcMACInEth
Source MAC address in the Ethernet frame header of the packet.
PktType
Type of the packet.
SrcIP
Source IPv6 address of the packet.
DstIP
Destination IPv6 address of the packet.
TrgIP
Target address carried in an NS packet, an NA packet, or a
redirect packet.
RRDstIP
Destination address carried in a redirect packet.
LLA
MAC address in the source link-layer address option field of the
ND packet.
121
Field
Description
Dropped ND Packet for no entry match
The ND packet was dropped because the ND detection function
failed to find any address binding entry matching the packet
during source verification.
Examples
# Enable ND packet debugging for ND detection.
<Sysname> debugging ipv6 nd detection packet
*Jun 23 16:36:16:719 2009 Sysname ND/7/ND DETECTION_PACKET:
Received: Port= Ethernet 1/1, VLAN= 1, DstMACInEth= 0015-e943-820e, SrcMACInEth=
3333-ff00-0001, PktType= 133, SrcIP= 5::4, DstIP= 5::1, TrgIP= ::, RRDstIP= ::, LLA=
0000-0000-0002
// An ND packet was received.
*Jun 23 16:36:16:734 2009 Sysname ND/7/ND DETECTION_PACKET:
Dropped ND Packet for no entry match.
// The ND packet was dropped because no matching address entry was found.
122
NetStream debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ip netstream event
Use debugging ip netstream event to enable NetStream event debugging.
Use undo debugging ip netstream event to disable NetStream event debugging.
Syntax
debugging ip netstream event
undo debugging ip netstream event
Default
NetStream event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 1 describes the output fields and messages for the debugging ip netstream event command.
Table 90 Output from the debugging ip netstream event command
Field
Description
IP Stream Create cache
NetStream created IP stream cache.
IP Stream Destroy cache
NetStream cleared IP stream cache.
IP Stream Reset cache by force
NetStream reset IP stream cache.
IP Stream Malloc from system
NetStream allocated memory for IP stream cache.
IP Stream Add to active list
NetStream added an IP stream to the active list.
IP Stream Add to age list
NetStream added an IP stream to the aged list.
IP Stream Add a stream (Now 1 active streams)
NetStream added an IP stream entry (a total of one
active entry).
IP Stream Update a stream
NetStream updated an IP stream entry.
IP Stream Age a stream (tcp fin or rst)
An IP stream entry (TCP FIN or RST) aged out.
IP Stream Age a stream (active age or overflow)
An IP stream entry aged out due to active flow aging
or entry overflow.
IP Stream Age 1 streams (inactive timeout)
An IP stream entry aged out due to inactive flow
aging.
IP Stream Age 1 streams (age all)
An IP stream entry aged out due to forced aging.
123
Field
Description
IP Stream Age 1 streams (cache full)
An IP stream entry aged out due to entry overflow.
IP Stream Age all streams (cache modify)
All IP stream entries aged out due to cache
modification.
IP Stream Age all streams (reset)
All IP stream entries aged out due to resetting.
IP Stream Export a stream
NetStream exported an IP stream entry.
IP Stream Export 0 packets for timeout (no host or no
template)
No IP packets were exported because of timeout. This
event typically occurs because no destination host is
configured or no template is activated.
IP Stream Export 0 packets for cache full (no host or no
template)
No IP packets were exported because the cache was
full. This event typically occurs because no destination
host is configured or no template is activated.
IP Stream Export 1 packets for timeout
An IP packet was exported due to timeout.
IP Stream Export 1 packets for cache full
An IP packet was exported because the cache was
full.
AS Aggre Create cache
NetStream created AS aggregation stream cache.
AS Aggre Destory cache when 0 entrys left
NetStream cleared the AS aggregation stream cache
when it did not contain entries.
AS Aggre Add a stream (Now 1 active streams)
NetStream added an AS aggregation stream entry (a
total of one active entry).
AS Aggre Update a stream
NetStream updated an AS aggregation stream entry.
AS Aggre Export a stream
NetStream exported an AS aggregation stream entry.
AS Aggre Export 0 packets for timeout (no host or no
template)
No AS aggregation packets were exported because
of timeout. This event typically occurs because no
destination host is configured or no template is
activated.
AS Aggre Export 0 packets for aggre cache full (no
host or no template)
No AS aggregation packets were exported because
the cache was full. This event typically occurs because
no destination host is configured or no template is
activated.
AS Aggre Export 1 packets for timeout
An AS aggregation packet was exported due to
timeout.
AS Aggre Export 1 packets for aggre cache full
An AS aggregation packet was exported because the
cache was full.
Add to send queue (Now queue length is 1)
Packet Type: Normal IP Version No: 9 Records: 1
A packet was added to packet export queue 1. The
packet type is single IP stream, the packet format is
v9, and the number of IP stream entries is 1.
A packet was sent and entered a packet export
queue.
Send 1 packets (enter queue)
A packet was successfully sent:
Succeed in sending (Now queue length is 0)
Packet Type: Normal IP Version No: 9 Records: 1
124
•
•
•
•
Packet export queue is 0.
Packet type is single IP stream
Packet format is v9.
Number of IP stream entries is 1.
Field
Description
NetStream failed to send a packet.
Fail to send (Now queue length is 0)
Packet Type: Normal IP Version No: 9 Records: 1
•
•
•
•
Packet export queue is 0.
Packet type is single IP stream.
Packet format is v9.
Number of IP stream entries is 1.
Active Template (Now 1 active
templates):protocol-port inbound Id 271
A template was activated (a total of one activated
template). The template type is protocol-port inbound
and template ID is 271.
Deactive Template (Now 1 active
templates):protocol-port inbound Id 271
A template was deactivated (a total of one activated
template). The template type is protocol-port inbound
and template ID is 271.
Export Template :protocol-port inbound Id 271
A template was exported. The template type is
protocol-port inbound and template ID is 271.
Select Template for stream(Version 9 Type IP
outbound Id 282 )
A v9 template was selected for a single stream entry.
The template type is IP outbound and template ID is
282.
Select Template for aggre(Version 9 Type
destination-prefix inbound Id 261 )
A v9 template was selected for an aggregation
stream entry. The template type is destination-prefix
inbound and template ID is 261.
IP stream entry fields:
CPU 0 IP Stream
Add to active list:
Direct: O Stream Type: IP IP version: 4
InIf: 0 OutIf: 1048577 InVrf: 0 OutVrf: 0
SrcIP: 5.4.3.2 DstIP: 5.4.3.1 Prot: 1
SrcPort: 0 DstPort: 2048 Tos: 0x0 TcpFlag: 0x0
SrcAS: 0 DstAS: 0 SrcMask: 0 DstMask: 0
Nexthop: 5.4.3.1 BGP Nexthop: 0.0.0.0
Lable 1:0-0-0 2:0-0-0 3:0-0-0
TopLabel Type: UNKNOWN, IP: 0.0.0.0, Mask:
0.0.0.0
SrcMAC: 0000-0000-0000 DstMAC:
0000-0000-0000 SrcVlan: 0 DstVlan: 0
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
First: 0 Last: 0 Pkts: 0 0 Bytes: 0 84
Sample Mode: 0 Sample Interval: 0
125
Direct—Direction.
InIf—Inbound interface number.
OutIf—Outbound interface number.
InVrf—VPN that inbound packets belong.
OutVrf—VPN that outbound packets belong.
SrcIP—Source IP address.
DstIP—Destination IP address.
Prot—Protocol.
SrcPort—Source port number.
DstPort—Destination port number.
SrcAS—Source AS number.
DstAS—Destination AS number.
SrcMask—Source mask.
DstMask—Destination mask.
TopLabel Type—Type of the label at the top of the
label stack.
SrcMAC—Source MAC address.
DstMAC—Destination MAC address.
SrcVlan—Source VLAN ID.
DstVlan—Destination VLAN ID.
First—First active time of a stream.
Last—Last active time of a stream.
Pkts—Number of packets in a stream.
Bytes—Number of bytes of a stream.
Field
Description
AS aggregation fields:
CPU 0 AS Aggre Add a stream (Now 1 active
streams):
InIf: 0 OutIf: 1048576 SrcAS: 0 DstAS: 0
Direct: O Aggre Type: AS IP version : 4
First: 551894110 Last: 551894110 Streams: 1 Pkts:
0 1 Bytes: 0 84
Sample Mode: FULL Sample Interval: 0
•
•
•
•
•
•
•
•
InIf—Inbound interface number.
OutIf—Outbound interface number.
SrcAS—Source AS number.
DstAS—Destination AS number.
Aggre Type—Aggregation type.
First—First active time of a stream.
Last—Last active time of a stream.
Streams—Number of streams for aggregation
statistics.
• Pkts—Number of packets in a stream.
• Bytes—Number of bytes of a stream.
Examples
The output in the following examples is generated when the following conditions exist:
•
NetStream statistics are configured in the inbound direction of the interface Ethernet 1/0 on a
device.
•
A destination host is configured.
•
AS aggregation is enabled.
•
Version 9 is configured.
•
The inactive timer is set to 10 seconds.
# Enable IPv4 NetStream event debugging. Output in the following example is generated when an IP
packet arrives at Ethernet 1/0:
<Sysname> debugging ip netstream event
*Mar 21 12:31:47:343 2008 H3C NS/7/NS_EVENT:
CPU 0
IP Stream
Direct: I Stream Type:
Add to active list:
IP IP version: 4
InIf: 51314696 OutIf: 0 InVrf: 0 OutVrf: 0
SrcIP: 192.168.20.180 DstIP: 192.168.20.173 Prot: 1
SrcPort: 0 DstPort: 2048 Tos: 0x0 TcpFlag: 0x0
SrcAS: 0 DstAS: 0 SrcMask: 0 DstMask: 0
Nexthop: 0.0.0.0 BGP Nexthop: 0.0.0.0
Lable 1:0-0-0 2:0-0-0 3:0-0-0
TopLabel Type: UNKNOWN IP: 0.0.0.0 Mask: 0.0.0.0
SrcMAC: 0000-0000-0000 DstMAC: 0000-0000-0000 SrcVlan: 0 DstVlan: 0
First: 0 Last: 0 Pkts: 0 0 Bytes: 0 60
Sample Mode: 0 Sample Interval: 0
// An IPv4 stream was added to the list.
*Mar 21 12:31:47:343 2008 H3C NS/7/NS_EVENT:
CPU 0
IP Stream
Direct: I Stream Type:
Add a stream (Now 1 active streams):
IP IP version: 4
InIf: 51314696 OutIf: 118816768 InVrf: 0 OutVrf: 0
SrcIP: 192.168.20.181 DstIP: 192.168.20.173 Prot: 2
SrcPort: 0 DstPort: 2048 Tos: 0x0 TcpFlag: 0x0
SrcAS: 0 DstAS: 0 SrcMask: 24 DstMask: 32
126
Nexthop: 127.0.0.1 BGP Nexthop: 0.0.0.0
Lable 1:0-0-0 2:0-0-0 3:0-0-0
TopLabel Type: UNKNOWN IP: 0.0.0.0 Mask: 0.0.0.0
SrcMAC: 0000-0000-0000 DstMAC: 0000-0000-0000 SrcVlan: 0 DstVlan: 0
First: 10981810 Last: 10981810 Pkts: 0 1 Bytes: 0 60
Sample Mode: 0 Sample Interval: 0
// An IPv4 stream was added to the list.
# Enable IPv4 NetStream event debugging. Output in the following example is generated when
NetStream entry aged out after 10 seconds because the NetStream inactive aging timer timed out.
<Sysname> debugging ip netstream event
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
CPU 0
IP Stream
Age 1 streams (inactive timeout)
// An IP stream entry aged out due to inactive flow aging.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
Select Template for stream(Version 9 Type
IP inbound Id 281 )
// A template was selected for the IP stream entry.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
CPU 0
IP Stream
Export a stream:
Direct: I Stream Type:
IP IP version: 4
InIf: 51314696 OutIf: 118816768 InVrf: 0 OutVrf: 0
SrcIP: 192.168.20.180 DstIP: 192.168.20.173 Prot: 1
SrcPort: 0 DstPort: 2048 Tos: 0x0 TcpFlag: 0x0
SrcAS: 0 DstAS: 0 SrcMask: 24 DstMask: 32
Nexthop: 127.0.0.1 BGP Nexthop: 0.0.0.0
Lable 1:0-0-0 2:0-0-0 3:0-0-0
TopLabel Type: UNKNOWN IP: 0.0.0.0 Mask: 0.0.0.0
SrcMAC: 0000-0000-0000 DstMAC: 0000-0000-0000 SrcVlan: 0 DstVlan: 0
First: 10981810 Last: 10981810 Pkts: 0 1 Bytes: 0 60
Sample Mode: 0 Sample Interval: 0
// An IP stream entry was exported.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
CPU 0 as Aggre
Add a stream (Now 1 active streams):
InIf: 51314696 OutIf: 118816768 SrcAS: 0 DstAS: 0
Direct: I Aggre Type: as IP version : 4
First: 10981810 Last: 10981810 Streams: 1 Pkts: 0 1 Bytes: 0 60
Sample Mode: FULL Sample Interval: 0
// An AS aggregation stream entry was added (a total of one active entry).
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
Add to send queue (Now queue length is 1):
Packet Type: Normal
IP
Version No: 9
Records: 1
// An IP packet was added to the packet queue.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
Send 1 packets (enter queue)
// NetStream was sending a packet.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
Succeed in sending (Now queue length is 0):
127
Packet Type: Normal
IP
Version No: 9
Records: 1
// A packet was successfully sent.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
CPU 0
IP Stream
Export 1 packets for timeout
// An IP stream entry packet was sent.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
Select Template for aggre(Version 9 Type as inbound Id 257 )
// A template was selected for an AS aggregation stream entry.
*Mar 21 12:31:56:890 2008 H3C NS/7/NS_EVENT:
CPU 0 as Aggre
Export a stream:
InIf: 51314696 OutIf: 118816768 SrcAS: 0 DstAS: 0
Direct: I Aggre Type: as IP version : 4
First: 10981810 Last: 10981810 Streams: 1 Pkts: 0 1 Bytes: 0 60
Sample Mode: FULL Sample Interval: 0
*Mar 21 12:31:56:906 2008 H3C NS/7/NS_EVENT:
CPU 0 as Aggre
Export 1 streams
// An AS aggregation stream entry was exported.
*Mar 21 12:31:56:906 2008 H3C NS/7/NS_EVENT:
Add to send queue (Now queue length is 1):
Packet Type: Aggre as
Version No: 9
Records: 1
// An AS aggregation packet was added to the packet export queue.
*Mar 21 12:31:56:906 2008 H3C NS/7/NS_EVENT:
Send 1 packets (enter queue)
// NetStream was sending a packet.
*Mar 21 12:31:56:906 2008 H3C NS/7/NS_EVENT:
Succeed in sending (Now queue length is 0):
Packet Type: Aggre as
Version No: 9
Records: 1
// A packet was successfully sent.
*Mar 21 12:31:56:906 2008 H3C NS/7/NS_EVENT:
CPU 0 as Aggre
Export 1 packets for timeout
// An AS aggregation packet was sent.
debugging ip netstream packet
Use debugging ip netstream packet to enable NetStream packet debugging.
Use undo debugging ip netstream packet to disable NetStream packet debugging.
Syntax
debugging ip netstream packet
undo debugging ip netstream packet
Default
NetStream packet debugging is disabled.
Views
User view
128
Default command level
1: Monitor level
Usage guidelines
Table 2 describes the output fields and messages for the debugging ip netstream packet command.
Table 91 Output from the debugging ip netstream packet command
Field
Description
Send succeed!
NetStream sent a packet successfully.
Send fail!
NetStream failed to send a packet.
Packet Type: Normal IP Version No: 5 Records: 2
SrcIP(Port): 192.168.20.173(40000) DstIP(Port):
192.168.20.180(138) VrfID: 0
•
•
•
•
Packet Type—Exported packet type.
Version No—Exported packet version.
Records—Number of packets exported.
SrcIP(Port)—Source IP address. The field in
parentheses shows the source port number.
• DstIP(Port)—Destination IP address. The field in
parentheses shows the destination port number.
• VrfID—Private network route index.
Examples
# Enable IPv4 NetStream packet debugging. Output similar to the following example is generated when
an IP packet arrives at Ethernet 1/0 and an entry ages out under the following conditions:
•
NetStream is enabled on Ethernet 1/0.
•
A destination host is configured.
<Sysname> debugging ip netstream packet
*Mar 21 09:41:07:953 2008 H3C NS/7/NS_PACKET:
Send succeed!
Packet Type: Normal
IP
Version No: 5
Records: 2
SrcIP(Port): 192.168.20.173(40000) DstIP(Port): 192.168.20.180(138) VrfID: 0
// A version 5 IP stream was sent successfully.
129
NQA debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging nqa
Use debugging nqa to enable NQA debugging.
Use undo debugging nqa to disable NQA debugging.
Syntax
debugging nqa { all | error | event | reaction }
undo debugging nqa { all | error | event | reaction }
Default
NQA debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Enables all types of debugging for NQA.
error: Enables NQA error debugging.
event: Enables NQA event debugging.
reaction: Enables debugging for NQA collaboration entries.
Usage guidelines
Table 1 describes output fields and messages for the debugging nqa event command.
Table 92 Output from the debugging nqa event command
• Field
• Description
• FTP test (owner-tag): state.
•
•
•
•
•
•
State of the FTP operation:
New user logging in.
Data connection created.
Ready for file transfer.
File transfer completed.
Data connection closed.
• Begin time
• Time when the NQA client began to obtain an IP address.
• End time
• Time when the NQA client obtained an IP address.
Table 2 describes output fields and messages for the debugging nqa reaction command.
130
Table 93 Output from the debugging nqa reaction command
• Field
• Description
• Owner: owner
• Name of the administrator who creates the NQA operation.
• Tag: tag
• NQA operation tag.
• Previous status: status
• Previous status:
• 1—The previous status is invalid.
• 2—The number of consecutive probe failures exceeds the
threshold.
• 3—The operation succeeded.
• Current status: status
• Current status:
• 1—The current status is invalid.
• 2—The number of consecutive probe failures exceeds the
threshold.
• 3—The operation succeeded.
Examples
# Enable all types of debugging for NQA.
<Sysname> terminal debugging
<Sysname> terminal monitor
<Sysname> debugging nqa all
# Create an NQA operation.
<Sysname> system-view
[Sysname] nqa entry admin test
*Apr 29 21:44:18:32 2007 Sysname NQA/7/NQA_Event: NQA entry(admin-test) is created.
// An NQA operation was created. The administrator name is admin and operation tag is test.
# Configure the operation type as ICMP echo, and specify the destination address for the ICMP echo
operation.
[Sysname-nqa-admin-test] type icmp-echo
[Sysname-nqa-admin-test-icmp-echo] destination ip 10.2.2.1
[Sysname-nqa-admin-test-icmp-echo] quit
# Schedule an NQA operation.
[Sysname] nqa schedule admin test start-time now lifetime forever
*Apr 29 21:47:25:630 2007 Sysname NQA/7/NQA_Event: NQA schedule: Entry(admin-test) is
added to the test schedule queue.
// NQA added the NQA operation to the scheduling queue.
*Apr 29 21:47:25:630 2007 Sysname NQA/7/NQA_Event: NQA schedule: Entry(admin-test) is
scheduled successfully.
// The NQA operation was successfully scheduled.
*Apr 29 21:47:25:674 2007 Sysname NQA/7/NQA_Event: ICMP test (admin-test): Start to probe.
// NQA started the ICMP echo operation.
*Apr 29 21:47:25:674 2007 Sysname NQA/7/NQA_Event: ICMP test (admin-test): Start to send
packets.
// NQA started to send packets.
131
*Apr 29 21:47:25:706 2007 Sysname NQA/7/NQA_Event: ICMP test (admin-test): Probe
succeeded.
// The operation succeeded.
# Cancel the NQA operation schedule.
[Sysname] undo nqa schedule admin test
*Apr 29 21:49:00:206 2007 Sysname NQA/7/NQA_Event: NQA Schedule: The schedule of
entry(admin-test) is cancelled.
// The NQA operation schedule was successfully cancelled.
132
NTP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ntp-service
Use debugging ntp-service to enable NTP debugging.
Use undo debugging ntp-service to disable NTP debugging.
Syntax
debugging ntp-service { access | adjustment | all | authentication | event | filter | packet | parameter
| refclock | selection | synchronization | validity }
undo debugging ntp-service { access | adjustment | all | authentication | event | filter | packet |
parameter | refclock | selection | synchronization | validity }
Default
All NTP debugging functions are disabled.
Views
User view
Default command level
1: Monitor level
Parameters
access: NTP access control debugging.
adjustment: NTP clock adjustment debugging.
all: All types of debugging for NTP.
authentication: NTP authentication debugging.
event: NTP event debugging.
filter: NTP filter debugging.
packet: NTP packet debugging.
parameter: Debugging for NTP clock parameters.
refclock: Debugging for NTP reference clock.
selection: Debugging for NTP clock selection information.
synchronization: Debugging for NTP clock synchronization.
validity: Debugging for NTP remote host validity.
Usage guidelines
Table 1 describes output fields and messages for the debugging ntp-service adjustment command.
133
Table 94 Output from the debugging ntp-service adjustment command
Field
Description
NTP: gradual systime
NTP is gradually adjusting the system time.
NTP: step systime
NTP is adjusting the system time in one step.
adj: string
Time that is adjusted in the current time adjustment operation.
residual: string
Remaining value for the most recent time adjustment.
offset: string
Offset for step adjustment.
Table 2 describes output fields and messages for the debugging ntp-service authentication command.
Table 95 Output from the debugging ntp-service authentication command
Field
Description
session_key
Session key.
srcadr: string
Source IP address.
dstadr: string
Destination IP address.
keyid: string
Key ID.
life: string
Lifetime of a key.
auth_agekeys
Parameters related to key lifetime.
time: string
Time period from when the system starts until the current time.
trusted keynum: string
Number of trusted keys.
expired keynum: string
Number of expired keys.
Authentication keyID: string
Authentication key ID.
Table 3 describes output fields and messages for the debugging ntp-service event command.
Table 96 Output from the debugging ntp-service event command
Field
Description
NTP: control event
NTP control event.
event: string
Event code.
eventnum: string
Number of events.
peer: string
IP address of the peer.
Table 4 describes output fields and messages for the debugging ntp-service filter command.
Table 97 Output from the debugging ntp-service filter command
Field
Description
NTP: adj freq
Adjustment frequency.
last clockoffset: string
Last clock offset.
last drift_comp: string
Last frequency.
new clockOffset: string
New clock offset.
134
Field
Description
new drift_comp: string
New frequency.
Table 5 describes output fields and messages for the debugging ntp-service packet command.
Table 98 Output from the debugging ntp-service packet command
Field
Description
NTP: titleAndTip control packet from
sourceIPAddress to DestIPAddress
• titleAndTip—Title and prompt information.
• sourceIPAddress—Source IP address of the packet.
• DestIPAddress—Destination IP address of the packet.
version: string
Version number in the control packet.
r: string
Response bit in the control packet.
e: string
Error bit in the control packet.
m: string
More bit in the control packet.
o: string
Operation code in the control packet.
sequence: string
Sequence number in the control packet.
status: string
Status words in the control packet.
associationID: string
Association ID in the control packet.
data: string
Data information in the control packet.
authenticator: string
Authenticator information in the control packet.
packet to string
Destination IP address of the packet.
leap: string
Leap indicator in a packet.
version: string
Version number in a packet.
mode: string
Working mode in a packet.
vrfindex: string
Index of the VPN that received or sent a packet.
stratum: string
Stratum information in a packet.
poll: string
Poll interval information in a packet.
precision: string
Precision information in a packet.
rdel: string
Root delay information in a packet.
rdsp: string
Root dispersion information in a packet.
ID of the reference clock.
refid: string
If the reference clock is a local clock, the contents of this field vary
by the stratum of the local clock. If the stratum is 1, this field
displays LOCL. If the stratum is another value, this field displays
the IP address of the local clock.
If the reference clock is the clock of another device in the network,
this field displays the IP address of this device.
reftime: string
Reference timestamp.
orgtime: string
Originate timestamp.
rectime: string
Receive timestamp.
135
Field
Description
xmttime: string
Transmit timestamp.
inptime: string
Timestamp for processing a packet.
packet from SourceIPAddress to
DestIPAddress on InterfaceName
• SourceIPAddress—Source IP address.
• DestIPAddress—Destination IP address.
• InterfaceName—Name of the interface receiving the packet.
Table 6 describes output fields and messages for the debugging ntp-service parameter command.
Table 99 Output from the debugging ntp-service parameter command
Field
Description
NTP: popcorn spike: string
Offset jitter.
NTP: discard: string
The sample is discarded if the lifetime of the new sample is
lower than or equal to the selected sample. This field displays
the lifetime of the new sample.
clock_filter(PeerAddr, SampleOffset,
SampleDelay, SampleDisp)
IP address, sample offset, sample delay, and sample
dispersion of the peer in clock-filter.
offset: string
Offset of the peer.
delay: string
Delay of the peer.
dispersion: string
Dispersion of the peer.
std: string
Jitter of the peer.
Table 7 describes output fields and messages for the debugging ntp-service refclock command.
Table 100 Output from the debugging ntp-service refclock command
Field
Description
Report Event:
Reference clock event.
Clock: string
IP address of the reference clock.
Event: string
Description of the clock event.
Code: string
Event code of the clock.
The reference clock sent analog information:
RefClock Transmit: At CurrentTime IPAddr
• CurrentTime—Current system time.
• IPAddr—IP address of the reference clock.
RefClock Sample:
Sample of the reference clock.
sampleNum: string
Number of samples.
offset: string
Offset.
disp: string
Dispersion.
std: string
Jitter.
The reference clock receive analog information:
RefClock Receive: At CurrentTime IPAddr
• CurrentTime—Current system time.
• IPAddr—IP address of the reference clock.
136
Table 8 describes output fields and messages for the debugging ntp-service selection command.
Table 101 Output from the debugging ntp-service selection command
Field
Description
nlist: string
Number of the candidate clocks in candidate clock list.
allow: string
Number of surviving candidates.
found: string
Number of discarded candidates.
low: string
Lower value of the sample offset.
high: string
Upper value of the sample offset.
candidate: string
IP address of a candidate clock.
cdist: string
Root distance of a candidate clock.
disp: string
Dispersion of a candidate clock.
survivor: string
IP address of the candidate clock survived in a check.
offset: string
Offset of the candidate clock survived in a check.
cdist: string
Dispersion of the candidate clock survived in a check.
syspeer: string
IP address of the clock selected by the system.
offset: string
Offset of the clock selected by the system.
Root-distance
Synchronization distance.
Max root-distance
Maximum synchronization distance selected by the clock
source.
SYSPOLL
System polling interval.
Table 9 describes output fields and messages for the debugging ntp-service validity command.
Table 102 Output from the debugging ntp-service validity command
Field
Description
• SourceIPAddr—Source IP address of the packet.
• TestResult—Test result, successful or failed.
• TestCode—Code of the object to be tested.
Code and its meaning of the object to be tested:
NTP: packet from SourceIPAddr, TestResult
validity tests TestCode
•
•
•
•
•
•
•
•
0x0001—Duplicate information.
0x0002—False information.
0x0004—Unsynchronized information.
0x0008—Peer delay/skew dispersion.
0x0010—Peer authentication failure.
0x0020—Unsynchronized peer clock.
0x0040—Peer stratum level exceeds the highest value.
0x0080—Root delay/dispersion exceeds the highest
value.
• 0x0100—No authentication on the peer.
• 0x0200—Access denied.
137
Examples
# Enable NTP packet debugging on Device A. The output in this example was created when the
following conditions exist:
•
On Device A and Device B, the IP addresses for VLAN-interface 1 are 10.1.1.1 and 10.1.1.2,
respectively.
•
The IP addresses can be pinged from each other.
•
Device B's local clock is to be used as a reference source, with the stratum level of 8.
•
Device A is configured to synchronize its clock to Device B in client/server mode.
<DeviceA> debugging ntp-service packet
<DeviceA> terminal debugging
<DeviceA> terminal monitor
// Log monitoring on the current terminal was enabled.
*Aug 12 06:04:42:129 2005 DeviceA NTP/7/debug_NTP_packet_xmt:
packet to 10.1.1.2
leap: 3, version: 3, mode: 3, vrfindex: 0
stratum: 0, poll: 64, precision: 2^18
rdel: 0.000, rdsp: 0.000, refid: 0.0.0.0
reftime: 06:02:26.094 UTC Aug 12 2005(C6A6B9F2.181A5870)
orgtime: 00:00:00.000 UTC Jan 1 1900(00000000.00000000)
rectime: 00:00:00.000 UTC Jan 1 1900(00000000.00000000)
xmttime: 06:04:42.127 UTC Aug 12 2005(C6A6BA7A.20B039EF)
// NTP sent an NTP time request to Device B at 10.1.1.2.
%Oct 11 14:42:45:139 2006 DeviceA NTP/4/NTP_LOG:
System leap changes from 3 to 0 after clock update.
%Oct 11 14:42:45:140 2006 DeviceA NTP/4/NTP_LOG:
System stratum changes from 16 to 9 after clock update.
// Log information when the clock alarm and clock stratum of the system changed was generated.
*Oct 11 14:42:45:141 2006 DeviceA NTP/7/debug_NTP_packet_rcv:
packet from 10.1.1.2 to 10.1.1.1 on Vlan-interface1
leap: 0, version: 3, mode: 4, vrfindex: 0
stratum: 8, poll: 64, precision: 2^18
rdel: 0.000, rdsp: 10.941, refid: 127.127.1.0
reftime: 14:42:31.278 UTC Oct 11 2006(C8D78157.4758D152)
orgtime: 06:04:42.127 UTC Aug 12 2005(C6A6BA7A.20B039EF)
rectime: 14:42:45.132 UTC Oct 11 2006(C8D78165.21F88FC9)
xmttime: 14:42:45.132 UTC Oct 11 2006(C8D78165.22075F6F)
inptime: 06:04:42.137 UTC Aug 12 2005(C6A6BA7A.23316E37)
// Device A at 10.1.1.1 received the NTP response from Device B at 10.1.1.2.
NOTE:
This example provides only the packet exchange process for the first two packets.
138
OAA debugging command
debugging oaa remote-interface
Use debugging oaa remote-interface to enable debugging for the OAA remote interface management
module.
Use undo debugging oaa remote-interface to disable debugging for the OAA remote interface
management module.
Syntax
debugging oaa remote-interface { all | error | event }
undo debugging oaa remote-interface { all | error | event }
Default
Debugging is disabled for the OAA remote interface management module.
Views
User view
Default command level
1: Monitor level
Parameters
all: All types of debugging for the OAA remote interface management module.
error: Error debugging for the OAA remote interface management module.
event: Event debugging for the OAA remote interface management module.
Examples
# Enable debugging for the remote interface management module. The output in this example was
created when the following conditions exist:
•
OAA remote interface management is configured on the client.
•
SNMP client is configured to communicate with the SNMP server.
•
Remote interface management is enabled.
•
The interface information is added to the dynamic remote interface table.
•
The Refresh button on the remote interface management page is clicked.
<Sysname> debugging oaa remote-interface all
*Mar 20 14:50:50:313 2008 Sysname RMIF/7/DEBUG_RMIF_EVENT:
Update snapshot remote-interface table.
// The snapshot remote interface table was updated.
139
OSPF debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ospf event
Use debugging ospf event to enable OSPF event debugging.
Use undo debugging ospf event to disable OSPF event debugging.
Syntax
debugging ospf [ process-id ] event [ bfd | error | graceful-restart | interface | neighbor ]
undo debugging ospf [ process-id ] event [ bfd | error | graceful-restart | interface | neighbor ]
Default
OSPF event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID, in the range of 1 to 65535.
bfd: Specifies OSPF BFD event debugging.
error: Specifies OSPF error event debugging.
graceful-restart: Specifies OSPF graceful restart (GR) event debugging.
interface: Specifies interface event debugging.
neighbor: Specifies OSPF neighbor event debugging.
Usage guidelines
If no process ID is specified, the event debugging information of all the OSPF processes will be
displayed.
Table 1 describes output fields and messages for the debugging ospf event bfd command.
Table 103 Output from the debugging ospf event bfd command
Field
Description
OSPF process-id:OSPF received packet having
conflicted Router ID :rt-id
OSPF received a packet with a conflicting Router ID.
rt-id indicates the router ID of the neighbor.
140
Field
Description
Detailed OSPF BFD message information:
• msg-type—BFD message type, which can be
OSPF-BFD: Message type msg-type, Connect type
conn-type, Src IP Address src-ip, Src IFIndex if-index,
Dst IP Address dst-ip
delete session, rcv BFD down, create session, or
disable BFD.
• conn-type—Connection type, which is
direct-connect.
• Source IP address, source interface, and
destination IP address.
Table 2 describes output fields and messages for the debugging ospf event neighbor command.
Table 104 Output from the debugging ospf event neighbor command
Field
Description
OSPF process-id
OSPF process ID.
Detailed information of neighbor state changes:
• nbr-ip—Neighbor interface IP address.
• nbr-event—Event triggering the HelloReceived,
Start, 2WayReceived, NegotiationDone,
ExchangeDone, BadLSReq, LoadingDone,
AdjOK?, 1-Way, KillNbr, Inactivity Timer, or
LLDown.
Nbr nbr-ip Rcv nbr-event State original-state ->
current-state
• original-state/current-state—Previous and current
neighbor state. The state can be Down, Attempt,
Init, 2-Way, ExStart, Exchange, Loading, or Full.
Examples
# Enable OSPF interface event debugging on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
•
On Router A, OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
<RouterA> debugging ospf event interface
%Dec 12 09:24:58:978 2006 RouterA IFNET/4/UPDOWN:
Line protocol on the interface Ethernet1/0 is UP
OSPF 1: Intf 150.1.1.1 Rcv InterfaceUp State Down -> Waiting.
// Interface state was changed from Down to Waiting.
OSPF 1: Intf 150.1.1.1 Rcv BackupSeen State Waiting -> BackupDR.
// Interface state was changed from Waiting to BackupDR.
# Enable OSPF neighbor event debugging on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
141
•
On Router A, OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
<RouterA> debugging ospf event neighbor
<RouterA>
OSPF 1: Nbr 150.1.1.2 Rcv KillNbr State Full -> Down.
OSPF 1: Nbr 150.1.1.2 Rcv HelloReceived State Down -> Init.
OSPF 1: Nbr 150.1.1.2 Rcv 2WayReceived State Init -> 2Way.
OSPF 1: Nbr 150.1.1.2 Rcv AdjOk? State 2Way -> ExStart.
OSPF 1: Nbr 150.1.1.2 Rcv NegotiationDone State ExStart -> Exchange.
OSPF 1: Nbr 150.1.1.2 Rcv ExchangeDone State Exchange -> Loading.
OSPF 1: Nbr 150.1.1.2 Rcv LoadingDone State Loading -> Full.
// OSPF process 1 established an adjacency relationship with neighbor 150.1.1.2
# Enable OSPF GR event debugging on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
•
On Router A:

OSPF process 1 is created and area 0 is created in OSPF process 1.

Ethernet 1/0 is enabled with OSPF and is configured to belong to area 0.

•
OSPF process 1 is enabled with OSPF local link signaling, OSPF out-of-band synchronization,
and OSPF GR.
On Router B:

OSPF process 1 is created.

Ethernet 1/0 is enabled with OSPF and is configured to belong to area 0.

OSPF process 1 is enabled with OSPF local link signaling and OSPF out-of-band
synchronization.
When you restart GR in OSPF process 1, output similar to the following example is generated:
<RouterA>reset ospf 1 process graceful-restart
%Dec 12 09:36:12:500 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Full to Down
OSPF 1: Intf 150.1.1.1 Rcv InterfaceDown State BackupDR -> Down.
OSPF 1 nonstandard GR Started for OSPF Router
// The device started OSPF GR.
OSPF 1 notify RM that OSPF process will enter GR.
OSPF 1 created GR wait timer, timeout interval is 40(s).
OSPF 1 created GR Interval timer,timeout interval is 120(s).
OSPF 1: Intf 150.1.1.1 Rcv InterfaceUp State Down -> Waiting.
OSPF 1: Intf 150.1.1.1 Rcv BackupSeen State Waiting -> BackupDR.
OSPF 1 created OOB Progress timer for neighbor 150.1.1.2.
OSPF 1 restarted OOB Progress timer for neighbor 150.1.1.2.
OSPF 1 restarted OOB Progress timer for neighbor 150.1.1.2.
%Dec 12 09:36:12:566 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Loading to Full
142
OSPF 1 restarted OOB Progress timer for neighbor 150.1.1.2.
OSPF 1 deleted OOB Progress timer for neighbor 150.1.1.2.
OSPF 1 Gr Wait Timeout timer fired.
OSPF 1 deleted GR wait timer.
OSPF 1 deleted GR Interval timer.
OSPF 1 GR Completed for OSPF Router
// The device completed the GR.
OSPF 1 notified RM that OSPF process left GR.
RM notified that all protocol left GR.
OSPF 1 started flushing STALE LSA after all protocol left GR.
// OSPF started to flush stale LSAs after all the protocol exited GR.
OSPF 1: Flush Stale Area LSAs
OSPF 1: Start Flush Stale ASE + NSSA LSAs
OSPF 1: End Flush Stale ASE + NSSA LSAs
// Procedure of adjacency synchronization during GR.
debugging ospf hot-standby
Use debugging ospf hot-standby to enable hot-standby debugging for OSPF.
Use undo debugging ospf hot-standby to disable hot-standby debugging for OSPF.
Syntax
debugging ospf [ process-id ] hot-standby
undo debugging ospf [ process-id ] hot-standby
Default
OSPF hot-standby debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID, in the range of 1 to 65535.
Usage guidelines
If no process ID is specified, the hot-standby debugging information of all the OSPF processes will be
displayed.
Table 3 describes output fields and messages for the debugging ospf hot-standby command.
Table 105 Output from the debugging ospf hot-standby command
Field
Description
OSPF HSB Bkp: Instance ID: instance-id Process ID:
process-id
143
OSPF backed up the OSPF process data under the
specified instance.
• instance-id—OSPF instance ID.
• process-id—OSPF process ID.
Field
Description
OSPF HSB Bkp: Instance ID: instance-id Process ID:
process-id Area ID: area-id
OSPF HSB Res: Instance ID: instance-id Process ID:
process-id
OSPF HSB Res: Instance ID: instance-id Process ID:
process-id Area ID: area-id
OSPF backed up the OSPF process area data
under the specified instance.
• instance-id—OSPF instance ID.
• process-id—OSPF process ID.
• area-id—Area ID.
OSPF restored the OSPF process data under the
specified instance.
• instance-id—OSPF instance ID.
• process-id—OSPF process ID.
OSPF restored the OSPF process area data under
the specified instance.
• instance-id—OSPF instance ID.
• process-id—OSPF process ID.
• area-id—Area ID.
Examples
# Enable hot-standby debugging for OSPF process 1. The output in this example was created when the
following conditions exist:
•
Router A is a dual-master device and its master board boots first.
•
On Router A, OSPF process 1 is created, and area 0 and area 1 are configured under OSPF
process 1.
•
Area 0 is configured to contain network 10.10.10.10/32. OSPF is enabled on Loopback 0
(10.10.10.10/32.
•
Area 1 is configured to contain network 11.11.11.11/32. OSPF is enabled on Loopback 1
(11.11.11.11/32).
When you insert the standby board, output similar to the following example is generated:
<RouterA> debugging ospf 1 hot-standby
%Apr 26 10:45:44:348 2007 RouterA HA/4/LOG: Batch backup started
OSPF 1 Back-up process data Start.
*Apr 26 10:45:44:363 2007 RouterA RM/6/RMDEBUG:
OSPF HSB Bkp: Instance ID: 0
Process ID: 1
OSPF 1 Back-up process data End.
// OSPF started and then ended backing up OSPF process 1 data.
OSPF 1 Back-up Area data Start.
*Apr 26 10:45:44:379 2007 RouterA RM/6/RMDEBUG:
OSPF HSB Bkp: Instance ID: 0
Process ID: 1
Area ID: 0.0.0.0
OSPF 1 Back-up Area data End.
// OSPF started and then ended backing up data for area 0 of OSPF process 1.
OSPF 1 Back-up Area data Start.
*Apr 26 10:45:44:394 2007 RouterA RM/6/RMDEBUG:
OSPF HSB Bkp: Instance ID: 0
Process ID: 1
Area ID: 0.0.0.1
OSPF 1 Back-up Area data End.
// OSPF started and then ended backing up data backup for area 1 of OSPF process 1.
*Apr 26 10:45:44:394 2007 RouterA RM/6/RMDEBUG:
144
OSPF HSB Bkp: Process ID: 1
Index:4
Area ID: 0.0.0.1
IpAdderss :11.11.11.11
Physical
Logical Index:0.0.0.0
// OSPF backed up the data on Loopback 1 in area 1 of process 1.
*Apr 26 10:45:44:428 2007 RouterA RM/6/RMDEBUG:
OSPF HSB Bkp: Process ID: 1
Index:3
Area ID: 0.0.0.0
IpAdderss :10.10.10.10
Physical
Logical Index:0.0.0.0
// OSPF backed up the data on Loopback 0 in area 0 of process 1.
%Apr 26 10:45:55:483 2007 RouterA HA/4/LOG: Batch backup finished
// Batch backup finished.
debugging ospf lsa
Use debugging ospf lsa to enable OSPF LSA debugging.
Use undo debugging ospf lsa to disable OSPF LSA debugging.
Syntax
debugging ospf [ process-id ] lsa [ generate | install ]
undo debugging ospf [ process-id ] lsa [ generate | install ]
Default
OSPF LSA debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
generate: Specifies LSA generation debugging.
install: Specifies debugging for the installation of LSAs into the LSDB.
Usage guidelines
If no process ID is specified, the LSA debugging information of all the OSPF processes will be displayed.
Table 4 describes output fields and messages for the debugging ospf lsa command.
Table 106 Output from the debugging ospf lsa command
Field
Description
OSPF process-id
OSPF process ID.
Operation on LSAs:
op-type LSA at x ms
• Generate—Generating LSAS
• Install—Installing LSAs.
145
Field
Description
LSA header information:
• ls-type—LSA type:
LSAType: ls-type LinkStateId: link-state-id
Advertising Rtr: rt-id

1 for Router LSA.

2 for network LSA.

3 for net-summary LSA.

4 for ASBR-summary LSA.

5 for AS-external–LSA.

7 for NSSA LSA.

9, 10, and 11 for Opaque LSA.
• link-state-id—LSA ID.
• rt-id—ID of the advertising router.
LSA header information:
LSA Age: age Options : ExRouting: ON/OFF
• age—LSA age.
• ON/OFF—Indicates whether external routing is
supported.
LSA header information:
Length: ls-len Seq: seq-num
CheckSum:checksum
• ls-len—LS length.
• seq-num—LS sequence number.
• checksum—Checksum of the entire LSA except for the LSA
age field.
Router LSA contents:
Capabilities: VBit: EBit: BBit: NtBit: Link#:
link-count TOS# tos-num Metric cost
•
•
•
•
VBit—0x40 for a virtual link.
EBit—0x200 for an External LSA.
BBit—0x100 for an ABR.
NtBit—0x1000 for a router that unconditionally translates
Type-7 LSAs to Type-5 LSAs.
• Link-count—Number of links in the Router LSA.
• tos-num—Number of TOSs in the Router LSA.
• cost—Link cost.
Network LSA contents:
Net Mask: net-mask Attached Router: rt-id
• net-mask—Network mask.
• rt-id—ID of a neighbor.
Contents of Summary and ASBR-Summary LSAs:
Net Mask: net-mask Metric: cost
• net-mask—Network mask.
• cost—Link cost.
Contents of AS_External LSA and NSSA LSA:
Net Mask: net-mask TOS: tos Metric: cost
FwdAddr: fwd-addr Tag: rt-tag
•
•
•
•
•
146
net-mask—Network mask.
tos—Type of Service.
cost—Link cost.
fwd-addr—Forwarding address.
rt-tag—External route tag.
Examples
# Enable debugging for the installation of LSAs into the LSDB on Router A. The output in this example was
created when the following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
•
On Router A,OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
<RouterA> debugging ospf lsa install
<RouterA>
*Sep
8 17:51:02:234 2006 RouterA RM/6/RMDEBUG:OSPF 1: Install LSA at 4796222 ms:
*Sep
8 17:51:02:244 2006 RouterA RM/6/RMDEBUG:LSAType: 1.
*Sep
8 17:51:02:244 2006 RouterA RM/6/RMDEBUG:LinkStateId: 201.1.1.1.
*Sep
8 17:51:02:254 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 201.1.1.1.
*Sep
8 17:51:02:254 2006 RouterA RM/6/RMDEBUG:LSA Age: 0 Options: ExRouting:ON.
*Sep 8 17:51:02:254 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 80000008 CheckSum: 60445.
*Sep 8 17:51:02:254 2006 RouterA RM/6/RMDEBUG:Capabilities: VBit:0 EBit: 512 BBit: 0 NtBit:
0 Link# 1.
*Sep 8 17:51:02:254 2006 RouterA RM/6/RMDEBUG:LinkID: 150.1.1.0 LinkData: 255.255.2 55.0
LinkType: 3.
*Sep
8 17:51:02:254 2006 RouterA RM/6/RMDEBUG:TOS# 0 Metric 10.
// OSPF process 1 installed the Router-LSAs it generated.
*Sep
8 17:51:06:766 2006 RouterA RM/6/RMDEBUG:OSPF 1: Install LSA at 4800748 ms:
*Sep
8 17:51:06:766 2006 RouterA RM/6/RMDEBUG:LSAType: 1.
*Sep
8 17:51:06:766 2006 RouterA RM/6/RMDEBUG:LinkStateId: 202.1.1.1.
*Sep
8 17:51:06:776 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 202.1.1.1.
*Sep
8 17:51:06:776 2006 RouterA RM/6/RMDEBUG:LSA Age: 5 Options: ExRouting:ON.
*Sep
8 17:51:06:776 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 80000001 CheckSum: 5373.
*Sep 8 17:51:06:776 2006 RouterA RM/6/RMDEBUG:Capabilities: VBit:0 EBit: 512 BBit: 256
NtBit: 0 Link# 1.
*Sep 8 17:51:06:786 2006 RouterA RM/6/RMDEBUG:LinkID: 150.1.1.0 LinkData: 255.255.255.0
LinkType: 3.
*Sep
8 17:51:06:786 2006 RouterA RM/6/RMDEBUG:TOS# 0 Metric 10.
// OSPF process 1 installed the Router-LSAs generated by the peer.
*Sep
8 17:51:06:786 2006 RouterA RM/6/RMDEBUG:OSPF 1: Install LSA at 4800748 ms:
*Sep
8 17:51:06:806 2006 RouterA RM/6/RMDEBUG:LSAType: 2.
*Sep
8 17:51:06:806 2006 RouterA RM/6/RMDEBUG:LinkStateId: 150.1.1.1.
*Sep
8 17:51:06:806 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 201.1.1.1.
*Sep
8 17:51:06:806 2006 RouterA RM/6/RMDEBUG:LSA Age: 0 Options: ExRouting:ON.
*Sep
8 17:51:06:816 2006 RouterA RM/6/RMDEBUG:Length: 32 Seq# 80000001 CheckSum: 2890.
*Sep
8 17:51:06:816 2006 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0.
*Sep
8 17:51:06:816 2006 RouterA RM/6/RMDEBUG:Attached Router: 202.1.1.1.
*Sep
8 17:51:06:826 2006 RouterA RM/6/RMDEBUG:Attached Router: 201.1.1.1.
// Because the local router is a DR, OSPF process 1 installed the Network-LSAs it generated.
*Sep
8 17:51:07:238 2006 RouterA RM/6/RMDEBUG:OSPF 1: Install LSA at 4801229 ms:
*Sep
8 17:51:07:238 2006 RouterA RM/6/RMDEBUG:LSAType: 1.
147
*Sep
8 17:51:07:238 2006 RouterA RM/6/RMDEBUG:LinkStateId: 201.1.1.1.
*Sep
8 17:51:07:248 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 201.1.1.1.
*Sep
8 17:51:07:248 2006 RouterA RM/6/RMDEBUG:LSA Age: 0 Options: ExRouting:ON.
*Sep 8 17:51:07:248 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 80000009 CheckSum: 34281.
*Sep 8 17:51:07:258 2006 RouterA RM/6/RMDEBUG:Capabilities: VBit:0 EBit: 512 BBit: 0 NtBit:
0 Link# 1.
*Sep 8 17:51:07:258 2006 RouterA RM/6/RMDEBUG:LinkID: 150.1.1.1 LinkData: 150.1.1.1
LinkType: 2.
*Sep
8 17:51:07:258 2006 RouterA RM/6/RMDEBUG:TOS# 0 Metric 10.
// OSPF process 1 installed the Router-LSAs it generated, with stub link changed to transit link.
*Sep
8 17:51:11:710 2006 RouterA RM/6/RMDEBUG:OSPF 1: Install LSA at 4805705 ms:
*Sep
8 17:51:11:720 2006 RouterA RM/6/RMDEBUG:LSAType: 1.
*Sep
8 17:51:11:720 2006 RouterA RM/6/RMDEBUG:LinkStateId: 202.1.1.1.
*Sep
8 17:51:11:720 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 202.1.1.1.
*Sep
8 17:51:11:720 2006 RouterA RM/6/RMDEBUG:LSA Age: 1 Options: ExRouting:ON.
*Sep 8 17:51:11:731 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 80000002 CheckSum: 47803.
*Sep 8 17:51:11:731 2006 RouterA RM/6/RMDEBUG:Capabilities: VBit:0 EBit: 512 BBit: 256
NtBit: 0 Link# 1.
*Sep 8 17:51:11:731 2006 RouterA RM/6/RMDEBUG:LinkID: 150.1.1.1 LinkData: 150.1.1.2
LinkType: 2.
*Sep
8 17:51:11:741 2006 RouterA RM/6/RMDEBUG:TOS# 0 Metric 10.
// OSPF process 1 installed the Router-LSAs generated by the peer into the LSDB, with stub link changed
to transit link.
*Sep
8 18:00:27:660 2006 RouterA RM/6/RMDEBUG:OSPF 1: Install LSA at 5361645 ms:
*Sep
8 18:00:27:660 2006 RouterA RM/6/RMDEBUG:LSAType: 5.
*Sep
8 18:00:27:670 2006 RouterA RM/6/RMDEBUG:LinkStateId: 123.1.1.0.
*Sep
8 18:00:27:670 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 201.1.1.1.
*Sep
8 18:00:27:670 2006 RouterA RM/6/RMDEBUG:LSA Age: 0 Options: ExRouting:ON.
*Sep 8 18:00:27:680 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 80000001 CheckSum: 25377.
*Sep
8 18:00:27:680 2006 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0.
*Sep 8 18:00:27:680 2006 RouterA RM/6/RMDEBUG:TOS: 128 Metric: 001 FwdAddr 0.0.0.0 Tag
0.0.0.1.
// OSPF process 1 installed type-5 LSAs, and included the redistributed route 123.1.1.0 255.255.255.0.
# Enable debugging for LSA generation on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
•
On Router A, OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
<RouterA> debugging ospf lsa generate
<RouterA>
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:OSPF 1: Generate LSA at 6352610 ms:
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:LSAType: 1.
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:LinkStateId: 1.1.1.1.
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 1.1.1.1.
148
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:LSA Age: 0 Options: ExRouting:ON.
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 8000002c CheckSum: 3185.
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:Capabilities: VBit:0 EBit: 0 BBit: 0 NtBit:
0 Link# 1.
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:LinkID: 150.1.1.0 LinkData: 255.255.255.0
LinkType: 3.
*Dec 12 11:07:33:610 2006 RouterA RM/6/RMDEBUG:TOS# 0 Metric 10.
// The device generated router LSAs.
%Dec 12 11:07:33:708 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Loading to Full
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:OSPF 1: Generate LSA at 6357625 ms:
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:LSAType: 1.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:LinkStateId: 1.1.1.1.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:Advertising Rtr: 1.1.1.1.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:LSA Age: 0 Options: ExRouting:ON.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:Length: 36 Seq# 8000002d CheckSum: 44595.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:Capabilities: VBit:0 EBit: 0 BBit: 0 NtBit:
0 Link# 1.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:LinkID: 150.1.1.2 LinkData: 150.1.1.1
LinkType: 2.
*Dec 12 11:07:38:630 2006 RouterA RM/6/RMDEBUG:TOS# 0 Metric 10.
// The device generated router LSAs after the neighbor entered the FULL state.
debugging ospf mpls-te
Use debugging ospf mpls-te to enable debugging for OSPF MPLS traffic engineering.
Use undo debugging ospf mpls-te to disable debugging for OSPF MPLS traffic engineering.
Syntax
debugging ospf [ process-id ] mpls-te
undo debugging ospf [ process-id ] mpls-te
Default
Debugging for OSPF MPLS traffic engineering is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID, in the range of 1 to 65535.
Usage guidelines
If no process ID is specified, the MPLS traffic engineering debugging information of all the OSPF
processes will be displayed.
149
Examples
# Enable MPLS-TE debugging for OSPF on Router A. The output in this example was created when the
following conditions exist:
•
•
•
Router A is configured with MPLS TE, OSPF, and LDP. Loopback 0 is created on Router A, with an
IP address of 1.1.1.1/32. Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0
(150.1.1.2/24) on Router B over a broadcast network. On Router A:

OSPF process 1 is created and is enabled with Opaque.

Area 0 is created in OSPF process 1 and is enabled with TE.

Ethernet 1/0 is enabled with OSPF and is configured to belong to area 0.
Router B is also configured with MPLS TE, CSPF, and LDP. Loopback 0 is created on Router B, with
an IP address of 2.2.2.2/32. On Router B:

OSPF process 1 is created and is enabled with Opaque.

Area 0 is created in OSPF process 1 and is enabled with TE.

Ethernet 1/0 is enabled with OSPF and is configured to belong to area 0.
A TE tunnel interface is created on Router A, with an IP address of 6.1.1.1/24. The TE tunnel interface
runs MPLS TE and the destination is 2.2.2.2.
<RouterA> debugging ospf 1 mpls-te
150.1.1.2(Ethernet1/1) from Loading to Full
*Dec 20 15:01:37:86 2006 RouterA RM/6/RMDEBUG:OSPF TE
NSM_LoadingDone: LOADING DONE
*Dec 20 15:01:37:86 2006 RouterA RM/6/RMDEBUG:OSPF TE
HandleNeighborStateChg: BROADCAST
*Dec 20 15:01:37:86 2006 RouterA RM/6/RMDEBUG:OSPF TE
GetBroadCastNewGenNbr: Nbr DR, NbrIp = 2.2.2.2
*Dec 20 15:01:37:86 2006 RouterA RM/6/RMDEBUG:OSPF TE
GetBroadCastNewGenNbr: SUCCESS, MultiCastTeNbrID = 2.2.2.2
*Dec 20 15:01:37:86 2006 RouterA RM/6/RMDEBUG:OSPF TE
Received Link Info from RM
Process
: 1
Area
: 0.0.0.0
Link Type
: 4
TE Metric
: 0
Max BW
: 0
Max Resv BW : 0
Admin Grp
: 0
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
Link Id
: 150.1.1.2
Attached Rtr Count
: 2
Advtg Router ID
: 2.2.2.2
*Dec 20 15:01:37:86 2006 RouterA RM/6/RMDEBUG:OSPF TE
Send Network LSA to CSPF SUCCESS
Process ID
: 1
150
Area ID
: 0.0.0.0
Attached Rtr Count
: 2
MPLS DR Router ID
: 2.2.2.2
DR Intf Addr
: 150.1.1.2
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
Link Id
: 150.1.1.2
Attached Rtr Count
: 2
Advtg Router ID
: 2.2.2.2
*Dec 20 15:01:37:98 2006 RouterA RM/6/RMDEBUG:OSPF TE
Send Network LSA to CSPF SUCCESS
Process ID
: 1
Area ID
: 0.0.0.0
Attached Rtr Count
: 2
MPLS DR Router ID
: 2.2.2.2
DR Intf Addr
: 150.1.1.2
*Dec 20 15:01:37:118 2006 RouterA RM/6/RMDEBUG:OSPF TE
UpdateNetworkLsa - MODIFY
*Dec 20 15:01:37:118 2006 RouterA RM/6/RMDEBUG:OSPF TE
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
Link Id
: 150.1.1.2
Attached Rtr Count
: 2
Advtg Router ID
: 2.2.2.2
*Dec 20 15:01:37:118 2006 RouterA RM/6/RMDEBUG:OSPF TE
Send Network LSA to CSPF SUCCESS
Process ID
: 1
Area ID
: 0.0.0.0
Attached Rtr Count
: 2
MPLS DR Router ID
: 2.2.2.2
DR Intf Addr
: 150.1.1.2
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
Link Id
: 150.1.1.2
Attached Rtr Count
: 2
Advtg Router ID
: 2.2.2.2
*Dec 20 15:01:37:130 2006 RouterA RM/6/RMDEBUG:OSPF TE
Send Network LSA to CSPF SUCCESS
Process ID
: 1
151
Area ID
: 0.0.0.0
Attached Rtr Count
: 2
MPLS DR Router ID
: 2.2.2.2
DR Intf Addr
: 150.1.1.2
*Dec 20 15:01:37:130 2006 RouterA RM/6/RMDEBUG:OSPF TE
ReceiveOpqLsa: Processed Success
*Dec 20 15:01:40:194 2006 RouterA RM/6/RMDEBUG:OSPF TE
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
Link Id
: 3.1.1.2
Attached Rtr Count
: 2
Advtg Router ID
: 3.3.3.3
*Dec 20 15:01:50:194 2006 RouterA RM/6/RMDEBUG:OSPF TE
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
Link Id
: 3.1.1.2
Attached Rtr Count
: 2
Advtg Router ID
: 3.3.3.3
*Dec 20 15:01:52:194 2006 RouterA RM/6/RMDEBUG:OSPF TE
Received Network LSA by OSPF TE
Process ID
: 1
Area ID
: 0.0.0.0
debugging ospf non-stop-routing
Use debugging ospf non-stop-routing to enable OSPF NSR debugging.
Use undo debugging ospf non-stop-routing to disable OSPF NSR debugging.
Syntax
debugging ospf non-stop-routing
undo debugging ospf non-stop-routing
Default
OSPF NSR debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 5 describes output fields and messages for the debugging ospf non-stop-routing command.
152
Table 107 Output from the debugging ospf non-stop-routing command
Field
Description
Smooth start
Active/standby switchover started.
Smooth start on the interface
Active/standby switchover started on the interface.
Back up in real time removal
neighbor neighbor of interface index
in area area-id of process process-id
Back up in batches removal neighbor
neighbor of interface index in area
area-id of process process-id
HA acknowledge flushed lsa type:
type, advertising router: advrtr, link
ID: linkid
OSPF NSR is backing up the specified neighbor to be removed in real
time.
•
•
•
•
neighbor—Neighbor ID.
index—Logical index of the interface.
area-id—Area ID.
process-id—Process ID.
OSPF NSR is backing up the specified neighbor to be removed in
batches.
•
•
•
•
neighbor—Neighbor ID.
index—Logical index of the interface.
area-id—Area ID.
process-id—Process ID.
HA acknowledged deleting the LSA.
• type—LSA type.
• advrtr—Advertising router.
• linkid—Link ID.
HA acknowledged the same LSA type.
HA acknowledge the same lsa type:
type, advertising router: advrtr, link
ID: linkid, age: age, sequence
number: seq
•
•
•
•
•
type—LSA type.
advrtr—Advertising router.
linkid—Link ID.
age—LSA age.
seq—Sequence number.
HA acknowledged updating the LSA.
HA acknowledge update lsa type:
type, advertising router: advrtr, link
ID: linkid, age: age, sequence
number: seq
•
•
•
•
•
type—LSA type.
advrtr—Advertising router.
linkid—Link ID.
age—LSA age.
seq—Sequence number.
Examples
# Enable OSPF NSR debugging on Router A. The output in this example was created when the following
conditions exist:
•
•
On Router A, both the active MPU and standby MPU start. On Router A, OSPF process 1 is created
and area 0 is created in OSPF process 1.Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.

OSPF process 1 is created.

Area 0 is created in OSPF process 1.

Area 0 contains network 3.1.1.0/32, and Area 1 contains network 4.1.1.1.0/32.

Two OSPF interfaces are configured.
Router B is the neighbor of Router A and has similar configurations.
153
<RouterA> debugging ospf non-stop-routing
<RouterA> system-view
[RouterA] ospf non-stop-routing
*Apr 19 10:39:17:641 2010 RouterA RM/6/RMDEBUG: NSR: NSR configuration backed up
// NSR backed up configuration data.
*Apr 19 10:39:17:641 2010 RouterA RM/6/RMDEBUG: NSR: Interface data of instance 0 backs
up in batches
*Apr 19 10:39:17:641 2010 RouterA RM/6/RMDEBUG: NSR: Data of interface 6 backs up in batches
*Apr 19 10:39:17:641 2010 RouterA RM/6/RMDEBUG: NSR: Data of interface 5 backs up in batches
// NSR is backing up interface data in batches.
*Apr 19 10:39:17:766 2010 RouterA RM/6/RMDEBUG: NSR: backup in batches neighbor 0x3030303
of interface 152502416 in area 0 of process 1
*Apr 19 10:39:17:766 2010 RouterA RM/6/RMDEBUG: NSR: backup in batches neighbor 0x3030303
of interface 152503504 in area 1 of process 1
// NSR is backing up neighbor data in batches.
*Apr 19 10:39:17:828 2010 RouterA RM/6/RMDEBUG: NSR: Back up LSDB of instance 0 in batches
*Apr 19 10:39:17:828 2010 RouterA RM/6/RMDEBUG: NSR: Back up LSDB of process 1 in batches
*Apr 19 10:39:17:844 2010 RouterA RM/6/RMDEBUG: NSR: Back up retransmission list of
instance 0 in batches
// NSR is backing up LSDB of the process in batches.
*Apr 19 10:54:48:969 2010 RouterA RM/6/RMDEBUG: NSR: Back up configuration change of
process 1 in real time
// NSR is backing up changed configuration data of the process in real time.
*Apr 19 10:53:10:172 2010 RouterA RM/6/RMDEBUG: NSR: Back up configuration of area 1 in
real time
// NSR is backing up changed configuration data of the area in real time.
*Apr 19 10:45:03:110 2010 RouterA RM/6/RMDEBUG: NSR: Data of interface 5 backs up in real
time
*Apr 19 10:45:03:110 2010 RouterA RM/6/RMDEBUG: NSR: Back up in real time enable-state
of interface 5 in the area 0
// NSR is backing up interface data in real time.
*Apr 19 10:57:32:735 2010 RouterA RM/6/RMDEBUG: NSR:
0x3030303(7) of interface 6 in area 1 of process 1
Back up in real time neighbor
// NSR is backing up neighbor data in real time.
*Apr 19 10:57:34:422 2010 RouterA RM/6/RMDEBUG: NSR: Back up in real time neighbor 0x3030303
data change of interface 6 in area 1 of process 1
// NSR is backing up changed neighbor data in real time.
*Apr 19 10:45:03:110 2010 RouterA RM/6/RMDEBUG: NSR: Back up in real time removal neighbor
0x3030303 of interface 5 in area 0 of process 1
// NSR is backing up in real time the neighbor to be removed.
*Apr 19 10:45:08:813 2010 RouterA RM/6/RMDEBUG: NSR: Back up retransmission node in real
time: type:0x3, advertising router:0x301010b, link ID:0x3010100
// NSR is backing up the retransmission node in real time.
*Apr 19 11:03:29:703 2010 RouterA RM/6/RMDEBUG: NSR: Back up LSAs in real time type: 0x1,
advertising router: 0x3030303, link ID: 0x3030303, age: 0x1, sequence number:0x8000000a,
recvif:6,recvNbr:0x4010121
154
*Apr 19 11:03:29:719 2010 RouterA RM/6/RMDEBUG: NSR:
0x3030303(7) of interface 6 in area 1 of process 1
Back up in real time neighbor
*Apr 19 11:03:29:719 2010 RouterA RM/6/RMDEBUG: NSR: Back up LSAs in real time type: 0x2,
advertising router: 0x3030303, link ID: 0x4010121, age: 0x1, sequence number:0x80000001,
recvif:6,recvNbr:0x4010121
// NSR is backing up LSAs in real time.
*Apr 19 11:03:29:735 2010 RouterA RM/6/RMDEBUG: NSR: HA acknowledge the same lsa type:
0x2, advertising
// HA acknowledged the same LSA type.
debugging ospf packet
Use debugging ospf packet to enable OSPF packet debugging.
Use undo debugging ospf packet to disable OSPF packet debugging.
Syntax
debugging ospf [ process-id ] packet [ ack | dd | hello | request | update ] [ filter { destination | source }
{ acl-number | prefix ip-prefix-name } ]
undo debugging ospf packet [ ack | dd | hello | request | update ] [ filter { nbr | src } { acl-number |
prefix ip-prefix-name } ]
Default
OSPF packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
ack: Specifies debugging for LSAck packets.
dd: Specifies debugging for Database Description (DD) packets.
hello: Specifies debugging for hello packets.
request: Specifies debugging for LSR packets.
update: Specifies debugging for LSU packets.
filter: Specifies a filtering policy.
destination: Applies the filtering policy based on the destination IP address of the packets.
source: Applies the filtering policy based on the source IP address of the packets.
acl-number: Specifies an ACL by its number in the range of 2000 to 3999.
ip-prefix-name: Specifies an IP prefix list by its name, a string of 1 to 19 characters.
Usage guidelines
If no process ID is specified, the packet debugging information of all the OSPF processes will be
displayed.
155
Table 6 describes output fields and messages for the debugging ospf packet command.
Table 108 Output from the debugging ospf packet command
Field
Description
OSPF process-id
OSPF process ID.
SEND Packet
OSPF sent packets.
RECV Packet
OSPF received packets.
Source Address: src-addr
Source IP address of the OSPF packet.
Destination Address: dst-addr
Destination IP address of the OSPF packet.
OSPF packet header information:
• ver—OSPF version2.
• pkt-type—OSPF packet type:
Ver# ver, Type: pkt-type, Length: pkt-len

1—Hello.

2—DD.

3—LSR.

4—LSU.

5—LSAck.
• pkt-len—OSPF packet length.
OSPF packet header information:
• rt-id—ID of the advertising router.
• area-id—Area ID of the sending interface.
• chksum—Checksum of the entire packet starting
Router: rt-id, Area: area-id, Chksum: chksum
from the OSPF header, excluding the 64-bit
authentication field.
OSPF packet header information:
• au-type—OSPF packet authentication type:
AuType: auth-type, Key(ascii): key

00—Non-authentication.

01—Simple authentication.

02—MD5 authentication.
• key—Authentication key.
OSPF hello packet information:
• net-mask—Network mask of the sending
interface.
Net Mask: net-mask, Hello Int: hello-interval, Option:
opt
• hello-interval—Hello interval, in seconds.
• opt—Optional capabilities supported by the
router:



156
E bit means external route support.
The "N" and "P" in N/P bit mean NSSA
capability and Type 7 to Type 5 translation,
respectively.
L bit means the packet carries GR-related
extended data.
Field
Description
OSPF hello packet information:
Rtr Priority: rt-pri, Dead Int: dead-interval, DR: ip-addr,
BDR: ip-addr
• rt-pri—Router priority.
• dead-interval—Neighbor dead interval , in
seconds.
• ip-addr—IP address of the DR or BDR on the
interface network segment.
OSPF hello packet information.
Attached Neighbor: rt-id
rt-id indicates the router ID of the neighbor discovered
by OSPF.
OSPF hello packet information.
Hello: hello timer mismatch
Hello intervals of the router and the neighbor are
different.
OSPF hello packet information.
Hello: dead timer mismatch
Dead intervals of the router and the neighbor are
different.
OSPF hello packet information.
Hello: netmask mismatch
Network masks of the router and the neighbor are
different.
OSPF hello packet information.
Hello: extern option mismatch
The optional capability support of the router and that
of the neighbor are different.
OSPF hello and DD packet information.
opt indicates the GR-related options:
Extended Options(LLS Data): opt
• LR—OOB negotiation.
• RS—Notifying the neighbor to enter the GR
(Graceful Restart) state.
OSPF DD packet information. This argument can be a
combination of the following values:
• mtu-val—MTU on the interface, in bytes. It is 0 if
the MTU of the DD packets is not configured as that
of the sending interface.
• opt—Optional capabilities supported by the
router:


MTU:mtu-val, Option: opt, R_I_M_MS Bit: bits

E bit means external route support.
The "N" and "P" in N/P bit mean NSSA
capability and Type 7 to Type 5 translation,
respectively.
L bit means the packet carries GR-related
extended data.
• bits—DD packet negotiation bit:


157
I bit means the negotiation starts.
M bit means more DD packets are to be
exchanged.

MS bit means it is the master.

R bit means OOB negotiation begins.
Field
Description
OSPF DD packet information.
DD SeqNumber: seq-num
seq-num indicates the DD packet sequence number.
OSPF DD, LSR, and LSAck packet information.
Contents of the LSAs described in the OSPF packets:
• ls-type—LSA type:
LSAType: ls-type, LinkStateId: ls-id, Advertising Rtr:
rt-id

1 for Router LSA.

2 for network LSA.

3 for net-summary LSA.

4 for ASBR-summary LSA.

5 for AS-external–LSA.

7 for NSSA LSA.

9, 10, and 11 for Opaque LSA.
• ls-id—LSA link ID.
• rt-id—ID of the advertising router.
OSPF DD and LSAck packet information:
LSA Age: ls-age, Options: ExRouting:ON/OFF
• ls-age—LSA age.
• ON/OFF—Indicates whether the router supports
external routing.
OSPF DD and LSAck packet information:
Length: ls-len, Seq# seq-num, CheckSum: chksum
• ls-len—LSA packet length.
• seq-num—LSA sequence number.
• chksum—LSA checksum.
OSPF LSU packet information.
LSACount: ls-count
ls-count indicates the number of LSAs in the LSU
packet.
Examples
# Enable OSPF hello packet debugging on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
•
On Router A, OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
<RouterA> debugging ospf packet hello
<RouterA>
*0.68908828 RouterA RM/6/RMDEBUG:OSPF 1: SEND Packet.
*0.68908828 RouterA RM/6/RMDEBUG:Source Address: 150.1.1.1
*0.68908828 RouterA RM/6/RMDEBUG:Destination Address: 224.0.0.5
*0.68908828 RouterA RM/6/RMDEBUG:Ver# 2, Type: 1, Length: 44.
*0.68908828 RouterA RM/6/RMDEBUG:Router: 201.1.1.1, Area: 0.0.0.0, Chksum: 39833.
*0.68908828 RouterA RM/6/RMDEBUG:AuType: 00, Key(ascii): 0 0 0 0 0 0 0 0.
*0.68908828 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0, Hello Int: 10, Option: _E_.
158
*0.68908828 RouterA RM/6/RMDEBUG:Rtr Priority: 1, Dead Int: 40, DR: 150.1.1.1, BDR:
0.0.0.0.
// OSPF process 1 sent a hello packet. It has not found any neighbors.
*0.68913955 RouterA RM/6/RMDEBUG:OSPF 1: RECV Packet.
*0.68913955 RouterA RM/6/RMDEBUG:Source Address: 150.1.1.2
*0.68913965 RouterA RM/6/RMDEBUG:Destination Address: 224.0.0.5
*0.68913965 RouterA RM/6/RMDEBUG:Ver# 2, Type: 1, Length: 44.
*0.68913965 RouterA RM/6/RMDEBUG:Router: 202.1.1.1, Area: 0.0.0.0, Chksum: 12700.
*0.68913965 RouterA RM/6/RMDEBUG:AuType: 00, Key(ascii): 0 0 0 0 0 0 0 0.
*0.68913965 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0, Hello Int: 10, Option: _E_.
*0.68913965 RouterA RM/6/RMDEBUG:Rtr Priority: 1, Dead Int: 40, DR: 0.0.0.0, BDR: 0.0.0.0.
// OSPF process 1 received a hello packet from the peer end. The peer end had not found any
neighbors.
*0.68918832 RouterA RM/6/RMDEBUG:OSPF 1: SEND Packet.
*0.68918832 RouterA RM/6/RMDEBUG:Source Address: 150.1.1.1
*0.68918832 RouterA RM/6/RMDEBUG:Destination Address: 224.0.0.5
*0.68918842 RouterA RM/6/RMDEBUG:Ver# 2, Type: 1, Length: 48.
*0.68918842 RouterA RM/6/RMDEBUG:Router: 201.1.1.1, Area: 0.0.0.0, Chksum: 53394.
*0.68918842 RouterA RM/6/RMDEBUG:AuType: 00, Key(ascii): 0 0 0 0 0 0 0 0.
*0.68918842 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0, Hello Int: 10, Option: _E_.
*0.68918852 RouterA RM/6/RMDEBUG:Rtr Priority: 1, Dead Int: 40, DR: 150.1.1.1, BDR:
0.0.0.0.
*0.68918852 RouterA RM/6/RMDEBUG:Attached Neighbor: 202.1.1.1.
// OSPF process 1 sent a hello packet, which indicates the neighbor 202.1.1.1 has been found.
*0.68924260 RouterA RM/6/RMDEBUG:OSPF 1: RECV Packet.
*0.68924260 RouterA RM/6/RMDEBUG:Source Address: 150.1.1.2
*0.68924270 RouterA RM/6/RMDEBUG:Destination Address: 224.0.0.5
*0.68924270 RouterA RM/6/RMDEBUG:Ver# 2, Type: 1, Length: 48.
*0.68924270 RouterA RM/6/RMDEBUG:Router: 202.1.1.1, Area: 0.0.0.0, Chksum: 14735.
*0.68924280 RouterA RM/6/RMDEBUG:AuType: 00, Key(ascii): 0 0 0 0 0 0 0 0.
*0.68924280 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0, Hello Int: 10, Option: _E_
*0.68924280 RouterA RM/6/RMDEBUG:Rtr Priority: 1, Dead Int: 40, DR: 150.1.1.1, BDR:
150.1.1.2.
*0.68924280 RouterA RM/6/RMDEBUG:Attached Neighbor: 201.1.1.1.
// OSPF process 1 received a hello packet from the peer end. 150.1.1.1 and 150.1.1.2 are elected as DR
and BDR, respectively.
*0.68928827 RouterA RM/6/RMDEBUG:OSPF 1: SEND Packet.
*0.68928827 RouterA RM/6/RMDEBUG:Source Address: 150.1.1.1
*0.68928827 RouterA RM/6/RMDEBUG:Destination Address: 224.0.0.5
*0.68928837 RouterA RM/6/RMDEBUG:Ver# 2, Type: 1, Length: 48.
*0.68928837 RouterA RM/6/RMDEBUG:Router: 201.1.1.1, Area: 0.0.0.0, Chksum: 14735.
*0.68928837 RouterA RM/6/RMDEBUG:AuType: 00, Key(ascii): 0 0 0 0 0 0 0 0.
*0.68928837 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0, Hello Int: 10, Option: _E_.
*0.68928847 RouterA RM/6/RMDEBUG:Rtr Priority: 1, Dead Int: 40, DR: 150.1.1.1, BDR:
150.1.1.2.
*0.68928847 RouterA RM/6/RMDEBUG:Attached Neighbor: 202.1.1.1.
// OSPF process 1 sent a hello packet to maintain the neighbor relationship.
159
*0.68934274 RouterA RM/6/RMDEBUG:OSPF 1: RECV Packet.
*0.68934274 RouterA RM/6/RMDEBUG:Source Address: 150.1.1.2
*0.68934274 RouterA RM/6/RMDEBUG:Destination Address: 224.0.0.5
*0.68934284 RouterA RM/6/RMDEBUG:Ver# 2, Type: 1, Length: 48.
*0.68934284 RouterA RM/6/RMDEBUG:Router: 202.1.1.1, Area: 0.0.0.0, Chksum: 14735.
*0.68934284 RouterA RM/6/RMDEBUG:AuType: 00, Key(ascii): 0 0 0 0 0 0 0 0.
*0.68934284 RouterA RM/6/RMDEBUG:Net Mask: 255.255.255.0, Hello Int: 10, Option: _E_.
*0.68934294 RouterA RM/6/RMDEBUG:Rtr Priority: 1, Dead Int: 40, DR: 150.1.1.1, BDR:
150.1.1.2.
*0.68934294 RouterA RM/6/RMDEBUG:Attached Neighbor: 201.1.1.1.
// OSPF process 1 received a hello packet to maintain the neighbor relationship from the peer end.
debugging ospf spf
Use debugging ospf spf to enable OSPF SPF debugging.
Use undo debugging ospf spf to disable OSPF SPF debugging.
Syntax
debugging ospf [ process-id ] spf { all | brief | intra | { asbr-summary | ase | net-summary | nssa }
[ filter { acl acl-number | ip-prefix ip-prefix-name } ] }
undo debugging ospf [ process-id ] spf { all | asbr-summary | ase | brief | intra | net-summary | nssa }
Default
OSPF SPF debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
all: Specifies all the SPF scheduling and calculation debugging.
brief: Specifies SPF job scheduling debugging.
intra: Specifies SPF debugging for intra-area LSAs.
asbr-summary: Specifies SPF debugging for ASBR-Summary LSAs.
ase: Specifies SPF debugging for ASE LSAs.
net-summary: Specifies SPF debugging for inter-area LSAs.
nssa: Specifies SPF debugging for NSSA LSAs.
filter: Filters the SPF debugging output information.
acl acl-number: Specifies a basic ACL number, in the range of 2000 to 2999.
ip-prefix ip-prefix-name: Specifies an IP prefix list for the filtering. It is a string of 1 to 19 characters.
Usage guidelines
If no process ID is specified, the SPF debugging information of all the OSPF processes will be displayed.
160
Table 7 describes output fields and messages for the debugging ospf spf brief command.
Table 109 Output from the debugging ospf spf brief command
Field
Description
OSPF process-id
OSPF process ID.
SPF schedule event.
schedule-event: SPF schedule event. It can be
0x80000000, 0x40000000, 0x10000000,
0x00008000, 0x00004000, 0x00000020, or
0x00000010.
Schedule Event: schedule-event at X ms
SPF schedule flag indicating SPF is scheduled.
schedule-flag: Schedule flag. It can be 0x80000000,
0x40000000, 0x20000000, 0x10000000,
0x08000000, 0x00008000, 0x00004000,
0x00002000, 0x00001000, 0x00000080,
0x00000020, or 0x00000010.
Schedule Flag: schedule-flag SPF is Scheduled
Schedule flag indicating SPF is stopped.
schedule-flag: Schedule flag. It can be 0x80000000,
0x40000000, 0x20000000, 0x10000000,
0x08000000, 0x00008000, 0x00004000,
0x00002000, 0x00001000, 0x00000080,
0x00000020, or 0x00000010.
Schedule Flag: schedule-flag SPF is Stopped
Present SPF schedule flag.
schedule –flag: Schedule flag. It can be
0x80000000, 0x40000000, 0x20000000,
0x10000000, 0x08000000, 0x00008000,
0x00004000, 0x00002000, 0x00001000,
0x00000080, 0x00000020, or 0x00000010.
Pre Proc: Schedule: schedule -flag
Present SPF calculation flag.
running –flag: Running flag. It can be 0x80000000,
0x40000000, 0x20000000, 0x10000000,
0x08000000, 0x00008000, 0x00004000,
0x00002000, 0x00001000, 0x00000080,
0x00000040, 0x00000020, 0x00000008,
0x00000004. It can also be a combination of these
values.
Pre Proc: Running: running-flag
FRR SPF Calc On Nbr Begin
In FRR auto-mode, an SPF route computation began
with the root as a neighboring node.
FRR SPF Calc On Nbr End
In FRR auto-mode, an SPF route computation ended
with the root as a neighboring node.
FRR Inter-Area ASBR Route Calc On Nbr Begin
In FRR auto-mode, an inter-area ASBR route
computation began with the root as a neighboring
node.
FRR Inter-Area ASBR Route Calc On Nbr End
In FRR auto-mode, an inter-area ASBR route
computation ended with the root as a neighboring
node.
FRR Intra-Area RtrRoute BkNextHop Calc Begin
In FRR auto-mode, the calculation for the backup next
hop of intra-area routes of the router type began.
161
Field
Description
FRR Intra-Area RtrRoute BkNextHop Calc End
In FRR auto-mode, the calculation for the backup next
hop of intra-area routes of the router type ended.
FRR Inter-Area RtrRoute BkNextHop Calc Begin
In FRR auto-mode, the calculation for the backup next
hop of inter-area routes of the router type began.
FRR Inter-Area RtrRoute BkNextHop Calc End
In FRR auto-mode, the calculation for the backup next
hop of inter-area routes of the router type ended.
FRR Intra-AS NetRoute BkNextHop Calc Begin
In FRR auto-mode, the calculation for the backup next
hop of intra-area and inter-area routes of the network
type began.
FRR Intra-AS NetRoute BkNextHop Calc End
In FRR auto-mode, the calculation for the backup next
hop of intra-area and inter-area routes of the network
type ended.
FRR Inter-AS NetRoute BkNextHop Calc Begin
In FRR auto-mode, the calculation for the backup next
hop of routes of the ASE and NSSA types began.
FRR Inter-AS NetRoute BkNextHop Calc End
In FRR auto-mode, the calculation for the backup next
hop of routes of the ASE and NSSA types ended.
ISPF-CALC: Area area-id ISPF Calculate Start at time
ms
ISPF-CALC: Area area-id ISPF Calculate End at time
ms
ISPF computation in the area starts.
• area-id—Area ID.
• time—Start time.
ISPF computation in the area ends.
• area-id—Area ID.
• time—End time.
ISPF full computation in the area was performed.
ISPF-CALC: Area area-id NOMAL FULL ISPF
area-id indicates the area ID.
ISPF TE Full computation in the area was performed.
ISPF-CALC: Area area-id TE FULL ISPF
area-id indicates the area ID.
ISPF subtree computation in the area was performed.
ISPF-CALC: Area area-id SUBTREE ISPF
area-id indicates the area ID.
ISPF initialization in the area was performed.
ISPF-CALC: Area area-id INIT ISPF
area id indicates the area ID.
ISPF deinitialization in the area was performed.
ISPF-CALC: Area area-id UNINIT ISPF
area-id indicates the area ID.
ISPF topology detection in the area was performed.
ISPF-CALC: Area area-id ISPF Topo Detect
area-id indicates the area ID.
Table 8 describes output fields and messages for the debugging ospf spf intra command.
Table 110 Output from the debugging ospf spf intra command
Field
Description
OSPF process-id
OSPF process ID.
SPF calculation in area area-id started.
Process (Intra) Area area-id
area-id indicates the area ID.
162
Field
Description
Add root to area area-id Candidate List
OSPF added the root node to the candidate list of SPF
calculation in area area-id.
Information of the router LSA associated with
candidate nodes:
• link-id—Link ID of the router LSA.
• rt-id—ID of the advertising router.
• link-count—Number of links in the router LSA.
Rtr-LSA link-id, adv rt-id, link count link-count
Information of the network LSA associated with
candidate nodes:
Net-LSA link-id, adv rt-id, router count : rt-count
• link-id—Link ID of the network LSA.
• rt-id—ID of the advertising router.
• rt-count—Number of routers listed in the network
LSA.
Description of each link in the router LSA:
• link-type—Link type. It can be P-2-P, TransNet,
StubNet, or Virtual.
link-type Link link-id, Data link-data, cost cost
• link-id—Link ID.
• link-data—Link data.
• cost—Link cost.
Neighbor described in the network LSA.
Attach Router: router-id
router-id indicates the ID of the router.
Reasons for dropping a candidate node:
•
•
•
•
•
•
•
•
•
•
•
Drop for reason
Maxage.
Not found neighbor.
Cost exceeds LSInfinity.
No back link.
Check neighbor in SPF tree fail.
In spf tree.
Next hop calculation fail.
No next hop.
Add into candidate list fail.
Find candidate list fail.
Old vertex is better.
Reasons for dropping a candidate node (router node).
• link-id—Link ID of the router LSA.
• reason—Reason for dropping the node.
Drop neighbor Rtr-Lsa link-id for reason
Reasons for dropping a candidate node (network
node).
Drop neighbor Net-Lsa link-id net-mask for reason
163
• link-id—Link ID of the network LSA.
• net-mask—Network mask in the network LSA.
• reason—Reason for dropping the node.
Field
Description
Operation on the current candidate node (router
node).
• op-type—Type of operation to perform on the
op-type vertex:Rtr-Lsa link-id, Cost to root cost, Nh
next-hop
candidate node. It can be Add, Update, Remove,
or Get.
• link-id—Link ID of the router LSA.
• cost—Cost to the root node.
• next-hop—Next hop.
Operation on the current candidate node (network
node).
• op-type—Type of operation to perform on the
op-type vertex:Net-Lsa link-id net-mask, Cost to root
cost, Nh next-hop
Can't find old route
candidate node. It can be Add, Update, Remove,
or Get.
•
•
•
•
link-id—Link ID of the router LSA.
net-mask—Network mask in the network LSA.
cost—Cost to the root node.
next-hop—Next hop.
There is no such route in the routing table.
Operation on the routing table entry.
• op-type—Type of operation to perform on the
candidate node. It can be Add, Update, Remove,
or Get.
op-type path-type route dest-ip net-mask, nh next-hop,
cost cost
• path-type—Route type. It can be unrecognized,
intra-area, transit, stub, inter-area, ase, type1, or
type2.
• dest-ip—Destination IP address.
• next-hop—Next hop.
• cost—Path cost.
The corresponding original route is found.
Find old route for net- addr /mask-len *route-type
route,nh next-hop,cost cost
•
•
•
•
•
net-addr—Network address.
mask-len—Length of IP address mask.
route-type—Route type. It can be transit or stub.
next-hop—Next hop.
cost—Route cost.
Operation on the router route.
• op-type—Operation type. It can be Old, Add, or
Update.
• route-type—Route type. It can be ABR, ASBR,
op-type rotue-type route, cost cost, nh next-hop
ABR/ASBR, or Rtr.
• cost—Path cost.
• next-hop—Next hop.
Stub route information:
Stub Route: DEST: dest-addr MASK: mask-len, cost:
cost
164
• dest-addr—Destination network address.
• mask-len—Network mask length.
• cost—Route cost.
Field
Description
Add nexthop next-hop to candidate nexthop list
In FRR auto-mode, a next hop is added to the
candidate next hop list.
In FRR auto-mode, the candidate next hop is
processed.
• next-hop—Candidate next hop address.
• nbr-id—Router ID of the neighbor corresponding
Candidate nexthop next-hop, Nbr nbr-id
to the candidate next hop.
In FRR auto-mode, the candidate next hop is
processed.
• next-hop—Candidate next hop address.
• area-id—ID of the area to which the primary next
Area area-id Get candidate nexthop next-hop
hop belongs.
In FRR auto-mode, the attribute of the old backup next
hop is listed.
• next-hop—Backup next hop address.
• attr-list—List to which the route belongs:
Old BkNexthop next-hop, attr-list

link—Link protection.

node—Node protection.

primary—Primary next hop.
In FRR auto-mode, the attribute of the current
candidate next hop is listed.
• next-hop—Backup next hop address.
• attr-list—List to which the route belongs:
Candidate nexthop next-hop, attr-list
165

link—Link protection.

node—Node protection.

primary—Primary next hop.
Field
Description
In FRR auto-mode, the candidate next hop is selected
because it is more optimal than the old backup next
hop.
The reasons why the candidate next hop is selected as
the route backup next hop include the following:
Candidate nexthop reason, update backup nexthop
•
•
•
•
•
•
•
Is loop-free.
Is primary.
Is node-protect.
Is link-protect.
Is downstream.
Is closer to destination.
Has smaller IP address.
In FRR auto-mode, the old backup next hop is reserved
because it is more optimal than the candidate next
hop.
The reasons why the candidate next hop is discarded
include the following:
Candidate nexthop reason, drop candidate nexthop
•
•
•
•
•
•
•
Is not loop-free.
Is not primary.
Is not node-protect.
Is not link-protect.
Is not downstream.
Is not closer to destination.
Has larger IP address.
In FRR auto-mode, the result of calculating the backup
next hop for intra-area routes of the router type is
listed.
• router-route-type—Router type, which can be
router-rotue-type route, dest dest-id ,nh next-hop,bnh
backup-next-hop ,attr-list
net-rotue-type route, dest-id /mask-len,Inherit backup
nexthop
ABR, ASBR, ABR/ASBR, or Rtr.
•
•
•
•
dest-id—Destination IP address.
next-hop—Next hop address.
backup-next-hop—Backup next hop address.
attr-list—List to which the route belongs. The value
can be link (link protection), node (node
protection), or primary (primary next hop).
In FRR auto-mode, the intra-area routes of the network
type inherit the backup next hop of the router-type
routes of the corresponding advertiser.
• net-route-type—Network type, which can be
Transit or Stub.
• dest-id—Destination IP address.
• mask-len—Mask length.
166
Field
Description
In FRR auto-mode, the result of calculating the backup
next hop for intra-area routes of the network type is
listed.
• net-route-type—Network type, which can be
Transit or Stub.
•
•
•
•
•
net-rotue-type route, dest-id /mask-len, nh
next-hop,bnh backup-next-hop ,attr-list
dest-id—Destination IP address.
mask-len—Mask length.
next-hop—Next hop address.
backup-next-hop—Backup next hop address.
attr-list—List to which the route belongs. The value
can be link (link protection), node (node
protection), or primary (primary next hop).
ISPF-VERT: Drop for Add into Candidate List Fail
Node dropped due to failure in adding into the
candidate list.
ISPF-VERT: Drop for TE link in nomal calc
Node dropped due to full computation for a TE link.
ISPF-VERT: Drop for TENT: nbr node not found
Node dropped due to neighbor node not found.
ISPF-NODE: Type: Type_id, Adv:Adv_id, Ls ID:Ls_ID
SPF node type, advertising router, and LS ID.
ISPF-NODE: Process CandList Node
Process candidate SPF node.
ISPF-NODE: Calc the child node
Compute the child SPF node.
Current router LSA node being processed.
ISPF-VERT: action vertex:Rtr-node node_id, Cost to
root cost, Nexthop Count:count, Nh nexthop
•
•
•
•
•
action—Add, update, remove, or get.
node_id—Node ID.
cost—Node cost.
count—Number of next hops.
nexthop—Next hop address.
Current network LSA node being processed.
ISPF-VERT: action vertex:Net-node node_id/mask,
Cost to root cost, Nexthop Count count, Nh nexthop
•
•
•
•
•
action—Add, update, remove, or get.
node_id/mask—Node ID/mask.
cost—Node cost.
count—Number of next hops.
nexthop—Next hop address.
Table 9 describes output fields and messages for the debugging ospf spf ase command.
Table 111 Output from the debugging ospf spf ase command
Field
Description
OSPF process-id
OSPF process ID.
Total route number less then maximum, the spf will be
rescheduled
Some routes were deleted to reduce the total route
number to be below the upper limit. SPF is now
rescheduled.
Process (Ase)
ASE SPF calculation started.
Start (Incr ASE)
Incremental ASE calculation started.
167
Field
Description
FULL SPF ASE Begin at bucket bucket-num
Full ASE SPF calculation began at bucket bucket-num
in the Hash table.
FULL SPF ASE Stop at bucket bucket-num
Full ASE SPF calculation stopped at bucket bucket-num
in the Hash table.
INCR SPF ASE Begin
Incremental ASE SPF began.
INCR SPF ASE End
Incremental ASE SPF ended.
LSA ID inconsistent with netmas. LSID: ls-id, Netmask:
net-mask
ASE LSA ID and network mask are inconsistent.
MaxAge and No associated route, flush and delete
ASE LSA
Flush or delete the ASE LSAs that are aged out or have
no associated routes.
ASE LSA cost is infinity, don't calculate
ASE LSA cost is infinite. It will not be calculated.
In FRR auto-mode, the routes of the ASE type inherit the
backup next hop of the following routes:
ASE net route, dest-id /mask-len,Inherit backup
nexthop
• Router type routes of the corresponding advertiser.
• Network type routes corresponding to the
forwarding address.
Parameter description:
• dest-id—Destination IP address.
• mask-len—Mask length.
In FRR auto-mode, the result of calculating the backup
next hop for routes of the ASE type is listed.
ASE net route, dest-id /mask-len, nh next-hop,bnh
backup-next-hop ,attr-list
•
•
•
•
•
dest-id—Destination IP address.
mask-len—Mask length.
next-hop—Next hop address.
backup-next-hop—Backup next hop address.
attr-list—List to which the route belongs. The value
can be link (link protection), node (node
protection), or primary (primary next hop).
Examples
# Enable debugging for OSPF job scheduling. The output in this example was created when the
following conditions exist:
•
Ethernet1/0 (3.3.3.2/24) on Router B is connected to Ethernet1/0 (3.3.3.1/24) on Router A over
a broadcast network.
•
Ethernet1/1 (4.4.4.1/24) on Router B is connected to Ethernet1/0 (4.4.4.2/24) on Router C over
a broadcast network.
•
OSPF process 1 is created on Router B. Area 0 and area 1 are created in OSPF process 1. OSPF
is enabled on Ethernet 1/0, which is configured to belong to area 0. OSPF is enabled on Ethernet
1/1, which is configured to belong to area 1.
•
OSPF process 1 is created on Router A. Area 0 is created in OSPF process 1. OSPF is enabled on
Ethernet 1/0, which is configured to belong to area 0.
•
OSPF process 1 is created on Router C. Area 1 is created in OSPF process 1. OSPF is enabled on
Ethernet 1/0, which is configured to belong to area 1.
•
On Router A, enable FRR to automatically calculate a backup next hop.
168
When you restart OSPF process 1, output similar to the following example is generated:
<RouterA>debugging ospf spf brief
<RouterA>reset ospf 1 process
Warning : Reset OSPF process? [Y/N]:
OSPF 1 Schedule Event: 0x80000000 at 1200641 ms.
// Event triggering the SPF schedule.
OSPF 1 SPF Intra Area Full Schedule
// Full SPF calculation schedule.
OSPF 1 Schedule Flag : 0x80000000 SPF is scheduled.
// SPF schedule flag.
OSPF 1 Schedule Event: 0x80000000 at 1200641 ms.
OSPF 1 SPF Intra Area Full Schedule
OSPF 1 Schedule Flag : 0x80000000 SPF is scheduled.
OSPF 1 Schedule Event: 0x00008000 at 1201422 ms.
OSPF 1 Schedule Event: 0x10000000 at 1201422 ms.
OSPF 1 Schedule Flag : 0x80000000 SPF is scheduled.
OSPF 1 Remove Unreachable Rts
// OSPF is deleting unreachable routes.
OSPF 1 Schedule Event: 0x80000000 at 1203750 ms.
OSPF 1 SPF Intra Area Full Schedule
OSPF 1 Schedule Flag : 0x80000000 SPF is scheduled.
OSPF 1 Pre Proc : Schedule: 0x80000000.
// Current SPF schedule flag.
OSPF 1 Pre Proc : Running : 0xF8000084.
// Current SPF calculation flag.
OSPF 1 *************SPF Start (Full) at 1205625 ms*************
// Full SPF calculation.
OSPF 1 **** Process (Intra) Area 0.0.0.0. ****
// OSPF is processing intra-area SPF calculation.
OSPF 1 SPF running Inter area Begin
// Inter-area SPF calculation began.
OSPF 1 SPF running Inter area end
// Inter-area SPF calculation ended.
OSPF 1 SPF running Inter area Begin
OSPF 1 SPF running Inter area end
OSPF 1 Remove Unreachable Rts
OSPF 1 SPF running ASE Begin
// ASE SPF calculation began.
OSPF 1 SPF running ASE end
// ASE SPF calculation ended.
OSPF 1 SPF deletes Inter AS unreachable routes Begin
// OSPF began deleting inter-AS unreachable routes.
OSPF 1 Remove Unreachable Rts
169
// OSPF is deleting unreachable routes.
OSPF 1 SPF deletes Inter AS unreachable routes end
// OSPF finished deleting inter-AS unreachable routes.
OSPF 1 **** FRR SPF Calc On Nbr Begin ****
// SPF route computation began. The root is the neighboring node.
OSPF 1 **** Process (Intra) Area 0.0.0.0. ****
// OSPF is processing SPF route computation in area 0. The root is the neighboring node.
OSPF 1 **** FRR SPF Calc On Nbr End ****
// SPF route computation ended. The root is the neighboring node.
OSPF 1 **** FRR Inter-Area ASBR Route Calc On Nbr Begin ****
// Inter-area ASBR route computation began. The root is the neighboring node.
OSPF 1 **** FRR Inter-Area ASBR Route Calc On Nbr End ****
// Inter-area ASBR route computation ended. The root is the neighboring node.
OSPF 1 **** FRR Intra-Area RtrRoute BkNextHop Calc Begin ****
// Calculation for the backup next hop of intra-area routes of the router type began.
OSPF 1 **** FRR Intra-Area RtrRoute BkNextHop Calc End ****
// Calculation for the backup next hop of intra-area routes of the router type ended.
OSPF 1 **** FRR Inter-Area RtrRoute BkNextHop Calc Begin ****
// Calculation for the backup next hop of inter-area routes of the router type began.
OSPF 1 **** FRR Inter-Area RtrRoute BkNextHop Calc End ****
// Calculation for the backup next hop of inter-area routes of the router type ended.
OSPF 1 **** FRR Intra-AS NetRoute BkNextHop Calc Begin ****
// Calculation for the backup next hop of intra-area and inter-area routes of the network type began.
OSPF 1 **** FRR Intra-AS NetRoute BkNextHop Calc End ****
// Calculation for the backup next hop of intra-area and inter-area routes of the network type ended.
OSPF 1 **** FRR Inter-AS NetRoute BkNextHop Calc Begin ****
// Calculation for the backup next hop of routes of the ASE and NSSA types began.
OSPF 1 **** FRR Inter-AS NetRoute BkNextHop Calc End ****
// Calculation for the backup next hop of routes of the ASE and NSSA types ended.
OSPF 1 *************SPF End at 1205641 ms*************
// SPF calculation ended.
# Enable SPF debugging for OSPF intra-area LSAs. The output in this example was created when the
following conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B.
•
On Router A, OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
•
On Router A, enable FRR to automatically calculate a backup next hop.
<RouterA>debugging ospf spf intra
%Dec 12 11:23:03:708 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Loading to Full
170
OSPF 1 Add root to area 0.0.0.0 Candidate List.
// OSPF added the root node to the candidate list of SPF calculation in area area-id.
OSPF 1 Get vertex:Rtr-Lsa 1.1.1.1, Cost to root 0,Nh
OSPF 1 Rtr-LSA 1.1.1.1,adv 1.1.1.1,link count 1
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.1,Cost 10
Add vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
// OSPF added a candidate node.
OSPF 1 Get vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1
OSPF 1
Find old route for 150.1.1.0/24EBUG:
*transit route,nh 150.1.1.1,cost 10,id 29
OSPF 1
New route is better
OSPF 1
Update transit route 150.1.1.0/24,Nh 150.1.1.1,cost 10
// OSPF updated a new route.
OSPF 1 Net-LSA 150.1.1.2,adv 2.2.2.2,router count 2
OSPF 1
Attach Router 1.1.1.1
:
OSPF 1
Attach Router 2.2.2.2
:
OSPF 1 Calculate the leaf network
OSPF 1 Router Type
Dest:2.2.2.2
OSPF 1 Add root to area 0.0.0.0 Candidate List.
OSPF 1 Get vertex:Rtr-Lsa 1.1.1.1, Cost to root 0,Nh
OSPF 1 Rtr-LSA 1.1.1.1,adv 1.1.1.1,link count 1
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.1,Cost 10
Add vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1 Get vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1
OSPF 1
Find old route for 150.1.1.0/24EBUG:
*transit route,nh 150.1.1.1,cost 10,id 29
OSPF 1
New route is better
OSPF 1
Update transit route 150.1.1.0/24,Nh 150.1.1.1,cost 10
OSPF 1 Net-LSA 150.1.1.2,adv 2.2.2.2,router count 2
OSPF 1
Attach Router 1.1.1.1
G:
OSPF 1
Attach Router 2.2.2.2
G:
OSPF 1
Add nexthop 150.1.1.2 to candidate nexthop list
// OSPF added the next hop to the candidate next hop list.
OSPF 1
Add vertex:Rtr-Lsa 2.2.2.2, Cost to root 10,Nh 150.1.1.2
OSPF 1 Get vertex:Rtr-Lsa 2.2.2.2, Cost to root 10,Nh 150.1.1.2
OSPF 1
Can't find Rtr route001 RM/6/RMDEBUG:
OSPF 1
Add ABR/ASBR route,cost 10,Nh 150.1.1.2
// OSPF added an ABR/ASBR route.
OSPF 1 Rtr-LSA 2.2.2.2,adv 2.2.2.2,link count 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.2,Cost 10
OSPF 1 Calculate the leaf network.
// OSPF calculated the leaf network.
OSPF 1 ** Candidate nexthop 150.1.1.2, Nbr 2.2.2.2 **
OSPF 1 Add root to area 0.0.0.0 Candidate List.
OSPF 1 Get vertex:Rtr-Lsa 2.2.2.2, Cost to root 0,Nh
OSPF 1 Rtr-LSA 2.2.2.2,adv 2.2.2.2,link count 1
171
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.2,Cost 1
Add vertex:Net-Lsa 150.1.1.2/24,Cost to root 1,Nh
OSPF 1 Get vertex:Net-Lsa 150.1.1.2/24,Cost to root 1,Nh
OSPF 1
Add transit route 150.1.1.0/24,Nh 0.0.0.0,cost 1
OSPF 1 Net-LSA 150.1.1.2,adv 2.2.2.2,router count 2
OSPF 1
OSPF 1
OSPF 1
OSPF 1
Attach Router 1.1.1.1
Add vertex:Rtr-Lsa 1.1.1.1, Cost to root 1,Nh
Attach Router 2.2.2.2
Drop neighbor Rtr-Lsa 2.2.2.2 for in spf tree
OSPF 1 Get vertex:Rtr-Lsa 1.1.1.1, Cost to root 1,Nh
OSPF 1
Add Rtr route 1.1.1.1,cost 1 G:
OSPF 1 Rtr-LSA 1.1.1.1,adv 1.1.1.1,link count 1
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.1,Cost 1
Drop neighbor Net-Lsa 150.1.1.2/24 for in spf tree
// OSPF is performing SPF computation on the neighbor corresponding to the candidate next hop.
OSPF 1 ** Candidate nexthop 150.1.1.2, Nbr 2.2.2.2 **
OSPF 1 ASBR route, dest 2.2.2.2,nh 150.1.1.2
OSPF 1
ASBR route, dest 2.2.2.2,nh 150.1.1.2,bnh 0.0.0.0
// OSPF is calculating the backup next hop of intra-area routes of the router type.
# Enable SPF debugging for OSPF inter-area LSAs. The output in this example was created when the
following conditions exist:
•
Ethernet1/0 (150.1.1.2/24) on Router B is connected to Ethernet1/0 (150.1.1.1/24) on Router A over
a broadcast network.
•
Ethernet1/1 (4.4.4.1/24) on Router B is connected to Ethernet1/0 (4.4.4.2/24) on Router C over
a broadcast network.
•
OSPF process 1 is created on Router B. Area 0 and area 1 are created in OSPF process 1. OSPF
is enabled on Ethernet 1/0, which is configured to belong to area 0. OSPF is enabled on Ethernet
1/1, which is configured to belong to area 1.
•
OSPF process 1 is created on Router A. Area 0 is created in OSPF process 1. OSPF is enabled on
Ethernet 1/0, which is configured to belong to area 0.
•
OSPF process 1 is created on Router C. Area 1 is created in OSPF process 1. OSPF is enabled on
Ethernet 1/0, which is configured to belong to area 1. Secondary addresses 1.1.1.1/24, 1.1.2.1/24,
1.1.3.1/24, and 1.1.4.1/24 are configured on Ethernet 1/0.
•
On Router A, enable FRR to automatically calculate the backup next hop.
<RouterA>debugging ospf spf net-summary
OSPF 1 Add root to area 0.0.0.0 Candidate List.
OSPF 1 Get vertex:Rtr-Lsa 1.1.1.1, Cost to root 0,Nh
OSPF 1 Rtr-LSA 1.1.1.1,adv 1.1.1.1,link count 1
OSPF 1 Calculate the leaf network.
OSPF 1 Stub Rt 150.1.1.0/24,Cost:10
OSPF 1
OSPF 1
Find old route for 150.1.1.0/24BUG:
*transit route,nh 150.1.1.1,cost 10,id 29
OSPF 1
New route is better
OSPF 1
Update stub route 150.1.1.0/24,Nh 150.1.1.1,cost 10
OSPF 1 Candidate list empty,SPF Area 0.0.0.0 finish.
OSPF 1 SPF area 0.0.0.0 running network summary
172
OSPF 1 NetSum-LSA 4.4.4.0/24 Adv 2.2.2.2 cost 10
OSPF 1 Don't calculate for route falling into active ABR range
OSPF 1 Router Type
Dest:3.3.3.3
OSPF 1 Router Type
Dest:2.2.2.2
OSPF 1
Delete Route Dest:4.4.4.0/24 Id:42 from RM
OSPF 1
Nexthop: 150.1.1.2 (Ethernet1/0)
OSPF 1
Delete OSPF inter-area Route:4.4.4.0/24 ID:42
OSPF 1
Delete Route Dest:11.11.11.0/24 Id:43 from RM
OSPF 1
OSPF 1
Nexthop: 150.1.1.2 (Ethernet1/0)
Delete OSPF type2
Route:11.11.11.0/24 ID:43
%Dec 12 11:43:30:924 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Loading to Full
OSPF 1 Add root to area 0.0.0.0 Candidate List.
OSPF 1 Get vertex:Rtr-Lsa 1.1.1.1, Cost to root 0,Nh
OSPF 1 Rtr-LSA 1.1.1.1,adv 1.1.1.1,link count 1
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.1,Cost 10
Add vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1 Get vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1
OSPF 1
Find old route for 150.1.1.0/24EBUG:
*stub route,nh 150.1.1.1,cost 10,id 29
OSPF 1
New route is better
OSPF 1
Update transit route 150.1.1.0/24,Nh 150.1.1.1,cost 10
OSPF 1 Net-LSA 150.1.1.2,adv 2.2.2.2,router count 2
OSPF 1
OSPF 1
OSPF 1
OSPF 1
Attach Router 1.1.1.1
G:
Drop neighbor Rtr-Lsa 1.1.1.1 for no back link
Attach Router 2.2.2.2
G:
Drop neighbor Rtr-Lsa 2.2.2.2 for no back link
OSPF 1 Calculate the leaf network.
OSPF 1 Candidate list empty,SPF Area 0.0.0.0 finish.
OSPF 1 SPF area 0.0.0.0 running network summary
OSPF 1 NetSum-LSA 4.4.4.0/24 Adv 2.2.2.2 cost 10
OSPF 1 Don't calculate for route falling into active ABR range
OSPF 1 Add root to area 0.0.0.0 Candidate List.
OSPF 1 Get vertex:Rtr-Lsa 1.1.1.1, Cost to root 0,Nh
OSPF 1 Rtr-LSA 1.1.1.1,adv 1.1.1.1,link count 1
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.1,Cost 10
Add vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1 Get vertex:Net-Lsa 150.1.1.2/24,Cost to root 10,Nh 150.1.1.1
OSPF 1
OSPF 1
Find old route for 150.1.1.0/24EBUG:
*transit route,nh 150.1.1.1,cost 10,id 29
OSPF 1
New route is better
OSPF 1
Update transit route 150.1.1.0/24,Nh 150.1.1.1,cost 10
OSPF 1 Net-LSA 150.1.1.2,adv 2.2.2.2,router count 2
OSPF 1
OSPF 1
OSPF 1
Attach Router 1.1.1.1
G:
Drop neighbor Rtr-Lsa 1.1.1.1 for in spf tree
Attach Router 2.2.2.2
G:
173
OSPF 1
Add vertex:Rtr-Lsa 2.2.2.2, Cost to root 10,Nh 150.1.1.2
OSPF 1 Get vertex:Rtr-Lsa 2.2.2.2, Cost to root 10,Nh 150.1.1.2
OSPF 1
Can't find Rtr route001 RM/6/RMDEBUG:
OSPF 1
Add ABR/ASBR route,cost 10,Nh 150.1.1.2
OSPF 1 Rtr-LSA 2.2.2.2,adv 2.2.2.2,link count 1
OSPF 1
OSPF 1
TransNet Link 150.1.1.2,Data 150.1.1.2,Cost 10
Drop neighbor Net-Lsa 150.1.1.2/24 for in spf tree
OSPF 1 Calculate the leaf network.
OSPF 1 Candidate list empty,SPF Area 0.0.0.0 finish.
OSPF 1 SPF area 0.0.0.0 running network summary
OSPF 1 NetSum-LSA 4.4.4.0/24 Adv 2.2.2.2 cost 10
OSPF 1 Don't calculate for route falling into active ABR range
OSPF 1 NetSum-LSA 4.4.4.0/24 Adv 2.2.2.2 cost 10
OSPF 1 New route is better
OSPF 1
OSPF 1
Add new Rt 4.4.4.0/24
Nexthop: 150.1.1.2 (Ethernet1/0)
OSPF 1 New route is better
OSPF 1
OSPF 1
Add new Rt 11.11.11.0/24
Nexthop: 150.1.1.2 (Ethernet1/0)
// OSPF performed net-summary calculation.
OSPF 1 Inter area net route,1.1.4.0/24,nh 150.1.1.2
OSPF 1
Inter area net route,1.1.4.0/24,Inherit backup nexthop
OSPF 1
Inter area net route,1.1.4.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 Inter area net route,4.4.4.0/24,nh 150.1.1.2
OSPF 1
Inter area net route,4.4.4.0/24,Inherit backup nexthop
OSPF 1
Inter area net route,4.4.4.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 Inter area net route,1.1.1.0/24,nh 150.1.1.2
OSPF 1
Inter area net route,1.1.1.0/24,Inherit backup nexthop
OSPF 1
Inter area net route,1.1.1.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 Inter area net route,1.1.2.0/24,nh 150.1.1.2
OSPF 1
Inter area net route,1.1.2.0/24,Inherit backup nexthop
OSPF 1
Inter area net route,1.1.2.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 Inter area net route,1.1.3.0/24,nh 150.1.1.2
OSPF 1
Inter area net route,1.1.3.0/24,Inherit backup nexthop
OSPF 1
Inter area net route,1.1.3.0/24,nh 150.1.1.2,bnh 0.0.0.0
// OSPF performed inter-area route backup next hop calculation.
# Enable SPF debugging for OSPF inter-area LSAs. The output in this example was created when the
following conditions exist:
•
Ethernet1/0 (150.1.1.2/24) on Router B is connected to Ethernet1/0 (150.1.1.1/24) on Router A over
a broadcast network.
•
Ethernet1/1 (4.4.4.1/24) on Router B is connected to Ethernet1/0 (4.4.4.2/24) on Router C over
a broadcast network.
•
OSPF process 1 is created on Router B. Area 0 and area 1 are created in OSPF process 1. OSPF
is enabled on Ethernet 1/0, which is configured to belong to area 0. OSPF is enabled on Ethernet
1/1, which is configured to belong to area 1.
174
•
OSPF process 1 is created on Router A. Area 0 is created in OSPF process 1. OSPF is enabled on
Ethernet 1/0, which is configured to belong to area 0.
•
OSPF process 1 is created on Router C. Area 1 is created in OSPF process 1. OSPF is enabled on
Ethernet 1/0, which is configured to belong to area 1. Static routes are configured and
redistributed into OSPF process 1.
•
On Router A, enable FRR to automatically calculate the backup next hop.
<RouterA>debugging ospf spf ase
OSPF 1 Process (Ase)
// ASE SPF calculation began.
OSPF 1 FULL SPF ASE Begin at bucket 0
OSPF 1 New route is better
OSPF 1 Process (Ase)
OSPF 1 FULL SPF ASE Begin at bucket 0
// SPF calculation started from the bucket 0 of the hash table.
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
OSPF 1 New route is better
// OSPF performed ASE SPF calculation debugging.
OSPF 1 ASE net route,100.1.9.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.9.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.9.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.10.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.10.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.10.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.11.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.11.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.11.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.1.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.1.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.1.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.2.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.2.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.2.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.3.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.3.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.3.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.4.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.4.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.4.0/24,nh 150.1.1.2,bnh 0.0.0.0
175
OSPF 1 ASE net route,100.1.5.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.5.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.5.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.6.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.6.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.6.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.7.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.7.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.7.0/24,nh 150.1.1.2,bnh 0.0.0.0
OSPF 1 ASE net route,100.1.8.0/24,nh 150.1.1.2
OSPF 1
ASE net route,100.1.8.0/24,Inherit backup nexthop
OSPF 1
ASE net route,100.1.8.0/24,nh 150.1.1.2,bnh 0.0.0.0
// OSPF performed ASE route backup next hop calculation.
debugging ospf timer
Use debugging ospf timer to enable OSPF timer debugging.
Use undo debugging ospf timer to disable OSPF timer debugging.
Syntax
debugging ospf [ process-id ] timer [ lsa-generate | spf ]
undo debugging ospf [ process-id ] timer [ lsa-generate | spf ]
Default
OSPF timer debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies an OSPF process by its ID in the range of 1 to 65535.
lsa-generate: Specifies LSA generation timer debugging.
spf: Specifies SPF calculation timer debugging.
Usage guidelines
If no process ID is specified, the timer debugging information of all the OSPF processes will be displayed.
Examples
# Enable OSPF timer debugging on Router A. The output in this example was created when the following
conditions exist:
•
Ethernet 1/0 (150.1.1.1/24) on Router A is connected to Ethernet 1/0 (150.1.1.2/24) on Router B
over a broadcast network.
•
On Router A, OSPF process 1 is created and area 0 is created in OSPF process 1. Ethernet 1/0 is
enabled with OSPF and is configured to belong to area 0.
•
On Router B, OSPF process 1 is created. Ethernet 1/0 is enabled with OSPF and is configured to
belong to area 0.
176
When you restart OSPF process 1, output similar to the following example is generated:
<RouterA>debugging ospf timer
<RouterA>reset ospf 1 process
Warning : Reset OSPF process? [Y/N]:y
%Sep 18 11:21:04:612 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Full to Down
OSPF 1 reset SPF TIMER,timeout value is 5000 ms
// OSPF reset the SPF calculation timer with a timeout value of 5000 milliseconds.
OSPF 1 delete SPF TIMER R1 RM/6/RMDEBUG:
// OSPF deleted the SPF calculation timer.
OSPF 1 delete MIN LS TIMER R1 RM/6/RMDEBUG:
// OSPF deleted the LSA generation timer.
OSPF 1 create SPF TIMER,timeout value is 5000 ms
// OSPF created the SPF calculation timer with a timeout value of 5000 milliseconds.
OSPF 1 create MIN LS TIMER,timeout value is 5000 ms
// OSPF created the LSA generation timer with a timeout time of 5000 milliseconds.
OSPF 1 reset MIN LS TIMER,timeout value is 714 ms
// OSPF reset the LSA generation timer with a timeout value of 714 milliseconds.
OSPF 1 reset SPF TIMER,timeout value is 5000 ms
OSPF 1 reset MIN LS TIMER,timeout value is 5000 ms
OSPF 1 reset MIN LS TIMER,timeout value is 714 ms
%Sep 18 11:21:13:908 2006 RouterA RM/3/RMLOG:OSPF-NBRCHANGE: Process 1, Neighbour
150.1.1.2(Ethernet1/0) from Loading to Full
OSPF 1 reset MIN LS TIMER,timeout value is 20 ms
OSPF 1 delete SPF TIMER RouterA RM/6/RMDEBUG:
OSPF 1 create SPF TIMER,timeout value is 5000 ms
177
OSPFv3 debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ospfv3 event
Use debugging ospfv3 event to enable OSPFv3 event debugging, such as ABR, ASBR, or virtual link
event debugging.
Use undo debugging ospfv3 event to disable OSPFv3 event debugging.
Syntax
debugging ospfv3 event { abr | all | bfd | asbr | vlink }
undo debugging ospfv3 event { abr | all | asbr | bfd | vlink }
Default
OSPFv3 event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
abr: Specifies ABR event debugging.
all: Specifies all event debugging.
asbr: Specifies ASBR event debugging.
bfd: Specifies BFD event debugging.
vlink: Specifies virtual link event debugging.
Usage guidelines
Table 1 describes output fields and messages for the debugging ospfv3 event abr command.
Table 112 Output from the debugging ospfv3 event abr command
Field
Description
OSPFv3 ROUTER[number]
OSPFv3 process number.
Router status change.
Change status to string
string indicates router status type. It can be ABR or
non-ABR.
No default Type-3 LSA is generated because there is
no FULL neighbor in the backbone area.
Donot creat default LSA for no FULL neighbors
Table 2 describes output fields and messages for the debugging ospfv3 event bfd command.
178
Table 113 Output from the debugging ospfv3 event bfd command
Field
Description
Message Type XXXX
Type of message that OSPF uses to notify information
to BFD, including create session and delete session.
Connect Type direct-connect
The connection type of the BFD session is direct
connection.
Src IP Address X::X
Source IPv6 address.
Dst IP Address X::X
Destination IPv6 address.
Examples
# Enable ASBR event debugging on Router A. The output in this example was created when the following
conditions exist:
•
Router A is connected to Router B through Ethernet 1/0.
•
OSPFv3 process 1 is created on Router A. OSPFv3 is enabled on Ethernet 1/0.
•
OSPFv3 process 1 is created on Router B. OSPFv3 is enabled on the corresponding interface.
•
Router A and Router B are configured to belong to area 0. On Router A, static route redistribution
is configured and then canceled.
<Sysname> debugging ospfv3 event asbr
*0.2383219 Sysname RM/6/RMDEBUG:OSPFv3 ROUTER: change status to non-ASBR
// The router status changed from ASBR to non-ASBR.
*0.2649563 Sysname RM/6/RMDEBUG:OSPFv3 ROUTER: change status to ASBR
// The router status changed from non-ASBR to ASBR.
debugging ospfv3 graceful-restart
Use debugging ospfv3 graceful-restart to enable OSPFv3 GR debugging.
Use undo debugging ospfv3 graceful-restart to disable OSPFv3 GR debugging.
Syntax
debugging ospfv3 graceful-restart
undo debugging ospfv3 graceful-restart
Default
OSPFv3 GR debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 3 describes output fields and messages for the debugging ospfv3 graceful-restart command.
179
Table 114 Output from the debugging ospfv3 graceful-restart command
Field
Description
received smooth message
OSPFv3 received a GR message.
Notify RM enter GR
OSPFv3 notified the route management module that
the device enters the GR process.
Grace-LSA sending timer expired on interface
IFNAME
Grace-LSA sending timer expired on interface
IFNAME specified by the interface type and interface
number.
Received maxage grace-LSA from neighbor RouterID
on interface IFNAME
OSPFv3 received a Grace-LSA with the age of 3600
seconds from the neighbor.
• RouterID—Router ID of the neighbor.
• IFNAME—Interface specified by the interface type
and interface number.
Flush self stale LSAs
OSPFv3 deleted local stale LSAs.
Schedule whole route calculation
OSPFv3 triggered the calculation of all routes.
OSPFv3 re-established neighbor NBRID on the
interface IFID of area AREAID.
Interface IFID add rebuild neighbor NBRID in area
AREAID
• IFID—Interface ID.
• NBRID—ID of the neighbor of the interface.
• AREAID—ID of the area where the interface
belongs.
Maxage LSAs don't rebuild neighbor
The LSAs exceeding 3600 seconds cannot be used to
establish neighbors.
Cancel interface IFNAME DR election for in GR
The DR election cannot be performed during a GR
process.
The age of the grace-LSA is more than the grace
period
The age of the Grace-LSA exceeds the GR interval.
Flush all self grace-LSAs
OSPFv3 deleted the Grace-LSAs generated on all the
local interfaces.
Start flush stale AS-external-LSAs
OSPFv3 started to delete stale AS-external-LSA.
Don't rebuild neighbor for no network-LSA of interface
IFID
OSPFv3 failed to establish adjacencies because no
Network-LSAs of interface IFID exist.
Examples
# Enable GR debugging on Router A. The output in this example was created when the following
conditions exist:
•
Router A is connected to Router B through Ethernet 1/1.
•
Create OSPFv3 process 1 and enable GR for Router A to act as a GR restarter. OSPFv3 is enabled
on Ethernet 1/1.
•
OSPFv3 process 1 is created on Router B, which is a GR helper by default. OSPFv3 is enabled on
Ethernet 1/1.
•
Router A and Router B are configured to belong to area 0.
180
When you perform a master/backup switchover on Router A, output similar to the following example is
generated:
<RouterA> debugging ospfv3 graceful-restart
%Jun 12 11:10:13:969 2008 RouterA RM/3/RMLOG:OSPFv3 Process 1 Neighbor 8.8.8.8(Ethernet1/1)
from Full to Down
*Jun 12 11:10:13:969 2008 RouterA RM/6/RMDEBUG:OSPFv3 received smooth message.
*Jun 12 11:10:13:969 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Notify RM enter GR.
*Jun 12 11:10:14:00 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Enter GR.
// Router A entered the GR process.
*Jun 12 11:10:14:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Grace-LSA sending timer expired
on interface Ethernet1/1.
*Jun 12 11:10:14:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Send grace-LSA from interface
Ethernet1/1.
*Jun 12 11:10:15:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Grace-LSA sending timer expired
on interface Ethernet1/1.
*Jun 12 11:10:15:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Send grace-LSA from interface
Ethernet1/1
*Jun 12 11:10:16:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Grace-LSA sending timer expired
on interface Ethernet1/1
*Jun 12 11:10:16:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Send grace-LSA from interface
Ethernet1/1
*Jun 12 11:10:17:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Grace-LSA sending timer expired
on interface Ethernet1/1
*Jun 12 11:10:17:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Send grace-LSA from interface
Ethernet1/1
*Jun 12 11:10:18:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Grace-LSA sending timer expired
on interface Ethernet1/1
*Jun 12 11:10:18:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Send grace-LSA from interface
Ethernet1/1
// OSPFv3 sent Grace-LSA to the GR helper.
*Jun 12 11:10:18:453 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Suppress hello timer expired.
*Jun 12 11:10:25:281 2008 RouterA RM/6/RMDEBUG:OSPFv3 Cancel interface Ethernet1/1 DR
election for in GR
%Jun 12 11:10:25:375 2008 RouterA RM/3/RMLOG:OSPFv3 Process 1 Neighbor 8.8.8.8(Ethernet1/1)
from Exchange to Full
*Jun 12 11:10:25:375 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Interface 0.143.0.8 add rebuild
neighbor 8.8.8.8 in area 0.0.0.0.
*Jun 12 11:10:25:375 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Interface 0.143.0.8 delete
rebuild neighbor 8.8.8.8 in area 0.0.0.0.
// The suppress hello timer expired and normal hello packets can be forwarded.
*Jun 12 11:10:25:375 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: All adjacencies had been
rebuilt.
*Jun 12 11:10:25:375 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Reoriginate self LSAs.
// OSPFv3 finished establishing adjacencies.
*Jun 12 11:10:25:375 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Flush all self grace-LSAs.
// OSPFv3 was deleting all local Grace-LSAs.
*Jun 12 11:10:25:391 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Flush self stale LSAs.
*Jun 12 11:10:25:391 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Flush all self stale link-LSAs.
181
*Jun 12 11:10:25:391 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Flush all self stale
router-LSAs and network-LSAs.
// OSPFv3 is deleting stale LSAs.
*Jun 12 11:10:25:391 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Schedule whole route
calculation.
// A route calculation was triggered.
*Jun 12 11:10:29:484 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Whole route calculation
finished.
*Jun 12 11:10:29:484 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Flush all self stale
intra-prefix-LSAs, inter-prefix-LSAs and inter-router-LSAs.
// OSPFv3 finished route calculation.
*Jun 12 11:10:29:484 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: RM notified all protocols left
GR.
*Jun 12 11:10:29:484 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: Start flush stale
AS-external-LSAs.
// The route management module notified all protocols to exit the GR process.
*Jun 12 11:10:29:484 2008 RouterA RM/6/RMDEBUG:OSPFv3 1 GR: GR successfully finished.
// OSPFv3 finished GR.
# Enable GR debugging on Router B.
<RouterB> debugging ospfv3 graceful-restart
*Jun 12 11:30:59:610 2008 RouterB RM/6/RMDEBUG:OSPFv3 1 GR: Enter helper mode for neighbor
9.9.9.9 on interface Ethernet1/1.
%Jun 12 11:31:05:625 2008 RouterB RM/3/RMLOG:OSPFv3 Process 1 Neighbor 9.9.9.9(Ethernet1/1)
from Full to ExStart
// Router B entered the helper mode.
%Jun 12 11:31:05:672 2008 RouterB RM/3/RMLOG:OSPFv3 Process 1 Neighbor 9.9.9.9(Ethernet1/1)
from Exchange to Full
// OSPFv3 is re-establishing adjacencies.
*Jun 12 11:31:05:688 2008 RouterB RM/6/RMDEBUG:OSPFv3 1 GR: Received maxage grace-LSA from
neighbor 9.9.9.9 on interface Ethernet1/1.
// OSPFv3 is deleting Grace-LSAs.
*Jun 12 11:31:05:688 2008 RouterB RM/6/RMDEBUG:OSPFv3 1 GR: Exit helper mode for neighbor
9.9.9.9 on interface Ethernet1/1.
// Router B exited the helper mode.
debugging ospfv3 ifsm
Use debugging ospfv3 ifsm to enable debugging for the OSPFv3 interface state machine.
Use undo debugging ospfv3 ifsm to disable debugging for the OSPFv3 interface state machine.
Syntax
debugging ospfv3 ifsm [ event | status | timer ]
undo debugging ospfv3 ifsm [ event | status | timer ]
Default
Debugging for the OSPFv3 interface state machine is disabled.
182
Views
User view
Default command level
1: Monitor level
Parameters
event: Specifies event debugging for the interface state machine.
status: Specifies status debugging for the interface state machine.
timer: Specifies timer debugging for the interface state machine.
Usage guidelines
Table 4 describes output fields and messages for the debugging ospfv3 ifsm command.
Table 115 Output from the debugging ospfv3 ifsm command
Field
Description
OSPFv3
IFSM[interfacename]
OSPFv3 interface state machine debugging.
Current interface state state and interface event interface-event.
Current interface state:
• Down—The interface is down.
• Loopback—The interface is a loopback interface.
• Waiting—The interface is in the waiting state.
• P-To-P —The interface is connected to a P2P network or configured as one end
of a virtual link.
• Backup—The interface is the backup designated router.
• DR—The interface is the designated router.
state (interface-event)
Event that triggers an interface state change:
• InterfaceUp—The interface state is changed from Down to UP.
• WaitTimer—The wait timer expires.
• BackupSeen—Indicates whether the interface detects a BDR on the network.
The interface receives from a neighbor a hello packet declaring the neighbor is
a BDR, or declaring the neighbor is a DR.
• NeighborChange—A neighbor becomes a DR or BDR, or it is no longer a DR
or BDR. A DR/BDR re-election is required.
• LoopInd—The interface is a loopback interface.
• UnLoopInd—The interface is no longer a loopback interface.
• InterfaceDown—The interface state changes from UP to Down.
Current DR. The string argument can take one of the following values:
DR-Election[string]: DR
ROUTER-ID
• 1st—The first DR election is performed.
DR-Election[string]: BDR
ROUTER-ID Backup
RouterID
• 1st—The first DR election is performed.
• 2nd—An interface state change occurs and a DR re-election is performed.
Current BDR. The string argument can take one of the following values:
• 2nd—An interface state change occurs and a DR re-election is performed.
183
Field
Description
ifsm_ignore called
The received event is not processed.
Interface state:
• Down—The interface is down.
• Loopback—The interface is a loopback interface.
Status change state1 ->
state2
• Waiting—The interface is in the waiting state.
• P-To-P—The interface is connected to a P2P network or configured as one end
of a virtual link.
• Backup—The interface is the backup designated router.
• DR—The interface is the designated router.
string timer expire
Timer expired. Timers include Wait timer, Hello timer, and LS ACK timer.
Examples
# Enable OSPFv3 interface state machine debugging on Router A. The output in this example was
created when the following conditions exist:
•
Router A is connected to Router B through Ethernet 1/0.
•
OSPFv3 process 1 is created on Router A. OSPFv3 is enabled on Ethernet 1/0.
•
OSPFv3 process 1 is created on Router B. OSPFv3 is enabled on Ethernet 1/0.
When a neighbor relationship is established between Router A and Router B, output similar to the
following example is generated:
<Sysname> debugging ospfv3 ifsm
*0.85734 Sysname RM/6/RMDEBUG:OSPFv3 IFSM[Ethernet1/0]: Down (InterfaceUp)
*0.95875 Sysname RM/6/RMDEBUG:OSPFv3 IFSM[Ethernet1/0]:
DR-Election[1st]: DR
34.1.1.1
// The first DR election was complete. The DR is 34.1.1.1.
*0.95890 Sysname RM/6/RMDEBUG:OSPFv3 IFSM[Ethernet1/0]:
DR-Election[2nd]: DR 34.1.1.1
*0.1688515 Sysname RM/6/RMDEBUG:OSPFv3 IFSM[Ethernet1/0]: Status change Backup -> DR
// A DR re-election was carried out and the state of Ethernet 1/0 changed from Backup to DR.
*0.3761765 Sysname RM/6/RMDEBUG:OSPFv3 IFSM[Ethernet1/0]: Hello timer expire
// The hello timer expired.
debugging ospfv3 lsa
Use debugging ospfv3 lsa to enable OSPFv3 LSA debugging.
Use undo debugging ospfv3 lsa to disable OSPFv3 LSA debugging.
Syntax
debugging ospfv3 lsa { all | flooding | generate | install | maxage | refresh | verbose }
undo debugging ospfv3 lsa { all | flooding | generate | install | maxage | refresh | verbose }
Default
OSPFv3 LSA debugging is disabled.
184
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all LSA debugging.
flooding: Specifies LSA flooding debugging.
generate: Specifies LSA generation debugging.
install: Specifies debugging of LSAs installation into the LSDB.
maxage: Specifies LSA maxage debugging.
refresh: Specifies LSA refresh debugging.
verbose: Specifies LSA detailed debugging information.
Usage guidelines
Table 5 describes output fields and messages for the debugging ospfv3 lsa flooding command.
Table 116 Output from the debugging ospfv3 lsa flooding command
Field
Description
string indicates the LSDB containing the LSA. It can be:
• Link—Identified by interface type and interface number.
• Area ID.
• AS—The flooding range is the entire AS.
number indicates the LSA type. It can be:
• 0x2001—Router-LSAs.
• 0x2002—Network-LSAs.
LSA[string:Type(number) :LSID:adv_ro
uter *]
• 0x2003—Inter-Area-Prefix-LSAs.
• 0x2004—Inter-Area-Router-LSAs.
• 0x2005—AS-external-LSAs.
• 0x0008—Link-LSAs.
• 0x2009—Intra-Area-Prefix-LSAs.
• 0x000b—Grace-LSA.
LSID indicates the Link-state ID of the LSA.
adv_router indicates the ID of the advertising router.
* indicates that the LSA is self-originated.
Table 6 describes output fields and messages for the debugging ospfv3 lsa maxage command.
185
Table 117 Output from the debugging ospfv3 lsa maxage command
Field
Description
Flag bit:
• V—Vlink end.
Flags;string
• E—ASBR.
• B—ABR.
• W—MOSPF support.
Router processing capabilities:
• V6—A value of 0 indicates that the router/link will not take part in IPv6
route calculation.
• E—A value of 0 indicates that the flooding of AS-External-LSAs is not
supported.
Options
• MC—Multicast-related.
• N—Indicates whether it is in a Not So Stub Area (NSSA).
• R—Indicates whether this is an Active Router. A value of 0 indicates that
the router only forwards locally originated packets.
• DC—Indicates whether dial-on-demand is supported.
Link type:
• (null).
Link connected to: linktype
• Point-to-point.
• Transit Network.
• (Reserved).
• Virtual Link.
PrefixOptions:
• NU—A value of 1 indicates that the prefix will not take part in IPv6
unicast route calculation.
Option
• MC—A value of 1 indicates that the prefix will take part in IPv6 multicast
route calculation.
• LA—A value of 1 indicates that the address is the local host address. The
prefix length is 128.
• P—Indicates whether the NSSA ABR advertises the prefix to other areas.
Destination Router ID
ASBR router ID.
Metric type:
Metric Type string
• 1 (Comparable directly to link state metric).
• 2 (Larger than any link state path).
Examples
# Enable LSA flooding debugging on Router A. The output in this example was created when the
following conditions exist:
•
Router A is connected to Router B through Ethernet 1/0.
•
OSPFv3 process 1 is created on Router A. OSPFv3 is enabled on Ethernet 1/0.
•
OSPFv3 process 1 is created on Router B. OSPFv3 is enabled on Ethernet 1/0.
186
When a neighbor relationship is established between Router A and Router B, output similar to the
following example is generated:
<Sysname> debugging ospfv3 lsa flooding
*0.14227421 Sysname RM/6/RMDEBUG: OSPFv3
LSA[Link(Ethernet1/0):Type(0x0008)
:0.15.0.24:34.1.1.1 *]: consider flooding through interface[Ethernet1/0]
// OSPFv3 advertised an LSA (the LSA type is 0x0008, Link State ID is 0.15.0.24, and advertising router
ID is 34.1.1.1) through Ethernet 1/0.
*0.284706031 Sysname RM/6/RMDEBUG:OSPFv3 LSA[Area(0.0.0.0):Type(0x2004)
:0.0.0.1:78.3.3.3]: flood started
*0.284705984 Sysname RM/6/RMDEBUG:OSPFv3 LSA[Area(0.0.0.0):
Type(0x2003):0.0.0.3:78.3.3.3 *]: Update param for self-originated LSA
*0.284706046 Sysname RM/6/RMDEBUG:OSPFv3 LSA[Area(0.0.0.0):
Type(0x2004):0.0.0.1:78.3.3.3 *]: Process self-originated LSA
// OSPFv3 was processing self-originated LSAs.
*0.79095047 Sysname RM/6/RMDEBUG:OSPFv3 LSA[Area(0.0.0.0):Type(0x2004):
0.0.0.1:78.3.3.3]: DISCARD, same instance exists in LSDB
// OSPFv3 discarded the received LSA because the same LSA already exists in the LSDB.
*0.14241000 Sysname RM/6/RMDEBUG:OSPFv3 LSA[Area(0.0.0.0):Type(0x2009)
:0.0.0.2:34.1.1.1]: DISCARD, LSA is MaxAge, there is no instance and none of router's
neighbors are in states Exchange or Loading
// OSPFv3 discarded the received LSA because its maximum age was reached and none of the router's
neighbors is in the Exchange or Loading state.
debugging ospfv3 nfsm
Use debugging ospfv3 nfsm to enable debugging for the OSPFv3 neighbor state machine.
Use undo debugging ospfv3 nfsm to disable debugging for the OSPFv3 neighbor state machine.
Syntax
debugging ospfv3 nfsm [ event | status | timer ]
undo debugging ospfv3 nfsm [ event | status | timer ]
Default
Debugging for the OSPFv3 neighbor state machine is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
status: Specifies status debugging of the neighbor state machine.
event: Specifies event debugging of the neighbor state machine.
timer: Specifies timer debugging of the neighbor state machine.
Usage guidelines
Table 7 describes output fields and messages for the debugging ospfv3 nfsm command.
187
Table 118 Output from the debugging ospfv3 nfsm command
Field
Description
NFSM[RouterID
-ifid]
Router ID and interface ID of the neighbor router.
Neighbor status changed from state1 to state2. The values of state1 and state2 can be:
• Down—The neighbor is down.
• Attempt—A further attempt is made to contact the neighbor after not receiving
anything from it.
• Init—A hello packet sent by the neighbor is received but 2-way communication is not
Status change
state1->state2
established.
• 2-Way—2-way communication is established.
• ExStart—The master/subordinate negotiation is performed.
• Exchange—DD packets are exchanged.
• Loading—LSR packets are sent to the neighbor.
• Full—An adjacency is established.
188
Field
Description
Neighbor state state and triggering event event.
Current neighbor state:
• Down—The neighbor is down.
• Attempt—A further attempt is made to contact the neighbor after receiving nothing
from it.
• Init—The hello packets sent by the neighbor were received but 2-way communication
is not established with the neighbor.
• 2-Way—2-way communication is established.
• ExStart—The master/subordinate negotiation is performed.
• Exchange—DD packets are exchanged.
• Loading—LSR packets are sent to the neighbor.
• Full—An adjacency is established.
Triggering event:
• HelloReceived—A hello packet is received from the neighbor.
• Start—Hello packets will be sent to the neighbor at an interval of HelloInterval. This
event is only related to a neighbor on an NBMA network.
• 2-WayReceived—2-way communication is established between the two neighboring
state (event)
routers.
• NegotiationDone—The master/subordinate negotiation is completed and DD
sequence numbers are exchanged.
• ExchangeDone—The two routers have exchanged DD packets successfully and know
which LSAs of the neighbor are missing from their LSDBs.
• BadLSReq—The received LSR contains LSAs that cannot be found in the local LSDB.
• LoadingDone—The LSR list is empty after the database exchange is complete.
• AdjOK—Indicates whether an adjacency needs to be established or maintained with
the neighbor.
• SeqNumberMismatch—An error has occurred when an adjacency is being
established.
• 1-WayReceived—The hello packet received from the neighbor does not contain the
local router.
• KillNbr—It is impossible to communicate with the neighbor and therefore the
neighbor is forced to enter the Down state.
• InactivityTimer—No hello packet has been received from the neighbor recently and
therefore the neighbor dead timer is started.
• LLDown—The neighbor is unreachable and therefore is forced to enter the Down
state.
nfsm_ignore called
The received event is not processed.
Timer expired. Timers include:
• Inactivity timer.
timer-name timer
expire
• DD retransmit timer.
• LS update timer.
• LS request timer.
189
Examples
# Enable neighbor state machine debugging on Router A. The output in this example was created when
the following conditions exist:
•
Router A is connected to Router B through Ethernet 1/0.
•
OSPFv3 process 1 is created on Router A. OSPFv3 is enabled on Ethernet 1/0.
•
OSPFv3 process 1 is created on Router B. OSPFv3 is enabled on Ethernet 1/0.
<Sysname> debugging ospfv3 nfsm
*0.5752906 Sysname RM/6/RMDEBUG:OSPFv3 NFSM[34.1.1.1-000f0018]: Down (HelloReceived)
// The Router ID, interface ID, and state of the neighbor is 34.1.1.1, 000f0018, and Down, respectively.
The HelloReceived event was triggered.
*0.5461109 Sysname RM/6/RMDEBUG:OSPFv3 NFSM[34.1.1.1-000f0018]: LS update timer expire
// The Router ID and interface ID of the neighbor are 34.1.1.1 and 000f0018, respectively. The update
packet timer expired.
*0.4252250 Sysname RM/6/RMDEBUG:OSPFv3 NFSM[34.1.1.1-000f0018]: Status change Full ->
Down
// The Router ID and interface ID of the neighbor are 34.1.1.1 and 000f0018, respectively. The neighbor
state changed from Full to Down.
debugging ospfv3 packet
Use debugging ospfv3 packet to enable OSPFv3 packet debugging.
Use undo debugging ospfv3 packet to disable OSPFv3 packet debugging.
Syntax
debugging ospfv3 packet { all | { ack | dd | hello | request | update } * } [ verbose ]
undo debugging ospfv3 packet { all | { ack | dd | hello | request | update } * } [ verbose ]
Default
OSPFv3 packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all packet debugging.
ack: Specifies LSAck packet debugging.
dd: Specifies DD packet debugging.
hello: Specifies hello packet debugging.
request: Specifies LSR packet debugging.
update: Specifies LSU packet debugging.
verbose: Specifies detailed packet debugging information.
190
Usage guidelines
Table 8 describes output fields and messages for the debugging ospfv3 packet command.
Table 119 Output from the debugging ospfv3 packet command
Field
Description
OSPFv3 sent/received hello packets.
• event—RECV indicates that a hello packet is
Packet[event] : src(source-ipv6) -> dst(dest-ipv6)
received. SEND indicates that a hello packet is
sent.
• source-ipv6—Source IPv6 link-local address of the
hello packet.
• dest-ipv6—Destination IPv6 link-local address of
the hello packet.
OSPFv3 packet type.
The value of number can be:
• 0—Unknown packets.
• 1—Hello packets.
• 2—DD packets.
• 3—Link state request packets.
• 4—Link state update packets.
• 5—Link state acknowledgement packets.
Type number(string)
The value of string can be:
• Unknown.
• Hello.
• Database Description.
• Link State Request.
• Link State Update.
• Link State Acknowledgment.
Router ID RouterID
ID of the sending/receiving router.
Area ID AreaID
Area ID of the packet.
Options number
Router processing capabilities.
Received LSA is not the latest.
number indicates the LSA number. It can be:
• 0x2001—Router-LSAs.
• 0x2002—Network-LSAs.
RECV[DD]: LSA received Type(number), ID(LSID) is not
recent
• 0x2003—Inter-Area-Prefix-LSAs.
• 0x2004—Inter-Area-Router-LSAs.
• 0x2005—AS-external-LSAs.
• 0x0008—Link-LSAs.
• 0x2009—Intra-Area-Prefix-LSAs.
• 0x000b—Grace-LSA.
LSID indicates the Link-state ID of the LSA.
191
Field
Description
OSPFv3 discarded the received DD packet.
state indicates the current neighbor state. It can be:
• Down—The neighbor is down.
RECV[DD]:Neighbor state is state, packet discarded
• Attempt—A further attempt is made to contact the
neighbor after receiving nothing from it.
• Init—The hello packet sent by the neighbor is
received but 2-way communication is not
established.
The neighbor state is less than Exchange and the
packet is discarded.
state indicates the neighbor state. It can be:
• Down—The neighbor is down.
• Init—The hello packet sent by the neighbor is
RECV[LS-Req]: Neighbor state is state packet
discarded
received but 2-way communication is not
established.
• 2-Way—2-way communication is established.
• ExStart—The master/subordinate negotiation is
performed.
OSPFv3 discarded the received packet because the
packet does not match the IPsec policy on the
receiving interface.
[RECV]: Discard interface interface-type
interface-number packet due to IPsec policy
mismatch. IF SPI: if-spi, Packet SPI: packet-spi
• if-spi—SPI on the interface.
• packet-spi—SPI carried in the packet.
Examples
# Enable DD packet debugging on Router A. The output in this example was created when the following
conditions exist:
•
Router A is connected to Router B through Ethernet 1/0.
•
OSPFv3 process 1 is created on Router A. OSPFv3 is enabled on Ethernet 1/0.
•
OSPFv3 process 1 is created on Router B. OSPFv3 is enabled on Ethernet 1/0.
<Sysname> debugging ospfv3 packet dd
*0.31611969 Sysname RM/6/RMDEBUG:OSPFv3 Packet[SEND]:
src:(FE80::200:5EFF:FE01:B400) -> dst:(FE80::200:5EFF:FE01:B403)
// OSPFv3 sent DD packets from FE80::200:5EFF:FE01:B400 to FE80::200:5EFF:FE01:B403.
*0.290484 Sysname RM/6/RMDEBUG:OSPFv3 RECV[DD]: Negotiation done (Slave)
// OSPFv3 finished the master/subordinate negotiation. The current router works as the subordinate
router.
debugging ospfv3 route
Use debugging ospfv3 route to enable OSPFv3 route debugging.
Use undo debugging ospfv3 route to disable OSPFv3 route debugging.
192
Syntax
debugging ospfv3 route [ ase | ia | install | spf ]
undo debugging ospfv3 route [ ase | ia | install | spf ]
Default
OSPFv3 route debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
ase: Specifies OSPFv3 ASE route debugging.
ia: Specifies OSPFv3 inter-area route debugging.
install: Specifies debugging of OSPFv3 routes installation into the routing table.
spf: Specifies OSPFv3 SPF route calculation debugging.
Usage guidelines
Table 9 describes output fields and messages for the debugging ospfv3 route command.
Table 120 Output from the debugging ospfv3 route command
Field
Description
SPF[AreaID]
SPF calculation.
string indicates the LSDB containing the LSA. It can be:
• Link, identified by interface type and interface number.
• Area ID.
• AS, indicating the flooding range is the entire AS.
number indicates LSA number. It can be:
• 0x2001—Router-LSAs.
• 0x2002—Network-LSAs.
LSA[string:Type(number) :LSID:adv_router *]
• 0x2003—Inter-Area-Prefix-LSAs.
• 0x2004—Inter-Area-Router-LSAs.
• 0x2005—AS-external-LSAs.
• 0x0008—Link-LSAs.
• 0x2009—Intra-Area-Prefix-LSAs.
• 0x000b—Grace-LSA.
LSID indicates link-state ID of the LSA.
adv_router indicates ID of the advertising router.
* indicates that the LSA is self-originated.
193
Field
Description
OSPFv3 installed the vertex to the candidate list.
LS_TYPE indicates LSA type. It can be:
Install LS_TYPE Vertex Id LSID Adv by
AdvRouter candidate list
• Router.
• Network.
LSID indicates link State ID of the LSA.
AdvRouter indicates ID of the advertising router.
Route[IA:AreaID]
Inter-area route calculation.
Examples
# Enable SPF route debugging on one of the two interconnected devices enabled with OSPFv3. When
you change the network topology, output similar to the following example is generated:
<Sysname> debugging ospfv3 route spf
*0.82470953 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Calculation timer scheduled [delay
5 secs]
// The calculation started 5 seconds later.
*0.82470953 Sysname RM/6/RMDEBUG:OSPFv3 SPF calculation timer is already scheduled
// The SPF calculation timer started.
*0.82475046 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Intra-Area SPF calculation timer
expire
// The SPF calculation timer of area 0 expired.
*0.82475046 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Intra-Area SPF calculation (1st
STAGE)
// SPF calculation in area 0 will be performed (first stage).
*0.82475046 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Get Router VertexId 0.0.0.0 Adv by
45.2.2.2
// OSPFv3 obtained the neighbor router vertex of the vertex whose router ID was 45.2.2.2 and whose
Link State ID was 0.0.0.0.
*0.82475046 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]:
by interface 0.15.0.24:
Link[0] to Transit-Net 34.1.1.1
// Link 0 was connected to neighbor 34.1.1.1 whose Link State ID was 0.15.0.24 over a transit network.
*0.82475046 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Install Network Vertex Id 0.15.0.24
Adv by 34.1.1.1 into candidate list
// The vertex with router ID 34.1.1.1 and Link State ID 0.15.0.24 was installed into the candidate list.
*0.82475062 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]:
list.
No candidate node in the candidate
// There was no candidate node in the candidate list.
*0.82475062 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]:
(34.1.1.1-0.15.0.24)
Calculate nexthop for
// OSPFv3 was calculating the nexthop to the neighbor with router ID 34.1.1.1 and Link State ID
0.15.0.24.
*0.82475062 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Get Network Vertex Id 0.15.0.24 Adv
by 34.1.1.1
// The vertex with Router ID 34.1.1.1 and Link State ID 0.15.0.24 got the next network vertex.
194
*0.82475062 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]:
Link[0] to Router 34.1.1.1
// Link 0 pointed to router 34.1.1.1.
*0.82475062 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]:
doesn't have link back to (34.1.1.1-0.15.0.24)
Link[0] (34.1.1.1-0.0.0.0):
// Vertex (34.1.1.1-0.0.0.0) did not have any link back to vertex 34.1.1.1-0.15.0.24.
*0.82475078 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]:
LSA[Area(0.0.0.0):Type(0x2001):0.0.0.0:45.2.2.2 *] is already in SPF tree
// The LSA (area ID is 0, type is 0x2001, router ID is 45.2.2.2, and Link State ID is 0.0.0.0) was already
in the SPF tree.
*0.82475078 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Intra-Area SPF calculation (2nd
STAGE)
// OSPFv3 performed SPF calculation (second stage).
*0.82475078 Sysname RM/6/RMDEBUG:OSPFv3 SPF[0.0.0.0]: Intra-Area SPF calculation (END)
// OSPFv3 finished intra-area SPF calculation.
195
PIM debugging commands
Support for VPN instances depends on your device model.
The output description tables in this document only contain fields and messages that require an
explanation.
debugging pim
Use debugging pim to enable PIM debugging.
Use undo debugging pim to disable PIM debugging.
Syntax
debugging pim [ all-instance | vpn-instance vpn-instance-name ] { all | assert [ advanced-acl-number ]
[ receive | send ] | df | event [ advanced-acl-number ] | join-prune [ advanced-acl-number ] [ receive
| send ] | msdp [ advanced-acl-number ] | neighbor [ basic-acl-number ] [ receive | send ] | register
[ advanced-acl-number ] | routing-table [ advanced-acl-number ] | rp [ receive | send ] | state-refresh
[ advanced-acl-number ] [ receive | send ] }
undo debugging pim [ all-instance | vpn-instance vpn-instance-name ] { all | assert [ receive | send ] |
df | event | join-prune [ receive | send ] | msdp | neighbor [ receive | send ] | register | routing-table
| rp [ receive | send ] | state-refresh [ receive | send ] }
Default
PIM debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all-instance: Specifies all MPLS L3VPN instances.
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance. The VPN instance name must be a
case-sensitive string of 1 to 31 characters and must not contain any spaces.
all: Specifies all types of PIM debugging.
assert: Specifies PIM assert message debugging.
advanced-acl-number: Specifies an advanced ACL number in the range of 3000 to 3999. An advanced
ACL defines the range of multicast groups to which the advertised RP is designated.
receive: Specifies inbound PIM packet debugging.
send: Specifies outbound PIM packet debugging.
df: Specifies DF information debugging.
event: Specifies PIM event debugging.
join-prune: Specifies PIM join/prune message debugging.
196
msdp: Specifies debugging for packets exchanged between PIM and MSDP.
neighbor: Specifies PIM neighbor debugging.
basic-acl-number: Specifies a basic ACL number in the range of 2000 to 2999.
register: Specifies PIM register message debugging.
routing-table: Specifies debugging for state change of the PIM multicast routing table.
rp: Specifies debugging for PIM packets related to the BSR and the RP.
state-refresh: Specifies PIM state refresh message debugging.
Usage guidelines
If neither all-instance nor vpn-instance is specified, this command enables PIM debugging for the public
network.
Table 1 describes output fields and messages for the debugging pim assert command.
Table 121 Output from the debugging pim assert command
Field
Description
pref
Preference value.
metric
Metric value.
rpt set/unset
The RPT bit is 1/0.
reserved field non-zero
The reserved field is non-zero.
unknown neighbor
The neighbor is unknown.
truncated assert packet
The packet length is invalid.
bad group address/mask
The group address or the address mask is incorrect.
unknown group family
The group family is incorrect.
bad source address
The source address is incorrect.
locally scoped
Node-local or link-local scope.
Fsm:assert
Assert state machine.
current state
Current state of the assert state machine.
received event
Type of the event received by the assert state machine.
loser/Winner/noinfo
The assert state machine was in
loser/winner/no-information state.
state1->state2
The assert state machine was transferred from state1
to state2.
Table 2 describes output fields and messages for the debugging pim df command.
Table 122 Output from the debugging pim df command
Field
Description
DF election
DF election started.
DFT
DF election timer.
DFT expire time
Expiration time of DF election timer.
197
Field
Description
MC
Number of sent Offer or Winner packets.
Offer
Initial state of DF election.
Lose
DF election state: Lose.
Win
DF election state: Win.
Backoff
The winner DF received better Offer packets.
Table 3 describes output fields and messages for the debugging pim event command.
Table 123 Output from the debugging pim event command
Field
Description
unsupported pim version
The PIM packet version is not supported.
PIM packet too short
The PIM packet is too short.
checksum error
The checksum of the packet is incorrect.
non-pim interface
A PIM message was received on a non-PIM-enabled
interface.
unsupported type
The specified PIM packet type is not supported.
Socket set option error
Socket option setting failed.
Packet send error
A PIM message failed to be sent out.
Source address is one of the interfaces address
The source address is the address of a local interface.
Source address address is invalid
The source address address is invalid.
Invalid source mask
The source address mask is invalid.
Active/Inactive event received
A source-active/inactive event was received.
Clear event received
A clear-entry event was received.
Wrong IIF
Incorrect incoming interface.
NoInfo
The downstream state machine was in no-information
state.
PPending
The downstream state machine was in prune pending
state.
Pruned
The PIM-DM downstream state machine was in pruned
pending state.
Joined
The PIM-SM downstream state machine was in joined
state.
Forwarding
The PIM-DM upstream state machine was in
forwarded state.
Pruned
The PIM-DM upstream state machine was in pruned
state.
AckPending
The PIM-DM upstream state machine was in
ack-pending state.
Joined
The PIM-SM (S, G) or (*, G) upstream state machine
was in joined state.
198
Field
Description
NotJoined
The PIM-SM (S, G) or (*, G) upstream state machine
was in not-joined state.
PruneTmp
The PIM-SM (S, G, RPT) downstream state machine
was in temporary prune state.
PPendingTmp
The PIM-SM (S, G, RPT) downstream state machine
was in temporary prune pending state.
PPT Expired
The prune pending timer timed out.
RPF_Interface changed
The RPF interface changed.
Genid changed
The neighbor generation ID changed.
PT Expired
The prune timer timed out.
Failed to pass MSF
Failed to pass multicast source filtering.
NotOriginator/Originator
The originator state machine was in
not-originator/originator state.
SAT Expired
The source-alive timer timed out.
Join suppressed
The device received a join message to the upstream
neighbor on the incoming interface and suppressed its
own join message.
Override it
The device received a prune message to the upstream
neighbor on the incoming interface and sent a join
message.
ET Expired
The PIM-SM downstream interface timer timed out.
register downstream
Registering the outgoing interface.
Mcast-Boundary-Changed
Multicast boundary change event.
flush timer
Timer used for periodically checking whether new RP
and DF information issued to the forwarding module
exist.
walk timer
Timer used for periodically traversing RP table entries.
Table 4 describes output fields and messages for the debugging pim join-prune command.
Table 124 Output from the debugging pim join-prune command
Field
Description
JP
Join/prune message.
GFT
Graft message.
GAK
Graft-ack message.
bad group/source address, mask or family
Incorrect group/source address, mask or family.
Upstream
Upstream neighbor information in the message.
Groups
Number of groups in the message.
Group: addr/mask --- m joins n prunes
Group information in the message, including group
address/mask length, m times of joins, and n times of
prunes.
199
Field
Description
Join: addr/mask flag
Join: source address/mask flag.
Message truncated. Ignoring message
The message was dropped due to invalid message
length.
Unable to decode address
Address decoding failed.
Upstream neighbor is not this router. Ignoring
The message was dropped because the upstream
neighbor is not this device.
group boundary detected for address1 on address2
Address 1 is within the multicast boundary configured
on the interface corresponding to address 2.
Group address1 ignored in message on address2
Address 1 is within the multicast boundary configured
on the interface corresponding to address 2. This
group is ignored.
Message from unknown neighbor
A message was received from an unknown neighbor.
Join/Prune received for non-local neighbor
A join/prune message for a non-local upstream
neighbor was received.
Override timer expires
The prune override timer timed out.
Table 5 describes output fields and messages for the debugging pim neighbor command.
Table 125 Output from the debugging pim neighbor command
Field
Description
HEL
PIM hello message.
hello packet
PIM hello message.
Option: m, length: n
PIM hello message option: option value (specified by
m) and option length: length value (specified by n).
Holdtime:
Holdtime field of the PIM hello message.
Tbit
Tbit option.
Lan delay
LAN delay option.
Override interval
Override interval option.
DR priority
DR priority option.
Genid
Generation ID option.
Version
Version field of the state refresh option.
Refresh interval
State refresh interval field of the state refresh option.
Reserved
Reserved field of the state refresh option.
Secondary address(es)
Address in the address list option.
Unknown option value
The option value is unknown.
without SR capability
No state refresh capability.
Elected as DR on interface interfacename
The device was elected as the DR in the network
attached to interfacename.
Unelected as DR on
The device was no longer the DR for the network
attached to interfacename.
interface interfacename
200
Field
Description
PIM Neighbor address on interface interfacename
timed out
Neighbor address on interfacename timed out.
Failed to create PIM neighbor address, PIM Hello
denied by neighbor policy on interfacename
A PIM neighbor relationship failed to be established
because the source address in the hello message
failed to pass the configured hello message filtering.
Table 6 describes output fields and messages for the debugging pim register command.
Table 126 Output from the debugging pim register command
Field
Description
REG
Register message.
RSP
Register-stop message.
Register Stop
Register stopped.
Border bit
Boundary bit.
src
Source address of the IP packet.
dst
Destination address of the IP packet.
probe
Probe message.
ignored
A message was dropped.
Table 7 describes output fields and messages for the debugging pim routing-table command.
Table 127 Output from the debugging pim routing-table command
Field
Description
Creating/Deleting
PIM created or deleted entries.
mrt
Multicast routing table.
Add/Del oil
PIM added or deleted outgoing interfaces.
Null iif
Null incoming interface.
Adding/Deleting iif
PIM added or deleted incoming interfaces.
RP is not found
The RP was not found.
Table 8 describes output fields and messages for the debugging pim rp command.
Table 128 Output from the debugging pim rp command
Field
Description
auto-RP announce
Auto-RP announce message.
auto-RP discovery
Auto-RP discovery message.
C-RP/CRP
Candidate RP.
BSR
Bootstrap router.
prefix count
Prefix count field in the C-RP advertisement message.
priority
Priority field in the C-RP advertisement message.
201
Field
Description
holdtime
Holdtime field in the C-RP advertisement message.
Admin Scope Zone
Administratively scoped zone.
Bad BSR address
Incorrect BSR address.
frag
Fragment tag field in the BSR bootstrap message.
pri
Priority field in the BSR bootstrap message.
hash mask len
Hash mask length field in the BSR bootstrap message.
Group address/length: frags m, C-RP's n
The frags field corresponding to address/length in the
BSR bootstrap message is specified by m. The number
of C-RPs is specified by n.
address pri: m, holdtime: n
The priority of C-RP address in the BSR bootstrap
message is specified by m and holdtime is specified
by n.
Auto-RP discovery packet: RP agent address, RP count
m, Holdtime n
An auto-RP discovery message was received.
Information about the auto-RP discovery message
includes the following:
• RP agent specified by address.
• RP count specified by m.
• Holdtime specified by n.
delete RP-Set
An RP set was deleted.
too short length
Message length is too short.
bad group address
Incorrect group address.
bad group mask length
Incorrect group mask length.
bad BSR address
Incorrect BSR address.
bad BSR address family
Incorrect BSR address family.
bad BSR hash mask length
Incorrect BSR hash mask length.
bad scope zone mask
Incorrect scope zone mask.
Unknown group address family
Incorrect group address family.
not directly connected source
The source is not directly connected.
unknown neighbor
The neighbor is unknown.
Bad frag-rp-count field
Incorrect frag-rp-count field in the BSR bootstrap
message.
Bad frag-rp field length
Incorrect total length of frag-rp fields in the BSR
bootstrap message.
BSR mechanism
BSR mechanism independent of administrative
scoping.
Upstream to BSR
Upstream toward the BSR.
no BSR is available
No BSR is available.
add/remove register vif
A register virtual interface was added or removed.
Expiring CRP
C-RP that aged out.
202
Field
Description
Lose the ASBSR election
The device lost the BSR election in the BSR
admin-scope region.
Lose the BSR election
The device lost the BSR election.
locally scoped
Node-local or link-local scope.
RP changed
The RP changed.
pending state
The BSR changed to the pending state.
Update the BSR's state to elected
The BSR changed to the elected state.
RPF Failure
RPF check failed.
admin scope multicast address
Address in the admin-scope range.
Table 9 describes output fields and messages for the debugging pim state-refresh command.
Table 129 Output from the debugging pim state-refresh command
Field
Description
SRM
State refresh message.
Message truncated
Message length is invalid.
bad group address
Incorrect group address.
invalid group mask length
Incorrect group mask length.
Originator address
Address of the state refresh message originator.
preference
Preference field of the message.
metric
Metric field of the message.
mask length
Mask length field of the message.
ttl
TTL value of the message.
prune indicator
Prune indicator flag bit.
prune now
Prune now indicator flag bit.
assert override
Assert override flag bit.
Examples
The output in the following examples was created under the condition that PIM-DM or PIM-SM is
enabled:
# Enable debugging for inbound PIM assert messages for the public network.
<Sysname> debugging pim assert receive
*0.594609 Sysname PIM/7/ASSERT:(public net): PIM ver 2 AST receiving 30.1.1.2 ->224.0.0.13
on Vlan-interface30 (P012343)
*0.594609 Sysname PIM/7/ASSERT:(public net): For 229.0.0.1/32 from 100.1.1.11, rpt unset,
pref 10, metric 3 (P012351)
// PIM received a PIMv2 assert message from 30.1.1.2 to 224.0.0.13 on VLAN-interface 30.
# Enable debugging for outbound PIM assert messages for the public network.
<Sysname> debugging pim assert send
203
*0.663235 Sysname PIM/7/ASSERT:(public net): PIM ver 2 AST sending 30.1.1.2 -> 224.0.0.13
on Vlan-interface30 (P012343)
*0.663235 Sysname PIM/7/ASSERT:(public net): For 229.0.0.1/32 from 100.1.1.11, rpt unset,
pref 10, metric 3 (P012351)
// PIM sent a PIMv2 assert message from 30.1.1.2 to 224.0.0.13 out of VLAN-interface 30.
# Enable DF information debugging on the public network.
<Sysname> debugging pim df
*May 21 10:34:41:875 2010 Sysname PIM/7/DF: (public net): Start DF election on interface
Vlan-interface2 of RP: 1.1.1.1 (P521628)
*May 21 10:34:41:875 2010 Sysname PIM/7/DF: (public net): Create DFT for RP: 1.1.1.1 on
interface Vlan-interface2, expire time is 60 msec (P51645)
*May 21 10:34:41:875 2010 Sysname PIM/7/DF: (public net): Set MC to 0 for RP: 1.1.1.1 on
interface Vlan-interface2 (P51345)
*May 21 10:34:41:891 2010 Sysname PIM/7/DF: (public net): Start DF election of RP: 1.1.1.1
(P521775)
*May 21 10:34:41:922 2010 Sysname PIM/7/DF: (public net): DFT expired for RP: 1.1.1.1 on
interface Vlan-interface2 (P51506)
*May 21 10:34:41:922 2010 Sysname PIM/7/DF: (public net): Send bidir-pim Offer packet at
interface Vlan-interface2 (P501065)
*May 21 10:34:41:922 2010 Sysname PIM/7/DF: (public net): Modify DFT expire time to 60
msec for RP: 1.1.1.1 on interface Vlan-interface2 (P51670)
*May 21 10:34:41:922 2010 Sysname PIM/7/DF: (public net): Set MC to 1 for RP: 1.1.1.1 on
interface Vlan-interface2 (P51345)
// The RP for BIDIR-PIM is 1.1.1.1. A DF election was triggered on VLAN-interface 2. The DF election timer
was started. After the timer expired, an Offer packet was sent and MC was set to 1.
*May 21 10:34:41:938 2010 Sysname PIM/7/DF: (public net): Receive bidir-pim Winner packet
from 2.1.1.1 at interface Vlan-interface2 (P50804)
*May 21 10:34:41:938 2010 Sysname PIM/7/DF: (public net): DF election event(Receive better
Pass/Win) for RP: 1.1.1.1 happened on interface Vlan-interface2 (P51231)
*May 21 10:34:41:938 2010 Sysname PIM/7/DF: (public net): DF election state changed from
Offer to Lose for RP: 1.1.1.1 on interface Vlan-interface2 (P51273)
*May 21 10:34:41:938 2010 Sysname PIM/7/DF: (public net): Set DF to 2.1.1.1(pref: 0, metric:
0) for RP: 1.1.1.1 on interface Vlan-interface2 (P51411)
*May 21 10:34:41:938 2010 Sysname PIM/7/DF: (public net): Stop DFT for RP: 1.1.1.1 on
interface Vlan-interface2 (P51705)
// PIM received a better winner packet on VLAN-interface 2. The DF state changed from Offer to Lose.
The DF was set to 2.1.1.1, the DF election timer was stopped, and the DF of the RP was issued to the driver.
# Enable debugging for PIM events for the public network.
<Sysname> debugging pim event
*0.7326515 Sysname PIM/7/EVENT:(public net): PIM-SM: Downstream (*, 229.0.0.1) on
interface Vlan-interface10 (10.1.1.2) FSM transited from Joined to PPending. Prune
Received (S151270)
// PIM received a prune message. The downstream state machine of the outgoing interface
VLAN-interface 10 of the PIM-SM state entry (*, 229.0.0.1) transited from joined to prune pending.
*0.7327484 Sysname PIM/7/EVENT:(public net): PIM-SM: Downstream (*, 229.0.0.1) on
interface Vlan-interface10 (10.1.1.2) FSM transited from PPending to NoInfo. PPT Expired
(S15760)
204
// Because the prune pending timer timed out, the downstream state machine of the outgoing interface
VLAN-interface 10 of the PIM-SM state entry (*, 229.0.0.1) transited from prune pending to
no-information.
# Enable debugging for join/prune messages for the public network.
<Sysname> debugging pim join-prune receive
*0.6209953 Sysname PIM/7/JP:(public net): PIM ver 2 JP receiving 20.1.1.2 -> 224.0.0.13
on Vlan-interface20 (P012176)
*0.6209953 Sysname PIM/7/JP:(public net): Upstream 20.1.1.1, Groups 1, Holdtime 210
(P012178)
*0.6209953 Sysname PIM/7/JP:(public net): Group: 229.0.0.1/32 --- 1 joins 0 prunes
(P012184)
*0.6209953 Sysname PIM/7/JP:(public net): Join: 100.1.1.11/32 S (P012188)
// PIM received a join/prune message from 20.1.1.2 to 224.0.0.13 on VLAN-interface 20.
# Enable debugging for outbound PIM join/prune messages for the public network.
<Sysname> debugging pim join-prune send
*0.5916437 Sysname PIM/7/JP:(public net): PIM ver 2 JP
on Vlan-interface20 (P012176)
sending 20.1.1.2 -> 224.0.0.13
*0.5916437 Sysname PIM/7/JP:(public net): Upstream 20.1.1.1, Groups 1, Holdtime 210
(P012178)
*0.5916437 Sysname PIM/7/JP:(public net): Group: 229.0.0.1/32 --- 1 joins 0 prunes
(P012184)
*0.5916437 Sysname PIM/7/JP:(public net): Join: 100.1.1.11/32 S (P012188)
// PIM sent a join/prune message from 20.1.1.2 to 224.0.0.13 out of VLAN-interface 2.
<Sysname> debugging pim neighbor receive
*0.2605047 Sysname PIM/7/NBR:(public net): PIM ver 2 HEL receiving 10.1.1.1 -> 224.0.0.13
on Vlan-interface10 (P011857)
*0.2605047 Sysname PIM/7/NBR:(public net): Option: 1, length: 2 (P011891)
*0.2605062 Sysname PIM/7/NBR:(public net): Holdtime: 105 (P011898)
*0.2605062 Sysname PIM/7/NBR:(public net): Option: 2, length: 4 (P011891)
*0.2605062 Sysname PIM/7/NBR:(public net): Tbit: unset
(P011907)
*0.2605062 Sysname PIM/7/NBR:(public net): Lan delay: 500 (P011908)
*0.2605062 Sysname PIM/7/NBR:(public net): Override interval: 2500 (P011909)
*0.2605062 Sysname PIM/7/NBR:(public net): Option: 19, length: 4 (P011891)
*0.2605062 Sysname PIM/7/NBR:(public net): DR priority: 1 (P011916)
*0.2605062 Sysname PIM/7/NBR:(public net): Option: 20, length: 4 (P011891)
*0.2605094 Sysname PIM/7/NBR:(public net): Genid: 0X67DC7FAB (P011923)
// PIM received a PIMv2 hello message from 10.1.1.1 to 224.0.0.13 on VLAN-interface 10.
# Enable debugging for outbound packets related to PIM neighbors for the public network.
<Sysname> debugging pim neighbor send
*0.1526312 Sysname PIM/7/NBR:(public net): PIM ver 2 HEL sending 10.1.1.1 -> 224.0.0.13
on Vlan-interface10 (P011857)
*0.1526312 Sysname PIM/7/NBR:(public net): Option: 1, length: 2 (P011891)
*0.1526312 Sysname PIM/7/NBR:(public net): Holdtime: 105 (P011898)
*0.1526328 Sysname PIM/7/NBR:(public net): Option: 2, length: 4 (P011891)
*0.1526328 Sysname PIM/7/NBR:(public net): Tbit: unset
(P011907)
*0.1526343 Sysname PIM/7/NBR:(public net): Lan delay: 500 (P011908)
*0.1526343 Sysname PIM/7/NBR:(public net): Override interval: 2500 (P011909)
205
*0.1526343 Sysname PIM/7/NBR:(public net): Option: 19, length: 4 (P011891)
*0.1526343 Sysname PIM/7/NBR:(public net): DR priority: 1 (P011916)
*0.1526343 Sysname PIM/7/NBR:(public net): Option: 20, length: 4 (P011891)
*0.1526343 Sysname PIM/7/NBR:(public net): Genid: 0X67DC7FAB (P011923)
// PIM sent a PIMv2 hello message from 10.1.1.1 to 224.0.0.13 out of VLAN-interface 10.
# Enable debugging for inbound PIM register messages for the public network.
<Sysname> debugging pim register receive
*0.4825671 Sysname PIM/7/REG:(public net): PIM ver 2 RSP receiving 12.12.12.12 -> 100.1.1.1
on Vlan-interface20 (S01648)
*0.4825671 Sysname PIM/7/REG:(public net): Register Stop: (100.1.1.10, 229.0.0.1)
(S01650)
// PIM received a register-stop message from 12.12.12.12 to 100.1.1.1 on VLAN-interface 20. In the
register-stop message, the group address is 229.0.0.1 and the multicast source address is 100.1.1.10.
# Enable debugging for outbound PIM register messages for the public network.
<Sysname> debugging pim register send
*0.5554875 Sysname PIM/7/REG:(public net): PIM ver 2 REG sending 100.1.1.1 -> 12.12.12.12
on Vlan-interface20 (S01729)
*0.5554875 Sysname PIM/7/REG:(public net):
Border bit: false Null bit: true (S01737)
*0.5554875 Sysname PIM/7/REG:(public net): Encapsulated ip src: 100.1.1.11, dst:229.0.0.1,
len: 20 (S01744)
// PIM sent a PIMv2 register message from 100.1.1.1 to 12.12.12.12 out of VLAN-interface 20. The border
bit is not set, but Null bit is set.
# Enable debugging for PIM multicast routing table state changes for the public network.
<Sysname> debugging pim routing-table
*0.4825125 Sysname PIM/7/ROUT:(public net): PIM-SM: Create (100.1.1.10, 229.0.0.1) entry
in mrt. (S018118)
*0.4825125 Sysname PIM/7/ROUT:(public net): PIM-SM: Adding iif 100.1.1.1 to (100.1.1.10,
229.0.0.1). (S012740)
*0.4825125 Sysname PIM/7/ROUT:(public net): PIM-SM: Add oif: register for (100.1.1.10,
229.0.0.1) (S017199)
// PIM created a PIM-SM state entry (100.1.1.10, 229.0.0.1), with the interface toward 100.1.1.1 as the
incoming interface and the registered virtual interface as the outgoing interface.
# Enable debugging for inbound PIM packets related to the BSR and the RP for the public network.
<Sysname> debugging pim rp receive
//*0.2776421 Sysname PIM/7/RP:(public net): PIM ver 2 CRP receiving 10.1.1.2 -> 19.1.1.1
on Vlan-interface10 (S01409)
*0.2776421 Sysname PIM/7/RP:(public net): C-RP 12.12.12.12, prefix count 1, priority: 0,
holdtime 150 (S01433)
*0.2776421 Sysname PIM/7/RP:(public net): 224.0.0.0/4 (S01454)
*0.2776421 Sysname PIM/7/RP:(public net): Admin Scope Zone: 0 (S01455)
// PIM received a PIMv2 C-RP advertisement message from 10.1.1.2 to 19.1.1.1 on VLAN-interface 10.
PIM ver 2 BSR receiving 10.1.1.1 -> 224.0.0.13 on Vlan-interface10
(S01500)
*0.3307890 Sysname PIM/7/RP:(public net): BSR 19.1.1.1, frag 0, pri 0, hash mask
len 30 (S01520)
*0.3307890 Sysname PIM/7/RP:(public net): Group 224.0.0.0/4: frags 1, C-RP's 1 (S01544)
*0.3307890 Sysname PIM/7/RP:(public net): 12.12.12.12 pri: 0, holdtime: 150 (S01568)
206
*0.3307890 Sysname PIM/7/RP:(public net): Receive BSR packet. And use BSR Mechanism now.
(S031694)
// PIM received a PIMv2 bootstrap message from 10.1.1.1 to 224.0.0.13 on VLAN-interface 10.
# Enable debugging for outbound PIM packets related to BSR and RP for the public network.
<Sysname> debugging pim rp send
*0.3303375 Sysname PIM/7/RP:(public net): PIM ver 2 CRP sending 10.1.1.2 -> 19.1.1.1 on
Vlan-interface10 (S01409)
*0.3303375 Sysname PIM/7/RP:(public net): C-RP 12.12.12.12, prefix count 1, priority: 0,
holdtime 150 (S01433)
*0.3303375 Sysname PIM/7/RP:(public net): 224.0.0.0/4 (S01454)
*0.3303375 Sysname PIM/7/RP:(public net): Admin Scope Zone: 0 (S01455)
// PIM sent a PIMv2 C-RP advertisement message from 10.1.1.2 to 19.1.1.1 out of VLAN-interface 10.
*0.2780906 Sysname PIM/7/RP:(public net): PIM ver 2 BSR sending 20.1.1.1 -> 224.0.0.13
on Vlan-interface20 (S01500)
*0.2780906 Sysname PIM/7/RP:(public net): BSR 19.1.1.1, frag 0, pri 0, hash masklen 30
(S01520)
*0.2780906 Sysname PIM/7/RP:(public net): Group 224.0.0.0/4: frags 2, C-RP's 2(S01544)
*0.2780906 Sysname PIM/7/RP:(public net): 10.1.1.2 pri: 0, holdtime: 150 (S01568)
*0.2780906 Sysname PIM/7/RP:(public net): 12.12.12.12 pri: 0, holdtime: 150 (S01568)
// PIM sent a PIMv2 BSR bootstrap message from 20.1.1.1 to 224.0.0.13 out of VLAN-interface 20.
# Enable debugging for inbound PIM state refresh packets for the public network.
<Sysname> debugging pim state-refresh receive
*0.8386062 Sysname PIM/7/SRM:(public net): PIM ver 2 SRM receiving 20.1.1.1 -> 224.0.0.13
on Vlan-interface20 (D19670)
*0.8386062 Sysname PIM/7/SRM:(public net): Group address: 229.0.0.1/32 flags: 00000000
(D19672)
*0.8386062 Sysname PIM/7/SRM:(public net): Source address: 100.1.1.11 (D19674)
*0.8386062 Sysname PIM/7/SRM:(public net): Originator address: 20.1.1.1 (D19676)
*0.8386062 Sysname PIM/7/SRM:(public net): preference: 0 metric: 0 mask length: 0 (D19696)
*0.8386062 Sysname PIM/7/SRM:(public net): ttl: 254 prune indicator: unset prunenow: set
assert override: set (D19699)
*0.8386062 Sysname PIM/7/SRM:(public net): interval: 1 (D19700)
// PIM received a state refresh packet from 20.1.1.1 to 224.0.0.13 on VLAN-interface 20.
# Enable debugging for outbound PIM state refresh packets for the public network.
<Sysname> debugging pim state-refresh send
*0.8345296 Sysname PIM/7/SRM:(public net): PIM ver 2 SRM sending 20.1.1.1 -> 224.0.0.13
on Vlan-interface20 (D19670)
*0.8345296 Sysname PIM/7/SRM:(public net): Group address: 229.0.0.1/32 flags: 00000000
(D19672)
*0.8345296 Sysname PIM/7/SRM:(public net): Source address: 100.1.1.11 (D19674)
*0.8345296 Sysname PIM/7/SRM:(public net): Originator address: 20.1.1.1 (D19676)
*0.8345296 Sysname PIM/7/SRM:(public net): preference: 0 metric: 0 mask length: 0 (D19696)
*0.8345312 Sysname PIM/7/SRM:(public net): ttl: 254 prune indicator: unset prunenow: unset
assert override: set (D19699)
*0.8345312 Sysname PIM/7/SRM:(public net): interval: 1 (D19700)
// PIM received a state refresh packet from 20.1.1.1 to 224.0.0.13 on VLAN-interface 2.
207
PKI debugging commands
debugging pki
Use debugging pki to enable PKI debugging.
Use undo debugging pki to disable PKI debugging.
Syntax
debugging pki { all | certificate access-control-policy | error | request | retrieval | verify }
undo debugging pki { all | certificate | error | request | retrieval | verify }
Default
PKI debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of IPsec debugging.
certificate access-control-policy: Specifies debugging for certificate attribute-based access control
policies.
error: Specifies PKI error debugging.
request: Specifies certificate request debugging.
retrieval: Specifies certificate retrieval debugging.
verify: Specifies certificate validation debugging.
Usage guidelines
Table 1 to Table 4 describe output fields and messages for the PKI debugging commands.
Table 130 Output from the debugging pki certificate access-control-policy command
Field
Description
the attribute number Match in attribute group
'group-number'
The certificate matches the attribute number in
certificate attribute group group-number.
the attribute number Not Match in attribute group
'group-number'
The certificate does not match the attribute number in
certificate attribute group group-number.
Not match the rule number in access control policy
'string'. Check the next rule.
The certificate did not match rule number in access
control policy string. Trying the next rule.
208
Table 131 Output from the debugging pki error command
Field
Description
SCEP receive message: wrong MIME content type
Type of the content of the SCEP packet received from
the CA is not correct.
Error while sending message
Error occurred when SCEP packet is sent.
PKCS#7 develope: reason
Reason for PKCS#7 de-encapsulation failure.
PKCS#7 develope: illegal size of payload
The size of the payload in the de-encapsulated packet
is illegal.
Certificate enroll failed, error code is 72
Certificate request failed. The error code is 72, which
means that the key pair has been used before.
Table 132 Output from the debugging pki request command
Field
Description
PKCS#7 envelope
PKCS#7 encapsulation.
PKCS#7 develope
PKCS#7 de-encapsulation.
SCEP send message
The PKI module sent a message to the CA through
SCEP.
SCEP receive message
The PKI module received a message from the CA
through SCEP.
PKI Get the Signed Certificates
The entity obtained the signed certificates.
issuer
DN of the certificate issuer.
Table 133 Output from the debugging pki retrieval command
Field
Description
PKI GetCert CA&RA
The PKI module obtained a CA/RA certificate chain
from the CA server.
PKCS#7 envelope
PKCS#7 encapsulation.
PKCS#7 develope
PKCS#7 de-encapsulation.
SCEP send message
The PKI module sent a message to the CA through
SCEP.
SCEP receive message
The PKI module received a message from the CA
through SCEP.
Examples
# Configure a certificate attribute-based access control policy and log in to the device through IE using
HTTPS. The IE client certificate is as shown in Figure 1.
209
Figure 2 IE client certificate
# Configure a certificate attribute group and a certificate attribute-based access control policy on the
device.
<Sysname> system-view
[Sysname] pki certificate attribute-group 1
[Sysname-pki-cert-attribute-group-1] attribute 1 issuer-name dn ctn ssl
[Sysname-pki-cert-attribute-group-1] attribute 2 issuer-name dn nctn hhh01
[Sysname-pki-cert-attribute-group-1] attribute 3 subject-name dn ctn ssl-client
[Sysname-pki-cert-attribute-group-1] quit
[Sysname] pki certificate access-control-policy 1
[Sysname-pki-cert-acp-1] rule 1 permit 1
[Sysname-pki-cert-acp-1] quit
# Enable HTTPS service.
[Sysname] ip https certificate access-control-policy 1
[Sysname] ip https ssl-server-policy ssl
[Sysname]ip https enable
[Sysname] quit
# Enable debugging for certificate attribute-based access control policy and then log in through IE.
<Sysname> debugging pki certificate access-control-policy
*0.35979976 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 1 Match in attribute
group '1'. Check the next attribute.
*0.35980120 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 2 Match in attribute
group '1'. Check the next attribute.
210
*0.35980270 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 3 Match in attribute
group '1'. Check the next attribute.
*0.35980425 Sysname PKI/7/PKI_Debug:PKI_Certificate: Match the rule id: 1, action: permit
in access control policy '1'. Access Permit
// The client certificate passed the certificate validation after it matched Attributes 1, 2, and 3 in the
certificate attribute group.
# Disable HTTPS service and add a new certificate attribute group.
<Sysname> system-view
[Sysname] undo ip https enable
[Sysname] pki certificate attribute-group 2
[Sysname-cert-attribute-group-2] attribute 1 issuer-name dn nctn ssl
[Sysname-cert-attribute-group-2] attribute 2 issuer-name dn nctn hhh01
[Sysname-cert-attribute-group-2] attribute 3 subject-name dn ctn ssl-client
[Sysname-cert-attribute-group-2] quit
[Sysname] pki certificate access-control-policy 2
[Sysname-cert-acp-2] rule 1 permit 2
[Sysname-cert-acp-2] quit
# Enable HTTPS service.
[Sysname] ip https certificate access-control-policy 2
[Sysname] ip https ssl-server-policy ssl
[Sysname]ip https enable
# Log in by using an IE browser.
*0.38231901 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 1 Not Match in
attribute group '2'.
*0.38232030 Sysname PKI/7/PKI_Debug:PKI_Certificate: Not match the rule 1 inaccess control
policy'2'. Check the next rule.
*0.38232190 Sysname PKI/7/PKI_Debug:PKI_Certificate: Certificate doesn't match any rules
in access control policy '2'. Access Deny
// The client certificate failed the certificate validation after it failed to match Attribute 1, 2, or 3 of the
certificate attribute group.
# Disable HTTPS service and apply multiple certificate attribute groups to the certificate attribute-based
access control policy.
[Sysname] undo ip https enable
[Sysname] pki certificate access-control-policy 2
[Sysname-cert-acp-2] rule 1 permit 2
[Sysname-cert-acp-2] rule 2 permit 1
[Sysname-cert-acp-2] quit
# Enable HTTPS service.
[Sysname] ip https certificate access-control-policy 2
[Sysname] ip https ssl-server-policy ssl
[Sysname] ip https enable
# Log in by using an IE browser.
*0.38011098 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 1 Not Match in
attribute group '2'.
*0.38011221 Sysname PKI/7/PKI_Debug:PKI_Certificate: Not match the rule 1 in access
control policy'2'. Check the next rule.
*0.38011383 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 1 Match in
211
attribute group '1'. Check the next attribute.
*0.38011540 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 2 Match in
attribute group '1'. Check the next attribute.
*0.38011706 Sysname PKI/7/PKI_Debug:PKI_Certificate: the attribute 3 Match in
attribute group '1'. Check the next attribute.
*0.38011860 Sysname PKI/7/PKI_Debug:PKI_Certificate: Match the rule id: 2, ac
tion: permit in access control policy '2'. Access Permit
// The client certificate passed the client certificate validation after failing to match Attribute 1 but
successfully matching the second rule in the policy.
# Enable PKI certificate retrieval debugging. When a local certificate is requested after a CA certificate
is retrieved, output similar to the following example is generated:
<Sysname> debugging pki retrieval
[Sysname] pki retrieval-certificate ca domain crt
Retrieving CA/RA certificates. Please wait a while......
*0.507125 Sysname PKI/7/PKI_Debug:Host: 4.4.4.133
// The host IP address of the CA server is 4.4.4.133.
*0.507141 Sysname PKI/7/PKI_Debug:Port: 446
// The port number of the SCEP protocol is 446.
*0.507141 Sysname PKI/7/PKI_Debug:Path: 6953bf7fb5b1cf514376243ce67ebed1209c292a
// The output shoes the path of the CA server.
*0.507157 Sysname PKI/7/PKI_Debug:HTTP request message is: GET
/6953bf7fb5b1cf514376243ce67ebed1209c292a/pkiclient.exe?operation=GetCACert&message=r
sa HTTP/1.0
// The content of the HTTP request message is "getting the CA certificate".
*0.507157 Sysname PKI/7/PKI_Debug:Start to send message...........
*0.507157 Sysname PKI/7/PKI_Debug:SCEP send message:IP = 0x85040404
// The PKI module sent a packet to the CA through SCEP.
The trusted CA's finger print is:
MD5
fingerprint:8FDC C669 7A95 5505 8C0A 8633 818D A0A1
SHA1 fingerprint:8CCD 07AD 6C9A 229B 3378 2430 F038 A142 D175 190E
// The certificate fingerprint of the CA was calculated by using the hash algorithm.
Is the finger print correct?(Y/N):
*0.507250 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned status code 200
// The PKI module received a status code from the CA server through SCEP, which means OK.
*0.507266 Sysname PKI/7/PKI_Debug:Get CA certificates: received 1 certificates.
//The PKI module received the CA certificate through SCEP.
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N]:y
Saving CA/RA certificates chain, please wait a moment......
CA certificates retrieval success.
[Sysname]
%Aug 8 11:23:55:250 2006 Sysname PKI/4/Verify_CA_Root_Cert:CA root certificate of the
domain crt is trusted.
// The CA root certificate of PKI domain crt is trusted.
212
%Aug 8 11:23:55:266 2006 Sysname PKI/4/Update_CA_Cert:Update CA certificates of the Domain
crt successfully.
// The PKI module updated the CA certificate of PKI domain crt successfully.
%Aug 8 11:23:55:266 2006 Sysname PKI/4/CA_Cert_Retrieval:Retrieval CA certificates of
the domain crt successfully.
// The PKI module obtained the CA certificate of PKI domain crt successfully.
*0.514266 Sysname PKI/7/PKI_Debug:Certificate-1
// The PKI module obtained the first certificate of the certificate chain.
*0.514282 Sysname PKI/7/PKI_Debug:PKI GetCert CA&RA: found certificate with
subject: CN=rsa,OU=sec,O=h3c,C=cn
*0.514282 Sysname PKI/7/PKI_Debug:
issuer: issuer: CN=rsa,OU=sec,O=h3c,C=cn
*0.514282 Sysname PKI/7/PKI_Debug:
PKI GetCert CA&RA: general purpose
*0.514282 Sysname PKI/7/PKI_Debug:
Add to trust pstSkTrust
// The PKI module added the certificate to the trusted certificate list.
[Sysname] pki request-certificate domain crt kkk
// The PKI module sent a local certificate request.
Certificate is being requested, please wait......
[Sysname]
Enrolling the local certificate,please wait a while......
*0.528672 Sysname PKI/7/PKI_Debug:SCEP transaction id: 8DDAA53A978FB25EDBC614561176E98D
// The SCEP ID is 8DDAA53A978FB25EDBC614561176E98D.
*0.528688 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: pkcs10 request 231 bytes
// The size of the certificate request message in PKCS#10 format is 231 bytes.
*0.528688 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: successfully encrypted payload
// The payload has been encrypted successfully.
*0.528688 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: inner payload size 533 bytes
// The size of the inner payload is 533 bytes.
*0.529704 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: creating outer PKCS#7
// The PKI module was creating the external PKCS#7 file.
*0.529704 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: signature added successfully
// The PKI module added the signature successfully.
*0.529704 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding signed attributes
*0.529719 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding string attribute transId
*0.529719 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding string attribute messageType
*0.529719 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding octet attribute senderNonce
// The PKI module added string attributes transID and messageType and octet attribute senderNonce.
*0.528750 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: PKCS#7 data written successfully
// The PKCS#7 file has been written into the memory successfully.
*0.528750 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: applying base64 encoding
*0.528750 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: base64 encoded payload size: 1735 bytes
// The PKI module encoded 1735 bytes of payload using base64 and encapsulated the certificate
request message in PKCS#7 format.
*0.528766 Sysname PKI/7/PKI_Debug:SCEP send message:IP = 0x85040404
Certificate enroll Successfully!
213
Saving the local certificate to device......
Done!
// The local certificate was successfully enrolled and saved to the device.
%Aug 8 11:24:10:407 2006 Sysname PKI/4/Local_Cert_Request:Request local certificate of
the domain crt successfully.
*0.529407 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned status code 200
// The PKI module received a response from the CA server.
*0.529407 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reading outer PKCS#7
*0.529422 Sysname PKI/7/PKI_Debug:PKCS#7 develope: PKCS#7 payload size: 2302 bytes
*0.529422 Sysname PKI/7/PKI_Debug:PKCS#7 develope: PKCS#7 contains 1254 bytes of enveloped
data
//The PKCS#7 file contains 1254 bytes of encapsulated data.
*0.529422 Sysname PKI/7/PKI_Debug:PKCS#7 develope: verifying signature
*0.529438 Sysname PKI/7/PKI_Debug:PKCS#7 develope: signature ok
// The signature is OK.
*0.529438 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding signed attributes
*0.529438 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute transId
*0.529454 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 32 bytes for attribute
*0.529454 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reply transaction id:
8DDAA53A978FB25EDBC614561176E98D
// The PKI module found signed attribute transId and allocated 32 bytes for it.
*0.529469 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute messageType
*0.529469 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for attribute
*0.529469 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reply message type is good
// The PKI module found attribute messageType and allocated one byte for it.
*0.529485 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute senderNonce
*0.529485 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 16 bytes for attribute
*0.529485 Sysname PKI/7/PKI_Debug:
PKCS#7 develope: senderNonce in reply: :
*0.529500 Sysname PKI/7/PKI_Debug:32e82738 c9383260 b6816ac2 b26671c6
// The PKI module found attribute senderNonce in the response and allocated 16 bytes for it.
*0.529500 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute recipientNonce
*0.529500 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 16 bytes for attribute
*0.529516 Sysname PKI/7/PKI_Debug:
PKCS#7 develope: recipientNonce in reply:
*0.529532 Sysname PKI/7/PKI_Debug:3673eedb 03ebe0fc 9c7d89ff 55eafba5
// The PKI module found attribute recipientNonce in the response and allocated 16 bytes for it.
*0.529532 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute pkiStatus
*0.529532 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for attribute
*0.529532 Sysname PKI/7/PKI_Debug:PKCS#7 develope: pkistatus SUCCESS
// The PKI module found attribute pkiStatus and allocated one byte for it.
*0.529547 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reading inner PKCS#7
*0.529547 Sysname PKI/7/PKI_Debug:PKCS#7 develope: decrypting inner PKCS#7
*0.529547 Sysname PKI/7/PKI_Debug:PKCS#7 develope: PKCS#7 payload size: 1036 bytes
214
// The PKI module de-encapsulated the PKCS#7 file and found that the payload size is 1036 bytes.
# Enable certificate request debugging. Output similar to the following example is generated:
[Sysname] pki retrieval-certificate ca domain crt
// Retrieval the CA certificate.
Retrieving CA/RA certificates. Please wait a while......
*0.179079 Sysname PKI/7/PKI_Debug:SCEP send message:IP = 0x85040404
// The PKI module sent a packet to the CA through SCEP.
The trusted CA's finger print is:
MD5
fingerprint:8FDC C669 7A95 5505 8C0A 8633 818D A0A1
SHA1 fingerprint:8CCD 07AD 6C9A 229B 3378 2430 F038 A142 D175 190E
// The certificate fingerprint of the CA was calculated by using the hash algorithm.
Is the finger print correct?(Y/N):
*0.179266 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned status code 200
Before pressing ENTER you must choose 'YES' or 'NO'[Y/N]:y
Saving CA/RA certificates chain, please wait a moment......
CA certificates retrieval success.
[Sysname]
%Aug 8 11:18:25:438 2006 Sysname PKI/4/Verify_CA_Root_Cert:CA root certificate of the
domain crt is trusted.
// The CA root certificate of PKI domain crt is trusted.
%Aug 8 11:18:25:438 2006 Sysname PKI/4/Update_CA_Cert:Update CA certificates of the Domain
crt successfully.
// The PKI module updated the CA certificate of PKI domain crt successfully.
%Aug 8 11:18:25:454 2006 Sysname PKI/4/CA_Cert_Retrieval:Retrieval CA certificates of
the domain crt successfully.
// The PKI module obtained the CA certificate of PKI domain crt successfully.
*0.184454 Sysname PKI/7/PKI_Debug:
PKI GetCert CA&RA: general purpose
// The PKI module obtained the CA certificate successfully.
[Sysname] pki request-certificate domain crt kkk
// The PKI module issued a local certificate request.
Certificate is being requested, please wait......
[Sysname]
Enrolling the local certificate,please wait a while......
*0.244407 Sysname PKI/7/PKI_Debug:Create PKCS#10 request: token seen: CN=crtSysname1
*0.244407 Sysname PKI/7/PKI_Debug:Create PKCS#10 request: CN=crtSysname1 added
*0.244407 Sysname PKI/7/PKI_Debug:Create PKCS#10 request: subject dn set to
'CN=crtSysname1'
// The PKI module created the DN used for certificate request.
*0.244422 Sysname PKI/7/PKI_Debug:Host: 4.4.4.133
*0.244422 Sysname PKI/7/PKI_Debug:Port: 446
*0.244422 Sysname PKI/7/PKI_Debug:Path: 6953bf7fb5b1cf514376243ce67ebed1209c292a
*0.244438 Sysname PKI/7/PKI_Debug:SCEP transaction id: 038DE310FA1404F6781ED659158FE236
// The output shows the following:
•
The host address of the CA server is 4.4.4.133.
215
•
The port number of the SCEP protocol is 446.
•
The path of the CA server is 6953bf7fb5b1cf514376243ce67ebed1209c292a.
•
The SCEP ID is 038DE310FA1404F6781ED659158FE236.
*0.244438 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: creating inner PKCS#7
// The PKI module was creating inner PKCS#7 file.
*0.244438 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: pkcs10 request 231 bytes
// The size of the certificate request message in PKCS#10 format is 231 bytes.
*0.244438 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: successfully encrypted payload
// The payload has been encrypted successfully.
*0.244454 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: inner payload size 533 bytes
// The size of the inner payload is 533 bytes.
*0.244454 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: creating outer PKCS#7
// The PKI module was creating the external PKCS#7 file.
*0.244454 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: signature added successfully
// The PKI module added the signature successfully.
*0.244469 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding signed attributes
*0.244469 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding string attribute transId
*0.244469 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding string attribute messageType
*0.244469 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: adding octet attribute senderNonce
//The PKI module added string attributes transID and messageType and octet attribute senderNonce.
*0.244485 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: PKCS#7 data written successfully
// The PKCS#7 file has been written into the memory successfully.
*0.244485 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: applying base64 encoding
*0.244485 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: base64 encoded payload size: 1735 bytes
// The PKI module encoded 1735 bytes of payload using base64 and encapsulated the certificate
request message in PKCS#7 format.
*0.244516 Sysname PKI/7/PKI_Debug:SCEP send message:IP = 0x85040404
// The PKI module sent a certificate request message through SCEP.
Certificate enroll Successfully!
Saving the local certificate to device......
Done!
%Aug 8 11:19:26:47 2006 Sysname PKI/4/Local_Cert_Request:Request local certificate of
the domain crt successfully.
*0.245063 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned status code 200
// The PKI module received a response from the CA server through SCEP.
*0.245063 Sysname PKI/7/PKI_Debug:Valid response from server
*0.245063 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reading outer PKCS#7
*0.245063 Sysname PKI/7/PKI_Debug:PKCS#7 develope: PKCS#7 payload size: 2302 bytes
*0.245079 Sysname PKI/7/PKI_Debug:PKCS#7 develope: PKCS#7 contains 1254 bytes of enveloped
data
//The PKCS#7 file contains 1254 bytes of encapsulated data.
*0.245079 Sysname PKI/7/PKI_Debug:PKCS#7 develope: verifying signature
*0.245079 Sysname PKI/7/PKI_Debug:PKCS#7 develope: signature ok
216
// The signature is OK.
*0.245079 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding signed attributes
*0.245079 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute transId
*0.245079 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 32 bytes for attribute
*0.245094 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reply transaction id:
038DE310FA1404F6781ED659158FE236
// The PKI module found signed attribute transId and allocated 32 bytes for it.
*0.245094 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute messageType
*0.245094 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for attribute
*0.245094 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reply message type is good
// The PKI module found attribute messageType and allocated one byte for it.
*0.245110 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute senderNonce
*0.245110 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 16 bytes for attribute
*0.245110 Sysname PKI/7/PKI_Debug:
PKCS#7 develope: senderNonce in reply: :
*0.245125 Sysname PKI/7/PKI_Debug:8fe84efc c3aa2942 ab0913b9 e6af539a
// The PKI module found attribute senderNonce in the response and allocated 16 bytes for it.
*0.245125 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute recipientNonce
*0.245125 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 16 bytes for attribute
*0.245141 Sysname PKI/7/PKI_Debug:
PKCS#7 develope: recipientNonce in reply:
*0.245141 Sysname PKI/7/PKI_Debug:cfbbbb7b a8737110 a5d618dd fb9133de
// The PKI module found attribute recipientNonce in the response and allocated 16 bytes for it.
*0.245141 Sysname PKI/7/PKI_Debug:PKCS#7 develope: finding attribute pkiStatus
*0.245141 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for attribute
*0.245141 Sysname PKI/7/PKI_Debug:PKCS#7 develope: pkistatus SUCCESS
// The PKI module found attribute pkiStatus and allocated one byte for it.
*0.245141 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reading inner PKCS#7
*0.245141 Sysname PKI/7/PKI_Debug:PKCS#7 develope: decrypting inner PKCS#7
*0.245141 Sysname PKI/7/PKI_Debug:PKCS#7 develope: PKCS#7 payload size: 1037 bytes
// The PKI module decapsulated the PKCS#7 file and found that the payload size is 1037 bytes.
*0.245141 Sysname PKI/7/PKI_Debug:PKI Get the Signed Certificates:
subject: CN=crtSysname1
*0.245141 Sysname PKI/7/PKI_Debug:
issuer: CN=sec,OU=software,O=aaa,C=cn
*0.245157 Sysname PKI/7/PKI_Debug:
Key usage: general purpose
// The PKI module obtained a certificate.

The DN of the entry is CN = crtSysname1.

The DN of the issuer is CN = sec,OU = software,O = aaa,C = cn.
# Enable certificate validation debugging. When a certificate validation operation is performed, output
similar to the following example is generated:
[Sysname] pki validate-certificate local domain crt
// Validate the local certificate.
Verifying certificate......
Serial Number:
217
FEADA5CA 028289AB CE95C6B6 E687639D
// The serial number of the certificate is FEADA5CA 028289AB CE95C6B6 E687639D.
Issuer:
C=cn
O=aaa
OU=software
CN=sec
// The above shows the DN of the issuer.
Subject:
CN=crtSysname3
// The above shows the Entity DN of the certificate being validated.
*0.745641 Sysname PKI/7/PKI_Debug:CN=crtSysname3
*0.745657 Sysname PKI/7/PKI_Debug:error at 0 depth:subject issuer mismatch
*0.745657 Sysname PKI/7/PKI_Debug:Check the last certificate self signed.
*0.745657 Sysname PKI/7/PKI_Debug:CN=crtSysname3
*0.745657 Sysname PKI/7/PKI_Debug:error at 0 depth:subject issuer mismatch
*0.745672 Sysname PKI/7/PKI_Debug:Lookup certificate issuers and push
into chain
*0.745672 Sysname PKI/7/PKI_Debug:CN=crtSysname3
*0.745672 Sysname PKI/7/PKI_Debug:error at 0 depth:subject issuer mismatch
*0.745688 Sysname PKI/7/PKI_Debug:Check certificates purpose.
*0.745688 Sysname PKI/7/PKI_Debug:Check certificates trust.
*0.746704 Sysname PKI/7/PKI_Debug:Check certificates revocation status.
Verify result: ok
// The PKI module checked the purpose, signature, and revocation status of the certificate. All items are
correct.
[Sysname]
%Aug 8 11:27:46:766 2006 Sysname PKI/4/Update_CRL:Update CRL of the domain crt
successfully.
%Aug 8 11:27:46:766 2006 Sysname PKI/4/Retrieval_CRL:Retrieval CRL of the domain crt
successfully.
// The PKI module updated and retrieved the CRL successfully.
%Aug 8 11:27:46:782 2006 Sysname PKI/4/Verify_Cert:Verify certificate CN=crtSysname3 of
the domain crt successfully.
*0.745782 Sysname PKI/7/PKI_Debug:ok
*0.745782 Sysname PKI/7/PKI_Debug:Verify certificate chain.
// The local certificate passed validation.
[Sysname] pki validate-certificate ca domain crt
Verifying certificate......
Serial Number:
EF425C97 E737B289 BB576A4B 5F657D86
Issuer:
C=cn
O=hhh
OU=software
CN=sec
Subject:
C=cn
218
O=hhh
OU=software
CN=sec
Verify result: ok
[Sysname]
%Aug
8 11:28:00:266 2006 Sysname PKI/4/Verify_Cert:Verify certificate CN=sec,OU=sof
tware,O=hhh,C=cn of the domain crt successfully.
*0.759266 Sysname PKI/7/PKI_Debug:Check the last certificate self signed.
*0.759282 Sysname PKI/7/PKI_Debug:Lookup certificate issuers and push
into chain
*0.759282 Sysname PKI/7/PKI_Debug:Check certificates purpose.
*0.759282 Sysname PKI/7/PKI_Debug:Check certificates trust.
*0.759297 Sysname PKI/7/PKI_Debug:Verify certificate chain.
// The CA certificate passed validation.
#Enable PKI error debugging. When an incorrect URL is specified for certificate retrieval, output similar
to the following example is generated:
<Sysname> debugging pki error
[Sysname] pki retrieval-certificate ca domain crt
Retrieving CA/RA certificates. Please wait a while......
Get CA/RA certificates error.
[Sysname]
%Aug 21 10:35:15:766 2006 Sysname PKI/4/CA_Cert_Retrieval:Fail to retrieval CA
certificates of the domain crt.
*Aug 21 10:35:15:766 2006 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned
status code 200
*Aug 21 10:35:15:766 2006 Sysname PKI/7/PKI_Debug:SCEP receive message: wrong MIME content
type
*Aug 21 10:35:15:766 2006 Sysname PKI/7/PKI_Debug:Error while sending message
// The SCEP message received from the CA states that the URL is incorrect.
[Sysname-pki-domain-crt] display this
#
pki domain crt
ca identifier rsaSysname
certificate request url http://4.4.4.133:446/6953bf7fb5b1cf514376243ce67ebed12
certificate request from ca
certificate request entity crt
certificate request polling interval 5
certificate request polling count 5
certificate request mode auto password simple kkk
crl url http://4.4.4.133:447/security%20rsa.crl
ldap-server ip 4.4.4.133
#
return
[Sysname-pki-domain-crt] certificate request url
http://4.4.4.133:446/6953bf7fb5b1cf514376243ce67ebed1209c292a
[Sysname-pki-domain-crt] quit
[Sysname] pki retrieval-certificate ca domain crt
Retrieving CA/RA certificates. Please wait a while......
219
The trusted CA's finger print is:
MD5
fingerprint:8FDC C669 7A95 5505 8C0A 8633 818D A0A1
SHA1 fingerprint:8CCD 07AD 6C9A 229B 3378 2430 F038 A142 D175 190E
Is the finger print correct?(Y/N):
*Aug 21 10:37:09:493 2006 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned
status code 200y
Saving CA/RA certificates chain, please wait a moment......
CA certificates retrieval success.
// The PKI module obtained the CA certificate successfully.
[Sysname]
%Aug 21 10:37:10:875 2006 Sysname PKI/4/Verify_CA_Root_Cert:CA root certificate of the
domain crt is trusted.
// The CA root certificate of PKI domain crt is trusted.
%Aug 21 10:37:10:891 2006 Sysname PKI/4/Update_CA_Cert:Update CA certificates of the
Domain crt successfully.
// The PKI module updated the CA certificate of PKI domain crt successfully.
%Aug 21 10:37:10:891 2006 Sysname PKI/4/CA_Cert_Retrieval:Retrieval CA certificates of
the domain crt successfully.
// The PKI module obtained the CA certificate of PKI domain crt successfully.
*Aug 21 10:37:10:891 2006 Sysname PKI/7/PKI_Debug:
PKI GetCert CA&RA: general purpose
[Sysname]pki request-certificate domain crt kkk
Certificate is being requested, please wait......
[Sysname]
Enrolling the local certificate,please wait a while......
*Aug 21 10:37:26:250 2006 Sysname PKI/7/PKI_Debug:PKCS#7 envelope: successfully encrypted
payload
Certificate enroll failed!
// The payload was encrypted successfully.
%Aug 21 10:37:26:946 2006 Sysname PKI/4/Local_Cert_Request:Fail to request local
certificate of the domain crt.
// The PKI module failed to request a local certificate for PKI domain crt.
*Aug 21 10:37:26:962 2006 Sysname PKI/7/PKI_Debug:SCEP receive message: Server returned
status code 200
// The status code returned by the CA server is 200.
*Aug 21 10:37:26:962 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 32 bytes
for attribute
*Aug 21 10:37:26:962 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for
attribute
*Aug 21 10:37:26:962 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 16 bytes
for attribute
*Aug 21 10:37:26:977 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 16 bytes
for attribute
*Aug 21 10:37:26:977 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for
attribute
*Aug 21 10:37:26:977 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: pkistatus FAILURE
*Aug 21 10:37:26:993 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: allocating 1 bytes for
attribute
220
*Aug 21 10:37:26:993 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: reason: Transaction
not permitted or supported
*Aug 21 10:37:26:993 2006 Sysname PKI/7/PKI_Debug:PKCS#7 develope: illegal size of payload
// The size of the payload after PKCS#7 decapsulation is invalid.
*Aug 21 10:37:27:16 2006 Sysname PKI/7/PKI_Debug:Certificate enroll failed, error code
is 72
// The PKI module failed to request a local certificate because the key pair was already used.
221
Policy-based routing debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ip policy-based-route
Use debugging ip policy-based-route to enable policy-based routing (PBR) debugging.
Use undo debugging ip policy-based-route to disable PBR debugging.
Syntax
debugging ip policy-based-route
undo debugging ip policy-based-route
Default
PBR debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 1 describes output fields and messages for the debugging ip policy-based-route command.
Table 134 Output from the debugging ip policy-based-route command
a. Field
b. Description
d. Data plane.
c. DP
e. This field is only supported by
multi-core devices.
f.
IP policy based routing success
g. PBR succeeded.
i.
PBR failed because the interface
with index [STRING] does not
exist.
j.
Support for this output depends
on the device model.
l.
PBR failed because the next hop
with index [STRING] does not
exist.
h. IP policy based routing fail for
interface index [STRING] not
exist
k. IP policy based routing fail for
next-hop [STRING] error
n. Memory allocation for [STRING]
m. No memory space while
failed due to insufficient memory
space.
[STRING]
o. headlen
p. Header length.
222
a. Field
b. Description
q. tos
r. Type of service.
s. pktlen
t.
u. pktid
v. Packet ID.
w. protocol
x. Upper layer protocol.
y. s
z. Source address.
aa. d
bb. Destination address.
Packet length.
Examples
# Enable PBR debugging. The output in this example was created when the following conditions exist:
•
Configure PBR on Ethernet 1/0 to allow forwarding packets with a length from 10 to 100 bytes to
Serial 2/0.
•
On another device, send ping packets (with a length from 10 to 100 bytes) to Ethernet 1/0.
<Sysname> debugging ip policy-based-route
*0.513578 Sysname PBR/8/POLICY-ROUTING:IP policy based routing success : output interface
Serial2/0 is down
// PBR succeeded, but the outgoing interface Serial 2/0 was down, resulting in packet forwarding
failures.
223
Port security debugging commands
The port security module name is identified as "PORTSEC" in debugging messages.
Some information in this chapter is device type specific. Devices in this chapter are categorized
depending on their IRF capability and support for interface cards that use independent processors for
forwarding traffic, as shown in Table 1.
Table 135 Device types
Device type
Distributed devices
Interface cards with
on-card processors
IRF capability
Examples
No
HP 6600 routers (except
for 6602)
Yes
Yes (in standalone mode)
Distributed IRF devices
Yes
Yes (in IRF mode)
Centralized devices
No
No
Centralized IRF devices
No
Yes
HP 12500 switches
HP 10500 switches
HP 12500 switches
HP 10500 switches
HP MSR routers
HP 6602 router
HP 5800 switches
HP 5500 switches
The output description tables in this document only contain fields and messages that require an
explanation.
debugging port-security
Use debugging port-security to enable port security debugging.
Use undo debugging port-security to disable port security debugging.
Syntax
Centralized devices:
debugging port-security { all | error | event }
undo debugging port-security { all | error | event }
Distributed devices/centralized IRF devices:
debugging port-security { all | error | event } [ slot slot-number ]
undo debugging port-security { all | error | event } [ slot slot-number ]
Distributed IRF devices:
debugging port-security { all | error | event } [ chassis chassis-number slot slot-number ]
undo debugging port-security { all | error | event } [ chassis chassis-number slot slot-number ]
224
Default
Port security debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of port security debugging.
error: Specifies port security error debugging.
event: Specifies port security event debugging.
slot slot-number: Specifies a card by its slot number. (Distributed devices—In standalone mode.)
slot slot-number: Specifies the ID of an IRF member device. (Centralized IRF devices.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number
argument represents the member ID of the IRF member device. The slot-number argument represents the
slot number of the card. (Distributed devices—In IRF mode.)
Usage guidelines
Table 2 describes output fields and messages for the debugging port-security error command.
Table 136 Output from the debugging port-security error command
Field
Description
InvalidAuth
Invalid user.
Failed to handle set operation of PortSec security MAC
table.
The port security module failed to configure secure
MAC entries.
Failed to set PortMode.
The port security module failed to set port security
mode.
Failed to get physical control of IfIndex.
The port security module failed to obtain the physical
layer control information of the specified interface.
Configure IntrusionAction when failed to get portCB.
The port security module set intrusion protection
action when it failed to obtain the port control block.
Error: Unable to delete any MACs at interface: IfIndex.
Self slot is SlotNum.
The port security module failed to delete any MAC
address at interface IfIndex. The slot number is
SlotNum.
Failed to set PortCB by handle.
The device failed to configure the port data structure
on the port security control block.
Failed to delete security MAC from list.Self slot is
SlotID.
The port security module failed to delete secure MAC
entries from the table. The slot is SlotID.
There is no security MAC match the delete condition.
Self slot is SlotID.
No secure MAC entry matches the delete condition.
The slot is SlotID.
Port Security's state is disabled!
Port security is not enabled.
225
Field
Description
Failed to Alloc memory for RPC message, when
request backuping MAC Address table to slave
board!
Failed to alloc memory for RPC message, when
request backuping BlockMac table to slave board.
RPC failed, when backup BlockMac table to new
board!(RPC wrong=ErrorCode)
RPC failed, the BlockMac table is not synchronized to
the new board.
The device failed to allocate memory for RPC
messages when it was backing up the MAC address
table to other cards except the active MPU.
(Distributed devices/distributed IRF devices.)
The device failed to allocate memory for RPC
messages when it was backing up the MAC address
table to the subordinate devices. (Centralized IRF
devices.)
The device failed to allocate memory for RPC
messages when it was backing up the blocked MAC
address table to other cards except the active MPU.
(Distributed devices/distributed IRF devices.)
The device failed to allocate memory for RPC
messages when it was backing up the blocked MAC
address table to the subordinate devices. (Centralized
IRF devices.)
The device failed to allocate memory for RPC
messages when it was backing up the blocked MAC
address table to the new card. (Distributed
devices/distributed IRF devices.)
The device failed to allocate memory for RPC
messages when it was backing up the blocked MAC
address table to the new subordinate device.
(Centralized IRF devices.)
RPC failed and the secure MAC address table was not
synchronized to the new card. (Distributed
devices/distributed IRF devices.)
RPC failed and the secure MAC address table was not
synchronized to the new subordinate device.
(Centralized IRF devices.)
Failed to show port.
The port security module failed to display port
information.
Failed to show BlockMac.
The port security module failed to display blocked
MAC entries.
The port security module failed to synchronize the
secure MAC entries to other cards. (Distributed
devices/distributed IRF devices.)
Failed to sync security MAC for distribution.
The port security module failed to synchronize the
secure MAC entries to other devices. (Centralized IRF
devices.)
Failed to malloc for RPC message, when request
getting portsec-security port information from IO
board.
The port security module failed to allocate memory for
RPC messages when it tried to obtain port security
information from an interface card. (Distributed
devices/distributed IRF devices.)
Failed to operate get-next-BlockMac:BlockMac list
reached end.
The port security module failed to perform the
get-next-BlockMac operation. The current entry is the
last entry in the BlockMac list.
226
Field
Description
Failed to malloc for RPC message, when request
getting BlockMac number from a board.
The device failed to allocate memory for RPC
messages when it tried to obtain the number of
blocked MAC addresses.
Failed to malloc for RPC message, when request
getting BlockMac address from a board.
The device failed to allocate memory for RPC
messages when it tried to obtain blocked MAC
addresses.
MIB:OUITable proc block number is wrong.
MIB operation of OUI MAC entries. The number of
message blocks is incorrect.
MIB OUI set: self slot is in slave status, backup auto.
The port security module set the OUI table through a
MIB operation. The current MPU is a standby MPU
and backs up the OUIs automatically. (Distributed
devices/distributed IRF devices.)
The port security module set the OUI table through a
MIB operation. The current device is a subordinate
device and backs up the OUIs automatically.
(Centralized IRF devices.)
Table 3 describes output fields and messages for the debugging port-security event command.
Table 137 Output from the debugging port-security event command
Field
Description
InvalidAuth
Invalid user.
Portsec SecureMAC table process begin...
The port security module began to add secure MAC
entries.
Configure IntrusionAction, the same as current config.
The Intrusion action to be configured is the same as the
action that is already configured.
Configure IntrusionAction, NoShutdown the port.
The port security module brought up the port, because
the port has been shut down by the intrusion
protection feature.
Configure IntrusionAction, port is not shutdown yet.
Intrusion protection action is configured and the port is
not shut down.
PortSec NoShutdown port...
The port security module brought up the port.
PortSec receives a new SrcUnkown MAC but
portmode is not autolern, secure or userloginwithoui,
bypass it to macauth !
The port received a packet with an unknown source
MAC, but the port security mode is not autoLearn,
secure, or userLoginWithOUI. The port security
module starts to perform MAC authentication.
Get NULL pointer for delete count, alloc a memory
block for it...
The port security module prepares to remove the
secure MAC entries. Because the count pointer is null,
the device will allocate a memory block for it.
Security MAC distributed-backup is finished on slot
SlotID.
227
The port security module finished adding secure MAC
entries on the card in slot SlotID. (Distributed
devices/distributed IRF devices.)
The port security module finished adding secure MAC
entries on device SlotID. (Centralized IRF devices.)
Field
Description
Broadcast send a MAC address sync msg,
IfIndex:IFINDEX, Status :STATUS, VlanID :VLANID,
Mac-addr: MacAddress, OpType: OPTYPE. Self slot is
SELFSLOTID.
The port security module broadcast a MAC address
synchronization message.
The port security module received an RPC message for
displaying port information of the current card.
(Distributed devices/distributed IRF devices.)
RPC receive show port msg from self board!
The port security module received an RPC message for
displaying port information of the current device.
(Centralized devices/centralized IRF devices.)
Examples
# Enable port security error debugging. Output similar to the following example is generated when you
perform the following tasks:
•
Enable port security on the device.
•
Change the port security mode to secure.
•
Add a secure MAC address.
<Sysname> debugging port-security error
[Sysname] port-security enable
Notice: The port-control of 802.1X will be restricted to auto when port-security is enabled.
Please wait...
Done.
[Sysname] interface gigabitethernet 1/1
[Sysname-GigabitEthernet1/1] port-security port-mode secure
[Sysname-GigabitEthernet1/1] port-security mac-address security 1-1-1 vlan 1
Error: Can not operate security MAC address for current port mode is not autoLearn!
*Apr 28 23:54:57:979 2000 Sysname PORTSEC/7/Event:InvalidPort,InvalidAuth,error occured
while adding security MAC(0001-0001-0001, IfIndex 0x900002) to list.
*Apr 28 23:54:57:980 2000 Sysname PORTSEC/7/Error:InvalidPort,InvalidAuth,Failed to
handle set operation of PortSec security MAC table.
// The port security module failed to add the MAC address to the secure MAC address table, because
the port security mode of the current port was not autoLearn.
# Enable port security event debugging. Output similar to the following example is generated when you
perform the following tasks:
•
Enable port security on the device.
•
Change the port security mode to secure.
•
Add a secure MAC address.
<Sysname> debugging port-security event
[Sysname] port-security enable
Notice: The port-control of 802.1X will be restricted to auto when port-security is enabled.
Please wait...
Done.
[Sysname] interface gigabitethernet 1/1
[Sysname-GigabitEthernet1/1] port-security port-mode secure
[Sysname-GigabitEthernet1/1] port-security mac-address security 1-1-1 vlan 1
228
Error: Can not operate security MAC address for current port mode is not autoLearn!
*Apr 28 23:54:57:975 2000 Sysname
PORTSEC/7/Event:InvalidPort,InvalidAuth,ExecID=1,Optype=2, Calling portsec cfg
module...
// The device called the port security configuration module.
*Apr 28 23:54:57:976 2000 Sysname PORTSEC/7/Event:InvalidPort,InvalidAuth,CFG:Portsec
SecureMAC table process begin...
// The port security module tried to add a secure MAC entry.
*Apr 28 23:54:57:978 2000 Sysname PORTSEC/7/Event:Port:GigabitEthernet1/1,InvalidAuth,
PortMode is not autoLearn!
// The port security module failed to add the secure MAC entry because the port security mode was not
autoLearn.
229
Portal debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging portal
Use debugging portal to enable portal debugging.
Use undo debugging portal to disable portal debugging.
Syntax
debugging portal { { acl | all | connection | packet [ acl acl-number ] } interface interface-type
interface-number | error | tcp-cheat }
undo debugging portal { { acl | all | connection | packet } interface interface-type interface-number |
error | tcp-cheat }
Default
Debugging for portal is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
acl: Specifies portal ACL debugging.
all: Specifies all types of portal debugging.
connection: Specifies portal connection debugging.
packet: Specifies portal packet debugging.
acl acl-number: Specifies an ACL to filter portal packets. The value range for the acl-number argument is
2000 to 3999. If you specify ACLs multiple times, the most recently specified ACL applies. Only the
source IP address field in the specified ACL rules is used for packet filtering.
interface: Specifies debugging on an interface.
interface-type interface-number: Specifies an interface by its type and number.
error: Specifies portal error debugging.
tcp-cheat: Specifies portal TCP anti-spoofing debugging.
Usage guidelines
Table 1 describes output fields and messages for the debugging portal tcp-cheat command.
230
Table 138 Output from the debugging portal tcp-cheat command
Field
Description
Source
Source information flag.
MAC
Source MAC address of TCP connection.
VLAN
ID of Source VLAN of TCP connection.
PortIndex
Index of source port of TCP connection.
changed from STATUS_A to STATUS_B
The status is changed from status A to status B.
Table 2 describes output fields and messages for the debugging portal packet command.
Table 139 Output from the debugging portal packet command
Field
Description
Portal socket receive packet length: packetlength
Length of the packet received through the portal
socket.
Portal check packet OK
Indicates whether the received packet is legal.
Portal packet head
Packet header.
SN: serialNo
Packet serial number.
Type: PacketType
Packet type.
AttrNum: Number
Number of attributes of the packet.
ErrCode: Number
Packet error code.
UserIP: IP-Address
IP address of the accessing user.
Portal packet attribute list
Attribute list of the packet.
Portal raw packet
Packet form.
Portal socket send packet length: packetlength
Length of the packet sent through the portal socket.
Table 3 describes output fields and messages for the debugging portal connection command.
Table 140 Output from the debugging portal connection command
Field
Description
Timer timer-name is started
Started timer named timer-name.
user index
User index.
state
Current state of the user.
IP
IP address of the user.
Timer timer-name is stopped
A timer named timer-name is stopped.
send message-name message to moduleA
Sent a message named message-name to module A.
State stateA changing to stateB
User state changed from state A to state B.
Recv portal message-name in state-name state
Received a message named message-name in the state
named state-name.
[ACM]
Debugging information output by ACM module.
231
Field
Description
Processing message-name
Processing the message named message-name.
1 user index IP ip-address
User index is index, and IP address is ip-address.
recv message-name from ACM
Received a message named message-name from ACM
module.
recv message-name from DRV
Received a message named message-name from the
driver.
Table 4 describes output fields and messages for the debugging portal acl command.
Table 141 Output from the debugging portal acl command
Field
Description
Portal interface
Name of the interface enabled with Portal.
Status
Portal running status. “Running” means the portal is
running normally.
Action of the matching rule:
•
•
•
•
Action
permit.
redirect.
deny.
NULL.
Match rule
Matching rule.
Inbound interface
Inbound interface.
Type
Portal rule type: Static or Dynamic.
Source
Source information of the matching rule.
IP
Source IP address of the matching rule.
Mask
Source mask of the matching rule.
Protocol
Protocol number of the matching rule.
Mac
Source MAC address of the matching rule.
Interface
Source port number of the matching rule. If Layer-2
interface is not bound, the value here is any for
portal-enabled interfaces.
Vlan
Source VLAN ID of the matching rule. For a
portal-enabled routing interface, the value here is 0.
Destination
Destination information of the matching rule.
IP
Destination IP address of the matching rule.
Mask
Destination mask of the matching rule.
TCP Port
Destination port number of the matching rule.
Context
Context sent by the driver module.
RuleID
Portal rule ID.
Sequence
Rule sequence number.
Failed to send core-message!
Failed to send inter-core messages.
232
Field
Description
VCPU ID
Virtual CPU ID.
DPIfIndex
Data plane interface index.
SrcIP
Source IP address.
SrcMask
Source IP address mask.
SrcMac
Source MAC address.
DstIP
Destination IP address.
DstMask
Destination IP address mask.
Flow
Flow tag of packets.
AuthorACL
Authorization ACL number.
Operation type:
Operation
•
•
DstPort
ADD: Adds an ACL.
DEL: Deletes an ACL.
Destination port number.
Table 5 describes output fields and messages for the debugging portal error command.
Table 142 Output from the debugging portal error command
Field
Description
User's ip address did not match the configured
auth-network. (user ip: ip)
User is not on any configured authentication subnet.
(User IP: ip)
Can not find the interface for user access. (user ip: ip)
Layer 3 interface for user access was not found.
Examples
# On a portal-enabled device, enable portal TCP anti-spoofing debugging. When an unauthenticated
portal user uses a browser to access a website, output similar to the following example is generated:
<Sysname> debugging portal tcp-cheat
*Dec 30 15:19:53:119 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG: Source MAC = 000d-88f8-0eab
VLAN =
0, PortIndex =
0
45 00 00 30 86 b1 40 00
80 06 af 68 02 02 02 03
c0 a8 00 01 0b b4 00 50
6a a3 af d0 00 00 00 00
70 02 ff ff 97 f9 00 00
02 04 05 b4 01 01 04 02
// Port 0 of VLAN 0 received a TCP connection packet with source MAC address 000d-88f8-0eab.
*Dec 30 15:19:53:138 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG:A connection of
added!
2020203
*Dec 30 15:19:53:147 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG: Source MAC = 000d-88f8-0eab
VLAN =
0, PortIndex =
0
// Portal added a connection with source IP 2.2.2.3 and source MAC address 000d-88f8-0eab. The
connection accessed port 0 of VLAN 0.
233
*Dec 30 15:19:53:168 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG:State of connection with
source IP 2.2.2.3 is LISTEN!
// The status of the connection with source IP 2.2.2.3 is LISTEN.
*Dec 30 15:19:53:177 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG:State of connection with
source IP 2.2.2.3 changed from LISTEN to SYN_RECVD!
// The status of the connection with source IP 2.2.2.3 changed from LISTEN to SYN_RECVD.
*Dec 30 15:19:53:507 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG:State of connection with
source IP 2.2.2.3 changed from FIN_WAIT_1 to FIN_WAIT_2!
// The status of the connection with source IP 2.2.2.3 changed from FIN_WAIT_1 to FIN_WAIT_2.
*Dec 30 15:19:53:537 2007 Sysname TCPCHEAT/7/TCPCHEAT_DEBUG:A connection of
deleted!
2020203
// The connection with source IP address 2.2.2.3 was removed.
# On a portal-enabled device, enable portal packet debugging. Perform portal authentication.
<Sysname> debugging portal packet interface ethernet 1/1
*Dec 30 15:19:53:137 2007 Sysname PORTAL/8/PORTAL_DEBUG:
Portal socket receive packet length:34
Portal check packet OK
// Portal received a portal packet at socket.
Portal packet head:
SN:3234 Type:9
AttrNum:1
ErrCode:0
UserIP:2.2.2.2
// The portal packet's header information:
•
SN—sequence number
•
AttrNum—Number of attributes carried in the packet.
•
ErrCode—Error code
•
UserIP—User IP address.
Portal packet attribute list:
[
8 Port
] [
2] []
// The attribute list carried in the packet: [ Attribute 8 Port
] [Length: 2] [Value: Null]
Portal raw packet:
02 09 00 00 0c a2 00 00 02 02 02 02 00 00 00 01
23 95 11 8b 1c 33 47 cf c5 1c de 8b bd 43 b8 24
08 02
// The whole packet, displayed in hexadecimal notation.
*Dec 30 15:19:53:147 2007 Sysname PORTAL/8/PORTAL_DEBUG:
Portal socket send packet length:65
// Portal sent a portal packet through socket, with the length as 65 bytes
Portal packet head:
SN:3234 Type:10 AttrNum:2
ErrCode:0
UserIP:2.2.2.2
// The portal packet's header information:
•
SN—sequence number
•
AttrNum—Number of attributes carried in the packet.
•
ErrCode—Error code
•
UserIP—User IP address.
234
Portal packet attribute list:
[
8 Port
[ 10 BAS-IP
] [ 27] [AR49-45-vlan-00-0000@vlan]
] [
6] [2.2.2.1]
// The attribute list carried in the packet:
[Attribute 8 Port
] [Length: 27] [Value: AR49-45-vlan-00-0000@vlan]
[Attribute 10 BAS-IP
] [Length: 6] [Value: 2.2.2.1]
Portal raw packet:
02 0a 00 00 0c a2 00 00 02 02 02 02 00 00 00 02
dd 64 55 49 ee b3 4c 79 2a a4 9e 76 91 86 91 82
08 1b 41 52 34 39 2d 34 35 2d 76 6c 61 6e 2d 30
30 2d 30 30 30 30 40 76 6c 61 6e 0a 06 02 02 02
01
// The whole packet, displayed in hexadecimal notation.
# On a portal-enabled device, enable portal connection debugging. Perform portal authentication.
<Sysname> debug portal connection interface vlan 5
*Dec 30 15:19:53:137 2007 Sysname PORTAL/8/PORTAL_DEBUG:
Timer TMR_REQAUTH is started: user index 1 IP 24.24.0.2 state DISCOVERED!
// The TMR_REQAUTH timer was started for the user.
*Dec 30 15:19:53:147 2007 Sysname PORTAL/8/PORTAL_DEBUG:
Timer TMR_REQAUTH is stopped: user index 1 IP 24.24.0.2 state DISCOVERED!
// The TMR_REQAUTH timer was stopped for the user.
*Dec 30 15:19:53:157 2007 Sysname PORTAL/8/PORTAL_DEBUG:
User: 1 IP: 24.24.0.2 state: DISCOVERED send AUTHREQ message to ACM!
// The user sent an AUTHREQ message to the ACM module.
*Dec 30 15:19:53:167 2007 Sysname PORTAL/8/PORTAL_DEBUG:
State DISCOVERED changing to WAIT_AUTHEN_ACK: user index 1 IP 24.24.0.2!
// The user's connection status changed from DISCOVERED to WAIT_AUTHEN_ACK.
*Dec 30 15:19:53:177 2007 Sysname PORTAL/8/PORTAL_DEBUG:
[ACM]User index 1: Recv portal AUTH-REQ in IDLE state!
// In the ACM module, the user with index 1 received an AUTHREQ message in IDLE state.
*Dec 30 15:19:53:187 2007 Sysname PORTAL/8/PORTAL_DEBUG:
[ACM]User index 1: Send AUTH-REQ to radius succ
// In the ACM module, the user with index 1 sent an AUTHREQ message to the RADIUS module
successfully.
*Dec 30 15:19:53:197 2007 Sysname PORTAL/8/PORTAL_DEBUG:
Processing AUTHEN-ACK user 1 IP 24.24.0.2 recv AUTH-ACCEPT from ACM!
// The user with IP address 24.24.0.2 and index 1 passed the authentication.
*0.1326010 Sysname PORTAL/8/PORTAL_DEBUG:
Processing AUTHOR-ACK user 1 IP 24.24.0.2 recv ACL-SUCC from DRV!
// An ACL was successfully assigned to the user.
*Dec 30 15:19:53:217 2007 Sysname PORTAL/8/PORTAL_DEBUG:
[ACM]User index 1: Online Succ,Update user's online time!
235
// In the ACM module, the user with index 1 changed to ONLINE state. The user online time was
refreshed.
# On a portal-enabled device, enable portal ACL debugging. Perform portal authentication. Output
similar to the following example is generated when the device is with a single-core CPU:
<Sysname> debugging portal acl interface vlan 5
*Dec 30 15:19:53:227 2007 Sysname PORTAL/8/PORTAL_DEBUG:Slot=4;
Portal interface:Vlan-interface5
Status:running, Action:redirect
// Portal was running normally on the portal-enabled interface VLAN-interface 5, which redirected the
packet as instructed by the matching portal rule.
Match rule:
Inbound interface = all
Type
= static
Action
= redirect
// The matching portal rule defines that the incoming interfaces are all interfaces, the rule type is static,
and the action is redirect.
Source:
IP
= 0.0.0.0
Mask
= 0.0.0.0
Protocol
= 6
MAC
= 0000-0000-0000
Interface = any
VLAN
= 2
// The source information of the portal rule.
Destination:
IP
= 0.0.0.0
Mask
= 0.0.0.0
TCP Port
Context
= 80
= 0x00000002,0xffffffff
// The destination information of the portal rule.
*Dec 30 15:19:53:237 2007 Sysname PORTAL/8/PORTAL_DEBUG:Slot=4;
Portal interface:Vlan-interface5
Status:running, Action:permit
// Portal was running correctly on the portal-enabled VLAN-interface 5, which permitted the packet as
instructed by the matching portal rule.
Match rule:
Inbound interface = all
Type
= static
Action
= permit
// The matching portal rule information:
•
Inbound interface—Incoming interfaces of the packets.
•
Type—Type of the portal rule.
•
Action—Action to be taken to the packets.
Source:
IP
= 0.0.0.0
236
Mask
= 0.0.0.0
Protocol
= 0
MAC
= 0000-0000-0000
Interface = any
VLAN
= 2
// The source information of the portal rule.
Destination:
IP
= 192.168.0.111
Mask
= 255.255.255.255
TCP Port
= 0
Context
= 0x00000000,0xffffffff
// The destination information of the portal rule.
*0.24586800 Sysname PORTAL/8/PORTAL_DEBUG:Slot=4;Add ACL driver return:0
Inbound interface = all
Type
= dynamic
Action
= permit
// The upper layer software assigned a portal rule to the driver successfully.
Source:
IP
= 24.24.0.2
Mask
= 255.255.255.255
Protocol
= 0
MAC
= 0000-0000-0000
Interface = any
VLAN
= 2
// The source information of the portal rule.
Destination:
IP
= 0.0.0.0
Mask
= 0.0.0.0
TCP Port
Context
= 0
= 0x0000000b,0xffffffff
// The destination information of the portal rule.
[Sysname] portal delete-user all
*Dec 30 15:19:53:247 2007 Sysname PORTAL/8/PORTAL_DEBUG:Slot=4;Delete ACL
interface = all
Type
= dynamic
Action
= permit
// The upper layer software removed a portal rule from the driver successfully.
Source:
IP
= 24.24.0.2
Mask
= 255.255.255.255
Protocol
= 0
MAC
= 0000-0000-0000
Interface = any
VLAN
= 2
// The source information of the portal rule.
Destination:
237
Inbound
IP
= 0.0.0.0
Mask
= 0.0.0.0
TCP Port
= 0
Context
= 0xffffffff,0xffffffff
// The destination information of the portal rule.
The output in the following examples was created on portal-enabled devices with a multi-core CPU.
# Enable portal ACL debugging on the device. When a user pings the remote server, output similar to the
following example is generated:
<Sysname> debugging portal acl interface gigabitethernet 1/1
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Match Permit ACL.
DPIfIndex=49153, SrcIP=76.1.1.1, DstIP=192.168.0.244, Flow=87043375!
// Packets matched the permit rule.
# Enable portal ACL debugging on the device. When an authenticated portal user accesses the external
IP address 192.168.0.222 through IE, output similar to the following example is generated:
<Sysname> debugging portal acl interface gigabitethernet 1/1
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Match Permit ACL.
DPIfIndex=49153, SrcIP=76.1.1.1, DstIP=192.168.0.222, Flow=16777415!
// Packets matched the permit rule.
# Enable portal ACL debugging on the device. When a user failing portal authentication accesses the
external IP address 192.168.0.251 through IE, output similar to the following example is generated:
<Sysname> debugging portal acl interface gigabitethernet 1/1
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Match Redirect ACL.
DPIfIndex=49153, SrcIP=76.1.1.1, DstIP=192.168.0.251, Flow=16777417!
// Packets matched the redirect rule.
# Enable portal ACL debugging on the device. When a user failing portal authentication accesses the
external IP address 192.168.0.221 through FTP, output similar to the following example is generated:
<Sysname> debugging portal acl interface gigabitethernet 1/1
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Match Deny ACL. SrcIP=76.1.1.1, DstIP=192.168.0.221, Flow=26778415!
// Packets matched the deny rule.
# Enable portal ACL debugging on the device, and enable portal on interface GigabitEthernet 1/1.
<Sysname> debugging portal acl interface gigabitethernet 1/1
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
DRV_FUNC2:
DPIfIndex = 49163;
SrcIP
= 0.0.0.0;
SrcMask
= 0.0.0.0;
SrcMac
= 0000-0000-0000;
DstIP
= 192.168.0.244;
DstMask
= 255.255.255.255;
AuthorACL = 0xFFFFFFFF;
Operation = ADD;
238
// The data plane received parameter information. The operation is to add a portal rule.
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Added permit ACL: Successfully!
RuleID
= 0x00000001
Sequence
= 0x00000001
// The portal module successfully added a permit rule. Rule ID is 1, and rule sequence is 1.
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Portal enabled on the interface!
// Portal was enabled on the interface.
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
DRV_FUNC3:
DPIfIndex = 41963;
SrcIP
= 0.0.0.0;
SrcMask
= 0.0.0.0;
DstPort
= 80;
Operation = ADD;
// The data plane received parameter information. The operation is to add a portal rule.
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Added redirect ACL: Successfully!
// The portal module successfully added a redirect rule.
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
DRV_FUNC4:
DPIfIndex = 41963;
SrcIP
= 0.0.0.0;
SrcMask
= 0.0.0.0;
Operation = ADD;
// The data plane received parameter information. The operation is to add a portal rule.
*Dec 15 16:47:28:600 2008 Sysname PORTAL_D/7/DP_PORTAL_DEBUG:Slot=3;
Added deny ACL: Successfully!
// The portal module successfully added a deny rule.
# Enable portal authentication on an interface of the device. Enable portal error debugging. When
online user (18.18.0.5) re-initiates portal authentication on the interface, output similar to the following
example is generated:
<Sysname> debugging portal error
*Apr 26 14:50:55:032 2010 Sysname PORTAL/7/PORTAL_DEBUG: Received req-info: User already
exists. (user ip: 18.18.0.5)
// The portal module received a req-info message. The user (IP: 18.18.0.5) is already online.
debugging portal server
Use debugging portal server to enable portal server debugging.
Use undo debugging portal to disable portal server debugging.
Syntax
debugging portal server
239
undo debugging portal server
Default
Portal server debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 6 describes output fields and messages for the debugging portal server command.
Table 143 Output from the debugging portal server command
Field
User user-ip is being
detected, index = index,
detection mode = mode.
Description
Detecting user user-ip. index indicates the user index. mode indicates the
detection mode:
•
•
•
0: No detection.
1: Traffic detection.
2: ICMP packet detection.
Failed to write the msg message to the portal message queue.
msg indicates the message type:
Failed to write msg message
to portal message queue.
•
•
•
•
Reqinfo: Request information.
ReqAuth: Authentication request.
ReqLogout: Logout request.
AckNtfLogout; Force-logout request.
Received a message from the portal module.
ip-address indicates the user IP. type indicates the message type:
Received message from
portal, IP = ip-address, type
= type.
•
•
•
•
•
•
•
REACH_USER_LIMIT: Number of users has reached the maximum.
ACCT_SUCCESS: Accounting succeeded.
ACCT_FAIL: Accounting failed.
PT_NORMAL_ACK_INFO: Information request response message.
PT_NORMAL_ACK_AUTH: Authentication response message.
PT_NORMAL_NTF_LOGOUT: Force-logout message.
PT_NORMAL_ACK_LOGOUT: Logout response message.
Received a message from the portal Web server.
Received message from
portal web server, IP =
ip-address, type = type.
ip-address indicates the user IP. type indicates the message type:
•
•
•
•
PT_NORMAL_REQ_INFO: Information request message.
PT_NORMAL_REQ_AUTH: Authentication request message.
PT_NORMAL_REQ_LOGOUT: Logout request message.
PT_NORMAL_ACK_NTF_LOGOUT: Force-logout response message.
Connection from WS is not
for local server.
The Socket connection request received on the Web service (WS) module is not
for the local server.
Failed to read data from
connection.
Failed to read data from the Socket connection.
240
Field
Description
Received async connection
is not for local server.
The received asynchronous Socket connection is not for the local server.
Failed to move connection
from WS to portal.
Failed to move the Socket connection from the Web service module to the portal
server.
Failed to write message to
connection queue.
Failed to write data to the Socket connection queue.
Received invalid msg for
connection.
Received a message indicating that the Socket connection is invalid.
Received connection from
WS.
Received a Socket connection from the Web service module.
Connection is invalid.
The Socket connection is invalid.
Processing connection.
Processing the Socket connection.
Data from connection is not
complete.
Data from the Socket connection is not complete.
Received close msg.
Received the Socket connection close message.
Saved connection.
The Socket connection was saved.
Deleted connection.
The Socket connection was deleted.
Conn ID: Reset age time to
time.
The aging time of the specified connection (Conn ID) was set to time.
SSID ssidname bind File
filename.
SSID is bound with a file.
Action: action, Type: type,
UserName: username,
Passwd: passwd.
URL information: request action, type, username, and password.
Action: POST, Type:
LOGOFF.
Logoff request information.
Get HTTP data offset failed.
Failed to get HTTP data offset.
Cut HTTP header failed.
Failed to remove HTTP header.
Read HTTP data failed.
Failed to read HTTP data.
Parse HTTP data failed.
Failed to parse HTTP data.
Get HTTP parse ID failed.
Failed to get HTTP parse ID.
Set parse message type
failed.
Failed to set the parse message type.
Write data failed.
Failed to write data.
Connection exists.
The Socket connection already exists.
Failed to malloc memory,
cannot save connection.
Failed to allocate memory; cannot save the Socket connection.
Failed to get port or VLAN
information (IP ip-addr).
Failed to get port or VLAN information of the user whose IP address is ip-addr.
Set MAC to zero (IP
ip-addr).
The MAC address was set to 0 for the user whose IP address is ip-addr.
241
Field
Description
Failed to get MAC
information (IP ip-addr).
Failed to get MAC information of the user whose IP address is ip-addr.
Examples
# On a device enabled with local portal server, enable portal server debugging. When a user uses the
IE browser to trigger portal authentication, output similar to the following example is generated:
<Sysname> debugging portal server
*Jan 10 16:17:01:94 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received connection from WS
*Jan 10 16:17:02:422 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Processing connection.
// The portal server processed the received portal connection request.
*Jan 10 16:17:02:422 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Replied a file logon.htm for client.
// The portal server replied with a logon file to the portal client, providing the logon page to the portal
client.
*Jan 10 16:17:11:984 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received read msg.
*Jan 10 16:17:11:984 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Action: POST, Type: LOGON, UserName: admin, Passwd: admin.
// The portal server received a logon post request from the portal client.
*Jan 10 16:17:11:984 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal web server, IP = 2.2.20.4, type = PT_NORMAL_REQ_INFO.
// The portal module received an information request message from the local portal server.
*Jan 10 16:17:11:984 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal, IP = 2.2.20.4, type = PT_NORMAL_ACK_INFO.
// The portal server received an information request response message from the portal module.
*Jan 10 16:17:11:984 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal web server, IP = 2.2.20.4, type = PT_NORMAL_REQ_AUTH.
// The portal module received an authentication request message from the local portal server.
*Jan 10 16:17:12:187 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal, IP = 2.2.20.4, type = PT_NORMAL_ACK_AUTH.
// The portal server received an authentication acknowledgement message from the portal module.
*Jan 10 16:17:12:390 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal, IP = 2.2.20.4, type = ACCT_SUCCESS.
// The portal server received an accounting success message from the portal module.
*Jan 10 16:17:12:390 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Send web page to inform user 2.2.20.4: Authentication succeeded!
*Jan 10 16:17:12:390 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Sent HTTP packet to user successfully.
// The portal server successfully informed the portal client of authentication success.
*Jan 10 16:19:40:531 2008 Sysname PORTAL/7/PORTAL_DEBUG:
User 2.2.20.4 is being detected, index = 0, detection mode = 2.
242
*Jan 10 16:19:40:531 2008 Sysname PORTAL/7/PORTAL_DEBUG:
User 2.2.20.4 sent ICMP detection request packet.
*Jan 10 16:19:40:734 2008 Sysname PORTAL/7/PORTAL_DEBUG:
User 2.2.20.4 received ICMP detection response packet.
// The portal server performed the ICMP detection.
*Jan 10 16:21:31:609 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received connection 1 from WS.
*Jan 10 16:21:31:609 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Processing connection.
*Jan 10 16:21:31:609 2008 Sysname PORTAL/7/PORTAL_DEBUG:
URL:POST, TYPE:LOGOFF.
// The portal server received a logoff request from the portal client.
*Jan 10 16:21:31:781 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal web server, IP = 2.2.20.4, type = PT_NORMAL_REQ_LOGOUT.
// The portal module received a logoff request from the local portal server.
*Jan 10 16:21:31:875 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Received message from portal, IP = 2.2.20.4, type = PT_NORMAL_ACK_LOGOUT.
*Jan 10 16:21:31:875 2008 Sysname PORTAL/7/PORTAL_DEBUG:
Replied a file logoffSuccess.htm for client.
// The local portal server informed the portal client of logoff success.
243
POS terminal access debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging posa all
Use debugging posa all to enable all POS access debugging.
Use undo debugging posa all to disable all POS access debugging.
Syntax
debugging posa all [ terminal terminal-id | app app-id ]
undo debugging posa all [ terminal terminal-id | app app-id ]
Default
All POS access debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
terminal-id: Specifies a POS terminal by its ID in the range of 1 to 255.
app-id: Specifies a POS application by its ID in the range of 1 to 31.
Usage guidelines
For the command output description, see Table 1 and Table 2.
Examples
# Enable all types of POS access debugging. When a listening port is created on terminal 2 that already
exists, output similar to the following example is generated:
<Sysname> debugging posa all
*Oct 18 16:23:19:486 2008 Sysname POSA/7/EVENT:
Terminal 2: Received ASYN_READ message from socket(12).
// Terminal 2 received an ASYN_READ message from the socket.
*Oct 17 20:42:16:880 2008 H3C POSA/7/ERROR:
App 2: Failed to send flow packet, because the connect state(2) is not up.
// Application 2 failed to send the asynchronous packet, because the interface was not up.
*Oct 18 16:23:19:486 2008 Sysname POSA/7/PACKET:
Received 10 bytes from tcp terminal 2.
PktLen(0x0008) ID(0x60) DST(0xaaaa) SRC(0x1111)
Total length: 10 Offset: 0, partial data as follows:
0x000: 00 08 60 aa aa 11 11 11 11 11
// A 10-byte packet was received from TCP terminal 2.
244
debugging posa event
Use debugging posa event to enable POS access event debugging.
Use undo debugging posa event to disable POS access event debugging.
Syntax
debugging posa event [ terminal terminal-id | app app-id ]
undo debugging posa event [ terminal terminal-id | app app-id ]
Default
POS access event debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
terminal-id: Specifies a POS terminal by its ID in the range of 1 to 255.
app-id: Specifies a POS application by its ID in the range of 1 to 31.
Usage guidelines
Table 1 describes output fields and messages for the debugging posa event command.
Table 144 Output from the debugging posa event command






Field

App n: Succeeded to
send connecting
request to server.

Terminal n: Received
control message of
deleting terminal.

App n: Received
control message of
disconnecting by app.

App n: Received
control message of
setting tcp keepalive
option.


App n: Received line
disable message.
Description
Application n successfully sent a
connecting request to the FEP.
POS access received a control message
that terminal n is deleted.
POS access received a control message
that all connections to application n are
terminated.
POS access received a control message
that TCP keepalive parameters of
application n are modified.
POS access received a message that
application n is switched between
synchronous and asynchronous modes.
Examples
# Enable POS access event debugging. When TCP application 2 in temporary connection mode is
connected to asynchronous terminal 1, output similar to the following example is generated:
<Sysname> debugging posa event
*Jul 30 19:44:18:392 2008 posa POSA/7/EVENT:
245
App 2: Received control message of deleting app.
// POS access received a control message that application 2 is deleted.
*Jul 30 19:44:18:392 2008 posa POSA/7/EVENT:
App 2: Received control message of disconnecting by app.
// POS access received a control message that all connections to application 2 are terminated.
debugging posa error
Use debugging posa error to enable POS access error debugging.
Use undo debugging posa error to disable POS access error debugging.
Syntax
debugging posa error [ terminal terminal-id | app app-id ]
undo debugging posa error [ terminal terminal-id | app app-id ]
Default
POS access error debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
terminal-id: Specifies a POS terminal by its ID in the range of 1 to 255.
app-id: Specifies a POS application by its ID in the range of 1 to 31.
Usage guidelines
Table 2 describes output fields and messages for the debugging posa error command.
Table 145 Output from the debugging posa error command





Field

Failed to create template
of teminal(n), because of
failing to malloc memory
for terminal template.

Terminal n: Failed to
hung up fcm when
reiniting terminal
instance.

Failed to get correct
terminal template by
terminal(n) when
creating listen socket.

Failed to get app
template by trans
appID(n) when resetting
terminal instance.

246
Description
POS access failed to create terminal
template (n) because memory failed to
be allocated for the template.
POS access failed to be hung up when
terminal n was reset.
POS access failed to obtain the
correct terminal template through
terminal (n) when it was creating the
listen socket.
POS access failed to obtain the
application terminal according to the
transparent application ID (n) when it
was resetting the terminal instance.













Field

Failed to create terminal
instance by terminal(n)
when accepting connect
from socket(i).

Failed to set socket(i) to
asyn mode when
connecting to app.

App n: Failed to create
linking timer by socket(i).

Failed to get terminal
template by terminal(n)
when updating the
statistics.

Failed to unbind the
application template (n)
with interface (m) in
command line.

Failed to send message
of creating listen socket
when creating terminal
template (n).

Failed to create socket
when checking terminal
listen port (n).

Failed to bind listen port
with socket checking
terminal listen port(n).

Interface index (n) is
invalid when binding
application template (m)
with interface.

Failed to send message
when binding interface
(n) with application (m).

Failed to send message
when setting tcp
parameters of
application template (n).

Failed to set fcm
parameter of tradetime
by mib.

247
Description
POS access failed to create a terminal
instance through terminal (n) when a
connection was received from socket
(i).
POS access failed to set socket (i) to
the asynchronous mode when a
connection to application n was
initiated.
POS access failed to create a timeout
timer for application n through socket
(i).
POS access failed to obtain the
terminal template through terminal (n)
when packet statistics were refreshed.
POS access failed to unbind
application template (n) from interface
(m).
POS access failed to send the
message that the listening port is
created when it was creating terminal
template n.
POS access failed to create the socket
when it was examining whether or not
listening port n of the terminal is
occupied.
POS access failed to bind the listening
port to the socket when it was
examining whether or not listening
port n of the terminal is occupied.
Interface index (n) is invalid when the
application template (m) is bound to
the interface.
POS access failed to send the
message that interface (n) is bound to
application (m).
POS access failed to send the
message that TCP parameters of
application template n were set.
POS access failed to set the FCM
transaction time parameter through
MIB.






Field

Failed to delete
application (n) because
of sending control
message unsuccessfully.

Failed to create fcm
terminal template in
terminal table because of
illegal interface index (n).
Failed to create flow
terminal template
because of illegal
workmode on interface.


Failed to remalloc
memory when echoing
global configuration.


Failed to get template by
ifindex(m) when echoing
interface configuration.
Description
POS access failed to delete
application n because the control
message requesting the deletion of the
template failed to be sent.
POS access failed to create the FCM
terminal in the terminal table because
the interface index n is invalid.
POS access failed to create the flow
terminal because the interface worked
in an improper mode.
POS access failed to reallocate
memory when it was displaying
global configuration information.
POS access failed to obtain the
template according to interface index
m when it was displaying the interface
configuration information.
Examples
# Enable POS access error debugging. When packets are received after the receive buffer of terminal 1
is full, output similar to the following example is generated:
<Sysname> debugging posa error
*Jul 30 19:44:18:392 2008 posa POSA/7/ERROR:
Terminal 1: Failed to insert transparent flow packet into receiving buffer.
// POS access failed to add the asynchronous packet transferred in transparent mode to the receive
buffer of terminal 1.
debugging posa packet
Use debugging posa packet to enable POS access packet debugging.
Use undo debugging posa packet to disable POS access packet debugging.
Syntax
debugging posa packet [ receive | send ] [ terminal terminal-id | app app-id ]
undo debugging posa packet [ receive | send ] [ terminal terminal-id | app app-id ]
Default
POS access packet debugging is disabled.
Views
User view
Default command level
2: System level
248
Parameters
receive: Specifies debugging for BPDU packets received.
send: Specifies debugging for BPDU packets sent.
terminal-id: Specifies a POS terminal by its ID in the range of 1 to 255.
app-id: Specifies a POS application by its ID in the range of 1 to 31.
Usage guidelines
Use the receive or send, and terminal or app keywords to enable or disable packet debugging in a
specific direction on a specific POS terminal or application.
Special fields of the POS packet include the following:
•
STX.
•
PktLen (packet length).
•
ID (ID of the Transport Protocol Data Unit ID, TPDU ID).
•
DST (destination address of the TPDU).
•
SRC (source address of the TPDU).
•
EXT.
•
CRC (cyclic redundancy check).
If a received packet is incomplete, fields that contain no data are displayed as 0. If a received packet is
longer than 32 bytes, only the first 32 bytes are displayed.
Examples
# Enable POS access packet debugging. When Terminal 2 communicates with the POS terminal device
in FCM mode, and is mapped to application 1 in TCP connection mode, output similar to the following
example is generated:
<Sysname> debugging posa packet
*May 13 14:56:45:891 2008 H3C POSA/7/PACKET:
Received 584 bytes from fcm terminal 2.
ID(0x60) DST(0xaaaa) SRC(0x1111)
Total length: 584 Offset: 0, partial data as follows:
0x000: 60 aa aa 11 11 30 6d 1b 5b 30 30 6d 61 6e 61 63
0x010: 6f 6e 64 61 2d 6b 73 2e 63 66 67 1b 5b 30 30 6d.
// POS access received a 584-byte packet.
249
PPP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
PPP debugging commands
debugging ppp
Use debugging ppp to enable PPP debugging.
Use undo debugging ppp to disable PPP debugging.
Syntax
debugging ppp { all [ interface interface-type interface-number ] | bcp | cbcp packet [ interface
interface-type interface-number ] | ccp | chap | compression iphc { rtp | tcp } | core event [ interface
interface-type interface-number ] | ip packet [ interface interface-type interface-number ] | ipcp | ipv6
| ipv6cp | ipx | ipxcp | lcp | lqc | mp | mpls-multicast packet [ interface interface-type
interface-number ] | mpls-unicast packet [ interface interface-type interface-number ] | mplscp |
osi-npdu | osicp | pap | scp | vjcomp { all | error | event | packet | state} [ interface interface-type
interface-number ] }
undo debugging ppp { all [ interface interface-type interface-number ] | bcp | cbcp packet [ interface
interface-type interface-number ] | ccp | chap | compression iphc { rtp | tcp } | core event [ interface
interface-type interface-number ] | ip packet [ interface interface-type interface-number ] | ipcp | ipv6
| ipv6cp | ipx | ipxcp | lcp | lqc | mp | mpls-multicast packet [ interface interface-type
interface-number ] | mpls-unicast packet [ interface interface-type interface-number ] | mplscp |
osi-npdu | osicp | pap | scp | vjcomp { all | error | event | packet | state} [ interface interface-type
interface-number ] }
Default
All types of PPP debugging are disabled.
Views
User view
Default command level
1. Monitor level
Parameters
all: All types of PPP debugging.
bcp: PPP Bridging Control Protocol (BCP) debugging.
cbcp: PPP Callback Control Protocol (CBCP) debugging.
ccp: PPP Compression Control Protocol (CCP) debugging.
chap: PPP CHAP debugging.
compression: PPP IP header compression (TCP and RTP) debugging.
250
core: PPP kernel event debugging.
ip: IP packet debugging.
ipcp: IP Control Protocol (IPCP) debugging.
ipv6: IPv6 packet debugging.
ipv6cp: IPv6 Control Protocol (IPv6CP) debugging.
ipx: IPX debugging.
ipxcp: IPX Control Protocol (IPXCP) debugging.
lcp: PPP Link Control Protocol (CCP) debugging.
lqc: PPP link quality control (LQC) debugging.
mp: MP debugging.
mpls-multicast: MPLS multicast debugging.
mpls-unicast: MPLS unicast debugging.
mplscp: MPLS Control Protocol (MPLSCP) debugging.
osi-npdu: OSI NPDU debugging.
osicp: OSI Control Protocol (OSICP) debugging.
pap: PAP debugging.
scp: Stac LZS debugging.
vjcomp: VJ TCP/IP header compression debugging.
error: PPP error debugging.
event: PPP event debugging.
packet: PPP packet debugging.
state: PPP state debugging.
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 2 describes the output fields and messages for the debugging ppp event command.
Table 146 Output from the debugging ppp event command
Field
Description
event
A PPP event occurred.
state
The state of a PPP state machine.
Up
The lower layer went up.
Down
The lower layer went down.
Open
The link was administratively opened.
Close
The link was administratively closed.
Timeout(T0+,T0-)
A timeout event occurred. T0+ indicates that the restart counter is
greater than 0, so retransmission is required. T0- indicates that the
restart counter is less than 0, so retransmission is not needed.
251
Field
Description
Receive-Configure-Request(RCR+,RCR-)
A Configure-Request packet was received from the peer. RCR+
indicates that the request is acceptable and a Configure-Ack should
be sent back. RCR- indicates that the request is unacceptable, and
a Configure-Nak or Configure-Rej should be sent back.
Receive-Configure-Ack(RCA)
A valid Configure-Ack packet was received from the peer. The
packet is a positive response to a configuration request.
Receive-Configure-Nak/Rej(RCN)
A valid Configure-Nak/Rej packet was received from the peer. The
packet is a negative response to some or all requested
configuration options.
Receive-Terminate-Request(RTR)
A Terminate-Request packet was received, indicating that the peer
wanted to close the connection.
Receive-Terminate-Ack(RTA)
A Terminate-Ack packet was received from the peer.
Receive-Unknown-Code(RUC)
An unknown packet was received from the peer.
Receive-Code-Reject,
Receive-Protocol-Reject(RXJ+,RXJ-)
A Code-Reject or Protocol-Reject packet was received from the
peer. RXJ+ indicates that the rejected options are within the scope
of normal operation, so the rejection is acceptable. RXJ- indicates
that the rejected options are not acceptable, and link termination
will result.
Receive-Echo-Request
An Echo-Request packet was received from the peer.
Receive-Echo-Reply
An Echo-Reply packet was received from the peer.
Receive-Discard-Request(RXR)
A Discard-Request packet was received from the peer.
Table 2 describes the output fields and messages for the debugging ppp ipcp command.
Table 147 Output from the debugging ppp ipcp command
Field
value
Field name
Description
2
IP-Compression-Protocol
The adopted IP compression protocol.
3
IP Address
IP address negotiation.
129
Primary DNS Server Address
PPP requested or allocated the primary DNS server.
130
Primary NBNS Server Address
PPP requested or allocated the primary NBNS server.
131
Secondary DNS Server Address
PPP requested or allocated a secondary DNS server.
132
Secondary NBNS Server Address
PPP requested or allocated a secondary NBNS server.
Examples
# Enable LCP debugging. Output similar to the following example is generated when you enable PPP on
the two Serial interfaces connecting two devices and PPP negotiation starts between them.
<Sysname> debugging ppp lcp all
*0.784906 Sysname PPP/8/debug2:
PPP Event:
Serial2/0 LCP Open
Event
state initial
// On interface Serial 2/0, the LCP state machine was opened and was in the initial state.
252
*0.784906 Sysname PPP/8/debug2:
PPP State Change:
Serial2/0 LCP : initial --> starting
// LCP moved from the initial state to the starting state.
*0.784906 Sysname PPP/8/debug2:
PPP Event:
Serial2/0 LCP Lower Up
Event
state starting
// A lower layer up event was reported for LCP. The LCP state machine was in the starting state.
*0.784906 Sysname PPP/8/debug2:
PPP State Change:
Serial2/0 LCP : starting --> reqsent
// LCP moved from the starting state to the reqsent state.
*0.784906 Sysname PPP/8/debug2:
PPP Packet:
Serial2/0 Output LCP(c021) Pkt, Len 35
State reqsent, code ConfReq(01), id 2a, len 31
MRU(1), len 4, val 05dc
AuthProto(3), len 4, PAP c023
MagicNumber(5), len 6, val 31180c00
MPRU(11), len 4, val 05dc
Discri(13), len 9, val 01fa4d432c8451
// Interface Serial 2/0 sent a 35-byte LCP packet. The type of the packet is Configure-Request, its ID is
2a, and its length is 31 bytes with the header removed. The LCP state machine transited to the request
sent state as a result.
PPPoE debugging commands
The PPPoE client module name is identified as "PPPOEC" in debugging messages.
The PPPoE server module name is identified as "PPPOES" in debugging messages.
debugging pppoe-client
Use debugging pppoe-client to enable PPPoE client debugging.
Use undo debugging pppoe-client to disable PPPoE client debugging.
Syntax
debugging pppoe-client { all | data | error | event | packet | verbose } [ interface interface-type
interface-number ]
undo debugging pppoe-client { all | data | error | event | packet | verbose } [ interface interface-type
interface-number ]
Default
All types of PPPoE client debugging are disabled.
Views
User view
253
Default command level
1. Monitor level
Parameters
all: All types of PPPoE client debugging.
data: Debugging for data information of the PPPoE client at the session stage.
error: Error debugging for the PPPoE client.
event: Event debugging for the PPPoE client.
packet: Debugging for data information of the PPPoE client at the discovery stage.
verbose: Detailed information debugging for the PPPoE client.
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 3 describes the output fields and messages for the debugging pppoe-client command.
Table 148 Output from the debugging pppoe-client command
Field
Description
IN
Incoming packets at the PPPoE session stage.
OUT
Outgoing packets at the PPPoE session stage.
Session Number
Session number.
Len
Packet length.
Table 4 describes the output fields and messages for the debugging pppoe-client packet command.
Table 149 Output from the debugging pppoe-client packet command
Field
Description
IN
Incoming packets at the PPPoE discovery stage.
OUT
Outgoing packets at the PPPoE discovery stage.
PADI
The PPPoE active discovery initiation (PADI) packet.
PADO
The PPPoE active discovery offer (PADO) packet.
PADR
The PPPoE active discovery request (PADR) packet.
PADS
The PPPoE active discovery session-conformation (PADS) packet.
PADT
The PPPoE active discovery terminate (PADT) packet.
Len
Packet length.
Table 5 describes the output fields and messages for the debugging pppoe-client verbose command.
Table 150 Output from the debugging pppoe-client verbose command
Field
Description
IN
Incoming packets at the PPPoE discovery stage.
OUT
Outgoing packets at the PPPoE discovery stage.
254
Field
Description
Len
Packet length.
Dest MAC Addr
Destination MAC address.
Src MAC Addr
Source MAC address.
Ver
Version.
Type
Type.
Code
Packet Type.
Session ID
Session number.
Tag Service-Name
Internet service provider.
Tag Host-Uniq
A particular unique request of a host.
Tag AC-Name
The field used for preventing denial of service attacks.
Examples
# Enable all types of PPPoE client debugging. Output similar to the following example is generated when
you enable PPPoE on Ethernet interfaces connecting two devices and PPPoE negotiation starts between
them.
*Aug 21 11:05:25:200 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client O
UT Discovery packet (PADI), Len = 30
*Aug 21 11:05:25:201 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client O
UT, Len = 30
ff ff ff ff ff ff 00 0f e2 00 00 03 88 63 11 09
00 00 00 0a 01 01 00 00 01 03 00 02 00 01
>>
Dest MAC Addr: ffff.ffff.ffff,
Discovery Stage,
Ver=1,
Src MAC Addr: 000f.e200.0003
Type=1,
Code=PADI,
Session ID=0
Tag Service-Name:
Tag Host-Uniq:
00 01 | ..
// Interface Ethernet 1/1 sent a discovery-stage packet.
*Aug 21 11:05:25:202 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client I
N, Len = 60
00 0f e2 00 00 03 00 0f e2 29 ad f4 88 63 11 07
00 00 00 21 01 01 00 00 01 03 00 02 00 01 01 02
00 13 51 75 69 64 77 61 79 30 30 30 66 65 32 32
39 61 64 66 34 00 00 00 00 00 00 00
>>
Dest MAC Addr: 000f.e200.0003,
Discovery Stage,
Ver=1,
Src MAC Addr: 000f.e229.adf4
Type=1,
Code=PADO,
Session ID=0
Tag Service-Name:
Tag Host-Uniq:
00 01 | ..
Tag AC-Name:
51 75 69 64 77 61 79 30 30 30 66 65 32 32 39 61 | Sysname000fe229a
255
64 66 34 | df4
*Aug 21 11:05:25:202 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client I
N Discovery packet (PADO), Len = 60
// Interface Ethernet 1/1 received a discovery-stage packet.
*Aug 21 11:05:25:203 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client O
UT Discovery packet (PADR), Len = 53
*Aug 21 11:05:25:203 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client O
UT, Len = 53
00 0f e2 29 ad f4 00 0f e2 00 00 03 88 63 11 19
00 00 00 21 01 01 00 00 01 03 00 02 00 01 01 02
00 13 51 75 69 64 77 61 79 30 30 30 66 65 32 32
39 61 64 66 34
>>
Dest MAC Addr: 000f.e229.adf4,
Discovery Stage,
Ver=1,
Src MAC Addr: 000f.e200.0003
Type=1,
Code=PADR,
Session ID=0
Tag Service-Name:
Tag Host-Uniq:
00 01 | ..
Tag AC-Name:
51 75 69 64 77 61 79 30 30 30 66 65 32 32 39 61 | Sysname000fe229a
64 66 34 | df4
// Interface Ethernet 1/1 sent a discovery-stage packet.
*Aug 21 11:05:25:208 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client I
N, Len = 60
00 0f e2 00 00 03 00 0f e2 29 ad f4 88 63 11 65
00 01 00 21 01 01 00 00 01 03 00 02 00 01 01 02
00 13 51 75 69 64 77 61 79 30 30 30 66 65 32 32
39 61 64 66 34 00 00 00 00 00 00 00
>>
Dest MAC Addr: 000f.e200.0003,
Discovery Stage,
Ver=1,
Src MAC Addr: 000f.e229.adf4
Type=1,
Code=PADS,
Session ID=1
Tag Service-Name:
Tag Host-Uniq:
00 01 | ..
Tag AC-Name:
51 75 69 64 77 61 79 30 30 30 66 65 32 32 39 61 | Sysname000fe229a
64 66 34 | df4
*Aug 21 11:05:25:209 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client I
N Discovery packet (PADS), Len = 60, Session ID = 1
// Interface Ethernet 1/1 received a discovery-stage packet.
*Aug 21 11:05:25:750 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client O
UT session1 data, Dialer1:0, Len = 16
*Aug 21 11:05:26:400 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: PPPoE Client O
256
UT, Len = 36
00 0f e2 29 ad f4 00 0f e2 00 00 03 88 64 11 00
00 01 00 10 c0 21 01 00 00 0e 01 04 05 d4 05 06
3c f3 37 79
>>
Dest MAC Addr: 000f.e229.adf4,
Session Stage,
Ver=1,
Src MAC Addr: 000f.e200.0003
Type=1,
Session ID=1
*Aug 21 11:05:26:550 2007 Sysname PPPOEC/7/debugging:Ethernet1/1: Dialer1:0 was
bound to Dialer1 for PPPoE Session
// Interface Ethernet 1/1 sent a session-stage packet.
debugging pppoe-server
Use debugging pppoe-server to enable PPPoE server debugging.
Use undo debugging pppoe-server to disable PPPoE server debugging.
Syntax
debugging pppoe-server { all | data | error | event | packet } [ interface interface-type
interface-number ]
undo debugging pppoe-server { all | data | error | event | packet } [ interface interface-type
interface-number ]
Default
All types of PPPoE server debugging is disabled.
Views
User view
Default command level
1. Monitor level
Parameters
all: All types of PPPoE server debugging.
data: Debugging for data information of the PPPoE server at the session stage.
error: Error debugging for the PPPoE server.
event: Event debugging for the PPPoE server.
packet: Debugging for data information of the PPPoE server at the discovery stage.
interface interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 6 describes the output fields and messages for the debugging pppoe-server command.
Table 151 Output from the debugging pppoe-server command
Field
Description
IN
Incoming packets at the PPPoE session stage.
OUT
Outgoing packets at the PPPoE session stage.
257
Field
Description
session
Session ID.
Table 7 describes the output fields and messages for the debugging pppoe-server event command.
Table 152 Output from the debugging pppoe-server event command
Field
Description
IN
Incoming packets at the PPPoE discovery stage.
OUT
Outgoing packets at the PPPoE discovery stage.
PADI
The PPPoE active discovery initiation (PADI) packet.
PADO
The PPPoE active discovery offer (PADO) packet.
PADR
The PPPoE active discovery request (PADR) packet.
PADS
The PPPoE active discovery session-conformation (PADS) packet.
PADT
The PPPoE active discovery terminate (PADT) packet.
Table 8 describes the output fields and messages for the debugging pppoe-server packet command.
Table 153 Output from the debugging pppoe-server packet command
Field
Description
IN
Incoming packets at the PPPoE discovery stage.
OUT
Outgoing packets at the PPPoE discovery stage.
len
Packet length.
Examples
# Enable all types of PPPoE client debugging. Output similar to the following example is generated when
you enable PPPoE on the two GigabitEthernet interfaces connecting two devices.
*Dec
8 07:59:44:405 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.404: PPPoE :GigabitEthernet1/1 IN discovery packet, len 60
ff ff ff ff ff ff 00 0f e2 00 00 03 88 63 11 09
00 00 00 0a 01 01 00 00 01 03 00 02 00 01 00 01
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00
*Dec
8 07:59:44:405 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.404: PPPoE Event: GigabitEthernet1/1, IN PADI packet
// Interface GigabitEthernet 1/1 received a discovery-stage packet.
*Dec
8 07:59:44:405 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.404: PPPoE :GigabitEthernet1/1 OUT discovery packet, len 53
00 0f e2 00 00 03 00 0f e2 29 ad f4 88 63 11 07
00 00 00 21 01 01 00 00 01 03 00 02 00 01 01 02
00 13 51 75 69 64 77 61 79 30 30 30 66 65 32 32
39 61 64 66 34
*Dec
8 07:59:44:405 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.404: PPPoE Event: GigabitEthernet1/1, OUT PADO packet
258
// Interface GigabitEthernet 1/1 sent a discovery-stage packet.
*Dec
8 07:59:44:407 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.405: PPPoE :GigabitEthernet1/1 IN discovery packet, len 60
00 0f e2 29 ad f4 00 0f e2 00 00 03 88 63 11 19
00 00 00 21 01 01 00 00 01 03 00 02 00 01 01 02
00 13 51 75 69 64 77 61 79 30 30 30 66 65 32 32
39 61 64 66 34 00 13 51 75 69 64 77
*Dec
8 07:59:44:407 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.405: PPPoE Event: GigabitEthernet1/1, IN PADR packet
// Interface GigabitEthernet 1/1 received a discovery-stage packet.
*Dec
8 07:59:44:407 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.406: PPPoE :GigabitEthernet1/1 OUT discovery packet, len 53
00 0f e2 00 00 03 00 0f e2 29 ad f4 88 63 11 65
00 01 00 21 01 01 00 00 01 03 00 02 00 01 01 02
00 13 51 75 69 64 77 61 79 30 30 30 66 65 32 32
39 61 64 66 34
*Dec
8 07:59:44:407 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.406: PPPoE Event: GigabitEthernet1/1, session 1(Virtual-Temp
late1:0), OUT PADS packet
// Interface GigabitEthernet 1/1 sent a discovery-stage packet.
// Now, the PPPoE server moves from the discovery stage to the session stage.
*Dec
8 07:59:44:898 2006 Sysname PPPOE/7/debug2:
2006-12-8 7:59:44.410: PPPoE: GigabitEthernet1/1 IN session data for Virtual-T
emplate1:0 (session 1), len 36
00 0f e2 29 ad f4 00 0f e2 00 00 03 88 64 11 00
00 01 00 10 c0 21 01 00 00 0e 01 04 05 d4 05 06
3c d0 b6 97
// Interface GigabitEthernet 1/1 received a session-stage packet.
259
PTP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging ptp
Syntax
debugging ptp { all | error | event | frame [ receive | send ] [ verbose ] | fsm | timer }
undo debugging ptp { all | error | event | frame [ receive | send ] [ verbose ] | fsm | timer }
Default
PTP debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: All types of debugging for PTP.
error: PTP error debugging.
event: PTP event debugging.
frame: PTP message debugging.
receive: Debugging for received PTP messages.
send: Debugging for sent PTP messages.
verbose: Detailed PTP message debugging.
fsm: PTP state machine debugging.
timer: Debugging for PTP timers.
Usage guidelines
Use debugging ptp to enable PTP debugging. Use undo debugging ptp to disable PTP debugging.
Table 1 describes output fields and messages for the debugging ptp error command.
Table 154 Output from the debugging ptp error command
Field
Description
Failed to initialzie PTP task information error, and failed
to malloc memory.
Failed to initialize PTP task information and failed to
allocate memory.
Table 2 describes output fields and messages for the debugging ptp fsm command.
260
Table 155 Output from the debugging ptp fsm command
Field
Description
Entered PRS
PTP entered role selection state.
Entered SEND_PDELAY_REQ state in PDelayReq state
machine.
The Pdelay_Req state machine is in Pdelay request
sending state.
Entered WAITING_FOR_PDELAY_RESP state in
PDelayReq state machine.
The Pdelay_Req state machine is in waiting for the
Pdelay response state.
Entered SENT_PDELAY_RESP state in PDelayResp state
machine.
The Pdelay_Req state machine is in Pdelay response
sending state.
Entered WAITING_FOR_PDELAY_INTERVAL_TIMER
state in PDelayReq state machine.
The Pdelay_Req state machine is in waiting for the
Pdelay interval timer state.
Examples
# Enable PTP error debugging.
<Sysname> debugging ptp error
*Apr
2 15:39:33:219 2010 Sysname PTP1/7/ERROR : PTP is not enabled on Eth1/1.
# Enable PTP event debugging.
<Sysname> debugging ptp event
*Apr
2 15:18:34:375 2010 Sysname PTP1/7/EVENT : Created PTP task successfully.
*Apr
2 15:18:34:375 2010 Sysname PTP1/7/EVENT : Created PTP timer queue successfully.
*Apr
2 15:18:34:391 2010 Sysname PTP1/7/EVENT : Created PTP event queue successfully.
*Apr
2 15:18:34:391 2010 Sysname PTP1/7/EVENT : Created PTP timer successfully.
*Apr
2 15:18:34:391 2010 Sysname PTP1/7/EVENT : Initialized PTP all successfully.
# Enable PTP message debugging.
<Sysname> debugging ptp frame receive verbose
*Apr
2 11:10:03:281 2010 Sysname PTP1/7/FRAME : -Slot=1;
Ethernet1/1 received Announce packet [length 76].
1b 02 00 4c 00 00 00 08 00 00 00 00 00 00 00 00
00 00 00 00 00 0f e2 ff fe 14 12 00 00 02 00 16
05 05 00 00 00 00 00 00 00 00 00 00 00 00 00 a0
00 00 00 0f e2 ff fe 14 12 00 f8 fe 41 00 80 80
00 08 00 08 00 0f e2 ff fe 14 12 00
# Enable PTP state machine debugging.
<Sysname> debugging ptp fsm
*Apr 2 15:27:27:704 2010 Sysname PTP1/7/FSM : Entered SENT_PDELAY_RESP state in PDelayResp
state machine.
// PTP entered the Pdelay response sending state in Pdelay_Resp state machine.
*Apr 2 15:27:27:704 2010 Sysname PTP1/7/FSM : Entered WAITING_FOR_PDELAY_INTERVAL_TIMER
state in PDelayReq state machine.
// PTP entered the state of waiting for the Pdelay interval timer in the Pdelay_Req state machine.
# Enable PTP timer debugging.
<Sysname> debugging ptp timer
*Apr 2 15:56:55:171 2010 Sysname PTP1/7/TIME : Eth1/1: Periodically sent Pdelay_req
packet.
261
QoS debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
NOTE:
Support for the following commands depends on the device model.
debugging dar
Use debugging dar to enable DAR debugging.
Use undo debugging dar to disable DAR debugging.
Syntax
debugging dar { all | error | event | packet }
undo debugging dar { all | error | event | packet }
Default
DAR debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: All types of DAR debugging.
error: Debugging for DAR errors.
event: Debugging for DAR events.
packets: Debugging for DAR packets.
Usage guidelines
Table 1 describes output fields and messages for the debugging dar error command.
Table 156 Output from the debugging dar error command
Field
Description
Failed to copy the data of the packet
DAR failed to copy the data of the packet during protocol
recognition.
Table 2 describes output fields and messages for the debugging dar event command.
262
Table 157 Output from the debugging dar event command
Field
Description
Failed to write queue
DAR failed to write information queue during traffic accounting.
Failed to trigger an event
DAR failed to trigger an event after writing information queue
successfully.
Failed to remove timer
DAR failed to remove the timer for traffic accounting.
Session count has reached the upper limit
The number of sessions monitored by DAR reached the
configured upper limit.
Table 3 describes output fields and messages for the debugging dar packet command.
Table 158 Output from the debugging dar packet command
Field
Description
The head of the packet does not match
The packet header did not match.
Examples
# Enable debugging for DAR events. When traffic accounting is enabled on Ethernet 1/0, output similar
to the following example is generated:
<Sysname> debugging dar event
*Apr 26 05:35:24:873 2007 Sysname DAR/7/DAR_Debug_Event: Ethernet1/0
Succeeded in starting protocol recognition!
// The protocol recognition function was enabled successfully on Ethernet 1/0.
# Enable debugging for DAR packets. Traffic accounting is enabled on Ethernet 1/0. Output similar to
the following example is generated when the IP address of Ethernet 1/0 is pinged from the device
connected to Ethernet 1/0.
<Sysname> debugging dar packet
*Apr 26 05:40:28:630 2007 Sysname DAR/7/DAR_Debug_Packet:
Succeeded in protocol recognition: icmp.
// ICMP packet was recognized successfully.
debugging p2p
Use debugging p2p to enable P2P debugging.
Use undo debugging p2p to disable P2P debugging.
Syntax
debugging p2p { all | error | event }
undo debugging p2p { all | error | event }
Default
P2P debugging is disabled.
Views
User view
263
Default command level
2: System level
Parameters
all: All types of P2P debugging.
error: P2P error debugging.
event: P2P event debugging.
Usage guidelines
Table 4 describes output fields and messages for the debugging p2p error command.
Table 159 Output from the debugging p2p error command
Field
Description
Failed to parse the protocol string
P2P failed to resolve the protocol string.
Failed to get statistics information. Zone: zone-id,
Protocol: protocol-id
P2P failed to obtain statistics about protocol
protocol-id in zone zone-id.
Failed to get the protocol Chinese description from
signature file
P2P failed to obtain the protocol description in
Chinese from the signature file.
Failed to get the protocol English description from
signature file
P2P failed to obtain the protocol description in English
from the signature file.
The value for a parameter was invalid.
Parameters include:
Invalid value of parameter(parameter-name)
• Starting position of the signature code.
• Offset of the signature code
• Signature code length.
Failed to synchronize the number of recognized
packets
P2P failed to synchronize the number of recognized
packets to the data plane.
P2P failed to obtain a parameter from the signature
file.
Parameters include:
Failed to get the parameter(parameter-name) from
signature file
•
•
•
•
•
•
•
•
Parent protocol of the signature file.
Protocol version.
Number of packets recognized.
Length of packets recognized.
Starting position of the signature code.
Offset of the signature code.
Signature code length.
Signature code type.
P2P failed to synchronize the signature code to the
data plane.
Failed to synchronize the signature
Examples
# Enable P2P error debugging. The signature file meta.mtd became invalid because it was modified by
the user without permission. When the modified signature file meta.mtd is loaded, output similar to the
following example is generated:
<Sysname> debugging p2p error
264
<Sysname>
*Dec
6 20:11:56:343 2007 Sysname P2P/7/P2P_Error:
Invalid signature file content.
// Contents of the signature file were invalid.
# Enable P2P event debugging when no protocol group exists on the device. Output similar to the
following example is generated when a user performs these tasks:
•
Creates protocol group 64.
•
Adds protocol 1, protocol 2, protocol 3, and protocol 4 to protocol group 64.
<Sysname> debugging p2p event
<Sysname>
*Dec 10 14:58:49:844 2007 Sysname P2P/7/P2P_Event:
The protocol group 64 does not exist.
// Protocol group 64 did not exist.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Start to set protocol group.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Succeeded in adding protocol 1 to protocol group 64.
// P2P started to set the protocol group. P2P added protocol 1 to protocol group 64.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Start to set protocol group.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Succeeded in adding protocol 2 to protocol group 64.
// P2P started to set the protocol group. P2P added protocol 2 to protocol group 64.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Start to set protocol group.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Succeeded in adding protocol 3 to protocol group 64.
// P2P started to set the protocol group. P2P added protocol 3 to protocol group 64.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Start to set protocol group.
*Dec 10 14:58:50:141 2007 Sysname DP_P2P/7/P2P_Event:
Succeeded in adding protocol 4 to protocol group 64.
// P2P started to set the protocol group. P2P added protocol 4 to protocol group 64.
*Dec 10 14:58:50:141 2007 Sysname P2P/7/P2P_Event:
Succeeded in creating protocol group 64.
// P2P succeeded in creating protocol group 64.
debugging qos all
Use debugging qos all to enable all types of QoS debugging.
Use undo debugging qos all to disable all types of QoS debugging.
Syntax
debugging qos all
undo debugging qos all
265
Default
All types of QoS debugging are disabled.
Views
User view
Default command level
1: Monitor level
debugging qos car
Use debugging qos car to enable CAR debugging.
Use undo debugging qos car to disable CAR debugging.
Syntax
debugging qos car
undo debugging qos car
Default
CAR debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 5 describes output fields and messages for the debugging qos car command.
Table 160 Output from the debugging qos car command
Field
Description
Dropped a packet for CAR action
A packet was dropped by a CAR action configured on
the interface.
Examples
# Enable CAR debugging on Router A. Output similar to the following example is generated when the
rate of traffic from Router C to Router A exceeds 8 kbps under the following conditions:
•
The traffic from Router C travels by way of Router A to Router B.
•
A CAR policy is configured on the egress port of Router A to limit the outgoing traffic rate to 8 kbps.
<RouterA> debugging qos car
*Apr 26 05:19:13:589 2007 RouterA QOS/7/QOS_Debug:
QOS_CAR: Dropped a packet for CAR action
// A packet was dropped by CAR.
debugging qos cbq
Use debugging qos cbq to enable CBQ debugging.
266
Use undo debugging qos cbq to disable CBQ debugging.
Syntax
debugging qos cbq { af | be | ef }
undo debugging qos cbq { af | be | ef }
Default
CBQ debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
af: AF queue debugging.
be: BE queue debugging.
ef: EF queue debugging.
Usage guidelines
Table 6 describes output fields and messages for the debugging qos cbq af command.
Table 161 Output from the debugging qos cbq af command
Field
Description
Dropped a packet of class id classID from the AF
queue for QoS cache was exhausted, and the current
length is queueLength
A packet matching class classID was dropped by the
AF queue because the global QoS cache was
exhausted. The current AF queue length is
queueLength.
Dropped a packet of class id classID from the AF
queue for zero bandwidth, and the current length is
queueLength
A packet matching class classID was dropped by the
AF queue because of zero bandwidth. The current AF
queue length is queueLength.
Dropped a packet of class id classID from the AF
queue for tail-drop, and the current length is
queueLength
A packet matching class classID was dropped by the
AF queue in the way of tail-drop. The current AF queue
length is queueLength.
Dropped a packet of class id classID from the AF
queue for WRED, and the current length is
queueLength
A packet matching class classID was dropped by the
AF queue in the way of WRED. The current AF queue
length is queueLength.
Dropped a packet of class id classID from the AF
queue for illegal drop-type, and the current length is
queueLength
A packet matching class classID was dropped by the
AF queue because of its illegal drop type. The current
AF queue length is queueLength.
Dropped a packet of class id classID from the AF
queue for insufficient packet wrapper memory, and
the current length is queueLength
A packet matching class id classID was dropped by
the AF queue because of insufficient packet wrapper
memory. The current length is queueLength.
Examples
The output in the following example was created when the following conditions exist:
•
Packets sourced from Router C pass through Router A and Router B to reach Router D.
267
•
The packets from Router C are classified into three classes according to their DSCP values. A QoS
policy is applied to the packets in the outbound direction of the egress port of Router A:


Applying assured forwarding (AF) policy for the packets with the DSCP value AF11 or AF21,
setting the minimum to bandwidth percentage to 5%.
Applying expedited forwarding (EF) policy to the packets with the DSCP value EF, setting the
maximum bandwidth percentage to 30%.
# Enable CBQ AF debugging and CBQ EF debugging on Router A. When the traffic of an AF class
exceeds the minimum bandwidth and the traffic of the EF class exceeds the maximum bandwidth, the
following information is generated:
<RouterA> debugging qos cbq af
<RouterA> debugging qos cbq ef
*Apr 26 05:19:13:589 2007 RouterA qos/7/qos_Debug:
QOS_CBQEF: Dropped a packet of class id 4 from the EF queue for token-bucket, and the
current length is 1
// Packets matching class ID 4 were dropped by the EF queue due to token bucket restrictions, and the
current EF queue length was 1.
*Apr 26 05:22:38:885 2007 RouterA QOS/7/QOS_Debug:
QOS_CBQAF: Dropped a packet of class id 2 from the AF queue for tail-drop, and the current
length is 64
// Packets matching class 2 were dropped by the AF queue in the way of tail-drop, and the current AF
queue length is 64.
debugging qos error
Use debugging qos error to enable QoS error debugging.
Use undo debugging qos error to disable QoS error debugging.
Syntax
debugging qos error
undo debugging qos error
Default
QoS error debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 7 describes output fields and messages for the debugging qos error command.
Table 162 Output from the debugging qos error command
Field
Description
Getting input packet link-layer-head length failed
QoS failed to obtain the link layer header length of
incoming packets.
Creating MQC flow-statistic timer failed
QoS failed to create an MQC flow-statistics timer.
268
Field
Description
Getting queue statistic error
QoS failed to obtain queue statistics.
Global fragment pre-drop count error
A global count error occurred on an interface enabled
with fragment pre-drop.
Cutting packet header error on QoS input process
QoS failed to remove a header of an incoming packet.
Pasting packet header error on QoS input process
QoS failed to add a header to an incoming packet.
debugging qos event
Use debugging qos event to enable QoS event debugging.
Use undo debugging qos event to disable QoS event debugging.
Syntax
debugging qos event
undo debugging qos event
Default
QoS event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 8 describes output fields and messages for the debugging qos event command.
Table 163 Output from the debugging qos event command
Field
Description
Module moduleID enable filling IP user tag direction,
and the current IPtype reference counter is counter.
A module enabled filling IP user tag in a direction
(inbound or outbound). The current IPtype (IPv4 or
IPv6) reference counter is counter.
Filling IP user tag is disabled for module moduleID
direction, and the current IPtype reference counter is
counter
Filling IP user tag was disabled for a module in a
direction (inbound or outbound). The current IPtype
(IPv4 or IPv6) reference counter is counter.
Global fragment pre-drop count increases to counter
The global count of interfaces enabled with fragment
pre-drop increased to counter.
Global fragment pre-drop count decreases to counter
The global count of interfaces enabled with fragment
pre-drop decreased to counter.
Getting link-layer-head length failed
QoS failed to obtain the link-layer header length.
Examples
# Enable QoS event debugging. When CAR is configured on an interface, output similar to the following
example is generated:
<Sysname> debugging qos event
269
*Dec 17 13:28:53:962 2007 Sysname QOS/7/QOS_Debug:
QOS_Event: Module 3200000 enable filling IP user tag outbound, and the current IPv4
reference counter is 1.
// Module 3200000 enabled filling IP user tags in the outbound direction. The current IPv4 reference
counter is 1 (IPv4 has referenced the function for one time).
*Dec 17 13:28:53:962 2007 Sysname QOS/7/QOS_Debug:
QOS_Event: Module 3200000 enable filling IP user tag outbound, and the current IPv6
reference counter is 1.
// Module 3200000 enabled filling IP user tags in the outbound direction. The current IPv6 reference
counter is 1 (IPv6 has referenced the function for one time).
debugging qos gts
Use debugging qos gts to enable GTS debugging.
Use undo debugging qos gts to disable GTS debugging.
Syntax
debugging qos gts
undo debugging qos gts
Default
GTS debugging is disabled.
Views
User view
Default command level
1: Monitor level
Examples
# Enable GTS debugging on Router A. Output similar to the following example is generated when the
rate of traffic from Router C to Router A exceeds 8 kbps under the following conditions:
•
The traffic from Router C travels by way of Router A to Router B.
•
A QoS policy that uses GTS is applied to the egress port of Router A to limit the outgoing traffic rate
to 8 kbps.
<RouterA> debugging qos gts
* Dec 17 14:10:32:480 2007 RouterA QOS/7/QOS_Debug:
QOS_GTS: Dropped a packet by GTS for exceeding queue limit.
// A packet was dropped by GTS because the queue limit was exceeded.
debugging qos match
Use debugging qos match to enable debugging for packet matching in QoS.
Use undo debugging qos match to disable debugging for packet matching in QoS.
Syntax
debugging qos match
undo debugging qos match
270
Default
Debugging for packet matching in QoS is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 9 describes output fields and messages for the debugging qos match command.
Table 164 Output from the debugging qos match command
Field
Description
Match match-type were ignored for match-type did
not match the packet.
The match criterion based on match-type was ignored
because the match-type did not match the packet type.
Examples
# Enable debugging for packet matching in QoS on Router A. Output similar to the following example
is generated when an IP packet arrives at Router A under the following conditions:
•
The traffic from Router C travels by way of Router A to Router B.
•
A QoS policy is applied to the egress port (GE port) of Router A to match outgoing packets by
FR-DE.
<RouterA> debugging qos match
*Dec 17 14:05:31:150 2007 RouterA QOS/7/QOS_Debug:
QOS_Match: Match FR-DE were ignored for match-type did not match the packet.
// The FR-DE match criterion was ignored because the match-type FR-DE did not match the packet type.
debugging qos remark
Use debugging qos remark to enable debugging for packet re-marking in QoS.
Use undo debugging qos remark to disable debugging for packet re-marking in QoS.
Syntax
debugging qos remark
undo debugging qos remark
Default
Debugging for packet re-marking in QoS is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 10 describes output fields and messages for the debugging qos remark command.
271
Table 165 Output from the debugging qos remark command
Field
Description
Failed to remark packet, for remark remark-type did
not match the packet type.
QoS failed to re-mark the packets because
remark-type did not match the packet type.
Examples
# Enable debugging for packet remarking in QoS on Router A. Output similar to the following example
is generated when an MPLS packet arrives at Router A under the following conditions:
•
The traffic from Router C (PE) travels by way of Router A (P device) to Router B (PE).
•
A QoS policy is applied to the egress port (GE port) of Router A to re-mark the IP precedence of
outgoing packets as 5.
<RouterA> debugging qos remark
*Dec 17 14:05:01:720 2007 RouterA QOS/7/QOS_Debug:
QOS_Remark: Failed to remark packet, for remark ip-precedence did not match the packet
type.
// QoS failed to set the IP precedence to 5 for the packets because the IP precedence type did not match
the packet type.
272
Voice RADIUS debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging voice radius
Use debugging voice radius to enable voice RADIUS debugging.
Use undo debugging voice radius to disable voice RADIUS debugging.
Syntax
debugging voice radius { all | error | event | fsm | timer | trace }
undo debugging voice radius { all | error | event | fsm | timer | trace }
Default
Voice RADIUS debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
all: Specifies all types of debugging for voice RADIUS.
error: Specifies error debugging.
event: Specifies event debugging.
fsm: Specifies finite state machine debugging.
timer: Specifies timer debugging.
trace: Specifies debugging for messages between the voice RADIUS module and the AAA module.
Usage guidelines
Table 1 describes output fields and messages for the debugging voice radius error command.
Table 166 Output from the debugging voice radius error command
•
Field
•
Description
•
Arg Error
•
The input parameter is incorrect.
•
Play Voice Error
•
Playing prompt tones failed.
•
Msg Not Support
In This State
•
A message that is not supported in the current state
was received.
•
Create Timer Fail
•
Creating a timer failed.
•
Start Authen Error
•
Originating an authentication request failed.
273
•
Field
•
Description
•
Disconnect Media
Error
•
Disconnecting the media failed.
Table 2 describes output fields and messages for the debugging voice radius event command.
Table 167 Output from the debugging voice radius event command
•
Field
•
Description
•
VORDS ---> CMC
•
Commands from the voice RADIUS module to
the CMC.
•
CMC [1] ---> VORDS [2]
•
Messages from CMC 1 to voice RADIUS
module 2.
•
VORDS
--->
UniConnect
CMC
•
The voice RADIUS module invoked a CMC
interface to establish a unidirectional
connection.
•
VORDS
--->
Disconnect Media
CMC
•
The voice RADIUS module invoked a CMC
interface to disconnect the media.
•
VORDS ---> CMC Connect
Media
•
The voice RADIUS module invoked a CMC
interface to connect the media.
•
VORDS ---> CMC Create
New Call
•
The voice RADIUS module invoked a CMC
interface to establish a new call.
•
VORDS ---> CMC
Trigger
Start
•
The voice RADIUS module invoked a CMC
interface to trigger a service.
•
VORDS ---> CMC
Trigger
End
•
The voice RADIUS module invoked a CMC
interface to stop triggering a service.
•
VORDS
--->
Terminate Call
CMC
•
The voice RADIUS module invoked a CMC
interface to end a call.
•
VORDS ---> CMC
History Info
Get
•
The voice RADIUS module invoked a CMC
interface to obtain call history information.
•
VORDS ---> IVR:
Voice
Play
•
The voice RADIUS module invoked an IVR
interface to play prompts.
•
VORDS ---> IVR
Voice
Stop
•
The voice RADIUS module invoked an IVR
interface to stop playing voice prompts.
•
VORDS ---> DRV
SigTone
Play
•
The voice RADIUS invoked a drive interface to
play signal tones.
•
VORDS ---> DRV
SigTone
Stop
•
The voice RADIUS module invoked a drive
interface to stop playing signal tones.
•
VORDS ---> DRV
Dtmf Detect
Start
•
The voice RADIUS module invoked a drive
interface to start DTMF detection.
•
VORDS ---> DRV
Dtmf Detect
Stop
•
The voice RADIUS module invoked a drive
interface to stop DTMF detection.
•
Dial Flow Type: Did
•
The dialing process is a two-stage dialing
process.
274
•
Field
•
Description
•
Dial Flow Type: Card
•
The
dialing
process
is
a
card
number/password process (two-stage dialing
process).
•
Dial
Flow
CallerNumber
Type:
•
The dialing process is a caller number process
(two-stage dialing process).
•
Dial
Flow
VoiceCaller
Type:
•
The dialing process is a caller number process
with IVR (two-stage dialing process).
Table 3 describes output fields and messages for the debugging voice radius fsm command.
Table 168 Output from the debugging voice radius fsm command
•
Field
•
Description
•
[1]
RDS_STATE_INIT
RDS_STATE_SELECT_LANG
•
The state of voice RADIUS module 1
changed from RDS_STATE_INIT to
RDS_STATE_SELECT_LANG.
•
RDS_STATE_INIT
•
Initial state.
•
RDS_STATE_SELECT_LANG
•
A language was selected for prompt
tones.
•
RDS_STATE_CARD_RCV
•
Receiving digits of a card number.
•
RDS_STATE_PWD_RCV
•
Receiving digits of the password.
•
RDS_STATE_CALLED_RCV
•
Receiving digits of the called number.
•
RDS_STATE_TALKING
•
Conversation state.
•
RDS_STATE_RELEASE
•
Call release state.
--->
Table 4 describes output fields and messages for the debugging voice radius timer command.
Table 169 Output from the debugging voice radius timer command
•
Field
•
[1]
[RDS_STATE_SELECT_LANG]
Create
Timer:
RDS_AUTHEN_TIMER
ID:3
Length: 4ms:
•
[1]
[RDS_STATE_SELECT_LANG]
Delete
Timer:
RDS_AUTHEN_TIMER ID:3
•
RDS_INIT_AAA_TIMER
•
RDS_FIRSTNUM_TIMER
•
RDS_INTERNUM_TIMER
275
•
Description
•
A timer was created in the voice RADIUS
module.
•
A timer was deleted from the voice
RADIUS module.
•
Timer that specifies a wait for an
AAA_OK message in the initial state.
•
Timer that specifies a wait for the first
digit of a called number or card number.
•
Timer that specifies a wait for a digit
other than the first one of a called number
or card number.
•
Field
•
RDS_AUTHEN_TIMER
•
RDS_AUTHOR_TIMER
•
RDS_ACCT_TIMER
•
RDS_MDACONN_TIMER
•
RDS_TALK_TIMER
•
RDS_LASTMINUTE_TIMER
•
Description
•
Timer that specifies a wait for an
Authentication_OK message.
•
Timer that specifies a wait for an
Authorization_OK message.
•
Timer that specifies a wait for an
Accounting_OK message.
•
Timer that specifies a wait for a
Media_Connect_OK message.
•
Timer that specifies the call duration.
•
Timer that specifies the last minute of a
call.
Table 5 describes output fields and messages for the debugging voice radius trace command.
Table 170 Output from the debugging voice radius trace command
•
Field
•
Description
•
AAA [10] ---> VORDS [20]
•
Messages from AAA 10 to voice RADIUS 20.
•
VORDS [20] ---> AAA [10]
•
Messages from voice RADIUS 20 to AAA 10.
•
Msg: ACCT_START
•
Accounting_Start request from the
RADIUS module to the AAA module.
voice
•
Msg: ACCT_STOP:
•
Accounting_Stop request from the
RADIUS module to the AAA module.
voice
•
Msg: AUTHOR:
•
Authorization request from the voice RADIUS
module to the AAA module.
•
Msg: AUTHEN
•
Authentication request from the voice RADIUS
module to the AAA module.
•
Msg: LEAVING
•
Leaving request from the voice RADIUS module
to the AAA module.
•
Msg: ACCT_FAIL
•
Accounting_Fail from the AAA module to the
voice RADIUS module.
•
Msg: ACCT_OK
•
Accounting_OK from the AAA module to the
voice RADIUS module.
•
Msg: AUTHEN_OK
•
Authentication_OK from the AAA module to
the voice RADIUS module.
•
Msg: AUTHEN_FAIL
•
Authentication_Fail from the AAA module to
the voice RADIUS module.
•
Msg: AUTHOR_OK
•
Authorization_OK from the AAA module to the
voice RADIUS module.
•
Msg: AUTHOR_FAIL
•
Authorization_Fail from the AAA module to the
voice RADIUS module.
•
Msg: CUT
•
Cut command from the AAA module to the
voice RADIUS module.
276
Examples
The output in the following examples was created when the following conditions exist:
•
A two-stage dialing process is configured for voice RADIUS.
•
The access number is 201.
•
The card number/password authentication, authorization, and accounting functions are enabled.
# Enable voice RADIUS event debugging.
<Sysname> debugging voice radius event
Enable VORDS event debugging functions
*Nov 17 17:40:30:86 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
VORDS ---> CMC
Start Trigger.
CMC ID: [0]
VORDS ID: [0]
// The voice RADIUS module invoked the CMC interface to trigger a service.
*Nov 17 17:40:30:87 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_SETUP
Calling: 200, Called: 201
CIT Index: 0
// The voice RADIUS module received a CMC_SETUP message from the CMC. The calling number is
200, and the access number is 201.
*Nov 17 17:40:30:87 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT: AAA SetUserID [0] OK, VORDS [0], VORDS AAAID: [0] [-1]
// The AAA module invoked the voice RADIUS interface to set the ID of the module that interacts with the
AAA module.
*Nov 17 17:40:30:88 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT: [0] [RDS_STATE_INIT]
VORDS ---> CMC
UniConnect. CMC ID: [0]
// The voice RADIUS module invoked the CMC interface to establish a unidirectional connection.
*Nov 17 17:40:30:89 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: ACCP_CHANNEL_READY
// An ACCP_CHANNEL_READY message was received from the CMC.
*Nov 17 17:40:30:89 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
SELECT_LANG]
VORDS ---> IVR:
Play Voice.
IfIndex: [0x2c0030]
VORDS ID: [0]
State: [RDS_STATE_
Tone ID: [1100]
// The voice RADIUS invoked the IVR interface to play the prompt for a language.
*Nov 17 17:40:30:90 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
VORDS ---> DRV
Start DTMF Detect.
VORDS ID: [0]
IfIndex: [0x2c0030]
// DTMF detection was started for voice interface 0x2c0030.
*Nov 17 17:40:35:65 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [1]
// The user pressed the digit 1, and the voice RADIUS module received a key message and played the
prompt in Chinese.
*Nov 17 17:40:35:65 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
SELECT_LANG]
VORDS ---> IVR
Clean Voice.
VORDS ID: [0]
IfIndex: [0x2c0030]
// The user pressed any key to stop playing the prompt.
*Nov 17 17:40:35:66 2006 Sysname VORDS/7/VOICE:
277
State: [RDS_STATE_
VORDS_EVENT:
CARD_RCV]
VORDS ---> IVR:
IfIndex: [0x2c0030]
Play Voice.
VORDS ID: [0]
State: [RDS_STATE_
Tone ID: [1300]
// A prompt was played for a card number.
*Nov 17 17:40:38:68 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
Receive IVR Message.
VORDS ID: [0]
Argument: [1]
// A prompt response message was received from the interactive voice response (IVR). The result of
prompt play was 1, which means that the prompt was played successfully.
*Nov 17 17:40:38:695 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [4]
// The digit 4 pressed was received by the user.
*Nov 17 17:40:39:115 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [5]
*Nov 17 17:40:39:565 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [0]
*Nov 17 17:40:40:15 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [1]
*Nov 17 17:40:40:405 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [1]
*Nov 17 17:40:40:885 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [0]
*Nov 17 17:40:42:295 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [#]
// The information above is the card number collection process.
*Nov 17 17:40:42:295 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
PWD_RCV]
VORDS ---> IVR:
IfIndex: [0x2c0030]
Play Voice.
VORDS ID: [0]
State: [RDS_STATE_
Tone ID: [1400]
// A prompt was played for a password.
*Nov 17 17:40:45:200 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
Receive IVR Message.
VORDS ID: [0]
Argument: [1]
// A prompt response message was received from the IVR. The result of prompt play was 1, which means
that the prompt was played successfully. If the result had been 2, the prompt was not played successfully.
*Nov 17 17:40:48:235 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar.
278
*Nov 17 17:40:48:775 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar.
*Nov 17 17:40:49:285 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar.
*Nov 17 17:40:49:645 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar.
*Nov 17 17:40:50:125 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar.
// The information above is the password collection process.
*Nov 17 17:40:50:125 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT: AAA SetUserID [1] OK, VORDS [0], VORDS AAAID: [0] [1]
// The AAA module invoked the RADIUS interface to set an AAA ID.
*Nov 17 17:40:50:163 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
PWD_RCV]
VORDS ---> IVR:
IfIndex: [0x2c0030]
Play Voice.
VORDS ID: [0]
State: [RDS_STATE_
Tone ID: [2060]
// The prompt was played to announce the balance in the card.
*Nov 17 17:40:50:163 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CALLED_RCV]
VORDS ---> IVR:
IfIndex: [0x2c0030]
Play Voice.
VORDS ID: [0]
State: [RDS_STATE_
Tone ID: [1500]
// The prompt was played for a called number.
*Nov 17 17:40:57:484 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
Receive IVR Message.
VORDS ID: [0]
*Nov 17 17:41:02:96 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [4]
// The user dialed the first digit 4 of the called number.
*Nov 17 17:41:03:85 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [0]
*Nov 17 17:41:03:895 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [0]
*Nov 17 17:41:05:155 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_INFORMATION
DTMFChar: [#]
279
Argument: [1]
// The information above is the called number collection process. After the user pressed the dial
terminator #, the called number collection process ended.
*Nov 17 17:41:05:187 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
VORDS ---> DRV
Stop DTMF Detect.
VORDS ID: [0]
IfIndex:[0x2c0030]
// DTMF detection stopped.
*Nov 17 17:41:05:187 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
ALKING]
VORDS ---> IVR
Stop Voice.
VORDS ID: [0]
State: [RDS_STATE_T
IfIndex: [0x2c0030]
// Going into conversation and stopping the playing of any prompt.
*Nov 17 17:41:05:188 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
[400] CIT: [1]
VORDS ---> CMC
Create New Call.
VORDS ID: [0]
CMC ID: [0]
Called:
// The CMC interface was invoked to create a connection for a new outgoing call.
*Nov 17 17:41:05:338 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [1] ---> VORDS [0]
Msg: CMC_ALERTING
InBandInfo: Invalid
// An Alerting message was received, which means that the in-band information is invalid and the voice
RADIUS module was required to play ringback tones.
*Nov 17 17:41:05:338 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
[RingBack Tone]
VORDS ---> DRV
Play SigTone.
VORDS ID: [0]
State: [5]
Type:
IfIndex: [0x2c0030]
// Ringback tones were played.
*Nov 17 17:41:11:129 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [1] ---> VORDS [0]
Msg: CMC_CONNECT
// A CMC_CONNECT (callee offhook) message was received from the CMC.
*Nov 17 17:41:11:129 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT: VORDS ---> DRV Stop SigTone. VORDS ID: [0] State: [5] IfIndex:[0x2c0030]
SigTone Type: [RingBack Tone]
// The voice RADIUS module ordered the driver to stop playing ringback tones, and the conversation
began.
*Nov 17 17:41:11:130 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
VORDS ---> CMC
Connect Media.
VORDS ID: [0]
CMC ID: [0][1].
// The media channel was connected.
*Nov 17 17:41:17:490 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [1] ---> VORDS [0]
MSG: ACCP_RELEASE
*Nov 17 17:41:17:491 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [1] ---> VORDS [0]
Msg: CMC_RELEASE
Release Cause: Normal clearing!
// After a period of time, the called user hung up, and the voice RADIUS module received the
CMC_Release message.
*Nov 17 17:41:17:492 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
TALKING]
VORDS ---> IVR:
IfIndex: [0x2c0030]
Play Voice.
Tone ID: [2084]
280
VORDS ID: [0]
State: [RDS_STATE_
// The prompt was played to notify the voice RADIUS module that the called user had hung up.
*Nov 17 17:41:20:161 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
Receive IVR Message.
VORDS ID: [0]
Argument: [1]
*Nov 17 17:41:20:161 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
VORDS ---> DRV
Start DTMF Detect.
VORDS ID: [0]
IfIndex: [0x2c0030]
// DTMF detection was enabled to start collecting the digits of a called number.
*Nov 17 17:41:20:161 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CALLED_RCV]
VORDS ---> IVR:
IfIndex: [0x2c0030]
Play Voice.
VORDS ID: [0]
State: [RDS_STATE_
Tone ID: [1500]
// The prompt was played for the called number.
*Nov 17 17:41:23:311 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
Receive IVR Message.
VORDS ID: [0]
Argument: [1]
*Nov 17 17:41:25:122 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
MSG: ACCP_RELEASE
// The calling user hung up while dialing the called number.
*Nov 17 17:41:25:123 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
ALLED_RCV]
VORDS ---> IVR
Stop Voice.
VORDS ID: [0]
State: [RDS_STATE_C
IfIndex: [0x2c0030]
// The prompt was stopped.
*Nov 17 17:41:25:123 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
VORDS ---> DRV
Stop DTMF Detect.
VORDS ID: [0]
IfIndex: [0x2c0030]
// DTMF detection was stopped.
*Nov 17 17:41:25:124 2006 Sysname VORDS/7/VOICE:
VORDS_EVENT:
CMC [0] ---> VORDS [0]
Msg: CMC_RELEASE
Release Cause: Normal clearing!
# Enable debugging for voice RADIUS finite state machines.
<Sysname> debugging voice radius fsm
Enable VORDS fsm debugging functions
*Nov 17 17:44:17:963 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_INIT ---> RDS_STATE_INIT
// The state of voice RADIUS module 1 changed from RDS_STATE_INIT to RDS_STATE_INIT.
*Nov 17 17:44:17:964 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_INIT ---> RDS_STATE_SELECT_LANG
// The state of voice RADIUS module 1 changed from RDS_STATE_INIT to RDS_STATE_SELECT_LANG.
*Nov 17 17:44:23:602 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_SELECT_LANG ---> RDS_STATE_CARD_RCV
// The state of voice RADIUS module 1 changed from RDS_STATE_SELECT_LANG to
RDS_STATE_CARD_RCV.
*Nov 17 17:44:29:242 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_CARD_RCV ---> RDS_STATE_PWD_RCV
// The state of voice
RDS_STATE_PWD_RCV.
RADIUS
module
281
1
changed
from
RDS_STATE_CARD_RCV
to
*Nov 17 17:44:39:919 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_PWD_RCV ---> RDS_STATE_CALLED_RCV
// The state of voice
RDS_STATE_CALLED_RCV.
RADIUS
module
changed
from
RDS_STATE_PWD_RCV
to
RDS_STATE_CALLED_RCV
to
*Nov 17 17:44:50:402 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_CALLED_RCV ---> RDS_STATE_TALKING
// The state of voice
RDS_STATE_TALKING.
RADIUS
module
1
changed
from
*Nov 17 17:45:05:635 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_TALKING ---> RDS_STATE_CALLED_RCV
// The state of voice
RDS_STATE_CALLED_RCV.
RADIUS
module
1
changed
from
RDS_STATE_TALKING
to
RDS_STATE_CALLED_RCV
to
*Nov 17 17:45:09:99 2006 Sysname VORDS/7/VOICE:
VORDS_FSM: [1] RDS_STATE_CALLED_RCV ---> RDS_STATE_RELEASE
// The state of voice
RDS_STATE_RELEASE.
RADIUS
module
1
changed
from
# Enable voice RADIUS timer debugging.
<Sysname> debugging voice radius timer
Enable VORDS timer debugging functions
<Sysname>
*Nov 17 17:45:43:292 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_INIT]
15000 ms
Create Timer: RDS_MDACONN_TIMER ID: 230 Length:
// A timer was created to specify the wait time for a Media_Connect_OK message as 15 seconds.
*Nov 17 17:43:45:293 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_INIT]
Delete Timer: RDS_MDACONN_TIMER
ID: 230
// The timer for waiting for a Media_Connect_OK message was deleted.
*Nov 17 17:44:51:167 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_FIRSTNUM_TIMER ID: 300 Length:
// A timer was created, specifying a wait time for the first digit of a card number.
*Nov 17 17:44:51:197 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Delete Timer: RDS_FIRSTNUM_TIMER ID: 300 Length:
// The RDS_FIRSTNUM_TIMER was deleted after the first digit of the card number was received.
*Nov 17 17:45:51:201 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_INTERNUM_TIMER ID: 303 Length:
// A timer was created, specifying a wait time for a digit other than the first one of a card number.
*Nov 17 17:45:51:501 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 303
// The RDS_INTERNUM_TIMER was deleted each time the user dialed a digit.
*Nov 17 17:45:51:501 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_INTERNUM_TIMER ID: 306 Length:
282
*Nov 17 17:45:51:891 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 306
*Nov 17 17:45:51:891 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_INTERNUM_TIMER ID: 246 Length:
*Nov 17 17:45:52:311 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 246
*Nov 17 17:45:52:311 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_INTERNUM_TIMER ID: 318 Length:
*Nov 17 17:45:52:611 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 318
*Nov 17 17:45:52:611 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_INTERNUM_TIMER ID: 254 Length:
*Nov 17 17:45:53:61 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 254
*Nov 17 17:45:53:61 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
10000 ms
Create Timer: RDS_INTERNUM_TIMER ID: 328 Length:
*Nov 17 17:45:53:361 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CARD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 328
// The information above is the card number collection process. When a digit of the card number was
received, an RDS_INTERNUM_TIMER was deleted. The process stopped when all digits of the card
number were received.
*Nov 17 17:45:56:270 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
222
Create Timer: RDS_FIRSTNUM_TIMER
ID:
Length: 10000 ms
// A timer was created, specifying a wait time for the first digit of a password.
*Nov 17 17:45:59:541 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
Delete Timer: RDS_FIRSTNUM_TIMER
ID:
222
*Nov 17 17:45:59:541 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
336
Create Timer: RDS_INTERNUM_TIMER
ID:
Length: 10000 ms
*Nov 17 17:45:59:901 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
283
Delete Timer: RDS_INTERNUM_TIMER
ID:
336
*Nov 17 17:45:59:901 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
410
Create Timer: RDS_INTERNUM_TIMER
ID:
Length: 10000 ms
*Nov 17 17:46:00:291 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID:
410
*Nov 17 17:46:00:292 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
414
Create Timer: RDS_INTERNUM_TIMER
ID:
Length: 10000 ms
*Nov 17 17:46:00:621 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID:
414
*Nov 17 17:46:00:622 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
417
Create Timer: RDS_INTERNUM_TIMER
ID:
Length: 10000 ms
*Nov 17 17:46:01:41 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID:
417
// The information above is the password collection process. When a digit of the password was received,
an RDS_INTERNUM_TIMER was deleted. The process stopped when all digits of the password were
received.
*Nov 17 17:46:01:41 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
10000 ms
Create Timer: RDS_AUTHEN_TIMER ID: 418 Length:
// The password collection process ended. A card number/password authentication request was
originated to the AAA module. An RDS_AUTHEN_TIMER was created.
*Nov 17 17:46:01:62 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_PWD_RCV]
Delete Timer: RDS_AUTHEN_TIMER
ID: 418
// The RDS_AUTHEN_TIMER was deleted after an Authentication_OK message was received.
*Nov 17 17:46:08:384 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Length: 10000 ms
Create Timer: RDS_FIRSTNUM_TIMER
ID: 511
// A timer was created, specifying a wait time for the first digit of a called number.
*Nov 17 17:46:08:750 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Delete Timer: RDS_FIRSTNUM_TIMER
ID: 511
*Nov 17 17:46:08:751 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Length: 10000 ms
Create Timer: RDS_INTERNUM_TIMER
*Nov 17 17:46:09:260 2006 Sysname VORDS/7/VOICE:
284
ID: 499
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 499
*Nov 17 17:46:09:261 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Length: 10000 ms
Create Timer: RDS_INTERNUM_TIMER
ID: 524
*Nov 17 17:46:10:190 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 524
*Nov 17 17:46:10:191 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Length: 10000 ms
Create Timer: RDS_INTERNUM_TIMER
ID: 529
*Nov 17 17:46:10:761 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Delete Timer: RDS_INTERNUM_TIMER
ID: 529
// The information above is the called number collection process. After the user pressed the dial
terminator #, all digits of the called number were received, and the RDS_FIRSTNUM_TIMER and
RDS_INTERNUM_TIMER were deleted.
*Nov 17 17:46:10:761 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
10000 ms
Create Timer: RDS_AUTHOR_TIMER ID: 541 Length:
// The digits of the called number were received. An authorization request was originated to the AAA
module. The RDS_AUTHOR_TIMER with a time length of 10 seconds was created.
*Nov 17 17:46:10:795 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Delete Timer: RDS_AUTHOR_TIMER
ID: 541
// An Authorization_OK message was received from the AAA module. The RDS_AUTHOR_TIMER was
deleted.
*Nov 17 17:46:14:189 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_TALKING]
8000 ms
Create Timer: RDS_TALK_TIMER ID: 559 Length:
// The RDS_TALK_TIMER with a time length of 8 seconds was created.
*Nov 17 17:46:21:391 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_TALKING]
Delete Timer: RDS_TALK_TIMER
ID: 559
// The RDS_TALK_TIMER was deleted.
*Nov 17 17:46:21:391 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_TALKING]
10000 ms
Create Timer: RDS_ACCT_TIMER
ID: 653 Length:
// A timer was created, specifying a wait time for a VoIP_Accounting_Stop_ACK message.
*Nov 17 17:46:21:438 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_TALKING]
Delete Timer: RDS_ACCT_TIMER
ID: 653
// The timer for waiting for a VoIP_Accounting_Stop_ACK message was deleted.
*Nov 17 17:46:21:444 2006 VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
ID: 965
Create Timer: RDS_FIRSTNUM_TIMER
Length: 10000 ms
// A timer was created, specifying a wait time for the first digit of a called number.
* Nov 17 17:46:25:456 2006 VORDS/7/VOICE:
285
VORDS_TIMER: [2] [RDS_STATE_CALLED_RCV]
Delete Timer: RDS_FIRSTNUM_TIMER
ID: 965
// The timer for waiting for the first digit of a called number was deleted.
*Nov 17 17:46:26:78 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_RELEASE]
10000 ms
Create Timer: RDS_ACCT_TIMER ID: 738 Length:
// A timer was created, specifying a wait time for a PSTN_Accounting_Stop_ACK message.
*Nov 17 17:46:26:99 2006 Sysname VORDS/7/VOICE:
VORDS_TIMER: [2] [RDS_STATE_RELEASE]
Delete Timer: RDS_ACCT_TIMER
ID: 738
// The timer for waiting for a PSTN_Accounting_Stop_ACK message was deleted.
# Enable debugging for messages between the voice RADIUS module and the AAA module.
<Sysname> debugging voice radius trace
Enable VORDS trace debugging functions
<Sysname>
*Nov 17 17:46:56:631 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
VORDS [3] ---> AAA [-1]
Msg: ACCT_START
Acct Type: 1
Calling Num: 200
Called Num: 201
Access Num: 201
// The voice RADIUS module sent an Accounting_Start message to the AAA module. The accounting
type is 1, which means that accounting was performed on the originating PSTN side.
*Nov 17 17:46:56:659 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
AAA [6] ---> VORDS [3]
Msg: ACCT_OK
Acct Type: 1
// A PSTN_Accounting_OK message was received from the AAA module.
*Nov 17 17:47:15:110 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
VORDS [3] ---> AAA [-1]
Msg: AUTHEN
Calling Num: 200
UserName: 450110
Called Num:
Access Num: 201
Service Type: 1
// The password was received, and a card number/password authentication request was originated to
the AAA module.
*Nov 17 17:47:15:134 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
AAA [7] ---> VORDS [3]
Msg: AUTHEN_OK
Remain Money: 7100
// An Authentication_OK message was received from the AAA module. The balance on the card is
RMB71.
*Nov 17 17:47:28:670 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
VORDS [3] ---> AAA [7]
Msg: AUTHOR
Calling Num: 200
UserName: 450110
Called Num: 400
Access Num: 201
// An Authorization message was sent to the AAA module for the called number.
*Nov 17 17:47:28:708 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
AAA [7] ---> VORDS [3]
Msg: AUTHOR_OK
Remain Time: 60
// An Authorization_OK message was received from the AAA module. The call duration was 60
seconds.
286
*Nov 17 17:47:31:739 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
VORDS [3] ---> AAA [7]
Msg: ACCT_START
Acct Type: 2
Calling Num: 200
Called Num: 400
Access Num: 201
// A VoIP_Accounting_Start message was sent to the AAA module.
*Nov 17 17:47:31:790 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
AAA [7] ---> VORDS [3]
Msg: ACCT_OK
Acct Type: 2
// A VoIP_Accounting_OK message was received. Accounting succeeded.
*Nov 17 17:47:43:142 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
VORDS [3] ---> AAA [7]
Msg: ACCT_STOP
Acct Type: 2
Calling Num: 200
Access Num: 201
Connection Time: 13
Called Num: 400
Stop-only: [No]
Session Time: 5
// A VoIP_Accounting_Stop message was sent to the AAA module. The connection time is 13 seconds,
and the call duration is 5 seconds.
*Nov 17 17:47:43:202 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
AAA [7] ---> VORDS [3]
Msg: ACCT_OK
Acct Type: 2
// An Accounting_OK message was received from the AAA module.
*Nov 17 17:47:47:706 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
VORDS [3] ---> AAA [6]
Msg: ACCT_STOP
Acct Type: 1
Calling Num: 200
Access Num: 201
Connection Time: 52
Called Num: 201
Stop-only: [No]
Session Time: 9
// A PSTN_Accounting_Stop message was sent to the AAA module.
*Nov 17 17:47:47:783 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
Msg: ACCT_OK
AAA [6] ---> VORDS [3]
Acct Type: 1
// An Accounting_OK message was received from the AAA module.
*Nov 17 17:47:47:784 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
Msg: LEAVING
VORDS [3] ---> AAA [6]
Calling Num: 200
Called Num: 201
// A Leaving message was sent to the AAA module for the incoming call.
*Nov 17 17:47:47:784 2006 Sysname VORDS/7/VOICE:
VORDS_TRACE:
Msg: LEAVING
VORDS [3] ---> AAA [7]
Calling Num: 200
Called Num: 201
// A LEAVING message was sent to the AAA module for the outgoing call.
287
RIP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging rip
Use debugging rip to enable RIP debugging.
Use undo debugging rip to disable RIP debugging.
Syntax
debugging rip process-id
undo debugging rip process-id
Default
RIP debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
Examples
# Enable RIP debugging for RIP process 1.
<Sysname> debugging rip 1
debugging rip brief
Use debugging rip brief to enable brief RIP debugging.
Use undo debugging rip brief to disable brief RIP debugging.
Syntax
debugging rip process-id brief
undo debugging rip process-id brief
Default
RIP brief debugging is disabled.
Views
User view
Default command level
1: Monitor level
288
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
Examples
# Enable brief RIP debugging on Router A. The output in this example was created when the following
conditions exist:
•
Router A is connected to Router B through Ethernet 1/1.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 brief
*Nov 24 15:28:22:814 2006 Sysname RM/6/RMDEBUG: RIP 1 : Sending v2 response on Ethernet1/1
from 40.0.0.2
// RIP process 1 sent a response packet of version 2 on Ethernet 1/1 from 40.0.0.2.
*Nov 24 15:28:34:868 2006 Sysname RM/6/RMDEBUG: RIP 1 : Receiving v2 response on Ethernet1/1
from 40.0.0.1
// RIP process 1 received a response packet of version 2 on Ethernet 1/1 from 40.0.0.1.
debugging rip event
Use debugging rip event to enable RIP event debugging.
Use undo debugging rip event to disable RIP event debugging.
Syntax
debugging rip process-id event
undo debugging rip process-id event
Default
RIP event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
Usage guidelines
Table 1 describes output fields and messages for the debugging rip event command.
289
Table 171 Output from the debugging rip event command
Field
Description
RIP sent a message to BFD successfully.
• msg-type—BFD message type.
• pkt-type—Packet type, which can be Echo or
RIP-BFD: Success to send msg. Message Type
msg-type, Pkt Type pkt-type, Src IP Address src-ip, Src
IFIndex if-index, Nbr IP Address nbr-ip.
Control.
• src-ip—Source IP address for session
establishment.
• if-index—Interface index maintained by route
management.
• nbr-ip—Neighbor IP address for session
establishment.
RIP-BFD: Failed to send msg. Message Type msg-type,
Pkt Type pkt-type, Src IP Address src-ip, Src IFIndex
if-index, Nbr IP Address nbr-ip.
RIP failed to send a message to BFD.
RIP-BFD: Receive BFD session down, Pkt Type pkt-type,
Src IP Address src-ip, Src IFIndex if-index, Dst IP
Address nbr-ip.
RIP received a message indicating that the BFD session
is down.
Examples
# Enable RIP event debugging on Router A. The output in this example was created when the following
conditions exist:
•
Router A is connected to Router B through Ethernet 1/1.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 event
# On Router A, disable RIP process 1 on Ethernet 1/1 attached to the network 40.0.0.0.
[Sysname-rip-1] undo network 40.0.0.0
*Nov 24 15:33:24:194 2006 Sysname RM/6/RMDEBUG: RIP 1 : Removing Ethernet1/1 from Network
List
// RIP process 1 was disabled on Ethernet 1/1.
# On Router A, enable RIP process 1 on Ethernet 1/1 attached to the network 40.0.0.0.
[Sysname-rip-1] network 40.0.0.0
*Nov 24 15:36:12:162 2006 Sysname RM/6/RMDEBUG: RIP 1 : Adding Ethernet1/1 to Network List
// RIP process 1 was enabled on Ethernet 1/1.
# Redistribute static routes into RIP process 1 on Router A.
[Sysname-rip-1] import-route static
*Nov 24 15:38:21:642 2006 Sysname RM/6/RMDEBUG: RIP 1 : Rebuilding of Database has started
*Nov 24 15:38:21:642 2006 Sysname RM/6/RMDEBUG: RIP 1 : Database has been rebuilt
// RIP process 1 had rebuilt the database.
# Enable RIP event debugging on Router A. The output in this example was created when the following
conditions exist:
•
Serial 2/0 of Router A is connected to Serial 2/0 of Router B.
•
RIP process 1 is created on Router A and TRIP is enabled on Serial 2/0.
•
RIP process is created on Router B and TRIP is enabled on Serial 2/0.
290
<Sysname> debugging rip 1 event
*Nov 24 15:42:35:836 2006 Sysname RM/3/RMDEBUG: TRIP 1 : TRIP's neighbour changes to NEW
status.
// The state of the neighbor of TRIP process 1 changed to NEW.
*Nov 24 15:42:35:836 2006 Sysname RM/3/RMDEBUG: TRIP 1 : TRIP's neighbour changes to UP
status.
// The state of the neighbor of TRIP process 1 changed to UP.
*Nov 24 15:42:35:868 2006 Sysname RM/3/RMDEBUG: TRIP 1 : TRIP's neighbour changes from
UP to FULL status.
// The state of the neighbor of TRIP process 1 changed from UP to FULL.
debugging rip packet
Use debugging rip packet to enable RIP packet debugging.
Use undo debugging rip packet to disable RIP packet debugging.
Syntax
debugging rip process-id packet [ interface interface-type interface-number ]
undo debugging rip process-id packet [ interface interface-type interface-number ]
Default
RIP packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Examples
# Enable RIP packet debugging on Ethernet 1/1 of Router A. The output in this example was created
when the following conditions exist:
•
Router A is connected to Router B through Ethernet 1/1.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 packet interface ethernet 1/1
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG: RIP 1 : Sending response on interface
Ethernet1/1 from 40.0.0.2 to 224.0.0.9
// RIP process 1 sent a response packet on Ethernet 1/1 from 40.0.0.2 to 224.0.0.9.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
84
Packet : vers 2, cmd response, length
// The response packet version is 2 and the packet length is 84 bytes.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
authentication-mode simple: 1234
// The packet uses simple authentication, with password 1234.
291
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.2/255.255.255.255,
// The first route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.0/255.0.0.0, nexthop
// The second route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 110.0.0.1/255.255.255.255,
// The third route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG: RIP 1 : Receive response from 40.0.0.1 on
Ethernet1/1
// RIP process 1 received a response packet from 40.0.0.1 on Ethernet 1/1.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
84
Packet : vers 2, cmd response, length
// The version of the received response packet is 2 and the packet length is 84 bytes.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.1/255.255.255.255,
// The first route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.0/255.0.0.0, nexthop
// The second route entry was output.
*Nov 24 15:57:46:86 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 100.0.0.1/255.255.255.255,
// The third route entry was output.
*Nov 24 15:57:46:86 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 16, tag 0
AFI 2, dest 110.0.0.1/255.255.255.255,
// The fourth route entry was output.
*Nov 24 15:57:46:102 2006 Sysname RM/3/RMDEBUG: RIP 1 : Ignoring this packet.
Authentication validation failed.
// Authentication failed. The received response packet was ignored.
# Clear the packet debugging information of the specified process, so no related debugging information
is displayed.
<Sysname> reset rip 1 process
Warning : Reset RIP process? [Y/N]:y
# Enable packet debugging if you want to view packet debugging information on Router A after the reset
operation.
<Sysname> debugging rip 1 packet
# Enable RIP packet debugging on Router A. The output in this example was created when the following
conditions exist:
•
Serial 2/0 of Router A is connected to Serial 2/0 of Router B.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 packet
*Nov 24 15:45:45:522 2006 Sysname RM/6/RMDEBUG: TRIP 1 : Sending request on interface
Serial2/0 to 224.0.0.9
// TRIP process 1 sent a request packet on Serial2/0 to 224.0.0.9.
292
*Nov 24 15:45:45:537 2006 Sysname RM/6/RMDEBUG:
8
Packet : vers 2, cmd request, length
// The version of the sent request packet is 2 and the packet length is 8 bytes.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG: TRIP 1 : Receive response on Serial2/0
from 50.0.0.2
// TRIP process 1 received a response packet from 50.0.0.2 on Serial 2/0.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG:
length 8, sequence num 0
Packet : vers 2, cmd response (FLUSH),
// The version of the received response packet (with FLUSH) is 2. The packet length is 8 bytes and the
sequence number is 0.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG: TRIP 1 : Sending acknowledgement on
interface Serial2/0 to 50.0.0.2
// TRIP process 1 sent an acknowledgement packet on Serial 2/0 to 50.0.0.2.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG:
(FLUSH), length 8, sequence num 0
Packet : vers 2, cmd acknowledgement
// The version of the sent acknowledgement packet (with FLUSH) is 2. The packet length is 8 bytes and
the sequence number is 0.
debugging rip receive
Use debugging rip receive to enable received RIP packet debugging.
Use undo debugging rip receive to disable received RIP packet debugging.
Syntax
debugging rip process-id receive [ interface interface-type interface-number ]
undo debugging rip process-id receive [ interface interface-type interface-number ]
Default
Received RIP packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 2 describes output fields and messages for the debugging rip receive command.
Table 172 Output from the debugging rip receive command
Field
Description
Authentication failure
Authentication failed because of an authentication
type mismatch or a non-minus RFC 2453 sequence
number.
293
Field
Description
Sequence: seq-number (number)
Sequence number of MD5 authentication (RFC 2453).
Sequence: seq-number
Sequence number of MD5 authentication (RFC 2082).
invalid authentication
The values of the 0xFFFF and 0x01 fields in the MD5
authentication (RFC 2082) packets are incorrect.
Therefore, the authentication is invalid.
Examples
# Enable RIP received packet debugging on Ethernet 1/1 of Router A. The output in this example was
created when the following conditions exist:
•
Router A is connected to Router B through Ethernet 1/1.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 receive interface ethernet 1/1
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG: RIP 1 : Receive response from 40.0.0.1 on
Ethernet1/0
// RIP process 1 received a response packet from 40.0.0.1 on Ethernet 1/1.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
84
Packet : vers 2, cmd response, length
// The version of the received response packet is 2 and the packet length is 84 bytes.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.1/255.255.255.255,
// The first route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.0/255.0.0.0, nexthop
// The second route entry was output.
*Nov 24 15:57:46:86 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 100.0.0.1/255.255.255.255,
// The third route entry was output.
*Nov 24 15:57:46:86 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 16, tag 0
AFI 2, dest 110.0.0.1/255.255.255.255,
// The fourth route entry was output.
# Clear the packet debugging information of the specified process, so no related debugging information
is displayed.
<Sysname> reset rip 1 process
Warning : Reset RIP process? [Y/N]:y
# Enable received packet debugging if you want to view packet debugging information on Router A after
the reset operation.
<Sysname> debugging rip 1 receive
# Enable RIP received packet debugging on Router A. The output in this example was created when the
following conditions exist:
•
Serial 2/0 of Router A is connected to Serial 2/0 of Router B.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 receive
294
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG: TRIP 1 : Receive response on Serial2/0
from 50.0.0.2
// TRIP process 1 received a response packet from 50.0.0.2 on Serial 2/0.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG:
length 8, sequence num 0
Packet : vers 2, cmd response (FLUSH),
// The version of the received response packet (with FLUSH) is 2. The packet length is 8 bytes and the
sequence number is 0.
debugging rip send
Use debugging rip send to enable sent RIP packet debugging.
Use undo debugging rip send to disable sent RIP packet debugging.
Syntax
debugging rip process-id send [ interface interface-type interface-number ]
undo debugging rip process-id send [ interface interface-type interface-number ]
Default
Sent RIP packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
Table 3 describes output fields and messages for the debugging rip send command.
Table 173 Output from the debugging rip send command
Field
Description
Sequence: seq-number (number)
Sequence number of MD5 authentication (RFC 2453).
Sequence: seq-number
Sequence number of MD5 authentication (RFC 2082).
invalid authentication
The values of the 0xFFFF and 0x01 fields in the MD5
authentication (RFC 2082) packets are incorrect.
Therefore, the authentication is invalid.
Examples
# Enable RIP sent packet debugging on Ethernet 1/1 of Router A. The output in this example was created
when the following conditions exist:
•
Router A is connected to Router B through Ethernet 1/1.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 send interface ethernet1/1
295
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG: RIP 1 : Sending response on interface
Ethernet1/1 from 40.0.0.2 to 224.0.0.9
// RIP process 1 sent a response packet on Ethernet 1/1 from 40.0.0.2 to 224.0.0.9.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
84
Packet : vers 2, cmd response, length
// The version of the response packet is 2 and the packet length is 84 bytes.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
authentication-mode simple: 1234
// The packet uses simple authentication, with the password 1234.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.2/255.255.255.255,
// The first route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
0.0.0.0, cost 1, tag 0
AFI 2, dest 50.0.0.0/255.0.0.0, nexthop
// The second route entry was output.
*Nov 24 15:57:46:32 2006 Sysname RM/6/RMDEBUG:
nexthop 0.0.0.0, cost 1, tag 0
AFI 2, dest 110.0.0.1/255.255.255.255,
// The third route entry was output.
# Clear the packet debugging information of the specified process, so no related debugging information
is displayed.
<Sysname> reset rip 1 process
Warning : Reset RIP process? [Y/N]:y
# Enable sent packet debugging if you want to view packet debugging information on Router A after the
reset operation.
<Sysname> debugging rip 1 send
# Enable RIP sent packet debugging on Router A. The output in this example was created when the
following conditions exist:
•
Serial 2/0 of Router A is connected to Serial 2/0 of Router B.
•
RIP is enabled on Router A and Router B.
<Sysname> debugging rip 1 send
*Nov 24 15:45:45:522 2006 Sysname RM/6/RMDEBUG: TRIP 1 : Sending request on interface
Serial2/0 to 224.0.0.9
// TRIP process 1 sent a request packet on Serial 2/0 to 224.0.0.9.
*Nov 24 15:45:45:537 2006 Sysname RM/6/RMDEBUG:
8
Packet : vers 2, cmd request, length
// The version of the sent request packet is 2 and the packet length is 8 bytes.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG: TRIP 1 : Sending acknowledgement on
interface Serial2/0 to 50.0.0.2
// TRIP process 1 sent an acknowledgement packet on Serial 2/0 to 50.0.0.2.
*Nov 24 15:45:45:564 2006 Sysname RM/6/RMDEBUG:
(FLUSH), length 8, sequence num 0
Packet : vers 2, cmd acknowledgement
// The version of the sent acknowledgement packet (with FLUSH) is 2. The packet length is 8 bytes and
the sequence number is 0.
296
debugging rip timer
Use debugging rip timer to enable RIP timer debugging.
Use undo debugging rip timer to disable RIP timer debugging.
Syntax
debugging rip process-id timer
undo debugging rip process-id timer
Default
RIP timer debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIP process by its ID in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Examples
# Enable timer debugging for RIP process 1.
<Sysname> debugging rip 1 timer
*Oct 23 14:21:01:382 2006 Sysname RM/6/RMDEBUG: RIP 1 : Periodic timer expired
// The periodic update timer of RIP process 1 expired.
297
RIPng debugging commands
debugging ripng
Use debugging ripng to enable all RIPng debugging.
Use undo debugging ripng to disable all RIPng debugging.
Syntax
debugging ripng process-id
undo debugging ripng process-id
Default
No RIPng debugging is enabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
debugging ripng brief
Use debugging ripng brief to enable RIPng brief debugging.
Use undo debugging ripng brief to disable RIPng brief debugging.
Syntax
debugging ripng process-id brief
undo debugging ripng process-id brief
Default
RIPng brief debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Examples
# Enable RIPng brief debugging on Router A. The output in this example was created when the following
conditions exist:
298
•
Ethernet 1/1 of Router A is connected to Ethernet 1/1 of Router B.
•
RIPng is enabled on Ethernet 1/1 of Router A and on Ethernet 1/1 of Router B.
<Sysname> debugging ripng 1 brief
*Nov 22 21:17:37:662 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Sending v1 response on Ethernet1/1
to FF02::9 with 2 RTEs
// RIPng process 1 sent a response packets of version 1 on Ethernet 1/1 to FF02::9 with two RTEs.
*Nov 22 21:17:40:390 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Receiving v1 response on
Ethernet1/1 from FE80::200:5EFF:FE71:A706 with 2 RTEs
// RIPng process 1 received a response packet of version 1 on Ethernet 1/1 from
FE80::200:5EFF:FE71:A706 with two RTEs.
debugging ripng event
Use debugging ripng event to enable RIPng event debugging.
Use undo debugging ripng event to disable RIPng event debugging.
Syntax
debugging ripng process-id event
undo debugging ripng process-id event
Default
RIPng event debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID, in the range of 1 to 65535.
Examples
# Enable RIPng event debugging on Router A. The output in this example was created when the following
conditions exist:
•
RIPng process 1 is created on Router A.
•
RIPng is enabled on Ethernet 1/1.
<Sysname> debugging ripng 1 event
[Sysname-Ethernet1/1] ripng 1 enable
*Nov 22 21:48:54:988 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Adding Ethernet1/1 to Network
List
// RIPng process 1 was enabled on Ethernet 1/1.
*Nov 22 21:47:25:836 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Triggered update sent
// RIPng process 1 sent a triggered update.
# Disable RIPng on Ethernet 1/1 of Router A.
[Sysname-Ethernet1/1] undo ripng enable
*Nov 22 21:50:46:270 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Removing Ethernet1/1 from Network
List
299
// RIPng process 1 was disabled on Ethernet 1/1.
# Redistribute direct routes into RIPng process 1 on Router A.
[Sysname-ripng-1] import-route direct
*Nov 23 13:29:24:640 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Rebuilding of Database has started
*Nov 23 13:29:24:640 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Database has been rebuilt
// RIPng process 1 rebuilt the database.
debugging ripng packet
Use debugging ripng packet to enable RIPng packet debugging.
Use undo debugging ripng packet to disable RIPng packet debugging.
Syntax
debugging ripng process-id packet [ interface interface-type interface-number ]
undo debugging ripng process-id packet [ interface interface-type interface-number ]
Default
RIPng packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID, in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Examples
# Enable RIPng packet debugging on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/1 of Router A is connected to Ethernet 1/1 of Router B.
•
RIPng process 1 is created on Router A and RIPng is enabled on Ethernet 1/1.
•
RIPng process is created on Router B and RIPng is enabled on Ethernet 1/1.
<Sysname> debugging ripng 1 packet
*Nov 24 13:49:27:98 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Receiving response message from
FE80::200:5EFF:FE71:A700 on Ethernet1/1
// RIPng process 1 received a response packet on Ethernet 1/1, whose IPv6 address is
FE80::200:5EFF:FE71:A700.
*Nov 24 13:49:27:98 2006 Sysname RM/6/RMDEBUG: Packet : vers 1, cmd response, length 64
// The version of the received response packet is 1 and the packet length is 64 bytes.
*Nov 24 13:49:27:98 2006 Sysname RM/6/RMDEBUG: Dest 22::/64, cost 16, tag 0
// The first route entry was output.
*Nov 24 13:49:27:98 2006 Sysname RM/6/RMDEBUG: Dest 50::/64, cost 1, tag 0
// The second route entry was output.
*Nov 24 13:49:27:98 2006 Sysname RM/6/RMDEBUG: Dest 1001::1/128, cost 1, tag 0
300
// The third route entry was output.
*Nov 24 13:49:51:130 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Sending response message on
Ethernet1/1 to FF02::9
// RIPng process 1 sent a response packet on Ethernet 1/1 to FF02::9.
*Nov 24 13:49:52:302 2006 Sysname RM/6/RMDEBUG: Packet : vers 1, cmd response, length 44
// The version of the sent response packet is 1 and the packet length is 44 bytes.
*Nov 24 13:49:52:317 2006 Sysname RM/6/RMDEBUG: Dest 22::/64, cost 16, tag 0
// The first route entry was output.
*Nov 24 13:49:52:317 2006 Sysname RM/6/RMDEBUG: Dest 2000::1/128, cost 1, tag 0
// The second route entry was output.
debugging ripng receive
Use debugging ripng receive to enable RIPng received packet debugging.
Use undo debugging ripng receive to disable RIPng received packet debugging.
Syntax
debugging ripng process-id receive [ interface interface-type interface-number ]
undo debugging ripng process-id receive [ interface interface-type interface-number ]
Default
RIPng received packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID, in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Examples
# Enable RIPng received packet debugging on Router A. The output in this example was created when
the following conditions exist:
•
Ethernet 1/1 of Router A is connected to Ethernet 1/1 of Router B.
•
RIPng process 1 is created on Router A and RIPng is enabled on Ethernet 1/1.
•
RIPng process 1 is created on Router B and RIPng is enabled on Ethernet 1/1.
<Sysname> debugging ripng 1 receive
*Nov 22 21:41:02:00 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Receiving response message from
FE80::200:5EFF:FE71:A706 on Ethernet1/1
// RIPng process 1 received a response packet from FE80::200:5EFF:FE71:A706 on Ethernet 1/1.
*Nov 22 21:41:02:00 2006 Sysname RM/6/RMDEBUG: Packet : vers 1, cmd response, length 44
// The version of the received response packet is 1, and the packet length is 44 bytes.
*Nov 22 21:41:02:00 2006 Sysname RM/6/RMDEBUG: Dest 22::/64, cost 1, tag 0
// The first route entry was output.
301
*Nov 22 21:41:02:00 2006 Sysname RM/6/RMDEBUG: Dest 50::/64, cost 1, tag 0
// The second route entry was output.
debugging ripng send
Use debugging ripng send to enable RIPng sent packet debugging.
Use undo debugging ripng send to disable RIPng sent packet debugging.
Syntax
debugging ripng process-id send [ interface interface-type interface-number ]
undo debugging ripng process-id send [ interface interface-type interface-number ]
Default
RIPng sent packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID, in the range of 1 to 65535.
interface interface-type interface-number: Specifies an interface by its type and number.
Examples
# Enable RIPng sent packet debugging on Router A. The output in this example was created when the
following conditions exist:
•
Ethernet 1/1 of Router A is connected to Ethernet 1/1 of Router B.
•
RIPng process 1 is created on Router A and RIPng is enabled on Ethernet 1/1.
•
RIPng process is created on Router B and RIPng is enabled on Ethernet 1/1.
<Sysname> debugging ripng 1 send
*Nov 22 21:35:29:86 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Sending response message on
Ethernet1/1 to FF02::9
// RIPng process 1 sent a RIPng response packet on Ethernet 1/1 to FF02::9.
*Nov 22 21:35:29:86 2006 Sysname RM/6/RMDEBUG: Packet : vers 1, cmd response, length 44
// The response packet version is 1, and the packet length is 44 bytes.
*Nov 22 21:35:29:86 2006 Sysname RM/6/RMDEBUG: Dest 22::/64, cost 1, tag 0
// The first route entry was output.
*Nov 22 21:35:29:86 2006 Sysname RM/6/RMDEBUG: Dest 33::/64, cost 1, tag 0
// The second route entry was output.
debugging ripng timer
Use debugging ripng timer to enable RIPng timer debugging.
Use undo debugging ripng timer to disable RIPng timer debugging.
302
Syntax
debugging ripng process-id timer
undo debugging ripng process-id timer
Default
RIPng timer debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
process-id: Specifies a RIPng process by its ID in the range of 1 to 65535.
Examples
# Enable RIPng timer debugging on the device running RIPng.
<Sysname> debugging ripng 1 timer
*Oct 18 13:38:32:406 2006 Sysname RM/6/RMDEBUG:RIPng 1 : Periodic timer expired
// The periodic update timer of RIPng process 1 expired.
303
RMON debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging rmon
Use debugging rmon to enable RMON debugging.
Use undo debugging rmon to disable RMON debugging.
Syntax
debugging rmon [ error | info | warning ]
undo debugging rmon [ error | info | warning ]
Views
User view
Default command level
1: Monitor level
Parameters
error: Specifies RMON error debugging.
info: Specifies RMON info debugging.
warning: Specifies RMON warning debugging.
Usage guidelines
If you execute the command without specifying any keyword, the command enables all type of RMON
debugging.
Table 1 describes output fields and messages for the debugging rmon command.
Table 174 Output from the debugging rmon command
Field
Description
INFO
Message severity level is informational.
WARNING
Message severity level is warning.
ERROR
Message severity level is error.
reallocate memory for saving configuration
Memory was reallocated for saving RMON
configuration.
failed to reallocate memory for saving configuration
Failed to reallocate memory for saving RMON
configuration.
update current RMON configuration of
interface-name
RMON configuration was updated on an interface.
invalid index index in real time
Invalid RMON table entry index was found during
real-time backup.
304
Field
Description
invalid index index in real time on slave board
Invalid RMON table entry index was found on the
standby MPU during real-time backup.
index—Index of an RMON table entry.
etherStatsEntry index aged at
time-hour:time-minute:time-second in real time on
slave board
The Ethernet statistics entry aged out during real-time
data backup on the standby MPU.
historyControlEntry index aged at
time-hour:time-minute:time-second in real time on
slave board
The history control entry aged out on the standby
MPU.
eventEntry index aged at
time-hour:time-minute:time-second in real time on
slave board
The event entry aged out during real-time data backup
on the standby MPU.
alarmEntry index aged at
time-hour:time-minute:time-second in real time on
slave board
The alarm entry aged out during real-time data
backup on the standby MPU.
prialarmEntry index aged at
time-hour:time-minute:time-second in real time on
slave board
The private alarm entry aged out during real-time data
backup on the standby MPU.
the port-removed flag of etherStatsEntry index
changed to false for interface-inserted event at
time-hour:time-minute:time-second in real time on
slave board
The port-removed flag of the Ethernet statistics entry
on the standby MPU changed to false because an
interface card was inserted during real-time data
backup.
the port-removed flag of historyControlEntry index
changed to false for interface-inserted event at
time-hour:time-minute:time-second in real time on
slave board
The port-removed flag of the history control entry on
the standby MPU changed to false because an
interface card was inserted during real-time data
backup.
failed to recover data in real time on slave board
The standby MPU failed to restore data during
real-time backup.
etherStatsEntry index aged at
time-hour:time-minute:time-second
Removal of an Ethernet interface can cause its Ethernet
statistics entry to age out.
historyControlEntry index aged at
time-hour:time-minute:time-second
A history control entry typically ages out because its
bucket is full or its timer expires.
synchronous RPC timeout in sampling statistics at
interface-name for historyControlEntry index
RPC call timed out when RMON was sampling data
on the Ethernet interface for the history control entry.
failed to call RPC synchronously (errCode: error-code)
in sampling statistics at interface-name for
historyControlEntry index
A synchronous RPC call failed when RMON was
sampling data on the Ethernet interface for the history
control entry.
sample no statistics at interface-name for
historyControlEntry index by synchronous RPC
RMON performed a synchronous RPC call to sample
statistics for the history control entry on the Ethernet
interface, but the call did not collect any statistics.
synchronous RPC timeout in sampling statistics at
interface-name for etherStatsEntry index
Synchronous RPC call timed out when RMON
sampled statistics on the Ethernet interface for the
Ethernet statistics entry.
failed to call RPC synchronously (errCode: error-code)
in sampling statistics at interface-name for
etherStatsEntry index
A synchronous RPC call failed when RMON was
sampling data on the Ethernet interface for the
Ethernet statistics entry.
305
Field
Description
sample no statistics at interface-name for
etherStatsEntry index by synchronous RPC
RMON performed a synchronous RPC call to sample
statistics for the Ethernet statistics entry on the Ethernet
interface, but the call did not collect any statistics.
the status of etherStatsEntry index changed to
underCreation for interface-removed event
Removal of an interface card caused all its interfaces
to be removed. As a result, the status of the Ethernet
statistics entry for an interface on the card changed to
underCreation. In this state, the entry does not take
effect.
the status of historyControlEntry index changed to
underCreation for interface-removed event
Removal of an interface card caused all its interfaces
to be removed. As a result, the status of the history
control entry for an interface on the card changed to
underCreation. In this state, the entry does not take
effect.
the port-removed flag of etherStatsEntry index
changed to false for interface-inserted event at
time-hour:time-minute:time-second
The port-removed flag of the Ethernet statistics entry
changed to false because an interface card was
inserted during real-time data backup.
the port-removed flag of historyControlEntry index
changed to false for interface-inserted event at
time-hour:time-minute:time-second
The port-removed flag of the history control entry on
the standby MPU changed to false because an
interface card was inserted during real-time data
backup.
An Ethernet statistics entry was deleted because its
associated interface was deleted.
delete etherStatsEntry index for interface-deleted event
delete historyControlEntry index for interface-deleted
event
the No. ordinal-number sample for prialarmEntry
index
An interface delete event typically occurs when you
replace an interface card with a different-model
interface card.
A history control entry was deleted because its
associated interface was deleted.
An interface delete event typically occurs when you
replace an interface card with a different-model
interface card.
The (ordinal-number)th sampling was performed for
prialarmTable entry index.
Examples
# Enable displaying debugging information and system message monitoring on the current terminal.
<Sysname> terminal debugging
<Sysname> terminal monitor
# Enable RMON info debugging.
<Sysname> debugging rmon info
# Configure a valid event group and a valid alarm group.
<Sysname> system-view
[Sysname] rmon event 1 log owner test
[Sysname]
*Apr 27 10:11:54:56 2000 Sysname RMON/7/INFO:
add eventEntry 1 through CLI or NMS
# Create an RMON alarm entry.
306
[Sysname] rmon alarm 1 1.3.6.1.2.1.6.3.0 5 absolute rising-threshold 100 1
falling-threshold 20 1
[Sysname]
*Apr 27 10:12:24:208 2000 Sysname RMON/7/INFO:
add alarmEntry 1 through CLI or NMS
*Apr 27 10:12:24:216 2000 Sysname RMON/7/INFO:
the No. 1 sample for alarmEntry 1
// RMON created the RMON alarm entry and sampled the monitored object for the first time.
[Sysname]
*Apr 27 10:12:28:403 2000 Sysname RMON/7/INFO:
sample statistics for alarmEntry 1 at 10:12:28
*Apr 27 10:12:28:408 2000 Sysname RMON/7/INFO:
the No. 2 sample for alarmEntry 1
*Apr 27 10:12:33:454 2000 Sysname RMON/7/INFO:
sample statistics for alarmEntry 1 at 10:12:33
*Apr 27 10:12:33:459 2000 Sysname RMON/7/INFO:
the No. 3 sample for alarmEntry 1
*Apr 27 10:12:38:504 2000 Sysname RMON/7/INFO:
sample statistics for alarmEntry 1 at 10:12:38
*Apr 27 10:12:38:509 2000 Sysname RMON/7/INFO:
the No. 4 sample for alarmEntry 1
// RMON periodically sampled the monitored object at the configured interval (5 seconds).
# Enable RMON error debugging.
<Sysname> debugging rmon error
<Sysname> system-view
# Configure an RMON private alarm entry with a nonexistent MIB variable.
[Sysname]rmon prialarm 1 100/(1.3.6.1.2.1.4.2.0-255) test 10 absolute rising-threshold
10 1 falling-threshold 20 1 entrytype forever
Failure! Wrong private alarm variable formula.
[Sysname]
*Jul 26 16:43:46:703 2007 Sysname RMON/7/ERROR:
failed to validate formula of prialarmEntry 1
// RMON failed to validate the formula of the monitored object in the newly created private alarm entry.
307
RPR debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging rpr error
Use debugging rpr error to enable RPR error debugging.
Use undo debugging rpr error to disable RPR error debugging.
Syntax
debugging rpr error [ interface interface-type interface-number ]
undo debugging rpr error [ interface interface-type interface-number ]
Default
RPR error debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
interface interface-type interface-number: Specifies a port by its type and number.
Usage guidelines
Table 1 describes output fields and messages for the debugging rpr error command.
Table 175 Output from the debugging rpr error command
Field
Description
RPR_Error: On interface-type
interface-number, String
System resource operation failed.
The String field content failed to allocate memory.
Error packets were received.
RPR_Error: On interface-type
interface-number, at String1
span, error packet is received.
String2
The String1 field indicates the direction (east or west).
The String2 field describes the detailed reason for errors:
• Invalid frame length. Type: packetType—Frames of invalid length were
received. packetType indicates the packet type, which can be TP, TC,
ATD, echo-response, or echo-request.
• Invalid frame type—Packets of invalid types were received.
308
Field
Description
Errors occurred to topology calculation.
The String field describes the detailed reason for errors:
• MAC duplicate error: ringlet ringlet_id hop hop_id duplicate with local
station, which means the MAC address of the hop hop-id of ringlet
ringlet-id overlaps with that of the local station. ringlet-id is 0 or 1, and
hop-id ranges from 1 to 254.
• MAC duplicate error: ringlet ringlet_id1 hop hop_id1 duplicate with
RPR_Error: On interface-type
interface-number, topology error
happened: String
ringlet ringlet_id2 hop hop_id2, which means the MAC address of the
hop hop-id1 of ringlet ringlet-id1 overlaps with that of the hop hop-id2 of
ringlet ringlet-id2. Both ringlet-id1 and ringlet-id2 range from 0 to 1, and
both hop-id1 and hop-id2 ranges from 1 to 254.
• IP duplicate error: ringlet ringlet_id hop hop_id duplicate with local
station, which means the IP address of the hop hop-id of ringlet ringlet-id
overlaps with that of the local station. ringlet-id is 0 or 1, and hop-id
ranges from 1 to 254.
• IP duplicate error: ringlet ringlet_id1 hop hop_id1 duplicate with ringlet
ringlet_id2 hop hop_id2, which means the IP address of the hop hop-id1
of ringlet ringlet-id1 overlaps with that of the hop hop-id2 of ringlet
ringlet-id2. Both ringlet-id1 and ringlet-id2 range from 0 to 1, and both
hop-id1 and hop-id2 ranges from 1 to 254.
Examples
# Enable debugging for RPR errors on interface RPR1. When you configure the same IP address for the
two stations that form a closed RPR ring, output similar to the following example is generated:
<Sysname> debugging rpr error interface rpr1
*Jun
5 10:06:39:104 2007 Sysname RPR/7/ERR_TOPO:Slot=3;
RPR_Error: On RPR1, topology error happened: Ip duplicate error: ringlet 0 hop 1 duplicate
with local station
// Topology calculation errors occurred on interface RPR1: the IP address of the first hop of ringlet 0
overlapped with that of the local station.
debugging rpr event
Use debugging rpr event to enable RPR event debugging.
Use undo debugging rpr event to disable RPR event debugging.
Syntax
debugging rpr event [ general | ringlet-selection ] [ interface interface-type interface-number ]
undo debugging rpr event [ general | ringlet-selection ] [ interface interface-type interface-number ]
Default
RPR event debugging is disabled.
Views
User view
Default command level
2: System level
309
Parameters
general: Specifies debugging for general RPR events, including protection state changes, miscabling
changes, and port UP/DOWN events.
ringlet-selection: Specifies debugging for RPR ringlet selection events.
interface interface-type interface-number: Specifies a port by its type and number.
Usage guidelines
Table 2 describes output fields and messages for the debugging rpr event command.
Table 176 Output from the debugging rpr event command
Field
Description
A ringlet selection table was updated.
The String1 field specifies the updated ringlet selection table:
•
•
•
•
•
•
•
default—Default ringlet selection table.
shortest path—Shortest path ringlet selection table.
overall—Overall ringlet selection table.
VRRP—VRRP ringlet selection table.
IPv6—IPv6 ringlet selection table.
VLANTunnel—VLAN tunnel ringlet selection table.
mac-learning—MAC learning ringlet selection table.
The String2 field specifies the updated contents:
RPR_Event: On interface-type
interface-number, String1 ringlet
selection table was updated!
String2
• MAC: MAC_ADDR updated—MAC addresses.
• Begin update ShortestPath rs with Wrap mode—Began updating the
shortest path ringlet selection table in wrap mode.
• End update dynamic rs with Wrap mode—Ended updating the
dynamic ringlet selection table in wrap mode.
• Begin update ShortestPath rs with Steer mode—Began updating the
shortest path ringlet selection table in steer mode.
• End update dynamic rs with ShortestPath—Ended updating the
dynamic ringlet selection table with ShortestPath.
• Update String RS start—Started updating the ringlet selection table.
The String field can be default, shortest path, overall, VRRP, IPv6,
VLANTunnel, or mac-learning.
• Update String RS finished—Finished updating the ringlet selection
table. The String field can be default, shortest path, overall, VRRP, IPv6,
VLANTunnel, or mac-learning.
• Update RS start—Began to update the ringlet selection table.
• Update RS finished—Finished updating the ringlet selection table.
The String field indicates the event that occurred:
RPR_Event: On interface-type
interface-number, String
•
•
•
•
•
TP content change flag is set.
Successed to Start protocol.
Begin to delete Ipv6 Mac Address: MAC_ADDR.
Begin to add Ipv6 Mac Address: MAC_ADDR.
End to add Ipv6 Mac Address: MAC_ADDR.
310
Field
Description
The String1 field indicates the direction (east or west)
The String2 field indicates the event that occurred:
RPR_Event: On interface-type
interface-number, at String1 span,
String2
•
•
•
•
•
Interface up—An interface went up.
Interface down—An interface went down.
Mistake cable is occurred—Miscabling occurred.
Protection status is changed—Protection state changed.
MATE status is changed—The state of the MATE port changed.
Examples
# Enable debugging for RPR ringlet selection event debugging. The output in this example was created
when two stations form a closed RPR ring. When you remove the optical fiber to trigger protection on the
station and update the ringlet selection table, output similar to the following example is generated:
<Sysname> debugging rpr event ringlet-selection
*Jun
5 11:24:51:218 2007 Sysname RPR/7/EVT_RS:Slot=3;
RPR_Event: On RPR1, overall ringlet selection table was updated! Update overall RS start!
// On interface RPR1, the overall ringlet selection table was updated. RPR began to update the overall
ringlet selection table.
*Jun
5 11:24:51:889 2007 Sysname RPR/7/EVT_RS:Slot=3;
RPR_Event: On RPR1, overall ringlet selection table was updated! Update overall RS
finished!
// On interface RPR1, the overall ringlet selection table was updated. RPR ended the updating of the
overall ringlet selection table.
# Enable debugging for RPR ringlet selection event debugging on interface RPR1. The output in this
example was created when two stations form a closed RPR ring. When you configure FS in the west
direction of a station to change the topology and update the ringlet selection table, output similar to the
following example is generated:
<Sysname> debugging rpr event ringlet-selection int rpr 1
*Jun
5 11:28:49:170 2007 Sysname RPR/7/EVT_RS:Slot=5;
RPR_Event: On RPR1, dynamic ringlet selection table was updated! Update shortest path
RS start!
// On interface RPR1, the dynamic ringlet selection table was updated. RPR began the updating of the
shortest path ringlet selection table.
*Jun
5 11:28:49:359 2007 Sysname RPR/7/EVT_RS:Slot=5;
RPR_Event: On RPR1, dynamic ringlet selection table was updated! Update shortest path
RS finished!
// On interface RPR1, the dynamic ringlet selection table was updated. RPR finished the updating of the
shortest path ringlet selection table.
# Enable RPR general event debugging. The output in this example was created when two stations form
a closed RPR ring. When you shut down the west physical port, output similar to the following example
is generated:
<Sysname> debugging rpr event general
*Jun
5 11:34:22:360 2007 Sysname RPR/7/EVT_SPAN:
RPR_Event: On RPR1, at west span, Interface down.
// On interface RPR1, the west physical port went down.
311
# Enable RPR general event debugging. The output in this example was created when two stations form
a closed RPR ring. When you remove the optical fiber connected to the west physical port, output similar
to the following example is generated:
<Sysname> debugging rpr event general int rpr 1
*Jun
5 11:38:40:211 2007 Sysname RPR/7/EVT_SPAN:Slot=3;
RPR_Event: On RPR1, at west span, Protection status is changed!
// On interface RPR1, the protection state on the west span changed.
debugging rpr fsm
Use debugging rpr fsm to enable RPR state machine debugging.
Use undo debugging rpr fsm to disable RPR state machine debugging.
Syntax
debugging rpr fsm [ interface interface-type interface-number ]
undo debugging rpr fsm [ interface interface-type interface-number ]
Default
RPR state machine debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
interface interface-type interface-number: Specifies a port by its type and number.
Usage guidelines
Table 3 describes output fields and messages for the debugging rpr fsm command.
Table 177 Output from the debugging rpr fsm command
Field
Description
The String field indicates the current protection event:
RPR_Fsm: On
interface-type
interface-number. String
protection switch is
current
•
•
•
•
•
•
•
•
TP_RCVD—Received TP frames.
WTR_EXP—WTR timer expired.
AUTO_IDLE—Link recovery event.
AUTO_SD—Signal degraded.
AUTO_SF—Signal failure.
ADMIN_IDLE—Manual recovery.
ADMIN_MS—Manual switch.
ADMIN_FS—Forced switch.
312
Field
Description
The String field indicates the current state machine:
RPR_Fsm: On
interface-type
interface-number. String
is running
•
•
•
•
WTR state machine.
receive TP frame state machine—Receiving TP frames.
transmit TP frame state machine—Transmitting TP frames.
topology DB update state machine stage1—Stage 1 of topology database
updating.
• topology DB update state machine stage2—Stage 2 of topology database
updating.
•
•
•
•
protection state machine.
topology validation state machine.
TC frame processing state machine.
ATD frame processing state machine—ATD frame processing state machine.
Protection switch.
The String1 field indicates the current protection state event:
RPR_Fsm: On
interface-type
interface-number
protection switch event
is overridden by String1
String2
•
•
•
•
•
•
•
•
TP_RCVD—Received TP frames.
WTR_EXP—WTR timer expired.
AUTO_IDLE—Link recovery event.
AUTO_SD—Signal degraded.
AUTO_SF—Signal failure.
ADMIN_IDLE—Manual recovery.
ADMIN_MS—Manual switch.
ADMIN_FS—Forced switch.
The String2 field indicates the switch type:
• locally.
• neighborly.
• distantly.
Print state machine information. The String field can be:
RPR_Fsm: On
interface-type
interface-number String
•
•
•
•
•
•
protection state machine: in stage START.
protection state machine: in stage FIRST.
protection state machine: in stage FINAL.
protection state machine: in stage POST.
protection state machine: in stage MAIN.
The current station is isolate—The current station is isolated.
Examples
# Enable RRPP state machine debugging. The output in this example was created when two stations form
a closed RPR ring. When you remove the optical fiber, output similar to the following example is
generated:
<Sysname> debugging rpr fsm
*Jun
5 11:44:12:982 2007 Sysname RPR/7/FSM_PRTEVT:Slot=5;
RPR_Fsm: On RPR1, at west span, AUTO_SF protection switch is current.
// On interface RPR1, signal failure occurred on the west span.
*Jun
5 11:44:13:142 2007 Sysname RPR/7/FSM:Slot=5;
RPR_Fsm: On RPR1, at west span, protection state machine: in stage START
// On interface RPR1, the protection state machine was in the START stage on the west span.
313
# Enable RPR state machine debugging on interface RPR1. The output in this example was created when
two stations form a closed RPR ring. When you shut down the west physical port, output similar to the
following example is generated:
<Sysname> debugging rpr fsm interface rpr 1
*Jun
5 11:50:04:203 2007 Sysname RPR/7/FSM:Slot=5;
RPR_Fsm: On RPR1, at west span, protection state machine: in stage POST
// On interface RPR1, the protection state machine was in the POST stage on the west span.
*Jun
5 11:50:04:363 2007 Sysname RPR/7/FSM:Slot=5;
RPR_Fsm: On RPR1, at west span, protection state machine: in stage FINAL
// On interface RPR1, the protection state machine was in the FINAL stage on the west span.
debugging rpr packet
Use debugging rpr packet to enable debugging for RPR packets.
Use undo debugging rpr packet to disable debugging for RPR packets.
Syntax
debugging rpr packet [ [ atd | echo-request | echo-response | tc | tp ] [ receive | send ] | { tc | tp }
burst_send ] [ interface interface-type interface-number ] [ verbose ]
undo debugging rpr packet [ [ atd | echo-request | echo-response | tc | tp ] [ receive | send ] | { tc |
tp } burst_send ] [ interface interface-type interface-number ]
Default
The debugging for RPR packets is disabled.
Views
User view
Default command level
2: System level
Parameters
atd: Specifies debugging for ATD frames.
echo-request: Specifies debugging for echo-request frames.
echo-response: Specifies debugging for echo-response frames.
tc: Specifies debugging for TC frames.
td: Specifies debugging for TD frames.
receive: Specifies debugging for received RPR packets.
send: Specifies debugging for sent RPR packets.
burst_send: Specifies debugging for burst_sent RPR packets.
verbose: Displays the detailed information about RPR packets. If this keyword is not specified, the brief
information about RPR packets is displayed.
interface interface-type interface-number: Specifies a port by its type and number.
314
Usage guidelines
If no packet type is specified, debugging for all types of RPR packets is enabled.
If neither receive nor send is specified, debugging for both received and sent RPR packets is enabled.
Table 4 describes output fields and messages for the debugging rpr packet command.
Table 178 Output from the debugging rpr packet command
Field
Description
RPR packet debugging information:
RPR_Packet: On interface-type
interface-number, at String1 span,
String2 packet was String3.
String 4
• String1—Direction (east or west).
• String2—Packet type, which can be TP, TC, ATD, echo-response, or
echo-request.
• String3—Received/sent packets. Received indicates the packets
received, sent indicates the packets sent, and burst-sent indicates the
packets burst-sent.
• String4—All contents of the packet.
Examples
# Enable RPR packet debugging on the device and display brief RPR packet debugging information. The
output in this example was created when two stations form a closed RPR ring.
<Sysname>debugging rpr packet
*Jun
5 12:43:02:365 2007 Sysname RPR/7/PKT_BRIEF_FUNC:Slot=5;
RPR_Packet: On RPR1, at east span, ATD packet was sent.
// On interface RPR1, the east span sent ATD frames.
# Enable RPR packet debugging on interface RPR1 and display detailed RPR packet debugging
information. The output in this example was created when two stations form a closed RPR ring.
<Sysname> debugging rpr packet interface rpr 1 verbose
*Jun
5 12:44:08:365 2007 Sysname RPR/7/PKT_VERBOSE_FUNC:Slot=5;
RPR_Packet: On RPR1, at east span, ATD packet was sent.
ttl:255
ri:0
fe:0
ft:1
sc:3
we:0
parity:0
DA:ffff-ffff-ffff SA:000f-e231-256d
ttlBase:255
ef:0
fi:0
ps:0
so:0
res:0
controlType:1 controlVersion:0
Ringlet0 weight: 0, ringlet1 weight: 0
Ringlet0 reserveband: 0, ringlet1 reserveband: 0
Station setting: mulitichoke-user 0;conversative 0;badfcs-user 0
Station name:
Manage address: 0.0.0.0
Ifindex: 63373312
Second mac1: 0000-0000-0000 Second mac2: 0000-0000-0000
// On interface RPR1, all contents of ATD frames sent to the east span were displayed.
# Enable debugging for RPR TP frames burst-sent on interface RPR1 and display detailed RPR packet
debugging information. The output in this example was created when two stations form a closed RPR
ring.
<Sysname> debugging rpr packet tp burst-send interface rpr 1 verbose
*Jun
5 13:45:21:56 2007 Sysname RPR/7/PKT_VERBOSE:Slot=5;
RPR_Packet: On RPR1, at west span, TP packet was burst-sent.
315
ttl:255
ri:0
fe:0
ft:1
sc:3
we:0
parity:0
DA:ffff-ffff-ffff SA:000f-e246-18af
ttlBase:255
ef:0
fi:0
ps:0
so:0
res:0
controlType:2 controlVersion:0
esw:1
ese:1
psw:5
pse:4
wc:0
jp:1
seqnum:29
// On interface RPR1, all contents of TP frames burst-sent to the west span were displayed.
NOTE:
For TP frames and TC frames, the sending function is mutually exclusive with the burst-sending function.
debugging rpr timer
Use debugging rpr timer to enable RPR timer debugging.
Use undo debugging rpr timer to disable RPR timer debugging.
Syntax
debugging rpr timer [ interface interface-type interface-number ]
undo debugging rpr timer [ interface interface-type interface-number ]
Default
RPR timer debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
interface interface-type interface-number: Specifies a port by its type and number.
Usage guidelines
Table 5 describes output fields and messages for the debugging rpr timer command.
316
Table 179 Output from the debugging rpr timer command
Field
Description
Timer event.
The String1 field indicates the timer name:
RPR_Timer: On interface-type
interface-number, String1 timer
String2
•
•
•
•
•
•
•
•
•
•
•
•
TD-Fast—TD fast timer.
TD-Slow—TD slow timer.
TC-Fast—TC fast timer.
TC-Slow—TC slow timer.
ATD—ATD timer.
holdoff—Holdoff timer.
keepalive—Keepalive timer.
stability—Stability timer.
instability—Instability timer.
Oam—OAM timer.
IdleIsolateDetect—IdleIsolateDetect timer.
ReportDefect—ReportDefect timer.
The String2 field indicates the timer action:
• starts.
• stops.
• expires.
Examples
# Enable RRPP timer debugging. The output in this example was created when two stations form a closed
RPR ring. When you remove the main interface board to trigger protection on the station, output similar
to the following example is generated:
<Sysname> debugging rpr timer
*Jun
5 13:46:50:236 2007 Sysname RPR/7/TIMER:Slot=5;
RPR_Timer: On RPR1, instability timer starts.
// On interface RPR1, the instability timer started.
*Jun
5 13:46:50:386 2007 Sysname RPR/7/TIMER:Slot=5;
RPR_Timer: On RPR1, stability timer starts.
// On interface RPR1, the stability timer started.
# Enable RRPP timer debugging on interface RPR1. The output in this example was created when two
stations form a closed RPR ring. When you remove the optical fiber connected to the main interface to
trigger protection on the station, output similar to the following example is generated:
<Sysname> debugging rpr timer interface rpr 1
*Jun
5 13:46:50:536 2007 Sysname RPR/7/TIMER:Slot=5;
RPR_Timer: On RPR1, stability timer expires.
// On interface RPR1, the stability timer expired.
*Jun
5 13:46:50:686 2007 Sysname RPR/7/TIMER:Slot=5;
RPR_Timer: On RPR1, instability timer stops.
// On interface RPR1, the instability timer expired.
317
RRPP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging rrpp
Use debugging rrpp to enable RRPP debugging.
Use undo debugging rrpp to disable RRPP debugging.
Syntax
debugging rrpp [ domain domain-id [ ring ring-id ] ] { all | error | event | fast-detect-fsm |
fast-detect-packet | fsm | packet }
undo debugging rrpp [ domain domain-id [ ring ring-id ] ] { all | error | event | fast-detect-fsm |
fast-detect-packet | fsm | packet }
Default
RRPP debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
domain-id: Specifies an RRPP domain by its ID, in the range of 1 to 8.
ring-id: Specifies an RRPP ring by its ID, in the range of 1 to 64.
all: Specifies all types of debugging for RRPP.
error: Specifies debugging for RRPP errors.
event: Specifies debugging for RRPP events.
fast-detect-fsm: Specifies debugging for the RRPP fast detection state machine.
fast-detect-packet: Specifies debugging for RRPP fast detection packets.
fsm: Specifies debugging for RRPP state machines.
packets: Specifies debugging for RPPP packets.
Usage guidelines
RRPP debugging can take effect on three levels: global, domain-level, and ring-level.
•
If neither the domain-id argument nor the ring-id argument is specified, the operation takes effect
globally. In this case, the debugging rrpp command enables debugging on all the rings and in all
the domains.
•
If only the domain-id argument is specified, the operation applies to all the rings in the domain.
318
•
If both the domain-id argument and the ring-id argument are specified, the operation applies to the
specified ring in the specified domain.
Table 1 describes output fields and messages for the debugging rrpp error command.
Table 180 Output from the debugging rrpp error command
Field
Description
The memory operation failed.
Failed to String
String field value:
• allocate memory—Applying for dynamic memory failed.
• copy MBUF to PDU—Copying Ethernet network packets to the PDU
failed.
Errors occurred when a port sent/received packets.
Domain domain-id Ring ring-id
Port interface-type
interface-number : String
•
•
•
•
domain-id—RRPP domain ID.
ring-id—RRPP ring ID.
interface-type interface-number—Interface type and interface number.
The string field describes the errors:


Master node received Health packet from primary port—The
primary port of the master node received Health packets from the
local node.
Send RRPP packet error—Sending RRPP packets failed.
RRPP failed to write a queue.
Failed to write String queue
String field value:
• packet—Writing a packet queue failed.
• link status—Writing a link status queue failed.
RRPP failed to write an event.
Failed to write String event
String field value:
• packet—Writing a packet event failed.
• link status—Writing a link status event failed.
319
Field
Description
A port received error packets. The reason is also given.
The string field describes the errors:
• illegal RRPP packet Length—The RRPP packet length field in the RRPP
packet received is invalid.
• illegal RRPP packet version—The RRPP version of the RRPP packet
received is invalid.
• illegal RRPP PDU Length—The RRPP PDU length field in the RRPP packet
received is invalid.
• illegal domain ID—The domain ID in the RRPP packet received is
invalid.
• inexistent domain—The domain ID in the RRPP packet received was not
the one configured on the local device.
• no active domain—The domain ID in the RRPP packet received was not
Received packet on port
interface-type interface-number
error ! Reason : String
activated, which means no ring was activated in the domain.
• illegal level—The level in the RRPP packet received is invalid.
• illegal RRPP packet—The type of the RRPP packet received is invalid.
• packet receives from non-ctrlvlan—The RRPP packet received was not
from the control VLAN of the specified domain, which means the
control VLAN did not match.
• illegal ring ID—The ring ID in the RRPP packet received is invalid.
• hello time out of range—The setting of the Hello timer in the RRPP
packet received is out of range.
• fail time out of range—The setting of the Fail timer in the RRPP packet
received is out of range.
• value of fail-time must not be less than triple value of hello-time—The
fail timer value is less than three times the Hello timer value.
• level mismatch—The ring level in the RRPP packet received does not
match the level of the ring in which the device resides.
• a conflicting master node of current ring was detected—Two master
nodes existed on the ring (this message was output by the master node).
Table 2 describes output fields and messages for the debugging rrpp event command.
Table 181 Output from the debugging rrpp event command
Field
Description
domain-id indicates the RRPP domain ID.
ring-id indicates the RRPP ring ID.
String field value:
Domain domain-id ring ring-id
String
•
•
•
•
is activated—The ring is activated.
is inactivated—The ring is deactivated.
turns to fault for link down—The ring fails because the link is down.
turns to fault for Link-Down packet—The ring fails because a link-down
packet is received.
• turns to fault for fail-timer timeout—The ring fails because the master
node receives no health packet of its own when the Fail timer expires.
• recovered for health packet—The ring recovers because the master
node receives health packets of its own.
320
Table 3 describes output fields and messages for the debugging rrpp fast-detect-fsm command.
Table 182 Output from the debugging rrpp fast-detect-fsm command
Field
Description
State machine information of a specific RRPP ring in a specific RRPP
domain.
Domain domain-id ring ring-id
String
• domain-id—RRPP domain ID.
• ring-id—RRPP ring ID.
• String field value:

RX FSM—Receive state machine.

TX FSM—Transmit state machine.

RXTX FSM—Receive and transmit state machines.
Previous state is State
Previous state of the state machine: Idle, Active, Complete, or Failed.
Current state is State
Current state of the state machine: Idle, Active, Complete, or Failed.
The String field indicates the state transition conditions:
• Receiving Fast-Detect packet from the primary port—The primary port
received fast-detection packets.
• Receiving Fast-Detect packet from the secondary port—The secondary
Transition event is String
port received fast-detection packets.
•
•
•
•
•
Fast-HelloTimer-Expired—The Fast-Hello Timer expired.
Fast-FailTimer-Expired—The Fast-Fail Timer expired.
Fail-Timer-Expired—The Fail timer expired.
Detect-Enabled—Fast detection was enabled.
Detect-Disabled—Fast detection was disabled.
Table 4 describes output fields and messages for the debugging rrpp fast-detect-packet command.
Table 183 Output from the debugging rrpp fast-detect-packet command
Field
Description
Information about fast-detection packets:
Domain domain-id ring ring-id
String1 fast-detect
packet.(Length: ULONG1, count:
ULONG2) String2
•
•
•
•
•
•
domain-id—RRPP domain ID.
ring-id—RRPP ring ID.
String1—Rcvd for receiving packets and Send for sending packets.
ULONG1—Packet length.
ULONG2—Number of packets.
String2—All contents of the packet in hexadecimal format.
Table 5 describes output fields and messages for the debugging rrpp fsm command.
321
Table 184 Output from the debugging rrpp fsm command
Field
Description
Information about a specific state machine of a specific ring in a specific
domain:
Domain domain-id ring ring-id
String
• domain-id—RRPP domain ID.
• ring-id—RRPP ring ID.
• The String1 field represents the state machine type:

Master Node FSM—Master node state machine.

Transit Node FSM—Transit node state machine.

Edge Node FSM—Edge node state machine.

Assistant-Edge Node FSM—Assistant edge node state machine.
Previous state is State
Previous state of the state machine: Complete, Failed, Init, Link-up,
Link-Down, Preforwarding, Link-Up-Notify, Link-Down-Notify,
Preforward-Notify, or Idle.
Current state is State
Current state of the state machine: Complete, Failed, Init, Link-up,
Link-Down, Preforwarding, Link-Up-Notify, Link-Down-Notify,
Preforward-Notify, or Idle.
A transition event occurred. The String2 field gives the cause of the state
transition:
Transition event is String
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Ring-Enabled—The ring is enabled.
Ring-Disabled—The ring is disabled.
the ports status under Init state—The port is in the initial state.
Hello-Timer-Expired—The Hello timer expires.
Fail-Timer-Expired—The Fail timer expires.
Edgehello-Timer-Expired—The Edgehello timer expires.
Edgefail-Timer-Expired—The Edgefail timer expires.
Receiving own Health packet.
Receiving Link-Down packet.
Receiving Common-Flush-FDB packet.
Receiving Complete-Flush-FDB packet.
Receiving Sub-Ring-FDB packet.
Receiving Edge-Hello packet.
Receiving Major-Fault packet.
own link down.
own link restoring.
Table 6 describes output fields and messages for the debugging rrpp packet command.
322
Table 185 Output from the debugging rrpp packet command
Field
Description
Packet debugging information:
Port interface-type
interface-number String1 packet
of domain domain-id
ringring-id.(Length: ULONG,
Type: String2) String3
• interface-type interface-number—Interface type and interface number.
• String1—Packet direction. This field can be Rcvd (indicating received
packets) or Send (indicating sent packets).
•
•
•
•
domain-id—RRPP domain ID.
ring-id—RRPP ring ID.
ULONG—Packet length.
String2—Packet type: Health, Link-Down, Complete-Flush-FDB,
Common-Flush-FDB, Edge-Hello, or Major-Fault.
• String3—The packet content in hexadecimal format.
Examples
# Enable debugging for RRPP errors on one of the two master nodes. The output in this example was
created when the following conditions exist:
•
Configure two master nodes on an RRPP ring, and configure the other devices as the transit nodes.
•
Enable RRPP on all the devices, and enable all the RRPP rings.
<Sysname> debugging rrpp error
*0.2484426 Sysname RRPP/8/RCVPKTERR:
Received packet on port Ethernet1/1 error ! Reason : a conflicting master node of current
ring was detected .
*0.2485436 Sysname RRPP/8/RCVPKTERR:
Received packet on port Ethernet1/1 error ! Reason : a conflicting master node of current
ring was detected .
// Two master nodes were detected on the ring.
# Enable debugging for RRPP events on Device B. The output in this example was created when Device
A operates as a transit node on the primary ring, with the RRPP ring enabled and RRPP protocol disabled.
When you configure Device B as the master node of the primary ring, with the RRPP ring and RRPP
protocol enabled, output similar to the following example is generated:
<Sysname> debugging rrpp event
*0.6664449 Sysname RRPP/8/EVT:
Domain 1 ring 1 is activated .
// Ring 1 of domain 1 was activated.
*0.6667140 Sysname RRPP/8/EVT:
Domain 1 ring 1 turns to fault for fail-timer timeout .
// The ring failed because the master node received no health packet of its own before the Fail timer
expired.
*0.8708437 Sysname RRPP/8/EVT:
Domain 1 ring 1 recovered for health packet .
// Ring 1 in domain 1 on Device B recovered after RRPP was enabled on Device A.
# Enable debugging for RRPP fast detection. The output in this example was created when transit nodes
and the assistant-edge node are configured for the primary ring.
<Sysname> debugging rrpp fast-detect-fsm
323
*0.8306346 Sysname RRPP/7/RRPPFSM:
Domain 1 ring 2 RX FSM. Previous state is Complete. Current state is Failed. Transition
event is Fast-FailTimer-Expired.
// The receive state machine of ring 2 in RRPP domain 1 transited from Complete to Failed because the
Fast-Fail timer expired.
# Enable debugging for fast-detection packets. The output in this example was created when the
following conditions exist:
•
A transit node is configured, which uses the default timer settings.
•
Ethernet 1/1 is configured as the primary port.
<Sysname> debugging rrpp fast-detect-packet
*0.160564 Sysname RRPP/7/RRPPPKT:
Domain 11 ring 2 Send fast-detect packet.(Length: 98, count: 1)
00 0f e2 07 83 98 00 0f e2 03 fd 75 81 00 e9 58
7f fe f0 6f 79 f0 70 00 00 48 aa aa 03 00 e0 2b
00 bb 99 0b 00 40 01 0d 00 0b 00 02 00 00 00 00
00 01 77 77 00 01 00 03 00 01 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00
// Ring 2 in domain 11 sent fast-detection packets.
# Enable debugging for RRPP state machines on the device. The output in this example was created when
a device is configured as the master node of the primary ring, with the following settings:
•
The timers adopt the default settings.
•
Ethernet 1/1 is configured as the primary port.
•
Ethernet 1/2 is configured as the secondary port.
<Sysname> debugging rrpp fsm
*0.190906 Sysname RRPP/7/RRPPFSM:
Domain 1 ring 1 Master Node FSM. Previous state is Complete. Current state is Complete.
Transition event is Hello-Timer-Expired.
// The information about the state machines of the master node of ring 1 in domain 1 was displayed.
The previous state of the state machine was Complete, and the current state of the state machine was
Complete. The state transited because the Hello timer expired.
*0.190922 Sysname RRPP/7/RRPPFSM:
Domain 1 ring 1 Master Node FSM. Previous state is Complete. Current state is Complete.
Transition event is Receiving own Health packet.
// The information about the state machines of the master node of ring 1 in domain 1 was displayed.
The previous state of the state machine was Complete, and the current state of the state machine is
Complete. The state transited because the master node received a health packet of its own.
# Enable debugging for RRPP packets on the device. The output in this example was created when a
device is configured as the master node of the primary ring, with the following settings:
•
The timers adopt the default settings.
•
Ethernet 1/1 is configured as the primary port.
•
Ethernet 1/2 is configured as the secondary port.
<Sysname> debugging rrpp packet
*0.9497594 Sysname RRPP/8/RRPPPKT:
324
Port Ethernet1/1 Send packet of domain1 ring1.(Length: 64, Type: Health)
99 0b 00 40 01 05 00 01 00 01 00 00 00 00 00 00
01 11 00 01 00 03 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
// The primary port Ethernet 1/1 sent a Health packet.
*0.9497605 Sysname RRPP/8/RRPPPKT:
Port Ethernet1/2 Rcvd packet of domain1 ring1.(Length: 64, Type: Health)
99 0b 00 40 01 05 00 01 00 01 00 00 00 00 00 00
01 11 00 01 00 03 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
// The secondary port Ethernet 1/2 received the Health packet the local node had sent.
325
RSH debugging commands
debugging rsh
Use debugging rsh to enable RSH debugging.
Use undo debugging rsh to disable RSH debugging.
Syntax
debugging rsh
undo debugging rsh
Default
RSH debugging is disabled.
Views
User view
Default command level
1: Monitor level
Examples
# Enable RSH debugging. When RSH is used to execute an OS command of a remote host, output
similar to the following example is generated:
<Sysname> debugging rsh
<Sysname> rsh 1.1.1.1 command cd c:
Trying 1.1.1.1 ...
Press CTRL+K to abort
*0.5850881 Sysname RSH/8/REQUEST:User Sysname start connection to Server (1.1.1.1)
*0.5850990 Sysname RSH/8/SEND:User Sysname sent 23 byte(s) to server (1.1.1.1)
*0.5851090 Sysname RSH/8/RECV:User Sysname received 1 byte(s) from server (1.1.1.1)
*0.5851200 Sysname RSH/8/CLOSECONN:Server (1.1.1.1) closed connection
// The device initiated an RSH connection to remote host 1.1.1.1 (the RSH server), sent 23 bytes, and
received 1 byte. The remote host closed the RSH connection.
326
Service loopback group debugging commands
The service loopback group module name is identified as "SLBG" in debugging messages.
debugging service-loopback
Use debugging service-loopback to enable service loopback group debugging.
Use undo debugging service-loopback to disable service loopback group debugging.
Syntax
debugging service-loopback { all | error | event }
undo debugging service-loopback { all | error | event }
Default
Service loopback group debugging is disabled.
Views
User view
Default command level
1: Monitor Level
Parameters
all: Specifies all types of service loopback group debugging.
error: Specifies service loopback group error debugging.
event: Specifies service loopback group event debugging.
Examples
# Enable service loopback group error debugging. When SLBG is modifying the service type on an
interface card, output similar to the following example is generated:
<Sysname> debugging service-loopback error
*Nov
3 19:29:12:860 2007 Sysname SLBG/7/SLBG_DEBUG:
EVENT.0-16338762:
The service loopback group did not exist when modifying service type on IO board.
// The service loopback group did not exist.
# Enable service loopback group event debugging. When a service loopback group is removed, output
similar to the following example is generated:
<Sysname> debugging service-loopback event
<Sysname> system-view
[Sysname] undo service-loopback group 1
*Nov
3 19:29:12:860 2007 Sysname SLBG/7/SLBG_DEBUG:
EVENT.0-16338762:
Service loopback group 1 is reporting message to another module.
// When service loopback group 1 was removed, the group reported the event to another module.
327
Session management debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging session aging-process
Use debugging session aging-process to enable debugging for session aging queue processing of
session management.
Use undo debugging session aging-process to disable debugging for session aging queue processing
of session management.
Syntax
debugging session aging-process [ acl acl-number ]
undo debugging session aging-process
Default
Debugging for session aging queue processing of session management is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
acl acl-number: Uses an ACL to match sessions for logging. The acl-number argument specifies an ACL
number in the range of 2000 to 3999. If you execute the command multiple times with different ACLs, the
most recent command takes effect.
Usage guidelines
Table 1 describes output fields and messages for the debugging session aging-process command.
328
Table 186 Output from the debugging session aging-process command
Field
Description
Protocol states:
State: PRO_STATE
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
TCP_SYN_OPEN.
TCP_ESTABLISHED.
TCP_FIN_CLOSE.
TCP_CLOSED.
UDP_OPEN.
UDP_READY.
ICMP_REQUEST.
ICMP_REPLY.
RAWIP_OPEN.
RAWIP_READY.
ICMP_ERROR_CTRL.
PRO_FTP.
PRO_DNS.
PRO_MSN.
PRO_QQ.
Session extension state:
Extent-State
•
•
•
•
•
•
•
•
•
WAITACK0.
WAITACK1.
WAITACK2.
INACTIVE.
ACCELERATE.
HALF_SESSION.
KEEP_ALIVE.
PERSIST.
DYNAMIC.
Examples
# Enable debugging for session aging queue processing on the device enabled with the security module.
When the device pings 192.168.1.58, output similar to the following example is generated:
<Sysname> debugging session aging-process
<Sysname> ping 192.168.1.58
*May 27 10:30:28:846 2009 Sysname SESSION/7/AGINGPROC:
Tuple5: 3.3.3.2/2048-->3.3.3.1/3(ICMP)
State: ICMP_REQUEST Extent-State: NULL
// Session management detected that the protocol state of the ICMP session is ICMP_REQUEST, with no
extension state.
debugging session engine
Use debugging session engine to enable debugging for session engine.
Use undo debugging session engine to disable debugging for session engine.
329
Syntax
debugging session engine { all | event | error }
undo debugging session engine { all | event | error }
Default
Debugging for session engine is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for session engine.
event: Specifies debugging for session engine events.
error: Specifies debugging for session engine errors.
Usage guidelines
Table 2 describes output fields and messages for the debugging session engine event command.
Table 187 Output from the debugging session engine event command
Field
Description
msg: Message name.
Received msg message from SESSION
•
•
•
•
SESSION_END_NOTIFY.
SESSION_DELETE_NOTIFY.
SESSION_ADD_RELATION_NOTIFY.
SESSION_DEL_RELATION_NOTIFY.
The session engine received a message from the session
management module, and notified the driver to perform the
processing action specified by event:
Succeeded in notifying DRIVER to process
the event: event
DRIVER refused to process the event from
SESSION: event
•
•
•
•
•
A session was created.
A session was deleted.
A session was updated.
A relation-table was created.
A relation-table was deleted.
The session engine received a message about the refuse event
from the driver.
event: Event that the driver refused to process.
The session engine did not send the message to the driver.
msg: Message name.
msg message not sent to DRIVER
• SESSION_END_NOTIFY.
• SESSION_DELETE_NOTIFY.
• SESSION_ADD_RELATION_NOTIFY.
330
Field
Description
Msg: Message name.
Received message from DRIVER: msg
• CREAT_SESSION.
• UPDATE_SESSION.
• DELETE_SESSION.
process: Processing action.
Succeeded in process according to DRIVER
message
• creating a session.
• updating a session.
• deleting a session.
Pro
Session protocol.
ID
Session ID.
VPN Index
VPN index in the HASH entry.
HASH entry:
Init IP/Port --> resp IP/Port VpnIndex
Initiator IP/port -> Responder IP/port VPN index.
Inverse HASH entry.
Init IP/Port <-- resp IP/Port VpnIndex
Initiator IP/port <- Responder IP/port VPN index.
Table 3 describes output fields and messages for the debugging session engine error command.
Table 188 Output from the debugging session engine error command
Field
Description
The driver failed to process the message sent by the session
engine, and the driver notified the session engine of the event.
event: Message name.
DRIVER failed to process the event: event
•
•
•
•
•
A session was created.
A session was deleted.
A session was updated.
A relation-table was created.
A relation-table was deleted.
process: Processing action.
Failed to process according to DRIVER
message
• creating a session.
• updating a session.
• deleting a session.
Examples
# Enable debugging for session engine on a firewall device. When the device sends out a UDP packet,
output similar to the following example is generated:
<Sysname> debugging session engine event
<Sysname> terminal debugging
*Apr 26 14:41:36:516 2007 Sysname SESS_DP/7/ENGINE:
EVENT:Received SESSION_END_NOTIFY message from SESSION.
Pro:UDP
ID:57
Initiator:
IP/ Port
1.1.1.2/
100
Responder:
-->
IP/ Port
2.2.2.2/
331
100
VPN Index
0
1.1.1.2/
100
<--
2.2.2.2/
100
0
// The session engine received a SESSION_END_NOTIFY message sent by the session management
module.
*Apr 26 14:41:36:517 2007 Sysname SESS_DP/7/ENGINE:
EVENT: Succeeded in notifying DRIVER to process the event: A session was created.
Pro:UDP
ID:57
Initiator:
IP/ Port
Responder:
IP/ Port
VPN Index
1.1.1.2/
100
-->
2.2.2.2/
100
0
1.1.1.2/
100
<--
2.2.2.2/
100
0
// The session engine received a message from the driver. The driver created a session successfully.
# Enable debugging for session engine on a firewall device. When the device sends out a TCP packet,
output similar to the following example is generated:
<Sysname> debugging session engine error
<Sysname> terminal debugging
*Apr 26 14:41:36:516 2007 Sysname SESS_DP/7/ENGINE:
EVENT:Received SESSION_END_NOTIFY message from SESSION.
Pro:TCP
ID:60
Initiator:
IP/ Port
Responder:
IP/ Port
VPN Index
1.1.1.2/
100
-->
2.2.2.2/
100
0
1.1.1.2/
100
<--
2.2.2.2/
100
0
// The session engine received a SESSION_END_NOTIFY message sent by the session management
module.
*Apr 26 14:41:36:517 2007 Sysname SESS_DP/7/ENGINE:
EVENT: DRIVER failed to process the event: A session was created.
Pro:TCP
ID:60
Initiator:
IP/ Port
Responder:
IP/ Port
VPN Index
1.1.1.2/
100
-->
2.2.2.2/
100
0
1.1.1.2/
100
<--
2.2.2.2/
100
0
// The session engine received a message from the driver. The driver failed to create a session.
debugging session ext-info
Use debugging session ext-info to enable debugging for extended information of session management.
Use undo debugging session ext-info to disable debugging for extended information of session
management.
Syntax
debugging session ext-info { all | event | error } [ acl acl-number ]
undo debugging session ext-info { all | event | error }
Default
Debugging for extended information of session management is disabled.
Views
User view
332
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for extended information.
event: Specifies debugging for events of extended information.
error: Specifies debugging for errors of extended information.
acl acl-number: Uses an ACL to match sessions for logging. The acl-number argument specifies an ACL
number in the range of 2000 to 3999. If you execute the command multiple times with different ACLs, the
most recent command takes effect.
Usage guidelines
Table 4 describes output fields and messages for the debugging session ext-info event command.
Table 189 Output from the debugging session ext-info event command
Field
Description
Attach, Detach, GetAttach
Extended information operation type: Attach, Detach, or
GetAttach.
succeed
Extension information operation is done successfully.
Service modules:
Module module
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
NAT.
ASPF.
ALG.
STAT (attack prevention)
TCPPROXY.
ENGINE (session engine)
P2P.
LB.
FLOW_REDIRECT.
FLT6.
NATPT.
CONNLMT.
PBR (policy routing)
DDOS.
SRVASST (Server Assistant)
SESSIONLOG.
Examples
# Enable debugging for extended information on the device with the security module enabled. The
output in this example was created when the following conditions exist:
•
The NAT server function is configured.
•
An ICMP packet that can be translated by the NAT server is sent.
<Sysname> debugging session ext-info all
*Mar 24 18:15:47:164 2007 Sysname DPSESSIO/7/EXTINFO:
Attach
succeed
Module NAT
333
Tuple5: 192.168.0.92/8-->192.168.1.58/3840(ICMP)
// The service module NAT added extended information to the session successfully.
debugging session packet-process
Use debugging session packet-process to enable debugging for packet processing of session
management.
Use undo debugging session packet-process to disable debugging for packet processing of session
management.
Syntax
debugging session packet-process
undo debugging session packet-process
Default
Debugging for packet processing of session management is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
packet-process: Specifies debugging for packet processing.
Examples
# Enable debugging for packet processing on the device with the security module enabled. Output
similar to the following example is generated when a checksum error packet is sent to the device under
the condition that the device is enabled with checksum verification.
<Sysname> debugging session packet-process
<Sysname> system-view
[Sysname] session checksum all
*Mar 26 08:50:24:568 2007 Sysname DPSESSIO/7/PKTPROC:
Tuple3: 192.168.1.58-->192.168.1.11(TCP)
Received: checksum error packet
// The packet process received a checksum error TCP packet.
*Mar 26 08:57:24:896 2007 Sysname DPSESSIO/7/PKTPROC:
Tuple3: 192.168.0.21-->192.168.1.89(TCP)
ERROR: unknown ICMP error control packet
// The packet process received a TCP ICMP error control packet.
debugging session relation
Use debugging session relation to enable debugging for session relation table of session management.
Use undo debugging session relation to disable debugging for session relation table of session
management.
334
Syntax
debugging session relation { all | event | error }
undo debugging session relation { all | event | error }
Default
Debugging for session relation table of session management is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for session relation table.
event: Specifies debugging for session relation table events.
error: Specifies debugging for session relation table errors.
Usage guidelines
Table 5 describes output fields and messages for the debugging session relation event command.
Table 190 Output from the debugging session relation event command
Field
Description
LocalTuple3: localIP / localPort
Internal network 3-tuple of relation table.
GlobalTuple3: globalIP/globalPort(ProtoType)
External network 3-tuple of relation table.
Create, Delete ,Update
Relation table events.
module call, time out, child full, module call / child full
Event causes.
Table 6 describes output fields and messages for the debugging session relation error command.
Table 191 Output from the debugging session relation error command
Field
Description
Error:
Relation table error.
Memory not enough for relation
Insufficient memory for creating a relation entry.
Relation number exceed max
The number of relation table entries exceeds the upper
limit.
Examples
# Enable debugging for session relation table on the device with the security module enabled. When the
ALG module added a relation table entry, output similar to the following example is generated:
<Sysname> debugging session relation all
*Mar 26 09:12:33:800 2007 Sysname DPSESSIO/7/RELATION:
LocalTuple3: 192.168.1.8/4780 : GlobalTuple3:192.168.1.8/4780 (TCP)
Create
module call
// Session management created a relation entry after receiving a creation command from an external
module.
335
*Mar 26 09:17:54:112 2007 Sysname DPSESSIO/7/RELATION:
LocalTuple3: 192.168.1.8/4780 : GlobalTuple3: 192.168.1.8/4780 (TCP)
Delete
time out
// Session management deleted the relation entry due to timeout.
*Mar 24 18:22:13:476 2007 Sysname DPSESSIO/7/RELATION:
Error: Memory not enough for relation
// Session management failed to create a relation entry due to insufficient resources.
debugging session session-table
Use debugging session session-table to enable debugging for session table entries of session
management.
Use undo debugging session session-table to disable debugging for session table entries of session
management.
Syntax
debugging session session-table { all | event | error | fsm } [ acl acl-number ]
undo debugging session session-table { all | event | error | fsm }
Default
Debugging for session table entries is disabled.
Views
User view
Default command level
2: System level
Parameters
all: Specifies all types of debugging for session table.
event: Specifies debugging for session table events.
error: Specifies debugging for session table errors.
fsm: Specifies debugging for session table state machine.
acl acl-number: Uses an ACL to match sessions for logging. The acl-number argument specifies an ACL
number in the range of 2000 to 3999. If you execute the command multiple times with different ACLs, the
most recent command takes effect.
Usage guidelines
Table 7 describes output fields and messages for the debugging session session-table fsm command.
Table 192 Output from the debugging session session-table fsm command
Field
Description
Tuple5(FSM):
Session 5-tuple.
FSM:preState-->nextState,
State machine changes from one state to another
state.
received: ProtoType
Transport layer protocol type of the received packet.
336
Examples
# Enable debugging for session table entries on the device with security module enabled. When a ping
packet passes through the device, output similar to the following example is generated:
<Sysname> debugging session session-table all
*Mar 24 18:15:47:164 2007 Sysname DPSESSIO/7/TABLE:
Tuple5(EVENT): 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Operation:Create
// Session management created an ICMP session entry.
*Mar 24 18:15:47:174 2007 Sysname DPSESSIO/7/TABLE:
Tuple5(FSM): 192.168.0.2/8-->192.168.1.58/3840(ICMP)
FSM:NONE
--> READY ,received:ICMP
// Session management changed the session state from NONE to READY because of the receipt of
ICMP packet.
*Mar 24 18:22:13:476 2007 Sysname DPSESSIO/7/TABLE:
Tuple5(EVENT): 192.168.0.2/8-->192.168.1.58/4096(ICMP)
Operation:Delete
// Session management deleted the session entry with source IP address 192.168.0.2 and destination IP
address 192.168.1.58.
# Enable debugging for session table entries on the device with security module enabled. When the
resources for session table are insufficient, output similar to the following example is generated:
*Mar 24 18:22:13:476 2007 Sysname DPSESSIO/7/TABLE:
Error: Memory not enough for session
// Session management failed to apply for session table resources due to insufficient memory.
debugging session log proc
Use debugging session log proc to enable debugging for session log processing.
Use undo debugging session log proc to disable debugging for session log processing.
Syntax
debugging session log proc { all | error | event }
undo debugging session log proc { all | error | event }
Default
Debugging for session log processing is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for session log processing.
error: Specifies for session log processing errors.
event: Specifies for session log processing events.
337
Examples
# Enable debugging for session log processing events on the device that supports session management.
<Sysname> debugging session log proc event
# Configure session logging output thresholds.
<Sysname> system-view
[Sysname] session log time-active 10
[Sysname] session log packets-active 1
# Enable the session logging function.
[Sysname] interface gigabitethernet 1/1
[Sysname-GigabitEthernet1/1] session log enable inbound
# Ping the device from 192.168.0.2. If the ping operation succeeds, output similar to the following
messages is generated:
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/logprocess:
Tuple5: 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Event: Logged a session creation event.
// Session management created an ICMP session. The system logged the session creation event.
# Remove the ICMP session. When the ICMP session is removed successfully, output similar to the
following messages is generated:
<Sysname> reset session source-ip 192.168.0.2
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/logprocess:
Tuple5: 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Event: Logged a session deleted event,type is AGING.
// Session management deleted the target ICMP session entry. The system logged the session deletion
event, and the log type is AGING.
Output similar to the following messages is generated when the ICMP session lasts 10 minutes under the
condition that the device is pinged continuously:
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/logprocess:
Tuple5: 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Event: Logged a session hold time threshold reached event.
// The system output a log about the event that the session reached the session hold time threshold.
Output similar to the following messages is generated when the number of ICMP session packets reaches
1M under the condition that the device is pinged continuously:
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/logprocess:
Tuple5: 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Event: Logged a session traffic threshold reached event.
// The system output a log about the event that the session reached the traffic threshold.
# Enable debugging for session log processing errors. The output in this example was created when the
following conditions exist:
•
The session logging function is enabled.
•
Thresholds for outputting session logs are configured.
<Sysname> debugging session log proc error
*Dec 16 15:52:55:677 2007 Sysname Sysname/7/LOG_PROCESS:Slot=1;
Tuple5(EVENT): 192.168.119.119/8-->2.2.2.2/1280(ICMP)
Error: Failed to log a session created event.
338
debugging session log active-flow
Use debugging session log active-flow to enable debugging for active flow.
Use undo debugging session log active-flow to disable debugging for active flow.
Syntax
debugging session log active-flow { all | event | error }
undo debugging session log active-flow { all | event | error }
Default
Debugging for active flow is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Specifies all types of debugging for active flow.
event: Specifies debugging for active flow operation events.
error: Specifies debugging for active flow operation errors.
Examples
# Enable debugging for active flow logging events on the device that supports session management.
<Sysname> debugging session log active-flow event
# Configure session logging output thresholds.
<Sysname> system-view
[Sysname] session log time-active 10
# Enable the session logging function.
[Sysname] interface gigabitethernet 1/1
[Sysname-GigabitEthernet1/1] session log enable inbound
When a data flow passes through the device, output similar to the following example is generated:
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/active-flow:
Event: Active-flow queue created.
// Session management created an active-flow queue.
# Disable the session logging function.
[Sysname-GigabitEthernet0/1] undo session log enable
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/active-flow:
Event: Active-flow queue deleted.
// Session management deleted the active-flow queue.
# Ping the device from the host at 192.168.0.2. If the ping operation succeeds, output similar to the
following messages is generated:
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/active-flow:
Tuple5: 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Event: Session appended to the active-flow queue.
339
// Session management added the created ICMP session to the active-flow queue.
# Delete the created ICMP session. When the created ICMP session is deleted successfully, output similar
to the following messages is generated:
<Sysname> reset session source-ip 192.168.0.2
*Mar 26 08:50:24:568 2007 Sysname DPSESS/7/active-flow:
Tuple5: 192.168.0.2/8-->192.168.1.58/3840(ICMP)
Event: Session removed from the active-flow queue.
// Session management deleted the ICMP session from the active-flow queue.
# Enable debugging for active flow logging errors on a device that supports session management. The
output in this example was created when the following conditions exist:
•
The session logging function is enabled.
•
Thresholds for outputting session logs are configured.
<Sysname> debugging session log active-flow error
*Dec 16 15:55:35:377 2007 Sysname SESSION/7/LOG_ACTFLOW:Slot=2;
Error: Failed to create the active-flow queue.
340
SIP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging voice sip
Use debugging voice sip to enable SIP debugging.
Use undo debugging voice sip to disable SIP debugging.
Syntax
debugging voice sip { all | error | event | message | stack | timer }
undo debugging voice sip { all | error | event | message | stack | timer }
Default
SIP debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
all: Specifies all types of SIP debugging.
error: Specifies error debugging.
event: Specifies event debugging.
message: Specifies message debugging.
stack: Specifies protocol stack debugging.
timer: Specifies timer debugging.
Usage guidelines
Table 1 describes output fields and messages for the debugging voice sip error command.
Table 193 Output from the debugging voice sip error command
Field
Description
Filling ACCP head failed
SIP failed to fill ACCP header.
Failed to Malloc Memory for XXX
SIP failed to allocate memory to XXX.
Get Local Address From Uri Failed
SIP failed to obtain the local address from URI.
The UserInfo Number is not exist
The UserInfo Number did not exist.
Send accp service ack msg failed
SIP failed to send an ACCP service Ack.
Stack --> Adapter : Refer Response
Adapter module received a REFER response from the
protocol stack.
341
Field
Description
Send Prack Request Failed
SIP failed to send a Prack request.
Send AccpAlerting message Failed
SIP failed to send an AccpAlerting message.
Send AccpConnect Failed
SIP failed to send an AccpConnect message.
Send SipConnectAck Failed
SIP failed to send a SipConnectAck message.
Find XXX error
SIP failed to get the XXX field.
Create AppRspMsg error
SIP failed to create an AppRspMsg message.
Cannot find the exist SIP CCB
The existing SIP CCB was not found.
SIP receive setup callinfotab error
SIP received a Setup message with an invalid call info
table.
The CMC state of ccb is error
CMC state error in SIP CCB.
SIP Find codec failed
SIP failed to find the codec type.
Create MediaChannel Failed
SIP failed to create a media channel.
VIM Attach IppId(= %d) to Line(= %d) Failed
SIP failed to attach CCB of the IPP module to VIM.
VIM Detach IppId from Line(= %d) Failed
SIP failed to detach CCB of the IPP module from VIM.
Transfer User Number is empty
The transfer destination number was empty.
SIP TPTD module register high call back function failed
TPTD module failed to register a callback function with
the higher layer.
Receive Network error packet
SIP received an error packet from the network side.
Receive Network too long packet
SIP received too long a packet from the network side.
Send udp Msg failed
SIP failed to send a UDP message.
Fail to create signal transport
SIP failed to create a signaling channel.
The contact header isn't exist
The Contact header didn't exist.
The number of contact item is invalid
The number of Contact headers was invalid.
Malloc for Require Failed
SIP failed to allocate memory to Require.
Encode SipFrag Failed
SIP failed to encode SipFrag.
Change Media Ip Addr Failed
SIP failed to change the IP address of the media
channel.
Replaces Parameter is not exist in SIP CCB
The Replaces parameter didn't exist in SIP CCB.
Analyze the destination of INVITE request: The SIP
CCB has been existed.
Analyzing the destination of INVITE request: The SIP
CCB existed.
Analyze the destination of INVITE request: SIP receive
setup callinfotab error.
Analyzing the destination of INVITE request: SIP
received a wrong callinfotab.
The number of contact item is invalid.
The number of Contact headers was invalid.
Call-hold service: Unsupport type.
Unsupported call-hold service type.
Copy address: Unsupport type!
Copy address: Unsupported type.
Failed to process 3XX contact header for rcb %u
because the number of the contact header is negative.
SIP failed to process 3XX contact header for rcb %u
because the number of Contact headers was negative.
342
Field
Description
Failed to get authentication because failed to
calculation response code.
SIP failed to obtain authentication information
because it failed to calculate response code.
Failed to calculate authentication because the number
of authentication header is negative.
SIP failed to calculate authentication information
because the number of authentication headers was
negative.
Build Options: Failed add To IE to Msg.
Build Options: SIP failed to add To IE to Msg.
Build Options: Failed add contact IE to msg.
Build Options: SIP failed to add contact IE to msg.
Delete server group: Failed to delete server %u, for it's
referenced.
Delete server group: SIP failed to delete server %u
because it was referenced.
Failed to create the send options timer.
SIP failed to create the timer for sending OPTIONS
messages.
Failed to create the highest priority server's auxiliary
timer.
SIP failed to create the auxiliary timer for the highest
priority server.
OPTIONS Message Response: Message response is
not with the right sequence.
OPTIONS Message Response: Message response
had a wrong sequence number.
OPTIONS Message Response: Message response is
not corressponding to the server using.
OPTIONS Message Response: Message response did
not match the server in use.
Options DNS proc: DNS query failed.
Options DNS processing: DNS query failed.
Table 2 describes output fields and messages for the debugging voice sip event command.
Table 194 Output from the debugging voice sip event command
Field
Description
SIP --> CMC : Accp Setup
SIP sent an ACCP Setup message to CMC.
SIP --> CMC : XXX
SIP sent a XXX message to CMC.
Stack --> Adapter : DIM Response
Adapter layer received a response from the DIM
module of the protocol stack.
Stack --> Adapter : DIM Request
Adapter layer received a request from the DIM
module of the protocol stack.
Stack --> Adapter : Ssn Response
Adapter layer received a response from the SSN
module of the protocol stack.
Stack --> Adapter : Ssn Request
Adapter layer received a request from the SSN
module of the protocol stack.
Stack --> Adapter : Subscription Response
Adapter layer received a response from the
Subscription module of the protocol stack.
Stack --> Adapter : Invite Request
Adapter layer received an Invite request from the
protocol stack.
Stack --> Adapter : Refer Request
Adapter layer received a Refer request from the
protocol stack.
Stack --> Adapter : Alerting Indication
Adapter layer received an Alerting response from the
protocol stack.
Stack --> Adapter : Prack Request
Adapter layer received a Prack request from the
protocol stack.
343
Field
Description
Find Codec in Prack Request Failed
SIP failed to get the codec in the Prack request.
Stack --> Adapter : Prack Response
Adapter layer received a response to the Prack
request from the protocol stack.
Stack --> Adapter : Update Request
Adapter layer received an Update request from the
protocol stack.
Stack --> Adapter : Update Response
Adapter layer received a response to the Update
request from the protocol stack.
Stack --> Adapter : Connect Indication
Adapter layer received a 200 OK response from the
protocol stack.
Stack --> Adapter : Connect Ack Request
Adapter layer received an ACK from the protocol
stack.
Stack --> Adapter : Re_Invite Request
Adapter layer received a Re_Invite request from the
protocol stack.
Stack --> Adapter : Re_Invite Response
Adapter layer received a response to the Re_Invite
request from the protocol stack.
Stack --> Adapter : Re_Invite Ack Request
Adapter layer received a Re_Invite Ack Request from
the protocol stack.
Stack --> Adapter : Release Indication
Adapter layer received a Release message from the
protocol stack.
Stack --> Adapter : Release Response
Adapter layer received a response to the Release
message from the protocol stack.
Stack --> Adapter : Release Complete Indication
Adapter layer received an error response to the Invite
request from the protocol stack.
Stack --> Adapter : Notify Request
Adapter layer received a Notify request from the
protocol stack.
Stack --> Adapter : Notify Response
Adapter layer received a response to the Notify
request from the protocol stack.
Stack --> Adapter : Release Complete Sub Indication
Adapter layer received error responses to the REFER
and NOTIFY requests from the protocol stack.
Stack --> Adapter : Information Request
Adapter layer received an Info request from the
protocol stack.
Stack --> Adapter : Information Response
Adapter layer received a response to the Info request
from the protocol stack.
Stack --> Adapter : Feature Response
Adapter layer received a response to the Feature
request from the protocol stack.
CMC --> SIP : Accp Setup
CMC sent an ACCP Setup message to SIP.
CMC --> SIP : XXX
CMC sent a XXX message to SIP.
SIP Delete Media Channel Success
SIP deleted a media channel successfully.
SIP ChangeCodec Media Channel Success
SIP changed the codec type for the media channel.
Configuration OutBandNte ENABLED by FEATURE
Enable Feature to enable the OutBandNte attribute.
Adapter --> Stack : Setup Ssn Request
Adapter layer sent a Setup request to the protocol
stack.
344
Field
Description
Adapter --> Stack : Alerting Request
Adapter layer sent an Alerting request to the protocol
stack.
Adapter --> Stack : Connect Request
Adapter layer sent a Connect request to the protocol
stack.
Adapter --> Stack : ConnectAck Request
Adapter layer sent a ConnectAck request to the
protocol stack.
Adapter --> Stack : Information Request
Adapter layer sent an Info request to the protocol
stack.
Adapter --> Stack : Release Response
Adapter layer sent an error response to the Setup
message to the protocol stack.
Adapter --> Stack : XX Ssn Request
Adapter layer sent a XX request to the SSN module of
the protocol stack.
Adapter --> Stack : XX Ssn Ack Request
Adapter layer sent an ACK for XX request to the SSN
module of the protocol stack.
Succeed to send Subscribe_Release Msg
SIP succeeded in sending a Subscribe_Release
message to the protocol stack.
Encode SipFrag Success
SIP succeeded in encoding SipFrag message.
Analyze the destination of INVITE request: Current
setup type(= %d) cannot be supported.
Analyze the destination of INVITE request: Current
setup type (= %d) was not supported.
Start get next SUBSCRIBE redirect server.
SIP started to obtain the next SUBSCRIBE redirect
server.
Succeed in getting next redirect IPv4 server.
SIP succeeded in obtaining the next redirect server
with an IPv4 address.
Examples
The output in the following examples was created when User A with number 1000 calls User B with
number 3000 using a out-of-band method:
# Enable debugging for SIP events on the originating device.
<Sysname> debugging voice sip event
Enable SIP EVENT message debuging functions
<Sysname>
*May 12 11:14:58:514 2007 Sysname SIP/7/VOICE:
SIP_Event: CMC --> SIP : Accp Setup.
// CMC sent an ACCP Setup message to SIP.
*May 12 11:14:58:514 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP --> CMC : Accp Setup Ack.
// SIP replied with an ACCP Setup Ack to CMC.
*May 12 11:14:58:514 2007 Sysname SIP/7/VOICE:
SIP_Event:
Get Nte From DPL : Configuration OutBandNte DISABLE.
// The OutBandNte attribute was not enabled on the local end.
*May 12 11:14:58:514 2007 Sysname SIP/7/VOICE:
SIP_Event: Adapter --> Stack : Setup Ssn Requestion .
// The SIP adapter layer sent a Setup request to the protocol stack.
345
*May 12 11:14:58:515 2007 Sysname SIP/7/VOICE:
SIP_Event: Stack --> Adapter : Setup Ack
// The protocol stack sent a Setup Ack to the SIP adapter layer.
*May 12 11:14:58:550 2007 Sysname SIP/7/VOICE:
SIP_Event: Stack --> Adapter : Alerting Indication.
// The protocol stack sent an Alerting message to the SIP adapter layer.
*May 12 11:14:58:550 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP --> CMC : Accp Alerting.
// SIP sent an ACCP Alerting message to CMC.
*May 12 11:14:58:550 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP Get PayLoad Size: Use the Payload Size[ 30 ].
// The packetization period is 30 ms.
*May 12 11:14:58:550 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP --> CMC : Accp ChannelReady.
// SIP sent an ACCP ChannelReady message to CMC.
*May 12 11:14:58:649 2007 Sysname SIP/7/VOICE:
SIP_Event: CMC --> SIP : Accp ChannelReadyAck.
// CMC sent an ACCP ChannelReadyAck message to SIP.
*May 12 11:14:58:699 2007 Sysname SIP/7/VOICE:
SIP_Event: VIM Attach IppId(= 107) to Line(= 2883680) Success.
// Ippid 107 was registered to line 2883680 successfully on VIM.
*May 12 11:14:58:849 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP Create Meida Channel:
Local Address
= 3.1.1.19 : 16598
Remote Address = 3.1.1.29 : 16560
Encode Type
= 11
// SIP set up a media channel. The IP address of the calling party is 3.1.1.19, the IP address of the called
party is 3.1.1.29, and the codec type is G.729.
*May 12 11:15:03:471 2007 Sysname SIP/7/VOICE:
SIP_Event: Stack --> Adapter : Connect Indication.
// The protocol stack sent a Connect message to the SIP adapter layer.
*May 12 11:15:03:471 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP --> CMC : Accp Connect.
// SIP sent an ACCP Connect message to CMC.
*May 12 11:15:03:471 2007 Sysname SIP/7/VOICE:
SIP_Event: Adapter --> Stack : ConnectAck Request .
// The SIP adapter layer sent a ConnectAck message to the protocol stack.
*May 12 11:15:03:472 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP Get PayLoad Size: Use the Payload Size[ 30 ].
// The packetization period is 30 ms.
*May 12 11:15:03:472 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP --> CMC : Accp Code Switch
// SIP sent an ACCP Code Switch message to CMC to change the codec type.
*May 12 11:15:03:472 2007 Sysname SIP/7/VOICE:
346
SIP_Event:
SIP ChangeCodec Media Channel: SIP ChangeCodec Media Channel Success!
// SIP changed the codec type for the media channel.
*May 12 11:15:03:473 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP Delete Media Channel: SIP Delete Media Channel Success!
// SIP deleted a media channel.
*May 12 11:15:03:473 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP Create Meida Channel:
Local Address
= 3.1.1.19 : 16598
Remote Address = 3.1.1.29 : 16560
Encode Type
= 11
// SIP set up a media channel. The IP address of the calling party is 3.1.1.19, the IP address of the called
party is 3.1.1.29, and the codec type is G.729.
*May 12 11:15:03:473 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP --> CMC : Accp Information.
Enable Outband Sip
// SIP sent an ACCP Information message to CMC to indicate that DTMF detection had been enabled.
*May 12 11:15:25:19 2007 Sysname SIP/7/VOICE:
SIP_Event: CMC --> SIP : Accp Release.
// The calling party hung up, and CMC sent an ACCP Release message.
*May 12 11:15:25:20 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP Delete Media Channel: SIP Delete Media Channel Success!
*May 12 11:15:25:20 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP --> CMC : Accp Information.
Disable Outband Sip
// SIP sent an ACCP Information message to CMC to indicate that DTMF detection had been disabled.
*May 12 11:15:25:20 2007 Sysname SIP/7/VOICE:
SIP_Event:
SIP Delete Media Channel: SIP Delete Media Channel Success!
// SIP deleted a media channel.
*May 12 11:15:25:20 2007 Sysname SIP/7/VOICE:
SIP_Event:
Adapter --> Stack : Bye Ssn Request
// The SIP adapter layer sent a BYE request to the protocol stack, and the originating device went
on-hook.
*May 12 11:15:25:20 2007 Sysname SIP/7/VOICE:
SIP_Event: SIP --> CMC : Accp ReleaseComp.
// SIP sent an ACCP ReleaseComp message to CMC as a confirmation to the ACCP Release.
*May 12 11:15:25:21 2007 Sysname SIP/7/VOICE:
SIP_Event: Send Sip Subscribe_Release to SIP-STACK: Failed to send Subscribe_Release Msg.
// SIP failed to send a Subscribe_Release message.
*May 12 11:15:25:23 2007 Sysname SIP/7/VOICE:
SIP_Event: Stack --> Adapter : Release Response.
// The SIP protocol stack sent a response to the BYE request to the adapter layer.
# Enable debugging for SIP messages on the originating device.
<Sysname> debugging voice sip message
Enable SIP message debugging functions
347
<Sysname>
*May 12 11:31:51:284 2007 Sysname SIP/7/VOICE:
Stack--->NetWork:
INVITE sip:3000@3.1.1.29:5060 SIP/2.0
Via: SIP/2.0/UDP 3.1.1.19:5060;branch=z9hG4bK9558081c4a9
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>
CSeq: 1 INVITE
Contact: <sip:1000@3.1.1.19:5060>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 12 May 2007 11:31:51 GMT
Supported: 100rel
Max-Forwards: 70
Content-Length: 230
Content-Type: application/sdp
v=0
o=H3C 1073742116 1073742116 IN IP4 3.1.1.19
s=Sip Call
c=IN IP4 3.1.1.19
t=0 0
m=audio 16602 RTP/AVP 18 8 0 4
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:4 G723/8000
// The originating device sent an INVITE request to the terminating device.
*May 12 11:31:51:286 2007 Sysname SIP/7/VOICE:
NetWork--->Stack:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 3.1.1.19:5060;branch=z9hG4bK9558081c4a9
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>
CSeq: 1 INVITE
Content-Length: 0
// The originating device received a 100 (Trying) response from the terminating device.
*May 12 11:31:51:320 2007 Sysname SIP/7/VOICE:
NetWork--->Stack:
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 3.1.1.19:5060;branch=z9hG4bK9558081c4a9
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>;tag=09804351
CSeq: 1 INVITE
Contact: <sip:3000@3.1.1.29:5060>
348
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 12 May 2007 11:30:14 GMT
Content-Length: 158
Content-Type: application/sdp
v=0
o=H3C 1073742102 1073742102 IN IP4 3.1.1.29
s=Sip Call
c=IN IP4 3.1.1.29
t=0 0
m=audio 16564 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
// The originating device received a 183 (Session Progress) response from the terminating device.
*May 12 11:31:54:801 2007 Sysname SIP/7/VOICE:
NetWork--->Stack:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 3.1.1.19:5060;branch=z9hG4bK9558081c4a9
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>;tag=09804351
CSeq: 1 INVITE
Contact: <sip:3000@3.1.1.29:5060>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 12 May 2007 11:30:17 GMT
Content-Length: 158
Content-Type: application/sdp
v=0
o=H3C 1073742104 1073742104 IN IP4 3.1.1.29
s=Sip Call
c=IN IP4 3.1.1.29
t=0 0
m=audio 16564 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
// The terminating device went off-hook, and the originating device received a 200 (OK) response from
the terminating device.
*May 12 11:31:54:801 2007 Sysname SIP/7/VOICE:
Stack--->NetWork:
ACK sip:3000@3.1.1.29:5060 SIP/2.0
Via: SIP/2.0/UDP 3.1.1.29:5060;branch=z9hG4bK4ce35b0fac2
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>;tag=09804351
CSeq: 1 ACK
Date: Sat, 12 May 2007 11:31:54 GMT
Max-Forwards: 70
349
Content-Length: 0
// The originating device sent an ACK to confirm the reception of the 200 response.
*May 12 11:33:04:949 2007 Sysname SIP/7/VOICE:
Stack--->NetWork:
BYE sip:3000@3.1.1.29:5060 SIP/2.0
Via: SIP/2.0/UDP 3.1.1.19:5060;branch=z9hG4bKd66d95e966e
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>;tag=09804351
CSeq: 2 BYE
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 12 May 2007 11:33:04 GMT
Max-Forwards: 70
Content-Length: 0
// The originating device went off-hook and sent a BYE request to the terminating device.
*May 12 11:33:04:952 2007 Sysname SIP/7/VOICE:
NetWork--->Stack:
SIP/2.0 200 OK
Via: SIP/2.0/UDP 3.1.1.19:5060;branch=z9hG4bKd66d95e966e
Call-ID: 178990f081c919d4752cd8e19558081c109@3.1.1.19
From: <sip:1000@3.1.1.19:5060>;tag=9558081c
To: <sip:3000@3.1.1.29:5060>;tag=09804351
CSeq: 2 BYE
Content-Length: 0
// The originating device received a 200 response from the terminating device as a response to the BYE
request.
# Enable debugging for SIP timers on the originating device.
<Sysname>debug voice sip timer
Enable SIP timer debugging functions
<Sysname>
*May 12 18:12:53:820 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 11 ulIndex = 158
ulDuration = 30000
// SIP started a timer (ulTimerGroup = 11 ulIndex = 158), with the value set to 30 seconds.
*May 12 18:12:53:820 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 3 ulIndex = 144
ulDuration = 500
*May 12 18:12:53:821 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 4 ulIndex = 144
ulDuration = 32000
*May 12 18:12:53:821 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:12:53:821 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 11 ulIndex = 158
// SIP stopped the timer (ulTimerGroup = 11 ulIndex = 158).
*May 12 18:12:53:823 2007 Sysname SIP/7/VOICE:
350
ulDuration = 600000
SIP_Timer: Stop Timer ulTimerGroup = 4 ulIndex = 144
*May 12 18:12:53:824 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 3 ulIndex = 144
*May 12 18:12:53:824 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 4 ulIndex = 144
ulDuration = 64000
*May 12 18:12:53:858 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 4 ulIndex = 144
*May 12 18:12:53:954 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 4 ulIndex = 144
ulDuration = 256000
*May 12 18:12:54:104 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 12 ulIndex = 13
ulDuration = 120000
*May 12 18:12:54:204 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:12:54:354 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 16 ulIndex = 13
ulDuration = 600000
*May 12 18:12:54:454 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 22 ulIndex = 13
ulDuration = 5000
*May 12 18:12:58:957 2007 Sysname SIP/7/VOICE:
SIP_Timer: Timer out ulTimerGroup = 22 ulIndex = 13
// The timer (ulTimerGroup = 22 ulIndex = 13) timed out.
*May 12 18:13:00:640 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 12 ulIndex = 13
*May 12 18:13:00:641 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 12 ulIndex = 13
ulDuration = 64000
*May 12 18:13:00:641 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:13:00:641 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 16 ulIndex = 13
ulDuration = 600000
*May 12 18:13:00:642 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 11 ulIndex = 159
*May 12 18:13:00:642 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 12 ulIndex = 13
*May 12 18:13:00:642 2007 Sysname SIP/7/VOICE:
351
ulDuration = 30000
SIP_Timer: Stop Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:13:00:643 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 16 ulIndex = 13
ulDuration = 1800000
*May 12 18:13:00:643 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 22 ulIndex = 13
*May 12 18:13:00:786 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 22 ulIndex = 13
ulDuration = 5000
*May 12 18:13:00:896 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 4 ulIndex = 144
*May 12 18:13:00:996 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 11 ulIndex = 159
*May 12 18:13:01:146 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 12 ulIndex = 13
ulDuration = 32000
*May 12 18:13:05:659 2007 Sysname SIP/7/VOICE:
SIP_Timer: Timer out ulTimerGroup = 22 ulIndex = 13
*May 12 18:13:06:490 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 22 ulIndex = 13
*May 12 18:13:06:491 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 11 ulIndex = 160
ulDuration = 30000
*May 12 18:13:06:491 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 3 ulIndex = 145
ulDuration = 500
*May 12 18:13:06:491 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 4 ulIndex = 145
ulDuration = 32000
*May 12 18:13:06:492 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 12 ulIndex = 13
*May 12 18:13:06:492 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:13:06:492 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:13:06:493 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 11 ulIndex = 160
*May 12 18:13:06:495 2007 Sysname SIP/7/VOICE:
352
ulDuration = 600000
SIP_Timer: Stop Timer ulTimerGroup = 4 ulIndex = 145
*May 12 18:13:06:638 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 3 ulIndex = 145
*May 12 18:13:06:738 2007 Sysname SIP/7/VOICE:
SIP_Timer: Stop Timer ulTimerGroup = 16 ulIndex = 13
*May 12 18:13:06:888 2007 Sysname SIP/7/VOICE:
SIP_Timer: Start Timer ulTimerGroup = 3 ulIndex = 145
ulDuration = 5000
*May 12 18:13:11:562 2007 Sysname SIP/7/VOICE:
SIP_Timer: Timer out ulTimerGroup = 3 ulIndex = 145
debugging voice ssm call
Use debugging voice ssm call to enable debugging for SIP server basic call functions.
Use undo debugging voice ssm call to disable debugging for SIP server basic call functions.
Syntax
debugging voice ssm call { all | error | event | fsm | info | prim | timer }
undo debugging voice ssm call { all | error | event | fsm | info | prim | timer }
Default
Debugging for SIP server basic call functions is disabled.
Views
User view
Default command level
2: System level
Parameters
call: Enables debugging for SIP server basic call functions.
all: Specifies all types of debugging.
error: Specifies error debugging.
event: Specifies event debugging.
fsm: Specifies finite state machine debugging.
info: Specifies information debugging.
prim: Specifies primitive debugging.
timer: Specifies timer debugging.
Examples
The output in the following examples was created when User A with number 2002 as the calling party
establishes a call with User B with number 200:
# Enable all types of debugging for SIP server basic call functions.
<Sysname> debugging voice ssm call all
353
Enable SSM CALL ALL debugging functions
<Sysname>
*Sep
7 16:38:37:637 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in getting a free element from the list.
Additional: Call control block ID is 42.
// The SSA module got a free element from the list as the control block (ID: 42) for the current call.
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Received message from the stack.
Additional: The message type is SetupInd.
Call control block ID is 42.
Caller number is 2002.
Called number is 200.
// The SSA module received a SetupInd message from the network side.
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Send UCM Setup request message.
// The SSA module sent a UCM_SETUPREQ message to the SLC module.
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Receive UCM Setup request message.
// The SLC module received the UCM_SETUPREQ message.
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: Succeed in getting a free element from the list.
Additional: Conference control block ID is 15.
// The SLC module got a free element from the list as the conference control block (ID: 15).
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCTRL: Received event CALLESTABLISH while at state INIT.(ObjectID = 15)
// The state machine CALLCTRL received a CALLESTABLISH event in the INIT state.
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: The authentication is needed.
// Authentication is needed for this call.
*Sep
7 16:38:37:638 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Setup reject message.
// The SLC module sent a UCM_SETUPREJ message to the SSA module.
*Sep
7 16:38:37:639 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 4, Group = 4, Index = 15, Length = 8000
// The SLC module started a timer, with the value set to 8000 ms.
*Sep
7 16:38:37:840 2007 Sysname SSM/7/VOICE:
354
SSM_FSM [CALL_SLC]:
CALLCTRL: State changed from INIT to CALLINPROGRESS.(ObjectID = 15)
// The state machine CALLCTRL transitioned from INIT to CALLINPROGRESS.
*Sep
7 16:38:38:102 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Receive UCM Setup reject message.
// The SSA module received the UCM_SETUPREJ message.
*Sep
7 16:38:38:253 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in sending the network message.
Additional: Method type is INVITE, status code is 407.
// The SSA module sent a 407 response to the network side for the INVITE method.
*Sep
7 16:38:38:354 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in freeing element to the list.
Additional: Call control block ID is 42.
// The SSA module released the current call control block (ID: 42).
*Sep
7 16:38:38:556 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in getting a free element from the list.
Additional: Call control block ID is 43.
// The SSA module got a free element from the list as the control block (ID: 43) for the current call.
*Sep
7 16:38:38:707 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Received message from the stack.
Additional: The message type is SetupInd.
Call control block ID is 43.
Caller number is 2002.
Called number is 200.
// The SSA module received a SetupInd message from the network side.
*Sep
7 16:38:38:858 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Send UCM Setup request message.
// The SSA module sent a UCM_SETUPREQ message to the SLC module.
*Sep
7 16:38:38:959 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Receive UCM Setup request message.
// The SLC module received the UCM_SETUPREQ message.
*Sep
7 16:38:39:110 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCTRL: Received event CALLESTABLISH while at state CALLINPROGRESS.(ObjectID = 15)
// The state machine CALLCTRL received a CALLESTABLISH event in the CALLINPROGRESS state.
*Sep
7 16:38:39:261 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 4, Group = 4, Index = 15, Length = 8000
355
// The SLC module stopped an 8000-ms timer.
*Sep
7 16:38:39:362 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: Succeed in getting a free element from the list.
Additional: Call control block ID is 22.
// The SSA module got a free element from the list as the call control block (ID: 22).
*Sep
7 16:38:39:573 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLSRV: Received event UCMSETUPREQ while at state IDLE.(ObjectID = 22)
// The state machine CALLSRV received a UCMSETUPREQ event in the IDLE state.
*Sep
7 16:38:39:775 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Setup ACK message.
// The SLC module sent a UCM_SETUPACK message to the SSA module.
*Sep
7 16:38:39:926 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 6, Group = 6, Index = 22, Length = 16000
// The SLC module started a timer, with the value set to 16000 ms.
*Sep
7 16:38:40:228 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLSRV: State changed from IDLE to SETUP.(ObjectID = 22)
// The state machine CALLSRV transitioned from IDLE to SETUP.
*Sep
7 16:38:40:329 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: Succeed in getting a free element from the list.
Additional: Call control block ID is 23.
// The SLC module got a free element from the list as the call control block (ID: 23).
*Sep
7 16:38:40:430 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCLT: Received event CCSETUPREQ while at state IDLE.(ObjectID = 23)
// The state machine CALLCLT received a CCSETUPREQ event in the IDLE state.
*Sep
7 16:38:40:631 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Setup request message.
// The SLC module sent a UCM_SETUPREQ message to the SSA module.
*Sep
7 16:38:40:782 2007 Sysname SSM/7/VOICE:
356
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 6, Group = 6, Index = 23, Length = 16000
// The SLC module started a timer, with the value set to 16000 ms.
*Sep
7 16:38:40:934 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLCLT: State changed from IDLE to SETUP.(ObjectID = 23)
// The state machine CALLCLT transitioned from IDLE to SETUP.
*Sep
7 16:38:41:135 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLCTRL: State changed from CALLINPROGRESS to INCALL.(ObjectID = 15)
// The state machine CALLCTRL transitioned from CALLINPROGRESS to INCALL.
*Sep
7 16:38:41:246 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SLC]:
General: Succeed in dealing with call request.
Additional: Conference ID is 15.
Incoming call ID is 22.
Outgoing call ID is 23.
Caller number is 2002.
Called number is 200.
// The SLC module succeeded in handling the call request.
*Sep
7 16:38:41:397 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Receive UCM Setup ACK message.
// The SSA module received the UCM_SETUPACK message.
*Sep
7 16:38:41:498 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Receive UCM Setup request message.
// The SSA module received the UCM_SETUPREQ message.
*Sep
7 16:38:41:699 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in getting a free element from the list.
Additional: Call control block ID is 44.
// The SSA module got a free element from the list as the control block (ID: 44) for the current call.
*Sep
7 16:38:41:851 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Received message from the stack.
Additional: The message type is SetupAck.
// The SSA module received a SetupAck message from the network side.
357
*Sep
7 16:38:42:02 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Send UCM Setup ACK message.
// The SSA module sent a UCM_SETUPACK message to the SLC module.
*Sep
7 16:38:42:153 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in sending the network message.
Additional: Method type is INVITE.
// The SSA module sent an INVITE to the network side.
*Sep
7 16:38:42:304 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Receive UCM Setup ACK message.
// The SLC module received the UCM_SETUPACK message.
*Sep
7 16:38:42:455 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCLT: Received event UCMSETUPACK while at state SETUP.(ObjectID = 23)
// The state machine CALLCLT received a UCMSETUPACK event in the SETUP state.
*Sep
7 16:38:42:707 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Received message from the stack.
Additional: The message type is AlertingInd.
// The SSA module received an AlertingInd message from the network side.
*Sep
7 16:38:42:868 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Send UCM Alerting message.
// The SSA module sent a UCM_ALERTING message to the SLC module.
*Sep
7 16:38:42:969 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Receive UCM Alerting message.
// The SLC module received the UCM_ALERTING message.
*Sep
7 16:38:43:171 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCLT: Received event UCMALERTINGIND while at state SETUP.(ObjectID = 23)
// The state machine CALLCLT received a UCMALERTING event in the SETUP state
*Sep
7 16:38:43:322 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
358
CALLCTRL: Received event CALLTRANSMIT while at state INCALL.(ObjectID = 15)
// The state machine CALLCTRL received a CALLTRANSMIT event in the INCALL state.
*Sep
7 16:38:43:422 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLSRV: Received event CCALERTINGIND while at state SETUP.(ObjectID = 22)
// The state machine CALLSRV received a CCALERTING event in the SETUP state.
*Sep
7 16:38:43:624 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Alerting message.
// The SLC module sent a UCM_ALERTING message to the SSA module.
*Sep
7 16:38:43:725 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 6, Group = 6, Index = 22, Length = 16000
// The SLC module stopped a 16000-ms timer.
*Sep
7 16:38:43:876 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 6, Group = 6, Index = 22, Length = 150000
// The SLC module started a timer, with the value set to 150000 ms.
*Sep
7 16:38:44:77 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLSRV: State changed from SETUP to ALERTING.(ObjectID = 22)
// The state machine CALLSRV transitioned from SETUP to ALERTING.
*Sep
7 16:38:44:178 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 6, Group = 6, Index = 23, Length = 16000
// The SLC module stopped a 16000-ms timer.
*Sep
7 16:38:44:289 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 6, Group = 6, Index = 23, Length = 150000
// The SLC module started a timer, with the value set to 150000 ms.
*Sep
7 16:38:44:440 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLCLT: State changed from SETUP to ALERTING.(ObjectID = 23)
// The state machine CALLCLT transitioned from SETUP to ALERTING.
*Sep
7 16:38:44:642 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
359
Receive UCM Alerting message.
// The SSA module received a UCM_ALERTING message.
*Sep
7 16:38:44:793 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in sending the network message.
Additional: Method type is INVITE, status code is 183.
// The SSA module sent a 183 response to the network side for the INVITE method.
*Sep
7 16:38:45:50 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Received message from the stack.
Additional: The message type is ConnectInd.
// The SSA module received a ConnectInd message from the network side.
*Sep
7 16:38:45:50 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Send UCM Connecting message.
// The SSA module sent a UCM_CONNECTING message to the SLC module.
*Sep
7 16:38:45:196 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Receive UCM Connecting message.
// The SLC module received the UCM_CONNECTING message.
*Sep
7 16:38:45:347 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCLT: Received event UCMCONNECTIND while at state ALERTING.(ObjectID = 23)
// The state machine CALLCLT received a UCMCONNECTING event in the ALERTING state.
*Sep
7 16:38:45:498 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCTRL: Received event CALLTRANSMIT while at state INCALL.(ObjectID = 15)
// The state machine CALLCTRL received a CALLTRANSMIT event in the INCALL state.
*Sep
7 16:38:45:649 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLSRV: Received event CCCONNECTIND while at state ALERTING.(ObjectID = 22)
// The state machine CALLSRV received a CCCONNECTING event in the ALERTING state.
*Sep
7 16:38:45:800 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Connecting message.
// The SLC module sent a Connecting message to the SSA module.
360
*Sep
7 16:38:45:901 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 6, Group = 6, Index = 22, Length = 150000
// The SLC module stopped a 150000-ms timer.
*Sep
7 16:38:46:103 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 6, Group = 6, Index = 22, Length = 16000
// The SLC module started a timer, with the value set to 16000 ms.
*Sep
7 16:38:46:254 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLSRV: State changed from ALERTING to CONNECT.(ObjectID = 22)
// The state machine CALLSRV transitioned from ALERTING to CONNECT.
*Sep
7 16:38:46:415 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 6, Group = 6, Index = 23, Length = 150000
// The SLC module stopped a 150000-ms timer.
*Sep
7 16:38:46:516 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 6, Group = 6, Index = 23, Length = 16000
// The SLC module started a timer, with the value set to 16000 ms.
*Sep
7 16:38:46:667 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLCLT: State changed from ALERTING to CONNECT.(ObjectID = 23)
// The state machine CALLCLT transitioned from ALERTING to CONNECT.
*Sep
7 16:38:46:818 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Receive UCM Connecting message.
// The SSA module received a UCM_CONNECTING message.
*Sep
7 16:38:47:20 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in sending the network message.
Additional: Method type is INVITE, status code is 200.
// The SSA module sent a 200 response to the network side for the INVITE method.
*Sep
7 16:38:47:121 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Received message from the stack.
Additional: The message type is ConnectCfm.
361
// The SSA module received a ConnectCfm message from the network side.
*Sep
7 16:38:47:272 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Send UCM Connect ACK message.
// The SSA module sent a UCM_CONNECTACK message to the SLC module.
*Sep
7 16:38:47:423 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Receive UCM Connect ACK message.
// The SLC module received the UCM_CONNECTACK message.
*Sep
7 16:38:47:574 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLSRV: Received event UCMCONNECTCFM while at state CONNECT.(ObjectID = 22)
// The state machine CALLSRV received a UCMCONNECTCFM event in the CONNECT state.
*Sep
7 16:38:47:725 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCTRL: Received event CALLCONFIRM while at state INCALL.(ObjectID = 15)
// The state machine CALLCTRL received a CALLCONFIRM event in the INCALL state.
*Sep
7 16:38:47:886 2007 Sysname SSM/7/VOICE:
SSM_EVENT [CALL_SLC]:
CALLCLT: Received event CCCONNECTCFM while at state CONNECT.(ObjectID = 23)
// The state machine CALLCLT received a CCCONNECTCFM event in the CONNECT state.
*Sep
7 16:38:48:37 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SLC]:
Send UCM Connect ACK message.
// The SLC module sent a UCM_CONNECTACK message to the SSA module.
*Sep
7 16:38:48:138 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 6, Group = 6, Index = 23, Length = 16000
// The SLC module stopped a 16000-ms timer.
*Sep
7 16:38:48:340 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLCLT: State changed from CONNECT to ACTIVE.(ObjectID = 23)
// The state machine CALLCLT transitioned from CONNECT to ACTIVE.
*Sep
7 16:38:48:491 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Start Timer: Type = 5, Group = 5, Index = 15, Length = 3600000
362
// The SLC module started a timer, with the value set to 3600000 ms.
*Sep
7 16:38:48:642 2007 Sysname SSM/7/VOICE:
SSM_TIMER [CALL_SLC]:
Stop Timer: Type = 6, Group = 6, Index = 22, Length = 16000
// The SLC module stopped a 16000-ms timer.
*Sep
7 16:38:48:743 2007 Sysname SSM/7/VOICE:
SSM_FSM [CALL_SLC]:
CALLSRV: State changed from CONNECT to ACTIVE.(ObjectID = 22)
// The state machine CALLSRV transitioned from CONNECT to ACTIVE.
*Sep
7 16:38:48:894 2007 Sysname SSM/7/VOICE:
SSM_PRIM [CALL_SSA]:
Receive UCM Connect ACK message.
// The SSA module received a UCM_CONNECTACK message.
*Sep
7 16:38:49:96 2007 Sysname SSM/7/VOICE:
SSM_INFO [CALL_SSA]:
General: Succeed in sending the network message.
Additional: Method type is ACK.
// The SSA module sent an ACK to the network side.
debugging voice ssm lsm
Use debugging voice ssm lsm to enable debugging for SIP server location service.
Use undo debugging voice ssm lsm to disable debugging for SIP server location service.
Syntax
debugging voice ssm lsm { all | error | info }
undo debugging voice ssm lsm { all | error | info }
Default
Debugging for SIP server location service is disabled.
Views
User view
Default command level
2: System level
Parameters
lsm: Enables debugging for SIP server location service.
all: Specifies all types of debugging.
error: Specifies error debugging.
info: Specifies information debugging.
363
Examples
# Enable all types of debugging for location service. When a user with number 2002 initiates a
registration request with authentication information to the SIP server, output similar to the following
example is generated:
<Sysname> debugging voice ssm lsm all
Enable SSM LSM ALL debugging functions
<Sysname>
*Sep
8 15:22:09:239 2007 Sysname SSM/7/VOICE:
SSM_INFO [LSM]:
General: Succeed in getting the user information.
Additional: The number is 2002.
// The location service succeeded in getting user information.
*Sep
8 15:22:09:240 2007 Sysname SSM/7/VOICE:
SSM_INFO [LSM]:
General: The authentication is needed.
Additional: The number is 2002, the realm is "H3C", the algorithm is "MD5",
the nonce is "46e2bf4d2871e5e985f96008c04a0f7c5a85f106".
// Authentication is needed.
*Sep
8 15:22:09:240 2007 Sysname SSM/7/VOICE:
SSM_INFO [LSM]:
General: Don't pass the authentication successfully.
Additional: The number is 2002.
// The authentication failed.
*Sep
8 15:22:09:243 2007 Sysname SSM/7/VOICE:
SSM_INFO [LSM]:
General: Succeed in getting the user information.
Additional: The number is 2002.
// The location service succeeded in getting user information.
*Sep
8 15:22:09:243 2007 Sysname SSM/7/VOICE:
SSM_INFO [LSM]:
General: Succeed in passing the authentication.
Additional: The number is 2002.
// The authentication succeeded.
debugging voice ssm probe
Use debugging voice ssm probe to enable debugging for SIP server probe.
Use undo debugging voice ssm probe to disable debugging for SIP server probe.
Syntax
debugging voice ssm probe { all | error | event | fsm | info | prim | timer }
undo debugging voice ssm probe { all | error | event | fsm | info | prim | timer }
364
Default
Debugging for SIP server probe is disabled.
Views
User view
Default command level
2: System level
Parameters
probe: Enables debugging for SIP server probe.
all: Specifies all types of debugging.
error: Specifies error debugging.
event: Specifies event debugging.
fsm: Specifies finite state machine debugging.
info: Specifies information debugging.
prim: Specifies primitive debugging.
timer: Specifies timer debugging.
Examples
# Enable all types of debugging for SIP server probe. When the server operating in probe mode is
disconnected from the primary server, output similar to the following example is generated:
<Sysname> debugging voice ssm lsm all
Enable SSM LSM ALL debugging functions
<Sysname>
*Sep
8 17:44:18:530 2007 Sysname SSM/7/VOICE:
SSM_EVENT [PROBE_SLC]:
PROBE: Received event STARTALIVEPROBE while at state IDLE.(ObjectID = 0)
// The Probe state machine received a STARTALIVEPROBE event in the IDLE state.
*Sep
8 17:44:18:530 2007 Sysname SSM/7/VOICE:
SSM_TIMER [PROBE_SLC]:
Start Timer: Type = 1, Group = 1, Index = 0, Length = 64000
// The SLC module started a probe timer, with the value set to 64000 ms.
*Sep
8 17:44:18:530 2007 Sysname SSM/7/VOICE:
SSM_PRIM [PROBE_SLC]:
Send UCM Options request message.
// The SLC module sent a UCM_OPTIONSREQ message to the SSA module.
*Sep
8 17:44:18:530 2007 Sysname SSM/7/VOICE:
SSM_FSM [PROBE_SLC]:
PROBE: State changed from IDLE to ACTIVE.(ObjectID = 0)
// The Probe state machine transitioned from IDLE to ACTIVE.
365
*Sep
8 17:44:18:530 2007 Sysname SSM/7/VOICE:
SSM_PRIM [PROBE_SSA]:
Receive UCM Options request message.
// The SSA module received the UCM_OPTIONSREQ message.
*Sep
8 17:44:18:530 2007 Sysname SSM/7/VOICE:
SSM_INFO [PROBE_SSA]:
General: Succeed in sending the network message.
Additional: Method type is OPTIONS.
// The SSA module sent an OPTIONS request to the network side.
*Sep
8 17:44:33:95 2007 Sysname SSM/7/VOICE:
SSM_INFO [PROBE_SSA]:
General: Received message from the stack.
Additional: The message type is options response, response code is 408.
// The SSA module received an OPTIONS response (408) from the protocol stack.
*Sep
8 17:44:33:95 2007 Sysname SSM/7/VOICE:
SSM_PRIM [PROBE_SSA]:
Send UCM Options response message.
// The SSA module sent a UCM_OPTIONSRSP message to the SLC module.
*Sep
8 17:44:33:95 2007 Sysname SSM/7/VOICE:
SSM_PRIM [PROBE_SLC]:
Receive UCM Options response message.
// The SLC module received the UCM_OPTIONSRSP message.
*Sep
8 17:44:33:96 2007 Sysname SSM/7/VOICE:
SSM_EVENT [PROBE_SLC]:
PROBE: Received event UCMOPTIONCFM while at state ACTIVE.(ObjectID = 0)
// The Probe state machine received a UCMOPTIONCFM event in the ACTIVE state.
*Sep
8 17:44:33:96 2007 Sysname SSM/7/VOICE:
SSM_INFO [PROBE_SLC]:
General: Receive options response message.
Additional: Response code is 408.
// The SLC module received the OPTIONS response (408).
*Sep
8 17:44:33:96 2007 Sysname SSM/7/VOICE:
SSM_INFO [PROBE_SLC]:
General: Link state change to disconnect.
// The link state changed to disconnect.
*Sep
8 17:44:33:96 2007 Sysname SSM/7/VOICE:
SSM_TIMER [PROBE_SLC]:
366
Stop Timer: Type = 1, Group = 1, Index = 0, Length = 64000
// The SLC module stopped a 64000-ms probe timer.
*Sep
8 17:44:33:96 2007 Sysname SSM/7/VOICE:
SSM_TIMER [PROBE_SLC]:
Start Timer: Type = 1, Group = 1, Index = 0, Length = 64000
// The SLC module started a probe timer, with the value set to 64000 ms.
debugging voice ssm reg
Use debugging voice ssm reg to enable debugging for SIP server registration service.
Use undo debugging voice ssm reg to disable debugging for SIP server registration service.
Syntax
debugging voice ssm reg { all | error | event | fsm | info | prim | timer }
undo debugging voice ssm reg { all | error | event | fsm | info | prim | timer }
Default
Debugging for SIP server registration service is disabled.
Views
User view
Default command level
2: System level
Parameters
reg: Enables debugging for SIP server registration service.
all: Specifies all types of debugging.
all: Specifies error debugging.
event: Specifies event debugging.
fsm: Specifies finite state machine debugging.
info: Specifies information debugging.
prim: Specifies primitive debugging.
timer: Specifies timer debugging.
Examples
# Enable all types of debugging for SIP server registration service. When a user with number 3001
registers with the SIP server, output similar to the following example is generated:
<Sysname> debugging voice ssm reg all
Enable SSM REG ALL debugging functions
<Sysname>
*Sep
7 16:51:40:326 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SSA]:
General: Received message from the stack.
Additional: The message type is RegisterInd.
Register number is 3001.
367
// The SSA module received a REGISTER request from the protocol stack.
*Sep
7 16:51:40:326 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SSA]:
Send UCM Register request message.
// The SSA module sent the REGISTER request to the UCM module.
*Sep
7 16:51:40:327 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SLC]:
Receive UCM Register request message.
// The SLC module received the REGISTER request from the UCM module.
*Sep
7 16:51:40:327 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SLC]:
General: Succeed in getting a free element from the list.
Additional: Register control block ID is 33.
// The SLC module got a free element from the list.
*Sep
7 16:51:40:327 2007 Sysname SSM/7/VOICE:
SSM_EVENT [REG_SLC]:
REGISTER: Received event UCMREGISTERREQ while at state IDLE.(ObjectID = 33)
// The SLC module received a UCMREGISTERREQ event in the IDLE state.
*Sep
7 16:51:40:328 2007 Sysname SSM/7/VOICE:
SSM_FSM [REG_SLC]:
REGISTER: State changed from IDLE to REGISTERING.(ObjectID = 33)
// The SLC module changed from IDLE state to REGISTERING state.
*Sep
7 16:51:40:328 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SLC]:
General: Succeed in dealing with register request.
Additional: Status code is 401.
expires is 3600(s).
user number is 3001.
// The SLC module handled the registration request successfully.
*Sep
7 16:51:40:328 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SLC]:
Send UCM Register response message.
// The SLC module sent a REGISTER response to the UCM module.
*Sep
7 16:51:40:328 2007 Sysname SSM/7/VOICE:
SSM_TIMER [REG_SLC]:
Start Timer: Type = 2, Group = 2, Index = 33, Length = 64000
// The SLC module started a timer, with the value set to 64000 ms.
368
*Sep
7 16:51:40:577 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SSA]:
Receive UCM Register response message.
// The SSA module received the REGISTER response from the UCM module.
*Sep
7 16:51:40:687 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SSA]:
General: Succeed in sending the network message.
Additional: Method type is REGISTER, status code is 401.
// The SSA module sent a REGISTER response (401) to the network side.
*Sep
7 16:51:40:787 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SSA]:
General: Received message from the stack.
Additional: The message type is RegisterInd.
Register number is 3001.
*Sep
7 16:51:40:987 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SSA]:
Send UCM Register request message.
*Sep
7 16:51:41:137 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SLC]:
Receive UCM Register request message.
*Sep
7 16:51:41:287 2007 Sysname SSM/7/VOICE:
SSM_EVENT [REG_SLC]:
REGISTER: Received event UCMREGISTERREQ while at state REGISTERING.(ObjectID = 33)
*Sep
7 16:51:41:487 2007 Sysname SSM/7/VOICE:
SSM_TIMER [REG_SLC]:
Stop Timer: Type = 2, Group = 2, Index = 33, Length = 64000
// The SLC module stopped a 64000-ms timer.
*Sep
7 16:51:41:587 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SLC]:
General: Succeed in dealing with register request.
Additional: Status code is 200.
expires is 3600(s).
user number is 3001.
*Sep
7 16:51:41:737 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SLC]:
Send UCM Register response message.
*Sep
7 16:51:41:887 2007 Sysname SSM/7/VOICE:
369
SSM_TIMER [REG_SLC]:
Start Timer: Type = 3, Group = 3, Index = 33, Length = 3600000
*Sep
7 16:51:42:37 2007 Sysname SSM/7/VOICE:
SSM_FSM [REG_SLC]:
REGISTER: State changed from REGISTERING to ACTIVE.(ObjectID = 33)
*Sep
7 16:51:42:297 2007 Sysname SSM/7/VOICE:
SSM_PRIM [REG_SSA]:
Receive UCM Register response message.
*Sep
7 16:51:42:397 2007 Sysname SSM/7/VOICE:
SSM_INFO [REG_SSA]:
General: Succeed in sending the network message.
Additional: Method type is REGISTER, status code is 200.
debugging voice ssm stack
Use debugging voice ssm stack to enable debugging for SIP server protocol stack.
Use undo debugging voice ssm stack to disable debugging for SIP server protocol stack.
Syntax
debugging voice ssm stack { all | info | packet | timer }
undo debugging voice ssm stack { all | info | packet | timer }
Default
Debugging for SIP server protocol stack is disabled.
Views
User view
Default command level
2: System level
Parameters
stack: Enables debugging for SIP server protocol stack.
all: Specifies all types of debugging.
info: Specifies information debugging.
packet: Specifies packet debugging.
timer: Specifies timer debugging.
Examples
The output in the following examples was created when User A with number 2001 calls User B with
number 3001. User A and User B have both registered with the SIP server.
# Enable timer debugging for SIP server protocol stack.
<Sysname>debugging voice ssm stack timer
Enable SSM STACK TIMER debugging functions
<Sysname>
370
*Sep
8 17:50:24:554 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2550, Group = 10, Index = 74, Length = 64000
// The protocol stack started a timer, with the value set to 64000 ms.
*Sep
8 17:50:24:555 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 0, Group = 8, Index = 127, Length = 30000
*Sep
8 17:50:24:555 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2805, Group = 15, Index = 21, Length = 600000
*Sep
8 17:50:24:555 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 0, Group = 8, Index = 127, Length = 30000
// The protocol stack stopped a 30000-ms timer.
*Sep
8 17:50:24:555 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 0, Group = 8, Index = 128, Length = 30000
*Sep
8 17:50:24:556 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 0, Group = 9, Index = 75, Length = 500
*Sep
8 17:50:24:556 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 255, Group = 10, Index = 75, Length = 32000
*Sep
8 17:50:24:556 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2805, Group = 15, Index = 22, Length = 600000
*Sep
8 17:50:24:557 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 0, Group = 8, Index = 128, Length = 30000
*Sep
8 17:50:24:901 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 255, Group = 10, Index = 75, Length = 32000
*Sep
8 17:50:24:901 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 0, Group = 9, Index = 75, Length = 500
*Sep
8 17:50:24:999 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
371
Start Timer: Type = 2805, Group = 10, Index = 75, Length = 256000
*Sep
8 17:50:25:149 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 0, Group = 11, Index = 22, Length = 128000
*Sep
8 17:50:25:303 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 2805, Group = 15, Index = 22, Length = 600000
*Sep
8 17:50:25:410 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2805, Group = 15, Index = 22, Length = 600000
*Sep
8 17:50:25:604 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 2805, Group = 10, Index = 75, Length = 256000
*Sep
8 17:50:25:774 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2805, Group = 10, Index = 75, Length = 256000
*Sep
8 17:50:25:904 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 0, Group = 11, Index = 22, Length = 128000
*Sep
8 17:50:26:35 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 0, Group = 11, Index = 22, Length = 128000
*Sep
8 17:50:26:340 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 2805, Group = 15, Index = 22, Length = 600000
*Sep
8 17:50:26:340 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2805, Group = 15, Index = 22, Length = 600000
*Sep
8 17:50:26:499 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 2550, Group = 10, Index = 74, Length = 64000
*Sep
8 17:50:26:638 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2550, Group = 10, Index = 74, Length = 128000
*Sep
8 17:50:26:769 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
372
Start Timer: Type = 0, Group = 8, Index = 129, Length = 30000
*Sep
8 17:50:26:899 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 2805, Group = 15, Index = 21, Length = 600000
*Sep
8 17:50:27:20 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2805, Group = 15, Index = 21, Length = 600000
*Sep
8 17:50:27:132 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 1020, Group = 12, Index = 21, Length = 120000
*Sep
8 17:50:27:355 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 2550, Group = 10, Index = 74, Length = 128000
*Sep
8 17:50:27:464 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 2550, Group = 10, Index = 74, Length = 128000
*Sep
8 17:50:27:713 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Start Timer: Type = 0, Group = 8, Index = 130, Length = 30000
*Sep
8 17:50:27:714 2007 Sysname SSM/7/VOICE:
SSM_TIMER [STACK]:
Stop Timer: Type = 1020, Group = 12, Index = 21, Length = 120000
# Enable packet debugging for SIP server protocol stack.
<Sysname>debug voice ssm stack packet
Enable SSM STACK PACKET debugging functions
<Sysname>
*Sep
8 17:40:32:561 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: NetWork--->Stack
INVITE sip:3001@100.1.1.188:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK275cffa6341
Call-ID: b824639c89ea2bdb3fc82faf275cffa66@192.168.1.101
From: <sip:2001@192.168.1.101:5060>;tag=275cffa6
To: <sip:3001@100.1.1.188:5060>
CSeq: 1 INVITE
Contact: <sip:2001@192.168.1.101:5060>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 08 Sep 2007 17:40:32 GMT
Supported: 100rel
Max-Forwards: 70
373
Content-Length: 239
Content-Type: application/sdp
v=0
o=HUAWEI 1073741844 1073741844 IN IP4 100.1.1.188
s=Sip Call
c=IN IP4 100.1.1.188
t=0 0
m=audio 16396 RTP/AVP 18 8 0 4
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:4 G723/8000
// The server received an INVITE request from the network side.
*Sep
8 17:40:32:562 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK275cffa6341
Call-ID: b824639c89ea2bdb3fc82faf275cffa66@192.168.1.101
From: <sip:2001@192.168.1.101:5060>;tag=275cffa6
To: <sip:3001@100.1.1.188:5060>
CSeq: 1 INVITE
Content-Length: 0
// The server sent a 100 (Trying) response to the network side.
*Sep
8 17:40:32:562 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork
INVITE sip:3001@100.1.1.185:5060;user=phone;ttl=0 SIP/2.0
Via: SIP/2.0/UDP 100.1.1.188:5060;branch=z9hG4bK423ec20d0a4
Call-ID: 3411a7fdb824639cd797366b423ec20d@100.1.1.188
From: <sip:2001@100.1.1.188:5060;user=phone;ttl=0>;tag=423ec20d
To: <sip:3001@100.1.1.185:5060;user=phone;ttl=0>
CSeq: 1 INVITE
Contact: <sip:Sip-Server@100.1.1.188:5060;user=phone;ttl=0>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 08 Sep 2007 17:40:32 GMT
Max-Forwards: 70
Supported: 100rel
Content-Length: 239
Content-Type: application/sdp
v=0
o=HUAWEI 1073741844 1073741844 IN IP4 100.1.1.188
s=Sip Call
374
c=IN IP4 100.1.1.188
t=0 0
m=audio 16396 RTP/AVP 18 8 0 4
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:4 G723/8000
// The server sent an INVITE to the network side.
*Sep
8 17:40:32:622 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: NetWork--->Stack
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 100.1.1.188:5060;branch=z9hG4bK423ec20d0a4
Call-ID: 3411a7fdb824639cd797366b423ec20d@100.1.1.188
From: <sip:2001@100.1.1.188:5060;user=phone;ttl=0>;tag=423ec20d
To: <sip:3001@100.1.1.185:5060;user=phone;ttl=0>;tag=e57f039c
CSeq: 1 INVITE
Contact: <sip:3001@100.1.1.185:5060>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 08 Sep 2007 17:39:37 GMT
Content-Length: 167
Content-Type: application/sdp
v=0
o=HUAWEI 1073741846 1073741846 IN IP4 100.1.1.185
s=Sip Call
c=IN IP4 100.1.1.185
t=0 0
m=audio 16392 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
// The server received a 183 response from the network side.
*Sep
8 17:40:32:622 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK275cffa6341
Call-ID: b824639c89ea2bdb3fc82faf275cffa66@192.168.1.101
From: <sip:2001@192.168.1.101:5060>;tag=275cffa6
To: <sip:3001@100.1.1.188:5060>;tag=aa465f5e
CSeq: 1 INVITE
Contact: <sip:Sip-Server@100.1.1.188:5060;user=phone;ttl=0>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 08 Sep 2007 17:39:37 GMT
Content-Length: 167
375
Content-Type: application/sdp
v=0
o=HUAWEI 1073741846 1073741846 IN IP4 100.1.1.185
s=Sip Call
c=IN IP4 100.1.1.185
t=0 0
m=audio 16392 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
// The server sent the 183 response to the network side.
*Sep
8 17:40:42:465 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: NetWork--->Stack
SIP/2.0 200 OK
Via: SIP/2.0/UDP 100.1.1.188:5060;branch=z9hG4bK423ec20d0a4
Call-ID: 3411a7fdb824639cd797366b423ec20d@100.1.1.188
From: <sip:2001@100.1.1.188:5060;user=phone;ttl=0>;tag=423ec20d
To: <sip:3001@100.1.1.185:5060;user=phone;ttl=0>;tag=e57f039c
CSeq: 1 INVITE
Contact: <sip:3001@100.1.1.185:5060>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
Date: Sat, 08 Sep 2007 17:39:43 GMT
Content-Length: 167
Content-Type: application/sdp
v=0
o=HUAWEI 1073741848 1073741848 IN IP4 100.1.1.185
s=Sip Call
c=IN IP4 100.1.1.185
t=0 0
m=audio 16392 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
// The server received a 200 response from the network side.
*Sep
8 17:40:42:466 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.1.101:5060;branch=z9hG4bK275cffa6341
Call-ID: b824639c89ea2bdb3fc82faf275cffa66@192.168.1.101
From: <sip:2001@192.168.1.101:5060>;tag=275cffa6
To: <sip:3001@100.1.1.188:5060>;tag=aa465f5e
CSeq: 1 INVITE
Contact: <sip:Sip-Server@100.1.1.188:5060;user=phone;ttl=0>
Allow: ACK,BYE,CANCEL,INFO,INVITE,NOTIFY,PRACK,REFER,REGISTER,UPDATE
376
Date: Sat, 08 Sep 2007 17:39:43 GMT
Content-Length: 167
Content-Type: application/sdp
v=0
o=HUAWEI 1073741848 1073741848 IN IP4 100.1.1.185
s=Sip Call
c=IN IP4 100.1.1.185
t=0 0
m=audio 16392 RTP/AVP 18
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
// The server sent the 200 response to the network side.
*Sep
8 17:40:42:484 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: NetWork--->Stack
ACK sip:Sip-Server@100.1.1.188:5060;user=phone;ttl=0 SIP/2.0
Via: SIP/2.0/UDP 100.1.1.188:5060;branch=z9hG4bK0c065f5e447
Call-ID: b824639c89ea2bdb3fc82faf275cffa66@192.168.1.101
From: <sip:2001@192.168.1.101:5060>;tag=275cffa6
To: <sip:3001@100.1.1.188:5060>;tag=aa465f5e
CSeq: 1 ACK
Date: Sat, 08 Sep 2007 17:40:42 GMT
Max-Forwards: 70
Content-Length: 0
// The server received an ACK from the network side.
*Sep
8 17:40:42:484 2007 Sysname SSM/7/VOICE:
SSM_PACKET [STACK]: Stack--->NetWork
ACK sip:3001@100.1.1.185:5060;user=phone;ttl=0 SIP/2.0
Via: SIP/2.0/UDP 100.1.1.188:5060;branch=z9hG4bK447ec20de08
Call-ID: 3411a7fdb824639cd797366b423ec20d@100.1.1.188
From: <sip:2001@100.1.1.188:5060;user=phone;ttl=0>;tag=423ec20d
To: <sip:3001@100.1.1.185:5060;user=phone;ttl=0>;tag=e57f039c
CSeq: 1 ACK
Contact: <sip:Sip-Server@100.1.1.188:5060;user=phone;ttl=0>
Date: Sat, 08 Sep 2007 17:40:42 GMT
Max-Forwards: 70
Content-Length: 0
// The server sent an ACK to the network side.
debugging voice ssm sub
Use debugging voice ssm sub to enable debugging for SIP server subscription service.
Use undo debugging voice ssm sub to disable debugging for SIP server subscription service.
377
Syntax
debugging voice ssm sub { all | error | event | fsm | info | prim | timer }
undo debugging voice ssm sub { all | error | event | fsm | info | prim | timer }
Default
Debugging for SIP server subscription service is disabled.
Views
User view
Default command level
2: System level
Parameters
sub: Enables debugging for SIP server subscription service.
all: Specifies all types of debugging.
error: Specifies error debugging.
event: Specifies event debugging.
fsm: Specifies finite state machine debugging.
info: Specifies information debugging.
prim: Specifies primitive debugging.
timer: Specifies timer debugging.
Examples
# Enable all types of debugging for SIP server subscription service. When User A with number 456
initiates a subscription to User B with number 2001 through the SIP server, output similar to the following
example is generated:
<Sysname> debugging voice ssm sub all
Enable SSM SUB ALL debugging functions
<Sysname>
*Sep
7 17:10:08:764 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in getting a free element from the list.
Additional: Subscribe control block ID is 0.
// The SSA module got a free element from the list.
*Sep
7 17:10:08:764 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Received message from the stack.
Additional: The message type is ReferInd.
Subscribe control block ID is 0
Caller number is 456
Called number is Sip-Server
// The SSA module received a ReferInd message from the protocol stack.
*Sep
7 17:10:08:764 2007 Sysname SSM/7/VOICE:
378
SSM_PRIM [SUB_SSA]:
Send UCM Subscribe request message.
// The SSA module sent a subscription request to the UCM module.
*Sep
7 17:10:08:765 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Receive UCM Subscribe request message.
// The SLC module received the subscription request from the UCM module.
*Sep
7 17:10:08:765 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SLC]:
General: Succeed in getting a free element from the list.
Additional: Subscirbe control block ID is 0.
// The SLC module got a free element from the list.
*Sep
7 17:10:08:765 2007 Sysname SSM/7/VOICE:
SSM_EVENT [SUB_SLC]:
SUBSCRIBE: Received event SUBSCRIBEREQ while at state IDLE.(ObjectID = 0)
// The SLC module received a SUBSCRIBEREQ event in the IDLE state.
*Sep
7 17:10:08:766 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SLC]:
General: Succeed in associate call.
Additional: Subscribe control block ID is 0
Call control block ID is 6
Caller number is 456
Called number is Sip-Server
// The SLC module found the relevant session.
*Sep
7 17:10:08:766 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe request message.
// The SLC module sent a subscription request to the UCM module.
*Sep
7 17:10:08:766 2007 Sysname SSM/7/VOICE:
SSM_FSM [SUB_SLC]:
SUBSCRIBE: State changed from IDLE to SUB.(ObjectID = 0)
// The SLC module changed from IDLE state to SUB state.
*Sep
7 17:10:08:963 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe request message.
// The SSA module received the subscription request from the UCM module.
*Sep
7 17:10:09:273 2007 Sysname SSM/7/VOICE:
379
SSM_INFO [SUB_SSA]:
General: Succeed in getting a free element from the list.
Additional: Subscribe control block ID is 1.
// The SSA module got a free element from the list.
*Sep
7 17:10:09:373 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is REFER.
// The SSA module sent a REFER message to the network side.
*Sep
7 17:10:09:473 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Received message from the stack.
Additional: The message type is ReferCfm.
*Sep
7 17:10:09:673 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Send UCM Subscribe response message.
*Sep
7 17:10:09:823 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Receive UCM Subscribe response message.
*Sep
7 17:10:10:73 2007 Sysname SSM/7/VOICE:
SSM_EVENT [SUB_SLC]:
SUBSCRIBE: Received event SUBSCRIBECFM while at state SUB.(ObjectID = 0)
*Sep
7 17:10:10:173 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe response message.
*Sep
7 17:10:10:323 2007 Sysname SSM/7/VOICE:
SSM_TIMER [SUB_SLC]:
Start Timer: Type = 7, Group = 7, Index = 0, Length = 120000
// The SLC module started a timer, with the value set to 120000 ms.
*Sep
7 17:10:10:473 2007 Sysname SSM/7/VOICE:
SSM_FSM [SUB_SLC]:
SUBSCRIBE: State changed from SUB to ACTIVE.(ObjectID = 0)
// The SLC module changed from SUB state to ACTIVE state.
*Sep
7 17:10:10:623 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe response message.
*Sep
7 17:10:10:833 2007 Sysname SSM/7/VOICE:
380
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is REFER, status code is 202.
*Sep
7 17:10:10:983 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Received message from the stack.
Additional: The message type is NotifyInd.
*Sep
7 17:10:11:83 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Send UCM Subscribe request message.
*Sep
7 17:10:11:233 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Receive UCM Subscribe request message.
*Sep
7 17:10:11:383 2007 Sysname SSM/7/VOICE:
SSM_EVENT [SUB_SLC]:
SUBSCRIBE: Received event SUBREQUESTREQ while at state ACTIVE.(ObjectID = 0)
*Sep
7 17:10:11:483 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe request message.
*Sep
7 17:10:11:633 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe request message.
*Sep
7 17:10:11:783 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is NOTIFY.
*Sep
7 17:10:11:883 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Received message from the stack.
Additional: The message type is NotifyCfm.
// The SSA module received a NotifyCfm message from the protocol stack.
*Sep
7 17:10:12:83 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Send UCM Subscribe response message.
*Sep
7 17:10:12:243 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Receive UCM Subscribe response message.
381
*Sep
7 17:10:12:394 2007 Sysname SSM/7/VOICE:
SSM_EVENT [SUB_SLC]:
SUBSCRIBE: Received event SUBREQUESTRSP while at state ACTIVE.(ObjectID = 0)
*Sep
7 17:10:12:494 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe response message.
*Sep
7 17:10:12:643 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe response message.
// The SSA module received a response to the subscription request from the UCM module.
*Sep
7 17:10:12:794 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is NOTIFY, status code is 200.
*Sep
7 17:10:17:733 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Received message from the stack.
Additional: The message type is NotifyInd.
*Sep
7 17:10:17:733 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Send UCM Subscribe request message.
*Sep
7 17:10:17:733 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Receive UCM Subscribe request message.
*Sep
7 17:10:17:733 2007 Sysname SSM/7/VOICE:
SSM_EVENT [SUB_SLC]:
SUBSCRIBE: Received event SUBREQUESTREQ while at state ACTIVE.(ObjectID = 0)
*Sep
7 17:10:17:734 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe request message.
*Sep
7 17:10:17:734 2007 Sysname SSM/7/VOICE:
SSM_FSM [SUB_SLC]:
SUBSCRIBE: State changed from ACTIVE to TERMINAL.(ObjectID = 0)
*Sep
7 17:10:17:734 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe request message.
*Sep
7 17:10:17:735 2007 Sysname SSM/7/VOICE:
382
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is NOTIFY.
*Sep
7 17:10:17:739 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Received message from the stack.
Additional: The message type is NotifyCfm.
*Sep
7 17:10:17:935 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Send UCM Subscribe response message.
*Sep
7 17:10:18:35 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Receive UCM Subscribe response message.
*Sep
7 17:10:18:185 2007 Sysname SSM/7/VOICE:
SSM_EVENT [SUB_SLC]:
SUBSCRIBE: Received event SUBREQUESTRSP while at state TERMINAL.(ObjectID = 0)
*Sep
7 17:10:18:335 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe response message.
*Sep
7 17:10:18:485 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe release message.
*Sep
7 17:10:18:585 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SLC]:
Send UCM Subscribe release message.
*Sep
7 17:10:18:735 2007 Sysname SSM/7/VOICE:
SSM_TIMER [SUB_SLC]:
Stop Timer: Type = 7, Group = 7, Index = 0, Length = 120000
// The SLC module stopped a 120000-ms timer.
*Sep
7 17:10:18:885 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SLC]:
General: Succeed in freeing element to the list.
Additional: Subscirbe control block ID is 0.
// The SSA module released an element to the list.
*Sep
7 17:10:19:85 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe response message.
383
*Sep
7 17:10:19:195 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is NOTIFY, status code is 200.
*Sep
7 17:10:19:345 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe release message.
// The SSA module received an unsubscription message from the UCM module.
*Sep
7 17:10:19:495 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is SUBRELEASE.
// The SSA module sent a SUBRELEASE message to the network side.
*Sep
7 17:10:19:595 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in freeing element to the list.
Additional: Subscribe control block ID is 0.
*Sep
7 17:10:19:745 2007 Sysname SSM/7/VOICE:
SSM_PRIM [SUB_SSA]:
Receive UCM Subscribe release message.
*Sep
7 17:10:19:845 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in sending the network message.
Additional: Method type is SUBRELEASE.
*Sep
7 17:10:19:995 2007 Sysname SSM/7/VOICE:
SSM_INFO [SUB_SSA]:
General: Succeed in freeing element to the list.
Additional: Subscribe control block ID is 1.
debugging voice ssm ucm
Use debugging voice ssm ucm to enable debugging for SIP server call management.
Use undo debugging voice ssm ucm to disable debugging for SIP server call management.
Syntax
debugging voice ssm ucm { all | error | info }
undo debugging voice ssm ucm { all | error | info }
Default
Debugging for SIP server call management is disabled.
384
Views
User view
Default command level
2: System level
Parameters
ucm: Enables debugging for SIP server call management.
all: Specifies all types of debugging.
error: Specifies error debugging.
info: Specifies information debugging.
Examples
# Enable all types of debugging for SIP server call management.
<Sysname> debugging voice ssm ucm all
Enable SSM UCM ALL debugging functions
•
When the server enable command is used to enable the SIP server, output similar to the following
example is generated:
*Sep
8 16:59:38:367 2007 Sysname SSM/7/VOICE:
SSM_INFO [UCM]:
General: Succeed in starting the server.
// The UCM module started the server.
•
When the undo server enable command is used to disable the SIP server, output similar to the
following example is generated:
*Sep
8 17:00:13:728 2007 Sysname SSM/7/VOICE:
SSM_INFO [UCM]:
General: Succeed in stopping the server.
// The UCM module stopped the server.
debugging voice srtp
Use debugging voice srtp to enable debugging for SRTP messages.
Use undo debugging voice srtp to disable debugging for SRTP messages.
Syntax
debugging voice srtp { all | error | event }
undo debugging voice srtp { all | error | event }
Default
Debugging for SRTP messages is disabled.
Views
User view
Default command level
2: System level
385
Parameters
srtp: Enables debugging for SRTP messages.
all: Specifies debugging for all SRTP message types.
error: Specifies debugging for error messages.
event: Specifies debugging for event messages.
Examples
# Enable debugging for SRTP event messages. When a call is established by using SRTP, output similar
to the following example is generated:
*Apr 10 09:36:53:924 2010 H3C_Down SRTP/7/VOICE:
SRTP_EVENT: Derive the session key whith AES_ICM algorithm.
// SRTP used the AES-ICM algorithm to generate a session key.
*Apr 10 09:36:53:924 2010 H3C_Down SRTP/7/VOICE:
SRTP_EVENT: AES_ICM: The context has been initialized.
// SRTP initialized the context for the AES-ICM algorithm.
*Apr 10 09:36:53:926 2010 H3C_Down SRTP/7/VOICE:
SRTP_EVENT: The cipher type is AES_ICM, generate RTP salt key.
// The encryption algorithm was AES_ICM, and an RTP salt key was generated.
*Apr 10 09:36:53:926 2010 H3C_Down SRTP/7/VOICE:
SRTP_EVENT: AES_ICM: The context has been initialized.
// SRTP initialized the context for the AES-ICM algorithm.
386
Smart Link debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
The Smart Link module name is identified as "SMLK" in debugging messages.
debugging smart-link
Use debugging smart-link to enable debugging for the specified or all smart link groups.
Use undo debugging smart-link to disable debugging for the specified or all smart link groups.
Syntax
debugging smart-link [ group group-id ] { all | error | event | fsm | packet }
undo debugging smart-link [ group group-id ] { all | error | event | fsm | packet }
Default
Smart link group debugging is disabled.
Views
User view
Default command level
1. Monitor level
Parameters
group group-id: Specifies a smart link group by its number.
all: Specifies all Smart Link debugging.
error: Specifies Smart Link error debugging.
event: Specifies Smart Link event debugging.
fsm: Specifies state machine debugging.
packet: Specifies packet debugging.
Usage guidelines
Table 1 describes output fields and messages for the debugging smart-link error command.
Table 195 Output from the debugging smart-link error command
Field
Description
SMLK failed to allocate memory for the following:
• batch bak—Bulk backup.
Failed to allocate memory for
String
• realtime bak—Realtime backup.
• create group—Smart link group creation.
• smlk port info—Smart link port information.
Failed to create mbuffer
Creating MBUF failed.
387
Field
Description
Failed to write packet queue
Writing packet queue failed.
Failed to write packet event
Writing packet event failed.
Table 2 describes output fields and messages for the debugging smart-link packet command.
Table 196 Output from the debugging smart-link packet command
Field
Description
Port Port Name : String
A Flush packet was sent or received on the port identified by Port Name.
VLAN Bit Map
VLAN bit map, presenting the list of VLANs carried on the other port in
the smart link group.
Examples
# Enable smart link group error debugging on a device with the Flush message reception capability.
When you configure the receive-control VLAN on Ethernet 1/1 to be different from the control VLAN of
the communicating smart link group, output similar to the following example is generated:
<Sysname> debugging smart-link error
*May 15 15:34:06:931 2007 Sysname SMLK/7/RCVPKTERR:Slot=2;
Received packet on port Ethernet1/1 error for control VLAN is different
// An error occurred because SMLK received a Flush message on port Ethernet 1/1. The message
includes a control VLAN different from the control VLAN for the receive-control VLAN configured on the
port.
# Enable event debugging for smart link group 1. The output in this example was created when the
following conditions exist:
•
Create smart link group 1.
•
Assign the master and backup ports to smart link group 1.
When a link switchover occurred in the group, output similar to the following example is generated:
<Sysname> debugging smart-link group 1 event
*May 15 15:35:12:427 2007 Sysname SMLK/7/SMLKSEND:
Smlk group 1 sent packet started.
// Smart link group 1 started to send packets upon a link switchover.
*May 15 15:35:12:437 2007 Sysname SMLK/7/SMLKSEND:
Smlk group 1 sent packet finished.
// Smart link group 1 finished sending packets.
# Enable FSM debugging for smart link group 1. The output in this example was created when the
following conditions exist:
•
Create smart link group 1.
•
Assign port Ethernet 1/1 to the group as the master port.
<Sysname> debugging smart-link group 1 fsm
*May 15 15:58:13:572 2007 Sysname SMLK/7/SMLKFSM:
Smart link group 1 : PIM occur event: Enter PIM state machine.
*May 15 15:58:13:581 2007 Sysname SMLK/7/SMLKFSM:
Smart link group 1 Port Ethernet1/1: PIM occur event: Enter EVENT_MASTER case.
*May 15 15:58:13:592 2007 Sysname SMLK/7/SMLKFSM:
388
Smart link group 1 : PSS occur event: Enter PSS state machine.
*May 15 15:58:13:602 2007 Sysname SMLK/7/SMLKFSM:
Smart link group 1 : PSS occur event: Member number is 1.
*May 15 15:58:13:611 2007 Sysname SMLK/7/SMLKFSM:
Smart link group 1 Port Ethernet1/1: PSS occur event: Link status is up.
*May 15 15:58:13:622 2007 Sysname SMLK/7/SMLKFSM:
Smart link group 1 Port Ethernet1/1: PST occur event: Enter PST state machine.
*May 15 15:58:13:632 2007 Sysname SMLK/7/SMLKFSM:
Smart link group 1 Port Ethernet1/1: PST occur event: State changes to active.
# Enable packet debugging for smart link group 1. The output in this example was created when the
following conditions exist:
•
Create smart link group 1.
•
Assign the master and backup ports to smart link group 1.
<Sysname> debugging smart-link group 1 packet
*May 15 16:04:30:546 2007 Sysname SMLK/7/SMLKPKT:
Smart link group 1:
Port Ethernet1/1: Send Flush Packet
// Port Ethernet 1/1 sent a Flush message. This indicates that a link switchover occurred in the group.
Device ID: 000f-e200-8500
// The device ID is 000F-E200-8500.
Control VLAN: 1
// The control VLAN is VLAN 1.
VLAN Bit Map:
02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
*May 15 16:04:30:625 2007 Sysname SMLK/7/SMLKPKT:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
389
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
390
SNMP debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging snmp agent packet
Use debugging snmp agent packet to enable SNMP packet debugging for the SNMP agent.
Use undo debugging snmp agent packet to disable SNMP packet debugging for the SNMP agent.
Syntax
debugging snmp agent packet { header | receive | send }
undo debugging snmp agent packet { header | receive | send }
Default
SNMP packet debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
header: Enables SNMP packet header debugging to output to the information center the following
information from an SNMP request header: version, community name, and username.
receive: Enables debugging for the SNMP packet received to output to the information center the
following information from an SNMP request received by the SNMP agent: the packet type, request-id,
error-status, error-index, and the variable binding list.
send: Enables debugging for the SNMP packet sent to output to the information center the following
information from an SNMP response sent by the SNMP agent: packet type, request-id, error-status,
error-index, and the variable binding list.
Usage guidelines
Table 1 describes output fields and messages for the debugging snmp agent packet header command.
Table 197 Output from the debugging snmp agent packet header command
Field
Description
An SNMP packet was received.
incoming SNMP-version packet
SNMP-version represents the SNMP version,
SNMPv1, SNMPv2c, or SNMPv3.
community name: community-name
SNMPv1/v2c community name.
security model: v3
SNMPv3 security model.
391
Field
Description
SNMPv3 security level:
• noAuthNoPriv—No authentication, no privacy.
• authNoPriv—Authentication without privacy.
• authPriv—Authentication with privacy.
security level: security-level
user name: user-name
SNMPv3 username.
snmpEngineID: engineID
SNMP engine ID.
snmpEngineBoots: n
Number of SNMP engine reboots.
snmpEngineTime: n
SNMP engine running time in seconds.
Table 2 describes output fields and messages for the debugging snmp agent packet receive command.
Table 198 Output from the debugging snmp agent packet receive command
Field
Description
PACKET
Information contained in the SNMP packet.
PACKET_SRC
Source address information for the SNMP packet.
The SNMP packet was received from address through
UDP.
packet received from address via UDP
address represents the source IP address of the SNMP
packet.
request-id: request-id
ID of the SNMP request, used to match the SNMP
response.
error-status: error-status
Error status of the SNMP request.
error-index: error-index
Error index of the SNMP request.
VBLIST
Variable binding list.
get request
SNMP get request.
set request
SNMP set request.
get-next request
SNMP get-next request.
get-bulk request
SNMP get-bulk request.
non-repeaters: non-repeaters
The non-repeaters field of a get-bulk request.
max-repetitions: max-repetitions
The max-repetitions field of a get-bulk request.
Table 3 describes output fields and messages for the debugging snmp agent packet send command
Table 199 Output from the debugging snmp agent packet send command
Field
Description
PACKET
Information contained in the SNMP packet.
PACKET_DES
Destination address information for the SNMP packet.
The SNMP packet was sent to address through UDP.
packet sent to address via UDP
address represents the destination IP address of the
SNMP packet.
392
Field
Description
request-id: request-id
ID of the SNMP response, used to match the SNMP
request.
error-status: error-status
Error status of the SNMP response.
error-index: error-index
Error index of the SNMP response.
VBLIST
Variable binding list.
response
SNMP response.
Examples
# Enable information center debugging and SNMP packet header debugging on the device. Output
similar to the following example is generated when network management software is used to access the
device under these conditions:
•
SNMPv1 is enabled.
•
A community name is configured.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp agent packet header
*Jul 27 08:37:26:313 2007 Sysname SNMP/7/HEADER:
incoming SNMPv1 packet
community name: public
// SNMP received an SNMPv1 request with the community name public.
# Enable information center debugging and SNMP packet header debugging on the device. Output
similar to the following example is generated when network management software is used to access the
device under these conditions:
•
SNMPv2c is enabled.
•
A community name is configured.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp agent packet header
*Jul 27 08:37:26:313 2007 Sysname SNMP/7/HEADER:
incoming SNMPv2c packet
community name: private
// SNMP received an SNMPv2c request with the community name private.
# Enable information center debugging and SNMP packet header debugging on the device. Output
similar to the following example is generated when network management software is used to access the
device under these conditions:
•
SNMPv3 is enabled.
•
A community name is configured.
<Sysname> terminal debugging
% Current terminal debugging is on
393
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp agent packet header
*Jul 27 08:51:00:563 2007 Sysname SNMP/7/HEADER:
incoming SNMPv3 packet
security model: v3
security level: authNoPriv
user name: v3user1
snmpEngineID: 000063A27F00000100001707
snmpEngineBoots: 1
snmpEngineTime: 54591
// SNMP received an SNMPv3 request.
# Enable information center debugging and received SNMP packet debugging on the device. Output
similar to the following example is generated when network management software is used to perform a
Get operation on object sysUpTime.0 under these conditions:
•
SNMPv2c is enabled.
•
A community name is configured.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp agent packet receive
*Jul 27 08:58:52:594 2007 Sysname SNMP/7/PACKET_SRC:
packet received from 10.165.81.75 via UDP
*Jul 27 08:58:52:594 2007 Sysname SNMP/7/PACKET:
get request
request-id: 13
error-status: 0
error-index: 0
*Jul 27 08:58:52:594 2007 Sysname SNMP/7/VBLIST:
sysUpTime.0:
// SNMP received an SNMP request from 10.165.81.75 through UDP.
# Enable information center debugging and sent SNMP packet debugging on the device. Output similar
to the following example is generated when network management software is used to perform a Get
operation on object sysUpTime.0 under these conditions:
•
SNMPv2c is enabled.
•
A community name is configured.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp agent packet send
*Jul 27 09:08:21:563 2007 Sysname SNMP/7/PACKET:
response
request-id: 16
error-status: 0
394
error-index: 0
*Jul 27 09:08:21:563 2007 Sysname SNMP/7/VBLIST:
sysUpTime.0: 5563114
*Jul 27 09:08:21:563 2007 Sysname SNMP/7/PACKET_DES:
packet sent to 10.165.81.75 via UDP
// SNMP sent an SNMP response to 10.165.81.75 through UDP.
debugging snmp agent process
Use debugging snmp agent process to enable debugging for SNMP packet processing.
Use undo debugging snmp agent process to disable debugging for SNMP packet processing.
Syntax
debugging snmp agent process { all | decode | stack | txrx } [ error | info | warning ]
undo debugging snmp agent process { all | decode | stack | txrx } [ error | info | warning ]
Default
SNMP packet processing debugging is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
all: Enables debugging for all SNMP packet processing, including decode, stack, and txrx.
decode: Enables debugging for decoding an SNMP request.
stack: Enables debugging for handling the SNMP request PDU.
txrx: Enables debugging for transmitting or receiving an SNMP message.
error: Enables error-level debugging to output error debugging information, which indicates the error
information generated during the running of the SNMP stack or the system.
info: Enables info-level debugging to output informational debugging information, which indicates the
prompt information generated during the running of the SNMP stack or the system.
warning: Enables warning-level debugging to output warning debugging information, which indicates
the important information generated during the running of the SNMP stack or the system.
Usage guidelines
If you do not specify the level of the debugging information, debugging information for all levels will be
output or disabled.
Table 4 describes output fields and messages for the debugging snmp agent process decode command.
Table 200 Output from the debugging snmp agent process decode command
Field
Description
DECODE_INFO
Info-level debugging information generated during
the SNMP request decoding process.
395
Field
Description
DECODE_WARNING
Warning-level debugging information generated
during the SNMP request decoding process.
DECODE_ERROR
Error-level debugging information generated during
the SNMP request decoding process.
Table 5 describes output fields and messages for the debugging snmp agent process txrx command.
Table 201 Output from the debugging snmp agent process txrx command
Field
Description
TXRX_INFO
Info-level debugging information generated when SNMP
messages were being sent and received.
TXRX_WARNING
Warning-level debugging information generated when
SNMP messages were being sent and received.
TXRX_ERROR
Error-level debugging information generated when SNMP
messages were being sent and received.
failed to set IPv6 socket option while creating
IPv6 socket (errCode: error-code)
This IPv6 socket option determines whether the IP address
and port number used by this socket can be bound with
another socket.
failed to set IPv4 socket option while receiving
PDU through IPv4 socket
This IPv4 socket option determines whether the destination IP
address can be parsed out from the received packet.
Table 6 describes output fields and messages for the debugging snmp agent process stack command.
Table 202 Output from the debugging snmp agent process stack command
Field
Description
STACK_INFO
Info-level debugging information generated when the SNMP
request PDU is being handled.
STACK_WARNING
Warning-level debugging information generated when the
SNMP request PDU is being handled.
STACK_ERROR
Error-level debugging information generated when the SNMP
request PDU is being handled.
create CFG message for get-request and
parse CFG message for response
CFG is an abbreviation of configuration.
get value from CFG message (CMO type:
CMO-type)
CMO is an abbreviation of Configuration Management
Object.
parameter number parameter-number from
CFG message less than index number
index-number
Number of parameters from the CFG message is smaller than
the number of parameters from the indexes.
The number of users who can set reaches the
limit.
Number of users who can perform the set operation has
reached the upper limit.
Examples
# Enable information center debugging and info-level SNMP PDU debugging on the device. Output
similar to the following example is generated when network management software is used to perform a
Get operation on object sysUpTime under these conditions:
396
•
SNMPv2c is enabled.
•
A community name is configured.
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp agent process stack info
<Sysname>
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
read request
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
PDU type is 160 and PDU version is 1.
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
make request
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
process request
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
get instance sysUpTime.0
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
create CFG message for get-request and parse CFG message for response
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
create CFG message
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
create CFG message for leaf node
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
get instance sysUpTime.0 in batch way
*Jul 27 09:42:13:578 2007 Sysname SNMP/7/STACK_INFO:
parse CFG message and fill variable-bindings
*Jul 27 09:42:13:594 2007 Sysname SNMP/7/STACK_INFO:
get value from CFG message (CMO type: 3)
*Jul 27 09:42:13:594 2007 Sysname SNMP/7/STACK_INFO:
convert data type 43 from CFG message
*Jul 27 09:42:13:594 2007 Sysname SNMP/7/STACK_INFO:
fill variable-bindings
*Jul 27 09:42:13:594 2007 Sysname SNMP/7/STACK_INFO:
send response to NMS (errStatus: 0, errIndex: 0)
// Info-level debugging information was generated during the process of handling the SNMP request
PDU and generating the response.
debugging snmp trap packet
Use debugging snmp trap packet to enable debugging for SNMP trap messages.
Use undo debugging snmp trap packet to disable debugging for SNMP trap messages.
Syntax
debugging snmp trap packet
undo debugging snmp trap packet
397
Default
Debugging for SNMP trap messages is disabled.
Views
User view
Default command level
1: Monitor level
Usage guidelines
Table 7 describes output fields and messages for the debugging snmp trap packet command.
Table 203 Output from the debugging snmp trap packet command
Field
Description
TRAP_PACKET
Trap message debugging information.
The system sent the trap-name trap message to address.
trap-name trap<version> send to:
address
• trap-name—Name of the trap message.
• version—Trap version, which is v1 or v2c.
• address—Destination IP address.
request-id: request-id
The request-id field of the trap PDU. The value of the field is always 0.
error-status: error-status
The error-status field of the trap PDU. The value of the field is always
0.
error-index: error-index
The error-index field of the trap PDU. The value of the field is always
0.
UDP port: port-number
UDP port number of the destination host for receiving the trap
messages.
send OK
Traps were sent successfully.
VBLIST
Variable binding list in the trap message.
Examples
# Enable information center debugging and SNMP trap message debugging on the device enabled with
the SNMP trap sending function. When the undo snmp-agent command and the snmp-agent command
are executed in system view, output similar to the following example is generated:
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp trap packet
[Sysname] undo snmp-agent
[Sysname] snmp-agent
[Sysname]
*Jul 27 10:10:35:297 2007 Sysname SNMP/7/TRAP_PACKET:
warmStart trap<v2> send to: 10.165.81.75
request-id: 0
error-status: 0
error-index: 0
UDP port: 162
398
send OK
*Jul 27 10:10:35:297 2007 Sysname SNMP/7/VBLIST:
sysUpTime.0: 5936387
*Jul 27 10:10:35:297 2007 Sysname SNMP/7/VBLIST:
snmpTrapOID.0: 1.3.6.1.6.3.1.1.5.2
// The device sent the version 2 trap message to the destination host 10.165.81.75.
The trap message was sent successfully, and the values of the binding variables sysUpTime.0 and
snmpTrapOID.0 are 5936387 and 1.3.6.1.6.3.1.1.5.2, respectively
debugging snmp trap process
Use debugging snmp trap process to enable debugging for the SNMP trap task.
Use undo debugging snmp trap process to disable debugging for the SNMP trap task.
Syntax
debugging snmp trap process [ error | info | warning ]
undo debugging snmp trap process [ error | info | warning ]
Default
Debugging for the SNMP trap task is disabled.
Views
User view
Default command level
1: Monitor level
Parameters
error: Specifies error debugging for the SNMP trap task.
info: Specifies info debugging for the SNMP trap task.
warning: Specifies warning debugging for the SNMP trap task.
Usage guidelines
If you do not specify the level of debugging information, debugging information for all levels will be
output or disabled.
Table 8 describes output fields and messages for the debugging snmp trap process command.
Table 204 Output from the debugging snmp trap process command
Field
Description
TRAP_INFO
Info-level debugging information generated during the trap task
implementation process.
TRAP_WARNING
Warning-level debugging information generated during the trap
task implementation process.
TRAP_ERROR
Error-level debugging information generated during the trap task
implementation process.
wrong number of parameters in
trap-name's trap message
Number of parameters in the trap message is incorrect.
399
Field
filter address address for sending
trap-name
Description
Trap messages whose destination address is address are filtered
when trap messages are being sent.
• trap-name—Name of the trap node.
• address—Destination IP address of trap messages.
Examples
# Enable information center debugging and SNMP trap module debugging on the device enabled with
the SNMP trap sending function. When the undo snmp-agent command and the snmp-agent command
are executed in system view, output similar to the following example is generated:
<Sysname> terminal debugging
% Current terminal debugging is on
<Sysname> terminal monitor
% Current terminal monitor is on
<Sysname> debugging snmp trap process info
[Sysname] undo snmp-agent
[Sysname] snmp-agent
[Sysname]
*Jul 27 10:21:22:938 2007 Sysname SNMP/7/TRAP_INFO:
send trap message to trap queue
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
create trap IPv4 socket
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
create trap IPv6 socket
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
handle trap message in trap queue at 10:21:22
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
parse trap message
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/STACK_INFO:
get value from CFG message (CMO type: 7)
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
get trap's index-lists
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
build warmStart's variable-bindings
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
get generic trap type
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
prepare to generate and send trap warmStart
*Jul 27 10:21:22:984 2007 Sysname SNMP/7/TRAP_INFO:
search entries in snmpTargetAddrTable to match snmpNotifyTag TrapHost
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
search entries in snmpTargetParamsTable to match snmpTargetAddrParams
traphost.u2.192.168.123.123
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
check trap warmStart's VACM
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
get source IPv4 address for sending trap
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
400
search entries in snmpTargetParamsTable to match snmpTargetAddrParams
traphost.uu.10.165.81.75
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
check trap warmStart's VACM
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
get source IPv4 address for sending trap
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
create warmStart packet
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
get enterprise OID
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
encode SNMPv2c trap
*Jul 27 10:21:23:00 2007 Sysname SNMP/7/TRAP_INFO:
send trap through IPv4 socket
*Jul 27 10:21:23:16 2007 Sysname SNMP/7/TRAP_INFO:
send warmStart successfully at 10:21:22
// The SNMP trap module handled the trap task, output the info-level debugging information, and sent
the warmStart trap message.
401
Spanning tree debugging commands
The output description tables in this document only contain fields and messages that require an
explanation.
debugging stp all
Use debugging stp all to enable all types of STP debugging.
Use undo debugging stp all to disable all types of STP debugging.
Syntax
debugging stp all
undo debugging stp all
Default
All types of STP debugging are disabled.
Views
User view
Default command level
2: System level
Examples
# Enable all types of STP debugging.
<Sysname> debugging stp all
debugging stp event
Use debugging stp event to enable STP event debugging.
Use undo debugging stp event to disable STP event debugging.
Syntax
debugging stp event [ interface interface-type interface-number ]
undo debugging stp event [ interface interface-type interface-number ]
Default
STP event debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
interface interface-type interface-number: Specifies a port by its type and number. If you do not specify
a port, this command enables STP event debugging for all ports.
402
Usage guidelines
Table 1 describes output fields and messages for the debugging stp event command.
Table 205 Output from the debugging stp event command
Field
Description
A String event occurred on port PortID. The possible values of the String
argument are:
Port PortID occurs String event
•
•
•
•
•
•
ADD VLAN—The port was assigned to a VLAN.
DEL VLAN—The port was removed from a VLAN.
SPEED CHANGE—The port speed changed.
DUPLEX CHANGE—The duplex mode of the port changed.
LINK DOWN—A link-down event occurred on the port.
LINK UP—A link-up event occurred on the port.
Examples
# Enable STP event debugging for port Ethernet 1/1.
<Sysname> debugging stp event interface ethernet 1/1
*Mar 18 14:28:41:887 2010 Sysname MSTP/7/PEVT: Slot=1;Port 2(Ethernet1/1) occurs LINK DOWN
event
// A link-down event occurred on Ethernet 1/1.
debugging stp fsm
Use debugging stp fsm to enable STP finite state machine (FSM) debugging.
Use undo debugging stp fsm to disable STP FSM debugging.
Syntax
debugging stp fsm [ instance instance-id | vlan vlan-id ] [ interface interface-type interface-number ]
undo debugging stp fsm [ instance instance-id | vlan vlan-id ] [ interface interface-type
interface-number ]
Default
STP FSM debugging is disabled.
Views
User view
Default command level
2: System level
Parameters
instance instance-id: Specifies an MSTI. The instance-id argument represents the MSTI ID. The minimum
value of this argument is 0, which represents the common internal spanning tree (CIST). The maximum
value depends on the device model. If you do not specify an MSTI, this command enables STP FSM
debugging for all MSTIs. This option is not applicable to the PVST mode.
vlan vlan-id: Specifies a VLAN by its ID. The value range for the vlan-id argument varies with device
models. If you do not specify a VLAN, this command enables STP FSM debugging for all VLANs. This
option is only applicable to the PVST mode.
403
interface interface-type interface-number: Specifies a port by its type and number. If you do not specify
a port, this command enables STP FSM debugging for all ports.
Usage guidelines
Table 2 describes output fields and messages for the debugging stp fsm command.
Table 206 Output from the debugging stp fsm command
Field
Description
The state of port PortID(PortName) on MSTI InstanceID or VLAN VLANID is
String. The possible values of the String argument are:
Instance InstanceID's port
PortID(PortName) enters String
state
VLAN VLANID's port
PortID(PortName) enters String
state
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
PIM%ENABLED
PIM%AGED
PIM%CURRENT
PIM%RECEIVED
PIM%SUPERIOR_DESIGNATED
PIM%REPEATED_DESIGNATED
PIM%ROOT
PIM%OTHER
PPM%SEND_RSTP
PPM%SENDING_RSTP
PPM%SEND_STP
PPM%SENDING_STP
PRT%BLOCK_PORT
PRT%BLOCKED_PORT
PRT%BACKUP_PORT
PRT%ACTIVE_PORT
PRT%PROPOSED
PRT%PROPOSING
PRT%AGREES
PRT%SYNCED
PRT%LEARN
PRT%FORWARD
PRT%REROOT
PRT%LISTEN
PRT%REROOTED
PRT%ROOT
TCM%INIT
TCM%INACTIVE
TCM%DETECTED
TCM%ACTIVE
TCM%NOTIFIED_TCN
TCM%NOTIFIED_TC
TCM%PROPAGATING
TCM%ACKNOLEDGED.
The percent sign (%) is preceded by the state machine name and followed
by the state machine state.
404
Field
Instance InstanceID's port
PortID(PortName) is selected as
String role
VLAN VLANID's port
PortID(PortName) is selected as
String role
Description
The role of port PortID(PortName) on MSTI InstanceID or VLAN VLANID is
String. The possible values of the String argument are:
•
•
•
•
•
DESIGNATED—The port is a designated port.
ROOT—The port is a root port.
ALTERNATE—The port is an alternate port.
BACKUP—The port is a backup port.
MASTER—The port is a master port.
Examples
# In MSTP mode, enable STP FSM debugging for all ports in MSTI 2.
<Sysname> debugging stp fsm instance 2
*Mar 18 14:28:41:739 2010 Sysname MSTP/7/MEXS:Slot=1;Instance 2's port105(Ethernet1/1)
enters PTX%PERIODIC state.
// Ethernet 1/1's PTX state machine in MSTI 2 was moved to the PERIODIC state.
*Mar 18 14:28:41:739 2010 Sysname MSTP/7/MEXS:Slot=1;Instance 2's port105(Ethernet1/1)
enters PTX%MSTP state.
// Ethernet 1/1's PTX state machine in MSTI 2 was moved to the MSTP state.
*Mar 18 14:28:41:741 2010 Sysname MSTP/7/MEXS:Slot=1;Instance 2's port105(Ethernet1/1)
enters PTX%PERIODIC state.
// Ethernet 1/1's PTX state machine in MSTI 2 was moved to the PERIODIC state.
*Mar 18 14:28:41:741 2010 Sysname MSTP/7/MEXS:Slot=1;Instance 2's port105(Ethernet1/1)
is selected as MASTER role
// Ethernet 1/1 was selected as the master port in MSTI 2.
# In PVST mode, enable STP FSM debugging for all ports in VLAN 2.
<Sysname> debugging stp fsm vlan 2
*Mar 18 14:28:41:739 2010 Sysname MSTP/7/MEXS:Slot=1;VLAN 2's port105(Ethernet1/1) enters
PTX%PERIODIC state.
// Ethernet 1/1's PTX state machine on VLAN 2 was moved to the PERIODIC state.
*Mar 18 14:28:41:739 2010 Sysname MSTP/7/MEXS:Slot=1;VLAN 2's port105(Ethernet1/1) enters
PTX%MSTP state.
// Ethernet 1/1's PTX state machine on VLAN 2 was moved to the MSTP state.
*Mar 18 14:28:41:741 2010 Sysname MSTP/7/MEXS:Slot=1;VLAN 2's port105(Ethernet1/1) enters
PT