Supported Platforms
Related Documentation
Configuring Layer 3 Tunnel Services Interfaces on an MX Series Router with a DPC
The MX Series routers support Dense Port Concentrators (DPCs) with built-in Ethernet ports, which do not support Tunnel Services PICs. To create tunnel interfaces on an MX Series router with a DPC, you configure the DPC and the corresponding Packet Forwarding Engine to use for tunneling services at the [edit chassis] hierarchy level. You also configure the amount of bandwidth reserved for tunnel services. The Junos OS creates tunnel interfaces on the Packet Forwarding Engine.
To create tunnel interfaces on MX Series routers, include the following statements at the [edit chassis] hierarchy level:
Include the fpc slot-number statement to specify the slot number of the DPC. If two SCBs are installed, the range is 0 through . If three SCBs are installed, the range is 0 through 5 and 7 through .
Include the pic number statement to specify the number of the Packet Forwarding Engine on the DPC. The range is 0 through 3.
You can also specify the amount of bandwidth to allocate for tunnel traffic on each Packet Forwarding Engine by including the bandwidth bandwidth-value statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level:
- 1g indicates that 1 Gbps of bandwidth is reserved for tunnel traffic. Configure this option only for a Packet Forwarding Engine on a Gigabit Ethernet 40-port DPC.
- 10g indicates that 10 Gbps of bandwidth is reserved for tunnel traffic. Configure this option only for a Packet Forwarding Engine on a 10-Gigabit Ethernet 4-port DPC.
- 20g or 40g—Configure 20 gigabits per second or 40 gigabits per second only on an MX Series router with the MPC3E and the 100-Gigabit CFP MIC.
If you specify a bandwidth that is not compatible with the type of DPC and Packet Forwarding Engine, tunnel services are not activated. For example, you cannot specify a bandwidth of 1 Gbps for a Packet Forwarding Engine on a 10-Gigabit Ethernet 4-port DPC.
When you configure tunnel interfaces on the Packet Forwarding Engine of a 10-Gigabit Ethernet 4-port DPC, the Ethernet interfaces for that port are removed from service and are no longer visible in the command-line interface (CLI). The Packet Forwarding Engine of a 10-Gigabit Ethernet 4-port DPC supports either tunnel interfaces or Ethernet interfaces, but not both. Each port on the 10-Gigabit Ethernet 4-port DPC includes two LEDs, one for tunnel services and one for Ethernet services, to indicate which type of service is being used. On the Gigabit Ethernet 40-port DPC, you can configure both tunnel and Ethernet interfaces at the same time.
To verify that the tunnel interfaces have been created, issue the show interfaces terse operational mode command. For more information, see the Junos OS Operational Mode Commands.
For additional information about tunnel services, see the “Tunnel Services” chapter in the Junos Services Interfaces Configuration Release 12.3.