NCPROUTE trace example and explanation

Figure 1 shows an example of an NCPROUTE trace with actions, packets, history, and contents traced. The trace was generated with trace level 4 specified in the OPTIONS statement and PARMS='/-t -t -dp' in the PROC statement of the NCPROUTE cataloged procedure.

The trace level column does not appear in the actual trace. It was added to the example to indicate the levels of the trace for which the line is generated. For example, including: trace.level 3 on the options statement NCP client GATEWAYS data set would result in a level 3 trace, and all of the lines indicated as trace level 1, 2, or 3 would be generated in the trace output. Lines indicated as trace level d are generated if the -dp parameter is specified.

Figure 1. NCPROUTE trace

Trace
level
0      1 15:29:48 EZB3826I Port 580 assigned to ncprout
0        15:29:49 EZB3885I Input parameter(s): -t -t -dp
1        15:29:49 EZB4159I Global tracing actions started
2        15:29:49 EZB4160I Global tracing packets started
0        15:29:49 EZB3834I ******************************************************
0      2 15:29:49 EZB4196I * Opening NCPROUTE profile dataset (DD:NCPRPROF)
0        15:29:49 EZB3834I ******************************************************
0      3 15:29:49 EZB4055I ** Attempting to (re)start SNMP connection
0        15:29:49 EZB4059I Connecting to agent 9.67.116.66 on DPI port 1141
0        15:29:49 EZB4062I SNMP DPI connection established
0        15:29:50 EZB4064I 1.3.6.1.4.1.2.6.17. registered with SNMP agent0
1        15:29:50 EZB3829I Waiting for incoming packets
d      4 =============== Received datagram from NCP client (length=32)
d        0000    0100 0000 c1f0 f4d5
d        0008    f7f1 f1d7 f0f5 61f0
d        0010    f661 f9f4 40f1 f07a
d        0018    f1f0 7af4 f200 0000
d        0020(32)
0        15:29:51 EZB3834I ******************************************************
0        15:29:51 EZB3876I * Hello from new client 9.67.116.65
0        15:29:51 EZB3877I * RIT dataset name: A04N711P
0        15:29:51 EZB3878I * RIT ID:  05/06/94 10:10:42
0        15:29:51 EZB3834I ******************************************************
0        15:29:51 EZB3867I Acknowledge to 9.67.116.65: Hello Received
0        15:29:51 EZB3999I Establishing session with client 9.67.116.65
0        15:29:51 EZB3868I Acknowledge to 9.67.116.65: RIT Loaded OK
0        15:29:51 EZB4166I Session with client 9.67.116.65 started
1        15:29:51 EZB3829I Waiting for incoming packets
1        =============== Received datagram from NCP client (length=8)
d        0000    0800 0000 0a44 005c
d        0008(8)
0        15:29:51 EZB3834I ******************************************************
0      5 15:29:51 EZB3898I * Recv:  Inactive Interface List from 9.67.116.65
0                          * 1 interface(s) found:
0        15:29:51 EZB3899I *   10.68.0.92 - TR92
0        15:29:51 EZB3834I ******************************************************
0        15:29:51 EZB3834I ******************************************************
0      6 15:29:51 EZB3956I * Processing interface NCSTALU1
0        15:29:51 EZB3834I ******************************************************
0        15:29:51 EZB3959I Point-to-point interface, using dstaddr
0        15:29:51 EZB3962I Adding (sub)network address for interface
1        15:29:51 EZB3912I ifwithnet:  compare with NCSTALU1
1        15:29:51 EZB3915I netmatch 9.67.116.65 and 9.67.116.65
1        15:29:51 EZB4029I Tue Jun 28 15:29:51:
1      7 15:29:52 EZB4030I ADD destination 9.67.116.66, router 9.67.116.66, metric 1
1                          flags UP|HOST state INTERFACE|CHANGED|INTERNAL|PERM|SUBNET timer 0

