PDP Activation failed Possible Root Cause 3GPP 29.060 7.7.

"No resources available" indicates that not enough resources are available within the network to
allow the PDP Context to be created.

"Missing or unknown APN" indicates e.g. when the GGSN does not support the Access Point
Name.

"Unknown PDP address or PDP type" indicates when the GGSN does not support the PDP type
or the PDP address.

"User authentication failed" indicates that the external packet network has rejected the service
requested by the user e.g. the authentication check in the RADIUS server failed.

"PDP context without TFT already activated" indicates that a PDP context has already been
activated without a TFT for that MS.

"Context not found" indicates that a Create PDP Request for a subsequent PDP context has been
received, but the PDP context associated with the request, which the SGSN believes to be active
does not exist on the GGSN.

"APN access denied – no subscription" indicates that the GGSN has denied the user access to an
APN because a subscription is required, but the subscriber does not have the necessary
subscription.

"New PDP type due to network preference" indicates that the GGSN has selected a PDP type
different from the one sent by the MS.

"New PDP type due to single address bearer only" indicates that the MS has requested PDP type
IPv4v6 and both IPv4 and IPv6 addressing is possible in the PDN but the Dual Address Bearer
Flag bit of the Common Flags IE is set to 0 or the Common Flags IE is absent, or only single IP
version addressing is possible in the PDN.
PDP Activation Failed due to Core

Cause value Cause

192 Non-existent
193 Invalid message format
194 IMSI not known
195 MS is GPRS Detached
196 MS is not GPRS Responding
197 MS Refuses
198 Version not supported
199 No resources available
200 Service not supported
201 Mandatory IE incorrect
202 Mandatory IE missing
203 Optional IE incorrect
204 System failure
205 Roaming restriction
206 P-TMSI Signature mismatch
207 GPRS connection suspended
208 Authentication failure
209 User authentication failed
210 Context not found
211 All dynamic PDP addresses are occupied
212 No memory is available
213 Relocation failure
214 Unknown mandatory extension header
215 Semantic error in the TFT operation
216 Syntactic error in the TFT operation
217 Semantic errors in packet filter(s)
218 Syntactic errors in packet filter(s)
219 Missing or unknown APN
220 Unknown PDP address or PDP type
221 PDP context without TFT already activated
222 APN access denied – no subscription
223 APN Restriction type incompatibility withcurrently active PDP Contexts
224 MS MBMS Capabilities Insufficient
225 Invalid Correlation-ID
 226 MBMS Bearer Context Superseded

PDP Activation Failed due to RAN

Cause value Cause

25 LLC or SNDCP Failure
26 Insufficient Resources
27 Missing or Unknown APN
28 Unknown PDP Address or PDP Type
29 User Authentication Failed
30 Activation Rejected By GGSN
31 Activation Rejected, Unspecified
32 Service Option Not Supported
33 Requested Service Opt Not Subscribed
34 Service Opt Temporarily Out of Order
35 NSAPI Already Used
36 Regular Deactivation
37 QoS Not Accepted
38 Network Failure
39 Reactivation Required
40 Feature Not Supported
41 Semantic Error in TFT Operation
42 Syntactical Error in TFT Operation
43 Unknown PDP Context
44 Semantic Error in Packet Filter(s)
45 Syntactical Error inPacket Filter(s)
46 PDP Context Without TFT Already Activated
81 Invalid Transaction Identifier Value
95 Semantically Incorrect Message
96 Invalid Mandatory Information
97 Msg Type Non-existent/Non ImplementedState
98 Msg Type Not Compatible With Protocol State
99 IE Non-existent or Not Implemented
100 Conditional IE Error
101 Msg Not Compatible With Protocol State
111 Protocol Error, Unspecified
112 APN Restrict Value Incompatible Without PDP Context
3GPP spesific cause value for mobility management (packet)

Mobile radio interface Layer 3 specification(3GPP TS 24.008)

In here are all the PDP reject response message. I'm just take the Packet portion since that is the world that i'm
currently in.

