CCNA High Availability Questions

Interface tracking monitors the state of a specified interface. When the tracked uplink goes down, the master reduces its priority by the configured decrement. If the resulting priority falls below the backup's, the backup preempts immediately, rather than waiting for advertisement timeouts. This is the standard Junos mechanism to trigger rapid VRRP failover based on an interface other than the VRRP interface itself.

NSR synchronises OSPF and BGP daemon state to the backup Routing Engine continuously, so protocol adjacencies survive the switchover without renegotiation. This satisfies the stem's requirement that routing sessions remain established and neighbours are not dropped.

Altering member priority values changes the election weight each member carries, so a subsequent reboot or mastership switchover command triggers a fresh election in which the newly favoured member can seize primary role. This directly satisfies the stem's unexpected switchover condition, since the election outcome shifts without any hardware fault.

ISSU on dual-RE MX240 routers requires GRES and NSR to be enabled and functioning, satisfying the stem's no-traffic-loss constraint. GRES preserves forwarding state across RE switchover, while NSR keeps routing protocol adjacencies and sessions intact, so neither control-plane nor data-plane traffic is dropped during the upgrade.

Binding member IDs to serial numbers via 'request virtual-chassis assign' or configuration statements decouples the ID from physical slot position, so each switch keeps its assigned member ID even when cabled into a different location within the Virtual Chassis.

Junos names aggregated Ethernet bundles ae0, ae1, ae2 and so on, so the LAG interface is referenced as ae0 in configuration and show commands. This satisfies the stem's request for the Junos CLI naming convention for the aggregated interface.

ISSU requires graceful restart or NSR so routing protocols maintain forwarding state across the software upgrade. Enabling NSR or graceful restart on all active interior and exterior protocols satisfies the pre-check constraint, allowing the in-service check to pass before proceeding.

Virtual Chassis members must run identical Junos OS major and minor versions; mismatched software prevents the replacement from joining the fabric or causes protocol errors. Verifying the version matches the master before insertion satisfies this compatibility requirement.

Graceful Restart preserves forwarding entries in the data plane while the OSPF control plane restarts, so traffic continues flowing. This satisfies the stem's requirement of uninterrupted packet forwarding during the routing protocol restart on the MX routers.

NSR synchronises OSPF protocol daemon state between Routing Engines, so the standby is already current and neighbours see no adjacency reset during switchover. GRES alone relies on neighbour helper mode, so NSR removes that dependency, satisfying the stem's control plane switchover constraint.

LACP requires member links to share identical speed, duplex and LACP mode settings; mismatched parameters prevent the bundle forming or cause member suspension. This satisfies the stem's requirement for a configuration condition on the EX4300 LAG.

VRRP priority determines which router becomes master; the highest priority wins. Raising the priority on the preferred switch's interface ensures it assumes the master role, satisfying the stem's requirement for the higher-capacity switch to lead.

ISSU requires both Routing Engines to run compatible Junos releases and matching hardware, since the upgrade proceeds by failing over between them while each RE runs a different software version. Identical models and supported images satisfy the dual-RE synchronisation constraint, allowing traffic to continue during the upgrade.

The `request chassis routing-engine master switch` command triggers a manual Routing Engine failover, satisfying the stem's requirement to initiate switchover on an MX router with GRES enabled. It forces the backup RE to assume the master role, preserving forwarding state through graceful switchover rather than relying on automatic failover.

Preemption directly satisfies the requirement that the recovered router immediately reclaims the master role. Enabled by default, it lets a router with higher priority seize mastership from the current backup, rather than waiting for the backup's advertisement timer to expire. Without preemption, the recovered higher-priority router would remain backup indefinitely.

With GRES enabled, the backup Routing Engine takes over the primary role while the Packet Forwarding Engine continues forwarding using existing state. Forwarding tables are not reset, so traffic keeps flowing through the switchover without disruption to the forwarding plane.

The show virtual-chassis command outputs member IDs, roles (master, backup, linecard) and status for every switch in the EX Series Virtual Chassis. It directly satisfies the stem's requirement to display operational status and roles of all members.

The 'show lacp interface' command exposes live LACPDU exchange state and partner system ID per member link, satisfying the requirement for real-time LACP status on the aggregated interface. Other operational commands show aggregate bundle state but not per-link partner identifiers.

Without dual primary detection, each Virtual Chassis partition independently elects its own primary Routing Engine, since the split severs the control-plane path used for mastership arbitration. Both partitions then remain active, so identical IP and MAC addresses can appear on the network simultaneously, satisfying the stem's default split-brain behaviour.

VRRP tracking reduces the master's priority by the configured decrement when a monitored interface fails. Once that decremented value drops below the backup's priority, the backup preempts and assumes mastership, which is exactly the failover behaviour described.

The VRRP virtual IP must sit in the same subnet as the physical interface on the broadcast domain, so hosts can resolve it via ARP. This satisfies the scenario's requirement for the virtual IP address assigned to the group.

