Huawei H12-891_V1.0 Dumps

✔Egress devicesinHuawei CloudCampus static IPsec VPNinclude:

Access Points (APs)

Routers

Firewalls✅

✔Why Firewalls?

Firewallssupport IPsec VPN terminationforsecure WAN interconnection.

Firewalls provideadvanced security filteringandencryptionfor IPsec traffic.

????Reference:Huawei HCIE Datacom – IPsec VPN in CloudCampus

Let’s break this down step-by-step based on Huawei IS-IS VPN and multi-process behavior.

???? Configuration Summary:

Process 1: IS-IS for the global routing table

Process 2: IS-IS for VPN instance tt

Process 3: IS-IS for VPN instance rr

✅ Option C: Correct

Process 1 contains only global routing information.

The configuration of isis 1 does not include any vpn-instance keyword, meaning it is bound to the global routing table.

It does not interact with VPN routing tables unless explicitly configured with import/export mechanisms or route leaking (which is not shown here).

Huawei Datacom Reference:

“When an IS-IS process is not associated with a VPN instance, it belongs to the global routing table and only maintains global routes.”

(Source: HCIE-Datacom Study Guide v3.0 – Chapter: IS-IS for IPv4 and IPv6, Section: Multi-Instance Routing)

✅ Option D: Correct

Routing information of process 2 is isolated from that of process 3.

isis 2 is bound to VPN instance tt

isis 3 is bound to VPN instance rr

Each IS-IS process in Huawei VRF context maintains independent LSDBs and routing tables, and by default, they do not share routing information unless route leaking or redistribution is configured (which is not shown in the config).

Huawei Datacom Reference:

“IS-IS processes bound to different VPN instances operate independently and do not share routing information.”

(Source: HCIE-Datacom Study Guide v3.0 – Chapter: MPLS L3VPN with IS-IS)

The command output shows:

*>i before both networks, which means these routes are the preferred routes (*) and are learned via internal BGP (i).

Two networks are listed: 3002::3 and 3002::4, which means R1does havethese two routes in its BGP IPv6 routing table.

For 3002::4, the path origin shows 65001 i, which means this route originated from AS 65001 and was learned through IBGP.

The AS Path attribute is only shown for 3002::4, but both routes are clearly present.

Therefore, the correct conclusion is:

D. R1 has routes 3002::3/128 and 3002::4/128.