Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Changes in Behavior and Syntax

 

This section lists the changes in behavior of Junos OS features and changes in the syntax of Junos OS statements and commands from Junos OS Release 16.2R2 for MX Series and T Series.

General Routing

  • Support for deletion of static routes when the BFD session goes down (MX Series)—Starting with Junos OS 16.2R2, the default behavior of the static route at the [edit routing-options static static-route bfd-admin-down] hierarchy level is active. So, the static routes are deleted when the BFD receives a session down message.

Interfaces and Chassis

  • Changes to show interfaces interface-name extensive output—Starting in Junos OS Release 16.1R5 and 16.2R2, the MAC Control Frames field of the show interface interface-name extensive command for a specified 10-Gigabit Ethernet interface displays a value of zero. In previous releases, the value for this field was calculated. Because of continuous traffic and as a result of the calculations, the value displayed for this field changed continuously.

Junos OS XML API and Scripting

  • XML output change for show subscribers summary port command (MX Series)—Starting in Junos OS Release 16.2R2, the display format has changed for the show subscribers summary port command to make parsing the output easier. The output is now displayed as in the following example:

    user@host> show subscribers summary port | display xml

    In earlier releases, that output is displayed as in the following example:

    user@host> show subscribers summary port | display xml

Management

  • Support for status deprecated statement in YANG modules (MX Series and T Series)—Starting with Junos OS Release 16.1R2, Juniper Networks YANG modules include the status deprecated statement to indicate configuration statements, commands, and options that are deprecated.

  • XPath expressions for specific YANG keywords disabled during commit operations (MX Series and T Series)—Starting in Junos OS Release 16.1R2, XPath expression evaluations for the following YANG keywords are disabled by default during commit operations: leafref, must, and when. Prior to Junos OS Release 16.1R2, Junos OS evaluates the constraints for these keywords, which can result in longer commit times.

MPLS

  • New field for LSP ping egress interface failure—Starting in Junos OS Release 16.2R2, if an LSP ping is started and the chosen egress interface fails, pings are still sent to the failed interface and then dropped. The ping must be manually stopped and restarted to select a working interface to the destination (if one exists). To help detect this ping situation, a new field, Packets dropped due to ifl down, has been added to the output of the show system statistics mpls command.

    [See show system statistics mpls]

  • RSVP LSP Attribute Order Complies with RFC6510 (M Series, MX Series, and T Series)—The Junos OS RSVP PATH/RESV messages follow the recommendations made in RFC6510 for the LSP attribute order.

Network Management and Monitoring

  • Possible change is in the object identifier (MX Series and T Series)—The many warnings that occurred previously during MIB loading in the SNMP client has been reduced. This update could change the resulting OID depending on the SNMP client-loading logic. For example, jnxProductACX1000 is defined under the two following nodes:

    • jnxProductACX1000 OBJECT IDENTIFIER ::= { jnxProductVariationACX 1 }

    • jnxProductACX1000 OBJECT IDENTIFIER ::= { jnxProductVariationACX1000 1 }

    Because the second definition is the duplicate, it is removed. If previously, the SNMP client referred to the second OID based on MIB loading logic, then you would see a change in OID for the client.

  • Update to SNMP support of apply-path statement (MX Series)—In Junos OS Release 16.2R2, SNMP implementation for the apply-path configuration statement supports only two lists:

    • apply-path "policy-options prefix-list <list-name> <*>"

      This configuration has been supported from day 1.

    • apply-path "access radius-server <*>"

      This configuration is supported as of this release.

  • MIB buffer overruns can only be counted under ifOutDiscard (MX Series)—Starting in Junos OS Release 16.2R2, qdrops (buffer overruns) are no longer counted under ifOutErrors along with ifOutDiscards. This contradicted RFC 2863, where buffer overruns should only be counted under ifOutDiscards and not under ifOutErrors.

  • SNMP syslog messages changed (MX Series)—In Junos OS Release 16.2R2, two misleading SNMP syslog messages were rewritten to accurately describe the event:

    • OLD --AgentX master agent failed to respond to ping. Attempting to re-register

      NEW –- AgentX master agent failed to respond to ping, triggering cleanup!

    • OLD –- NET-SNMP version %s AgentX subagent connected

      NEW --- NET-SNMP version %s AgentX subagent Open-Sent!

    [See the MIB Explorer.]

  • Improved usage of wildcard in SNMP notify-filter OID (MX Series)—In Junos OS Release 15.1R7, the filter subtree using an asterisk (*) is correctly read as a wildcard character and not as an ASCII value of 42. This issue previously occurred in the following routers:

    • M Series running Junos OS Release 11.4R13.5, 13.3R7-S1

    • ACX2000 Series running Junos OS Release 12.3X54-D20.9

    • MX Series running Junos OS Release 14.1X50-D125

    A sample of the change appears in the output of the show snmp v3 command:

    Old Output

    New Output

    [See the SNMP MIB Explorer.]

  • Enhancement to SMNPv3 traps for contextName field (MX Series)—Starting in Junos OS Release 16.2R2 and Release 17.2, the contextName field in SNMPv3 traps generated from a non-default routing instance, is populated with the same routing-instance information as is given in SNMPv2 traps. SNMPv2 traps provide the routing-instance information as context in the form of context@community. This information gives the network monitoring system (NMS) the origin of the trap, which is information it might need. But in SNMPv3, until now, the contextName field was empty. For traps originating from a default routing instance, this field is still empty, which now indicates that the origin of the trap is the default routing instance.

    See SNMP MIB Explorer.

  • Juniper MIBs Loading Errors Fixed (MX Series)—In junos OS Release 16.2R1, duplicated entries and errors while loading MIBs on ManageEngine MIB browser are fixed for the following MIB files:

    • jnx-gen-set.mib

    • jnx-ifotn.mib

    • jnx-optics.mib

    [See MIB Explorer.]

