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,

Similar Messages

Circuit 1/e1, what is this ? is it frame-relay or mpls or other ? help me?

I read in one of Job descritpion "Experience of working on circuit(T1/E1,T3/E3,Ethernet) troubleshooting would be preferred".
Could u please help me this circuit t1/e1,etc. Is it covered in ccnap or ccnp rs ?
Is it frame-relay or mpls or other ?
Could you please explain or suggest me the book/blog/doc/etc.

Please refer this:
http://www.ad-net.com.tw/index.php?id=500

Cell-relay over MPLS using MGX 8850

we have existing ATM network using TDM links between MGX 8850 & have PVCs for voice & data traffic. We are planning to migrate the same over MPLS network
following is the setup.
MGX1----> PE1 ------>MPLS Cloud ------> PE2 ---->MGX2
As per this plan we will terminate existing TDM trunks to PE routers at both the end & map VPI/VCI values at PE routers for virtual ATM pvcs over MPLS cloud.We are using cell-relay over MPLS with VC mode. My query is, can we enable MPLS L3 & L2 on the same last mile in this scenario? We want to have one IP over ATM interface on same ATM interface at PE router & make that part of VRF & enable L3 MPLS VPN between all the sites for any to any data transfer. For data we don't want to use L2 MPLS as its any to any & it will end up with too many ATM PVCs.
In this setup PE router & MGX will be configured in NNI-NNI at both end. If we want to create one sub-interface at same ATM interface at PE router end, then that port need to be in UNI. Is it possible to use same ATM trunk port as NNI & UNI?
In MGX 8850 we have RPM,AXSM & VISM modules.

the following document should give you some idea,
http://www.cisco.com/en/US/products/hw/modules/ps2797/products_module_installation_guide_chapter09186a0080086f9a.html

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

Frame Relay vs MPLS

Why does the Cisco CCNA certification cover Frame Relay if MPLS is the more used WAN technology?

CCNA is more like a foundation building certification. So it tends to cover a whole array of topics, but all at the basic level, just enough to give food for thought, and a fair level of understanding how each technology works. To cover MPLS would not have been appropriate in CCNA as MPLS needs the foundation as well as the routing level professional knowledge already in place..
But again with one level below CCNA certification, this may change probably, and they may cover light basics of MPLS. So that you can actually study the operations in professional and expert level certifications. Just a thought.
HTH-Cheers,
Swaroop

Frame Relay and MPLS

Hi,
I want to ask about the frame relay and MPLS.
Frame Relay Scenerio
The frames reached at the frame relay network and forwarded on the basis of DLCI. All the VCs are defined prior to the traffic on the network on the basis of DLCI (This is just like the MPLS network as packets are forwarded on the basis of Labels).
Now my Question is How can MPLS is used in frame relay network or what are its affects in the presence of DLCI (As DLCIs are also performing the same task and also works on layer 2) or these two are different equivalent technologies ?

Hi Muhammad,
The answer is : MPLS is working on FR like it's working on ethernet. Because the FR and Ethernet are running on Layer2. It's told that MPLS is working at layer 2.5 , meaning that is between Layer 3 , and Layer 2. So in order to work it needs a layer2 forwarding in your case FR's DLCI. On top of the Layer 2 it is the MPLS header.
Dan

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

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

MPLS Verses Frame Relay

I am looking for any comparison document between Frame Relay and MPLS
Can anyone help me to find such a document ?
Thanks
Kind Regards
Mohamed Abdallah

If you are looking for a security comparison there is a draft document from Michael Behringer at : http://www.ietf.org/internet-drafts/draft-behringer-mpls-security-00.txt
Hope this helps.
-Ives-

Simplest way to POC IPT over MPLS IPVPN Link

Were helping one of our subsidiary to migrate from the frame-relay to MPLS-IPVPN, the integration part for network is almost done. But since the bandwidth allocated is quite substantial, they came out the idea of VOIP using the same IP-VPN link.
Since the CE equipment is fairly simple, a 2611XM. What other things Ill required in order to POC that the VOIP can use the current IP-VPN link as well? Now the subsidiary (HQ nor branches) has nothing related to VOIP. Whats the cheapest way to POC the VOIP thing? We just need to show them the call can be made over the IP-VPN link. Nothing more nothing less.
List of Equipments (In my mind)
i. Few IP phones (depends of the POC sites)
ii. Switches (for IP phone connection and Voice Gateway Connection)
iii. A VOIP server located at HQ (can the router act as a VOIP server as well)?

So can i save to say that here's the list of equipment i'll ever need for the demo.
Headquarter
i. 2811 with Voice IOS (act as the CE router and the Express Server)
ii. 2950 for the IP Phone connection
Branches
i. 2811 with Voice IOS (act as the CE router and voice gateway)
ii. 2950 for the IP Phone connection
Is that all?

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

