EasyManua.ls Logo

Juniper JUNOS OS 10.4 - RELEASE NOTES - Page 31

Juniper JUNOS OS 10.4 - RELEASE NOTES
197 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
To configure Layer 2 wholesale for a subscriber access network:
Configure a VLAN dynamic profile. See the Subscriber Access Configuration Guide
for details.
Include the routing-instances statement along with the $junos-routing-instance
dynamic variable at the [edit dynamic-profiles profile-name interface
$junos-interface-name] hierarchy level.
Include the interfaces statement along with the $junos-interface-name dynamic
variable at the [edit dynamic-profiles profile-name interface “$junos-interface-name”
routing-instances “$junos-routing-instance”] hierarchy level.
Include the interfaces statement along with the $junos-interface-ifd-name dynamic
variable at the [edit dynamic-profiles profile-name] hierarchy level.
Include the unit statement along with the $junos-interface-unit dynamic variable at
the [edit dynamic-profiles profile-name interface “$junos-interface-ifd-name”]
hierarchy level.
(Optional) Include the encapsulation statement at the [edit dynamic-profiles
profile-name interface “$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy
level and specify the unit encapsulation as vlan-vpls or vlan-ccc.
NOTE: If you choose not to specify an encapsulation for the logical
interface, you must specify encapsulation for the physical interface.
Include the vlan-tags statement and define the outer VLAN tag using the
$junos-stacked-vlan-id dynamic variable and the inner VLAN tag using the
$junos-vlan-id dynamic variable at the [edit dynamic-profiles profile-name interface
“$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy level.
Include the input-vlan-map statement at the [edit dynamic-profiles profile-name
interface “$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy level and
define the map settings as follows:
NOTE: You configure the input-vlan-map statement only when there is
a need to either push an outer tag on a single-tagged subscriber packet
or modify the outer tag in a subscriber dual-tagged packet.
Specify the action that you want the input VLAN map to take. See the Network
Interfaces Configuration Guide for details on how to configure input-vlan-map
statement options.
Include the vlan-id statement along with the $junos-vlan-map-id dynamic variable.
Include the output-vlan-map statement at the [edit dynamic-profiles profile-name
interface “$junos-interface-ifd-name” unit $junos-interface-unit] hierarchy level and
specify the action that you want the output VLAN map to take. See the Network
31Copyright © 2010, Juniper Networks, Inc.
New Features in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

Table of Contents

Related product manuals