Configuring Inline Service Interface for PPPoE and LNS Subscribers
The inline service (si) interface
is a virtual physical interface that resides on lookup engines. The si interface, referred to as an anchor interface, makes it possible to support multilink PPP (MLPPP) bundles
without a special services PIC. The si interface
is supported on MLPPP on the MX Series. Four inline service interfaces
are configurable per MPC-occupied chassis slot.
For existing Layer 2 and Layer 3 services, the si interface unit 0 is currently
used to store the unilist next-hop information. However, you must
reserve and configure si interface unit 0 and set family inet for both PPPoE and LNS subscribers because the si interface implements the bundle functionality. Setting family inet6 is ignored by the system.
The following example shows how to configure inline services
for PIC 0 on MPC slot 1, and PIC 1 on MPC on slot 5, and set unit 0 family inet for both.
To configure inline service interfaces:
The following shows sample output:
interfaces {
si-1/0/0 {
hierarchical-scheduler maximum-hierarchy-levels 2;
encapsulation generic-services;
unit 0 {
family inet;
}
}
si-5/1/0 {
hierarchical-scheduler maximum-hierarchy-levels 2;
encapsulation generic-services;
unit 0 {
family inet;
}
}
}