Performance Routing Version 3 Configuration Guide, Cisco IOS XE Fuji 16.9.x

Prerequisites for PfRv3 Event Tracing

PfRv3 event trace is enabled by default. When PfRv3 features are enabled on the route, PfRv3 writes event trace data into PfRv3’s event trace buffer.

Restrictions for PfRv3 Event Tracing

By default, PfRv3 event trace can store 4096 entries of event traces. The entry size can be adjusted from 1 to 1000000 entries. Event traces are stored in memory and every event trace entry uses the memory size. The greater the number of entries, more memory is consumed. In PfRv3, each entry consumes 104 bytes. This indicates that PfRv3 event trace will consume about 416K bytes memory. Per design, the memory will have a delay allocation until first entry is written.

Information About PfRv3 Event Tracing

PfRv3 Event Tracing Options

Event Tracing uses event-trace infra framework by providing the ability to retrieve relevant part of event trace by providing show commands, such as, show monitor event-trace pfrv3 sub-comp channel command.

In Cisco IOS XE Fuji 16.9.1, PfRv3 supports event trace for the following subcomponents:

process
policy
PDP
channel

You can use the Event Trace for PFRv3 feature to analyze the cause of a device failure. When you configure PFRv3 features, the device records PfRv3 setup workflow and logs messages from specific subsystem components into the device memory. You can view trace messages stored in the memory by using the commands or save them to a file.

Benefits of PfRv3 Event Tracing

Displays debug information on the console during runtime.
Avoids multiple debug calls, and, therefore, improves device performance.
Saves memory space.

How to Display PfRv3 Event Tracing

SUMMARY STEPS

show monitor event-trace pfrv3 sub-comp channel {all | back duration | clock duration | from-boot seconds | latest } [detail ]
show monitor event-trace pfrv3 sub-comp pdp {all | back duration | clock duration | from-boot seconds | latest } [detail ]
show monitor event-trace pfrv3 sub-comp policy {all | back duration | clock duration | from-boot seconds | latest } [detail ]
show monitor event-trace pfrv3 sub-comp process {all | back duration | clock duration | from-boot seconds | latest } [detail ]

DETAILED STEPS

