Data Forwarding and Campus Network Lifecycle

Data Forwarding and Campus Network Lifecycle

Quick Answer: Data moves from a user PC through access switching, optional aggregation, and Layer 3 gateways using MAC forwarding inside a VLAN and IP routing between networks. Huawei campus projects also follow a lifecycle—planning, design, deployment, and O&M—that frames how you build and run that path.

Knowing OSI layers and Ethernet frames is not enough until you can walk a packet through a realistic campus and explain what each device does. HCIA-Datacom also expects the broader lifecycle view: networks are planned and operated, not only configured once in a lab.

End-to-End Data Forwarding Process

Scenario setup

• PC-A: 192.168.10.10/24, gateway 192.168.10.1, VLAN 10
• PC-B: 192.168.20.20/24, gateway 192.168.20.1, VLAN 20
• Access switches: Huawei Layer 2 access
• Gateway: Huawei Layer 3 switch or router with VLANIF 10 and VLANIF 20

PC-A sends an HTTP request to PC-B. Walk the path.

Step 1 — Host determines local vs remote

PC-A masks its address and the destination. Because 192.168.20.20 is not on 192.168.10.0/24, PC-A must send to its default gateway 192.168.10.1, not directly to PC-B’s MAC.

Step 2 — ARP for the gateway (if needed)

If PC-A’s ARP table lacks 192.168.10.1, it broadcasts an ARP request: “Who has 192.168.10.1? Tell 192.168.10.10.” The gateway replies with its MAC (physical VLANIF MAC or VRRP virtual MAC). PC-A then builds an Ethernet frame:

• Destination MAC = gateway MAC
• Source MAC = PC-A MAC
• Type = IPv4
• Payload = IP packet (src 192.168.10.10, dst 192.168.20.20) with TCP and HTTP inside

Step 3 — Access switch Layer 2 forward

The access switch in VLAN 10 learns PC-A’s MAC on the access port and forwards the frame toward the port that leads to the gateway (access uplink/trunk). It does not change IP addresses. If the destination MAC is known, forwarding is unicast; if not, it floods in VLAN 10 until learning converges.

Step 4 — Layer 3 decision at the gateway

The gateway accepts the frame (destination MAC matches an interface MAC), de-encapsulates to IP, and looks up 192.168.20.20:

• Longest-match route points to connected VLANIF 20 (or a next-hop).
• TTL decrements.
• If needed, the gateway ARPs for PC-B on VLAN 20.
• It encapsulates a new Ethernet frame: source MAC = VLANIF 20 MAC, destination MAC = PC-B MAC, same IP packet inside.

Step 5 — Delivery on VLAN 20

Access switching on VLAN 20 delivers the frame to PC-B. PC-B de-encapsulates Ethernet → IP → TCP → HTTP and responds. The return path reverses the same logic: PC-B uses its gateway, which routes back to VLAN 10 and rewrites MAC headers again.

What stayed constant vs what changed

This table is pure exam gold: if a capture shows MAC change but IP constant, you crossed a router (or L3 switch).

Hub vs Switch vs Router — Behavioral Roles

Same symptom, different root cause:

• Hosts share a hub and see collisions → replace with switch / fix duplex.
• Hosts in same VLAN cannot ARP each other → check VLAN membership, not OSPF.
• Hosts in different VLANs can ping gateways but not each other → check inter-VLAN routing, ACLs, or missing routes.

Typical Huawei Campus Hierarchy

Enterprise campuses often use a three-tier model (sometimes collapsed core/aggregation in smaller sites):

Traffic patterns:

• East-west (user to local server): may stay within building aggregation if servers are local.
• North-south (user to Internet): climbs to core/border, then NAT/firewall.
• Wireless: AP at access, CAPWAP to AC (centralized) or local forwarding modes—still Ethernet/IP underneath.

For HCIA, you do not need every product SKU, but you must map functions to tiers: do not put Internet NAT solely on every access switch, and do not leave user access ports unfiltered on the core.

Campus Network Lifecycle (Huawei Exam Framing)

