---
name: vmwaresolutions-juniper_managing
title: Managing Juniper vSRX
description: As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
last-updated: 2026-05-26
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vmwaresolutions?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Managing Juniper vSRX
{: #juniper-managing}

As of 17 July 2025, new automated installations of Red Hat® OpenShift® for VMware® are no longer available for new or existing deployments of VMware Cloud Foundation for Classic - Automated instances. You can still use or delete your existing Red Hat OpenShift for VMware automated installations until 16 July 2026. The service will no longer be available from 17 July 2026.
{: deprecated}

To manage the Juniper® vSRX service, you can either:
* Log in to the J-Web Web Client by using the credentials that you can find on the Juniper vSRX service details page.
* Access the console through an SSH connection by using the credentials that you can find on the Juniper vSRX service details page.

For more information, see [Ordering services for VCF for Classic - Automated instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices&format=markdown).

## Juniper vSRX security and ease of use features
{: #juniper-managing-security-enhance}

Juniper vSRX provides various features for security and ease of use on VMware Cloud Foundation for Classic - Automated. The following are some considerations:

* Any Juniper vSRX that is deployed with public access comes with its public interfaces deactivated. The deactivation ensures that the vSRX is not made available to the public internet before users are ready.
* The default deny policy is set to `permit`, so you can identify any necessary flows before you lock down the vSRX traffic.
* It is recommended that you change the default credentials that IBM® created in the service details page for Juniper vSRX, the root, and the admin passwords.
* On gateway cluster installations, protectable VLANs are associated, but not routed, with the edge gateway.

## Considerations when you delete Juniper vSRX
{: #juniper-overview-remove-consider}

Any network operations that rely on routes that are established through vSRX might be affected and require reconfiguration.

## Related links
{: #juniper-managing-related-links}

* [Juniper vSRX overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-juniper-overview&format=markdown)
* [FAQ for VCF for Classic](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions&format=markdown)
* [Getting help and support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support&format=markdown)
* [Juniper vSRX Virtual Firewall](https://buy.hpe.com/us/en/networking/juniper-solutions/juniper-security-solutions/juniper-vsrx-virtual-firewall/p/1014920022){: external}
* [Juniper vSRX Documentation](https://www.juniper.net/documentation/product/us/en/vsrx/){: external}