Step 1	show monitor event-trace pfrv3 sub-comp channel {all \| back `duration` \| clock `duration` \| from-boot `seconds` \| latest } [detail ] Example: Router# show monitor event-trace pfrv3 sub-comp channel all Jul 12 02:03:01.966: CHANNEL: INFO: BR[3] create WAN interface: name[Tunnel11] sp_color[ISP1] ip_addr[172.16.0.1] intf_index[29] snmp index[24] CMD enabled[YES] intf_type[External] sp_tag[0x1] zero_sla[Disable] plr[Disabled] Jul 12 02:03:01.971: CHANNEL: INFO: BR[3] create WAN interface: name[Tunnel31] sp_color[ISP3] ip_addr[192.168.0.1] intf_index[31] snmp index[26] CMD enabled[YES] intf_type[External] sp_tag[0x7] zero_sla[Disable] plr[Disabled] Jul 12 02:03:02.469: CHANNEL: INFO: BR[3] Tunnel0 interface line protocol is coming back Jul 12 02:03:11.685: CHANNEL: INFO: BR[2] Tunnel1 interface line protocol is coming back Jul 12 02:03:16.272: CHANNEL: INFO: BR[2] create WAN interface: name[Tunnel10] sp_color[ISP1] ip_addr[172.16.0.1] intf_index[28] snmp index[23] CMD enabled[YES] intf_type[External] sp_tag[0x1] zero_sla[Disable] plr[Disabled] Jul 12 02:03:16.282: CHANNEL: INFO: BR[2] create WAN interface: name[Tunnel30] sp_color[ISP3] ip_addr[192.168.0.1] intf_index[30] snmp index[25] CMD enabled[YES] intf_type[External] sp_tag[0x7] zero_sla[Disable] plr[Disabled] Jul 12 02:04:48.465: CHANNEL: INFO: MC[3] add channel[1]: site_id[10.30.1.1] dscp[0] intf_index[29] label[0x1] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:48.465: CHANNEL: INFO: MC[3] add channel[2]: site_id[10.30.1.1] dscp[0] intf_index[31] label[0x7] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:48.465: CHANNEL: INFO: MC[3] add channel[3]: site_id[10.30.1.1] dscp[0] intf_index[29] label[0x3] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:48.464: CHANNEL: INFO: MC[3] add channel[4]: site_id[10.30.1.1] dscp[0] intf_index[31] label[0x9] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:48.465: CHANNEL: INFO: MC[3] add channel[5]: site_id[10.30.1.1] dscp[0] intf_index[27] label[0x2] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:48.465: CHANNEL: INFO: MC[3] add channel[6]: site_id[10.30.1.1] dscp[0] intf_index[27] label[0x4] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:48.472: CHANNEL: INFO: BR[3] create channel[1] site_id[10.30.1.1] dscp[0] intf_index[29] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:04:48.475: CHANNEL: INFO: BR[3] create channel[2] site_id[10.30.1.1] dscp[0] intf_index[31] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:04:57.246: CHANNEL: INFO: MC[2] add channel[7]: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x1] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:57.246: CHANNEL: INFO: MC[2] add channel[8]: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x7] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:57.246: CHANNEL: INFO: MC[2] add channel[9]: site_id[10.30.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:57.246: CHANNEL: INFO: MC[2] add channel[10]: site_id[10.30.1.1] dscp[0] intf_index[26] label[0x2] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:57.247: CHANNEL: INFO: MC[2] add channel[11]: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:57.248: CHANNEL: INFO: MC[2] add channel[12]: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:04:57.251: CHANNEL: INFO: BR[2] create channel[7] site_id[10.30.1.1] dscp[0] intf_index[28] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:04:57.264: CHANNEL: INFO: BR[2] create channel[8] site_id[10.30.1.1] dscp[0] intf_index[30] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:05:13.128: CHANNEL: INFO: MC[3] add channel[13]: site_id[10.20.1.1] dscp[0] intf_index[29] label[0x1] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:13.129: CHANNEL: INFO: MC[3] add channel[14]: site_id[10.20.1.1] dscp[0] intf_index[31] label[0x7] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:13.129: CHANNEL: INFO: MC[3] add channel[15]: site_id[10.20.1.1] dscp[0] intf_index[29] label[0x3] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:13.129: CHANNEL: INFO: MC[3] add channel[16]: site_id[10.20.1.1] dscp[0] intf_index[31] label[0x9] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:13.129: CHANNEL: INFO: MC[3] add channel[17]: site_id[10.20.1.1] dscp[0] intf_index[27] label[0x2] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:13.129: CHANNEL: INFO: MC[3] add channel[18]: site_id[10.20.1.1] dscp[0] intf_index[27] label[0x4] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:13.132: CHANNEL: INFO: BR[3] create channel[13] site_id[10.20.1.1] dscp[0] intf_index[29] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:05:13.134: CHANNEL: INFO: BR[3] create channel[14] site_id[10.20.1.1] dscp[0] intf_index[31] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:05:15.268: CHANNEL: INFO: MC[2] add channel[19]: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x1] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:15.268: CHANNEL: INFO: MC[2] add channel[20]: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x7] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:15.269: CHANNEL: INFO: MC[2] add channel[21]: site_id[10.20.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:15.270: CHANNEL: INFO: MC[2] add channel[22]: site_id[10.20.1.1] dscp[0] intf_index[26] label[0x2] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:15.270: CHANNEL: INFO: MC[2] add channel[23]: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:15.270: CHANNEL: INFO: MC[2] add channel[24]: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[default channel to branch] op state[Initiated and open] Jul 12 02:05:15.272: CHANNEL: INFO: BR[2] create channel[19] site_id[10.20.1.1] dscp[0] intf_index[28] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:05:15.274: CHANNEL: INFO: BR[2] create channel[20] site_id[10.20.1.1] dscp[0] intf_index[30] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Initial state] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:05:21.766: CHANNEL: INFO: MC[2] delete channel[23] created 00:00:06 ago: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:05:21.766: CHANNEL: INFO: MC[2] delete channel[11] created 00:00:24 ago: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:05:21.766: CHANNEL: INFO: MC[2] delete channel[12] created 00:00:24 ago: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:05:21.767: CHANNEL: INFO: MC[2] delete channel[24] created 00:00:06 ago: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:05:21.877: CHANNEL: INFO: MC[2] delete channel[21] created 00:00:06 ago: site_id[10.20.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:05:21.877: CHANNEL: INFO: MC[2] delete channel[9] created 00:00:24 ago: site_id[10.30.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:07:15.434: CHANNEL: INFO: MC[2] add channel[25]: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[new interface/sp-tag added] op state[Initiated and open] Jul 12 02:07:15.434: CHANNEL: INFO: MC[2] add channel[26]: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[new interface/sp-tag added] op state[Initiated and open] Jul 12 02:07:15.438: CHANNEL: INFO: MC[2] add channel[27]: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[new interface/sp-tag added] op state[Initiated and open] Jul 12 02:07:15.438: CHANNEL: INFO: MC[2] add channel[28]: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[new interface/sp-tag added] op state[Initiated and open] Jul 12 02:07:15.788: CHANNEL: INFO: MC[2] add channel[29]: site_id[10.30.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[new interface/sp-tag added] op state[Initiated and open] Jul 12 02:07:15.788: CHANNEL: INFO: MC[2] add channel[30]: site_id[10.20.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] IDC channel[NO] MHOP channel[NO] To-HUB channel[NO] reason[new interface/sp-tag added] op state[Initiated and open] Jul 12 02:08:47.133: CHANNEL: INFO: BR[2] delete channel[7] when clear BR DB: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:47.135: CHANNEL: INFO: BR[2] delete channel[8] when clear BR DB: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:47.136: CHANNEL: INFO: BR[2] delete channel[19] when clear BR DB: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:47.137: CHANNEL: INFO: BR[2] delete channel[20] when clear BR DB: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:47.174: CHANNEL: INFO: MC[2] delete channel[30] created 00:01:31 ago: site_id[10.20.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.174: CHANNEL: INFO: MC[2] delete channel[29] created 00:01:31 ago: site_id[10.30.1.1] dscp[0] intf_index[26] label[0x4] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.175: CHANNEL: INFO: MC[2] delete channel[19] created 00:03:31 ago: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x1] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.175: CHANNEL: INFO: MC[2] delete channel[7] created 00:03:49 ago: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x1] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.175: CHANNEL: INFO: MC[2] delete channel[8] created 00:03:49 ago: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x7] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.175: CHANNEL: INFO: MC[2] delete channel[20] created 00:03:31 ago: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x7] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.175: CHANNEL: INFO: MC[2] delete channel[22] created 00:03:31 ago: site_id[10.20.1.1] dscp[0] intf_index[26] label[0x2] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.175: CHANNEL: INFO: MC[2] delete channel[10] created 00:03:49 ago: site_id[10.30.1.1] dscp[0] intf_index[26] label[0x2] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.176: CHANNEL: INFO: MC[2] delete channel[26] created 00:01:31 ago: site_id[10.20.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.176: CHANNEL: INFO: MC[2] delete channel[25] created 00:01:31 ago: site_id[10.30.1.1] dscp[0] intf_index[28] label[0x3] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.177: CHANNEL: INFO: MC[2] delete channel[27] created 00:01:31 ago: site_id[10.30.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.177: CHANNEL: INFO: MC[2] delete channel[28] created 00:01:31 ago: site_id[10.20.1.1] dscp[0] intf_index[30] label[0x9] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:47.211: CHANNEL: INFO: BR[2] Tunnel1 interface line protocol is going down, may enqueue ALL_CHAN_UNREACH msg Jul 12 02:08:48.235: CHANNEL: INFO: BR[3] delete channel[1] when clear BR DB: site_id[10.30.1.1] dscp[0] intf_index[29] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:48.235: CHANNEL: INFO: BR[3] delete channel[2] when clear BR DB: site_id[10.30.1.1] dscp[0] intf_index[31] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:48.235: CHANNEL: INFO: BR[3] delete channel[13] when clear BR DB: site_id[10.20.1.1] dscp[0] intf_index[29] label[0x1] sp_color[ISP1] next-hop[172.16.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:48.235: CHANNEL: INFO: BR[3] delete channel[14] when clear BR DB: site_id[10.20.1.1] dscp[0] intf_index[31] label[0x7] sp_color[ISP3] next-hop[192.168.0.1] RX state[Reachable] TX state[Reachable] muted-by-0-sla[NO] op state[Initiated and open] Jul 12 02:08:48.259: CHANNEL: INFO: MC[3] delete channel[6] created 00:03:59 ago: site_id[10.30.1.1] dscp[0] intf_index[27] label[0x4] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.259: CHANNEL: INFO: MC[3] delete channel[18] created 00:03:35 ago: site_id[10.20.1.1] dscp[0] intf_index[27] label[0x4] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.260: CHANNEL: INFO: MC[3] delete channel[1] created 00:03:59 ago: site_id[10.30.1.1] dscp[0] intf_index[29] label[0x1] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.260: CHANNEL: INFO: MC[3] delete channel[13] created 00:03:35 ago: site_id[10.20.1.1] dscp[0] intf_index[29] label[0x1] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[2] created 00:03:59 ago: site_id[10.30.1.1] dscp[0] intf_index[31] label[0x7] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[14] created 00:03:35 ago: site_id[10.20.1.1] dscp[0] intf_index[31] label[0x7] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[5] created 00:03:59 ago: site_id[10.30.1.1] dscp[0] intf_index[27] label[0x2] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[17] created 00:03:35 ago: site_id[10.20.1.1] dscp[0] intf_index[27] label[0x2] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[3] created 00:03:59 ago: site_id[10.30.1.1] dscp[0] intf_index[29] label[0x3] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[15] created 00:03:35 ago: site_id[10.20.1.1] dscp[0] intf_index[29] label[0x3] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[4] created 00:03:59 ago: site_id[10.30.1.1] dscp[0] intf_index[31] label[0x9] intf_type[External] channel status[Not-Available] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.261: CHANNEL: INFO: MC[3] delete channel[16] created 00:03:35 ago: site_id[10.20.1.1] dscp[0] intf_index[31] label[0x9] intf_type[External] channel status[Not-Available(no next-hop)] TC count[0] backup-TC count[0] op state[Initiated and open] Jul 12 02:08:48.288: CHANNEL: INFO: BR[3] Tunnel0 interface line protocol is going down, may enqueue ALL_CHAN_UNREACH msg Displays event trace for PfRv3 channels.
Step 2	show monitor event-trace pfrv3 sub-comp pdp {all \| back `duration` \| clock `duration` \| from-boot `seconds` \| latest } [detail ] Example: Router# show monitor event-trace pfrv3 sub-comp pdp all Jul 12 02:23:01.024: PDP: INFO: MC[6] TC[2] PDP RESULT: state is un-controlled, PDP trigger reason is New TC Learned, violate type is None Jul 12 02:23:31.948: PDP: INFO: MC[6] TC[2]: +Channel[55]: Path-Pref[Primary], Usable[P], Reachable[P], TCA Loss[-], TCA Delay[-], TCA Jitter[-], 95Bandwidth[P], Prefix Reachable[P] Jul 12 02:23:31.948: PDP: INFO: MC[6] TC[2]: -Channel[57]: Path-Pref[Fallback], Usable[P], Reachable[P], TCA Loss[-], TCA Delay[-], TCA Jitter[-], 95Bandwidth[P], Prefix Reachable[P] Jul 12 02:23:31.948: PDP: INFO: MC[6] TC[2]: -Channel[58]: Path-Pref[Fallback], Usable[P], Reachable[P], TCA Loss[-], TCA Delay[-], TCA Jitter[-], 95Bandwidth[P], Prefix Reachable[P] Jul 12 02:23:31.948: PDP: INFO: MC[6] TC[2]: *Channel[59]: Path-Pref[Primary], Usable[P], Reachable[P], TCA Loss[-], TCA Delay[-], TCA Jitter[-], 95Bandwidth[P], Prefix Reachable[P] Jul 12 02:23:31.948: PDP: INFO: MC[6] TC[2] PDP RESULT: state is controlled, PDP trigger reason is Backoff Timer Expired, violate type is Uncontrolled to Controlled Transition Displays event trace for PfRv3 policy decision points (PDP).
Step 3	show monitor event-trace pfrv3 sub-comp policy {all \| back `duration` \| clock `duration` \| from-boot `seconds` \| latest } [detail ] Example: Router# show monitor event-trace pfrv3 sub-comp policy all Jul 12 02:02:42.727: POLICY: INFO: MC[2]: Pol_map seq 10: Set sp pref to ISP1 at index 0 Jul 12 02:02:42.727: POLICY: INFO: MC[2]: Pol_map seq 10: Set sp fallback to ISP2 at index 0 Jul 12 02:02:42.890: POLICY: INFO: MC[2]: Pol_map seq 20: Set sp pref to ISP1 at index 0 Jul 12 02:03:01.959: POLICY: INFO: BR[3]: Create C3PL policy for Egress direction Jul 12 02:03:01.959: POLICY: INFO: BR[3]: Create C3PL policy for Ingress direction Jul 12 02:03:01.967: POLICY: INFO: BR[3]: Create C3PL policy for Egress direction Jul 12 02:03:01.967: POLICY: INFO: BR[3]: Create C3PL policy for Ingress direction Jul 12 02:03:08.212: POLICY: INFO: MC[2]: MC policy downloaded:site id[10.10.1.1], domain[default], vrf[green] Jul 12 02:03:08.212: POLICY: INFO: MC[2]: Policy publish max allowed xml size[3030], exact xml size[2099] Jul 12 02:03:09.355: POLICY: INFO: MC[3]: MC policy downloaded:site id[10.10.1.1], domain[default], vrf[red] Jul 12 02:03:09.355: POLICY: INFO: MC[3]: Policy publish max allowed xml size[2303], exact xml size[1571] Jul 12 02:03:10.927: POLICY: INFO: BR[2]: Updating PMI policies Jul 12 02:03:10.927: POLICY: INFO: BR[2]: Create C3PL policy for Ingress direction Jul 12 02:03:10.949: POLICY: INFO: BR[2]: Create flow monitor MON-Ingress-per-DSCP-2-48-0 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create filter dscp:46,appid:0 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create class CENT-Class-Ingress-DSCP-ef-2-2 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create filter dscp:40,appid:0 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create class CENT-Class-Ingress-DSCP-cs5-2-3 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create filter dscp:32,appid:0 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create class CENT-Class-Ingress-DSCP-cs4-2-4 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create react for class CENT-Class-Ingress-DSCP-ef-2-2 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react packet-loss-rate val=100 id=2 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react one-way-delay val=20 id=3 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react network-delay-avg val=40 id=4 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react jitter val=5000 id=5 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react byte-loss-rate val=100 id=6 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create react for class CENT-Class-Ingress-DSCP-cs5-2-3 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react jitter val=5000 id=7 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create react for class CENT-Class-Ingress-DSCP-cs4-2-4 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react one-way-delay val=20 id=8 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Provision react network-delay-avg val=40 id=9 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create PMI policy CENT-Policy-Ingress-2-2 Jul 12 02:03:10.950: POLICY: INFO: BR[2]: Create C3PL policy for Egress direction Jul 12 02:03:10.976: POLICY: INFO: BR[2]: Create flow monitor MON-Egress-aggregate-2-48-1 Jul 12 02:03:10.976: POLICY: INFO: BR[2]: Create filter dscp:0,appid:0 Jul 12 02:03:10.976: POLICY: INFO: BR[2]: Create class CENT-Class-Egress-ANY-2-5 Jul 12 02:03:10.977: POLICY: INFO: BR[2]: Create PMI policy CENT-Policy-Egress-2-3 Jul 12 02:03:12.013: POLICY: INFO: BR[3]: Updating PMI policies Jul 12 02:03:12.013: POLICY: INFO: BR[3]: Create C3PL policy for Ingress direction Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Create flow monitor MON-Ingress-per-DSCP-3-48-2 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Create filter dscp:46,appid:0 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Create class CENT-Class-Ingress-DSCP-ef-3-6 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Create filter dscp:40,appid:0 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Create class CENT-Class-Ingress-DSCP-cs5-3-7 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Create react for class CENT-Class-Ingress-DSCP-ef-3-6 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Provision react packet-loss-rate val=100 id=10 Jul 12 02:03:12.014: POLICY: INFO: BR[3]: Provision react byte-loss-rate val=100 id=11 Jul 12 02:03:12.015: POLICY: INFO: BR[3]: Create react for class CENT-Class-Ingress-DSCP-cs5-3-7 Jul 12 02:03:12.015: POLICY: INFO: BR[3]: Provision react packet-loss-rate val=100 id=12 Jul 12 02:03:12.015: POLICY: INFO: BR[3]: Provision react byte-loss-rate val=100 id=13 Jul 12 02:03:12.015: POLICY: INFO: BR[3]: Create PMI policy CENT-Policy-Ingress-3-4 Jul 12 02:03:12.094: POLICY: INFO: BR[3]: Activate flow monitor MON-Ingress-per-DSCP-3-48-2 Jul 12 02:03:12.094: POLICY: INFO: BR[3]: Activate PMI policy CENT-Policy-Ingress-3-4 on Tunnel31 Jul 12 02:03:12.094: POLICY: INFO: BR[3]: Activate PMI policy CENT-Policy-Ingress-3-4 on Tunnel11 Jul 12 02:03:12.094: POLICY: INFO: BR[3]: Create C3PL policy for Egress direction Jul 12 02:03:12.119: POLICY: INFO: BR[3]: Create flow monitor MON-Egress-aggregate-3-48-3 Jul 12 02:03:12.118: POLICY: INFO: BR[3]: Create filter dscp:0,appid:0 Jul 12 02:03:12.118: POLICY: INFO: BR[3]: Create class CENT-Class-Egress-ANY-3-8 Jul 12 02:03:12.118: POLICY: INFO: BR[3]: Create PMI policy CENT-Policy-Egress-3-5 Jul 12 02:03:12.151: POLICY: INFO: BR[3]: Activate PMI policy CENT-Policy-Egress-3-5 on Tunnel31 Jul 12 02:03:12.151: POLICY: INFO: BR[3]: Activate PMI policy CENT-Policy-Egress-3-5 on Tunnel11 Jul 12 02:03:16.251: POLICY: INFO: BR[2]: Activate PMI policy CENT-Policy-Egress-2-3 on Tunnel10 Jul 12 02:03:16.265: POLICY: INFO: BR[2]: Activate flow monitor MON-Ingress-per-DSCP-2-48-0 Jul 12 02:03:16.265: POLICY: INFO: BR[2]: Activate PMI policy CENT-Policy-Ingress-2-2 on Tunnel10 Jul 12 02:03:16.274: POLICY: INFO: BR[2]: Activate PMI policy CENT-Policy-Egress-2-3 on Tunnel30 Jul 12 02:03:16.275: POLICY: INFO: BR[2]: Activate PMI policy CENT-Policy-Ingress-2-2 on Tunnel30 Jul 12 02:08:47.180: POLICY: INFO: BR[2]: De-activate PMI policy CENT-Policy-Egress-2-3 on Tunnel30 Jul 12 02:08:47.182: POLICY: INFO: BR[2]: De-activate PMI policy CENT-Policy-Ingress-2-2 on Tunnel30 Jul 12 02:08:47.188: POLICY: INFO: BR[2]: Delete class CENT-Class-Egress-ANY-2-5 Jul 12 02:08:47.190: POLICY: INFO: BR[2]: Delete flow monitor MON-Egress-aggregate-2-48-1 Jul 12 02:08:47.190: POLICY: INFO: BR[2]: De-activate PMI policy CENT-Policy-Egress-2-3 on Tunnel10 Jul 12 02:08:47.190: POLICY: INFO: BR[2]: De-activate flow monitor MON-Ingress-per-DSCP-2-48-0 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete react from class CENT-Class-Ingress-DSCP-ef-2-2 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete class CENT-Class-Ingress-DSCP-ef-2-2 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete react from class CENT-Class-Ingress-DSCP-cs5-2-3 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete class CENT-Class-Ingress-DSCP-cs5-2-3 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete react from class CENT-Class-Ingress-DSCP-cs4-2-4 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete class CENT-Class-Ingress-DSCP-cs4-2-4 Jul 12 02:08:47.201: POLICY: INFO: BR[2]: Delete flow monitor MON-Ingress-per-DSCP-2-48-0 Jul 12 02:08:47.202: POLICY: INFO: BR[2]: De-activate PMI policy CENT-Policy-Ingress-2-2 on Tunnel10 Jul 12 02:08:48.264: POLICY: INFO: BR[3]: De-activate PMI policy CENT-Policy-Egress-3-5 on Tunnel31 Jul 12 02:08:48.265: POLICY: INFO: BR[3]: De-activate PMI policy CENT-Policy-Ingress-3-4 on Tunnel31 Jul 12 02:08:48.281: POLICY: INFO: BR[3]: Delete class CENT-Class-Egress-ANY-3-8 Jul 12 02:08:48.281: POLICY: INFO: BR[3]: Delete flow monitor MON-Egress-aggregate-3-48-3 Jul 12 02:08:48.281: POLICY: INFO: BR[3]: De-activate PMI policy CENT-Policy-Egress-3-5 on Tunnel11 Jul 12 02:08:48.281: POLICY: INFO: BR[3]: De-activate flow monitor MON-Ingress-per-DSCP-3-48-2 Jul 12 02:08:48.287: POLICY: INFO: BR[3]: Delete react from class CENT-Class-Ingress-DSCP-ef-3-6 Jul 12 02:08:48.287: POLICY: INFO: BR[3]: Delete class CENT-Class-Ingress-DSCP-ef-3-6 Jul 12 02:08:48.287: POLICY: INFO: BR[3]: Delete react from class CENT-Class-Ingress-DSCP-cs5-3-7 Jul 12 02:08:48.287: POLICY: INFO: BR[3]: Delete class CENT-Class-Ingress-DSCP-cs5-3-7 Jul 12 02:08:48.287: POLICY: INFO: BR[3]: Delete flow monitor MON-Ingress-per-DSCP-3-48-2 Jul 12 02:08:48.286: POLICY: INFO: BR[3]: De-activate PMI policy CENT-Policy-Ingress-3-4 on Tunnel11 Displays event trace for PfRv3 policies.
Step 4	show monitor event-trace pfrv3 sub-comp process {all \| back `duration` \| clock `duration` \| from-boot `seconds` \| latest } [detail ] Example: Router# show monitor event-trace pfrv3 sub-comp process all Jul 12 02:02:42.467: PROCESS: INFO: BR[2] Register CMD client : client id 4, result Succeed Jul 12 02:02:42.473: PROCESS: INFO: BR[2] started Jul 12 02:02:42.965: PROCESS: INFO: BR[3] started Jul 12 02:02:57.957: PROCESS: INFO: MC[2] Eigrp autocfg opcode: Listening, interface: Loopback1, split: FALSE, action: Add, result: Succeed Jul 12 02:02:57.957: PROCESS: INFO: MC[2] Eigrp autocfg opcode: Stub, interface: Loopback1, split: FALSE, stub stubbed: FALSE, stub connected: FALSE, stub leaking: FALSE, action: Delete Jul 12 02:02:57.957: PROCESS: INFO: MC[2] SAF peering succeed listener: 10.10.1.1 Jul 12 02:02:57.958: PROCESS: INFO: MC[2] SAF peering subscribe sub-service: cent-policy succeed Jul 12 02:02:57.968: PROCESS: INFO: MC[2] SAF peering publish sub-service: globals, origin: 10.10.1.1, size: 997, compressed size: 417, publish seq: 1, publish reason: Normal, result: Peering Success Jul 12 02:02:57.968: PROCESS: INFO: MC[2] SAF peering subscribe sub-service: site-prefix succeed Jul 12 02:02:57.968: PROCESS: INFO: MC[2] SAF peering subscribe sub-service: Capability succeed Jul 12 02:02:57.968: PROCESS: INFO: MC[2] SAF peering subscribe sub-service: globals succeed Jul 12 02:02:57.970: PROCESS: INFO: MC server listening on: 10.10.1.1, port: 17749 Jul 12 02:02:57.970: PROCESS: INFO: MC[2] SAF peering publish sub-service: globals, origin: 10.10.1.1, size: 997, compressed size: 417, publish seq: 2, publish reason: Normal, result: Peering Success Jul 12 02:02:57.970: PROCESS: INFO: MC[2] SAF peering publish sub-service: globals, origin: 10.10.1.1, size: 997, compressed size: 417, publish seq: 3, publish reason: Normal, result: Peering Success Jul 12 02:02:58.490: PROCESS: INFO: MC[3] Eigrp autocfg opcode: Listening, interface: Loopback2, split: FALSE, action: Add, result: Succeed Jul 12 02:02:58.492: PROCESS: INFO: MC[3] Eigrp autocfg opcode: Stub, interface: Loopback2, split: FALSE, stub stubbed: FALSE, stub connected: FALSE, stub leaking: FALSE, action: Delete Jul 12 02:02:58.492: PROCESS: INFO: MC[3] SAF peering succeed listener: 10.10.1.1 Jul 12 02:02:58.492: PROCESS: INFO: MC[3] SAF peering subscribe sub-service: cent-policy succeed Jul 12 02:02:58.500: PROCESS: INFO: MC[3] SAF peering publish sub-service: globals, origin: 10.10.1.1, size: 996, compressed size: 419, publish seq: 1, publish reason: Normal, result: Peering Success Jul 12 02:02:58.500: PROCESS: INFO: MC[3] SAF peering subscribe sub-service: site-prefix succeed Jul 12 02:02:58.500: PROCESS: INFO: MC[3] SAF peering subscribe sub-service: Capability succeed Jul 12 02:02:58.500: PROCESS: INFO: MC[3] SAF peering subscribe sub-service: globals succeed Jul 12 02:02:58.501: PROCESS: INFO: MC server listening on: 10.10.1.1, port: 17749 Jul 12 02:03:00.020: PROCESS: INFO: MC[2] SAF peering subscribe sub-service: pmi succeed Jul 12 02:03:01.455: PROCESS: INFO: BR[3] no shutdown Jul 12 02:03:01.462: PROCESS: INFO: BR[3] start communication process Jul 12 02:03:01.463: PROCESS: INFO: BR[3] start exporter process Jul 12 02:03:01.535: PROCESS: INFO: BR[3] start route learn Jul 12 02:03:01.540: PROCESS: INFO: MC[3] SAF peering subscribe sub-service: pmi succeed Jul 12 02:03:01.738: PROCESS: INFO: BR[3] ip: 10.10.1.1, port: 20660, connected to MC ip: 10.10.1.1, port: 17749 Jul 12 02:03:01.739: PROCESS: INFO: BR[3] Eigrp autocfg opcode: Stub, interface: Loopback2, split: FALSE, stub stubbed: FALSE, stub connected: FALSE, stub leaking: FALSE, action: Delete Jul 12 02:03:01.739: PROCESS: INFO: BR[3] Eigrp autocfg opcode: Neighbor multihop, Hub ip: 10.10.1.1, interface: Loopback2, split: FALSE, action: Add, result: Succeed Jul 12 02:03:01.739: PROCESS: INFO: BR[3] SAF peering succeed: 10.10.1.1 to 10.10.1.1 Jul 12 02:03:01.740: PROCESS: INFO: BR[3] SAF peering subscribe sub-service: pmi succeed Jul 12 02:03:01.740: PROCESS: INFO: BR[3] SAF peering subscribe sub-service: site-prefix succeed Jul 12 02:03:01.740: PROCESS: INFO: BR[3] SAF peering received sub-service: globals, from: 10.10.1.1, data size: 439, data seq: 1 Jul 12 02:03:01.741: PROCESS: INFO: BR[3] SAF peering subscribe sub-service: globals succeed Jul 12 02:03:01.741: PROCESS: INFO: BR[3] SAF peering subscribe sub-service: Capability succeed Jul 12 02:03:01.958: PROCESS: INFO: BR[3] Register CMD IDB : idb Tunnel0, client id 4, result Succeed Jul 12 02:03:01.966: PROCESS: INFO: BR[3] Register CMD IDB : idb Tunnel11, client id 4, result Succeed Jul 12 02:03:01.971: PROCESS: INFO: BR[3] Register CMD IDB : idb Tunnel31, client id 4, result Succeed Jul 12 02:03:04.116: PROCESS: INFO: MC[2] SAF peering publish sub-service: site-prefix, origin: 10.10.1.1, size: 333, compressed size: 174, publish seq: 4, publish reason: On-Demand, result: Peering Success Jul 12 02:03:04.117: PROCESS: INFO: MC[2] SAF peering publish sub-service: Capability, origin: 10.10.1.1, size: 274, compressed size: 159, publish seq: 5, publish reason: Periodic, result: Peering Success Jul 12 02:03:05.247: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.10.1.1, data size: 190, data seq: 2 Jul 12 02:03:05.256: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.10.1.1/32 from 10.10.1.1 Jul 12 02:03:05.257: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.10.1.1 Jul 12 02:03:05.258: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.10.1.1 Jul 12 02:03:05.258: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.10.1.1 Jul 12 02:03:05.259: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.10.1.1 Jul 12 02:03:05.259: PROCESS: INFO: MC[3] SAF peering publish sub-service: site-prefix, origin: 10.10.1.1, size: 333, compressed size: 170, publish seq: 2, publish reason: On-Demand, result: Peering Success Jul 12 02:03:05.258: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.10.1.1, data size: 260, data seq: 3 Jul 12 02:03:05.259: PROCESS: INFO: MC[3] SAF peering publish sub-service: Capability, origin: 10.10.1.1, size: 618, compressed size: 240, publish seq: 3, publish reason: Periodic, result: Peering Success Jul 12 02:03:08.213: PROCESS: INFO: MC[2] SAF peering publish sub-service: cent-policy, origin: 10.10.1.1, size: 210, compressed size: 455, publish seq: 6, publish reason: Normal, result: Peering Success Jul 12 02:03:09.355: PROCESS: INFO: MC[3] SAF peering publish sub-service: cent-policy, origin: 10.10.1.1, size: 1572, compressed size: 372, publish seq: 4, publish reason: Normal, result: Peering Success Jul 12 02:03:09.610: PROCESS: INFO: MC[3] SAF peering received sub-service: site-prefix, from: 10.15.1.1, data size: 193, data seq: 1 Jul 12 02:03:09.610: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.15.1.1, data size: 193, data seq: 1 Jul 12 02:03:09.610: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:09.610: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:09.610: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:09.610: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:09.610: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:09.611: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:09.611: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:09.611: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:09.611: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:09.611: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:09.614: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:09.614: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:09.614: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:09.614: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:09.615: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:09.615: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:09.615: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:09.615: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:09.615: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:09.615: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:09.626: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 251, data seq: 2 Jul 12 02:03:09.626: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 251, data seq: 2 Jul 12 02:03:10.180: PROCESS: INFO: BR[2] no shutdown Jul 12 02:03:10.185: PROCESS: INFO: BR[2] start communication process Jul 12 02:03:10.185: PROCESS: INFO: BR[2] start exporter process Jul 12 02:03:10.262: PROCESS: INFO: MC[2] SAF peering publish sub-service: pmi, origin: 10.10.1.1, size: 1874, compressed size: 494, publish seq: 7, publish reason: Normal, result: Peering Success Jul 12 02:03:10.724: PROCESS: INFO: BR[2] start route learn Jul 12 02:03:10.925: PROCESS: INFO: BR[2] ip: 10.10.1.1, port: 52402, connected to MC ip: 10.10.1.1, port: 17749 Jul 12 02:03:10.925: PROCESS: INFO: BR[2] Eigrp autocfg opcode: Stub, interface: Loopback1, split: FALSE, stub stubbed: FALSE, stub connected: FALSE, stub leaking: FALSE, action: Delete Jul 12 02:03:10.924: PROCESS: INFO: BR[2] Eigrp autocfg opcode: Neighbor multihop, Hub ip: 10.10.1.1, interface: Loopback1, split: FALSE, action: Add, result: Succeed Jul 12 02:03:10.924: PROCESS: INFO: BR[2] SAF peering succeed: 10.10.1.1 to 10.10.1.1 Jul 12 02:03:10.925: PROCESS: INFO: BR[2] SAF peering received sub-service: pmi, from: 10.10.1.1, data size: 514, data seq: 7 Jul 12 02:03:10.925: PROCESS: INFO: BR[2] SAF peering subscribe sub-service: pmi succeed Jul 12 02:03:10.925: PROCESS: INFO: BR[2] SAF peering received sub-service: site-prefix, from: 10.10.1.1, data size: 194, data seq: 4 Jul 12 02:03:10.925: PROCESS: INFO: BR[2] SAF peering subscribe sub-service: site-prefix succeed Jul 12 02:03:10.925: PROCESS: INFO: BR[2] SAF peering received sub-service: globals, from: 10.10.1.1, data size: 437, data seq: 3 Jul 12 02:03:10.926: PROCESS: INFO: BR[2] SAF peering subscribe sub-service: globals succeed Jul 12 02:03:10.926: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.10.1.1, data size: 179, data seq: 5 Jul 12 02:03:10.926: PROCESS: INFO: BR[2] SAF peering subscribe sub-service: Capability succeed Jul 12 02:03:10.977: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.10.1.1/32 from 10.10.1.1 Jul 12 02:03:10.978: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.10.1.1 Jul 12 02:03:10.978: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.10.1.1 Jul 12 02:03:10.978: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.10.1.1 Jul 12 02:03:10.979: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.10.1.1 Jul 12 02:03:12.011: PROCESS: INFO: BR[3] SAF peering received sub-service: pmi, from: 10.10.1.1, data size: 460, data seq: 5 Jul 12 02:03:12.131: PROCESS: INFO: MC[3] SAF peering publish sub-service: pmi, origin: 10.10.1.1, size: 1682, compressed size: 440, publish seq: 5, publish reason: Normal, result: Peering Success Jul 12 02:03:16.244: PROCESS: INFO: BR[2] Register CMD IDB : idb Tunnel1, client id 4, result Succeed Jul 12 02:03:16.272: PROCESS: INFO: BR[2] Register CMD IDB : idb Tunnel10, client id 4, result Succeed Jul 12 02:03:16.281: PROCESS: INFO: BR[2] Register CMD IDB : idb Tunnel30, client id 4, result Succeed Jul 12 02:03:24.577: PROCESS: INFO: MC[2] SAF peering received sub-service: site-prefix, from: 10.15.1.1, data size: 193, data seq: 1 Jul 12 02:03:24.577: PROCESS: INFO: BR[2] SAF peering received sub-service: site-prefix, from: 10.15.1.1, data size: 193, data seq: 1 Jul 12 02:03:24.577: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:24.577: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:24.577: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:24.578: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:24.578: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:24.579: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:24.579: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:24.579: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:24.579: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:24.579: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:24.581: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:24.581: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:24.581: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:24.581: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:24.581: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:24.582: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.15.1.1/32 from 10.15.1.1 Jul 12 02:03:24.582: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.10.0.0/16 from 10.15.1.1 Jul 12 02:03:24.582: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.15.0.0/16 from 10.15.1.1 Jul 12 02:03:24.582: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.16.0.0/16 from 10.15.1.1 Jul 12 02:03:24.582: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.0.0.0/8 from 10.15.1.1 Jul 12 02:03:24.582: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 250, data seq: 2 Jul 12 02:03:24.582: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 250, data seq: 2 Jul 12 02:03:40.913: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 280, data seq: 3 Jul 12 02:03:40.913: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 280, data seq: 3 Jul 12 02:03:51.318: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.10.1.1, data size: 290, data seq: 6 Jul 12 02:03:51.319: PROCESS: INFO: MC[3] SAF peering publish sub-service: Capability, origin: 10.10.1.1, size: 822, compressed size: 270, publish seq: 6, publish reason: On-Demand, result: Peering Success Jul 12 02:03:55.763: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 278, data seq: 3 Jul 12 02:03:55.763: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.15.1.1, data size: 278, data seq: 3 Jul 12 02:04:00.542: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.10.1.1, data size: 287, data seq: 8 Jul 12 02:04:00.543: PROCESS: INFO: MC[2] SAF peering publish sub-service: Capability, origin: 10.10.1.1, size: 822, compressed size: 267, publish seq: 8, publish reason: On-Demand, result: Peering Success Jul 12 02:04:48.460: PROCESS: INFO: MC[3] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 159, data seq: 1 Jul 12 02:04:48.460: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 159, data seq: 1 Jul 12 02:04:48.461: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:48.461: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:48.462: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:48.463: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:48.463: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 183, data seq: 2 Jul 12 02:04:48.464: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 183, data seq: 2 Jul 12 02:04:57.245: PROCESS: INFO: MC[2] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 159, data seq: 1 Jul 12 02:04:57.245: PROCESS: INFO: BR[2] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 159, data seq: 1 Jul 12 02:04:57.245: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:57.245: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:57.246: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:57.247: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:04:57.247: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 183, data seq: 2 Jul 12 02:04:57.246: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 183, data seq: 2 Jul 12 02:05:00.536: PROCESS: INFO: MC[3] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 184, data seq: 3 Jul 12 02:05:00.536: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 184, data seq: 3 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.0.1/32 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.0.0/24 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.2.1/32 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.0.1/32 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.0.0/24 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.30.2.1/32 from 10.30.1.1 Jul 12 02:05:00.537: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:00.538: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.0.1/32 from 10.30.1.1 Jul 12 02:05:00.539: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.0.0/24 from 10.30.1.1 Jul 12 02:05:00.540: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.2.1/32 from 10.30.1.1 Jul 12 02:05:00.540: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:00.540: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.0.1/32 from 10.30.1.1 Jul 12 02:05:00.540: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.0.0/24 from 10.30.1.1 Jul 12 02:05:00.540: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.30.2.1/32 from 10.30.1.1 Jul 12 02:05:00.541: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 306, data seq: 4 Jul 12 02:05:00.541: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 306, data seq: 4 Jul 12 02:05:11.981: PROCESS: INFO: MC[2] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 171, data seq: 3 Jul 12 02:05:11.981: PROCESS: INFO: BR[2] SAF peering received sub-service: site-prefix, from: 10.30.1.1, data size: 171, data seq: 3 Jul 12 02:05:11.982: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:11.982: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.30.0.0/16 from 10.30.1.1 Jul 12 02:05:11.982: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:11.983: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.30.0.0/16 from 10.30.1.1 Jul 12 02:05:11.983: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:11.985: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.30.0.0/16 from 10.30.1.1 Jul 12 02:05:11.985: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.30.1.1/32 from 10.30.1.1 Jul 12 02:05:11.985: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.30.0.0/16 from 10.30.1.1 Jul 12 02:05:11.985: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 297, data seq: 4 Jul 12 02:05:11.985: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 297, data seq: 4 Jul 12 02:05:13.127: PROCESS: INFO: MC[3] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 159, data seq: 1 Jul 12 02:05:13.127: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 159, data seq: 1 Jul 12 02:05:13.126: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:13.126: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:13.128: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:13.128: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:13.128: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 184, data seq: 2 Jul 12 02:05:13.128: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 184, data seq: 2 Jul 12 02:05:15.265: PROCESS: INFO: MC[2] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 159, data seq: 1 Jul 12 02:05:15.265: PROCESS: INFO: BR[2] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 159, data seq: 1 Jul 12 02:05:15.265: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:15.265: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:15.267: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:15.267: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:15.267: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 184, data seq: 2 Jul 12 02:05:15.267: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 184, data seq: 2 Jul 12 02:05:21.764: PROCESS: WARNING: MC[2] Tcp connection to peer: 10.10.3.1, socket: 9 is reset, detected at TCP read handler Jul 12 02:05:21.874: PROCESS: WARNING: MC[2] Tcp connection to peer: 10.10.4.1, socket: 7 is reset, detected at TCP read handler Jul 12 02:05:23.756: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 306, data seq: 5 Jul 12 02:05:23.756: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 306, data seq: 5 Jul 12 02:05:26.806: PROCESS: INFO: MC[2] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 185, data seq: 3 Jul 12 02:05:26.806: PROCESS: INFO: BR[2] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 185, data seq: 3 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.0.0/16 from 10.20.1.1 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:26.807: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:26.808: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:26.808: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.0.0/16 from 10.20.1.1 Jul 12 02:05:26.808: PROCESS: INFO: MC[2] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:26.808: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:26.810: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:26.810: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.0.0/16 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.0.0/16 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:26.811: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 299, data seq: 4 Jul 12 02:05:26.811: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 299, data seq: 4 Jul 12 02:05:29.366: PROCESS: INFO: MC[3] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 194, data seq: 3 Jul 12 02:05:29.366: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 194, data seq: 3 Jul 12 02:05:29.366: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.2/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.2/32 from 10.20.1.1 Jul 12 02:05:29.367: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:29.369: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:29.370: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:29.371: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.2/32 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.2.1/32 from 10.20.1.1 Jul 12 02:05:29.372: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:05:29.373: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.2/32 from 10.20.1.1 Jul 12 02:05:29.373: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 300, data seq: 4 Jul 12 02:05:29.374: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 300, data seq: 4 Jul 12 02:05:32.997: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 297, data seq: 5 Jul 12 02:05:32.997: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.30.1.1, data size: 297, data seq: 5 Jul 12 02:05:48.848: PROCESS: INFO: MC[2] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 299, data seq: 5 Jul 12 02:05:48.848: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 299, data seq: 5 Jul 12 02:05:48.847: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 300, data seq: 5 Jul 12 02:05:48.847: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 300, data seq: 5 Jul 12 02:05:52.133: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.10.1.1, data size: 258, data seq: 9 Jul 12 02:05:52.134: PROCESS: INFO: MC[2] SAF peering publish sub-service: Capability, origin: 10.10.1.1, size: 548, compressed size: 238, publish seq: 9, publish reason: On-Demand, result: Peering Success Jul 12 02:07:46.213: PROCESS: INFO: BR[2] SAF peering received sub-service: Capability, from: 10.10.1.1, data size: 288, data seq: 10 Jul 12 02:07:46.213: PROCESS: INFO: MC[2] SAF peering publish sub-service: Capability, origin: 10.10.1.1, size: 822, compressed size: 268, publish seq: 10, publish reason: On-Demand, result: Peering Success Jul 12 02:08:27.105: PROCESS: INFO: MC[3] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 183, data seq: 6 Jul 12 02:08:27.105: PROCESS: INFO: BR[3] SAF peering received sub-service: site-prefix, from: 10.20.1.1, data size: 183, data seq: 6 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:08:27.107: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:08:27.106: PROCESS: INFO: MC[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:08:27.106: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:08:27.106: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:08:27.106: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:08:27.106: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:08:27.109: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.1.1/32 from 10.20.1.1 Jul 12 02:08:27.109: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.1/32 from 10.20.1.1 Jul 12 02:08:27.109: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.0.0/24 from 10.20.1.1 Jul 12 02:08:27.109: PROCESS: INFO: BR[3] SAF peering site prefix update: prefix 10.20.3.1/32 from 10.20.1.1 Jul 12 02:08:27.110: PROCESS: INFO: MC[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 265, data seq: 7 Jul 12 02:08:27.110: PROCESS: INFO: BR[3] SAF peering received sub-service: Capability, from: 10.20.1.1, data size: 265, data seq: 7 Jul 12 02:08:47.153: PROCESS: INFO: BR[2] Deregister CMD IDB : idb Tunnel1, client id 4, result Succeed Jul 12 02:08:47.155: PROCESS: INFO: BR[2] Deregister CMD IDB : idb Tunnel10, client id 4, result Succeed Jul 12 02:08:47.157: PROCESS: INFO: BR[2] Deregister CMD IDB : idb Tunnel30, client id 4, result Succeed Jul 12 02:08:47.174: PROCESS: INFO: BR[2] SAF peering destroyed: 10.10.1.1 to 10.10.1.1 Jul 12 02:08:47.177: PROCESS: INFO: MC[2] SAF peering listener destroyed: 10.10.1.1 Jul 12 02:08:47.177: PROCESS: INFO: BR[2] SAF peering unsubscribe sub-service: pmi succeed Jul 12 02:08:47.178: PROCESS: INFO: MC[2] SAF peering unsubscribe sub-service: cent-policy succeed Jul 12 02:08:47.178: PROCESS: INFO: BR[2] SAF peering unsubscribe sub-service: site-prefix succeed Jul 12 02:08:47.178: PROCESS: INFO: MC[2] SAF peering unsubscribe sub-service: site-prefix succeed Jul 12 02:08:47.178: PROCESS: INFO: BR[2] SAF peering unsubscribe sub-service: globals succeed Jul 12 02:08:47.178: PROCESS: INFO: MC[2] SAF peering unsubscribe sub-service: Capability succeed Jul 12 02:08:47.179: PROCESS: INFO: BR[2] SAF peering unsubscribe sub-service: Capability succeed Jul 12 02:08:47.179: PROCESS: INFO: MC[2] SAF peering unsubscribe sub-service: globals succeed Jul 12 02:08:47.179: PROCESS: INFO: BR[2] Eigrp uncfg opcode: Neighbor multihop, vrf: , interface: Loopback1, action: Delete, result: Succeed Jul 12 02:08:47.226: PROCESS: INFO: BR[2] stopped Jul 12 02:08:47.226: PROCESS: INFO: MC[2] SAF peering unsubscribe sub-service: pmi succeed Jul 12 02:08:48.234: PROCESS: INFO: MC[2] Eigrp uncfg opcode: Family only, vrf: , interface: Loopback1, action: Delete, result: Succeed Jul 12 02:08:48.246: PROCESS: INFO: BR[3] Deregister CMD IDB : idb Tunnel0, client id 4, result Succeed Jul 12 02:08:48.248: PROCESS: INFO: BR[3] Deregister CMD IDB : idb Tunnel11, client id 4, result Succeed Jul 12 02:08:48.249: PROCESS: INFO: BR[3] Deregister CMD IDB : idb Tunnel31, client id 4, result Succeed Jul 12 02:08:48.261: PROCESS: INFO: BR[3] SAF peering destroyed: 10.10.1.1 to 10.10.1.1 Jul 12 02:08:48.263: PROCESS: INFO: MC[3] SAF peering listener destroyed: 10.10.1.1 Jul 12 02:08:48.264: PROCESS: INFO: BR[3] SAF peering unsubscribe sub-service: pmi succeed Jul 12 02:08:48.264: PROCESS: INFO: MC[3] SAF peering unsubscribe sub-service: cent-policy succeed Jul 12 02:08:48.263: PROCESS: INFO: BR[3] SAF peering unsubscribe sub-service: site-prefix succeed Jul 12 02:08:48.263: PROCESS: INFO: MC[3] SAF peering unsubscribe sub-service: site-prefix succeed Jul 12 02:08:48.263: PROCESS: INFO: BR[3] SAF peering unsubscribe sub-service: globals succeed Jul 12 02:08:48.263: PROCESS: INFO: MC[3] SAF peering unsubscribe sub-service: Capability succeed Jul 12 02:08:48.263: PROCESS: INFO: BR[3] SAF peering unsubscribe sub-service: Capability succeed Jul 12 02:08:48.263: PROCESS: INFO: MC[3] SAF peering unsubscribe sub-service: globals succeed Jul 12 02:08:48.263: PROCESS: INFO: BR[3] Eigrp uncfg opcode: Neighbor multihop, vrf: , interface: Loopback2, action: Delete, result: Succeed Jul 12 02:08:48.298: PROCESS: INFO: BR[3] Deregister CMD client : client id 4, result Succeed Jul 12 02:08:48.299: PROCESS: INFO: BR[3] stopped Jul 12 02:08:48.299: PROCESS: INFO: MC[3] SAF peering unsubscribe sub-service: pmi succeed Jul 12 02:08:49.301: PROCESS: INFO: MC[3] Eigrp uncfg opcode: Family only, vrf: , interface: Loopback2, action: Delete, result: Succeed Displays event trace for PfRv3 processes.

