Known Problems and Limitations
This section identifies known problems and limitations in this release.
For the most complete and latest information about known defects, use the Juniper Networks online Problem Report Search application.
If SRC’s Gy is enabled after the SAE, SRC’s plug-ins are not initialized for certain subscribers. For a workaround, see the PR record. PR1097126
An existing HTTP session will get logged out automatically if you log in to C-Web through HTTPS and then try to log in to C-Web through HTTP in the same browser. For a workaround, see PR1389011.
The scheduler format has been changed, but new attributes (action name, event name, and except name) are not currently supported in Enterprise Manager. PR1325483
Time synchronization is not observed for unauthenticated NTP broadcast client when default restrict commands are configured. For a workaround, see PR1389059.
The kod option under the system ntp restrict address address, system ntp restrict default-v4, and system ntp restrict default-v6 commands may not function properly because there is no option to configure limited requests. The behaviors of nopeer and notrap options have not been tested by Juniper Networks. PR1389024
After changing the VM memory of vSRC, the new SAE heap parameter values are not displayed in the CLI even though the new values are properly allotted to the SAE. For a workaround, see PR1389004.
While upgrading from SRC 4.11R3 release to SRC 4.12.0 release, MIB errors (Bad Format) are displayed. PR1390411
JPS component has been removed from the SRC software but SNMP notify alarm and event configurations related to JPS have not been removed. PR1388388