Small campus network design

We have a new building about 300 meters from our main data center. 8 catalyst 4500 series switches will be installed for access layer. We are running a Nexus 7k on our data center, with a user VDC that we plan to connect these access layer switches. I plan to use two of eight
switches as the distribution/access layer switches (I plan to run two to four fiber from the Data center to these two switches and distribute the connection to the rest of the switches). Is what I am planning to do going to be practical? Please advice me the best approach/options to connect this small campus.

If you have enough fiber (2x8=16 pairs) between the data center and the campus, you can directly run all the access switches to the 7k and no need for distribution switches.
Also you said, you have one 7k. For redundancy you really need 2 7ks.
As for VDC, if this is all for the same organization, there is no need to connect the access switches to a different VDC. If you do connect them to a different VDC and the users need to talk to data center you would need to run a physical cable between the data center VDC and the Campus VDC which defeat the purpose.
HTH

Similar Messages

In a huge campus network design, should be the Core layer operate on L3 if the Distribution is operating on L3?

Or the routing overhead is less if the Core is operating on L2?
For example:
Wan routers and Dist L3 switches connect to Core switches (L2)
Access layer L2 switches connects to Dist.
So Access layer SW's do Diffserv marking, Dist layer switches do queuing, the inter vlan routing as well as routing and the core only forwards traffic based on L2.
Is it a valid design? Should the core also have QoS?
Thanks!

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
Yes, you can have a L2 core, but as Rick has noted, modern designs lean toward L3 cores.
There are, even today, pros and cons to each, but the biggest factor would be a modern L3 core would normally use L3 switches, rather than traditional routers. Generally you want the core to move packets as quickly as possible, and L2 switches were generally better at that than "traditional" routers. L3 switches, though, have nearly L2 switch performance, so the performance difference isn't much of issue any longer (especially with CEF L3 switches and/or MPLS).
BTW, not something you'll see in many current design documents, but modern L3 switches are so powerful and support so many ports, that you might have distribution and access just L2.
If you're doing QoS, yes I would recommend it also be enabled in the core too, L2 or L3.

Campus Network Question

In a Campus Network design where you have Core switch, Distribution switch and Access switch layers and SVI's acting as your gateways for different VLANs.
Since it is advised that Core Switches should be the root bridges, does that mean that the Core Switches should be the default gateways for your Vlans?
I thought that it was the job of the distribution layer for being the default gateways.
Anyone clarify?

hi friend,
It generally depends on your LAN design.
If you follow Cisco's 3 tier architecture, you should restrict your VLAN boundaries on the distribution switch and should be running a L3 link between the core and the distribution. This means the SVI's are created on the distribution switch which will act as gateways for your VLANs.
This helps in restricting the broadcasts from reaching the core.
If your LAN is actually a collapsed core, you end up configuring the SVIs on the distribution switch which also acts as your core.
HTH, rate if it does
Narayan

Location Aplliance will not synch network design

2710 Location appliance running 4.0.33.0, WCS running 4.2.130.
2 Campus Network Designs each with multiple buildings and floors. One can be assigned to the location server and synchroization works perfectly. The second network design shows unassigned. If I assign it to the location appliance and then sychronize network designs it reverts to unassigned.
Has anyone run into this issue and been able to resolve it?

1) Connect to LOCAPP CLI
2) Stop the LOC Service(/etc/init.d/locserverd stop)
3) Take the backup of Loation DB which can be found at /opt/locserver/db/linux/server-eng.db
i.e. copy the server-eng.db to some other directory e.g. /home
4) Delete the DB by issuing the command
rm -f /opt/locserver/db/linux/server-eng.db
5) Start the LOC service (/etc/init.d/locserverd start)
6) Perform the sync. through WCS
Hope this will help you...

Ask the Expert: Hierarchical Network Design, Includes Core, Distribution, and Access

