Huawei HCIP-Datacom study materials
Huawei HCIP-Datacom study resources

Huawei HCIP-Datacom study plan

Huawei HCIP-Datacom · Give each week a clear focus.

8 weeks · About 7 hours per week

Week 1

Datacom

  • Map the HCIP-Datacom exam blueprint into a personal checklist that lists every routing and switching topic area you must cover and rates your current confidence from 1 to 5 for each

  • Build a home lab of at least three routers and two switches in an emulator, and verify full reachability with static routes and a single IGP before the week ends

  • Configure and troubleshoot OSPFv2 in a single area, including neighbor adjacency formation, DR/BDR election, and cost-based path selection

  • Explain and demonstrate the OSPF packet types and LSA types that appear most often in troubleshooting scenarios, using packet captures to confirm each

Your checkpoint

A written lab report containing the completed blueprint checklist plus captured output (show ip ospf neighbor, show ip ospf database, routing tables) proving a working multi-area-ready OSPF topology

Week 2

Datacom

  • Configure OSPF multi-area with ABRs, stub and NSSA areas, and verify inter-area route propagation and default route injection

  • Implement route summarization and authentication in OSPF, then deliberately break each and document the symptoms you observe

  • Configure IS-IS at Level 1 and Level 2 with an L1/L2 router, and compare its adjacency and database behavior against OSPF in a written note

  • Compare OSPF and IS-IS convergence and scalability characteristics well enough to justify a design choice in a short paragraph

Your checkpoint

A convergence comparison table plus lab captures showing multi-area OSPF and multi-level IS-IS running simultaneously in one topology

Week 3

Datacom

  • Configure BGP peering (iBGP and eBGP) across at least four routers, and verify session establishment with correct source addresses and TTL handling

  • Apply and test at least six BGP path-selection attributes in order, changing one attribute at a time and recording which route wins

  • Implement route reflection and peer groups to solve the iBGP full-mesh requirement, and explain when confederation would be preferable

  • Configure prefix lists, AS-path filters, and route policies to control inbound and outbound advertisements

Your checkpoint

A decision log listing each BGP attribute test with the before/after best-path output, plus a working route-reflector design that replaces a full mesh

Week 4

Datacom

  • Configure MPLS L3VPN end to end with VRFs, MP-BGP VPNv4 address family, and RD/RT values on at least two customer sites

  • Verify label switching behavior with label stack output and explain the roles of IGP, LDP, and MP-BGP in the forwarding path

  • Deploy VXLAN with EVPN control plane in the lab, and compare it against the MPLS L3VPN design in terms of configuration and failure domains

  • Troubleshoot a deliberately broken VPN by isolating whether the fault lies in the underlay, the label distribution, or the BGP VPNv4 peering

Your checkpoint

A working MPLS L3VPN topology with captured label stacks and VRF routing tables, plus a troubleshooting flowchart for isolating underlay versus overlay faults

Week 5

Datacom

  • Configure VLANs, trunk links, link aggregation, and Spanning Tree Protocol variants, then verify loop prevention and fast convergence behavior

  • Implement inter-VLAN routing with both router-on-a-stick and Layer 3 switching, and measure the difference in throughput or configuration complexity

  • Configure DHCP, NAT, and ACLs in a branch topology, and validate that each policy blocks or permits exactly the intended traffic

  • Diagnose a Layer 2 loop scenario using STP topology output and port state changes, and document the recovery sequence

Your checkpoint

A branch office topology diagram with verified VLAN, STP, NAT, and ACL configurations, plus a written incident note on the loop scenario

Week 6

Datacom

  • Configure IPv6 addressing, OSPFv3, and IPv6 static routing, and verify dual-stack operation alongside the existing IPv4 design

  • Implement network automation using Python scripts against device APIs or NETCONF/YANG models to retrieve and push configuration

  • Use a controller-based or SDN-style workflow in the lab to provision a change, and contrast it with manual CLI provisioning

  • Apply QoS classification and queuing on a WAN link, and verify marking and scheduling with show commands

Your checkpoint

A Python script that automates one repeatable configuration task across at least three devices, with before/after configuration captures and a short write-up of the SDN versus CLI comparison

Week 7

Datacom

  • Complete a timed 60-question practice set covering routing, switching, VPN, and automation, and score each miss by topic area

  • Re-study the three weakest topic areas identified by the practice set, rebuilding each as a fresh lab exercise rather than rereading notes

  • Reconfigure one previously completed topology from scratch without notes to test retention, and time how long it takes

  • Review documentation for features you have not yet labbed and decide which to lab versus which to learn conceptually

Your checkpoint

A scored practice-set report with a ranked list of weak areas and evidence of at least three rebuilt labs addressing them

Week 8

Datacom

  • Run two full timed mock exams under exam conditions, and record both raw scores and time remaining at completion

  • Revisit every missed question from both mocks and confirm you can explain the correct answer without referring to notes

  • Do a final pass over your week 1 blueprint checklist and confirm every item is rated at least 4 out of 5 confidence

  • Prepare exam-day logistics, including scheduling, identification requirements, and a one-page summary sheet of high-risk topics for last-minute review

Your checkpoint

A final readiness report containing both mock exam scores, the completed confidence checklist, and a one-page high-risk topic summary sheet

Milestones

Week 2: You can build a multi-area OSPF and multi-level IS-IS topology from a blank emulator in under 45 minutes without notes, and explain every command you typed

Week 4: An MPLS L3VPN between two customer sites passes traffic end to end, and you can trace the label stack and explain each hop's forwarding decision aloud

Week 6: You have a working automation script that changes at least three devices, and you can describe the difference between CLI-driven and controller-driven provisioning in your own words

Week 7: Your timed practice score is at or above 75 percent with all remaining misses concentrated in no more than two topic areas

Week 8: Both full mock exams are complete, scores are stable or improving, and every blueprint item is rated 4 or 5 out of 5 confidence