Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
Received Assert Metric is 19 and our Metric is 201 but the PIM route put the received metric . 39) Event:E_DEBUG, length:80, at 463415 usecs after Thu Oct 20 18:47:50 2016 [120] (DCT) : (10.156.140.202/32, 239.52.15.222/32), metric-pref: 19, metric: 0 --- Received metric 40) Event:E_DEBUG, length:58, at 463400 usecs after Thu Oct 20 18:47:50 2016 [120] (DCT) : Received Assert from 10.252.130.42 on mti25 45) Event:E_DEBUG, length:59, at 463067 usecs after Thu Oct 20 18:47:50 2016 [120] (DCT) : Changing RPF neighbor, our pref/metric: 201/0 ---- Our metric AB_rtzhtdct01# show ip pim route internal detail vrf dcT | begin 239.52.11.222 (10.158.140.202/32, 239.52.11.222/32), expires 00:03:14, rp-register Incoming interface: mti25, RPF nbr 10.252.130.42 , assert-metric [19/0] Uptime: 01:22:52 Attached: No, Static: No, Other clients have OIFs: No, External: No OTV Decap: No OTV router mode: No Data-created: No, MDT-Encap: No, MDT-Decap: No S/W Stats: 0/0 [Packets/Bytes] H/W Stats: 972807/79770174 [Packets/Bytes] RPF-Source 10.158.140.202, JP-holdtime 210, [0/19] --- Wrong metric is displayed Register Stop Delayed/Received: FALSE/FALSE Oif-list: (0) 00000000, timeout-list: (0) 00000000 Immediate-list: (0) 00000000, timeout-list: (0) 00000000 Sgr-prune-list: (0) 00000000 Assert-win-oif-list: (0) 00000000 Timeout-interval: 4, JP-holdtime round-up: 4 (10.22.1.202/32, 239.52.12.222/32), expires 00:06:44, rp-register Incoming interface: mti25, RPF nbr 10.252.130.42 , assert-metric [19/0] Uptime: 01:22:52 Attached: No, Static: No, Other clients have OIFs: No, External: No OTV Decap: No OTV router mode: No Data-created: No, MDT-Encap: No, MDT-Decap: No S/W Stats: 0/0 [Packets/Bytes] H/W Stats: 1486935/121928670 [Packets/Bytes]
When the multicast has multiple forwarder upstream.
None
When the PIM assert happens on the rpf interface the route's metric and metric -pref changes PIM route copies the received Assert metric as its own metric. Received Assert Metric is 19 and our Metric is 201 but the PIM route put the received metric . 39) Event:E_DEBUG, length:80, at 463415 usecs after Thu Oct 20 18:47:50 2016 [120] (DCT) : (10.156.140.202/32, 239.52.15.222/32), metric-pref: 19, metric: 0 --- Received metric 40) Event:E_DEBUG, length:58, at 463400 usecs after Thu Oct 20 18:47:50 2016 [120] (DCT) : Received Assert from 10.252.130.42 on mti25 45) Event:E_DEBUG, length:59, at 463067 usecs after Thu Oct 20 18:47:50 2016 [120] (DCT) : Changing RPF neighbor, our pref/metric: 201/0 ---- Our metric AB_rtzhtdct01# show ip pim route internal detail vrf dcT | begin 239.52.11.222 (10.158.140.202/32, 239.52.11.222/32), expires 00:03:14, rp-register Incoming interface: mti25, RPF nbr 10.252.130.42 , assert-metric [19/0] Uptime: 01:22:52 Attached: No, Static: No, Other clients have OIFs: No, External: No OTV Decap: No OTV router mode: No Data-created: No, MDT-Encap: No, MDT-Decap: No S/W Stats: 0/0 [Packets/Bytes] H/W Stats: 972807/79770174 [Packets/Bytes] RPF-Source 10.158.140.202, JP-holdtime 210, [0/19] --- Wrong metric is displayed Register Stop Delayed/Received: FALSE/FALSE Oif-list: (0) 00000000, timeout-list: (0) 00000000 Immediate-list: (0) 00000000, timeout-list: (0) 00000000 Sgr-prune-list: (0) 00000000 Assert-win-oif-list: (0) 00000000 Timeout-interval: 4, JP-holdtime round-up: 4 (10.22.1.202/32, 239.52.12.222/32), expires 00:06:44, rp-register Incoming interface: mti25, RPF nbr 10.252.130.42 , assert-metric [19/0] Uptime: 01:22:52 Attached: No, Static: No, Other clients have OIFs: No, External: No OTV Decap: No OTV router mode: No Data-created: No, MDT-Encap: No, MDT-Decap: No S/W Stats: 0/0 [Packets/Bytes] H/W Stats: 1486935/121928670 [Packets/Bytes]