Routing

hi

having just read the juniper configuring Hierarchical VPLS I have a couple of questions:

1.  Is the example for this book given that fact that there are multiple CE units all in the same LAN/broadcast domain?

2.  If on the PE1 MTU-s unit I had another CE device connected how would I differentiate the traffic?

      something along the lines of:

      PE1 -> would need another l2circuit towards the PE3/PE5 nodes?

      PE5/PE3 -> would need another VPLS instance with a neighbor of PE1 and the correct circuit-ID?

3.  In this H-VPLS setup the vlan tag manipulation and CoS stuff is done on the MTU-s and the other nodes ssimply forward frames?

Attachment(s)

Configuring_Hierarchical_VPLS.pdf   545 KB 1 version

due to the over whelming response I had to this post, I will place the answers here for others:

1.  Is the example for this book given that fact that there are multiple CE units all in the same LAN/broadcast domain?

      yes, all the CPE devices are in the same LAN segment

2.  If on the PE1 MTU-s unit I had another CE device connected how would I differentiate the traffic?

      something along the lines of:

      PE1 -> would need another l2circuit towards the PE3/PE5 nodes?

      PE5/PE3 -> would need another VPLS instance with a neighbor of PE1 and the correct circuit-ID?

      so to setup another service independant of the first one:

      different l2circuit ID's on MTU-s

      different VPLS instance on the PE-rs nodes accepting those new l2circuit ID's.

3.  In this H-VPLS setup the vlan tag manipulation and CoS stuff is done on the MTU-s and the other nodes ssimply forward frames?

    Yes this is the normal way, the marking and manipulation is performed at the edge of the network.

One thing that I'm missing here is how to terminate multipe l2circuits from the same neighbor address into the VPLS instance.

Logically it appears simple that i can do this:

{master}[edit routing-instances]
Lab-1@PE-B# show
TESTv.ELAN {
    instance-type vpls;
    interface ge-0/0/0.101;
    vrf-target target:11427:8000;
    protocols {
        vpls {
            no-tunnel-services;
            site TEST {
                automatic-site-id;
            }
            vpls-id 2000;
            mtu 1950;
            mesh-group VC_10 {
                vpls-id 10;
                neighbor 10.0.0.3;    <--- note the same neighbor but different VC
            }
            mesh-group VC_11 {
                vpls-id 11;
                neighbor 10.0.0.3;   <--- note the same neighbor but different VC
            }
        }
    }
}
                    
{master}[edit routing-instances]
Lab-1@PE-B#

However when I come to commit this I get an error because I have the same neighbor in 2 differnet mesh-groups:

{master}[edit routing-instances]
Lab-1@PE-B# commit
re0:
[edit routing-instances TESTv.ELAN protocols vpls mesh-group VC_11]
  'neighbor 10.0.0.3'
    LDP-VPLS: Same neighbor 10.0.0.3 is configured in VC_10 mesh-group also
error: configuration check-out failed

{master}[edit routing-instances]
Lab-1@PE-B#

Why is this not allowed? it seams like it should be.

R./