Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    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 17.1R1 for MX Series routers.

    Interfaces and Chassis

    • Support for maximum queues configuration on MPC7E, MPC8E, and MPC9E (MX Series)—You can configure the maximum number of queues per MPC on MPC7E, MPC8E, and MPC9E. By default, these MPCs operate in per port queuing mode.

      You can use the set chassis fpc slot-number max-queues queues-per-line-card command to configure number of queues per MPC. The possible values for queues-per-line-card are 8k, 16k, 32k, 64k, 128k, 256k, 512k, or 1M.

      Per-unit scheduling and hierarchical queuing on MPC7E, MPC8E, and MPC9E are licensed features.

      You cannot configure the max-queues and the flexible-queuing-mode statements at the same time. You use the flexi-queuing-mode statement to configure a maximum of 32,000 queues per MPC.

      If the max-queues statement is not configured, which is the default mode, the MPC starts with a message similar to the following:

      FPC 0 supports only port based queuing. A license is required for per-VLAN and hierarchical features.

      If the max-queues statement is configured and the value is less than or equal to 32,000, the MPC starts with a message similar to the following:

      FPC 0 supports port based queuing and is configured in 16384 queue mode. A limited per-VLAN queuing license is required for per VLAN and hierarchical queuing features.

      If the max-queues statement is configured and the value is greater than 32,000, the MPC starts with a message similar to the following:

      FPC 0 supports port based queuing and is configured in 524288 queue mode. A full scale per-VLAN queuing license is required for per VLAN and hierarchical queuing features.

      [See Understanding Hierarchical Scheduling for MIC and MPC Interfaces
      and Flexible Queuing Mode Overview.]

    Junos OS XML API and Scripting

    • XML output change for show subscribers summary port command (MX Series)—Starting in Junos OS Release 17.1R1, the display format changed for the show subscribers summary port command to make parsing the output easier. The output is displayed as in the following example:
      user@host> show subscribers summary port | display xml
      <rpc-reply xmlns:junos="http://xml.juniper.net/junos/17.1R1/junos">
          <subscribers-summary-information xmlns="http://xml.juniper.net/junos/16.1R2/junos-subscribers">
              <counters junos:style="port-summary">
                  <port-name>ge-1/2/0</port-name>
                  <port-count>1</port-count>
               </counters>
              <counters junos:style="port-summary">
                  <port-name>ge-1/2/1</port-name>
                  <port-count>1</port-count>
               </counters>
      </rpc-reply>

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

      user@host> show subscribers summary port | display xml
      <rpc-reply xmlns:junos="http://xml.juniper.net/junos/16.1R2/junos">
          <subscribers-summary-information xmlns="http://xml.juniper.net/junos/16.1R2/junos-subscribers">
              <counters junos:style="port-summary">
                  <port-name>ge-1/2/0</port-name>
                  <port-count>1</port-count>
                  <port-name>ge-1/2/1</port-name>
                  <port-count>1</port-count>
              </counters>
      </rpc-reply>

    LDP

    • Importing IS-IS tag value into LDP—When a tag value is assigned to an IS-IS route, the IS-IS tag value is imported and used by LDP while installing the route in the inet.3 and mpls.0 routing tables if the track-igp-metric command is configured. This enables policy configuration to be applied on the inet.3 and mpls.0 routing tables based on the imported tag value.

    Management

    • Enhancement to Junos Telemetry Interface (MX Series)—Starting with Junos OS Release 17.1R1, Junos Telemetry Interface data streamed through gRPC no longer includes the phrase oc-path in the prefix field. For example, a physical interface sensor streaming data for interface et-0/0/0:0 now displays the following output: str_value:/interfaces/interface[name='et-0/0/0:0']/.

    Multiprotocol Label Switching (MPLS)

    • Representation for OSPF DR node—Up until version -10 of the BGP-LS draft, the OSPF DR node representation was ambiguous. One could represent DR node as 'AdvertisingRouterId-InterfaceIpAddress' or 'InterfaceIpAddress-1'. JUNOS used to follow 'InterfaceIpAddress-1' format. Starting with version '-11' of the BGP-LS draft, the representation for OSPF DR node must be 'AdvertisingRouterId-InterfaceIpaddress'. Junos OS now follows the latest format.

    • PPPoE subscribers do not bind over ps interfaces—Starting with JUNOS OS Release 17.1R1, the termination of single, multiple, and dual-tagged service delimited vlans are transported over a single ethernet-ccc pseudowire using ps virtual port devices. This feature provides scaled layer-3 service application at the pseudowire head-end termination appliance. This behavior is as an extension and evolution for ethernet pseudowire that is described in RFC 4448.

    Network Management and Monitoring

    • SNMP syslog messages changed (MX Series)—Starting in Junos OS Release 17.1R1, two misleading SNMP syslog messages have been 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 SNMP MIB Explorer.

    • MIB buffer overruns only be counted under ifOutDiscard (MX Series)---The change done via PR 1140400 Introduced a CVBC where qdrops (buffer overruns) were counted under ifOutErrors along with ifOutDiscards. This is against RFC 2863 where buffer overruns should only be counted under ifOutDiscards and not under ifOutErrors. In Junos OS Release 17.1R1, this is now fixed.

    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 CFM protocol, cfmd starts.

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

    Routing Protocols

    • Optimization of link-state packets (LSPs) flooding in IS-IS (MX Series)—Starting in Junos OS Release 17.1R1, flooding of LSPs in IS-IS no longer occurs as a result of the commitment of configuration changes unrelated to IS-IS. Now, when the router is not in the restart state, every time a new LSP is generated after a CLI commit, the contents of the new LSP are compared to the contents of the existing LSP already installed in the link-state database (LSDB) between Intermediate Systems. When the contents of the two LSPs do not match, the system does not process the new LSP or install it in the LSDB, and consequently does not flood it through the IS-IS network. The new behavior does not affect the rebuilding of LSPs after they refresh in the LSDB. No configuration is required to invoke the new behavior.

      In earlier releases, IS-IS generates new LSPs even when the configuration changes are not related to IS-IS. Because the new LSPs are flooded across the network and synchronized in the LSDB, this flooding process is time-consuming and CPU intensive in a scaled network environment.

    • Range of flow route rate-limit modified—Starting with Junos OS Release 17.1R1, the range of flow route rate-limit has changed from [9600..1000000000000] to [0..1000000000000]. Earlier Junos OS releases had range restrictions for flow route rate-limit at the [edit routing-options flow route flow then] hierarchy level. Junos OS can now accept any configured rate-limit value. If the rate limit is set in the range of 0 through 999, the Packet Forwarding Engine discards the packets. For configured rate limit value between 1000 and 1000000000000, Junos OS sets the corresponding value in kbps as the rate limit.
    • Change in default behavior of router capability (MX Series)—In Junos OS Release 17.1R1 and later releases, the 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

    • Deprecated security IDP statements (MX Series)—In Junos Release 17.1R1 and later releases, [edit security idp] configuration statements are deprecated for the MX Series routers.
    • Device discovery with device-initiated connection (MX Series)—In Junos OS Release 17.1R1 and later releases, when you configure statements and options under the [system services ssh] hierarchy and commit the configuration, make sure that the system reaches a stable state before you commit any outbound-ssh configurations.

      You use the device discovery feature in the Devices workspace to add devices to Junos Space Network Management Platform. By default, Junos Space manages devices by initiating and maintaining a connection to the device.

      [See Device Discovery Overview.]

    Security

    • Packet types added for DDoS protection L2TP policers (MX Series routers with MPCs, T4000 routers with FPC5)—Starting in Junos OS Release 17.1R1, the following eight packet types have been added to the DDoS protection L2TP protocol group to provide flexibility in controlling L2TP packets:

      cdn

      scccn

      hello

      sccrq

      iccn

      stopccn

      icrq

      unclassified

      Previously, no individual packet types were available for this protocol group and all L2TP packets were policed the same based on the aggregate policer value. The default values for the bandwidth and burst policers for all packet types is 20,000 pps. The default recover-time is 300 seconds for each of the L2TP packet types.

      [See protocols (DDoS).]

    • Global configuration for DDoS protection flow detection mode and flow level control (MX Series)—Starting in Junos OS Release 17.1R1, you can configure the mode of operation (on, off, or automatic) for flow detection and tracking globally. You can also configure globally how traffic in culprit flows is handled (drop, keep, or police). Both configurations apply to all protocol groups and packet types in the traffic flow unless overridden by the configuration for a protocol group or packet type for all or some flow aggregation levels.

      In earlier releases, you cannot configure the behavior globally; you can configure the behavior only for individual protocol groups or packet types, or at the individual flow aggregation levels: physical interface, logical interface, or subscriber.

      See Configuring How Flow Detection Operates Globally and Configuring How Traffic in a Culprit Flow Is Controlled Globally.

    Subscriber Management and Services

    • Changes to the test aaa authd-lite user, test aaa dhcp user, and test aaa ppp user commands (MX Series)—Starting in Junos OS Release 17.1R1, the following changes have been made to the test aaa user commands:
      • The Virtual Router Name and Routing Instance fields became the Virtual Router Name (LS:RI) field.
      • The Redirect VR Name field was renamed to Redirect VR Name (LS:RI).
      • The Attributes area in the CLI output header section was renamed to User Attributes.
      • The IGMP field was renamed to IGMP Enable.
      • The IGMP Immediate Leave and the MLD Immediate Leave default values changed from disabled to <not set>.
      • The Chargeable user identity value changed from an integer to a string.
      • The Virtual Router Name field was added to the display for the DHCP client.
      • The commands display only attributes that are supported by Junos OS; these attributes appear even when their values are not set. The Virtual Router Name (LS:RI) field matches the Juniper Networks Virtual-Router VSA (26-1), if present; otherwise, the field displays default:default. The displayed value for all other attributes that are not received is <not set>.

        [See test aaa authd-lite user, test aaa dhcp user, and test aaa ppp user.]

    • interfaces statement restored for ESSM subscriber secure policy (MX Series)—Starting in Junos OS Release 17.1R1, the interfaces statement was undeprecated at the [edit services radius-flow-tap] hierarchy level. When you use subscriber secure policies to mirror ESSM interfaces, you must configure the virtual tunnel (vt) interfaces that are used to send the mirrored packets to a mediation device. In some earlier releases, this statement was erroneously deprecated and hidden.

      [See interfaces (Subscriber Secure Policy).]

    • New option to display all pending accounting stops (MX Series)—Starting in Junos OS Release 17.1R1, the brief option is added to the show accounting pending-accounting-stops command. This option displays the current count of pending RADIUS accounting stop messages for subscribers, services, and total combined stops. The output is displayed as follows:
      user@host> show accounting pending-accounting-stops brief
        Total pending accounting stops: 4
          Subscriber pending accounting stops: 2
          Service pending accounting stops: 2

      [See show accounting pending-accounting-stops brief.]

    User Interface and Configuration

    • Integers in configuration data in JSON format are displayed without quotation marks (MX Series)—Starting in Junos OS Release 17.1R1, integers in Junos OS configuration data emitted in JavaScript Object Notation (JSON) format are not enclosed in quotation marks. Prior to Junos OS Release 17.1R1, integers in JSON configuration data were treated as strings and enclosed in quotation marks.
    • Changes to the show system schema module juniper-command output directory (MX Series)—Starting in Junos OS Release 17.1, when you issue the show system schema module juniper-command operational command in the Junos OS CLI, the device places the generated output files in the current working directory, which defaults to the user’s home directory. Prior to Junos OS Release 17.1, the generated output files are placed in the /var/tmp directory.

    Modified: 2017-04-29