[j-nsp] QinQ interface configuration question

[R S]

Hi
I'm wondering if under a QinQ interface configuration it's accepted by the MX the same SVLAN (outer vlan) or the commit will fail.

The PE QinQ interface prospect configuration scenarios are:

1) different SVLAN and CVLAN
2) different SVLAN and same CVLAN
3) same SVLAN and different CVLAN
4) same SVLAN and CVLAN

I'm sure 1) and 2) are accepted, not sure about 3) and 4).

Sorry but I've no lab device under my desk and any help is appreciated.

Regards


Example of scenario 4)

interfaces {
                     ge-3/3/1 {
                        description "*** QinQ interface  ***";
                        per-unit-scheduler;
                        flexible-vlan-tagging;
                        link-mode full-duplex;
                        encapsulation flexible-ethernet-services;
                        gigether-options {
                                   no-flow-control;
                                   no-auto-negotiation;
                                   ethernet-switch-profile {
                                               tag-protocol-id [ 0x8100 ];
                                              }
                        }
                        unit 1010 {
                                   description "*** customer 1 attached to routing instance of customer 1 ***";
                                   vlan-tags outer 0x88a8.1001 inner 0x8100.100;                        
                                   family inet {
                                        address 10.207.190.33/30;
                                   }
               unit 1011 {
                                   description "*** customer 2 attached to routing instance of customer 2 ***";
                                   vlan-tags outer 0x88a8.1001 inner 0x8100.100;                        
                                   family inet {
                                        address 10.207.190.33/30;
                                   }
                        }
            }
}
routing-instances {
            customer-1 {   
                        interface ge-3/3/1.1010;
                        protocols {
                                   bgp {
                                               group customer {
                                                               neighbor 10.207.190.34 {
                                                                       peer-as 65100;
                                                                       as-override;
                                                           }
                                               }
                                   }
                        }
    customer-2 {   
                        interface ge-3/3/1.1011;
                        protocols {
                                   bgp {
                                               group customer {
                                                               neighbor 10.207.190.34 {
                                                                       peer-as 65100;
                                                                       as-override;
                                                           }
                                               }
                                   }
                        }