G.1 Causes related to MS identification

Cause value = 2 IMSI unknown in HLR

This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code
does not affect operation of the GPRS service, although is may be used by a GMM procedure.

Cause value = 3 Illegal MS

This cause is sent to the MS when the network refuses service to the MS either because an
identity of the MS is not acceptable to the network or because the MS does not pass the
authentication check, i.e. the SRES received from the MS is different from that generated by the
network. When used by an MM procedure, except the authentication procedure, this cause does
not affect operation of the GPRS service.

Cause value = 4 IMSI unknown in VLR

This cause is sent to the MS when the given IMSI is not known at the VLR.

Cause value = 5 IMEI not accepted

This cause is sent to the MS if the network does not accept emergency call establishment using
an IMEI or not accept attach procedure for emergency services using an IMEI.

Cause value = 6 Illegal ME

This cause is sent to the MS if the ME used is not acceptable to the network, e.g. blacklisted.
When used by an MM procedure, this cause does not affect operation of the GPRS service.

G.2 Cause related to subscription options

Cause value = 11 PLMN not allowed

This cause is sent to the MS if it requests location updating in a PLMN where the MS, by
subscription or due to operator determined barring is not allowed to operate.

Cause value = 12 Location Area not allowed

This cause is sent to the MS if it requests location updating in a location area where the HPLMN
determines that the MS, by subscription, is not allowed to operate.

NOTE: If cause #12 is sent to a roaming subscriber the subscriber is denied service even if other
PLMNs are available on which registration was possible.
Cause value = 13 Roaming not allowed in this location area
This cause is sent to an MS which requests location updating in a location area of a PLMN which
by subscription offers roaming to that MS but not in that Location Area.

Cause value = 15 No Suitable Cells In Location Area

This cause is sent to the MS if it requests location updating in a location area where the MS, by
subscription, is not allowed to operate, but when it should find another allowed location area in
the same PLMN.

NOTE: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to
search for another allowed location area on the same PLMN.

Cause value = 25 Not authorized for this CSG

This cause is sent to the MS if it requests access in a CSG cell where the MS either has no
subscription to operate or the MS's subscription has expired and it should find another cell in the
same PLMN.

NOTE: The MS not supporting CSG will not receive cause# 25, as such a MS is not supposed to
try to access a CSG cell.

G.3 Causes related to PLMN specific network failures and congestion/Authentication Failures

Cause value = 20 MAC failure

This cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION
REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is not fresh (see
3GPP TS 33.102 [5a]).

Cause value = 21 Synch failure

This cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION
REQUEST or AUTHENTICATION_AND_CIPHERING REQUEST message is out of range
(see 3GPP TS 33.102 [5a]).

Cause value = 17 Network failure

This cause is sent to the MS if the MSC cannot service an MS generated request because of
PLMN failures, e.g. problems in MAP.

Cause value = 22 Congestion

This cause is sent if the service request cannot be actioned because of congestion (e.g. no
channel, facility busy/congested etc.).

Cause value = 23 GSM authentication unacceptable

This cause is sent to the network in Iu mode if a USIM is inserted in the MS and there is no
Authentication Parameter AUTN IE present in the AUTHENTICATION REQUEST or
AUTHENTICATION_AND_CIPHERING REQUEST message.
G.4 Causes related to nature of request

Cause value = 32 Service option not supported

This cause is sent when the MS requests a service/facility in the CM SERVICE REQUEST
message which is not supported by the PLMN.

Cause value = 33 Requested service option not subscribed

This cause is sent when the MS requests a service option for which it has no subscription.

Cause value = 34 Service option temporarily out of order

This cause is sent when the MSC cannot service the request because of temporary outage of one
or more functions required for supporting the service.

Cause value = 38 Call cannot be identified

This cause is sent when the network cannot identify the call associated with a call re-
establishment request.

G.5 Causes related to invalid messages

Cause value = 95 Semantically incorrect message.

