Study guide

FTP, TFTP, DNS, NTP, HTTP Basics

Huawei Certified ICT Associate - Datacom HCIA-Datacom H12-811 V1.0

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About HCIA-Datacom H12-811 V1.0 Study Strategies and Exam Logistics

2 Chapter 1: Network Models and Ethernet Fundamentals

OSI and TCP/IP Models Ethernet Technology and MAC Addressing Data Forwarding and Campus Network Lifecycle

3 Chapter 2: IPv4 Addressing and Transport Protocols

IPv4 Addressing and Subnetting ARP and ICMP TCP and UDP Principles Common Ports and Application Protocols

4 Chapter 3: Huawei VRP Basics and Device Management

VRP CLI Views and Core Commands Configuration Save, Reset, and File System SSH, Telnet, and Console Access Display Commands and Basic Troubleshooting

5 Chapter 4: Ethernet Switching and VLANs

Switch Forwarding and MAC Address Tables VLAN Concepts and Segmentation Access, Trunk, and Hybrid Link Types VLANIF and Inter-VLAN Routing

6 Chapter 5: STP, RSTP/MSTP, and Link Aggregation

STP Concepts and Election RSTP and MSTP Eth-Trunk Static and LACP Stacking Basics for Campus Switches

7 Chapter 6: IP Routing Fundamentals

RIB, FIB, and Forwarding Decisions Static and Default Routes on VRP Route Preference and Longest Match Floating Static Routes and Blackhole Routes

8 Chapter 7: OSPF Fundamentals

OSPF Areas and Router Types Neighbor States and Adjacency LSA Types and LSDB DR/BDR Election and VRP OSPF Configuration

9 Chapter 8: ACLs and AAA

Basic and Advanced ACLs traffic-filter Application and Matching Order AAA with Local, RADIUS, and HWTACACS

10 Chapter 9: DHCP, NAT, and Network Services

DHCP Server, Relay, and Snooping NAT, Easy IP, and NAT Server FTP, TFTP, DNS, NTP, HTTP Basics

11 Chapter 10: WLAN Basics

WLAN Architecture: AC, AP, and Fit Mode CAPWAP Tunnels and Forwarding Modes WPA2, WPA3, and WLAN Security Basics Basic WLAN Configuration Concepts

12 Chapter 11: WAN Basics

WAN Concepts and Encapsulation PPP Authentication: PAP and CHAP PPPoE Basics and Client Configuration

13 Chapter 12: IPv6 Fundamentals

IPv6 Address Types and Format Neighbor Discovery and ICMPv6 Stateful and Stateless DHCPv6 IPv6 Static Routes on VRP

14 Chapter 13: SDN and NFV Fundamentals

SDN and NFV Fundamentals

15 Chapter 14: Network Management and O&M

Network Management, O&M, and Automation Basics

FTP, TFTP, DNS, NTP, HTTP Basics

Key Takeaways Explain This Topic AI

FTP uses TCP (control port 21, data port 20 in active mode) with a reliable, session-oriented transfer; TFTP uses UDP port 69 for simple, lightweight file transfer without rich authentication.

DNS resolves human-readable names to IP addresses (primarily UDP/TCP port 53); broken DNS looks like “the network is down” even when IP connectivity works.

NTP synchronizes clocks across devices (UDP 123) so logs, certificates, and authentication timestamps remain trustworthy.

HTTP (TCP 80) and HTTPS (TCP 443) carry web applications and many device GUIs; prefer HTTPS for management and user data protection.

HCIA scenarios combine these services with ACLs, NAT, and VRP file operations—know ports, reliability differences, and which service solves which operational problem.

Last updated: July 2026

FTP, TFTP, DNS, NTP, HTTP Basics

Quick Answer: FTP (TCP 21/20) is reliable and feature-rich; TFTP (UDP 69) is simple and connectionless. DNS (port 53) maps names to IPs. NTP (UDP 123) keeps clocks aligned. HTTP/HTTPS (80/443) deliver web apps and management UIs—use HTTPS whenever credentials or sensitive data are involved.

