H12-821_V1.0 Exam Dumps - HCIP-Datacom-Core Technology V1.0

ï‚· 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​​.

Mandatory BGP Attributes

Next_Hop : Specifies the next hop to reach the destination.

AS_Path : Lists the autonomous systems traversed, crucial for loop prevention and route selection.

Optional Attributes

MED (Multi-Exit Discriminator) and Local_Preference are optional attributes that aid in route preference but are not mandatory.

HCIP-Datacom-Core Reference

BGP attribute behavior and classifications are detailed in BGP path selection principles​​.

Comprehensive and Detailed Step-by-Step Explanation:

Firewall Session Table:

A session table is used to track active sessions. If a session remains idle for longer than the configured aging time, it is removed to free resources and enhance security.

TCP Session Timeout:

If the interval between two packets exceeds the session timeout, the firewall deletes the session information, requiring the session to be re-established.

Comprehensive and Detailed In-Depth Explanation:

A. TRUE → EBGP-learned routes can be advertised to both IBGP and EBGP peers .

B. FALSE → BGP uses incremental updates , meaning it only advertises changed routes , not all routes.

C. TRUE → BGP advertises only the best path to prevent unnecessary routing information.

D. TRUE → IBGP split-horizon rule : Routes learned from IBGP peers are not re-advertised to other IBGP peers (to prevent loops).

📖 Reference: Huawei HCIA-Datacom Study Guide, BGP Route Advertisement and Split-Horizon Rule.

Comprehensive and Detailed Step-by-Step Explanation:

1. Overview of AS_Path Attribute Modification:

The apply as-path command in a route-policy is used to modify the AS_Path attribute of routes. This is often required to influence the selection of routes or to adjust routing policies for incoming or outgoing BGP updates.

2. Parameters of the apply as-path Command:

Option A: Delete

Correct .

The delete parameter removes specific AS numbers from the AS_Path attribute. This is used to simplify or manipulate the AS_Path for specific routing policies.

Option B: Additive

Correct .

The additive parameter appends an AS number to the existing AS_Path attribute, instead of overwriting it. This is useful when you want to prepend AS numbers to influence route selection without removing the original AS_Path.

Option C: Copy

Incorrect .

The copy parameter is not supported in the apply as-path command for modifying AS_Path attributes.

Option D: Overwrite

Correct .

The overwrite parameter replaces the existing AS_Path with a new one. This provides complete control over the AS_Path attribute but removes the original AS_Path entirely.

3. Summary:

The valid parameters for the apply as-path command are delete, additive, and overwrite.

The mandatory parameters for BGP peer configuration are the peer IP address ( peer ip-address ) and AS number ( as-number ). A password is optional for MD5 authentication, and a description is an optional comment for reference. These are not required for establishing the peer relationship ​.

Comprehensive and Detailed Step-by-Step Explanation:

Bidirectional Forwarding Detection (BFD):

BFD is a lightweight protocol that provides rapid fault detection on links independent of the underlying routing protocol or media.

Requirements for BFD:

Both devices at the endpoints of the link must support and configure BFD for it to operate.

If one device does not support BFD, the feature cannot be used for link detection.