See annex H, subclause H.5.10.

Cause value = 96 Invalid mandatory information.

See annex H, subclause H.6.1.

Cause value = 97 Message type non-existent or not implemented.

See annex H, subclause H.6.2.

Cause value = 98 Message not compatible with protocol state.

See annex H, subclause H.6.3.

Cause value = 99 Information element non-existent or not implemented.

See annex H, subclause H.6.4.

Cause value = 100 Conditional IE error.

See annex H, subclause H.6.5.

Cause value = 101 Message not compatible with protocol state.

See annex H, subclause H.6.6.

Cause value = 111 Protocol error, unspecified.

See annex H, subclause H.6.8.
G.6 Additional cause codes for GMM

Cause value = 7 GPRS services not allowed

This cause is sent to the MS when it is not allowed to operate GPRS services.

Cause value = 8 GPRS services and non-GPRS services not allowed

This cause is sent to the MS when it is not allowed to operate either GPRS or non-GPRS
services.

Cause value = 9 MS identity cannot be derived by the network

This cause is sent to the MS when the network cannot derive the MS's identity from the P-TMSI
in case of inter-SGSN routing area update.

Cause value = 10 Implicitly detached

This cause is sent to the MS either if the network has implicitly detached the MS, e.g. some
while after the Mobile reachable timer has expired, or if the GMM context data related to the
subscription dose not exist in the SGSN e.g. because of a SGSN restart.

Cause value = 14 GPRS services not allowed in this PLMN

This cause is sent to the MS which requests GPRS service in a PLMN which does not offer
roaming for GPRS services to that MS.

Cause value = 16 MSC temporarily not reachable

This cause is sent to the MS if it requests a combined GPRS attach or routing are updating in a
PLMN where the MSC is temporarily not reachable via the GPRS part of the network.

Cause value = 40 No PDP context activated

This cause is sent to the MS if the MS requests an establishment of the radio access bearers for
all active PDP contexts by sending a SERVICE REQUEST message indicating "data" to the
network, but the SGSN does not have any active PDP context(s).

Reference:
Mobile radio interface Layer 3 specification(3GPP TS 24.008)
GPRS specific cause values for GPRS Session Management

!" # $ # % !" &' &(

)* + + & ! !
!" # $ + +& , #
% !" # $-! + + &! ! + +&

). // &(0 123' ! "4

!" +& 0 0 , ! // &( 0
1 &+ &( &+ 5& 2 6 & # 7 + 7 7
8 7- 9' 00 & ** :;. <= >4

);
!" +& !" # $ 0 0 , -
"0 0 , -0 0 , - + +& ,
!

)= 6 $ #
!" # $ # % !"
, $ # $! #
!

) 6 $ # 0 0 0 0 "
!" # $ # % !"
, $ # $! 0 0 " !

)? 6
!" # $ # % !"
, $ # $

9: 2 % !" ' ' &( -& '@ 0 ( '@

!" # $ # % !" ' ' &( -
& '@ 0 ( '@

9 2 % -
!" # $ # %
 9) &
