All: When you configure 'no-tunnel-services' under VPLS, does the router still steal bandwidth from the PFEs in various line cards to support VPLS? It seems to me it does. A "show interface" terse shows logical interfaces dedicated to VPLS. >From the PFE shell, these are ifls created for VPLS lsis:
####### ADPC2(TL-MX240-A vty)# show xeth-pic 0 PIC Information pic name : XETH(2/0) port count : 10 ifd count : 10 debug flags : 0x0 mac db instance id : 1 num of dest filters : 3 macdb isr invoke count : 1636 link isr invoke count : 21 periodic poll : TRUE mac poll : TRUE num vpls lsi ifls : 1 num mf entries : 0 separate l2-l3 scheduler : FALSE ############ Not the "num vpls lsi ifls." On a 40 port 10/100/1000 blade if we fully populate the 10 ports associated with this PFE, then adding VPLS ifls on top of that means we are effectively oversubscribing the PFE, correct? 2. In the MX solution guide there is an example where you can connect L2 instances with L3 instances using lt interfaces. You need to enable tunnel-services on the PIC to do this, and in that configuration you specify a "bandwidth" of 1G on the 40 port 10/100/1000 card. The documentation says this is a reservation. What does this mean? That traffic tied to tunnel services is guaranteed 1G of bandwidth on the PFE but can use more if available? Or does it mean tunnel-services traffic will be policed at 1G? 3. (a) If I use "no-tunnel-services" in VPLS and I also decided to connect an L2 instance to an L3 instance using an "lt" interface pair and (b) the VPLS lsi ifl happens to be on the same PFE as the "lt" interface pair, does that mean traffic could potentially hit the same PFE twice? Thanks! _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
