Juniper JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010, Руководство по настройке

Страница: 622 / 774

■
Use to set the MTU using a combination of lower layer restrictions and controls.
■
You can specify an MTU greater than the current maximum permitted by
RFC 2516, in the range 66–65535.
■
You can use the use-lower-layer keyword to use the lower layer interface value
minus any PPPoE overhead. You can use the use-mtu-tag keyword to use the
provided PPPoE mtu tag value.
■
Example
host1(config-profile)# pppoe mtu 1380
■
Use the no version to restore the default value, 1494.
■
See pppoe mtu.
pppoe remote-circuit-id
■
Use to enable the router to capture and process a vendor-specific tag containing
a remote circuit ID transmitted from a DSLAM device.
■
Optionally, the router can use the remote circuit ID in place of either or both of
the Calling-Station-Id [31] and NAS-Port-Id [87] RADIUS attributes to uniquely
identify subscriber locations.
■
Example
host1(config-profile)# pppoe remote-circuit-id
■
Use the no version to restore the default behavior, which is not to capture and
process the remote circuit ID.
■
See pppoe remote-circuit-id.
pppoe service-name-table
■
Use to assign a PPPoE service name table to dynamic interfaces created with
this profile.
■
A PPPoE service name table defines the set of specific service name tags that
an AC, such as an E Series router, offers to PPPoE clients. It also controls whether
the router responds to or does not respond to client requests containing an empty
service name tag.
■
Specify the name of the PPPoE service name table configured with the pppoe
service-name-table command from Global Configuration mode.
■
Example
host1(config-profile)# pppoe service-name-table myServiceTable1
■
Use the no version to remove the PPPoE service name table assignment.
■
See pppoe service-name-table.
pppoe sessions
590 ■
Configuring a Dynamic Interface from a Profile
JUNOSe 11.1.x Link Layer Configuration Guide