Feedback
Table Of Contents
Configuring I/O Memory Allocation
Configuring Gigabit Ethernet Interfaces
Configuring Wireless LAN Interfaces
Configuring Interface Card and Module Interfaces
Configuring a Loopback Interface
Configuring Command-Line Access
Configuring Routing Information Protocol
Configuring Enhanced Interior Gateway Routing Protocol
Basic Router Configuration
This module provides configuration procedures for Cisco 3900 series, 2900 series, and 1900 series integrated services routers (ISRs). It also includes configuration examples and verification steps whenever possible.
Note
See Appendix A, "Cisco IOS CLI for Initial Configuration" for information on how to perform the initial configuration using the Cisco Internet Operating System (IOS) command line interface on Cisco 3900 series, 2900 series, and 1900 series integrated services routers.
Basic Configuration
•
Interface Configuration
•
•
•
•
Routing Configuration
•
Default Configuration
When you boot up your Cisco router for the first time, you notice some basic configuration has already been performed. Use the show running-config command to view the initial configuration, as shown in the following example.
Router# show running-configBuilding configuration...Current configuration : 723 bytes!version 12.4no service padservice timestamps debug datetime msecservice timestamps log datetime msecno service password-encryption!hostname Router!boot-start-markerboot-end-marker!logging message-counter syslog!no aaa new-model!no ipv6 cefip source-routeip cef!!!!multilink bundle-name authenticated!!archivelog confighidekeys!!!!!interface GigabitEthernet0/0no ip addressshutdownduplex autospeed auto!interface GigabitEthernet0/1no ip addressshutdownduplex autospeed auto!interface GigabitEthernet0/2no ip addressshutdownduplex autospeed auto!ip forward-protocol nd!no ip http server!!!!!control-plane!!line con 0line aux 0line vty 0 3login!exception data-corruption buffer truncatescheduler allocate 20000 1000endConfiguring Global Parameters
To configure the global parameters for your router, follow these steps.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
For complete information on global parameter commands, see the Cisco IOS Release configuration guide documentation set.
Configuring I/O Memory Allocation
To reallocate the percentage of DRAM in use for I/O memory and processor memory on Cisco 3925E and Cisco 3945E routers, use the memory-size iomem i/o-memory-percentage command in global configuration mode. To revert to the default memory allocation, use the no form of this command. This procedure enables smartinit.
Tip
When you specify the percentage of I/O memory in the command line, the processor memory automatically acquires the remaining percentage of DRAM memory.
Example
The following example allocates 25% of the DRAM memory to I/O memory and the remaining 75% to processor memory:
Router#config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# memory-size iomem 5IO memory size too small: minimum IO memory size is 201MRouter(config)#Router(config)# memory-size iomem ?<5-50> percentage of DRAM to use for I/O memory: 5, 10, 15, 20, 25, 30, 40, 50Router(config)# memory-size iomem 25Smart-init will be disabled and new I/O memory size will take effect upon reload.Router(config)# endVerifying IOMEM Setting
Router# show runCurrent configuration : 6590 bytes!! Last configuration change at 16:48:41 UTC Tue Feb 23 2010 !version 15.1service timestamps debug datetime msecservice timestamps log datetime msecno service password-encryptionservice internal!hostname Router1!!no aaa new-model!memory-size iomem 25!Interface Ports
Table 7 lists the interfaces that are supported on Cisco 3900 series, 2900 series, and 1900 series integrated services routers.
Table 7 Interfaces by Cisco Router
Onboard GE ports
Gi0/0,Gi0/1
Gi0/0,Gi0/1
Gi0/0,Gi0/1,GI0/2
Gi0/0,Gi0/1,GI0/2
Gi0/0,Gi0/1,GI0/2, GI0/3
Onboard WLAN
Wlan-ap0
not supported
not supported
not supported
not supported
Onboard WLAN GE connection to MGF2
Wlan-Gi0/0
not supported
not supported
not supported
not supported
Onboard ISM GE interface on the PCIe
service-module-name-ISM 0/0
service-module-
name-ISM 0/0service-module-
name-ISM 0/0service-module-
name-ISM 0/0not supported
Onboard ISM GE connection to MGF
service-module-name-ISM 0/1
service-module-
name-ISM 0/1service-module-
name-ISM 0/1service-module-
name-ISM 0/1not supported
USB
usbflash0, usbflash1
usbtoken0, usbtoken1
usbflash0, usbflash1
usbtoken0, usbtoken1
usbflash0, usbflash1
usbtoken0, usbtoken1
usbflash0, usbflash1
usbtoken0, usbtoken1
usbflash0, usbflash1
usbtoken0, usbtoken1
Interfaces on HWIC and VWIC
interface0/0/ port
interface0/1/ portinterface0/0/port
interface0/1/port
interface0/2/port
interface 0/3/portinterface0/0/port
interface0/1/port
interface0/2/port
interface 0/3/portinterface0/0/port
interface0/1/port
interface0/2/port
interface 0/3/port<int>0/0/<port>
<int>0/1/<port>
<int>0/2/<port>
Interfaces on Double Wide-HWIC
interface0/1
portinterface0/1/port
interface0/3/port
interface0/1/port
interface0/3/port
interface0/1/port
interface0/3/port
<int>0/1/<port>
Interfaces on SM
not supported
not supported
interface1/port
interface1-2/port
interface1-4/portInterfaces on Double Wide-SM
not supported
not supported
not supported
interface 2/port
interface 4/portInterfaces HWIC on SM
Interfaces VWIC on SM
not supported
not supported
interface1wic-slot/port
interface1-2/wic-
slot/port7interface1-4/wic-
slot/port8interface1-2/wic-
slot/port
interface1-4/wic-
slot/port
1 On the Cisco 2901 router, the numbering format for configuring an asynchronous interface is 0/slot/port. To configure the line associated with an asynchronous interface, simply use the interface number to specify the asynchronous line. For example, line 0/1/0 specifies the line associated with interface serial 0/1/0 on a WIC-2A/S in slot 1. Similarly, line 0/2/1 specifies the line associated with interface async 0/2/1 on a WIC-2AM in slot 2.
2 MGF = multi-gigabit fabric
3 Applies only to Cisco 2951, Cisco 3925, and Cisco 3925E routers.
4 Applies only to Cisco 3945 and Cisco 3945E routers.
5 Applies only to Cisco 2951, Cisco 3925, and Cisco 3925E routers.
6 Applies only to Cisco 3945 and Cisco 3945E routers.
7 Applies only to Cisco 2951, Cisco 3925, and Cisco 3925E routers.
8 Applies only to Cisco 3945 and Cisco 3945E routers.
Configuring Gigabit Ethernet Interfaces
To manually define onboard Gigabit Ethernet (GE) interfaces, follow these steps, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Wireless LAN Interfaces
The wireless LAN interface on the Cisco 1941W router enables connection to the router through interface wlan-ap0. For more information about configuring a wireless connection, see the "Configuring the Wireless Device" section on page 1.
Configuring Interface Card and Module Interfaces
To configure interface cards and modules inserted in internal services module (ISM), enhanced high-speed WAN interface card (EHWIC), Ethernet WAN interface card (EWIC), and service module (SM) slots, see the appropriate interface card or module configuration documents on Cisco.com.
Configuring a Loopback Interface
The loopback interface acts as a placeholder for the static IP address and provides default routing information.
For complete information on the loopback commands, see the Cisco IOS Release configuration guide documentation set.
To configure a loopback interface, follow these steps, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Example
The loopback interface in this sample configuration is used to support Network Address Translation (NAT) on the virtual-template interface. This configuration example shows the loopback interface configured on the gigabit ethernet interface with an IP address of 200.200.100.1/24, which acts as a static IP address. The loopback interface points back to virtual-template1, which has a negotiated IP address.
!interface loopback 0ip address 200.200.100.1 255.255.255.0 (static IP address)ip nat outside!interface Virtual-Template1ip unnumbered loopback0no ip directed-broadcastip nat outside!Verifying Configuration
To verify that you have properly configured the loopback interface, enter the show interface loopback command. You should see verification output similar to the following example.
Router# show interface loopback 0Loopback0 is up, line protocol is upHardware is LoopbackInternet address is 200.200.100.1/24MTU 1514 bytes, BW 8000000 Kbit, DLY 5000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation LOOPBACK, loopback not setLast input never, output never, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/0, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outAnother way to verify the loopback interface is to ping it:
Router# ping 200.200.100.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 200.200.100.1, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 msConfiguring Command-Line Access
To configure parameters to control access to the router, follow these steps, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Example
The following configuration shows the command-line access commands.
You do not need to input the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
!line con 0exec-timeout 10 0password 4youreyesonlylogintransport input none (default)stopbits 1 (default)line vty 0 4password secretlogin!Configuring Static Routes
Static routes provide fixed routing paths through the network. They are manually configured on the router. If the network topology changes, the static route must be updated with a new route. Static routes are private routes unless they are redistributed by a routing protocol.
To configure static routes, follow these steps, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Step 1
ip route prefix mask {ip-address | interface-type interface-number [ip-address]}
Example:
Router(config)# ip route 192.168.1.0 255.255.0.0 10.10.10.2
Router(config)#
Specifies the static route for the IP packets.
For details about this command and about additional parameters that can be set, see Cisco IOS IP Command Reference, Volume 2 of 4: Routing Protocols, Release 12.3
Step 2
end
Example:
Router(config)# end
Router#
Exits router configuration mode, and enters privileged EXEC mode.
Example
In the following configuration example, the static route sends out all IP packets with a destination IP address of 192.168.1.0 and a subnet mask of 255.255.255.0 on the Gigabit Ethernet interface to another device with an IP address of 10.10.10.2. Specifically, the packets are sent to the configured PVC.
You do not need to enter the command marked "(default)." This command appears automatically in the configuration file generated when you use the show running-config command.
!ip classless (default)ip route 192.168.1.0 255.255.255.0 10.10.10.2!Verifying Configuration
To verify that you have properly configured static routing, enter the show ip route command and look for static routes signified by the "S."
You should see verification output similar to the following:
Router# show ip routeCodes: C - connected, S - static, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2ia - IS-IS inter area, * - candidate default, U - per-user static routeo - ODR, P - periodic downloaded static routeGateway of last resort is not set10.0.0.0/24 is subnetted, 1 subnetsC 10.108.1.0 is directly connected, Loopback0S* 0.0.0.0/0 is directly connected, FastEthernet0Configuring Dynamic Routes
In dynamic routing, the network protocol adjusts the path automatically, based on network traffic or topology. Changes in dynamic routes are shared with other routers in the network.
The Cisco routers can use IP routing protocols, such as Routing Information Protocol (RIP) or Enhanced Interior Gateway Routing Protocol (EIGRP), to learn routes dynamically. You can configure either of these routing protocols on your router.
•
•
Configuring Routing Information Protocol
To configure the RIP routing protocol on the router, follow these steps, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Example
The following configuration example shows RIP version 2 enabled in IP network 10.0.0.0 and 192.168.1.0.
To see this configuration, use the show running-config command from privileged EXEC mode.
!Router# show running-configrouter ripversion 2network 10.0.0.0network 192.168.1.0no auto-summary!Verifying Configuration
To verify that you have properly configured RIP, enter the show ip route command and look for RIP routes signified by "R." You should see a verification output like the example shown below.
Router# show ip routeCodes: C - connected, S - static, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2ia - IS-IS inter area, * - candidate default, U - per-user static routeo - ODR, P - periodic downloaded static routeGateway of last resort is not set10.0.0.0/24 is subnetted, 1 subnetsC 10.108.1.0 is directly connected, Loopback0R 3.0.0.0/8 [120/1] via 2.2.2.1, 00:00:02, Ethernet0/0Configuring Enhanced Interior Gateway Routing Protocol
To configure Enhanced Interior Gateway Routing Protocol GRP (EGRP), follow these steps, beginning in global configuration mode.
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Example
The following configuration example shows the EIGRP routing protocol enabled in IP networks 192.145.1.0 and 10.10.12.115. The EIGRP autonomous system number is 109.
To see this configuration use the show running-config command, beginning in privileged EXEC mode.
Router# show running-config...!router eigrp 109network 192.145.1.0network 10.10.12.115!...Verifying Configuration
To verify that you have properly configured IP EIGRP, enter the show ip route command, and look for EIGRP routes indicated by "D." You should see verification output similar to the following:
Router# show ip routeCodes: C - connected, S - static, R - RIP, M - mobile, B - BGPD - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter areaN1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2E1 - OSPF external type 1, E2 - OSPF external type 2i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2ia - IS-IS inter area, * - candidate default, U - per-user static routeo - ODR, P - periodic downloaded static routeGateway of last resort is not set10.0.0.0/24 is subnetted, 1 subnetsC 10.108.1.0 is directly connected, Loopback0D 3.0.0.0/8 [90/409600] via 2.2.2.1, 00:00:02, Ethernet0/0
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009-2010 Cisco Systems, Inc. All rights reserved.