Welcome to the Cisco® Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about hierarchical network design.
Recommending a network topology is required for meeting a customer's corporate network design needs in their business and technical goals and often consists of many interrelated components. The hierarchical design made this easier like "divide and conquer" the job and develop the design in layers.
Network design experts have developed the hierarchical network design model to help to develop a topology in discrete layers. Each layer can be focused on specific functions, to select the right systems and features for the layer.
A typical hierarchical topology is
A core layer of high-end routers and switches that are optimized for availability and performance.
A distribution layer of routers and switches that implement policies.
An access layer that connects users via lower-end switches and wireless access points.
Ahmad Manzoor is a Senior Pre-Sales Engineer at AGCN, Pakistan. He has more than 10 years of experience in first-rate management, commercial and technical skills in the field of data communication and services lifecycle—from solution design through sales pitch, designing RFPs, architecture, and solution—all with the goal toward winning projects (creating win/win situations) of obsolete solutions. Ahmad also has vast experience in designing end-to-end data centers, from building infrastructure design to data communication and network Infrastructure design. He has worked for several large companies in Pakistan and United Arab Emirates markets; for example, National Engineer, WATEEN Telecom, Emircom, Infotech, Global Solutions, NETS International, Al-Aberah, and AGCN, also known as Getronics, Pakistan.
Remember to use the rating system to let Ahmad know if he has given you an adequate response.
Because of the volume expected during this event, Ahmad might not be able to answer every question. Remember that you can continue the conversation in the Solutions and Architectures under the sub-community Data Center & Virtualization, shortly after the event. This event lasts through August 15, 2014. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Dear Leo,
We are discussing the following without any product line, discussing the concept of hierarchical design, which will help you to take decision which model is better for you Two Layer or Three Layer hierarchical model.
Two-Layer Hierarchy
In many networks, you need only two layers to fulfill all of the layer functions—core and aggregation
Only one zone exists within the core, and many zones are in the aggregation layer. Examine each of the layer functions to see where it occurs in a two-layer design:
Traffic forwarding—Ideally, all interzone traffic forwarding occurs in the core. Traffic flows from each zone within the aggregation layer up the hierarchy into the network core and then back down the hierarchy into other aggregation zones.
Aggregation—Aggregation occurs along the core/aggregation layer border, allowing only interzone traffic to pass between the aggregation and core layers. This also provides an edge for traffic engineering services to be deployed along.
Routing policy—Routing policy is deployed along the edge of the core and the aggregation layers, generally as routes are advertised from the aggregation layer into the core.
User attachment—User devices and servers are attached to zones within the aggregation layer. This separation of end devices into the aggregation permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, it is best not to mix transit and destination traffic in the same area of the network.
Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the aggregation layer. You can also place traffic admittance controls at the aggregation points exiting from the aggregation layer into the core of the network, but this is not common.
You can see, then, how dividing the network into layers enables you to make each layer specialized and to hide information between the layers. For instance, the traffic admittance policy implemented along the edge of the aggregation layer is entirely hidden from the network core.
You also use the core/aggregation layer edge to hide information about the topology of routing zones from each other, through summarization. Each zone within the aggregation layer should have minimal routing information, possibly just how to make it to the network core through a default route, and no information about the topology of the network core. At the same time, the zones within the aggregation layer should summarize their reachability information into as few routing advertisements as possible at their edge with the core and hide their topology information from the network core.
Three-Layer Hierarchy
A three-layer hierarchy divides these same responsibilities through zones in three vertical network layers,
Traffic Forwarding—As with a two-layer hierarchy, all interzone traffic within a three- layer hierarchy should flow up the hierarchy, through the layers, and back down the hierarchy.
Aggregation—A three-layer hierarchy has two aggregation points:
At the edge of the access layer going into the distribution layer
At the edge of the distribution layer going into the core
At the edge of the access layer, you aggregate traffic in two places: within each access zone and flowing into the distribution layer. In the same way, you aggregate interzone traffic at the distribution layer and traffic leaving the distribution layer toward the network core. The distribution layer and core are ideal places to deploy traffic engineering within a network.
Routing policy—The routing policy is deployed within the distribution layer in a three- layer design and along the distribution/core edge. You can also deploy routing policies along the access/distribution edge, particularly route and topology summarization, to hide information from other zones that are attached to the same distribution layer zone.
User attachment—User devices and servers are attached to zones within the access layer. This separation of end devices into the access layer permits the separation of traffic between traffic through a link and traffic to a link, or device. Typically, you do not want to mix transit and destination traffic in the same area of the network.
Controlling traffic admittance—Traffic admittance control always occurs where user and server devices are attached to the network, which is in the access layer. You can also place traffic admittance controls at the aggregation points along the aggregation/core edge.
As you can see, the concepts that are applied to two- and three-layer designs are similar, but you have more application points in a three-layer design.
Now the confusion takes place in our minds where do we use Two Layer and where the Three layer hierarchical model.
Now we are discussing that How Many Layers to Use in Network Design?
Which network design is better: two layers or three layers? As with almost all things in network design, it all depends. Examine some of the following factors involved in deciding whether to build a two- or three-layer network:
Network geography—Networks that cover a smaller geographic space, such as a single campus or a small number of interconnected campuses, tend to work well as two-layer designs. Networks spanning large geographic areas, such as a country, continent, or even the entire globe, often work better as three layer designs.
Network topology depth—Networks with a compressed, or flattened, topology tend to work better as two-layer hierarchies. For instance, service provider networks cover large geographic areas, but reducing number of hops through the network is critical in providing the services they sell; therefore, they are often built on a two-layer design. Networks with substantial depth in their topologies, however, tend to work better as three-layer designs.
Network topology design—Highly meshed networks, with many requirements for interzone traffic flows, tend to work better as two-layer designs. Simplifying the hierarchy to two levels tends to focus the design elements into meshier zones. Networks that focus traffic flows on well-placed distributed resources, or centralized resources, such as a network with a large number of remote sites connecting to a number of centralized Data Centers, tend to work better as three-layer designs.
Policy implementation—If policies of a network tend to focus on traffic engineering, two-layer designs tend to work better. Networks that attempt to limit access to resources attached to the network and other types of policies tend to work better as three-layer designs.
Again, however, these are simple rules of thumb. No definitive way exists to decide whether a network should have two or three layers. Likewise, you cannot point to a single factor and say, “Because of this, the network we are working on should have three layers instead of two.”
I hope that this helps you to understand the purposes of Two Layer & Three layer Hierarchical Model.
Best regards,
Ahmad Manzoor