Additional References for PfRv3 Event Tracing

Related Topic	Document Title
PfRv3 commands	Cisco IOS Performance Routing Version 3 Command Reference

Technical Assistance


Description	Link
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password.	http://www.cisco.com/cisco/web/support/index.html

Feature Information for PfRv3 Event Tracing

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Table 1. Feature Information for PfRv3 Event Tracing
Feature Name	Releases	Feature Information
Event Trace for PFRv3 Errors and PFRv3 Channels	Cisco IOS XE Fuji 16.9.1	The Event Trace for PFRv3 feature provides a trace facility for troubleshooting Performance Routing Version 3 (PfRv3). This feature enables you to monitor PfRv3 events and channels. During runtime, the event trace mechanism logs trace information in a buffer space. A display mechanism extracts and decodes the debug data. The following commands were introduced or modified: show monitor event-trace pfrv3 sub-comp channel, show monitor event-trace pfrv3 sub-comp pdp, show monitor event-trace pfrv3 sub-comp policy, show monitor event-trace pfrv3 sub-comp process .

Bias-Free Language

Book Title

Performance Routing Version 3 Configuration Guide, Cisco IOS XE Fuji 16.9.x

Chapter Title

PfRv3 Event Tracing

Results

Chapter: PfRv3 Event Tracing

PfRv3 Event Tracing

Prerequisites for PfRv3 Event Tracing

Restrictions for PfRv3 Event Tracing

Information About PfRv3 Event Tracing

PfRv3 Event Tracing Options

Benefits of PfRv3 Event Tracing

How to Display PfRv3 Event Tracing

SUMMARY STEPS

DETAILED STEPS

Example:

Example:

Example:

Example:

Additional References for PfRv3 Event Tracing

Related Documents

Technical Assistance

Feature Information for PfRv3 Event Tracing

Was this Document Helpful?

Contact Cisco