Routing and switching move packets, but operators still depend on network services to load images, resolve names, timestamp logs, and open management pages. HCIA-Datacom expects rapid recall of how FTP differs from TFTP, what DNS and NTP provide, and how HTTP versus HTTPS affects security. Earlier port tables listed numbers; this section focuses on behavior, operational use on Huawei devices, and exam traps when services interact with ACLs and NAT.

Service map for day-2 operations

Service Primary ports Transport Operator use on campus/edge

FTP TCP 21 (control), TCP 20 (active data) TCP Transfer VRP images, patches, config archives with authentication

  • TFTP UDP 69 UDP Quick lab image/config copy; minimal overhead, weaker controls
  • DNS UDP/TCP 53 Both Resolve names for users and for device features that call hosts by name
  • NTP UDP 123 UDP Sync device clocks to a hierarchy of time servers
  • HTTP TCP 80 TCP Unencrypted web apps / some legacy device GUIs
  • HTTPS TCP 443 TCP TLS-protected web apps and secure management portals

When an ACL or firewall question says “allow image download from the jump host,” translate the human task into protocol + port + direction before choosing permit rules.

FTP: reliable file transfer

File Transfer Protocol runs over TCP , so lost segments are retransmitted and a byte stream is delivered in order. Classic model:

Client opens a control connection to the server on TCP 21 for login and commands ( GET , PUT , directory listing).

A separate data connection carries the file.

Active mode: server typically sources data from TCP 20 toward the client.

Passive mode: client initiates the data connection to a server-chosen port (easier through many firewalls).

  • Attribute FTP characteristic
  • Reliability High (TCP)
  • Authentication Username/password (and richer methods on modern servers)
  • Complexity Control + data channels; mode-sensitive firewalls
  • Encryption Original FTP is clear text—prefer FTPS/SFTP in production
  • Huawei lab use Device as FTP client or server for *.cc / software packages

Exam implications:

Blocking only TCP 21 may still confuse data channels depending on mode—know that control and data are separate .

Credentials on classic FTP can be sniffed; associate-level guidance is to prefer SSH-based SFTP (TCP 22) or other encrypted methods when the stem stresses security.

FTP is the right mental default when the scenario needs directory listing, resume, or authenticated bulk transfer rather than a tiny config blip.

TFTP: simple and lightweight

Trivial File Transfer Protocol deliberately strips features:

  • Attribute TFTP characteristic
  • Port UDP 69
  • Transport UDP (no TCP session)
  • Authentication Essentially none in classic TFTP
  • Reliability Application-level ACKs/retries; no TCP guarantees
  • Typical payload Firmware, small configs in lab or constrained environments

Because TFTP is simple, it appears in many bootstrap and lab stories. Because it lacks strong authentication and encryption, it is a poor fit for untrusted networks. HCIA items often contrast:

“Need quick unauthenticated lab transfer” → TFTP.

“Need reliable authenticated transfer of large images across a WAN” → FTP (or better, SFTP).

Exam trap: Assigning TCP 69 to TFTP, or claiming TFTP uses the same control/data split as FTP. TFTP is UDP 69 and does not use FTP’s dual TCP channels.

DNS: resolving names to addresses

Users type www.example.com , not 93.184.216.34 . Domain Name System (DNS) stores resource records and answers queries from resolvers.

  • Query path (simplified) What happens
  • Stub resolver on PC Asks configured DNS server (often learned via DHCP)
  • Recursive resolver Walks hierarchy if needed (root → TLD → authoritative)
  • Response Returns A/AAAA (and other) records; client caches per TTL

Transport notes:

Most ordinary queries use UDP 53 .

TCP 53 appears for large responses and zone transfers between servers.

Operational failures that look like “Internet is broken”:

  • User symptom Underlying issue
  • Browse by name fails; ping by IP works DNS server unreachable, wrong DHCP DNS option, or ACL blocking 53
  • Only some names fail Authoritative or cache problem for that zone
  • Slow first page load Timing out on primary DNS before secondary

On Huawei networks, ensure DHCP pools hand out reachable DNS IPs , and that security policies permit client → DNS server traffic. Devices themselves may need DNS if features reference hostnames (logging hosts, controllers, license portals).

NTP: time synchronization

