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>

Reminder

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

upgrade

Due to reserved DCC bytes the transparent transmission cannot be configured

Publication Date:  2012-07-25 Views:  56 Downloads:  0
Issue Description

One day customer complained that they want to create transparent transmission on 5-N1SLD4 port no 1. They want to provide vendor S OAM via transparent transmission. According to them whenever they create transparent transmission following error appears “39125, Error Code: 39125” as shown in attached Figure 1. They reported the issue to Huawei Engineer for further investigation.

Alarm Information
No alarm.
Handling Process
After analyzing issue it was found that Error Code: 39125 shows that time slot is already occupied. So these D4-D12 bytes are already occupied although NMS is not showing this. For this following command was tried
:cm-get-dccphy;
ECC-PHY-INFO                                              
SRC-BID  SRC-PORT  SRC-BYTE      DST-BID  DST-PORT  DST-BYTE                      
5        1         D4            13       1         D4                            
5        1         D5            13       1         D5                            
5        1         D6            13       1         D6                            
5        1         D7            13       1         D7                            
5        1         D8            13       1         D8                            
5        1         D9            13       1         D9                            
5        1         D10           13       1         D10                           
5        1         D11           13       1         D11          
5        1         D12           13       1         D12                        
This shows that 1st port is configured with 13th slot board 1st port. But actually there was no board in 13th slot as shown below and therefore problem appeared as some one deleted the board improperly
:cfg-get-board; 
INSTALLED-BOARD                                  
                          BID   BD-TYPE       ACTIVE-STATE                         
                          5     ssn1sld4      active                               
                          8     ssn2sl64      active                               
                          9     ssn1uxcsb     active                               
                          10    ssn1uxcsb     active                               
                          11    ssn2sl64      active                               
                          14    ssn1sld4      active                               
                          17    gscc          active                               
                          18    gscc          active 
                          27    piu           active                               
                          28    piu           active                               
                          37    ssn1aux       active                               
                          38    ssn1fan       active                               
                          39    ssn1fan       active                               
                          40    ssn1fan       active    
After deleting DCC bytes as shown in attached command line the issue resolved and customer succeeded in configuring transparent transmission.
Root Cause
1-Checked whether DCC resources are enough for the assignment of the transparent transmission. There were enough idle number for 3-Byte rate and 9-Byte rate as shown in Figure 2. It means that this can’t be the problem.
2-Checked whether this is NMS problem. Then checked other boards of same NE for assignment of DCC bytes for transparent transmission. The results were successful so it means that this is not NMS issue.
3-Then checked the issues on board level as other boards were able to be configured successfully on NE,and tried to configure 2nd port of the same boards and results were successful and its behavior was normal. It means that this issue is with only 1st port. Even the port was not allowing configuring D4-D12 bytes of 1st port as shown in Figure 3. The same error appeared in this operation as well.
Suggestions
If you also face the same error in configuring transparent transmission then check first by :cm-get-dccphy; command output for relation. After deleting the DCC bytes from :cm-del-dccphy; the issue will be resolved. 

END