12-03-2010 06:33 AM
Hi, i've been searching the support forums and looked at numerous discussions but haven't been able to get my 2511 to connect to other devices via rollover cables. Each device responds differently (which i've included below). Here is my config:
dc01-console#show configuration
Using 745 out of 32762 bytes
!
version 11.3
no service password-encryption
!
hostname ######
!
enable secret 5 $####################
enable password ################
!
ip subnet-zero
no ip domain-lookup
ip host MX960 2001 192.168.45.1
ip host cisco3825 2005 192.168.45.1
ip host sa2500 2009 192.168.45.1
ip host ssg550-2 2004 192.168.45.1
ip host ssg550-1 2006 192.168.45.1
ip host 28ADE 2010 192.168.45.1
!
!
interface Loopback0
ip address 192.168.45.1 255.255.255.255
no ip directed-broadcast
!
interface Ethernet0
ip address 10.10.10.5 255.255.0.0
no ip directed-broadcast
!
interface Serial0
no ip address
no ip directed-broadcast
shutdown
!
ip classless
ip route 0.0.0.0 0.0.0.0 10.10.0.1
snmp-server community ######### RO
!
line con 0
line 1 16
session-timeout 25
no exec
exec-timeout 0 0
login
transport input all
telnet speed 9600 9600
stopbits 1
flowcontrol hardware
line aux 0
line vty 0 4
password password!
no login
!
end
---------------------------------------------------------------
MX960 - Hangs
dc01-console#connect mx960
Trying MX960 (192.168.45.1, 2001)... Open
Cisco 3825
Works
SA2500 -- Hangs
dc01-console#connect sa2500
Trying sa2500 (192.168.45.1, 2009)... Open
SSG550-2 -- Login Failure Loop -- NOW WORKS
dc01-console#connect ssg550-2
Trying ssg550-2 (192.168.45.1, 2004)... Open
### Login failed
login: dc01-console>
password:
### Login failed
login: dc01-console>
password:
SSG550-1 -- Login Failure Loop -- NOW WORKS
dc01-console#connect ssg550-1
Trying ssg550-1 (192.168.45.1, 2006)... Open
### Login failed
login: dc01-console>login: dc0
password:
### Login failed
login: dc01-console>login: dc01-console>
password:
28ADE
Works
Updated with what works.
Edited with updated config. Still no luck on MX960 or SA2500.
12-03-2010 11:29 AM
This is fairly old stuff. I tried to find some of the older documents on the subject.
http://www.cisco.com/en/US/docs/ios/11_3/configfun/configuration/guide/fctrmopr.html
http://www.cisco.com/en/US/docs/ios/12_0/dial/configuration/guide/dcmodem.html#wp9362
In the lower one, check the section: Specify Decimal TCP Port Numbers when Connecting to Lines
It has helped me in the past.
regards,
Leo
12-04-2010 12:08 PM
Eric
The suggestion from Leo about specifying TCP port numbers suggests that there might be an issue with how you have specified the port numbers in your ip host commands. Since most of the devices do work I am not sure that there is a problem in how you are specifying the TCP port numbers. But I do think that it would be good if you could check and verify that the devices that are not working are plugged into the ports specified by your ip host commands.
It also occurs to me to wonder since both devices that are not working are not Cisco devices whether those devices might want their console connections on straight through cables rather than the roll over cables that work so well for Cisco.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide