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.


Error Selection of Mapping Protocols Causing EPL Service Failure on EFGS

Publication Date:  2012-07-24 Views:  111 Downloads:  0

Issue Description

      Services configured on EPL are not through after being configured. In a metropolis network, the user configures EPL services on the EFS board in slot IU3 of No. 41 NE (155622H). The services flow through No.1 node in the central node and are accessed to the Internet through the EPLAN services. After the configuration, the services fail to work.

Alarm Information


Handling Process

1. Alarms in Node 41 and in Node 1 are normal;

2. Check whether the services are successfully configured through the command below.



3                1                             0                           0                                   5

The frame test feedbacks that no response frame is received at the local node. That is implication of error configured services.

3. Check the SDH service configuration. No abnormality is found. Check the interface attributes of the Ethernet boards, but no fault is found, either. The Ethernet service configuration is normal.

4. Configure the Ethernet services once again. In Node 41, of the internal port attributes of the EFS, the mapping protocol was LAPS, and the bit sequence of FCS was little endian. 5. In that metropolis network, all the Ethernet boards employ GFP protocols and big endian (bit sequence of FCS). In Node 41, the unsuccessful service configure is due to different protocols. Modify the protocol in Node 41, and the services runs normally.

Root Cause

The mapping protocol in Node 41 is mistakenly configured, causing service failure.