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 

No index entries found.

Known Issues

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

  • In a scaled deployment, an interface of a network service that uses the vSRX VNF might not obtain an IP address through DHCP.

    Workaround: Restart the srxpfe process. PR1148336

  • In a scaled deployment, vSRX VNFs may drop DHCP acknowledgements if the DHCP server responds with a short lease time.

    Workaround: Set the DHCP retransmission interval for the vSRX to a value greater than 30 seconds. PR1148363

  • In a scaled deployment, if you update a network service instance, VNF manager may fail to activate new instances of the network service.

    Workaround: Retry the update operation. PR1148717

  • When the vSRX 2.0 VNF is initializing, it may enter debug mode.

    Workaround: At the db prompt, enter the panic command. The vSRX restarts and initializes correctly. PR1148730

  • When you use vSRX 2.0 VNF with Contrail 2.2.1, NETCONF operations, such as those between the Junos Space Virtual Appliance and the vSRX, may cause the Junos OS sshd process to terminate and generate a core file.

    Workaround: Monitor the vSRX VNF with Service and Infrastructure Monitor. If you see error messages indicating that the Junos Space Virtual Appliance cannot configure the VNF, restart the VNF. PR1152434

  • In a scaled deployment, when the VIM activates multiple heat stacks for network services, the contrail-svc-monitor process may persist in the initialization state.

    Workaround: Restart the network service. PR1527945

  • In a scaled deployment, the Contrail vRouter agent may terminate.

    Workaround: Restart the vRouter agent. PR1528106

Modified: 2016-02-01