Exact Extract — Huawei Training Material (Automatic SDN Network O & M, p.22):
“Automatic service recovery: Based on service SLA requirements, NCE recalculates a service path based on SRv6, isolates the faulty node, and automatically restores the faulty service.”
Huawei Reference Verification:
Huawei's Automatic SDN O & M curriculum describes centralized path computation and controller-driven restoration after faults. For millisecond-level protection, the better design is to compute and install backup FRR forwarding state in advance. A failed link or node can then trigger immediate local switching to the alternate entry on the forwarder, avoiding the delay of reporting the fault, waiting for a controller decision and receiving new entries. Controller recalculation remains useful for later optimization and restoration. Therefore an SDN controller delivering FRR routes ahead of failure is the optimal choice.
Technical Deep Dive:
D is correct. The controller has a global topology view and can calculate primary and backup transport paths based on bandwidth, policy and service SLA. Rather than waiting for a fault before computing everything, it distributes the required FRR backup entries proactively. Upon link-down or BFD notification, the router's forwarding subsystem switches to the preinstalled alternate next hop or tunnel, minimizing customer interruption. Recomputing routes after failure through the controller introduces detection, signaling, calculation and programming delay. Forwarders can compute local routing in distributed architectures, but the question specifies centralized control and asks for the optimal immediate protection. IP FRR, TI-LFA, SR-TE backup paths and VPN FRR are examples of underlying forwarding protections. Supported Huawei NP/ASIC hardware performs fast local switching once the backup forwarding state is installed. Controller-based path optimization can then restore the desired long-term service state.
───────────────────────────────────────────────────────
Submit