<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic RE: Load-balance problem using VPLS as transport in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40312#M9077</link>
    <description>In our lab test we have one LDP LSP for VPLS. It goes from X460-2 to X460-1. It does not go through sharing group 21 to customer equipment.&lt;BR /&gt;
&lt;BR /&gt;
X460-1.1 # sho mpls ldp lsp  Prefix            Adv Label Peer Label Next Hop        VLAN            &lt;BR /&gt;
10.0.0.1/32        0x00434   --         --              LB1              &lt;BR /&gt;
10.0.0.2/32        --        0x00434    172.22.0.2      VLAN_12</description>
    <pubDate>Wed, 09 Nov 2016 20:25:00 GMT</pubDate>
    <dc:creator>Anatoly_Machekh</dc:creator>
    <dc:date>2016-11-09T20:25:00Z</dc:date>
    <item>
      <title>Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40308#M9073</link>
      <description>Hi, everyone!&lt;BR /&gt;
&lt;BR /&gt;
Here is lab network to test balancing on client ports on Extreme Network switches (X460 in lab, but we have the same problem with X670-G2 in production).&lt;BR /&gt;
We are interested in sharing group 21 (ports 21, 22) on X460-1.&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="2f487b932e024cbe879972cd1d20e258_RackMultipart20161109-42592-dm8hxq-Ex460_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/1630iFADE39A223DCD949/image-size/large?v=v2&amp;amp;px=999" role="button" title="2f487b932e024cbe879972cd1d20e258_RackMultipart20161109-42592-dm8hxq-Ex460_inline.png" alt="2f487b932e024cbe879972cd1d20e258_RackMultipart20161109-42592-dm8hxq-Ex460_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
From Agilent (IP tester) IP traffic goes to Lab-M01 to 18 different VRFs (1001-1009 and 2001-2009). Lab-M01 sends out traffic in VRF 1001 through 1009 with one MPLS label, in VRF 2001 through 2009 with two MPLS labels. When we configure X460-1 and X460-2 as simple L2 switches with one vlan from sharing group 21 on X460-1 to sharing group 21 on X460-2, then balancing works. &lt;BR /&gt;
&lt;BR /&gt;
1 MPLS label:&lt;BR /&gt;
&lt;BR /&gt;
X460-1.8 # sh port 21,22,28 utilization packets &lt;BR /&gt;
Port     Link    Rx              Peak Rx          Tx               Peak Tx&lt;BR /&gt;
         State   pkts/sec        pkts/sec         pkts/sec         pkts/sec&lt;BR /&gt;
================================================================================&lt;BR /&gt;
21        A             0              1             6632            8034&lt;BR /&gt;
22        A             0              0            13238           16037&lt;BR /&gt;
28        A         19857          23909                0               1&lt;BR /&gt;
================================================================================&lt;BR /&gt;
2 MPLS labels:&lt;BR /&gt;
&lt;BR /&gt;
X460-1.10 # sh port 21,22,28 utilization packets &lt;BR /&gt;
Port     Link    Rx              Peak Rx          Tx               Peak Tx&lt;BR /&gt;
         State   pkts/sec        pkts/sec         pkts/sec         pkts/sec&lt;BR /&gt;
================================================================================&lt;BR /&gt;
21        A             2              3             8725           10678&lt;BR /&gt;
22        A             0              1            13118           13208&lt;BR /&gt;
28        A         23657          23731                3               3&lt;BR /&gt;
================================================================================&lt;BR /&gt;
The problem is that when we configure VPLS on X460-1 and X460-2 to pass the same traffic balancing stops working. All traffic goes to one port (either 21 or 22 depending...). &lt;BR /&gt;
What can we do to make balancing work with VPLS?&lt;BR /&gt;
&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Anatoly&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Nov 2016 19:46:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40308#M9073</guid>
      <dc:creator>Anatoly_Machekh</dc:creator>
      <dc:date>2016-11-09T19:46:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40309#M9074</link>
      <description>This is a LAG, correct? What config is on it (algo, hashing)? I'd recommend custom there. If not good enough, since 15.4 we have a feature - LSP Load Sharing - (for VPLS and RSVP-TE) to distribute the traffic more efficiently, using more LSPs (p.1123 of 22.1 User Guide).&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Nov 2016 20:02:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40309#M9074</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2016-11-09T20:02:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40310#M9075</link>
      <description>Here is information on X460:&lt;BR /&gt;
