•
The following firewall filter types are supported on lt- interfaces:
•
Logical interface-level filters
•
Bridge family filters
•
CCC family filters
All firewall configurations are supported. The scaling limitation with such filters is the
same as the existing firewall filter restrictions.
•
OAM is not supported on lt- interfaces.
•
Similar to other physical interfaces, the number of logical interfaces that can be
supported on logical tunnel physical interfaces is 30.
•
When a bridge domain is configured with a VLAN ID (bridge domain has normalized
VLANs), the difference is behavior between MX and ACX Series routers is that the MX
router does not match the user-vlan-id in output filter, whereas the ACX router matches
the user-vlan-id specified in the output filter.
•
If the logical tunnel interface is created using non Ethernet PICs, then default classifier
is not bound to the interface.
To create logical tunnel interfaces and the bandwidth in gigabits per second to reserve
for tunnel services, include the tunnel-services bandwidth (1g | 10g) statement at the [edit
chassis fpc slot-number pic number] hierarchy level:
[edit interfaces]
lt-fpc/pic/port {
unit logical-unit-number {
encapsulation encapsulation;
peer-unit unit-number; # peering logical system unit number
dlci dlci-number;
family (inet | inet6 | iso | mpls);
}
}
The ACX5048 and ACX5096 routers support ethernet-vpls and vlan-vpls encapsulations.
These encapsulations are supported only on logical tunnel interface and are required for
configuring hierarchial VPLS.
You can use any unused physical port on the ACX5048 and ACX5096 routers to create
a logical tunnel interface as shown below:
user@host# edit chassis
fpc 0 {
pic 0 {
tunnel-services {
port port-number;
}
}
}
The following sample configuration allows you to encapsulate vlan-ccc to vlan-vpls using
LT interface in ACX5048 and ACX5096 routers:
139Copyright © 2017, Juniper Networks, Inc.
Chapter 4: Configuring Interfaces and Chassis
To Next Page
Loading...
Need help?
General
