If you are managing an SRX345 deployment, the first step is to identify whether the lifecycle concern applies to the firewall hardware, a Junos-related license, or a Security Director Cloud software SKU. This distinction affects support planning, spare-hardware decisions, replacement timing, and migration requirements. You can also review the SRX345 product page before preparing a replacement request.
Is the Juniper SRX345 End of Life?
The answer depends on the exact SKU. The Juniper model name “SRX345” can refer to the firewall hardware, a complete system SKU, or a software and security-service license. These products do not necessarily share the same lifecycle dates.
Juniper's official SRX Series lifecycle table lists several SRX345-related Security Director Cloud software license SKUs as End of Life. The current listing identifies the following milestone information:
| Lifecycle item | Information | What it means |
|---|---|---|
| Product type | Security Director Cloud software license | It is not the same as the SRX345 firewall chassis. |
| Affected license SKUs | S-SD-SRX345-S-C-1, S-SD-SRX345-S-C-3, S-SD-SRX345-S-C-5 | Verify whether one of these SKUs is installed or included in the current contract. |
| EOL announced | April 15, 2024 | The affected software licenses entered the formal EOL process. |
| Last order date | October 15, 2024 | The listed last order date has already passed. |
| End of Support | Refer to TSB76687 | Confirm the applicable support position for the specific license and contract. |
This software lifecycle information does not automatically establish that every SRX345 hardware SKU is EOL. Confirm the exact device label, system SKU, software license, and support contract before deciding whether to replace the firewall.
Which SRX345 SKUs Are Affected?
The most important procurement step is to separate SRX345 software and service licenses from SRX345 hardware and system SKUs.
| SKU or SKU family | Product type | Procurement consideration |
|---|---|---|
| S-SD-SRX345-S-C-1 | Security Director Cloud software license | Check the EOL milestone and replacement management option. |
| S-SD-SRX345-S-C-3 | Security Director Cloud software license | Confirm the existing contract and license term. |
| S-SD-SRX345-S-C-5 | Security Director Cloud software license | Verify whether the license is still required for the deployment. |
| SRX345-SYS-JB | SRX345 hardware/system SKU | Confirm hardware support, software bundle, and power configuration. |
| SRX345-SYS-JE | SRX345 hardware/system SKU | Verify the included Junos software and security features. |
| SRX345-SYS-JB-2AC or SRX345-SYS-JB-DC | Power-specific system variants | Check dual-AC or DC power requirements before selecting a replacement. |
If your current configuration uses the SRX345-SYS-JB system configuration , do not replace it based only on the “SRX345” family name. Confirm the power type, Mini-PIM modules, installed licenses, and required interfaces.
What Does the SRX345 Provide?
The SRX345 is a 1U security gateway designed for distributed enterprise branch deployments. The published hardware configuration includes eight 1GbE RJ-45 ports, eight 1GbE SFP ports, one management port, and four Mini-PIM slots.
The official SRX300 Line Firewall datasheet lists firewall performance of up to 5 Gbps for the SRX345 platform. Review the official SRX345 datasheet before comparing throughput, ports, power, and expansion requirements.
SRX345 Replacement Options
There is no universal one-to-one replacement for every SRX345 deployment. The correct option depends on the firewall role, port requirements, VPN throughput, Mini-PIM usage, power environment, security services, and future capacity requirements.
| Option | Suitable scenario | Checks before selection |
|---|---|---|
| Continue with the existing SRX345 | The current topology must remain unchanged temporarily. | Verify the exact hardware SKU, support contract, software license, and spare requirements. |
| Evaluate the SRX380 | The deployment needs higher port density or 10GbE connectivity. | Check 1GbE PoE+ ports, 10GbE SFP+ ports, Mini-PIMs, power, Junos, and chassis-cluster requirements. |
| Evaluate another SRX platform | The current firewall requires higher VPN throughput, more sessions, or a longer-term capacity plan. | Compare performance, interfaces, security features, lifecycle, licensing, and migration effort. |
Juniper describes the SRX380 platform as a 1U firewall with 16 PoE-enabled 1GbE ports and four 10GbE SFP+ ports. It may be a candidate for deployments that need higher interface density, but it should not be described as an automatic SRX345 successor.
Send the exact SKU and migration requirements.
SRX345 Migration Planning Checklist
A successful SRX345 replacement requires more than matching the number of Ethernet ports. Complete the following checks before approving a migration design.
1. Record the Exact Hardware and License SKUs
- Record the chassis label and complete system SKU.
- Record the software, security-service, and support license SKUs.
- Document the current Junos OS release and support contract.
- Confirm whether the device uses single AC, dual AC, or DC power.
2. Map Interfaces and Mini-PIM Modules
- Document active RJ-45 and SFP interfaces.
- Record Mini-PIM models and WAN circuit types.
- List installed optics, cables, and transceivers.
- Check whether the replacement supports the required interface speed and connector type.
- Confirm rack depth, airflow, power-feed type, and cable length.
3. Review Security and Routing Features
- Review NAT, IPsec VPN, OSPF, BGP, VLAN, and Layer 3 routing requirements.
- Document security policies, application security, URL filtering, and threat-prevention features.
- Confirm concurrent-session, VPN-throughput, and new-session requirements.
- Check whether the current deployment uses chassis clustering or high availability.
4. Prepare Configuration, Cutover, and Rollback
- Back up the current configuration and record interface, routing, VPN, and management settings.
- Prepare a port-by-port mapping table for the replacement platform.
- Test security policies, NAT rules, VPN tunnels, and routing behavior before production cutover.
- Define a maintenance window and rollback configuration.
- Verify the target Junos release and feature compatibility before migration.
Do not assume that a higher-capacity SRX platform can use the existing configuration without changes. Interface names, security features, license requirements, chassis-cluster settings, and WAN modules may need to be reviewed or reconfigured.
SRX345 EOL and Replacement FAQs
These questions help separate an actual hardware lifecycle issue from a software or licensing lifecycle issue.
Final Takeaway
The SRX345 EOL question cannot be answered by the model name alone. First identify whether the affected item is the firewall hardware, a Junos-related license, or a Security Director Cloud software SKU. Then compare replacement platforms by interfaces, Mini-PIMs, power, throughput, security features, software compatibility, and lifecycle requirements.
For a configuration-specific review, you can send your exact SRX345 SKU and migration details for replacement planning and quotation review.