4982474
Description
Mind Map by Manueel Sepulveda, updated more than 1 year ago
|
Created by Manueel Sepulveda
about 8 years ago
|
|
CCDA 200-310 CAP03
Exploring Basic Campus and
Data Center Network Design
- Understanding
Campus Design
Considerations
- Enterprise campus
- Server Farm and
Data Center
- Campus Backbone
- Building Distribution
- Building Access
- Server Farm and
Data Center
- Enterprise campus design
- Network application
considerations
- Peer-to-peer
applications
- Client/local
server
applications
- Client/server
farm
applications
- Client/enterprise
edge server
applications
- Peer-to-peer
applications
- Environmental considerations
- Intrabuilding
- Interbuilding
- Remote Buildings
- Intrabuilding
- Transmission media
- Twisted pair
- Multimode fiber
- Single-mode fiber
- Wireless
- Twisted pair
- Network application
considerations
- Enterprise campus
- Understanding the Campus
Infrastructure Module
- Building access best practices
- Limit the scope of
most VLANs
- RPVST+
- Trunk to desirable
- Remove unneeded VLANs from trunks
- (VTP) mode to transparent
- EtherChannel mode to desirable
- routing at the access layer
- Limit the scope of
most VLANs
- Building-distribution considerations
- Distribution layer require wirespeed
- Aggregation point for access layer switches
- High-speed connectivity to campus core
- Redundant connections to the campus core layer
- Stateful Switchover (SSO) and Nonstop Forwarding (NSF)
- High availability, quality of service (QoS), and policy enforcement
- Distribution layer require wirespeed
- Campus core considerations
- interconnecting three or more buildings
- High-speed ports required to aggregate the building distribution layer.
- least two switches Core
- interconnecting three or more buildings
- Server farm considerations
- Determine server placement in the network
- All server-to-server traffic should be kept
within the server farm module
- For large network designs, consider placing
the servers in a separate data center
- Consider using network interface cards
(NIC) in servers that provide at least two
ports
- For security, place servers with similar
access policies in the same VLANs
- limit interconnections between servers in
different policy domains using ACLs on the server
farm’s multilayer switches.
- Determine server placement in the network
- Building access best practices
- Understanding Enterprise
Data Center Considerations
- Cisco enterprise data center architecture
- Networked Infrastructure Layer
- Interactive Services Layer
- Networked Infrastructure Layer
- design best practices
- Data center access layer design best practices
- Layer 2 and Layer 3 connectivity
- port density to meet server farm
- Support both single-attached
and dual-attached servers
- RPVST+
- Layer 2 and Layer 3 connectivity
- Data center aggregation layer
design best practices
- advanced application and security options
- hardware failover
- Offer Layer 4 through 7 services, such as
firewalling, server load balancing, Secure
Sockets Layer (SSL) offloading, and IDS.
- processor resources to accommodate a
large STP processing load.
- advanced application and security options
- Data center core layer design
best practices
- Use the separate cores (that is, the campus
core and the data center core) to create
separate administrative domains and
policies (for example, QoS policies and
ACLs)
- Use the separate cores (that is, the campus
core and the data center core) to create
separate administrative domains and
policies (for example, QoS policies and
ACLs)
- Data center access layer design best practices
- Cisco enterprise data center architecture
Want to create your own Mind Maps for free with GoConqr? Learn more.