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

Reminder

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

upgrade

Non-ASON NE line board receive null j0 byte when interface with ASON NE

Publication Date:  2019-07-08 Views:  97 Downloads:  0

Issue Description

One day, customer report that they can't get the tracing J0 byte rightly. 
The NE connect like this
NDR_1   2-4--------------------- VAS_1      11-1
NDR_1   17-4--------------------VAS_1     8-1
The board 2 and 17 of NDR can receive the right j0 byte
#9-5xxx[][2010-11-17 00:34:35+08:00]>
:cfg-get-rj0:2,4 
                                    RJ0                                           
                        Bid   Pid   J0MODE  J0VALUE                               
                        2     4              4       *VAS 11///1                           
  Total records :1   
#9-5xxx[][2010-11-17 00:34:54+08:00]>
:cfg-get-rj0:17,4 
                                    RJ0                                           
                        Bid   Pid   J0MODE  J0VALUE                               
                        17    4               4       *VAS 8.1                              
  Total records :1  
But the 8 and 11 of VAS_1 can't receive right j0 byte when set a special j0 
#9-5xxx[][2010-11-17 00:36:47+08:00]>
:cfg-get-rj0:8,1 
                                    RJ0                                           
                        Bid   Pid   J0MODE  J0VALUE                               
                        8           1     1                      *??
#9-5xxx[][2010-11-17 00:37:03+08:00]>
:cfg-get-rj0:11,1 
                                    RJ0                                           
                        Bid   Pid   J0MODE  J0VALUE                               
                        11    1     1       *                                     
  Total records :1   

Alarm Information

None

Handling Process

use the follow command to disable the TE_LINK verify
:sc-set-port-test:bid,pid,disable; (Disable the TEST message sending of this port)

Root Cause

Because when line board of ASON NE get online,  GSCC will report this event to ASON, ASON will enable j0 flag.  ASON NE will begin to TE_LINK verify, so the J0 
will be a fix value some time and 0 for the other time.
 when ASON NE connect with non-ASON NE, the TE_Link can't verify successfully, this time line board will keep sending the same j0 byte as which used in TE_link verify, so the non-ASON NE will receive the 0 j0 byte.

Suggestions

When some ASON NE boards connect to non-ASON NE, need to close the protocol verify according to the ASON beginning guide.

END