Huawei MA5600 Manual page 72

MSAN UA5000 Cases
Cause
VOD vlan was not configuered at 10G transmission equipment, becuase VOD vlan is bind with S
Analysis: TB, and for IPTV service we need to dial from STB for any user so if VOD vlan for said ONU w
as not created at 10G transmission equipment which is connected with uplink (BRAS).
Handling
I have checked all the configuration form ONU to 2.5G each and every thing was configuered ac
Process: cording to plan and there were no any alarm found in between, Finllay 10G service was remainin
g at our part to check when I checked the serivce for said ONU at 10G, I found VOD vlan for sai
d ONU was not created. Than I creat VOD vlan and checked service which was running normally
and issue is resolved.
Suggestions No
and summary:
4.8 Packet loss to UA5000. When occurring, the IPMB reports CPU occupancy at 73
Title:
Packet loss to UA5000. When occurring, the IPMB reports CPU occupancy at 73
ID: SE0000383242
Update time: 2009-04-17 15:29:58
Author: Chee Kong Lau
Integrated Acsess
Product
Family:
Fault Type: UA5000 Broadband Service
Keywords: UA5000 IPMB packet loss high cpu occupancy
Digest: UA5000 IPMB packet loss high cpu occupancy
Phenomenon Customer experienced severe packet loss to a UA5000 IPMB. A switch-over to the standby IPM
Description: B was performed, however the issue still existed. When looking at the CPU on the active IPMB,
the CPU utilization got quite high – up to 70+%. It normally would sit at 25%. When they ping th
e UA5000 from the local CX200, they got packet loss, also when they connected to the MSAN fr
om their office, their sessions often stall. Their customers were saying they were getting dropout
s too.
Alarm
When occurring, the IPMB reports CPU at 73% ALARM 41340 RECOVERY MAJOR 0x0e22
Information: 0000 PROCESS ERROR 2008-08-25 12:05:25
ALARM NAME : CPU occupancy recovery alarm
PARAMETERS : The current CPU occupancy is: 73%
DESCRIPTION : CPU occupancy returns to normal value
CAUSE
ADVICE
Cause 1. Telnet to affected UA5000. The cpu occupancy in slot 0/3 was sitting at 63% at one instance.
Analysis: Ping the vlanif IP from NMS has some packet loss. Telnet session got interrupted and need to rest
art.
The packet loss issue is intermittent. The disconnection experienced was due to the packet loss
– there maybe a period of up to 1 minute where the UA5000 will not reply to any pings.
2. There were some transmitted multicast frames and oversized frames on the uplink GE port 0/3
/0 and the frames seem to be rather high.
3. There is also a duplicated mac-address accosiated with slot 3 and slot 6. The duplicated mac-a
ddress is their BRAS mac-address.
4. If the BRAS mac-address has been learnt by the CPE port, this phenomena is not normal. It co
uld cause mac-addresses "drifting" and create network instability.
There are generally two conditions causing BRAS mac-address learnt by user CPE port: (1) Us
er attack. User CPE attempts to send "attacking" packets with the upper-layer BRAS, (2) There e
xists a "ring" or "loop" the customer network.
Handling 1. Modified the traffic-suppress mode for multicast and broadcast traffic on IPMB port 0/3/0 fro
Confidential Information of Huawei. No Spreading without Permission
: CPU occupancy returns to normal value
: No need to proceed"
Chapter 4 UA5000 Broadband Service
Product: UA5000
67