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 

Release Highlights

Highlights include the following product enhancements:

Note: The SRC software runs on C Series Controllers—a range of hardware platforms. The SRC 4.8.0 software contains the features found in the SRC 4.7.0 release plus the features listed in this section. The SRC 4.8.0 software may contain references to the service activation engine (SAE) Release version 7.14.0. The SRC 4.8.0 software does not run on discontinued C2000 and C4000 controllers because of hardware incompatibility.

Centos Upgrade

The base operating system of SRC software has now been upgraded from Centos 4.9 to Centos 6.5. To migrate to SRC Release 4.8.0, please see Migrating the C Series Controller to Software Release 4.8.0.

SAE Failover Traps Enhanced for Third-Party Device Drivers

The routerConnUp and routerConnDown traps are now enhanced to notify the SAE when the third-party device driver is appointed or dismissed as a master.

VTA Alarm Support for EJB Connection Status and SAE Fail Queue

Whenever the SAE fails to restore the connection to the SRC VTA, events are added to the SAE fail queue of the SRC VTA. The addition of events to the SAE fail queue increases the fail queue size and leads to the consumption of a substantial amount of disk space in the memory partition. The SAE polls the fail queue size at regular intervals (every 90 seconds) and checks the free space in the disk. If the free disk space is less than the configured minimum free disk space value, the SAE stops adding the events to the fail queue. You can use the min-free-diskspace-percentage option under the [edit shared sae group group-name configuration plug-ins vta-failqueue-size-config] hierarchy level to configure the minimum free disk space required to add the events in the fail queue.

The juniSdxSaeVTAFailQueueSize MIB entry is newly introduced to store the sum of all SAE VTA fail queue sizes. In addition to this, the saeVtaFailQueueSize performance trap is introduced to signal the increasing fail queue size of the SRC VTA. To enable the saeVtaFailQueueSize performance trap, configure the saeVtaFailQueueSize option under the edit snmp notify alarm category sae alarm hierarchy level.

The vtaEjbConnectionStatus event trap is newly introduced to signal the EJB connection state changes. You can enable the vtaEjbConnectionStatus event trap by configuring the vtaEjbConnectionStatus option under the edit snmp notify event category sae-plugin hierarchy level.

SRC VTA Performance Statistics Output Specific to an Event Queue, Event Handlers, or Actions

The event-queue, event-handler event-handler-name, and actions action-name options are newly introduced in the show vta statistics performance group name command to view the performance statistics of an event queue, event handlers, or actions separately.

In-Memory Fail Queue Validation During Synchronization of the State Synchronization Plug-in

You can now configure a threshold for the in-memory fail queue size to raise an SNMP event trap by using the fail-queue-size-during-sync fail-queue-size-during-sync option that is newly introduced under the edit shared sae configuration plug-ins state-synchronization hierarchy level. The trap is used to notify about the constant increase in the heap usage due to events stored in the queue. The SRC software adds the events to the queue even after raising the trap.

The newly introduced sspluginSyncFailQueueSize event trap is raised if the plug-in events stored in the in-memory fail queue during synchronization exceeds the configured threshold. If the plug-in events stored in the in-memory fail queue decreases and falls below the configured threshold, the raised sspluginSyncFailQueueSize event trap is cleared.

Monitor Support for VTA Performance Statistics

The SRC software now enables you to monitor SRC VTA group-specific performance statistics of event queue, event handler, and action collectively or separately at an interval by using the newly introduced monitor vta statistics group command.

IPv6 Support for Redirect Server

You can now use the newly introduced redirect-server ipv6-redirect and redirect-server ipv6-redirect https configuration statements to configure the redirect server for handling IPv6 requests. The redirect-server ipv6-redirect statement enables you to define the TCP port on which the redirect server runs. The redirect-server ipv6-redirect https statement enables you to configure the certificate details for HTTPS IPv6 connection and the HTTPS port on which the redirect server runs.

The redirect server uses the other common configuration details (such as request rate, ports configured for IP traffic redirection, and so on) for handling both IPv4 and IPv6 requests.

Extensible Subscriber Services Manager Daemon Support with JSRC for Policy Provisioning

The SRC software includes support for Extensible Subscriber Services Manager Daemon (ESSMD). This feature enables you to provision JSRC policy rules through operation scripts.

Modified: 2015-07-22