Professional Documents
Culture Documents
PDP Activation Failures Further Suggestions PDF
PDP Activation Failures Further Suggestions PDF
1
"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.
Cause value
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
Cause
Non-existent
Invalid message format
IMSI not known
MS is GPRS Detached
MS is not GPRS Responding
MS Refuses
Version not supported
No resources available
Service not supported
Mandatory IE incorrect
Mandatory IE missing
Optional IE incorrect
System failure
Roaming restriction
P-TMSI Signature mismatch
GPRS connection suspended
Authentication failure
User authentication failed
Context not found
All dynamic PDP addresses are occupied
No memory is available
Relocation failure
Unknown mandatory extension header
Semantic error in the TFT operation
Syntactic error in the TFT operation
Semantic errors in packet filter(s)
Syntactic errors in packet filter(s)
Missing or unknown APN
Unknown PDP address or PDP type
PDP context without TFT already activated
APN access denied no subscription
APN Restriction type incompatibility withcurrently active PDP Contexts
MS MBMS Capabilities Insufficient
Invalid Correlation-ID
Cause value
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
81
95
96
97
98
99
100
101
111
112
Cause
LLC or SNDCP Failure
Insufficient Resources
Missing or Unknown APN
Unknown PDP Address or PDP Type
User Authentication Failed
Activation Rejected By GGSN
Activation Rejected, Unspecified
Service Option Not Supported
Requested Service Opt Not Subscribed
Service Opt Temporarily Out of Order
NSAPI Already Used
Regular Deactivation
QoS Not Accepted
Network Failure
Reactivation Required
Feature Not Supported
Semantic Error in TFT Operation
Syntactical Error in TFT Operation
Unknown PDP Context
Semantic Error in Packet Filter(s)
Syntactical Error inPacket Filter(s)
PDP Context Without TFT Already Activated
Invalid Transaction Identifier Value
Semantically Incorrect Message
Invalid Mandatory Information
Msg Type Non-existent/Non ImplementedState
Msg Type Not Compatible With Protocol State
IE Non-existent or Not Implemented
Conditional IE Error
Msg Not Compatible With Protocol State
Protocol Error, Unspecified
APN Restrict Value Incompatible Without PDP Context
!"
)* + + & !
!"
# $-!
!"
). //
!"
&' &(
!
#
$
+ + &!
+ +&
#
+ +&
0
123' !
+&
&+
&( &+ 5& 2 6 &
79' 00 & ** :;. <= >4
&(
!"
"4
0 0
!
7 +
//
&(
7 7
);
!"
"0 0
+&
!"
#
-0 0
0 0
,
,
+ +&
!
)= 6 $ #
!"
$
# $!
!"
!"
!"
!"
#
!
) 6 $ # 0 0
!"
#
$
# $!
0 0 "
$
0 0
"
)? 6
,
!"
# $
$
9: 2
%
!"
&
'@
'@
0 ( '@
0 ( '@
9 2
%
!"
9) &
!"
$#
+&
!"
0/+ (
99
&
,'-
!
*
9* &
&
,'-
"
*
9. ( &20
"!
"
!"
$
!"
"
-!
( &20
0 0
,
?=3 ?
!"
+&
0 0
+&
0 0
9;
+&
#
+ +&
0 0
9= A &
#
!"
+&
, +
0 0
9 ( #
$
!"
# A &
!"
!"
+&
# $
0 0
# $
!"
!"
+ +&
9?
0 0
*: B
!"
*
0 0
,
!"
+&
+ +&
B
!"
#
# $
"0 0
+&
+ &5
"0 0
0 0
*) "
B
!"
#
*9
/ $
# $
"0 0
+&
"
+ &5
"0 0
$ # 0 0
,
!"
# $
"0 0
,
B
0 0
+&
0 0
# $
!"
"0 0
,
**
$
0 0
14
$
!"
B
*. "
$
0 0
14
$
!"
B
, #
!"
+ &5
,
+&
B
#
"
,
"0 0
"
+&
+ &5
,
"
0 0
B
*= +
!
5
$
!
B )= : < : >- !
!"
'+ 0
1
* 2
%
!"
,
"0 0
14
"0 0
,
*; 0 0
14
+&
"0 0
+ +&
,
1
B 99=; < :=>- !
= *4 ,
!
*4
+/
+
$
+&
+
.: 0 0 " 0 *
"
!"
# $
"0 0 " 0 *
. 0 0 " 0 ;
"
!"
# $
"0 0 " 0 ;
0 (
"
0 (
"
.)
!
# $
0
!"
"
.;
#
0 (
+ &5
20(
,D- !
D.
&
?. &
,D- !
"
D ..
&
?;
,D- !
D;
&
?= +
,D- !
"
D ;)
&
? +
,D- !
D ;9
&
??
,D- !
D ;*
&
::
,D- !
&
: +
,D- !
"
5 ,
! #
5 ,
C
D ;.
! #
D ;;
0 0
0 0
#
!
9' 00 & )9 :;: <=*>- !
&
%
#
! #
#
) 20(
!"
"
# $
# $
"0 0
!"
#
"
#
.*
,
, 14
"
+ +&
0 0
, 14
,
$5
0
&
,D- !
D;
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 ITUT 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.
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)
Signaling Problem
Author:
00724829
Quality Level: C
Views:
Keywords:
88
Instability in PDP context
activation with Direct Tunnel
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
Handling
Process:
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.
We did some changes in our configuration for SGSN and RNC as below :
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
Handling
Process:
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:
65
Update Time: 2013-07-29 15:49:00 Views:
Transmission
PDP Reject activation-rejectedFault 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
Information:
Cause
Analysis:
None
From 3GPP protocol 24008, the description of the code cause 31 and 38 are
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-causeupdate-rnc-path-failure":
Then the SGSN originate the reject and delete the PDP:
Handling
Process:
From the previous analyze, the test of trace route, its stop on IP 10.58.63.29.
So the problem is caused on the IP transmission.
It were identified the GTPU/GTPC GGSN IP and the RNC IP:
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.