action for the unknown service name tag is
drop
. If both
terminate
and
drop
are configured for services in the table, all unknown service name tags are
dropped by default.
Features
PPPoE service name tables enable an AC, such as an E Series router, to support
multiple service name tags in addition to the empty service name tag and the
unknown service name tag. You can configure up to 16 PPPoE service name tables
per E Series router to:
■
Define the set of service name tags (empty service name, custom service name,
and unknown service name) that the router advertises in the PADO packets sent
to PPPoE clients.
■
Control whether the router responds to (
terminate
) or denies (
drop
) PADI requests
based on the action associated with the service name tags.
Table Structure
Each entry, or row, in a PPPoE service name table consists of the following
components:
■
Service name tag—Service name tags specify the client services that an AC
supports. You can add three types of service name tags to the PPPoE service
name table: empty service name, custom service name (
serviceName
), and
unknown service name. Every PPPoE service name table includes one empty
service name tag and one unknown service name service tag. An empty service
name tag is a service tag of zero length that is used to represent any service. An
unknown service name service tag is used to represent a service tag that has not
been configured in the service name table. In addition to these two tags, you
can configure up to 16 custom service name tags per table.
■
Action—Each service name tag has an associated action:
terminate
(the default
action) or
drop
. For empty service name and unknown service name entries,
you can use the
action
keyword with the
service
command to modify the default
action associated with the service. For custom service name (
serviceName
) entries,
using the
action
keyword with the
service
command is optional. The default
action for a custom service tag entry is
terminate
.
For example, Table 19 on page 378 shows a PPPoE service name table containing
five entries: three custom service name tags, two associated with the
terminate
action and one associated with the
drop
action; an empty service name tag (“ ” )
associated with the
drop
action; and an unknown service name tag associated with
the
drop
action.
Table 19: Sample PPPoE Service Name Table
Action
Service Name
Terminate
“myISPService”
Terminate
“myQOSClass1”
378
■
Overview
JUNOSe 11.1.x Link Layer Configuration Guide
Содержание JUNOSE 11.1.X - LINK LAYER CONFIGURATION 4-7-2010
Страница 6: ...vi...
Страница 8: ...viii JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 26: ...xxvi List of Figures JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 34: ...2 Chapters JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 200: ...168 Monitoring Upper Level Protocols over Ethernet JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 230: ...198 Monitoring VLAN and S VLAN Subinterfaces JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 258: ...226 Monitoring 802 3ad Link Aggregation JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 334: ...302 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 394: ...362 Monitoring Multiclass MLPPP JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 406: ...374 Monitoring POS JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 468: ...436 Troubleshooting JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 498: ...466 Monitoring Bridged Ethernet JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 546: ...514 Monitoring Cisco HDLC JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 747: ...Part 2 Index Index on page 717 Index 715...
Страница 748: ...716 Index JUNOSe 11 1 x Link Layer Configuration Guide...
Страница 774: ...742 Index JUNOSe 11 1 x Link Layer Configuration Guide...