Basic Router Configuration
First Published: May 27, 2010, OL-20356-01
Last Updated: October 25, 2017
This document provides basic configuration procedures for the Cisco Connected Grid Router 2010. It also includes configuration examples and verification steps, when possible.
Basic Configuration
Interface Configuration
Routing Configuration
Default Configuration
When you boot up your Cisco router for the first time, you will notice a default 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-config
Building configuration...
Current configuration : 961 bytes
! Last configuration change at 20:41:11 UTC Thu Mar 1 1900
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
multilink bundle-name authenticated
license udi pid CISCOCGR2010/K9 sn FHH1338P007
interface GigabitEthernet0/0
ip address 172.25.212.39 255.255.255.128
interface GigabitEthernet0/1
ip default-gateway 172.25.212.1
ip route 0.0.0.0 0.0.0.0 172.19.164.1
ip route 0.0.0.0 0.0.0.0 172.25.212.1
exception data-corruption buffer truncate
scheduler allocate 20000 1000
Configuring Basic Parameters
To configure the basic parameters on the router, perform one or more of the following tasks:
Configuring Global Parameters
To configure the following global parameters for your router, perform these steps:
|
|
|
Step 1 |
configure terminal Example: Router> enable Router# configure terminal Router(config)# |
Enters global configuration mode, when using the console port. Use the following to connect to the router with a remote terminal: telnet router name or address Login: login id Password: ********* Router> enable |
Step 2 |
hostname name Example: Router(config)# hostname Router Router(config)# |
Specifies the name for the router. |
Step 3 |
enable secret password Example: Router(config)# enable secret cr1ny5ho Router(config)# |
Specifies an encrypted password to prevent unauthorized access to the router. |
Step 4 |
no ip domain-lookup Example: Router(config)# no ip domain-lookup Router(config)# |
Disables the router from translating unfamiliar words (typos) into IP addresses. |
Interface Ports
Table 1 lists the interfaces that are supported on the Cisco CGR 2010.
Table 1 Interfaces by Cisco CGR 2010 Router
|
Slots, Ports, Logical Interface, Interfaces
|
|
Onboard GE ports |
Gi0/0,Gi0/1 |
Interfaces on GRWIC |
interface 0/0/ port
interface 0/1/ port |
Interfaces on GRWIC |
interface 0/1/ port |
Configuring Gigabit Ethernet Interfaces
To manually define onboard Gigabit Ethernet interfaces, complete the following steps, in global configuration mode.
|
|
|
Step 1 |
interface gigabitethernet slot/port Example:
Router(config)# interface gigabitethernet 0/1
|
Enters the configuration mode for a Gigabit Ethernet interface on the router. |
Step 2 |
ip address ip-address mask Example:
Router(config-if)# ip address
192.168.12.2 255.255.255.0
|
Sets the IP address and subnet mask for the specified Gigabit Ethernet interface. |
Step 3 |
media-type { rj45 | sfp } Example: Router(config-if)# media-type sfp Router(config-if)# Example: Router(config-if)# media-type rj45 Router(config-if)# |
Designates SFP port as the primary media. or Designates RJ45 as the primary media. |
Step 4 |
no shutdown Example:
Router(config-if)# no shutdown
|
Enables the Gigabit Ethernet interface, changing its state from administratively down to administratively up. |
Step 5 |
exit Example:
|
Exits configuration mode for the Gigabit Ethernet interface and returns to global configuration mode. |
Configuring Grid Router WAN Interface Cards
The Cisco Connected Grid Router 2010 supports RS-232 low-speed serial Grid Router WAN Interface Cards (GRWICs) and T1/E1 channelized and clear channel GRWICs.
Configuring T1/EI GRWICs
To configure the one- and two-port channelized T1/E1 GRWICs inserted in the GRWIC slots, see Configuring 1- and 2-Port T1/E1 GRWICs Guide.
Configuring a Loopback Interface
The loopback interface acts as a placeholder for the static IP address and provides default routing information.
To configure a loopback interface perform these steps, beginning in global configuration mode:
|
|
|
Step 1 |
interface type number Example:
Router(config)# interface Loopback 0
|
Enters configuration mode for the loopback interface. |
Step 2 |
ip address ip-address mask Example:
Router(config-if)# ip address 10.108.1.1 255.255.255.0
|
Sets the IP address and subnet mask for the loopback interface. |
Step 3 |
exit Example:
|
Exits configuration mode for the loopback interface and returns to global configuration mode. |
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 with an IP address of 200.200.100.1/32, which acts as a static IP address.The loopback interface points back to virtual-template1, which has a negotiated IP address.
ip address 200.200.100.1 255.255.255.255
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 interfaces loopback 0
Loopback0 is up, line protocol is up
Internet address is 200.200.100.1/32
MTU 1514 bytes, BW 8000000 Kbit/sec, DLY 5000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation LOOPBACK, loopback not set
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Another way to verify the loopback interface is to ping it:
Router#ping 200.200.100.1
Type 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/1/1 ms
Configuring Command-Line Access
To configure parameters to control access to the router, perform these steps, beginning in global configuration mode:
|
|
|
Step 1 |
line [ aux | console | tty | vty ] line-number Example:
Router(config)# line console 0
|
Enters line configuration mode, and specifies the type of line. This example specifies a console terminal for access. |
Step 2 |
password password Example:
Router(config)# password 5dr4Hepw3
|
Specifies a unique password for the console terminal line. |
Step 3 |
login Example:
Router(config-line)# login
|
Enables password checking at terminal session login. |
Step 4 |
exec-timeout minutes [seconds ] Example:
Router(config-line)# exec-timeout 5 30
|
Sets the interval wherein the EXEC command interpreter waits until user input is detected. The default is 10 minutes. Following entry of the minutes variable, you can optionally add seconds to the interval value. This example shows a timeout of 5 minutes and 30 seconds. Entering a timeout of 0 0 specifies never to time out. |
Step 5 |
line [ aux | console | tty | vty ] line-number Example:
Router(config-line)# line vty 0 4
|
Specifies a virtual terminal for remote console access. |
Step 6 |
password password Example:
Router(config-line)# password aldf2ad1
|
Specifies a unique password for the virtual terminal line. |
Step 7 |
login Example:
Router(config-line)# login
|
Enables password checking at the virtual terminal session login. |
Step 8 |
end Example:
|
Exits line configuration mode, and returns to privileged EXEC mode. |
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.
transport input none (default)
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, perform these steps, beginning in global configuration mode:
|
|
|
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
|
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:
|
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 permanent virtual circuit.
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 route 172.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:
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, + - replicated route
Gateway of last resort is 172.25.212.1 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 172.25.212.1
172.25.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.25.212.0/25 is directly connected, GigabitEthernet0/0
L 172.25.212.39/32 is directly connected, GigabitEthernet0/0
200.200.100.0/32 is subnetted, 1 subnets
C 200.200.100.1 is directly connected, Loopback0
Configuring 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 IGRP (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 perform these steps, beginning in global configuration mode:
|
|
|
Step 1 |
router rip Example:
Router> configure terminal
Router(config)# router rip
|
Enters router configuration mode, and enables RIP on the router. |
Step 2 |
version { 1 | 2 } Example:
Router(config-router)# version 2
|
Specifies use of RIP version 1 or 2. |
Step 3 |
network ip-address Example:
Router(config-router)# network 192.168.1.1
Router(config-router)# network 10.10.7.1
|
Specifies a list of networks on which RIP is to be applied, using the address of the network of each directly connected network. |
Step 4 |
no auto-summary Example:
Router(config-router)# no auto-summary
|
Disables automatic summarization of subnet routes into network-level routes. This allows subprefix routing information to pass across classful network boundaries. |
Step 5 |
end Example:
Router(config-router)# end
|
Exits router configuration mode, and enters privileged EXEC mode. |
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-config
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.
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
10.0.0.0/24 is subnetted, 1 subnets
C 10.108.1.0 is directly connected, Loopback0
R 3.0.0.0/8 [120/1] via 2.2.2.1, 00:00:02, Ethernet0/0
Configuring Enhanced Interior Gateway Routing Protocol
To configure EIGRP perform these steps, beginning in global configuration mode:
|
|
|
Step 1 |
router eigrp as-number Example:
Router(config)# router eigrp 109
|
Enters router configuration mode, and enables EIGRP on the router. The autonomous-system number identifies the route to other EIGRP routers and is used to tag the EIGRP information. |
Step 2 |
network ip-address Example:
Router(config)# network 192.145.1.0
Router(config)# network 10.10.12.115
|
Specifies a list of networks on which EIGRP is to be applied, using the IP address of the network of directly connected networks. |
Step 3 |
end Example:
Router(config-router)# end
|
Exits router configuration mode, and enters privileged EXEC mode. |
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.
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:
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is not set
10.0.0.0/24 is subnetted, 1 subnets
C 10.108.1.0 is directly connected, Loopback0
D 3.0.0.0/8 [90/409600] via 2.2.2.1, 00:00:02, Ethernet0/0
Typical Example of a Cisco CGR 2010 Configuration
Use the show running-config command to view the configuration or the Cisco CGR 2010 after the Gigabit Ethernet and serial GRWIC ports have been configured. The following is an example of a typical Cisco CGR 2010 router that is only minimally configured:
Router# show running-config
Building configuration...
Current configuration : 1795 bytes
! Last configuration change at 03:11:17 UTC Sat Jul 7 1900
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
multilink bundle-name authenticated
crypto pki token default removal timeout 0
license udi pid CGR-2010/K9 sn FHH1338P00S
license boot module cgr2010 technology-package datak9
bstun peer-name 192.168.1.2
bstun protocol-group 1 async-generic
interface GigabitEthernet0/0
ip address 192.168.1.2 255.255.255.0
interface GigabitEthernet0/1
bstun route all tcp 192.168.1.1
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0
snmp-server community public RW
exception data-corruption buffer truncate
scheduler allocate 20000 1000
Feedback