Juniper JN0-352 - Enterprise Routing and Switching, Specialist (JNCIS-ENT)

A floating static route is a backup static route that remains present in the configuration but stays inactive in the routing table under normal conditions, only becoming active if the primary, preferred route to the same destination is withdrawn or otherwise becomes unavailable. Junos determines which of several competing routes to the same prefix becomes active strictly by comparing each route's preference value (administrative distance), with the numerically lowest preference always winning; every routing protocol and static routes themselves carry a default preference (5 for standard static routes), and this value can be explicitly overridden per route using the preference statement under the static route's configuration. To create a floating static route, the administrator deliberately configures a preference value higher (that is, numerically worse, less preferred) than the preference of the primary route it is meant to back up — for example, a value higher than the 5 default of an ordinary static route, or higher than a dynamic protocol's preference such as OSPF's 10 — ensuring the floating route only becomes active once the more-preferred primary route disappears from the table entirely. This preference-based mechanism is the essential, defining configuration element of a floating static route. Priority is not a valid Junos static-route statement, next-hop simply defines where matching traffic is forwarded without controlling route selection behavior, and qualified-next-hop is a related but distinct mechanism used to assign a per-next-hop preference within a single multi-next-hop static route statement rather than between the standalone static route and its dynamic counterpart. Reference topics: Junos Enterprise Routing – Protocol Independent Routing, Configuring Floating Static Routes with Preference.

The factory-default storm control configuration on EX Series switches operates in a purely rate-limiting mode rather than an interface-shutdown mode. When broadcast, multicast, or unknown-unicast traffic on a port exceeds the configured bandwidth-percentage threshold, the default action is simply to police the offending traffic type and silently drop only the packets that exceed that threshold, while all traffic within the allowed rate continues to be forwarded normally and the interface itself remains administratively and operationally up throughout the event. This explains the observed symptom precisely: during the burst of unknown-unicast frames, the switch dropped the excess volume above the configured limit, producing a brief period of packet loss, but as soon as the burst subsided and traffic fell back under the threshold, storm control simply stopped dropping packets and normal forwarding resumed automatically — no administrative shutdown, recovery timer, or manual intervention was ever involved, because the interface was never taken down in the first place. This default drop-only behavior is distinct from the optional interface-shutdown action, which must be explicitly configured if an administrator wants storm control to disable a port outright on violation (as seen in a related scenario requiring the clear ethernet-switching recovery-timeout command). Storm control by default covers broadcast, multicast, and unknown-unicast traffic types together, not multicast alone, and it has no functional relationship to GRES, which governs Routing Engine redundancy rather than Layer 2 traffic policing. Reference topics: Junos Enterprise Switching – Storm Control, Default Drop Behavior Versus Interface Shutdown Action.