
•
Use the
no
version to remove the association between a policy list and an interface or
a profile.
•
See vlan policy.
vlan profile
•
Use to add a nested profile assignment to a base profile for a dynamic VLAN
subinterface.
•
A nested profile assignment references another profile that configures attributes for
a dynamic upper-interface type over the VLAN subinterface.
•
Examples
host1(config-profile)#
vlan profile pppoe vlanProfilePppoe
host1(config-profile)#
vlan profile ip vlanProfileIP
•
Use the
no
version to remove the profile assignment for the upper-interface
encapsulation type.
•
See vlan profile.
vlan service-profile
•
Use to specify a service profile name for a dynamic VLAN and to enter Service Profile
Configuration mode. Service profiles contain user and password information, and are
used in route maps for subscriber management and to authenticate subscribers with
RADIUS.
•
You can specify a service profile name with up to 80 alphanumeric characters.
•
Example
host1(config)#
vlan service-profile vlanClass1Service
host1(config-service-profile)#
•
Use the
no
version to delete the service profile.
•
See vlan service-profile.
Assigning a Profile to an Interface
Use the
profile
command from Interface Configuration mode when you assign a profile
to an interface.
For static PPP interfaces, you can assign only a profile for IP encapsulations. For static
ATM 1483 subinterfaces, you can assign one profile for each bridged Ethernet, IP, PPP,
and PPPoE encapsulation. For static VLAN subinterfaces, you can assign one profile for
each IP or PPPoE encapsulation. You can also use the default keyword
any
, which applies
to any autoconfigured encapsulation that does not have specific profile assignment.
For example, the following commands cause the router to use ProfileB when an IPoA
packet is received, and to use ProfileA for any other received encapsulation that is
autoconfigured. When you omit the keyword, it defaults to
any
.
host1(config-subif)#
profile any ProfileA
host1(config-subif)#
profile ip ProfileB
589
Copyright © 2010, Juniper Networks, Inc.
Chapter 17: Configuring Dynamic Interfaces
Summary of Contents for JUNOSE 11.2
Page 6: ...Copyright 2010 Juniper Networks Inc vi ...
Page 8: ...Copyright 2010 Juniper Networks Inc viii JunosE 11 2 x Link Layer Configuration Guide ...
Page 26: ...Copyright 2010 Juniper Networks Inc xxvi JunosE 11 2 x Link Layer Configuration Guide ...
Page 34: ...Copyright 2010 Juniper Networks Inc 2 JunosE 11 2 x Link Layer Configuration Guide ...
Page 136: ...Copyright 2010 Juniper Networks Inc 104 JunosE 11 2 x Link Layer Configuration Guide ...
Page 162: ...Copyright 2010 Juniper Networks Inc 130 JunosE 11 2 x Link Layer Configuration Guide ...
Page 228: ...Copyright 2010 Juniper Networks Inc 196 JunosE 11 2 x Link Layer Configuration Guide ...
Page 290: ...Copyright 2010 Juniper Networks Inc 258 JunosE 11 2 x Link Layer Configuration Guide ...
Page 330: ...Copyright 2010 Juniper Networks Inc 298 JunosE 11 2 x Link Layer Configuration Guide ...
Page 376: ...Copyright 2010 Juniper Networks Inc 344 JunosE 11 2 x Link Layer Configuration Guide ...
Page 390: ...Copyright 2010 Juniper Networks Inc 358 JunosE 11 2 x Link Layer Configuration Guide ...
Page 402: ...Copyright 2010 Juniper Networks Inc 370 JunosE 11 2 x Link Layer Configuration Guide ...
Page 468: ...Copyright 2010 Juniper Networks Inc 436 JunosE 11 2 x Link Layer Configuration Guide ...
Page 496: ...Copyright 2010 Juniper Networks Inc 464 JunosE 11 2 x Link Layer Configuration Guide ...
Page 534: ...Copyright 2010 Juniper Networks Inc 502 JunosE 11 2 x Link Layer Configuration Guide ...
Page 650: ...Copyright 2010 Juniper Networks Inc 618 JunosE 11 2 x Link Layer Configuration Guide ...
Page 739: ...PART 2 Index Index on page 709 707 Copyright 2010 Juniper Networks Inc ...
Page 740: ...Copyright 2010 Juniper Networks Inc 708 JunosE 11 2 x Link Layer Configuration Guide ...
Page 772: ...Copyright 2010 Juniper Networks Inc 740 JunosE 11 2 x Link Layer Configuration Guide ...