0        15:29:52 EZB3834I ******************************************************
0        15:29:52 EZB3956I * Processing interface TR88
0        15:29:52 EZB3834I ******************************************************
0        15:29:52 EZB3960I This interface is not point-to-point
0        15:29:52 EZB3962I Adding (sub)network address for interface
1        15:29:52 EZB3912I ifwithnet:  compare with NCSTALU1
1        15:29:52 EZB3912I ifwithnet:  compare with TR88
1        15:29:52 EZB3915I netmatch 10.68.0.88 and 10.68.0.88
1        15:29:52 EZB4030I ADD destination 10.0.0.0, router 10.68.0.88, metric 1
1                          flags UP state INTERFACE|CHANGED|INTERNAL|SUBNET|PERM timer 0
1        15:29:52 EZB3912I ifwithnet:  compare with NCSTALU1
1        15:29:52 EZB3912I ifwithnet:  compare with TR88
1        15:29:52 EZB3915I netmatch 10.68.0.88 and 10.68.0.88
1        15:29:52 EZB4030I ADD destination 10.68.0.0, router 10.68.0.0, metric 1
1                          flags UP state INTERFACE|CHANGED|SUBNET|PERM timer 0
0        15:29:52 EZB3834I ******************************************************
0        15:29:52 EZB3956I * Processing interface TR92
0        15:29:52 EZB3834I ******************************************************
0        15:29:52 EZB3960I This interface is not point-to-point
0        15:29:52 EZB3948I Interface TR92 not up
0        15:29:52 EZB3834I ******************************************************
0      8 15:29:52 EZB3973I * Opening GATEWAYS dataset for client 9.67.116.65
0                          *   'TCPCS.NCPROUTE.GATEWAYS(A04N711P)'
0        15:29:52 EZB3834I ******************************************************
0        15:29:52 EZB3968I Start of GATEWAYS processing:
0        15:29:52 EZB4195I Option(s): trace.level 4 supply on default.router no
1        15:29:52 EZB4015I Client tracing actions started
2        15:29:52 EZB4016I Client tracing packets started
3        15:29:52 EZB4017I Client tracing history started
4        15:29:52 EZB4018I Client tracing packet contents started
0        15:29:52 EZB4198I (no etc.gateway definitions)
0        15:29:52 EZB4150I End of GATEWAYS processing
1        15:29:52 EZB3829I Waiting for incoming packets
d      9 =============== Received datagram from NCP client (length=80)
d     10 0000    0700 0000 9200 004a
         0008    4500 0048 09c0 0000
d        0010    3c11 79dc 0943 7442
d        0018    0943 7441 0208 0208
d        0020    0034 079e 0201 0000
d        0028    0002 0000 0943 7441
d        0030    0000 0000 0000 0000
d        0038    0000 0001 0002 0000
d        0040    0943 7000 0000 0000
d        0048    0000 0000 0000 0001
d        0050(80)
d        =============== Transport PDU header (length=8)
d        0000    0700 0000 9200 004a
d        0008(8)
d        =============== IP header (length=20)
d        0000    4500 0048 09c0 0000
d        0008    3c11 79dc 0943 7442
d        0010    0943 7441 8002 c12c
d        0018(24)

d        =============== UDP header (length=8)
d        0000    0208 0208 0034 079e
d        0008(8)
d        =============== UDP data (length=44)
d        0000    0201 0000 0002 0000
d        0008    0943 7441 0000 0000
d        0010    0000 0000 0000 0001
d        0018    0002 0000 0943 7000
d        0020    0000 0000 0000 0000
d        0028    0000 0001 0001 6e68
d        0030(48)
1     11 15:30:04 EZB3894I Transport from 9.67.116.65:  44 bytes of RIP data
2        15:30:04 EZB4045I     RESPONSE from 9.67.116.66 -> 520:
d     12 =============== RIP net info (length=20)
d        0000    0002 0000 0943 7441
d        0008    0000 0000 0000 0000
d        0010    0000 0001 8002 c12c
d        0018(24)
4        15:30:04 EZB4049I         destination 9.67.116.65 metric 1
d        =============== RIP net info (length=20)
d        0000    0002 0000 0943 7000
d        0008    0000 0000 0000 0000
d        0010    0000 0001 8002 c12c
4        0018(24)
1        15:30:04 EZB4049I         destination 9.67.112.0 metric 1
1        15:30:04 EZB4029I Tue Jun 28 15:30:04:
1     13 15:30:04 EZB4030I ADD destination 9.67.112.0, router 9.67.116.66, metric 2
1                          flags UP|GATEWAY state CHANGED|SUBNET timer 0
1     14 15:30:04 EZB3855I NCP_Add out to 9.67.116.65
1                          Route to: 9.67.112.0 via interface 9.67.116.65 to 9.67.116.66
1                          Metric: 2, Type Subnet
1        15:30:04 EZB3829I Waiting for incoming packets
1     15 15:30:20 EZB4011I client 9.67.116.65:  30 second timer expired (broadcast)
1        15:30:20 EZB3951I client 9.67.116.65:  supply 9.67.116.66 -> 0 via NCSTALU1
4     16 15:30:20 EZB4045I     RESPONSE to 9.67.116.66 -> 0:
d        =============== RIP net info (length=20)
d        0000    0002 0000 0943 7442
d        0008    0000 0000 0000 0000
d        0010    0000 0001 8002 c12c
d        0018(24)
4        15:30:20 EZB4049I         destination 9.67.116.66 metric 1
d        =============== RIP net info (length=20)
d        0000    0002 0000 0a00 0000
d        0008    0000 0000 0000 0000
d        0010    0000 0001 8002 c12c
d        0018(24)
4        15:30:20 EZB4049I         destination 10.0.0.0 metric 1
d        =============== RIP net info (length=20)
d        0000    0002 0000 0943 7000
d        0008    0000 0000 0000 0000
d        0010    0000 0002 8002 c12c
d        0018(24)
4        15:30:20 EZB4049I         destination 9.67.112.0 metric 2