Small DC Switch Design

Hello,
I'm working on options for a small DC switch design. This DC has 5
virtual hosts with 10-20 guest vm's each. Each server has two quad
port gig nics with 6 of the 8 gig ports connected (3 for iSCSI and 3
for data or management. It also has two 3 node sans each with 2 gig
ports per node, a host of other small servers including voice servers,
management servers, asa firewall, and a few routers. Total of 50-60
ports as of right now.
Connected to the DC is 7 other buildings each with there own 1 gig
fiber connection serving about 3000 devices in total including
desktops, laptops, ip phones, wireless ap's, building automation,
alarm panels, etc....
Right now in each of the 7 buildings has a 3560G as an aggregation
switch connected back to the DC. The DC also has a few 3560G's and
3750G's for the sans and servers. The system seems to work ok for the
most part aside from micro bursts overwhelming the buffers on these
switches and the etherchannel trunks between them dropping a minor
amount of packets. QOS is configured for the voice network and there
are little to no complaints.
What I would like to know (costs being the biggest factor) is what
would be a better switch design for the current and future traffic in
this network. Some options I was thinking about are as follows:
I would needs at least 96 ports.
So option A is to go with a 4506-E bundle with 2 48 port line cards,
sup 6l-e and a WS-X4712-SFP+E or something of the sorts.   And then
upgrade to the enterprise services license and do all of the routing
and switching for the DC on this one switch. Means little redundancy
and no failover.
Option B was to go with the same 4506-E bundle, without the extra
license and without the SFP line card and put in some sort of layer
three aggregation switch, possibly an me3600x.
Option C Is to go with the 4503-E, the SFP line card and the IP
Enterprise services license. And two top of rack switches, either
2360's or 4948's.
I would like to do some PBR on the aggregation switch, but I am unsure if the me3600x is capable of doing that.
I have no experience in this matter so any other thoughts or
suggestions would be appreciated.
Thanks,
Dan.

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
If cost is the biggest factor, and the only notable issue now is occasional packet drops due to insufficient buffers, perhaps some buffer tuning would be something to consider.
A really important question to answer is how important redundancy. At lower port densities (3 to 4 stack members), the switch stack is less expensive than a chassis that supports redundancy. At very low port densities (2 to 3 stack members) the stack might be less expensive than even a non-redundant chassis.
BTW, the 3750-E/X offers much more performance than the original 3750 series. If offers wire-speed PPS and fabric per switch, twice the ring bandwidth and uses the ring, for unicast, much "smarter".
Perhaps a dual WS-C3750X-12S or WS-C3750X-24S for your core with dual MEC fiber etherchannl links to your aggregation switches? In the DC itself, you might also use 2960s to provide DC edge ports. For growth, a dual 3750-X stack would support four 10 gig ports which could be used with 10 gig servers or 10 gig SAN or as a 10gig link to other DC switches, such as the 2960S (which support their own stacking technology).

WiSM Redundancy in Campus Network L3 Access

Hi guys,
I'm designing a Campus network L3 Access in a Building with 30 floors and aproximately 250 APs,8 APs in each floor.
For each floor I will use two /24 subnet (one for data and one for voice). I have 2 WiSM...
I don't wanna to use another two /24 subnet for each floor only for redundancy, so I want to know
if i can use the following idea (Please take a look in the PPT File)
I will create a AP Group in each controller to include the APs for each 2 floors (for example floor 1 and 2).
The only diference between those AP Group in each controller is the network subnet associated with the Dynamic
Interface. The AP Group in controller WiSM1-A will be associated with the 192.168.1.0 network and the AP Group
in controller WiSM2-A will be associated with the 192.168.2.0 network.
The APs in the first floor I will configure to use the controller WiSM1-A as primary and I expect to see the hosts with the 192.168.1.0/24 network.
The APs in the second floor I will configure to use the controller WiSM2-A as primary and I expect to see he hosts with the 192.168.2.0/24 network.
If one of those controllers fail (for example WiSM1-A), I think all the APs will use the another controller and I expect to see the hosts with the 192.168.2.0. In this case I know that network 192.168.2.0 is used for both the two floors, not more just one floor. I accept that half the users can use the wireless network during the fail..
Is this works and if yes, can I use this idea with Mobility Group, Roaming L3, etc ????
Thanks in Advanced,
Andre Lomonaco

Hi gamccall,
First thanks for your reply...
I like you idea but initially I can't use it cause I put each wism in a ospf tottaly stub area and I use area summarization to have less networks in the core routers....
In my designing, the wism1 is in the
range 10.0.0.0 -> 10.0.95.0 and the
wism2 is in the range 10.0.96.0 ->
10.0.191.0
My Best Regards,
Andre Lomonaco

Network Design Pointers...

Hey everyone, I am not too sure if this is the correct location to be posting this, but I have some questions regarding networking design.
I have created a test network within Packet Tracer, which I have added as an attachment. I just wanted some pointers on how I could have changed things, just regarding the topology. My main arean of concern is with the printers, could they have been better located.
I have uploaded a screen shoot, and the Packet Tracer file of my design, please let me know what you guys think. This is my first time creating a network, this helps me study for my exams, as I just finished my CCENT, and now working on CCNA.
Thanks so much for your time everyone.
Paul St.Onge

>
Threaded interfaces - do you mean user
interfaces?Not quite, and it possibly comes as part of the other questions, but a description (or an attempt at) is, imagine that you have one application on a server and some small applications in a series of pcs connected with the server. This applications,when started, send a command to te server which creates a thread that interfaces with the client app so that the processing can be spread more or less evenly. <hope to make sense>
>
Detection of java/javaw - what do you mean by that?The System.getProperties(... was what i was looking for

Network Designs

Hi all
I wanted to know if someone can give me some adivce,I've started my own consulting company and I have a client who wants a network redesign and a
Core network design.Both of these are for different sites and I wanted to know what questions should I ask the client and is there some books that I can
read upon about network design that will give me a good feel on how to proceed. I have a good ideal already about the hardware that is needed at each layer, but the network I learned on was a large enterprise network and these are smaller networks and I really want to do a good job for this user so that
I can get repeat business.Thanks in advance and have a great day and I look forward to your replies.

1) you should ask is why does the client want a network redesign and what are they looking to achieve by doing this ie. no one does a network redesign just for the fun of it
2) based on the answers to the first question you need to see the existing network design and then work out why it does not meet the clients needs.
3) probably as important as anything else is what budget is available for the redesign ie. consultancy for you and hardware budget.
4) what inhouse experience the client has. You can setup the loveliest shiny network but if the customer cannot then support it it is not particularly useful to them.
5) future plans for expansion for the client
6) the hardest part - application, traffic patterns, bandwidth requirements of the network. Make sure you at least identify the apps that the client makes their money from and design accordingly.
Don't decide on hardware before the design. The design dictates the hardware design and not the other way around. If you already have an idea of the hardware you are going to use you either have answers to all the above or you are getting ahead of yourself
A good place for design info are Cisco's design papers -
www.cisco.com/go/srnd
Jon

