[j-nsp] MX80 bridge-domain QinQ question

[Jeff Wheeler]

On Wed, Sep 19, 2012 at 4:07 PM, Doug Hanks <dhanks at juniper.net> wrote:
> Use a SP-style IFL using 802.1ad for telco. Use a SP-style IFL using
> 802.1q for the EX4200. The BD will automatically pop and push tags for
> you.

Could you give an example?  I searched high and low in the KB and
elsewhere.  What I am doing now is below.  The physical interfaces
obviously have many other things connected and are setup with
flexible-vlan-tagging and encap flexible-ethernet-services.

interface ge-1/1/8.14281 {
  description "customer office via telco network";
  encapsulation vlan-bridge;
  vlan-tags outer 1428 inner 423;
  family bridge;
}
interface xe-0/0/3.423 {
  description "customer servers via EX4200";
  encapsulation vlan-bridge;
  vlan-id 423;
  family bridge;
}
bridge-domain vl423 {
  interface ge-1/1/8.14281;
  interface xe-0/0/3.423;
}

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.

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.

Thanks
--
Jeff S Wheeler <jsw at inconcepts.biz>
Sr Network Operator  /  Innovative Network Concepts