Huawei H19-402_V1.0 - HCSP-Presales-Data Center Network Planning and Design V1.0

In Huawei CloudFabric and VXLAN-based data center designs, it is a best practice to use the IP address of a loopback interface as the VTEP (VXLAN Tunnel End Point) source address instead of a physical interface IP. This recommendation is based on reliability, stability, and operational flexibility.

A loopback interface is always in the UP state as long as the device is operational, whereas physical interfaces may go down due to link failures. If a physical interface IP is used as the VTEP source, any link failure would cause VXLAN tunnels to flap, impacting service continuity. In contrast, loopback interfaces remain reachable through the underlay network via dynamic routing protocols such as OSPF, IS-IS, or BGP, ensuring consistent tunnel endpoints.

Additionally, using loopback addresses supports ECMP (Equal-Cost Multi-Path) forwarding in the underlay, improving load balancing and network utilization. Huawei documentation strongly emphasizes this design principle to enhance VXLAN tunnel resilience and simplify network operations. Therefore, the statement is TRUE.

In Huawei CloudFabric and VXLAN-based overlay networking, the overlay provides abstraction, flexibility, and scalability by decoupling logical services from the physical infrastructure. NVEs (Network Virtualization Edge nodes) can indeed be deployed on physical switches (such as leaf switches), which is a fundamental capability of hardware-based VXLAN fabrics. Additionally, overlay networks are designed to meet the needs of private cloud environments, offering high performance, simplified O & M, and enhanced security through network segmentation (e.g., VXLAN VNIs).

Overlay networks also support access for both virtual machines and physical servers, ensuring consistent connectivity regardless of workload type.

However, statement D is incorrect. In Huawei’s architecture, especially with BGP EVPN-based VXLAN, the control plane is distributed rather than relying on a controller to synchronously deliver flow tables. Devices dynamically learn and exchange forwarding information using EVPN. Even in SDN-based scenarios with iMaster NCE-Fabric, policy delivery is not strictly synchronous flow table pushing in the traditional sense (like OpenFlow).

Therefore, “controller delivers flow tables synchronously” is not a standard capability of Huawei overlay networks, making option D incorrect.

Huawei CloudFabric is designed with an open and extensible ecosystem , enabling seamless integration with multiple platforms and services across modern data center environments. This openness is a key principle in Huawei’s architecture, ensuring interoperability and flexibility for diverse workloads.

Third-party VAS interconnection (A) is supported to allow integration with value-added services such as firewalls, load balancers, and security appliances, enabling service chaining and enhanced network functionality.

Container platform interconnection (B) is critical in cloud-native environments. CloudFabric integrates with platforms like Kubernetes, allowing automated network provisioning for containerized applications through APIs and SDN control.

Cloud platform interconnection (C) includes integration with cloud management platforms such as OpenStack and Huawei ManageOne, enabling unified orchestration of compute, storage, and network resources.

Virtualization platform interconnection (D) supports platforms like VMware and FusionSphere, allowing dynamic VM-based networking and automated service deployment.

Huawei documentation emphasizes that CloudFabric supports all these interconnection scenarios to deliver full-stack, multi-platform integration , making all options correct.

In Huawei CloudFabric solutions integrated with OpenStack, Neutron is the key component responsible for network service management and integration with external network controllers such as iMaster NCE-Fabric .

Neutron provides APIs for creating and managing network resources such as:

Networks (VXLAN/BD)

Subnets

Ports

Routers

iMaster NCE-Fabric integrates with Neutron via northbound APIs , allowing it to automatically translate cloud network requests into underlay and overlay configurations (e.g., VXLAN, EVPN, routing policies) on physical network devices.

Other components:

Nova (A) manages compute resources (VM lifecycle)

Keystone (B) handles authentication and identity services

Cinder (C) provides block storage services

These components do not directly interact with network controllers for fabric provisioning.

Huawei emphasizes tight integration between Neutron and iMaster NCE-Fabric to enable automated, policy-driven network deployment , which is essential for cloud data center operations.

Therefore, the correct answer is D (Neutron) .

In OpenStack Neutron, the core network abstraction models are Network, Subnet, and Port , which align with Huawei CloudFabric’s logical network design principles. A Network represents a Layer 2 broadcast domain, similar to a VXLAN segment (VNI) in Huawei data center fabrics. It provides tenant-level isolation and forms the foundation for overlay networking.

A Subnet defines the Layer 3 IP addressing scheme within a network, including CIDR blocks, gateway addresses, and DHCP configurations. This aligns with Huawei’s underlay/overlay separation, where IP addressing is critical for both service reachability and automation.

A Port is the connection point between a virtual machine (VM) and the virtual network, equivalent to a virtual NIC. It carries MAC/IP bindings and security policies, similar to endpoint definitions in EVPN-based fabrics.

The option vRouter is incorrect because Neutron uses the concept of a Router , not “vRouter,” and it is considered a higher-layer service component rather than a fundamental network model. Huawei documentation consistently emphasizes these three as the foundational constructs for virtualized network design.

In Huawei CloudFabric architecture, logical switches are a key abstraction used to simplify network service deployment and management. These logical switches are built on top of VXLAN Layer 2 networks and represent virtualized broadcast domains (similar to VLANs, but more scalable).

Huawei extends the function of these logical switches by integrating distributed Layer 3 gateway capabilities directly into them. This means that each logical switch can provide both Layer 2 connectivity and Layer 3 routing services (commonly referred to as distributed gateways). These gateways are typically implemented on leaf nodes using VXLAN with BGP EVPN as the control plane.

As a result, traffic between subnets can be routed locally at the ingress leaf switch without needing to traverse to a centralized gateway, significantly improving efficiency and reducing latency. Logical ports connected to these logical switches automatically receive gateway services, enabling seamless inter-subnet communication.

This design aligns with Huawei’s intent of decoupling physical and logical networks while providing scalable, agile, and highly efficient data center networking. Therefore, the statement is TRUE.

According to Huawei’s CloudFabric intelligent O & M description, the health model is built as a multi-dimensional evaluation system that assesses the network from five dimensions: device, network, protocol, overlay, and service . This means every option listed in the question is part of the CloudFabric health model. Huawei explains that this model integrates telemetry-assisted data such as configuration data, forwarding entry data, logs, and KPI performance information, allowing the platform to detect faults and risks in real time across these five layers.

In practical Huawei CloudFabric operations, the device layer focuses on node health, hardware state, and resource status; the network layer checks connectivity and path quality; the protocol layer verifies control-plane protocols and convergence behavior; the overlay layer evaluates virtualized forwarding networks such as VXLAN fabrics; and the service layer measures the actual service experience and traffic exchange status. Huawei explicitly presents these five as the full health-evaluation scope of CloudFabric intelligent O & M, so the correct response is all five options

In Huawei M-LAG design, strict requirements ensure stability and consistency between the two participating devices. Option A is false because M-LAG must be established between devices of the same type and model (or at least fully compatible models) . This ensures consistent forwarding behavior, synchronization of MAC/ARP tables, and proper operation of the peer-link and keepalive mechanisms. Using different device types is not supported and may lead to instability.

Option B is correct : unidirectional isolation is relevant only for dual-homed scenarios. If a device is single-homed, this mechanism is not applied.

Option C is correct : the peer-link is a critical connection between M-LAG peers and is typically configured as an Eth-Trunk (link aggregation) to ensure high bandwidth and redundancy.

Option D is also correct : peer-link interfaces are dedicated and cannot be used for other services, ensuring reliable synchronization and control-plane communication.

Huawei best practices emphasize homogeneous device deployment for M-LAG to guarantee predictable and stable operation.