d        =============== UDP data (length=64)
d        0000    0201 0000 0002 0000
d        0008    0943 7442 0000 0000
d        0010    0000 0000 0000 0001
d        0018    0002 0000 0a00 0000
d        0020    0000 0000 0000 0000
d        0028    0000 0001 0002 0000
d        0030    0943 7000 0000 0000
d        0038    0000 0000 0000 0002
d        0040(64)
d        =============== UDP header (length=8)
d        0000    0208 0208 0048 fd70
d        0008(8)
d        =============== IP header (length=20)
d        0000    4500 005c 0000 0000
d        0008    0411 bb88 0943 7441
d        0010    0943 7442 8002 c12c
d        0018(24)
d        =============== Transport PDU header (length=8)
d        0000    0700 0000 0943 7441
d        0008(8)
d        =============== Sending Transport PDU to NCP client (length=100)
d        0000    0700 0000 0943 7441
d        0008    4500 005c 0000 0000
d        0010    0411 bb88 0943 7441
d        0018    0943 7442 0208 0208
d        0020    0048 fd70 0201 0000
d        0028    0002 0000 0943 7442
d        0030    0000 0000 0000 0000
d        0038    0000 0001 0002 0000
d        0040    0a00 0000 0000 0000
d        0048    0000 0000 0000 0001
d        0050    0002 0000 0943 7000
d        0058    0000 0000 0000 0000
d        0060    0000 0002 0000 0001
d        0068(104)
⋮
1    17 15:30:20 EZB3948I Interface TR92 not up
1       15:30:20 EZB3829I Waiting for incoming packets
                             .
1       15:30:20 EZB3894I Transport from 9.67.116.65:  64 bytes of RIP data
2       15:30:20 EZB4045I     RESPONSE from 10.68.0.88 -> 520:
                             .
4       15:30:20 EZB4049I         destination 9.67.116.66 metric 1
                             .
4       15:30:20 EZB4049I         destination 10.68.0.0 metric 1
                             .
4       15:30:20 EZB4049I         destination 9.67.112.0 metric 2
1       15:30:20 EZB3829I Waiting for incoming packets
                             .
                             .
                             .

1        15:30:34 EZB3829I Waiting for incoming packets
1        15:30:50 EZB4011I client 9.67.116.65:  30 second timer expired (broadcast)
1        15:30:50 EZB3951I client 9.67.116.65:  supply 9.67.116.66 -> 0 via NCSTALU1
2        15:30:50 EZB4045I     RESPONSE to 9.67.116.66 -> 0:
                             .
4        15:30:50 EZB4049I         destination 9.67.116.66 metric 1
                             .
4        15:30:50 EZB4049I         destination 10.0.0.0 metric 1
                             .
4        15:30:50 EZB4049I         destination 9.67.112.0 metric 2
                             .
1        15:30:50 EZB3951I client 9.67.116.65:  supply 10.68.15.255 -> 0 via TR88
2        15:30:50 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
4        15:30:50 EZB4049I         destination 9.67.116.66 metric 1
                             .
4        15:30:50 EZB4049I         destination 10.68.0.0 metric 1
                             .
4        15:30:50 EZB4049I         destination 9.67.112.0 metric 2
⋮
1        15:32:35 EZB3894I Transport from 9.67.116.65:  64 bytes of RIP data
2        15:32:35 EZB4045I     RESPONSE from 9.67.116.66 -> 520:
                             .
4        15:32:35 EZB4049I         destination 9.67.116.65 metric 1
                             .
4        15:32:35 EZB4049I         destination 10.0.0.0 metric 2
                             .
