Cannot see other routers over WAN 2

[ManagerJay]

The company I work for is preparing to change orivders for our frame relay service from AT&T to SPRINT.

Yesterday, we cut over the voice and Internet service without a problem. However, our frame-relay service would not come up.

Today, I tried to connect two of the routers over the WAN, but was not able to do so. Both routers show Serial0 Up, Line Protocol UP. Additionally, both routers are sending and receiving LMI requests properly. I am able to see the counters incrementing using sh frame-relay lmi and SPRINT is able to see the LMI requests in their switch, but router 1 cannot see router 2.

Router 1 is a Cisco 2501, is located in our headquarters office and all of our services come in on the same T-1 line. Channels 1-7 and for frame, 8-18 for voice, and 19-24 for IP. Both voice and IP are working fine. The CSU/DSU is an AT&T Paradyne 3610 (I can't remember the exact model right now).

Router 2 is a Cisco 2510 and is located in one of our regional offices. The data comes in on a PL to an AT&T Paradyne 3510 (56K line speed).

In working with the engineers today, they were not able to find anything obviously wrong with my router configuration.

I will post the configuration files for both routers tomorrow.

Has anyone seen anything like this before? Could this be a problem with the CSU/DSUs? Or, have I overlooked the obvious?

Thanks for your help.



Jay

 

[Guest_imported]

Jay,

Check your ip addresses and subnet masks. What do you see in your routing table?

Send your configs so we can take a look.

d_westall@yahoo.com

Also have you had Sprint throw you some loops from various COs? Just because your interface is UP/UP doesn't mean the path is good all the way through the cloud. UP/UP and LMI UP just means you can see the nearest frame relay switch. Work on the phone with the frame relay folks while they throw the loops to you. You should be able to see the loops as they throw them. Your interfaces will go UP/UP/LOOPED. If they put up a loop and you don't see your interface change to UP/UP/LOOPED something is wrong with the path.

Good Luck

Debbie Westall

 

[jeter]

Agree, with Sprint ANS 18006038044 you should be able to provide a loop to them. Make sure that the circuit is normal up, not in a test mode. If this is correct then you may want to check your ip scheme and subnet masks. I would also at a last resort have the pvc rebuilt and mapped correctly. Good Luck !!! Jeter@LasVegas.com
J.Fisher CCNA

 

[ManagerJay]

The router configuration we are using is the same configuration we were using with AT&T, except the LMI type has been changed from CISCO to ANSI. On Friday, the engineers were able to loop the CSU/DSUs on both ends of the circuits without an problems, and they were able to see traffic from each of the routers in the switches. But, we are still not able to see any routers on our WAN.

I have also confirmed the DLCI numbers we were assigned/requested and they are correct. Do a sh frame-relay pvc from a regional office only shows the PVC to the headquarters office. Sorry, but I do not have the exact text of what was displayed.

Our network is configured in a star, with the headquarters office being the center of the star. Following is the configuration for that

Current configuration:
!
version 11.0
service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname JCMr01
!
enable secret 5 $1$kIyG$4kfwo7eER8m6CeURPnWNH0
!
!
interface Ethernet0
description JC Backbone Ethernet
ip address 10.129.10.1 255.255.255.0 secondary
ip address 12.X.X.X 255.255.255.0
!
interface Serial0
description Frame Relay Link - Local DLCI 100
ip unnumbered Ethernet0
encapsulation frame-relay
bandwidth 192
frame-relay map ip 199.223.158.65 105 broadcast
frame-relay map ip 199.223.158.129 115 broadcast
frame-relay map ip 199.223.158.193 140 broadcast
frame-relay map ip 199.223.158.33 135 broadcast
frame-relay map ip 199.223.158.97 110 broadcast
frame-relay map ip 199.223.158.161 120 broadcast
!
interface Serial1
description Internet Link
ip address 12.127.114.222 255.255.255.252
encapsulation ppp
bandwidth 128
!
router eigrp 25
passive-interface Serial1
network 199.223.158.0
network 12.0.0.0
network 10.0.0.0
network 192.168.77.0
!
ip host SFMr01 199.223.158.65
ip host KCMr01 199.223.158.97
ip host SPMr01 199.223.158.129
ip host SSLr01 199.223.158.193
ip host SGMr01 199.223.158.33
ip host NSLr01 199.223.158.161
ip host NET-ADMIN 12.13.103.67 255.255.255.0
ip classless
ip route 0.0.0.0 0.0.0.0 12.13.103.126
ip route 172.16.8.0 255.255.248.0 12.13.103.3
ip route 192.168.40.0 255.255.255.0 12.13.103.3
ip route 199.223.158.224 255.255.255.224 12.13.103.126
ip route 199.223.201.0 255.255.255.0 12.13.103.3
logging buffered

line con 0
password 7 073D244866080D291E1C1E14
login
length 0
line aux 0
password 7 073D244866080D291E1C1E14
transport input all
line vty 0
password 7 073D244866080D291E1C1E14
login
length 0
line vty 1 4
password 7 073D244866080D291E1C1E14
login
!
end

Following is the configuration of one of the regional office routers (all are essentially configured the same except for DLCI, IP and bandwidth).

Current configuration:
!
version 11.0
service udp-small-servers
service tcp-small-servers
!
hostname SPMr01
!
enable secret 5 $1$Tdrp$dd0.uKiZtBGkf2S.5w/XW.
!
!
hub ether 0 1
link-test
auto-polarity
!
hub ether 0 2
link-test
auto-polarity
!
hub ether 0 3
link-test
auto-polarity
!
hub ether 0 4
link-test
auto-polarity
!
hub ether 0 5
link-test
auto-polarity
!
hub ether 0 6
link-test
auto-polarity
!
hub ether 0 7
link-test
auto-polarity
!
hub ether 0 8
link-test
auto-polarity
!
interface Ethernet0
description St. Peters Ethernet
ip address 10.128.40.1 255.255.255.0 secondary
ip address 199.223.158.129 255.255.255.224
!
interface Serial0
description Frame Relay Link - Local DLCI 115
ip unnumbered Ethernet0
encapsulation frame-relay
bandwidth 56
no fair-queue
frame-relay map ip 12.13.103.1 100 broadcast
!
interface Serial1
no ip address
shutdown
!
router eigrp 25
network 199.223.158.0
network 10.0.0.0
network 192.168.77.0
!
ip host NSLr01 199.223.158.161 255.255.255.224
ip host SSLr01 199.223.158.193 255.255.255.224
ip host KCMr01 199.223.158.97 255.255.255.224
ip host SGMr01 199.223.158.33 255.255.255.224
ip host SFMr01 199.223.158.65 255.255.255.224
ip host JCMr01 12.13.103.1 255.255.255.0
ip route 0.0.0.0 0.0.0.0 12.13.103.1
ip route 12.27.0.0 255.255.0.0 12.13.103.126
ip route 12.40.0.0 255.255.0.0 12.13.103.126
!
line con 0
password XXXXXXX
login
line aux 0
password XXXXXXX
login
transport input all
line vty 0 4
password XXXXXXXX
login
!
end

The CSU/DSU at the remote office is an AT&T Paradyne 3510 and the CSU/DSU at the headquarters office is an AT&T Paradyne 3160 which is also passing voice channels to the PBX.

To the headquarters office, channels 1-7 are for frame-relay, 8-18 are for voice and 19-24 and for IP. While we were working last week, the voice portion came up fine, and the IP portion came up fine.

Thanks again for all your help. If you need any additonal informaiton, please do not hesitate to ask.



Jay

 

[jeter]

interface Serial0
description Frame Relay Link - Local DLCI 100
ip unnumbered Ethernet0
encapsulation frame-relay
bandwidth 192
frame-relay map ip 199.223.158.65 105 broadcast
frame-relay map ip 199.223.158.129 115 broadcast
frame-relay map ip 199.223.158.193 140 broadcast
frame-relay map ip 199.223.158.33 135 broadcast
frame-relay map ip 199.223.158.97 110 broadcast
frame-relay map ip 199.223.158.161 120 broadcast


Host router on int ser 0 setup like so

int ser 0
router#(config-if)no ip address
router#(config-if)encapsulation frame-relay
router#(config-if)frame-relay lmi-type ansi
router#(config-if)no directed-broadcast
router#(config-if)no shut

int ser 0.1 point-to-point
router#(config-if)ip address xxx.xxx.xxx.xxx subnet x.x.x.x
router#(config-if)frame-relay interface DLCI xxx IETF

Then if there is more you can keep adding sub interfaces
on the HOST router. Let me know how this goes. With the way
you setup is now I do not see a LMI-TYPE and or a DLCI.







Jeter@LasVegas.com
J.Fisher CCNA

 

[wybnormal]

Ding!!ding!!ding!!! Give the man a cigar.. I'm willing to bet with Jeter that the missing DLCI statement is the problem

Just for the record, the Cisco defaults the LMI to to auto:
"Beginning with Cisco IOS Release 11.2, the software supports Local Management Interface (LMI) autosense, which enables the interface to determine the LMI type supported by the switch. Support for LMI autosense means that you are no longer required to configure the LMI explicitly"

Here is a useful link about frame relay configuration:

http://www.cisco.com/univercd/cc/td...os121/121cgcr/wan_c/wcdfrely.htm#xtocid155318

Let us know how it goes.

MikeS
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin

 

[ManagerJay]

Thanks to everyone for their help. As it turns out, our provider had something mapped wrong in their switch.

Thanks again for all your help.



Jay