用 NM-8AM 或 NM-16AM 模拟调制解调器模块配置拨出
简介
本文档显示如何使用带有NM-AM模拟调制解调器网络模块的调制解调器配置拨出。在此场景中，带有NM-8AM调制解调器模块的路由器拨打中心站点路由器的主速率接口(PRI)。
本文档假设您对调制解调器配置相关的各种问题有充分的了解。如果您需要有关这些问题的详细信息，请参阅《调制解调器 — 路由器连接指南》。
先决条件
要求
本文档没有任何特定的要求。
使用的组件
此配置使用下面软件和硬件版本被开发并且被测试：
-
带NM-8AM卡的Cisco 3640路由器运行Cisco IOS®软件版本12.1(5)T。
规则
有关文档规则的详细信息，请参阅 Cisco 技术提示规则。
配置
本部分提供有关如何配置本文档所述功能的信息。
注：要查找有关本文档中使用的命令的其他信息，请使用命令查找工具(仅注册客户)。
网络图
本文档使用下图所示的网络设置。
配置
本文档使用如下所示的配置。
| 路由器 1 (Cisco 3640) |
|---|
Current configuration : 1676 bytes ! version 12.1 no service single-slot-reload-enable service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname router1 ! enable password ww ! username router2 password 0 ww !--- username for remote router (Router 2) and shared secret !--- shared secret(used for CHAP authentication) must be the same on both sides ip subnet-zero ! chat-script async "" "AT" OK "ATDT\T" TIMEOUT 30 CONNECT \c !--- chat script "async" used for the dialout connection ! ! interface Ethernet2/0 ip address 10.200.20.51 255.255.255.0 half-duplex ! interface Async104 !--- async interface corresponding to the modem !--- This was determined using the show line command. ip address 10.10.0.2 255.255.255.252 !--- IP address of this async interface encapsulation ppp dialer in-band dialer wait-for-carrier-time 180 dialer map ip 10.10.0.1 name router2 modem-script async 8214 !--- dialer map statements for the remote router !--- The name must match the one used by the remote router to identify itself. !--- use modem chat script "async" for this connection dialer-group 1 !--- apply interesting traffic definition from dialer-list 1 async mode dedicated !--- Place the line into dedicated asynchronous network mode. !--- This interface is now automatically configured for PPP connections. ppp authentication chap !--- use chap authentication ! ip classless ip route 10.10.0.0 255.255.0.0 10.10.0.1 !--- Traffic for the 10.10.0.0/16 network uses a next hop of 10.10.0.1 ip route 10.10.0.1 255.255.255.255 Async104 !--- the next hop for 10.10.0.1/32 (which is also the next hop for the !--- previous route) is interface Async104. ! dialer-list 1 protocol ip permit !--- All IP traffic is defined interesting. !--- This is applied to Async104 using dialer-group 1. ! ! line con 0 exec-timeout 0 0 password ww transport input none line 33 38 line 97 103 modem InOut transport input all line 104 !--- line interface configuration for Async 104 modem InOut !--- allow incoming and outgoing modem calls on this line transport input all transport output lat pad v120 lapb-ta telnet rlogin udptn flowcontrol hardware line aux 0 line vty 0 4 password ww login ! end |
在此3600机箱中，NM-8AM卡安装在插槽3中。请参阅Cisco 3600系列路由器文档中异步线路的编号方式，我们确定插槽3保留了线路97到128。要确定应配置哪个特定异步接口，请使用show line命令查找可用的线路。在此配置中，请注意，在该范围内仅有97-104（8行）可用。因此，要配置卡中的第一个调制解调器，请配置线路97（和接口async97），而最后一个调制解调器是line/async104。
验证
当前没有可用于此配置的验证过程。
排除模拟连接故障
要排除拨出连接故障，请完成以下步骤：
-
检查调制解调器配置。
检验调制解调器的配置。您应该检查与调制解调器对应的线路配置以及异步接口。
-
反向telnet至调制解调器并启动拨出。
将端口反向telnet至调制解调器，然后使用AT命令集拨号并连接到远程设备。这可用于检验调制解调器硬件和电话电路是否正常工作。在本例中，由于调制解调器端口在线104，因此请反向telnet至路由器上的端口2104。有关反向Telnet的详细信息，请参阅建立到调制解调器的反向Telnet会话。
router1#telnet 10.200.20.51 2104 Trying 10.200.20.51, 2104 ... Open User Access Verification Username: admin Password: !--- Authentication performed by local router for the reverse telnet at OK atdt 81690 !--- The modem dials (81690) and connects. !--- This takes approximately 30-45 seconds. CONNECT 31200/ARQ/V34/LAPM/V42BIS !--- Connect speed and protocols that were negotiated User Access Verification Username: admin Password: !--- Authentication performed by remote router for the incoming call router2> !--- Remote router's prompt
您还可以应用其他AT命令以验证调制解调器设置。有关模拟调制解调器模块可用的AT命令的详细信息，请参阅模拟调制解调器网络模块的AT命令集和寄存器摘要。
-
手动激活聊天脚本并启动拨号。
使用start-chat命令激活聊天脚本并启动拨号。start-chat命令要求您指定要激活的聊天脚本的名称、要拨打的电话号码以及要拨出的调制解调器接口。
-
检验是否有到异步接口的路由。
使用show ip route命令检查是否存在到异步接口的路由。如果没有路由，请创建静态路由。示例显示：
ip route 10.10.0.1 255.255.255.255 Async104
-
生成发往步骤4中指定的下一跳网络的ping。
从步骤4使用下一跳网络指定对远程路由器执行ping操作后，路由器会拨打远程设备。
router1#ping 10.10.0.1
有关如何排除连接故障的详细信息，请参阅排除出站呼叫故障。
常见错误
-
验证聊天脚本名称是否与拨号程序映射语句中指定的名称相同。另外，请确认要拨打的电话号码已正确指定。
-
检查相关流量是否已正确定义。使用dialer-list命令指定相关流量。
-
确保相关流量定义已应用到异步接口。这是使用dialer-group命令完成的，其中组编号必须与使用dialer-list命令指定的相关流量定义匹配。
-
验证PAP/CHAP身份验证的用户名和密码是否正确。
-
检查以确保拨号器映射语句具有正确的名称、IP地址和要拨号的电话号码。
debug命令
在发出 debug 命令之前，请参阅有关 debug 命令的重要信息。
-
debug dialer - 用于显示关于拨号接口上接收的数据包的调试信息。在接口上启用按需拨号路由(DDR)时，还会显示有关任何呼叫原因（称为拨号原因）的信息。有关详细信息，请参阅Debug Commands文档中的debug dialer信息。
-
debug modem — 显示路由器上的调制解调器线路活动、调制解调器控制和进程激活消息。
-
debug ppp negotiation — 在协商PPP组件(包括链路控制协议(LCP)、身份验证和网络控制协议(NCP))时显示有关PPP流量和交换的信息。成功的PPP协商将首先打开LCP状态，然后进行身份验证，最后协商NCP。
-
debug ppp authentication — 显示PPP身份验证协议消息，包括质询身份验证协议(CHAP)数据包交换和密码身份验证协议(PAP)交换。
调试输出示例
router1#show debug General OS: Modem control/process activation debugging is on Dial on demand: Dial on demand events debugging is on Generic IP: ICMP packet debugging is on PPP: PPP protocol negotiation debugging is on Chat Scripts: Chat scripts activity debugging is on router1# router1#ping 10.10.0.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.10.0.1, timeout is 2 seconds: *Mar 1 00:22:58.663: As104 DDR: Dialing cause ip (s=10.10.0.2, d=10.10.0.1) !--- Dialing reason is the ping for 10.10.10.1 !--- The dialout is using Async104. *Mar 1 00:22:58.663: As104 DDR: Attempting to dial 8214 !--- Phone number to be dialed *Mar 1 00:22:58.663: CHAT104: Attempting async line dialer script *Mar 1 00:22:58.663: CHAT104: Dialing using Modem script: async & System script: none !--- Use chat script named "async" *Mar 1 00:22:58.663: CHAT104: process started *Mar 1 00:22:58.667: CHAT104: Asserting DTR *Mar 1 00:22:58.667: CHAT104: Chat script async started !--- Chat-script "async" is started. *Mar 1 00:22:58.667: CHAT104: Sending string: AT *Mar 1 00:22:58.667: CHAT104: Expecting string: OK *Mar 1 00:22:58.739: CHAT104: Completed match for expect: OK *Mar 1 00:22:58.739: CHAT104: Sending string: ATDT\T<8214> *Mar 1 00:22:58.739: CHAT104: Expecting string: CONNECT *Mar 1 00:22:58.751: Modem 3/7 Mcom: in modem state 'Dialing/Answering' *Mar 1 00:23:10.775: Modem 3/7 Mcom: in modem state 'Waiting for Carrier' *Mar 1 00:23:21.903: Modem 3/7 Mcom: in modem state 'Connected' *Mar 1 00:23:22.323: Modem 3/7 Mcom: CONNECT at 26400/24000(Tx/Rx), V34, LAPM, V42bis, Originate !--- Connect speeds, protocols and so forth, and so on negotiated for the connection !--- Note that the modem used is 3/7 which is equivalent to line 104. !--- Refer to How Async Lines are Numbered in Cisco 3600 Series Routers. *Mar 1 00:23:22.375: CHAT104: Completed match for expect: CONNECT *Mar 1 00:23:22.375: CHAT104: Sending string: \c *Mar 1 00:23:22.375: CHAT104: Chat script async finished, status = Success !--- Chat script is successful. Notice the Expect/Send attributes and the time elapsed. *Mar 1 00:23:22.375: Modem 3/7 Mcom: switching to PPP mode *Mar 1 00:23:22.379: TTY104: no timer type 1 to destroy *Mar 1 00:23:22.379: TTY104: no timer type 0 to destroy *Mar 1 00:23:22.379: As104 IPCP: Install route to 10.10.0.1 *Mar 1 00:23:24.379: %LINK-3-UPDOWN: Interface Async104, changed state to up *Mar 1 00:23:24.379: As104 DDR: Dialer statechange to up *Mar 1 00:23:24.379: As104 DDR: Dialer call has been placed *Mar 1 00:23:24.379: As104 PPP: Treating connection as a callout !--- PPP negotiation begins. *Mar 1 00:23:24.379: As104 PPP: Phase is ESTABLISHING, Active Open [0 sess, 0 load] *Mar 1 00:23:24.379: Modem 3/7 Mcom: PPP escape map: Tx map = FFFFFFFF, Rx map = 0 *Mar 1 00:23:24.379: As104 LCP: O CONFREQ [Closed] id 17 len 25 *Mar 1 00:23:24.379: As104 LCP: ACCM 0x000A0000 (0x0206000A0000) *Mar 1 00:23:24.379: As104 LCP: AuthProto CHAP (0x0305C22305) *Mar 1 00:23:24.379: As104 LCP: MagicNumber 0x1090720F (0x05061090720F) *Mar 1 00:23:24.379: As104 LCP: PFC (0x0702) *Mar 1 00:23:24.379: As104 LCP: ACFC (0x0802) *Mar 1 00:23:24.543: As104 LCP: I CONFREQ [REQsent] id 1 len 25 *Mar 1 00:23:24.543: As104 LCP: ACCM 0x000A0000 (0x0206000A0000) *Mar 1 00:23:24.543: As104 LCP: AuthProto CHAP (0x0305C22305) *Mar 1 00:23:24.543: As104 LCP: MagicNumber 0x41B616FF (0x050641B616FF) *Mar 1 00:23:24.543: As104 LCP: PFC (0x0702) *Mar 1 00:23:24.543: As104 LCP: ACFC (0x0802) *Mar 1 00:23:24.543: As104 LCP: O CONFACK [REQsent] id 1 len 25 *Mar 1 00:23:24.543: As104 LCP: ACCM 0x000A0000 (0x0206000A0000) *Mar 1 00:23:24.543: As104 LCP: AuthProto CHAP (0x0305C22305) *Mar 1 00:23:24.543: As104 LCP: MagicNumber 0x41B616FF (0x050641B616FF) *Mar 1 00:23:24.543: As104 LCP: PFC (0x0702) *Mar 1 00:23:24.543: As104 LCP: ACFC (0x0802) *Mar 1 00:23:24.555: As104 LCP: I CONFACK [ACKsent] id 17 len 25 *Mar 1 00:23:24.555: As104 LCP: ACCM 0x000A0000 (0x0206000A0000) *Mar 1 00:23:24.555: As104 LCP: AuthProto CHAP (0x0305C22305) *Mar 1 00:23:24.559: As104 LCP: MagicNumber 0x1090720F (0x05061090720F) *Mar 1 00:23:24.559: As104 LCP: PFC (0x0702) *Mar 1 00:23:24.559: As104 LCP: ACFC (0x0802) *Mar 1 00:23:24.559: As104 LCP: State is Open !--- LCP negotiation is complete. *Mar 1 00:23:24.559: Modem 3/7 Mcom: PPP escape map: Tx map = A0000, Rx map = 0 *Mar 1 00:23:24.559: As104 PPP: Phase is AUTHENTICATING, by both [0 sess, 0 load] !--- Two-way PPP authentication begins. *Mar 1 00:23:24.559: As104 CHAP: O CHALLENGE id 4 len 28 from "router1" *Mar 1 00:23:24.691: As104 CHAP: I CHALLENGE id 1 len 28 from "router2" *Mar 1 00:23:24.691: As104 CHAP: O RESPONSE id 1 len 28 from "router1" *Mar 1 00:23:24.707: As104 CHAP: I RESPONSE id 4 len 28 from "router2" *Mar 1 00:23:24.707: As104 CHAP: O SUCCESS id 4 len 4 *Mar 1 00:23:24.815: As104 CHAP: I SUCCESS id 1 len 4 !--- Incoming and outgoing CHAP authentication is successful. *Mar 1 00:23:24.815: As104 PPP: Phase is UP [0 sess, 0 load] *Mar 1 00:23:24.819: As104 IPCP: O CONFREQ [Closed] id 6 len 10 *Mar 1 00:23:24.819: As104 IPCP: Address 10.10.0.2 (0x03060A0A0002) *Mar 1 00:23:24.835: As104 IPCP: I CONFREQ [REQsent] id 1 len 10 *Mar 1 00:23:24.835: As104 IPCP: Address 10.10.0.1 (0x03060A0A0001) *Mar 1 00:23:24.839: As104 IPCP: O CONFACK [REQsent] id 1 len 10 *Mar 1 00:23:24.839: As104 IPCP: Address 10.10.0.1 (0x03060A0A0001) *Mar 1 00:23:24.931: As104 IPCP: I CONFACK [ACKsent] id 6 len 10 *Mar 1 00:23:24.931: As104 IPCP: Address 10.10.0.2 (0x03060A0A0002) *Mar 1 00:23:24.931: As104 IPCP: State is Open !--- IP Control Protocol (IPCP) negotiation is complete. *Mar 1 00:23:24.931: As104 DDR: dialer protocol up *Mar 1 00:23:25.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async104, changed state to up !--- Interface is up.
反馈