How to setup a small office network

Hello,
I am looking to setup a small office network comprising 6 G4 macs (existing computers) that have been upgraded to the newest OS version. What is the best way to go about networking these computers together in terms of being able to share files, internet connection, access to peripherals and also implementing a firewall.
Any suggestions or help would be greatly appreciated.
Thank you

1, Get a cable internet ISP account; depending on your service you should be able to secure a 5Mbps down and 2Mbps up on the cable e.g. Cox or Comcast.
2. Get a good router. The mass market Linksys and Netgear routers aren't very good in terms of reliability. I use a ZyXEL P-330W router is the best I've ever seen. Its reliable and very efficient in terms of throughout. The Apple Airport Extreme is good.
3. Set up the router to support UPnP. This way all computers will be able to share iChatAV video conferencing. If you enabled "port forwarding" only one Mac would be able to use iChatAV video conferencing.
4. Set up your router for DHCP to dynamically issue Internet address to all your computers.
5. Setup the wireless router for encryption such as WPA. This will encrypt wireless communication.
6. Setup the wireless router for only your computers. You'll have to get the MAC/AirPort ID network addresses as expressed in terms of an xx:xx:xx:xx address. You can get this thru your Systems Preferences -> Network window -> AirPort (in the sidebar) -> Advanced button.
7. If you have Ethernet in your office then skip steps 5 and 6 above.
8. On each computer open up the System Preferences -> Sharing and check-off the File Sharing. Set your user access preferences appropriately.
9. Get a Network enabled All-in-one printer and setup Printer Sharing options. Hook-it up to your network and add your printer by clicking on the "+" sign in your "Print and Fax" Preferences.
10. Don't enable Apple Firewall on each Mac. The router will be the Firewall.
Ok. That's the short-hand.. plug it all in and go!

