Juniper Network & Security Lifecycle Services

Juniper platforms and services we cover

ENCSE is a Juniper partner in India. That page covers the product portfolio and procurement; this one covers lifecycle services on equipment you already run.

Junos upgrade path determination

The single most important question in a Junos upgrade is which path is actually supported from where you are. Junos releases fall into different categories with different support durations, and moving between distant versions frequently requires intermediate hops rather than a direct jump. Determining the correct path is not something to work out during the window — it changes how long the change takes, how many reboots are involved, and what the rollback position looks like at each stage.

Storage is the second recurring constraint, particularly on branch SRX platforms that have been in service for several years. Junos images are substantial, and a device that has accumulated logs, dumps and previous software packages may not have room for the target image. Cleaning up storage is straightforward but has to happen before the window rather than during it.

Chassis clusters add sequencing requirements. A healthy cluster can usually be upgraded with limited service impact by taking one node at a time, but this depends on the cluster being genuinely synchronised and on the versions involved supporting the in-service approach. Verifying cluster health, checking for existing system alarms and confirming the configuration is committed and synchronised are all pre-change work.

Our Junos upgrade sequence

1. Version & hardwareCurrent Junos version, platform model and hardware revision established, along with the recommended target version for your requirements.
2. Storage & alarmsStorage headroom verified against the target image size, and any existing system alarms investigated before they are compounded by a change.
3. EntitlementSoftware entitlement confirmed so the required image can actually be obtained.
4. Path determinationSupported upgrade path established, including any intermediate versions required between current and target.
5. BackupFull configuration capture verified as complete and restorable, and rollback image confirmed present where storage permits.
6. Upgrade & validateExecution in the agreed window with cluster sequencing where applicable, followed by service validation — routing adjacencies, security policy, VPN tunnels and management reachability.

Supported platforms

Supported platforms include the SRX300 series and other supported Juniper SRX platforms, EX campus switching, QFX data centre switching and MX routing — subject in each case to hardware lifecycle status, Junos version compatibility and software entitlement. Rather than publishing a page per model, we assess the specific devices in your estate during the upgrade assessment and confirm precisely what is supportable for your hardware and entitlement position.

Frequently asked questions

How do I determine the correct Junos upgrade path?

It depends on your current version, target version and platform. Junos release categories carry different support durations, and distant version jumps frequently require intermediate hops rather than a direct upgrade. Our assessment establishes the supported path for your specific devices, including how many stages are involved and what the rollback position is at each one.

Can you upgrade an SRX chassis cluster without downtime?

In many cases the impact can be limited substantially by upgrading one node at a time with validation between, though this depends on cluster health and on whether the versions involved support the in-service approach. Some major-version transitions require both nodes on the same version and cannot be staged. The assessment establishes which case applies before a window is agreed.

What checks do you run before an SRX upgrade?

Current version and hardware revision, available storage against the target image size, existing system alarms, configuration commit and cluster synchronisation state, software entitlement, and the supported upgrade path. Storage in particular is a frequent blocker on branch SRX devices that have been in service several years and accumulated logs and old packages.

Do you support SRX300 series devices?

Yes. Supported platforms include the SRX300 series and other supported Juniper SRX platforms, subject to hardware lifecycle status, Junos compatibility and software entitlement. We confirm the position for your specific devices during assessment rather than assuming from the model number alone.

Can you upgrade Juniper devices without a support contract?

Downloading current Junos images generally requires active entitlement on the device. Verifying this is part of the assessment, and where entitlement has lapsed we will set out the options — including that a support renewal is sometimes the least expensive route to closing the exposure you are trying to address.

Related services

• Juniper Partner India
• Firewall Upgrade Services
• Network Switch Upgrade
• EOL / EOS Management
• Request an Upgrade Assessment