Operation, Administration, and Maintenance (OAM)

  • Change in behavior of the Ethernet OAM CFM process (MX Series)—When you deactivate the connectivity fault management (CFM) protocol, the CFM process (cfmd) stops. When you activate the CFM protocol, cfmd starts.

    Prior to Junos OS Release 16.1R1, when you deactivate the CFM protocol, the CFM process continues to run.

  • Change in status of CFM sessions (MX Series with MPCs)—Starting in Junos OS Release 16.2R1, for connectivity fault management (CFM) up MEP sessions on trunk interfaces, when the physical link is down and if the router's network service mode is configured as enhanced-ip, the local CFM session fails and the status of the CFM session displays Failed.

    In releases before Junos OS Release 16.2R1, when the physical link is down, the local CFM session does not fail and the status of the CFM session displays OK.

Platform and Infrastructure

  • The length of TACACS messages allowed on Junos OS devices has been increased from 8150 to 65535 bytes. PR1147015

  • Improvements to MIB validation during Junos OS build (libjsnmp) (MX Series and T Series)—Many warnings can be ignored if produced while MIBs are compiling. The following are some warnings should be considered errors because they can break the build:

    [0-9]:.*failed to locateAn OID that has failed to be located.
    [0-9]:.*redefinition of identifierRedefinition of OIDs found in jnx-chas-defines.
    [0-9]:.*sequence-type-mismatchType mismatch found in sequence syntax of the table and actual OID type.
    [0-9]:.*cannot be imported from moduleMIB failed to import because order is not being defined properly.

Routing Protocols

  • Option to display routing instance table in the show route advertising-protocol output—Beginning with Junos OS Release 16.2, you can use the show route advertising-protocol table foo command to display the routing instance table for any address family on a VPN route reflector, or a VPN AS boundary router that is advertising local VPN routes . However, if you do not specify the table in the command, the output displays each VRF prefix twice.

  • Timers of delay-route-advertisements are modified—Beginning with Junos OS Release 15.1F7, the range of the timer values of delay-route-advertisements has been increased to 36000 from 3600. The default value of route age, that is the maximum delay after route aggregates have been created has also been modified to 0. In earlier Junos releases, the default route age was 1200. The timer values of delay-route-advertisements are configured to avoid premature route advertisements that might result in traffic loss in a BGP session.

    [See delay-route-advertisements.]

  • Change in default behavior of router capability (MX Series)—Starting in Junos OS Release 15.1F7, 16.1R4, 16.2R2, 16.1X65, and 17.1R1 and later , router capability TLV distribution flag (S-bit), which controls IS-IS advertisements, will be reset, so that the segment routing capable sub-TLV is propagated throughout the IS-IS level and not advertised across IS-IS level boundaries.

Services Applications

  • Change in option name to configure inactive timeout for IKE ALG child sessions (MX Series)—Starting in Junos OS Release 16.2R1, the name of the option to configure the inactive timeout for Internet Key Exchange (IKE) application-level gateway (ALG) child sessions is changed from child-session-timeout to child-inactivity-timeout.

  • Deprecated security idp statements (MX Series)—Starting in Junos OS Release 16.2R2 and earlier, the [edit security idp] configuration statements are deprecated for the MX Series.

  • Change in behavior of IKE negotiation (MX Series)—Starting in Junos OS Release 16.2R2, when you commit an IPsec configuration that includes establish-tunnels immediately at the [edit services ipsec-vpn] hierarchy level, the service set might take up to 30 seconds to initiate IKE negotiations.