4        15:32:35 EZB4049I         destination 9.67.112.0 metric 16
1        15:32:35 EZB4029I Tue Jun 28 15:32:35:
1     18 15:32:35 EZB4036I CHANGE metric destination 9.67.112.0, router 9.67.116.66, from 2 to 16
      19 15:32:35 EZB3862I NCP_Delete out to 9.67.116.65:
                           Route to 9.67.112.0, type = Subnet
1        15:32:35 EZB3943I Send dynamic update
1        15:32:35 EZB3950I toall:  requested to skip interface NCSTALU1
1        15:32:35 EZB3951I client 9.67.116.65:  supply 10.68.15.255 -> 0 via TR88
2        15:32:35 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
4        15:32:35 EZB4049I         destination 9.67.112.0 metric 16
                             .
1        15:32:35 EZB3948I Interface TR92 not up
1        15:32:35 EZB3945I Inhibit dynamic update for 2017537 usec
1        15:32:35 EZB3829I Waiting for incoming packets
                             .
1        15:32:35 EZB3894I Transport from 9.67.116.65:  24 bytes of RIP data
1        15:32:35 EZB4045I     RESPONSE from 10.68.0.88 -> 520:
                             .
4        15:32:35 EZB4049I         destination 9.67.112.0 metric 16
1        15:32:35 EZB3829I Waiting for incoming packets

1        15:32:50 EZB4011I client 9.67.116.65:  30 second timer expired (broadcast)
1        15:32:50 EZB3951I client 9.67.116.65:  supply 9.67.116.66 -> 0 via NCSTALU1
2        15:32:50 EZB4045I     RESPONSE to 9.67.116.66 -> 0:
                             .
4        15:32:50 EZB4049I         destination 9.67.116.66 metric 1
                             .
4        15:32:50 EZB4049I         destination 10.0.0.0 metric 1
                             .
4        15:32:50 EZB4049I         destination 9.67.112.0 metric 16
         15:32:50 EZB3951I client 9.67.116.65:  supply 10.68.15.255 -> 0 via TR88
2        15:32:50 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
1        15:32:50 EZB3948I Interface TR92 not up
1        15:32:50 EZB3829I Waiting for incoming packets
⋮
1        15:36:15 EZB3829I Waiting for incoming packets
1     20 15:36:39 EZB4009I client 9.67.116.65:  5 minute timer expired for route to 9.67.112.0
1        15:36:39 EZB4029I Tue Jun 28 15:36:39:
1     21 15:36:39 EZB4030I DELETE destination 9.67.112.0, router 9.67.116.66, metric 16
1                          flags UP|GATEWAY state SUBNET timer 300
1        15:36:39 EZB4011I client 9.67.116.65:  30 second timer expired (broadcast)
1        15:36:39 EZB3951I client 9.67.116.65:  supply 9.67.116.66 -> 0 via NCSTALU1
2        15:36:39 EZB4045I     RESPONSE to 9.67.116.66 -> 0:
                             .
4        15:36:39 EZB4049I         destination 9.67.116.66 metric 1
                             .
4        15:36:39 EZB4049I         destination 10.0.0.0 metric 1
                             .
1        15:36:39 EZB3951I client 9.67.116.65:  supply 10.68.15.255 -> 0 via TR88
2        15:36:39 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
4        15:36:39 EZB4049I         destination 9.67.116.66 metric 1
                             .
4        15:36:39 EZB4049I         destination 10.68.0.0 metric 1
⋮
1     22 15:43:01 EZB3895I Transport from 9.67.116.65:  43 bytes of SNMP data
1     23 15:43:01 EZB4182I SNMP request received from NCP client 9.67.116.65
d        =============== Object data (length=13)
d        0000    2b06 0102 0104 1501
d        0008    0709 4374 4207 39f8
d        0010(16)
d        =============== prefix + address (length=12)
d        0000    2b06 0104 0102 0611
d        0008    0943 7441 4207 39f8
d        0010(16)

