Your customer requests that you provide a transparent Layer 2 service between two of their remote locations. This service must allow the customer to pass tagged traffic from multiple VLANs. You…

Question

Options

• AAs traffic enters the Q-in-Q tunnel on the core-facing interface on the ingress PE device, a push
• BAs traffic passes through intermediary P routers in the Q-in-Q tunnel, a push operation is
• CAs traffic passes through intermediary P routers in the Q-in-Q tunnel, a swap operation is
• DAs traffic enters the Q-in-Q tunnel on the core-facing interface on the ingress PE device, a swap

• A
  83% (24)
• B
  10% (3)
• D
  7% (2)

Explanation

Q-in-Q tunneling adds a service VLAN tag before the customer's 802.1Q VLAN tags. The Juniper Networks Junos operating system implementation of Q-in-Q tunneling supports the IEEE 802.1ad In Q-in-Q tunneling, as a packet travels from a customer VLAN (C-VLAN) to a service provider's or data center VLAN (S-VLAN), another 802.1Q tag for the appropriate S-VLAN is added before The C-VLAN tag remains and is transmitted through the network. As the packet leaves the S- VLAN in the downstream direction, the S-VLAN 802.1Q tag is removed. With the push option, a packet retains its tag and an additional VLAN tag is added. With the swap option, the incoming tag is replaced with an S-VLAN tag. (This is VLAN tunneling-qfx-series.html

No community discussion yet for this question.