Configuring CE-PE link on Frame Relay over ATM

Hi!
Need you guys expert opinion on how to configure configuring CE-PE link on Frame Relay over ATM. I am stump by this one because I never done it before. The CE is a Cisco 7206 with ATM PA and the parameters given to us is DLCI number in x/y format...isn't that the format for PVC. When asked, my SP contact says that it is indeed FR over ATM. Any of you guys who have experience to guide on this or point me in the right direction is most welcome. Thanks
Rgds
Helme

Hello Helme,
ask your provider if they are doing FR to ATM service interworking.
In that case one side is configured for Frame-Relay and the other side for ATM
Service interworking is done by provider.
Verify that you have the same MTU on both sides and configure following ISP specifications
ATM uses two numbers to identify a PVC
int atm 4/0
no ip address
no shut
int atm 4/0.1 point-to-point
mtu 1500
ip address x.x.x.1 255.255.255.252
pvc x/y
enc aal5snap
protocol ip x.x.x.2 broadcast
this should be enough to have it working
on the other side configure or have a point-to-point subif configured on FR
see this example
http://www.cisco.com/en/US/tech/tk39/tk53/technologies_configuration_example09186a00801747e3.shtml
Hope to help
Giuseppe

Similar Messages

  • Configure Frame-Relay over ISDN

    Hi can we configure frame-relay over ISDN can anyone provide me with the details

    Hi
    Check this link
    http://www.cisco.com/warp/public/125/19.pdf
    Hope this helps you,
    Thanks
    Raj

  • XML configuration file to link to frames in Flash - As2.0

    How can I set the url or link attribute from the XML configuration file to link to frames in my movie instead opening a HTML page? I am using Actionscript 2.0
    Thank you.

    What type of file is using this xml data?  If it is being read by the AS2 file, then your data should resemble either frame labels or frame numbers.

  • AToM Frame Relay over MPLS

    Is it possible to have multipoint topologies with FRoMPLS? In other words, if I'm receiving some Frame Relay PVCs on one physical interface on a PE, can I transport some of them to one remote PE and others to another remote PE? Or do I need to have separate physical interfaces to talk to different remote PEs?
    Thanks
    Tarek

    On the PE router, you can indeed take each one of the DLCIs from a same physical interface and connect them to a different egress PE.
    Hope this helps,

  • Frame-relay - config a router as a switch

    I am trying to configure a router as a frame-relay switch called R3.
    R1 (S0/1) is connected to my Frame-Relay Switch R3 (S1/0). R3 has a further 3 connections (S1/1, S1/2 & S1/3) to R2, R4 &R5. So R1 uses subinterfaces.
    I am having problems configuring the switch to say connect R1 to R2.
    Here is my R1 config:
    Interface Serial0/0
    No ip address
    Encapsulation frame-relay
    interface Serial0/0.1 point-to-point
    ip address 10.1.1.1 255.255.255.0
    frame-relay interface-dlci 16
    interface Serial0/0.2 point-to-point
    ip address 10.1.2.1 255.255.255.0
    frame-relay interface-dlci 17
    interface Serial0/0.3 point-to-point
    ip address 10.1.3.1 255.255.255.0
    frame-relay interface-dlci 18
    Here is my Frame-Relay switch (R3) config:
    frame-relay switching
    Interface Serial1/0
    No ip address
    Encapsulation frame-relay
    Clock rate 64000
    Frame-relay intf-type dce
    interface Serial1/0.1 point-to-point
    frame-relay interface-dlci 16
    interface Serial1/0.2 point-to-point
    frame-relay interface-dlci 17
    interface Serial1/0.3 point-to-point
    frame-relay interface-dlci 18
    Interface Serial1/1
    No ip address
    Encapsulation frame-relay
    Clock rate 64000
    frame-relay interface-dlci 20
    Interface Serial1/2
    No ip address
    Encapsulation frame-relay
    Clock rate 64000
    frame-relay interface-dlci 21
    Interface Serial1/3
    No ip address
    Encapsulation frame-relay
    Clock rate 64000
    frame-relay interface-dlci 22
    Here is my R2 config:
    interface Serial0/0
    ip address 10.1.1.2 255.255.255.0
    encapsulation frame-relay
    no fair-queue
    frame-relay interface-dlci 20
    Normally I would enter the frame-relay switch command?
    Frame-relay route 16 interface s1/1 20
    I want to use subinterrfaces and not multipoint.
    Why does this not work?? I cannot get connectivity from R1 to R2!

    John
    It is fine to use subinterfaces on R1 and R2 (in fact it is best practice to use point to point subinterface for Frame Relay). But I do not believe that you can do subintefaces on the router that is acting as the switch. I believe that the key elements of the router as frame relay switch include: frame-relay switching (which you have), Frame-relay intf-type dce (which you have), and Frame-relay route 16 interface s1/1 20 (which you need to add in place of the subinterfaces with DLCI identifier).
    HTH
    Rick

  • MPLS over ATM - VP Tunnel (cell) or VC (frame)?

    Does anybody use the MPLS over VP tunnel with the Cisco 8540 ATM MPLS core? Is it a stable solution or one should better leave the ATM MPLS cell mode and convert to frame mode over ATM?

    Both Cell mode and frame mode are stable solutions. But the scenario where we use them are different. I see that Cisco 8540 ATM MPLS Core is used. In this case, I would say that cell mode MPLS is a better solution for the following reason(s); In normal (non-MPLS) ATM core the L2 topology might be different from L3 topology. Say for example, a destination IP (a.b.c.d) might be shown as 3 hops (routers) away but there can be even 10 or more ATM switches in between. In this case the L2 topology might not be an optimal path. Hence we go for cell mode operation, where we form a full mesh topology and hence an optimal path.

  • "frame-relay fragment XYZ" causes link to stop working

    Hi people!
    I have a strange problem regarding the "frame-relay fragment xyz" command. I have the following configuration:
    interface Serial0/0
    description R3926704: phy. FrameRelay-Interface (Se0/0)
    bandwidth 512
    no ip address
    max-reserved-bandwidth 95
    encapsulation frame-relay IETF
    no ip mroute-cache
    load-interval 30
    no snmp trap link-status
    no fair-queue
    cdp enable
    frame-relay traffic-shaping
    frame-relay lmi-type q933a
    end
    interface Serial0/0.1 point-to-point
    description YYY: FR-Verbindung zum YY(Se0/0.1)
    bandwidth 512
    ip address A.A.A.A B.B.B.B
    frame-relay class egress_queue_512k
    frame-relay interface-dlci 16
    end
    map-class frame-relay egress_queue_512k
    frame-relay cir 486000
    frame-relay bc 48600
    frame-relay be 0
    frame-relay mincir 486000
    service-policy output egress_queue
    ... if i change the map-class to:
    map-class frame-relay egress_queue_512k_voice
    frame-relay cir 486000
    frame-relay bc 4860
    frame-relay be 0
    frame-relay mincir 486000
    service-policy output egress_queue
    frame-relay fragment 53
    ... no traffic goes over the link any more. no telnet no other traffic. the strange thing is, that i can ping the router!??
    does anyone know what's the problem here??
    thanks for any help!!
    Mario

    also, this fragment size must be set on both sides of the link, the same size, even if the hub has a greater link speed than the spoke.
    see this document for more info:
    http://www.cisco.com/en/US/partner/tech/tk652/tk698/technologies_configuration_example09186a0080094af9.shtml#topic9

  • "frame-relay fragment" causes link to stop working

    Hi people!
    I have a strange problem regarding the "frame-relay fragment xyz" command. I have the following configuration:
    interface Serial0/0
    description R3926704: phy. FrameRelay-Interface (Se0/0)
    bandwidth 512
    no ip address
    max-reserved-bandwidth 95
    encapsulation frame-relay IETF
    no ip mroute-cache
    load-interval 30
    no snmp trap link-status
    no fair-queue
    cdp enable
    frame-relay traffic-shaping
    frame-relay lmi-type q933a
    end
    interface Serial0/0.1 point-to-point
    description YYY: FR-Verbindung zum YY(Se0/0.1)
    bandwidth 512
    ip address A.A.A.A B.B.B.B
    frame-relay class egress_queue_512k
    frame-relay interface-dlci 16
    end
    map-class frame-relay egress_queue_512k
    frame-relay cir 486000
    frame-relay bc 48600
    frame-relay be 0
    frame-relay mincir 486000
    service-policy output egress_queue
    ... if i change the map-class to:
    map-class frame-relay egress_queue_512k_voice
    frame-relay cir 486000
    frame-relay bc 4860
    frame-relay be 0
    frame-relay mincir 486000
    service-policy output egress_queue
    frame-relay fragment 53
    ... no traffic goes over the link any more. no telnet no other traffic. the strange thing is, that i can ping the router!??
    does anyone know what's the problem here??
    thanks for any help!!
    Mario

    Mario,
    You need to base the fragment size on the lowest speed link between the 2 routers. If the lowest speed link is 512k, the recommended fragment size is 640 bytes.This is to achieve a 10ms serialization delay. The formula to compute this is Max Delay X Bandwidth. Please see Table 5 in the following link for recommended fragment sizes for 10ms serialization delay for different speed links.
    frame-relay fragment command
    http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/products_command_reference_chapter09186a008017cf52.html#wp1034268
    Hope this helps. If so, please rate the post.
    Brandon

  • Difrence between ... MPLS over Frame-Relay ATM

    Hai all,
    Sorry to ask very basic quiestion ..can some one tell what is the difrnce and advantage of MPLS over ATM and Frame-Relay ......pls provide me a better link ..for refrnce
    Thanks in advance
    Lijesh

    MPLS over ATM or MPLS over Frame-Relay it's not good idea, because if you use cell-mode labeling, you find someone limitation at this technology. DLCI and VPI/VCI value at this protocols it's not have large space. If you know how operate cell-mode, try to look at just for sample bits length with DLCI value at Frame-Relay protocol or VPI/VCI value at ATM protocol… Of course you can use same cheat like VCI-merge, but I think it's not very good idea.
    Building new network infrastructure at this protocols it's not good idea… It's good idea to fast implement MPLS technology in old network infrastructure build with this protocols (just for sample, you can linked ATM forwarding plane and MPLS forwarding plane (in this situation you can abandon to use fixed configuration VPI/VCI for IP network and can use benefits offered ATM technology with MPLS)), but not for new network infrastructure. If you need to offer services with this protocols, you can use Any Transport Over MPLS technology.
    For more information look at this page - http://www.cisco.com/en/US/tech/tk436/tk798/tsd_technology_support_protocol_home.html

  • 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

  • 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.

  • 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!

  • Viop over Frame Relay QOS

    I'm tryint to apply qos to our frame-relay links.
    Rferencing this document
    http://www.cisco.com/en/US/tech/tk652/tk698/technologies_configuration_example09186a0080094af9.shtml
    I'm using software vers. 123-14.T3
    The problem I am having is that when I apply frame-relay traffic-shaping to the frame-relay serial interface all my data and voice get corrupted(very choppy voice, intermittant pings, application timeouts etc.) My network essentially slows to a crawl.
    This occurs before I have applied the class to the dlci.
    I would assume no traffic shaping would take place until I apply a class to the frame relay dlci.
    Has anyone seen this or have any suggestions?

    Hello,
    The moment you apply the command "frame-relay traffic-shaping" under the frame-relay serial interface, all the sub-interfaces/DLCIs will default to 56kbps CIR, since you haven't applied the class under the DLCI yet.
    Best practice is to configure a default map-class with a higher CIR and apply that under the main interface before you configure frame-relay traffic-shaping. So, if there is no class defined under any sub-interface, the DLCI will inherit the traffic shaping parameters from the class defined under the main interface. If there is a class defined under the DLCI, the traffic shaping properties from that class will take affect for that DLCI.
    Hope that helps.
    Regards,
    Srikanth

  • Ipx over frame relay and route redistribution

    Hi,
    When I configure ipx over frame-relay multipoint interface, I need to run eigrp and disable the split horizon, and I'm running ipx rip on the same router thus, redistribution is automatic by default. This will cause potential routing loop when the route is advertised back from the same interface. In this situation, I have few questions:
    1. How to prevent routing loop in this situation?
    2. What is the administrative distance for ipx rip, eigrp, nslp?
    3. How does eigrp and rip convert the metric?
    Thank you
    Fujin

    Often times complex configuration issues are best addressed in an interactive session with one of our trained technical assistance engineers. While other forum users may be able to help, it’s often difficult to do so for this type of issue.
    To utilize the resources at our Technical Assistance Center, please visit http://www.cisco.com/tac and to open a case with one of our TAC engineers, visit http://www.cisco.com/tac/caseopen
    If anyone else in the forum has some advice, please reply to this thread.
    Thank you for posting.

  • Frame Relay Configuration

    All,
    Sorry for asking this, but I have been beating my head against the wall here. I am getting a T1 installed in my residence for internet connectivity. I am using an old wic-1-dsu-t1-v1 in a 2610 router. I am unable to get this configuration working. I have a very simple configuration so far on the router, but I am unable to get this to come up. I have put the show run below. Some of the commands are default and are not showing up. Obviously I have changed the ip's to generic ones below. Any ideas?
    version 12.1
    no service single-slot-reload-enable
    service timestamps debug uptime
    service timestamps log uptime
    no service password-encryption
    hostname JSS-2610-001
    memory-size iomem 10
    ip subnet-zero
    interface Ethernet0/0
     no ip address
     shutdown
    interface Serial0/0
     no ip address
     shutdown
    interface Serial0/1
     no ip address
     shutdown
    interface Serial0/2
     no ip address
     encapsulation frame-relay IETF
     frame-relay lmi-type ansi
    interface Serial0/2.21 point-to-point
     ip address 1.1.1.3 255.255.255.252
     frame-relay interface-dlci 16   
    ip classless
    ip route 0.0.0.0 0.0.0.0 1.1.1.2
    ip http server
    line con 0
     speed 115200
    line aux 0
    line vty 0 4

    Sorry when I transposed the ip's to post i made a mistake in them. 1.1.1.2 is my address and 1.1.1.1 is the gateway for them (their side of the t1). I have it configure correctly on my router with the real ip's.
    Here is the post to the rest of your questions:
    Serial0/2 is up, line protocol is up 
      Hardware is PQUICC with Fractional T1 CSU/DSU
      MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, 
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation FRAME-RELAY IETF, loopback not set
      Keepalive set (10 sec)
      LMI enq sent  16787, LMI stat recvd 16788, LMI upd recvd 0, DTE LMI up
      LMI enq recvd 0, LMI stat sent  0, LMI upd sent  0
      LMI DLCI 0  LMI type is ANSI Annex D  frame relay DTE
      FR SVC disabled, LAPF state down
      Broadcast queue 0/64, broadcasts sent/dropped 2812/0, interface broadcasts 15
      Last input 00:00:04, output 00:00:04, output hang never
      Last clearing of "show interface" counters 1d22h
      Input queue: 0/75/3/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: weighted fair
      Output queue: 0/1000/64/0 (size/max total/threshold/drops) 
         Conversations  0/1/256 (active/max active/max total)
         Reserved Conversations 0/0 (allocated/max allocated)
      5 minute input rate 0 bits/sec, 0 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         16791 packets input, 249054 bytes, 0 no buffer
         Received 0 broadcasts, 0 runts, 1 giants, 0 throttles
         3350 input errors, 1097 CRC, 1758 frame, 0 overrun, 0 ignored, 495 abort
         19638 packets output, 1080335 bytes, 0 underruns
         0 output errors, 0 collisions, 2 interface resets
         0 output buffer failures, 0 output buffers swapped out
         6 carrier transitions
         DCD=up  DSR=up  DTR=up  RTS=up  CTS=up
    JSS-2610-001#show frame-relay pvc 
    PVC Statistics for interface Serial0/2 (Frame Relay DTE)
                  Active     Inactive      Deleted       Static
      Local          1            0            0            0
      Switched       0            0            0            0
      Unused         0            0            0            0
    DLCI = 16, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/2.21
      input pkts 0             output pkts 2834         in bytes 0         
      out bytes 844139         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 2809       out bcast bytes 841611    
      pvc create time 1d22h, last time pvc status changed 15:31:28
    Is it possible the carrier just hasn't "activated" the circuit?

Maybe you are looking for