Cisco 1801 dial backup (near the suicide) 2

[Docsharing]

Hi all,
I'm trying to configure a Cisco 1800 router dial backup to US Robotics 5630D analog modem by AUX port.
I have read documents about it but not runs, but not runs. I configure interfaces like this:
INterface F0-> 192.168.1.212/24 GW:192.168.1.252
Interface VLAN1 (switch)->10.10.10.1/24

I want that when F0 interface goes down, the router inits a dial conection to an ISP using the analog modem attached to AUX port for backup.

Now, with this config, when F0 goes down dialer0 goes up, but nothing happens in modem, no debugging comands appears, and no modem sound...

Could anyone help me before i suicide?

Thanks a lot
This is the actual configuration of the router:


Current configuration : 4779 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname yourname
!
boot-start-marker
boot-end-marker
!
logging buffered 51200 warnings
enable secret 5 $1$KHA4$1v4KF2emdabShMs6X3Ocw.
!
no aaa new-model
!
resource policy
!
mmi polling-interval 60
no mmi auto-configure
no mmi pvc

mmi snmp-timeout 180
ip subnet-zero
!
!
ip cef
no ip dhcp use vrf connected
ip dhcp excluded-address 10.10.10.1
!
ip dhcp pool sdm-pool1
import all
network 10.10.10.0 255.255.255.0
dns-server 195.235.113.3
default-router 10.10.10.1
!
!
ip domain name yourdomain.com
ip name-server 195.235.113.3
!
chat-script DIALOUT ABORT ERROR BUSY "" "ATZ" OK "ATDT T" TIMEOUT 120 CONNECT c
modemcap entry MY_USR_MODEM:MSC=&F0X2L1M0S0=1
!
username USUARIO privilege 15 secret 5 $1$uN3j$V1.G6ZDefXqhoT4E8k72o.
!
!
!
!
!
!
interface FastEthernet0
description $ES_WAN$
backup interface Dialer0
ip address 192.168.1.212 255.255.255.0
ip nat outside
ip virtual-reassembly
duplex auto
speed auto
!
interface BRI0
no ip address
encapsulation hdlc

interface Vlan1
description $ETH-SW-LAUNCH$$INTF-INFO-FE 1$$ES_LAN$
ip address 10.10.10.1 255.255.255.0
ip nat inside
ip virtual-reassembly
ip tcp adjust-mss 1452
!

!
interface Async5
no ip address
encapsulation ppp
dialer in-band
dialer pool-member 1
async mode interactive
!
interface Dialer0
ip address negotiated
encapsulation ppp
dialer pool 1
dialer remote-name REMOTO
dialer idle-timeout 300
dialer string 0607612812
dialer hold-queue 10

dialer-group 1
no peer default ip address
no cdp enable
ppp authentication pap chap callin
ppp chap hostname marcos
ppp chap password 0 marcos
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.168.1.252
ip route 0.0.0.0 0.0.0.0 Dialer0
!
!
ip http server
ip http authentication local
ip http secure-server
ip http timeout-policy idle 5 life 86400 requests 10000
ip nat inside source list 1 interface FastEthernet0 overload
ip nat inside source list 101 interface Dialer0 overload
!
access-list 1 remark INSIDE_IF=Vlan1
access-list 1 remark SDM_ACL Category=2
access-list 1 permit 10.10.10.0 0.0.0.255
access-list 101 permit ip any any

dialer-list 1 protocol ip list 101
no cdp run
!
!
!
!
control-plane
!
banner login ^CAuthorized access only!
Disconnect IMMEDIATELY if you are not an authorized user!^C
!
line con 0
login local
line aux 0
exec-timeout 0 0
password cisco
script dialer DIALOUT
login
modem InOut
modem autoconfigure type MY_USR_MODEM
no exec
transport input all
autoselect ppp

exec-timeout 0 0
password cisco
script dialer DIALOUT
login
modem InOut
modem autoconfigure type MY_USR_MODEM
no exec
transport input all
autoselect ppp
stopbits 1
speed 115200
flowcontrol hardware
line vty 0 4
privilege level 15
login local
transport input telnet ssh
line vty 5 15
privilege level 15
login local
transport input telnet ssh
!
end

 

[helpdeskdan]

Have you done a debug dialer? Can you reverse telnet to the modem?

 

[KiscoKid]

Some stuff for you to consider:

1. If you do 'show line', does async 5 correspond with the AUX port?

2. Your chat script doesn't look quite right to me. You have "ATDT T" and CONNECT c but I've always previously used "ATDT \T" and CONNECT \c

3. This won't affect the ability of the modem to dial out but I also notice you haven't defined a PPP username or password on your dialer interface. The username can be anything you want (so long as the remote end - USUARIO - is configured to recognise this username). Also the password should match the password used by USUARIO.

Also I notice that whilst you have a username for USUARIO (which I have assumed if your remote router), you are also defining the remote name as REMOTO under the dialer interface. These two should match otherwise you will get authentication problems.

Give that lot a go and see what happens.

 

[Docsharing]

To HELPDESKDAN: "debug dialer" the most of times not shows anything. I don´t know how i could reverse telnet to the modem
Thanks a lot

To KISKOKID:

1- Yes, sure
2- I will try using "ATDT \T" and CONNECT \c
3- I'm configuring only a test. User and password are not important to me now, because the "dialer string" that i have configured is my mobile phone only for test if router begins a sucess call. Later, if i succeed modem call me, i try next step: put the isp dial number, user, password, etc. That will be a future problem, but now i hope resolve first mistake.
Thanks a lot

 

[helpdeskdan]

I would imagine that it would be a chat script problem as KiscoKid said or perhaps a modem connection problem. It is hard to find much good information on chat scripts.

Rerverse Telnet:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/12cgcr/dial_c/dcrtelnt.htm

Use those instructions and to the first test to make sure you get an OK. If you don't get the OK, something is wrong with the modem or connection. You can also test the modem init string.

 

[Docsharing]

Hi,

I have done a right reverse telnet with the modem. When i send AT, modem request OK.

But the problem is here yet: when F0 goes down, dialer0 wakes up, but no dialing, no modem noise, no leds blink.... nothing.

I was trying using diferent innitialization commands for USR modem, but nothing happens. Debugging comands, like "debug dialer", not shows anything.

Thank you very much

 

[helpdeskdan]

luerces -

Thank you for reminding me how much I have forgotten about this subject! It has lead to an interesting review. Thanks also for the star; it is not deserved as I haven't solved your problem.

Do a debug dialer events. If the router is not in use (sounds like it isn't) do a debug dialer packets. (lots of output) Also, if the router is not in use, you'll need to ping the destination address or you will have no interesting traffic to bring up the connection!

Last, do a show ip route after dialer 0 comes up and make sure it shows a route to the destination address.