Data Center Network Design

I'm looking at a couple options for a small network in a data center. I seem to be getting hung up on all the different options. One of the options I'm looking at is end or row using both 2960Ss and Blade Center chassis switches with each physical server dual homed into a 2960, each ESX server dual homed into a blade switch and each of the switches with a Layer 2 10Gb uplink (20 total with etherchannel) to one of two 4900Ms. The 4900Ms would then have a layer 2 uplink between them to accomodate VLANs that span the access layer switches. This would be an inverted U topology. That's simple enough, and maybe that is where I should leave it, but there is the now available stacking feature of 2960s that has me wondering if there is another option available with dual homing a stack. Is there such a beast? Would it be better to stack 2960s, or even 3750s, so as to make each end of row with 2 redundant switches appear as one logical stack, and then uplink that stack to an aggregate multilayer switch such as a pair of 4900Ms? Or might that limit me to keeping VLANs within a stack and end or row?
thank you,
Bill

Hi Bill-
First, I personally would not use the 2960S for the data center, no matter the size. That switch was purposely built for user access and has some limitations. Also, depending on what you need to accomplish will determine your design. I recently did a design similar to what you are describing. We ended up putting 3750X's at the top of rack as a stack. This allows for etherchannel to your servers with both server NICs being active. From there we uplinked to a pair of 6509's in VSS. From a layer 2 point of view this was about as simple as it gets; 1 switch connected to another switch connected to a server. No spanning tree! If you can't afford stackable switches, you may want to look at routing at the top of rack. However you will lose functionality like moving VLAN's between racks, relying on server NIC software for active/passive links and the moving of VM's could be limited.

Similar Messages

Deploying Cisco Overlay Transport Virtualization (OTV) in Data Center Networks

Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to plan, design, and implement Cisco Overlay Transport Virtualization (OTV) in your Data Center Network with Cisco experts Anees Mohamed Abdulla and Pranav Doshi.
Anees Mohamed Abdulla is a network consulting engineer for Cisco Advanced Services, where he has been delivering plan, design, and implementation services for enterprise-class data center networks with leading technologies such as vPC, FabricPath, and OTV. He has 10 years of experience in the enterprise data center networking area and has carried various roles within Cisco such as LAN switching content engineer and LAN switching TAC engineer. He holds a bachelor's degree in electronics and communications and has a CCIE certification 18764 in routing and switching.
Pranav Doshi is a network consulting engineer for Cisco Advanced Services, where he has been delivering plan, design, and implementation services for enterprise-class data center networks with leading technologies such as vPC, FabricPath, and OTV. Pranav has experience in the enterprise data center networking area and has carried various roles within Cisco such as LAN switching TAC engineer and now network consulting engineer. He holds a bachelor's degree in electronics and communications and a master's degree in electrical engineering from the University of Southern California.
Remember to use the rating system to let Anees and Pranav know if you have received an adequate response.
Because of the volume expected during this event, Anees and Pranav might not be able to answer each question. Remember that you can continue the conversation on the Data Center, sub-community forum shortly after the event. This event lasts through August 23, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Dennis,
    All those Layer 2 extension technologies require STP to be extended between Data Centers if you need to have multiple paths between Data Centers. OTV does not extend STP rather it has its own mechanism (AED election) to avoid loop when multiple paths are enabled. It means any STP control plane issue, we don't carry to the other Data Center.
    OTV natively suppresses Unknown Unicast Flooding across the OTV overlay. Unknown unicast flooding is a painful problem in layer 2 network and difficult to troubleshoot to identify the root cause if you don't have proper network monitoring tool.
   It has ARP optimization which eliminates flooding ARP packets across Data Center by responding locally with cached ARP messages. One of the common issues I have seen in Data Center is some server or device in the network sends continuous ARP packets which hits Control plane in the Aggregation layer which in turn causes network connectivity issue.
The above three points proves the Layer 2 domain isolation between data centers. If you have redundant Data Centers with Layer 2 extended without OTV, the above explained layer 2 issue which happens in one Data Center carries the same failure to the second data center which creates the question of what is the point of having two different Data Centers if we can not isolate the failure domain.
OTV natively supports HSRP localization with few command lines. This is a very important requirement in building Active/Active Data Center.
Even though your question is related to L2TP, OTV deserves the comparison with VPLS and those comparison will also be applicable for L2TP. The below link explains in detail...
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9402/white_paper_c11-574984.html
Thanks,
Anees.