Interface tracking with a priority decrement lowers the VRRP priority when a monitored upstream link fails, forcing mastership to transfer to a healthier router. This directly customises failover behaviour by making the active router step down on link loss, satisfying the stem's requirement for tunable failover parameters.

ISSU upgrades the backup Routing Engine first, then performs a graceful switchover so the upgraded engine becomes primary, preserving forwarding state. Finally, the newly elected backup is upgraded, maintaining continuous packet forwarding throughout. This satisfies the stem's requirement for non-disruptive upgrade behaviour across both Routing Engines.

Graceful Restart preserves BGP forwarding state across the routing engine switchover by having peers retain routes and mark them stale, rather than tearing sessions down. Verifying that both ends negotiated the capability and that helper mode was active ensures the restarting router's peers hold prefixes during the ISSU reboot, preventing the drops observed.

Mastership flapping stems from missed advertisements, so the physical layer must be verified first. Checking error counters and link stability, then raising the advertisement interval, prevents transient congestion from triggering premature failover to the backup EX4600.

A virtual IP address is mandatory because it becomes the shared default gateway that hosts on the subnet point to. Without it, VRRP has no address to assume ownership of during mastership transition, so clients could not reach a redundant next hop.

LACP fast timeout expects partner PDUs every second, while slow expects every 30 seconds. A mismatch means one side ages out the partner and tears down the bundle, producing the intermittent flapping and timeout errors observed.

When configured mastership priorities are equal, Junos falls back to uptime or boot order: the switch that has been up longest, or booted first, becomes primary. This tie-breaking criterion is evaluated alongside priority and member ID.

The minimum-links setting defines how many active member links must be up before the aggregate interface is marked up. Setting it to 2 on ae0 ensures the bundle drops traffic when fewer than two links remain operational.

Booting the new member standalone lets you align its Junos OS release with the master before rejoining, resolving the image mismatch and hardware errors on the Virtual Chassis ports. Isolation prevents the incompatible member from disrupting the existing chassis during the upgrade.

VRRP interface tracking decrements the gateway's priority by the configured value when the monitored uplink fails, allowing the backup to preempt and become master. This satisfies the stem's requirement that the backup router assumes the master role after core connectivity loss.

Aggregating multiple physical links into one logical LAG sums their individual capacities, so the bundle carries more traffic than any single member. This satisfies the stem's bandwidth benefit: aggregate throughput between connected devices increases, and traffic is load-balanced across active member links.

In a Virtual Chassis, the management IP address is a virtual address associated with the master role. When a switchover occurs, the backup becomes master and the virtual management IP is reassigned to the new master, so management connectivity is preserved without manual reconfiguration. This is a core high-availability behavior of the Virtual Chassis architecture.

ICCP runs between the two MC-LAG peer switches over the inter-chassis link, exchanging state and synchronising MAC address information so both control planes present consistent forwarding. This satisfies the requirement for MAC table consistency across separate control plane devices.

`show virtual-chassis` queries the Virtual Chassis operational state directly, returning each member's ID, configured priority, and current role (Master, Backup, or Linecard). This satisfies the stem's requirement for a single command exposing all three fields, unlike interface or protocol-specific commands that omit member priority data.

The command 'set chassis redundancy graceful-switchover' enables GRES globally at the chassis level, allowing the backup Routing Engine to assume control without restarting the Packet Forwarding Engine. This matches the stem's requirement for a global GRES configuration command.

Static LAG requires no LACP negotiation, so omitting the lacp stanza under aggregated-ether-options lets the Junos bundle form without protocol handshakes. The server's static mode cannot respond to LACPDUs, so enabling LACP would keep links down. Matching the server's non-negotiated mode satisfies the stem's constraint.

`show interfaces ae0` displays the aggregated Ethernet interface's operational state, including its LACP bundle status and member link roles, directly satisfying the stem's requirement to verify link aggregation and LACP operation. It confirms whether member interfaces are actively bundled or detached, which is the precise operational evidence the question demands.

Active mode makes the interface transmit LACPDUs unconditionally rather than waiting for the peer, so negotiation begins immediately. This satisfies the stem's requirement that the local interface initiate and negotiate the aggregation with the peer device.

'show interfaces ae0' reports the LAG's aggregated packet statistics, error counters and drop counters, satisfying the requirement to view all three for interface ae0. Adding 'extensive' or 'detail' is unnecessary for the basic counters requested.

'show bgp neighbor' displays the Graceful Restart capability exchanged with the peer and the helper-mode restart state flags, confirming whether the local router is retaining routes for the restarting peer. This satisfies the stem's requirement to verify helper operation during a control-plane restart.

The Expired state means the local port stopped receiving LACP PDUs from the peer before the timeout window elapsed, so the LAG cannot aggregate. This satisfies the stem's constraint: aggregation requires continuous bidirectional LACP exchange, and a silent peer expires the receive state machine.

Dedicated Virtual Chassis ports use specialised stacking cables on the rear or dedicated ports, providing the primary supported connection method for forming an EX Series Virtual Chassis. This satisfies the stem's requirement for one of the two valid connection methods.