Multilink frame relay troubles on CIsco 7206vxr

[rharruff]

I have just changed to a multilink frame relay service at our head end and now I have sluggishness.
I have a 7206VXR at the head end and 2620's at the remote sites, using traffic shaping.
The remotes have frac T's and a 56k backup circuit.
There are distance statements on the backups, only used if the primary goes down.
This was wotrking pretty good before the multilink ... now I have troubles with sluggishness and the 7206 states the traffic shaping is not active and dropping packets, but does show packets being delayed.

What am I missing?

 

[plshlpme]

youll need to post up some config to get help...
maybe your map class is not assigned to your interface properly?

 

[rharruff]

Thank you for the reply.

I have used the same configuration and only made minimal adjustments for the multilink.
We sort of upgraded from three separate T's ... two fractional and 1 full ... to three full bonded T's.
Very little has changed with the configurations, but had to upgrade IOS and memory componets to support MFR at the head end.

Here is my head end config ...

Cisco 7206VXR (NPE400) processor (revision A) with 229376K/32768K bytes of memory.
Processor board ID 21271546
R7000 CPU at 350MHz, Implementation 39, Rev 3.2, 256KB L2 Cache
6 slot VXR midplane, Version 2.0

Last reset from power-on

PCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.
Current configuration on bus mb0_mb1 has a total of 400 bandwidth points.
This configuration is within the PCI bus capacity and is supported.

PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.
Current configuration on bus mb2 has a total of 0 bandwidth points
This configuration is within the PCI bus capacity and is supported.

Please refer to the following document "Cisco 7200 Series Port Adaptor
Hardware Configuration Guidelines" on Cisco.com <

http://www.cisco.com>

for c7200 bandwidth points oversubscription and usage guidelines.


2 FastEthernet interfaces
4 Serial interfaces
4 Channelized T1/PRI ports
125K bytes of NVRAM.

62720K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).

Configuration register is 0x2102


version 12.4
no service pad
service timestamps debug uptime
service timestamps log datetime msec localtime
service password-encryption
!
hostname FW_Host
!
boot-start-marker
boot-end-marker
!
enable secret 5
enable password 7
!
no aaa new-model
!
resource policy
!
no ip cef
!
!
ip domain name ad.xxxx.org
ip name-server 172.16.4.200
ip name-server 172.16.100.51
frame-relay switching
!
!
controller T1 1/0
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
description AT&T_MFR_T1_3
!
controller T1 1/1
shutdown
framing esf
linecode b8zs
!
controller T1 2/0
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
description AT&T_MFR_T1_1
!
controller T1 2/1
framing esf
linecode b8zs
channel-group 0 timeslots 1-24
description AT&T_MFR_T1_2
!
!
interface MFR1
no ip address
encapsulation frame-relay IETF
frame-relay traffic-shaping
frame-relay lmi-type ansi
!
interface MFR1.101 point-to-point
description 10 512k/768k
bandwidth 768
ip address 172.16.110.1 255.255.255.0
frame-relay class 512/768
frame-relay interface-dlci 101
!
interface MFR1.102 point-to-point
description 02 512k/768k
bandwidth 768
ip address 172.16.102.1 255.255.255.0
frame-relay class 512/768
frame-relay interface-dlci 102
!
interface MFR1.103 point-to-point
description 03 512k/1.54m
bandwidth 1536
ip address 172.16.103.1 255.255.255.0
frame-relay class 512/768
frame-relay interface-dlci 103
!
interface MFR1.104 point-to-point
description 13 32k/56k
bandwidth 56
ip address 172.16.213.1 255.255.255.0
frame-relay class 56k
frame-relay interface-dlci 104
!
interface MFR1.105 point-to-point
description 01 32k/56k
bandwidth 56
ip address 172.16.201.1 255.255.255.0
frame-relay class 56k
frame-relay interface-dlci 105
!
interface MFR1.106 point-to-point
description 06 32k/56k
bandwidth 56
ip address 172.16.206.1 255.255.255.0
frame-relay class 56k
frame-relay interface-dlci 106
!
interface MFR1.202 point-to-point
description 01 256k/768k
ip address 172.16.101.1 255.255.255.0
frame-relay class 768k
frame-relay interface-dlci 202
!
interface MFR1.203 point-to-point
description 06 256k/768k
bandwidth 768
ip address 172.16.106.1 255.255.255.0
frame-relay class 768k
frame-relay interface-dlci 203
!
interface MFR1.204 point-to-point
description 10 32k/56k
bandwidth 56
ip address 172.16.210.1 255.255.255.0
frame-relay class 56k
frame-relay interface-dlci 204
!
interface MFR1.205 point-to-point
description 02 32k/56k
bandwidth 56
ip address 172.16.202.1 255.255.255.0
frame-relay class 56k
frame-relay interface-dlci 205
!
interface MFR1.206 point-to-point
description 03 32k/56k
bandwidth 56
ip address 172.16.203.1 255.255.255.0
frame-relay class 56k
frame-relay interface-dlci 206
!
interface MFR1.210 point-to-point
description 13 512k/768k
bandwidth 768
ip address 172.16.113.1 255.255.255.0
frame-relay class 512/768
frame-relay interface-dlci 210
!
interface FastEthernet0/0
description 100_network
ip address 172.16.100.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/1
description 04_network
ip address 172.16.4.1 255.255.255.0
duplex auto
speed auto
!
interface Serial1/0:0
description Host-3
no ip address
encapsulation frame-relay MFR1
no arp frame-relay
frame-relay multilink lid 3
!
interface Serial2/0:0
description Host-1
no ip address
encapsulation frame-relay MFR1
no arp frame-relay
frame-relay multilink lid 1
!
interface Serial2/1:0
description Host-2
no ip address
encapsulation frame-relay MFR1
no arp frame-relay
frame-relay multilink lid 2
!
router rip
version 2
passive-interface MFR1.104
passive-interface MFR1.105
passive-interface MFR1.106
passive-interface MFR1.204
passive-interface MFR1.205
passive-interface MFR1.206
network 172.16.0.0
no auto-summary
!
ip route 0.0.0.0 0.0.0.0 172.16.100.52
ip route 172.16.1.0 255.255.255.0 172.16.201.2 150
ip route 172.16.2.0 255.255.255.0 172.16.202.2 150
ip route 172.16.3.0 255.255.255.0 172.16.203.2 150
ip route 172.16.5.0 255.255.255.0 172.16.3.1
ip route 172.16.6.0 255.255.255.0 172.16.206.2 150
ip route 172.16.7.0 255.255.255.0 172.16.100.52
ip route 172.16.8.0 255.255.255.0 172.16.100.52
ip route 172.16.10.0 255.255.255.0 172.16.210.2 150
ip route 172.16.11.0 255.255.255.0 172.16.100.52
ip route 172.16.13.0 255.255.255.0 172.16.213.2 150
ip http server
no ip http secure-server
!
!
!
map-class frame-relay 512/768
frame-relay cir 768000
frame-relay mincir 512000
frame-relay adaptive-shaping becn
!
map-class frame-relay 768k
frame-relay cir 768000
frame-relay mincir 256000
frame-relay adaptive-shaping becn
!
map-class frame-relay 56k
frame-relay cir 56000
frame-relay mincir 32000
frame-relay adaptive-shaping becn
logging alarm informational
!
!
control-plane
!
!
gatekeeper
shutdown
!
!
end