Randomly monitor small office network

Looking for a user-friendly, dummy-proof article on creating a small office network from a total of four Mac's (3 iMacs, one Air), allowing the administrator to randomly monitor without detection the real-time activities taking place on the other two machines. Triple points for iOS monitoring capabilities, as well

Hello, rjbm_exact.
You definitely need a managed switch and a Cisco Small Business (200 or 300 series) can meet your requirements. You can setup separate VLAN to segregate user access level. Are you also looking at expanding your wireless (guest access)?
Let me know if you need more assistance or e-mail ([email protected]) me directly. Kind regards.

Computers on small office network - names getting confused on iChat

We are using bonjour and iChat on the computers on a small airport network in our office as an instant messaging solution in our office - however, 2 of the computers (which are named differently) keep getting confused and both being called the same name.
I have done the fix where you go to System Prefs, Users & Groups and then set the address book card to that particular computer owner, restart the computer and then open iChat (using bonjour) - it saves the name but then my colleague becomes the same name as me on iChat - so we do the same thing to her computer (set address book card etc) and it changes her iChat name, but then also seems to override what I had set for mine previously.
Help!! What can I do to stop these 2 computers seemingly overriding each other? It doesn't happen with the other 4 computers sharing our network...

Hi,
In System Preferences > Sharing is the Name the Computer has.
This does play a part in any Bonjour Connection.
It is this name that appears in Shares in the Finders's Side bar.
Separate for that iChat and Messages that have the Bonjour Account Enabled broadcast the details from the My Card in the Address Book.
Issues can arise with some Server based Logins that create a Global Address book that changes the My Card.
You get similar difficulties on some DiskImage roll outs of updates and the like if the details of the Address Book are copied as well.
I am not sure what you mean by the "fix" in System Preferences > Users and Groups to change the My Card or the Computer's Name.
Yes you can click the Contact Card for that account and it will show you it in the Address Book and it should be th My Card.
Changing the My Card then does not alter which Card is associated with the Mac User Account.
There is no access to the Computer's Name
7:53 PM Wednesday; August 1, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Small business network issues!!!

