Risoluzione dei problemi relativi al diametro Codice di errore: "IP-CAN_SESSION_NOT_AVAILABLE (5065)" in CPS
Sommario
Introduzione
Questo documento descrive vari metodi di indagine per gestire il Diameter Error Code: "IP-CAN_SESSION_NOT_AVAILABLE (5065)" in Cisco Policy Suite (CPS).
Prerequisiti
Requisiti
Cisco raccomanda la conoscenza dei seguenti argomenti:
- Linux
- CPS
- Funzione PCRF (Policy Control Charge Rule Function)
- Diametro
Nota: Cisco consiglia di disporre dell'accesso privilegiato alla directory principale di CPS CLI.
Componenti usati
Le informazioni fornite in questo documento si basano su CPS 21.1.
Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi.
Premesse
Codice errore diametro: "IP-CAN_SESSION_NOT_AVAILABLE (5065)" è un Diameter Experimental-Result-Code comunemente visualizzato in PCRF che gestisce Voice over Long-Term Evolution (VoLTE) servizi.
Questo errore non viene generato per un sistema VoLTE integro. In questo documento vengono illustrati alcuni scenari in cui l'errore viene segnalato e i diversi approcci per la relativa risoluzione.
In generale, se il PCRF non riesce a eseguire un'associazione di sessioni tra le sessioni Rx e Gx, risponde al Application Function (AF) con una risposta AA, che include una coppia di valori dell'attributo del codice risultato sperimentale (AVP) impostata sul valore " IP-CAN_SESSION_NOT_AVAILABLE (5065) ".
Problema
Scenario 1
Differenza nel valore AVP con prefisso Framed-IP in GX_ (CCR-I) e Rx_AAR
La regola di base per il binding tra Rx e sessione Gx è basata sullo stesso Framed-IPv6-Prefix ricevuto da Gx_Credit Control Request Initial (CCR-I) 543 mentre la creazione della sessione Gx e quella ricevuta da Rx_Authorization Authentication Request (AAR) per la creazione di sessioni Rx.
In questo scenario, si osserva che tutti i campioni di errore IP-CAN_SESSION_NOT_AVAILABLE (5065) sono segnalati da uno specifico elenco di Framed-IPv6-Prefix. Questi Framed-IPv6-Prefixes non sono segnalati in Gx_CCR-I .
Questa CLI fornisce l'elenco univoco e il conteggio totale di Framed-IPv6-Prefixper i quali IP-CAN_SESSION_NOT_AVAILABLE (5065) viene ripristinato da CPS su AF.
[root@LAB-PCRF02CO-pcrfclient01 broadhop]# zgrep -B80 "IP-CAN_SESSION_NOT_AVAILABLE" consolidated-engine.*.gz | grep "Framed-IPv6-Prefix:" | cut -f3,4,5 -d: | sort| uniq -c
6 2402:XXXX:YYYY
3 2402:PPPP:QQQQ
1 2402:JJJJ:KKKK
Questa CLI fornisce l'elenco univoco e il numero di Framed-IPv6-Prefix segnalato in Gx_CCR-I da Packet Data Network Gateway (PGW) .
[root@LAB-PCRF02CO-pcrfclient01 broadhop]# zgrep -A 50 CCR-I consolidated-engine.*.gz | grep Framed-IPv6-Prefix: | cut -f 3,4,5 -d: | sort | uniq -c
115 2402:AAAA:BBBB
116 2402:NNNN:MMMM
246 2402:SSSS:RRRR
Nota: per eseguire CLI, è necessario accedere a pcrfclient01 di CPS e passare a /var/log/broadhop/ directory.
L'aspettativa di un sistema sano è che Framed-IPv6-Prefixricevuto da Gx_CCR-I e Rx_AAR deve provenire dallo stesso pool di prefissi IP allocato per Gm IP (da PGW a AF).
In questo scenario, è chiaro che, per tutti i campioni di errore raccolti, Framed-IP-Prefix segnalato in Rx_AAR è completamente diverso dal Framed-IP-Prefix ricevuto in Gx_CCR-I.
Scenario 2
Contraddizione in Gx Timer di sessione non aggiornato e Timer di scadenza sessione impostato in CPS
1. Che cos'è il timer di sessione Gx Stale?
Questo timer viene attivato ogni volta che si riceve o si invia un messaggio per una determinata sessione Gx. Alla scadenza del timer, Gx_Re-Auth-Request (RAR) viene inviato con Re-Auth-Request-Type AVP impostare su AUTHORIZE_ONLY (0) per quella sessione Gx verso PGW. Se viene ricevuta una Gx_Re-Auth-Answer (RAA) con il valore AVP del codice risultato impostato su DIAMETER_UNKNOWN_SESSION_ID (5002) o DIAMETER_UNABLE_TO_COMPLY (5012) la sessione Gx viene considerata non aggiornata e rimossa dal database interno di PCRF. Su qualsiasi attività tramite l'interfaccia Gx (Gx_RAR/Gx_CCR) , il timer viene reimpostato.
2. Che cos'è un timer di scadenza sessione?
Se non viene ricevuto alcun messaggio entro il timer impostato, la sessione viene rimossa da PCRF.
Nello scenario problematico, i timer sono impostati in questo modo.
Timer sessione Gx non aggiornato: 180 minuti
Durata sessione: 240 min.
In base alla configurazione del timer, dopo 180 minuti viene generato e inviato a PGW un record RAR keep-alive e se la sessione è inattiva per 240 minuti, viene rimossa dal database PCRF.
Se il comando Keep alive RAR non viene eseguito per più motivi [Gx interface flap, PGW out of service o qualsiasi corner case], la sessione raggiunge la scadenza e, contemporaneamente, se è presente un Rx_AAR ricevuto da AF, è possibile visualizzare questo errore e inviare un Gx_RAR a PGW con Session-Release-Cause: UNSPECIFIED_REASON (0).
INFO : (core) Deletion started at Wed Oct 19 07:07:03 IST 2022
WARN : (core) Resending original message since the existing session is in deletion and this session triggered a start
Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-19 01:37:03,676
Application Id: Gx (16777238)
Command Code: Gx_RAR (258)
Dest host: 0006-diamproxy.lab.cisco.com
Dest realm: vpcrf.cisco.com
Device protocol: GX_TGPP
End to end id: 0 (0x00000000)
Hop by hop id: 0 (0x00000000)
Origin state: 0
Stack name: null
Origin realm: x.x.x.x
Session-Id: 0006-diamproxy.lab.cisco.com;1200190897;28719897;634ebb76-11902
Auth-Application-Id: 16777238
Re-Auth-Request-Type: AUTHORIZE_ONLY (0)
Session-Release-Cause: UNSPECIFIED_REASON (0)
Inoltre, la sessione Gx è contrassegnata per l'eliminazione temporanea in PCRF. Poiché PCRF non è stato in grado di associare la sessione Gx, a Rx_AAA viene risposto con AVP Experimental-Result-Code impostato sul valore IP-CAN_SESSION_NOT_AVAILABLE (5065).
Questo è il flusso di chiamate completo che spiega lo scenario:
=========================================================================
LAB-PCRF02-qns05 [2022-10-19 07:07:03,676] ===============================================
POLICY RESULT SUCCESS:
session action = Delete
domainId = IMS
locationId = ims
SERVICES: IMS_DEFAULT
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-19 01:37:03,673
Application Id: Rx (16777236)
Command Code: Rx_AAR (265)
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1274920388 (0x4bfdbdc4)
Hop by hop id: 3440610237 (0xcd138bbd)
Origin state: 0
Stack name: null
Origin host: x.x.x.x
Origin realm: x.x.x.x
Session-Id: x.x.x.x;168440;1;5.3576663599.2;pcsf.ims322-002
Auth-Application-Id: 16777236
Media-Component-Description:
Media-Component-Number: 1
Media-Sub-Component:
Flow-Number: 1
Flow-Description: permit in 17 from xxxx:xxxx:xxxx:xxxx:xxxx:xxxx to xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Flow-Description: permit out 17 from xxxx:xxxx:xxxx:xxxx:xxxx:xxxx to xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Media-Sub-Component:
Flow-Number: 2
Flow-Description: permit in 17 from xxxx:xxxx:xxxx:xxxx:xxxx:xxxx to xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Flow-Description: permit out 17 from xxxx:xxxx:xxxx:xxxx:xxxx:xxxx to xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
Flow-Usage: RTCP (1)
Codec-Data: downlink\r\noffer\r\nm=audio 23096 RTP/AVP 108 102 8 18 100 101 116\r\na=rtpmap:108 AMR/8000\r\na=fmtp:108 mode-set=0,2,4,7; mode-change-period=2; Codec-Data: uplink\r\nanswer\r\nm=audio 41660 RTP/AVP 108 116\r\na=rtpmap:108 AMR/8000/1\r\na=ptime:20\r\na=maxptime:240\r\na=rtpmap:116 telephone-event/
Media-Type: AUDIO (0)
Max-Requested-Bandwidth-UL: 37000
Max-Requested-Bandwidth-DL: 37000
Flow-Status: ENABLED (2)
RS-Bandwidth: 462
RR-Bandwidth: 1387
Subscription-Id:
Subscription-Id-Type: END_USER_SIP_URI (2)
Subscription-Id-Data: sip:+91XXXXXXXXXX
AF-Charging-Identifier: ABCA4C23EA4C0320221019772
Specific-Action: INDICATION_OF_LOSS_OF_BEARER (2)
Specific-Action: INDICATION_OF_RECOVERY_OF_BEARER (3)
Specific-Action: INDICATION_OF_RELEASE_OF_BEARER (4)
Specific-Action: IP_CAN_CHANGE (6)
Framed-IPv6-Prefix: XXXX:XXXX:XXXX:XXXX (0xxxxxxxxxxxxxxxxxxxxx)
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 65587
Service-Info-Status: FINAL SERVICE INFORMATION (0)
Req-Received-Time: 1666143423673
QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
DEBUG MSGS:
INFO : (core) Tagging message with ID: RX_TGPP
INFO : (core) Successful load by secondary key: FramedIpv6PrefixKey:framedIpv6Prefix:XXXX%XXXX%XXXX%XXXX
INFO : (core) Start session triggered
INFO : (core) Deletion started at Wed Oct 19 07:07:03 IST 2022
WARN : (core) Resending original message since the existing session is in deletion and this session triggered a start
INFO : (core) domain: IMS
INFO : (gx) Sending RAR Message on session 0006-diamproxy.lab.cisco.com;1200190897;28719897;634ebb76-11902
INFO : (core) Adding network-id keys for missing credentials
INFO : (custrefdata) QueryTable: TAI_BASED_POLICY Field: {ECGI=XXXXX, packname=-1, AN GW IPV4=*, RAT_TYPE=1004, IMSI_Prefix=XXXXX, TAI=4042052329, APN=XXX}
INFO : (custrefdata) QueryTable: LAC_BASED_POLICY Field: {MCC_MNC=XXXX, packname=-1, rat=1004, CGI=*, SGSN_IP=*, CI=*, IMSI_Prefix=XXXXXX, LAC=XXXX, APN=XX}
INFO : (core) domain: IMS
INFO : (core) Session removed
SERVICE CALC MSGS:
USE CASES:
INFO : (use-cases) Use case ‘Lab IMS Default', status: true, Condition: No Condition Set
SENT MESSAGES (asynchronous):
Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-19 01:37:03,676
Application Id: Gx (16777238)
Command Code: Gx_RAR (258)
Dest host: 0006-diamproxy.lab-spgw01.cisco.com
Dest realm: vpcrf.cisco.com
Device protocol: GX_TGPP
End to end id: 0 (0x00000000)
Hop by hop id: 0 (0x00000000)
Origin state: 0
Stack name: null
Origin realm: x.x.x.x
Session-Id: 0006-diamproxy.lab-spgw01.cisco.com;1200190897;28719897;634ebb76-11902
Auth-Application-Id: 16777238
Re-Auth-Request-Type: AUTHORIZE_ONLY (0)
Session-Release-Cause: UNSPECIFIED_REASON (0)
=========================================================================
Allo stesso tempo, per lo stesso pacchetto, session action: create viene elaborato da CPS ma non è stato possibile associare la sessione Gx, pertanto un errore 5065 viene ripristinato su AF.
LAB-VPCRF02-qns05 [2022-10-19 07:07:03,696] ===============================================
POLICY RESULT SUCCESS:
session action = Create
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-19 01:37:03,673
Application Id: Rx (16777236)
Command Code: Rx_AAR (265)
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1274920388 (0x4bfdbdc4)
Hop by hop id: 3440610237 (0xcd138bbd)
Origin state: 0
Stack name: null
Origin host: x.x.x.x
Origin realm: x.x.x.x
Session-Id: x.x.x.x;168440;1;5.3576663599.2;pcsf.ims322-002
Auth-Application-Id: 16777236
Media-Component-Description:
Media-Component-Number: 1
Media-Sub-Component:
Flow-Number: 1
Flow-Description: permit in 17 from xxxxxx 8975:b101 41660 toxxxxxx::2 23096
Flow-Description: permit out 17 fromxxxxxx::2 23096 toxxxxxx:b101 41660
Media-Sub-Component:
Flow-Number: 2
Flow-Description: permit in 17 from xxxxxx 8975:b101 41660 toxxxxxx::2 23096
Flow-Description: permit out 17 fromxxxxxx::2 23096 toxxxxxx:b101 41660
Flow-Usage: RTCP (1)
Codec-Data: downlink\r\noffer\r\nm=audio 23096 RTP/AVP 108 102 8 18 100 101 116\r\na=rtpmap:108 AMR/8000\r\na=fmtp:108 mode-set=0,2,4,7; mode-change-period=2; Codec-Data: uplink\r\nanswer\r\nm=audio 41660 RTP/AVP 108 116\r\na=rtpmap:108 AMR/8000/1\r\na=ptime:20\r\na=maxptime:240\r\na=rtpmap:116 telephone-event/ Media-Type: AUDIO (0)
Max-Requested-Bandwidth-UL: 37000
Max-Requested-Bandwidth-DL: 37000
Flow-Status: ENABLED (2)
RS-Bandwidth: 462
RR-Bandwidth: 1387
Subscription-Id:
Subscription-Id-Type: END_USER_SIP_URI (2)
Subscription-Id-Data: sip:+xxxxxxxx
AF-Charging-Identifier: ABCA4C23EA4C0320221019772
Specific-Action: INDICATION_OF_LOSS_OF_BEARER (2)
Specific-Action: INDICATION_OF_RECOVERY_OF_BEARER (3)
Specific-Action: INDICATION_OF_RELEASE_OF_BEARER (4)
Specific-Action: IP_CAN_CHANGE (6)
Framed-IPv6-Prefix: xxxx:xxxx:xxxx:xxxx
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 65587
Service-Info-Status: FINAL SERVICE INFORMATION (0)
Req-Received-Time: 1666143423673
QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
DEBUG MSGS:
INFO : (core) Tagging message with ID: RX_TGPP
INFO : (rx) Could not perform Gx session binding for Framed-IP-Address null, Framed-IPv6-Prefix xxxx:xxxx:xxxx:xxxx
INFO : (core) Start session triggered
INFO : (rx) Could not perform Gx session binding for Framed-IP-Address null, Framed-IPv6-Prefix xxxx:xxxx:xxxx:xxxx
INFO : (rx) Sending 265 Message on session x.x.x.x;168440;1;5.3576663599.2;pcsf.ims322-002
ERROR : (rules) Could not perform Gx session binding: Could not perform Gx session binding 5065
SERVICE CALC MSGS:
USE CASES:
SENT MESSAGES (asynchronous):
Message: com.broadhop.diameter2.messages.DiameterResponseMessage
Timestamp: 2022-10-19 01:37:03,696
Application Id: Rx (16777236)
Command Code: Rx_AAA (265)
Dest host: x.x.x.x
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1274920388 (0x4bfdbdc4)
Hop by hop id: 3440610237 (0xcd138bbd)
Origin state: 0
Stack name: null
Origin realm: x.x.x.x
Session-Id: x.x.x.x;168440;1;5.3576663599.2;pcsf.ims322-002
Auth-Application-Id: 16777236
QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
Experimental-Result:
Vendor-Id: 10415
Experimental-Result-Code: IP-CAN_SESSION_NOT_AVAILABLE (5065)
=========================================================================
Scenario 3
Sessione del sottoscrittore disponibile in PCRF, ma non in PGW causata da Flap dell'interfaccia Gx
In uno scenario ad angolo, le sessioni del sottoscrittore vengono rimosse in PGW, ma sono presenti in PCRF. Questo accade quando è presente un link flap Gx causato da un'interruzione del layer di trasporto.
Diagramma del flusso delle chiamate non riuscite:
Scenario di errore: IP_CAN_SESSION_NOT_AVAILABLE(5065)
Flusso di chiamata di esempio per questo errore dal log del motore:
lab-qns07 [2022-08-24 00:42:48,643] ===============================================
POLICY RESULT SUCCESS:
session action = None
domainId = IMS
locationId = ims
SERVICES: IMS_DEFAULT
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-08-23 19:12:48,638
Application Id: Rx (16777236)
Command Code: Rx_AAR (265)
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1797266185 (0x6b201b09)
Hop by hop id: 1690686712 (0x64c5d4f8)
Origin state: 0
Stack name: null
Origin host: x.x.x.x
Origin realm: x.x.x.x
Session-Id: x.x.x.x;367169;1;5.1236049266.2;pcsf-stdn.ims332-012
Auth-Application-Id: 16777236
Media-Component-Description:
Media-Component-Number: 1
Media-Sub-Component:
Flow-Number: 1
Flow-Description: permit in 17 from xxxxxx 50060 to xxxxxx::4 28532
Flow-Description: permit out 17 from xxxxxx::4 28532 to xxxxxxx 50060
Media-Sub-Component:
Flow-Number: 2
Flow-Description: permit in 17 from xxxxxx 50060 to xxxxxx::4 28532
Flow-Description: permit out 17 from xxxxxx::4 28532 to xxxxxxx 50060
Flow-Usage: RTCP (1)
Codec-Data: uplink\r\noffer\r\nm=audio 50060 RTP/AVP 104 102 105 96\r\na=rtpmap:104 AMR-WB/16000/1\r\na=fmtp:104 mode-set=0,3;mode-change-capability=2;max-
Codec-Data: downlink\r\nanswer\r\nm=audio 28532 RTP/AVP 102 96\r\na=rtpmap:102 AMR/8000/1\r\na=fmtp:102 mode-set=0,2,4,7; mode-change-period=2; mode-change-capability=2;
Media-Type: AUDIO (0)
Max-Requested-Bandwidth-UL: 72000
Max-Requested-Bandwidth-DL: 72000
Flow-Status: ENABLED (2)
RS-Bandwidth: 362
RR-Bandwidth: 1087
Subscription-Id:
Subscription-Id-Type: END_USER_SIP_URI (2)
Subscription-Id-Data: sip:+919XXXXXX
AF-Charging-Identifier: "PCSF:1-MU1-cfed-12-00000000630526b2-0000000017442828"
Specific-Action: INDICATION_OF_LOSS_OF_BEARER (2)
Specific-Action: INDICATION_OF_RECOVERY_OF_BEARER (3)
Specific-Action: INDICATION_OF_RELEASE_OF_BEARER (4)
Specific-Action: IP_CAN_CHANGE (6)
Framed-IPv6-Prefix: xxxx:xxxx:xxxx:xxxx
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 65587
Service-Info-Status: FINAL SERVICE INFORMATION (0)
Req-Received-Time: 1661281963763
QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
DEBUG MSGS:
INFO : (core) Tagging message with ID: RX_TGPP
INFO : (core) Successful load by secondary key: FramedIpv6PrefixKey:framedIpv6Prefix:xxxx%3Axxxx%3Axxxx%3Axxxx
INFO : (core) Start session triggered
INFO : (rx) Success binding to Gx session 0001-diamproxy.ndc3-ims-lab-sbc1;1106437295;560189406;63051856-de02 by IP Address
INFO : (TGPP) [Rel8, Rel9, Rel10, NetLoc, NetLocUntrustedWLAN] features supported for Vendor-Id 10415, Feature-List-ID 1
INFO : (rx) Creating new diameter session x.x.x.x;367169;1;5.1236049266.2;pcsf-stdn.ims332-012
INFO : (policy) Load CRD for Unknown Subscriber
INFO : (location) Location found for avp matching: logical_apn\ims
WARN : (core) Session has switched from known to unknown as subscriber could not be found
INFO : (core) Adding unknown service code: IMS_DEFAULT for session
INFO : (core) domain: IMS
INFO : (core) Adding network-id keys for missing credentials
INFO : (core) domain: IMS
INFO : (rx) Sending AAA Message on session x.x.x.x;367169;1;5.1236049266.2;pcsf-stdn.ims332-012
INFO : (gx) Installing preconfigured rule: _6_1_2_AF_AUDIO
INFO : (gx) Installing preconfigured rule: _6_1_1_AF_AUDIO
INFO : (et) Event trigger 2 added
INFO : (et) Event trigger 5 added
INFO : (et) Event trigger 6 added
INFO : (et) Event trigger 7 added
INFO : (gx) Sending RAR Message on session 0001-diamproxy.ndc3-ims-lab-sbc1;1106437295;560189406;63051856-de02
SERVICE CALC MSGS:
USE CASES
INFO : (use-cases) Use case 'WLAN', status: false, Condition: ("Rat-Type WLAN"=false)
INFO : (use-cases) Use case 'IMS Default', status: true, Condition: No Condition Set
SENT MESSAGES (asynchronous):
Message: com.broadhop.diameter2.messages.DiameterResponseMessage
Timestamp: 2022-08-23 19:12:48,643
Application Id: Rx (16777236)
Command Code: Rx_AAA (265)
Dest host: x.x.x.x
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1797266185 (0x6b201b09)
Hop by hop id: 1690686712 (0x64c5d4f8)
Origin state: 0
Stack name: null
Origin realm: x.x.x.x
Session-Id: x.x.x.x;367169;1;5.1236049266.2;pcsf-stdn.ims332-012
Auth-Application-Id: 16777236
IP-CAN-Type: 3GPP_EPS (5)
RAT-Type: EUTRAN (1004)
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 65587QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
Result-Code: DIAMETER_SUCCESS (2001)
Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-08-23 19:12:48,643
Application Id: Gx (16777238)
Command Code: Gx_RAR (258)
Dest host: 0001-diamproxy.ndc3-ims-lab-sbc1
Dest realm: vpcrf.cisco.com
Device protocol: GX_TGPP
End to end id: 0 (0x00000000)
Hop by hop id: 0 (0x00000000)
Origin state: 0
Stack name: null
Origin realm: x.x.x.x
Session-Id: 0001-diamproxy.ndc3-ims-airpcrf02-sbc1;1106437295;560189406;63051856-de02
Auth-Application-Id: 16777238
Re-Auth-Request-Type: AUTHORIZE_ONLY (0)
Charging-Rule-Install:
Charging-Rule-Definition:
Charging-Rule-Name: _6_1_2_AF_AUDIO
Rating-Group: 2
Flow-Information:
Flow-Description: permit in 17 from xxxxxx 50061 to xxxxxxx28533
Flow-Direction: UPLINK (2)
Flow-Information:
Flow-Description: permit out 17 from xxxxx 28533 to xxxxxx 50061
Flow-Direction: DOWNLINK (1)
Flow-Status: ENABLED (2)
QoS-Information:
QoS-Class-Identifier: Conversational (1)
Max-Requested-Bandwidth-UL: 1449
Max-Requested-Bandwidth-DL: 1449
Guaranteed-Bitrate-UL: 1449
Guaranteed-Bitrate-DL: 1449
Reporting-Level: RATING_GROUP_LEVEL (1)
Precedence: 0
AF-Charging-Identifier: "PCSF:1-MU1-cfed-12-00000000630526b2-0000000017442828"
Flows:
Media-Component-Number: 1
Flow-Number: 2
Charging-Rule-Install:
Charging-Rule-Definition:
Charging-Rule-Name: _6_1_1_AF_AUDIO
Rating-Group: 2
Flow-Information:
Flow-Description: permit in 17 from xxxxxx 50060 to xxxxxx 28532
Flow-Direction: UPLINK (2)
Flow-Information:
Flow-Description: permit out 17 from xxxxxxx 28532 to 2xxxxx 50060
Flow-Direction: DOWNLINK (1)
Flow-Status: ENABLED (2)
QoS-Information:
QoS-Class-Identifier: Conversational (1)
Max-Requested-Bandwidth-UL: 72000
Max-Requested-Bandwidth-DL: 72000
Guaranteed-Bitrate-UL: 72000
Guaranteed-Bitrate-DL: 72000
Reporting-Level: RATING_GROUP_LEVEL (1)
Precedence: 0
AF-Charging-Identifier: "PCSF:1-MU1-cfed-12-00000000630526b2-0000000017442828"
Flows:
Media-Component-Number: 1
Flow-Number: 1
Event-Trigger: RAT_CHANGE (2)
Event-Trigger: LOSS_OF_BEARER (5)
Event-Trigger: RECOVERY_OF_BEARER (6)
Event-Trigger: IP-CAN_CHANGE (7)
=======================================================================
lab-qns04 [2022-08-24 00:42:49,849] ===============================================
POLICY RESULT SUCCESS:
session action = None
domainId = IMS
locationId = ims
SERVICES: IMS_DEFAULT
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterResponseMessage
Timestamp: 2022-08-23 19:12:49,844
Application Id: Gx (16777238)
Command Code: Gx_RAA (258)
Device protocol: GX_TGPP
End to end id: 2244560894 (0x85c947fe)
Hop by hop id: 2040440255 (0x799ea5bf)
Origin state: 1657916833
Stack name: null
Origin host: 001-diamproxy.ndc3-ims-lab-sbc1
Origin realm: vpcrf.cisco.com
Session-Id: 0001-diamproxy.ndc3-ims-lab-sbc1;1106437295;560189406;63051856-de02
Origin-State-Id: 1657916833
Error-Message: Unknown Session ID
Req-Received-Time: 0
Result-Code: DIAMETER_UNKNOWN_SESSION_ID (5002)
DEBUG MSGS:
INFO : (core) Tagging message with ID: GX_TGPP
INFO : (core) Successful load by primary key: diameterSessionKey:0001-diamproxy.ndc3-ims-airpcrf02-sbc1%3B1106437295%3B560189406%3B63051856-de02
INFO : (core) Stop session triggered
INFO : (core) Deletion started at Wed Aug 24 00:42:49 IST 2022
INFO : (core) Soft deletion triggered for session
INFO : (policy) Load CRD for Unknown Subscriber
INFO : (location) Location found for avp matching: logical_apn\ims
WARN : (core) Session has switched from known to unknown as subscriber could not be found
INFO : (core) Adding unknown service code: IMS_DEFAULT for session
INFO : (core) domain: IMS
INFO : (core) Adding network-id keys for missing credentials
INFO : (core) domain: IMS
SERVICE CALC MSGS:
USE CASES:
INFO : (use-cases) Use case 'WLAN', status: false, Condition: ("Rat-Type WLAN"=false)
INFO : (use-cases) Use case 'Vodafone IMS Default', status: true, Condition: No Condition Set
=========================================================================
lab-qns04 [2022-08-24 00:43:02,349] ===============================================
POLICY RESULT SUCCESS:
session action = Create
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-08-23 19:13:02,330
Application Id: Rx (16777236)
Command Code: Rx_AAR (265)
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1811425453 (0x6bf828ad)
Hop by hop id: 1690687469 (0x64c5d7ed)
Origin state: 0
Stack name: null
Origin host: x.x.x.x
Origin realm: x.x.x.x
Session-Id: x.x.x.x;367195;1;5.1236262316.2;pcsf-stdn.ims332-012
Auth-Application-Id: 16777236
Media-Component-Description:
Media-Component-Number: 1
Media-Sub-Component:
Flow-Number: 1
Flow-Description: permit in 17 from xxxx:xxxx:xxxx:xxxx: 50032 to xxxx:xxxx:xxxx:xxxx::6 5144
Flow-Description: permit out 17 from xxxx:xxxx:xxxx:xxxx::6 xxxx to xxxx:xxxx:xxxx:xxxx: 50032
Media-Sub-Component:
Flow-Number: 2
Flow-Description: permit in 17 from 2402:3a80:2027:2db8:ac0e:ff4:dc53:af02 50033 to 2402:3a80:2000:606::6 5145
Flow-Description: permit out 17 from 2402:3a80:2000:606::6 5145 to 2402:3a80:2027:2db8:ac0e:ff4:dc53:af02 50033
Flow-Usage: RTCP (1)
Codec-Data: downlink\r\noffer\r\nm=audio 5144 RTP/AVP 96 8 18 100 101 97\r\na=rtpmap:96 AMR/8000\r\na=fmtp:96 mode-set=0,2,4,7; mode-change-period=2; mode-change-Codec-Data: uplink\r\nanswer\r\nm=audio 50032 RTP/AVP 96 97\r\na=rtpmap:96 AMR/8000/1\r\na=fmtp:96 mode-set=0,2,4,7;mode-change-capability=2;max-red=0\r\na=rtpmap:97 Media-Type: AUDIO (0)
Max-Requested-Bandwidth-UL: 37000
Max-Requested-Bandwidth-DL: 37000
Flow-Status: ENABLED (2)
RS-Bandwidth: 0
RR-Bandwidth: 0
Subscription-Id:
Subscription-Id-Type: END_USER_SIP_URI (2)
Subscription-Id-Data: sip:+xxxxxxx
AF-Charging-Identifier: GYlkAABklmEFGKS7UELMBecR
Specific-Action: INDICATION_OF_LOSS_OF_BEARER (2)
Specific-Action: INDICATION_OF_RECOVERY_OF_BEARER (3)
Specific-Action: INDICATION_OF_RELEASE_OF_BEARER (4)
Specific-Action: IP_CAN_CHANGE (6)
Framed-IPv6-Prefix: xxxxxxxxx
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 65587
Service-Info-Status: FINAL SERVICE INFORMATION (0)
Req-Received-Time: 1661281976257
QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
DEBUG MSGS:
INFO : (core) Tagging message with ID: RX_TGPP
INFO : (rx) Could not perform Gx session binding for Framed-IP-Address null, Framed-IPv6-Prefix xxxxxx
INFO : (core) Start session triggered
INFO : (rx) Could not perform Gx session binding for Framed-IP-Address null, Framed-IPv6-Prefix xxxxxx
INFO : (rx) Sending 265 Message on session x.x.x.x;367195;1;5.1236262316.2;pcsf-stdn.ims332-012
ERROR : (rules) Could not perform Gx session binding: Could not perform Gx session binding 5065
SERVICE CALC MSGS:
USE CASES:
SENT MESSAGES (asynchronous):
Message: com.broadhop.diameter2.messages.DiameterResponseMessage
Timestamp: 2022-08-23 19:13:02,349
Application Id: Rx (16777236)
Command Code: Rx_AAA (265)
Dest host: x.x.x.x
Dest realm: x.x.x.x
Device protocol: RX_TGPP
End to end id: 1811425453 (0x6bf828ad)
Hop by hop id: 1690687469 (0x64c5d7ed)
Origin state: 0
Stack name: null
Origin realm: x.x.x.x
Session-Id: x.x.x.x;367195;1;5.1236262316.2;pcsf-stdn.ims332-012
Auth-Application-Id: 16777236
QPS-Internal-Route-Record-Host: x.x.x.x
QPS-Internal-Route-Record-Realm: x.x.x.x
Experimental-Result:
Vendor-Id: 10415
Experimental-Result-Code: IP-CAN_SESSION_NOT_AVAILABLE (5065)
===============================================
Quando si controlla attentamente l'andamento dell'indicatore KPI Error per RX_AAR [IP-CAN_SESSION_NOT_AVAILABLE (5065)] e Gx_RAR [DIAMETER_UNKNOWN_SESSION_ID (5002)], è possibile vedere l'incremento lineare di questi errori dopo un flap dell'interfaccia Gx.
Tendenza errori Gx_RAR e Rx_AAR
Soluzione
Approccio per lo scenario 1
La soluzione a questo problema deve essere eseguita all'esterno di CPS. È necessario eseguire una riconciliazione del pool IP utilizzato nell'interfaccia Gm (l'interfaccia tra SPGW e AF) e verificare che Framed-IP-Prefixes sono utilizzati sia in PGW che in AF per User Equipment (UE).
Approccio per lo scenario 2
Imposta il timer di scadenza della sessione su > (3 * Gx stale-session timer).
Procedura per impostare il timer
Passaggio 1. Accedere a Policy Builder con l'utente di lettura/scrittura.
Passaggio 2. Impostare la Default Gx Stale Session Timer Minutes come valore consigliato.
Configurazione Timer Sessione Non Aggiornata Gx
Passaggio 3. Impostare la Session Expiration Hours and Session Expiration Minutes come consigliato 3 * of Gx Stale session timer.
Configurazione timer scadenza sessione
Passaggio 4. Salvare il repository e pubblicare nella versione più recente.
Approccio per lo scenario 3
Introdurre un Rx_ASR verso AF per cancellare la sessione Rx già creata se CPS riceve Diameter Error Code=5002 nella risposta di Gx_RAR da PGW. In questo modo, se la sessione non è presente in PGW e CPS riceve Diameter Error 5002 , insieme all'eliminazione temporanea della sessione Gx, CPS invia un messaggio Rx_ASR verso il nodo AF con un Abort-Cause: 0.
Procedura per impostare il parametro Rx_ASR
Passaggio 1. Accedere a Gestione cluster come utente root.
Passaggio 2. Backupqns.conf file.
cp /etc/broadhop/qns.conf /etc/broadhop/qns.conf.$(date +%m%d%Y).bkp
Passaggio 3. Modificare il file /etc/broadhop/qns.conf con vi e inserire la riga "-Dsend.Rx.ASR.For.AdditionalErrorCodes=5002"
Passaggio 4. Genera script di marionetta.
/var/qps/install/current/puppet/modules/qps/templates/var/broadhop/build_etc.sh
Passaggio 5. Popolare le modifiche in tutte le VM.
/var/qps/install/current/scripts/upgrade/reinit.sh
Passaggio 6. Riavviare tutto per rendere effettive le modifiche.
restartall.sh
Flusso di chiamata previsto dopo la modifica del parametro richiesto.
Scenario di successo dopo la modifica
Flusso di chiamata previsto dal log del motore CPS dopo la modifica del parametro richiesto.
=========================================================================
[2022-10-10 09:46:28,899] ===============================================
POLICY RESULT SUCCESS:
session action = None
domainId = F1660RxPriorityLevel
locationId = F1660IMS
SERVICES: RxPriorityLevel
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-10 09:46:28,332
Application Id: Rx (16777236)
Command Code: Rx_AAR (265)
Dest host: qns-site-server-1
Dest realm: cisco.com
Device protocol: RX_TGPP
End to end id: 535285358 (0x1fe7ce6e)
Hop by hop id: 655749306 (0x2715f0ba)
Origin state: 0
Stack name: null
Origin host: site-host-rx
Origin realm: site-rx-client
Session-Id: site-host-rx;132419;581;311482316600001IMSSession
Auth-Application-Id: 16777236
Media-Component-Description:
Media-Component-Number: 1
Media-Sub-Component:
Flow-Number: 1
Flow-Description: permit in ip from xxxxxxx 10000 to xxxxxxx:1 20000
Flow-Description: permit out ip from xxxxxxxxx1 20000 to xxxxxxx 10000
Flow-Usage: AF_SIGNALLING (2)
AF-Application-Identifier: lab.test.f1660.afapid01
Media-Type: VIDEO (1)
Max-Requested-Bandwidth-UL: 50000
Max-Requested-Bandwidth-DL: 50000
RS-Bandwidth: 800
RR-Bandwidth: 800
Specific-Action: INDICATION_OF_FAILED_RESOURCES_ALLOCATION (9)
Specific-Action: CHARGING_CORRELATION_EXCHANGE (1)
Specific-Action: INDICATION_OF_LOSS_OF_BEARER (2)
Specific-Action: INDICATION_OF_RECOVERY_OF_BEARER (3)
Specific-Action: INDICATION_OF_RELEASE_OF_BEARER (4)
Specific-Action: IP_CAN_CHANGE (6)
Specific-Action: ACCESS_NETWORK_INFO_REPORT (12)
Subscription-Id:
Subscription-Id-Type: END_USER_SIP_URI (2)
Subscription-Id-Data: sip:xxxxxxx
Framed-IP-Address: x.x.x.x (0x01020304)
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 32
MIP6-Agent-Info:
MIP-Home-Agent-Host:
Destination-Realm: pcef
Destination-Host: vzr
Req-Received-Time: 1665395188271
QPS-Internal-Route-Record-Host: site-host-rx
QPS-Internal-Route-Record-Realm: site-rx-client
DEBUG MSGS:
INFO : (core) Tagging message with ID: RX_TGPP
INFO : (diameter) Adding extracted AVP to policy: DiameterMessageAvp [code=Media-Type, value=1]
INFO : (core) Successful load by secondary key: FramedIpKey:framedIp:x.x.x.x
INFO : (core) Start session triggered
INFO : (rx) Success binding to Gx session site-host-gx;132419;575;9001660001 by IP Address
INFO : (TGPP) [NetLoc] features supported for Vendor-Id 10415, Feature-List-ID 1
INFO : (rx) Creating new diameter session site-host-rx;132419;581;311482316600001IMSSession
INFO : (gx) Installing preconfigured rule: _1_1_1_AF_VIDEO
INFO : (et) Event trigger 2 added
INFO : (et) Event trigger 5 added
INFO : (et) Event trigger 6 added
INFO : (et) Event trigger 7 added
INFO : (et) Event trigger 28 added
INFO : (gx) Sending RAR Message on session site-host-gx;132419;575;9001660001
SERVICE CALC MSGS:
USE CASES:
INFO : (use-cases) Use case 'F1660_Rx_priorityLevel', status: true, Condition: No Condition Set
SENT MESSAGES (asynchronous):
com.broadhop.diameter2.actions.ISendDiameterResponse
DestinationName:
ResponseMessage: Message: com.broadhop.diameter2.messages.DiameterResponseMessage
Timestamp: 2022-10-10 09:46:28,893
Application Id: Rx (16777236)
Command Code: Rx_AAA (265)
Dest host: site-host-rx
Dest realm: site-rx-client
Device protocol: RX_TGPP
End to end id: 535285358 (0x1fe7ce6e)
Hop by hop id: 655749306 (0x2715f0ba)
Origin state: 0
Stack name: null
Origin realm: cisco
Session-Id: site-host-rx;132419;581;311482316600001IMSSession
Auth-Application-Id: 16777236
IP-CAN-Type: 3GPP_EPS (5)
RAT-Type: EUTRAN (1004)
Supported-Features:
Vendor-Id: 10415
Feature-List-ID: 1
Feature-List: 32
QPS-Internal-Route-Record-Host: site-host-rx
QPS-Internal-Route-Record-Realm: site-rx-client
Result-Code: DIAMETER_SUCCESS (2001)
com.broadhop.diameter2.actions.ISendDiameterRequest
RequestMessage: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-10 09:46:28,899
Application Id: Gx (16777238)
Command Code: Gx_RAR (258)
Dest host: site-host-gx
Dest realm: site-gx-client
Device protocol: GX_TGPP
End to end id: 0 (0x00000000)
Hop by hop id: 0 (0x00000000)
Origin state: 0
Stack name: null
Session-Id: site-host-gx;132419;575;9001660001
Auth-Application-Id: 16777238
Re-Auth-Request-Type: 0
Charging-Rule-Install:
Charging-Correlation-Indicator: 0
Charging-Rule-Definition:
Charging-Rule-Name: _1_1_1_AF_VIDEO
Flow-Information:
Flow-Description: permit in ip from xxxx:xxxx:xxxx:xxxx: 10000 toxxxx:xxxx:xxxx:xxxx 20000
Flow-Information:
Flow-Description:permit in ip from xxxx:xxxx:xxxx:xxxx: 10000 toxxxx:xxxx:xxxx:xxxx 20000
QoS-Information:
QoS-Class-Identifier: 3
Max-Requested-Bandwidth-UL: 204800
Max-Requested-Bandwidth-DL: 204800
Allocation-Retention-Priority:
Priority-Level: 1
Pre-emption-Capability: 0
Pre-emption-Vulnerability: 1
Event-Trigger: 2
Event-Trigger: 5
Event-Trigger: 6
Event-Trigger: 7
Event-Trigger: 28
DestinationName: lab-1:diameter-lb
=========================================================================
[2022-10-10 09:46:29,323] ===============================================
POLICY RESULT SUCCESS:
session action = None
domainId = F1660RxPriorityLevel
locationId = F1660IMS
SERVICES: RxPriorityLevel
TRIGGER: Message: com.broadhop.diameter2.messages.DiameterResponseMessage
Timestamp: 2022-10-10 09:46:29,148
Application Id: Gx (16777238)
Command Code: Gx_RAA (258)
Device protocol: GX_TGPP
End to end id: 2577399809 (0x99a00001)
Hop by hop id: 1095304429 (0x414904ed)
Origin state: 0
Stack name: null
Origin host: site-host-gx
Origin realm: site-gx-client
Session-Id: site-host-gx;132419;575;9001660001
Auth-Application-Id: 16777238
Req-Received-Time: 0
Result-Code: DIAMETER_UNKNOWN_SESSION_ID (5002)
DEBUG MSGS:
INFO : (core) Tagging message with ID: GX_TGPP
INFO : (core) Lock obtained on key: diameterSessionKey:site-host-gx%3B132419%3B575%3B9001660001
INFO : (core) Successful load by primary key: diameterSessionKey:site-host-gx%3B132419%3B575%3B9001660001
INFO : (core) Stop session triggered
INFO : (core) Deletion started at Mon Oct 10 09:46:29 UTC 2022
INFO : (core) Soft deletion triggered for session
INFO : (rx) Trigger Rx-ASR for error code 5002
INFO : (rx) Sending ASR Message on session site-host-rx;132419;581;311482316600001IMSSession
SERVICE CALC MSGS:
USE CASES:
INFO : (use-cases) Use case 'F1660_Rx_priorityLevel', status: true, Condition: No Condition Set
SENT MESSAGES (asynchronous):
com.broadhop.diameter2.actions.ISendDiameterRequest
RequestMessage: Message: com.broadhop.diameter2.messages.DiameterRequestMessage
Timestamp: 2022-10-10 09:46:29,323
Application Id: Rx (16777236)
Command Code: Rx_ASR (274)
Dest host: site-host-rx
Dest realm: site-rx-client
Device protocol: RX_TGPP
End to end id: 0 (0x00000000)
Hop by hop id: 0 (0x00000000)
Origin state: 0
Stack name: null
Session-Id: site-host-rx;132419;581;311482316600001IMSSession
Auth-Application-Id: 16777236
Abort-Cause: 0
DestinationName: lab-1:diameter-lb
=========================================================================
Cronologia delle revisioni
| Revisione | Data di pubblicazione | Commenti |
|---|---|---|
2.0 |
24-Aug-2023 |
Release iniziale |
1.0 |
24-Nov-2022 |
Versione iniziale |
Feedback