Subscriber Management and Services

  • Configuring a pseudowire subscriber interface for a logical tunnel (MX Series)—Starting in Junos OS release 16.1R2, you can configure a pseudowire subscriber interface and anchor it to a logical tunnel interface without explicitly specifying the tunnel bandwidth. In earlier releases, if you do not explicitly specify the tunnel bandwidth, or the tunnel bandwidth is anything other than 1G or 10G, the pseudowire interface is not created.

  • Change in range for PPP keepalive interval (MX Series)—Starting in Junos OS Release 16.2, you can configure the PPP keepalive interval for subscriber services in the range 1 second through 600 seconds. Subscriber PPP keepalives are handled by the Packet Forwarding Engine. If you configure a value greater than 600 seconds, the number is accepted by the CLI, but the Packet Forwarding Engine limits the interval to 600 seconds. The interval is configured in a PPP dynamic profile with the interval statement at the [edit dynamic-profiles profile-name interfaces pp0 unit $junos-interface-unit keepalives] hierarchy level.

    In earlier Junos OS releases, the range is from 1 second through 60 seconds. The Packet Forwarding Engine limits any higher configured value to an interval of 60 seconds.

    PPP keepalives for nonsubscriber services are handled by the Routing Engine with an interval range from 1 second through 32,767 seconds.

  • Automatic limit set for transmit window size (MX Series)—Starting in Junos OS Release 16.2, when the LAC receives a receive window size of more than 128 in the Start-Control-Connection-Reply (SCCRP) message, it sets the transmit window size to 128 and logs an Error level syslog message.

    In earlier releases, the LAC accepts any value sent in the Receive Window Size attribute-value pair (AVP 10) from an L2TP peer. Some implementations send a receive window size as large as 65530. Accepting such a large value causes issues in the L2TP congestion/flow control and slow start. The router may run out of buffers because it can support only up to a maximum of 60,000 tunnels.

  • New option to display all pending accounting stops (MX Series)—Starting in Junos OS Release 16.2R2, the brief option is added to the show accounting pending-accounting-stops command. This option displays the current count of pending RADIUS Acct-Stop messages for subscribers, services, and total combined value:

    user@host> show accounting pending-accounting-stops brief
  • DNS servers displayed by the show subscribers extensive command (MX Series)—Starting in Junos OS Release 16.2R2, the output display of DHCP domain name servers (DNS) by the show subscribers extensive command has changed. When DNS addresses are configured at multiple levels, the command displays only the preferred address according to this order of precedence: RADIUS > access profile > global access. The command does not display DNS addresses configured as DHCP local pool attributes.

    DNS addresses from RADIUS appear in the following fields: Primary DNS Address, Secondary DNS Address, IPv6 Primary DNS Address, IPv6 Secondary DNS Address.

    DNS addresses from the access profile or the global access configuration appear in the following fields: Domain name server inet, Domain name server inet6.

    In earlier releases, the command output displays only DHCP DNS addresses provided by RADIUS.

  • Change in display of IPv6 Interface Address field by the show subscribers extensive command (MX Series)—Starting in Junos OS 16.2R2, the show subscribers extensive command displays the IPv6 Interface Address field only when the dynamic profile includes the $junos-ipv6-address predefined variable.

    In earlier releases, the command always displays this field, even when the variable is not in the profile. In this case, the field shows the value of the first address from the Framed-IPv6-Prefix attribute (97).

  • Change to DHCP option 82 suboptions support to differentiate duplicate clients (MX Series)—Starting in Junos OS Release 16.2R2, only the ACI (suboption 1) and ARI (suboption 2) values from the option 82 information are considered when this information is used to identify unique clients in a subnet. Other suboptions, such as Vendor-Specific (suboption 9), are ignored.

  • Default L2TP resynchronization method changed and statement deprecated (MX Series)—Starting in Junos OS Release 16.2R2, the default resynchronization method for L2TP peers in the event of a control connection failure is changed to silent failover. In earlier releases, the default method is failover-protocol-fall-back-to-silent-failover. The silent failover method is preferred because it does not keep tunnels open without traffic flow, waiting for the failed peer to recover and resynchronize. You can use the new failover-resync statement at the [edit services l2tp tunnel] hierarchy level to specify either failover protocol or silent failover as the resynchronization method.

    Because silent failover is now the default, the disable-failover-protocol statement is no longer needed and has been deprecated. If you upgrade to this release with a configuration that includes this statement, it is supported, but the CLI notifies you that it is deprecated.

  • Traffic shaping and L2TP tunnel switches (MX Series)—Starting in Junos OS Release 16.2R2, when a dynamic profile attaches a statically configured firewall filter to an L2TP tunnel switch (LTS) session, the filter polices traffic from the LTS (acting as a LAC) to the ultimate endpoint L2TP network server (LNS),, in addition to the previously supported traffic from the LAC to the LTS (acting as an LNS). In previous releases, the firewall filter applied to only the traffic from the LAC to the LTS.

  • Change in display of IPv6 Interface Address field by the show subscribers extensive command (MX Series)—Starting in Junos OS 16.2R2, the show subscribers extensive command displays the IPv6 Interface Address field only when the dynamic profile includes the $junos-ipv6-address predefined variable.

    In earlier releases, the command always displays this field, even when the variable is not in the profile. In this case, the field shows the value of the first address from the Framed-IPv6-Prefix attribute (97).

  • Change in display of IPv6 Interface Address field by the show subscribers extensive command (MX Series)—Starting in Junos OS 16.2R2, the show subscribers extensive command displays the IPv6 Interface Address field only when the dynamic profile includes the $junos-ipv6-address predefined variable.

    In earlier releases, the command always displays this field, even when the variable is not in the profile. In this case, the field shows the value of the first address from the Framed-IPv6-Prefix attribute (97).

  • IPv6 Link Local Addresses Assigned to Underlying Static Demux Interfaces (MX Series)—Starting in Junos OS Release 16.2R2, when you are using Router Advertisement for IPv6 subscribers on dynamic demux interfaces that run over underlying static demux interfaces, configure the software to use the same link-local address for both interfaces. In this case, the link-local address for the underlying interface should be based the MAC address of the underlying interface. The following statement causes the system to assign an address using the 64-bit Extended Unique Identifier (EUI-64) as described in RFC 2373:

  • Change in display of IPv6 Interface Address field by the show subscribers extensive command (MX Series)—Starting in Junos OS 16.2R2, the show subscribers extensive command displays the IPv6 Interface Address field only when the dynamic profile includes the $junos-ipv6-address predefined variable.

    In earlier releases, the command always displays this field, even when the variable is not in the profile. In this case, the field shows the value of the first address from the Framed-IPv6-Prefix attribute (97).

  • Memory mapping statement removed for Enhanced Subscriber Management (MX Series)— In Junos OS Release 17.3R1, use the following command when configuring database memory for Enhanced Subscriber Management:

    set system configuration-database max-db-size

    CLI support for the set configuration-database virtual-memory-mapping process-set subscriber-management command has been removed to avoid confusion. Using the command for subscriber management now results in the following error message:

    WARNING: system configuration-database virtual-memory-mapping not supported. error: configuration check-out failed.

    [See Interface Configuring Junos OS Enhanced Subscriber Management for an example of how to use the max-db-size command.]