Huawei training materials and enterprise practice describe network construction as a lifecycle, not a one-time CLI exercise. Four stages appear repeatedly:

1. Planning

Capture business requirements and constraints:

• User counts, wired/wireless density, PoE budget
• Application needs (voice, video, office SaaS, guest Wi-Fi)
• Security zones (employees, guests, OT/IoT if present)
• Availability targets (dual uplinks, dual core, dual exit)
• Addressing plan at high level (private IPv4 ranges, dual-stack intent)
• Compliance and management (SNMP, telemetry, iMaster NCE readiness)

Output of planning: requirements document, rough scale (ports, APs, WAN bandwidth), risk list.

2. Design

Turn requirements into a buildable blueprint:

• Physical topology (star of access into aggregation, dual-homing)
• Logical design: VLAN plan, IP plan, gateway placement (distribution vs access gateway models)
• Routing design: static vs OSPF areas, default route injection
• Security design: ACL points, AAA for admin and users, guest isolation
• High availability: Eth-Trunk, stacking, VRRP, dual exits
• WLAN design: channels, power, SSID-to-VLAN mapping
• Management: OOB/in-band, NTP, syslog, SSH-only policy

Output of design: diagrams, IP/VLAN spreadsheets, template configurations, BOM (bill of materials).

3. Deployment (Implementation)

Build and verify in controlled order:

1. Rack, power, cable, label
2. Baseline VRP software version and device naming
3. Management reachability (console → SSH)
4. Underlay switching: VLANs, trunks, STP/RSTP/MSTP, Eth-Trunk
5. Underlay routing: VLANIF, OSPF/static, verification with ping/traceroute
6. Services: DHCP, WLAN, ACLs, QoS basics
7. Cutover and rollback plan

Golden rule: verify Layer 1/2 before chasing Layer 3; verify unicast before complex services. Use display interface brief, display vlan, display mac-address, display ip routing-table, and structured ping tests from user VLAN gateways.

4. O&M (Operations and Maintenance)

Keep the network healthy after go-live:

• Monitoring: interface errors, CPU/memory, optical power, AP status
• Change control: configuration backup (save, backup to server), peer review
• Fault handling: isolate layer, capture symptoms, use divide-and-conquer along the forwarding path
• Optimization: capacity upgrades, QoS tuning, wireless RF optimization
• Lifecycle hygiene: certificate expiry, password rotation, software patches
• Automation direction: scripts, Ansible, NETCONF/YANG, telemetry via NCE (covered in later chapters)

O&M closes the loop back to planning when growth or new apps appear—campus networks are living systems.

Putting Lifecycle and Forwarding Together

Imagine a university campus project:

1. Planning identifies 8,000 students, dense Wi-Fi, exam-season east-west peaks to LMS servers.
2. Design places LMS in a data VLAN reachable via aggregation L3, separates guest SSID into a firewalled VRF/VLAN, dual-homes buildings.
3. Deployment brings up access VLANs first, proves gateway ARP and inter-VLAN routing, then enables WLAN and ACLs.
4. O&M watches DHCP pool exhaustion during term start and adjusts; investigates a single building slowness as duplex/CRC on one uplink rather than “OSPF is broken.”

At every stage, the same forwarding mental model applies: MAC inside the VLAN, IP between networks, services on top.

Troubleshooting Checklist Along the Path

This layered checklist is how Huawei engineers reduce mean time to repair—and how you should structure multi-step HCIA scenario questions.

Exam Pitfalls

• Assuming PC-A ARPs directly for PC-B’s MAC when PC-B is on another subnet.
• Forgetting TTL decrement and MAC rewrite at the router.
• Placing “lifecycle” answers only as vague management speak—tie each phase to concrete deliverables (IP plan, templates, backups).
• Collapsing hub/switch/router behaviors into “they all forward packets.”
• Skipping verification order during deployment (services before underlay).

When you can narrate PC-to-PC delivery and place each task in planning → design → deployment → O&M, you have the operational mindset HCIA-Datacom expects before diving into VLAN, STP, and OSPF configuration details.