H31-161 HCIE-Carrier IP (Written) Questions and Answers

Run the peer 2.2.2.2 enable command in the BGP-VPNv4 subsequent address family view to enable the peer to exchange BGP-VPNv4 routing information.

Run the peer 2.2.2.2 upe command in the BGP-VPNv4 subsequent address family view to

designate the peer as a UPE of the SPE.

Run the peer default-originate vpn-instance command in the BGP-VPNv4 subsequent address family view.

Configure the default-route imported command in the BGP-VPN instance view without importing default IGP routes, and then configure the peer default-originate vpn-instance command in the BGP-VPNv4 address family view.

Configure the peer default-originate vpn-instance command in the BGP-VPNv4 address family view, and then configure the default-route imported command in the BGP-VPN instance view.

The tunnel policy is configured in the system view. You can run the tunnel-policy policy-name command to create tunnel policies and enter the tunnel policy view. One VPN instance supports multiple tunnel policies, and multiple VPN instances can share a tunnel policy.

You can run tunnel select-seq { gre | lsp | cr-lsp } * load-balance-number load-balance-number in the tunnel policy view to configure the priorities of tunnels and the number of tunnels among which load is balanced.

You can run the tnl-policy policy-name command in the VPN instance view to apply tunnel

policies to VPN instances. If the required tunnel policy does not exist, the configuration is saved but does not take effect. If you create this tunnel policy in the system view later, the saved configuration will take effect.

If a VPN instance does not have a tunnel policy, an LSP is used and the number of tunnels

configured for load balancing is set to 1

If the length of a L2VPN packet that arrives at a P node exceeds the maximum transmission unit (MTU) of relevant interfaces of the P node, the packet will be fragmented and then forwarded.

When a traditional L2VPN (ATM and FR) is upgraded to an MPLS L2VPN, the network topology does not need to be adjusted.

When providing the MPLS L2VPN service for enterprise users, the carrier must filter user route advertisements. Otherwise, flapping of user routes may lead to flapping of network routes.

On a L2VPN, routing information of users does not need to be maintained or managed.

MPLS

IP

A or B

None of the above

Option A

Option B

Option C

Option D

vrf4

vrf3

vrf2

ssm-mapping 225.0.0.0 255.255.255.0 2.2.2.2

igmp on-demand

igmp prompt-leave

igmp ssm-mapping enable

The NAT cannot be used in easy IP mode.

VRIDs of the VRRP must be bound with the NAT during NAT configuration in the outbound direction between domain.

VRIDs of the VRRP do not need to be bound with the NAI during NAI configuration in the outbound direction between domains.

The FTP Nat Alg function must be enabled on the firewall

The leaf router in the idle state receives host Join messages.

The router receives prune messages of the RPF neighbor from other routers when it is receiving data from the upstream.

The intermediate router receives graft messages from the downstream router when all

downstream interfaces of the intermediate router are in the prune state.

The router receives state-refresh messages.

It connects users to the network by providing various access means, and converts the format of

information so that the information can be transmitted on the network.

Using the packet technology, it provides a comprehensive transport platform that boasts high

reliability, quality of service (QoS) assurance, and large capacity.

It implements call control. With the softswitch technology as the core, it completes basic realtime call control and connection control.

It provides additional value-added services and operation support for established calls

The LSP Ping Echo request must contain the downstream mapping TLV

A unique Sender's Handle is generated during each LSP Ping operation

A unique sequence number is generated during each LSP Ping operation

The LSP Ping Echo request may contain the FEC stack TLV

Construct an outband NM network to manage all devices.

Leak public and private network routes to manage devices on the public and private networks.

Establish two physical or logical links with the PE to manage devices on the public and private networks. One link belongs to the public network and the other belongs to the private network.

Establish a physical or logical link with the PE and mount MCEs to the PE to manage devices on the public and private networks.

RTA—RTB—RTC; 1

RTA—RTD—RTE—RTC; 1

RTA—RTB—RTC; 20

RTA—RTD—RTE—RTC; 3

a=b=c=d

c>a+b+d

d>a+b+c

a=b>c=d

True

False

When TE FRR in FA mode is enabled, nodes except the node on which FA is configured can sense the TE tunnel interface. When the primary tunnel link becomes faulty, the PLR switches traffic to the bypass tunnel through protection switching. The upstream node assumes the TE tunnel link is normal and therefore it continues traffic forwarding. In this case, the route does not change and an FRR is not triggered.

When TE FRR in FA mode is enabled, nodes except the node on which FA is configured can sense the TE tunnel interface. When the primary tunnel link becomes faulty, the PLR switches traffic to the bypass tunnel through protection switching. The upstream node assumes the TE tunnel link changes and therefore it triggers an FRR.

When TE FRR in IGP Shortcut mode is enabled, nodes except the node on which FA is configured cannot sense the TE tunnel interface. When the primary tunnel link becomes faulty, the PLR switches traffic to the bypass tunnel through protection switching. On the PLR, traffic is still forwarded through the bypass tunnel. The upstream node of the PLR cannot sense the TE tunnel interface and does not trigger an FRR.

When TE FRR in IGP Shortcut mode is enabled, nodes except the node on which FA is configured cannot sense the TE tunnel interface. When the primary tunnel link becomes faulty, the PLR switches traffic to the bypass tunnel through protection switching. Though the upstream node of the PLR cannot sense the TE tunnel interface, IGP can sense the faulty link. Therefore, the upstream node triggers an FRR.

Sends group-specified query messages for group 224.1.2.3.

Deletes the record of group 224.1.2.3.

Both A and B are correct.

Neither A nor B is correct.

Bearer network delay=50 ms, allowed maximum delay = 100 ms

Bearer network delay=150 ms, allowed maximum delay = 200 ms

Bearer network delay=10s, allowed maximum delay = 20s

No strict requirement.

Option A

Option B

Option C

Option D

The interface that is bound to a CCC connection is physically Up.

MPLS is enabled on the outbound interface of the public network.

MPLS LDP is enabled on the outbound interface of the public network.

If a next hop is specified in CCC configuration, a route to the next hop is available.

If an outbound interface is specified in CCC configuration, the outbound interface is Up.

ASBRs are required to exchange VPN-IPv4 routes.

ASBRs do not exchange VPN-IPv4 route.

PEs in different ASs are connected using multi-hop EBGP for direct exchange of VPN-IPv4 routes.

Compared with Option B, Option C greatly reduces the load of the ASBR; therefore, the ASBR will no longer be a bottleneck that hinders network development.

Category 5 LSAs cannot be sent in a stub area.

A stub area cannot be connected using a virtual link.

The cost of the link between RT 1 and RT 3 is excessively large.

RT1 does not inform RT 5 that category 3 LSAs are configured by default.

232.0.0.0/24

225.0.0.0/8

232.0.0.0/8

225.0.0.0/24

After LDP FRR is enabled, a backup LSP is generated both the primary and backup LSPs are stored in the forwarding table.

LDP TFRR can be deployed on the ingress node and the intermediate node. The primary and backup LSPas are recorded in the ILM table on the intermediate node and on the FIB table on the ingress node.

After LDP FRR enable, a backup can degenerated for a primary LSP to prevent serious packet loss during fats flapping of the primary LSP.

Multiple LSPs can be up on the ingress node, that is entries about multiple backup LSPs are generated in the forwarding table according to the priority of the FRR, implementing multi-layer protection.