Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

maintenance-mode

Syntax

Hierarchy Level

Description

EVPN maintenance mode streamlines maintenance and upgrade operations in EVPN environments by minimizing traffic disruption. By isolating devices in a controlled manner, service interruptions during upgrades can be prevented. This feature operates seamlessly with multihomed collapsed core, Core-Distribution, edge-routed bridging (ERB) and IP Clos leaf nodes, rerouting traffic to alternate nodes to maintain network stability. It includes pre-checks and validations to ensure multihomed configurations, service tracking, and non-revertive designated forwarder (DF) settings are correctly configured.

Before initiating EVPN maintenance mode, prepare your network by ensuring out-of-band management capabilities and bandwidth availability to handle potential traffic loads when traffic is diverted to the multihomed peer. This feature does not support single-homed configurations or in-band network management during maintenance.

EVPN maintenance mode leverages the network isolation (NISO) configurations to disable the end-device facing access interfaces and divert traffic towards multihomed peer devices. This helps to isolate the node and prepare it for maintenance.

You initiate maintenance mode by configuring the set protocols evpn maintenance-mode (collapsed-core|core-distribution|erb-leaf|ip-clos) action-type (validate-only|validate-and-set|force) statement. The validation options certify that your network is adequately configured before entering maintenance mode. These pre-checks verify multihomed configurations, enforce service tracking actions, and confirm non-revertive DF settings. By ensuring these conditions are met, the risk of service disruption during maintenance is reduced.

You can use the schedule-start-at time and schedule-end-at time options to schedule maintenance in advance. Configuring a maintenance schedule also enables a validation check that verifies that NTP-based DF operation is configured. Deleting or modifying the maintenance-mode configuration cancels existing schedule timers or re-triggers them as needed. If a configuration change causes the maintenance pre-check validation to fail after the scheduled start time, the system immediately clears maintenance mode. The system automatically exits maintenance mode at the configured schedule-end-at time. To end maintenance earlier, either update the schedule-end-at time or use delete protocols evpn maintenance-mode to remove the maintenance-mode configuration. Removing the maintenance-mode configuration brings the EVPN instances back online.

At the scheduled start time, the system changes the active DF preference and no-preempt settings for all locally hosted Ethernet segment identifiers (ESIs). The system applies these changes with jitter so that the device relinquishes DF responsibility for its locally hosted ESIs before maintenance actions affect local interfaces. 60 seconds after the scheduled maintenance start time, the system performs the configured maintenance-mode action and brings down interfaces with an enabled NISO profile. The 60-second delay allows the device to relinquish DF status for all locally hosted ESIs before interfaces are brought down.

Note: During the 60-second delay, the system expects all locally hosted ESIs to relinquish DF status. If transient network events cause the maintenance node to remain the DF for one or more ESIs, entering maintenance mode can cause additional traffic loss.

You can validate configurations before and after starting maintenance mode with the request evpn validate-maintenance-mode-pre-checks command. Then use show evpn maintenance-mode-status to view results of the pre-checks and monitor the current status. If you change any maintenance mode related configurations, rerun request evpn validate-maintenance-mode-pre-checks to update the validation.

Options

collapsed-core Sets the maintenance-mode for a collapsed core leaf.
  • action-type—Defines maintenance-mode action to take.
    • force—Trigger maintenance-mode, ignores pre-check validations
    • validate-and-set—Trigger maintenance-mode after pre-check validation
    • validate-only—Validate maintenance-mode pre-checks, no action is taken
  • schedule-end-at—Sets time to end maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
  • schedule-start-at—Sets time to start maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
core-distribution Sets the maintenance-mode for a core distribution leaf.
  • action-type—Defines maintenance-mode action to take.
    • force—Trigger maintenance-mode, ignores pre-check validations
    • validate-and-set—Trigger maintenance-mode after pre-check validation
    • validate-only—Validate maintenance-mode pre-checks, no action is taken
  • schedule-end-at—Sets time to end maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
  • schedule-start-at—Sets time to start maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
erb-leaf Sets the maintenance-mode for an ERB leaf.
  • action-type—Defines maintenance-mode action to take.
    • force—Trigger maintenance-mode, ignores pre-check validations
    • validate-and-set—Trigger maintenance-mode after pre-check validation
    • validate-only—Validate maintenance-mode pre-checks, no action is taken
  • schedule-end-at—Sets time to end maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
  • schedule-start-at—Sets time to start maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
ip-clos Sets the maintenance-mode for an IP Clos leaf.
  • action-type—Defines maintenance-mode action to take.
    • force—Trigger maintenance-mode, ignores pre-check validations
    • validate-and-set—Trigger maintenance-mode after pre-check validation
    • validate-only—Validate maintenance-mode pre-checks, no action is taken
  • schedule-end-at—Sets time to end maintenance-actions. Format is [yyyy-mm-dd.]hh:mm
  • schedule-start-at—Sets time to start maintenance-actions. Format is [yyyy-mm-dd.]hh:mm

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 25.3R1

Options for collapsed-core, core-distribution, and ip-clos leaf configurations and scheduling times introduced in Junos OS Release 26.2R1.