Catalyst 9000交換器上的Precision時間通訊協定疑難排解
簡介
本文說明如何對Catalyst 9000交換器上的精確時間通訊協定(PTP)進行疑難排解。
必要條件
需求
思科建議您瞭解以下主題：
- 精確時間通訊協定(PTP)
採用元件
本檔案中的資訊是根據Catalyst 9300、9400、9500和9600交換器。
本文中的資訊是根據特定實驗室環境內的裝置所建立。文中使用到的所有裝置皆從已清除（預設）的組態來啟動。如果您的網路運作中，請確保您瞭解任何指令可能造成的影響。
慣例
如需檔案慣例的詳細資訊，請參閱思科技術提示和慣例。
限制和限制
- Catalyst 9200交換機不支援PTP，但從17.14.01開始的C9200CX交換機支援PTP。
- 在17.06.01之前，Stackwise部署中的Catalyst 9300交換機不支援PTP。
- 在17.10.01之前，Stackwise-Virtual中的Catalyst 9400、9500或9600交換機不支援PTP
Cisco Catalyst交換機支援Precision時間協定常見問題
有關適用於Catalyst 9000的PTP的限制和限制的詳盡清單，請參閱給定平台和版本的第2層配置指南的PTP部分。
技術
| 字詞 | 定義 |
大師級時鐘(GMC) |
在PTP域內，主時鐘是使用PTP進行時鐘同步的主要時間源。特級時鐘通常有非常精確的時間源，例如GPS或原子鐘。當網路不需要任何外部時間參考且只需要內部同步時，主時鐘可以自由運行。 |
普通時鐘(OC) |
普通時鐘是具有單個PTP埠的PTP時鐘。它作為PTP網路中的節點運行，並可被BMCA選為子域內的主節點或從節點。普通時鐘是PTP網路上最常見的時鐘型別，因為它們用作連線到需要同步的裝置上的網路端節點。普通時鐘與外部裝置有不同的介面。 |
| 邊界鍾(BC) | PTP網路中的邊界時鐘代替標準網路交換機或路由器運行。邊界時鐘有多個PTP埠，每個埠提供對獨立PTP通訊路徑的訪問。邊界時鐘提供PTP域之間的介面。它們會攔截和處理所有PTP消息，並傳遞所有其他網路流量。邊界時鐘使用BMCA選擇任何埠所看到的最佳時鐘。然後，將選定的埠設定為從埠。主埠同步下游連線的時鐘，而從埠同步上遊主時鐘。 |
| 透通時鐘(TC) | PTP網路中透明時鐘的作用是更新PTP事件消息中的時間間隔欄位。此更新補償了交換機延遲，其精確度在1皮秒以內。透明時鐘有兩種型別： |
| 端到端(E2E)透明 | 測量SYNC和DELAY_REQUEST消息的PTP事件消息傳輸時間（也稱為駐留時間）。此測量的傳輸時間將新增到相應消息中的資料欄位（更正欄位）中：
|
| 對等(P2P)透明 | 如上所述使用E2E透明時鐘來測量PTP事件消息傳輸時間。此外，P2P透明時鐘可以測量上行鏈路的延遲。上游鏈路延遲是所考慮的上游鄰居P2P透明時鐘和P2P透明時鐘之間的估計分組傳播延遲。這兩次（消息傳送時間和上行鏈路延遲時間）都被新增到PTP事件消息的校正欄位，並且從裝置接收的消息的校正欄位包含所有鏈路延遲的總和。理論上，這是SYNC資料包的端到端總延遲（從主到從）。 |
PTP時鐘故障同步
原因：
- 導致在介面（傳輸中）或通過控制平面策略(CoPP)緩衝或丟棄PTP資料包的網路擁塞。
- 防火牆攔截PTP資料包。
- 耗盡硬體資源，如CPU、記憶體或TCAM。
- 硬體或軟體限制，無法精確測量時間。
要採取的操作：
檢視show命令疑難排解流程
特定故障點
通告和發現
| 症狀 | 可能起因 |
| 普通時鐘CPU不處理來自GMC的通告資料包。普通時鐘不會傳送延遲請求資料包。在PTP協商之後，時鐘無法同步。 | Grandmaster Clock未配置為傳送Announce packets.PTP Packets lost in transit。介面、控制平面或ASIC丟棄的PTP資料包。配置錯誤導致GMC傳送錯誤的PTP域/配置檔案或普通時鐘配置了錯誤的域/配置檔案。 |
要採取的操作：
驗證PTP配置和狀態：
執行介面或控制平面EPC以驗證時鐘正在接收和傳送PTP資料包：
如果EPC不可靠，請使用PTP調試收集的資料來驗證正在傳送和接收的PTP值：
最佳主時鐘演演算法(BMCA)
| 症狀 | 可能起因 |
| 同步失敗 忽略或拒絕來自GMC的PTP消息的時鐘 記錄錯誤重新同步嘗試 |
網路裝置和GMC之間的PTP版本不相容。Announce packets中的時鐘資料不準確。同一域中的多個主時鐘引起的時鐘不穩定性。 |
要採取的操作：
排除任何可能導致延遲或不準確計時的中轉時鐘或邊界時鐘。
排除平台上的任何硬體或軟體限制，這些限制會妨礙精確計時。
收集PTP調試並檢查是否有任何錯誤。
主時鐘選擇
| 症狀 | 可能起因 |
| 最佳主時鐘演算法(BMCA)不選擇最準確的GMC。BMCA不計算網路延遲。優先順序設定不匹配。 |
要採取的操作：
同步郵件交換
| 症狀 | 可能起因 |
| 透明時鐘(TC)配置錯誤，例如PTP配置檔案或模式不正確。延遲計算錯誤。同步消息資料包在傳輸中或OC的控制平面上丟棄。 |
要採取的操作：
延遲請求和響應
| 症狀 | 可能起因 |
| 透明時鐘無法計算精確的時間戳，從而導致不準確的延遲計算。延遲請求或響應資料包以錯誤的順序接收、在傳輸過程中丟失或在控制平面之前被丟棄 |
要採取的操作：
更正和同步
| 症狀 | 可能起因 |
| 由時鐘計算的不準確的時間校正和延遲補償。硬體或軟體限制導致不正確的系統時鐘調整，從而導致同步失敗。 |
要採取的操作
PTP命令列介面Show命令
驗證PTP模式、配置檔案、身份、域、啟用PTP的介面和PTP介面的狀態：
Cat9300#show ptp clock PTP CLOCK INFO PTP Device Type: Unknown PTP Device Profile: Default Profile Clock Identity: 0x70:B:4F:FF:FE:A8:52:80 Clock Domain: 0 Network Transport Protocol: 802.3 Number of PTP ports: 0 Cat9300#
沒有PTP配置的介面將保留在域0中並處於INITIALIZING狀態。
Cat9300#show ptp brief Interface Domain PTP State GigabitEthernet1/0/1 0 INITIALIZING
這是端到端透明模式下時鐘的過渡階段。
Cat9300#configuration terminal Cat9300(config)#interface twe1/0/1 Cat9300(config-if)#shut Cat9300(config-if)#no shut Cat9300(config-if)#end %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to down Cat9300#show ptp brief | i 1/0/1 Interface Domain PTP State TwentyFiveGigE1/0/1 8 FAULTY %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to up Cat9300#show ptp brief | i 1/0/1 Interface Domain PTP State TwentyFiveGigE1/0/1 8 LISTENING %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to up Cat9300#show ptp brief | i 1/0/1 Interface Domain PTP State TwentyFiveGigE1/0/1 8 UNCALIBRATED Cat9300#show ptp brief | i 1/0/1 Interface Domain PTP State TwentyFiveGigE1/0/1 8 SLAVE
Cat9300#show platform software fed switch active ptp debugs interface twe1/0/1 Offload Monitor Data: ======================================= Ofld sig cnt: 0, Ofld ts cnt: 0, Ofld miss cnt: 0, Ofld issue hit: 0 Sig (rd,wr)ptr: (0,0), Nif (rd,wr)ptr: (0,0) Drop counters: ======================================= ptp messages dropped due to qos drain count : 0
Cat9300#show platform software fed switch active ifm mappings Interface IF_ID Inst Asic Core Port SubPort Mac Cntx LPN GPN Type Active TwentyFiveGigE1/0/1 0x9 0 0 0 0 0 7 8 1 1 NRU Y <> Cat9300#show platform software fed switch active ptp if-id 0x009 Displaying port data for if_id 9 ======================================= Port Mac Address 9C:54:16:AE:4C:81 Port Clock Identity 9C:54:16:FF:FE:AE:4C:80 Port number 1 PTP Version 2 domain_value 8 Profile Type: : DEFAULT Clock Mode : TRANSPARENT CLOCK E2E Delay mechanism: End-to-End port_enabled: TRUE ptt_port_enabled: TRUE Port state: : SLAVE sync_seq_num 52439 delay_req_seq_num 0 ptp vlan is valid : TRUE ptp vlan id 10 port mode 2 tag native vlan : FALSE num sync messages transmitted 0 num followup messages transmitted 0 num sync messages received 4434 num followup messages received 4434 num delay requests transmitted 0 num delay responses received 0 num delay requests received 0 num delay responses transmitted 0
Cat9300#show platform software fed switch active ptp domain Displaying data for domain number 8 ======================================= Profile Type : DEFAULT Profile State: enabled Clock Mode : TRANSPARENT CLOCK E2E Delay Mechanism: : END-TO-END PTP clock : 1970-1-1 1:45:13 mean_path_delay 0 nanoseconds Transport Method : 802.3 Message general ip dscp : 59 Message event ip dscp : 47
Cat9300#show platform software fed switch active ptp auto-calibrate PTP Auto Calibration: PTP auto_calibration status : FALSE
C9300-4c80#ptp calibrate interface twe1/0/1 speed all %SYS-5-CONFIG_P: Configured programmatically by process PTP protocol engine from console as vty0 %PTP_RP_MODULE-6-PTP_AUTO_CALIBRATION_COMPLETE: PTP auto calibration on the interface TwentyFiveGigE1/0/1 is complete %SYS-5-CONFIG_P: Configured programmatically by process PTP protocol engine from console as vty0
檢查平台資源
檢查介面
PTP資料包路徑中的輸入丟棄、輸出丟棄或CRC錯誤的非零值會導致故障。
Cat9300#show interfaces twe1/0/1 human-readable
TwentyFiveGigE1/0/1 is up, line protocol is up (connected)
Hardware is Twenty Five Gigabit Ethernet, address is 9c54.16ae.4c81 (bia 9c54.16ae.4c81)
MTU 1500 bytes, BW 10000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not set
Full-duplex, 10Gb/s, link type is auto, media type is SFP-10GBase-CX1
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 3.0 kilobits , 5 pps
5 minute output rate 0 bits/sec, 0 packets/sec
26,497 packets input, 1,955,114 bytes, 0 no buffer
Received 26,477 broadcasts (26,476 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 26,476 multicast, 0 pause input
0 input packets with dribble condition detected
947 packets output, 124,533 bytes, 0 underruns
Output 17 broadcasts (917 multicasts)
0 output errors, 0 collisions, 3 interface resets
2 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
檢查控制階段管制
PTP資料包通過低延遲隊列進行處理。PTP流量與其他網路流量型別共用策略索引，因此最好驗證控制平面上沒有遞增丟包。
Cat9300#show platform hardware fed switch active qos queue stats internal cpu policier
CPU Queue Statistics
============================================================================================
(default) (set) Queue Queue
QId PlcIdx Queue Name Enabled Rate Rate Drop(Bytes) Drop(Frames)
--------------------------------------------------------------------------------------------
0 11 DOT1X Auth Yes 1000 1000 0 0
1 1 L2 Control Yes 2000 2000 0 0
2 14 Forus traffic Yes 4000 4000 0 0
3 0 ICMP GEN Yes 600 600 0 0
4 2 Routing Control Yes 5400 5400 0 0
5 14 Forus Address resolution Yes 4000 4000 0 0
6 0 ICMP Redirect Yes 600 600 0 0
7 16 Inter FED Traffic Yes 2000 2000 0 0
8 4 L2 LVX Cont Pack Yes 1000 1000 0 0
9 19 EWLC Control Yes 13000 13000 0 0
10 16 EWLC Data Yes 2000 2000 0 0
11 13 L2 LVX Data Pack Yes 1000 1000 0 0
12 0 BROADCAST Yes 600 600 0 0
13 10 Openflow Yes 200 200 0 0
14 13 Sw forwarding Yes 1000 1000 0 0
15 8 Topology Control Yes 13000 13000 0 0
16 12 Proto Snooping Yes 2000 2000 0 0
17 6 DHCP Snooping Yes 400 400 0 0
18 13 Transit Traffic Yes 1000 1000 0 0
19 10 RPF Failed Yes 200 200 0 0
20 15 MCAST END STATION Yes 2000 2000 0 0
21 13 LOGGING Yes 1000 1000 0 0
22 7 Punt Webauth Yes 1000 1000 0 0
23 18 High Rate App Yes 13000 13000 0 0
24 10 Exception Yes 200 200 0 0
25 3 System Critical Yes 1000 1000 0 0
26 10 NFL SAMPLED DATA Yes 200 200 0 0
27 2 Low Latency Yes 5400 5400 0 0 <<< Queue for PTP traffic.
28 10 EGR Exception Yes 200 200 0 0
29 5 Stackwise Virtual OOB Yes 8000 8000 0 0
30 9 MCAST Data Yes 400 400 0 0
31 3 Gold Pkt Yes 1000 1000 0 0
* NOTE: CPU queue policer rates are configured to the closest hardware supported value
CPU Queue Policer Statistics
====================================================================
Policer Policer Accept Policer Accept Policer Drop Policer Drop
Index Bytes Frames Bytes Frames
-------------------------------------------------------------------
0 4052 48 0 0
1 3520420 10686 0 0
2 1966076 16634 0 0 <<< PTP packets share this Policier Index w/other network traffic.
3 0 0 0 0
4 0 0 0 0
5 0 0 0 0
6 0 0 0 0
7 0 0 0 0
8 2937088 45892 0 0
9 0 0 0 0
10 1770 15 0 0
11 0 0 0 0
12 0 0 0 0
13 20246 191 0 0
14 24918 252 0 0
15 0 0 0 0
16 0 0 0 0
17 0 0 0 0
18 0 0 0 0
19 0 0 0 0
Second Level Policer Statistics
====================================================================
20 8423584 73212 0 0
21 50986 506 0 0
Policer Index Mapping and Settings
--------------------------------------------------------------------
level-2 : level-1 (default) (set)
PlcIndex : PlcIndex rate rate
--------------------------------------------------------------------
20 : 1 2 8 13000 13000
21 : 0 4 7 9 10 11 12 13 14 15 6000 6000
====================================================================
Second Level Policer Config
====================================================================
level-1 level-2 level-2
QId PlcIdx PlcIdx Queue Name Enabled
--------------------------------------------------------------------
0 11 21 DOT1X Auth Yes
1 1 20 L2 Control Yes
2 14 21 Forus traffic Yes
3 0 21 ICMP GEN Yes
4 2 20 Routing Control Yes
5 14 21 Forus Address resolution Yes
6 0 21 ICMP Redirect Yes
7 16 - Inter FED Traffic No
8 4 21 L2 LVX Cont Pack Yes
9 19 - EWLC Control No
10 16 - EWLC Data No
11 13 21 L2 LVX Data Pack Yes
12 0 21 BROADCAST Yes
13 10 21 Openflow Yes
14 13 21 Sw forwarding Yes
15 8 20 Topology Control Yes
16 12 21 Proto Snooping Yes
17 6 - DHCP Snooping No
18 13 21 Transit Traffic Yes
19 10 21 RPF Failed Yes
20 15 21 MCAST END STATION Yes
21 13 21 LOGGING Yes
22 7 21 Punt Webauth Yes
23 18 - High Rate App No
24 10 21 Exception Yes
25 3 - System Critical No
26 10 21 NFL SAMPLED DATA Yes
27 2 20 Low Latency Yes
28 10 21 EGR Exception Yes
29 5 - Stackwise Virtual OOB No
30 9 21 MCAST Data Yes
31 3 - Gold Pkt No
<>
檢查CPU和記憶體
Cat9300#show platform resources **State Acronym: H - Healthy, W - Warning, C - Critical Resource Usage Max Warning Critical State ---------------------------------------------------------------------------------------------------- Control Processor 1.28% 100% 90% 95% H DRAM 3566MB(47%) 7575MB 85% 90% H TMPFS 1001MB(13%) 7575MB 40% 50% H show processes cpu sorted | ex 0.00 show cpu history show processes memory sorted
檢查TCAM
Cat9300#show platform hardware fed switch active fwd-asic resource tcam utilization Codes: EM - Exact_Match, I - Input, O - Output, IO - Input & Output, NA - Not Applicable CAM Utilization for ASIC [0] Table Subtype Dir Max Used %Used V4 V6 MPLS Other ------------------------------------------------------------------------------------------------------ Mac Address Table EM I 32768 20 0.06% 0 0 0 20 Mac Address Table TCAM I 1024 21 2.05% 0 0 0 21 L3 Multicast EM I 8192 0 0.00% 0 0 0 0 L3 Multicast TCAM I 512 9 1.76% 3 6 0 0 L2 Multicast EM I 8192 0 0.00% 0 0 0 0 L2 Multicast TCAM I 512 11 2.15% 3 8 0 0 IP Route Table EM I 24576 12 0.05% 11 0 1 0 IP Route Table TCAM I 8192 25 0.31% 12 10 2 1 QOS ACL TCAM IO 5120 85 1.66% 28 38 0 19 Security ACL TCAM IO 5120 129 2.52% 26 58 0 45 Netflow ACL TCAM I 256 6 2.34% 2 2 0 2 PBR ACL TCAM I 1024 22 2.15% 16 6 0 0 Netflow ACL TCAM O 768 6 0.78% 2 2 0 2 Flow SPAN ACL TCAM IO 1024 13 1.27% 3 6 0 4 Control Plane TCAM I 512 282 55.08% 130 106 0 46 <<< Expected to be at least 50% Tunnel Termination TCAM I 512 18 3.52% 8 10 0 0 Lisp Inst Mapping TCAM I 2048 1 0.05% 0 0 0 1 Security Association TCAM I 256 4 1.56% 2 2 0 0 CTS Cell Matrix/VPN Label EM O 8192 0 0.00% 0 0 0 0 CTS Cell Matrix/VPN Label TCAM O 512 1 0.20% 0 0 0 1 Client Table EM I 4096 0 0.00% 0 0 0 0 Client Table TCAM I 256 0 0.00% 0 0 0 0 Input Group LE TCAM I 1024 0 0.00% 0 0 0 0 Output Group LE TCAM O 1024 0 0.00% 0 0 0 0 Macsec SPD TCAM I 256 2 0.78% 0 0 0 2
平台工具
執行嵌入式資料包捕獲(EPC)
配置EPC
Cat9300#monitor capture tac [interface | control-plane] [in | out | both] [match | access-list] buffer size 100
附註：有關更多EPC配置選項，請檢視給定平台/版本的《網路管理配置指南》。
在介面級別驗證Rx PTP資料包
Cat9300#monitor capture tac interface twe1/0/1 in match any buffer size 100
Cat9300#monitor capture tac start
Started capture point : tac
%BUFCAP-6-ENABLE: Capture Point tac enabled.
C9300-4c80#monitor capture stop
Capture statistics collected at software:
Capture duration - 3 seconds
Packets received - 28
Packets dropped - 0
Packets oversized - 0
Bytes dropped in asic - 0
Capture buffer exists till exported or cleared
Stopped capture point : tac
%BUFCAP-6-DISABLE: Capture Point tac disabled.
C9300-4c80#show monitor capture tac buffer brief | i PTP
2 0.032858 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message
12 1.032894 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message
15 2.032831 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message
28 3.033414 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message
檢驗Rx資料包是否到達控制平面
Cat9300#monitor capture cpu control-plane in match any buffer size 100 Cat9300#monitor capture cpu start Started capture point : cpu Cat9300# *Sep 28 14:05:28.375: %BUFCAP-6-ENABLE: Capture Point cpu enabled. Cat9300#
在控制平面級別驗證Tx PTP資料包
這表示Cisco IOS® XE軟體和CPU正在生成Rx PTP資料包。
附註：在下一躍點交換器或SPAN/RSPAN上的輸入EPC更可靠以驗證本地普通時鐘正在發出PTP封包。
附註：CPU生成的資料包（如「 」）在出口端不會看到，EPC配置在物理介面上，這是EPC工具的書面限制。
Cat9300#monitor capture cpu control-plane out match any buffer size 100 Cat9300#monitor capture cpu start
收集PTP調試
| 偵錯 | 目的 |
| 自動校準 | |
| bmc | 顯示介面的選定對象。 |
| 消息 |
自動校準調試
21:41:12.543: %LINK-5-CHANGED: Interface TwentyFiveGigE1/0/1, changed state to administratively down 21:41:13.542: %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to down 21:41:13.543: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down 1:41:29.714: Autocalibration: No autocalibration is progress (status - 0) or linkup interface TwentyFiveGigE1/0/1 different from autocalibrtion interface No interface 21:41:30.118: %SYS-5-CONFIG_I: Configured from console by console 21:41:31.714: %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to down 21:41:35.821: %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to up 21:41:37.824: %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to up 21:41:37.824: Autocalibration: No autocalibration is progress (status - 0) or linkup interface TwentyFiveGigE1/0/1 different from autocalibrtion interface No interface 21:41:38.849: Autocalibration: No autocalibration is progress (status - 0) or linkup interface Vlan10 different from autocalibrtion interface No interface 21:41:39.849: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up
bmc debug
21:41:12.543: %LINK-5-CHANGED: Interface TwentyFiveGigE1/0/1, changed state to administratively down 21:41:13.542: %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to down 21:41:13.543: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to down 21:41:30.118: %SYS-5-CONFIG_I: Configured from console by console 21:41:31.714: %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to down 21:41:35.821: %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to up 21:41:37.824: %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to up 21:41:39.849: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up 21:41:40.277: Set gmc interface: TwentyFiveGigE1/0/1 <<<
消息調試
Cat9300#clear logging
Cat9300#conf t Enter configuration commands, one per line. End with CNTL/Z. Clear logging buffer [confirm] Cat9300(config)# Cat9300(config)#int twe1/0/1 Cat9300(config-if)#shut Cat9300(config-if)#end Cat9300# Cat9300#debug ptp messages PTP Messages debugging is on Cat9300# Cat9300#conf t Enter configuration commands, one per line. End with CNTL/Z. Cat9300(config)#interface twe1/0/1 Cat9300(config-if)#no shut Cat9300(config-if)#end Cat9300# Cat9300#show ptp bri | i 1/0/1 TwentyFiveGigE1/0/1 8 FAULTY Cat9300#show ptp bri | i 1/0/1 TwentyFiveGigE1/0/1 8 LISTENING Cat9300#show ptp bri | i 1/0/1 TwentyFiveGigE1/0/1 8 UNCALIBRATED Cat9300#show ptp bri | i 1/0/1 TwentyFiveGigE1/0/1 8 SLAVE Cat9300#undebug all All possible debugging has been turned off Cat9300# Cat9300#show logging <> Log Buffer (131072 bytes): 21:59:06.980: %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to down 21:59:07.826: %SYS-5-CONFIG_I: Configured from console by console 21:59:11.271: %LINK-3-UPDOWN: Interface TwentyFiveGigE1/0/1, changed state to up 21:59:12.976: Cisco IOS-FMAN-PTP:retrieve interface: Twe1/0/1 iif_id: 9(fmanrp_ptp_port_data_update) ptp port data: <<< local data sent by clock if_hdl = 9 mac address = 9c54.16ae.4c81 <<< similar to local clock identity domain_value = 8 port_number = 1 port_state = 4 port_enabled = 1 ptt_port_enabled = 1 delete_flag = False
21:59:13.273: %LINEPROTO-5-UPDOWN: Line protocol on Interface TwentyFiveGigE1/0/1, changed state to up <<< 21:59:13.846: received message on TwentyFiveGigE1/0/1 <<< 21:59:13.846: PTP message received, intf: TwentyFiveGigE1/0/1, type: ANNOUNCE 21:59:14.846: received message on TwentyFiveGigE1/0/1 21:59:14.846: PTP message received, intf: TwentyFiveGigE1/0/1, type: ANNOUNCE 21:59:15.845: received message on TwentyFiveGigE1/0/1 21:59:15.845: PTP message received, intf: TwentyFiveGigE1/0/1, type: ANNOUNCE 21:59:15.976: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan10, changed state to up 21:59:16.775: Set gmc interface: TwentyFiveGigE1/0/1 <<<
執行Show Platform Forward(SPF)
如果看到PTP資料包到達介面但未傳送到控制平面，請運行此工具。
1. Configure ingress EPC on PTP enabled interface.
2. View buffer output and filter for PTP and make note of PTP packet number. Cat9300#show monitor capture tac buffer brief | i PTP 2 0.032858 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message <<< 12 1.032894 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message 15 2.032831 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message 28 3.033414 74:8f:c2:dc:b0:63 -> 01:1b:19:00:00:00 PTPv2 82 Announce Message
3. Export buffer to .pcap on Switch's flash. Cat9300-4c80#monitor capture tac export location flash:/ptp-cpu.pcap
4. Execute the SPF command and make note of interface where PTP packets are expected to ingress and reference the packet number from buffer brief command. Cat9300#show platform hardware fed switch active forward interface twe1/0/1 pcap flash:ptp-cpu.pcap number 2 data Show forward is running in the background. After completion, syslog can be generated. 4. View Forward/Drop decision Cat9300#show platform hardware fed switch active forward last summary Input Packet Details: ###[ Ethernet ]### dst = 01:1b:19:00:00:00 src=74:8f:c2:dc:b0:63 type = 0x8100 ###[ 802.1Q ]### prio = 0 id = 0 vlan = 10 type = 0x88f7 ###[ Raw ]### load = '0B 02 00 40 08 00 00 08 00 00 00 00 00 00 00 00 00 00 00 00 74 8F C2 FF FE DC B0 60 00 03 0B 11 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 F8 FE 43 6A 80 74 8F C2 FF FE DC B0 60 00 00 A0' Ingress: Port : TwentyFiveGigE1/0/1 Global Port Number : 1 Local Port Number : 1 Asic Port Number : 0 Asic Instance : 0 Vlan : 10 Mapped Vlan ID : 5 STP Instance : 3 BlockForward : 0 BlockLearn : 0 L3 Interface : 38 IPv4 Routing : enabled IPv6 Routing : enabled Vrf Id : 0 Adjacency: Station Index : 172 Destination Index : 21151 Rewrite Index : 1 Replication Bit Map : 0xa ['localCpu', 'remoteCpu'] Decision: Destination Index : 21151 [DI_CPUQ_LOW_LATENCY] Rewrite Index : 1 [RI_CPU] Dest Mod Index : 0 [IGR_FIXED_DMI_NULL_VALUE] CPU Map Index : 0 [CMI_NULL] Forwarding Mode : 0 [Bridging] Replication Bit Map : ['localCpu', 'remoteCpu'] Winner : CPPMAC LOOKUP2 Qos Label : 65 SGT : 0 DGTID : 0 Egress: Possible Replication : Port : CPU_Q_LOW_LATENCY <<< This should be the forwarding decision to this CPU queue. Any drops are unexpected and should be investigated. Output Port Data : Port : CPU Asic Instance : 0 CPU Queue : 27 [CPU_Q_LOW_LATENCY] Unique RI : 0 Rewrite Type : 0 [Unknown] Mapped Rewrite Type : 17 [CPU_ENCAP] Vlan : 10 Mapped Vlan ID : 5 ******************************************************************************** C9300-4c80#
執行Packet Tracer(PT)
Catalyst 9000上的PTP警告
| 思科錯誤 ID | 標題思科錯誤ID |
| 思科錯誤ID CSCvg24999 | 在ptp mode p2ptransparent上交換機崩潰。 |
| 思科錯誤ID CSCwf81913 | PTP在Catalyst交換機上停止工作，埠進入未校準的狀態。 |
| 思科錯誤ID CSCwa49052 | PTP偏移和平均路徑延遲可能會停滯在故障交換機上，而且永遠不會增加。思科錯誤ID |
| 思科錯誤ID CSCvu73652 | C9300 — 源埠不等於319的PTP事件消息被丟棄。 思科錯誤 ID |
| 思科錯誤ID CSCwc35946 | 在8275.1、802.1AS和預設PTP配置檔案之間更改時，CLI選項不一致。 |
| 思科錯誤ID CSCwc00050 | 無法通過Web UI更改PTP模式 |
相關資訊
修訂記錄
| 修訂 | 發佈日期 | 意見 |
|---|---|---|
1.0 |
10-Oct-2023
|
初始版本 |
意見