cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
891
Views
0
Helpful
1
Replies

T1 Wan lab setup

Jose Borquez
Level 1
Level 1

I am attempting to setup a home practice wan lab with 3 1841 routers.  Routers R1 & R3 each have 1 wic 1dsu t1 v2 interface and R2 has two wic 1dsu t1 v2 interfaces to connect to R1 & R3.  I am experiencing a problem where the serial connection from R2 to R3 has line status of up and protocol status of down.  The serial connection from R2 to R1 is up up.  The configs on each router look good, but perhaps I am missing something.  Are two T1 lines supported on an 1841?  Should I switch the interfaces to wic 1t?  Below are the configs for each router if anyone can identify a configuration problem.  Any help would be greatly appreciated.  Thank you.

R1#sh run
Building configuration...

Current configuration : 815 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R1
!
boot-start-marker
boot-end-marker
!
!
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
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0

description Link to R2
ip address 10.1.1.1 255.255.255.252
encapsulation ppp
no fair-queue
service-module t1 clock source internal
service-module t1 timeslots 1-24
!
ip classless
!
ip http server
no ip http secure-server
!
!
!
control-plane
!
!
line con 0
logging synchronous
line aux 0
line vty 0 4
login
!
end

_______________________________________________________

R2#sh run
Building configuration...

Current configuration : 1005 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R2
!
boot-start-marker
boot-end-marker
!
logging message-counter syslog
!
no aaa new-model
dot11 syslog
ip source-route
!
!
!
!
ip cef
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
archive
log config
  hidekeys
!
!
!
!
!
!
!
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/0/0

description Link to R1
ip address 10.1.1.2 255.255.255.252
encapsulation ppp
service-module t1 timeslots 1-24
!
interface Serial0/1/0
description Link to R3

ip address 10.2.2.2 255.255.255.252
encapsulation ppp
service-module t1 clock source internal
service-module t1 timeslots 1-24
!
ip forward-protocol nd
no ip http server
no ip http secure-server
!
!
!
!
!
!
!
!
!
control-plane
!
!
!
line con 0
logging synchronous
line aux 0
line vty 0 4
login
!
scheduler allocate 20000 1000
end

______________________________________________________

R3#sh run
Building configuration...

Current configuration : 865 bytes
!
version 12.4
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname R3
!
boot-start-marker
boot-end-marker
!
logging message-counter syslog
!
no aaa new-model
dot11 syslog
ip source-route
!
!
!
!
ip cef
no ipv6 cef
!
multilink bundle-name authenticated
!
!
!
!
!
archive
log config
  hidekeys
!
!
!
!
!
!
!
!
interface FastEthernet0/0
no ip address
shutdown
duplex auto
speed auto
!
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
!
interface Serial0/1/0

description Link to R2
ip address 10.2.2.1 255.255.255.252
encapsulation ppp
no fair-queue
service-module t1 timeslots 1-24
!
ip forward-protocol nd
no ip http server
no ip http secure-server
!
!
!
!
!
!
!
!
!
control-plane
!
!
!
line con 0
logging synchronous
line aux 0
line vty 0 4
login
!
scheduler allocate 20000 1000
end

1 Reply 1

Richard Burts
Hall of Fame
Hall of Fame

There are several things that might cause these symptoms. I would start by checking on the clocking. I note that R1 to R2 is reported as working and the clock source internal is configured on R1. R3 to R2 is reported as not working and the clock source is configured on R2. Try moving the clock source internal to R3 and see if it makes any difference.

HTH

Rick

HTH

Rick
Review Cisco Networking for a $25 gift card