The delivered configuration clearly indicates that aVPN instancenamedMKThas been created and bound to a VXLAN identifier. In Huawei virtualized campus networks that useVXLAN + BGP EVPN, aVN (Virtual Network)configured on iMaster NCE-Campus is typically instantiated on devices as anip vpn-instance. This VPN instance represents the logical tenant or virtual routing domain used for service isolation.
Several key lines confirm this mapping. The commandip vpn-instance MKTis the core object created for a VN. Theroute-distinguisher (RD)is configured to ensure route uniqueness for that VPN instance. The presence ofvpn-target import/export extcommunityandvpn-target ... evpnshows that routes are controlled and exchanged using BGP extended communities, including EVPN-related RTs for VXLAN EVPN route import/export. This is exactly what iMaster NCE-Campus generates when a VN is created and needs to participate in EVPN route distribution.
Finally, vxlan vni 6 binds the VPN instance to a VNI, which is how VXLAN identifies and separates virtualized networks. Creating a fabric or external network would not directly generate an ip vpn- instance with RD/RTs and a VNI binding. Therefore, the administrator operation was to create a VN named MKT.