📘Cisco DevNet Associate (200-901 DEVASC)
Understanding Protocols and Ports
In computer networks, protocols are rules that devices follow to communicate with each other. Each protocol usually uses a port number, which is like a virtual “door” on a device. A port allows different types of traffic to be sent to the correct application on a server or device.
For example:
- A web server listens for web requests on one port (like 80 for HTTP or 443 for HTTPS).
- A network device like a router or switch may allow secure administrative access on another port (like 22 for SSH).
Ports are categorized into:
- Well-known ports: 0–1023 (used by standard services like web, SSH, email)
- Registered ports: 1024–49151 (used by applications)
- Dynamic/private ports: 49152–65535 (used temporarily for client connections)
For this exam, focus on well-known ports.
Common Protocols and Their Port Numbers
1. SSH (Secure Shell)
- Port: 22 (TCP)
- Purpose: Securely access and manage devices like routers, switches, and servers over a network.
- How it’s used in IT:
- Network engineers use SSH to log into switches or routers remotely to configure them.
- SSH encrypts all data, so login credentials and commands are secure.
- Exam tip: Remember that SSH is secure and replaces Telnet in most modern networks.
2. Telnet
- Port: 23 (TCP)
- Purpose: Provides remote access to network devices like routers and switches.
- How it’s used in IT:
- Older method for remotely managing devices.
- Sends all data in plain text, which is not secure.
- Exam tip: Telnet is mostly deprecated in real networks because of security risks. Modern networks prefer SSH.
3. HTTP (Hypertext Transfer Protocol)
- Port: 80 (TCP)
- Purpose: Transfer web pages and content over the internet or intranet.
- How it’s used in IT:
- Web servers host websites, and HTTP allows clients (browsers) to request web pages.
- Often used in internal IT dashboards or REST API calls without encryption.
- Exam tip: HTTP is not encrypted, so sensitive information can be exposed.
4. HTTPS (Hypertext Transfer Protocol Secure)
- Port: 443 (TCP)
- Purpose: Secure version of HTTP. Encrypts web traffic using TLS/SSL.
- How it’s used in IT:
- Accessing network device management portals (like Cisco DNA Center) securely.
- Secure API calls between applications.
- Exam tip: HTTPS = HTTP + encryption. Always preferred for web-based management.
5. NETCONF (Network Configuration Protocol)
- Port: 830 (TCP)
- Purpose: Provides programmatic configuration of network devices using XML or JSON over SSH.
- How it’s used in IT:
- Automates device configuration and retrieves device state in network automation.
- Often used in DevOps and network automation scripts with tools like Python or Ansible.
- Exam tip: NETCONF is designed for automated device management. Port 830 is the standard.
Quick Reference Table
| Protocol | Port | Transport | Purpose | Usage in IT |
|---|---|---|---|---|
| SSH | 22 | TCP | Secure remote device access | Configure routers/switches securely |
| Telnet | 23 | TCP | Remote device access (insecure) | Legacy device management |
| HTTP | 80 | TCP | Web traffic (non-secure) | Access internal dashboards, APIs |
| HTTPS | 443 | TCP | Secure web traffic | Access secure portals, web management, secure APIs |
| NETCONF | 830 | TCP | Network device automation | Programmatically configure and manage devices |
Exam Tips
- Remember SSH = 22, Telnet = 23, HTTP = 80, HTTPS = 443, NETCONF = 830.
- Focus on the purpose and security of each protocol.
- Know the difference between manual management (SSH/Telnet) and automated management (NETCONF).
- For automation questions, think NETCONF over SSH for secure network scripts.
