BGP does not advertise all routes learned from peers to other peers. By default, only the best (optimal) routes selected by BGP are advertised to other peers. Additionally, routes learned from IBGP peers are not forwarded to other IBGP peers unless a route reflector or confederation setup is used. The statement claiming all learned routes are advertised is false ​.

BGP, IS-IS, and OSPF support the configuration of default routes through specific command configurations. For example, BGP uses the default-originate command, IS-IS uses a default-route-advertise method, and OSPF can advertise default routes using default-information originate . ICMP, however, is not a routing protocol and does not support this functionality ​.

 ACL in Routing Policies

ACLs are frequently used in routing policies to match specific routes based on criteria such as source IP, destination IP, and more. This allows ACLs to influence route redistribution, filtering, and forwarding decisions.

 HCIP-Datacom-Core Reference

ACL applications in routing policies are discussed in the routing policy chapters​​.

VRRP defines the following states:

Initialize – The router is starting up or has not joined a VRRP group.

Backup – The router is in standby and monitors the Master.

Master – The only state where the device forwards traffic for the virtual IP address .

Only the router in the Master state owns the virtual MAC and responds to ARP for the virtual IP.

Reference from Huawei HCIP-Datacom-Core Technology Study Guide:

“In VRRP, only the Master forwards packets destined for the virtual IP address. Backup routers take over only if the Master fails.”

(Chapter: VRRP Concepts – Section: State Roles and Transitions)

All four are valid reasons why IKE (Internet Key Exchange) negotiation might not be triggered:

A – Security policy mismatches can block data flows , preventing IPsec from initiating.

B – If the route to the peer is unreachable , no packets can reach the tunnel interface, and IKE will not start.

C – If the IPsec policy is not bound to the correct interface , no protection is triggered.

D – If the ACL does not match the actual traffic , the flow will bypass IPsec.

Reference from Huawei HCIP-Datacom-Core Technology Study Guide:

“Common causes of IKE negotiation failure include incorrect ACLs, misapplied policies, unreachable peers, and misconfigured security zones.”

(Chapter: VPN Technologies – Section: IPsec Troubleshooting)

 Link fault alarm

 The BFD session goes down.

 Interrupted OSPF neighbor relationship

If VRRP is not configured to track uplink interfaces, a failure in the master device ' s uplink or link will not trigger a switchover, resulting in a traffic blackhole. The VRRP mechanism relies on interface tracking to monitor connectivity and ensure role transitions upon faults. Without this configuration, no failover occurs, and traffic directed toward the master device is lost ​.

 ACL Number Ranges

Basic ACLs : Numbered from 2000 to 2999.

Advanced ACLs : Numbered from 3000 to 3999.

Layer 2 ACLs : Numbered from 5000 to 5999.

User-defined ACLs : Numbered from 4000 to 4999.

 HCIP-Datacom-Core Reference

ACL classifications and their number ranges are covered in the ACL principles and configuration chapters​​.