Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

Cant telnet to router via ATM interface side

Deployed a new 3825 to this office w/ ATM.

Since moving to ATM have not been able to telnet to the router through the ATM Interface (Tried ip of atm, eth, and loopback no success). Can telnet to a switch behind the router and then telnet to the router from the switch.

Switch <--> ATM Router <--> T3 Router <--> Client trying to connect to ATM Router.

ATM Router ATM Config

interface ATM0/IMA1

mac-address 0015.629a.f100

ip address 10.216.117.1 255.255.255.0

ip route-cache flow

atm vc-per-vp 1024

atm uni-version 3.0

no atm auto-configuration

no atm ilmi-keepalive

no atm address-registration

no atm ilmi-enable

pvc 1/777

protocol ip 10.216.117.2 broadcast

vbr-nrt 3000 3000 1

oam-pvc manage

encapsulation aal5snap

!

!

interface ATM0/0/0

no ip address

no scrambling-payload

ima-group 1

no atm oversubscribe

atm uni-version 3.0

no atm auto-configuration

no atm ilmi-keepalive

no atm address-registration

no atm ilmi-enable

!

interface ATM0/0/1

no ip address

no scrambling-payload

ima-group 1

no atm oversubscribe

atm uni-version 3.0

no atm auto-configuration

no atm ilmi-keepalive

no atm address-registration

no atm ilmi-enable

ATM Router gig interface

interface GigabitEthernet0/0

description Lancaster router to switch connection

ip address 172.16.0.1 255.255.255.0 secondary

ip address 10.231.16.1 255.255.254.0

ip helper-address 10.231.16.20

no ip unreachables

duplex auto

speed auto

media-type rj45

negotiation auto

2 REPLIES
Hall of Fame Super Gold

Re: Cant telnet to router via ATM interface side

Jacob

There are several things that might produce the symptoms that you describe and we do not yet have enough information to identify the most likely cause.

One potential problem is not having a working route to the telnet target, or the telnet target not having a return route to the client. One way to test this would be to ping the address of the telnet target from the client. If ping works then it is not an IP connectivity problem. The fact that you can telnet to the switch behind the router suggests that it is not an IP connectivity problem. ping would confirm this.

When you attempt to telnet what happens? Do you get a prompt to login? Do you get an error message and if so what is the error message? Knowing these things would help narrow down the cause of the problem.

Another thing that might cause these problems is an access list. Is there any access list on any interface? There did not seem to be any in the config that you posted but it was not the complete config. There might also be an access list on the vty ports (assigned with access-class) which controls telnet access. Is there any access-class on the vty ports?

HTH

Rick

New Member

Re: Cant telnet to router via ATM interface side

Can ping Router ethernet interface from host:

H:\>ping 10.231.16.1

Pinging 10.231.16.1 with 32 bytes of data:

Reply from 10.231.16.1: bytes=32 time=148ms TTL=248

Reply from 10.231.16.1: bytes=32 time=52ms TTL=248

Can ping from router also to host.

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.221.40.139, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 76/111/148 ms

No access-list defined on any of the interfaces.

VTY Configed as follows

line vty 0 4

password 7 ****************

login

length 25

transport input all

Pretty stumped on this one, seems weve tried everything.

325
Views
0
Helpful
2
Replies
CreatePlease to create content