Professional Documents
Culture Documents
"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
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.
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.
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
Reference:
Mobile radio interface Layer 3 specification(3GPP TS 24.008)
GPRS specific cause values for GPRS Session Management
)* + + & ! !
!" # $ + +& , #
% !" # $-! + + &! ! + +&
);
!" +& !" # $ 0 0 , -
"0 0 , -0 0 , - + +& ,
!
)= 6 $ #
!" # $ # % !"
, $ # $! #
!
) 6 $ # 0 0 0 0 "
!" # $ # % !"
, $ # $! 0 0 " !
)? 6
!" # $ # % !"
, $ # $
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
*; 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;
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.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.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.
Reference:
Mobile radio interface Layer 3 specification(3GPP TS 24.008)
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.
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:
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.