Ask the Expert: Scaling Data Center Networks with Cisco FabricPath

With Hatim Badr and Iqbal Syed
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about the Cisco FabricPath with Cisco technical support experts Hatim Badr and Iqbal Syed. Cisco FabricPath is a Cisco NX-OS Software innovation combining the plug-and-play simplicity of Ethernet with the reliability and scalability of Layer 3 routing. Cisco FabricPath uses many of the best characteristics of traditional Layer 2 and Layer 3 technologies, combining them into a new control-plane and data-plane implementation that combines the immediately operational "plug-and-play" deployment model of a bridged spanning-tree environment with the stability, re-convergence characteristics, and ability to use multiple parallel paths typical of a Layer 3 routed environment. The result is a scalable, flexible, and highly available Ethernet fabric suitable for even the most demanding data center environments. Using FabricPath, you can build highly scalable Layer 2 multipath networks without the Spanning Tree Protocol. Such networks are particularly suitable for large virtualization deployments, private clouds, and high-performance computing (HPC) environments.
This event will focus on technical support questions related to the benefits of Cisco FabricPath over STP or VPC based architectures, design options with FabricPath, migration to FabricPath from STP/VPC based networks and FabricPath design and implementation best practices.
Hatim Badr is a Solutions Architect for Cisco Advanced Services in Toronto, where he supports Cisco customers across Canada as a specialist in Data Center architecture, design, and optimization projects. He has more than 12 years of experience in the networking industry. He holds CCIE (#14847) in Routing & Switching, CCDP and Cisco Data Center certifications.
Iqbal Syed is a Technical Marketing Engineer for the Cisco Nexus 7000 Series of switches. He is responsible for product road-mapping and marketing the Nexus 7000 line of products with a focus on L2 technologies such as VPC & Cisco FabricPath and also helps customers with DC design and training. He also focuses on SP customers worldwide and helps promote N7K business within different SP segments. Syed has been with Cisco for more than 10 years, which includes experience in Cisco Advanced Services and the Cisco Technical Assistance Center. His experience ranges from reactive technical support to proactive engineering, design, and optimization. He holds CCIE (#24192) in Routing & Switching, CCDP, Cisco Data Center, and TOGAF (v9) certifications.
Remember to use the rating system to let Hatim and Iqbal know if you have received an adequate response.
They 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 Data Center sub-community Unified Computing discussion forum shortly after the event. This event lasts through Dec 7, 2012.. Visit this support forum often to view responses to your questions and the questions of other Cisco Support Community members.

Hi Sarah,
Thank you for your question.
Spanning Tree Protocol is used to build a loop-free topology. Although Spanning Tree Protocol serves a critical function in these Layer 2 networks, it is also frequently the cause of a variety of problems, both operational and architectural.
One important aspect of Spanning Tree Protocol behavior is its inability to use parallel forwarding paths. Spanning Tree Protocol forms a forwarding tree, rooted at a single device, along which all data-plane traffic must flow. The addition of parallel paths serves as a redundancy mechanism, but adding more than one such path has little benefit because Spanning Tree Protocol blocks any additional paths
In addition, rooting the forwarding path at a single device results in suboptimal forwarding paths, as shown below, Although a direct connection may exist, it cannot be used because only one active forwarding path is allowed.
Virtual PortChannel (vPC) technology partially mitigates the limitations of Spanning Tree Protocol. vPC allows a single Ethernet device to connect simultaneously to two discrete Cisco Nexus switches while treating these parallel connections as a single logical PortChannel interface. The result is active-active forwarding paths and the removal of Spanning Tree Protocol blocked links, delivering an effective way to use two parallel paths in the typical Layer 2 topologies used with Spanning Tree Protocol.
vPC provides several benefits over a standard Spanning Tree Protocol such as elimination of blocker ports and both vPC switches can behave as active default gateway for first-hop redundancy protocols such as Hot Standby Router Protocol (HSRP): that is, traffic can be routed by either vPC peer switch.
At the same time, however, many of the overall design constraints of a Spanning Tree Protocol network remain even when you deploy vPC such as
1.     Although vPC provides active-active forwarding, only two active parallel paths are possible.
2.     vPC offers no means by which VLANs can be extended, a critical limitation of traditional Spanning Tree Protocol designs.
With Cisco FabricPath, you can create a flexible Ethernet fabric that eliminates many of the constraints of Spanning Tree Protocol. At the control plane, Cisco FabricPath uses a Shortest-Path First (SPF) routing protocol to determine reachability and selects the best path or paths to any given destination in the Cisco FabricPath domain. In addition, the Cisco FabricPath data plane introduces capabilities that help ensure that the network remains stable, and it provides scalable, hardware-based learning and forwarding capabilities not bound by software or CPU capacity.
Benefits of deploying an Ethernet fabric based on Cisco FabricPath include:
• Simplicity, reducing operating expenses
– Cisco FabricPath is extremely simple to configure. In fact, the only necessary configuration consists of distinguishing the core ports, which link the switches, from the edge ports, where end devices are attached. There is no need to tune any parameter to get an optimal configuration, and switch addresses are assigned automatically.
– A single control protocol is used for unicast forwarding, multicast forwarding, and VLAN pruning. The Cisco FabricPath solution requires less combined configuration than an equivalent Spanning Tree Protocol-based network, further reducing the overall management cost.
– A device that does not support Cisco FabricPath can be attached redundantly to two separate Cisco FabricPath bridges with enhanced virtual PortChannel (vPC+) technology, providing an easy migration path. Just like vPC, vPC+ relies on PortChannel technology to provide multipathing and redundancy without resorting to Spanning Tree Protocol.
Scalability based on proven technology
– Cisco FabricPath uses a control protocol built on top of the powerful Intermediate System-to-Intermediate System (IS-IS) routing protocol, an industry standard that provides fast convergence and that has been proven to scale up to the largest service provider environments. Nevertheless, no specific knowledge of IS-IS is required in order to operate a Cisco FabricPath network.
– Loop prevention and mitigation is available in the data plane, helping ensure safe forwarding that cannot be matched by any transparent bridging technology. The Cisco FabricPath frames include a time-to-live (TTL) field similar to the one used in IP, and a Reverse Path Forwarding (RPF) check is also applied.
• Efficiency and high performance
– Because equal-cost multipath (ECMP) can be used the data plane, the network can use all the links available between any two devices. The first-generation hardware supporting Cisco FabricPath can perform 16-way ECMP, which, when combined with 16-port 10-Gbps port channels, represents a potential bandwidth of 2.56 terabits per second (Tbps) between switches.
– Frames are forwarded along the shortest path to their destination, reducing the latency of the exchanges between end stations compared to a spanning tree-based solution.
    – MAC addresses are learned selectively at the edge, allowing to scale the network beyond the limits of the MAC addr

Welcome to the Enterprise Data Center Networking Discussion

Welcome to the Cisco Networking Professionals Connection Network Infrastructure Forum. This conversation will provide you the opportunity to discuss general issues surrounding Enterprise Data Center Networking. We encourage everyone to share their knowledge and start conversations on issues such as Mainframe connectivity, SNA Switching Services, DLSw+, managing SNA/IP and any other topic concerning Enterprise Data Center Networking.
Remember, just like in the workplace, be courteous to your fellow forum participants. Please refrain from using disparaging or obscene language or posting advertisements.
We encourage you to tell your fellow networking professionals about the site!
If you would like us to send them a personal invitation simply send their names and e-mail addresses along with your name to us at [email protected]

Hi together,
Since the release of SAP NetWeaver 2004s to 'Unrestricted Shipment' as of 6th of June 2006, we have renamed the forum 'SAP NetWeaver2004s Ramp-Up' to 'BI in SAP NetWeaver2004s'.
The forum should continue to adress BI issues particular to the release SAP NetWeaver 2004s. Please post general BI, project, etc. question to the other existing BI forums.
The SAP NetWeaver BI organisation will also use this forum to communicate / roll-out information particular to the release of SAP NetWeaver 2004s (in addtion to the FAQs and other material on the SAP Service Marketplace and information in other areas of the SDN).
Cheers
SAP NetWeaver BI Organisation

Why data center begin to build large layer 2 domain?

Hi all,
I found large layer 2 domain is becoming more and more popular these days in data center networking design. Why we need a larger layer 2 domain? Do we have any use cases that could explain this?
thanks a lot!

Duplicate post #2.

Data center out-of-band management network

Would "Cisco Prime Data Center Network Manager" be classed as an out-of-band management tool that I could use on a 2 tier data centre?
If not what solutions could I have for a data center that has a bunch of racks with servers and switches in that connect to an aggregation switch?

My take on "out-of-band" depends not so much on the tool but rather on how it accesses the managed devices.
Most Cisco data center devices have a management port that is independent of the data plane (separate communications processor, separate VRF).
If you communicate to that port using a system and via a network not co-mingled with your user traffic, then you have an out-of-band management tool.

WAN Router Connection to Data Center

We have a WAN router that needs to connect to our Data Center network. The Data Center consists of two N7K core switches, with a pair of N5K switches as aggregation, and each N5K has twelve N2K fabric extenders. The N2Ks are single-homed to the N5Ks. The N5Ks are vPC connected to the N7Ks.
We would like to attach the WAN router to both N7K switches in the Data Center. The N7K switches only have 10G ports in them, so we can't terminate the WAN router directly to the N7Ks.
I was considering creating one dedicated VLAN on each N7K, and assigning an SVI to each VLAN, to correspond to the L3 connections between the N7Ks and the WAN router. Then, we could trunk these VLANs to each of the N5Ks, and configure one 1G port on each N5K for the VLAN, and connect the WAN router to the N5Ks.
Two questions regarding this design:
1) Is there a problem in connecting the L3 WAN router to the N7K via the N5K?
2) Does vPC connectivity between the N7K and N5K pose a problem for the proposed WAN connectivity?
Thanks in advance for any feedback.
-rb