!" # $# +& # !"
0/+ (

99 ! !
& 2 ,'- *

9* & "
& 2 ,'- *

9. ( &20 "
"! !" # $ ( &20 !" +& 0 0
, " !" 0 0 , +&

( ! -! ! ?=3 ? # $ 0 0 ,

9;
+& # $ 0 0 ,
# $ + +& ,

9= A &
!" +& # A & ! # !"
# $ 0 0 , +

9 ( # $
!" # $ 0 0 , + +&
, !" # $

9?
!" # $ 0 0 , ' ' &(

*: B
!" +& 0 0 , + +& ,
!" # $ !" +&

* B
!" # $ +& B
"0 0 , + &5 0 0 ,
# $ "0 0 ,
 *) " B
!" # $ +& " B
"0 0 , + &5 0 0 ,
# $ "0 0 ,

*9 $ # 0 0 ,
!" # $ +& 0 0 , !"
/ $ C "0 0 , # $ "0 0
,

** $ 14
!" # $ +&
$ 14 B "0 0 , + &5
0 0 , # $ "0 0 ,

*. " $ 14

!" # $ +& "

$ 14 B "0 0 , + &5
0 0 , # $ "0 0 ,

*; 0 0 , # B "
!" # $ +& " 0 0 ,
# B

*= + ! 5
!" # $ + +& , !
'+ 0 ! 1 B 99=; < :=>- ! *4 +/
1 B )= : < : >- ! = *4 ,

* 2 % - +
!" # $ +& # %
! +

.: 0 0 " 0 * " #
!" # $ 0 ( " #
"0 0 " 0 * #

. 0 0 " 0 ; " #
!" # $ 0 ( " #
"0 0 " 0 ; #
 .) ! " #
!" # $ 0 ( " #
" 0 ! #

.; # # $
!" # $ + &5 # %
# $ "0 0 , # $5

) 20( ! # 0 0 ,
!" # $ 0 0 , 14 + +& , 14
20( # ! # " 0 0 ,
9' 00 & )9 :;: <=*>- ! .*

& ,D- ! D.

?. & "
& ,D- ! D ..

?; "
& ,D- ! D;

?= + " 5 ,
& ,D- ! D ;)

? + ! #
& ,D- ! D ;9

?? 5 ,
& ,D- ! D ;*

:: C
& ,D- ! D ;.

: + ! #
& ,D- ! D ;;
 0 -
& ,D- ! D;

3GPP specific cause values for call control

This is just extension from 3GPP specific cause value for mobility management (packet) . They seems connected
somehow.

H.1 Normal class

H.1.1 Cause No. 1 "unassigned (unallocated) number"

This cause indicates that the destination requested by the mobile station cannot be reached
because, although the number is in a valid format, it is not currently assigned (allocated).

H.1.2 Cause No. 3 "no route to destination"

This cause indicates that the called user cannot be reached because the network through which
the call has been routed does not serve the destination desired.

H.1.3 Cause No. 6 "channel unacceptable"

This cause indicates the channel most recently identified is not acceptable to the sending entity
for use in this call.

H.1.4 Cause No. 8 "operator determined barring"

This cause indicates that the MS has tried to access a service that the MS's network operator or
service provider is not prepared to allow.

H.1.5 Cause No.16 "normal call clearing"

This cause indicates that the call is being cleared because one of the users involved in the call has
requested that the call be cleared.
Under normal situations, the source of this cause is not the network.

H.1.6 Cause No.17 "user busy"

This cause is used when the called user has indicated the inability to accept another call.
It is noted that the user equipment is compatible with the call.

H.1.7 Cause No. 18 "no user responding"

This cause is used when a user does not respond to a call establishment message with either an
alerting or connect indication within the prescribed period of time allocated (defined by the
expiry of either timer T303 or T310).

H.1.8 Cause No. 19 "user alerting, no answer"

This cause is used when a user has provided an alerting indication but has not provided a connect
indication within a prescribed period of time.
H.1.9 Cause No. 21 "call rejected"
This cause indicates that the equipment sending this cause does not wish to accept this call,
although it could have accepted the call because the equipment sending this cause is neither busy
nor incompatible.

H.1.10 Cause No. 22 "number changed"

This cause is returned to a calling mobile station when the called party number indicated by the
calling mobile station is no longer assigned. The new called party number may optionally be
included in the diagnostic field. If a network does not support this capability, cause No.
1 "unassigned (unallocated) number" shall be used.

H.1.11 Cause No. 25 "pre-emption"

This cause is returned to the network when a mobile station clears an active call which is being
pre-empted by another call with higher precedence.

H.1.12 Cause No. 26 "non-selected user clearing"

Not supported. Treated as cause no. 31.

H.1.13 Cause No. 27 "destination out of order"

This cause indicates that the destination indicated by the mobile station cannot be reached
because the interface to the destination is not functioning correctly. The term "not functioning
correctly" indicates that a signalling message was unable to be delivered to the remote user; e.g.,
a physical layer or data link layer failure at the remote user, user equipment off-line, etc.

H.1.14 Cause No. 28 "invalid number format (incomplete number)"

This cause indicates that the called user cannot be reached because the called party number is not
a valid format or is not complete.

H.1.15 Cause No. 29 "facility rejected"

This cause is returned when a facility requested by user can not be provided by the network.

H.1.16 Cause No. 30 "response to STATUS ENQUIRY"

This cause is included in STATUS messages if the message is sent in response to a STATUS
ENQUIRY message. See also subclause 5.5.3.

H.1.17 Cause No. 31 "normal, unspecified"

This cause is used to report a normal event only when no other cause in the normal class applies.

H.2 Resource unavailable class

H.2.1 Cause No. 34 "no circuit/channel available"

This cause indicates that there is no appropriate circuit/channel presently available to handle the
call.

H.2.2 Cause No. 38 "network out of order"

This cause indicates that the network is not functioning correctly and that the condition is likely
to last a relatively long period of time; e.g., immediately re-attempting the call is not likely to be
successful.

H.2.3 Cause No. 41 "temporary failure"

This cause indicates that the network is not functioning correctly and that the condition is not
likely to last a long period of time; e.g., the mobile station may wish to try another call attempt
almost immediately.

H.2.4 Cause No. 42 "switching equipment congestion"

This cause indicates that the switching equipment generating this cause is experiencing a period
of high traffic.

H.2.5 Cause No. 43 "access information discarded"

This cause indicates that the network could not deliver access information to the remote user as
requested; i.e., a user-to-user information, low layer compatibility, high layer compatibility, or
sub-address as indicated in the diagnostic.
It is noted that the particular type of access information discarded is optionally included in the
diagnostic.

H.2.6 Cause No. 44 "requested circuit/channel not available"

This cause is returned when the circuit or channel indicated by the requesting entity cannot be
provided by the other side of the interface.

H.2.7 Cause No. 47 "resource unavailable, unspecified"

This cause is used to report a resource unavailable event only when no other cause in the
resource unavailable class applies.

H.3 Service or option not available class

H.3.1 Cause No. 49 "quality of service unavailable"

This cause indicates to the mobile station that the requested quality of service, as defined in ITU-
T Recommendation X.213, cannot be provided.

H.3.2 Cause No. 50 "Requested facility not subscribed"

This cause indicates that the requested supplementary service could not be provided by the
network because the user has no completed the necessary administrative arrangements with its
supporting networks.

H.3.3 Cause No. 55 "Incoming calls barred within the CUG"

This cause indicates that although the called party is a member of the CUG for the incoming
CUG call, incoming calls are not allowed within this CUG.

H.3.4 Cause No. 57 "bearer capability not authorized"

This cause indicates that the mobile station has requested a bearer capability which is
implemented by the equipment which generated this cause but the mobile station is not
authorized to use.
H.3.5 Cause No. 58 "bearer capability not presently available"
This cause indicates that the mobile station has requested a bearer capability which is
implemented by the equipment which generated this cause but which is not available at this time.

H.3.6 Cause No. 63 "service or option not available, unspecified"

This cause is used to report a service or option not available event only when no other cause in
the service or option not available class applies.

H.3.7 Cause No. 68 "ACM equal to or greater than ACMmax"

This cause is used by the mobile to indicate that call clearing is due to ACM being greater than
or equal to ACMmax.

H.4 Service or option not implemented class

H.4.1 Cause No. 65 "bearer service not implemented"

This cause indicates that the equipment sending this cause does not support the bearer capability
requested.

H.4.2 Cause No. 69 "Requested facility not implemented"

This cause indicates that the equipment sending this cause does not support the requested
supplementary service.

H.4.3 Cause No. 70 "only restricted digital information bearer capability is available"
This cause indicates that one equipment has requested an unrestricted bearer service, but that the
equipment sending this cause only supports the restricted version of the requested bearer
capability.

H.4.4 Cause No. 79 "service or option not implemented, unspecified"

This cause is used to report a service or option not implemented event only when no other cause
in the service or option not implemented class applies.

H.5 Invalid message (e.g., parameter out of range) class

H.5.1 Cause No. 81 "invalid transaction identifier value"

This cause indicates that the equipment sending this cause has received a message with a
transaction identifier which is not currently in use on the MS-network interface.

H.5.2 Cause No. 87 "user not member of CUG"

This cause indicates that the called user for the incoming CUG call is not a member of the
specified CUG.

H.5.3 Cause No. 88 "incompatible destination"

This cause indicates that the equipment sending this cause has received a request to establish a
call which has low layer compatibility, high layer compatibility, or other compatibility attributes
(e.g., data rate) which cannot be accommodated.
H.5.4 Cause No. 91 "invalid transit network selection"
For further study. Treated as cause no. 95.

H.5.5 Cause No. 95 "semantically incorrect message"

This cause is used to report receipt of a message with semantically incorrect contents (see
subclause 8.8).

H.6 Protocol error (e.g., unknown message) class

H.6.1 Cause No. 96 "invalid mandatory information"

This cause indicates that the equipment sending this cause has received a message with a non-
semantical mandatory IE error (see subclause 8.5).

H.6.2 Cause No. 97 "message type non-existent or not implemented"

This cause indicates that the equipment sending this cause has received a message with a
message type it does not recognize either because this is a message not defined, or defined but
not implemented by the equipment sending this cause.

H.6.3 Cause No. 98 "message type not compatible with protocol state"
This cause indicates that the equipment sending this cause has received a message not
compatible with the protocol state (subclause 8.4).

H.6.4 Cause No. 99 "information element non-existent or not implemented"

This cause indicates that the equipment sending this cause has received a message which
includes information elements not recognized because the information element identifier is not
defined or it is defined but not implemented by the equipment sending the cause. However, the
information element is not required to be present in the message in order for the equipment
sending the cause to process the message.

H.6.5 Cause No. 100 "conditional IE error"

This cause indicates that the equipment sending this cause has received a message with
conditional IE errors (see subclause 8.7.2).

H.6.6 Cause No. 101 "message not compatible with protocol state"
This cause indicates that a message has been received which is incompatible with the protocol
state or that a STATUS message has been received indicating an incompatible call state.

H.6.7 Cause No. 102 "recovery on timer expiry"

This cause indicates that a procedure has been initiated by the expiry of a timer in association
with 3GPP TS 24.008 error handling procedures.

H.6.8 Cause No. 111 "protocol error, unspecified"

This cause is used to report a protocol error event only when no other cause in the protocol error
class applies.

H.7 Interworking class

H.7.1 Cause No. 127 "interworking, unspecified"
This cause indicates that there has been interworking with a network which does not provide
causes for actions it takes; thus, the precise cause for a message which is being sent cannot be
ascertained.

Reference:
Mobile radio interface Layer 3 specification(3GPP TS 24.008)

FAQ-Instability in PDP context activation with Direct Tunnel

Download

Document Properties
ID: SE0000547101 Author: 00724829
Information Troubleshooting
Quality Level: C
Type: Cases
Update Time: 2011-10-28 16:59:57 Views: 88
Instability in PDP context
Fault Type: Signaling Problem Keywords:
activation with Direct Tunnel
Permission
01Huawei Engineers Permission
Level:
Symptom: After we implement the direct tunnel we faced problem as we found
instability in the service as sometime get accept PDP context and
sometime reject PDP context and in rejection case , the SGSN send the
reject message to MS with cause :
00100110 cause:network-failure (38)
Alarm
null
Information:
Cause Analysis: we did User trace on SGSN and User trace on GGSN to know the reason of
reject PDP context it was " network-failure "
we did test many time but sometime PDP accepted and sometime PDP
rejected as per attached failure traces.
we checked our configuration , it was on the SGSN there was 2 IPs : 1st IP
for control plane
and 2nd IP for user plane for normal two tunnel to carry the roamer user
plane data ,
and on the RNC there are three IPs : 1st IP for control plane between
SGSN and RNC ,
2nd IP for user plane for normal two tunnel between SGSN and RNC and
3rd IP for user plane between RNC and GGSN.
the problem was in the two IPs that for User plane on the RNC between
SGSN for normal two tunnel
 and GGSN for Direct Tunnel as it was different it is solved after make only
one IP on RNC for user plane between RNC-SGSN adn RNC-GGSN ,
after this changes the service is ok and stable as per attached traces.
Handling We did some changes in our configuration for SGSN and RNC as below :
Process: On SGSN : there is two IP address 1st : for Iu control plane and 2nd for Iu
user plane between SGSN and RNC for normal two tunnel.
On GGSN : there is one IP address for user plane between RNC and GGSN
for Direct tunnel.
on RNC : there is two IPs : 1st for control plane between RNC and SGSN ,
2nd one for user plane between RNC-SGSN for normal two tunnel and
RNC-GGSN for direct tunnel.
Suggestions and
null
Summary:
Faliure trace.rar
Attachments:
succ trace.rar

PDP Activation Failure During AAA Switchover Due to Incorrect Setting of T3 and N3 on
GGSN
Download

Document Properties
ID: SE0000525685 Author: z00133448
Information
Troubleshooting Cases Quality Level: C
Type:
Update Time: 2011-06-16 14:25:13 Views: 21
Fault Type: Data Configuration Problem Keywords: t3 n3, active/standby AAA
Permission
02Huawei Partners Permission
Level:
Symptom: During the active/standby AAA switchover test in the acceptance test for the
GGSN V9R7C03SPC205 in an office in country R, both the active and standby
AAAs communicate with the GGSN normally. The first PDP activation fails
after the communication between the GGSN and the active AAA is interrupted,
but all subsequent PDP activations are successful. That is, the PDP activation
fails in the process of AAA switchover.
Alarm None
Information:
Cause 1. After the communication between the GGSN and the active AAA is
Analysis: interrupted, all PDP activations except for the first request are successful,
which indicates that traffic is transferred normally between the GGSN and the
standby AAA after the switchover and the Radius configuration is correct.
What is the reason for the first activation failure during the switch?
The configuration of the GGSN is as follows:
radius-server group test
radius-server accounting 10.78.95.38 port 1813 vpn Radius key huawei
radius-server accounting 10.78.95.37 port 1813 vpn Radius key huawei
secondary
radius-server retransmit 1 timeout 6 .
2. User trace and Gi interface trace are performed on the GGSN (see the
attachment). The user trace shows that the SGSN sends two Create PDP
Context Requests. The SGSN configuration is T3=7 and N3=1. When the
SGSN sends the first PDP activation request, the GGSN is still in
communication with the AAA and does not reply to the SGSN. After T3 and
N3 reach the threshold, the SGSN sends the request for the second time.
3. The GGSN returns two Create PDP Context Responses. The first Create
PDP Context Response is for rejection and the second is for response to
successful activation. Then the SGSN rejects the PDP activation request form
the MS after receiving the first rejection message from the GGSN and does not
reply to the MS after receiving the response for successful activation from the
GGSN because the PDP context is not available.
4. The possible cause is that the GGSN rejects the PDP activation request and
repeatedly processes the retransmission requests sent from the SGSN, but the
SGSN does not respond to the MS for the second time. Usually, the GGSN
does not reject any activation request from the SGSN or process the
retransmission message from the SGSN. The GGSN should reply to only the
first activation request. It is confirmed that the GGSN responds to the PDP
activation request from the SGSN based on the setting of T3 and N3. The
configuration of the GGSN is as follows:
access-view
t3-timer 1 n3-times 3
That is, if the SGSN resends the activation request after N3 and T3 reach the
threshold, the GGSN responds to the request as a new one sent from the MS. If
the SGSN resends the activation request before N3 and T3 reach the threshold,
the GGSN ignores the request and replies to only the first Create PDP context
Response. During the test, the GGSN configuration is T3=1 and N3=3 and the
SGSN configuration is T3=7 (7>1x3). Therefore, the GGSN considers the PDP
activation request received later as a different request with the same content.
To avoid conflict, the GGSN rejects the one received earlier and responded to
the one received later. However, the SGSN does not distinguish which request
is rejected but sends the activation failure response to the MS. After the alarm
for active AAA interruption is generated, the GGSN starts to communicate
with the standby AAA. The PDP activation request is no longer sent for the
 second time and all later activations are successful.
Handling Modify the setting of T3 and N3 of GGSN as follows:
Process: access-view
t3-timer 5 n3-times 3,
T3 of SGSN is set to 7 (7< 3x5). Then the GGSN ignores the PDP activation
request sent from the SGSN later and all PDP activations are successful.

Suggestions During office deployment, the interval and times for request resending between
and Summary: the GGSN and AAA must be taken into consideration for the setting of T3 and
N3 for the Gn interface between the SGSN and GGSN. These parameters will
significantly affect traffic transfer, especially if certain NEs fail, such as AAA
congestion.

Document Properties
ID: SE0000677986 Author: Bruno Felipe Cardoso
Information Troubleshooting Quality
C
Type: Cases Level:
Update Time: 2013-07-29 15:49:00 Views: 65
Transmission PDP Reject activation-rejected-
Fault Type: Keywords:
Problem unspecified SGSN USN Transmission
Permission
Warranty Users Permission
Level:
Symptom: The customer checking the counters extracted by analysis of the S-CDR could
see that after 2013/03/19
there are a lot of release calls on 2 SGSN (SGS02 and SGS03). This problem is
happening just on some regions.
The code cause 31 and code cause 38 started on 2013/03/19:

Alarm
None
Information:
Cause From 3GPP protocol 24008, the description of the code cause 31 and 38 are
Analysis: described below:
Unsuccessful PDP context activation initiated by the MS.
Upon receipt of an ACTIVATE PDP CONTEXT REQUEST message the
network may reject the MS initiated PDP context activation by sending an
ACTIVATE PDP CONTEXT REJECT message to the MS. The message shall
 contain a cause code that typically indicates one of the following causes:
# 8: Operator Determined Barring;
# 26: insufficient resources;
# 27: missing or unknown APN;
# 28: unknown PDP address or PDP type;
# 29: user authentication failed;
# 30: activation rejected by GGSN;
# 31: activation rejected, unspecified;
# 32: service option not supported;
# 33: requested service option not subscribed;
# 34: service option temporarily out of order;
# 35: NSAPI already used. The network shall not send this cause code (see
note 1); or
# 95 - 111: protocol errors.
#112: APN restriction value incompatible with active PDP context.

Cause value = 30 Activation rejected by GGSN

This cause code is used by the network to indicate that the requested
service was rejected by the GGSN.
Cause value = 38 Network failure
This cause code is used by the network to indicate that the PDP context
deactivation or the MBMS context deactivation is caused by an error situation
in the network.
Checking the user trace, after the PDP create, SGSN and RNC establish RAB,
then SGSN send message to SCP, and also get the response:

Then SGSN update the GTPUinformation, but the response is "gtpu-sm-cause-

update-rnc-path-failure":

Then the SGSN originate the reject and delete the PDP:

From the previous analyze, the test of trace route, it’s stop on IP 10.58.63.29.
So the problem is caused on the IP transmission.”
Handling It were identified the GTPU/GTPC GGSN IP and the RNC IP:
Process:

After that a ping test was performed between these 2 equipments:

A trace route test was performed to identify where the ping were been lost:

After the tests, the customer could ask to the transmission engineer check the
transmission.
The issue was solved and the root cause was transmission problem.