WRED om MPLS links

Hi
On MPLS based on 7500 routers, want to configure WRED on MPLS trunks. In each class I should configure the random-detect command, that can be based on IP Precedence or DSCP. My question is if the random detect shouldn´t be based on EXP bit value, like matches on class maps for MPLS links are based on EXP instead of Ip Prec or DSCP, because on DSCP links we see only the label. So, to configure WRED on MPLS trunks, does it look inside each IP packet, and it is it based on IP Prec or DSPC, or is there any way to configure WRED based on EXP value? What is the recomended configuration? Also, if possible, are there default values with lower-drop probabilities for higher priority classes?

You can use IPPrec to match exp, below configuration i have tested and its working on the MPLS network.
Class COS2
bandwidth remaining percent 53
random-detect precedence-based
random-detect precedence 3 10366 packets 16586 packets 1
random-detect precedence 4 12440 packets 18659 packets 1
Class COS3
bandwidth remaining percent 27
random-detect precedence-based
random-detect precedence 1 8293 packets 14513 packets 1
random-detect precedence 2 10366 packets 16586 packets 1

Similar Messages

Redundancy and Failover setup for 2 MPLS link with 2 different countries

Hi Sir/Madam,
We have 2 MPLS link and both links are active (from COUNTRY A to COUNTRY B) and we also have 2 partners who are located in COUNTRY B with same building but with different offices and each partner will be using each MPLS link. For example, PARTNER A will use the 1st MPLS link and PARTNER B will use the 2nd MPLS link and we want to have a failover setup (please see sample design below). What is the best solution for COUNTRY A and B to have a full redundancy and failover setup/network?
Any recommendation and sample configuration will be a big help for me. Your feedback is highly appreciated.
Thank you in advance.
Best regards,
Marvin

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
MPLS links, eh. You mean your MPLS facing ports have actual MPLS labels? Or do you mean your WAN links are running across a MPLS network, but the handoff isn't MPLS?
Country A's two routers are your company's devices? Do you have interior connectivity between them?
Country B's two routers - do they or can they have interior connectivity?
What routing protocols are being used (and where)?

VOIP configuration over mpls link

Hi
we want to deploy voip for multiple location over the mpls lines we have between the multiple location can any body suggest the feasibility and how to do it and any related document and guidance for that
Thanks
Manish gaur

Hi,
what do you call a "mpls link"? Do you have an IP interface connecting to a MPLS network implemented by a provider or do you operate a MPLS network yourself?
In any case you might have a look at
1) Enterprise QoS Solution Reference Network Design Guide Version 3.3
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns432/c649/ccmigration_09186a008049b062.pdf
2) Layer 3 MPLS VPN Enterprise Consumer Guide Version 2
http://www.cisco.com/application/pdf/en/us/guest/netsol/ns171/c649/ccmigration_09186a008077b19b.pdf
3) Various design guides for Unified communications
http://www.cisco.com/en/US/netsol/ns656/networking_solutions_design_guidances_list.html#anchor10
Hope this helps!
Regards, Martin

PBR on MPLS link

Hi ,
We have 2 MPLS Link with 100 Mbps of 2 service provider .
PBR Is configured on primary router .
PBR CONF
interface GigabitEthernet0/0.130
encapsulation dot1Q 130
ip address 10.10.10.1 255.255.255.240
ip policy route-map SANTTML
route-map SANTTML permit 10
match ip address SANTTML
set ip next-hop 10.136.22.6
ip access-list extended SANTTML
permit ip host 10.136.100.8 host 10.132.22.8
permit ip host 10.136.100.10 host 10.132.22.8
When we sending data from our server 10.136.100.10 to 10.132.22.8 traffic is out from second router,
but at receive only primary router.
Is there any MPLS routing issue
Please help .
Sanjay Nalawade.