The vPC between N5K and N7K is the catch here. Layer-3 routing over vPC member ports is currently not supported so I will advise you to stay away from this approach.
Atif

Please shed some light on Data Center design

Hi,
    I want you guys to recommend what the design should be. I'm familiar with HP blade system. Let me clarify the existing device.
1. HP Blade with Flex Fabric. It supports FCOE.
2. MDS SAN switch for the storage
3. Network Switch for IP network.
4. HP Storage.
    HP Blade has 2 interface types for IP Network(Network Switch) and Fiberchannel(SAN).
   What is the benifit for using Nexus switch and FCOE for my exising devices. What should be a new design with Nexus switch? Please guide me ideas.
THX
Toshi

Hi, Toshi:
Most of these chat boards have become quite boring. Troubleshooting OSPF LSA problems is old news. But I do pop my head in every now and then. Also, there are so many other companies out there doing exciting things in the data center. You have Dell, Brocade, Arista, Juniper, etc. So one runs the risk of developing a myopic view of the world of IT by lingering around this board for too long.
If you want to use the new B22 FEX for the HP c7000 blade chassis, you certainly can. That means the Nexus will receive the FCoE traffic and leverage its FCF functionality; either separate the Ethernet and FC traffic there, or create a VE-port instantiation with another FCF for multihop deployments. Good luck fighting the SAN team with that one! Another aspect of using the HP B22 is the fact that the FEX is largely plug and play, so you dont have to manage the Flex Fabric switches.
HTH

