Router# show ip interface brief\n<\/code><\/pre>\nThe router will output a structured table similar to the following:<\/p>\n
Interface IP-Address OK? Method Status Protocol\nGigabitEthernet0\/0\/0 192.168.1.1 YES manual up up \nGigabitEthernet0\/0\/1 203.0.113.15 YES manual up up \nGigabitEthernet0\/0\/2 unassigned YES unset administratively down down \nVlan1 10.10.10.1 YES manual up up \nLoopback0 1.1.1.1 YES manual up up \n<\/code><\/pre>\nInterpret the columns as follows:
\n– Interface:<\/strong> The physical or virtual interface name (such as GigabitEthernet, FastEthernet, Vlan, or Loopback).
\n– IP-Address:<\/strong> The IPv4 address assigned to the interface. Interfaces showing unassigned<\/code> have no Layer 3 address configured.
\n– Method:<\/strong> How the address was assigned (manual<\/code> for static configurations, DHCP<\/code> for automated leases).
\n– Status:<\/strong> The Layer 1 physical link state (up<\/code> means a cable\/signal is detected; administratively down<\/code> indicates the port has been disabled with the shutdown<\/code> command).
\n– Protocol:<\/strong> The Layer 2 operational state (up<\/code> indicates line framing and keepalives are functioning).<\/p>\n<\/span>Step 3: Run Targeted Diagnostic Commands<\/span><\/h3>\nTo gather additional subnet masking and routing context, run these complementary commands:<\/p>\n
\n- Verify Subnet Masks:<\/strong>
\nThe brief<\/code> parameter omits subnet masks. To view the exact subnet mask configured on a specific port, execute:
\ntext
\nRouter# show ip interface GigabitEthernet0\/0\/0<\/code>
\nLook for the line stating: Internet address is 192.168.1.1\/24<\/code>.<\/li>\n- Inspect the Active Routing Table:<\/strong>
\nTo identify connected subnets and the upstream next-hop router, run:
\ntext
\nRouter# show ip route<\/code>
\nLines prefixed with C<\/code> indicate directly connected subnets and their associated router interfaces. Lines marked with S*<\/code> represent static default routes (Gateway of Last Resort).<\/li>\n<\/ol>\nKey Takeaway:<\/em> The show ip interface brief<\/code> command provides an instantaneous, comprehensive overview of all operational, administrative, and WAN IP addresses on any Cisco IOS router.<\/p>\n
\n<\/span>Default Cisco Router IP Addresses and Subnets by Model Line<\/span><\/h2>\nIf you are setting up a router fresh out of the box or following a complete factory reset, the device will not retain custom addresses. Factory default IP schemes differ significantly between Cisco’s small-business product lines and its enterprise-grade routing infrastructure.<\/p>\n
<\/span>Frequently Asked Questions<\/span><\/h3>\nWhat is the default IP address for Cisco Small Business RV Series routers?<\/h4>\n
Cisco Small Business and RV Series models (such as the RV130, RV160, RV260, RV340, and legacy RV042\/082) ship with a factory-configured LAN IP address of 192.168.1.1<\/code><\/strong> with a subnet mask of 255.255.255.0<\/code> (\/24<\/code>)<\/strong>. These devices have an active DHCP server pool enabled by default on LAN ports, automatically assigning client machines addresses in the 192.168.1.100<\/code>\u2013192.168.1.149<\/code> range.<\/p>\nWhat default IP addresses are used by Cisco Business switches and access points?<\/h4>\n
Unlike routers that claim the first host address (.1<\/code>), Cisco Business Series switches (such as the CBS220, CBS250, CBS350, and Catalyst 1200\/1300 lines) default to 192.168.1.254<\/code><\/strong> on VLAN 1 when no DHCP server is present. Cisco Business Wireless Access Points (such as the CBW140 and CBW240) default to 192.168.1.245<\/code><\/strong> for out-of-band management setup.<\/p>\nDo enterprise Cisco ISR and ASR routers have a default IP address?<\/h4>\n
Standard enterprise Cisco routers\u2014including the Integrated Services Router (ISR) 800, 1000, 1100, 4000 series and ASR platforms running Cisco IOS or IOS XE\u2014do not have an active default IP address<\/strong> in their raw factory-fresh state. All physical interfaces default to no ip address<\/code> and are placed in an administratively down<\/code> state.<\/p>\nHowever, modern ISR 1000 Series routers equipped with Day-0 WebUI bootstrapping pre-populate a temporary setup pool on VLAN 1 or GigabitEthernet 0\/0\/1 with the IP 192.168.1.1<\/code><\/strong> and an active DHCP pool named WEBUIPool<\/code>. If the configuration register has been wiped and bootstrapping is disabled, the router requires direct serial console provisioning.<\/p>\nWhat is the default management IP for Cisco Meraki MX security routers?<\/h4>\n
Cisco Meraki MX cloud-managed security appliances assign the local management IP 192.168.128.1<\/code><\/strong> with a subnet mask of 255.255.255.0<\/code> on all local LAN ports. You can also reach the local status page on a connected client by browsing to http:\/\/setup.meraki.com<\/code>.<\/p>\nWhat default login credentials accompany these factory IP addresses?<\/h4>\n\n- Cisco RV Series (Current):<\/strong> Username:
cisco<\/code> | Password: cisco<\/code><\/li>\n- Cisco RV Series (Legacy):<\/strong> Username:
admin<\/code> | Password: admin<\/code><\/li>\n- Cisco Business Devices:<\/strong> Username:
cisco<\/code> | Password: cisco<\/code><\/li>\n- Cisco ISR Day-0 WebUI:<\/strong> Username:
webui<\/code> | Password: cisco<\/code><\/li>\n- Enterprise Cisco IOS\/IOS XE:<\/strong> No default password exists. The device prompts for initial credential generation upon first boot through the console setup wizard.<\/li>\n<\/ul>\n
Key Takeaway:<\/em> Commercial and small-business Cisco models typically default to 192.168.1.1<\/code>, while modular enterprise routers require initial console bootstrapping before an IP address becomes active.<\/p>\n
\n<\/span>Recovering an Unknown or Forgotten Cisco Router IP Address via Console Cable<\/span><\/h2>\nWhen dealing with a pre-owned, legacy, or misconfigured Cisco router where DHCP is disabled and static IP assignments are unknown, standard network connections will fail. In this scenario, establishing an out-of-band serial connection bypasses network settings entirely.<\/p>\n
<\/span>Step 1: Assemble Physical Hardware<\/span><\/h3>\nConnect your management computer to the router’s physical management port:
\n1. Identify the router’s Console<\/strong> port (usually outlined in light blue or labeled with a terminal icon).
\n2. Depending on the model, use an RJ-45-to-DB9 rollover console cable with a USB-to-serial adapter, or a direct USB Type-B mini or USB-C console cable.
\n3. Plug the USB end into your computer and ensure your operating system recognizes the virtual COM port (verify in Windows Device Manager under Ports (COM & LPT)<\/em> or on macOS via ls \/dev\/cu.usbserial*<\/code>).<\/p>\n<\/span>Step 2: Configure Your Terminal Emulator<\/span><\/h3>\nLaunch a serial terminal client such as PuTTY, Tera Term, or SecureCRT. Create a serial connection pointing to your identified COM port using the standard Cisco serial connection parameters:<\/p>\n
\n\n\n| Parameter<\/th>\n | Required Value<\/th>\n<\/tr>\n<\/thead>\n |
\n\nConnection Type<\/strong><\/td>\n| Serial<\/td>\n<\/tr>\n | \nBaud Rate (Speed)<\/strong><\/td>\n9600<\/code><\/td>\n<\/tr>\n\nData Bits<\/strong><\/td>\n8<\/code><\/td>\n<\/tr>\n\n | | | | |