X460-1.1 # sh conf | i sharing enable sharing 21 grouping 21-22 algorithm address-based custom lacp&lt;BR /&gt;
X460-1.2 # sho sharing&lt;BR /&gt;
Load Sharing Monitor&lt;BR /&gt;
Config    Current Agg     Min    Ld Share  Flags Ld Share  Agg Link  Link Up&lt;BR /&gt;
Master    Master  Control Active Algorithm       Group     Mbr State Transitions&lt;BR /&gt;
================================================================================&lt;BR /&gt;
    21     21     LACP       1    custom    A     21        Y     A       2&lt;BR /&gt;
                                  custom          22        Y     A       0&lt;BR /&gt;
================================================================================&lt;BR /&gt;
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback&lt;BR /&gt;
Minimum Active: (&amp;lt;) Group is down. # active links less than configured minimum&lt;BR /&gt;
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based&lt;BR /&gt;
                        (L3_L4) Layer 3 address and Layer 4 port based&lt;BR /&gt;
                        (custom) User-selected address-based configuration&lt;BR /&gt;
Custom Algorithm Configuration: ipv4 L3-and-L4, xor&lt;BR /&gt;
Distribution Mode Flags:&lt;BR /&gt;
        A - All: Distribute to all members&lt;BR /&gt;
        L - Local Slot: Distribute to members local to ingress slot&lt;BR /&gt;
        P - Port Lists: Distribute to per-slot configurable subset of members&lt;BR /&gt;
Number of load sharing trunks: 1&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Nov 2016 20:08:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40310#M9075</guid>
      <dc:creator>Anatoly_Machekh</dc:creator>
      <dc:date>2016-11-09T20:08:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40311#M9076</link>
      <description>Then configure LSP load sharing.&lt;BR /&gt;</description>
      <pubDate>Wed, 09 Nov 2016 20:19:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40311#M9076</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2016-11-09T20:19:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40312#M9077</link>
      <description>In our lab test we have one LDP LSP for VPLS. It goes from X460-2 to X460-1. It does not go through sharing group 21 to customer equipment.&lt;BR /&gt;
&lt;BR /&gt;
X460-1.1 # sho mpls ldp lsp  Prefix            Adv Label Peer Label Next Hop        VLAN            &lt;BR /&gt;
10.0.0.1/32        0x00434   --         --              LB1              &lt;BR /&gt;
10.0.0.2/32        --        0x00434    172.22.0.2      VLAN_12</description>
      <pubDate>Wed, 09 Nov 2016 20:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40312#M9077</guid>
      <dc:creator>Anatoly_Machekh</dc:creator>
      <dc:date>2016-11-09T20:25:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40313#M9078</link>
      <description>Hi Anatoly, &lt;BR /&gt;
we had discussion within service case but this is just to share with community.&lt;BR /&gt;
&lt;BR /&gt;
 As Stephane said we can utilize LSP load sharing feature. Here are examples from my lab:&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Test 1&lt;/B&gt;&lt;BR /&gt;
Description: single VPLS tunnel without LSP load sharing&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-46943-dxlv6b-fig1_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/3461i3B85E6133DF5A694/image-size/large?v=v2&amp;amp;px=999" role="button" title="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-46943-dxlv6b-fig1_inline.png" alt="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-46943-dxlv6b-fig1_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
Sharing algorithm cannot distribute packets across sharing group member ports because packet headers are almost the same.&lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Test 2&lt;/B&gt;&lt;BR /&gt;
Description: single VPLS tunnel with LSP load sharing&lt;BR /&gt;
&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-14873-10oy7gf-fig2_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/1111iC240C3AC6D985463/image-size/large?v=v2&amp;amp;px=999" role="button" title="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-14873-10oy7gf-fig2_inline.png" alt="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-14873-10oy7gf-fig2_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
In this case packets from test-flows are shared between several LSPs and it makes MPLS labels to be different for the different packets from the same VPLS tunnel:&lt;BR /&gt;
X670G2-48X[L5:U32].14 # show mpls statistics l2vpn &lt;BR /&gt;
&lt;BR /&gt;
L2VPN Name&lt;BR /&gt;
  Peer IP/LSP    Flags            RxPackets              RxBytes            TxPackets              TxBytes&lt;BR /&gt;
