Hi Hung.

Please help to check the procedure & arrange onsite engineer for the requir=
ed log from Ericsson team.
If you need any support, please let me know.
Thank you.
BR//ChiBuiV
From: Kuldeep Dagar
Sent: Thursday, June 09, 2016 11:34 AM
To: Chi Bui V
Cc: Phuong Thai; Cong Nguyen T; Truong Minh Hung (minhhung@vnpt.vn); 'Dang=
Tran Phuong-DHUC-OMCKV2' (phuongdt@vinaphone.vn); Ritesh Shreevastav
Subject: RE: 2999422, Medium Access Unit Fault Alarm
Hi Chi,
We need below logs & traces for further analysis. Please help in fetching=
as it needs to be fetched in maintenance window.
Regards
Kuldeep Dagar
9958911304

From: Ritesh Shreevastav

Sent: Wednesday, June 08, 2016 11:48 PM
To: Kuldeep Dagar
Subject: FW: 2999422, Medium Access Unit Fault Alarm
Hi Kuldeep,
Pls see below request from Goutham (CPP).
Thanks
Ritesh
From: Goutham Yarlagadda
Sent: den 8 juni 2016 19:18
To: Ritesh Shreevastav <ritesh.shreevastav@ericsson.com<mailto:ritesh.shree=
vastav@ericsson.com>>
Subject: RE: 2999422, Medium Access Unit Fault Alarm
Hi Ritesh
when a link is established between node and an external device, a certain=
speed is set to communicate which we call default transmission capabilitie=
s(1000/100/10).
If the Auto-negotiation fails, Medium access unit fault alarm will be raise=
d.
Then communication is re triggered with reduced transmission capabilities(1=
0/100).
If the Auto-negotiation succeeds, then communication will be done at reduce=
d speed but still the alarm persists.
Restarting the board will re triggered the Auto-negotiation but this is =
not guaranteed as it is said that the driver saves the status of Auto-negot=

iation once done between node and external device.

If at all, Auto-negotiation is re triggered, alarm will be cleared if the=
Auto-negotiation succeeds with the default transmission capabilities.
>After upgrade,
(1) Node will restart.
(2) Auto-negotiation happens freshly with default transmission capabilities=
(10/10/1000) between node and external device.
(3) If (2) fails for some reason (faulty cable or network disturbance etc),=
we will try to auto-negotiate with reduced transmission capabilities(10/10=
0).
Hence, the auto-negotiation is succeeded(with reduced capabilities) at spee=
d 100 in TO state.
> As long as the link exists, there won't be any effect with alarm on traff=
ic.
> If your traffic is O&M, there won't be any problem even if the speed is=
10Mbps.
Could you please help us in collecting logs for the below scenario
please enable the following traces
lhsh
lhsh
lhsh
lhsh

000500
000500
002400
002400

te
te
te
te

enable
enable
enable
enable

rec_sig
rec_sig
rec_sig
rec_sig

Osa_EthLinkFro_proc
Osa_EthMauFro_proc
Osa_EthLinkFro_proc
Osa_EthMauFro_pro

Step #1 Please provide the remote end ( where boards in MS-05 and MS-24 =
are connected via cable directly ) capabilities ( Speed,duplex )
Step #2 Execute following commands on both MS-24 and MS-05 boards
$
$
$
$
$
$
$
$
$
$
$
$
$
$
$

readclock
ethmode le0
pboot sh pa
ethmode le0
ethernet info lae0
ethernet phy lae0
ethernet stat lae0
dumpelg
te log read
llog -l
splitethstat read
splitethcdbg
splitethsdbg
get MediumAccessUnit
rld -a

Step #3 Remove the ethernet cable from MS-24.

Step #4 Remove the ethernet cable from MS-05 and insert to MS-24.
Collect the following commands output on MS-24: ( Non working condition =
)
$readclock
$ ethmode le0

$
$
$
$
$
$
$
$
$
$
$
$
$

pboot sh pa
ethmode le0
ethernet info lae0
ethernet phy lae0
ethernet stat lae0
dumpelg
te log read
llog -l
splitethstat read
splitethcdbg
splitethsdbg
get MediumAccessUnit
rld -a

Step #5 Remove the ethernet cable from MS-24 and insert to MS-05.
Collect the following commands output on MS-05: ( Working condition )
$readclock
$ ethmode le0
$ pboot sh pa
$ ethmode le0
$ ethernet info lae0
$ ethernet phy lae0
$ ethernet stat lae0
$ dumpelg
$ te log read
$ llog -l
$ splitethstat read
$ splitethcdbg
$ splitethsdbg
$ get MediumAccessUnit
$ rld -a
Step #6 Re-insert the ethernet cable for MS-24.
Collect the following commands output on MS-24: ( Non working condition =
)
$readclock
$ ethmode le0
$ pboot sh pa
$ ethmode le0
$ ethernet info lae0
$ ethernet phy lae0
$ ethernet stat lae0
$ dumpelg
$ te log read
$ llog -l
$ splitethstat read
$ splitethcdbg
$ splitethsdbg
$ get MediumAccessUnit
$ rld -a
Regards
Goutham Y
From: Ritesh Shreevastav

Sent: Wednesday, June 08, 2016 1:26 PM

To: Goutham Yarlagadda <goutham.yarlagadda@ericsson.com<mailto:goutham.yarl=
agadda@ericsson.com>>
Subject: FW: 2999422, Medium Access Unit Fault Alarm
Thanks Goutham=85
From: Kuldeep Dagar
Sent: den 8 juni 2016 11:49
To: Ritesh Shreevastav <ritesh.shreevastav@ericsson.com<mailto:ritesh.shree=
vastav@ericsson.com>>
Subject: 2999422, Medium Access Unit Fault Alarm
Hi Ritesh,
I suppose you are handling CSR 2999422. Please find the problem at a glance=
.
Alarm =93Medium Access unit fault=94 was raised after sw update from 15.0.0=
.2 to 15.0.0.11.
Customer have tried to test the cable from APP to router by unplug the conn=
ector in APP & connect to the switch, the port was up with 1G. So we can=
say that the connection from APP to router is OK
Other things tried:
-

Restart the board (MS, Slot 24).

Replace the GPB75 board (MS, slot 24).

Restart JVM

Restart the node.

Exchange the cables from C1 slot 5 to C1 slot 24

Logs attached.
Regards
Kuldeep Dagar
9958911304