Specifications

by the destination-prefix statement in the then statement. Starting in Junos OS Release
13.3, this restriction is enforced.
[edit services nat]
rule rule-name {
term term-name {
from {
destination-address-range low minimum-value high maximum-value <except>;
destination-prefix-list list-name <except>;
}
then {
destination-prefix destination-prefix;
}
}
}
•
Change in running RPM traceoptions—Starting in Junos OS Release 13.2, running RPM
traceoptions is performed from the [edit services rpm] hierarchy. Prior to Junos OS
Release 13.2, running RPM traceoptions was performed at the [edit snmp] hierarchy
level.
The RPM traceoptions are configured as follows:
[edit services rpm]
traceoptions {
file filename <files number> <match regular-expression > <size maximum-file-size>
<world-readable | no-world-readable>;
flag flag;
}
This issue was being tracked by PR857470.
•
Restrictions for maximum block size for NAT port block allocation—Beginning with
Junos OS Release 13.3, the maximum blocksize for NAT port block allocation (PBA) is
32,000.
•
Support for display of NAT type for EIF flows (MX Series routers with MS-MICs and
MS-MPCs)—Starting with Junos OS Release 13.3R4, the output of the show services
sessions extensive command, the Translation Type field displays the value as NAPT-44
for Endpoint Independent Filtering (EIF) flows. Also, the label, EIF, is displayed beside
the translation type parameter to enable easy identification of EIF flows.
•
Support for passive-mode tunneling (MX Series routers with MS-MICs and
MS-MPCs)—Starting with Junos OS Release 13.3R4, passive mode tunneling is
supported on MS-MICs and MS-MPCs. You can include the passive-mode-tunneling
statement at the [edit services service-set service-set-name ipsec-vpn-options] hierarchy
level to enable the service set to tunnel malformed packets.
61Copyright © 2015, Juniper Networks, Inc.
Changes in Behavior and Syntax