Specifications

•
The following information regarding the guidelines for configuration of IP addresses
for NAT processing applies to the "Configuring Source and Destination Addresses
Network Address Translation Overview " section of the "Network Address Translation
Rules Overiew" topic:
The addresses that are specified as valid in the inet.0 routing table and not supported
for NAT translation are orlonger match filter types. You cannot specify any regions
within such address prefixes in a NAT pool.
•
The following information regarding the working of APP with NAT rules applies to the
"Network Address Translation Rules Overiew" topic:
For MX Series routers with MS-MICs and MS-MPCs, although the address pooling
paired (APP) functionality is enabled within a NAT rule (by including the address-pooling
statement at the [edit services nat rule rule-name term term-name then translated]
hierarchy level), it is a characteristic of a NAT pool. Such a NAT pool for which APP is
enabled cannot be shared with NAT rules that do not have APP configured.
Junos OS High Availability Feature Guide for Routing Devices
•
In Junos OS Release 13.3, the “Unified ISSU System Requirements” topic in the Junos
OS High Availability Feature Guide for Routing Devices incorrectly states in Table 2:
Unified ISSU Protocol Support that an MX Series Virtual Chassis supports unified ISSU
in Junos OS Release 12.2 and later releases. In fact, an MX Series Virtual Chassis supports
unified ISSU in Junos OS Release 14.1 and later releases.
[See Unified ISSU System Requirements.]
Junos
®
OS Release 13.3R1 for the EX Series, M Series, MX Series, PTX Series, and
T Series
•
Virtual Chassis support on MX104 routers—In Junos OS Release 13.3, the “Software
feature support (MX104)” feature description in the Release Notes: Junos
®
OS Release
13.3R1 for the EX Series, M Series, MX Series, PTX Series, and T Series incorrectly states
in the Layer 2 Features section that Virtual Chassis is supported on MX104 routers.
Virtual Chassis is not supported on MX104 routers.
Layer 2 Configuration Guide, Bridging, Address Learning, and Forwarding
•
The following information regarding the differences in the default limit on MAC
addresses that can be learned on an access port and a trunk port is inadvertently
omitted from the “Limiting MAC Addresses Learned from an Interface in a Bridge
Domain” topic:
•
For an access port, the default limit on the maximum number of MAC addresses
that can be learned on an access port is 1024. Because an access port can be
configured in only one bridge domain in a network topology, the default limit is 1024
addresses, which is same as the limit for MAC addresses learned on a logical interface
in a bridge domain (configured by including the interface-mac-limit limit statement
at the [edit bridge-domains bridge-domain-name bridge-options interface
interface-name] or [edit bridge-domains bridge-domain-name bridge-options] hierarchy
level.
145Copyright © 2015, Juniper Networks, Inc.
Documentation Updates