The JUNOS Software also supports M13 mapped T1 interfaces under CAU4. To
configure a T1 interface under CAU4, use the
t1
statement at the
[edit interfaces
cau4-
fpc
/
pic
/
port
:
unit
partition
partition-number interface-type
t1]
or
[edit interfaces
cau4-
fpc
/
pic
/
port
:
unit
partition
partition-number interface-type
ct1]
hierarchy level.
The JUNOS Software does not allow combined configurations of E1 and E3
interfaces together under a CAU4 interface.
Similarly, you cannot mix T1, E1, T3, and E3 interfaces directly under CAU4.
NOTE:
The TUG-3 partition is not supported.
ITU-T VT-mapping in combination with TUG3 partition is not supported.
[
Network Interfaces
,
PIC Guide
]
■
Stateful firewall chaining for FTP, TFTP, and RTSP data sessions (MX Series
routers with Multiservices DPCs, and M120 or M320 routers with Multiservices
400 PICs)
—Adds support for stateful firewall rule sets in Dynamic Application
Awareness for JUNOS Software service chains. New application-level gateways
(ALGs) are available for FTP (
junos-ftp
), TFTP (
junos-tftp
), and RTSP (
junos-rtsp)
;
you can include them as values for the
applications
statement at the
[edit services
stateful-firewall rule
rule-name
term
term-name
from]
hierarchy level. In addition,
you can include new statement options at the
[edit interfaces ms-
fpc
/
pic
/
port
services-options ignore-errors]
hierarchy level to enable stateful firewall sessions
to operate in a no-drop mode and ignore various traffic errors that would normally
result in dropped packets. There are no CLI changes in the APPID, IDP, AACL,
or L-PDF configurations. The associated operational mode commands should
report the new applications when identified.
[
Services Interfaces
]
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
17
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