I am at my wits end with this problem: We have a small business network consisting of 6 Mac Pro computers and 2 Windows PCs. Everything was working fine until we needed to replace one of the WinXP machines with a Windows 7 machine. None of the Macs can see the PCs unless they physically type in the IP address (they used to show up in the finder as the computer name). None of the PCs can access the Macs at all and now shares on one of the Macs are no longer visible by the rest of the network. Any help would be appreciated.
Computers:
Mac Pro 10.7.5
Mac Pro 10.6.8 (x4)
Mac Pro 10.5
Windows 7 64-bit Professional
Windows XP Professional
I have made sure that every computer uses the correct workgroup name and that all file sharing is enabled.

I've seen it take 45 minuyes for a PC to announce it's name on the network, just sayin'.
Anyway, does the PCs IPs ever change?

Small home network using a mini

Hello i'd like to set up a small home network. The component i have are:
A broadband connection via a cable modem
A mac mini which can act as a server (i'd like to provide access to shared photos and music, and connect an external HD for backup and storage)
2 airport wireless routers
2 macbook pro laptops and 1 mini all with wireless
Any suggestions as to the most effective way to link this all together?
Thanks
Tim

Hi Tim,
You've accidentally posted this on the iPod Mini forum, not the Mac Mini!
Mark

Office network design ideas..

Hey all, we are upgrading to a Cisco network and wanted some input on our possible network design...
Currently we have:
A Juniper SSG 140 and IDP for our firewall and IDS
3com (layer2/3) switches for our desktops
2 Dell PowerConnect 5424 switches for our servers and firewalls
2 Dell PowerConnect 5424 switches (separate network) for our SAN/VM hosts
This is what we are thinking of for our next solution
ASA 5512 for our firewall (I read we could possibly get a 25% performance speed improvement for user VPN connections?)
2 WS-C3750x-48t-e (I think this does Layer 2/3) for our desktops
2 WS-C3750x-48t-e for our firewalls/servers
2 WS-C3750x-24P-L for our SAN/VM hosts
The problem is different network services providers who are going to implement this for us are giving us different solutions
Some desktop 3560X for desktops and 4948 for servers and others are telling me 3750x for desktops and Nexus 3048 switches for SAN
Some are telling me we can keep SAN+VM+core traffic on the same switches and just separate them with VLANs while others are telling me we should get separate switches for them
Basically, we just want a improved improvement with better PERFORMANCE and REDUNDANCY (esp with our core + SAN/VM traffic) without going overboard and spending a ton of money
More thoughts:
We need Layer 2/3 switches for core + SAN
Do we need 10G ports?
Let me know your thoughts...

Hi There,
the hardware selection actually depends on the network/site topology, number of users, traffic load and more other factors
this is for IP network, for SAN do you mean iscsi, FCoE or pure FC SAN because these are different things and may change the HW selection,
in general 3560 are good fro access switches and 3750 provide same capabilities with improved performance and support for swtckwise ( 3750 is a good option especially if you planing to stack them )
for L3 it is supported on both but consider the license/image you buy with regard to the features you need
nexus for Data center switch are the best as they are design for data center switching however you need to know, port density, 1G or 10G, do you need any FC SAN, DC load/capacity, any L3 function is required and future growth then you can decide if Nexus 3K or 5K is good for you or not
N5K
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/data_sheet_c78-618603.html
N3K
http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps11541/at_a_glance_c45-648255.pdf
if yo have a network topology with more details of what you need, post it here for more discussions
hope this help
if helpful rate

Small campus network design

Similar Messages

Maybe you are looking for