Loading...
Loading...
When N9K-X9624D-R2 in an IPFM environment running One-Step PTP mode with Hardware Offload receives a PIM Join for 224.0.1.129, PTP is no longer processed in hardware on the Linecard and ceases to work correctly. PTP packets originating from the boundary clock will continue and be forwarded out the Master ports. This issue primarily affects PTP packets received on the Master ports from the downstream switches.
SP-1# show ip mroute | begin 224.0.1.129 next 5 (*, 224.0.1.129/32), uptime: 01:46:06, pim ip <<<<<<<<<< (*,G) PIM entry for 224.0.1.129 Incoming interface: Null, RPF nbr: 0.0.0.0 Outgoing interface list: (count: 1) Ethernet3/1, uptime: 01:46:06, pim PTP Delay Request and Delay Response counters will no longer increment: SP-1# show ptp counters interface ethernet 8/1 PTP Packet Counters of Interface Eth8/1: ---------------------------------------------------------------- Packet Type TX RX ---------------- -------------------- -------------------- Announce 358194 43 Sync 2816065 352 FollowUp 0 352 Delay Request 299 508086 <<<<<<< No longer increase. Delay Response 508086 299 <<<<<<<< No longer increase. PDelay Request 0 0 PDelay Response 0 0 PDelay Followup 0 0 Management 0 0 Signaling 0 0 ----------------------------------------------------------------
There are mitigation options available depending on placement. For placement on the boundary clock - Option 1 - The following Global Boundary Multicast configuration can be used to filter PIM and IGMP to exclude only 224.0.1.129: ip prefix-list PTP-FILTER seq 10 deny 224.0.1.129/32 ip prefix-list PTP-FILTER seq 250 permit 224.0.0.0/4 le 32 ip multicast group-range prefix-list PTP-FILTER Option 2 - The following PIM Join Prune Policy can be deployed on uplinks to downstream switches to prune any PIM Joins for 224.0.1.129 while allowing for all other groups: route-map JP-POLICY deny 10 match ip multicast group 224.0.1.129/32 route-map JP-POLICY permit 20 match ip multicast group 224.0.0.0/4 interface Ethernet8/1 ip pim jp-policy JP-POLICY in For placement on the downstream switch originating the PIM Joins - The following IGMP Filter can be deployed on host interface(s) where IGMP Membership Report containing 224.0.1.129 group is being received to exclude while allowing join for all other groups: route-map ptp-igmp-filter deny 10 match ip multicast group 224.0.1.129/32 route-map ptp-igmp-filter permit 20 interface Ethernet1/1 ip igmp report-policy ptp-igmp-filter Once the (*,G) entry for 224.0.1.129 is gone, PTP will work again as confirmed by PTP counters increasing. You can manually clear this by issuing `clear ip pim route 224.0.1.129/32` on the boundary clock & `clear ip igmp route 224.0.1.129/32` on the originating switch.
If the Nexus 9500 chassis also has a N9K-X9636C-RX installed, PTP on this module will continue to work without issue in the case of PTP group PIM entry. Due to changes made to resolve CSCvm11554, as of 10.2(2), IGMP for the PTP group is blocked on Nexus 9500s using -R/RX modules.
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.