Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
[+] Expand All
[-] Collapse All

No index entries found.

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 15.1F4 for the MX Series and T Series.


  • Inline BFD support on IRB interfaces (MX Series routers with MPCs or MICs)—Starting with Junos OS Release 15.1F4, the inline BFD sessions transmitted or received from FPC hardware are supported on integrated routing and bridging (IRB) interfaces. This enhancement is available only on MX Series routers with MPCs/MICs that have configured the enhanced-ip option.

Network Management and Monitoring

  • New 64-bit Counter of octets for interfaces (M Series, MX Series, and T Series)—Starting with Release 15.1F4, Junos OS supports two new Juniper Networks enterprise-specific Interface MIB Extension objects—ifHCIn1SecOctets and ifHCOut1SecOctets—that act as 64-bit counters of octets passing through an interface.

Subscriber Management and Services (MX Series)

Note: Although present in the code, the subscriber management features are not supported in Junos OS Release 15.1F4. Documentation for subscriber management features is included in the Junos OS Release 15.1 documentation set.

  • Local DNS configurations available when authentication order is set to none (MX Series)—Starting in Junos OS Release 15.1F2, subscribers get the DNS server addresses when both of the following are true:
    • The authentication order is set to none at the [edit access profile profile-name authentication-order] hierarchy level.
    • A DNS server address is configured locally in the access profile with the domain-name-server, domain-name-server-inet, or domain-name-server-inet6 statement at the [edit access profile profile-name] hierarchy level.

    In earlier releases, subscribers get an IP address in this situation, but not the DNS server addresses.

  • Support for longer CHAP challenge local names (MX Series)—Starting in Junos OS Release 15.1F4, the supported length of the CHAP local name is increased to 32 characters. In earlier releases, only eight characters are supported even though the CLI allows you to enter a longer name. You can configure the name with the local-name statement at the [edit dynamic-profiles profile-name interfaces pp0 unit “$junos-interface-unit” ppp-options] or [edit dynamic-profiles profile-name interfaces "$junos-interface-ifd-name" unit “$junos-interface-unit” ppp-options] hierarchy levels. The maximum length of the local name for PAP authentication remains unchanged at eight characters.


  • Clear all Internet key exchange (IKE), traffic encryption key (TEK), key encryption key (KEK) security associations (SAs) for group VPN (MX Series)—The clear security group-vpn member group CLI command has been introduced in the Release 15.1F3 of Junos OS for MX Series routers to clear all Internet key exchange (IKE), traffic encryption key (TEK), key encryption and key (KEK) security associations (SAs) for a group VPN.
    user@host> clear security group-vpn member group

Related Documentation

Modified: 2016-04-20