YT YouTube2Text

YouTube2Text → Transcripts → Designing Basic Enterprise Campus Networks Part 3

Designing Basic Enterprise Campus Networks Part 3 — Transcript

by Santelmo · 1,693 words · 379 segments · language en · Watch on YouTube

Open in transcriber Summarize with AI Download SRT/VTT

Full transcript

0:04enterprise data center design
0:06considerations
0:09this section describes general
0:11enterprise data center design
0:13considerations
0:15and provides an overview of the general
0:18technologies and models
0:19used in an enterprise data center
0:25server centric to service center
0:30so this server-centric data center model
0:32is evolving
0:33into a service-centric model
0:37well the evolution includes the
0:40deployment of the virtual machine
0:42software
0:43such as a vmware and zen
0:47which breaks the one-to-one relationship
0:49between the applications
0:51and the server hardware and operating
0:53systems on which they run
0:56so virtual machine software allows
0:58multiple
0:59applications to run on a single server
1:01independent of each
1:02other and of the underlying operating
1:05system
1:07so the removal of storage from the
1:09server
1:10consolidating it in a storage spools
1:14so network storage such as the sun okay
1:16or the storage area networks
1:18allows easier management provisioning
1:22improved utilization and consistent
1:24recovery practices
1:26so the creation of pools of one-way
1:30two-way or four-way servers that can be
1:33pulled and provisioned
1:34on demand so the consolidation
1:37of the io resources so that the i o
1:40can be pulled and provisioned on demand
1:44for connectivity to other servers
1:46storage
1:47and land pools
1:51the cisco enterprise data center
1:53architecture framework
1:55so the consolidation and virtualization
1:58of data center resources
2:00requires highly scalable resilient
2:03secure data center network foundation
2:06so as described in the previous video
2:10applying methodology to a network design
2:13the cisco sona or the service oriented
2:15network architecture framework
2:17defines how enterprises can evolve
2:20towards intelligence in the network that
2:22optimizes applications
2:25business processes and resources
2:28so the cisco enterprise data center
2:31architecture
2:32based on sauna provides organizations
2:36with framework to address immediate data
2:38center demands
2:40for consolidation and business
2:42continuance
2:44while enabling emergence okay
2:47virtualization and on-demand computing
2:50technologies in the data center
2:52so this cisco enterprise data center
2:55architecture
2:56as illustrated on this diagram here
2:59aligns data center resources with
3:03business applications and provides
3:06multiple resources to end users in an
3:09enterprise
3:10so the cisco enterprise data center
3:13architecture has the following layers
3:15so basically you'll have there the
3:18network infrastructure layer
3:21so meets all the bandwidth latency
3:25and protocol requirements for user to
3:27server
3:28server to server and server to storage
3:31connectivity
3:32and communications in a modular
3:35hierarchical structure so the next one
3:38would be the interactive services layer
3:40so which provides
3:43a hierarchical okay infrastructure
3:47services
3:48that ensure the fast and secure
3:51alignment of resources with application
3:54requirements
3:54and cisco application networking
3:57services or ants
3:59that optimize application integration
4:02and the delivery of applications to end
4:04users
4:05[Music]
4:08let's have an example this is a data
4:10center network topology
4:11this illustrates example high
4:13performance data center network topology
4:17that requires many technologies and
4:19connectivity options among applications
4:21and data centers
4:23so this network topology provides
4:26connectivity services
4:28for network elements within the data
4:30center
4:31such as servers and storage as well as
4:35to external users or other data centers
4:40enterprise data center infrastructure
4:42overview
4:44so this figure here shows a typical
4:47large
4:48enterprise data center infrastructure
4:50design
4:51so the design follows the multi-layer
4:54infrastructure architecture
4:56including the core aggregation
4:59and access layers okay so we've got four
5:03aggregation and of course our access
5:06layer here
5:09now the data center infrastructure must
5:11provide port density
5:13and layer 2 and layer 3 connectivity for
5:16servers
5:18at the access layer while supporting
5:20security
5:22services provided by access lists or
5:24acls
5:26firewalls ips okay at the data center
5:30aggregation layer
5:32it must support server farm services
5:35such as content switching
5:37caching and secure socket layer or the
5:41ssl okay so
5:46well that secure socket layer is
5:48basically used in the web access
5:50offloading while integrating with a
5:53multi-tier
5:54server farms mainframes
5:58and mainframe services okay so with load
6:01balancing and
6:03ssl offloading now
6:06network devices are often deployed in
6:10redundant pairs
6:12to avoid a single point of failure so if
6:14you will observe
6:15you've got redundancy among connectivity
6:17you've got
6:18aggregation on this on a part here okay
6:21under the
6:22data center aggregation you also have
6:25link aggregation
6:26on the data center core and you have
6:29some sort of redundancy
6:34data center access layer so what do we
6:37have here
6:38so the data center access layer provides
6:40layer 2
6:42layer 3 and mainframe connectivity
6:46the design of the data center access
6:48layer varies depending on whether layer
6:502 or layer 2 access switches are used
6:53so it is typically built with high
6:55performance
6:57low latency layer 2 switches
7:00allowing better sharing of service
7:03devices across multiple servers
7:06and allowing the use of the layer 2
7:08clustering
7:09which requires the server to be a layer
7:12to adjacent
7:14so with layer two access switches the
7:16default gateway for the servers cannot
7:18be configured at the access or
7:20aggregation layer
7:22so servers can be single or
7:26dual attached okay so with dual attached
7:29nic's
7:31in the server a vlan or trunk is
7:33required between the two redundant
7:35access layer switches
7:37to support having a single ip address
7:40on the two server links to two separate
7:44switches so the default gateway is
7:48implemented
7:49at the axis layer it makes up both
7:53layer two and layer three axis switches
7:56using one wrap unit or one ru
7:59okay and modular platforms
8:02in a flexible solution and allows
8:05application environments to be optimally
8:10positioned
8:12density and scalability implications
8:15so some scaling issues in the data
8:17center relate
8:18to physical environment the typical
8:21enterprise data center experiences
8:24high growth in the sheer number of
8:27servers
8:28at the same time server density has been
8:31improved
8:32with one ru and blade server solutions
8:35so three particular challenges result
8:38from
8:38this trend so you've got the cabling
8:42okay or cable bulb typically
8:45three to four interfaces are connected
8:47on the server
8:48with a higher density of servers per
8:50wrap
8:52so cable routing and management can
8:55become
8:56quite difficult
8:59next would be power
9:02so the increased density of components
9:04in a wrap
9:05is driving a need for a larger power
9:08feed
9:08to the wrap so many data centers do not
9:11have the power capacity
9:13at the server rows to support price
9:16increase
9:17and the last one is cooling system or
9:20the cooling
9:22the number of cables lying under
9:25and raised floor and the
9:29cable bulk at the cabinet base entry is
9:31blocking the airflow
9:33required to pull the equipment in the
9:36wraps
9:37so at the same time the servers in the
9:40wrap
9:40require more cooling volume because of
9:43their
9:44high density so basically
9:48these challenges have forced the
9:50customers to find alternative solutions
9:53by spacing cabinets modifying cable
9:56routes
9:57and other means including not deploying
10:00high density server solutions
10:06defining the data center aggregation
10:08layer
10:09so the data center aggregation or
10:11distribution layer
10:13aggregates the uplinks from the access
10:16layer
10:17okay to the data center core layer
10:20and is the critical point for control
10:23and application services
10:25so security and applications
10:29such as load balancing devices
10:32ssl of loading devices firewalls
10:35ips so that provides layer 4
10:39through layer 7 services and are often
10:42deployed as
10:43module in the aggregation layer
10:47okay like service modules here now this
10:50highly flexible design
10:52takes advantage of the economies of
10:54scale
10:55by lowering the total cost of ownership
10:57or pco
10:59and reducing complexity by reducing the
11:01number of components to configure and
11:02manage
11:04so service devices deployed
11:09at the aggregation layer are shared
11:12among
11:12all the servers where a service device
11:15is deployed
11:17at the access layer benefit only the
11:19servers that are directly attached to
11:21the specific
11:22access switch
11:27defining the data center core layer
11:30so implementing a data center core layer
11:33is
11:34a best practice for large data centers
11:37so the following should be taken into
11:39consideration
11:40when determining whether the core is
11:43appropriate
11:45so first you've got a 10 gigabit
11:47ethernet port density
11:49so without the data center core will
11:52there be enough
11:5310 gb ethernet ports on the campus score
11:56switch
11:57where to support both the campus
11:59building distribution layer and
12:00in the data center aggregation layer
12:04next would be the administrative domains
12:07and policies so separate campus
12:11and data center cores help isolate the
12:14campus building distribution layers
12:17from data center aggregation layers for
12:19troubleshooting maintenance
12:22administration and implementation of
12:25policies using the quality of service
12:26and access lists
12:29next would be anticipation of the future
12:32development
12:34so the impact that could result from
12:37implementing
12:38a separate data center core layer at a
12:41layer date
12:42okay or at a later date might
12:45make it worthwhile to install it
12:49at the beginning so the data center
12:52typically connects
12:53to the campus core using a layer three
12:55links okay
12:57the data center network addresses are
13:00summarized into the campus core
13:02and the campus core injects a default
13:04route
13:05into the data center network
13:08so key data center core layer
13:11characteristics includes the following
13:14okay so you've got the distributed
13:16forwarding architecture
13:18low latency switching 10 gb
13:21ethernet scalability and scalable ip
13:25multicast
13:26support
13:29so to summarize the enterprise data
13:32center design considerations
13:34so enterprise data centers support
13:37a rich set of applications and servers
13:41so the sauna-based cisco enterprise data
13:43center architecture
13:45provides a modular hierarchical approach
13:49to align data center resources with
13:52small business applications
13:56so the enterprise campus and data center
13:58design review
13:59so analyze the organizational
14:01requirements
14:03so type of applications traffic volume
14:06and traffic patterns so redundancy and
14:10backup
14:12will be needed okay so you have the
14:14options
14:15like different protocols used for
14:17redundancy
14:20characterize the existing network and
14:22sites so technology used
14:24and location of hosts servers
14:27terminals and other endnotes
14:31develop enterprise campus and enterprise
14:33data center network designs
14:35so based on requirements implement two
14:39or three hierarchical layers
14:41so select the hardware and software
14:43components to support
14:45requirements
14:48now to summarize the entire module
14:51the campus network design is influenced
14:54by
14:54application environmental and
14:57infrastructure device characteristics
15:01an enterprise campus network is
15:02conducted hierarchically
15:05with building access building
15:07distribution
15:08and campus corridors an enterprise
15:12data center network is constructed
15:14hierarchically
15:15with data center access data center
15:19aggregation and data center
15:23core layers
15:26that's the end of this video i hope you
15:29have learned something from this
15:31thank you and see you on the next video
15:33have a great day

About this transcript

This page contains the full transcript of Designing Basic Enterprise Campus Networks Part 3 by Santelmo, generated from the public captions YouTube serves with the video. The transcript has 1,693 words across 379 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.

What you can do with it

Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to translate the transcript into 100+ languages.

Free YouTube transcript tool

YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, translation to 100+ languages, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.