Specifications

the inline-jflow statement at the [edit forwarding-options sampling instance

instance-name family inet output] hierarchy level).

•

The following information regarding the interoperation of FTP ALG and address-pooling

paired features is missing from the "ALG Descriptions" topic of the "Application

Properties" chapter:

On MS-MPCs and MS-MICs, for passive FTP to work properly without FTP application

layer gateway (ALG) enabled (by not specifying the application junos-ftp statement

at the [edit services stateful-firewall rule rule-name term term-name from] and the [edit

services nat rule rule-name term term-name from] hierarchy levels), you must enable

the address pooling paired (APP) functionality enabled (by including the

address-pooling statement at the [edit services nat rule rule-name term term-name then

translated] hierarchy level). Such a configuration causes the data and control FTP

sessions to receive the same NAT address.

Standards Reference

•

The “Supported Flow Monitoring and Discard Accounting Standards” topic fails to

mention the following additional information:

On MX Series routers, Junos OS partially supports the following RFCs:

•

RFC 5101, Specification of the IP Flow Information Export (IPFIX) Protocol for the

Exchange of IP Traffic Flow Information

Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series