Assigning A Profile To An Interface - Juniper JUNOSE SOFTWARE 11.2.X - LINK LAYER CONFIGURATION GUIDE 7-7-2010 Configuration Manual

Software for e series broadband services routers link layer configuration guide
Table of Contents

Advertisement

vlan profile
vlan service-profile

Assigning a Profile to an Interface

Copyright © 2010, Juniper Networks, Inc.
Use the no version to remove the association between a policy list and an interface or
a profile.
See vlan policy.
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.
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.
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
Chapter 17: Configuring Dynamic Interfaces
589

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.2

Table of Contents