Understanding VXLAN and NVE Interfaces

VXLAN (Virtual Extensible LAN) allows for Layer 2 network extension over Layer 3 infrastructure.

???? Key VXLAN Components:

NVE (Network Virtualization Edge) Interface → VXLAN tunnels are created using one or more NVE interfaces.

BD (Bridge Domain) → Logical grouping of VXLAN traffic.

VNI (VXLAN Network Identifier) → 24-bit unique ID for traffic segmentation.

???? Analysis of Each Option:

✅ A. One NVE interface can be used for multiple VXLAN tunnels if ingress replication is used.

Correct: VXLAN tunnels can be dynamically learned using BGP EVPN, meaning multiple tunnels can use the same NVE interface.

✅ B. An NVE interface can be associated with multiple VNIs, allowing multiple BDs on one NVE.

Correct: Each NVE interface can carry multiple VNIs, reducing the need for separate interfaces.

❌ C. One NVE interface must be created per VXLAN tunnel.

Incorrect: Multiple VXLAN tunnels can share a single NVE interface.

❌ D. One NVE must be created for each BD.

Incorrect: One NVE can support multiple BDs.

???? Real-World Application:

Cloud Data Centers: VXLAN enables multi-tenant network segmentation.

Campus Networks: Simplifies Layer 2/Layer 3 connectivity across sites.

✅ Reference: Huawei HCIE-Datacom Guide – VXLAN and NVE Configuration

SR-MPLS leverages IGP (OSPF/IS-IS) extensions to advertise Segment IDs (SIDs) and can also integrate with TE (Traffic Engineering) for bandwidth reservation using RSVP-TE or SR-TE.

Exact Extract – Huawei SR-MPLS Configuration Guide:

“SR-MPLS uses extensions in IGP to distribute label bindings and, combined with traffic engineering, supports bandwidth assurance and high-bandwidth services.”

Comprehensive and Detailed Explanation:

✔ iMaster NCE-WAN provides a RESTful API for integration with third-party applications and network automation platforms.

✔ Why RESTful API?

Uses HTTP/HTTPS for communication.

Supports JSON and XML data formats.

Enables orchestration, monitoring, and automation.

✔ Why Not Other Options?

❌ (A) NETCONF → Used for device-level configuration, not northbound APIs.

❌ (B) SNMP → Used for network monitoring, not northbound integration.

❌ (C) CLI → Used for manual command execution, not API communication.

???? Reference: Huawei HCIE Datacom – iMaster NCE-WAN Northbound API

In SR-MPLS (Segment Routing over MPLS), prefix SID conflicts may occur if multiple prefixes are assigned the same SID or vice versa.

Conflict resolution principle (Huawei standard):

When there are multiple SIDs for the same prefix, the SID with the lowest value wins.

When the same SID is assigned to multiple prefixes, the prefix with the smallest address wins.

Apply to this case:

Conflict: Two entries for 1.1.1.1/32 with SID 2 and SID 1.

SID 1 is lower, so 1.1.1.1/32 → SID 1 is selected.

Correct answer: D. 1.1.1.1/32 → SID 1

Comprehensive and Detailed In-Depth Explanation:

NSR (Non-Stop Routing) and NSF (Non-Stop Forwarding) are high-availability mechanisms used to maintain network stability during routing process failures:

NSR (Non-Stop Routing):

Operates within the local router only.

Keeps routing information synchronized between the active and standby processes.

Does not require collaboration from neighboring routers.

NSF (Non-Stop Forwarding):

Requires collaboration from neighboring routers that support graceful restart.

The router undergoing failover relies on its neighbors to maintain forwarding tables while control plane recovery takes place.

Neighboring routers must support GR (Graceful Restart) for NSF to function correctly.

Therefore, the correct answer is B because NSF requires neighboring router collaboration, while NSR does not.

6PE (IPv6 Provider Edge over MPLS) vs. 6VPE (IPv6 VPN Provider Edge over MPLS VPNs)

6PE (IPv6 over MPLS without VPNs):

Uses global IPv6 routing over MPLS.

No VPN instances (VRFs) are created on PEs.

IPv6 addresses cannot be reused across different CEs because all traffic is routed using a single global table.

6VPE (IPv6 over MPLS with VPNs):

Uses MPLS VPN (VRF instances) to provide IPv6 VPN services.

VPN instances (VRFs) are created on PEs to separate customer networks.

IPv6 addresses of CEs can be reused in different VPN instances because each VRF maintains separate routing tables.

Correct Answer Explanation:

