簡介
本檔案介紹在備援組態管理員(RCM)切換後對使用者層面功能(UPF)升級進行疑難排解。
問題
第1步：在活動UPF（基於RCM）中，觀察到缺失資料塊的例項：
[local]UPF# context n6
[n6]UPF# show ipv6 chunks
Failure: This CLI is only for User-plane
注意：始終在託管UPF的源和目標UCS伺服器上檢查DIMM/ECC/UEC/ADDDC錯誤，並進行RCM tac調試/檢查
第2步：在活動UPF上，在缺少資料塊的情況下，監控SNMP陷阱事件，以將UPF狀態從待機狀態轉換為活動狀態。
[n6]UPF# show snmp trap history verbose | grep RCM
Tuesday November 14 21:16:45 UTC 2023
Mon Oct 13 08:24:42 2023 Internal trap notification 1426 (RCMChassisState) RCM Chassis State: (0) Chassis State Init
Mon Oct 13 08:24:49 2023 Internal trap notification 1414 (RCMServiceStart) Context Name:rcm Service Name:rcm started
Mon Oct 13 08:25:04 2023 Internal trap notification 1425 (RCMTCPConnect) Context Name: rcm
Mon Oct 13 08:25:04 2023 Internal trap notification 1421 (RCMConfigPushCompleteSent) Context Name: rcm
Mon Oct 13 08:25:04 2023 Internal trap notification 1426 (RCMChassisState) RCM Chassis State: (2) Chassis State Standby
Mon Oct 13 08:33:47 2023 Internal trap notification 1420 (RCMConfigPushCompleteReceived) Context Name:
Mon Oct 13 08:33:47 2023 Internal trap notification 1421 (RCMConfigPushCompleteSent) Context Name: rcm
Mon Oct 13 08:48:10 2023 Internal trap notification 1421 (RCMConfigPushCompleteSent) Context Name: rcm
Mon Oct 13 08:48:10 2023 Internal trap notification 1420 (RCMConfigPushCompleteReceived) Context Name: up
Mon Oct 13 08:48:12 2023 Internal trap notification 1426 (RCMChassisState) RCM Chassis State: (1) Chassis State Active
第3步：在活動UPF上，遇到缺少的塊時，檢查系統日誌中是否存在指示相應冗餘組(RG-1)中停止rest(5)sx-demux服務的日誌事件，同時備用UPF將轉換為活動狀態。
Oct 13 08:48:11 UPF evlogd: [local-60sec11.091] [sessctrl 8066 info] [1/0/9050 <sessctrl:0> ctrl_mgrs_cfg.c:2201] [context: up, contextID: 2] [software internal system critical-info syslog] Session Controller: stopping SX-DEMUX service up1 2023-10-13T08:48:11.000+0000
Oct 13 08:48:11 UPF evlogd: [local-60sec11.483] [sessctrl 8066 info] [1/0/9050 <sessctrl:0> ctrl_mgrs_cfg.c:2201] [context: up, contextID: 2] [software internal system critical-info syslog] Session Controller: stopping SX-DEMUX service up2 2023-10-13T08:48:11.000+0000
Oct 13 08:48:11 UPF evlogd: [local-60sec11.582] [sessctrl 8066 info] [1/0/9050 <sessctrl:0> ctrl_mgrs_cfg.c:2201] [context: up, contextID: 2] [software internal system critical-info syslog] Session Controller: stopping SX-DEMUX service up3 2023-10-13T08:48:11.000+0000
Oct 13 08:48:11 UPF evlogd: [local-60sec11.726] [sessctrl 8066 info] [1/0/9050 <sessctrl:0> ctrl_mgrs_cfg.c:2201] [context: up, contextID: 2] [software internal system critical-info syslog] Session Controller: stopping SX-DEMUX service up5 2023-10-13T08:48:11.000+0000
Oct 13 08:48:18 UPF evlogd: [local-60sec18.749] [sessctrl 8066 info] [1/0/9050 <sessctrl:0> ctrl_mgrs_cfg.c:2201] [context: up, contextID: 2] [software internal system critical-info syslog] Session Controller: stopping SX-DEMUX service up6 2023-10-13T08:48:18.000+0000
第4步：在缺少區塊的Active UPF上，啟用debug模式(cli test-commands password <password>)，然後執行命令以監視與UPF活動期間對齊的Sx DeReg事務。
[n6]UPF# show ip pool vpn-sx-transactions
Context: n6
Sx transactions:
sent: 0, received: 0
Failed transactions: 0
**************************************************************************************
Sx Deregistration transactions:
**************************************************************************************
Peer Address Deregistration Time
================================ ====================================================
192.168.1.55 Mon Oct 13 08:48:18 2023
192.168.1.49 Mon Oct 13 08:48:18 2023
192.168.1.49 Mon Oct 13 08:48:18 2023
192.168.2.55 Mon Oct 13 08:48:18 2023
192.168.2.55 Mon Oct 13 08:48:18 2023
192.168.2.49 Mon Oct 13 08:48:18 2023
192.168.2.49 Mon Oct 13 08:48:18 2023
[n6]UPF#
第5步：在缺少資料塊的活動UPF上，搜尋系統日誌，查詢在轉換為「活動」狀態的UPF附近出現的日誌。
Oct 13 08:48:12 UPF evlogd: [local-60sec12.060] [vpn 5013 error] [1/0/9399 <vpnmgr:3> _cups_ip_pool.c:16149] [context: n6, contextID: 3] [software internal system syslog] #01Prefix fd12:3456:7890:abcd::/64 is not allocated to this UP: Closest chunk found with id -2146435055 prefix0: 638057330 start_prefix1: -1391067126 end_prefix1: -1391050752 2023-10-13T08:48:12.000+0000
連續觀察來自vpnmgr例項3任務(vpnmgr:3)的日誌事件。
localsystem:$ less UPF-Destination-UPF-Syslog.log | grep "Pool_name is not present" | head -1
Oct 13 08:48:18 UPF evlogd: [local-60sec18.811] [vpn 5013 error] [1/0/9399 <vpnmgr:3> vpn_ip_pool.c:27493] [context: n6, contextID: 3] [software internal system syslog] #01Pool_name is not present in release request for prefixfd1:3456:7892:abcd::/64 2023-10-13T08:48:18.000+0000
localsystem:$
localsystem:$ less UPF-Destination-UPF-Syslog.log | grep "Pool_name is not present" | tail -1
Oct 13 09:29:59 UPF evlogd: [local-60sec59.671] [vpn 5013 error] [1/0/9399 <vpnmgr:3> vpn_ip_pool.c:27493] [context: n6, contextID: 3] [software internal system syslog] #01Pool_name is not present in release request forprefixfd1:3456:7894:abcd::/64 2023-10-13T09:29:59.000+0000
localsystem:$
解決方案
若要解決此問題，請參閱錯誤報告以瞭解更多詳細資訊：思科錯誤ID CSCwh97931
此問題的解決方法涉及增強SxDemux以防止SRP過渡期間清除IP資料塊，同時提高日誌調試功能。
如果所提到的CDETS修復程式在您使用的UPF生成中尚不可用，則可以採用以下解決方法：
在MW時間範圍內執行標準N4關聯Disassociate/Associate MOP。
意見