[j-nsp] R: Q in Q on EX 4500 / 4200
Laurent CARON
lcaron at unix-scripts.info
Wed Jan 18 05:34:33 EST 2017
Hi,
Just tried it to no avail:
# show vlans S-vlan1219
vlan-id 1219;
interface {
ge-0/2/3.0 {
mapping {
1019 {
push;
}
}
}
}
dot1q-tunneling {
customer-vlans 1019;
layer2-protocol-tunneling {
all;
}
}
# show vlans C-vlan1019
vlan-id 1019;
l3-interface vlan.1019;
# show interfaces vlan unit 1019
family inet {
address 1.1.1.1/30;
}
The l3 interface vlan.1019 never comes up :(
> show vlans C-vlan1019 extensive
VLAN: C-vlan1019, Created at: Wed Jan 18 11:30:35 2017
802.1Q Tag: 1019, Internal index: 54, Admin State: Enabled, Origin: Static
Layer 3 interface: vlan.1019 (DOWN)
IPV4 addresses:
1.1.1.1/30(Primary)
Protocol: Port Mode, Mac aging time: 300 seconds
Number of interfaces: Tagged 0 (Active = 0), Untagged 0 (Active = 0)
On 18/01/2017 08:11, Misak Khachatryan wrote:
> Hi,
>
> You can push/pop/swap tags on specific interfaces. See example:
>
> show vlans
> Data3 {
> vlan-id 69;
> interface {
> ae6.0 {
> mapping {
> 10 {
> push;
> }
> 100 {
> push;
> }
> 1040 {
> push;
> }
> 1111 {
> push;
> }
> 20 {
> push;
> }
> 200 {
> push;
> }
> 220 {
> push;
> }
> 242 {
> push;
> }
> 252 {
> push;
> }
> 30 {
> push;
> }
> 586 {
> push;
> }
> }
> }
> }
> dot1q-tunneling {
> customer-vlans [ 10 20 30 100 586 252 242 1040 200 220 1111 ];
> }
> }
>
> Hope this will help.
>
> Best regards,
> Misak Khachatryan,
> Network Administration and
> Monitoring Department Manager,
>
> GNC- ALFA CJSC
> 1 Khaghaghutyan str., Abovyan, 2201 Armenia
> Tel: +374 60 46 99 70 (9670),
> Mob.: +374 93 19 98 40
> URL: www.rtarmenia.am
>
>
> On Tue, Jan 17, 2017 at 6:03 PM, Laurent CARON <lcaron at unix-scripts.info> wrote:
>> Thanks Lucio,
>>
>> It perfectly matches with my empirical findings, but just wanted to make
>> sure I didn't miss the obvious.
>>
>> I'll then have to add an intermediate EX to strip/add a VLAN tag as
>> needed...ugly... :(
>>
>> On 17/01/2017 14:52, Valentini, Lucio wrote:
>>> Hi,
>>>
>>> as far as I know, no. there is a complete separation between S-LAN and C-LAN; local VLANs can be S-LANs, if you are a provider, or C-LANs, if you are a customer; but you cannot manage an S-LAN if you are a customer or manage a C-LAN if you are a provider.
>>>
>>> However some time ago somebody told you can do that with an MX router, but never with an EX switch.
>>>
>>> I hope this helps
>>>
>>> Lucio
>>>
>>> -----Messaggio originale-----
>>> Da: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] Per conto di Laurent CARON
>>> Inviato: martedì 17 gennaio 2017 13:59
>>> A: juniper-nsp at puck.nether.net
>>> Oggetto: [j-nsp] Q in Q on EX 4500 / 4200
>>>
>>> Hi,
>>>
>>> I'm trying to achieve the following:
>>> - One of my providers is handing to me a Q-in-Q link
>>> - Each S-VLAN is heading to a remote site
>>> - Each C-VLAN range is mapped to a S-VLAN
>>>
>>> Is there a way with only EX4500/4200 (no hairpin, no second device to pop the S-VLAN tags) to terminate any C-VLAN to a local (on the EX) l3 interface ?
>>>
>>> Juniper support website is most of the time contradictory with itself...
>>>
>>> Thanks
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> !DSPAM:587f18ad184612001115034!
>
More information about the juniper-nsp
mailing list