✅ C. In 6VPE networking, IPv6 addresses of a CE can be reused.

Since each VPN instance (VRF) maintains its own IPv6 routing table, IPv6 addresses of CEs can be reused across different VPNs.

Incorrect Answer Explanations:

❌ A. In 6PE networking, VPN instances need to be created on PEs.

Wrong! 6PE does not use VPN instances (VRFs); it relies on a global IPv6 routing table.

❌ B. In 6PE networking, IPv6 addresses of a CE can be reused.

Wrong! Since 6PE uses a single IPv6 global routing table, IPv6 addresses cannot be reused.

❌ D. In 6VPE networking, no VPN instance needs to be created on PEs.

Wrong! 6VPE requires VPN instances (VRFs) on PEs to separate customer traffic.

Reference from Huawei HCIE-Datacom Documentation:

Huawei MPLS VPN Configuration Guide – 6PE and 6VPE Deployment

HCIE-Datacom Training Material – IPv6 MPLS Solutions

Huawei iMaster NCE-Campus provides open APIs for seamless integration with third-party applications and services. Each API serves a specific purpose in managing network security, operations, analytics, and user interactions.

1. Authentication and authorization → Third-party authentication API

This API is used to integrate third-party authentication systems, such as:

LDAP (Lightweight Directory Access Protocol)

RADIUS (Remote Authentication Dial-In User Service)

OAuth/OpenID authentication

It ensures secure user identity verification, access control, and single sign-on (SSO) in CloudCampus networks.

2. Network O & M → Infrastructure API

The Infrastructure API provides tools for network monitoring, diagnostics, and automated management.

It is used for:

Device status monitoring

Network topology visualization

Fault detection and real-time alerts

Performance optimization

3. LBS (Location-Based Services) → LBS API

The LBS API enables applications to access location data collected by the network.

It is used for:

Tracking users or assets within a campus network

Heatmap generation and movement analytics

Geo-fencing and location-based policies

4. Crowd profiling → VAS API

VAS (Value-Added Services) API is designed for advanced analytics and business intelligence.

It supports:

User behavior analytics

Demographic profiling

Marketing strategies based on network usage patterns

Reference from Huawei HCIE-Datacom Documentation:

HCIE-Datacom Training Guide – CloudCampus Solution

Huawei iMaster NCE-Campus API Documentation

Huawei CloudCampus Solution Whitepaper – Open API and Use Cases

SRv6 Policies can be:

Statically configured via CLI on routers.

Dynamically generated and delivered from a controller such as Huawei iMaster NCE for centralized path computation.

This dual approach allows flexibility in deployments.

Exact Extract – Huawei SRv6 Deployment Guide:

“SRv6 Policies can be locally configured or dynamically delivered via PCEP from the controller, enabling both static and SDN-based implementations.”

There are three standard inter-AS MPLS VPN options, as per RFC 4364:

Option A (Back-to-Back VRF):

VRFs are directly connected between ASBRs using routing exchange (like static/BGP).

No label switching between ASs — no MPLS label needed between ASs.

Option B (EBGP Label Exchange):

ASBRs exchange labeled VPNv4 routes via EBGP.

One MPLS label is required — MPLS forwarding across AS boundary is used.

Option C (End-to-End LSP):

Full end-to-end LSP is created across ASs.

MPLS labels are definitely used end-to-end, even between ASs.

Option D (Commonly vendor-specific extensions based on Option B/C):

Similar to Option C — requires MPLS labels.

So:

B. Option B — needs MPLS label ✅

D. Option D — also needs MPLS label ✅

A. Option A — no MPLS label ❌

C. Option C — also uses MPLS label ✅, but not listed as an answer option in this question format (should have been).

Assuming valid options are A, B, D, the correct ones needing MPLS labels are:

Correct answers: B, D

Comprehensive and Detailed In-Depth Explanation:

In BGP EVPN, Type 2 routes (MAC/IP Advertisement routes) are used to advertise:

MAC addresses of endpoints.

ARP entries (MAC-to-IP bindings).

IRB (Integrated Routing and Bridging) routes, allowing the advertisement of both Layer 2 and Layer 3 reachability.

These routes are essential for enabling dynamic VXLAN tunnel establishment and seamless host mobility.

Type 1 (Ethernet Auto-Discovery): Used for multi-homing information.

Type 3 (Inclusive Multicast Ethernet Tag): Used for BUM (Broadcast, Unknown unicast, and Multicast) traffic.

Type 4 (Ethernet Segment): Used for identifying Ethernet segments in multi-homing scenarios.