User Interface and Configuration

  • Integers in configuration data in JSON format are displayed without quotation marks (MX Series and T Series)—Starting in Junos OS Release 16.2R2, integers in Junos OS configuration data emitted in JavaScript Object Notation (JSON) format are not enclosed in quotation marks. Prior to Junos OS Release 16.2R2, integers in JSON configuration data were treated as strings and enclosed in quotation marks.

  • Changes to the XML and JSON output when displaying the differences between the candidate and active configurations (MX Series)—Starting in Junos OS Release 16.2R2, when you compare the candidate and active configurations and display the differences in XML or JSON format, for example by using the show | compare | display (json | xml) CLI command or the <get-configuration compare="rollback" format="(json | xml)"> RPC, the device omits the <configuration> tag in the XML output and omits the configuration object in the JSON output if the comparison either returns no differences or if the comparison returns differences for only non-native configuration data, for example, configuration data associated with an OpenConfig data model.

VLAN Infrastructure

  • ACI and ARI from PADI messages included in Access-Request messages for VLAN authentication (MX Series)—Starting in Junos OS Release 16.2, when the PPPoE PADI message includes the agent circuit identifier (ACI), agent remote identifier (ARI), or both, these attributes are stored in the VLAN shared database entry. If the VLAN needs to be authenticated, then these attributes are included in the RADIUS Access-Request message as DSL Forum VSAs 26-1 and 26-2, respectively (vendor ID 3561). The presence of these attributes in the Access-Request enables the RADIUS server to act based on the attributes.

VPNs

  • Support for ping on a virtual gateway address—Starting in Junos OS Release 16.2R2, Junos supports pinging an IPv4 or IPv6 address on the preferred virtual gateway interface. To set up support for ping, you must include both the virtual-gateway-accept-data and the preferred statements at the [edit interfaces irb unit] hierarchy of the preferred virtual gateway. This enables the interface on the preferred virtual gateway to accept all packets for the virtual IP address, including ping packets.