MPLS design recommendation

Hello all
i have 2 ASR 9000 acting as P routers connected to PEs in different remote locations.
access switch ------ PE router 1 ------DSW switch -------ASR 9k (P router)--------PE router in remote locations
both PE 1 and ASR 9k are in the same location
the DSW Switch is connected to AAA server and also terminates the microwave connection that acts as a redundant link
my question is :
what would be the impact if i remove the DSW Switch and terminate the microwave redundant connection on the ASR9k ?
where can i connect the AAA server then ?

If you want to completly eleminate the DSW switch from your network then,
HQ(AAA-----access Switch---PE Router-----ASR9k(P Router)---Other PE Router
If you challenge is only terminating the link between PE to P directly and you still can put the DSW then
HQ(Access Switch-----DSW------ Router(PE)-------ASR 9k P Router----Other PE Router
                                            |
                                            |
                                         AAA
Hope Answer to your question
BR
Thanveer
"Please Rate All Helpful Posts"

Similar Messages

Design Recommendations 1941 and 2921 still good?

Hi All, I've been asked to make some design recommendations. The 1941 and 2921 would be a good fit for this customer. Anybody know if there are plans for these routers to go EOL anytime soon?
Thanks in advance

I'm installing many 19/29xx series routers and haven't heard anything from my rep about EOL. Even if it goes EOL you still have support for many years after that and a solid piece of equipment.

Design Recommendation

I am looking for some design recommendation. Our application has set of n (lets assume 2) processes. The definition of each process is in a XML file. The XML file looks like:
<processes>
<process name ="a" action="b" />
<process name ='x' action="y" />
</processes>
Now we have several clients that have certain characteristics and run these processes in specific order. For example:
Client 1 name = "clean" order = a, x
Client 2 name = "fun" order = x, a
I am trying to figure out what will be a good, clean design to store this information. Should I create another XML with client list?

Thanks for your replies. The process is currently in
production. I recently joined the team and I am now
trying to clean up the design. In current
implementation every thing is hard coded and we have
tough time adding any new clients that use the
current set of processes. Our goal is to add new
clients with minimum turn around.OK, is the in memory design cleaned up?
My experience is that when the design approach comes from the input or output perspective, the resulting design tends to be rigid and sub-optimal. Once you have determined how you wish to represent the data in memory, then you can desing the input and output to be a natural extension of that design (you may want to change it subtlely.) You can even use built-in classes from the JDK to write and read your Objects to/from XML.

Best practice MPLS design/configuration for small service provider

We are a small regional service provider and did not have MPLS supported on our network. To start supporting MPLS, I’d like to get opinions and recommendations on the best practice configuration.
Here is what we have today –
We have our own BGP AS and multiple /24s.
We are running OSPF on the Cores and BGP on the Edge routers peering with ISPs.
We peer with multiple tier-1 ISPs for internet traffic. We do not provide public transit.
What we want for phase one MPLS implementation –
Configure basic MPLS /vpn functionality.
No QoS optimization required for phase 1.
We have Cisco ME 3600X for PE. Any recommendations will be appreciated.

Not sure what kind of devices or routers you have in your network but looks for if you have support for labeled multicast for MVPN support. That will avoid other complexity of using other control protocols (like PIM) in core.
PE redundancy can be obtained by BGP attributes, CE-PE connectivity can be tunned using IGP or VRRP/HSRP...
You can have mutiple RSVP TEs for various contract traffic and you can bind various kind of traffic to different RSVP Tunnels based on contract or service with your customer.
RSVP-TE with link/node protection design will be of great help to achieve quicker failover.

MPLS Design Best Practices for SP

When deploying a new MPLS backbone for a Service Provider, what will be consider the best practices in general? For example what about the following list and any other items:
- Define the Internet as a VRF?
- Use private ASNs?
- Define a VRF per special service?
- Use at least two route reflectors?
- Use OSPF as IGP?
- Limit the CE-PE routing support to OSPF and BGP?
What will be the best approach for management of the devices? A management VRF or the nodes to natively be on a management network?
What to consider when designing from scratch?

William some recommended practises, although you can point out your specific constraints in adopting any.
- Define the Internet as a VRF?
(Yes Logical speperation is the way to go.)
- Use private ASNs?
(No, use a Public AS, you may have to peer outside your AS in a VRF with other AS's)
- Define a VRF per special service?
(This is Perfect , Logical Seperation)
- Use at least two route reflectors?
(Right, atleast 2 and above that depends on the size of your network)
- Use OSPF as IGP?
(I dont see any problems with OSPF in scaling for big networks)
- Limit the CE-PE routing support to OSPF and BGP?
(This aspect shouldnt impact much really, you can very well support all the protocols, as its more of serving your customers, rather than dictating the conditions.
Yes have a seperate VRF for Device Managements (also give a thought for a management subnet, which would be unique across your network)
You should generally start with a overview topology, introdcution of the objectives. And then go ahead with the suggested phy topo,
And then move on to the logical services, beggining from Core IGP, then core BGP, and then all the add on protocols, multicast , MPLS TE etc/. Then you can cover specilized service and their logic and description in the end.
Pretty much, just simply think of building out right from scratch that is Physical Layer and Move to Layer 2 and then Layer 3 Layer 4 .
So basically you doc should be index in a manner following the sequence of the OSI layers, this gives a good flow to the doc. And rest remains is the description of the logic used in each service or deployment method, that would be your skill.
HTH-Cheers,
Swaroop

Wireless re-design recommendation

Hi, We have a wireless network setup and would like to expand it.
Currently we have wireless in the HQ only - 4402 controllers (2) and 1142 APs.
We have over 90 branches and would like to provide wireless to them as well. Some offices are large (20-30 users) and others are small (2-6 users). They connect to MPLS cloud with a low bandwidth connection (1.5 T1 to 5Mb ethernet connection)
Should the branches get autonomous APs instead of lightweight and create a VLANs for each SSID with ACLs before routing them to the rest of the network, or is it advisable to implement them as "light weight" and increase the license on my controllers (there aren't too many licenses left if I can recall correctly)? Is there a document that covers a scenario like mine? I am ready to look at a total revamp of the wireless infrastructure if that is what is needed.
Thank you very much experts.

I would NOT recommend to go with Autonomous AP deployment at Branch sites, it will give you lots of admin overhead to maintain that setup.
Instead you can use lightweight AP in FlexConnect mode which will give you good branch wireless design. Refer below Ciscolive material which will go through all the options available for good branch wireless design.
http://d2zmdbbm9feqrf.cloudfront.net/2013/usa/pdf/BRKEWN-2016.pdf
since you have 4402 WLC, I would recommend to do a whole revamp of your wireless infrastructure including wireless controller as well (probably with 5508).
PS: If you are looking more towards future, then you can consider next generation controllers like 3850/5760, but this involve most of hardware replacment in your switch network as well.
HTH
Rasika
**** Pls rate all useful responses ****

Adobe Flex & DESIGN Recommendations ?

Hi Folks,
While I am a bit beyond scratching the surface in Adobe Flex 4 & AS3 usage and knowledge, I am looking to spruce up the look and feel of my applications. So, I am looking at and getting confused by a never ending alpha soup of various Adobe products - such as Photoshop, Illustrator, InDesign, Catalyst, etc.
Where do I start and what do I actually need in order to be able to spruce up my Flex App with some custom looking components, UI controls and logos ?
What are you using and what would you recommend for a noobish person like my self?
Thanks again,
VC

When I got Flex 2 certified, I found this software to be
fairly useful. The Flex 3 exam version is not out yet, so you might
consider getting the version for Flex 2, as it still should be
useful:
Attest
I suggest going through these FB help topics and all
sub-topics TWICE, compiling all sample programs.
Flex Programming Elements
User Interfaces
Advanced Flex Programming
Data Access and Interconnectivity
Application Design
Application Development
Application Deployment
Custom Component Development
MXML Custom Components
ActionScript Custom Components
Nonvisual Custom Components
Flex Data Visualization Developer's Guide
Using Flex Builder 3
Developing AIR applications with Flex
Programming ActionScript 3.0

Layer 3 to the Access Layer and MPLS Design Considerations

Hi,
We are about to install a new network consisting of Cat 4500s with Sup7E at the Access Layer, with Nexus 7000 at the Distribution and Core layers.
We have 14 floors with at least three 4500s on each floor. Within the office block where the Access Layer and Distribution Layer reside we need to support secure borderless networking using 802.1x to place users from different parts of the business into segregated networks at layer 3.
All switches will have the feature sets to support MPLS/ VRF / OSPF / EIGRP / BGP etc.
We quickly dismissed the idea of using VRF-Lite due to the sheer number of Vlans we would need to managage and maintain, the point to point links alone just to get one additional VRF on each floor required far too many Vlans.
As a result we are now considering deploying MPLS. The obvious benefits include scalability and manageability, the fact that all switch to switch links can now be routed, instead of having to using SVIs.
My query is one of design surrounding MPLS and how this maps to an enterprise network with a routed access layer. Do Cat 4500s become the CEs and take part in MPLS / BGP and Label Distribution, or does the BGP peering and Label Distribution only occur between the Distrubtion - Core - Distrubtion layers, mapping to the PE - P - PE topology in an ISP environment, the access layer simply uses the IGP (OSPF in this case) to learn routes ?
Any help would be greatly appreciated.
Chris.

Hi Andy,
Thanks for your response.
I have been doing a little bit more research it seems the Cat 4500s do not support MPLS!! Nor do Cisco have any plans to support it on this platform. I find this a little rediculous considering the level that Cisco are pitching this platform. With the Sup 7E only VRF Lite is supported, with plans to support EVN (which still uses trunk links for logical separation).
So it looks like we are going to have to go back to the drawing board.
(perhaps we should have gone HP or Juniper!)
Chris.

LAN Design Recommendations?

Hello,
We have a 48 port 2960G switch distributing our LAN to numerous 24 port 2960G switches.
We have been talking about bringing in another 48 port 2960G switch for redundancy.
Can someone please let me know what the best design options are for this setup, in terms of redundancy and possibly even load balancing? I am interested to find out what Cisco technologies/features are recommended in this situation.
I created a quick drawing of what we currently have and what we are thinking about. None of these devices have been put into production yet. Let me know if you have any questions, thanks.

Ok, scratch all that. My project has been updated, to the point where my design needs to go back to the drawing board. I was told to implement 100% end-to-end redundancy (from the distribution switches to the servers).
We have nine racks of servers for this project. Each rack will get a primary access switch, and a secondary access switch. That is a total of 18 access switches. These switches will all have uplinks to two distribution switches. For the servers themselves, we will utilize NIC adapter teaming. The server network adapters will be configured in a primary/secondary relationship. I have an example drawing of how I think one rack would be laid out.
- The two distribution switches are 2960G, 48 ports (already purchased).
- The access switches are 2960G, 24 ports (already purchased).
- There will be a total of five vlans, but only two of them will carry around 90% of the traffic.
- The network will be strictly data. There is no voice traffic.
- There will be a ballpark of around 60 servers (no more than 10 servers on a rack). Almost half of these servers are only there as backups.
- There will be no end-user workstations off any of these switches. This is strictly a server farm.
- I do not have a strong feel of the overall traffic on this network, but I was told that it could pass a few terabytes per day (moderate-low load I suppose?).
I have a number of questions....
1. Can two 2960G switches effeciently handle the stress of connecting to 18 access switches each? There will also be other links on these distribution switches, such as connections to the internet and end-user access from our corporate network.
2. All five vlans will be propagated to all of our racks. I was hoping to balance the traffic by vlan. Make one distribution/access switch the primary link for one vlan - while making the other distribution/access switch the primary link for a different vlan. Is that feasible under my circumstances?
3. Etherchanneling the trunks (that is, having two or more links from a distribution switch to an access switch) would not be possible, because you can only configure six etherchannels per switch total. My distribution switches would have 18 different etherchannels (one channel for each access switch). Am I right in thinking this?
4. Will NIC adaptor teaming on each server effectively work in this scenario, or is there a better solution for redundancy? I read this can be done with Cisco's Link-State Tracking feature.
5. Are there any modification suggestions to my drawing, or is that the best end-to-end redundant method for my situation?
Feel free to ask questions. I look forward to some feedback, and appreciate the help.

MPLS Design

Looking at converting a smaller SP network to MPLS.
H/W is a 7206VXR w/NPE300
- 256MB DRAM
- 20480K bytes of Flash PCMCIA card at slot 0
- 125440K bytes of ATA PCMCIA card at slot 1
- 4096K bytes of Flash internal SIMM
Multiple ATM vc supporting
- ATM - to Frame (CE)
- ADSL
- ATM
- IDSL
Would run primarily static routes or OSPF/EIGRP as required.
7206 has approx 50 subinterfaces for various cstomers
Only selected customers would be migrated to MPLS VPN, others (e.g. those with a single office only) would be routed in a global table
Assume an initial count of 10-12 vrf instances
Ref http://www.cisco.com/en/US/tech/tk436/tk428/technologies_configuration_example09186a00801445fb.shtml#diag
1. Can I safely collapse the PE1/PE2/P onto a single platform (the 7206)?
2. IGW is replaced by PIX
3. Is the NPE300 adequate?
4. Any potential design issues?

1. Can I safely collapse the PE1/PE2/P onto a single platform (the 7206)?
Yes
3. Is the NPE300 adequate?
Yes
4. Any potential design issues?
only how much traffic you want to run i see NPE300 working fine with 100Mb traffic.
MPLS-Layer3 VPN do not have much load on resources

MPLS Book recommendation

Can someone recommend a good book to get me started on MPLS ?
Thanks

I am quoting Harold (hritter) in his answer some time ago:
======================
MPLS Books:
http://www.mplsrc.com/books.shtml
The MPLS Resource Center:
http://www.mplsrc.com/index.shtml
You can also refer to the basic RFC for MPLS:
http://www.ietf.org/rfc/rfc3031.txt
======================
Did it help?

Cisco best practice design recommendation for adding a subscriber?

Hello all,
We have UC Manager 7.1(3) running on a publisher and subscriber that is serving as the central voip to five (soon to be six) offices. At what point does cisco recommend an additional subscriber be added to a cluster for call processing and load balancing? I have been tearing through cisco's website and I am not finding this info. I am sure it is there, just buried!
Any feedback and links to the doc would be a huge help.
Thank you.
Rgds,
Vicky

Vicky,
The answer you are looking for depends on a few things. The most basic are:
1) What hardware are you running? This will determine the maximum number of phones that can be registered to any one server.
2) The answer to the first question comes into play as you total up how many phones you need to accommodate throughout the entire cluster. In addition, you want to provide adequate redundancy as well. Right now, you have a 1:1 model (Sub should be primary call processing agent but can failover to Publisher). As your cluster expands, you may need to consider a 2:1 model (2 active Subs, 1 backup) or continue with a 1:1 model.
3) If your cluster has 1000+ phones, you need to look into going with a Pub, 2 Subs, and a dedicated TFTP server.
Without getting too far into the weeds, take a look here first: http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/srnd/7x/c7ccmsrv.pdf
Then, if you have additional questions - please ask!
Hailey
Please rate helpful posts!

Exchange 2013 deployment design recommendations?

We are planning on upgrading from Exchange 2010 to 2013.
Currently, we have 2 Exchange servers. One server with mailbox and hub transport in our local office with users. The CAS is in a remote data center. So, whenever either server is down or being restarted, all mail stops.
We have received licenses for three Exchange 2013 servers. What is the best way to set these up so there is high availability whenever any one of the three servers is offline. Also, since we will still have the licenses for our existing two Exchange
2010 servers, will there be any benefit in keeping those in this scenario?
I have attached a diagram of our current layout and we want to revamp it.

Hi
The current setup of your environment is not Microsoft recommended solution as there is no HA set up for mailbox hub as well as CAS
My recommendation for exchange 2013
You can have CAS servers deployed one in each datacenter
Below thing can be thought for DAG Config
In order to increase the service level which is to have one site alive when the other site is down, its
better to Move the file share witness server to a server that does not belong to neither site but it needs to have reliable network communications between both sites.
So if any of two sites fails, the DAG will have a quorum and it can remain operational. The databases will
not be dismounted and service and data access will not be disrupted.
If in case if you don't have 3 sites you can follow below( again this is not best recommended HA )
Put the FSW in the primary Data Center and set the DAG to DAC mode so you can easily do a data center
switchover in case the primary fails.
http://technet.microsoft.com/en-us/library/dd351049(v=exchg.150).aspx
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Design Recommendations for Evolving Business Needs

Hi All,
Over time it is feasible that business needs will evolve. This could include changing the data that is captured within business processes as well as workflows, changing core shell information, to having to reorganize the initially designed shell hierarchy.
Wanted to find out from past experiences what guidelines/best practices/considerations there could be to prevent unintentionally designing shell hierarchy, shells and business processes that are either too inflexible for change or create major effort and rework in implementing it?
Look forward to hearing any thoughts around this.
Many Thanks
Lim

I meant no disrespect on the rating. I guess I really don't want to spend more than $300 - $400. I need to get a larger switch since I'm at capacity for my 8 port unmanaged switch, which was why I was looking at managed switches. Honestly, I'm really only wanting a managed (layer 3) switch so I can isolate the guest wireless with VLAN's and have POE for the 1142 AP. If I have to spend $1,000+ to do that I should probably rethink what I'm doing. I'm sure the 3560x and 2960XR are great switches and have a lot of capabilities, but if I'm only using a small fraction of their capabilities then it doesn't make cost sense to go that route. If there isn't any Cisco products in my price range with the features I'm looking for, feel free to tell me that. I'll just have to see what else is out there or like I mentioned, rethink the guest internet access.
Thanks
Josh

MPLS design question

Hi all,
what is the best solution to extend a node (PE router) over a third party IP network.
Here is the scenario - there is a need to extend an MPLS network to a new location, but due to commercial/policy reason the only available options are a third part IP Network (non-MPLS) and a back haul wireless link. We are thinking of making the IP Network the primary link and the wireless back haul the back up links.
Is L2TPv3 the only solution? I want to make use of the wireless back haul also for some traffic.
Regards,
san

Hi Aasheesh,
The service provider will only give me a L3 connectivity. In this case the LDP session will not establish with my PE on both ends.
I tries GRE on my PE with LDP enabled and it seems to take the command, but i have to try this between two PE. so I am not sure if I can bring the tunnel up and allow the two PEs to exchange LDP. I was just hoping that i could find a doc on it so that I can be sure that it will work. If you know if any doc that would be great.
reagrds,
san

MPLS design recommendation

Similar Messages

Maybe you are looking for