----------------------------------------------------------------------------------------------------------&lt;BR /&gt;
VPLS_VPN       &lt;BR /&gt;
  10.0.0.35          U                 2920               227552             15099705           1298574028&lt;BR /&gt;
    LSP1             +                  360                28720              1886864            162270218&lt;BR /&gt;
    LSP2             +                  370                29760              1885514            162153946&lt;BR /&gt;
    LSP3             +                  342                28200              1885072            162116106&lt;BR /&gt;
    LSP4             +                  350                28562              1888660            162424674&lt;BR /&gt;
    LSP5             +                  381                27602              1887981            162366366&lt;BR /&gt;
    LSP6             +                  372                28002              1887950            162363700&lt;BR /&gt;
    LSP7             +                  375                27200              1888686            162426910&lt;BR /&gt;
    LSP8             +                  370                29506              1888978            162452108&lt;BR /&gt;
Here is configuration example for this setup:&lt;BR /&gt;
# # Module mpls configuration. # configure mpls add vlan "lo0" enable mpls vlan "lo0" enable mpls rsvp-te vlan "lo0" enable mpls ldp vlan "lo0" configure mpls add vlan "v3233" enable mpls vlan "v3233" enable mpls rsvp-te vlan "v3233" enable mpls ldp vlan "v3233" create mpls rsvp-te path "lsp-path" create mpls rsvp-te lsp "LSP1" destination 10.0.0.35 create mpls rsvp-te lsp "LSP2" destination 10.0.0.35 create mpls rsvp-te lsp "LSP3" destination 10.0.0.35 create mpls rsvp-te lsp "LSP4" destination 10.0.0.35 create mpls rsvp-te lsp "LSP5" destination 10.0.0.35 create mpls rsvp-te lsp "LSP6" destination 10.0.0.35 create mpls rsvp-te lsp "LSP7" destination 10.0.0.35 create mpls rsvp-te lsp "LSP8" destination 10.0.0.35 configure mpls rsvp-te lsp "LSP1" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP2" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP3" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP4" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP5" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP6" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP7" add path "lsp-path" primary configure mpls rsvp-te lsp "LSP8" add path "lsp-path" primary configure mpls lsr-id 10.0.0.32 enable mpls protocol ldp enable mpls protocol rsvp-te enable mpls create l2vpn vpls VPLS_VPN fec-id-type pseudo-wire 111 configure l2vpn vpls VPLS_VPN add service vlan v1000 &lt;B&gt;enable l2vpn sharing&lt;/B&gt; configure l2vpn vpls VPLS_VPN add peer 10.0.0.35 core full-mesh &lt;B&gt;configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP1 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP2 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP3 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP4 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP5 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP6 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP7 configure l2vpn vpls VPLS_VPN peer 10.0.0.35 add mpls lsp LSP8&lt;/B&gt; As you can see traffic can be well distributed across links when sharing algorithm can get packets with different MPLS labels.&lt;B&gt;&lt;BR /&gt;
&lt;BR /&gt;
Test 3&lt;/B&gt;&lt;BR /&gt;
Description: single LSP and multiply source ports involved in sharing&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-36309-14ppdoh-fig3_inline.png"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/3558iE75683152E7EC51C/image-size/large?v=v2&amp;amp;px=999" role="button" title="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-36309-14ppdoh-fig3_inline.png" alt="8d02590771b8484e9d16d72f2e8321e2_RackMultipart20161209-36309-14ppdoh-fig3_inline.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
In this example sharing algorithm can use information about source ports to better distribute traffic across ports in sharing group.</description>
      <pubDate>Wed, 09 Nov 2016 20:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40313#M9078</guid>
      <dc:creator>Korsovsky__Kons</dc:creator>
      <dc:date>2016-11-09T20:25:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40314#M9079</link>
      <description>Please, I followed the instructions above but didn't have success. Is it possible you check my configuration bellow?:&lt;BR /&gt;
