Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Known Behavior

 

This section lists known behavior, system maximums, and limitations in hardware and software in Juniper Networks CSO Release 5.3.0.

Device Management

  • The SRX4100 and SRX4200 devices support all existing SD-WAN features, except the following:

    • Phone-home client (PHC)—The devices must be manually activated by copying the stage-1 configuration from the CSO portal, pasting it to the console of the SRX4100 and SRX4200 devices, and then committing the stage-1 configuration.

    • LTE and xDSL interfaces.

  • In a dual SRX Series cluster, the devices must be manually activated by copying the stage-1 configuration from the CSO portal, pasting it to the console of the SRX Series device, and then committing the configuration.

  • LTE and xDSL interfaces are not supported on dual CPE devices.

  • You cannot remotely access a cloud spoke device and edit the configuration.

  • You can intall and use only an external LTE Vodafone K5160 dongle to the NFX250 device.

  • NFX150 is not supported in cluster mode.

  • You cannot use an NFX150 dual CPE device for deploying SD-WAN services.

  • Do not zeroize EX2300 and EX3400 devices as doing so might result in unexpected behavior.

  • PHC is supported for EX2300, EX3400, and EX4300 switches (except EX4300-MP) with Junos OS Release 18.4R2 and later. The CSO release is qualified for Junos OS Release 18.3R1, and the PHC capability is currently not supported for EX Series switches that are onboarded with Junos OS Release 18.3R1.

    If the PHC capability is not supported for EX Series switches, you must manually copy the stage-1 configuration from the CSO portal and paste it to the device console to commit the stage-1 configuration when you create a LAN site or activate an EX Series switch.

  • UTM Web filtering is not supported in an active-active SRX Series cluster device.

Dynamic VPN (DVPN)

  • Creation and deletion of DVPN tunnels based on the DVPN create and delete thresholds are governed by the MAX_DVPN_TUNNELS and MIN_TUNNELS_TO_START_DVPN_DEACTIVATE parameters, respectively. However, MAX_DVPN_TUNNELS and MIN_TUNNELS_TO_START_DVPN_DEACTIVATE are not honored when DVPNs are created or deleted from the CSO UI. This might cause the total active DVPN tunnels count on the Site > WAN tab to show a greater value than the MAX_DVPN_TUNNELS value configured for that site.

  • DVPN create and delete thresholds are based on the APPTRACK_SESSION_CLOSE messages. When APPTRACK_SESSION_CLOSE messages reach the specified threshold, an alarm is generated for creating or deleting a DVPN tunnel. However, the alarms are not cleared until the APPTRACK_SESSION_CLOSE message count goes below the threshold (for create alarms) or above the threshold (for delete alarms) to trigger a fresh cycle. This causes the create and delete alarms to remain active and prevent further alarms and to, thus, slow down the creation or deletion of tunnels.

  • Passive probes created by an SD-WAN policy time out because of inactivity in 60 seconds. This causes CSO to close the corresponding sessions and trigger APPTRACK_SESSION_CLOSE messages. The APPTRACK_SESSION_CLOSE messages are tracked and added to the number of sessions closed. The sessions closed count is used to calculate the DVPN delete threshold.

Policy Deployment

  • An SD-WAN policy deployment is successful even if there is no matching WAN link meeting the SLA. This is expected behavior and it ensures that when a WAN link matching the SLA becomes available, traffic is routed through that link.

  • The policy intents defined for a firewall or an SD-WAN policy must not have conflicts with other policy intents in that policy because such conflicts lead to inconsistent behavior. For example:

    • You cannot define an SD-WAN policy with one policy intent for application X and SLA profile S-1 and another policy intent for application X and SLA profile S-2.

    • You cannot define two firewall policy intents with the same source and destination endpoints but one with action Allow and another with action Deny.

