Hardware Failure

Juniper SRX300 stack member missing: Diagnose & Fix

Q: Where can I find the Juniper official documentation?

https://kb.juniper.net/ — search the product family + feature name.

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance

Vendor	Juniper
Operating system	Junos OS
Category	Hardware Failure
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need JTAC + RMA.

If you have ever stared at a Juniper SRX300 that just refused to come up, you know the muscle memory: serial console at 9600 8N1, wait for the loader> line, hope it actually paints. On Junos OS the first move is always `show version` and `show chassis environment`, if those return cleanly the box is alive enough to talk to you, which is the difference between a ten-minute fix and an RMA paperwork morning.

I keep a small notebook of Juniper part-numbers next to the rack because the LED legend differs between hardware generations. The Junos OS platform tends to tell the truth in `show` output before the front-panel LED catches up, so trust the CLI first.

This guide assumes you have console access and an active JTAC entitlement. If the device is out of warranty, skip straight to the recovery section: most of the steps still apply, you just lose the RMA option at the end.

What this guide covers

Diagnose and recover from stack member missing on a Juniper SRX300.

Step-by-step

Run the stack / chassis status command to see member states.
Inspect the stack cables, re-seat both ends.
Try replacing one stack cable at a time to identify a bad cable.
Power-cycle the affected member if cables are good.
If the member still doesn't rejoin, RMA it.

CLI / commands

# Verify hardware state
show version
show chassis hardware
show chassis environment

# Collect for JTAC
request support information | save /var/tmp/rsi.txt

When to RMA

Repeated failure after re-seat and power-cycle
Visible burn, scorching, or physical damage
POST or memory diagnostic failure
Hardware crashinfo without a software workaround

Frequently asked questions

Will this work on my specific Junos OS version?

The procedure reflects current Junos OS behaviour. Older releases may need minor syntax adjustments. use the CLI help (? or tab-completion) to verify.

Should I open a JTAC case immediately?

Open one if you suspect hardware failure or the symptom persists after a maintenance-window reload. Make sure your support entitlement is active first.

Where can I find the Juniper official documentation?

https://kb.juniper.net/, search the product family + feature name.

Is this procedure safe in production?

Test in a lab or maintenance window first. Capture pre-change state so you can roll back.

All Juniper fix guides → /juniper/
All vendor guides → /vendors/

Related guides worth a look while you sort this one out:

References

Juniper support portal: https://support.juniper.net
Juniper knowledge base: https://kb.juniper.net/
Juniper security advisories: https://supportportal.juniper.net/s/global-search/Security%20Advisory
Open a case: https://supportportal.juniper.net/s/case

Reference material, not professional advice. Validate against your specific Junos OS version and test in a non-production environment before applying.

Common patterns we see

When this symptom shows up on a Juniper device, three patterns repeat:

1. Recent firmware update changed behavior: the symptom started within a week of an OTA push. Rollback or wait for the hotfix. 2. Environmental trigger, temperature, humidity, line voltage, network changes. Look at what changed in the environment. 3. Cumulative wear. components like batteries, gaskets, fans degrade over time. Replace the consumable rather than chasing a software fix.

Knowing which pattern applies saves time on the wrong fix.

Safety + preconditions

Before any work on a Juniper device:

Unplug from mains for any internal-access procedure.
Discharge stored energy (capacitors in PSUs, residual battery charge) per manufacturer guidance.
Use ESD-safe handling for boards and modules, no carpet, no wool sleeves.
Avoid moisture; never apply liquids near vents or connectors.
If you smell smoke, see scorch marks, or feel uneven heat, stop and escalate.

How to confirm it's actually fixed

On a Juniper device, the test is rarely "reboot and see". Use this list:

Active reproduction: trigger the original failure path on purpose.
Indirect reproduction: do an activity that would expose the same subsystem.
Status indicator review: every LED / display / app status should be green.
24-hour soak: leave the device under normal load overnight; check the next morning.
Telemetry check: review the device or app's diagnostic log for new error entries.

Escalation guide

For a Juniper device, the right escalation depends on impact:

Cosmetic / minor: log a ticket via the Juniper app or web portal. Response 1-3 business days.
Mid-impact: phone support. Have your serial number ready.
Critical (production down, safety issue): in-person dealer / TAC visit. Bring proof of purchase.
Out of warranty: third-party repair shop with manufacturer-certified technicians.

Topology deep dive, how the SRX300 actually moves a packet

The Junos OS RPD (routing protocol daemon) holds the BGP / OSPF tables, and the kernel installs them into the PFE forwarding table via the rpd-to-kernel socket. On a busy NSEL Mumbai colo edge with 1.2 million BGP routes from two ISP feeds (Reliance Jio + Airtel), the rpd memory footprint hits 6.4 GB. The SRX1500 ships 8 GB DRAM, and you will see the RE swap to disk during convergence storms if you do not damp the import. `show route summary` is your friend.

VCP-trunk (Virtual Chassis Port) on the SRX340 runs at 40 Gbps over the dedicated rear ports. If you cable VCP over the front 10G optics by mistake (a common install error at remote BFSI branches), the stack joins but every inter-member packet eats a hop of latency. Use `show virtual-chassis vc-port` to confirm cabling. The output column should read VCP rather than Network.

The SRX1500 boot sequence runs U-Boot → Junos loader → Junos OS. If the loader> prompt appears and stays there, the bootloader survived but the Junos OS image on flash has gone bad. The recovery is to TFTP a known-good image from a 169.254.0.0/16 link-local laptop. On the BFSI side, we keep a staging laptop at every colo with a JTAC-approved image archive named by `sha256` for exactly this scenario.

Configuration walkthrough with Junos commit safety

