Enabling Inline Service Interfaces 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. The following MPC2 slots are supported:
The MPC2-3D contains two lookup engines, each with two
siinterfaces.The MPC1-3D contains only one lookup engine and it hosts all four
siinterfaces.
You can configure the following inline service interfaces as
anchor interfaces for MLPPP bundles: si-slot/0/0, si-slot/1/0, si-slot/2/0, and si-slot/3/0.
For MLPPP over PPPoE subscribers,
family mlpppis supported inpp0member link IFL, and the bundle is ansiIFL.For MLPPP over LNS subscribers,
family mlpppis supported insi-member link IFL, and the bundle is ansiIFL.
You enable inline services for PICs 0 to 3 individually by setting
the inline-services statement at the [edit chassis] hierarchy level for the FPCs.
The following example shows how to enable inline services
for PIC 0 on MPC slot 1, and PIC 1 on MPC on slot 5, and set 10g as
the bandwidth for tunnel traffic. As a result, both si-1/0/0 and si-5/0/0 are created for the specified
PICs as well.
To enable inline service interfaces:
The following shows sample output:
chassis {
fpc 1 {
pic 0 {
inline-services {
bandwidth 10g;
}
}
}
fpc 5 {
pic 1 {
inline-services {
bandwidth 10g;
}
}
}
}