Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About Gilles Dufour
07-18-2018
Gilles Dufour
Cisco Employee
Joined Cisco Systems Belgium in 1997 after completing my 5 years engineering school at University of Liege (Belgium).
After 6 months of intensive training, I joined the TAC.
One year later, I got my first CCIE in routing/switching.
In 2000 I moved to Denver Colorado as consulting engineer to assist Cisco's customers deploying MPLS/VPN.
In the meantime, I got the Security CCIE.
Two years after that I came back to belgium to work on loadbalancers (CSM and CSS).
I'm now technical leader inside the Application Datacenter BU working primarily on the ACE module and appliance.
Joined Cisco Systems Belgium in 1997 after completing my 5 years engineering school at University of Liege (Belgium).
After 6 months of intensive training, I joined the TAC.
One year later, I got my first CCIE in routing/switching.
In 2000 I moved to Denver Colorado as consulting engineer to assist Cisco's customers deploying MPLS/VPN.
In the meantime, I got
Recent Badges
Stats
Member since
02-21-2002
5920
Posts
3754
Helpful
664
Solutions
Created by
Gilles Dufour
in Wireless - Mobility Documents
in Wireless - Mobility Documents
11-21-2016
06:20 AM
11-21-2016
06:20 AM
Topology
picture from http://lteworld.org/blog/lcs-architecture-lte-eps
ASR5x00 MME Configuration
context SGSN_MME
mme-service mme
mme-id group-id 32768 mme-code 105
plmn-id mcc MMM mnc NN
associate egtp-service mme-egtp-s10s11 context SGSN_MME
associate hss-peer-service HSS context HSS
associate sgtpc-service sgtp-mme context SGSN_MME
associate sgs-service SGs context SGs
associate location-service SLG_SLS
...
context HSS
interface sls-27/1-vlan704
ip address 10.6.1.60 255.255.255.248
#exit
interface sls-lb1 loopback
ip address 10.6.0.1 255.255.255.255
#exit
interface sls-lb2 loopback
ip address 10.6.0.2 255.255.255.255
location-service SLG_SLS
associate diameter endpoint SLg
associate sls-service egmlc
exit
sls-service egmlc
esmlc esmlc-id 1 ipv4-address 10.200.6.30 ipv4-address 10.200.6.11 port 2905 weight 1
bind ipv4-address 10.16.0.1 ipv4-address 10.6.0.2 port 9082 sctp-template SLs
#exit
diameter endpoint SLg
origin realm cisco.com
use-proxy
origin host MMEXXX.MMEXXX.MME.EPC.MNC0NN.MCCMMM.3GPPNETWORK.ORG address 10.6.0.4 port 3868 address 10.6.0.5
destination-host-avp always
peer diameter.ciscowireless.com realm ciscowireless.com address 10.200.6.9 port 2906 sctp
route-entry peer diameter.ciscowireless.com
route-entry realm ciscowireless.com peer diameter.ciscowireless.com
associate sctp-parameters-template SLg
Troubleshooting
Flow Chart
picture from http://lteworld.org/blog/lcs-architecture-lte-eps
Monitor Subscriber
To understand messages exchanged for LCS, use monitor subscriber with following options (Diameter, S1AP, SLs)
First we receive the SLg Location Request in a diameter message.
+ in 09:20:53:572 Diameter 0x80000c (8388620) Provide-Location-Request Diameter message from 10.200.6.9:2906 to 10.6.0.4:3868 Base Header Information: Version: 0x01 (1) Message Length: 0x0001c0 (448) Command Flags: 0xc0 (192) REQ PXY Command Code: 0x80000c (8388620) Provide-Location-Request
MME triggers S1 Paging
+ out 09:20:53:573 S1AP PAGING (10) ... + out 09:20:53:573 S1AP PAGING (10)
UE responds and MME sends Sls request.
+ in 09:20:53:921 S1AP INITIAL UE MESSAGE (12) + out 09:20:53:921 SLS Procedure Code: LOCATION SERVICE REQUEST (0) SLS Tx PDU, from 10.6.0.1:9082 to 10.200.6.30:2905 (71) SLs-AP (71 bytes) Choice Index : Initiating Message (1) Procedure Code: LOCATION SERVICE REQUEST (0) Criticality : reject (0) LOCATION SERVICE REQUEST value: IEs Count : 9 IE : 0 Protocol IE ID : CORRELATION_ID (2) Criticality : reject (0) CORRELATION_ID Value: 52428800 (0x3200000) IE : 1 Protocol IE ID : LOCATION_TYPE (13) Criticality : reject (0) LOCATION_TYPE Value: Geographic-Information (0) IE : 2 Protocol IE ID : E_UTRAN_CELL_IDENTIFIER (4) Criticality : ignore (1) E_UTRAN_CELL_IDENTIFIER Value: PLMN Identity 0xNNMMM Cell Identity 265986 (0x40f02) IE : 3 Protocol IE ID : LCS_CLIENT_TYPE (8) Criticality : reject (0) LCS_CLIENT_TYPE Value: Lawful-Intercept-Services (3) IE : 4 Protocol IE ID : LCS_PRIORITY (9) Criticality : reject (0) LCS_PRIORITY Value: Highest-Priority (0) IE : 5 Protocol IE ID : LCS_QOS (10) Criticality : reject (0) LCS_QOS Value: Horizontal Accuracy 0 Vertical Requested Vertical Coordinate Is Requested (1) Response Time Delay-Tolerant (1) IE : 6 Protocol IE ID : UE_POSITIONING_CAPABILITY (20) Criticality : reject (0) UE_POSITIONING_CAPABILITY Value: TRUE (1) IE : 7 Protocol IE ID : INCLUDE_VELOCITY (5) Criticality : reject (0) INCLUDE_VELOCITY Value: Not-Requested (1) IE : 8 Protocol IE ID : IMSI (7) Criticality : ignore (1) IMSI Value: XXXXXX09516386f4
End-to-end SLs communication through MME.
+ in 09:20:53:930 SLS Procedure Code: CONNECTION ORIENTED INFORMATION TRANSFER (1) + out 09:20:53:930 S1AP DOWNLINK UE ASSOCIATED LPPA TRANSPORT (44) + in 09:20:53:964 S1AP INITIAL CONTEXT SETUP (9) + in 09:20:54:201 S1AP UPLINK UE ASSOCIATED LPPA TRANSPORT (45) + out 09:20:54:201 SLS Procedure Code: CONNECTION ORIENTED INFORMATION TRANSFER (1)
After that we should respond to SLg diameter request.
Or if We timeout, we could see an abort.
+ out 09:23:19:833 SLS Procedure Code: LOCATION ABORT (3)
+ out 09:23:19:834 Diameter 0x80000c (8388620) Provide-Location-Answer Data: DIAMETER_ERROR_POSITIONING_FAILED (4225)
Show commands
Peer information
******** show sls-service peers all *******
Monday October 10 12:01:27 AST 2016
Total ESMLC:1
MM ESMLC-ID AssocStatus Uptime Peer-ID IP-Addresses-1[state] IP-address-2[state]
-- -------- ----------- ---------- ---------- -------------------------------------------- ----------------------------
08 1 UP 10h48m29s 1xxxxxxx0 10.200.6.30[UP] 10.200.6.11[DOWN]
SLS Service status
******** show sls-service all *******
Monday October 10 12:01:27 AST 2016
Service name : egmlc
Service id : 12
Context : HSS
Status : STARTED
Bind : Done
SLs-MME IP Address : 10.6.0.1
10.6.0.2
SCTP Port : 9082
T-3x01 (Low Delay) : 20 s
T-3x01 (Delay Tolerant) : 20 s
T-3x02 : 3 s
Max Re-Transmission : reset (0)
SCTP Param Template Associated : SLs
SCTP Alpha : 12
SCTP Beta : 25
SCTP Checksum Type : CRC32
SCTP Valid Cookie Lifetime : 60000ms
SCTP Max Assoc Retrans : 8
SCTP Max Number of In Streams : 16
SCTP Init Retransmissions : 8
SCTP Max MTU : 1428bytes
SCTP Max Number of Out Streams : 16
SCTP Path Retransmissions : 4
SCTP Min MTU : 1428bytes
SCTP RTO Initial : 200ms
SCTP RTO Max : 500ms
SCTP RTO Min : 150ms
SCTP Sack Frequency : 1
SCTP Sack Period : 10ms
SCTP Start MTU : 1428bytes
SCTP Heartbeat Status : Enabled
SCTP HeartBeat Timer : 1s
SCTP Bundle Status : Enabled
SCTP Bundle Timer : 100ms
SCTP Alternate Accept Flag : Enabled
SLS Service stats
******** show sls-service statistics *******
Monday October 10 12:01:27 AST 2016
SLS-AP Statistics:
Sent Messages:
Location Request: 633 Location Abort: 126
Connection Info: 8351 Connectionless Info: 0
Reset Req: 0 Reset Ack: 0
Recevied Messages:
Location Response: 508 Connection Info: 8792
Connectionless Info: 0 Reset Req: 0
Reset Ack: 0
SCTP Statistics:
Transmitted SCTP Data:
Init Chunks: 218 Init Ack Chunks: 0
Shutdown Chunks: 0 Shutdown Ack Chunks: 36
Cookie Chunks: 58 Cookie Ack Chunks: 0
Data Chunks: 9120 Data Ack Chunks: 9436
Shutdown Complete Chunks: 0 Heartbeat Chunks: 13644384
HeartBeat Ack Chunks: 11610193 Abort Chunks: 55
Error Chunks: 0
Received SCTP Data:
Init Chunks: 0 Init Ack Chunks: 58
Shutdown Chunks: 36 Shutdown Ack Chunks: 0
Cookie Chunks: 0 Cookie Ack Chunks: 40
Data Chunks: 9436 Data Ack Chunks: 8747
Shutdown Complete Chunks: 36 Heartbeat Chunks: 11610193
HeartBeat Ack Chunks: 4273331 Abort Chunks: 158
Error Chunks: 0
Retransmitted SCTP Data:
Init Chunks: 32 Shutdown Chunks: 0
Shutdown Ack Chunks: 0 Cookie Chunks: 144
Data Chunks: 562
Total Bytes Sent: 1215159 Total Bytes Received: 737483
Total Packets Sent: 9120 Total Packets Received: 9436
Debug logs
2016-Oct-12+11:43:35.438 [sls 206303 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:230] [software internal user syslog] Sent SLS message 2016-Oct-12+11:43:35.438 [sls 206303 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:156] [software internal user syslog] Starting location response timer (40 seconds) 2016-Oct-12+11:43:35.448 [sls 206301 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:417] [callid 209afa9d] [software internal user inbound protocol-log syslog] SLS Rx PDU, from 10.200.6.30:2905 to 10.6.0.1:9082 (69) 2016-Oct-12+11:43:35.556 [sls 206302 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:227] [callid 209afa9d] [software internal user outbound protocol-log syslog] SLS Tx PDU, from 10.6.0.1:9082 to 10.200.6.30:2905 (209) 2016-Oct-12+11:43:51.876 [sls 206303 debug] [5/0/6766 <sessmgr:110> sls_app_utils.c:149] [software internal user syslog] Deleted SLS request. Correlation id : 115343363 2016-Oct-12+11:43:57.965 [sls 206305 info] [5/0/6766 <sessmgr:110> sls_app_msg.c:379] [software internal user syslog] Received SLs message(1) with invalid correlation id (115343363)
... View more
Created by
Gilles Dufour
in Wireless - Mobility Documents
in Wireless - Mobility Documents
11-21-2016
06:20 AM
11-21-2016
06:20 AM
Topology
picture from http://lteworld.org/blog/lcs-architecture-lte-eps
ASR5x00 MME Configuration
context SGSN_MME
mme-service mme
mme-id group-id 32768 mme-code 105
plmn-id mcc MMM mnc NN
associate egtp-service mme-egtp-s10s11 context SGSN_MME
associate hss-peer-service HSS context HSS
associate sgtpc-service sgtp-mme context SGSN_MME
associate sgs-service SGs context SGs
associate location-service SLG_SLS
...
context HSS
interface sls-27/1-vlan704
ip address 10.6.1.60 255.255.255.248
#exit
interface sls-lb1 loopback
ip address 10.6.0.1 255.255.255.255
#exit
interface sls-lb2 loopback
ip address 10.6.0.2 255.255.255.255
location-service SLG_SLS
associate diameter endpoint SLg
associate sls-service egmlc
exit
sls-service egmlc
esmlc esmlc-id 1 ipv4-address 10.200.6.30 ipv4-address 10.200.6.11 port 2905 weight 1
bind ipv4-address 10.16.0.1 ipv4-address 10.6.0.2 port 9082 sctp-template SLs
#exit
diameter endpoint SLg
origin realm cisco.com
use-proxy
origin host MMEXXX.MMEXXX.MME.EPC.MNC0NN.MCCMMM.3GPPNETWORK.ORG address 10.6.0.4 port 3868 address 10.6.0.5
destination-host-avp always
peer diameter.ciscowireless.com realm ciscowireless.com address 10.200.6.9 port 2906 sctp
route-entry peer diameter.ciscowireless.com
route-entry realm ciscowireless.com peer diameter.ciscowireless.com
associate sctp-parameters-template SLg
Troubleshooting
Flow Chart
picture from http://lteworld.org/blog/lcs-architecture-lte-eps
Monitor Subscriber
To understand messages exchanged for LCS, use monitor subscriber with following options (Diameter, S1AP, SLs)
First we receive the SLg Location Request in a diameter message.
+ in 09:20:53:572 Diameter 0x80000c (8388620) Provide-Location-Request Diameter message from 10.200.6.9:2906 to 10.6.0.4:3868 Base Header Information: Version: 0x01 (1) Message Length: 0x0001c0 (448) Command Flags: 0xc0 (192) REQ PXY Command Code: 0x80000c (8388620) Provide-Location-Request
MME triggers S1 Paging
+ out 09:20:53:573 S1AP PAGING (10) ... + out 09:20:53:573 S1AP PAGING (10)
UE responds and MME sends Sls request.
+ in 09:20:53:921 S1AP INITIAL UE MESSAGE (12) + out 09:20:53:921 SLS Procedure Code: LOCATION SERVICE REQUEST (0) SLS Tx PDU, from 10.6.0.1:9082 to 10.200.6.30:2905 (71) SLs-AP (71 bytes) Choice Index : Initiating Message (1) Procedure Code: LOCATION SERVICE REQUEST (0) Criticality : reject (0) LOCATION SERVICE REQUEST value: IEs Count : 9 IE : 0 Protocol IE ID : CORRELATION_ID (2) Criticality : reject (0) CORRELATION_ID Value: 52428800 (0x3200000) IE : 1 Protocol IE ID : LOCATION_TYPE (13) Criticality : reject (0) LOCATION_TYPE Value: Geographic-Information (0) IE : 2 Protocol IE ID : E_UTRAN_CELL_IDENTIFIER (4) Criticality : ignore (1) E_UTRAN_CELL_IDENTIFIER Value: PLMN Identity 0xNNMMM Cell Identity 265986 (0x40f02) IE : 3 Protocol IE ID : LCS_CLIENT_TYPE (8) Criticality : reject (0) LCS_CLIENT_TYPE Value: Lawful-Intercept-Services (3) IE : 4 Protocol IE ID : LCS_PRIORITY (9) Criticality : reject (0) LCS_PRIORITY Value: Highest-Priority (0) IE : 5 Protocol IE ID : LCS_QOS (10) Criticality : reject (0) LCS_QOS Value: Horizontal Accuracy 0 Vertical Requested Vertical Coordinate Is Requested (1) Response Time Delay-Tolerant (1) IE : 6 Protocol IE ID : UE_POSITIONING_CAPABILITY (20) Criticality : reject (0) UE_POSITIONING_CAPABILITY Value: TRUE (1) IE : 7 Protocol IE ID : INCLUDE_VELOCITY (5) Criticality : reject (0) INCLUDE_VELOCITY Value: Not-Requested (1) IE : 8 Protocol IE ID : IMSI (7) Criticality : ignore (1) IMSI Value: XXXXXX09516386f4
End-to-end SLs communication through MME.
+ in 09:20:53:930 SLS Procedure Code: CONNECTION ORIENTED INFORMATION TRANSFER (1) + out 09:20:53:930 S1AP DOWNLINK UE ASSOCIATED LPPA TRANSPORT (44) + in 09:20:53:964 S1AP INITIAL CONTEXT SETUP (9) + in 09:20:54:201 S1AP UPLINK UE ASSOCIATED LPPA TRANSPORT (45) + out 09:20:54:201 SLS Procedure Code: CONNECTION ORIENTED INFORMATION TRANSFER (1)
After that we should respond to SLg diameter request.
Or if We timeout, we could see an abort.
+ out 09:23:19:833 SLS Procedure Code: LOCATION ABORT (3)
+ out 09:23:19:834 Diameter 0x80000c (8388620) Provide-Location-Answer Data: DIAMETER_ERROR_POSITIONING_FAILED (4225)
Show commands
Peer information
******** show sls-service peers all *******
Monday October 10 12:01:27 AST 2016
Total ESMLC:1
MM ESMLC-ID AssocStatus Uptime Peer-ID IP-Addresses-1[state] IP-address-2[state]
-- -------- ----------- ---------- ---------- -------------------------------------------- ----------------------------
08 1 UP 10h48m29s 1xxxxxxx0 10.200.6.30[UP] 10.200.6.11[DOWN]
SLS Service status
******** show sls-service all *******
Monday October 10 12:01:27 AST 2016
Service name : egmlc
Service id : 12
Context : HSS
Status : STARTED
Bind : Done
SLs-MME IP Address : 10.6.0.1
10.6.0.2
SCTP Port : 9082
T-3x01 (Low Delay) : 20 s
T-3x01 (Delay Tolerant) : 20 s
T-3x02 : 3 s
Max Re-Transmission : reset (0)
SCTP Param Template Associated : SLs
SCTP Alpha : 12
SCTP Beta : 25
SCTP Checksum Type : CRC32
SCTP Valid Cookie Lifetime : 60000ms
SCTP Max Assoc Retrans : 8
SCTP Max Number of In Streams : 16
SCTP Init Retransmissions : 8
SCTP Max MTU : 1428bytes
SCTP Max Number of Out Streams : 16
SCTP Path Retransmissions : 4
SCTP Min MTU : 1428bytes
SCTP RTO Initial : 200ms
SCTP RTO Max : 500ms
SCTP RTO Min : 150ms
SCTP Sack Frequency : 1
SCTP Sack Period : 10ms
SCTP Start MTU : 1428bytes
SCTP Heartbeat Status : Enabled
SCTP HeartBeat Timer : 1s
SCTP Bundle Status : Enabled
SCTP Bundle Timer : 100ms
SCTP Alternate Accept Flag : Enabled
SLS Service stats
******** show sls-service statistics *******
Monday October 10 12:01:27 AST 2016
SLS-AP Statistics:
Sent Messages:
Location Request: 633 Location Abort: 126
Connection Info: 8351 Connectionless Info: 0
Reset Req: 0 Reset Ack: 0
Recevied Messages:
Location Response: 508 Connection Info: 8792
Connectionless Info: 0 Reset Req: 0
Reset Ack: 0
SCTP Statistics:
Transmitted SCTP Data:
Init Chunks: 218 Init Ack Chunks: 0
Shutdown Chunks: 0 Shutdown Ack Chunks: 36
Cookie Chunks: 58 Cookie Ack Chunks: 0
Data Chunks: 9120 Data Ack Chunks: 9436
Shutdown Complete Chunks: 0 Heartbeat Chunks: 13644384
HeartBeat Ack Chunks: 11610193 Abort Chunks: 55
Error Chunks: 0
Received SCTP Data:
Init Chunks: 0 Init Ack Chunks: 58
Shutdown Chunks: 36 Shutdown Ack Chunks: 0
Cookie Chunks: 0 Cookie Ack Chunks: 40
Data Chunks: 9436 Data Ack Chunks: 8747
Shutdown Complete Chunks: 36 Heartbeat Chunks: 11610193
HeartBeat Ack Chunks: 4273331 Abort Chunks: 158
Error Chunks: 0
Retransmitted SCTP Data:
Init Chunks: 32 Shutdown Chunks: 0
Shutdown Ack Chunks: 0 Cookie Chunks: 144
Data Chunks: 562
Total Bytes Sent: 1215159 Total Bytes Received: 737483
Total Packets Sent: 9120 Total Packets Received: 9436
Debug logs
2016-Oct-12+11:43:35.438 [sls 206303 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:230] [software internal user syslog] Sent SLS message 2016-Oct-12+11:43:35.438 [sls 206303 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:156] [software internal user syslog] Starting location response timer (40 seconds) 2016-Oct-12+11:43:35.448 [sls 206301 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:417] [callid 209afa9d] [software internal user inbound protocol-log syslog] SLS Rx PDU, from 10.200.6.30:2905 to 10.6.0.1:9082 (69) 2016-Oct-12+11:43:35.556 [sls 206302 debug] [5/0/6766 <sessmgr:110> sls_app_msg.c:227] [callid 209afa9d] [software internal user outbound protocol-log syslog] SLS Tx PDU, from 10.6.0.1:9082 to 10.200.6.30:2905 (209) 2016-Oct-12+11:43:51.876 [sls 206303 debug] [5/0/6766 <sessmgr:110> sls_app_utils.c:149] [software internal user syslog] Deleted SLS request. Correlation id : 115343363 2016-Oct-12+11:43:57.965 [sls 206305 info] [5/0/6766 <sessmgr:110> sls_app_msg.c:379] [software internal user syslog] Received SLs message(1) with invalid correlation id (115343363)
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
01-26-2015
04:19 AM
01-26-2015
04:19 AM
You can use direct connection if you want. DRA are not mandatory. However they offer some functionalities which could be useful in big network like load balancing. Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
01-24-2015
05:34 AM
01-24-2015
05:34 AM
The config is what I sent you for pgw. qci-qos-mapping allows you to set the user dscp (inner header) and encaps header dscp (outer header). Or ip qos-dscp qci 1 be qci 2 be qci 3 be qci 4 be qci 5 be qci 6 be qci 7 be qci 8 be Under apn or ggsn-service or sgsn-service. You can also use a dscp template http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/14_0/OL-27223_SGSN_Admin.pdf The following configuration procedure is used to configure DSCP value for 3GPP QoS class downlink data packets: config context <context_name> sgsn-global dscp-template<template_name> data-packet { background | conversationa | interactive { priority1 | priority2 | priority3 } | streaming } qos-dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | cs1 | cs2 | cs3 | cs4 | cs5 | cs6 | cs7 | ef } exit Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
01-23-2015
01:11 AM
01-23-2015
01:11 AM
policing and marking are done separately. If you need to mark your traffic, you can do it in many different ways. For example under apn configuration apn internet ip qos-dscp qci 1 be qci 2 be qci 3 be qci 4 be qci 5 be qci 6 be qci 7 be qci 8 be or in a qci-qos map qci-qos-mapping pgw-qos-mapping qci 1 uplink user-datagram dscp-marking 0x2e encaps-header dscp-marking 0x2e downlink user-datagram dscp-marking 0x2e encaps-header dscp-marking 0x2e qci 2 uplink user-datagram dscp-marking 0x22 encaps-header dscp-marking 0x22 downlink user-datagram dscp-marking 0x22 encaps-header dscp-marking 0x22 qci 3 uplink user-datagram dscp-marking 0x22 encaps-header dscp-marking 0x22 downlink user-datagram dscp-marking 0x22 encaps-header dscp-marking 0x22 qci 4 uplink user-datagram dscp-marking 0x22 encaps-header dscp-marking 0x22 downlink user-datagram dscp-marking 0x22 encaps-header dscp-marking 0x22 qci 5 uplink user-datagram dscp-marking 0x2e encaps-header dscp-marking 0x2e downlink user-datagram dscp-marking 0x2e encaps-header dscp-marking 0x2e qci 6 uplink user-datagram dscp-marking 0x00 encaps-header dscp-marking 0x00 downlink user-datagram dscp-marking 0x00 encaps-header dscp-marking 0x00 qci 7 uplink user-datagram dscp-marking 0x00 encaps-header dscp-marking 0x00 downlink user-datagram dscp-marking 0x00 encaps-header dscp-marking 0x00 qci 9 uplink user-datagram dscp-marking 0x00 encaps-header dscp-marking 0x00 downlink user-datagram dscp-marking 0x00 encaps-header dscp-marking 0x00 and you link it to a pgw or sgw service pgw-service pgw-svc associate qci-qos-mapping pgw-qos-mapping The encaps-header cab also be set to copy-inner. In this case you have the same DSCP for GTPU than the packet contains in GTPU. So this is one way to do E2E QOS. Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
01-23-2015
12:20 AM
01-23-2015
12:20 AM
diameter for Gx and Gy can be very chatty. So indeed you need a robust server to handle all the traffic. My question regarding multimode and single mode is regarding the diameter-proxy function. Forgot to also ask you if you use the diamter-proxy option. Basically, you could have every sessmgr communicating with the PCRF or have 1 (single mode) diameter-proxy receiving all the requests from the sessmgr and sending them to the server or have 1 diameter proxy per PSC/DPC card (multimode). Diameter-proxy in multimode is what I would recommend. It will be easier I believe for the server to handle a few connections than to manage traffic from all sessmgr. Not sure what configuration you have in place.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
01-22-2015
05:20 AM
01-22-2015
05:20 AM
Did you capture sniffer trace to check if there is any packet drops on the network ? Are you using TCP or SCTP ? Multimode or single mode ? There could be many reasons for retransmit. Thanks. Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
01-20-2015
07:47 PM
01-20-2015
07:47 PM
I believe you are talking about virtual-apn http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_5000/12_2/OL-25637_GGSN_Admin1.pdf Virtual APNs are references (or links) to alternative APNs to be used for PDP context processing based on properties of the context. Use the following example to configure the virtual APNs. configure context <dst_ctxt_name> apn <apn_name> virtual-apn preference <priority> apn <apn_name> { access-gw-address <IP_addr | IP_addr/mask> | bearer-access-service <bearer_access_svc_name> | cc-profile <cc_profile_index> | domain <domain_name> | mcc <mcc_number> mnc <mnc_number> | msisdn-range from <start_range> to <end_range> | rat-type { eutran | gan | geran | hspa | utran | wlan } | roaming-mode { home | visiting | roaming } end Notes: Up to 1023 references can be configured per APN. Additional information about “virtual” APNs and their operation can be found in the Command Line Interface Reference So a sample config would look like this : apn ggsn3drivetest pdp-type ipv4 ipv6 selection-mode subscribed sent-by-ms chosen-by-sgsn virtual-apn gcdr apn-name-to-be-included Gn virtual-apn preference 100 apn ggsn3drivetest-voice msisdn-range from xxxx0102901 to xxxx0102901 virtual-apn preference 200 apn ggsn3drivetest-voice cc-profile 1 virtual-apn preference 900 apn ggsn3drivetest-pub exit apn ggsn3drivetest-pub pdp-type ipv4 ipv6 bearer-control-mode mixed accounting-mode none gtpp group pgwtest accounting-context ga apn-ambr rate-limit direction downlink burst-size auto-readjust duration 1 violate-action drop apn-ambr rate-limit direction uplink burst-size auto-readjust duration 1 violate-action drop ims-auth-service activesdby-lte aaa group radius-dpi dns primary x.x.x.x dns secondary x.x.x.x timeout idle 11400 ip access-group ecs in ip access-group ecs out ip source-violation check drop-limit 0 mediation-device context-name gi ip context-name gi ip address pool name pub qos rate-limit direction downlink burst-size auto-readjust exceed-action drop qos rate-limit direction uplink burst-size auto-readjust exceed-action drop credit-control-group ocs-dr-test active-charging rulebase bypass apn ggsn3drivetest-voice pdp-type ipv4 ipv6 bearer-control-mode mixed accounting-mode none gtpp group pgwtest accounting-context ga apn-ambr rate-limit direction downlink burst-size auto-readjust duration 1 violate-action drop apn-ambr rate-limit direction uplink burst-size auto-readjust duration 1 violate-action drop ims-auth-service activesdby-lte aaa group radius-dpi dns primary x.x.x.x dns secondary x.x.x.x timeout idle 11400 ip access-group ecs in ip access-group ecs out ip source-violation check drop-limit 0 mediation-device context-name gi ip context-name gi ip address pool name priv qos rate-limit direction downlink burst-size auto-readjust exceed-action drop qos rate-limit direction uplink burst-size auto-readjust exceed-action drop credit-control-group ocs-dr-test active-charging rulebase bypass fw-and-nat policy TESTNAT44 ... Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-29-2013
01:57 AM
11-29-2013
01:57 AM
Indeed the ASR5k could also be configured with eWAG service to interconnect Wifi world with LTE. It all depends on the wifi you want to use. Maybe it is clearer from this link http://www.cisco.com/en/US/prod/collateral/wireless/ps11035/ps11047/ps11072/ps12542/data_sheet_c78-712213_ps11080_Products_Data_Sheet.html But basically, with an ASR5k you're sure to have the right equipment to interconnect both world. You may have to play a bit with the config to find the right setup for your environment. I find the following document also very interesting http://www.cisco.com/assets/global/YU/expo2012/pdfs/sp_wifi_sesija_1_core.pdf Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-28-2013
07:19 AM
11-28-2013
07:19 AM
I believe the structure is like this :
* 31 30 29 24 23 18 17 9 8 0
* |----| |------------| |------------| |----------------| |------------------|
* | 11 | | SubId High | | NRI bits | | Sub Id Low | | SMGR Instance |
* | | | Order Bits | | | | Order Bits | | bits |
* |----| |------------| |------------| |----------------| |------------------|
*
* Total Protocol reseved bit = 2 (31-30)
* Subscriber High Order bits = 6 (29-24)
* NRI bits = 6 (23-18)
* Subscriber Low Order bits = 9 (17-9)
* SMGR instance bits = 9 (8-0)
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-27-2013
04:44 AM
11-27-2013
04:44 AM
Here is a potential solution a) “rau-inter restrict access-type umts/gprs all” To restrict Inter SGSN handoff b) ”rau-inter access-type umts/gprs all failure-code 10” To set the gmm cause “Implicit Detach(10)” in RAU Reject msg. Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-25-2013
01:57 AM
11-25-2013
01:57 AM
Assuming you have LTE environment and Wifi network, what you need is a gateway between the 2. The ASR5k configured as an HNbGW can service this purpose. Some example here http://www.cisco.com/web/HR/ciscoconnect/2013/pdfs/Cisco_Small_Cell_Architecture_Patrice_Nivaggioli_Consulting_System_Engineer_SP_EMEAR.pdf Or the ASR1k setup as an ISG. See slide 42 from http://www.slideshare.net/c0nd3/cisco-mobile-offloadarchitecture21062012 Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-24-2013
06:04 AM
11-24-2013
06:04 AM
SAEGW is a combination of SGW/PGW services, once you add following three lines SGW/PGW services (in same ingress context) get associated with each other. If a subscriber lands on SGW/PGW service part of SAEGW, then we collapse two call lines into single call line. This basically saves one call line across chassis, effectively doubling the session handling capacity of the system. Regards. Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-23-2013
06:22 AM
11-23-2013
06:22 AM
Hi Henry,
The username displayed in monitor info can be received in “Protocol Config Options” IE
received from SGSN or ff this is not available in the PCO option then username
is locally derived at the GGSN based on config. Regards. Gilles.
... View more
Created by
Gilles Dufour
in Wireless Security and Network Management
in Wireless Security and Network Management
11-20-2013
11:19 PM
11-20-2013
11:19 PM
Hi Evan, yes it is possible but you need 14.0 or higher version. You need a version which fixes ddts CSCtw84421. Regards. Gilles.
... View more
Created by
Gilles Dufour
in Wireless - Mobility Documents
11-21-2016
11-21-2016
Topology picture from http://lteworld.org/blog/lcs-architecture-lte-eps
ASR5x00 MME Configuration co...
Created by
Gilles Dufour
in Wireless - Mobility Documents
11-21-2016
11-21-2016
Topology picture from http://lteworld.org/blog/lcs-architecture-lte-eps
ASR5x00 MME Configuration co...
Created by
Gilles Dufour
in Wireless Security and Network Management
01-26-2015
01-26-2015
You can use direct connection if you want. DRA are not mandatory.However
they offer some functionali...
Created by
Gilles Dufour
in Wireless Security and Network Management
01-24-2015
01-24-2015
The config is what I sent you for pgw.qci-qos-mapping allows you to set
the user dscp (inner header)...
Created by
Gilles Dufour
in Wireless Security and Network Management
01-23-2015
01-23-2015
policing and marking are done separately.If you need to mark your
traffic, you can do it in many dif...
Created by
Gilles Dufour
in Wireless Security and Network Management
01-23-2015
01-23-2015
diameter for Gx and Gy can be very chatty. So indeed you need a robust
server to handle all the traf...
Created by
Gilles Dufour
in Wireless Security and Network Management
01-22-2015
01-22-2015
Did you capture sniffer trace to check if there is any packet drops on
the network ?Are you using TC...
Created by
Gilles Dufour
in Wireless Security and Network Management
01-20-2015
01-20-2015
I believe you are talking about virtual-apn
http://www.cisco.com/c/dam/en/us/td/docs/wireless/asr_50...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-29-2013
11-29-2013
Indeed the ASR5k could also be configured with eWAG service to
interconnect Wifi world with LTE.It a...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-28-2013
11-28-2013
I believe the structure is like this : * 31 30 29 24 23 18 17 9 8 0 *
|----| |------------| |-------...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-27-2013
11-27-2013
Here is a potential solutiona) “rau-inter restrict access-type umts/gprs
all” To restrict Inter SGSN...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-25-2013
11-25-2013
Assuming you have LTE environment and Wifi network, what you need is a
gateway between the 2.The ASR...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-24-2013
11-24-2013
SAEGW is a combination of SGW/PGW services, once you add following three
lines SGW/PGW services (in ...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-23-2013
11-23-2013
Hi Henry, The username displayed in monitor info can be received in
“Protocol Config Options” IE rec...
Created by
Gilles Dufour
in Wireless Security and Network Management
11-20-2013
11-20-2013
Hi Evan,yes it is possible but you need 14.0 or higher version.You need
a version which fixes ddts C...
Public Statistics
| Date Registered | 02-21-2002 07:51 PM |
| Date Last Visited | 07-18-2018 12:03 AM |
| Total Messages Posted | 5,920 |
| Total Helpful Votes Received | 3754 |
Helpful Votes Given To
| User | Helpful Count |
|---|---|
| 5 | |
| 1 | |
| 7 | |
| 5 | |
| 10 |
Helpful Votes From
| User | Helpful Count |
|---|---|
| 20 | |
| 98 | |
| 5 | |
| 10 | |
| 10 |