And here is a remote ...

cisco 2620XM (MPC860P) processor (revision 0x200) with 94208K/4096K bytes of memory.
Processor board ID JAE08020SNC (2948225132)
M860 processor: part number 5, mask 2
Bridging software.
X.25 software, Version 3.0.0.
1 FastEthernet/IEEE 802.3 interface(s)
2 Serial network interface(s)
32K bytes of non-volatile configuration memory.
32768K bytes of processor board System flash (Read/Write)

Configuration register is 0x2102


version 12.3
service timestamps debug uptime
service timestamps log datetime msec localtime
service password-encryption
!
hostname 10
!
boot-start-marker
boot-end-marker
!
logging buffered 4096 debugging
enable secret 5
enable password 7
!
no aaa new-model
ip subnet-zero
!
!
ip domain name ad.xxxx.org
ip name-server 172.16.10.200
no ftp-server write-enable
!
!
interface FastEthernet0/0
ip address 172.16.10.1 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
bandwidth 768
no ip address
encapsulation frame-relay IETF
no ip mroute-cache
no fair-queue
service-module t1 timeslots 1-12
no arp frame-relay
frame-relay traffic-shaping
frame-relay lmi-type ansi
!
interface Serial0/0.101 point-to-point
description 512K/768K to Host DLCI 101
bandwidth 768
ip address 172.16.110.2 255.255.255.0
no ip mroute-cache
no arp frame-relay
frame-relay class 768k
frame-relay interface-dlci 101
!
interface Serial0/1
bandwidth 56
no ip address
encapsulation frame-relay IETF
no ip mroute-cache
no fair-queue
no arp frame-relay
frame-relay traffic-shaping
frame-relay lmi-type ansi
!
interface Serial0/1.204 point-to-point
description 32K/56K to Host DLCI 204
bandwidth 56
ip address 172.16.210.2 255.255.255.0
no ip mroute-cache
no arp frame-relay
frame-relay class 56k
frame-relay interface-dlci 204
!
router rip
version 2
passive-interface Serial0/1.204
network 172.16.0.0
no auto-summary
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.16.100.52
ip route 172.16.0.0 255.255.0.0 172.16.210.1 150
ip route 172.16.7.0 255.255.255.0 172.16.100.1
ip http server
!
!
map-class frame-relay 768k
frame-relay adaptive-shaping becn
frame-relay cir 768000
frame-relay mincir 512000
!
map-class frame-relay 56k
frame-relay adaptive-shaping becn
frame-relay cir 56000
frame-relay mincir 32000
!
!
end

Any pointers would be great.

Thanks
RAH

 

[plshlpme]

what kind of utilization are you getting on the three t1's?

have you confirmed that it is using the three individual 1s properly?

a couple little things that i see.. not sure if they will make a difference but...
ip cef is disabled, and i don't see ip subnet zero or ip classless..
this could be effecting your routing???


we use frame-relay fragment for you frame-relay traffic shaping it looks like this:

map-class frame-relay 512k
frame-relay cir 512000
frame-relay bc 5120
frame-relay mincir 512000
frame-relay fragment 640


the fragment command basically works out to the number of time slots*80

512k = 8 times slots * 80 = 640
the fragmentation allows the packets to be put onto the line faster for the fractional circuits...

what kind of cpu load are you experiencing at the sluggish times?

sh proc cpu his