Connecting Frame Relay for 3 sites using subinterfaces on Cisco 2611

I have 3 video conferencing sites using frame rely as a dedicated IP netowork for videoconferencing only.  Initally, we were using Tasman routers at all three sites but at the main site (detention center) we found that the Tasman does not allow for subinterfacing.  We have replaced the Tasman with a 2611.  I am now trying to config the 2611 to match the Tasman config which is a little different.  I have attached the origial config from the 3 routers and have followed it with the IP information i was given. I need assistance in the config to connect the two site through the Verizon network via pvc.

Thanks in advance

1 site is the main site where the t1 comes in (Detention Center)
2 remote sites (Circuit and District) which are connected via PVC.

Detention router:
config t
interface ethernet 0
ip address 192.168.168.17 28
exit
interface bundle wan1
link t1 1:1-12
encapsulation frelay
fr
pvc 100
ip address 192.168.168.1 30
exit 3
interface bundle wan2
link t1 1:13-24
encapsulation frelay
fr
pvc 101
ip address 192.168.168.5 30
exit 3
router routerid 192.168.168.17
router ospf
redistribute connected
interface wan1 dlci 100 area 0
exit
interface wan2 dlci 101 area 0
exit
save local

Circuit Router config

config t
interface ethernet 0
ip address 192.168.168.25 28
exit
interface bundle wan1
link t1
encapsulation frelay
fr
pvc 100
ip address 192.168.168.2 30
exit 3
router routerid 192.168.168.25
router ospf
redistribute connected
interface wan1 dlci 100 area 0
exit
save local

District Router config
config t
interface ethernet 0
ip address 192.168.168.33 28
exit
interface bundle wan1
link t1
encapsulation frelay
fr
pvc 100
ip address 192.168.168.6 30
exit 3
router routerid 192.168.168.33
router ospf
redistribute connected
interface wan1 dlci 100 area 0
exit
save local

This is the IP info for each site.
Detention
             Wire add               Interface                 Broadcast                sbnett
serial     192.168.168.0     192.168.168.1         192.168.168.3      255.255.255.252
serial     192.168.168.4     192.168.168.5         192.168.168.7      255.255.255.252
Ethernt   192.168.168.16   192.168.168.17       192.168.168.23    255.255.255.248

Circuit
serial     192.168.168.0      192.168.168.2        192.168.168.3      255.255.255.252
Ethernt   192.168.168.24    192.168.168.25      192.168.168.31    255.255.255.248

District
serial      192.168.168.4     192.168.168.6         192.168.168.7     255.255.255.252
Ethernt    192.168.168.32   192.168.168.33       192.168.168.39   255.255.255.248

Each site only has one endpoint connected to it by ethernet.


























maddoxmaloneAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
lrmooreConnect With a Mentor Commented:
Are you keeping the Tasman's at the remote sites?

Basic config:
  interface serial 0/0
    encap frame-relay IETF
    no shutdown
    frame-relay lmi-type ansi | cisco  <== optional
   
   interface serial 0/0.1 point-to-point
    descript Circuit
    ip address 192.168.168.1 255.255.255.252
    frame-relay interface-dlci 100
 
   interface serial 0/0.2 point-to-point
    descript District
    ip address 192.168.168.5 255.255.255.252
    frame-relay interface-dlci 101

   router ospf 100
    network 192.168.168.0 0.0.0.255 area 0
    redistribute connected

0
 
AutoSpongeCommented:
Try reposting this config with a 'show run' or 'show config'.  The way it's laid out here isn't clear to me.
0
 
maddoxmaloneAuthor Commented:
AutoSponge-Unfortunately, I do not have the ability to do a show run or show config from my location.  Also, the Tasman is set up a little differently and the commands for show run and show config do not return information.

lrmoore-Yes, I will be keeping the two Tasmans at the remote sites (circuit and district)  Currently, I have the detention center connected in a point to point with the circuit.  This is temporary until I get the 2611 installed.

Thanks
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
lrmooreCommented:
Any luck with your config yet? Do you need more information?
What I posted should work for you.
0
 
maddoxmaloneAuthor Commented:
It looks like your solution will work.  Thanks for your help.
0
 
lrmooreCommented:
Post back if you run into any snafus...

-Cheers!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.