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

OSN 1500 lost management caused by DCN not supporting load sharing mode LAG

Publication Date:  2012-07-25 Views:  69 Downloads:  0
Issue Description
Customer use S5348C switch to connect OSN1500 and OSN3500. After upgrade S5348C from V1R3 to V1R6, the OSN1500 lost management.
OSN  1500 version: V2R11C00SPC300
customer did test as below:
1.  S5348 V100R006C00SPC800 + V100R006SPH003
Configuring LAG on OSN3500, and configuring Eth-trunk on S5348C
after rebooting device, find OSN1500 lost management.


2.  S5348 V100R006C00SPC800 + V100R006SPH003
customer used any one cable between OSN3500 and S5348C, OSN1500 was under management.,


3. S5348C V100R003C00SPC301 + V100R006SPH003
Configuring LAG on OSN3500, and configuring Eth-trunk on S5348
OSN1500 was under management






Alarm Information
none




Handling Process

solutions:
1.Both OSN 3500 and switch S5328 support master and slave mode LAG. change to master and slave mode on both sides to  fix this problem On this condition , service and DCN protocol all pass through the master port.
2.Use out-of-band  DCN, that is to say, use another fiber to connect  OSN3500 with switchS5328 for DCN communication.

 





Root Cause

1.The condition OSN will be under management is that the PPPOE protocol negotiate successfully, it contains  3 messages: pppoe hello、pppoe req、 pppoe ack, which need to be transmitted and received by both sides successfully
2.Before  switch upgrade, all the DCN  messages sent from OSN1500  pass through switch 1-1 to OSN 3500 slot15-5, the shaking hand process is successful. 
3.After switch upgrade, some arithmetic are optimized, switch S5328  transmit  DCN message from different port of LAG (0/1/2 and 0/1/1). from the captured packet, OSN 3500 received pppoe hello,  pppoe ack Message from slot15-5 and received pppoe req from slot4-2.


4.OSN can’t assemble the DCN message from these different ports.  So PPPOE protocol negotiated unsuccessfully, it caused OSN 1500 lose management







Suggestions
Current verison V2R11, platform didn't realize the load sharing  mode of DCN protocol for LAG, It is planed to add this function on  version V2R12C01.




END