URGENT: QoS Design on Data Center MPLS - MediaNet Question...

Hello,
I am posting this in hopes I can get some guidance from anyone who has done this in the field. We have a large enterprise customer with 21 sites all around the world, they have Verizon MPLS and are experiencing QoS related issues on their WAN regarding Video/Voice. We have proposed remediating their network acccording to the Enterprise QoS SRND 3.3 and the new MediaNet SRND to account for Video and TP QoS (
http://www.cisco.com/en/US/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND_40/QoSCampus_40.html )
Here is the problem/question that was proposed in our presales meeting and I honestly don't know where to look for an answer... I am not asking for anyone to design a solution for me, just merely point me in the right direction:
The Data Center has a ~40MB MPLS Connection ( full mesh ) into the cloud ( Verizon )
Site A has a 8MB connection
Site B has a 4MB connection
I know on the Service policy and the interfaces at SiteA and SiteB I can assign "Bandwidth xxxx" and use ~95% of the bandwidth to do queuing and shaping/policing ect. I am not concerned with SiteA and SiteB, that I think I can handle...
Question was posed from the customer, "How can we ensure at the DataCenter level the 40MB MPLS is "chopped" up so that only 8MB of the total speed goes to SiteA ALONG with an attached QoS policy designed for that specific site, as well as ensure only 4MB goes to SiteB with an attached QoS policy.
So I am looking for a way to allocate bandwith per site on the DC 40MB connection going into the cloud ( so that SiteB cannot use more than 4MB ) and attach a MediaNet specific QoS Service policy to that site. The customer does not have seperate MPLS circuits for each site, they all come into the DC on 40MB shared ethernet connection ( no VC, or dedicated circuits to other sites ).
Any thoughts on if this is possible?
Thanks!
Alex

This is an example I have seen and I hope that is useful to you.
Site A
Subnet: 172.16.1.0/24
Site B
Subnet:172.16.2.0/24
HeadOffice:
ip access-list extended Site_A
permit ip any 172.16.1.0 0.0.0.255
ip access-list extended Site_B
permit ip any 172.16.2.0 0.0.0.255
class-map match-any Site_A
match access-group name Site_A
class-map match-any Site_B
match access-group name Site_B
policy-map To_Spokes
class Site_A
shape average 8000000
service-policy Sub_Policy(Optional)
class Site_B
shape average 4000000
service-policy Sub_Policy(Optional)
class class-default
shape average 28000000
service-policy Sub_Policy(Optional)
Interface G0/0
Description To MPLS cloud
bandwidth 40000000
service-policy output To_Spokes
interface G0/1
Description To HeadOffice
bandwidth 40000000
service-policy output To_Spokes
It would be greatly appreciated if someone can correct this or improve it as I am still learning.
Please see the netflow graph from one of our routers using a similar policy as above.

Data Center Design

I am looking for a good article about data center design. I need some information about requirements for topics such temperature control, power, security, ventilation, etc.

The practice of System and Network administration is a great resource for the "other" things that make a data center successful.
http://www.amazon.com/gp/product/0321492668?ie=UTF8&tag=wwwcolinmcnam-20&linkCode=as2&camp=1789&creative=9325&creativeASIN=0321492668
Another great resource that you should reference is your local power company. PG&E for example will consult with you, and sometimes pay for upgrades to lower your power consumption.
Here is an article that talks about that in general -
http://www.colinmcnamara.com/2008/02/22/moving-towards-a-green-data-center-truth-behind-the-hype
If this is helpful please rate it
--Colin

Need helip for data center designing

Sir ,
I am going to design a data center where the following equipments are the
1. one router 7609
2. two core switch (WS-C6509-E)
3. two firewall (WS-C6506-E, with Firewall blade)
4. one VOICE ROUTER (CISCO2821with PVDM2-64, VWIC2-2MFT-T1/E1, PVDM2-32)
5. one Remote Access Server (AS5400XM, AS5000XM 60 Dial Port Feature Card, AS5400 Octal E1/PRI DFC card)
6. two CALLMANAGER-5.1
7. multiple no of Cisco IP Phone 7940G with Video Advantage with VT Camera II
8. one Gatekeeper (2811)
9. one Internet Router (3845)
10. one Authentication, Authorization and Accounting (AAA) System
11. one ISDN RAS 2811 with2-Port Channelized E1/T1/ISDN-PRI Network Module with video conferencing (polycom)
12. one Network Intrusion Detection/ Prevention System (NIDS)
13. one NMS
14. one Content Switch for Server Load Balancing
15. multiple Video Phone
16. lots of sever ( mail. Web, storage, etc )
17. polycom MGC 100
18. polycom 7000
also 20 no of 7206 VXR will be connect with 7609 router through lease line
so.. if u send me some link or some sample design and share some advice where I can gather some idea to design this data center in a proper way
thanks
tirtha

IMO opinion the best place to start is by reading the SRNDs. They can be found here-
http://www.cisco.com/en/US/netsol/ns656/networking_solutions_design_guidances_list.html
Hope that helps.

What are share point server 2013 & Share point Designer 2013 & Office 365 & Yammer & Share point 2013 & Windows server 2008 server & Windows Server 2012 Server Data Center?

I need some clarifications.
What are share point server 2013 & Share point Designer 2013 & Office 365 & Yammer & Share point 2013 & Windows server 2008 server & Windows Server 2012 Server Data Center? How each them are related in collaboration system?
Is Share point server 2013 and Share pointer Designer 2013 available in 32bit version? If not, then how to use it in 32 bit machine by using any VMs?
Thanks
Senthil

SharePoint Server 2013:
http://office.microsoft.com/en-us/microsoft-sharepoint-collaboration-software-FX103479517.aspx
SharePoint Designer 2013:
Designer is used to develop SharePoint pages using HTML/CSS/JS as well as SharePoint Designer Workflows
Yammer:
https://about.yammer.com/
Windows Server is Windows, but the Server OS. SharePoint runs on top of supported Windows Servers editions (see http://technet.microsoft.com/en-us/library/cc262485.aspx).
SharePoint Server is 64-bit only (trial:
http://technet.microsoft.com/en-us/evalcenter/hh973397.aspx), although Designer does have a 32-bit edition (full product:
http://www.microsoft.com/en-us/download/details.aspx?id=35491).
You will need the capability to run 64bit VMs. Minimum recommended all-in-one VM for SharePoint is to allocate 24GB of RAM, but you can get away with as little as 12GB (I wouldn't go below that). Because of this, it generally rules out 32bit OSes as a virtual
machine host.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

Data Center Design: Nexus 7K with VDC-core/VDC-agg model

Dear all,
I'm doing with a collapsed VDC-core/VDC-agg model on the same chassis with 2 Redundant Cisco Nexus 7010 and a pair of Cisco 6509 used as a Service Chassis without VSS. Each VDC Core have redundant link to 2 PE based on Cisco 7606.
After reading many design document of Cisco, I'm asking what is the need of a Core Layer in a Data Center especially if it is small or medium size with only 1 aggregation layer and dedicated for a Virtualized Multi-Tenanted environement? What is driving to have a core layer?
Thanx

If your data center is small enough to not require a core, then its fine to run with a collapsed core (distribution + core as the same device). For a redundant design you need to uplink all your distribution switches to each of your cores. If you have no cores, then you need full mess at your distribution layer (for full redundancy).
Lets say you have only 4 distribution pairs...so 8 switches For full redundancy each one needs uplink to each other. This means you need 28 total ports used to connect all the switches together (n(n-1)/2). Thats also assuming 1 link to each device. However if you had redundant cores, the number of links used for uplinks reduces to 21 total links (this includes links between each distribution switch in a site, and link between the two cores). So here you see your only saving 7 links. Here your not gaining much by adding a core.
However if you have 12 distribution pairs...so 24 switches. Full redundancy means you have 276 links dedicated for this. If you add a core, this drops to 61 links. Here you see the payoff.

Data center design guide

Hi all,
does anybody familiar with good design guide of Cisco data center design evolving nexus 2000, 5000 & 7000 with FCoE ?
thanks,

Hi all,does anybody familiar with good design guide of Cisco data center design evolving nexus 2000, 5000 & 7000 with FCoE ?thanks,
Hi ,
Check out the below link on Data center design with Nexus switches
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/C07-572831-00_Dsgn_Nexus_vPC_DG.pdf
Hope to Help !!
Ganesh.H
Remember to rate the helpful post

Recommended Design for WAAS in both Data center and Branch Offices

Hi All,
I need to purchase different appliances for WAAS, but before I decide what to purchase, I need to know exactly how I am going to put these devices so that I can know which one to purchase and how the designs will be.
My environment is as follows:
I have two core routers (ASR 1000 series) at Data center, two 6509 switches (expecting to insert the ACE module, and FW module) and the I have access switches which connects servers.
At the branch offices, I am expecting to place ASR1000 series also.
Now, I need to know the recommended designs for these WAAS appliances so that, I can know in advance what to purchase(i.e. how many WAAS CM, Core WAE, and Edge WAE).
Any input will highly be appreciated.
Thanks,

If you purchase the Standard Edition, your license supports:
One installation of Cisco Security Manager on one Windows-based server.
The configuration or management of 5 devices (in the Standard-5 option) or 25 devices (in the Standard-25 option). This excludes Catalyst 6500 and 7600 Series devices and their associated service modules.
If you purchase either the Standard-5 or Standard-25 license, you cannot purchase an incremental device license. Your license is fixed at either 5 or 25 devices.

Data Center Network Design

Similar Messages

Maybe you are looking for