Hardening & Safe Protocols

Juniper: How to configure logging to a central SIEM

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	Hardening & Safe Protocols
Skill level	Intermediate to advanced
DIY-able?	Yes with CLI access; some scenarios need JTAC + RMA.

Anyone who has automated a real Juniper fleet will tell you the same three lessons: capture request support information | save /var/tmp/rsi.txt on every run, version-control the rendered configs, and never push without a dry-run. Junos OS on the EX3400 platform supports all three.

I keep a small library of vendor-specific quirks per platform. Juniper is consistent enough that most code ports cleanly, but the commit semantics differ from what people coming from other vendors expect.

The rest of this guide is the actual workflow. credentials, render, validate, push, verify. Bring your own secret store.

What this guide covers

How to configure logging to a central SIEM on Juniper devices (Junos OS).

Recommendation

Forward syslog to a central SIEM (Splunk / Elastic / Sentinel). Helps incident response.

CLI / commands

# Entered from: configure
set interfaces ge-0/0/1 unit 0 family inet address 10.0.0.1/24

# Save / commit
commit

Verify

Test from a non-admin workstation.
Confirm fallback works if AAA or external service is down.
Document the change in your CMDB / change-control.

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.

What changed recently?

Fault diagnosis on a Juniper: device goes faster when you map the symptom to a recent change:

Did firmware update in the last 7 days?
Did the network (router, ISP, VPN) change?
Was the device moved physically?
Did paired devices (phone, hub, app) update?
Were any accessories swapped in or out?

The answer narrows the root cause to a manageable subset.

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.

Quick verification

Before you walk away from a Juniper: device fix, run through:

1. Reproduce the original trigger. does the issue reappear? 2. Check the device's status / health screen for any new alerts. 3. Confirm paired devices (app, hub, controller) reconnected. 4. Save / commit any configuration changes per the device's normal workflow. 5. Note the change in your maintenance log with date + firmware version.

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 Junos hardening actually moves a packet

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.

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.

On the SRX300 / SRX340 / SRX1500 platform, the data-plane is built around a Juniper Trio chipset that splits the forwarding pipeline from the routing engine. The implication for an enterprise network engineer is direct: a `show chassis hardware` that reports the Trio PFE as up does not mean the routing engine is healthy. The two clocks run independently. In a BFSI data center, I always check both with `show chassis routing-engine` and `show chassis hardware extensive` before I touch anything.

Configuration walkthrough with Junos commit safety

Rollback in Junos is granular. `rollback 1` brings back the last commit, `rollback 5` brings back five commits ago, and `show | compare rollback 1` diffs the live config against the previous one. On a Reliance Industries change window, our standard workflow is: open the candidate, `load merge terminal relative`, paste the change, `show | compare`, `commit check`, `commit confirmed 5`, then a final `commit` only after the verification script in `request system commands` passes.

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.

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.

Troubleshooting commands I keep on the laminated card

request system snapshot, clone the current Junos OS slice to the secondary. Always run this before a firmware add.
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 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 log messages | last 50. recent syslog. Look for FPC FRU events, PEM events, and any RPD_ABORTED entries.
show system processes extensive | match rpd, rpd memory and CPU. Above 60% sustained, plan an RE upgrade or BGP import filtering.
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 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 support information | save /var/tmp/rsi.txt. the JTAC bundle. Compress with `gzip` and upload via the JTAC case web upload.

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.

Under DPDP 2023 (Digital Personal Data Protection Act), logs that carry source IP plus a user identifier qualify as personal data. The syslog forwarding configuration on the SRX1500 must therefore include log retention boundaries (typically 180 days hot, 365 days cold) and access control at the SIEM. Splunk RBAC roles aligned to the data controller and processor responsibilities. On a Reliance Industries BFSI rollout, I have seen the legal team push back on raw syslog leaving the Mumbai data center perimeter, so the SIEM forward is to an on-prem instance, not a cloud SaaS.

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.

During an SBI data center cutover at Belapur, we ran a controlled Junos OS upgrade across 28 SRX340 firewalls. The procedure: `request system snapshot`, then `request system software add` with `no-validate` only on the first unit, then full validate on the rest. Two units failed the package signature check on Junos 22.4R3 because the staging server had served the file truncated. Hash matching against `sha256sum` saved a four-hour rollback window.

Extended FAQs from the field

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.

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.

How do I verify a Junos OS image before flashing?

Pull the image hash from the JTAC download page (it lists SHA-512). On the device, use `file checksum sha-256 /var/tmp/junos-srxsme-22.4R3.7.tgz` and compare. Mismatch means the file was truncated or tampered, do not flash. On a BFSI environment, the staging server must enforce TLS 1.2+ on the file transfer, and the JTAC web download uses HTTPS by default.

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.