Table Of Contents
Configuring the 3G Wireless High-Speed WAN Interface Card for Cisco 1841, and 2800 and 3800 Series Routers (HWIC-3G-CDMA-x)
Contents
Prerequisites for Configuring the 3G Wireless HWIC
Restrictions for Configuring the 3G Wireless HWIC
Technology Overview
CDMA Network Overview
Supported Cisco Antennas and Cables
Configuring the 3G Wireless HWIC
Modem Activation and Provisioning
Verifying Signal Strength and Service Availability
Activating the Modem
Data Call Set up
Configuring the Cellular Interface
Configuring DDR
Configuring DDR Backup
Configuration Examples for the 3G Wireless HWIC
Basic Cellular Interface Configuration: Example
Tunnel over Cellular Interface Configuration: Example
3G Wireless Modem as Backup with NAT and IPSec: Example
Modem Firmware Upgrade
Command Reference
cellular cdma activate iota
cellular cdma activate manual
cellular cdma activate otasp
debug cellular driver
debug cellular firmware
debug cellular messages all
debug cellular messages async
debug cellular messages data
debug cellular messages dm
debug cellular messages management
debug cellular messages virt-con
show cellular all
show cellular connection personality
show cellular connection
show cellular hardware
show cellular network
show cellular profile
show cellular radio
show cellular security
show controllers cellular
show interfaces cellular
show run interface cellular
Troubleshooting Tips
Verifying Configuration
Checking Signal Strength
Call Setup Using CHAT Script
Modem Troubleshooting Using the Diagnostic Port
Configuring the 3G Wireless High-Speed WAN Interface Card for Cisco 1841, and 2800 and 3800 Series Routers (HWIC-3G-CDMA-x)
First Published: March 14, 2007
Revised: July 16, 2007
The Third Generation (3G) Wireless High-Speed WAN Interface Card (HWIC) is a multiband, multiservice WAN card for use over Code Division Multiple Access/Evolution-Data Optimized (CDMA/EVDO) networks. Its primary application is WAN connectivity as a backup data link for critical data applications. However, the 3G wireless HWIC can also function as the primary WAN connection. It is supported on the following Cisco integrated services routers (Cisco ISRs):
•
Cisco 1841
•Cisco 2800 series
•Cisco 3800 series
The 3G wireless HWIC provides the following functionality:
•Broadband WAN connectivity using high speed cellular data technology
•Support for the following technologies:
–Evolution-Data Optimized (EVDO) Revision (Rev) A
–EVDO Release 0
–Single channel Radio Transmission Technology (1xRTT)
•Automatic best-network selection
•Supports over-the-air service provisioning (OTASP) and Internet over-the-air (IOTA) data profile provisioning
•Multiple product SKUs for multiple CDMA carriers
•Multiple external antenna options
•Static and dynamic IP addressing
•Modem-based support for mobile IP
•Cellular interface based on the async interface in Cisco IOS
•Network Address Translation (NAT) support
•Security features such as Firewall, intrusion-detection systems (IDS), intrusion-prevention systems (IPS), and IPSec VPN on the router
•WAN switchover using Cisco IOS backup interface feature
Table 1 shows the SKU and the frequencies supported by the 3G wireless WAN HWICs.
Table 1 SKU Description and Supported Frequencies
SKU Number
|
Description
|
Region
|
Frequency Bands
|
HWIC-3G-CDMA-x
|
EVDO Rev A/Rel 0/1xRTT, where x is an initial for a specific carrier
|
US
|
800/1900MHz
|
Figure 1 shows the front panel of the HWIC-3G-CDMA-x.
Figure 1 Front Panel of HWIC-3G-CDMA-x
1
|
Mounting Screws
|
4
|
LEDs
|
2
|
Diagnostic Port
|
5
|
Diversity Antenna Connector
|
3
|
Main Antenna Connector
|
|
|
Note The diagnostic port is not required for normal operation. It is used only for advanced radio diagnostics. Please refer to "Modem Troubleshooting Using the Diagnostic Port" section for details on enabling this port and the diagnostic tools that are supported.
Table 2 explains each of the LEDs with their functionality and the different states. The LEDs provide a visual indication of your available services. Please refer to Chapter 13 in the Cisco Interface Cards Hardware Installation Guide for details on hardware installation.
Table 2 3G Wireless HWIC (CDMA) LED Descriptions
LED
|
Description
|
RSSI
|
Off: Low RSSI (under -100 dBm).
|
Slow Green Blink: Low or medium RSSI (-99 to -90 dBm).
|
Fast Green Blink: Medium RSSI (-89 to -70 dBm).
|
Solid Green: High RSSI (-69 dBm or higher).
|
Solid Yellow: No service or no RSSI detected.
|
WWAN
|
Off: HWIC in reset mode or not powered.
|
Slow blink: Searching for service.
|
Solid Green: Active service; no traffic detected.
|
Fast Blink: Active service, and traffic detected proportional to blink rate.
|
1xRTT
|
1xRTT is the active service.
|
EVDO
|
1xEVDO is the active service.
|
Note Both 1xRTT and EVDO Off: No service is active.
Note If the RSSI LED is solid yellow, it means that no service and no RSSI are detected.
Note Active service means the currently available service. Your 3G WAN wireless HWIC automatically selects the best available connection.
|
The 3G wireless HWIC provides the following software functionality:
•Modem activation—You can activate the modem either by using Cisco IOS commands either manually or by using over-the-air service provisioning (OTASP).
•Modem management—You can access modem software and hardware information, radio and network status, and data profile information using Cisco IOS commands.
•Dial-on-demand routing (DDR)—This allows you to set up a data call when there is data traffic to be sent over the wireless network.
•Fallback connection (DDR backup)—The 3G wireless HWIC allows you to configure the cellular modem to initiate a dialup connection when connection to a primary service is lost.
•Teardown after fallback (part of fallback DDR)—After a primary connection has failed and the cellular connection is in fallback mode, the 3G wireless HWIC tears down the connection when the primary connection is available.
•Automatic teardown—After a configurable timeout value, the 3G wireless HWIC automatically tears down a connection if there has been no activity.
•Portable application—You can move the router into different coverage areas (different base stations within the same service provider network) and the router establishes a connection with the nearest cell infrastructure automatically.
•Autodetect—The 3G wireless HWIC automatically detects and uses the best available service.
•Firmware upgrade—You can upgrade the firmware on the modem by using Cisco IOS commands.
Feature History
Release
|
Modification
|
12.4(11)XV
|
This feature was introduced.
|
12.4(15)T
|
This feature was integrated into Cisco IOS Release 12.4(15)T.
|
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Contents
•Prerequisites for Configuring the 3G Wireless HWIC
•Restrictions for Configuring the 3G Wireless HWIC
•Technology Overview
•Configuring the 3G Wireless HWIC
•Configuration Examples for the 3G Wireless HWIC
•Modem Firmware Upgrade
•Command Reference
•Troubleshooting Tips, page 71
Prerequisites for Configuring the 3G Wireless HWIC
The following are prerequisites to configuring the 3G wireless HWICs:
•You must have service availability from a wireless service provider, and you must have network coverage where your router will be physically located. For a complete list of supported carriers, see the data sheet at the following URL: http://www.cisco.com/go/3g
•You must subscribe to a service plan with a wireless service provider. For manual activation, you will need the following specific information from the provider:
–Master Subsidy Lock (MSL) number
–Mobile Directory number (MDN)
–MSID
–Electronic Serial Number (ESN)
Note The ESN number is on the modem itself, as shown in Figure 2. Make sure that your service is registered with the ESN number. You can also obtain the ESN by using the show cellular hardware command.
•You must install the required antennas before you configure the 3G wireless HWIC. See the following URLs for instructions on how to install the antennas:
–3G-ANTM1919D—See the Cisco Multiband Swivel Mount Dipole Antenna (3G-ANTM1919D)
–3G-ANTM1916-CM—See the Cisco Multiband Omnidirectional Ceiling Mount Antenna (3G-ANTM1916-CM)
–3G-AE015-R (Antenna Extension)—See the Cisco Single-Port Antenna Stand for Multiband TNC Male-Terminated Portable Antenna (3G-AE015-R)
•You must make sure to check your LEDs for signal reception as described in Table 2.
•You should be familiar with Cisco IOS.
Figure 2 Location of the ESN Number
1
|
The ESN is located on the modem that is attached to the back of the 3G wireless HWIC. The ESN is just below the barcode.
|
Restrictions for Configuring the 3G Wireless HWIC
The following restrictions apply to the Cisco 3G Wireless HWICs:
•Data connection can be originated only by the 3G wireless HWIC. Remote dial-in is not supported.
•Throughput—Because of the shared nature of wireless communications, the amount of throughput that is experienced varies, depending on the number of active users or congestion in a network.
•Cellular networks have higher latency, compared to wired networks. Latency rates depend on the technology and carrier. Latency can increase because of network congestion.
•VoIP is not supported.
•Any restrictions that are a part of the terms of service from your carrier.
Technology Overview
This section contains the following topics:
•CDMA Network Overview
•Supported Cisco Antennas and Cables
CDMA Network Overview
CDMA is a standard for mobile communication. A typical CDMA network includes terminal equipment, mobile termination, base transceiver station (BTS), base station controller (BSC), packet data serving node (PDSN), and other data network entities. The PDSN is the interface between a BSC and a internet gateway.
Figure 3 shows the relationship of the components of a typical CDMA network, including a PDSN and a branch office with the 3G wireless HWIC.
As the figure shows, the branch office connects to a radio tower and a BTS. The BTS connects to a BSC, which contains a component called the packet control function (PCF). The PCF communicates with the Cisco PDSN for data communication and with the mobile switching center (MSC) for voice.
Figure 3 Overview of the CDMA Network
Supported Cisco Antennas and Cables
Table 3 lists the Cisco antennas that are supported for use on the 3G wireless HWIC
.
Table 4 lists insertion loss information for the ultra-low loss (ULL) LMR 400 extension cables available from Cisco for use with the ceiling-mounted antenna.
Table 4 Cisco Extension Cables for Use with Antennas
Cisco Product Number
|
Cable Length
|
Insertion Loss
|
Frequency (MHz)
|
3G-CAB-ULL-20
|
20 ft (6 m)
|
1.50 dB max.
|
2100
|
3G-CAB-ULL-50
|
50 ft (15 m)
|
3.50 dB max.
|
2100
|
Figure 4 shows the various antenna options with the 3G wireless HWIC.
Figure 4 Antenna Options
Configuring the 3G Wireless HWIC
To configure the 3G wireless HWIC, you must do the following procedures:
•Modem Activation and Provisioning
•Data Call Set up
Modem Activation and Provisioning
To activate and provision your modem, follow these procedures:
•Verifying Signal Strength and Service Availability
•Activating the Modem
Verifying Signal Strength and Service Availability
SUMMARY STEPS
To verify the signal strength and service availability on your modem, use the following commands beginning in the EXEC mode.
Note For modem activation, you should be attached to a 1xRTT/EVDO service.
1. show cellular network
2. show cellular radio
3. show cellular all
DETAILED STEPS
Use the following commands to verify the signal strength and service availability on your modem beginning in the EXEC mode:
| |
Command or Action
|
Purpose
|
Step 1
|
Router# show cellular <slot/wic/port> network
Example:
Router# show cellular 0/0/0 network
|
Displays information about the carrier network, cell site, and available service.
|
Step 2
|
Router# show cellular <slot/wic/port> radio
Example:
Router# show cellular 0/0/0 radio
|
Shows the radio signal strength.
Note The RSSI should be better than -90 dBm for steady and reliable connection and better than -80 dBm for optimal data throughput.
|
Step 3
|
Router# show cellular <slot/wic/port> all
Example:
Router# show cellular 0/0/0 all
|
Shows consolidated information about the modem, profiles created, radio signal strength, network security, and so forth.
|
Activating the Modem
The activation procedures may differ depending upon your carrier. Consult your carrier, and follow one of the following procedures:
•Manual Activation
•Activating Using OTASP
The following table lists activation and provisioning process suupported by different wireless carriers.
Activation Process
|
Carrier
|
Manual Activation using MDN/MSID/MSL
|
Sprint
|
OTASP Activation
|
Verizon Wireless
|
IOTA for Data Profile refresh
|
Sprint
|
Manual Activation
Note You must have valid MDN, MSL, and MSID information from your carrier before you start this procedure.
To configure a modem profile manually, use the following command beginning in EXEC mode:
cellular slot/wic_slot/port cdma activate manual mdn msid sid nid msl
For more infomation about the parameters, see the "cellular cdma activate manual" section
In addition to activation, the modem data profile provisioning is done using a process called IOTA. IOTA is initiated automatically when you use the cellular cdma activate manual command.
Here is a sample output from this command:
router#cellular 0/0/0 cdma activate manual 1234567890 1234567890 1234 12 12345
NAM 0 will be configured and will become Active
Modem will be activated with following Parameters
MDN :1234567890; MSID :1234567890; SID :1234; NID 12:
Checking Current Activation Status
Modem activation status: Not Activated
Account activation - Step 1 of 5
Account activation - Step 2 of 5
Account activation - Step 3 of 5
Account activation - Step 4 of 5
Account activation - Step 5 of 5
Secure Commit Result: Succeed
Done Configuring - Resetting the modem
The activation of the account is Complete
Waiting for modem to be ready to start IOTA
*Feb 6 23:29:08.459: IOTA Status Message Received. Event: IOTA Start, Result: SUCCESS
*Feb 6 23:29:08.459: Please wait till IOTA END message is received
*Feb 6 23:29:08.459: It can take up to 5 minutes
*Feb 6 23:29:27.951: OTA State = SPL unlock, Result = Success
*Feb 6 23:29:32.319: OTA State = Parameters commited to NVRAM, Result = Success
*Feb 6 23:29:40.999: Over the air provisioning complete; Result:Success
*Feb 6 23:29:41.679: IOTA Status Message Received. Event: IOTA End, Result: SUCCESS
Note The IOTA start and end must have "success" as the resulting output. If you receive an error message, you can run IOTA independently by using the cellular cdma activate iota command.
Tip A periodic refresh of the data profile may be needed as required by your carrier. Use the following command to refresh the data profile: cellular cdma activate iota.
Activating Using OTASP
To provision and activate your modem using OTASP, use the following command beginning in EXEC mode:
cellular slot/wic_slot/port cdma activate otasp phone_number
Note You need to obtain the phone number for use with this command from your carrier. The standard OTASP calling number is *22899.
Data Call Set up
To set up a data call, use the following procedures:
•Configuring the Cellular Interface
•Configuring DDR
•Configuring DDR Backup
Figure 5 shows a data call setup using the 3G wireless HWIC.
Figure 5 Data Call Setup with the HWIC-3G-CDMA
Configuring the Cellular Interface
To configure the cellular interface, enter the following commands in the cellular interface mode.
SUMMARY STEPS
1. configure terminal
2. interface cellular <slot/wic/port>
3. encapsulation ppp
4. ppp chap password 0 <password>
5. asynchronous mode interactive
6. ip address negotiated
Note The modem supports both mobile IP (MIP) and simple IP (SIP). In both modes, the modem authenticates with the network. However, when the modem is configured in MIP-preferred mode (ask your carrier which mode is supported), if MIP authentication fails, the modem tries to set up a SIP call. The modem uses SIP authentication parameters derived during modem provisioning and passes the CHAP authentication challenge to the cellular interface. The purpose of the authentication challenge is to keep the cellular interface informed of Link Control Protocol (LCP) negotiations between the modem and the network. The authentication challenge from the modem does not have a username, so under the cellular interface, you should configure a default CHAP password, i.e., configure only the ppp chap password and not the ppp chap hostname. If your carrier supports only MIP, you do not need to configure either of the two parameters.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
Router# configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode from the terminal.
|
Step 2
|
Router(config)# interface cellular
<slot/wic/port>
Example:
Router (config)# interface cellular 0/0/0
|
Specifies the cellular interface.
|
Step 3
|
Router(config-if)# encapsulation ppp
Example:
Router (config-if)# encapsulation ppp
|
Specifies PPP encapsulation for an interface configured for dedicated asynchronous mode or dial-on-demand routing (DDR).
|
Step 4
|
Router (config-if)# ppp chap password <password>
Example:
Router (config-if)# ppp chap password cisco
|
Defines an interface-specific CHAP password.
Note You can set the password to any value. This password is used only when the modem has failed MIP authentication and fails over to SIP mode. The modem ignores the CHAP authentication response from the cellular interface.
|
Step 5
|
Router(config-if)# async mode interactive
Example:
Router (config-if)# async mode interactive
|
Returns a line that has been placed into dedicated asynchronous network mode to interactive mode, thereby enabling the slip and ppp EXEC commands.
|
Step 6
|
Router(config-if)# ip address negotiated
Example:
Router (config-if)# ip address negotiated
|
Specifies that the IP address for a particular interface is obtained via PPP/IPCP address negotiation.
|
Note When static IP address is required for the cellular interface, the address may be configured as ip address negotiated. During IPCP, the network ensures that the correct static IP address is allocated to the device. If a tunnel interface is configured with ip address unnumbered <cellular interface>, it is necessary to configure the actual static IP address under the cellular interface, in place of ip address negotiated. For a sample cellular interface configuration, see "Basic Cellular Interface Configuration: Example" section.
Configuring DDR
To configure DDR for the cellular interface, follow these steps:
SUMMARY STEPS
1. configure terminal
2. interface cellular <slot/wic/port>
3. dialer in-band
4. dialer idle-timeout <seconds>
5. dialer string <string>
6. dialer group <number>
7. exit
8. dialer-list <dialer-group> protocol <protocol-name> {permit | deny | list <access-list-number> | access-group}>
9. ip access-list<access list number>permit <ip source address>
10. line <slot/wic/port>
11. script dialer <regexp>
12. exit
13. chat-script <script name> "" "ATDT#777" TIMEOUT <timeout value> CONNECT
14. interface cellular <slot/wic/port>
15. dialer string <string>
| |
Command or Action
|
Purpose
|
Step 1
|
Router# configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode from the terminal.
|
Step 2
|
Router(config)# interface cellular <slot/wic/port>
Example:
Router (config)# interface cellular 0/0/0
|
Specifies the cellular interface.
|
Step 3
|
Router(config-if)# dialer in-band
Example:
Router (config-if)# dialer in-band
|
Enables DDR and configures the specified serial interface to use in-band dialing.
|
Step 4
|
Router(config-if)# dialer idle-timeout <seconds>
Example:
Router (config-if)# dialer idle-timeout 30
|
Specifies the duration of idle time, in seconds, after which a line will be disconnected.
|
Step 5
|
Router(config-if)# dialer string <string>
Example:
Router (config-if)# dialer string cdma
|
Specifies the number or string to dial. Use the name of the CHAT script here.
|
Step 6
|
Router(config-if)# dialer-group <number>
Example:
Router (config-if)# dialer-group 1
|
Specifies the number of the dialer access group to which the specific interface belongs.
|
Step 7
|
Router(config-if)# exit
Example:
Router (config-if)# exit
|
Enters the global configuration mode.
|
Step 8
|
Router(config)# dialer-list <dialer-group> protocol <protocol-name> {permit | deny | list <access-list-number> | access-group}>
Example:
Router (config)# dialer-list 1 protocol ip list 1
|
Creates a dialer list for traffic of interest and permits access to an entire protocol.
|
Step 9
|
Router(config)# ip access-list<access list number>permit <ip source address>
Example:
Router (config)# ip access list 1 permit any
|
Defines traffic of interest.
|
Step 10
|
Router(config)# line <slot/wic/port>
Example:
Router (config-line)# line 0/0/0
|
Specifies the line configuration mode.
|
Step 11
|
Router(config-line)script dialer <regexp>
Example:
Router (config-line)# script-dialer cdma
|
Specifies a default modem chat script.
|
Step 12
|
Router(config-line)exit
Example:
Router (config-line)# exit
|
Exits line configuration mode.
|
Step 13
|
Router(config)# chat-script <script name> "" "ATDT#777" TIMEOUT <timeout value> CONNECT
Example:
Router (config)# chat-script cdma "" "ATDT#777"
TIMEOUT 60 "CONNECT"
|
Defines the ATDT commands when the dialer is initiated.
|
Step 14
|
Router(config)# interface cellular <slot/wic/port>
Example:
Router (config)# interface cellular 0/1/0
|
Specifies the cellular interface.
|
Step 15
|
Router(config-if)# dialer string <string>
Example:
Router (config)# dialer string cdma
|
Specifies the dialer script (defined using the chat script command).
|
Configuring DDR Backup
To monitor the primary connection and initiate the backup connection when needed, the router can use one of the following methods:
•Backup Interface—The backup interface that stays in standby mode until the primary interface line protocol is detected as down and then is brought up.
•Floating Static Route—The route through the backup interface has an administrative distance that is greater than the administrative distance of the primary connection route and therefore would not be in the routing table until the primary interface goes down.
•Dialer Watch—Dialer watch is a backup feature that integrates dial backup with routing capabilities.
Configuring Interfaces to Use a Backup Interface
To configure one or more interfaces to use a backup interface, use the following commands, beginning in global configuration mode.
SUMMARY STEPS
1. interface type number
2. backup interface cellular number
3. backup delay enable-delay disable-delay
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
Router(config)# interface type number
Example:
Router(config)# interface ATM0/0/0
|
Specifies the interface to be backed up and begins interface configuration mode.
|
Step 2
|
Router(config-if)# backup interface cellular
<number>
Example:
Router(config-if)# backup interface cellular0/3/0
|
Specifies the cellular interface as backup.
|
Step 3
|
Router(config-if)# backup delay enable-delay disable-delay
Example:
Router(config-if)# backup delay enable delay
|
Specifies delay between the physical interface going down and the backup interface being enabled, and between the physical interface coming back up and the backup being disabled.
|
Note You cannot configure a backup interface for the cellular interface and any other asynchronous serial interface.
Configuring DDR Backup Using Dialer Watch
To initiate dialer watch, you must configure the interface to perform DDR and backup. Use traditional DDR configuration commands, such as dialer maps, for DDR capabilities. To enable dialer watch on the backup interface and create a dialer list, use the following commands in interface configuration mode.
SUMMARY STEPS
1. configure terminal
2. interface type number
3. dialer watch group group-number
4. dialer watch-list group-number ip ip-address address-mask
5. dialer-list <dialer-group> protocol <protocol name> {permit | deny | list <access list number> | access-group}
6. ip access-list <access list number> permit <ip source address>
7. interface cellular <slot/wic/port>
8. dialer-group <dialer group number>
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
Router# configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode from the terminal.
|
Step 2
|
Router(config)# interface type number
Example:
Router (config)# interface ATM0/0/0
|
Specifies the interface.
|
Step 3
|
Router(config-if)# dialer watch-group
Example:
Router(config-if)# dialer watch-group 2
|
Enables dialer watch on the backup interface.
|
Step 4
|
Router(config)# dialer watch-list group-number ip ip-address address-mask
Example:
Router(config-if)# dialer watch-list 2 ip 10.4.0.254 255.255.0.0
|
Defines a list of all IP addresses to be watched.
|
Step 5
|
Router(config)# dialer-list <dialer-group> protocol <protocol-name> {permit | deny | list <access-list-number> | access-group}>
Example:
Router(config)# dialer-list 2 protocol ip permit
|
Creates dialer list for traffic of interest and permits access to an entire protocol.
|
Step 6
|
Router(config)# ip access-list<access list number>permit <ip source address>
Example:
Router(config)# access list 2 permit 10.4.0.0
|
Defines traffic of interest.
Note Do not use the access list permit all command to avoid sending traffic to the IP network. This may result in call termination.
|
Step 7
|
Router(config)# interface cellular<slot/wic_slot/port>
Example:
Router(config)# interface cellular 0/1/0
|
Enters the interface configuration mode.
|
Step 8
|
Router(config-if)# dialer-group <dialer group number>
Example:
Router(config-if)# dialer-group 2
|
Maps a dialer list to the dialer interface.
|
Configuring DDR Backup Using Floating Static Route
To configure a floating static default route on the secondary interface beginning in the global configuration mode, perform the following tasks.
Note Make sure you have ip classless enabled on your router.
SUMMARY STEPS
1. configure terminal
2. ip route network-number network-mask {ip address | interface} [administrative distance] [name name]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
Router# configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode from the terminal.
|
Step 2
|
Router(config)# ip route network-number network-mask
{ip-address | interface} [administrative distance]
[name name]
Example:
Router (config)# ip route 0.0.0.0 Dialer 2 track 234
|
Establishes a floating static route with the configured administrative distance through the specified interface.
Note A higher administrative distance should be configured for the route through the backup interface, so that it is used only when the primary interface is down.
|
Configuration Examples for the 3G Wireless HWIC
This section provides the following configuration examples:
•Basic Cellular Interface Configuration: Example
•Tunnel over Cellular Interface Configuration: Example
•3G Wireless Modem as Backup with NAT and IPSec: Example
Basic Cellular Interface Configuration: Example
The following is an example configuration where the cellular interface is used as a primary and is configured as the default route:
chat-script cdma "" "ATDT#777" TIMEOUT 60 "CONNECT"
ppp chap password 0 cisco
ip route 0.0.0.0 0.0.0.0 Cellular0/0/0
dialer-list 1 protocol ip list 1
Tunnel over Cellular Interface Configuration: Example
The following sample configuration shows the configuration of the static IP address when a tunnel interface is configured using the ip address unnumbered <cellular interface> command:
ip unnumbered Cellular0/3/0
tunnel source Cellular0/3/0
tunnel destination 128.107.248.254
bandwidth receive 1400000
ip address 23.23.0.1 255.255.0.0
ppp chap password 0 cisco
! traffic of interest through the tunnel/cellular interface
ip route 10.10.0.0 255.255.0.0 Tunnel2
3G Wireless Modem as Backup with NAT and IPSec: Example
The following sample configuration shows the configuration of the 3G wireless modem on the router as backup with NAT and IPSec:
ip dhcp excluded-address 10.4.0.254
network 10.4.0.0 255.255.0.0
dns-server 66.209.10.201 66.102.163.231
default-router 10.4.0.254
chat-script cdma "" "atdt#777" TIMEOUT 30 "CONNECT"
crypto isakmp key abcd address 128.107.241.234
crypto ipsec transform-set abcd ah-sha-hmac esp-3des
crypto map cdma1 10 ipsec-isakmp
interface ATM0/0/0.1 point-to-point
backup interface Cellular0/3/0
pppoe-client dial-pool-number 2
bandwidth receive 1400000
ppp chap password 0 cisco
description used as default gateway address for DHCP clients
ip address 10.4.0.254 255.255.0.0
ppp authentication chap callin
ppp chap hostname cisco@dsl.com
ppp chap password 0 cisco
ip local policy route-map track-primary-if
ip route 0.0.0.0 0.0.0.0 Dialer2 track 234
ip route 0.0.0.0 0.0.0.0 Cellular0/3/0 254
ip nat inside source route-map nat2cell interface Cellular0/3/0 overload
ip nat inside source route-map nat2dsl interface Dialer2 overload
icmp-echo 209.131.36.158 source-interface Dialer2
ip sla schedule 1 life forever start-time now
<