Hi Sanjay
My viewpoint on your traffic flow requirements.
First let me put forward my understanding of your network setup.
You have taken MPLS VPN Services from 2 Different Service Providers and you want to achieve source-based routing between a pair of Source & Destination utilizing a particular ISP Uplink. Is that Correct.
If thats so, the PBR will only help to control the Forward Traffic and decide to choose which ISP Uplink to use depenind upon the Source.
For controlling the reverse traffic for the same pair of source-destination over that particular ISP you need to manipulate the route advertisement for that particular source making the Particular ISP as preferred and keeping the other ISP as backup for that particular source network.
Say for example if you are using BGP then doing an AS-Path Prepend for the Source Network you are doing PBR on the backup ISP will help achive you desired results for using a particlar ISP preferred for both Uplink and Downlink with respect to a particular destination.
Hope it Helps
Thanks & Regards
Vaibhava Varma

Port Channel over L2 MPLS links

Hello.
I was hoping that someone could over some suggestions on best practice or recommendations for configuring port channel to bundle to layer 2 MPLS links that we have.
We have racks in two geographically separated data centres, each rack has a stack of Cisco 3850 switches, and there are two 100Mbps layer 2 connections linking these stacks together. The links are provided by our supplier and runs over their core network (I can get more info on their setup if need be).
I had initially just configured a simple port channel bundling the two ports on "Switch A", and the same on "Switch B". However I have since noticed that one of the ports was put into error disabled state, and I have my doubts that we ever had 200Mbps throughput over the portchannel.
The logs showed:
UDLD-4-UDLD_PORT_DISABLED: UDLD disabled interface Gix/x/x, aggressive mode failure detected
%PM-4-ERR_DISABLE: udld error detected on Gix/x/x, putting Gix/x/x in err-disable state
How I understand is that one of ports recieved an unexpected (or incorrect) BPDU packet, and shut the port down as part of spanning tree process to stop a loop forming.
For the time being I have removed the port channel config and re-opened all the ports, so I believe one of the ports is now in blocking state.
Whilst redundancy for these links is great, ideally I would like to have the links bundled so I also get the benefit of higher throughput.
Any thoughts are greatly appreciated.
Thank you

