So I just copied Li Ling's config to my routers. Still doesn't work. Yes,
I am using a rolled cable.
Check this out:
r1#show int async 65
Async65 is up, line protocol is down
Hardware is Async Serial
Internet address is 192.168.10.1/24
MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
DTR is pulsed for 5 seconds on reset
LCP ACKsent
Closed: IPCP, CDPCP
Last input 00:00:01, output 00:00:00, output hang never
Last clearing of "show interface" counters 18:04:47
Input queue: 1/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
Conversations 0/1/256 (active/max active/max total)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1354 packets input, 32496 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
2709 packets output, 65016 bytes, 0 underruns
0 output errors, 0 collisions, 126 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
No matter what I do, the async interface is always up-down. And I am always
getting these kinds of messages:
2d13h: %LINK-5-CHANGED: Interface Async65, changed state to reset
r1#
2d13h: %LINK-3-UPDOWN: Interface Async65, changed state to up
r1#
2d13h: %LINK-5-CHANGED: Interface Async65, changed state to reset
r1#
2d13h: %LINK-3-UPDOWN: Interface Async65, changed state to up
Funny, I copied the exact same config as on CCO, and from Li Ling, and it
doesn't work. I hate when that happens.
""Maness, Drew"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> You might just need to clear both lines. Clear line x Also are you using
a
> rollover cable?
>
> -----Original Message-----
> From: Doug Hammond [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, May 24, 2001 11:04 PM
> To: [EMAIL PROTECTED]
> Subject: Re: anybody ever connected 2600 AUX ports back2back? [7:5844]
>
>
> Some thoughts -
> Try putting in this command on your async interface: async default routing
> Also what type of cable are you using? I've always used the cisco black
> cable.
> And try to hard-code the rxspeed and txspeed. I never trust auto-select.
> Why are you using async65? Wouldn't it be async1?
>
> ""NRF"" wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Well, now I've just tried back2back aux between a 2610 and a 2514. It
> still
> > doesn't work, exact same errors as before.
> >
> >
> >
> >
> > ""NRF"" wrote in message
> > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > > So I'm trying to connect the AUX ports of 2 2610's back to back. I am
> > > following a known procedure on CCO where you can connect 2500's AUX
> ports
> > > back to back.
> > > http://www.cisco.com/warp/public/793/access_dial/auxback.html
> > >
> > > So I follow exactly what they do. But it doesn't work. Maybe the
> problem
> > > is that 2600's don't do back2back aux ports (the CCO example was for
> > > 2500's). But that doesn't make much sense, because why not? Anyway,
> has
> > > anybody ever gotten AUX 2600's (or any router for that matter) to
> connect
> > > back to back?
> > >
> > > For example, here is the Async config on one of the 2610's.
> > >
> > > interface Async65
> > > ip address 192.168.10.1 255.255.255.0
> > > no ip directed-broadcast
> > > encapsulation ppp
> > > async dynamic routing
> > > async mode dedicated
> > >
> > > Here is the aux line config:
> > >
> > > ine aux 0
> > > modem InOut
> > > transport input all
> > > speed 38400
> > > flowcontrol hardware
> > >
> > > So I believe that everything is good, it's exactly like the CCO
config.
> > > Yet, the async interface just keeps bouncing up and down. For
example:
> > >
> > > r1#
> > > 1d19h: %LINK-5-CHANGED: Interface Async65, changed state to reset
> > > r1#
> > > 1d19h: %LINK-3-UPDOWN: Interface Async65, changed state to up
> > > r1#
> > > 1d19h: %LINK-5-CHANGED: Interface Async65, changed state to reset
> > >
> > >
> > > Here's what happens when I debug async packet
> > > r1#debug async packet
> > > Async packet I/O debugging is on
> > > r1#
> > > 1d19h: %LINK-5-CHANGED: Interface Async65, changed state to reset
> > > r1#
> > > 1d19h: %LINK-3-UPDOWN: Interface Async65, changed state to up
> > > r1#
> > > 1d19h: APPP65: Output packet, len = 24, header = FF 3 C0 21
> > > 1d19h: APPP65: Output packet, len = 24, header = FF 3 C0 21
> > > 1d19h: APPP65: Output packet, len = 24, header = FF 3 C0 21
> > > r1#
> > > 1d19h: APPP65: Output packet, len = 24, header = FF 3 C0 21
> > > 1d19h: APPP65: Input packet, len = 24, header = FF 3 C0 21
> > > 1d19h: APPP65: Output packet, len = 24, header = FF 3 C0 21
> > > r1#
> > >
> > > Here's what happens when I debug async framing
> > >
> > > r1#debug async framing
> > > Async interface framing debugging is on
> > > r1#
> > > 1d19h: %LINK-5-CHANGED: Interface Async65, changed state to reset
> > > r1#
> > > 1d19h: Async65: Reset PPP framing on TTY65
> > > r1#
> > > 1d19h: Async65: Setup PPP framing on TTY65
> > > 1d19h: As65 PPP: Processed packet cached during autoselect
> > > r1#
> > > 1d19h: %LINK-3-UPDOWN: Interface Async65, changed state to up
> > > r1#
> > > 1d19h: As65: Enabling PPP framing in UART Microcode on TTY65
> > > r1#
> > > 1d19h: As65: Enabling PPP framing in UART Microcode on TTY65
> > > r1#
> > > 1d19h: As65: Enabling PPP framing in UART Microcode on TTY65
> > > r1#
> > > 1d19h: As65: Enabling PPP framing in UART Microcode on TTY65
> > > r1#
> > > 1d19h: As65: Enabling PPP framing in UART Microcode on TTY65
> > > r1#
> > > 1d19h: As65: Enabling PPP framing in UART Microcode on TTY65
> > > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=5965&t=5844
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