d    =============== Inbound SNMP packet (post edit) (length=55)
d    0000 3035 0201 0004 0473
d    0008    6e6d 70a0 2a02 0115
d    0010    0201 0002 0100 301f
d    0018    301d 0619 2b06 0104
d    0020    0102 0611 0943 7441
d    0028    2b06 0102 0104 1501
d    0030    0709 4374 4205 0000
d    0038(56)
d    =============== Sending SNMP request to agent (length=55)
d    0000    3035 0201 0004 0473
d    0008    6e6d 70a0 2a02 0115
d    0010    0201 0002 0100 301f
d    0018    301d 0619 2b06 0104
d    0020    0102 0611 0943 7441
d    0028    2b06 0102 0104 1501
d    0030    0709 4374 4205 00f3
d    0038(56)
1    15:43:01 EZB3829I Waiting for incoming packets
1    15:43:01 EZB4194I SNMP sub-agent received DPI request
d    =============== Received DPI request from SNMP agent (length=69)
d    0000    0043 0201 0101 f14b
d    0008    f34b f64b f14b f44b
d    0010    f14b f24b f64b f1f7
d    0018    4bf9 4bf6 f74b f1f1
d    0020    f64b f6f5 4bf4 f34b
d    0028    f64b f14b f24b f14b
d    0030    f44b f2f1 4bf1 4bf7
d    0038    4bf9 4bf6 f74b f1f1
d    0040    f64b f6f6 0007 2b30
d    0048(72)
1    15:43:01 EZB4072I SNMP sub-agent:DPI GET request
                        (1.3.6.1.4.1.2.6.17.9.67.116.65.43.6.1.2.1.4.21.1.7.9.67.116.66) received
1    15:43:01 EZB4083I iproutenexthop.9.67.116.66
d    =============== Sending DPI response to SNMP agent (length=77)
d    0000    004b 0201 0105 00f1
d    0008    4bf3 4bf6 4bf1 4bf4
d    0010    4bf1 4bf2 4bf6 4bf1
d    0018    f74b f94b f6f7 4bf1
d    0020    f1f6 4bf6 f54b f4f3
d    0028    4bf6 4bf1 4bf2 4bf1
d    0030    4bf4 4bf2 f14b f14b
d    0038    f74b f94b f6f7 4bf1
d    0040    f1f6 4bf6 f600 8500
d    0048    0409 4374 4149 5f3c
d    0050(80)
1    15:43:01 EZB3829I Waiting for incoming packets
1    15:43:01 EZB4068I SNMP response received from agent 9.67.116.66

d        =============== Received SNMP response from agent (length=59)
d        0000    3039 0201 0004 0473
d        0008    6e6d 70a2 2e02 0115
d        0010    0201 0002 0100 3023
d        0018    3021 0619 2b06 0104
d        0020    0102 0611 0943 7441
d        0028    2b06 0102 0104 1501
d        0030    0709 4374 4240 0409
d        0038    4374 4196 95a2 8540
d        0040(64)
d        =============== Object data (length=25)
d        0000    2b06 0104 0102 0611
d        0008    0943 7441 2b06 0102
d        0010    0104 1501 0709 4374
d        0018    4240 2910 0000 0001
d        0020(32)
d        =============== prefix + address (length=12)
d        0000    2b06 0104 0102 0611
d        0008    0943 7441 2b06 0102
d        0010(16)
d        =============== Outbound SNMP packet (post edit) (length=47)
d        0000    302d 0201 0004 0473
d        0008    6e6d 70a2 2202 0115
d        0010    0201 0002 0100 3017
d        0018    3015 060d 2b06 0102
d        0020    0104 1501 0709 4374
d        0028    4240 0409 4374 4100
d        0030(48)
1        15:43:01 EZB4172I SNMP reply sent to NCP client 9.67.116.66
d        =============== UDP data (length=47)
d        0000    302d 0201 0004 0473
d        0008    6e6d 70a2 2202 0115
d        0010    0201 0002 0100 3017
d        0018    3015 060d 2b06 0102
d        0020    0104 1501 0709 4374
d        0028    4240 0409 4374 4168
d        0030(48)
d        =============== UDP header (length=8)
d        0000    00a1 040e 0037 ec9f
d        0008(8)
d        =============== IP header (length=20)
d        0000    4500 004b 0034 0000
d        0008    0411 a18e 0a44 0058
d        0010    0a44 0001 8002 c12c
d        0018(24)
d        =============== Transport PDU header (length=8)
d        0000    0700 0000 0a44 0058
d        0008(8)

