Can I backup a frame relay NNI trunk with ISDN?

I have four Cisco routers interlinked as frame relay switches. I would like to backup my NNI trunks with ISDN, is it possible? If so, how do I configure my frame-relay route statements to point to the ISDN if the same statements also point to the serial NNI trunk?

No, you cannot backup with ISDN a Frame relay NNI trunk.
ISDN can backup frame relay interfaces DTE-DCE.

Similar Messages

How would you backup your Frame-relay links betweeen sites?

We have a need to backup or do overflow type routing between sites in the event our frame-relay line goes down or service is degraded. We are exploring several options such a VPN using a access circuit or ISDN. What stategy are you currently and are you happy with thte performance?

Other than an ISDN as backup you could get a lower CIR frame circuit from another vendor and load balence weighing the load to your primary circuit

Can I backup multiple users on one mac with Personal Backup X5

Thinking of getting Personal Backup X5 by Intego. I have 4 users on my one mac and need to be able to back up each user's home directory. Does anyone have experience with this app? Can I do this? What do you think if PB X5?
Thanks

Thanks for the advise. I have used CCC before, but right now, I just want a backup solution to backup the home directories of each user on my single mac. I may someday need to clone my main disk, but right now I don't need that. I am using "Backup" now, but I have to log in as each user and run it from their account. I guess I would need to do this with whatever app I use, since some files are protected. Can SuperDuper just do this sort of thing? Can I copy from my account in some "root" mode, and copy the home directories of all my users (wife and kids)?
I downloaded a trial version of Personal Backup X5, but I can't figure out how much the actual app costs, and I don't want to spend too much, considering I can do most of what I need with "Backup", which I already have. I would consider $30 for SuperDuper if it could do the basic incremental backups, etc. I was ****** when I tried to install Personal Backup and it told me it required a re-boot. With 4 accounts logged in, it isn't a simple request.
Thanks for your help.

Frame Relay Setup

Greetings!
I'm attempting to set up a Frame Relay (FR) lab with a few routers, and I'm running into some trouble. The router I'm using as the FR switch is a 3825, which has two VWIC2-2MFT-T1/E1 cards installed. The three other routers are 1841s with WIC-1DSU-T1 cards.
I'm getting the following message, when trying to apply clocking to the FR controllers: "This command applies only to DCE interfaces". I read elsewhere that the "V" in "VWIC2" applies to Voice, and that DCE simply can't be done on them. I'm very new to all of this, so I hope this isn't a ridiculous question: could I uninstall the VWICs from the FR router, put them on the 1841s, and then put the three WIC-1DSUs on the FR switch to make it work? Again, I hope that's not utterly silly, and it's worth asking.
If I can't pull this off, may I get some suggestions?
Thanks, in advance!