Network Time Protocol keeps clocks aligned. Accurate time is not cosmetic:

  • Dependency Why time matters
  • Log correlation Incident timelines across routers, switches, firewalls, and servers
  • Certificates / TLS Validity windows; wrong clocks break HTTPS and secure management
  • Authentication systems Kerberos and some AAA methods are time-sensitive
  • Scheduled jobs Config backup or script windows fire at the wrong moment

NTP uses UDP 123 . Devices act as clients toward upstream servers and may serve downstream peers in a hierarchy (stratum levels). HCIA-level expectations:

Know why NTP exists (logs, security, consistency).

Know the port and that it is UDP .

Recognize symptoms of wrong time (TLS failures, confusing log order) as possible NTP issues.

Prefer reliable internal NTP sources or trusted Internet pools depending on design policy; random public servers without oversight can be a governance concern, but the exam cares more about protocol role than vendor pool URLs.

HTTP and HTTPS basics

HTTP is the application protocol of the web. HTTPS is HTTP over TLS .

  • Feature HTTP HTTPS
  • Default port TCP 80 TCP 443
  • Encryption None TLS-protected
  • Integrity / authenticity Weak on the wire Certificate-based server auth (and optional client certs)
  • Management use Legacy device Web UIs Preferred for modern GUIs and user apps
  • ACL implication Permit 80 only if clear text is acceptable Permit 443 for secure web

Campus relevance:

User applications (portals, SaaS) overwhelmingly need 443 outbound through NAT/Easy IP.

Device web management should not sit on the open Internet over clear HTTP when avoidable.

Captive portals and WLAN guest flows often intermingle HTTP redirects with HTTPS—know both ports appear in ACL designs.

Exam trap: Claiming HTTPS uses UDP, or swapping 80/443. Another trap: assuming NAT Server for a web server should map port 80 when the stem clearly specifies HTTPS only—map 443 unless both are required.

Putting services together with NAT, DHCP, and ACLs

Real tickets rarely isolate one protocol:

PC receives IP/gateway/ DNS via DHCP.

User opens HTTPS site → DNS query (53) then TCP 443 through Easy IP .

Engineer upgrades a switch → FTP/TFTP pull of a new image; confirm ACL allows the chosen method.

After change, logs disagree across devices → check NTP .

Partner must reach internal web tools → NAT Server for 443 plus DNS name pointing at the public IP.

  • Goal Service + related feature
  • Hosts autoconfigure DHCP (+ correct DNS/gateway options)
  • Share Internet Easy IP / source NAT
  • Publish web app NAT Server + HTTPS
  • Copy image in lab TFTP or FTP
  • Align timestamps NTP
  • Block lateral threats ACLs on ports 21/69/80/443/53 as policy dictates
  • FTP vs TFTP decision table (memorize)
  • Question Prefer FTP Prefer TFTP
  • Need authentication / accounts? Yes No (classic)
  • Large image over lossy path? Better (TCP) Riskier
  • Simplest client in tiny ROM environment? Heavier Often available
  • Untrusted network? Still encrypt (SFTP/FTPS) Avoid
  • Exam keyword “trivial” / “UDP 69” No Yes
  • Troubleshooting vignettes
  • Stem cue Likely focus
  • “Ping to 8.8.8.8 works; browser fails” DNS
  • “Certificate not yet valid” on device GUI NTP/clock
  • “Transfer aborts on large file; small file OK over same tool” Reliability path—consider TCP FTP vs UDP TFTP
  • “Internet users cannot open company portal; staff browse fine” NAT Server / inbound ACL, not DNS alone
  • “Only HTTP works; HTTPS times out” ACL or NAT port mapping missing 443
  • Practice goals for this chapter

Recite FTP vs TFTP ports, transport, and security posture in one breath each.

Trace a failed web session: DHCP options → DNS → TCP 443 → NAT.

Explain two business reasons to deploy NTP on every managed Huawei device.

Write an ACL intent list for allowing DNS and HTTPS for a user VLAN while denying clear-text device Telnet.

DHCP assigns addresses, NAT translates them at the edge, and these services keep files, names, time, and web applications usable. Together they form the network-services slice of the HCIA-Datacom blueprint—expect scenario questions that combine at least two of them on a single topology.