[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring SCU on a Virtual Loopback Tunnel Interface

To configure source class usage on the virtual loopback tunnel interface, perform the tasks described in the following sections:

Example: Configuring a Virtual Loopback Tunnel Interface on a Provider Edge Router Equipped with a Tunnel PIC

Define a virtual loop interface on a provider edge router with a Tunnel PIC:

[edit interfaces]vt-0/3/0 {unit 0 {family inet {accounting {source-class-usage {input;}}}}}

Example: Mapping the VRF Instance Type to the Virtual Loopback Tunnel Interface

Map the VRF instance type to the virtual loopback tunnel interface:

[edit]routing-instances {VPN-A {instance-type vrf;interface at-2/1/1.0;interface vt-0/3/0.0;route-distinguisher 10.255.14.225:100;vrf-import import-policy-name;vrf-export export-policy-name;protocols {bgp {group to-r4 {local-address 10.27.253.1;peer-as 400;neighbor 10.27.253.2;}}}}}

Note: For SCU and DCU to work, do not include the vrf-table-label statement at the [edit routing-instances instance-name] hierarchy level.

Example: Sending Traffic Received from the Virtual Loopback Interface Out the Source Class Output Interface

Send traffic received from the virtual loopback tunnel interface out of the source class output interface:

[edit interfaces]at-1/1/0 {unit 0 {family inet {accounting {source-class-usage {output;}}}}}

For more information about configuring source class usage on the virtual loopback tunnel interface, see the JUNOS Network Interfaces Configuration Guide.


Published: 2010-04-27

[an error occurred while processing this directive]