Troubleshooting / Physical LayerCCNA 200-301

Interface Up/Down: Line Protocol Down Troubleshooting

Presenting Symptom

A router or switch interface shows 'up' for the physical layer but 'down' for the line protocol in `show ip interface brief` — displayed as 'up/down'. The interface has a cable connected and the link light may be on, but no traffic passes and no routing protocol adjacencies form through this interface.

Network Context

A Cisco router with a WAN serial interface (Serial0/0/0) or LAN Ethernet interface connected to another network device. The physical cable is in place, but the line protocol will not come up. The situation also occurs on Ethernet interfaces between switches and routers.

Diagnostic Steps

Root Cause

The 'up/down' status means Layer 1 (physical) is working but Layer 2 (data link) is failing. Common causes: **1. Encapsulation mismatch (most common on serial links)** One end configured for HDLC, other configured for PPP. Both ends must match. Cisco default is HDLC; non-Cisco devices use PPP by default. **2. Missing clock rate on DCE serial interface** Serial WAN links require one end to be DCE (data communications equipment) providing a clock signal. In lab environments, the DCE end (determined by the cable type) must have `clock rate <bps>` configured, or the line protocol never comes up. **3. Keepalive mismatch** HDLC and PPP use keepalive messages to maintain the link. If one end has keepalives disabled (`no keepalive`) and the other has them enabled, the enabled end sees no keepalive responses and marks the protocol as down. **4. PPP authentication failure** PPP with CHAP or PAP authentication configured — if credentials don't match between peers, authentication fails and the protocol goes down. **5. Layer 2 misconfiguration on Ethernet (rare)** Ethernet interfaces rarely show up/down without a physical cause. If seen: check for speed mismatch (10/100/1000 auto-negotiation failure), a faulty cable that passes some Layer 1 signal but not enough for keepalives, or a bug in a specific IOS version.

Resolution

**Fix encapsulation mismatch:** ``` ! Both routers must match: Router(config)# interface Serial0/0/0 Router(config-if)# encapsulation hdlc ! or: encapsulation ppp ``` **Fix missing clock rate (DCE end in lab):** ``` ! First verify which end is DCE: Router# show controllers serial0/0/0 ! If output shows 'DCE cable': Router(config)# interface Serial0/0/0 Router(config-if)# clock rate 64000 ``` **Fix keepalive mismatch:** ``` ! Ensure both ends have keepalives enabled (default 10 seconds): Router(config-if)# keepalive 10 ! Or disable on both ends if not needed: Router(config-if)# no keepalive ``` **Fix PPP CHAP authentication:** ``` Router(config)# username R2 password cisco Router(config)# interface Serial0/0/0 Router(config-if)# encapsulation ppp Router(config-if)# ppp authentication chap ! Note: CHAP password must match on both ends, username is the neighbour hostname ```

Verification

After applying the fix: 1. `show ip interface brief` — Serial0/0/0 shows 'up up' 2. `show interfaces Serial0/0/0` — Line protocol is up, Encapsulation matches expected, no input errors accumulating 3. Routing protocol adjacency forms (check `show ip ospf neighbor` or `show ip eigrp neighbors`) 4. Ping test across the link: `ping <far-end-IP>` 5. For PPP: `show ppp all` — confirms PPP negotiation completed (LCP and NCP open)

Prevention

Best practices to prevent interface up/down issues: 1. Standardise on a single WAN encapsulation (PPP is recommended over HDLC for multi-vendor environments) 2. In labs with serial cables, always check DCE/DTE first with `show controllers` before configuring interfaces 3. Document encapsulation and authentication settings in network runbooks 4. For PPP authentication: ensure usernames match the peer's hostname exactly (case-sensitive) 5. For new WAN links: configure `no keepalive` on both ends temporarily during troubleshooting to eliminate keepalive as a variable

CCNA Exam Relevance

Interface up/down is a classic CCNA troubleshooting scenario tested in the Network Fundamentals and IP Connectivity domains. The CCNA exam expects candidates to identify the cause from show command output. Key question format: 'Router R1 shows Serial0/0/0 up/down. Which command output would BEST help identify the cause?' → show interfaces (shows encapsulation and keepalive status).

Exam Tips

CCNA exam: memorise the four interface status combinations — up/up (working), up/down (Layer 1 OK, Layer 2 failing), down/down (no physical signal), admin down/down (shutdown applied)

For serial interfaces: up/down almost always means encapsulation mismatch or missing clock rate

For Ethernet: up/down is unusual — check for a proxy ARP or keepalive issue. `show interfaces` (not show ip interface brief) shows the encapsulation and keepalive details needed to diagnose

Commands Used in This Scenario

clear counters

Resets all interface packet and error counters to zero without affecting the interface operational state, allowing a clean baseline for traffic monitoring or error rate measurement.

show interfaces

Displays detailed Layer 1 and Layer 2 statistics for all interfaces or a specific interface: line protocol state, hardware type, MAC address, MTU, bandwidth, duplex, speed, input/output rates, error counters, and queue statistics.

show ip interface brief

Displays a one-line summary of all interfaces showing the IP address assigned, operational status (up/down), and line protocol status. The fastest way to get a device health overview.

show ip ospf neighbor

Displays OSPF neighbour table showing router IDs, adjacency state, dead timer, and the interface the neighbour is reachable through.

Test Your CCNA Knowledge

Practice with scenario-based questions to prepare for the CCNA 200-301 exam.

Practice CCNA Questions