d        =============== Sending Transport PDU to NCP client (length=84)
d        0000    0700 0000 0a44 0058
d        0008    4500 004b 0034 0000
d        0010    0411 a18e 0a44 0058
d        0018    0a44 0001 00a1 040e
d        0020    0037 ec9f 302d 0201
d        0028    0004 0473 6e6d 70a2
d        0030    2202 0115 0201 0002
d        0038    0100 3017 3015 060d
d        0040    2b06 0102 0104 1501
d        0048    0709 4374 4240 0409
d        0050    4374 4100 0007 3568
d        0058(88)
1        15:43:01 EZB3829I Waiting for incoming packets
⋮
0        15:44:30 EZB3834I ******************************************************
0     24 15:44:30 EZB3890I * Recv:  status from 9.67.116.65
0        15:44:30 EZB3891I * Interface: 10.68.0.88 is now inactive - TR88
0        15:44:30 EZB3834I ******************************************************
3     25 15:44:30 EZB4038I *** Packet history for interface TR88 ***
3        15:44:30 EZB4044I Output: trace:
3        15:44:30 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
                             .
3        15:44:30 EZB4049I         destination 9.67.112.0 metric 2
3        15:44:30 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
                             .
3        15:44:30 EZB4049I         destination 9.67.112.0 metric 2
⋮
3        15:44:30 EZB4045I     RESPONSE to 10.68.15.255 -> 0:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
3        15:44:30 EZB4044I Input: trace:
3        15:44:30 EZB4045I     RESPONSE from 10.68.0.88 -> 520:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
                             .
3        15:44:30 EZB4049I         destination 9.67.112.0 metric 2

3        15:44:30 EZB4045I     RESPONSE from 10.68.0.88 -> 520:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
                             .
3        15:44:30 EZB4049I         destination 9.67.112.0 metric 2
3        15:44:30 EZB4045I     RESPONSE from 10.68.0.88 -> 520:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
                             .
3        15:44:30 EZB4049I         destination 9.67.112.0 metric 2
⋮
3        15:44:30 EZB4045I     RESPONSE from 10.68.0.88 -> 520:
                             .
3        15:44:30 EZB4049I         destination 9.67.116.66 metric 1
                             .
3        15:44:30 EZB4049I         destination 10.68.0.0 metric 1
3        15:44:30 EZB4039I *** End packet history ***
         15:44:31 EZB3829I Waiting for incoming packets
                             .
                             .
                             .
1        15:44:41 EZB3948I Interface TR88 not up
1        15:44:41 EZB3948I Interface TR92 not up
1        15:44:41 EZB3829I Waiting for incoming packets
                             .
                             .
                             .

The following information explains the numbered items in the trace:

1: The port number and the service name are defined as 580 and ncprout in the hlq.ETC.SERVICES data set for this NCPROUTE server.
2: NCPROUTE is processing the NCPROUTE.PROFILE definitions.
3: NCPROUTE is establishing the connection with the SNMP agent defined in NCPROUTE.PROFILE.
4: The NCP client is starting the hand-shaking process with NCPROUTE. NCPROUTE is establishing a session with the NCP client.
5: NCPROUTE received a list of inactive interfaces from the NCP client.
6: NCPROUTE is initializing its interface tables with interface information from the NCP client.
7: NCPROUTE is adding a route to its interface tables.
8: NCPROUTE is processing the NCP client GATEWAYS data set. The trace shows NCPROUTE server options and no additional gateway definitions.
9: NCPROUTE received a transport datagram from the NCP client.
10: The trace shows the contents of the datagram in hexadecimal followed by a division of the datagram into its parts (transport PDU header, IP header, UDP header, and UDP data).
11: The trace shows that the NCP client 9.67.116.65 received the broadcasted routing tables from adjacent router 9.67.116.66.
12: The UDP data in the datagram contains two routing table entries.
13: NCPROUTE is adding a new route to its tables from the information received in the transport datagram.
14: NCPROUTE is issuing a request to the NCP client to add the route to its tables.
15: The NCP client 30-second timer has expired, so NCPROUTE supplies its routing tables to other routers.
16: NCPROUTE is responding to the request by sending its routing tables to the requesting router for the NCP client.
17: This line shows an inactive state for interface TR92.
18: The NCP client 3-minute timer expired. The client was broadcast as a network unreachable route (in the range metric 16—infinite), so NCPROUTE updates its routing tables for the NCP client.
19: NCPROUTE is deleting the NCP client from its tables.
20: The NCP client five-minute timer has expired for the route to 9.67.112.0.
21: NCPROUTE is deleting the route to 9.67.112.0 from its tables for the NCP client.
22: NCPR received a transport datagram from the SNMP client through NCP client 9.67.116.65.
23: NCPROUTE is processing the SNMP request.
24: NCPROUTE has received a status notification from the NCP client. The interface TR88 has become inactive.
25: The packet history for the interface TR88 is included in the trace because the interface has become inactive.