Configuring an Inline Service Interface for L2TP LNS
The inline service interface is a virtual physical service interface that resides on the Packet Forwarding Engine. This si interface, referred to as an anchor interface, makes it possible to provide L2TP services without a special services PIC. The inline service interface is supported only by MPCs on MX Series routers. Four inline service interfaces are configurable per MPC-occupied chassis slot.
You can maximize the number of sessions that can be shaped in one service interface by setting the maximum number of hierarchy levels to two. In this case, each LNS session consumes one L3 node in the scheduler hierarchy for shaping.
If you do not specify the number of levels (two is the only option), then the number of LNS sessions that can be shaped on the service interface is limited to the number of L2 nodes, or 4096 sessions. Additional sessions still come up, but they are not shaped.
To configure an inline service interface:
- Access the service interface.[edit interfaces]user@host# edit si-slot/pic/port
- (Optional; for per-session shaping only) Enable the inline
service interface for hierarchical schedulers and limit the number
of scheduler levels to two.[edit interfaces si-slot/pic/port]user@host# set hierarchical-scheduler maximum-hierarchy-levels 2
- (Optional; for per-session shaping only) Configure services
encapsulation for inline service interface.[edit interfaces si-slot/pic/port]user@host# set encapsulation generic-services
- Configure the IPv4 family on the reserved unit 0 logical
interface.[edit interfaces si-slot/pic/port]user@host# set unit 0 family inet
