JNCIE-ENT: System Management and Monitoring

This domain tests operational control of Junos devices: configuration lifecycle, commit safety, logging, telemetry, and health checks. JNCIE-ENT expects procedures that survive a mistake or a Routing Engine switchover, not just commands that work once.

Core rules

• Junos edits a candidate configuration. commit check validates syntax and constraints but does not apply it. commit confirmed N applies the change and automatically rolls back after N minutes unless you issue commit; use it for remote access changes.
• On dual-RE platforms, commit synchronize commits both REs; commit synchronize confirmed combines synchronization with auto-rollback. rollback N restores a prior commit.
• Archive configuration with system archival configuration transfer-on-commit plus archive-sites; save a rescue config with request system configuration rescue save.
• Monitor with show log messages, show system alarms, monitor traffic interface, and traceoptions. Bound trace files with size and files so they cannot fill /var.
• RPM probes test reachability and latency; SNMP traps and syslog should be tested, not assumed.

Worked example

A management-filter change can lock you out. Stage it, then: commit confirmed 5 Verify SSH/HTTPS from an out-of-band path. If access works, issue commit to confirm. If not, do nothing: Junos restores the previous configuration after five minutes. The timer, not the login session, controls rollback, so an idle session does not keep the change alive.

Traps

commit check is not a trial run. commit confirmed rolls back the entire candidate, including unrelated edits. Traceoptions with no file limits can exhaust disk. commit synchronize fails if the backup RE is not ready, so check RE status first. A rescue configuration is not loaded automatically.