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>


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


FAQ-Lag configuration rules in N+0 links

Publication Date:  2012-07-25 Views:  92 Downloads:  0
Issue Description
Lag configured on the 4+0 links, when configure the “manual” “sharing” there is part of the planned IP can pass the link, after the Lag attribute change to “Static” “sharing”, all the service OK;

Alarm Information
There are LOF alarms on link BLDP048-BLDP051;

Handling Process
After Lag attribute change from the Manual to static all service OK;

Root Cause
4+0 means 4 tunnel working on link BLDP048-BLDP051, when LOF alarm happened on one of the tunnel, the service not switch from the broken to the rest 3 tunnel because the Lag attribute is Manual;

About N+ 0 configuration (take 4+0 as example):
Solution A:  Manual/sharing – No suggested:
When 1 channel invalidation service cannot switch other channels because the LACP protocol not runs;
Solution B: Static/sharing – run LACP protocol;
Solution C: Configure to 3+1 configuration: the actual working tunnel is 4   - suggested;
Notes: N+1 configuration principle is Lag with attribute: “Manual” “Sharing”; but switch induce by IF part.