For automation, NETCONF over SSH on port 830 is the standard. `set system services netconf ssh` enables it. Pair this with a service account whose AAA profile in `set system login user` uses `class super-user-local` only (no remote root). On the SRX340 at a BSNL POP in Vijayawada, we run Ansible juniper.device collection against this account, with vault-encrypted RSA 4096 keys. The keys rotate quarterly via a `gpg`-backed CI pipeline.

Junos OS supports `commit comment` and `commit synchronize` (for dual-RE chassis). On the SRX1500 single-RE platform, the `synchronize` flag is a no-op, but I leave it in the muscle-memory commit script. On a dual-RE MX series, omitting `synchronize` is a silent split-brain risk that BFSI auditors will flag. The ITSAR network device baseline (TEC 31318) calls out config sync as a mandatory control.

The Junos commit model is two-stage by default: candidate config first, then `commit`. On a production SRX1500 at a BFSI data center, I always run `commit check` first, then `commit confirmed 5`. The `confirmed 5` flag rolls back automatically after five minutes if you do not run a second `commit` to make it permanent. This single habit has saved me from a midnight session at a colo cage more than once.

Troubleshooting commands I keep on the laminated card

request support information | save /var/tmp/rsi.txt: the JTAC bundle. Compress with `gzip` and upload via the JTAC case web upload.
show chassis environment, power, temperature, fan tray status. The temperature column reports Marginal before Failed, which gives you a 24-hour window in most BFSI cages to plan a cooling fix.
show chassis hardware extensive. full inventory including serial numbers, FRU type, version. This is the first command JTAC asks for in any RMA case.
show interfaces ge-0/0/1 extensive, drops, errors, queue depth, and SFP DDM voltages. The DDM optical RX power should sit between -3 dBm and -7 dBm on a standard 10km SMF link.
show system processes extensive | match rpd: rpd memory and CPU. Above 60% sustained, plan an RE upgrade or BGP import filtering.
show route summary, table sizes per RIB. If inet.0 exceeds 1 million on the SRX1500, you are crowding RPD memory and BGP convergence will degrade.
request system snapshot. clone the current Junos OS slice to the secondary. Always run this before a firmware add.
show log messages | last 50, recent syslog. Look for FPC FRU events, PEM events, and any RPD_ABORTED entries.

India compliance and procurement notes (MeitY, DPDP, GeM)

The GeM (Government e-Marketplace) listing for SRX340 at the time of writing is INR 4,87,500 per unit, with SmartNet renewal at INR 85,000 per year. The BoQ for a typical BSE colo deployment includes 2 SRX340 in cluster, 1 EX4300 management switch, 2 RJ45 console servers (Opengear), and the AMC line item for 3 years totalling around INR 14,75,000. The procurement cycle is 90-120 days end-to-end through GeM.

The MeitY-cleared list (the TEC Mandatory Testing and Certification of Telecom Equipment list under ITSAR) covers Juniper SRX300, SRX340, and SRX1500 under the network security device family. For a BFSI deployment, the procurement team must verify the device serial is on the cleared list. If it is not, the audit finding lands in the next RBI cyber security framework audit, and the network handover is delayed.

Real-world deployment I did

Last quarter at a BSE colo cage in BKC Mumbai, we had an SRX1500 that started dropping ge-0/0/12 every Tuesday at 02:14 IST. Three NOC shifts blamed the cable. I pulled `show interfaces ge-0/0/12 extensive` and the input errors lined up with a weekly cron on the upstream Cisco Catalyst pushing a full BGP table refresh. The actual fault was TCAM pressure on the SRX, not the optic. We added a route summarisation policy and the flap stopped. The replacement SFP we had pulled and labelled bad? Still in my toolbox, working fine.

An Outlook from the SOC desk at a private bank in HITEC City Hyderabad: the SRX1500 IDP licence had silently expired and the JTAC case said Renewal Pending while traffic was still flowing. The renewal SKU was INR 1,52,000 for one year. We pushed the temporary licence over `request system license add terminal` from the JTAC portal, brought the IDP profile back online, and only then did the AAA-driven daily log push to the Splunk SIEM start matching the expected event volume.

Extended FAQs from the field

What is the realistic RMA turnaround in India?

JTAC depot in Bengaluru ships in 7-10 working days for in-warranty SRX300 / SRX340. For SRX1500 the depot is in Mumbai and the shipping is usually 5-7 working days. Out of warranty units go via the JTAC Spares purchase line at roughly 60-70% of the new BoQ price. Always confirm the serial entitlement via the support portal before opening the case.

Should the SRX cluster run active-active or active-passive in a BSE colo?

Active-passive (`chassis cluster reth`) is the safer default. Active-active needs careful flow synchronisation tuning and the BFSI NOC must be ready to handle asymmetric paths. On every NSEL colo I have built, we stay active-passive unless the trading throughput specifically demands the doubled forwarding capacity.

Does the Junos OS upgrade need a maintenance window?

Yes. Even with `commit confirmed` and a dual-RE chassis, the FPC reboots during the package install. On the SRX1500 single-RE platform, this is a 6-8 minute outage. I schedule them in the 02:00-04:00 IST window after coordinating with the BFSI NOC on-call, the upstream Reliance Jio / Airtel ISP, and the downstream switch fabric team.

What if `show chassis environment` reports Fan Tray Failed but the unit is cool?

Check the fan tray seating first: at India colo sites, dust loading and vibration from BMS construction nearby can dislodge a tray. Reseat, wait 60 seconds, recheck. If still failed, swap the tray (FRU SRX-FAN-TRAY is field-replaceable on the SRX1500). The tray FRU price is approximately INR 38,000 from the JTAC spares line.