Skip to main content

Welcome to a Grasp lesson

Create a free account to keep studying and create your own study path.

Lesson 8

Verifying Cisco IP Configuration

Recommended resources

In our last lesson, you learned how to use ping and traceroute to test network connectivity and pinpoint where a problem might be located. Now, we'll take the next logical step. Once traceroute has led you to a suspect device, how do you inspect it to find out what is wrong?

This lesson focuses on the essential Cisco IOS commands for verifying the IP configuration of an interface. We will concentrate on the show ip interface brief command—your primary tool for a quick health check—and explore related commands that provide deeper insight. Mastering these commands is fundamental for diagnosing the issues you'll encounter in your project and in any networking role.

1. The Quick Check: show ip interface brief

When you first log in to a router or switch to troubleshoot a connectivity problem, your first "go-to" command should almost always be show ip interface brief. It provides a concise, table-based summary of the status of all IP interfaces on the device, allowing you to spot problems at a glance.

6 Go-To Cisco IOS Show Commands to Troubleshoot a Router | How to Get Started in IT

This short clip from ACI Learning introduces the command and its purpose.

Watch from this introduction to see what kind of essential information this command provides.

The output of this command is packed with valuable information. Let's break it down column by column.

A typical output of the `show ip interface brief` command on a Cisco router. This summary is your starting point for IP-level verification.

Looking at the output in the image above, you see several columns:

  • Interface: The name of the interface (e.g., FastEthernet0/0, Vlan1).
  • IP-Address: The IP address assigned to the interface. "unassigned" means no IP address is configured.
  • OK?: This indicates if the configuration is considered valid. It's almost always YES.
  • Method: Shows how the IP address was configured (e.g., manual for static assignment, DHCP).
  • Status: This column reflects the Layer 1 (Physical) status.
    • up: The interface is physically active (e.g., a cable is plugged in and the device on the other end is on).
    • down: There is a physical layer issue (e.g., no cable, bad cable, other end is off).
    • administratively down: The interface has been manually disabled with the shutdown command. You must use the no shutdown command in interface configuration mode to enable it.
  • Protocol: This column reflects the Layer 2 (Data Link) status.
    • up: The data link layer protocol is functioning correctly (e.g., it's receiving keepalives).
    • down: There is a data link layer issue, such as a protocol mismatch (e.g., HDLC vs. PPP on a serial link) or a problem on the other side of the connection.

Interpreting Status and Protocol Pairs

The combination of the Status and Protocol columns is a powerful diagnostic indicator:

Status Protocol Meaning & Common Cause
up up Healthy. The interface is fully operational at both Layer 1 and Layer 2. This is the desired state.
down down Layer 1 issue. Check if the cable is plugged in correctly and if the device on the other end is powered on.
administratively down down Intentionally disabled. The interface was manually shut down. Use the no shutdown command to bring it up.
up down Layer 2 issue. The physical layer is fine, but data link layer negotiation is failing. This is common with serial links (encapsulation mismatch) or EtherChannel misconfigurations.

To see how this command is used in a real troubleshooting scenario, let's look at an example.

My Go To Cisco Troubleshooting Commands - 101Labs.net

This article from 101Labs.net demonstrates a practical troubleshooting workflow.

Read the section for "Router0". Notice how the output of show ip interface brief immediately reveals that the IP address is assigned to the wrong interface (G0/1 instead of G0/0). This is a perfect example of how this command quickly identifies configuration errors.


2. The Detailed View: show ip interface

While show ip interface brief is excellent for a quick overview, sometimes you need more detail. The show ip interface <interface_name> command provides a comprehensive look at a single interface's IP-related parameters.

Detailed output for interface FastEthernet0/0, showing its IP address, broadcast address, MTU, and other settings.

This detailed view gives you information that the brief version omits, such as:

  • The IP address and subnet mask in CIDR notation (e.g., 10.1.11.1/24).
  • The broadcast address for the subnet (10.1.11.255).
  • The Maximum Transmission Unit (MTU) size.
  • Reliability and traffic counters (useful for detecting errors).
  • Any helper addresses or access lists applied to the interface.

You can use show ip interface without specifying an interface to see this detailed output for all interfaces on the device.


3. Verifying IP Configuration on Switches

On a Layer 2 switch, you typically don't assign IP addresses to physical ports. Instead, you assign them to Switch Virtual Interfaces (SVIs), which are logical interfaces representing a VLAN. The verification commands are the same, but the interface name will be a VLAN, such as interface Vlan1 or interface Vlan20. This allows the switch to be managed remotely or to participate in routing.

The following video from Cisco demonstrates the process of configuring and verifying IP addresses on VLAN interfaces.

How to Configure IP Address Settings via CLI | Cisco Switch CLI Networking Basics

This video shows the practical steps of viewing, setting, and changing IP addresses on a Cisco switch's VLAN interfaces.

Watch the following clips to see the verification commands in action on a switch: Viewing existing IPs: Show IP interface is used to see the initial IP configuration on the switch's VLANs. Verifying a new IP: After configuring an IP on VLAN 30, the presenter uses do show IP interface to confirm the change was successful. (The do prefix allows you to run a privileged-mode command from configuration mode). Verifying a changed IP: After modifying an IP address, the command is used again from this point to verify the update.

As you can see, the same commands work for both physical router interfaces and logical switch interfaces, making them versatile tools in your toolkit.


4. Viewing the Running Configuration

Finally, to see the actual commands that were typed to create the current state, you can use the show running-config command. This displays the entire active configuration file stored in the device's RAM.

Complete Cisco Commands Cheat Sheet for Devices

This guide from Netwrix provides a reference for many fundamental commands, including how to view the device configuration.

Read the section "Displaying System Configuration". It introduces the show running-config command and distinguishes it from show startup-config.

While show running-config shows everything, it can be overwhelming. You can use a pipe (|) to filter the output for what you need. For example:

  • show running-config | include ip address: Shows only the lines containing "ip address".
  • show running-config interface GigabitEthernet0/1: Shows only the configuration specific to that interface.

This is extremely useful for confirming the exact IP address and subnet mask commands that have been applied, helping you spot typos or incorrect masks.


Conclusion

You are now equipped with the primary commands for verifying Layer 3 configurations on a Cisco device. This moves you beyond just identifying a problem's location with ping and traceroute to actively inspecting a device to find the root cause.

Key Takeaways:

  • show ip interface brief is your first and most important command for a quick summary of interface status and IP addressing.
  • Pay close attention to the Status (Layer 1) and Protocol (Layer 2) columns to rapidly diagnose where a problem lies. An "up/up" status is the goal.
  • Use show ip interface <interface_name> to get a detailed view of a specific interface's configuration, including its subnet mask and broadcast address.
  • These commands apply to both physical interfaces on routers and Switch Virtual Interfaces (SVIs) on switches.
  • Use show running-config with filters to view the exact configuration commands that have been applied to an interface.

In our next lesson, we will build on these verification skills. Now that you know how to look at the configuration, we will focus on what to look for by diagnosing common IP addressing errors like incorrect subnet masks, duplicate IP addresses, and misconfigured default gateways.