Hi,
Thank you for your reply and suggestions. I have been reading up on layer 2 protocol tunnelling and I'm not sure if this will work for us. According to these guidelines for the catalyst 3550 (http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3550/software/release/12-1_19_ea1/configuration/guide/3550scg/swtunnel.html#wp1006657) it states:
•If you enable PAgP or LACP tunneling, we recommend that you also enable UDLD on the interface for faster link-failure detection.
•Tunneling is not supported on trunk ports. If you enter the l2protocol-tunnel interface configuration command on a trunk port, the command is accepted, but Layer 2 tunneling does not take affect unless you change the port to a tunnel port or an access port.
•EtherChannel port groups are compatible with tunnel ports when the 802.1Q configuration is consistent within an EtherChannel port group.
(maybe its a different and is supported on 3850's)
Also, I cant use layer 3 over this link as I am looking to extend VLANs over the link so devices and virtual machines in each of the datacentre are in the same subnet and broadcast domain.
I will speak with the supplier to see what they are willing to do.
Thanks again.

Voip deployment over mpls link

Hi
we want to deploy voip for multiple location over the mpls lines we have between the multiple location can any body suggest the feasibility and how to do it and any related document and guidance for that
Thanks
Manish gaur

Manish,
That is probably the best way to connect multiple sites without having to connect each one with a T1, etc. Our MPLS vendor has an SLA on latency with 50ms or less guaranteed. With voice you want to make sure the latency is definitely less than 150ms. For ease of management we're using a router at each remote site with SRST capabilities so that all of the configuration remains at the main HQ callmanager, but if the connection ever goes down, the remote site phones will still be able to call each other (not main office until connection is restored) Alternatively you can put a router at each site with CallManager Express, you will just have to manage each site separately. Hope that helps a little.

Wred based on MPLS exp bits on 12000

I want to use WRED with MQC on 12000 but there is no mpls/exp-bits statment on the "random-detect" command.
I found this note at cisco documentation:
Note: The legacy CLI also uses the precedence syntax for Multiprotocol Label Switching (MPLS) traffic. The router treats the MPLS bits as though they are IP Type of Service (ToS) bits and puts the appropriate packets into the correct queues. This is not at all true for MQC.
so, is there a way to use WRED with MPLS EXP-bits on MQC?

Hi,
As fas as I know the solution is as follows:
1. Use MQC on the inbound interface of your P/PE LSR to match your desired traffic and set discard-class
2. Use MQC on the outbound interface of your P/PE
LSR to set desired WRED policy based on discard-class you marked in previous step. You also need to mark WRED as "discard-class-based"
Here is an example:
Inbound:
class-map class1
match XXXXX
class-map class2
match YYYYY
policy-map in-policy
class class1
set discard-class 0
class class2
set discard-class 1
Outbound:
policy-map out-policy
class class-default
random-detect discard-class-based
random-detect discard-class 0 10 20 5
random-detect discard-class 1 20 30 5
Hope that helped.
David

DMVPN as Backup link to MPLS

Hi,
i want to implement DMVPN to one of our branch as a fail over link if the MPLS point to point is down.
The MPLS VPN is working fine but due to SP faults we are experiencing frequent link downs.so i want to place a dsl router at branch and configure DMVPN to our existing HUB router.
i am configuring branch router as a spoke to HUB router R3 with rip so when the MPLS which using eigrp goes down , then DMVPN link should be up depending upon AD but, my doubt is if again MPLS link gets up, will it switchover to MPLS from DMVPN.
here is the topology
Here is the configurations for HO,HUB and Branch Routers
******** HO ********
interface Tunnel102
description " Tunnel HO-Br3"
bandwidth 2048
ip address 10.10.0.10 255.255.255.252
tunnel source 172.33.1.18
tunnel destination 172.33.33.18
interface FastEthernet0/0
description "HO-LAN"
ip address 192.168.1.10 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
description " Connection MPLS SP"
ip address 172.33.1.18 255.255.255.252
duplex full
speed 100
router eigrp 200
redistribute ospf 10 metric 512 600 100 100 1500
network 10.10.0.8 0.0.0.3
no auto-summary
router ospf 10
log-adjacency-changes
redistribute eigrp 200 subnets
redistribute bgp 65350 subnets
network 192.168.12.0 0.0.0.255 area 0
router bgp 65350
no synchronization
bgp log-neighbor-changes
bgp redistribute-internal
network 10.10.10.0 mask 255.255.255.0
neighbor 172.31.3.17 remote-as 65400
no auto-summary
******** HUB *********
(Router R3 Config)
crypto isakmp policy 10
encr 3des
authentication pre-share
group 2
lifetime 3600
crypto isakmp key welc0me address 0.0.0.0 0.0.0.0
crypto ipsec transform-set strong esp-3des
crypto ipsec profile cisco
set security-association lifetime seconds 7200
set transform-set strong
interface Tunnel10
ip address 172.20.20.1 255.255.255.0
no ip redirects
ip mtu 1400
ip nhrp authentication welc0me
ip nhrp map multicast dynamic
ip nhrp network-id 250
ip tcp adjust-mss 1360
no ip split-horizon
delay 100
tunnel source GigabitEthernet0/1
tunnel mode gre multipoint
tunnel key 100
tunnel protection ipsec profile cisco
interface GigabitEthernet0/1
ip address 74.99.128.25 255.255.255.240
ip flow ingress
ip flow egress
duplex auto
speed auto
router rip
version 2
redistribute ospf 10 metric 5
network 172.20.0.0
no auto-summary
ip route 0.0.0.0 0.0.0.0 74.99.128.17
(Fail over DMVPN with RIP )
crypto isakmp policy 1
encr 3des
authentication pre-share
group 2
lifetime 3600
crypto isakmp key welc0me address 74.99.128.25
crypto ipsec transform-set strong esp-3des
crypto ipsec profile cisco
set security-association lifetime seconds 7200
set transform-set strong
interface Tunnel10
bandwidth 1024
ip address 172.20.20.2 255.255.255.0
no ip redirects
ip mtu 1400
ip nhrp authentication
ip nhrp map multicast 74.99.128.25
ip nhrp map 172.20.20.1 74.99.128.25
ip nhrp network-id 250
ip nhrp holdtime 300
ip nhrp nhs 172.20.20.1
ip nhrp registration no-unique
ip tcp adjust-mss 1360
no ip split-horizon
delay 1000
tunnel source FastEthernet4
tunnel destination 74.99.128.25
tunnel key 100
tunnel protection ipsec profile cisco
interface vlan 1
description " HWIC-DSL Link"
ip addresss dhcp
ip virtual-reassembly in
duplex auto
speed auto
router rip
version 2
network 172.20.0.0
network 192.168.50.0
no auto-summary
ip route 74.99.128.25 255.255.255.255 192.168.1.1
interface Tunnel102
description " Tunnel BR-HO "
bandwidth 2048
ip address 10.10.0.9 255.255.255.252
tunnel source 172.33.33.18
tunnel destination 172.33.1.18
interface FastEthernet0/0
description "BR LAN"
ip address 192.168.50.5 255.255.255.0
duplex auto
speed auto
interface FastEthernet0/1
bandwidth 2048
ip address 172.33.33.18 255.255.255.252
duplex auto
speed auto
router eigrp 200
network 10.10.0.8 0.0.0.3
network 192.168.50.0
no auto-summary
router bgp 65350
no synchronization
bgp log-neighbor-changes
neighbor 172.33.33.17 remote-as 65400
no auto-summary

Hi,
i am running eigrp over MPLS and i want the dmvpn as failover, so configured rip as it's AD is higher and it will be preferred only when the primary is down, but i want to make sure , it switches over to primary as soon as MPLS comes up.
if not DMVPN then canyou please suggest me anyother way to get over it...

Link Redundancy Mpls primary on ethernet & point to point secoundary leaseline on serial

hi i am having one link mpls with internet (primary) (e0/0)-10.1.1.1 and secound link point to point serial (s0/0) i want to do redundancy between two links
but problem is mpls link never shows down . so if mpls fails then my point to point should be up please Find Attach file.
can i get confuration according to my e.g. drawing
as per my knowledge ip sla track command is thier but i dont know exact command.

Hi,
You are right...You should use IP SLA to track the primary link (ISP side IP)....
Try these...
track 125 ip sla 10 reachability
delay down 15 up 10
ip sla 10
icmp-echo 4.2.2.2 (change this with the exact IP) source-interface Dialer1
threshold 40
If it doesn't work, just tewak some parameters..Some the methodilogy remain same..
Good Luck !!!!

Hotline is not working after migrating to MPLS

Hi,
I am facing one new problem, after migrating with MPLS link my customer not able to make calls. If he connecting to Leased Line then its working(OLD LINE). In data also we faced same problem, after removing the TCP Compression then only data also start to work. If any body aware of this type of problem can you please help me.
Regards,
Sunish

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

Does BT IP Clear MPLS support multicast?

Hi
Requirement is to multicast music on hold RTP stream from a Data Center to a remote site over BT IP Clear MPLS network. Catalyst 3750 switches (both running IP Services Image) will BGP peer with BT PE equipment. The Catalyst 3750 switches will also be configured with PIM-SM.
Does BT MPLS support IP Multicast? I could not find any info on the web so I am hoping people have tried it and (hopefully) it worked for them!
Are there any restictictions/limitations using Catalyst 3750 for BGP peering?
Thanks

sidhu
If you are looking for multicast support on mpls link then you need to ask your SP to provide you the mVPN services. Because they need to configure the default and data mdt under the vrf.
regards
shivlu jain

Help in strategy for Migrating to MPLS from PRN cloud Same provider

Dear,
We are planning to migrate to MPLS from PRN using same provider, I have about 12 sites to migrate, new circuits have been provisioned and new routers are ready to be shipped to each site for installation.
Now, I am facing a dilemma, briefly speaking with provider they tell me that we can migrate a site a time no problem here, then next day they tell me it needs to be a hot cut over migration how can this be? so going back and forth and tayloring routers configurations I literally stopped, would like ask for assistance and your opinion on how to go about such migration to tentatively lock into a solid strategy.
Any documents out there you can point me to or experience in such migration will be appreciated.
All of our sites currently connect to PRN cloud including HQ, running OSPF multiple areas, at a glance I was thinking the provider would somehow bridge the two clouds so that I could build a parallel infrastructure and migrate branch offices one at a time but I am still unclear on how to proceed, I will be speaking with the provider more extensively in the next few days but any guidance will be appreciated.
Best Regards

Henry, thanks for those links and help.
Would like to share what I have done which seems so far to be working properly, so that if any one comes accross they get an idea.
It turned out our RPN/MPLS provider cannot or don't want to somehow cross connect the two clouds, so I was forced to do the cross connect at my end begining with two sites, I have setup what I had in mind, for each of the two targeted sites I have installed a new 3845 router with new DS3 link to MPLS cloud and created a cross connect to a 6509_switch_router that is connected under the PRN infrastructure. The 3845 was configured as a virtual link for ospf, all good here so far the 3845 joing ospf domain and received routing table from from PRN side. The next site had also new router and new circuit for the MPLS side, at this second site I brough down the router connecting to PRN cloud then brought up the new 2811 router which I had preconfigured under the same ospf domain and received routing table from the 3845 router DS3 MPLS link. We will let it run for a week to allow to troubleshoot or spod any issues before proceeding to migrate more sites.
Rgds
Jorge

OSPF design for branch offices across MPLS

Hello fellow networking engineers,
I want to implement OSPF in our network. We have multiple branch offices, all linked to an MPLS backbone.
I know that in order to get linked areas, I would need to setup GRE tunnels between them, but I want to avoid static/manual configurations as much as possible. With multiple sites, it would become cumbersome to create a mesh real fast.
Is running OSPF independent areas at each site, and simply redistributing over eBGP a valid solution? This will host voice and data, and will failover to VPN connection (Cisco ASAs) if the MPLS goes down.
For the VPN backup links, I thought of two options. Either simply using the default route to send everything to the ASA in case of MPLS "death", or inject routes using IP SLA...
Any input would be appreciated.

Marc
You don't GRE tunnels to link your areas if that is what you want to do.
If the SP supports it then you can exchange your OSPF routes between areas and they will still be seen as inter area routes rather than OSPF externals which they would if you simply treated each area as isolated from each other.
In effect the MPLS network becomes an OSPF super backbone area and your main site would also be part of the backbone area with all your other sites having an area each.
You still redistribute your OSPF routes into BGP but with some extra configuration on both your CEs and the SP PE devices.
Like I say you would need to check with your SP but it is possible.
Whether or not you need or want it I don't know.
Your other option is as you have proposed to treat each OSPF area as an isolated one and simply redistribute into OSPF at each CE. Then within each site all non local routes would be seen as OSPF external routes.
Either way in terms of backup I would keep it simple and use a default route at each site pointing to the ASA device. I can't see what you gain from IP SLA because if the main MPLS link goes down at any site the only other path they have out is via the ASA so there is nothing really worth tracking.
The only other thing I would mention is remote site to remote site traffic. If there is any then presumably with your VPN tunnels you would be doing a sort of hub and spoke where the hub is the main site so you may need to think about traffic coming in from one VPN tunnel and going out to another VPN tunnel on the main site ASA.
This would only really be needed if two or more sites had to use their backup links at the same time.
In terms of which is better ie. OSPF inter area across the MPLS cloud or OSPF externals I can't really say to be honest. With the MPLS networks i have worked on we ran EIGRP and simply treated each remote site as an isolated AS.
If you are already running OSPF then you may want to preserve your existing areas so it would make sense to go with the inter area option.
If it is a new setup then I don't really know the pros and cons of either so can't really comment.
Perhaps others may add to the thread with their thoughts.
Jon

Forest Trust RPC timeout across MPLS

Hi, I am having trouble setting up a Forest trust between two networks. The issue "seems" to be RPC timeout (i see RPC age-out on firewall) but i'm now wondering if it's actually the LDAP or KErberos thats failing first.
I have read that RPC needs to have the same path outgoing as incoming otherwise you can get SYN-ACK problems (especially through a firewall). So i need to try and work out why it doesnt work. It is laid out something like this.
Network 1 (domain BOB) (server 2008 R2 at domain functional level 2003)
Site1,Site2 and Site3 all connect to each other via Site-To-Site link provided by 3rd party. They all egress at Site1's ISA Firewall in a normal 3 leg perimeter config. All works fine
Network 2 (domain RITA) (server 2008 R2 at domain functional level 2003)
SiteA,B,C and D all connecto to each other over 3rd party MPLS (essentially Gig ethernet)
Site1 and SiteA are on the same premises in the same room. There is a spare NIC on the ISA server. So i configured the ISA with a NIC in the same subnet as SiteA (RITA domain) - ie i plugged RITA into BOB. I configured the ISA for routing. Allow ANY ANY
internal to RITA and ANY ANY RITA to internal
I set up conditional forwarders on both domains pointing at each other and can ping everything from the other sites. DNS is working fine. I can RDP across sites to each other's DCs. From a "network" point of view it all looks good (though in the
back of my mind i cant rule out the site to site or the MPLS links)
When i try and create the trust it fails very quickly with "Cannot Continue. The trust relationship cannot be created because the following error occurred: The operation failed. The error is: The remote procedure call failed"
I can do a portqry and see all RPC comms looks good
In ISA and another firewall i tried i can see the RPC ageing out. Have tried wireshark but hard to see whats going on
I used another server in the BOB domain and dcpromo'd it to a new domain in that subnet and tried setting up a trust. worked first time
Similarly i did the same at the RITA side and that worked too.
THere are no errors in DNS or the event logs on either side to suggest anything is failing. i tried verbose DNS logs but couldnt really follow them.
Help!! Thanks

Hi,
To verify if this is a network issue, please try to perform a network capture on the servers in both side.
We can use "IPv4.Address==xxx.xxx.xxx.xxx" to filter the traffic between the servers. Then compare the capture data from the servers. If all the packets have been forwarded, it should not be caused by network.
To download Network Monitor, please click the link below:
http://www.microsoft.com/en-hk/download/details.aspx?id=4865
About the question related to Directory Services, to get better help, please post your questions on the DS forum.
Here is the address:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverDS
Best Regards.
Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

L3 Link for Storage Replication

Hi,
Has anyone experienced on provisioning L3 MPLS link for Storage Replication. I have two DC at different location and EMC Storage.
we will have 2 MPLS L3 Link between two DCs to replicate the data. We have 4 RPA at each side and 2 MPLS Link. but dont have idea how to connect all these things. I have Nexus 7k in new DC and 6509 in old DC.
If anyone has any idea how to provisioned this link, it would great help to me.

Hi Micky,
Such table doesn´t exist in standard SAP! You should try to accomplish this in a view!

WRED om MPLS links

Similar Messages

Maybe you are looking for