Learning paths › JNCIA-Junos › Monitoring, maintenance and routing fundamentals
Monitoring, maintenance and routing fundamentals
Logging to a collector, SNMP objects, traceoptions, a rescue configuration kept outside the commit history, DHCP served by the device, ping and traceroute as bounded evidence, password recovery, a safe halt, image selection and an upgrade taken with a snapshot in hand, then route preference, inet.0 against the forwarding table, routing instances, and a first pass at policy and firewall filters.
Lessons
- Read a local log, then ship events to a collector
- Expose counters to a manager through MIB objects
- Capture protocol internals with traceoptions
- Keep a known baseline outside the commit history
- Lease addresses and options from the device itself
- Build the same DHCP pool through J-Web forms
- Assemble a baseline you can hand to someone else
- Separate observing the device from changing it
- Get version, hardware and interface state out of show
- Bound a connectivity claim with ping and traceroute
- Recover administrative access from the console
- Halt or power off without corrupting storage
- Read a Junos filename for release and platform
- Upgrade with a backup and a bootable snapshot in hand
- Judge whether an in-service upgrade is actually possible
- Match the evidence to the claim you are making
- Separate route selection from packet forwarding
- Name a destination and its next hop by hand
- Predict which protocol wins the same prefix
- Tell inet.0 from the forwarding table
- Give a customer its own routing context
- Know what each protocol advertises without a policy
- Match prefixes with route-filter and act on them
- Accept, discard or count packets term by term