See inline.
On 9/19/12 4:09 PM, "Jeff Wheeler" <j...@inconcepts.biz> wrote:
>The above configuration works. Unfortunately, I must duplicate the
>above stanzas for each CVLAN. If I try to use vlan-id-list [ 423 424
>] on the EX4200-facing port, the IFL sees 0 packets. For example:
>
>interface xe-0/0/3.423 {
> description "customer servers via EX4200";
> encapsulation vlan-bridge;
> vlan-id-list [ 423 424 ];
> family bridge;
>}
>That commits but xe-0/0/3.423 never sees any packets arrive, and the
>BD never learns any MACs from it. Certainly it doesn't work as I
>thought it might.
That's because you defined a BD with a type of "default" which requires
that any IFL placed into that BD has to have all tags matching to be able
to bridge. If you wish to modify the tags, you have to use the
input-vlan-map and output-vlap-map to do so. Also keep in mind that the MX
will bridge on the C-TAG by default.
>Using interface-mode trunk and configuring a vlan-id-list in the BD is
>not possible, as far as I can understand, because I can't work out how
>to configure the telco-facing IFL to push/pop as needed to get the
>outer-tag on it. It seems I can't use input/output-vlan-mapping in
>concert with a BD configured with a vlan-id-list in order to utilize
>mode trunk.
You can't use ENT-style IFL (family bridge) configurations with a default
BD (no vlan definition)
You'll just need to define each CTAG as you have been doing.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
