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 

Known Behavior

This section describes certain SRC software behaviors and related issues to clarify how the system works.

For the most complete and latest information about known defects, use the Juniper Networks online Problem Report Search application.

Aggregate Services

  • NIC does not map primary username to managing SAE in aggregate services.

    If you use aggregate services and specify a primary username for a subscriber reference expression, note that the configuration scenarios provided with the NIC do not provide a mapping from a primary username to the managing SAE. Consider using the login name instead. If you want to use the primary username as the subscriber reference expression for a fragment service, contact Juniper Networks Professional Services for assistance with setting up the NIC configuration to resolve the primary username to locate the managing SAE.

Configuration Updates

  • When you use the load merge, load override, or load replace command at any hierarchy level, the command loads all the configuration in the specified file.

    If you want to load the configuration for a specified hierarchy level:

    • Ensure that the file contains the sdx:current=true text to identify the level at which the configuration is to be loaded.
    • Run a load command with the relative option at the level at which you want to update the configuration.

    If a file contains configuration statements other than those at and below the level identified by sdx:current=true, the command disregards the other statements.

    If you enter a load command with the relative option and the file does not contain the text sdx:current=true, you receive a message indicating that the configuration cannot be loaded.

Hardware

  • From Release 4.8.0 onwards, the SRC software runs on CentOS 6.5. However, this operating system does not support older C series controllers (C2000 and C4000) because of hardware incompatibility. PR1049794

Juniper Networks Database

  • Recommendations for use of multiple primary Juniper Networks databases.

    We recommend that you configure two to four Juniper Networks databases as primary databases in a community. If you plan to use more than two Juniper Networks databases in a primary role and expect to have frequent updates to the Juniper Networks database, we recommend that you test your application scenario with a projected traffic load. For assistance testing your application scenario, contact Juniper Networks Professional Services or JTAC.

Memory Test Utility

  • From Release 4.8.0 onwards, the SRC software does not support the memory test utility. Hence, the boot menu in SRC Release 4.8.0 and later does not display the option for memory test utility. In addition, you cannot execute the memory test utility in SRC Release 4.7.0 and earlier even though the utility option is displayed in the boot menu if you have restored SRC to Release 4.7.0 and earlier from Release 4.8.0 and later.

    We recommend that you use a bootable USB storage device for executing the memory test utility. To test the SRC system memory using the memory test utility:

    1. Download the memtest86-usb.img image file to your Linux workstation from the http://www.memtest86.com/download.htm link.
    2. Insert your USB storage device into the USB port on your Linux workstation.
    3. Determine the system device of your USB storage device by executing the fdisk -l command.
    4. Copy the downloaded image onto your USB storage device by using the dd command. For example, if sda is the system device of the USB storage device then the dd command should be executed as:

      dd if=/tmp/memtest86-usb.img of=/dev/sda

    5. Remove the USB storage device from the Linux workstation.
    6. Plug the USB storage device into the USB port on the SRC system.
    7. Restart the SRC system.
    8. Change the boot order to boot from the USB storage device while the SRC system is rebooting.

MIBs

Policy Management

  • Use care when modifying configurations with other policy management tools for interfaces on JunosE routers that are managed by the SRC software.

    When applying policies to interfaces on JunosE routers that are managed by the SRC software, carefully consider using other policy management tools, such as CLI, RADIUS, CoA, or Service Manager. Policies that are applied to the interface before SRC management begins, such as at access-accept time, are properly replaced. However, if other policy managers change existing policies while SRC management is active, problems can occur.

    • If you have a preconfigured policy through CLI or RADIUS as part of subscriber PVC/VLAN provisioning, the existing policy becomes inactive and the SAE manages the subscriber interface. When the SAE stops managing the interface, the preconfigured policy becomes active. However, if you change the policy on the interface using CLI or CoA, problems can occur.
    • If you have a policy in Access-Accept, the existing policy becomes inactive and the SAE manages the interface.

SAE

  • When you configure an interface classifier rule under the [edit shared classification-script interface classifier] hierarchy level, the changes do not take effect immediately on the SRC software. For a workaround, see the PR record. PR973224
  • When policies are installed via RAR, service mismatch between SRC and SCG occurs if there are partial charging rule install failures at SCG side. PR1127708

Software Upgrade

  • Unsupported class version error is displayed while upgrading SRC release 4.9.0 to 4.10.0. PR1180633

VTA

  • In SRC 4.1 and earlier software releases, the SRC VTA provided a public Enterprise Java Bean (EJB)-based API. In the SRC 4.2.x software release, this API has been deprecated. It may be removed in a future release. In SRC 4.2.0 and later software releases, the EJB-based API has been replaced with a SOAP API that provides the same functionality.

Modified: 2016-06-03