SD-WAN

  • If WAN link endpoints are not of similar type but overlay tunnels are created based on matching mesh tags, the static policy for site-to-site or central Internet breakout traffic gives preference to the remote link type.

  • Advanced SLA configurations, such as CoS rate limiting, are not supported during local breakout if no specific application is selected; that is, if Application is set to ANY. Choose specific applications if you want to enable advanced SLA configurations, such as CoS rate limiting.

  • If two or more SD-WAN policy rules are configured for the same application with different levels of granularity, such as all, sites, and departments, then CSO applies the CoS rate limiter in the same order in which you have created the intents.

  • On the SD-WAN Events page, when you hover the mouse over the Reason field of link switch events, sometimes Above Target is displayed instead of the absolute SLA metric value for very large values (for example, for an SLA metric value that is 100 times the target value).

  • When an SD-WAN policy is deployed and a high rate of traffic flows through the CPE device, this might lead to network congestion and introduce delays or cause traffic loss. However, even though an SLA violation is reported, the traffic does not switch to a different link.

  • If any spoke site in a tenant doesn’t use the Internet breakout WAN link of the provider hub to provision the overlay tunnel, then the site-to-Internet traffic is dropped.

  • Active-Active mode is not supported with cloud breakout for GRE tunnels.

  • ADSL and VDSL are not supported on an NFX250 device running Junos OS Release 18.4R3.3.

SD-LAN

  • When a Virtual Chassis member goes down, the chassis view shows the last known status of the Virtual Chassis member ports until the member is up again.

Site and Tenant Workflow

  • In the Add Site workflow, use IP addresses instead of hostnames for the NTP server configuration. If you are using hostnames instead of IP addresses, ensure that the hostname is DNS-resolvable; if the hostname is not DNS-resolvable, ZTP for the device fails.

  • CSO uses RSA-key-based authentication when establishing an SSH connection to a managed CPE device. The authentication process requires that the device has a configured root password, and you can use Administration Portal to specify the root password in the device template.

    To specify a root password for the device:

    1. Log in to Administration Portal.
    2. Select Resources > Device Templates.
    3. Select the device template and click Edit.
    4. Specify the plain text root password in the ENC_ROOT_PASSWORD field.
    5. Click Save.
  • When you try to deploy a LAN segment on an SRX Series spoke device, the CSO GUI allows you to select more than one port for a LAN segment. However, for SRX Series devices, only one port for a LAN segment can be deployed; multiple ports in a LAN segment can be deployed only on NFX Series devices.

  • On a site with an NFX Series device, if you deploy a LAN segment without the VLAN ID specified, CSO uses an internal VLAN ID meant for internal operations and this VLAN ID is displayed in the LAN section of the Site Detail View page. There is no impact on the functionality.

  • Do not create departments that have names starting with default, default-reverse, mpls, internet, or default-hub because CSO uses the following departments for internal use:

    • Default-vpn_name

    • Default-reverse-vpn_name

    • mpls-vpn_name

    • internet-vpn_name

    • Default-hub-vpn_name

User Interface

  • When you use Mozilla Firefox to access the CSO GUIs, a few pages do not work as expected. We recommend that you use Google Chrome version 60 or later to access the CSO GUIs.

  • When you copy and paste a stage–1 configuration from Chrome version 71.0.3578.98, insert a new line, as shown in the following example, in the private key text:

    If you do not insert the new line, the private key fails.

General

  • On an NFX Series device:

    • To activate a virtualized network function (VNF), perform the following steps:

      1. Add the VNF to the device.
      2. Initiate the activation workflow and ensure that the job is 100% completed.
    • To retry the activation of a VNF that failed, perform the following steps:

      1. Deactivate the VNF.
      2. Remove the VNF.
      3. Add the VNF to the device.
      4. Initiate the activation workflow and ensure that the job is 100% completed.
  • Enterprise hub is not supported for cloud spoke sites.

  • CSO internally uses IP addresses starting from 100.112.0.0 through 100.127.255.255. You must avoid using these IP addresses in LAN and WAN subnets.

  • NFX250 uses some IP addresses in the 192.0.2.0/24 subnet for VNF management. You must avoid using these IP addresses in LAN. For more information on the usage of this subnet, see the NFX250 documentation.

  • VLAN IDs 4050 through 4094 are reserved for CSO configurations.