Hello,

Check in Node B the counters in the MO Aal2Ap

pmUnSuccInConnsLocalQosClassA
pmUnSuccInConnsLocalQosClassB
pmUnSuccInConnsLocalQosClassC
pmUnSuccInConnsLocalQosClassD
Check in RNC the counters in the MO Aal2Ap
pmUnSuccOutConnsLocalQosClassA
pmUnSuccOutConnsLocalQosClassB
pmUnSuccOutConnsLocalQosClassC
pmUnSuccOutConnsLocalQosClassD
A - CS + Signaling
B - PS R99
C - HS and EUL
D - Normally Not Used
All common channels and CS Speech, CS Data and CS Streaming services are recommended
to be configured with AAL2QoS class A.
Best Effort packet services on DCH for Interactive and Background are recommended to be
configured with AAL2QoS class B.
The high speed data services, EUL and HSDPA, are best effort services and are
recommended to be configured with AAL2QoS class C.
If you have some of them different than 0 you have a problem.
Note that each service consume CIDs from each Class but all B and C services
consume CIDs from Class A, because all of them uses Class A for signaling, that
explain you only see Class A congestion.
Normally this type of congestion will reduce you RAB CS and HSDPA accessibility
or just one of them and after adm fails.
1) Check if your problem is not related to the Iub bandwidth. Node -> pmr ->
IubDataStreams -> Check IubHsLimitingRatio, if you have 0 ok if not you can have
not sufficient bandwidth or a TX bottleneck problem.
If not...
2) If you are having this problem just in Class A try to reduce some Eul Users and
check by pmxh if the counters are reducing.
3) If you are having problems in Class A and C you will have to duplicate VCs,
when you duplicate VCs you gain more CIDs with the same bandwidth and can

solve this problem, after that if the problem continues a suggest you to change
this Iub for IP.

Normally you will just duplicate VCs for Class A and C, for B you can but is not
usual unless you have a high PS R99 traffic in your network.
When you have Iub ATM problems you can:
1) Temporally reduce Eul Users to reduce just Class A congestion or in some cases
block this service until VC expansion.
(This action will just take effect in Class A congestion and is just temporally)
2) Resquest 2nd VC expansion for Class A and C, B just if you have congestion or
high PS R99 traffic.
3) If the action above not bring effects you must change your Iub for IP with the
necessary bandwidth.
4) Check if your Iub bandwidth is enough.
I hope it can help you, give REP if useful...

4 E1's is not a problem, it doesn't matter. Your 4 E1's give you 8 Mbps bandwidth and the
question here is not bandwidth, but you can check it using another counters. The question
here is CID Utilization as our friend said. Eul uses 2 Class A CIDs + 1 Class C CID, then you
probably having problems in Class A and it is affecting signaling which affects all you NodeB and/or RNC counters and performance. The remedy for it is reduce some Eul Users or
disable Eul after that create a second VC por Class A and second VC por Class C, this way
you double the CID capacity with the same bandwidth. If you are having values different
from 0 in pmr -> IubDataStreams -> Check IubHsLimitingRatio (Normally in Spi03)
consider IUB change for IP or add more E1's, but is necessary create second VCs if
you choose add more E1's to avoid problems with CID usage.