&lt;BR /&gt;
Topollogy:&lt;BR /&gt;
&lt;P class="fancybox-image"&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="74fbe67cc19e48e58b4ce9fbb519ac29_77c15d6f-69ab-4db4-8c24-820fc117e4e8.jpg"&gt;&lt;img src="https://community.extremenetworks.com/t5/image/serverpage/image-id/574i7A337CD8D7565CA8/image-size/large?v=v2&amp;amp;px=999" role="button" title="74fbe67cc19e48e58b4ce9fbb519ac29_77c15d6f-69ab-4db4-8c24-820fc117e4e8.jpg" alt="74fbe67cc19e48e58b4ce9fbb519ac29_77c15d6f-69ab-4db4-8c24-820fc117e4e8.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;BR /&gt;
&lt;BR /&gt;
Router 1:&lt;BR /&gt;
ATG_TESTE.19 # sh conf&lt;BR /&gt;
#&lt;BR /&gt;
# Module devmgr configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure snmp sysName "ATG_TESTE"&lt;BR /&gt;
configure snmp sysContact "support@extremenetworks.com, +1 888 257 3000"&lt;BR /&gt;
configure sys-recovery-level switch reset&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module vlan configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure vlan default delete ports all&lt;BR /&gt;
configure vr VR-Default delete ports 1-64&lt;BR /&gt;
configure vr VR-Default add ports 1-64&lt;BR /&gt;
configure vlan default delete ports 1-64&lt;BR /&gt;
configure jumbo-frame-size size 9198&lt;BR /&gt;
configure sharing address-based custom hash-algorithm crc-32 lower&lt;BR /&gt;
create vlan "L3_ATG_SFO"&lt;BR /&gt;
configure vlan L3_ATG_SFO tag 50&lt;BR /&gt;
create vlan "LPBK_MPLS"&lt;BR /&gt;
configure vlan LPBK_MPLS tag 147&lt;BR /&gt;
enable loopback-mode vlan LPBK_MPLS&lt;BR /&gt;
create vlan "MPLS_balance"&lt;BR /&gt;
configure vlan MPLS_balance tag 77&lt;BR /&gt;
enable jumbo-frame ports 1&lt;BR /&gt;
configure ports 1 display-string 1.MPLS_in&lt;BR /&gt;
configure ports 1 auto on speed 1000&lt;BR /&gt;
enable jumbo-frame ports 47&lt;BR /&gt;
configure ports 47 display-string 47.MPLS_ATG_SFO&lt;BR /&gt;
configure ports 47 auto off speed 1000 duplex full&lt;BR /&gt;
enable jumbo-frame ports 48&lt;BR /&gt;
configure ports 48 display-string 48.MPLS_ATG_SFO&lt;BR /&gt;
configure ports 48 auto off speed 1000 duplex full&lt;BR /&gt;
enable sharing 47 grouping 47-48 algorithm address-based custom lacp&lt;BR /&gt;
configure vlan L3_ATG_SFO add ports 47 untagged&lt;BR /&gt;
configure vlan MPLS_balance add ports 47 tagged&lt;BR /&gt;
configure vlan MPLS_balance add ports 1 untagged&lt;BR /&gt;
configure vlan Mgmt ipaddress 20.2.2.200 255.255.0.0&lt;BR /&gt;
configure vlan MPLS_balance ipaddress 10.10.10.200 255.255.255.0&lt;BR /&gt;
configure vlan L3_ATG_SFO ipaddress 31.0.23.1 255.255.255.252&lt;BR /&gt;
enable ipforwarding vlan L3_ATG_SFO&lt;BR /&gt;
configure vlan LPBK_MPLS ipaddress 21.41.47.1 255.255.255.255&lt;BR /&gt;
enable ipforwarding vlan LPBK_MPLS&lt;BR /&gt;
configure ip-mtu 1550 vlan LPBK_MPLS&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module rtmgr configuration.&lt;BR /&gt;
#&lt;BR /&gt;
enable iproute sharing vr VR-Default&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module mcmgr configuration.&lt;BR /&gt;
#&lt;BR /&gt;
disable igmp snooping vlan "L3_ATG_SFO"&lt;BR /&gt;
disable igmp snooping vlan "MPLS_balance"&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module mpls configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure mpls add vlan "L3_ATG_SFO"&lt;BR /&gt;
enable mpls vlan "L3_ATG_SFO"&lt;BR /&gt;
enable mpls rsvp-te vlan "L3_ATG_SFO"&lt;BR /&gt;
enable mpls ldp vlan "L3_ATG_SFO"&lt;BR /&gt;
configure mpls add vlan "LPBK_MPLS"&lt;BR /&gt;
enable mpls rsvp-te vlan "LPBK_MPLS"&lt;BR /&gt;
enable mpls ldp vlan "LPBK_MPLS"&lt;BR /&gt;
enable mpls php vlan "LPBK_MPLS"&lt;BR /&gt;
create mpls rsvp-te path "path-link"&lt;BR /&gt;
configure mpls rsvp-te path path-link add ero include 31.0.23.2/32 strict order 10&lt;BR /&gt;
create mpls rsvp-te lsp "lsp1" destination 21.41.23.1&lt;BR /&gt;
create mpls rsvp-te lsp "lsp2" destination 21.41.23.1&lt;BR /&gt;
create mpls rsvp-te lsp "lsp3" destination 21.41.23.1&lt;BR /&gt;
create mpls rsvp-te lsp "lsp4" destination 21.41.23.1&lt;BR /&gt;
configure mpls rsvp-te lsp "lsp1" add path "path-link" primary&lt;BR /&gt;
configure mpls rsvp-te lsp "lsp2" add path "path-link" primary&lt;BR /&gt;
configure mpls rsvp-te lsp "lsp3" add path "path-link" primary&lt;BR /&gt;
configure mpls rsvp-te lsp "lsp4" add path "path-link" primary&lt;BR /&gt;
configure mpls lsr-id 21.41.47.1&lt;BR /&gt;
enable mpls protocol ldp&lt;BR /&gt;
enable mpls protocol rsvp-te&lt;BR /&gt;
enable mpls&lt;BR /&gt;
create l2vpn vpls vpls-v77 fec-id-type pseudo-wire 77&lt;BR /&gt;
configure l2vpn vpls vpls-v77 add service vlan MPLS_balance&lt;BR /&gt;
configure l2vpn vpls vpls-v77 mtu 9198&lt;BR /&gt;
enable l2vpn sharing&lt;BR /&gt;
configure l2vpn vpls vpls-v77 add peer 21.41.23.1 core full-mesh&lt;BR /&gt;
configure l2vpn vpls vpls-v77 peer 21.41.23.1 add mpls lsp lsp1&lt;BR /&gt;
configure l2vpn vpls vpls-v77 peer 21.41.23.1 add mpls lsp lsp2&lt;BR /&gt;
configure l2vpn vpls vpls-v77 peer 21.41.23.1 add mpls lsp lsp3&lt;BR /&gt;
configure l2vpn vpls vpls-v77 peer 21.41.23.1 add mpls lsp lsp4&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module ospf configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure ospf routerid 21.41.47.1&lt;BR /&gt;
enable ospf mpls-next-hop&lt;BR /&gt;
enable ospf&lt;BR /&gt;
create ospf area 0.0.0.40&lt;BR /&gt;
configure ospf add vlan L3_ATG_SFO area 0.0.0.40 link-type point-to-point&lt;BR /&gt;
configure ospf vlan L3_ATG_SFO cost 20&lt;BR /&gt;
configure ospf vlan L3_ATG_SFO priority 0&lt;BR /&gt;
configure ospf add vlan LPBK_MPLS area 0.0.0.40&lt;BR /&gt;
configure ospf vlan LPBK_MPLS priority 0&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module ospfv3 configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure ospfv3 spf-hold-time 10&lt;BR /&gt;
&lt;BR /&gt;
#&lt;BR /&gt;
# Module thttpd configuration.&lt;BR /&gt;
#&lt;BR /&gt;
configure ssl certificate hash-algorithm sha512&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
Router 2 (the similar to the first)</description>
      <pubDate>Mon, 29 Jul 2019 22:29:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40314#M9079</guid>
      <dc:creator>Renato_Santos1</dc:creator>
      <dc:date>2019-07-29T22:29:00Z</dc:date>
    </item>
    <item>
      <title>RE: Load-balance problem using VPLS as transport</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40315#M9080</link>
      <description>In the example that Korsovsky, Konstantin did, how kind of sharing was used?&lt;BR /&gt;
&lt;BR /&gt;
L2 or L3_L4 or port??</description>
      <pubDate>Thu, 01 Aug 2019 23:26:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/load-balance-problem-using-vpls-as-transport/m-p/40315#M9080</guid>
      <dc:creator>Renato_Santos1</dc:creator>
      <dc:date>2019-08-01T23:26:00Z</dc:date>
    </item>
  </channel>
</rss>

