Fehlerbehebung für das SMF-Fehlerprotokoll "Alle Peers sind inaktiv"
Einleitung
In diesem Dokument wird die Fehlerbehebung bei SMF-Protokollwarnungen (Session Management Function) im Zusammenhang mit All Peers are Dead, Setting status code to 0.
Problem
Die Auswirkung der Sitzung wurde auf die SMF gemeldet.
Analyse
Alle Peers sind tot.
Das Protokoll gibt an, dass alle Peers in SelectedProfileName:CHF-OFF ausgefallen sind.
Das Protokoll deckt alle auf SMF konfigurierten Endpunkte ab, und jedes Mal, wenn im Profil alle Peers inaktiv sind, führt dies zu Sitzungsbeeinträchtigungen.
master-1 b26897bce81a[2516]:
master-1 c77834f772f7[2516]: ************* TRANSACTION: 2475167152 *************
master-1 c77834f772f7[2516]: ************* TRANSACTION: 2475167152 *************
master-1 c77834f772f7[2516]: TRANSACTION SUCCESS:
master-1 c77834f772f7[2516]: TRANSACTION SUCCESS:
master-1 c77834f772f7[2516]: GR Instance ID : 1
master-1 c77834f772f7[2516]: GR Instance ID : 1
master-1 c77834f772f7[2516]: Txn Type : N40ChargingDataReq(3585)
master-1 c77834f772f7[2516]: Txn Type : N40ChargingDataReq(3585)
master-1 c77834f772f7[2516]: Priority : 1
master-1 c77834f772f7[2516]: Priority : 1
master-1 c77834f772f7[2516]: Session Namespace : smf(1)
master-1 c77834f772f7[2516]: Session Namespace : smf(1)
master-1 c77834f772f7[2516]: CDL Slice Name : smf
master-1 c77834f772f7[2516]: CDL Slice Name : smf
master-1 c77834f772f7[2516]: LOG MESSAGES:
master-1 c77834f772f7[2516]: LOG MESSAGES:
master-1 c77834f772f7[2516]: 2023/09/10 15:00:00.007 [ERROR] [nrfClient.Discovery.nrf] All Peers are Dead, Setting status code to 0 (timeout)
master-1 c77834f772f7[2516]: 2023/09/10 15:00:00.007 [ERROR] [nrfClient.Discovery.nrf] All Peers are Dead, Setting status code to 0 (timeout)
master-1 c77834f772f7[2516]: 2023/09/10 15:00:00.007 [ERROR] [nrfClient.Discovery.nrf] Message send failed, response [Type:CHF ServiceName:nchf-convergedcharging SelectedProfileName:"CHF-OFF" FailureProfile:"Fail-H-CHF-OFF" GroupID:"CHF-*" ]
master-1 c77834f772f7[2516]: 2023/09/10 15:00:00.007 [ERROR] [nrfClient.Discovery.nrf] Message send failed, response [Type:CHF ServiceName:nchf-convergedcharging SelectedProfileName:"CHF-OFF" FailureProfile:"Fail-H-CHF-OFF" GroupID:"CHF-*" ]
master-1 c77834f772f7[2516]: ***********************************************
master-1 c77834f772f7[2516]: ***********************************************
Basierend auf der Konfiguration versucht die SMF, den primären Server mit höherer Priorität zu erreichen, falls ein HTTP-Code-504-System (Timeout) vorhanden ist, und dann versucht die SMF, den sekundären Server zu erreichen. Wenn dies fehlschlägt, setzt das System auch die Sitzung in den Fortsetzungsmodus.
Im Beispiel ist die sekundäre Charging-Funktion (CHF) für Offline 10.10.10.2. Die SMF hat den Fehler 504 empfangen, und die Aktion lautet FailureContinueAction.
master-2 42013075464a[2621]: 2023/09/10 15:00:00.063 rest-ep [ERROR] [RestClient.go:175] [infra.rest_client.core] Error in rest call err Post "http://10.10.10.2:1090/OFFLINE/nchf-convergedcharging/v2/chargingdata": context deadline exceeded
master-2 42013075464a[2621]: 2023/09/10 15:00:00.063 rest-ep [ERROR] [Config.go:1721] [nrfClient.Discovery.nrf] Send to NF rpcName[CHF], method:[DataRequest] EndPoint[http://10.10.10.2:1090/OFFLINE/nchf-convergedcharging/v2] failed
master-2 42013075464a[2621]: ************* TRANSACTION: 2252879781 *************
master-2 42013075464a[2621]: TRANSACTION SUCCESS:
master-2 42013075464a[2621]: GR Instance ID : 1
master-2 42013075464a[2621]: Txn Type : N40ChargingDataReq(3521)
master-2 42013075464a[2621]: Priority : 1
master-2 42013075464a[2621]: Session Namespace : smf(1)
master-2 42013075464a[2621]: CDL Slice Name : smf
master-2 42013075464a[2621]: LOG MESSAGES:
master-2 42013075464a[2621]: 2023/09/10 15:00:00.063 [ERROR] [rest_ep.app.ChargingIntf] {imsi-1234567891011121:21} Received Charging Data Response error with timediff 10001557123 - Request message {{"invocationSequenceNumber":1,"invocationTimeStamp":"2025-11-10T14:29:29Z","nfConsumerIdentification":{"nFIPv4Address":"10.10.10.12","nFName":"dce0c1d7-aa37-4f2c-870b-6f7c1be10af1","nFPLMNID":{"mcc":"123","mnc":"456"},"nodeFunctionality":"SMF"},"notifyUri":"http://10.10.10.12:8195/callbacks/v2/notifyUri/1909959397/chargingNotification","pDUSessionChargingInformation":{"chargingId":1909959397,"pduSessionInformation":{"authorizedQoSInformation":{"5qi":1,"arp":{"preemptCap":"NOT_PREEMPT","preemptVuln":"PREEMPTABLE","priorityLevel":1}},"authorizedSessionAMBR":{"downlink":"2048000 bps","uplink":"2048000 bps"},"chargingCharacteristicsSelectionMode":"VISITING_DEFAULT","dnnId":"data","hPlmnId":{"mcc":"123","mnc":"456"},"networkSlicingInfo":{"sNSSAI":{"sst":1}},"pduAddress":{"iPv6dynamicPrefixFlag":true,"pduIPv6AddresswithPrefix":"x:x:x:x::"},"pduSessionID":21,"pduType":"IPV6","ratType":"WLAN","servingCNPlmnId":{"mcc":"123","mnc":"456"},"sscMode":"SSC_MODE_1","startTime":"2025-11-10T14:29:29Z"},"userInformation":{"roamerInOut":"IN_BOUND","servedGPSI":"msisdn-12345678901"},"userLocationinfo":{"n3gaLocation":{"portNumber":4505,"ueIpv4Addr":"x.x.x.x"}}},"subscriberIdentifier":{"subscriberIdentityType":"SUPI","supi":"imsi-1234567891011121"}}}
master-2 42013075464a[2621]: 2023/09/10 15:00:00.063 [ERROR] [nrfClient.SendMesg.NRF] FHI status 504 timediff 1000332537, Uri: http://10.10.10.2:1090/OFFLINE/nchf-convergedcharging/v2, retryCount = 0 loopMaxRetry = 0, maxRetry = 0
master-2 42013075464a[2621]: 2023/09/10 15:00:00.063 [ERROR] [nrfClient.Discovery.nrf] Message send failed, response [Type:CHF Http2_Status:504 FailAction:FailureContinueAction MsgType:3587 ServiceName:nchf-convergedcharging SelectedProfileName:"CHF-OFF" FailureProfile:"Fail-H-CHF-OFF" GroupID:"CHF-*" ]
master-2 42013075464a[2621]: ***********************************************
SMF-Prüfungen
Überprüfen Sie auf SMF die Peers und deren Verbindungszeit in Bezug auf den Endpunkt, der das Problem gemeldet hat.
smf# show peers GR POD CONNECTED ADDITIONAL INSTANCE ENDPOINT LOCAL ADDRESS PEER ADDRESS DIRECTION INSTANCE TYPE TIME RPC DETAILS INTERFACE NAME VRF -------------------------------------------------------------------------------------------------------------------------------------------------------------- 1 <none> 192.168.1.1 10.10.10.2:1090 Outbound rest-ep-0 Rest 4 hours CHF <none> n40 NA 1 <none> 192.168.1.2 10.10.10.2:1090 Outbound rest-ep-1 Rest 4 hours CHF <none> n40 NA 1 <none> 192.168.1.3 10.10.10.1:1090 Outbound rest-ep-2 Rest 4 hours CHF <none> n40 NA 1 <none> 192.168.1.3 10.10.10.2:1090 Outbound rest-ep-2 Rest 4 hours CHF <none> n40 NA 1 <none> 192.168.1.4 10.10.10.1:1090 Outbound rest-ep-3 Rest 4 hours CHF <none> n40 NA 1 <none> 192.168.1.2 10.10.10.1:1090 Outbound rest-ep-1 Rest 4 hours CHF <none> n40 NA 1 <none> 192.168.1.4 10.10.10.2:1090 Outbound rest-ep-3 Rest 2 hours CHF <none> n40 NA 1 <none> 192.168.1.1 10.10.10.1:1090 Outbound rest-ep-0 Rest 4 hours CHF <none> n40 NA
// CHF related profiles
profile network-element chf CHF-OFFLINE
nf-client-profile CHF-OFF
failure-handling-profile Fail-H-CHF-OFF
discovery local
exit
// Here is configuration for CHF profile where all peers are dead
profile nf-client nf-type chf
chf-profile CHF-OFF
locality LOC1
priority 1
service name type nchf-convergedcharging
responsetimeout 1000
endpoint-profile epprof
capacity 10
api-root OFFLINE
uri-scheme http
version
uri-version v2
exit
exit
endpoint-name ep1
priority 1
capacity 10
primary ip-address ipv4 10.10.10.1
primary ip-address port 1090
exit
endpoint-name ep2
priority 2
capacity 10
primary ip-address ipv4 10.10.10.2
primary ip-address port 1090
exit
exit
exit
exit
exit
// Failure handling that in case of timeout (HTTP code 504) then try secondary server one time and then proceed with continuing the session
profile nf-client-failure nf-type chf
profile failure-handling Fail-H-CHF-OFF
service name type nchf-convergedcharging
responsetimeout 1000
message type ChfConvergedchargingCreate
status-code httpv2 504
retry 1
action continue
exit
exit
message type ChfConvergedchargingUpdate
status-code httpv2 504
retry 1
action continue
exit
exit
message type ChfConvergedchargingDelete
status-code httpv2 504
retry 1
action continue
exit
exit
exit
Grafana-Schecks
Es wurde eine direkte Korrelation zwischen dem HTTP 504-Timeout und dem Zeitpunkt des Problems beobachtet.
query: sum(increase(smf_restep_http_msg_total{nf_type="chf", namespace=~"$namespace"}[15m])) by (api_name, response_cause, response_status)
Nexus-Prüfungen
Überprüfen Sie, ob irgendwelche Klappen aufgetreten sind.
Nexus# show logging last 500 | include BFD
Lösung
Die Lösung dieses Problems ist in diesem Fall unterschiedlich, da SMF der Client und CHF der Server ist.
Der Verbindungsverlust wurde nicht durch SMF verursacht.
Revisionsverlauf
| Überarbeitung | Veröffentlichungsdatum | Kommentare |
|---|---|---|
1.0 |
03-Oct-2023 |
Erstveröffentlichung |
FeedbackCisco kontaktieren
- Eine Supportanfrage öffnen
- (Erfordert einen Cisco Servicevertrag)