Ask the Expert:Concepts, Configuration and Troubleshooting Layer 2 MPLS VPN – Any Transport over MPLS (AToM)

With Vignesh R. P.
Welcome to the Cisco Support Community Ask the Expert conversation.This is an opportunity to learn and ask questions about concept, configuration and troubleshooting Layer 2 MPLS VPN - Any Transport over MPLS (AToM) with Vignesh R. P.
Cisco Any Transport over MPLS (AToM) is a solution for transporting Layer 2 packets over an MPLS backbone. It enables Service Providers to supply connectivity between customer sites with existing data link layer (Layer 2) networks via a single, integrated, packet-based network infrastructure: a Cisco MPLS network. Instead of using separate networks with network management environments, service providers can deliver Layer 2 connections over an MPLS backbone. AToM provides a common framework to encapsulate and transport supported Layer 2 traffic types over an MPLS network core.
Vignesh R. P. is a customer support engineer in the Cisco High Touch Technical Support center in Bangalore, India, supporting Cisco's major service provider customers in routing and MPLS technologies. His areas of expertise include routing, switching, and MPLS. Previously at Cisco he worked as a network consulting engineer for enterprise customers. He has been in the networking industry for 8 years and holds CCIE certification in the Routing & Switching and Service Provider tracks.
Remember to use the rating system to let Vignesh know if you have received an adequate response.
Vignesh might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Service Provider sub-community discussion forum shortly after the event. This event lasts through through September 21, 2012. Visit this forum often to view responses to your questions and the questions of other community members.

Hi Tenaro,
AToM stands for Any Transport over MPLS and it is Cisco's terminology used for Layer 2 MPLS VPN or Virtual Private Wire Service. It is basically a Layer 2 Point-to-Point Service. AToM basically supports various Layer 2 protocols like Ethernet, HDLC, PPP, ATM and Frame Relay.
The customer routers interconnect with the service provider routers at Layer 2. AToM eliminates the need for the legacy network from the service provider carrying these kinds of traffic and integrates this service into the MPLS network that already transports the MPLS VPN traffic.
AToM is an open standards-based architecture that uses the label switching architecture of MPLS and can be integrated into any network that is running MPLS. The advantage to the customer is that they do not need to change anything. Their routers that are connecting to the service provider routers can still use the same Layer 2 encapsulation type as before and do not need to run an IP routing protocol to the provider edge routers as in the MPLS VPN solution.
The service provider does not need to change anything on the provider (P) routers in the core of the MPLS network. The intelligence to support AToM sits entirely on the PE routers. The core label switching routers (LSRs) only switch labeled packets, whereas the edge LSRs impose and dispose of labels on the Layer 2 frames.
Whereas pseudowire is a connection between the PE routers and emulates a wire that is carrying Layer 2 frames. Pseudowires use tunneling. The Layer 2 frames are encapsulated into a labeled (MPLS) packet. The result is that the specific Layer 2 service—its operation and characteristics—is emulated across a Packet Switched Network.
Another technology that more or less achieves the result of AToM is L2TPV3. In the case of L2TPV3 Layer 2 frames are encapsulated into an IP packet instead of a labelled MPLS packet.
Hope the above explanation helps you. Kindly revert incase of further clarification required.
Thanks & Regards,
Vignesh R P

No modem conection with voip over frame-relay

I'm trying to connect two modems through voip over frame-relay network using the modem passthrough command but that is no working. The voice calls is operating very well but the modems no connect between them. I'm using G-729 codec with ip header compression and data fragment in 80 bytes.

There are some know issues with cisco dsps and V.90+ modems, but we have been able to get most modems to work correctly accross our network. If you are using g729 for all other voice calls you will want to use the modem passthrough command to have both gw's turn to modem passthrough. I typically set up each dial peer with the specific commands, since I have found the global commands are not consistently applied. Here is a sample dial peer config....
dial-peer voice 3 voip
description Default voip peer
preference 1
incoming called-number .T
destination-pattern .T
progress_ind setup enable 3
progress_ind connect enable 8
modem passthrough nse codec g711ulaw
voice-class codec 1
session protocol sipv2
session target sip-server
dtmf-relay rtp-nte
fax rate disable
fax protocol pass-through g711ulaw
ip qos dscp cs3 signaling
no vad
Some of these commands are specific to the isdn signaling set up we have at this site. Also, we are using sip hence the sip session target. But the modem and fax passthrough commands are pretty much universal.
Also, some of those commands are not supported until 12.2.13. You might want to think about an ios upgrade.

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!

AToM Frame Relay over MPLS

Similar Messages

Maybe you are looking for