[AusNOG] Juniper SRX and VPLS

[Tom Storey]

Hi Matt,

I did try this, specifying a list of VLAN ID's for a single unit but
that didnt work. :-(

FWIW I set up Wireshark to monitor what was flowing between two of the
Junipers (thank f**k for Wireshark :-D) and I can actually see that
the VLAN ID's are maintained within MPLS as I'd like them to be. It
just seems that for what ever reason when I try to configure a second
logical unit in to the routing-instance the first one stops working,
but the second one never works either.

If it joined them all together in to one big broadcast domain I could
understand that. Its the fact it stops working that is confusing and
frustrating. And as soon as you remove one of the logical units from
the routing-instance the remaining one will start working fine.

On 6 February 2014 19:50, Matt Ayre <matt.ayre at bigair.net.au> wrote:
> Hi Tom,
>
> As you have alluded, multiple VLAN interfaces inside the VPLS adds them to a
> single broadcast domain allowing flooding between them and is not desirable.
>
> I see "vlan-id-list" available and pass syntax check on SRX220, that may
> solve your issue;
>
> http://www.juniper.net/techpubs/en_US/junos12.2/topics/reference/configuration-statement/vlan-id-list-edit-interfaces-vpls.html
>
> Cheers,
> Matt
>
> On 07/02/2014 4:46 AM, "Tom Storey" <tom at snnap.net> wrote:
>>
>> Thought I might try my luck here as Im running out of places to ask
>> about this. :-)
>>
>> But Im looking for anyone who has implemented VPLS using SRX hardware
>> (240 and lower) and perhaps anyone that has implemented it in a semi
>> specific way, that being multiple logical interfaces with different
>> VLAN IDs assigned in the same VPLS routing-instance.
>>
>> I seem to be hitting a road block in that one sub-int with VLAN works
>> perfectly fine, but as soon as you add a second with a different VLAN
>> it all falls in a heap.
>>
>> FWIW if I assign an entire interface to the routing-instance I can
>> trunk VLANs until the cows come home just fine, but Im looking for a
>> solution where I could have an aggregation interface hooked up to a
>> switch and pick and choose which interfaces go in to which VPLS or VRF
>> for example.
>>
>> Im not looking to merge the VLANs together to form one large broadcast
>> domain, but rather want to maintain the VLANs across the VPLS so I
>> can, in a way, "trunk" multiple VLANs in at any given site and pick
>> them out as required at other sites.
>>
>> Would appreciate contact from anyone who can help, Ive been through
>> probably just about every piece of sample configuration and
>> configuration guide I can find and just cant seem to find the answer.
>> At the moment I feel like Im going in circles.
>>
>> Thanks
>> Tom
>> _______________________________________________
>> AusNOG mailing list
>> AusNOG at lists.ausnog.net
>> http://lists.ausnog.net/mailman/listinfo/ausnog