5-127
Cisco Broadband Cable Command Reference Guide
OL-1581-08
Chapter 5 Cisco CMTS Debugging Commands
debug packetcable gate
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to set gate state to 3 in upstream direction for
gate handle 622D3650
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to transition gate ID 2430632 direction upstream
to state 3
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to set gate state to 3 in downstream direction
for gate handle 622D3650
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to transition gate ID 2430632 direction
downstream to state 3
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to set gate state to 3 in upstream direction for
gate handle 622C3EF8
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to transition gate ID 2359392 direction upstream
to state 3
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to set gate state to 3 in downstream direction
for gate handle 622C3EF8
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to transition gate ID 2359392 direction
downstream to state 3
Jul 25 16:17:29 UTC: Pktcbl(gdb): request to transition gate ID 2430632 direction upstream
to state 4
Jul 25 16:17:29 UTC: Pktcbl(gdb): Started gate [id 2430632] timert2 [2000000 ms]
Jul 25 16:17:29 UTC: Pktcbl(gdb): Started gate [id 2430632] timer t5 [500 msec]
Jul 25 16:17:29 UTC: Pktcbl(gdb): Cancelled gate [id 2430632] timer t1
Jul 25 16:17:29 UTC: Pktcbl(gdb): Cancelled gate [id 2430632] timer t2
Jul 25 16:17:29 UTC: Pktcbl(gdb): Cancelled gate [id 2430632] timer t5
DOCSIS-to-RSVP Mapping Debugging
The following example shows typical debugging messages for the mapping between DOCSIS and RSVP
messages:
Router#
debug packetcable subscriber 192.168.78.21
Router#
debug packetcable docsis-mapping
Pktcbl rsvp-to-docsis msgs debugging is on
Jul 25 16:17:33 UTC: Pktcbl(d2r): rsvp->docsis: Received a DOCSIS_RESERVE request
Jul 25 16:17:33 UTC: Pktcbl(d2r): rsvp->docsis: Received a DOCSIS_RESERVE request
Jul 25 16:17:33 UTC: Pktcbl(d2r): docsis->rsvp, DSA received, gateid: 2430632
Jul 25 16:17:33 UTC: Pktcbl(d2r): Notifying RSVP layer of CM initiated req
[api_msg.opcode: 4]
Jul 25 16:17:33 UTC: Pktcbl(d2r): docsis->rsvp, DSA received, gateid: 2359392
Jul 25 16:17:33 UTC: Pktcbl(d2r): Notifying RSVP layer of CM initiated req
[api_msg.opcode: 4]
Jul 25 16:17:33 UTC: Pktcbl(d2r): rsvp->docsis: Received a DOCSIS_COMMIT request
Jul 25 16:17:33 UTC: Pktcbl(d2r): rsvp->docsis: Received a DOCSIS_COMMIT request
Jul 25 16:17:33 UTC: Pktcbl(d2r): request to transition gate ID 2359392 direction upstream
to state 4
Event Message Debugging
The following example shows typical debugging messages for event messages:
Router#
debug packetcable subscriber 192.168.78.21
Router#
debug packetcable events
Pktcbl event msgs debugging is on
Jul 25 16:14:41 UTC: Pktcbl(em): RKS send call-answer for gate_id=2430632
Jul 25 16:14:41 UTC: Pktcbl(em): pktcbl_send_event() event_type=CALL_ANSWER port=0
Jul 25 16:14:41 UTC: Pktcbl(em): add_attributes, attr_id=1
Jul 25 16:14:41 UTC: Pktcbl(em): add_attributes(ATTR_HEADER)
Jul 25 16:14:41 UTC: Pktcbl(em): pktcbl_add_header(): seq_no=136
event_time=19170628064103.06 event_msg_type=15
Jul 25 16:14:41 UTC: Pktcbl(em): add_attributes, attr_id=5
Jul 25 16:14:41 UTC: Pktcbl(em): add_attributes(ATTR_PARTY_NUMBER)
Jul 25 16:14:41 UTC: Pktcbl(em): length=28, vendor_attr_length=22
Jul 25 16:14:41 UTC: Pktcbl(em): add_attributes, attr_id=16
Jul 25 16:14:41 UTC: Pktcbl(em): add_attributes(ATTR_CHARGE_NUMBER)