No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


EFT8A Board reset cause service interruption as physical parameters not enabled automatically due to version mismatch

Publication Date:  2012-07-25 Views:  105 Downloads:  0

Issue Description

On one site customer complaint that one EFT8A board got faulty due to which the services goes offline, Customer also told that even after resetting the board the services are not recovered and no alarm observed on the ports of EFT8A board and external port status also enabled in Enable/Disable column.

Alarm Information


Handling Process

While dealing with etherner boards
1- Note the alalrms at every port and rectify first the alarms (Unused ports should be closed)
2-After checking all the alarms I have not seen any alarm on the board or port.
3- Check the configuration of the services (Boound path and SDH cross connection services)
4-Check all the parameters of the port by query the external port status (Physical parameters are also in the port parameters)
5- I found that rest all the things are ok and port is also in enable state but the Physical parameters (Port Physical Parameters) shown me that port is disabled.
6-After that I have also seen that NMS shows me port is at auto negociation mode (Port Physical Parameters) while we configure it at 1000 M fullduplex.
7- I have disable the port (Enable\Disable) from NMS and then again enable the port from NMS after that the port physical parameters also  shows me the right configuration and the state is also enable. And the issue is resolved.

Root Cause

After checking it was found that when I query the external port status from NMS the ports shown enable in the Enable\Disable column. But when I look in the "Port Physical Parameters" I found that port was shown disabled and also the negociation mode also turn to default whic is "Auto negosiation". But we set the negosiation mode to 100Mb full duplex. As from our side we enable the port at NMS so it shows us enabled but port was physically disabled and no alarm was observed on the ports.
So that's why the DSLAM's connected to all the ports were found down and customer decleared the EFT8 board hardware faulty.

After checkin the version of EFT8 board and the NE version the version does not match in the version matching table of V1R8C02SPC200 of OSN 3500 due to which even after reset the NE fails to enable the ports physically but the GSCC reports that EFT8 board ports are in enable state while physically ports are not enabled. After matching the version of the EFT8A board (7.54) with the required NE version V1R8C02SPC200 the issue is resolved.
The board version details are as follows

OSN 3500 (V1R8C02SPC200)
EFT8A            4.13     (Running Board version)

EFT8A            7.54     (Required Board Version)


Always use the version matching table before replacing or adding new ethernet boards (EFT8A,EFS or EGS) to avoid problems related to versions.
Before replacing any hardware engineer should check Throughly the alarms with parameters and also all the configurations on Ethernet boards and analyse the situation if found some abnormality then first remove that abnormality then see again if services are ok then no need to replace the hardware.
But hardware replacement should be the last choice.