Thanks very much for the breakdown, rhirani! I made a few T1-crossover cables to connect the 1841s, so that's what's being used. I ran "sh controller", and the FR switch gave me a ton of information:
FR#sh controller T1
T1 0/0/0 is down.
Applique type is Channelized T1
Cablelength is long 0db
Transmitter is sending remote alarm.
Receiver has loss of signal.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20071011, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (147 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 147 Unavail Secs
Total Data (last 67 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 60300 Unavail Secs
T1 0/0/1 is up.
Applique type is Channelized T1
Cablelength is long 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20071011, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (149 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 67 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 10 Unavail Secs
T1 0/1/0 is up.
Applique type is Channelized T1
Cablelength is long 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20071011, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (146 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 67 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 11 Unavail Secs
T1 0/1/1 is up.
Applique type is Channelized T1
Cablelength is long 0db
No alarms detected.
alarm-trigger is not set
Soaking time: 3, Clearance time: 10
AIS State:Clear LOS State:Clear LOF State:Clear
Version info Firmware: 20071011, FPGA: 13, spm_count = 0
Framing is ESF, Line Code is B8ZS, Clock Source is Line.
CRC Threshold is 320. Reported from firmware is 320.
Data in current interval (148 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
2 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs
Total Data (last 67 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
607 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
607 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 11 Unavail Secs
I also ran a show-controller for one of the serial interfaces, in case it's at all relevant, here:
FR#sh controller ser0/0/1:0
Interface Serial0/0/1:0
Hardware is GT96Kidb at 0x706FF898, driver data structure at 0x70700424
wic_info 0x0
There was a *lot* more that printed out for the serial interface, but I didn't paste all of it.
I hope this is enough to tell.....

Frame-Relay through MPLS cloud

Hi All ,
Can anybody explain if I make a MPLS pe act as a frame-relay sw too is there in LDP related issue or not ?

It is possible to use Frame Relay switches as Label, Switching Routers. Such Frame Relay switches run network layer routing algorithms (such as OSPF, IS-IS, etc.), and their forwarding
is based on the results of these routing algorithms. No specific
Frame Relay routing is needed.
When a Frame Relay switch is used for label switching, the top
(current) label, on which forwarding decisions are based, is carried
in the DLCI field of the Frame Relay data link layer header of a
frame. Additional information carried along with the top (current)
label, but not processed by Frame Relay switching, along with other
labels, if the packet is multiply labeled, are carried in the generic
MPLS encapsulation defined in [STACK].
Check this out.
http://www.ietf.org/rfc/rfc3034.txt

Is Low MTU (ie 320) for VoIP over Frame-relay can be used to avoid serialization delay for large data packets?

In order to provide voice quality for VoIP, is FR fragmentation equivalent to lowering the MTU size for the serial subinterface of a Frame relay subinterface?
Is there any isues like stop communications, using Low MTU ?

If the router belongs to any of the
platform listed below, then use
FRF12 for you fragmentation. The MTU size
lowering also works but this can cause a high over
head as it can't be specified on a per dlci level.
With multiple dlci i.e. subinterfaces use per dlci fragmentation.. this helps reduce the overhead of changing the MTU size of the physical interface.
Snip config example.( __Must be configured on both side of the termination___)
PHONE 3333312---ROUTERA ----DLCI 100----ROUTERB ---PHONE 2111123
ROUTER A
dial-peer voice 1 voip
destination-pettern 2T
session target ipv4:10.10.10.2
int ser 0/0
encap frame-relay
frame-relay traffic-shaping
no ip address
interface serial0/0.1 point-to-point
ip add 10.10.10.1 255.255.255.252
frame-relay interface-dlci 100
class voice
map-class frame-relay voice
frame cir 64000
frame bc 640
frame mincir 64000
frame-relay ip rtp priority 16384 16383 48
frame fragment 80
frame fair-queue 64 256 0
ROUTER B
dial-peer voice 3 voip
destination-pettern 3T
session target ipv4:10.10.10.1
int ser 0/0
encap frame-relay
frame-relay traffic-shaping
no ip address
interface serial0/0.1 point-to-point
ip add 10.10.10.2 255.255.255.252
frame-relay interface-dlci 100
class voice
map-class frame-relay voice
frame cir 64000
frame bc 640
frame mincir 64000
frame-relay ip rtp priority 16384 16383 48
frame fragment 80
frame fair-queue 64 256 0
This should help if your router is
c2600, c3600, mc3810, c7200, c1750
all running the right level of IOS.
12.1(5)T and above should work well.

VLAN trunk over Frame Relay

I want to define a VLAN 101 within a branch office on one port of a CAT3524XL, that will in turn go to a router in that branch and be trunked back to the main office router (through a frame relay connection). Once in that main router, I want that one VLAN to specifically be directed to one of the unused ethernet interfaces and in turn to another 3500XL switch for distribution. There are already VLANs in the branch that are connected to the main office, but they all come out on the main branch router's e0/0 interface. I need to make an exception with the new VLAN 101 by forcing all VLAN 101 traffic to be on the e1/1. Please HELP!!!

Yes, my requirement is to be able to direct traffic that originated on that one VLAN to a different port on the central router, where there is a captive portal device which will manage that remote traffic. I may have used the wrong term..."trunk". I really need full visibility and control of that remote VLAN. I have other VLANS (voice, data, management) in the remote branch, and they all come back through the frame. I really need to take this particular VLAN and "point" it to the available interface in the main office. Does that sound feasible with PBR? I will read more on it.
Thanks for the info Rick. Any other ideas or help is appreciated.
Mark

Can't ping routers across point-to-point frame-relay

'evening,
Really basic setup. Designed with Packet Tracer, trying to ping routers across a point-to-point frame-relay. I've designed this according to three different training sources who all say the same thing. Yet, all pings failed.
The shows:
R1
R1#copy run st
Destination filename [startup-config]?
Building configuration...
[OK]
R1#show run
Building configuration...
Current configuration : 883 bytes
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
hostname R1
no ip domain-lookup
interface FastEthernet0/0
no ip address
duplex auto
speed auto
shutdown
interface FastEthernet0/1
no ip address
duplex auto
speed auto
shutdown
interface Serial1/0
no ip address
encapsulation frame-relay
interface Serial1/0.12 point-to-point
ip address 192.168.12.1 255.255.255.0
frame-relay interface-dlci 102
interface Serial1/0.13 point-to-point
ip address 192.168.13.1 255.255.255.0
frame-relay interface-dlci 103
ip classless
end
R1#show frame-relay lmi
LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 638 Num Status msgs Rcvd 638
Num Update Status Rcvd 0 Num Status Timeouts 16
LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 0 Num Status msgs Rcvd 0
Num Update Status Rcvd 0 Num Status Timeouts 16
LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 0 Num Status msgs Rcvd 0
Num Update Status Rcvd 0 Num Status Timeouts 16
R1#show frame-relay map
Serial1/0.12 (up): point-to-point dlci, dlci 102, broadcast, status defined, active
Serial1/0.13 (up): point-to-point dlci, dlci 103, broadcast, status defined, active
R1#show frame-relay pvc
PVC Statistics for interface Serial1/0 (Frame Relay DCE)
DLCI = 102, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
input pkts 14055 output pkts 32795 in bytes 1096228
out bytes 6216155 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 32795 out bcast bytes 6216155
DLCI = 103, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
input pkts 14055 output pkts 32795 in bytes 1096228
out bytes 6216155 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 32795 out bcast bytes 6216155
R2
R2#SHOW RUN
Building configuration...
Current configuration : 772 bytes
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
hostname R2
no ip domain-lookup
interface Serial1/0
no ip address
encapsulation frame-relay
interface Serial1/0.12 point-to-point
ip address 192.168.12.2 255.255.255.0
frame-relay interface-dlci 201
ip classless
end
R2#show fr map
Serial1/0.12 (up): point-to-point dlci, dlci 201, broadcast, status defined, active
R2#show fr pvc
PVC Statistics for interface Serial1/0 (Frame Relay DTE)
DLCI = 201, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.12
input pkts 14055 output pkts 32795 in bytes 1096228
out bytes 6216155 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 32795 out bcast bytes 6216155
R2#show fr lmi
LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 679 Num Status msgs Rcvd 678
Num Update Status Rcvd 0 Num Status Timeouts 16
LMI Statistics for interface Serial1/0.12 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 0 Num Status msgs Rcvd 0
Num Update Status Rcvd 0 Num Status Timeouts 16
R3
R3#show run
Building configuration...
Current configuration : 772 bytes
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
hostname R3
interface Serial1/0
no ip address
encapsulation frame-relay
interface Serial1/0.13 point-to-point
ip address 192.168.13.2 255.255.255.0
frame-relay interface-dlci 301
ip classless
end
R3#show fr map
Serial1/0.13 (up): point-to-point dlci, dlci 301, broadcast, status defined, active
R3#show fr lmi
LMI Statistics for interface Serial1/0 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 703 Num Status msgs Rcvd 702
Num Update Status Rcvd 0 Num Status Timeouts 16
LMI Statistics for interface Serial1/0.13 (Frame Relay DTE) LMI TYPE = CISCO
Invalid Unnumbered info 0 Invalid Prot Disc 0
Invalid dummy Call Ref 0 Invalid Msg Type 0
Invalid Status Message 0 Invalid Lock Shift 0
Invalid Information ID 0 Invalid Report IE Len 0
Invalid Report Request 0 Invalid Keep IE Len 0
Num Status Enq. Sent 0 Num Status msgs Rcvd 0
Num Update Status Rcvd 0 Num Status Timeouts 16
R3#show fr pvc
PVC Statistics for interface Serial1/0 (Frame Relay DTE)
DLCI = 301, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0.13
input pkts 14055 output pkts 32795 in bytes 1096228
out bytes 6216155 dropped pkts 0 in FECN pkts 0
in BECN pkts 0 out FECN pkts 0 out BECN pkts 0
in DE pkts 0 out DE pkts 0
out bcast pkts 32795 out bcast bytes 6216155
Any input would really be appreciated.
Thanks

Turns out the mistake was not adding a mask to the subnet. Ex:
Router_2(config_router)# network 192.168.0.0 0.0.255.255
Router_2(config_router)# network 172.27.0.0 0.0.255.255
Doing that on both routers made the hosts capable of pinging each other.
Thanks for the tips everyone

Frame Relay V/s TDM

Why there is a need of Frame Relay services instead of having TDM links,I mean what is the basic difference b/w these two. We can have TDM Muxes instead of FR mux and can provide the connecitivity over TDM links why choose frame relay

Further I want to ask, What is frame relay UNI and NNI apart from its definition I m curious abt the mechanism beyond

Connection from remote sites (Frame Relay WAN) to AS/400 dissapears

Hello,
We have the following problem appearing in our environment:
All connections from remote sites dissapears unexpected from AS/400. After 2-3 minutes remote users get normal connectivity again.
The environment is the the following:
Frame Relay/ATM WAN (Frame Relay on remote sites and ATM in datacenter) comes to Cisco 7204VXR router which connected to LAN switch with 10/100/1000 ports. AS/400 with Fast Ethernet interface also connected to the similar LAN switch. CEF is enabled on the router, IOS version 12.4.3a. We have ETHSTD *ALL parameter set on AS/400. Remote users uses TCP/IP and Telnet but there are a number of 5494 controllers wich uses SNA.
We got the problem for the first time after we enabled CEF on the router.
I suspect that the cause of problem is Ethernet frames of different standards due to ETHSTD *ALL, but can neither reproduce the problem nor understand why it behaves so.
Have anybody had similar problem?
I would be very thanksfull if somebody can help me to solve it.
Thank you in advance.
//Mikhail Galiulin

Hi Martin,
Cisco 7200 itself can access AS/400 as well as all other hosts in the same with AS/400 LAN. There is no any outage in communications which goes to another LAN segment via Netscreen firewall while the communication via Cisco is down. Only those hosts which connected via Cisco are experiencing the problem. I can not say where the traceroute from AS/400 stucks (there are other people who maintain the machine and they never could catch the exact moment of outage).
To turn off CEF I treat as the last option actually and unfortunatelly there is no guarantee that software upgrade will help (we have 12.4.3a now).
So first of all I'm trying to understan WHY it happens because I can not see any systematics in the problem appearance. It can happen 3 times under 2 days and then dissapear for 1-2 months...
//Mikhail Galiulin

Configuring Frame-Relay and the Frame-Relay Switch To Participate in WAN Routing

Hey,
My WAN in my voice lab is currently functional between all of my routers HQ, BR1, and BR1 with full-mesh connectivity. I am using my PSTN router for the frame-relay switching as is shown in the attached configs. I have used the connect commands for the PVC routing logic.
connect HQ-BR1 Serial0/3/0 101 Serial0/2/0 201
connect HQ-BR2 Serial0/3/0 102 Serial0/2/1 301
connect BR1-BR2 Serial0/2/0 202 Serial0/2/1 302
My question concerns the possibility of getting the PSTN router to participate in the WAN and the OSPF routing process? The connect command tells how the PVCs are to be connected and pass through the PSTN router. Is there anyway to do it so that a PVC connects to the PSTN router itself?
I would specifically like to create a connection between the HQ and PSTN router over the WAN. If anyone has any insight on this I would really appreciate it.
Thank you.

Hello Adam,
you don't need to do FR switching.
You just need to configure a back to back PVC associated to a p2p subinterface under PSTN router interface se0/3/0 and HQ:se0/1/0. the new PVC can be 103 on both sides
PSTN
interface ser0/3/0.103 point-to-point
ip address 10.1.13.1 255.255.255.0
frame-relay interface-dlci 103
HQ
interface ser0/1/0.103 point-to-point
ip address 10.1.13.1 255.255.255.0
frame-relay interface-dlci 103
note: I was able to do this using the older syntax frame-relay route under interface configuration on frame relay switch. I would expect to work for you too with newer syntax connect.
Hope to help
Giuseppe

ASR1K 5xE1 MFR Frame relay traffic not forwarding in one direction

Dear Techies,
Hope all is well !
Im doing this inter-op testing with Alcatel device for frame-relay and MFRs and got stuck at this situation which is actually mind boggling and I think i might be missing something "silly" :-(
Its a simple setup of
1. My ASR 1002-X with a LAN (Gig0/0/0) port is connected to a traffic generator.(ixia).
2. ASR WAN port is a 5xE1 bundled into a MFR circuit.
3. WAN link goes to a Alcatel box giving me my FR-DCE with E1s over MFR.
Issue is , I can send traffic to max throughput with  flow initiated from LAN to WAN bit NOT the reverse flow initiated  from WAN side to LAN port. I see traffic coming into my 5xE1s (1.8 mbps each) but the traffic just wont go to the LAN side , somewhere it gets "stuck" or "dropped".
PING works fine from both sides.......but sending traffic is not possible !!
ASR CONFIG
controller SONET 0/3/0
framing sdh
clock source line
aug mapping au-4
au-4 1 tug-3 1
mode c-12
tug-2 1 e1 1 unframed
tug-2 1 e1 2 unframed
tug-2 1 e1 3 unframed
tug-2 2 e1 1 unframed
tug-2 2 e1 2 unframed
tug-2 2 e1 3 unframed
au-4 1 tug-3 2
mode c-12
tug-2 1 e1 1 unframed
tug-2 1 e1 2 unframed
tug-2 1 e1 3 unframed
au-4 1 tug-3 3
mode c-12
interface MFR1
no ip address
encapsulation frame-relay IETF
load-interval 30
frame-relay multilink bid 10MB-PiPe
frame-relay multilink bandwidth-class a
frame-relay lmi-type ansi
interface MFR1.1 point-to-point
ip address 10.10.17.2 255.255.255.0
frame-relay interface-dlci 100
interface GigabitEthernet0/0/0
no ip address
load-interval 30
negotiation auto
interface GigabitEthernet0/0/0.110
encapsulation dot1Q 110
ip address 11.11.11.1 255.255.255.0
interface Serial0/3/0.1/1/1/1:0
no ip address
encapsulation frame-relay MFR1
frame-relay multilink lid First-Link
interface Serial0/3/0.1/1/1/2:0
no ip address
encapsulation frame-relay MFR1
frame-relay multilink lid Second-Link
interface Serial0/3/0.1/1/1/3:0
no ip address
encapsulation frame-relay MFR1
frame-relay multilink lid Third-Link
interface Serial0/3/0.1/1/2/1:0
no ip address
encapsulation frame-relay MFR1
frame-relay multilink lid Fourth-Link
interface Serial0/3/0.1/1/2/2:0
no ip address
encapsulation frame-relay MFR1
frame-relay multilink lid Fifth-Link
SDH_FR#sh frame-relay mul
SDH_FR#sh frame-relay multilink
Bundle: MFR1, State = up, class = A, fragmentation disabled
BID = 10MB-PiPe
Bundle links:
Serial0/3/0.1/1/1/1:0, HW state = up, link state = Up, LID = First-Link
Serial0/3/0.1/1/2/2:0, HW state = up, link state = Up, LID = Fifth-Link
Serial0/3/0.1/1/2/1:0, HW state = up, link state = Up, LID = Fourth-Link
Serial0/3/0.1/1/1/3:0, HW state = up, link state = Up, LID = Third-Link
Serial0/3/0.1/1/1/2:0, HW state = up, link state = Up, LID = Second-Link
SDH_FR#
SDH_FR#
SDH_FR#
SDH_FR#sh fram
SDH_FR#sh frame-relay pvc 100
PVC Statistics for interface MFR1 (Frame Relay DTE)
DLCI = 100, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = MFR1.1
input pkts 8045 output pkts 8044 in bytes 515748
out bytes 527920 dropped pkts 0 in pkts dropped 0
out pkts dropped 0 out bytes dropped 0
in FECN pkts 0 in BECN pkts 0 out FECN pkts 0
out BECN pkts 0 in DE pkts 0 out DE pkts 0
out bcast pkts 0 out bcast bytes 0
5 minute input rate 1000 bits/sec, 2 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
pvc create time 01:07:58, last time pvc status changed 01:07:58
fragment type end-to-end fragment size 1400
SDH_FR#
SDH_FR#
SDH_FR#
SDH_FR#
SDH_FR#
SDH_FR#
SDH_FR#ping 10.10.17.1-------------------------------------------------------------------------- THIS IS ALCATEL SIDE FROM TRAFFIC HAS TO COME.
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.10.17.1, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 3/3/4 ms
SDH_FR#
SDH_FR#
SDH_FR#sh frame-relay traffic
Frame Relay statistics:
ARP requests sent 0, ARP replies sent 0
ARP request recvd 0, ARP replies recvd 0
SDH_FR#

What is the access rate of the head end?
Are you using a codec other than G711?
How many total sites are involved, what protocols are you running?
From the math, 32K is not enough CIR to ensure 4 calls proper Bandwidth. At what point is the voice degrading, is is choppy missing message, sound, jitter, echo or after 1, 2 or 3 calls.
Even if you are using G729a, voice packets could be dropped. Not to say that it is here, but look at the FRS stats to see ip packets are being dropped.
Traffic shaping is always recommended, rtp header compression will help, but the trade-off is around a 20% CPU hit.
If you implement traffic shapping , it needs to be done throughout the network as queueing delays related to data on other slow links and at the headend (specifically here) could be the cause of the distortion alone. I would at least try traffic shapping first, then if the problem doen't go away, increase CIR for Voice, if there are still issues, implement LLQ.

Map-class frame-relay , policy map

Does a service-policy output have to be applied to an interface for qos to work?
here is the config but there is nothing applied to the serial interface..
Thanks for your help
policy-map 256/128KVoice
class 256/128KVoice
priority 112
class class-default
fair-queue
map-class frame-relay 256/128KVoice
frame-relay cir 128000
frame-relay bc 1280
frame-relay be 600
frame-relay mincir 128000
no frame-relay adaptive-shaping
frame-relay fair-queue
frame-relay fragment 150
frame-relay ip rtp priority 16384 16380 210
interface Serial0/0
bandwidth 1544
ip address xxx.xxx.xxx.xxx 255.255.255.255
ip route-cache flow
no fair-queue
service-module t1 timeslots 1-24

Hello,
Will QOS will work in this way where class is put on WAN interface where it should be service policy.
router#sh run interface Se0/0/0.1
Building configuration...
Current configuration : 239 bytes
interface Serial0/0/0.1 point-to-point
bandwidth 2048
ip address XXXX
ip nat outside
frame-relay interface-dlci 555
class COS-OUT-S0/0/0.1
end
COS-OUT-S0/0/0.1 is defined as policy map with class of voice and video.
When checking on WAN int #sh policy-map interface Se0/0/0.1 , can see output of service policy input/output with policy map recpective classes and packets match entries.Is QOS working with this configuration?
Appreciate any input on this.
Regards,
Brajesh.

FRAME RELAY NETWORK TOPOLOGY

THERE IS A FR NETWORK HUB AND SPOKE
IN STAR TOPOLOGY. AT HUB ROUTER THERE ARE POINT-TO-POINT SUBINTERFACES TO SPOKE ROUTERS AND STATIC FR MAP ENTRIES ARE PRESENT. tHE SPOKE ROUTERS COMMUNICATE WITH HUB ROUTER BUT DO NOT COMMUNICATE WITH EACH OTHER.
MY QUESTION IS WHAT TO DO FOR COMMUNICATIONS BETWEEN SPOKE ROUTERS,
1. IS ANY MORE DLCI MAY BE REQUIRED BETWEEN SPOKE ROUTERS?.
2.IS MAP STATEMENT REQUIRED, DLCI WITH IP ADDRESS BETWEEN SPOKE ROUTERS ?

Abdul
There are a couple of things in your question that I hope you can clarify and if so we should be able to get good answers to your question.
At one point you describe the topology as hub and spoke and at another point you describe it as star. Most of us understand these to be two different topologies. So is it hub and spoke or is it star?
Many of us understand hub and spoke to be remote routers connected directly to a central (hub) router while a star is remote routers where some of the remote routers have direct connections to other remotes.
Also you say that the hub has point to point subinterfaces and this is generally the best practice for Frame Relay. Then you say that static FR map entries are present. I do not understand this because with p-t-p subinterfaces you do not need FR maps.
Based on what we have so far I would say that these are the answers to your questions:
1. you might choose to add additional DLCIs but they are not required. any spoke should be able to communicate with any spoke by going to the hub and having the hub forward to the other spoke.
2. No map statements should be required. Part of having p-t-p subinterfaces at the hub is that each spoke is an separate subnet. Therefore from any spoke to any other spoke is just going to a different subnet (through the hub) and no map would be required.
If these answers do not satisfy your requirements then perhaps you can clarify the points about your question.
HTH
Rick

Voice over Frame-Relay

Hi,
Customer of me has several sites connected with leased lines. The leased lines have frame-relay encapsulation (frame-relay back-to-back)
The line has two pvc's configured, one for voice and one for data. The voice PVC works fine. On the data pvc we want to put some QoS.
Here is the partial configuration:
interface Serial0
bandwidth 2000
no ip address
encapsulation frame-relay
no ip route-cache cef
ip route-cache flow
no ip mroute-cache
frame-relay intf-type dce
interface Serial0.1 point-to-point
ip address 10.xx.xx.1 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 120
interface Serial0.2 point-to-point
ip address 10.0.0.1 255.255.255.252
no ip mroute-cache
frame-relay interface-dlci 100
class VOICE
vofr cisco
map-class frame-relay VOICE
frame-relay cir 512000
frame-relay voice bandwidth 256000
frame-relay fragment 320
frame-relay fair-queue
Question is can I just apply a service policy out to the data DLCI or doi i also have to enable frame-relay traffic shaping?
Thanks,
JH

The disadvantage of shaping is that it will actually limit you bandwidth. That is, you won't be able to use the circuit at full capacity, because of the artificial limitation induced by shaping. This is particularly true for a situation like you where the actual circuits is a leased line, and not a FR network.
A better approach would be to reconfigure for simple hdlc encap, and run VoIP instead. This way, you would have all the QOS features you need for voice and data, and be able to use the full capacity with a much simpler configuration.
Actually, even if you want to retain the FR encapsulation and the voice over FR approach, still using a single PVC would be better, for the same reasons given above.
Hope this helps, please rate post if it does!

Can I backup a frame relay NNI trunk with ISDN?

Similar Messages

Maybe you are looking for