03-03-2003 01:17 PM - edited 03-02-2019 05:32 AM
I have 2 7513's in my core with ATM DS3 attached, connecting remote offices using Frame-Relay Internetworking. 2 PVC's are mapped to the 2 7513's, one is primary the other is for backup. If I shut any of the connections the other end doesn't see it go away. I know this is because the frame is still seeing lmi responses and the ATM is still seeing OAM. How do I config to make the interfaces actually see the other end go down? No traffic will go to the backup PVC if the router thinks the primary is still up.
03-03-2003 02:10 PM
Check out FRF.8 Spec. End to end Frame to ATM pvc/vc management should get you what you want.
http://www.cisco.com/en/US/tech/tk39/tk53/technologies_configuration_example09186a00800945b3.shtml
Hope this helps you,
Don
03-04-2003 06:33 AM
Unfortunately, the switch belongs to AT&T, so I don't have any control over it. I am using 160X routers with point-to-point subinterfaces on the remote end and 7513's with PA-A3-T3's in VIPs also with point-to-point subinterfaces.
Here is the config of the serial interface on the remote:
interface Serial0
no ip address
encapsulation frame-relay
no ip route-cache
no ip mroute-cache
bandwidth 128
no fair-queue
service-module t1 timeslots 1-2
!
interface Serial0.60 point-to-point
description Primary PVC to AlnA ATM 11/0/0.905
ip address 192.168.7.66 255.255.255.252
no ip route-cache
no ip mroute-cache
bandwidth 128
frame-relay interface-dlci 60 IETF
!
interface Serial0.61 point-to-point
description Secondary PVC to AlnB ATM 11/0/0.905
ip address 192.168.7.70 255.255.255.252
no ip route-cache
no ip mroute-cache
bandwidth 4
frame-relay interface-dlci 61 IETF
!
interface Serial0.109 point-to-point
description Local DLCI 905
ip address 192.168.64.22 255.255.255.252
ip broadcast-address 192.168.64.23
no ip proxy-arp
no ip route-cache
no ip mroute-cache
frame-relay interface-dlci 109
Here is the config from one of the 7513's:
interface ATM11/0/0
no ip address
load-interval 30
atm uni-version 3.1
!
interface ATM11/0/0.51 point-to-point
description AlnB-SchRTR4 ATM 1/1/0.55
ip address 192.168.7.17 255.255.255.252
pvc SchRTR4 1/51
vbr-nrt 45000 45000 1
no ilmi manage
oam-pvc manage
!
!
interface ATM11/0/0.63 point-to-point
description AlnB-CMS2 ATM 6/0.61
ip address 192.168.7.13 255.255.255.252
pvc CMS1.63 1/63
vbr-nrt 45000 45000 1
no ilmi manage
oam-pvc manage
!
!
interface ATM11/0/0.65 point-to-point
description AlnB-SchRTR4 ATM 1/1/0.61
ip address 192.168.7.9 255.255.255.252
pvc SchRTR4.65 1/65
vbr-nrt 45000 45000 1
no ilmi manage
oam-pvc manage
!
!
interface ATM11/0/0.905 point-to-point
description Secondary ATM/FR Link to gwLoveland
bandwidth 4
ip address 192.168.7.69 255.255.255.252
pvc Loveland 1/905
protocol ip 192.168.7.71 broadcast
vbr-nrt 128 4 1
no ilmi manage
oam-pvc manage
encapsulation aal5snap
Any suggestions on what I can do with what is under my control?
03-04-2003 06:59 AM
For End to end PVC management you'll need some IWF/FRF.8 function in the cloud for this to happen. Possibly your provider can give you these functions. Here is another good link showing what is needed for this to occur.
http://www.cisco.com/warp/public/121/frf8_pvc_manage.html
Hope this helps you,
Don
03-05-2003 07:30 AM
Don, Thanks. Scenario 2 in this document creates exactly what we are seeing. Now I just have to get AT&T to configure the IWF correctly.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: