|
|
This chapter includes feature-by-feature configuration procedures for Cisco 827 routers. This chapter is useful if you have a network in place and you want to add specific features.
If you prefer to use network scenarios to build a network, refer to "Network Scenarios."
This chapter contains the following sections:
Each section includes a configuration example and verification steps.
Before you configure your network, you must do the following:
To configure the router, perform the tasks described in the following sections:
A configuration file example that illustrates how to configure the network is presented after the tasks.
After your router boots, the following prompt displays. Enter no.
Would you like to enter the initial configuration dialog [yes]: no
For complete information on how to access global configuration mode, refer to the "Entering Global Configuration Mode" section in Appendix A, "Cisco IOS Basic Skills." For more information on the commands used in the following tables, refer to the Cisco IOS Release 12.0 documentation set.
Use the following table to configure the router for global parameters.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode. | Router# | configure terminal | ||
| Specify the name for the router. | Router (config)# | hostname name | ||
| Specify an encrypted password to prevent unauthorized access to the router. | Router (config)# | enable secret password | ||
| Configure the router to recognize zero subnet range as valid range of addresses. | Router (config)# | ip subnet-zero | ||
| Disable the router from translating unfamiliar words (typos) entered during a console session into IP addresses. | Router (config)# | no ip domain-lookup |
For complete information on the global parameter commands, refer to the Cisco IOS Release 12.0 documentation set.
To configure the Ethernet interface, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the Ethernet interface. | Router (config)# | interface ethernet 0 | ||
| Set the IP address and subnet mask for the Ethernet interface. | Router (config-if)# | ip address ip-address mask | ||
| Enable the Ethernet interface to change the state from administratively down to up. | Router (config-if)# | no shutdown | ||
| Exit configuration mode for the Ethernet interface. | Router (config-if)# | exit |
For complete information on the Ethernet commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on Ethernet concepts, refer to "Concepts."
The following example shows the Ethernet interface configuration. You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! interface Ethernet0 ip address 192.168.1.1 255.255.255.0 no ip directed-broadcast (default) !
To verify that you have properly configured the Ethernet interface, enter the show interface ethernet0 command. You should see a verification output like the example shown below.
router#sh int eth0 Ethernet0 is up, line protocol is up Hardware is PQUICC Ethernet, address is 0000.Oc13.a4db (bia0010.9181.1281) Internet address is 170.1.4.101/24 MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255., txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec)
Use these commands if you are using PPP encapsulation for the ATM PVC.
Use the following table to configure the dialer interface, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the dialer interface. | Router (config)# | interface dialer number | ||
| Specify the encapsulation type for the PVC as PPP. | Router (config-atm-vc)# | encapsulation ppp | ||
| Set the IP address and subnet mask for the dialer interface. | Router (config-if)# | ip address ip-address mask | ||
| Specify which dialer pool number you are using. | Router (config-if)# | dialer pool number | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Specify the encapsulation type as AAL5MUX PPP. | Router (config-atm-vc)# | encapsulation aal5mux ppp dialer | ||
| Specify a dialer pool-member. | Router (config-atm-vc)# | dialer pool-member number | ||
| Exit configuration mode for the ATM interface. | Router (config-atm-vc)# | exit |
The following example shows the dialer interface configuration. 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.
! interface atm0 pvc 1/40 encapsulation aal5mux ppp dialer dialer pool-member 1 ! interface dialer 0 ip address 200.200.100.1 255.255.255.0 encapsulation ppp dialer pool 1 !
To verify that you have properly configured the dialer interface, enter the show interface virtual-access 1 command. Both line protocol and dialer 0 should be up and running. You should see a verification output like the example shown below.
router#sh int virtual-access 1 Virtual-Access1 is up, line protocol is up Hardware is Virtual Access interface Interface is unnumbered. Using address of Dialer0 (2.2.2.1) MTU 1500 bytes, BW 100000 Kbit, DLY 100000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set
Virtual-access 1 is up means that the interface is up and running. If you see the output Virtual-access 1 is down, it means that the interface is "administratively down," and the interface is configured with the shutdown command. To bring the interface up, you must enter the no shutdown command.
To configure the ATM interface, use the following table, beginning in global configuration mode.
| Step | Task Description | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the ATM interface. | Router (config)# | interface ATM 0 | ||
| Set the IP address and subnet mask for the ATM interface. | Router (config-if)# | ip address ip-address mask | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Set the protocol broadcast for the IP address. | Router (config-if)# | protocol ip ip-address broadcast | ||
| Specify the encapsulation type for the PVC. Encapsulations can be specified as AAL5SNAP, AAL5MUX IP, or AAL5MUX PPP.1 | Router (config-atm-vc)# | encapsulation protocol | ||
| Enable the ATM interface. | Router (config-atm-vc)# | no shutdown | ||
| Exit configuration mode for the ATM interface. | Router (config-atm-vc)# | exit |
| 1This step is optional. If you specify the AAL5MUX PPP encapsulation, you will need to add an additional step to specify the dialer pool-member number using the command dialer-pool member number. |
For complete information on the ATM commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on ATM concepts, refer to "Concepts."
The following example shows the ATM interface configuration for AAL5SNAP encapsulation.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! interface ATM0 ip address 200.200.100.1 255.255.255.0 no ip directed-broadcast (default) no atm ilmi-keepalive (default) pvc 8/35 encapsulation aal5snap protocol ip 200.200.100.254 broadcast !
To verify that you have properly configured the ATM interface with AAL5SNAP encapsulation, enter the show interface atm0 command. You should see a verification output like the example shown below.
router#sh int atm0 ATM0 is up, line protocol is up Hardware is PQUICC_SAR (with Alcatel ADSL Module) Internet address is 1.1.1.1/24 MTU 1500 bytes, sub MTU 1500, BW 640 Kbit, DLY 80 usec, reliability 113/255. txload 1/255, rxload 1/255 Encapsulation aal5snap, loopback not set Keepalive not supported DTR is pulsed for 5 seconds on reset LCP Closed
The following example shows an ATM interface configuration for an AAL5MUX PPP encapsulation.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! interface ATM0 no ip directed-broadcast (default) no atm ilmi-keepalive (default) pvc 8/35 encapsulation aal5mux ppp dialer dialer pool-member 1 !
To verify that you have properly configured the ATM interface with AAL5MUX PPP encapsulation, enter the virtual-access 1 command. You should see a verification output like the example shown below.
router#sh int virtual-access 1 Virtual-Access1 is up, line protocol is up Hardware is Virtual Access interface Interface is unnumbered. Using address of Dialer0 (2.2.2.1) MTU 1500 bytes, BW 100000 Kbit, DLY 100000 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation PPP, loopback not set
Virtual-access 1 is up means that the interface is up and running. If you see the output Virtual-access 1 is down, it means that the interface is "administratively down," and the interface is configured with the shutdown command. To bring the interface up, you must enter the no shutdown command.
To configure parameters to control access to the router, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter line configuration mode, and specify the console terminal line. | Router (config)# | line console 0 | ||
| Specify a unique password on the line. | Router (config-line)# | password password | ||
| Enable password checking at terminal session login. | Router (config-line)# | login | ||
| Set the interval that EXEC command interpreter waits until user input is detected. Exec-timeout 10 0 is the default. | Router (config-line)# | exec-timeout 10 0 | ||
| Specify a virtual terminal for remote console access. | Router (config-line)# | line vty 0 4 | ||
| Specify a unique password on the line. | Router (config-line)# | password password | ||
| Enable password checking at virtual terminal session login. | Router (config-line)# | login | ||
| Exit line configuration mode, and return to privileged EXEC mode. | Router (config-line)# | end |
For complete information on the command line commands, refer to the Cisco IOS Release 12.0 documentation set.
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 0 exec-timeout 10 0 password 4youreyesonly login transport input none (default) stopbits 1 (default) line vty 0 4 password secret login !
To enable IPX routing and configure the IPX network number, use the following table, beginning in global configuration mode. You must configure IPX for every interface in the network.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enable IPX routing. | Router (config)# | ipx routing | ||
| Enter configuration mode for the Ethernet interface. | Router (config)# | interface Ethernet 0 | ||
| Enable IPX routing, assign the IPX network number, and assign the encapsulation type to the Ethernet interface. Setting the encapsulation type is optional. | Router (config-if)# | ipx network network encapsulation encapsulation-type | ||
| Exit the configuration mode for the Ethernet interface. | Router (config-if)# | exit | ||
| Enter configuration mode for the ATM interface. | Router (config)# | interface ATM 0 | ||
| Enable IPX routing, assign the IPX network number, and assign the encapsulation type to the ATM interface. Setting the encapsulation type is optional. | Router (config-if)# | ipx network network encapsulation encapsulation-type | ||
| Set the protocol broadcast. | Router (config-if)# | protocol ipx mac-address broadcast | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Specify the encapsulation type for the PVC. | Router (config-atm-vc)# | encapsulation type | ||
| Exit configuration mode for the ATM interface and the router. | Router (config-if)# | end |
For complete information on the IPX routing commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on IPX concepts, refer to "Concepts."
The ATM interface has the IPX network number assigned as 999, and the encapsulation type is specified as AAL5SNAP. IP addressing is disabled. IP directed broadcast is disabled, which prevents the translation of directed broadcasts to physical broadcasts.
! interface Ethernet0 no ip address no ip directed-broadcast (default) ipx network 888 ! interface ATM0 no ip address no ip directed-broadcast (default) ipx network 999 no atm ilmi-keepalive (default) pvc 8/35 encapsulation aal5snap protocol ipx 999.0030.8064.68a1 broadcast !
To verify that you have properly configured IPX routing, enter the show ipx interface brief command. IPX status should be up. You should see a verification output like the example shown below.
router#sh ipx interface brief Interface IPX Network Encapsulation Status IPX State ATM0 2000 SNAP up [up] Ethernet0 1000 NOVELL-ETHER up [up]
Bridges are store-and-forward devices that use unique hardware addresses to filter traffic that would otherwise travel from one segment to another. You can configure the 827 routers as pure bridges.
To configure bridging, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Disable IP routing. | Router (config)# | no ip routing | ||
| Specify the bridge protocol to define the type of Spanning-Tree Protocol (STP). | Router (config)# | bridge number protocol protocol | ||
| Enter configuration mode for the Ethernet interface. | Router (config-if)# | interface ethernet 0 | ||
| Specify the bridge-group number to which the Ethernet interface belongs. | Router (config-if)# | bridge-group number | ||
| Enable the Ethernet interface. | Router (config-if)# | no shutdown | ||
| Exit configuration mode for the Ethernet interface and the router. | Router (config-if)# | exit | ||
| Enter configuration mode for the ATM interface. | Router (config)# | interface ATM 0 | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Specify the encapsulation type for the PVC. | Router (config-atm-vc)# | encapsulation type | ||
| Specify the bridge-group number to which the ATM interface belongs. | Router (config-atm-vc)# | bridge-group number | ||
| Enable the ATM interface. | Router (config-if)# | no shutdown | ||
| Exit the configuration mode for the ATM interface. | Router (config-if)# | end |
For complete information on the bridging commands, refer to the Cisco IOS Release 12.0 documentation set. For more general concepts on bridging, refer to "Concepts."
The following configuration example uses bridging with AAL5SNAP encapsulation. You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
This configuration example shows the Ethernet and ATM interfaces configured. The Ethernet interface has IP addressing turned off for bridging, and IP directed broadcast is disabled, which prevents the translation of directed broadcasts to physical broadcasts. The bridge-group number to which the ATM interface is associated is set to 1.
The ATM interface has a PVC of 8/35, and the encapsulation is set to AAL5SNAP. The IP address is disabled for bridging and the IP directed broadcast is disabled, which prevents the translation of directed broadcasts to physical broadcasts. The bridge protocol is set to 1 to define the STP.
no ip routing ! interface Ethernet0 no ip address no ip directed-broadcast (default) bridge-group 1 ! interface ATM0 no ip address no ip directed-broadcast (default) pvc 8/35 encapsulation aal5snap ! bridge-group 1 ! ip classless (default) ! bridge 1 protocol ieee ! end
To verify that you have properly configured bridging, enter the show spanning-tree command. You should see a verification output like the example shown below.
router#sh spanning-tree Bridge group 1 is executing the IEEE compatible Spanning Tree protocol Bridge Identifier has priority 32768, address 1205.9356.0000 Configured hello time 2, max age 20, forward delay 15 We are the root of the spanning tree Port Number size is 9 Topology change flag set, detected flag set Times: hold 1, topology change 35, notification 2 hello 2, max age 20, forward delay 15 Timers:hello 1, topology change 34, notification 0 bridge aging time 15 Port 2 (Ethernet0) of Bridge group 1 is forwarding Port path cost 100, Port priority 128 Designated root has priority 32768, address 1205.9356.0000 Designated bridge has priority 32768, address 1205.9356.0000 Designated port is 2, path cost 0 Timers:message age 0, forward delay 0, hold 0 BPDU:sent 0, received 0 Port 3 (ATM0 RFC 1483) of Bridge group 1 is forwarding Port path cost 1562, Port priority 128 Designated root has priority 32768, address 1205.9356.0000 Designated bridge has priority 32768, address 1205.9356.0000 Designated port is 3, path cost 0 Timers:message age 0, forward delay 0, hold 0 BPDU:sent 0, received 0
To configure static routing, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Set up a best route for packets destined for networks unknown by the router. | Router (config)# | ip classless | ||
| Specify the static route for the IP packets. | Router (config)# | ip route network-number mask | ||
| Exit router configuration mode. | Router (config)# | end |
For complete information on the static routing commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on static routing, refer to "Concepts."
In the following configuration example, the static route is sending all IP packets with a destination of 1.0.0.0 and a subnet mask of 255.0.0.0 out on the ATM interface to another device with an IP address of 14.0.0.1. Specifically, the packets are being sent to the configured PVC.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! ip classless (default) ip route 1.0.0.0 255.0.0.0 atm0 14.0.0.1 no ip http server (default) !
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 a verification output like the example shown below.
router#sh ip route
Codes:C - connected, S - static, I - IGRP, 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, E - EGP
i - IS-IS, 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 0.0.0.0 to network 0.0.0.0
5* 2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Ethernet0/0
S* 0.0.0.0/0 is directly connected, Ethernet0/0
In dynamic routing, the network protocol adjusts the path automatically based on network traffic or topology. Changes in dynamic routing are shared with other routers in the network.
The IP routing protocol can use RIP or Enhanced IGRP to learn routes dynamically. You can configure either one of these routing protocols.
To configure RIP routing protocol on the router, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter router configuration mode and enable RIP on the router. | Router (config)# | router rip | ||
| Specify use of RIP version 2. | Router (config-router)# | version 2 | ||
| Specify the network number for each directly connected network. | Router (config-router)# | network network-number | ||
| Disable automatic summarization of subnet routes into network-level routes. This allows subprefix routing information to transmit across classful network boundries. | Router (config-router)# | no auto-summary | ||
| Exit router configuration mode. | Router (config-router)# | end |
For complete information on the dynamic routing commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on RIP, refer to "Concepts."
The following configuration shows RIP version 2 enabled in IP network 10.10.10.0.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! router rip version 2 network 10.0.0.0 no auto-summary !
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#sh ip route
Codes:C - connected, S - static, I - IGRP, 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, E - EGP
i - IS-IS, 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
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Ethernet0/0
R 3.0.0.0/8 [120/1] via 2.2.2.1, 00:00:02, Ethernet0/0
To configure IP Enhanced IGRP, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter router configuration mode and enable Enhanced IGRP on the router. The autonomous-system number identifies the route to other Enhanced IGRP routers and is used to tag the Enhanced IGRP information. | Router (config)# | router eigrp autonomous-system | ||
| Specify the network number for each directly connected network. | Router (config-router)# | network network-number | ||
| Exit router configuration mode. | Router (config-router)# | end |
For complete information on the IP Enhanced IGRP commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on Enhanced IGRP concepts, refer to "Concepts."
The following configuration shows Enhanced IGRP routing protocol enabled in IP networks 10.0.0.0 and 172.17.0.0. The Enhanced IGRP autonomous system number is assigned as 100.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! router eigrp 100 network 10.0.0.0 network 172.17.0.0 !
To verify that you have properly configured IP Enhanced IGRP, enter the show ip route command and look for Enhanced IGRP routes signified by "D." You should see a verification output like the example shown below.
router#sh ip route
Codes:C - connected, S - static, I - IGRP, 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, E - EGP
i - IS-IS, 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
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Ethernet0/0
D 3.0.0.0/8 [90/409600] via 2.2.2.1, 00:00:02, Ethernet0/0
This section describes how to configure addressing using Network Address Translation (NAT) and Easy IP Phase 1 and 2.
You can configure NAT for either static or dynamic address translations.
To configure static or dynamic inside source translation using NAT, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Create pool of global IP addresses for NAT. | Router (config)# | ip nat pool name start-ip end-ip {netmask netmask | prefix-length prefix-length} | ||
| Define a standard access list permitting addresses that need translation. | Router (config)# | access-list access-list-number permit source [source-wildcard] | ||
| Enable dynamic translation of addresses permitted by access list to one of addresses specified in pool. | Router (config)# | ip nat inside source list access-list-number pool name | ||
| Enable static translation of specified inside local address to globally unique IP address. This command is optional. | Router (config)# | ip nat inside source static local-ip global-ip number extendable | ||
| Enter configuration mode for Ethernet interface. | Router (config)# | interface ethernet 0 | ||
| Establish Ethernet interface as inside interface. | Router (config-if)# | ip nat inside | ||
| Exit configuration mode for Ethernet interface. | Router (config-if)# | exit | ||
| Enter configuration mode for ATM interface. | Router (config)# | interface atm 0 | ||
| Establish ATM interface as outside interface. | Router (config-if)# | ip nat outside | ||
| Exit configuration mode for ATM interface. | Router (config-if)# | exit |
For complete information on the NAT commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on NAT concepts, refer to "Concepts."
The following configuration shows NAT configured for the Ethernet and ATM interfaces.
The Ethernet 0 interface has an IP address of 192.168.1.1 with a subnet mask of 255.255.255.0. NAT is configured for inside, which means that the interface is connected to the inside network that is subject to NAT translation.
The ATM 0 interface has an IP address of 200.200.100.1 and a subnet mask of 255.255.255.0. NAT is configured for outside, which means that the interface is connected to an outside network, such as the Internet.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! interface Ethernet0 ip address 192.168.1.1 255.255.255.0 no ip directed-broadcast (default) ip nat inside ! interface ATM0 ip address 200.200.100.1 255.255.255.0 no ip directed-broadcast (default) ip nat outside no atm ilmi-keepalive (default) pvc 8/35 encapsulation aal5snap ! ip route 0.0.0.0.0.0.0.0 200.200.100.254 ! ip nat pool test 200.200.100.1 200.200.100.1 netmask 255.255.255.0 ip nat inside source list 101 pool test overload ip classless (default) !
To verify that you have properly configured NAT, enter the show ip nat statistics command. You should see a verification output like the example shown below.
router#sh ip nat statistics
Total active translations:45 (10 static, 35 dynamic; 45 extended)
Outside interfaces:
ATM0
Inside interfaces:
Ethernet0
Hits:34897598 Misses:44367
Expired translations:119305
Dynamic mappings:
-- Inside Source
access-list 1 pool homenet refcount 14
pool homenet:netmask 255.255.255.0
start 200.200.100.1 end 200.200.100.1
type generic, total addresses 1, allocated 1 (100%), misses
This section explains how to configure Easy IP (Phase 1). Easy IP Phase 1 includes NAT overload and PPP/Internet Protocol Control Protocol (IPCP). NAT overload means that you can use one registered IP address for the interface and use it to access the Internet from all devices in the network.
With PPP/IPCP, both models of the Cisco 827 routers automatically negotiate a globally unique (registered or public) IP address for the interface from the ISP route.
To configure Easy IP (Phase 1), use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Define a standard access list that permits nonregistered IP addresses of hosts. | Router (config)# | access-list access-list-number permit source [source-wildcard] | ||
| Set up translation of addresses identified by the access list defined in Step 1. | Router (config)# | ip nat inside source list access-list-number interface interface overload | ||
| Enter configuration mode for Ethernet interface. | Router (config)# | interface ethernet 0 | ||
| Establish the Ethernet interface as inside interface for NAT. | Router (config-if)# | ip nat inside | ||
| Enable the Ethernet interface and the configuration changes just made to it. | Router (config-if)# | no shutdown | ||
| Exit configuration mode for Ethernet interface. | Router (config-if)# | exit | ||
| Enter configuration mode for the dialer interface. | Router (config-if)# | interface dialer | ||
| Assign a negotiated IP address to the dialer interface. | Router (config-if)# | ip address negotiated | ||
| Establish the dialer interface as the outside interface for NAT. | Router (config-if)# | ip nat outside | ||
| Specify which dialer pool number you are using. | Router (config-if)# | dialer pool number | ||
| Exit the dialer interface. | Router (config-if)# | exit | ||
| Enter configuration mode for the ATM interface. | Router (config)# | interface ATM 0 | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci
| ||
| Specify the encapsulation type for the PVC to be AAL5MUX PPP and point back to the dialer interface. | Router (config-atm-vc)# | encapsulation aal5mux ppp dialer | ||
| Specify which dialer pool-member you are using. | Router (config)# | dialer pool-member number | ||
| Enable the interface and configuration changes just made to the ATM interface. | Router (config-atm-vc)# | no shutdown | ||
| Exit configuration mode for the ATM interface. | Router (config-atm-vc)# | exit |
For complete information on the Easy IP commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on Easy IP (Phase 1) concepts, refer to "Concepts."
This section explains how to configure the Cisco 827 routers as DHCP servers.
The Easy IP (Phase 2) feature combines DHCP server and relay. With DHCP, LAN devices on an IP network (DHCP clients) can request IP addresses from the DHCP server. The DHCP server allocates IP addresses from a central pool as needed. A DHCP server can be a workstation, PC, or a Cisco router. With the DHCP relay feature configured on the Cisco 827 routers, the routers can relay IP address requests from the LAN interface and to the DHCP server as shown in Figure 3-1.
To configure the router as a DHCP server, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter DHCP configuration mode, and create a pool of IP addresses that can be assigned to DHCP clients. | Router (config)# | ip dhcp pool name | ||
| Specify a range of IP addresses that can be assigned to the DHCP clients. | Router (dhcp-config)# | network ip-address subnet-mask | ||
| Configure the domain name. | Router (dhcp-config)# | domain-name domain name | ||
| Designate the router as the default router, and specify an IP address. | Router (dhcp-config)# | dns-server ip-address | ||
| Configure the netbios name server. | Router (dhcp-config)# | netbios-name-server ip-address | ||
| Configure the DNS server. | Router (dhcp-config)# | default-router ip-address | ||
| Specify the duration of the lease. | Router (dhcp-config)# | lease days hours minutes | ||
| Exit DHCP configuration mode. | Router (dhcp-config)# | exit |
For more information on the features not used in this configuration, refer to the Cisco IOS DHCP Server feature module. For more general information on DHCP servers, refer to "Concepts."
The following configuration shows a DHCP server configuration for the IP address 20.1.1.2.
! ip dhcp pool CLIENT network 20.20.20.0 255.255.255.0 domain-name cisco.com default-router 20.20.20.20 netbios-name-server 1.1.1.1 dns-server 1.1.1.2 lease 0 1 !
To verify that you have properly configured the DHCP server, enter the show dhcp server command and look for the assigned server IP. You should see a verification output like the example shown below.
router# sh dhcp server show ip dhcp binding show ip dhcp conflict show ip dhcp server statics
This section describes how to configure the router to forward UDP broadcasts, including IP address requests, from DHCP clients.
To configure the DHCP relay, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the Ethernet interface. | Router (config)# | interface Ethernet 0 | ||
| Forward default UDP broadcasts including IP configuration requests to the DHCP server. | Router (config-if)# | ip helper-address address | ||
| Enable the Ethernet interface and the configuration changes. | Router (config-if)# | no shutdown | ||
| Exit configuration mode for the Ethernet interface. | Router (config-if)# | exit |
For complete information on the DHCP relay commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on DHCP relays, refer to "Concepts."
The following configuration contains commands relevant to DHCP relay only.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! int Ethernet0 ip address 192.168.100.1 255.255.255.0 ip helper-address 200.200.200.1 !
To verify that you have properly configured the DHCP relay, enter the show dhcp server command. You should see a verification output like the example shown below.
router#sh dhcp server
DHCP server:2.2.2.2
Leases: 0
Offers: 0 Requests:0 Acks:0 Naks:0
Declines:0 Releases:0 Bad: 0
Cisco 827 routers support the Terminal Access Controller Access Control System Plus (TACACS+) protocol through Telnet. TACACS+ is a Cisco proprietary authentication protocol that provides remote access authentication and related network security services, such as event logging. User passwords are administered in a central database rather than in individual routers. TACACS+ also provides support for separate modular authentication, authorization, and accounting (AAA) facilities that are configured at individual routers.
To include one or more extended access lists in your router configuration, you can use the following commands, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Permit any host on the network to access any Internet server. | Router (config)# | access-list 100 permit tcp any ip ip address-mask established | ||
| Deny any Internet host from spoofing any host on the network. | Router (config)# | access-list 100 deny ip ip adddress-mask any | ||
| Permit Internet DNS server to send TCP replies to any host on the network. | Router (config)# | access-list 100 permit tcp host ip address-mask | ||
| Permit Internet DNS server to send UDP replies to any host on the network. | Router (config)# | access-list 100 permit udp host ip address-mask | ||
| Permit SMTP mail server to access any Internet server. | Router (config)# | access-list 100 permit tcp any host ip address | ||
| Permit web server to access any Internet server. | Router (config)# | access-list 100 permit tcp any host ip address | ||
| Permit FTP server to access any Internet server. | Router (config)# | access-list 100 permit tcp any host ip address | ||
| Restrict any Internet host from making a Telnet connection to any host on the network. | Router (config)# | access-list 100 deny tcp any ip address-mask | ||
| Enter configuration mode for the ATM interface. | Router (config)#
| interface atm 0 | ||
| Activate access list 100. | Router (config-if)# | ip access-group 100 in | ||
| Enable interface and configuration changes made to the interface. | Router (config-if)# | no shutdown | ||
| Exit configuration mode for the ATM interface. | Router (config-if)# | exit |
For more complete information on the extended access list commands, refer to the Cisco IOS Release 12.0 documentation set. For information on TCP and UDP port assignments, refer to "Common Port Assignments."
This configuration shows an access list being applied to IP address 192.168.1.0.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! access-list 101 permit tcp any host 192.168.1.0 0.0.0.255 !
This section describes how to configure Quality of Service (QOS) parameters. The requirements for voice QoS are:
You can configure QoS in a single or multiple PVC environment. In a single PVC environment, the traffic relies on IOS to provide priority queuing, using Class Based Weighted Fair Queuing (CBWFQ) to prioritize voice traffic and MTU size reduction to perform Layer 3 fragmentation of data packets. In a multiple PVC environment, the traffic relies on the ATM interface to provide priority queuing for voice and fragmentation and interleaving.
For complete information on the QoS commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on QoS concepts, refer to "Concepts."
In the single PVC environment, the traffic relies on IOS to provide priority queuing (using CBWFQ). The tasks to configure a single PVC environment are:
IP precedence gives voice packets a higher priority than other IP data traffic. The ip precedence command is used by the Cisco 827 router to differentiate voice traffic from data traffic. So you need to ensure that the data IP packets do not have the same IP precedence as that of the voice packets.
To configure real-time voice traffic precedence over other IP network traffic, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter the dial peer configuration mode to configure a VoIP dial peer. | Router (config-dial-peer)# | dial-peer voice number voip | ||
| Set a destination pattern. | Router (config-dial-peer) | destination-pattern number | ||
| Specify a destination IP address for the dial peer. | Router (config-dial-peer)# | session target {ipv4:destination-address} | ||
| Select a precedence level for the voice traffic associated with that dial peer. | Router (config-dial-peer) | ip precedence number | ||
| Exit configuration mode for the dial peer interface. | Router (config-if)# | exit |
To create a policy map and associate a priority queue to the voice class, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Configure an access list to match voice packets. | Router (config)# | access-list 101 permit ip any any precedence 5 | ||
| Configure a voice class. | Router (config)# | class-map voice | ||
| Associate the voice class with the access list. | Router (config-cmap)# | match access-group 101 |
To associate the policy map to the ATM PVC and decrease the MTU of the ATM interface so large data packets are fragmented, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Configure a policy map1. | Router (config)# | policy map name | ||
| Specify the class for queuing. | Router (config-pmap)# | class voice | ||
| Specify the priority for queuing. | Router (config-pmap-c)# | priority bandwidth | ||
| Exit configuration mode for the policy map. | Router (config-pmap-c)# | exit |
| 1Total bandwidth for the policy map may not exceed 75 percent of the total PVC bandwidth. |
To associate the policy map to the ATM PVC and decrease the MTU, use the following table, beginning in global configuration mode. It is recommended that 300 is used for the MTU size because it is larger than the size of the voice packets generated by the different codecs.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the ATM interface. | Router (config)# | interface ATM 0 | ||
| Set the IP address and subnet mask for the ATM interface. | Router (config-if)# | ip address ip-address mask | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Specify the encapsulation type for the PVC. Encapsulations can be specified as AAL5SNAP or AAL5MUX PPP. | Router (config-atm-vc)# | encapsulation protocol | ||
| Associate the service policy name. | Router (config-atm-vc)# | service policy out name | ||
| Specify the service class. | Router (config-atm-vc)# | vbr-rt pcr scr bs
| ||
| Exit configuration mode for the ATM PVC. | Router (config-atm-vc)# | exit | ||
| Specify the MTU for the ATM interface. | Router (config-atm)# | mtu number | ||
| Enable the ATM interface. | Router (config-atm-vc)# | no shutdown | ||
| Exit configuration mode for the ATM interface. | Router (config-atm-vc)# | exit |
The following example shows a voice QoS configuration in a single PVC environment using AAL5SNAP encapsulation.
! dial-peer voice 105 voip destination-pattern 3.. session target ipv4:10.1.2.3 ip precedence 5 access-list 101 permit ip any any precedence critical class-map voice match access-group 101 policy-map mypolicy class voice priority 480 int atm0 mtu 300 pvc 8/35 encapsulation aal5snap service-policy out mypolicy vbr-rt 640 640 10 !
In a multiple PVC environment, the traffic relies on the ATM interface to provide priority queuing for voice and fragmentation and interleaving. The following figures show the configurations that you can use.
Figure 3-2 shows voice and data packets on different subnets. You can have all voice traffic on an ATM PVC with a vbr-rt service class while the data traffic is transported on an ATM PVC with a ubr service class.
Use this table to configure the ATM interface and subinterfaces, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Specify the ATM0.1 subinterface. | Router (config-if)# | interface ATM 0.1 point-to-point | ||
| Set the IP address and subnet mask for the ATM0.1 subinterface. | Router (config-if)# | ip address ip-address mask | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Specify the encapsulation type for the PVC. | Router (config-atm-vc)# | encapsulation type | ||
| Set the protocol broadcast for the IP address. | Router (config-atm-vc)# | protocol ip address broadcast | ||
| Specify the ATM0.2 subinterface. | Router (config-if)# | interface ATM 0.2 point-to-point | ||
| Set the IP address and subnet mask for the ATM0.2 subinterface. | Router (config-if)# | ip address ip-address mask | ||
| Create an ATM PVC for each end node with which the router communicates. | Router (config-if)# | pvc vpi/vci | ||
| Specify the encapsulation type for the PVC. | Router (config-atm-vc)# | encapsulation type | ||
| Set the protocol broadcast for the IP address. | Router (config-atm-vc)# | protocol ip address broadcast | ||
| Exit configuration mode for the ATM interface. | Router (config-if)# | exit |
The following example shows a voice QoS configuration with all data traffic on the 30.0.0.1 network and all voice traffic on the 20.0.0.1 network.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! interface ATM0.1 point-to-point ip address 20.0.0.1 255.0.0.0 no ip directed-broadcast (default) pvc 1/100 protocol ip 20.0.0.2 broadcast vbr-rt 424 424 5 encapsulation aal5snap ! interface ATM0.2 point-to-point ip address 30.0.0.1 255.0.0.0 no ip directed-broadcast (default) pvc 1/101 protocol ip 30.0.0.2 broadcast encapsulation aal5snap
Figure 3-3 shows voice and data packets on the same subnet using virtual circuit bundling. Virtual circuit bundling allows multiple PVC's on the same bundle. Using virtual circuit bundling and assigning precedence 5 to voice packets and not data packets ensures that traffic for the two are separated onto two PVCs.
The tasks to configure a voice and data network on the same subnet with virtual circuit bundling are:
Use this table to configure the ATM interface, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the ATM interface. | Router (config)# | interface ATM 0 | ||
| Set the IP address and subnet mask for the ATM interface. | Router (config-if)# | ip address ip-address mask | ||
| Specify a bundle name. | Router (config-if)# | bundle name | ||
| Specify the encapsulation type for the voice bundle PVC. | Router (config-is-atm-bundle)# | encapsulation protocol | ||
| Set the protocol broadcast for the IP address. | Router (config-is-atm-bundle)# | protocol ip ip-address broadcast | ||
| Create a PVC for the voice bundle. | Router (config-is-atm-bundle)# | pvc-bundle name vpi/vci | ||
| Set the service class for the voice bundle.1 | Router (config-is-atm-bundle)# | vbr-rt pcr scr bs | ||
| Select an IP precedence level specific to the voice bundle that you created. | Router (config-is-atm-bundle) | ip precedence number | ||
| Create a PVC for the data bundle. | Router (config-is-atm-bundle)# | pvc-bundle name vpi/vci | ||
| Set the service class for the data2 bundle. | Router (config-is-atm-bundle)# | ubr pcr | ||
| Set the IP precedence level other to the data bundle that you created. | Router (config-is-atm-bundle) | precedence other | ||
| Exit configuration mode for the ATM interface. | Router (config-is-atm-bundle)# | exit |
| 1For voice, the service class must be vbr-rt or vbr-nrt. 2For data, the service class must be vbr-nrt or ubr. |
To configure real-time voice traffic precedence over other IP network traffic, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter the dial peer configuration mode to configure a VoIP dial peer. | Router (config-dial-peer)# | dial-peer voice number voip | ||
| Set a destination pattern. | Router (config-dial-peer) | destination-pattern number | ||
| Specify a destination IP address for the dial peer. | Router (config-dial-peer)# | session target {ipv4:destination-address} | ||
| Select a precedence level for the voice traffic associated with that dial peer. | Router (config-dial-peer) | precedence number |
The following configuration shows both voice and data on the same subnet with virtual circuit bundling. IP precedence is set to 5 for the voice packets, but not for the data packets so that the traffic can be separated onto two different ATM PVCs.
! interface atm0 ip address 20.0.0.1 255.0.0.0 bundle test encapsulation aal5snap protocol ip 20.0.0.2 broadcast ! pvc-bundle voice 1/100 vbr-rt 424 424 5 precedence 5 ! pvc-bundle data 1/101 precedence other ! dial-peer voice 100 voip destination-pattern 26.. session target ipv4:20.0.0.8 ip precedence 5 !
You should configure multilink PPP fragmentation if you have point-to-point connection using PPP encapsulation or links slower than 2 Mbps in your network.
PPP support for interleaving can be configured on dialer or PRI interfaces.
To configure multilink PPP and interleaving on a dialer interface, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the dialer interface. | Router (config)# | interface dialer | ||
| Enable multilink PPP for the dialer interface. | Router (config-if) | ppp multilink | ||
| Specify the bandwidth number associated with the PVC that is using the dialer interface, where n is the value of the sustained cell rate (SCR) parameter of the PVC using that dialer interface.This is important because otherwise the dialer interface will assume a value of 100 kbps if a specific class of service is configured. | Router (config-if) | bandwidth n | ||
| Enable interleaving for RTP packets among the fragments of larger packets on a multilink PPP bundle. | Router (config-if) | ppp multilink interleave | ||
| Configure a maximum fragment delay of 20 ms. This command is optional. | Router (config-if) | ppp multilink fragment-delay milliseconds | ||
| Reserve a special queue for real-time packet flows to specified destination UDP ports, allowing real-time traffic to have higher priority than other flows. This only applies if you have not configured RSVP. | Router (config-if) | ip rtp reserve lowest-UDP-port range-of-ports [maximum-bandwidth] | ||
| Exit configuration mode for the dialer interface. | Router (config-if)# | exit |
For complete information on the PPP fragmentation and interleaving commands, refer to the Dial Solutions Configuration Guide for Cisco IOS Release 12.0T. For more general information on PPP fragmentation and interleaving concepts, refer to "Concepts."
The following configuration defines a dialer interface that enables multilink PPP with interleaving and a maximum real-time traffic delay of 20 ms. The encapsulation type is defined as aal5mux.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! interface dialer 1 ppp multilink encapsulated ppp ppp multilink interleave bandwidth 640 ppp multilink fragment-delay 20 ip rtp reserve 16384 100 64 ! interface ATM0 pvc 8/35 encapsulation aal5mux ppp dialer dialer pool-member 1
To verify that you have properly configured PPP fragmentation and interleaving, enter the debug ppp multilink fragment command, then send out one 1500-byte ping packet. The debug message will display information about the fragments being transmitted.
IP precedence gives voice packets a higher priority than other IP data traffic. The ip precedence command should also be used if RSVP is not enabled and you would like to give voice packets a priority over other IP data traffic. IP precedence scales better than RSVP, but it provides no admission control.
To configure real-time voice traffic precedence over other IP network traffic, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode. | Router# | configure terminal | ||
| Enter the dial peer configuration mode to configure a VoIP dial peer. | Router (config-dial-peer)# | dial-peer voice number voip | ||
| Set a destination pattern. | Router (config-dial-peer) | destination-pattern number | ||
| Select a precedence level for the voice traffic associated with that dial peer. | Router (config-dial-peer) | ip precedence number |
For complete information on the IP precedence commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on IP precedence, refer to
"Concepts."
This configuration example shows a voice configuration with IP precedence set. The IP destination target is set to 8 dialing digits, which automatically sets the IP precedence to 5 by the Cisco 827 routers. The dial peer session target is RAS, which is a protocol that runs between the H.323 voice protocol gateway and gatekeeper.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! access-list 101 permit route-map data permit 10 set ip precedence routing !
To minimally configure RSVP for voice traffic, you must enable RSVP on each interface where priority needs to be set. The RSVP feature applies to a single-PVC network only.
By default, RSVP is disabled so that it is backwards compatible with systems that do not implement RSVP. To enable RSVP for IP on an interface, use the following interface configuration command:
Router(config-if)# ip rsvp bandwidth [interface-kbps] [single-flow-kbps]This command starts RSVP and sets the bandwidth and single-flow limits. The default maximum bandwidth is up to 75 percent of the bandwidth available on the interface. By default, a flow can reserve up to the entire reservable bandwidth.
On subinterfaces, RSVP applies to the more restrictive of the available bandwidths of the physical interface and the subinterface.
After enabling RSVP, you must also use the req-qos dial-peer configuration command to request an RSVP session on each VoIP dial peer. Otherwise, no bandwidth is reserved for voice traffic.
To request an RSVP session on each VoIP dial peer, use the following table, beginning in global configuration mode:
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the dial peer. | Router (config)# | configure dial-peer | ||
| Assign the dial peer voice number to configure a VoIP dial peer. | Router (config-dial-peer) | dial-peer voice number voip | ||
| Request an RSVP session for each dial peer. | Router (config-dial-peer) | req-qos controlled load |
For more information about configuring RSVP, refer to the "Configuring RSVP" chapter of the Network Protocols Configuration Guide, Part 1, for Cisco IOS Release 12.0T. For more general information on RSVP commands, refer to "Concepts."
This configuration shows two voice dial peers (number 211 and 212) being configured for RSVP.
You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! dial-peer voice 211 voip req-qos controlled-load ! dial-peer voice 212 voip req-qos controlled-load !
The Cisco 827 routers support voice using the H.323 signaling protocol.
Before you can configure your router to use voice, you need to perform the following tasks:
This section describes the tasks you need to perform to configure the router for H.323 signaling on the voice ports.
To configure the POTS dial peers, use the following table, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the dial peer. | Router (config)# | dial-peer voice number POTS | ||
| Define the destination telephone number associated with the VoIP dial peer. | Router (config-dial-peer)# | destination-pattern string | ||
| Specify the port number. | Router (config-dial-peer)# | port number |
Follow the steps below to configure voice dial peers for H.323 signaling, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the dial peer. | Router (config)# | dial-peer voice number VoIP | ||
| Define the destination telephone number associated with each VoIP dial peer. | Router (config-dial-peer)# | destination-pattern string | ||
| Specify a codec if you are not using the default codec of g.729. | Router (config-dial-peer)# | codec string | ||
| Specify a destination IP address for each dial peer. | Router (config-dial-peer)# | session target {ipv4:destination-address} |
Voice port configuration should be automatic in the United States, however, if you are overseas, you may need to do the following voice port configuration, beginning in global configuration mode.
| Step | Task | Router Prompt | Command | ||
|---|---|---|---|---|---|
| Enter configuration mode for the dial peer. | Router (config)# | configure dial-peer | ||
| Identify the voice port you want to configure and enter the voice port configuration mode. | Router (config-dial-peer)# | voice-port port | ||
| Select the appropriate voice call progress tone for this interface. The default country for this command is us. | Router (config-dial-peer)# | cptone country | ||
| Select the ring frequency (in Hz) specific to the equipment attached to this voice port and appropriate to the country you are in. | Router (config-dial-peer)# | ring frequency (25 \ 50) | ||
| Attach descriptive text about this voice port connection. | Router (config-dial-peer)# | description string | ||
| If voice activity detection (VAD) is activated, specify that background noise is generated. | Router (config-dial-peer)# | comfort-noise | ||
| Specify impedance, which is related to the electrical characteristics of the device that is plugged into a POTS port. Impedance is measured in ohms. | Router (config-dial-peer)# | impedance |
For complete information on the dial peer commands, refer to the Cisco IOS Release 12.0 documentation set. For more general information on dial peer concepts, refer to "Concepts."
This section describes how to expand an extension number into a particular destination pattern. Use the following global configuration command to expand the extension number:
Router(config)# num-exp extension-number extension-string
To verify that you have mapped the telephone numbers correctly, enter the show num-exp command.
After you have configured dial peers and assigned destination patterns to them, enter the show dialplan number command to see how a telephone number maps to a dial peer.
For complete information on the number expansion commands, refer to the Cisco IOS Release 12.0 documentation set.
This configuration shows voice traffic configured. You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
! class-map voice match access-group 101 ! policy-map mypolicy class voice priority 128 class class-default fair-queue 16 ! ip subnet-zero ! gateway ! interface Ethernet0 ip address 20.20.20.20 255.255.255.0 no ip directed-broadcast (default) ip route-cache policy ip policy route-map data ! interface ATM0 ip address 10.10.10.20 255.255.255.0 no ip directed-broadcast (default) no atm ilmi-keepalive (default) pvc 1/40 service-policy output mypolicy protocol ip 10.10.10.36 broadcast vbr-nrt 640 600 4 ! 640 is the maximum upstream rate of ADSL encapsulation aal5snap ! bundle-enable h323-gateway voip interface h323-gateway voip id gk-twister ipaddr 172.17.1.1 1719 h323-gateway voip h323-id gw-820 h323-gateway voip tech-prefix 1# ! router eigrp 100 network 10.0.0.0 network 20.0.0.0 ! ip classless (default) no ip http server ! access-list 101 permit ip any any precedence critical route-map data permit 10 set ip precedence routine ! ! line con 0 exec-timeout 0 0 transport input none stopbits 1 line vty 0 4 login ! ! voice-port 1 local-alerting timeouts call-disconnect 0 ! voice-port 2 local-alerting timeouts call-disconnect 0 ! voice-port 3 local-alerting timeouts call-disconnect 0 ! voice-port 4 local-alerting timeouts call-disconnect 0 ! dial-peer voice 10 voip destination-pattern ........ ip precedence 5 session target ras ! dial-peer voice 1 pots destination-pattern 5258111 port 1 ! dial-peer voice 2 pots destination-pattern 5258222 port 2 ! dial-peer voice 3 pots destination-pattern 5258333 port 3 ! dial-peer voice 4 pots destination-pattern 5258444 port 4 ! end
The following examples are for the following configurations:
These configurations are intended to be examples only. Your router configuration may look different depending on your network.
The following is a configuration for the Cisco 827-4V router configured for H.323 signaling voice traffic. These commands appear automatically in the configuration file generated when you use the show running-config command.
ip subnet-zero ! bridge crb ! interface Ethernet0 no ip address no ip directed-broadcast bridge-group 1 ! interface ATM0 no ip address no ip directed-broadcast no atm ilmi-keepalive bundle-enable ! interface ATM0.1 point-to-point ip address 1.0.0.1 255.255.255.0 no ip directed-broadcast pvc voice 1/40 protocol ip 1.0.0.2 broadcast encapsulation aal5snap ! ! interface ATM0.2 point-to-point no ip address no ip directed-broadcast pvc data 1/41 encapsulation aal5snap ! bridge-group 1 ! ip classless ! bridge 1 protocol ieee ! voice-port 1 local-alerting timeouts call-disconnect 0 ! voice-port 2 local-alerting timeouts call-disconnect 0 ! voice-port 3 local-alerting timeouts call-disconnect 0 ! voice-port 4 local-alerting timeouts call-disconnect 0 ! dial-peer voice 101 pots destination-pattern 14085271111 port 1 ! dial-peer voice 1100 voip destination-pattern 12123451111 codec g711ulaw session target ipv4:1.0.0.2 ! dial-peer voice 102 pots destination-pattern 14085272222 port 2 ! dial-peer voice 1200 voip destination-pattern 12123452222 codec g711ulaw session target ipv4:1.0.0.2 ! dial-peer voice 103 pots destination-pattern 14085273333 port 3 ! dial-peer voice 1300 voip destination-pattern 12123453333 codec g711ulaw session target ipv4:1.0.0.2 ! dial-peer voice 104 pots destination-pattern 14085274444 port 4 ! dial-peer voice 1400 voip destination-pattern 12123454444 codec g711ulaw session target ipv4:1.0.0.2 !
The following is a configuration for the Cisco 827 router. These commands appear automatically in the configuration file generated when you use the show running-config command.
Current configuration: ! version 12.0 no service pad (default) service timestamps debug uptime (default) service timestamps log uptime (default) no service password-encryption (default) hostname Cisco827 enable secret 5 $1$RnI.$K4mh5q4MFetaqKzBbQ7gv0 ip subnet-zero no ip domain-lookup ip dhcp-server 20.1.1.2 ipx routing 0010.7b7e.5499 !In the preceding command, the router MAC address is automatically used !as the router IPX address. ! interface Ethernet0 ip address 10.1.1.1 255.255.255.0 no ip directed-broadcast (default) ipx network 100 novell-ether ! interface ATM0 ip address 14.0.0.17 255.0.0.0 no ip directed-broadcast (default) no atm ilmi-keepalive (default) pvc 8/35 protocol ip 14.0.0.1 no broadcast encapsulation aal5snap ! router rip version 2 network 10.0.0.0 network 30.0.0.0 no auto-summary ! no ip http server (default) ip classless (default) ! line con 0 exec-timeout 10 0 password 4youreyesonly login transport input none (default) stopbits 1 (default) line vty 0 4 password secret login ! end
This section shows a configuration that you can use to configure a Cisco 3600 router as a corporate or endpoint router in your data network.You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
Current configuration: ! version 12.0 no service pad (default) service timestamps debug uptime (default) service timestamps log uptime (default) no service password-encryption (default) ! hostname c3600 enable secret 5 $1$8TI8$WjLcYWgZ7EZhqH49Y2hJV! ip subnet-zero no domain-lookup ipx routing 0010.7b7e.5498 !In the preceding command, the router MAC address is automatically used !as the router IPX address. ! interface Ethernet0 ip address 20.0.0.1 255.0.0.0 no ip directed-broadcast (default) ipx network 200 ! router rip version 2 network 20.0.0.0 network 30.0.0.0 no auto-summary ! no ip http server (default) ip classless (default) ! protocol ip 2.0.0.1 broadcast ! line con 0 exec-timeout 0 0 transport input none (default) stopbits 1 (default) line vty 0 4 password secret login ! end
This section shows a configuration that you can use to configure a Cisco 3600 router as a corporate or endpoint router in your data and voice network.You do not need to enter the commands marked "default." These commands appear automatically in the configuration file generated when you use the show running-config command.
Current configuration: ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname c3640 ! ip subnet-zero ! cns event-service server ! ! ! voice-port 1/0/0 no echo-cancel enable ! voice-port 1/1/0 ! voice-port 1/1/1 ! dial-peer voice 101 pots destination-pattern 5552222 port 1/0/0 ! dial-peer voice 102 pots destination-pattern 5554444 port 1/0/1 ! dial-peer voice 103 pots destination-pattern 5556666 port 1/1/0 ! dial-peer voice 104 pots destination-pattern 5558888 port 1/1/1 dial-peer voice 1100 voip destination-pattern 5551111 codec g711alaw ip precedence 5 no vad session target ipv4:2.0.0.3 ! dial-peer voice 1101 voip destination-pattern 5553333 codec g711alaw ip precedence 5 no vad session target ipv4:2.0.0.3 ! dial-peer voice 1102 voip destination-pattern 5555555 codec g711alaw ip precedence 5 session target ipv4:2.0.0.3 ! dial-peer voice 1103 voip destination-pattern 5557777 codec g711alaw ip precedence 5 session target ipv4:2.0.0.3 ! process-max-time 200 ! interface Ethernet0/1 no ip address no ip directed-broadcast (default) shutdown ! router rip version 2 network 3.0.0.0 ! ip classless (default) ip route 0.0.0.0 0.0.0.0 Ethernet 0/0 ip route 1.0.0.0 255.0.0.0 3.0.0.0 ip route 2.0.0.0 255.0.0.0 3.0.0.1 ip route 5.0.0.0 255.0.0.0 3.0.0.1 ip route 40.0.0.0 255.255.255.0 172.28.9.1 ip route 172.28.5.0 255.255.255.0 172.28.9.1 ip route 172.28.9.0 255.255.255.0 172.28.9.1 no http server ! line con 0 transport input none (default) line aux 0 line vty 0 4 login ! end
Posted: Tue Apr 11 11:52:32 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.