Switching

Hello Community,

Got an issue that I need some help with. Currently, I have a managed TLS with another provider that is access and transparent. We can face it with any of our c-tags, and they pop out on the other side the same way.

That carrier wants to migrate this to a tagged NNI agreement. I am used to doing this with ACX2200s but this involes all EX devices.

Currently, our NNI starts at an EX4300. That carrier uses Advas with EPL circuits for our last mile to a Juniper EX2300.

We will agree on VL1201 for this transport. I need to configure out Junipers on both ends to use VL1201 but under 1201 tags 501 and 370 must be allowed for the customers traffic on the EX2300. 

Try this

EX4300 Side (The NNI Head-end)

You need to define the S-VLAN and then configure the interface facing the carrier to "push" that tag onto the incoming customer traffic.

set vlans S-VLAN-1201 vlan-id 1201
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 370
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 501

ge-0/0/31 config

You must set the interface to trunk mode for the S-VLAN

     set interfaces ge-0/0/31 description "Link to Carrier Adva - VLAN 1201"
set interfaces ge-0/0/31 vlan-tagging
set interfaces ge-0/0/31 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/31 unit 0 family ethernet-switching vlan members S-VLAN-1201

     set interfaces ge-0/0/31 mtu 9000

EX2300 Side (The Customer Hand-off)

The EX2300 is the egress point. It needs to receive the double-tagged frame (1201 + 501/370), "pop" the 1201 tag, and deliver the C-tags to the customer equipment.

set vlans S-VLAN-1201 vlan-id 1201
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 370
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 501

Configure the Uplink Interface

This is the port connected to the Adva/Carrier.

ge-0/0/0

set interfaces ge-0/0/0 description "Uplink to Carrier Adva"
set interfaces ge-0/0/0 vlan-tagging
set interfaces ge-0/0/0 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members S-VLAN-1201

Configure the Customer Hand-off Port

This port will "tunnel" the traffic. Any frame tagged with 501 or 370 entering this port will be wrapped in tag 1201.

ge-0/0/1

set interfaces ge-0/0/1 description "Customer Hand-off"
set interfaces ge-0/0/1 unit 0 family ethernet-switching interface-mode access
set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members S-VLAN-1201

Hello Community,

Got an issue that I need some help with. Currently, I have a managed TLS with another provider that is access and transparent. We can face it with any of our c-tags, and they pop out on the other side the same way.

That carrier wants to migrate this to a tagged NNI agreement. I am used to doing this with ACX2200s but this involes all EX devices.

Currently, our NNI starts at an EX4300. That carrier uses Advas with EPL circuits for our last mile to a Juniper EX2300.

We will agree on VL1201 for this transport. I need to configure out Junipers on both ends to use VL1201 but under 1201 tags 501 and 370 must be allowed for the customers traffic on the EX2300. 

EX2300/EX4300 being ELS JunOS config style, I guess QinQ is not configured with «dot1q-tunneling» that was for older switches...

This was answered a long time and may work: Community Juniper / RE: Q-in-Q configuration on EX2300

Try this

EX4300 Side (The NNI Head-end)

You need to define the S-VLAN and then configure the interface facing the carrier to "push" that tag onto the incoming customer traffic.

set vlans S-VLAN-1201 vlan-id 1201
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 370
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 501

ge-0/0/31 config

You must set the interface to trunk mode for the S-VLAN

     set interfaces ge-0/0/31 description "Link to Carrier Adva - VLAN 1201"
set interfaces ge-0/0/31 vlan-tagging
set interfaces ge-0/0/31 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/31 unit 0 family ethernet-switching vlan members S-VLAN-1201

     set interfaces ge-0/0/31 mtu 9000

EX2300 Side (The Customer Hand-off)

The EX2300 is the egress point. It needs to receive the double-tagged frame (1201 + 501/370), "pop" the 1201 tag, and deliver the C-tags to the customer equipment.

set vlans S-VLAN-1201 vlan-id 1201
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 370
set vlans S-VLAN-1201 dot1q-tunneling customer-vlans 501

Configure the Uplink Interface

This is the port connected to the Adva/Carrier.

ge-0/0/0

set interfaces ge-0/0/0 description "Uplink to Carrier Adva"
set interfaces ge-0/0/0 vlan-tagging
set interfaces ge-0/0/0 unit 0 family ethernet-switching interface-mode trunk
set interfaces ge-0/0/0 unit 0 family ethernet-switching vlan members S-VLAN-1201

Configure the Customer Hand-off Port

This port will "tunnel" the traffic. Any frame tagged with 501 or 370 entering this port will be wrapped in tag 1201.

ge-0/0/1

set interfaces ge-0/0/1 description "Customer Hand-off"
set interfaces ge-0/0/1 unit 0 family ethernet-switching interface-mode access
set interfaces ge-0/0/1 unit 0 family ethernet-switching vlan members S-VLAN-1201

Hello Community,

Got an issue that I need some help with. Currently, I have a managed TLS with another provider that is access and transparent. We can face it with any of our c-tags, and they pop out on the other side the same way.

That carrier wants to migrate this to a tagged NNI agreement. I am used to doing this with ACX2200s but this involes all EX devices.

Currently, our NNI starts at an EX4300. That carrier uses Advas with EPL circuits for our last mile to a Juniper EX2300.

We will agree on VL1201 for this transport. I need to configure out Junipers on both ends to use VL1201 but under 1201 tags 501 and 370 must be allowed for the customers traffic on the EX2300.