0:22 hi this is david voss ccie11372
0:23 ccie11372
0:25 and in this video you're going to learn
0:27 about the osi model
0:31 in preparation for your cisco ccda exam
0:33 first i will teach you about the osi
0:34 model and then i'm going to give you
0:37 some challenges within the video
0:39 so that you can make sure you've
0:41 absorbed what you need to know for the
0:44 ccda exam
0:46 let's just do a quick overview of the
0:48 osi model before we dig in
0:51 the open system interconnection
0:52 reference model
0:54 is a seven layer model used in networking
0:56 networking
0:59 the model specifies layer by layer how
1:01 information from an application on a
1:03 network device
1:06 moves from the source to the destination
1:08 using a physical medium
1:09 and then how it interacts with the
1:11 software application
1:14 on that specific network device
1:16 so the osi model defines the network
1:19 functions required for sending data and
1:21 divides them into seven unique
1:25 categories the physical layer data link
1:28 layer network layer transport layer
1:30 session layer
1:32 presentation layer and then the
1:34 application layer you're going to get to
1:37 know each of these layers in detail in
1:38 this video
1:40 the upper three layers are concerned
1:43 with application issues such as the user
1:45 interface for data formatting
1:47 and then the lower four layers relate to
1:49 transport issues such as data
1:51 transmission and the physical
1:53 characteristics of the network
1:55 the osi model is a key concept in the
1:57 networking industry and you must know it
2:00 by heart in each of the layers
2:02 in detail because it plays a very
2:05 important role in the design phase of a
2:09 network using this modular approach
2:12 obviously you need to know it as well
2:15 for for troubleshooting issues as well
2:17 so the overall goals of the
2:19 osi model are to enhance
2:21 interoperability and functionality
2:23 between different applications and
2:25 vendors so for example
2:28 a cisco router can also communicate with
2:29 a juniper router
2:31 or an application
2:33 that is running on a network that
2:37 supports ip can communicate to another
2:39 network that happens to be running let's
2:43 say apple talk the osi model ensures
2:46 that everybody can communicate together
2:49 because it is based on and requires that
2:50 players on the network
2:53 adhere to set standards at each layer of
2:55 the osi model
2:57 so as you can see here
2:59 here are the seven detailed layers of
3:02 the osi model and i created this chart
3:04 for you and you can download it from
3:06 howtonetwork.com as well
3:08 this chart will help you study there are
3:10 many charts out there so feel free to
3:12 google osi model
3:14 and maybe find the one that works best
3:15 for you
3:17 but this one really does lay it out it
3:19 shows you all seven layers one through seven
3:21 seven
3:23 then the name of that specific layer so
3:26 you will need to memorize that for sure
3:28 and then the responsibilities
3:30 for each layer i give you a high level
3:32 of overview of each layer's responsibilities
3:34 responsibilities
3:36 and then the functions so
3:38 what is its function what's it supposed
3:40 to be doing
3:42 what is it supposed to be supporting
3:45 and then i give you some examples
3:48 of how those functions are actually put
3:50 into use
3:53 or actually defined
3:56 and then next is the data type
3:58 the terminology that is used to describe
4:00 the data then when it's at that level of
4:03 the osi model
4:05 and then finally the devices
4:08 that are actually participating
4:12 at that specific layer of the osi model
4:14 the fact is if you memorize this chart
4:16 you're going to be well on your way to
4:18 passing your ccda exam
4:20 but that being said we still need to
4:22 dive much deeper so you have a
4:24 comprehensive foundation of the osi
4:26 model you'll see how i have it color coded
4:27 coded
4:30 the top three layers five six and seven
4:32 generally these are the layers that
4:35 really tie in with the application
4:38 itself and a lot of application specific
4:41 information is set here
4:44 now the lower four layers typically are
4:46 considered more of the networks layers
4:47 when you think of actual networking
4:49 although all these layers participate in networking
4:50 networking
4:52 when you're talking to a network professional
4:54 professional
4:56 ninety percent of their job is spent on
5:00 layers one through four uh 95 percent of
5:01 their job probably is working at layers
5:03 one through four
5:05 and if there is troubleshooting in the
5:06 osi model
5:09 oftentimes uh between layer four and
5:12 five is where the handoff would would be
5:14 between the network team troubleshooting
5:16 versus the application team troubleshooting
5:17 troubleshooting
5:19 so if the network team for example
5:21 if they can say
5:24 you know what we can confirm that
5:26 traffic is passing over the physical
5:28 layer we can see that it's being routed
5:30 at layer three and we can see it's being
5:33 received by the tcp port
5:35 we've done our job we've transferred
5:37 your data you your port has sent and
5:38 received it
5:40 um that's where they would hand it off
5:42 and then the application team would
5:43 start saying
5:44 all right well now that we've now that
5:46 we've received the data
5:49 are we actually handling it correctly
5:51 so the color coding there should help you
5:53 you
5:55 so let's go ahead and get granular let's
5:59 learn about these these layers in detail
6:01 and let's start with actually let's
6:03 start with the application layer
6:15 everything at this layer is application specific
6:17 specific
6:18 that is this layer supports the
6:21 application in the end user processes
6:23 but also then defines who the
6:26 communication partners are
6:27 quality of service and user authentication
6:29 authentication
6:31 all of these application specific
6:34 settings are determined here
6:36 and will be dealt with at the lower
6:39 layers of the osi model
6:42 this layer provides application services
6:44 for such thing as file transfers email
6:46 email
6:49 and other networked software services
6:52 next is the presentation layer
6:55 this layer provides independence from
6:57 differences in data representation
6:59 such as encryption
7:02 by translating from application to the
7:05 network format and vice versa so it's
7:06 the intermediary
7:08 between the application
7:11 and the lower layers of the osi osi model
7:12 model
7:15 so this layer works to transform data
7:18 into the form that the application layer
7:20 can accept
7:22 this layer also formats and encrypts data
7:23 data
7:26 to be sent across the network
7:27 which provides freedom from
7:29 compatibility issues
7:38 the session layer establishes terminates
7:41 or manages connections between applications
7:42 applications
7:44 so the session layer will actually set
7:46 up and then coordinate and then
7:48 terminate a conversation
7:51 or dialogue between the applications at
7:53 each end of the conversation over the network
7:54 network
7:57 so it deals with session and connection coordination
7:58 coordination
8:00 now once we go ahead and scroll over to
8:02 the examples of each of these layers i
8:03 think these are going to look very
8:06 familiar to you
8:09 examples of applications that run at
8:12 layer 7 are telnet or email or a web browser
8:18 the presentation layer surely also looks
8:20 familiar to you in the examples given
8:24 file types such as jpeg or mpeg or mp4
8:27 all of these serve as compression types or
8:28 or
8:32 ways that the data is actually handled
8:33 and then the session layer these should
8:36 look familiar to to you as well such as
8:39 sql communications or windows operating
8:42 systems communications so you can see
8:44 there are things that you already know
8:45 about you just didn't know where they
8:48 fit in the osi model now all these data types
8:50 types
8:52 are considered a part of the application
8:54 stream so when we talk about data type
8:56 and devices you know when we get down to
8:58 the network layers these are going to be
9:00 a bit more unique but all of these three
9:02 layers what they have in common is that
9:04 they're a part of this application
9:06 stream which is why i say this is kind
9:09 of the d mark point between
9:12 the network and the application when
9:14 troubleshooting does occur or when
9:15 you're designing
9:19 oftentimes these higher layers
9:21 are designed
9:28 now let's go ahead and take a look at
9:30 the first four layers
9:33 of the osi model and these will probably
9:35 be the ones that look more familiar to
9:38 you in your day-to-day job or in your
9:39 studies because
9:42 this is where a lot of the very specific
9:43 network tasks
9:49 the transport layer ensures that there
9:53 is a transparent communication process
9:55 or transfer of data between the end
9:58 systems or hosts so it takes care of
10:01 error recovery and flow control
10:04 to ensure that the data transfer has
10:11 layer 4 is the transport layer and that
10:14 obviously defines ports such as tcp or
10:15 udp ports
10:18 so for example if we have a
10:19 a
10:22 pc that is communicating to a website
10:24 it's communicated communicating to that
10:31 and let's say it has multiple brows
10:33 let's say the user has multiple browsers
10:35 open they are communicating over and
10:37 over again over port 80. now how does
10:39 the website or websites know how to
10:41 communicate back to the user
10:44 well the user has his own port numbers
10:46 and they're all different
10:48 that way he can maintain three different
10:51 conversations at the same time to let's
10:53 say three different servers over port 80
10:56 and they can communicate back to the laptop
10:58 laptop
11:01 by communicating to individual ports
11:03 in this case we'll just use an example 65009
11:05 65009
11:13 and at this layer 2 five this is where
11:15 firewalls participate so let's say we
11:17 have a firewall here that's allowing
11:20 port 80. any traffic that's coming in
11:23 for let's say port 21 that will be
11:24 blocked the firewall will not allow it
11:27 based on the port number but any traffic
11:29 destined for port 80 the firewall will
11:32 allow it to come in
11:34 so for example if users need to get to 443
11:35 443
11:37 and they will not be able to unless the
11:41 firewall administrator enables port 443
11:44 on that firewall and then when they try
11:47 to communicate to port 443 it will work
11:50 so firewalls play a key role in
11:53 maintaining security at layer 4.
11:55 the network layer provides the routing
11:59 technologies it uses the logical paths
12:01 throughout the network to ensure that
12:03 data is forwarded to the correct location
12:05 location
12:06 so such thing as
12:09 ip addressing and subnetting
12:14 now the routed layer is probably the
12:15 most well-known layer especially if
12:18 you're in networking and this actually
12:21 makes sure that packets for example here
12:24 are packet destined for 172 31 1.1
12:26 is received by the router but the router
12:27 then knows what to do with it at this
12:29 layer it then
12:31 asks well what interface do i need to
12:34 forward this out of and it will then
12:37 choose based on the layer 3 information
12:39 of the osi model what port to send it
12:48 the data link layer data packets are
12:51 encoded and decoded into bits
12:53 so it's the intermediary between the
12:56 network and physical layer
12:58 it furnishes transmission protocol
13:00 knowledge and manages and handles errors
13:03 at the physical layer including flow
13:06 control and frame synchronization
13:07 as you know switches normally
13:09 participate at layer 2
13:12 and it is broken into two sections the
13:14 mac sub layer
13:16 and the llc sub layer now you know the
13:20 mac sub layer probably very well
13:21 because if you're looking at mac
13:23 addresses on a switch for example when
13:26 you're troubleshooting
13:28 this is the layer that
13:29 is assisting with your troubleshooting
13:31 methodology so for example we pull up a
13:33 mac address
13:35 and we take a look at the mac address in
13:36 the switch
13:38 this is the sub layer that we we are
13:39 referring to
13:41 the llc layer is going to allow the
13:43 communication between layer 2 and layer
13:46 3 and layer 1. it's the it's going to
13:48 allow that communication flow between
13:50 those two layers
13:52 and then finally
13:54 the physical layer this layer conveys
13:56 the actual bit stream that is the
13:59 electrical impulse light or radio signal
14:01 through the network at the electrical or
14:03 mechanical level
14:05 so it provides the hardware means of
14:08 sending and receiving data on a carrier
14:11 and it includes defining the cable type
14:13 network interface cards and any other
14:19 so at the physical layer this is
14:21 actually where the bits are
14:22 are
14:25 heading onto the wire so literally
14:29 1 0 1 0 etc etc
14:30 are hitting
14:31 the wire
14:34 so at this layer all of the other layers
14:36 from two through seven all of that information
14:37 information
14:41 is now transmitted very simply as binary
14:43 on or off
14:45 over the wire and then when it reaches
14:48 the destination this will be decoded by
14:51 the upper layers as appropriate so
14:53 obviously now that we see these binary
14:54 numbers hitting the wire we can
14:56 appreciate what the osi model actually
14:58 does for us it take it can take this information
15:00 information
15:02 can pass it all the way back up to an
15:09 so now that you've learned about the
15:11 first four layers of the osi model let's
15:12 go ahead and take a look at what
15:14 actually operates at these layers specifically
15:16 specifically
15:17 a lot of it is a lot of this is going to
15:20 look very familiar i'm sure
15:22 so some examples of what's actually
15:24 working at layer one is one example
15:27 would be cat6 cabling which surely
15:29 you've worked with in the past
15:31 but again these are just examples so it
15:32 could be
15:36 a network interface card it could be
15:39 any type of transport
15:42 that is your physical layer
15:44 next at the data link layer
15:45 this should
15:46 next is data link layer this should look
15:50 familiar it's broken into the llc and
15:52 the mac sub layers obviously mac
15:55 addresses are something you know about
15:56 but now you know where it fits within
15:58 the osi model
16:00 next on layer 3
16:03 obviously ip or apple talk but also the
16:07 routing protocol such as ospf or bgp
16:09 these are all operating at layer three
16:11 and then layer four is some examples are
16:14 your tcp or udp ports the many different
16:16 ports that are used as the channels for
16:20 communications between applications
16:22 now when data is passing through each of
16:25 these layers it does have a unique signifier
16:26 signifier
16:28 so at the physical layer you've already
16:29 learned that it's a binary digit it's
16:31 one or zero
16:34 at layer two we call them frames
16:37 layer three we consider them packets
16:40 and layer four is considered a segment
16:42 these are all terms you should know for
16:44 your ccda exam
16:46 and finally here are some examples of
16:48 network devices that run at each of
16:51 these layers so at layer one
16:52 hubs run at layer one they're
16:54 essentially repeaters
16:56 network interface cards
16:59 layer two switches
17:03 layer three routers and firewalls
17:05 surely you will do some reading about
17:07 layer 3 switches as well but really this
17:09 is where the routing functionality comes
17:11 or if a firewall is operating at this
17:14 level it's filtering on a layer 3
17:15 address only
17:18 not the tcp or udp port number and then
17:20 layer four would be typically firewalls
17:23 are operating at this level and this is
17:25 where the filtering is occurred solely
17:28 on the port
17:31 so be prepared to pause the video
17:32 here's your challenge this chart is
17:35 going to disappear in about 10 seconds
17:38 what i want you to do is to the best
17:40 your ability on a piece of paper
17:43 fill out columns one two
17:45 two 4
17:47 4
17:48 and 7.
17:50 i want to know
17:52 the layer
17:55 the name of the layer
17:58 the functions within that layer what
18:00 it's responsible for and then the
18:03 devices that run at that layer
18:06 do your best columns one two
18:07 two four
18:09 four
18:10 and seven
18:12 go ahead and pause the video at this time
18:18 so let's pull the chart up again how did
18:21 you do go ahead and pause the video with
18:30 now if you didn't get 100 my advice to
18:32 you is to keep studying because the osi
18:35 model is something you have to know
18:38 for your ccda exam but obviously you
18:39 need to know it to be a good engineer as well
18:40 well
18:43 in this video which is complemented the
18:46 ccda study guide which how to network
18:47 provides for you
18:51 you've received a good overview of the
18:54 osi model layer by layer
18:56 my suggestion to you is do not move on
18:58 to anything else
19:00 until you've mastered this
19:03 because everything else you learn
19:04 will ultimately
19:07 in some way shape or form relate back to
19:09 this model
19:10 i wish you the best of luck in your studies
19:11 studies
19:37 hi this is david voss ccie 11372 and in
19:38 this video
19:40 we're going to cover the unique
19:43 attributes of networking devices
19:45 this video is the companion to the how
19:48 to network ccda study guide
19:50 you will receive instruction on the
19:52 individual network devices
19:54 but you will also be challenged with
19:56 some exercises to make sure the
20:03 when it comes to networking technology
20:04 it's important to understand the
20:07 different products that cisco offers for
20:09 different solutions
20:11 especially when designing lan and wan solutions
20:13 solutions
20:16 if you have already watched video 1-1
20:18 which covers the osi model
20:20 then you will appreciate how network
20:24 devices can play a very unique role in a network
20:25 network
20:28 if you haven't watched video 1-1 then i
20:30 encourage you to do so because this
20:34 information will build off of that video
20:37 the three most common network devices in
20:40 use today are routers switches and hubs
20:42 but i will also add a fourth which are firewalls
20:43 firewalls
20:45 as they may not necessarily be
20:48 considered devices used for quote
20:50 unquote networking
20:52 but they can in fact participate in
20:54 layer 3 routing of traffic
20:56 and they most certainly filter traffic
21:00 based on layer 3 and 4 qualities
21:02 so let's work our way up through the osi model
21:03 model
21:06 starting at layer one to learn about the
21:16 at layer one we begin with hubs
21:18 became necessary when the need to
21:21 connect more than two devices first arose
21:22 arose
21:24 because a cable can only connect two endpoints
21:26 endpoints
21:28 hubs are network devices that operate at
21:32 this layer and connect multiple devices
21:34 which are all on the same local area network
21:35 network
21:38 unlike switches hubs do not have any
21:41 intelligence and therefore they do not
21:43 process packets in any way they simply
21:45 forward them
21:47 their main function is to send all the
21:50 data received on a port to all other ports
21:51 ports
21:53 so devices
21:55 receive all the packets that traverse a
21:57 specific network
21:59 even if they are not addressed to them
22:00 for this reason
22:03 hubs are also called repeaters
22:06 hubs work fine in very small offices
22:08 or at someone's desk
22:11 but imagine if you have 20 50 or even
22:14 100 devices on a network
22:16 using hubs is certainly not efficient
22:19 so in order to improve performance
22:21 especially from a bandwidth and security standpoint
22:22 standpoint
22:24 local area networks are divided into
22:26 multiple smaller lands
22:29 called collision domains
22:30 and these collision domains are
22:34 interconnected by a lan switch
22:36 switches have some intelligence unlike
22:39 hubs because they send data to a port
22:41 only if the data needs to reach that
22:43 particular segment
22:46 when using switches only the destination device
22:47 device
22:49 in a communication flow receives the
22:52 data sent by the source device
22:54 however multiple conversations between
22:56 devices connected to a switch can happen
22:59 simultaneously as you see here
23:02 these are each unique flows that the
23:04 switch is processing it's receiving it
23:07 on one port and forwarding it out the
23:09 other another
23:12 and forwarding it out a different port
23:14 see the difference between this and hubs
23:16 is that it's receiving one port sending
23:19 it out one port versus all ports
23:22 switching intelligence functions based
23:24 on the mac table
23:26 the mac table contains mac address to
23:30 port mappings and is populated as
23:32 traffic traverses the switch the switch
23:34 uses that information to build the mac
23:36 address table
23:38 in this example a frame is received by
23:41 the switch but the switch does not know
23:43 the location or does not have in its mac
23:46 address table the location for this frame
23:47 frame
23:49 therefore it sends the frame out to all ports
23:50 ports
23:53 now ultimately the server receives it
23:55 and then forwards it back
23:57 and with that information the switch can
23:59 then build the mac table
24:01 so the next time
24:04 that a frame is destined for server c
24:07 the switch will know exactly which port
24:09 it is off of and it will not have to
24:15 now notice that the most important
24:18 feature of a switch is the separation of
24:20 collision domains
24:22 all the devices on a switch
24:25 may be on separate collision domains per port
24:26 port
24:28 but note that they are all a part of the
24:30 same broadcast domain
24:33 it is routers that separate broadcast
24:36 domains and switches that separate
24:42 routers operate at layer 3 of the osi
24:45 model and thus they use layer 3 addresses
24:46 addresses
24:48 the primary purpose of a router
24:51 is to forward traffic to the correct subnet
24:53 subnet
24:55 so a router is consistently looking up
24:58 destination paths in its routing table
25:00 to understand where to forward the
25:01 traffic to
25:05 that is out which specific port
25:07 now as i said earlier
25:10 routers break up broadcast domains
25:12 switches do not do that
25:15 so for example each port on this router
25:18 is its own separate broadcast domain
25:20 this ensures network efficiency so that
25:22 broadcasts are not forward throughout
25:24 the entire network when they do not have
25:26 to be
25:29 generally speaking
25:32 for each interface you have a specific
25:34 subnet is assigned to that interface and
25:36 therefore broadcasts for that subnet are
25:40 limited to that interface only
25:42 now as a reminder switches typically
25:44 connect to routers and those
25:46 ensure the segmentation of collision domains
25:53 so for example
25:55 if there was an endpoint
25:57 sending a packet to destination address
26:01 192 168 1.10
26:03 the router would receive it
26:04 and then it would check its routing table
26:06 table
26:07 in this case it looks in its routing
26:10 table and it sees that it knows of a
26:16 and that it is located off of ethernet 0.
26:17 0.
26:19 therefore the packet comes in
26:21 the router says i am aware of that destination
26:22 destination
26:25 and then forwards it out ethernet 0
26:29 and the host then receives the packet
26:32 at a high level this is the primary
26:34 function of a router
26:36 now let's say
26:38 a router does not have many entries in
26:40 the routing table only a default gateway
26:42 and that default gateway in this case is
26:45 off of the serial interface serial zero zero
26:46 zero
26:48 that means any packet
26:50 regardless of destination that is sent
26:53 to the router will be forwarded
26:59 now this is a very basic description of
27:02 how routers work routers can use static
27:04 routes but that's not ideal especially
27:06 when you have networks that are quite large
27:07 large
27:10 so in this case we have six routers all interconnected
27:12 interconnected
27:14 and to try to manage static routes for
27:16 all of the possible paths
27:18 administratively not only would be a burden
27:19 burden but
27:20 but
27:22 if you had certain static routes
27:25 pointing to specific routers and beyond
27:28 that router there was a failure of an interface
27:29 interface
27:31 due to the static nature of the routes
27:33 the routers downstream would not really
27:35 understand the true topology
27:38 therefore routers speak to one another
27:42 and they do that using routing protocols
27:44 and the in this case the entire routing
27:47 domain all six routers can be a part of
27:50 a routing protocol such as ospf
27:52 eigrp or any of the other routing protocols
27:53 protocols
27:55 and in this way they are communicating
27:57 back and forth
28:00 layer 3 information
28:02 so for example if an interface went down
28:04 on a router that would that information
28:07 would be forwarded to its neighbors and
28:08 its neighbors would then forward that
28:11 information to all of their neighbors
28:14 therefore the entire domain would
28:16 quickly be updated with this information
28:19 if you effectively have a routing
28:21 protocol enrolled out to your entire campus
28:23 campus really
28:25 really
28:28 no static routes should be required
28:30 and i want to emphasize one more point
28:33 no static routes are desired
28:35 static routes should only be used as a
28:37 last resort
28:39 next let's talk about firewalls now
28:41 please understand firewalls are not
28:44 typically considered a networking device
28:46 when people think of networking devices
28:48 they generally think of hubs switches
28:49 and routers
28:52 but the fact is firewalls do operate at
28:54 layer 3 and layer 4
28:57 and they can be used as routed devices
28:59 although it's not always the ideal there
29:01 definitely are situations where you are
29:04 going to find firewalls acting as
29:10 now as we talk about firewalls let's see
29:12 how firewalls fit in the big picture
29:13 let's just recap everything we've
29:15 learned so
29:17 first you've learned about the layer one
29:19 device which is a hub
29:22 hubs are normally found on desktops or
29:25 in very small offices
29:27 hubs generally
29:29 connect up to switches
29:31 switches are your aggregation points and remember
29:32 remember
29:36 they segment collision domains
29:40 switches then connect into routers
29:43 and routers are your aggregation points
29:45 for your separate subnets
29:47 and they often will connect to for example
29:49 example
29:51 exterior networks or in this case the internet
29:53 internet
29:55 so the firewall
29:59 protects the network from these exterior networks
30:00 networks
30:03 so the firewall is the protection point
30:05 for the networks one possible way of
30:08 doing it there are many ways of doing it
30:11 is to simply put the firewall
30:13 and directly connect it into the router
30:16 so that all traffic from the router must
30:18 go through the firewall
30:20 and then on a separate nick on the
30:23 firewall you would connect that to the
30:24 internal switch now again there's many
30:26 ways you can do this
30:28 but you'll get the general idea that all
30:30 layer 3 traffic
30:33 must go through this firewall
30:35 the firewall will have set rules at
30:37 layer 3
30:39 only allowing specific layer 3
30:42 conversations through the firewall or
30:42 or
30:45 what is generally seen more often
30:48 is layer 4 rules on the firewall only
30:51 allowing specific ports inbound
30:54 so let's say if you had an internal
30:57 web server that you wanted users on the
30:59 internet to hit
31:01 you could allow only that traffic
31:04 inbound to port 80 to hit this specific
31:08 ip this specific web server
31:10 now that being said
31:12 firewalls do this filtering function and
31:14 the reason they're in this video as a
31:16 network device
31:18 is that sometimes
31:20 it can occur
31:22 where a firewall can actually act as a
31:24 routed device
31:28 so if you had a dmz off of the firewall
31:30 for example
31:42 and its own switch
31:45 you're running an actual ecommerce site
31:47 and you have your web server here
31:49 because you have a lot of traffic coming in
31:50 in
31:52 and you want to make sure that you keep
31:54 it secure so you have your web server
31:57 your ids
32:00 which monitors all traffic etc
32:02 in this case
32:04 the traffic's coming into the router the
32:05 firewall is actually actually making a
32:06 decision here
32:09 do i forward it inbound or do i forward
32:11 it over to a separate nic over to this dmz
32:12 dmz
32:14 so although you won't see firewalls
32:17 listed as network devices per se
32:19 the fact is sometimes they very much can
32:21 play a part in the network and the
32:23 routing decisions
32:25 and actually there are even times where
32:28 firewalls can run routing protocols it's
32:30 not the norm but there are times where
32:31 you will see
32:34 bgp especially configured
32:35 configured
32:37 to a firewall
32:39 security experts would probably take
32:41 issue with that but that doesn't mean
32:43 you won't see it
32:45 so therefore there's your overview of
32:46 firewalls understanding that they
32:49 operate at both layer 3 and layer 4 and
32:52 then again they can operate as actual
32:53 forwarding devices making routing
32:57 decisions on the network
32:58 so why do you see a blank screen well
33:00 it's your term please get a blank piece
33:04 of paper and write down vertically one
33:06 two three and four
33:09 and then write down which devices match
33:12 which layer of the osi model
33:14 go ahead and do that now write down one
33:16 two three and four on your piece of
33:18 paper and write down which network devices
33:19 devices match
33:20 match
33:34 so how did you do
33:36 as you can see here are the layers of
33:38 the osi model and the network hardware
33:41 that matches with each layer
33:42 you're going to need to know this for sure
33:44 sure
33:46 as you proceed in your ccda studies but
33:52 so just to recap what we've learned
33:54 you've gone through
33:56 layer one two three and four of the osi
33:59 model and specifically you can see
34:02 how the network devices work within each
34:04 of these layers of the osi model so
34:06 again if you are not an expert at the
34:10 osi model yet please revisit video one
34:13 one and study it because as you can see
34:14 everything you're beginning to learn is
34:15 based off of that
34:18 hubs are at layer one switches work at
34:19 layer two
34:21 just a note switches can also work at
34:22 layer three there are such thing as
34:24 layer three switches that have some
34:26 routing functionality um
34:27 um
34:29 routers and firewalls work at layer three
34:30 three
34:34 and then firewalls work at layer four
34:36 this provides you a really solid
34:38 foundation moving forward so that when
34:41 you do hear about hubs switches routers
34:42 and firewalls
34:44 you understand where they fit in the osi
34:47 model and what their primary task is on
35:16 hi this is david voss
35:18 cci11372 and in this video you are going
35:21 to learn about network types
35:24 specifically wide area and local area networks
35:25 networks
35:28 let's go ahead and dig in
35:31 and learn about local area networks
35:34 local area networks are local computer
35:36 networks used to communicate between
35:37 host systems
35:39 generally for sharing information such
35:42 as documents audio files video email
35:44 they have limited reach and they connect
35:47 devices generally in the same building
35:49 or the same campus if you're using fiber
35:52 to extend the local area network
35:53 usually they're private and belong
35:55 solely to the companies in which they
35:57 are deployed
35:59 now in the past the topologies were ring bus
36:00 bus
36:04 mesh and star but today the most common
36:07 topology is switched ethernet
36:09 the different lan technologies available
36:11 today that are the most popular are
36:14 ethernet fast ethernet
36:15 gigabit ethernet
36:18 and now 10 gigabit ethernet is becoming
36:19 more and more popular
36:22 and then finally what is obviously very
36:24 popular at this point is wireless lan
36:26 where you can reach up to 600 megabits
36:27 per second
36:31 under the 802.11n specification
36:33 now at the higher layers of the osi
36:37 model it's the tcpip is the standard
36:41 which has replaced net buoy ipx spx and
36:44 apple talk among others although
36:46 if you travel around enough you
36:48 certainly are going to see some of these
36:50 older protocols
36:52 still out there so let's just go ahead
36:53 and draw out a typical local area
36:55 network first you're going to have an
36:57 access layer switch and if you remember
36:59 from typical design there's core
37:01 distribution and access layer well we're
37:03 in the access layer now
37:04 and the access layer switch is going to
37:08 connect out to let's say pcs or
37:09 or
37:12 ip based phones
37:13 these are all things that can be
37:16 connected into the local area network
37:19 including wireless access points
37:21 so the local area network can be extended
37:22 extended
37:24 as you can see here to a wireless access point
37:25 point
37:28 and then other systems wireless systems
37:31 can communicate such as laptops
37:33 or mobile phones
37:35 can be a part of can connect to the
37:38 local area network as well
37:40 now this access switch connects up to a
37:42 distribution switch
37:44 and the distribution switch ultimately
37:46 connects back into the core
37:48 and this would all still be considered
37:52 part of the local area network
37:54 but once we connect into a router then
37:56 we start talking about what the edge is
37:58 so we're moving off the edge into the
37:59 router then the wind would be off the
38:02 router itself
38:05 so there's kind of a dmarc point
38:06 if you think of local area network and
38:08 it's right about here between the router
38:11 and the core switch
38:13 now this distribution layer switch would
38:15 often be a layer three switch this would
38:18 this would be where your gateway is and
38:20 i bring this up because systems on your
38:22 local area network generally are on the
38:23 same subnet so in this case 192.168.1.0.24
38:31 and then here we have 1.10 1.11. now the
38:33 wireless access point may be 1.12 for
38:35 management and maybe that wireless
38:37 access point extends out another let's
38:40 say 10 dot network that assigns ip
38:42 addresses to anything that's wireless
38:44 these even those are even though these
38:47 are different subnets this would all be
38:50 considered a part of your local area network
38:55 so as you can see whether it's wired or
38:57 wireless that is your
39:00 lan and then the when is anything off of
39:02 your router and we'll talk about winds
39:03 in a minute
39:05 now the wide area network is used to
39:08 connect lands or other types of networks
39:10 together we'll briefly cover some of the
39:12 other types of networks as well
39:14 it allows users and computers in one
39:17 location to communicate with users and
39:20 computers in other locations
39:22 these are usually private networks
39:24 and they're usually built for one
39:30 but that being said
39:32 if you have an internet connection and
39:34 most businesses do nowaday nowadays
39:36 nowadays
39:38 there is a public connection from an organization
39:39 organization
39:41 to the internet
39:43 and at the end of each wan connection a
39:46 router connects the lan on one side with
39:53 now again you can connect over a private
39:56 network or you can connect over the internet
39:57 internet
39:59 as you can see there are five primary
40:02 types of wide area network technologies
40:04 lease line circuit switching packet switching
40:06 switching
40:08 connection oriented packet switching
40:12 connection lists and then cell relay
40:15 some are still very popular and some are
40:17 not used much at all anymore but that
40:19 being said you should be aware of all five
40:20 five
40:23 for your ccda exam
40:25 let's begin with discussing least line
40:28 now at least line very simply
40:31 would be connecting two routers
40:34 over a dedicated circuit so in this case
40:38 let's say chicago over to washington dc
40:40 a wide area can network a wide area
40:43 network connection is one single circuit
40:45 purchased by the company no other traffic
40:46 traffic
40:48 can go on that circuit except for the
40:50 traffic from this company
40:52 and it's connecting two local area
40:54 networks so yes
40:57 this is a very secure method of
40:59 transferring data between chicago
41:01 and dc
41:02 and this connection will be the wide
41:05 area network
41:07 next let's talk about
41:09 circuit switching now circuit switching
41:12 was once very popular and is still often used
41:12 used
41:14 for backup solutions so circuit
41:16 switching provides
41:19 temporary data communications over a
41:21 wide area network
41:24 which requires a call setup procedure
41:26 but that being said you will not be
41:28 charged for using the circuit when it's
41:30 not in use
41:32 so a circuit switching you would have
41:38 and then if interesting traffic hit one
41:45 and that is traffic destined for the
41:48 other location it would then place a
41:50 call or set up the wide area network connection
41:52 connection
41:54 and once that session was initiated
41:56 the traffic would then flow over the circuit
42:05 next let's talk about packet switched
42:08 connection oriented
42:10 some popular types of implementations of
42:12 this are frame relay
42:15 x25 and
42:18 more recently mpls
42:21 now in this case let's say we have one
42:22 hub site
42:25 and three remote sites you can set up a pvc
42:27 pvc
42:29 permanent virtual circuit which means
42:31 that that circuit is always up regardless
42:33 regardless
42:36 or an svc switch virtual circuit where
42:38 if there's interesting traffic
42:39 it will bring up
42:42 a virtual circuit and then forward
42:44 traffic and then tear it down again
42:46 now that being said
42:47 all this traffic is floating over a
42:50 provider network so
42:50 so
42:53 making sure that your
42:56 circuits are secure is going to be key
42:58 working with your vendor to ensure
43:00 security is a high priority not only for them
43:01 them
43:03 but additional measures that you can
43:06 take on your end to ensure all data
43:08 transmissions are secure over their
43:11 network where many customers are sharing it
43:13 it
43:15 next there is packet switched connectionless
43:17 connectionless
43:18 you certainly know of this or you
43:20 certainly use this already
43:22 whenever you connect to the internet
43:25 you're using this type of service
43:27 the system is relying on the i p
43:30 forwarding of routers on the network
43:32 it's not so concerned about the exact
43:34 path it takes
43:36 rather it just makes sure it relies on
43:38 the upper layer protocols to make sure
43:40 that the traffic reaches reaches its
43:44 destination so in this case we have an
43:46 internet edge
43:48 connecting to an internet service provider
43:49 provider
43:52 and let's say we have another location
43:53 with an edge connected to another
43:55 internet service provider
43:58 now how it gets there we don't know i
44:00 mean there we can't it can't be guaranteed
44:01 guaranteed
44:03 the path it will take it'll be going
44:05 over the internet
44:07 and um certainly we can look up how it's
44:10 getting there and how it's returning
44:12 but it can take many different paths
44:14 to get there
44:16 so that means traffic might not arrive
44:18 in order it may not be taking the path
44:20 you expect and you don't have ultimate
44:23 control over that now that being said if
44:25 you want more control and you want more
44:27 security you can connect two devices
44:29 into the internet and create your own
44:31 little private wide area network connection
44:32 connection
44:35 by creating tunnel interfaces on your
44:38 routers and then creating a gre tunnel or
44:39 or
44:41 an ipsec tunnel
44:44 which would encrypt the data
44:45 and to you it would look like a
44:47 point-to-point connection even though
44:49 it's going over the internet you're not
44:50 exactly sure which router just going over
44:51 over
44:53 but according to your systems and your
44:56 routing protocols it could look like a
44:58 point-to-point connection
45:00 and that's one very popular way of
45:01 saving money
45:03 is by rolling out
45:06 secure communications
45:11 and then finally there is cell relay now
45:16 this was very popular about 15 years ago
45:19 but due to the increase in bandwidth and
45:21 availability of ethernet and other options
45:23 options
45:25 this fell by the wayside due to the
45:27 large overhead but that being said
45:29 you should be aware of it
45:32 with atm it is a fixed cell technology
45:33 technology
45:37 so all the cells are the same size
45:41 and data is then placed inside
45:42 and is forwarded
45:45 so think of a train heading down the tracks
45:46 tracks
45:48 all the compartments are the same size
45:51 data is placed in it's very efficient
45:52 that way
45:54 but that being said there is a lot of
45:56 overhead because you don't always need
45:58 to use
46:00 that size of cell so here's what you
46:02 learned you learned about local area and
46:05 wide area networks
46:07 these are the two network types that you
46:10 are going to need to understand in and
46:13 out to pass your ccda exam
46:15 so this just got you started in the very basics
46:16 basics
46:17 and i encourage you to watch the rest of
46:18 the videos
46:20 so that you master the knowledge
46:22 necessary to understand all the
46:24 components of local and wide area networks
46:25 networks
46:28 enough information so that you can pass
46:30 your ccda exam
46:56 hi this is david voss ccie 11372
46:57 and in this video we're going to cover
47:00 tcpip fundamentals
47:02 as well as we're going to discuss udp
47:05 and icmp to bundle it in there for you
47:07 as you prepare for your ccda exam
47:08 so let's begin
47:10 begin
47:12 in this video you will specifically
47:13 learn about the different types of
47:17 headers used on the network the ip tcp
47:19 and udp header as well as how they
47:21 operate on the network
47:23 you will then review how routing works
47:25 and some of the issues faced or tools
47:28 used when routing
47:30 so let's begin
47:33 the tcp stack maps to the network and
47:36 transport layers of the osi model
47:39 ip or internet protocol has become the
47:41 de facto standard for network
47:48 what you see before you is the ip header
47:49 you will need to know the functions for
47:52 each of the fields you see before you
47:54 let me cover some of the functions that
47:56 you will most likely need to know for
47:57 your exam and in real world troubleshooting
47:59 troubleshooting
48:01 first there's the version field
48:04 the version field indicates that it is
48:07 ipv4 in this instance with a value of 0
48:10 1 0 0.
48:12 then there's the type of service field
48:14 this field is
48:16 commonly referred to as the type of
48:19 service byte it has 8 bits used to set
48:21 quality of service markings
48:24 and specifically within this
48:28 field is dscp the six left most bits are
48:30 used for dscp
48:32 which obviously commonly is associated
48:35 with quality of service marking
48:38 next is the ip flags field this is a
48:39 three bit field
48:42 the second bit of this field is the df
48:45 or do not fragment fragment bit
48:47 and that indicates that a packet should
48:49 not be fragmented
48:51 then there's the time to live field
48:53 this is an eight bit field that is
48:56 decremented by one each time a packet is
48:59 routed from one ip network to another if
49:02 ttl ever reaches zero the packet is discarded
49:04 discarded
49:06 the protocol field which is an eight bit
49:09 field specifies what kind of data
49:12 type of data is encapsulated
49:13 in the packet
49:16 tcp and udp are common protocols
49:18 identified by this field
49:20 finally the source address field which
49:22 is a 32-bit field indicating the source
49:24 of the ipv4 packet and then the
49:26 destination address field which again is
49:30 a 32-bit destination destination address
49:32 which indicates the destination
49:34 for that packet
49:41 first you have the version field just
49:44 like ipv4 but in ipv6
49:48 the value is 0 1 1 0.
49:50 the traffic class field
49:53 performs the same function as the type
49:56 of service field in ipv4
50:00 header the flow label field
50:02 is used by a router to use a specific
50:05 outbound connection for a traffic flow
50:07 if a router has multiple outbound connections
50:08 connections
50:10 the hot limit field probably sounds
50:13 familiar it's the same as the ipv4 ttl field
50:15 field
50:16 and then you have your source and
50:18 destination address field which is
50:22 similar to ib ipv4 headers 32-bit source
50:24 address field but in this case because
50:28 it's ipv6 it's 128 bits for both
50:31 obviously source and destination
50:33 next let's move on to the tcp segment
50:35 header here are some of the fields you
50:37 will certainly need to know you have the
50:40 source port field which is the 16-bit
50:43 field indicating the sending port number
50:45 and the destination port field again a
50:48 16-bit field so for example
50:50 if you connect to howtonetwork.com
50:52 you're connecting
50:55 to a destination port of 80 which is the
50:58 tcp port for http the sequence number
51:00 field is a 32-bit field indicating the
51:03 amount of data sent during a tcp session
51:05 the sending party uses this field to
51:07 make sure the receiving party actually
51:09 receive the data
51:11 the receiving party uses the sequence
51:14 number from this field as the basis for
51:16 the acknowledgment number
51:18 in the next segment that it sends back
51:20 to the sender and then the window field
51:23 which is a 16-bit field it specifies the
51:25 number of bytes a sender is willing to
51:27 transmit before receiving an
51:29 acknowledgement from the receiver and
51:31 we're going to follow this up in a few
51:33 minutes as we talk more about tcp window sizes
51:34 sizes
51:36 now that you've learned about what is in
51:38 a tcp header you need to understand the
51:41 basics of how tcp initiates traffic
51:44 flows over a network it's not complex
51:45 but you certainly need to know it if
51:46 you're tested on it
51:49 the process of setting up a tcp session
51:52 involves a three-way handshake
51:53 step one
51:56 the session initiator sends a sin packet
51:59 or a send message to the target host
52:00 and then
52:03 the host the target host acknowledges
52:05 the receipt of that sin message and
52:08 sends an act or acknowledgement message
52:10 and it also sends a sin message of its own
52:12 own
52:15 finally the session initiator receives
52:17 the send message from the target and
52:20 again it acknowledges receipt by sending
52:22 an ack message
52:25 and therefore you have a tcp session established
52:26 established
52:28 you need to know each of those steps one
52:30 two and three for your exam
52:32 earlier you learned about the window
52:34 field so let's circle back and talk
52:35 about that a little bit
52:39 tcp communication uses windowing
52:42 one or more segments can be sent at one time
52:43 time
52:45 the receiver acknowledges the receipt of
52:48 all segments in a window with an
52:50 acknowledgement now tcp can use a
52:52 sliding window
52:54 the window size can begin with one
52:56 segment and then if there's a successful
52:58 acknowledgement of that segment the
53:01 window size doubles to two segments
53:02 and then if those two segments are
53:05 received the next window can contain
53:06 four segments
53:09 this increase in window size continues
53:11 until the receiver does not acknowledge
53:13 successful receipt of all segments
53:15 within a certain time frame
53:18 known as the round-trip time the other
53:21 iplayer for transport protocol is udp
53:23 udp is considered to be an unreliable
53:26 protocol because it lacks all of the
53:28 features of tcp there's no sequence
53:31 numbering no window size no acknowledgements
53:33 acknowledgements
53:34 you can see here the header is quite simple
53:35 simple
53:38 it contains only source and destination
53:39 port numbers
53:42 and then a udp checksum and then segment
53:46 length so why use udp well it's best for
53:48 servicing applications that need to
53:50 maximize bandwidth and do not require
53:53 acknowledgments such as video streams or
53:56 audio and in fact the primary protocol
53:58 used to carry voice and video traffic
54:00 over networks is rtp
54:01 rtp
54:04 real-time transport protocol and that's
54:07 a layer 4 protocol that is encapsulated
54:09 inside of udp
54:11 now that you have a good understanding
54:13 of the individual headers in the tcpip stack
54:14 stack
54:16 cisco wants you to understand how this
54:18 traffic actually traverses the network
54:20 so let's go ahead and use this basic example
54:22 example
54:24 we have a pc that wants to send data
54:27 over to a server
54:28 the first step in this process is that
54:31 the pc will compare its ip address and
54:34 subnet mask to that of the destination
54:37 the pc by doing this is aware that the
54:40 destination ip address is on a remote
54:42 network and it cannot directly reach it
54:45 so the pc understands it needs to send
54:49 this packet now to its default gateway
54:51 it doesn't do that automatically yet it
54:53 needs to know actually who the default
54:54 gateway is
54:57 the pc needs to know the layer 2 address
54:59 of the default gateway so it sends an
55:00 arp request
55:03 for router 1's mac address and then it
55:06 receives a response
55:08 the pc adds router 1's mac address to
55:11 its arp cache and then now it can send
55:13 the data in a frame destined for server
55:17 1 to the default gateway because it has
55:19 the matching layer 2 and layer 3
55:21 information needed to forward that
55:24 request or to forward that message onto
55:26 the gateway
55:28 router 1 then receives the frame sent
55:30 from the personal computer
55:32 and looks at the ip header
55:35 and remember the ttl field it decrements
55:37 that field by one
55:39 now if the ttl field happened to be zero
55:41 which is not but if it happened to be
55:44 zero the router would discard the frame
55:46 and then send a time exceeded icmp
55:50 message back to the pc
55:52 the ttl is not decremented to zero here
55:56 so router one checks its routing table
55:58 and then understands that the best path
56:02 to re to reach network 192.168.4.0 is
56:03 is
56:07 the wan connection or over serial one
56:10 so it then forwards that message over to router2
56:12 router2
56:14 note that it does not need to do an arp
56:16 request because this is a serial
56:19 interface and serial interface types do
56:22 not have mac addresses
56:25 so then router 2 receives the frame and
56:27 again it decrements the ttl and the ip header
56:29 header
56:30 looks at the ip header
56:31 and then
56:34 determines where is this destination
56:36 network the destination network is
56:38 directly connected off the ethernet interface
56:39 interface so
56:40 so
56:42 router 2
56:44 needs to understand
56:47 now that it has the destination what the
56:50 mac address is for that destination
56:53 and it sends out an arp request
56:55 receives the information back the arp reply
56:56 reply
56:58 from server one
57:00 and then router two forwards the frame
57:03 out it's fast ethernet interface to
57:04 server one
57:07 so that's a really basic example
57:09 but cisco wants you to understand all
57:11 the individual steps and how routing
57:13 actually works
57:15 now let's dig even deeper into what's
57:17 occurring on the network and an
57:19 important concept that cisco wants you
57:21 to know which is mtu or maximum
57:22 transmission unit
57:25 an mtu refers to the largest packet size
57:27 supported on a router interface and
57:30 typically 1500 is the common value
57:33 smaller mtu sizes result in more
57:35 overhead because more packets have to be sent
57:37 sent
57:39 but if you're sending data over slower
57:40 speed links
57:43 large mtu values could cause delay for latency
57:44 latency
57:47 sensitive traffic
57:48 when you have high speed connections let
57:51 me give you an example of let's say a
57:54 private interconnect between two servers
57:56 what happens is administrators often
57:58 enable jumbo frames
58:01 those are frames over the standard size
58:03 or the standard mtu size so that more
58:06 data can be forwarded in fewer number of
58:08 packets and therefore
58:10 fewer headers that routers have to
58:12 process on the network or systems need
58:14 to process on the network
58:16 now if you're going to run a network
58:18 you're going to need to troubleshoot it
58:20 and icmp messages are something that you
58:22 probably are going to be tested on
58:25 in the ccnp route exam
58:27 icmp is most often associated with the
58:30 ping utility and you use that obviously
58:31 you've used that in the past to check connectivity
58:33 connectivity
58:35 but it has many other roles beyond ping
58:37 it uses a variety of message types as
58:39 you can see here
58:41 but there's two that it appears cisco
58:43 wants you to focus on the first is
58:44 destination unreachable which you're
58:46 probably already aware of but if a packet
58:47 packet
58:50 enters a router which is destined for an
58:51 address that the router has no idea how
58:53 to reach the router will let the sender
58:55 know by sending a destination
58:58 unreachable icmp message back to the senator
58:59 senator
59:01 the other message that you may not be
59:04 aware of is the redirect a host may have
59:06 routing information
59:08 that will help it reach a particular
59:10 destination network
59:12 so it'll send it to that next top ip address
59:13 address
59:16 but network conditions can change
59:19 and a different next hop ip address may
59:21 need to be used
59:22 in that case the original next hop
59:26 router can let the host know to use a
59:28 different path by sending a host
59:31 redirect icmp message
59:33 so you've learned a lot in this video
59:35 when you started it you probably thought
59:37 it would be a simple review but surely
59:38 you've picked up quite a bit of information
59:40 information
60:07 hi this is david voss ccie 11372 and in this video we will be covering
60:08 and in this video we will be covering the first of two videos on layer 2
60:11 the first of two videos on layer 2 technologies
60:12 technologies we will start with spanning tree
60:15 we will start with spanning tree in this video you will learn about
60:17 in this video you will learn about spanning tree
60:18 spanning tree bpdus or bridge protocol data units
60:22 bpdus or bridge protocol data units stp port states
60:24 stp port states cost and
60:26 cost and priority stp port types
60:30 priority stp port types and then finally bpdu timers
60:33 and then finally bpdu timers all of this information is not only
60:34 all of this information is not only going to help you on your ccda exam
60:37 going to help you on your ccda exam but will certainly make you a better
60:39 but will certainly make you a better engineer as well
60:41 engineer as well so let's begin
60:43 so let's begin stp is defined in the ieee 802.1d
60:47 stp is defined in the ieee 802.1d standard and its primary purpose is to
60:49 standard and its primary purpose is to make sure that your network is loop free
60:52 make sure that your network is loop free it operates by making the following
60:54 it operates by making the following assumptions that all links are
60:56 assumptions that all links are bi-directional and that they can in fact
60:58 bi-directional and that they can in fact send and receive bpdus
61:00 send and receive bpdus and that the switch itself
61:02 and that the switch itself is able to regularly receive process and
61:05 is able to regularly receive process and send
61:11 bpdus now all switches that reside in the same stp domain regularly regularly
61:14 the same stp domain regularly regularly exchange these bridge protocol data
61:17 exchange these bridge protocol data units these messages with one another
61:24 and ultimately the network uses the information from
61:25 the network uses the information from these data units
61:27 these data units to determine the network topology and
61:29 to determine the network topology and the flows of traffic
61:32 the flows of traffic the topology of an active switch network
61:34 the topology of an active switch network is determined by the following three
61:36 is determined by the following three variables the unique mac address or the
61:39 variables the unique mac address or the switch identifier associated with each
61:42 switch identifier associated with each switch
61:43 switch the path cost to the root bridge
61:45 the path cost to the root bridge associated with each port on the switch
61:48 associated with each port on the switch and the port identifier
61:50 and the port identifier all these play a big role in the
61:52 all these play a big role in the decision making
61:53 decision making of how traffic will flow on a network
62:03 some basic facts bpdus are sent to the stp multicast destination address as you
62:06 stp multicast destination address as you see here
62:07 see here and by default they are sent every two
62:09 and by default they are sent every two seconds
62:10 seconds now there are two type of data units
62:12 now there are two type of data units that we should know of
62:14 that we should know of configuration bpdus and tcns or topology
62:18 configuration bpdus and tcns or topology change notification bpd use
62:21 change notification bpd use now switch has determined the best
62:22 now switch has determined the best configuration bpdu
62:24 configuration bpdu based on the following criteria
62:28 based on the following criteria which is lowest root bridge id which is
62:30 which is lowest root bridge id which is based on root bridge id
62:32 based on root bridge id root path cost to the root bridge
62:34 root path cost to the root bridge sender bridge id and sender port id
62:41 before we can continue we should really understand
62:43 understand how things work in spanning tree
62:44 how things work in spanning tree regarding just the ports themselves so
62:46 regarding just the ports themselves so spanning tree ports so in a typical
62:49 spanning tree ports so in a typical environment we're going to have one root
62:50 environment we're going to have one root switch and we have three switches
62:52 switch and we have three switches connected here switch one two and three
62:55 connected here switch one two and three and switch one is the root and this is
62:57 and switch one is the root and this is gonna help us understand how
62:59 gonna help us understand how spanning tree
63:01 spanning tree designates ports so
63:04 designates ports so in spanning tree the root never has root
63:07 in spanning tree the root never has root ports because root is always the
63:08 ports because root is always the forwarding port that is closest to the
63:10 forwarding port that is closest to the root bridge so this root only has
63:12 root bridge so this root only has designated ports switch 2 and switch 3
63:14 designated ports switch 2 and switch 3 both have root ports that is the
63:16 both have root ports that is the forwarding port that is closest to the
63:18 forwarding port that is closest to the root bridge in terms of path cost
63:21 root bridge in terms of path cost and then
63:22 and then switch 3 has a designated port this is
63:24 switch 3 has a designated port this is one forwarding port on each lan segment
63:27 one forwarding port on each lan segment and then switch 2 is the alternate port
63:30 and then switch 2 is the alternate port this is the best alternate path to the
63:32 this is the best alternate path to the root bridge on that very same segment
63:34 root bridge on that very same segment segment
63:36 segment next to switch 3 we're going to connect
63:37 next to switch 3 we're going to connect switch 4.
63:39 switch 4. switch 3 is going to have a designated
63:41 switch 3 is going to have a designated port but it's going to also here have a
63:44 port but it's going to also here have a backup port a backup port
63:47 backup port a backup port is a backup redundant path to a segment
63:50 is a backup redundant path to a segment where another bridge port already
63:52 where another bridge port already connects
63:56 the backup port applies only when a single switch has two links to the same
63:59 single switch has two links to the same segment
64:11 now we can better understand the following slide at the completion of
64:14 following slide at the completion of configuration bpdu exchange the
64:16 configuration bpdu exchange the following results a root switch is
64:19 following results a root switch is elected for the entire spanning tree
64:20 elected for the entire spanning tree domain
64:22 domain and a root port is elected on every
64:24 and a root port is elected on every non-root switch in the spanning tree
64:26 non-root switch in the spanning tree domain
64:28 domain as you will remember a root port is a
64:30 as you will remember a root port is a forwarding port that is the closest to
64:31 forwarding port that is the closest to the root bridge in terms of path cost
64:35 the root bridge in terms of path cost a designated switch is elected for every
64:37 a designated switch is elected for every land segment and a designated port is
64:40 land segment and a designated port is elected on the designated switch for
64:42 elected on the designated switch for every segment
64:44 every segment and if we and if you will remember a
64:46 and if we and if you will remember a designated port is a forwarding port
64:49 designated port is a forwarding port for every lan segment the chosen
64:51 for every lan segment the chosen forwarding
64:52 forwarding port then finally based on all this
64:55 port then finally based on all this information and all these calculations
64:57 information and all these calculations loops are avoided in the network
65:11 now topology change bpdus play a key role
65:12 role in handling changes in the active
65:13 in handling changes in the active topology
65:19 they are proactively originated by any switch and sent upstream toward the root
65:22 switch and sent upstream toward the root bridge
65:23 bridge providing information that would be key
65:26 providing information that would be key to keeping the network loop free
65:32 let's next let's talk about spanning tree port states
65:39 802.1d has five different port states disabled blocking listening learning and
65:43 disabled blocking listening learning and forwarding
65:44 forwarding let's talk about each of these in depth
65:54 when a switch port is in blocking mode the port is not transmitting or
65:56 the port is not transmitting or receiving data
65:57 receiving data and it's prevented from transmitting
65:59 and it's prevented from transmitting bpdus
66:01 bpdus packets arriving on the port are not
66:02 packets arriving on the port are not learned by the bridges filtering
66:04 learned by the bridges filtering database
66:05 database a block port though can receive bpdus
66:09 a block port though can receive bpdus and is included in the spanning tree
66:11 and is included in the spanning tree algorithm calculation
66:13 algorithm calculation so
66:14 so ultimately it could be used to transfer
66:16 ultimately it could be used to transfer data but it's not it's blocking at this
66:19 data but it's not it's blocking at this point
66:32 next let's talk about the port state of listening
66:37 a listening port is not transmitting or receiving data and packets on the port
66:39 receiving data and packets on the port are not learned by the bridges filtering
66:41 are not learned by the bridges filtering database
66:42 database but it can transmit and receive bbdus
66:46 but it can transmit and receive bbdus and is included in the spanning tree
66:47 and is included in the spanning tree algorithm calculation
66:50 algorithm calculation the listening state is a transitional
66:51 the listening state is a transitional state
66:52 state that will change to the learning state
66:54 that will change to the learning state after a settable time of period which we
66:57 after a settable time of period which we know as the forward delay timer
67:11 in a learning state the port is not transmitting or receiving data but it
67:13 transmitting or receiving data but it can receive and transmit bpd use
67:16 can receive and transmit bpd use it is included in the spanning tree
67:18 it is included in the spanning tree algorithm calculation
67:20 algorithm calculation and the packets arriving on the port are
67:21 and the packets arriving on the port are in fact learned by the bridges filtering
67:23 in fact learned by the bridges filtering database
67:24 database this also is a transitional state that
67:27 this also is a transitional state that will automatically change to a
67:28 will automatically change to a forwarding state after a settable period
67:30 forwarding state after a settable period of time which is called the forward
67:32 of time which is called the forward delay timer
67:42 and as appropriate let's move on to the forwarding state
67:47 the forwarding state is the only state in which data is being transmitted and
67:49 in which data is being transmitted and received by the port
67:51 received by the port it can receive and transmit bpdus and is
67:54 it can receive and transmit bpdus and is included in the spanning tree algorithm
67:56 included in the spanning tree algorithm calculation
67:57 calculation the packets arriving on the port are
67:59 the packets arriving on the port are learned by the bridge's filtering
68:01 learned by the bridge's filtering database
68:11 finally let's talk about the disabled port state
68:16 a port is disabled or in a disabled state
68:17 state when the port is not transmitting or
68:19 when the port is not transmitting or receiving data packets or bpdus and is
68:22 receiving data packets or bpdus and is not considered in the spanning tree
68:24 not considered in the spanning tree algorithm
68:30 so as you can see once a port is enabled by a network administrator or through
68:31 by a network administrator or through initialization
68:33 initialization it goes through a process or these
68:34 it goes through a process or these different port states
68:38 different port states the port will move into a listening and
68:40 the port will move into a listening and learning and ultimately a forwarding
68:42 learning and ultimately a forwarding state if the spanning tree algorithm
68:45 state if the spanning tree algorithm has chosen it as a root port or a
68:48 has chosen it as a root port or a designated port if spanning tree has not
68:51 designated port if spanning tree has not chosen the port
68:52 chosen the port as a root or designated port
68:54 as a root or designated port it will put the port into a blocking
68:57 it will put the port into a blocking state
69:02 you know that also as an alternate port or a backup port
69:10 now spanning tree uses the bridge id to uniquely identify each switch and
69:13 to uniquely identify each switch and it's actually used to assist in the
69:14 it's actually used to assist in the election of a spanning tree root bridge
69:16 election of a spanning tree root bridge unless of course the root bridge has
69:18 unless of course the root bridge has been manually configured
69:20 been manually configured in the 802.1d standard each vlan
69:23 in the 802.1d standard each vlan requires a unique bridge id
69:26 requires a unique bridge id so spanning tree root bridge election
69:28 so spanning tree root bridge election following initialization all switches
69:30 following initialization all switches initially assume that they are root but
69:33 initially assume that they are root but the switch with the highest bridge
69:34 the switch with the highest bridge priority is elected this the spanning
69:37 priority is elected this the spanning tree root bridge
69:38 tree root bridge now all things being equal if nothing's
69:40 now all things being equal if nothing's been configured and all things set are
69:42 been configured and all things set are set to default
69:44 set to default then the root bridge is chosen
69:46 then the root bridge is chosen by the lowest order mac address
69:50 by the lowest order mac address during route election no traffic is
69:53 during route election no traffic is forwarded over any switch in the same
69:55 forwarded over any switch in the same spanning tree domain until things are
69:57 spanning tree domain until things are stabilized and there's a loop free
69:58 stabilized and there's a loop free topology
70:04 spanning tree uses cost and priority values to determine the best path to the
70:06 values to determine the best path to the root bridge
70:07 root bridge in the 802.1d specification it assigns a
70:11 in the 802.1d specification it assigns a 16-bit default port cost values to each
70:14 16-bit default port cost values to each port now
70:16 port now note this before we dig into the actual
70:19 note this before we dig into the actual port values
70:20 port values the port cost is globally significant
70:24 the port cost is globally significant and is included in all propagated bpdus
70:28 and is included in all propagated bpdus by default the lower number the lower
70:31 by default the lower number the lower costs are more preferred
70:33 costs are more preferred so you're going to see this in a second
70:34 so you're going to see this in a second as we draw this out
70:36 as we draw this out but in the event that multiple ports
70:38 but in the event that multiple ports have the same path cost then spanning
70:41 have the same path cost then spanning tree will consider the port priority the
70:44 tree will consider the port priority the default value is 128
70:47 default value is 128 but you should note that the port
70:49 but you should note that the port priority is locally significant
70:51 priority is locally significant and not included in spanning tree
70:53 and not included in spanning tree protocol bpdus
70:59 so the spanning tree protocol default port cost
71:01 port cost it depends on the interface speed and
71:03 it depends on the interface speed and you'll notice here from this chart
71:06 you'll notice here from this chart that the higher the speed the lower the
71:08 that the higher the speed the lower the cost and this comes into play
71:10 cost and this comes into play when spanning tree is actually trying to
71:12 when spanning tree is actually trying to calculate
71:13 calculate the best path to root
71:15 the best path to root so for example
71:18 so for example let's draw out a network with five
71:20 let's draw out a network with five switches
71:22 switches and we're going to bring each of these
71:23 and we're going to bring each of these switches online
71:25 switches online and lets spinning tree decide which is
71:27 and lets spinning tree decide which is the best path
71:30 the best path and which ports should be root which
71:32 and which ports should be root which ports should be designated ports
71:34 ports should be designated ports so they are all
71:40 interconnected and let's pretend we are powering them all on
71:43 powering them all on now let's say the switches aren't all of
71:45 now let's say the switches aren't all of the same speed so
71:47 the same speed so for example
71:48 for example we have a 10 megabit switch
71:55 100 megabit switch and we'll just say all the interfaces on the switch
71:57 all the interfaces on the switch are that speed
71:59 are that speed a one gigabit switch
72:02 a one gigabit switch 100 megabit switch here
72:18 so as you remember from the chart these numbers should start to look
72:21 these numbers should start to look the cost of two is assigned to a 10
72:23 the cost of two is assigned to a 10 gigabit interface cost of four a one
72:26 gigabit interface cost of four a one gigabit interface
72:28 gigabit interface cost of a 19 100 megabit interface
72:31 cost of a 19 100 megabit interface and a cost of 100 to a 10 megabit
72:33 and a cost of 100 to a 10 megabit interface
72:36 interface and spanning tree will calculate as you
72:39 and spanning tree will calculate as you can see
72:40 can see it's doing right here spanning tree is
72:42 it's doing right here spanning tree is calculating best path
72:45 calculating best path to
72:46 to to the root and let's say we've let's
72:49 to the root and let's say we've let's say we've assigned the one gigabit
72:50 say we've assigned the one gigabit switch as our we've manually set it
72:52 switch as our we've manually set it spanning tree would then calculate
72:54 spanning tree would then calculate and as you can see here from the 10
72:57 and as you can see here from the 10 megabit switch through the 100 meg over
72:59 megabit switch through the 100 meg over to the one gig
73:00 to the one gig it's a hundred and the total cost is
73:03 it's a hundred and the total cost is 123.
73:05 123. and then the other path the total cost
73:07 and then the other path the total cost is 119. that's the lower cost
73:10 is 119. that's the lower cost that would be the root port
73:12 that would be the root port because that would be the preferred path
73:21 so as you know we've already talked about some of these
73:22 we've already talked about some of these ports but spanning tree elects two types
73:24 ports but spanning tree elects two types of ports that are used to forward bpd
73:26 of ports that are used to forward bpd use
73:27 use and that's the root port
73:29 and that's the root port now note the root switch never has any
73:31 now note the root switch never has any root ports because
73:32 root ports because this is the port that provides the best
73:34 this is the port that provides the best path to the root bridge
73:36 path to the root bridge so every other switch is going to have
73:38 so every other switch is going to have one root port that's the best path to
73:40 one root port that's the best path to the root bridge the root bridge will not
73:42 the root bridge the root bridge will not have a root port for obvious reasons
73:46 have a root port for obvious reasons the root path cost is calculated based
73:48 the root path cost is calculated based on the
73:49 on the cumulative cost to the root
73:59 the designated port actually points away from the spanning tree root and it sits
74:01 from the spanning tree root and it sits in a blocking state
74:03 in a blocking state all ports on the root are designated
74:05 all ports on the root are designated ports because the root path cost will
74:07 ports because the root path cost will always be zero
74:10 always be zero the designated port
74:11 the designated port is the best port on a segment
74:14 is the best port on a segment so for example
74:16 so for example on a segment you will have
74:18 on a segment you will have on a segment where there is no root
74:20 on a segment where there is no root switch you will have one designated port
74:22 switch you will have one designated port and all the other ports will be either
74:24 and all the other ports will be either alternate or backup ports
74:33 we talked about quite a bit about bpd use in
74:35 use in in video lesson three module one but
74:38 in video lesson three module one but let's build upon that further
74:40 let's build upon that further bpdus includes several timers that play
74:42 bpdus includes several timers that play an integral role in the operation of the
74:44 an integral role in the operation of the protocol
74:45 protocol and the modification of these timers
74:47 and the modification of these timers should always be made at the root bridge
74:50 should always be made at the root bridge there are three configurable spanning
74:51 there are three configurable spanning tree timer values which is hello
74:54 tree timer values which is hello forward delay and max age
74:56 forward delay and max age the hello time is two seconds by default
75:00 the hello time is two seconds by default forward delay is 15 seconds by default
75:03 forward delay is 15 seconds by default and max age is 20 seconds by default
75:12 so here's what you've learned you've learned about the foundation of spanning
75:14 learned about the foundation of spanning tree which is bpdus
75:17 tree which is bpdus port states
75:18 port states cost and priority and the stp port types
75:22 cost and priority and the stp port types so this provides you a solid foundation
75:25 so this provides you a solid foundation for designing your networks and your
75:28 for designing your networks and your ccda exam good luck in your studies
75:56 hi this is david voss ccie 11372 and in this video you're going to learn
75:57 and in this video you're going to learn about the layer 2 technology vlans
76:01 about the layer 2 technology vlans so here's what you'll learn you'll learn
76:02 so here's what you'll learn you'll learn about vlans and then you're going to
76:04 about vlans and then you're going to learn specifically about what makes
76:06 learn specifically about what makes voice vlans unique so let's go ahead and
76:10 voice vlans unique so let's go ahead and begin our video with just some of the
76:11 begin our video with just some of the basics about what vlans are
76:19 what exactly is a vlan well cisco says it's a group of end stations with a
76:20 it's a group of end stations with a common set of requirements
76:23 common set of requirements using vlans allows you to put
76:26 using vlans allows you to put many different devices in many different
76:28 many different devices in many different locations on the same
76:30 locations on the same logical network on the same layer 2
76:32 logical network on the same layer 2 network
76:34 network in the past without vlans
76:36 in the past without vlans you would have to rely upon
76:39 you would have to rely upon simple hardware solutions but a vlan
76:41 simple hardware solutions but a vlan allows you to virtualize your layer 2
76:44 allows you to virtualize your layer 2 segment
76:46 segment vlans are usually associated by the same
76:49 vlans are usually associated by the same subnet so normally devices on a vlan
76:52 subnet so normally devices on a vlan are are sharing the same subnet
76:55 are are sharing the same subnet and and with this in mind
76:58 and and with this in mind they're sharing the same broadcast
76:59 they're sharing the same broadcast domain that is the norm
77:02 domain that is the norm and then vlans must be routed to
77:05 and then vlans must be routed to communicate with other vlans so it is a
77:07 communicate with other vlans so it is a true layer 2 segment
77:10 true layer 2 segment a vlan is not going to be able to
77:11 a vlan is not going to be able to communicate with another vlan
77:14 communicate with another vlan unless it is passed through a layer 3
77:17 unless it is passed through a layer 3 device which can route it
77:19 device which can route it now there are two types of switch port
77:22 now there are two types of switch port types
77:23 types for vlan membership that we need to
77:24 for vlan membership that we need to understand
77:26 understand and the first is
77:27 and the first is the access port
77:29 the access port now access ports can only belong to a
77:31 now access ports can only belong to a single vlan now when you think of an
77:33 single vlan now when you think of an access port
77:34 access port it's pretty much probably what you think
77:36 it's pretty much probably what you think of it's usually for end devices like a
77:38 of it's usually for end devices like a workstation
77:39 workstation or a server
77:41 or a server it is a device that is an end station
77:43 it is a device that is an end station and again accessport can only belong to
77:46 and again accessport can only belong to a single vlan
77:48 a single vlan typically used to connect end devices
77:51 typically used to connect end devices and there are two methods to assign
77:53 and there are two methods to assign ports
77:54 ports uh to vlans
77:56 uh to vlans for these access ports the first which
77:58 for these access ports the first which is by far the the most popular
78:01 is by far the the most popular is the static vlan assignment so an
78:04 is the static vlan assignment so an administrator actually doing it and then
78:06 administrator actually doing it and then dynamic vlan assignment
78:09 dynamic vlan assignment which is done by a server so let's dig a
78:11 which is done by a server so let's dig a little bit more into that into those two
78:13 little bit more into that into those two concepts
78:15 concepts so
78:16 so when we have a static vlan assignment
78:19 when we have a static vlan assignment the network administrator is actually
78:20 the network administrator is actually manually configuring a switch port to be
78:23 manually configuring a switch port to be a part of a vlan
78:25 a part of a vlan the network administrator is saying is
78:27 the network administrator is saying is programming the port to say you are
78:29 programming the port to say you are going to be an access port
78:31 going to be an access port and you're going to be associated with
78:32 and you're going to be associated with this specific vlan
78:34 this specific vlan now you can do this dynamically and this
78:37 now you can do this dynamically and this is not as popular but there is something
78:41 is not as popular but there is something called a vlan management policy server
78:44 called a vlan management policy server which can assign a desired vlan to users
78:46 which can assign a desired vlan to users connecting to a switch
78:48 connecting to a switch we don't need to get much deeper than
78:50 we don't need to get much deeper than that
78:51 that for your exam but you need to you do
78:53 for your exam but you need to you do need to know these two methods
78:56 need to know these two methods now there's another type of port that we
78:58 now there's another type of port that we need to understand to understand the
79:00 need to understand to understand the concept of vlans and that is trunk ports
79:02 concept of vlans and that is trunk ports and trunk ports are used to carry data
79:05 and trunk ports are used to carry data from multiple vlans
79:07 from multiple vlans so
79:08 so access ports only allow communication
79:12 access ports only allow communication from
79:13 from one end device over a specific vlan
79:16 one end device over a specific vlan well ultimately if you're hosting many
79:18 well ultimately if you're hosting many vlans
79:21 vlans this traffic's gonna need to be able to
79:22 this traffic's gonna need to be able to communicate
79:23 communicate um throughout your network uh so that
79:26 um throughout your network uh so that they're not limited
79:27 they're not limited uh limited by a hardware device so your
79:30 uh limited by a hardware device so your vlan may your vlans may be spread
79:33 vlan may your vlans may be spread throughout
79:34 throughout many floors or
79:36 many floors or maybe even many buildings
79:38 maybe even many buildings trunk ports allow you to carry data from
79:41 trunk ports allow you to carry data from all these different vlans between all
79:44 all these different vlans between all your different hardware devices
79:47 your different hardware devices now there are some standard vlan numbers
79:49 now there are some standard vlan numbers and ranges you should know specifically
79:51 and ranges you should know specifically let's focus on two 1001 these vlans are
79:55 let's focus on two 1001 these vlans are created and used and deleted on all
79:58 created and used and deleted on all cisco catalyst switches
80:00 cisco catalyst switches and another one that you should really
80:02 and another one that you should really focus in on is the range of 1006 to
80:05 focus in on is the range of 1006 to 4094.
80:07 4094. these are
80:08 these are extended this is an extended range of
80:11 extended this is an extended range of vlans for ethernet vlans only
80:15 vlans for ethernet vlans only now you may be asked about these other
80:16 now you may be asked about these other ranges but i would focus in on
80:19 ranges but i would focus in on vlan ranges two to one thousand and one
80:22 vlan ranges two to one thousand and one and one thousand six to four thousand
80:25 and one thousand six to four thousand ninety four
80:32 now we talked a little bit about vlan trunks earlier but let's just
80:36 trunks earlier but let's just hit upon let's just hit upon vlan trunks
80:38 hit upon let's just hit upon vlan trunks a little bit more so we can understand
80:40 a little bit more so we can understand it now again i want to remind you that
80:42 it now again i want to remind you that there is another video that is dedicated
80:44 there is another video that is dedicated solely to vlan trunks
80:47 solely to vlan trunks but let's just get a basic understanding
80:49 but let's just get a basic understanding here
80:50 here vlan trunks are used to carry data from
80:52 vlan trunks are used to carry data from multiple vlans which you already know
80:54 multiple vlans which you already know now there are two methods two protocols
80:57 now there are two methods two protocols that can be used
80:59 that can be used to build these trunks and the first is
81:02 to build these trunks and the first is inner switch link or isl
81:05 inner switch link or isl and that's a cisco proprietary protocol
81:08 and that's a cisco proprietary protocol that is used to preserve the source vlan
81:10 that is used to preserve the source vlan identification information
81:12 identification information for frames that traverse trunk links
81:15 for frames that traverse trunk links and then
81:16 and then there is i would say the more popular
81:18 there is i would say the more popular 802.1 q
81:20 802.1 q which is an open standard
81:23 which is an open standard and then it performs a little bit
81:25 and then it performs a little bit differently than the cisco proprietary
81:27 differently than the cisco proprietary protocol
81:29 protocol now the reason
81:30 now the reason 802.1q is so popular is you probably
81:33 802.1q is so popular is you probably understand that for obvious reasons
81:35 understand that for obvious reasons that if you want to trunk between
81:38 that if you want to trunk between two devices like one is cisco and one is
81:41 two devices like one is cisco and one is non-cisco
81:42 non-cisco you're able to do that
81:44 you're able to do that so
81:44 so this standard works very effectively and
81:47 this standard works very effectively and 802.1q is very popular but you will
81:50 802.1q is very popular but you will definitely be asked about isl and you
81:52 definitely be asked about isl and you will definitely be asked about the
81:54 will definitely be asked about the differences between isl and 802.1q
82:00 now so you've received a lot of information
82:03 so you've received a lot of information right now so let's go ahead and kind of
82:05 right now so let's go ahead and kind of draw out some of these concepts that
82:07 draw out some of these concepts that we've been talking about
82:10 we've been talking about so
82:12 so when we think of vlans we think first of
82:15 when we think of vlans we think first of we need to connect
82:16 we need to connect endpoints need to connect on a local
82:18 endpoints need to connect on a local area network so
82:20 area network so here we have
82:23 here we have four endpoints
82:29 and we have one switch and each of these endpoints
82:31 and each of these endpoints need to communicate and not all of them
82:33 need to communicate and not all of them need to communicate with with each other
82:36 need to communicate with with each other so let's say we have two workstations
82:41 so let's say we have two workstations and two servers
82:43 and two servers and we're gonna put this one workstation
82:45 and we're gonna put this one workstation in vlan 10 and this other workstation in
82:48 in vlan 10 and this other workstation in vlan 10
82:49 vlan 10 and then these two servers in vlan 2.
82:52 and then these two servers in vlan 2. these two servers are segmented on their
82:54 these two servers are segmented on their own vlan and as are the workstations
82:57 own vlan and as are the workstations they cannot communicate between each
82:58 they cannot communicate between each other
83:00 other between vlan 2 and 10
83:02 between vlan 2 and 10 but anything on vlan 10 can communicate
83:04 but anything on vlan 10 can communicate with vlan 10. now here's another
83:07 with vlan 10. now here's another dedicated vlan we'll say vlan 3 to a
83:09 dedicated vlan we'll say vlan 3 to a dedicated device
83:11 dedicated device now
83:12 now and here is a router so for any of these
83:14 and here is a router so for any of these vlans to communicate with one another
83:16 vlans to communicate with one another they need to pass through a layer 3
83:17 they need to pass through a layer 3 device so this this workstation that
83:20 device so this this workstation that from vlan 10 if it wants to communicate
83:23 from vlan 10 if it wants to communicate over to a server it needs to be routed
83:25 over to a server it needs to be routed and go through the router and passed
83:27 and go through the router and passed over to vlan 2.
83:30 over to vlan 2. um let's say you want to keep vlan 3
83:32 um let's say you want to keep vlan 3 devices
83:34 devices not accessible from the network you can
83:36 not accessible from the network you can prevent that
83:38 prevent that so here we have other devices on vlan 3
83:41 so here we have other devices on vlan 3 and we will say let's say this is a
83:42 and we will say let's say this is a back-end connection between two servers
83:44 back-end connection between two servers that we have no need to route it vlan 3
83:47 that we have no need to route it vlan 3 can be segmented from the entire network
83:50 can be segmented from the entire network nobody can reach it so there's some
83:51 nobody can reach it so there's some security built into vlans as well
83:54 security built into vlans as well now vlans can extend
83:56 now vlans can extend obviously over to other hardware
83:58 obviously over to other hardware platforms so this router is connected to
84:00 platforms so this router is connected to another switch
84:01 another switch and on this switch let's say that's in a
84:03 and on this switch let's say that's in a different building we have another
84:04 different building we have another device on vlan 2
84:06 device on vlan 2 another device
84:08 another device another endpoint
84:09 another endpoint on an access port to vlan 10
84:12 on an access port to vlan 10 and if they want to communicate over to
84:15 and if they want to communicate over to the other building let's say vlan 2 or
84:17 the other building let's say vlan 2 or vlan 10 they simply go over this trunk
84:20 vlan 10 they simply go over this trunk port you know that term
84:23 port you know that term goes over the trunk port and can
84:24 goes over the trunk port and can communicate over to
84:26 communicate over to the other sites
84:30 the other sites configuring a vlan is rather
84:31 configuring a vlan is rather straightforward
84:33 straightforward you simply go into configuration mode
84:36 you simply go into configuration mode and type in vlan
84:38 and type in vlan and for the sake of this example we're
84:40 and for the sake of this example we're assigning it number 10
84:42 assigning it number 10 and then normally you would name the
84:43 and then normally you would name the vlan so anybody logging in would
84:45 vlan so anybody logging in would understand what that vlan what the
84:47 understand what that vlan what the purpose of the vlan actually is so the
84:49 purpose of the vlan actually is so the purpose of this vlan is actually to host
84:51 purpose of this vlan is actually to host servers
84:52 servers um you can name it obviously anything
84:54 um you can name it obviously anything you want but in this case we'll just say
84:56 you want but in this case we'll just say servers and then you have the vlan build
85:00 servers and then you have the vlan build but you still need to assign ports to
85:01 but you still need to assign ports to that vlan
85:02 that vlan so you assign a port to a vlan by
85:05 so you assign a port to a vlan by actually going into interface
85:06 actually going into interface configuration mode and in this example
85:09 configuration mode and in this example it's fast ethernet 0 two
85:12 it's fast ethernet 0 two and then you need to make the ethernet
85:14 and then you need to make the ethernet port in access port now remember those
85:16 port in access port now remember those two port types that we're concerned
85:18 two port types that we're concerned about
85:18 about accessport and trunk port we're making
85:21 accessport and trunk port we're making this an access port
85:23 this an access port and then you enter in the command switch
85:26 and then you enter in the command switch port access vlan in the vlan you want it
85:29 port access vlan in the vlan you want it to participate in and let's say on fast
85:32 to participate in and let's say on fast ethernet 02 we have a server we're
85:34 ethernet 02 we have a server we're connecting so we're going to assign it
85:36 connecting so we're going to assign it to vlan 10
85:38 to vlan 10 and that is it that is it
85:42 and that is it that is it next let's learn about the unique
85:43 next let's learn about the unique attributes of voice vlans
85:50 a cisco ip phone provides a data connection for a user's
85:53 provides a data connection for a user's personal computer
85:55 personal computer in addition to voice data coming from
85:58 in addition to voice data coming from itself
85:59 itself so this allows one single ethernet
86:02 so this allows one single ethernet connection to be installed per user and
86:05 connection to be installed per user and makes maximum use of your ports
86:08 makes maximum use of your ports even though several different types of
86:11 even though several different types of data can pass over that port
86:13 data can pass over that port the voice and user pc ports always
86:16 the voice and user pc ports always function as access mode switch ports
86:20 function as access mode switch ports but the port that connects to the switch
86:24 but the port that connects to the switch that can operate as an 802.1q trunk
86:27 that can operate as an 802.1q trunk or it can operate as an access port
86:30 or it can operate as an access port now when bringing up a trunk between an
86:32 now when bringing up a trunk between an ip phone and a switch
86:34 ip phone and a switch this is normally negotiated
86:37 this is normally negotiated but you can specify that the ports at
86:39 but you can specify that the ports at both ends are brought up as an 802.1q
86:42 both ends are brought up as an 802.1q trunk
86:43 trunk now you could bring the switch port up
86:45 now you could bring the switch port up as an access port
86:47 as an access port but that would not allow you to segment
86:49 but that would not allow you to segment voice and data appropriately
86:52 voice and data appropriately the trunk allows you to segment voice
86:54 the trunk allows you to segment voice and data on separate vlans
86:57 and data on separate vlans and this would allow you to easily
86:59 and this would allow you to easily provide quality of service capabilities
87:02 provide quality of service capabilities to the voice traffic since it's already
87:04 to the voice traffic since it's already segmented
87:06 segmented to configure the iphone uplink you just
87:09 to configure the iphone uplink you just need to configure the switch port
87:11 need to configure the switch port where the phone connects
87:13 where the phone connects the switch then instructs the phone
87:16 the switch then instructs the phone to follow the mode that is selected
87:19 to follow the mode that is selected if an 802.1q trunk is needed the trunk
87:22 if an 802.1q trunk is needed the trunk is automatically negotiated by dtp and
87:25 is automatically negotiated by dtp and cdp
87:27 cdp so here's what you've learned you've
87:28 so here's what you've learned you've learned about vlans
87:30 learned about vlans and specifically what makes voice vlans
87:33 and specifically what makes voice vlans unique
87:34 unique and all of this information not only
87:36 and all of this information not only will help you with passing your ccda
87:38 will help you with passing your ccda exam
87:39 exam it will help you
87:40 it will help you design your networks moving forward
87:44 design your networks moving forward good luck in your studies
88:09 hi this is david voss ccie 11372 and in this video you're going to learn
88:11 and in this video you're going to learn basic layer 3 technologies
88:15 basic layer 3 technologies specifically you're going to learn the
88:16 specifically you're going to learn the basics of
88:17 basics of ipv4 and v6 addressing
88:21 ipv4 and v6 addressing and routing
88:23 and routing so let's go ahead and begin
88:26 so let's go ahead and begin network addresses are logical addresses
88:29 network addresses are logical addresses assigned when a device is placed in the
88:32 assigned when a device is placed in the network and change when the device is
88:34 network and change when the device is moved
88:35 moved network layer addresses have a
88:37 network layer addresses have a hierarchical structure
88:39 hierarchical structure comprised of two parts
88:41 comprised of two parts the network address and the host address
88:45 the network address and the host address logical addresses can be assigned
88:47 logical addresses can be assigned manually by the administrator or
88:49 manually by the administrator or dynamically via a dedicated protocol
88:52 dynamically via a dedicated protocol such as dhcp or dynamic host
88:55 such as dhcp or dynamic host configuration protocol
88:57 configuration protocol using a server on the network
89:01 using a server on the network all the devices in a network have the
89:03 all the devices in a network have the same network portion of the address
89:06 same network portion of the address but different host identifiers
89:13 routers analyze the network portion of ip addresses and compare them with
89:15 ip addresses and compare them with entries from its routing table
89:18 entries from its routing table if a match is found the packet is sent
89:20 if a match is found the packet is sent to the appropriate interface
89:29 ipv4 addresses are 32-bit numbers represented as strings of zeros and ones
89:33 represented as strings of zeros and ones for a more intuitive representation of
89:35 for a more intuitive representation of ipv4 addresses
89:37 ipv4 addresses the 32 bits can be divided into four
89:40 the 32 bits can be divided into four octet groupings separated by dots which
89:43 octet groupings separated by dots which is called dotted decibel notation
89:46 is called dotted decibel notation the octets can be converted into decimal
89:49 the octets can be converted into decimal numbers
89:51 numbers for example considering the following
89:54 for example considering the following for example consider the following
89:56 for example consider the following 32-bit string
89:58 32-bit string if you were to divide it into four
90:00 if you were to divide it into four octets it results in the following
90:02 octets it results in the following binary representation
90:05 binary representation this translates into an easy to read
90:07 this translates into an easy to read decimal representation of 192 168
90:11 decimal representation of 192 168 128.169
90:18 ipv4 addresses are categorized into five classes a b and c are used for
90:21 classes a b and c are used for addressing devices
90:23 addressing devices d is for multicast groups
90:26 d is for multicast groups and e is reserved for experimental use
90:29 and e is reserved for experimental use the first bits of the address define
90:32 the first bits of the address define which class it belongs to as illustrated
90:35 which class it belongs to as illustrated in this chart
90:36 in this chart knowing the class of an ipv4 address
90:39 knowing the class of an ipv4 address helps to determine which part of the
90:41 helps to determine which part of the address represents the network
90:43 address represents the network and which part represents the host bits
90:48 and which part represents the host bits ipv4 addresses can be classified into
90:50 ipv4 addresses can be classified into the following categories
90:52 the following categories there are public addresses which are
90:54 there are public addresses which are used for external communication
90:57 used for external communication private addresses which are reserved and
90:59 private addresses which are reserved and used only internally within a company
91:02 used only internally within a company the private address ranges are defined
91:05 the private address ranges are defined by rfc 1918
91:08 by rfc 1918 and include the following ranges
91:16 so far we've been talking about classful networks
91:17 networks class less addressing allows class a b
91:20 class less addressing allows class a b and c addresses to be divided into even
91:23 and c addresses to be divided into even smaller networks called subnets
91:27 smaller networks called subnets this results in a larger number of
91:28 this results in a larger number of possible networks
91:30 possible networks each with fewer host addresses
91:33 each with fewer host addresses the subnets are created by borrowing
91:35 the subnets are created by borrowing bits from the host portion and using
91:37 bits from the host portion and using them as subnet bits
91:40 them as subnet bits an important aspect of ipv4 addressing
91:43 an important aspect of ipv4 addressing is separating the network and the host
91:45 is separating the network and the host part of the addressing string
91:47 part of the addressing string this is accomplished by using a subnet
91:50 this is accomplished by using a subnet mask
91:51 mask also represented by a 32-bit number
91:54 also represented by a 32-bit number the subnet mask starts with the
91:56 the subnet mask starts with the continuous strings of bits
91:58 continuous strings of bits with the value of 1 and ends with a
92:00 with the value of 1 and ends with a string of zeros
92:03 string of zeros the number of bits with the value of 1
92:05 the number of bits with the value of 1 represents the number of bits in the ip
92:07 represents the number of bits in the ip address that must be considered in order
92:10 address that must be considered in order to calculate the network address
92:13 to calculate the network address a subnet mask
92:15 a subnet mask bit of 0 indicates that the
92:17 bit of 0 indicates that the corresponding bit in the ipv4 address is
92:20 corresponding bit in the ipv4 address is a host bit
92:22 a host bit using the same example
92:24 using the same example that we've used earlier and then add a
92:31 255.255.255.0 mask results in the following situation
92:34 results in the following situation with a string of 24 bits of one in the
92:37 with a string of 24 bits of one in the subnet mask
92:38 subnet mask we're going to consider only the first
92:40 we're going to consider only the first 24 bits in the ip address as the network
92:44 24 bits in the ip address as the network portion
92:45 portion this results in the network address of
92:47 this results in the network address of 192 168
92:50 192 168 128.0
92:51 128.0 with a subnet mask of 255-255-255-0
92:59 the last eight bits in the ip address are called the host portion of the ip
93:01 are called the host portion of the ip address and can be assigned to network
93:04 address and can be assigned to network devices so let's ask the basic question
93:07 devices so let's ask the basic question why even upgrade to ipv6 other than the
93:10 why even upgrade to ipv6 other than the fact that you simply get more ip
93:12 fact that you simply get more ip addresses
93:13 addresses well there's a lot of reasons why you
93:15 well there's a lot of reasons why you would want to upgrade to ipv6
93:18 would want to upgrade to ipv6 and here are a few of them spelled out
93:20 and here are a few of them spelled out for you but please note you no longer
93:22 for you but please note you no longer need nat or pat it has inherent ipsec
93:25 need nat or pat it has inherent ipsec support these are key and critical
93:27 support these are key and critical updates now once you've committed to
93:29 updates now once you've committed to using ipv6 you need to understand
93:31 using ipv6 you need to understand how these different ip addresses are
93:33 how these different ip addresses are labeled there's a global unicast address
93:36 labeled there's a global unicast address these are unicast packets sent through
93:38 these are unicast packets sent through the public internet with public ipa
93:41 the public internet with public ipa addresses unique local which are unicast
93:44 addresses unique local which are unicast packets inside one organization which is
93:46 packets inside one organization which is basically equal to your private ipa
93:48 basically equal to your private ipa addressing
93:49 addressing link local which are packets sent to a
93:51 link local which are packets sent to a local subnet and are not rotter audible
93:54 local subnet and are not rotter audible across networks
94:01 and and then finally take note of the loopback address which you know from
94:03 loopback address which you know from ipv4 is 127.001
94:06 ipv4 is 127.001 ipv6 also has a loopback addressing as
94:09 ipv6 also has a loopback addressing as well
94:10 well an ipv6 address has 128 bits
94:15 an ipv6 address has 128 bits broken out into 32 hexadecimal numbers
94:18 broken out into 32 hexadecimal numbers organized into eight quartets
94:21 organized into eight quartets so here is the hexadecimal numbering
94:23 so here is the hexadecimal numbering system
94:24 system which i'm sure we won't need much of a
94:25 which i'm sure we won't need much of a refresher on but we do need to use it to
94:28 refresher on but we do need to use it to understand ipv6
94:30 understand ipv6 and here is an ipv6 ip address and as
94:33 and here is an ipv6 ip address and as you can see it looks quite long mainly
94:35 you can see it looks quite long mainly because we're used to looking at ipv4
94:37 because we're used to looking at ipv4 addresses so
94:39 addresses so this ups the game a little bit and we
94:41 this ups the game a little bit and we may begin to wonder how we're going to
94:43 may begin to wonder how we're going to support this on our network or document
94:45 support this on our network or document this and we get concerned about managing
94:48 this and we get concerned about managing a network of addressing this long well
94:50 a network of addressing this long well there are built-in mechanisms within ib
94:52 there are built-in mechanisms within ib version 6 to help us manage it and we're
94:54 version 6 to help us manage it and we're going to cover that
94:57 going to cover that there's ways you can summarize ipv6
94:59 there's ways you can summarize ipv6 addresses to make it more manageable not
95:01 addresses to make it more manageable not only to read but to understand and
95:03 only to read but to understand and explain to other people
95:05 explain to other people so you can shorten ipv6 by omit by
95:08 so you can shorten ipv6 by omit by omitting the leading zeros in any given
95:10 omitting the leading zeros in any given quartet or you can represent one or more
95:13 quartet or you can represent one or more consecutive quartets
95:15 consecutive quartets with a double colon
95:17 with a double colon so here you see an ipv version six
95:19 so here you see an ipv version six address with many zeros in it here's how
95:22 address with many zeros in it here's how we can summarize it
95:24 we can summarize it on the left hand side you can see that
95:26 on the left hand side you can see that we used a double colon to represent the
95:28 we used a double colon to represent the first
95:29 first the second and third quartet
95:32 the second and third quartet and then we summarize the remaining
95:35 and then we summarize the remaining quartets of zeros and in the second
95:37 quartets of zeros and in the second example we did the opposite
95:40 example we did the opposite we summarized the first two quartets
95:44 we summarized the first two quartets with zeros and then used a double colon
95:46 with zeros and then used a double colon for the end you can only use the double
95:48 for the end you can only use the double colon once in an ipv version six ipa
95:51 colon once in an ipv version six ipa address
95:52 address so here we see an ipv6 ip address and
95:55 so here we see an ipv6 ip address and this is the subnet it's this remember
95:57 this is the subnet it's this remember it's a slash 64. so we're matching the
96:00 it's a slash 64. so we're matching the first 64 bits as you see here
96:03 first 64 bits as you see here and this also can be summarized you
96:06 and this also can be summarized you don't need to write out all these zeros
96:08 don't need to write out all these zeros so to explain what the subnet is to
96:10 so to explain what the subnet is to somebody you can simply write it out
96:12 somebody you can simply write it out this way
96:14 this way so ipv6 is manageable it gives you tools
96:17 so ipv6 is manageable it gives you tools to manage it
96:19 to manage it so whether you're reviewing
96:20 so whether you're reviewing documentation or holding a general
96:22 documentation or holding a general discussion about your network or simply
96:25 discussion about your network or simply logging into a cisco rudder to take a
96:26 logging into a cisco rudder to take a look at what's going on
96:28 look at what's going on understanding abbreviation is key to
96:30 understanding abbreviation is key to ipv6
96:32 ipv6 here are some other ways we can
96:33 here are some other ways we can understand ipv6 addressing
96:36 understand ipv6 addressing in our first example you'll see that
96:39 in our first example you'll see that it's two zero zero zero and then a
96:41 it's two zero zero zero and then a double colon slash four
96:43 double colon slash four the slash four would match the first
96:45 the slash four would match the first four bits and hex that would be zero
96:48 four bits and hex that would be zero zero one zero
96:50 zero one zero so all addresses whose first four bits
96:52 so all addresses whose first four bits are equal to the first four bits of the
96:54 are equal to the first four bits of the hex number
96:56 hex number two zero zero zero
96:59 two zero zero zero in the second second example we're
97:01 in the second second example we're matching all addresses whose first 20
97:04 matching all addresses whose first 20 bits match the listed hex number and you
97:06 bits match the listed hex number and you can see in red
97:08 can see in red what
97:09 what match that would be
97:10 match that would be and then the final example all addresses
97:12 and then the final example all addresses whose first 32 bits match the listed hex
97:15 whose first 32 bits match the listed hex number
97:22 here's another ipv6 address how do we break it out into subnets well here you
97:24 break it out into subnets well here you have it
97:25 have it we're honoring the first 48 bits of this
97:29 we're honoring the first 48 bits of this range and then we are breaking this out
97:31 range and then we are breaking this out into smaller subnets as you can see here
97:41 each subnet matching the first 112 bits now that you've learned about ipv4 and
97:43 now that you've learned about ipv4 and v6 let's learn about ip routing
97:47 v6 let's learn about ip routing every machine in a particular lan will
97:49 every machine in a particular lan will have the same network address and subnet
97:52 have the same network address and subnet mask
97:53 mask however the host portion of the ip
97:55 however the host portion of the ip address will be different
98:06 the process of choosing the best path is called routing
98:08 called routing although routers are the most popular
98:10 although routers are the most popular devices that make routing decisions
98:12 devices that make routing decisions other network devices can have routing
98:15 other network devices can have routing functionality
98:16 functionality such as layer 3 switches or security
98:19 such as layer 3 switches or security appliances
98:20 appliances a router is responsible for sending the
98:23 a router is responsible for sending the packet the correct way
98:24 packet the correct way no matter what is happening above the
98:26 no matter what is happening above the network layer
98:28 network layer routers look at the packet's destination
98:30 routers look at the packet's destination address to determine where the packet is
98:32 address to determine where the packet is going
98:33 going so they can select the best route to get
98:35 so they can select the best route to get the packet there
98:37 the packet there in order to calculate the best path
98:39 in order to calculate the best path routers must know what interface should
98:41 routers must know what interface should be used in order to reach the packet's
98:43 be used in order to reach the packet's destination network
98:45 destination network routers learn about networks by either
98:48 routers learn about networks by either being connected to them physically
98:51 being connected to them physically or by having a network administrator
98:53 or by having a network administrator program the routes
98:55 program the routes or by learning them dynamically from
98:57 or by learning them dynamically from other routers using routing protocols
99:01 other routers using routing protocols routers keep the best path to
99:03 routers keep the best path to destinations learned via direct
99:05 destinations learned via direct connections
99:06 connections static routing or dynamic routing in the
99:08 static routing or dynamic routing in the internal data structures called routing
99:11 internal data structures called routing tables
99:12 tables a routing table consists of networks the
99:15 a routing table consists of networks the router has learned about and information
99:17 router has learned about and information about how to reach them
99:20 about how to reach them as mentioned before dynamic routing is
99:22 as mentioned before dynamic routing is the process by which a router exchanges
99:24 the process by which a router exchanges routing information and learns about
99:26 routing information and learns about remote networks from other routers
99:29 remote networks from other routers different routing protocols can
99:31 different routing protocols can accomplish this task
99:33 accomplish this task including the following
99:35 including the following rip
99:36 rip eigrp
99:38 eigrp ospf
99:39 ospf isis and bgp
99:42 isis and bgp the most important information a routing
99:44 the most important information a routing table contains includes the following
99:46 table contains includes the following items
99:47 items how the route was learned
99:50 how the route was learned the address of the neighbor router from
99:52 the address of the neighbor router from which the network was learned
99:55 which the network was learned the interface through which the network
99:56 the interface through which the network can be reached
99:59 can be reached and the route metric which is a
100:01 and the route metric which is a measurement that gives routers
100:03 measurement that gives routers information about how far or how
100:05 information about how far or how preferred a network is
100:11 so here's what you've learned you've learned about ipv4 and ipv6
100:15 you've learned about ipv4 and ipv6 addressing
100:16 addressing but you've also learned about how ip
100:19 but you've also learned about how ip routing basically works which is a good
100:21 routing basically works which is a good foundation as you move forward in your
100:23 foundation as you move forward in your ccda studies good luck in your studies
100:26 ccda studies good luck in your studies thank you
100:53 hi this is david voss ccie11372 and in this video we're going to cover
100:55 and in this video we're going to cover network design principles
100:58 network design principles specifically in this video you're going
101:00 specifically in this video you're going to learn about the design of a cisco
101:03 to learn about the design of a cisco ecosystem
101:05 ecosystem then we're going to talk about the
101:06 then we're going to talk about the modern organization
101:08 modern organization specifically organizational i.t
101:11 specifically organizational i.t architecture
101:12 architecture and the policy cycle
101:15 and the policy cycle and then finally we will talk about
101:17 and then finally we will talk about infrastructure design considerations and
101:20 infrastructure design considerations and by the end of this video you will be
101:22 by the end of this video you will be well versed in all five areas
101:25 well versed in all five areas when building a network choosing the
101:27 when building a network choosing the network hardware and software components
101:30 network hardware and software components must be performed with consideration for
101:32 must be performed with consideration for design planning deployment and support
101:36 design planning deployment and support all phases have design principles that
101:38 all phases have design principles that must be taken into account
101:41 must be taken into account and which will be covered in this video
101:44 and which will be covered in this video today's modern organizational models
101:47 today's modern organizational models try to leverage internet working power
101:50 try to leverage internet working power and the benefits of the global internet
101:53 and the benefits of the global internet the modern approach is different in many
101:55 the modern approach is different in many ways from the traditional organizational
101:57 ways from the traditional organizational model that was based on an isolated
102:00 model that was based on an isolated network design
102:02 network design traditional companies have closed
102:04 traditional companies have closed structure and a limited ability to
102:06 structure and a limited ability to integrate with other organizations and
102:08 integrate with other organizations and other companies from an i.t standpoint
102:11 other companies from an i.t standpoint which results in limited access to
102:13 which results in limited access to information
102:15 information these companies are difficult to both
102:16 these companies are difficult to both partner and interact with
102:19 partner and interact with because most of the processes and
102:20 because most of the processes and applications aren't done internally
102:23 applications aren't done internally therefore companies that adopt this
102:25 therefore companies that adopt this model
102:26 model are unable to adapt and take advantage
102:28 are unable to adapt and take advantage of new technologies
102:30 of new technologies let me give you an example
102:32 let me give you an example if i roll out a network
102:34 if i roll out a network with private leased lines
102:36 with private leased lines over a specific provider
102:39 over a specific provider using non-standard hardware such as hp
102:42 using non-standard hardware such as hp juniper and cisco
102:44 juniper and cisco and maybe dell
102:46 and maybe dell and then protocol a variety of protocols
102:48 and then protocol a variety of protocols such as ospf and isis
102:51 such as ospf and isis when it comes time to merge with a
102:53 when it comes time to merge with a company or connect with a company i'm
102:56 company or connect with a company i'm not ready to do that unless they happen
102:58 not ready to do that unless they happen to support the same technologies
103:01 to support the same technologies in the same areas or the locations
103:04 in the same areas or the locations as you can see how are we supposed to
103:06 as you can see how are we supposed to connect with this new strategic partner
103:08 connect with this new strategic partner using our existing infrastructure
103:10 using our existing infrastructure with the wide array of technology
103:13 with the wide array of technology platforms and private lines is very
103:15 platforms and private lines is very difficult
103:17 difficult this is the old way of doing things
103:20 this is the old way of doing things these disadvantages create the need for
103:22 these disadvantages create the need for a new modern networking organizational
103:25 a new modern networking organizational model based on a network design that
103:28 model based on a network design that allows partnership in collaboration with
103:30 allows partnership in collaboration with other entities
103:32 other entities it also provides a more focused
103:33 it also provides a more focused expertise over the products and services
103:36 expertise over the products and services vital to a company's business model the
103:39 vital to a company's business model the reality is is that it's much easier for
103:41 reality is is that it's much easier for companies running simply just cisco with
103:44 companies running simply just cisco with let's say ospf and bgp
103:46 let's say ospf and bgp and who are already leveraging internet
103:48 and who are already leveraging internet based technologies
103:50 based technologies to communicate with one another
103:52 to communicate with one another because the infrastructure that is
103:54 because the infrastructure that is needed is already in place
103:57 needed is already in place as you can see here because this company
104:00 as you can see here because this company leverages internet technologies and
104:02 leverages internet technologies and standard platforms and protocols
104:05 standard platforms and protocols it's very easy to integrate with
104:07 it's very easy to integrate with external entities whether it's a
104:08 external entities whether it's a strategic partner or a customer
104:11 strategic partner or a customer anybody you need to communicate with or
104:13 anybody you need to communicate with or create private connections to
104:16 create private connections to this can easily be done with the
104:18 this can easily be done with the leveraging of internet technologies and
104:20 leveraging of internet technologies and standard platforms which can be
104:22 standard platforms which can be implemented with a strong policy
104:24 implemented with a strong policy governance which we'll talk about very
104:27 governance which we'll talk about very shortly
104:28 shortly the design of an ecosystem
104:30 the design of an ecosystem must include a scalable and flexible
104:33 must include a scalable and flexible network infrastructure
104:34 network infrastructure that will be able to leverage enterprise
104:36 that will be able to leverage enterprise networking and the internet
104:38 networking and the internet creating an environment that is highly
104:40 creating an environment that is highly accessible and collaborative and that
104:42 accessible and collaborative and that can break geographical boundaries and
104:45 can break geographical boundaries and will promote an efficient integration of
104:48 will promote an efficient integration of all stakeholders
104:50 all stakeholders the modern organizational model includes
104:52 the modern organizational model includes the following four entities
104:55 the following four entities employees
104:56 employees who consume hr information data about
105:00 who consume hr information data about such things as benefits and job openings
105:02 such things as benefits and job openings stock reports schedules or even expense
105:05 stock reports schedules or even expense reporting
105:06 reporting these all depend on the corporate
105:08 these all depend on the corporate intranet
105:09 intranet this intranet provides instant access to
105:12 this intranet provides instant access to all the most recent information and
105:14 all the most recent information and services and application updates used by
105:16 services and application updates used by the employees
105:19 the employees the customer related aspects of a
105:21 the customer related aspects of a company are online support technical
105:23 company are online support technical support or providing different types of
105:26 support or providing different types of customer services
105:28 customer services depending on the situation customers
105:29 depending on the situation customers might need to access some of the
105:31 might need to access some of the company's resources for example opening
105:33 company's resources for example opening a support ticket
105:36 a support ticket the vendors and suppliers are involved
105:38 the vendors and suppliers are involved in the process of ordering billing and
105:40 in the process of ordering billing and delivery of the products the company
105:42 delivery of the products the company uses
105:43 uses these processes can be very time and
105:45 these processes can be very time and labor intensive so organizations can
105:48 labor intensive so organizations can leverage their existing internet works
105:49 leverage their existing internet works to create links to their suppliers and
105:52 to create links to their suppliers and vendors which lowers costs per
105:55 vendors which lowers costs per transaction
105:58 transaction strategic partners work to create
105:59 strategic partners work to create strategic relationships in order to
106:01 strategic relationships in order to leverage resources
106:03 leverage resources and services to complete in-house
106:05 and services to complete in-house expertise and skills
106:09 expertise and skills this modern organizational model applies
106:11 this modern organizational model applies to small medium and large companies
106:14 to small medium and large companies designs that support this model are
106:16 designs that support this model are built around a modular architecture that
106:19 built around a modular architecture that uses technology consistent with the
106:21 uses technology consistent with the needs of the organization
106:23 needs of the organization and allows companies to have a network
106:25 and allows companies to have a network infrastructure
106:26 infrastructure that is better suited for scalable
106:28 that is better suited for scalable applications
106:30 applications now when discussing the architectural
106:32 now when discussing the architectural components of the network
106:34 components of the network the architecture that cisco recommends
106:37 the architecture that cisco recommends is divided into multiple layers which
106:40 is divided into multiple layers which make the processes in the organization
106:42 make the processes in the organization easier to expand
106:44 easier to expand implement and scale
106:46 implement and scale so let's go ahead and cover those now
106:50 so let's go ahead and cover those now applications and services comprise the
106:52 applications and services comprise the top layer and include organizational
106:54 top layer and include organizational goals
106:56 goals applications and services offer a
106:58 applications and services offer a concrete set of functions that can be
107:00 concrete set of functions that can be accessed by the network
107:02 accessed by the network but only by authorized users
107:05 but only by authorized users this layer also includes productivity
107:07 this layer also includes productivity tools
107:08 tools such as word processing databases and
107:11 such as word processing databases and email
107:12 email the next layer is intelligent solutions
107:15 the next layer is intelligent solutions and then there is structured data in
107:17 and then there is structured data in business logic
107:18 business logic these comprise this middle layer these
107:22 these comprise this middle layer these elements make the modern network much
107:23 elements make the modern network much more intelligent
107:25 more intelligent and help support applications and
107:27 and help support applications and services in an efficient manner
107:30 services in an efficient manner this level includes such functions as
107:32 this level includes such functions as messaging
107:33 messaging such as chat
107:34 such as chat voip or video conferencing
107:37 voip or video conferencing database structures
107:38 database structures and other content networking solutions
107:42 and other content networking solutions the bottom layer is the foundation of
107:44 the bottom layer is the foundation of the organizational architecture the
107:47 the organizational architecture the network infrastructure
107:49 network infrastructure this is composed of the network platform
107:52 this is composed of the network platform the connections that work together to
107:54 the connections that work together to provide a highly available secure and
107:56 provide a highly available secure and scalable network
107:59 scalable network all of these layers are combined
108:01 all of these layers are combined to offer a foundation for all
108:03 to offer a foundation for all organizational policies goals and
108:05 organizational policies goals and procedures
108:07 procedures that are put in place by management
108:09 that are put in place by management and then handed down to the other
108:11 and then handed down to the other departments in the company to support
108:13 departments in the company to support the overall goals and mission of the
108:15 the overall goals and mission of the organization
108:17 organization before designing a network an important
108:20 before designing a network an important aspect must be considered
108:22 aspect must be considered all organizations have policies at one
108:25 all organizations have policies at one level or another
108:27 level or another even if the procedures are not written
108:28 even if the procedures are not written well
108:29 well there is some kind of understanding at
108:32 there is some kind of understanding at the management level about the goals of
108:33 the management level about the goals of the organization
108:35 the organization organizational policy and procedures are
108:38 organizational policy and procedures are generally a collection of very specific
108:40 generally a collection of very specific guidelines and rules which are in
108:42 guidelines and rules which are in written form
108:43 written form for all to understand and implement and
108:45 for all to understand and implement and maintain at every level of the
108:47 maintain at every level of the organization
108:48 organization in order to reach the well-defined
108:50 in order to reach the well-defined business goals
108:52 business goals the organizational policy cycle contains
108:54 the organizational policy cycle contains the following three components or steps
108:57 the following three components or steps first set the policy
109:01 first set the policy next enforce the policy
109:04 next enforce the policy and then the final step is to maintain
109:07 and then the final step is to maintain and or adapt the policy as needed
109:10 and or adapt the policy as needed now the policy makers include the
109:12 now the policy makers include the following from top to bottom
109:15 following from top to bottom you have your board of directors and
109:17 you have your board of directors and other executives
109:19 other executives departmental management
109:22 departmental management employees
109:24 employees these can be subject matter experts who
109:26 these can be subject matter experts who can be relied upon to formulate
109:28 can be relied upon to formulate procedures
109:30 procedures external consultants and strategic
109:32 external consultants and strategic partners can also provide
109:34 partners can also provide outside input to set policy within an
109:37 outside input to set policy within an organization
109:40 organization now a flexible network infrastructure
109:42 now a flexible network infrastructure helps the organization and its customer
109:45 helps the organization and its customer meets the needs policies and procedures
109:48 meets the needs policies and procedures to help facilitate these information
109:50 to help facilitate these information flows
109:51 flows and designing that network
109:53 and designing that network infrastructure involves considering the
109:54 infrastructure involves considering the following essential features recommended
109:57 following essential features recommended by cisco
109:59 by cisco first availability
110:01 first availability critical business applications must have
110:03 critical business applications must have access to network resources
110:05 access to network resources on a 24x7 basis
110:08 on a 24x7 basis all components of the network
110:10 all components of the network infrastructure should be redundant and
110:12 infrastructure should be redundant and resilient
110:13 resilient efficiency
110:15 efficiency the best equipment and software that is
110:17 the best equipment and software that is tuned for optimal results should be
110:19 tuned for optimal results should be provided
110:21 provided obviously this should be accomplished
110:23 obviously this should be accomplished with reasonable costs in investment
110:26 with reasonable costs in investment functionality the network infrastructure
110:28 functionality the network infrastructure must support the business applications
110:30 must support the business applications and services regardless of what is being
110:33 and services regardless of what is being rolled out today or tomorrow
110:36 rolled out today or tomorrow manageability using management tools
110:38 manageability using management tools such as cisco works
110:40 such as cisco works should include technology
110:42 should include technology that improves the control of the network
110:44 that improves the control of the network such as snmp
110:47 such as snmp performance
110:49 performance obviously important applications need to
110:52 obviously important applications need to get the bandwidth they need in order to
110:54 get the bandwidth they need in order to operate correctly
110:56 operate correctly and the latency on the network needs to
110:58 and the latency on the network needs to be within an acceptable range
111:00 be within an acceptable range and finally scalability
111:02 and finally scalability this includes the ability to grow and
111:04 this includes the ability to grow and expand depending on the organizational
111:07 expand depending on the organizational goals of today
111:09 goals of today and tomorrow
111:11 and tomorrow so take three quick challenges for me
111:14 so take three quick challenges for me and pause the video when i say so
111:16 and pause the video when i say so on a piece of paper
111:17 on a piece of paper write down the four primary entities of
111:20 write down the four primary entities of the modern organizational model
111:24 the modern organizational model go ahead and pause the video and write
111:25 go ahead and pause the video and write those down now
111:32 the four entities of the modern organizational model are employees
111:35 organizational model are employees customers
111:36 customers vendors and suppliers and partners
111:43 next on a piece of paper draw out the
111:45 on a piece of paper draw out the organizational architecture of the
111:47 organizational architecture of the network that cisco recommends
111:51 network that cisco recommends go ahead and do that now
111:56 as you will see here on the top layer there's applications and services
111:59 there's applications and services on the middle layer there is
112:00 on the middle layer there is intelligence solutions
112:02 intelligence solutions and then structured data in business
112:04 and then structured data in business logic
112:05 logic and on the bottom layer there is the
112:07 and on the bottom layer there is the network infrastructure
112:09 network infrastructure finally see if you can list at least
112:11 finally see if you can list at least four of the essential features
112:13 four of the essential features recommended by cisco
112:15 recommended by cisco when considering a network design
112:18 when considering a network design at least four essential features to be
112:20 at least four essential features to be considered
112:22 considered go ahead and pause the video
112:27 let's see how you did there's availability
112:29 availability efficiency
112:30 efficiency functionality
112:32 functionality manageability
112:34 manageability performance
112:36 performance and scalability
112:39 and scalability so here's what you've learned you've
112:40 so here's what you've learned you've learned the design of an
112:42 learned the design of an ecosystem you've learned about the
112:44 ecosystem you've learned about the modern organization
112:46 modern organization and organizational i.t architecture
112:49 and organizational i.t architecture as well as the organizational policy
112:51 as well as the organizational policy cycle
112:52 cycle which can and does play a role in
112:55 which can and does play a role in infrastructure design considerations all
112:58 infrastructure design considerations all of this you will need to know for your
113:00 of this you will need to know for your ccda exam and i'm confident if you've
113:02 ccda exam and i'm confident if you've mastered the material in this video
113:04 mastered the material in this video you're going to do very well in this
113:06 you're going to do very well in this area
113:07 area thank you and good luck in your studies
113:34 and in this video you are going to learn about cisco's intelligent information
113:36 about cisco's intelligent information network
113:38 network and service oriented network
113:40 and service oriented network architecture
113:42 architecture we are going to cover these two topics
113:43 we are going to cover these two topics in detail
113:45 in detail so that you are fully prepared to handle
113:47 so that you are fully prepared to handle these topics when they come up on your
113:49 these topics when they come up on your ccda exam
113:51 ccda exam first let's begin with cisco intelligent
113:54 first let's begin with cisco intelligent information network
113:56 information network iin represents a multi-phased
113:59 iin represents a multi-phased architecture that injects intelligence
114:02 architecture that injects intelligence into a network infrastructure
114:04 into a network infrastructure its single integrated system provides
114:07 its single integrated system provides intelligence across multiple layers as
114:10 intelligence across multiple layers as you see here
114:11 you see here and aligns the network infrastructure
114:13 and aligns the network infrastructure with the rest of the it infrastructure
114:16 with the rest of the it infrastructure integrating the network
114:18 integrating the network with applications software servers and
114:21 with applications software servers and services
114:23 services in other words the network becomes an
114:25 in other words the network becomes an active participant in the total delivery
114:28 active participant in the total delivery of applications and services
114:31 of applications and services cisco sees this as an evolving
114:33 cisco sees this as an evolving environment or what they would call an
114:35 environment or what they would call an ecosystem
114:37 ecosystem that responds to constantly changing
114:39 that responds to constantly changing business requirements
114:42 business requirements the intelligent information network
114:45 the intelligent information network is a cisco ideal
114:47 is a cisco ideal where network and application services
114:50 where network and application services are integrated
114:52 are integrated allowing for cost savings and improved
114:54 allowing for cost savings and improved user productivity
114:56 user productivity it allows the network to be used as a
114:58 it allows the network to be used as a strategic asset
115:00 strategic asset and provides capabilities which include
115:02 and provides capabilities which include some of the following such as cdp which
115:05 some of the following such as cdp which is a simple broadcast protocol that
115:08 is a simple broadcast protocol that network devices use to advertise their
115:10 network devices use to advertise their presence it operates in the background
115:13 presence it operates in the background and facilitates communication between
115:15 and facilitates communication between for example a cisco unified iphone
115:18 for example a cisco unified iphone plugged into a network and the network
115:20 plugged into a network and the network switch itself
115:22 switch itself qos
115:24 qos cisco provides an end-to-end solution
115:26 cisco provides an end-to-end solution with qos to ensure that packets are
115:29 with qos to ensure that packets are serviced the way they need to be as
115:32 serviced the way they need to be as traffic flows through the access layer
115:34 traffic flows through the access layer for example priority queueing and buffer
115:36 for example priority queueing and buffer management ensure that real-time traffic
115:39 management ensure that real-time traffic is prioritized over less
115:42 is prioritized over less time critical data
115:44 time critical data next is vlans with vlans
115:47 next is vlans with vlans the lan infrastructure can distinguish
115:49 the lan infrastructure can distinguish between a phone for example from a pc
115:53 between a phone for example from a pc using vlan tagging wireless
115:56 using vlan tagging wireless cisco wireless access points allow cisco
115:59 cisco wireless access points allow cisco wireless users to roam a campus without
116:01 wireless users to roam a campus without losing connectivity if a user roams to a
116:04 losing connectivity if a user roams to a different site the system will discover
116:06 different site the system will discover the new physical location of that user
116:09 the new physical location of that user power over ethernet
116:11 power over ethernet this eliminates the need for local power
116:13 this eliminates the need for local power connections to every phone
116:16 connections to every phone and finally gigabit ethernet which
116:18 and finally gigabit ethernet which allows voice video and data to take
116:22 allows voice video and data to take advantage of high bandwidth speeds on
116:25 advantage of high bandwidth speeds on the lan infrastructure
116:28 the lan infrastructure as you saw before the iin is broken up
116:31 as you saw before the iin is broken up into three individual phases phase one
116:34 into three individual phases phase one of the iin is the integrated systems
116:37 of the iin is the integrated systems phase
116:38 phase this phase involves the convergence of
116:41 this phase involves the convergence of voice data and video
116:43 voice data and video into a single transport network or
116:45 into a single transport network or across a system of networks
116:47 across a system of networks this phase is facilitated by platforms
116:50 this phase is facilitated by platforms such as cisco isr routers
116:53 such as cisco isr routers phase 2 of the iin is the integrated
116:56 phase 2 of the iin is the integrated services phase
116:58 services phase this phase merges common elements such
117:01 this phase merges common elements such as storage and data center server
117:03 as storage and data center server capacity
117:04 capacity additionally virtualization technologies
117:07 additionally virtualization technologies allow for the integration of servers
117:09 allow for the integration of servers storage and network devices
117:13 storage and network devices and finally phase three of the iin is
117:15 and finally phase three of the iin is the integrated applications phase
117:19 the integrated applications phase this phase is the ultimate goal of the
117:21 this phase is the ultimate goal of the iin in that it allows the network to
117:24 iin in that it allows the network to become application aware
117:27 become application aware cisco refers to this as aon application
117:31 cisco refers to this as aon application oriented networking
117:33 oriented networking now
117:34 now iin
117:36 iin should not be mentioned without
117:38 should not be mentioned without discussing cisco sona or cisco service
117:41 discussing cisco sona or cisco service oriented network architecture
117:45 oriented network architecture this framework applies iin within the
117:49 this framework applies iin within the enterprise network
117:51 enterprise network sona divides the iin and ideal into the
117:54 sona divides the iin and ideal into the following three different layers
117:57 following three different layers the network infrastructure layer
118:00 the network infrastructure layer also referred to as the physical
118:02 also referred to as the physical infrastructure layer
118:04 infrastructure layer facilitates the transport of services
118:06 facilitates the transport of services across the network
118:08 across the network it refers to a hierarchical converged
118:10 it refers to a hierarchical converged network that includes servers storage
118:13 network that includes servers storage and clients
118:15 and clients this is where the server storage and
118:17 this is where the server storage and clients are located and includes
118:19 clients are located and includes different modular design areas
118:22 different modular design areas such as the wan or enterprise edge
118:25 such as the wan or enterprise edge branch campus data center or teleworker
118:30 branch campus data center or teleworker the interactive services layer also
118:32 the interactive services layer also referred to as the core common services
118:35 referred to as the core common services layer
118:36 layer optimizes the communication between
118:38 optimizes the communication between applications and services
118:40 applications and services using intelligent network functions such
118:42 using intelligent network functions such as security
118:44 as security identity voice virtualization and qos
118:48 identity voice virtualization and qos the application layer
118:50 the application layer contains the business and collaboration
118:52 contains the business and collaboration applications
118:53 applications used by end users
118:55 used by end users these applications include commercial
118:58 these applications include commercial and internally developed applications
119:00 and internally developed applications such as software as a service
119:02 such as software as a service and composite applications within the
119:04 and composite applications within the service oriented architecture
119:07 service oriented architecture the sauna network is built from the
119:09 the sauna network is built from the ground up with redundancy and resiliency
119:12 ground up with redundancy and resiliency to prevent network downtime
119:14 to prevent network downtime the goal of sona is to provide high
119:17 the goal of sona is to provide high performance
119:18 performance fast response times and throughput by
119:21 fast response times and throughput by assuring quality of service on an
119:23 assuring quality of service on an application by application basis
119:26 application by application basis the sauna network is configured in order
119:28 the sauna network is configured in order to maximize the throughput of all
119:31 to maximize the throughput of all critical applications such as voice and
119:33 critical applications such as voice and video
119:35 video sona also provides built-in
119:36 sona also provides built-in manageability configuration management
119:39 manageability configuration management performance monitoring fault detection
119:41 performance monitoring fault detection and analysis tools sauna provides an
119:45 and analysis tools sauna provides an efficient design with the goal of
119:46 efficient design with the goal of reducing the total cost of ownership
119:49 reducing the total cost of ownership and maximizing the company's existing
119:51 and maximizing the company's existing resources when application demands
119:54 resources when application demands increase
119:55 increase so now that you've learned about iin and
119:57 so now that you've learned about iin and sona let's take two challenges first
120:01 sona let's take two challenges first on a piece of paper
120:03 on a piece of paper please write out the three phases of iin
120:08 please write out the three phases of iin the three phases and their names
120:13 the three phases and their names go ahead and pause the video now
120:19 let's see how you've done there's phase one which is integrated
120:22 there's phase one which is integrated systems
120:24 systems phase two which is integrated services
120:28 phase two which is integrated services and then phase three
120:30 and then phase three which is integrated applications
120:34 which is integrated applications next on a piece of paper what i'd like
120:35 next on a piece of paper what i'd like you to try to the best of your ability
120:38 you to try to the best of your ability and as detailed as possible
120:41 and as detailed as possible draw out the cisco service oriented
120:43 draw out the cisco service oriented network architecture framework
120:46 network architecture framework see if you can draw it out to the best
120:48 see if you can draw it out to the best of your ability and try to include some
120:51 of your ability and try to include some modules
120:52 modules within your layers to see how well you
120:55 within your layers to see how well you do
121:02 let's see how you've done there's the network infrastructure layer
121:03 there's the network infrastructure layer and you can see the modules here there's
121:05 and you can see the modules here there's the interactive services layer
121:08 the interactive services layer and you can see the sub modules here
121:11 and you can see the sub modules here and then there's the application layer
121:13 and then there's the application layer and you can see the sub modules here
121:16 and you can see the sub modules here so in this video you learned about
121:19 so in this video you learned about cisco intelligent information network
121:22 cisco intelligent information network and cisco service oriented network
121:24 and cisco service oriented network architecture framework
121:26 architecture framework and how they work together
121:28 and how they work together you will be tested on both of these in
121:31 you will be tested on both of these in your ccda exam
121:33 your ccda exam so if you understand the concepts in
121:35 so if you understand the concepts in this video very well
121:36 this video very well i'm confident you're going to do well on
121:38 i'm confident you're going to do well on this portion of your ccda exam
121:41 this portion of your ccda exam good luck in your studies
122:07 hi this is david voss ccie 11372 and in this video we're going to be
122:08 and in this video we're going to be covering the cisco ppd io lifecycle
122:14 covering the cisco ppd io lifecycle in this video you will learn about the
122:16 in this video you will learn about the benefits of ppd-io
122:19 benefits of ppd-io as well as its design methodology
122:23 as well as its design methodology you will also learn about how to
122:25 you will also learn about how to identify customer requirements
122:27 identify customer requirements for network design
122:29 for network design and the characteristics of a customer
122:32 and the characteristics of a customer network
122:34 network and then finally we'll discuss
122:37 and then finally we'll discuss design approaches
122:39 design approaches and design documentation
122:42 and design documentation so let's
122:44 so let's begin cisco has formalized a network's
122:48 begin cisco has formalized a network's life cycle into six phases
122:50 life cycle into six phases prepare
122:51 prepare plan
122:53 plan design
122:54 design implement
122:56 implement operate and optimize
122:58 operate and optimize and these phases are collectively known
123:00 and these phases are collectively known as ppdio
123:03 as ppdio the life cycle has four main benefits
123:07 the life cycle has four main benefits it lowers the total cost of ownership
123:10 it lowers the total cost of ownership it increases network availability
123:13 it increases network availability it improves business agility
123:16 it improves business agility and it speeds access to applications and
123:19 and it speeds access to applications and services
123:22 services let's discuss the ppdio
123:24 let's discuss the ppdio phases in detail
123:26 phases in detail first the prepare phase
123:28 first the prepare phase this phase establishes organization and
123:31 this phase establishes organization and business requirements
123:33 business requirements develops a network strategy and proposes
123:35 develops a network strategy and proposes a high level conceptual architecture to
123:39 a high level conceptual architecture to support that strategy
123:42 support that strategy technologies that support the
123:43 technologies that support the architecture are identified in this
123:45 architecture are identified in this phase
123:47 phase as well as a business case to establish
123:50 as well as a business case to establish the financial justification for the
123:52 the financial justification for the strategy
123:55 strategy the plan phase identifies the network
123:57 the plan phase identifies the network requirements based on goals facilities
123:59 requirements based on goals facilities and user needs
124:02 and user needs this phase characterizes sites and
124:04 this phase characterizes sites and assesses the network performs a gap
124:06 assesses the network performs a gap analysis against best practice
124:08 analysis against best practice architectures and looks at the
124:10 architectures and looks at the operational environment
124:13 operational environment in the design phase the network design
124:16 in the design phase the network design is developed based on the technical and
124:18 is developed based on the technical and business requirements
124:20 business requirements obtained from the previous phases
124:22 obtained from the previous phases a good design will provide high
124:24 a good design will provide high availability reliability security
124:27 availability reliability security scalability and performance
124:30 scalability and performance in the implement phase new equipment is
124:32 in the implement phase new equipment is installed and configured according to
124:35 installed and configured according to the design specifications
124:38 the design specifications in this phase any planned network
124:40 in this phase any planned network changes should be communicated in change
124:42 changes should be communicated in change control meetings and with the necessary
124:45 control meetings and with the necessary approvals to proceed
124:48 approvals to proceed the operate phase maintains the
124:50 the operate phase maintains the network's day-to-day operational health
124:54 network's day-to-day operational health operations include managing
124:56 operations include managing and monitoring network components and
124:59 and monitoring network components and performing the appropriate maintenances
125:02 performing the appropriate maintenances and then finally the optimize phase
125:05 and then finally the optimize phase which involves proactive network
125:07 which involves proactive network management
125:08 management by identifying and resolving issues
125:11 by identifying and resolving issues before they affect the network
125:17 now there is a design methodology for the first three phases of the ppdio
125:20 the first three phases of the ppdio methodology
125:22 methodology and there are three steps to it
125:24 and there are three steps to it in step one
125:25 in step one decision makers identify the
125:27 decision makers identify the requirements and a conceptual
125:28 requirements and a conceptual architecture is proposed
125:32 architecture is proposed in step two the network is assessed
125:35 in step two the network is assessed the network is assessed on function
125:37 the network is assessed on function performance and quality
125:41 performance and quality and then in step three
125:42 and then in step three the network topology is designed to meet
125:46 the network topology is designed to meet the requirements
125:47 the requirements and close the network gaps identified in
125:50 and close the network gaps identified in the previous two steps
125:52 the previous two steps let's review these three phases in
125:54 let's review these three phases in detail
125:55 detail to obtain customer requirements
125:58 to obtain customer requirements you need not only to talk to network
126:00 you need not only to talk to network engineers but you need to talk to the
126:02 engineers but you need to talk to the business
126:03 business personnel and company managers
126:06 personnel and company managers networks are designed to support
126:08 networks are designed to support applications
126:09 applications and you want to determine the network
126:11 and you want to determine the network services that you need to support
126:13 services that you need to support both now
126:14 both now and in the future
126:16 and in the future this this analysis is broken into five
126:20 this this analysis is broken into five steps
126:21 steps first identifying network applications
126:24 first identifying network applications and services
126:26 and services then define the organizational goals
126:29 then define the organizational goals define the possible organizational
126:32 define the possible organizational constraints
126:34 constraints and then define the technical goals
126:37 and then define the technical goals and finally define the possible
126:39 and finally define the possible technical constraints
126:48 when you're characterizing an existing network
126:50 an existing network you need to obtain all the existing
126:52 you need to obtain all the existing documentation
126:54 documentation sometimes no formal documentation exists
126:58 sometimes no formal documentation exists so you need to be prepared to use tools
127:00 so you need to be prepared to use tools to obtain the information needed and to
127:02 to obtain the information needed and to get access to log into network devices
127:04 get access to log into network devices to obtain the information required
127:07 to obtain the information required here are the steps you want to take to
127:09 here are the steps you want to take to gather information
127:11 gather information first you're going to identify all
127:13 first you're going to identify all existing organization information and
127:16 existing organization information and documentation
127:18 documentation then you'll perform a network audit that
127:20 then you'll perform a network audit that adds detail to the description of the
127:23 adds detail to the description of the network
127:24 network and then finally you're going to use
127:26 and then finally you're going to use traffic analysis information to augment
127:29 traffic analysis information to augment information on applications and
127:31 information on applications and protocols used
127:38 when you're designing the network topology and solutions
127:41 topology and solutions cisco recommends that you use the
127:43 cisco recommends that you use the top-down approach for network design
127:46 top-down approach for network design top-down simply means starting your
127:48 top-down simply means starting your design from the top layer of the osi
127:50 design from the top layer of the osi model and working your way down
127:52 model and working your way down top-down design adapts the network and
127:55 top-down design adapts the network and physical infrastructure to the network
127:57 physical infrastructure to the network applications needs
127:59 applications needs with a top-down approach network devices
128:01 with a top-down approach network devices and technologies are not selected until
128:03 and technologies are not selected until the application's requirements are
128:05 the application's requirements are analyzed
128:07 analyzed here you can compare and contrast top
128:09 here you can compare and contrast top down versus bottom up
128:11 down versus bottom up a bottom-up design may result in an
128:14 a bottom-up design may result in an inappropriate design
128:16 inappropriate design because the requirements of the
128:17 because the requirements of the organization that is those requirements
128:20 organization that is those requirements of the applications and the users using
128:22 of the applications and the users using those applications are not included in
128:24 those applications are not included in this type of design
128:30 next the design document itself
128:32 the design document itself the design document
128:34 the design document should include the following sections
128:36 should include the following sections the introduction
128:38 the introduction the design requirements
128:41 the design requirements existing network infrastructure
128:43 existing network infrastructure including layer 3 topology diagrams
128:47 including layer 3 topology diagrams physical topology diagrams audit results
128:50 physical topology diagrams audit results network health analysis routing
128:52 network health analysis routing protocols
128:53 protocols applications and a list of routers and
128:56 applications and a list of routers and switches and other devices
128:58 switches and other devices among many other things
129:01 among many other things then the design portion which actually
129:03 then the design portion which actually contains the specific design information
129:06 contains the specific design information such as logical physical topology ip
129:08 such as logical physical topology ip addressing routing protocols etc
129:12 addressing routing protocols etc proof of concept
129:14 proof of concept which results from the live pilot or
129:16 which results from the live pilot or prototype testing
129:19 prototype testing and then the implementation plan
129:21 and then the implementation plan which includes the detailed steps for
129:23 which includes the detailed steps for the network staff to implement the new
129:25 the network staff to implement the new installation
129:27 installation and then the appendixes which will list
129:29 and then the appendixes which will list all the existing network devices
129:31 all the existing network devices configurations and additional
129:33 configurations and additional information used in the design of a
129:35 information used in the design of a network
129:42 so now it's your turn go ahead and on a piece of paper or whiteboard
129:44 piece of paper or whiteboard go ahead and draw out the ppd io
129:48 go ahead and draw out the ppd io methodology
129:49 methodology uh start with the first step the first p
129:53 uh start with the first step the first p i guess you could say
129:55 i guess you could say and write it out
129:56 and write it out and then write out the
129:58 and then write out the full chart of ppdio
130:02 full chart of ppdio what each letter stands for
130:04 what each letter stands for and also put a sentence next to each
130:06 and also put a sentence next to each word
130:07 word to summarize the activity that occurs at
130:10 to summarize the activity that occurs at that phase
130:12 that phase go ahead and do that now and pause the
130:13 go ahead and do that now and pause the video
130:26 so let's see how you did the first phase is prepare
130:59 and the final phase is optimize this is a life cycle
131:01 this is a life cycle that is
131:02 that is it doesn't mean once you hit optimize
131:04 it doesn't mean once you hit optimize that it's over it's a continual process
131:07 that it's over it's a continual process going from prepare plan over to design
131:10 going from prepare plan over to design implement operate and optimize
131:13 implement operate and optimize and then around again on a regular basis
131:16 and then around again on a regular basis you're constantly looking at the network
131:19 you're constantly looking at the network seeing what can be done to make it run
131:21 seeing what can be done to make it run more efficiently and more cost effective
131:29 now assuming you went ahead and added a sentence or two after each word here are
131:32 sentence or two after each word here are some good foundational sentences or
131:35 some good foundational sentences or questions
131:36 questions regarding what is going on in each phase
131:46 so here's what you've learned you've learned about the benefits and the
131:48 learned about the benefits and the design methodology of ppd io
131:52 design methodology of ppd io you've learned how to identify customer
131:54 you've learned how to identify customer requirements in the characteristics of a
131:56 requirements in the characteristics of a network
131:57 network and then you dug into the design
132:00 and then you dug into the design approach
132:01 approach as far as top down versus bottom up and
132:04 as far as top down versus bottom up and how to properly document a design
132:08 how to properly document a design it appears from the study materials that
132:10 it appears from the study materials that cisco does want you to focus in
132:12 cisco does want you to focus in on the first three phases of ppd-io
132:16 on the first three phases of ppd-io which is why this video also focused on
132:18 which is why this video also focused on the first three phases
132:20 the first three phases we wish you the best of luck in your
132:22 we wish you the best of luck in your studies thank you
132:45 hi this is david voss ccie11372 and in this video you're going
132:48 ccie11372 and in this video you're going to learn about sla resources
132:51 to learn about sla resources specifically we're going to talk about
132:53 specifically we're going to talk about how sla and specifically slcs
132:56 how sla and specifically slcs affect network design
132:58 affect network design so many companies vendors and service
133:01 so many companies vendors and service providers must provide
133:03 providers must provide service level contract or slcs
133:07 service level contract or slcs to their partners or customers
133:10 to their partners or customers in an sla which is a service level
133:12 in an sla which is a service level agreement is a component of the overall
133:15 agreement is a component of the overall service level
133:16 service level contract
133:18 contract the slc
133:19 the slc designates connectivity
133:21 designates connectivity and the performance level that the
133:23 and the performance level that the service provider guarantees to its
133:26 service provider guarantees to its customers
133:27 customers and the organization guarantees to its
133:30 and the organization guarantees to its end users
133:31 end users the sla
133:33 the sla defines specific parameters and
133:35 defines specific parameters and performance measurements between devices
133:37 performance measurements between devices such as routers servers
133:39 such as routers servers workstations or other equipment on the
133:41 workstations or other equipment on the network
133:42 network so here's an example of a service level
133:45 so here's an example of a service level agreement as you can see things are
133:47 agreement as you can see things are spelled out in detail
133:50 spelled out in detail regarding service to the customer
133:53 regarding service to the customer but also software updates
133:56 but also software updates customer support and then even a part of
133:59 customer support and then even a part of the contract states what the customer
134:01 the contract states what the customer responsibility is
134:03 responsibility is so that they're in the event of an
134:05 so that they're in the event of an outage or just on day-to-day disputes
134:09 outage or just on day-to-day disputes you can refer back to the contract so
134:11 you can refer back to the contract so the customer
134:12 the customer and the provider are both very clear
134:15 and the provider are both very clear about what is expected
134:17 about what is expected this protects
134:18 this protects both the customer and the provider
134:21 both the customer and the provider so that roles and responsibilities are
134:24 so that roles and responsibilities are very clear but when there is confusion
134:28 very clear but when there is confusion or when there is a major outage
134:31 or when there is a major outage there is a legal backing
134:33 there is a legal backing for operation procedures
134:36 for operation procedures and decisions
134:38 and decisions now that being said
134:39 now that being said some of this needs to be measured and
134:41 some of this needs to be measured and cisco allows you to do that using cisco
134:44 cisco allows you to do that using cisco ipsla
134:53 let's do a refresh on how cisco ipsla works
134:54 works ipsla allows you to monitor analyze and
134:57 ipsla allows you to monitor analyze and verify
134:58 verify ip service levels
135:00 ip service levels it's comprised of two components a
135:02 it's comprised of two components a source and a target
135:04 source and a target operations can broadly be categorized
135:06 operations can broadly be categorized into five functional areas
135:09 into five functional areas let's take a look at an example
135:22 you can use ipslas to monitor the performance between any area in the
135:24 performance between any area in the network core distribution and edge
135:27 network core distribution and edge without deploying a physical probe
135:29 without deploying a physical probe it uses generated traffic to measure
135:32 it uses generated traffic to measure network performance between two
135:33 network performance between two networking devices
135:35 networking devices so as we draw this out this shows how
135:37 so as we draw this out this shows how ipslas begins when the source device
135:40 ipslas begins when the source device sends a generated packet to the
135:41 sends a generated packet to the destination device
135:43 destination device after the destination device receives
135:45 after the destination device receives the packet depending on the type of
135:47 the packet depending on the type of ipsla's operation it responds with the
135:50 ipsla's operation it responds with the timestamp information for the source to
135:52 timestamp information for the source to make the calculation on performance
135:54 make the calculation on performance metrics
135:58 it then can communicate with a performance management application via
136:01 performance management application via snmp
136:02 snmp to provide real-time analysis of the
136:04 to provide real-time analysis of the network
136:14 it should be noticed that ipsla can communicate with any i p device on the
136:17 communicate with any i p device on the network
136:18 network that's enabled for these types of
136:19 that's enabled for these types of measurements
136:25 although this video has covered what you need to know for cisco sla
136:29 need to know for cisco sla be aware that there are other white
136:30 be aware that there are other white papers out there should you want to read
136:33 papers out there should you want to read more
136:34 more and here they are service level
136:36 and here they are service level management best practices
136:38 management best practices deploying service level management in an
136:40 deploying service level management in an enterprise
136:41 enterprise and service level management defining
136:43 and service level management defining and monitoring service levels in the
136:45 and monitoring service levels in the enterprise
136:47 enterprise now again that being said
136:49 now again that being said within this video and throughout this
136:50 within this video and throughout this video series you will have the
136:52 video series you will have the information you need to do well on your
136:54 information you need to do well on your ccda exam
136:56 ccda exam but again we want to apply this to
136:59 but again we want to apply this to our work environments so if you want to
137:00 our work environments so if you want to do additional reading please refer to
137:03 do additional reading please refer to this
137:04 this so here's what you've learned you've
137:05 so here's what you've learned you've received an overview of cisco sla we
137:08 received an overview of cisco sla we talked about slc service level contracts
137:12 talked about slc service level contracts so you have a foundational understanding
137:14 so you have a foundational understanding of how this applies to any enterprise
137:17 of how this applies to any enterprise campus network
137:43 hi this is david voss ccie113 and in this video you're going to learn
137:45 and in this video you're going to learn about the cisco hierarchical network
137:48 about the cisco hierarchical network model
137:49 model specifically you're going to learn about
137:51 specifically you're going to learn about what cisco calls the core
137:54 what cisco calls the core distribution and access layers of a
137:57 distribution and access layers of a campus network
137:59 campus network the information is rather
138:00 the information is rather straightforward but it is information
138:02 straightforward but it is information you'll need to know very well to do well
138:05 you'll need to know very well to do well on your ccda exam
138:07 on your ccda exam so let's begin
138:10 so let's begin the most important idea concerning the
138:12 the most important idea concerning the cisco hierarchical network model
138:15 cisco hierarchical network model is the step-by-step construction of the
138:17 is the step-by-step construction of the network which implements one module at a
138:20 network which implements one module at a time
138:21 time starting with the foundation the
138:24 starting with the foundation the implementation of each module can be
138:26 implementation of each module can be supervised by a network architect
138:28 supervised by a network architect but the details are covered by a
138:31 but the details are covered by a specialized team such as routing or
138:33 specialized team such as routing or security or voice teams
138:36 security or voice teams this modular approach is the key to
138:38 this modular approach is the key to simplifying the network
138:41 simplifying the network before we cover each module within the
138:43 before we cover each module within the network model
138:45 network model let's talk about the main advantages of
138:47 let's talk about the main advantages of the cisco hierarchical network model
138:51 the cisco hierarchical network model there are eight key advantages
138:54 there are eight key advantages ease to understand and implement
138:57 ease to understand and implement flexibility
138:59 flexibility cost savings
139:01 cost savings modularity
139:03 modularity it's easily modified
139:05 it's easily modified it allows for network growth
139:08 it allows for network growth it facilitates summarization of networks
139:12 it facilitates summarization of networks and there is also built-in fault
139:14 and there is also built-in fault isolation
139:16 isolation the three-tier model was created in
139:18 the three-tier model was created in order to make the construction of
139:19 order to make the construction of networks easier to understand
139:22 networks easier to understand cisco has always tried to make
139:24 cisco has always tried to make efficient and cost effective networks
139:26 efficient and cost effective networks with a modular structure
139:28 with a modular structure so they can easily be divided into
139:31 so they can easily be divided into building blocks
139:32 building blocks the modular network design facilitates
139:35 the modular network design facilitates modifications in certain modules
139:38 modifications in certain modules after their implementation
139:40 after their implementation it makes it easy to track faults in the
139:42 it makes it easy to track faults in the network
139:44 network the cisco hierarchical network model is
139:46 the cisco hierarchical network model is defined by three layers
139:49 defined by three layers the core or backbone layer
139:51 the core or backbone layer the distribution layer
139:53 the distribution layer and the access layer
139:56 and the access layer now if you're working for a small
139:57 now if you're working for a small company
139:58 company these layers might be collapsed core and
140:01 these layers might be collapsed core and distribution are often collapsed into a
140:04 distribution are often collapsed into a single layer
140:05 single layer or sometimes all three layers are
140:08 or sometimes all three layers are collapsed
140:14 that being said let's dive into each of the layers
140:15 the layers the access layer is the on-ramp to the
140:17 the access layer is the on-ramp to the network
140:18 network so for the most part any end user or
140:21 so for the most part any end user or device that wants to connect to the
140:24 device that wants to connect to the network will do so via the access layer
140:27 network will do so via the access layer as you can see access layer switches
140:30 as you can see access layer switches should have redundant connectivity to
140:32 should have redundant connectivity to the distribution layer
140:34 the distribution layer this will ensure network connectivity
140:36 this will ensure network connectivity for the hosts even when there is an
140:38 for the hosts even when there is an equipment failure
140:40 equipment failure you could take it another step further
140:42 you could take it another step further and provide redundant connectivity for
140:44 and provide redundant connectivity for the host to the access layer switches
140:46 the host to the access layer switches but this is the exception to the rule
140:48 but this is the exception to the rule and certainly not the norm
140:51 and certainly not the norm the access layer is comprised of layer
140:53 the access layer is comprised of layer two switches workstations ip telephones
140:56 two switches workstations ip telephones or any other device that requires access
140:58 or any other device that requires access to the network
141:04 here are some specific features you should be aware of at the access layer
141:07 should be aware of at the access layer it should provide high availability
141:10 it should provide high availability and flexible security features
141:13 and flexible security features you can also implement authentication
141:17 you can also implement authentication broadcast control
141:19 broadcast control and it's where you would define qos
141:22 and it's where you would define qos trust boundaries
141:24 trust boundaries in the access layer you would also
141:26 in the access layer you would also implement rate limiting techniques
141:29 implement rate limiting techniques and it's where you would often program
141:32 and it's where you would often program spanning tree protocol
141:35 spanning tree protocol include power over ethernet for your
141:36 include power over ethernet for your phones
141:39 phones and configure voice vlan settings
141:46 as you can see the distribution layer has redundant connectivity to both the
141:48 has redundant connectivity to both the access and core layers
141:51 access and core layers the distribution layer is often where
141:53 the distribution layer is often where the brains of the network resides since
141:56 the brains of the network resides since many decisions such as filtering quality
141:59 many decisions such as filtering quality of service and policy based routing are
142:02 of service and policy based routing are performed in the distribution layer
142:04 performed in the distribution layer as you can see the distribution layer
142:06 as you can see the distribution layer has redundant connectivity to the axis
142:08 has redundant connectivity to the axis and core layers
142:11 and core layers the distribution layer normally has
142:13 the distribution layer normally has advanced layer 3 switches that can
142:15 advanced layer 3 switches that can support a wide array of functionality to
142:18 support a wide array of functionality to support the services required from this
142:21 support the services required from this layer
142:26 here are the attributes of the distribution layer
142:28 distribution layer it gives access control to core devices
142:32 it gives access control to core devices it has redundancy to access devices
142:35 it has redundancy to access devices it's where the boundaries are for
142:37 it's where the boundaries are for routing protocols
142:42 redistribution occurs at this layer as well as filtering
142:44 well as filtering route summarization
142:47 route summarization policy routing
142:49 policy routing and here you will see your security
142:51 and here you will see your security implemented
142:54 implemented it provides separate multicast and
142:56 it provides separate multicast and broadcast domains
142:58 broadcast domains using layer 2 and layer 3 technologies
143:02 using layer 2 and layer 3 technologies and provides routing between vlans
143:05 and provides routing between vlans it is a media translation and provides
143:08 it is a media translation and provides boundaries for media
143:11 boundaries for media and also provides
143:19 redistribution there is a lot going on in the core layer the high speed
143:20 in the core layer the high speed switching fabric ensures that all
143:23 switching fabric ensures that all modules which connect to the core are
143:25 modules which connect to the core are serviced immediately
143:27 serviced immediately you rarely will put any programming on
143:29 you rarely will put any programming on these switches that could cause them to
143:31 these switches that could cause them to slow down processing for example no qos
143:34 slow down processing for example no qos no acls
143:36 no acls rather you want to keep it so that these
143:38 rather you want to keep it so that these high-end switches
143:40 high-end switches spend their time processing forwarding
143:42 spend their time processing forwarding traffic rather than doing anything else
143:46 traffic rather than doing anything else although it's not always required to
143:47 although it's not always required to have redundancy to and from the
143:49 have redundancy to and from the distribution and access layers
143:51 distribution and access layers redundancy is certainly required in the
143:53 redundancy is certainly required in the core
143:54 core as you can see the core is the hub for
143:56 as you can see the core is the hub for the interconnects in the network
143:59 the interconnects in the network it connects to the server farm
144:01 it connects to the server farm to the distribution layer and then off
144:03 to the distribution layer and then off to the enterprise edge as well
144:06 to the enterprise edge as well so having a high performing core is
144:08 so having a high performing core is critical
144:09 critical here are some key features of the core
144:11 here are some key features of the core layer that you will want to memorize
144:15 layer that you will want to memorize the core layer is high speed
144:17 the core layer is high speed it's reliable
144:20 it's reliable it's redundant
144:22 it's redundant it has fault tolerance
144:25 it has fault tolerance and load balancing
144:27 and load balancing it has manageability and scalability
144:31 it has manageability and scalability in the core layer there are no filters
144:33 in the core layer there are no filters packet handling or other overhead that
144:36 packet handling or other overhead that would slow traffic down or the
144:37 would slow traffic down or the processing of traffic down
144:40 processing of traffic down it has a limited but consistent diameter
144:44 it has a limited but consistent diameter and it can provide quality of service
144:52 the cisco core distribution and access layer hierarchical model is rather
144:54 layer hierarchical model is rather straightforward but that's the point
144:57 straightforward but that's the point cisco wants you to know this
144:59 cisco wants you to know this by memory
145:01 by memory and the features of each of the modules
145:04 and the features of each of the modules in preparation for your ccda exam
145:07 in preparation for your ccda exam not only by watching this video are you
145:09 not only by watching this video are you prepared for your ccda exam regarding
145:12 prepared for your ccda exam regarding these areas you're also a much better
145:15 these areas you're also a much better engineer
145:16 engineer now that you understand
145:18 now that you understand the basic organization of a campus
145:20 the basic organization of a campus network good luck in your studies
145:48 hi this is david voss ccie 11372 and in this video you're going to learn
145:49 and in this video you're going to learn about cisco intelligent network services
145:53 about cisco intelligent network services intelligent network services are
145:55 intelligent network services are essential support services
145:57 essential support services that are part of the network and enable
145:59 that are part of the network and enable applications
146:01 applications this involves a rich set of different
146:03 this involves a rich set of different processes that enable packet forwarding
146:05 processes that enable packet forwarding on an ip network and may include
146:08 on an ip network and may include network management tools quality of
146:10 network management tools quality of service
146:11 service security mechanisms high availability
146:15 security mechanisms high availability voice transport and content networking
146:18 voice transport and content networking we will cover all of these topics in
146:20 we will cover all of these topics in this video
146:22 this video so let's begin with network management
146:25 so let's begin with network management network management is an intelligent
146:27 network management is an intelligent network service that allows the
146:29 network service that allows the management and monitoring of the server
146:31 management and monitoring of the server farm
146:32 farm and network devices in different blocks
146:35 and network devices in different blocks also when or lan connections
146:38 also when or lan connections this also involves system administration
146:41 this also involves system administration for servers with software tools specific
146:43 for servers with software tools specific to each operating system provider or
146:46 to each operating system provider or third-party tools network management
146:49 third-party tools network management also includes logging
146:51 also includes logging usually through a syslog server
146:52 usually through a syslog server implementation
146:54 implementation or security features such as
146:56 or security features such as one-time password or otp
146:59 one-time password or otp next let's discuss quality of service
147:02 next let's discuss quality of service quality of service invokes a wide
147:04 quality of service invokes a wide variety of techniques used
147:06 variety of techniques used especially in networks that offer
147:08 especially in networks that offer multimedia services voice and or video
147:11 multimedia services voice and or video because these services are usually delay
147:13 because these services are usually delay sensitive and require low latency and
147:15 sensitive and require low latency and low jitter
147:16 low jitter traffic generated by these applications
147:18 traffic generated by these applications must be prioritized which is the role of
147:21 must be prioritized which is the role of qos techniques
147:23 qos techniques in this example we have voice coming
147:26 in this example we have voice coming from a telephone hitting a switch
147:28 from a telephone hitting a switch and that's fine but as soon as it goes
147:30 and that's fine but as soon as it goes upstream let's say to the distribution
147:31 upstream let's say to the distribution layer or the core layer there's going to
147:33 layer or the core layer there's going to be contention other traffic is going to
147:36 be contention other traffic is going to be fighting
147:37 be fighting with this traffic for priority so we
147:40 with this traffic for priority so we want to move the voice because of its
147:42 want to move the voice because of its very nature to quote unquote a fast lane
147:45 very nature to quote unquote a fast lane or an express lane
147:46 or an express lane and therefore through qos
147:48 and therefore through qos proper marking of traffic and servicing
147:52 proper marking of traffic and servicing of those markings
147:53 of those markings the voice traffic can be given higher
147:55 the voice traffic can be given higher priority
147:57 priority that's just one example of how qos can
148:00 that's just one example of how qos can be used in your network
148:02 be used in your network please note qos is never supposed to be
148:05 please note qos is never supposed to be the first solution to solve problems
148:07 the first solution to solve problems it's really supposed to be used as a
148:09 it's really supposed to be used as a last resort ideally you have enough
148:12 last resort ideally you have enough bandwidth to service any application
148:15 bandwidth to service any application that needs to communicate over your
148:16 that needs to communicate over your network for the times that you do not
148:19 network for the times that you do not have enough bandwidth or you're
148:20 have enough bandwidth or you're concerned about performance then quality
148:22 concerned about performance then quality of service would be crucial to give
148:25 of service would be crucial to give priority to the traffic when there is
148:27 priority to the traffic when there is contention to give priority to the high
148:29 contention to give priority to the high priority traffic such as voice or video
148:35 priority traffic such as voice or video next let's talk about network security
148:37 next let's talk about network security security is an intelligent service and
148:40 security is an intelligent service and it's vital to the health of a network
148:42 it's vital to the health of a network security invokes such features as
148:45 security invokes such features as authentication services such as radius
148:47 authentication services such as radius or attack x
148:48 or attack x encryption
148:50 encryption and filtering
148:52 and filtering network security design principles are
148:54 network security design principles are presented later in the ccda
148:57 presented later in the ccda video series but please note that this
149:00 video series but please note that this is a part of intelligent network
149:02 is a part of intelligent network services from cisco
149:08 next is network availability network availability and network management are
149:11 availability and network management are two of the most critical technology
149:13 two of the most critical technology areas in network design
149:16 areas in network design these areas impact all other
149:18 these areas impact all other technologies presented to you in the
149:21 technologies presented to you in the ccda studies
149:22 ccda studies the focus of this section or this video
149:25 the focus of this section or this video right now is high availability network
149:27 right now is high availability network design
149:28 design high availability is often a factor
149:30 high availability is often a factor taken into consideration when designing
149:32 taken into consideration when designing end-to-end solutions
149:34 end-to-end solutions this assures redundancy for network
149:36 this assures redundancy for network services and for the end users and is
149:39 services and for the end users and is accomplished by ensuring that the
149:41 accomplished by ensuring that the network devices are reliable and fault
149:43 network devices are reliable and fault tolerant
149:45 tolerant many redundancy options can be utilized
149:47 many redundancy options can be utilized in different components of modern
149:49 in different components of modern networks
149:50 networks here are some examples
149:52 here are some examples workstation to router redundancy at the
149:54 workstation to router redundancy at the access layer
149:56 access layer server redundancy in the server farm
149:58 server redundancy in the server farm route redundancy
150:00 route redundancy media redundancy in the access layer
150:02 media redundancy in the access layer block each of these areas are now going
150:04 block each of these areas are now going to be covered in detail because you may
150:07 to be covered in detail because you may be tested in detail on any of these in
150:09 be tested in detail on any of these in your ccda exam
150:12 your ccda exam the most important topic in the list of
150:15 the most important topic in the list of redundancy that we've just spoken about
150:17 redundancy that we've just spoken about is workstation to router redundancy
150:19 is workstation to router redundancy because access devices must maintain
150:21 because access devices must maintain their default gateway information
150:24 their default gateway information if they don't most likely they're going
150:26 if they don't most likely they're going to lose network connectivity
150:29 to lose network connectivity as mentioned before modern networks
150:31 as mentioned before modern networks respect the 80 20 model which states
150:33 respect the 80 20 model which states that 80 of traffic will pass through a
150:36 that 80 of traffic will pass through a default gateway and 20 percent of the
150:38 default gateway and 20 percent of the destinations will be local
150:41 destinations will be local so this is a perfect example of why a
150:43 so this is a perfect example of why a default gateway
150:45 default gateway must be available
150:47 must be available workstation to router redundancy
150:50 workstation to router redundancy can be accomplished in multiple ways
150:53 can be accomplished in multiple ways first proxy arp this involves a
150:55 first proxy arp this involves a workstation that has no default gateway
150:57 workstation that has no default gateway configured but wants to communicate with
150:59 configured but wants to communicate with a remote host
151:00 a remote host a request for the address of the host is
151:03 a request for the address of the host is sent and the router that hears this
151:05 sent and the router that hears this request
151:06 request realizes that it can service it
151:09 realizes that it can service it that is it knows it can reach the client
151:11 that is it knows it can reach the client so it responds on behalf of the client
151:14 so it responds on behalf of the client using a proxy arp
151:16 using a proxy arp the router actually pretends to be the
151:17 the router actually pretends to be the host so the workstation can send traffic
151:20 host so the workstation can send traffic destined to that specific client to the
151:23 destined to that specific client to the router
151:24 router next is explicit configuration
151:27 next is explicit configuration this allows you to create multiple
151:29 this allows you to create multiple default gateways within the
151:31 default gateways within the configuration of an endpoint
151:33 configuration of an endpoint many operating systems allow for this
151:35 many operating systems allow for this programming of multiple default gateways
151:38 programming of multiple default gateways to be configured
151:40 to be configured but the most common way of establishing
151:42 but the most common way of establishing workstation redundancy is to use first
151:44 workstation redundancy is to use first hop redundancy protocols
151:47 hop redundancy protocols these are hsrp
151:49 these are hsrp vrrp and glbp
151:52 vrrp and glbp hsrp is a cisco proprietary first hop
151:56 hsrp is a cisco proprietary first hop redundancy protocol
151:58 redundancy protocol two versions of hsrp are supported on
152:00 two versions of hsrp are supported on ios software version one and this is the
152:03 ios software version one and this is the default hsrp version
152:06 default hsrp version and this restricts the number
152:08 and this restricts the number of configurable hsrp groups to 255.
152:11 of configurable hsrp groups to 255. i don't expect you should be exceeding
152:13 i don't expect you should be exceeding that anytime soon
152:16 that anytime soon and then there's version two
152:18 and then there's version two some updates to version two
152:21 some updates to version two it uses a new multicast address among
152:24 it uses a new multicast address among many other things that you can see here
152:35 finally hsrp authentication gives you the option of plain text or md5
152:38 the option of plain text or md5 authentication
152:43 md5 authentication can be configured with or without keychains
152:52 when implementing hsrp two or more routers are configured with a standby ip
152:54 routers are configured with a standby ip address on a broadcast interface usually
152:56 address on a broadcast interface usually an ethernet segment so while they will
152:59 an ethernet segment so while they will each have
153:00 each have a local ip address in this case dot two
153:03 a local ip address in this case dot two and dot three
153:04 and dot three a passive election is held to determine
153:06 a passive election is held to determine the active router which is actually
153:08 the active router which is actually answering for the gateway ip address dot
153:10 answering for the gateway ip address dot one the active router answers arp
153:13 one the active router answers arp requests for the standby ip address with
153:15 requests for the standby ip address with a virtual mac address so that the host
153:18 a virtual mac address so that the host sends packets to the gateway ip address
153:21 sends packets to the gateway ip address winds up sending it to the active router
153:23 winds up sending it to the active router now if the active router dies then
153:25 now if the active router dies then another election is held and in this
153:27 another election is held and in this case traffic would go out the dot 3
153:30 case traffic would go out the dot 3 interface even though
153:32 interface even though traffic would still be pointing to the
153:33 traffic would still be pointing to the virtual one ip address
153:40 vrrp is an open standard first hop redundancy protocol which elects a
153:42 redundancy protocol which elects a virtual router master and then virtual
153:44 virtual router master and then virtual router backups
153:46 router backups you can configure up to
153:47 you can configure up to 255 virtual routers on an interface
153:51 255 virtual routers on an interface that is if your system is capable of
153:53 that is if your system is capable of handling it
153:56 handling it the default vrrp priority value is 100
153:59 the default vrrp priority value is 100 and that's important to note because the
154:01 and that's important to note because the lower you set it the less likely it's
154:02 lower you set it the less likely it's going to take over as the master the
154:05 going to take over as the master the higher you set it the more likely it
154:06 higher you set it the more likely it will be
154:12 the virtual router master is in charge of sending advertisements to the other
154:14 of sending advertisements to the other routers in the same group and vrrp it
154:17 routers in the same group and vrrp it should be noted can support both
154:19 should be noted can support both plaintext and md5 authentication
154:27 so let's say we have three switches with vrrp which is non-proprietary
154:30 vrrp which is non-proprietary in vrrp one router is elected as the
154:33 in vrrp one router is elected as the virtual router master and the other
154:36 virtual router master and the other routers are acting as backups in case
154:38 routers are acting as backups in case the virtual router master fails
154:40 the virtual router master fails so in this case the master has been
154:42 so in this case the master has been elected
154:51 dot 3 and dot 4 will serve as backups 2.2
155:04 0.2 will answer to the virtual ip address and if it were to fail
155:07 address and if it were to fail then a backup device would take over
155:13 in this example that would be the dot 3 device
155:14 device and if the dot 3 system failed
155:18 and if the dot 3 system failed then the final backup system.4 would
155:20 then the final backup system.4 would take over
155:21 take over next let's cover glbp
155:24 next let's cover glbp glpp allows multiple gateways in the
155:26 glpp allows multiple gateways in the same glbp group to actively forward
155:29 same glbp group to actively forward traffic
155:30 traffic so instead of just one device forwarding
155:32 so instead of just one device forwarding traffic you can have multiple
155:35 traffic you can have multiple gateway gateways communicate via hellos
155:37 gateway gateways communicate via hellos messages that are sent by default every
155:39 messages that are sent by default every three seconds
155:41 three seconds the glbp group members elect one gateway
155:44 the glbp group members elect one gateway to be the avg
155:45 to be the avg now the avg answers all arp requests to
155:48 now the avg answers all arp requests to the virtual router address and assigns a
155:51 the virtual router address and assigns a virtual mac address to each member of
155:52 virtual mac address to each member of the glbp group
155:55 the glbp group glbp has many other features
155:58 glbp has many other features but you should really focus on the fact
156:00 but you should really focus on the fact that glbp does provide
156:02 that glbp does provide load sharing and many different load
156:04 load sharing and many different load sharing methods host dependent round
156:07 sharing methods host dependent round robin in weighted
156:09 robin in weighted and it does support plain text and or
156:11 and it does support plain text and or md5 authentication
156:14 md5 authentication but the big advantage and the question
156:16 but the big advantage and the question you're most likely to get regarding glbp
156:18 you're most likely to get regarding glbp is when would you use it and you would
156:20 is when would you use it and you would use it if you would like to load balance
156:22 use it if you would like to load balance between devices
156:24 between devices glbp provides a standby ip just as hsrp
156:27 glbp provides a standby ip just as hsrp but it also provides multiple virtual
156:29 but it also provides multiple virtual mac addresses so when a host on the
156:32 mac addresses so when a host on the connected network sends an arp request
156:34 connected network sends an arp request one of the routers answers with the
156:36 one of the routers answers with the virtual mac address
156:48 now this does allow for load balancing you can load balance across multiple
156:51 you can load balance across multiple systems instead of just relying on one
156:53 systems instead of just relying on one system to serve all the traffic
156:56 system to serve all the traffic in this case we're going to load balance
156:58 in this case we're going to load balance 50 percent to router 1 20 percent to
157:01 50 percent to router 1 20 percent to router 2 and 30 percent of the traffic
157:03 router 2 and 30 percent of the traffic to router three
157:08 this can be done because you're using virtual mac addresses
157:13 which take turns answering traffic requests
157:16 requests if a router were to fail the other
157:18 if a router were to fail the other remaining routers could take over for
157:20 remaining routers could take over for all the traffic
157:22 all the traffic next let's talk about server redundancy
157:25 next let's talk about server redundancy server-based redundancy technologies can
157:27 server-based redundancy technologies can be implemented in server farms or data
157:30 be implemented in server farms or data centers
157:31 centers this is often needed to ensure high
157:33 this is often needed to ensure high availability for key server functions
157:36 availability for key server functions such as file or application sharing
157:39 such as file or application sharing one way to solve this problem is to
157:41 one way to solve this problem is to mirror multiple servers so that if one
157:43 mirror multiple servers so that if one server fails the network can dynamically
157:46 server fails the network can dynamically fail over to another server
157:48 fail over to another server with cloud computing this obviously
157:50 with cloud computing this obviously becomes a non-issue the servers become
157:53 becomes a non-issue the servers become more virtual in nature the only time you
157:56 more virtual in nature the only time you would truly need redundancy would be if
157:59 would truly need redundancy would be if you're concerned about an entire area or
158:01 you're concerned about an entire area or entire city losing connectivity due to a
158:04 entire city losing connectivity due to a major catastrophe
158:06 major catastrophe then you could make sure that your data
158:08 then you could make sure that your data is replicated throughout the cloud maybe
158:11 is replicated throughout the cloud maybe even to different cloud
158:12 even to different cloud providers next let's talk about route
158:15 providers next let's talk about route redundancy with wan configuration
158:17 redundancy with wan configuration configuring redundancy between the
158:19 configuring redundancy between the campus infrastructures
158:21 campus infrastructures is a best practice
158:22 is a best practice in order to achieve this you can
158:24 in order to achieve this you can implement load balancing at the routing
158:26 implement load balancing at the routing protocols level this increases
158:29 protocols level this increases availability because in the case of a
158:31 availability because in the case of a direct path failure as you can see here
158:33 direct path failure as you can see here between two sites
158:35 between two sites these two sites can still reach each
158:37 these two sites can still reach each other by going via a different location
158:41 other by going via a different location next is media redundancy
158:44 next is media redundancy this is useful in case one link fails
158:48 this is useful in case one link fails media redundancy demands the
158:50 media redundancy demands the configuration of spanning tree protocol
158:52 configuration of spanning tree protocol at layer two
158:54 at layer two in order to avoid loops that can bring
158:56 in order to avoid loops that can bring the network down
159:02 another technology used to achieve media redundancy is ether channel
159:04 redundancy is ether channel this layer 2 logical bundling or channel
159:07 this layer 2 logical bundling or channel aggregation technique can be used
159:09 aggregation technique can be used between switches the bundled links can
159:12 between switches the bundled links can appear as one single link between
159:14 appear as one single link between specific devices
159:17 specific devices now should there be a link failure
159:18 now should there be a link failure between two switches data will continue
159:20 between two switches data will continue to pass using the existing configuration
159:24 to pass using the existing configuration even though there would not be as much
159:25 even though there would not be as much bandwidth available but data would still
159:28 bandwidth available but data would still pass because you have this redundant
159:30 pass because you have this redundant connectivity through ether channel
159:33 connectivity through ether channel next let's talk about voice transport
159:36 next let's talk about voice transport voice transport is a network solution
159:39 voice transport is a network solution that is implemented on top of the
159:40 that is implemented on top of the existing network infrastructure
159:43 existing network infrastructure when designing voice transport solutions
159:45 when designing voice transport solutions you must carefully consider the existing
159:47 you must carefully consider the existing enterprise network already in place
159:50 enterprise network already in place and it's very important that you first
159:51 and it's very important that you first implement the data solution
159:53 implement the data solution after that you can integrate voice and
159:55 after that you can integrate voice and data on the same network infrastructure
160:00 data on the same network infrastructure next let's talk about content networking
160:02 next let's talk about content networking content networking is also known as cdn
160:06 content networking is also known as cdn or content delivery networking
160:08 or content delivery networking it's a service that is used more and
160:10 it's a service that is used more and more in modern and large enterprise
160:12 more in modern and large enterprise networks and it offers more
160:14 networks and it offers more sophisticated types of network solutions
160:16 sophisticated types of network solutions and applications that accommodate video
160:19 and applications that accommodate video and voice for online services
160:22 and voice for online services using intranet in internet broadcast
160:24 using intranet in internet broadcast this can be delivered as training
160:26 this can be delivered as training modules using different audio and visual
160:30 modules using different audio and visual streaming technologies
160:32 streaming technologies but content networking demands content
160:35 but content networking demands content aware technologies from a cisco
160:37 aware technologies from a cisco environment in the campus infrastructure
160:40 environment in the campus infrastructure including content and wear hardware and
160:42 including content and wear hardware and content aware software
160:45 content aware software so there are three technologies we want
160:47 so there are three technologies we want to talk about
160:49 to talk about content routing
160:50 content routing content caching and content switching
160:54 content caching and content switching the first component of cdn content
160:56 the first component of cdn content routing is the process that actually
160:58 routing is the process that actually redirects a user to the best device in
161:01 redirects a user to the best device in the network
161:02 the network based on a set of well-defined user
161:04 based on a set of well-defined user policies there are specific rules for
161:07 policies there are specific rules for the different types of content delivered
161:09 the different types of content delivered in the network infrastructure
161:11 in the network infrastructure one rule might be the server load if it
161:13 one rule might be the server load if it is high in one place the rule may
161:16 is high in one place the rule may dictate that traffic is forwarded in a
161:18 dictate that traffic is forwarded in a different way
161:19 different way content routing can deliver the contents
161:21 content routing can deliver the contents as quickly as possible using high
161:24 as quickly as possible using high availability techniques and fast server
161:26 availability techniques and fast server responses
161:28 responses next is content caching
161:30 next is content caching from a cisco standpoint content caching
161:33 from a cisco standpoint content caching could be delivered by a cce or cisco
161:36 could be delivered by a cce or cisco content engine
161:38 content engine and this module can be found on a router
161:41 and this module can be found on a router this speeds up the delivery of content
161:43 this speeds up the delivery of content for end users because it transparently
161:45 for end users because it transparently caches information
161:47 caches information used on a regular basis as well as
161:49 used on a regular basis as well as frequently accessed content so the
161:52 frequently accessed content so the request can be fulfilled locally
161:56 request can be fulfilled locally finally content switching the third
161:58 finally content switching the third component of cdn which is known as web
162:01 component of cdn which is known as web switching or content switching this is
162:04 switching or content switching this is used for content delivery to different
162:06 used for content delivery to different network modules
162:07 network modules and is a sophisticated mechanism for
162:09 and is a sophisticated mechanism for load balancing and for accelerating the
162:11 load balancing and for accelerating the intelligence of the content
162:14 intelligence of the content content switching gives users a much
162:16 content switching gives users a much better web experience
162:18 better web experience by delivering the content much more
162:20 by delivering the content much more quickly and by customizing the content
162:22 quickly and by customizing the content for individual users
162:25 for individual users so here's what you've learned you've
162:26 so here's what you've learned you've learned about cisco intelligent network
162:28 learned about cisco intelligent network services
162:29 services specifically network management tools
162:32 specifically network management tools quality of service mechanisms
162:34 quality of service mechanisms security mechanisms high availability
162:37 security mechanisms high availability voice transport and content networking
162:41 voice transport and content networking for some of these we cover them higher
162:42 for some of these we cover them higher level because the information is
162:44 level because the information is available for you in other videos such
162:46 available for you in other videos such as network management tools and security
162:49 as network management tools and security mechanisms
162:50 mechanisms all of this information you'll need to
162:52 all of this information you'll need to do well on your cca exam and i hope this
162:54 do well on your cca exam and i hope this video has been helpful good luck in your
162:56 video has been helpful good luck in your studies thank you
163:22 hi this is david voss ccie113 and in this video you're going to learn
163:25 and in this video you're going to learn about geographical and application
163:29 about geographical and application considerations in network design
163:33 considerations in network design first let's begin with geographical
163:35 first let's begin with geographical considerations
163:37 considerations the geographical considerations
163:39 the geographical considerations regarding the enterprise campus network
163:41 regarding the enterprise campus network design
163:42 design involve locating the entire campus
163:44 involve locating the entire campus building blocks and the components of
163:46 building blocks and the components of those blocks
163:47 those blocks and then determining the distance
163:49 and then determining the distance between them
163:51 between them the geographical structures can be
163:53 the geographical structures can be broken down into four different types of
163:55 broken down into four different types of geography
163:57 geography intra building which is inside the
163:59 intra building which is inside the building
164:00 building inter building
164:01 inter building between buildings
164:03 between buildings remote building which is relatively
164:06 remote building which is relatively close which is less than 100 kilometers
164:08 close which is less than 100 kilometers away
164:09 away or a remote building that is greater
164:12 or a remote building that is greater than 100 kilometers away
164:15 than 100 kilometers away first let's begin with intra building
164:18 first let's begin with intra building design
164:23 an intra building structure can be comprised of a single floor or multiple
164:25 comprised of a single floor or multiple floors
164:26 floors but it's in a single building
164:28 but it's in a single building the goal is to connect all the different
164:30 the goal is to connect all the different components such as servers workstations
164:33 components such as servers workstations printers
164:34 printers and give all of them access to the
164:35 and give all of them access to the network resources depending on their
164:38 network resources depending on their type of system
164:40 type of system the access and distribution layers are
164:42 the access and distribution layers are typically located in an intra building
164:44 typically located in an intra building area
164:45 area user workstations are connected either
164:47 user workstations are connected either to a wiring closet or directly to an
164:49 to a wiring closet or directly to an access layer switch
164:51 access layer switch that is connected to a distribution
164:53 that is connected to a distribution layer switches and then ultimately those
164:55 layer switches and then ultimately those are connected into the core
164:57 are connected into the core interior building design
164:59 interior building design now with this network structure links
165:02 now with this network structure links this links individual buildings in the
165:04 this links individual buildings in the campus
165:05 campus or corporate complex using the
165:07 or corporate complex using the distribution layer or it could be at the
165:09 distribution layer or it could be at the core layer as well depending on the size
165:11 core layer as well depending on the size of the organization the distance between
165:14 of the organization the distance between buildings
165:15 buildings should range from a few hundred meters
165:17 should range from a few hundred meters to a few kilometers usually less than
165:19 to a few kilometers usually less than one mile
165:21 one mile the connection between the building
165:22 the connection between the building should provide as high bandwidth and
165:24 should provide as high bandwidth and throughput as possible
165:27 throughput as possible now another issue is ensuring that there
165:29 now another issue is ensuring that there is very little environmental
165:31 is very little environmental interference
165:32 interference so the typical medium
165:34 so the typical medium used in this case is optical fiber
165:37 used in this case is optical fiber the optical fiber used can be either
165:40 the optical fiber used can be either multi-mode fiber or single mode fiber
165:47 multi-mode and single-mode fiber share common characteristics
165:49 common characteristics the cabling uses glass or plastic fibers
165:53 the cabling uses glass or plastic fibers to move the information from building to
165:55 to move the information from building to building
165:57 building they're made the cables are made from a
165:58 they're made the cables are made from a bundle of threads each of which can
166:01 bundle of threads each of which can transmit messages
166:03 transmit messages modulated under light waves
166:06 modulated under light waves optical fiber has greater bandwidth than
166:08 optical fiber has greater bandwidth than copper cables so it can carry more data
166:12 copper cables so it can carry more data and it is less susceptible to
166:13 and it is less susceptible to interference
166:16 interference fiber optic cables
166:18 fiber optic cables are also much thinner and lighter than
166:20 are also much thinner and lighter than metal wires
166:22 metal wires and data can be transmitted digitally
166:24 and data can be transmitted digitally which is the natural way in which
166:26 which is the natural way in which computer data moves rather than through
166:28 computer data moves rather than through analog signaling signaling
166:31 analog signaling signaling now the big disadvantage of fiber optic
166:34 now the big disadvantage of fiber optic is that the cables are more expensive to
166:36 is that the cables are more expensive to install they're often more fragile and
166:40 install they're often more fragile and difficult to split up
166:42 difficult to split up but despite these disadvantages fiber
166:44 but despite these disadvantages fiber optic cabling is becoming more and more
166:46 optic cabling is becoming more and more popular for local area networking and
166:48 popular for local area networking and telecom provider infrastructure
166:55 let's look at the differences between multi-mode and single mode fiber
166:58 multi-mode and single mode fiber multi-mode has the following
167:00 multi-mode has the following characteristics
167:02 characteristics specific installation and performance
167:03 specific installation and performance guidelines it also has specific
167:05 guidelines it also has specific connectors
167:07 connectors concurrently transports multiple
167:09 concurrently transports multiple lightweight waves and modes within the
167:11 lightweight waves and modes within the core
167:12 core used for relatively short distances
167:15 used for relatively short distances typical diameter is 50 to 62.5
167:18 typical diameter is 50 to 62.5 micrometers bandwidth is usually up to
167:21 micrometers bandwidth is usually up to 10 gigabits per second
167:24 10 gigabits per second range is 550 meters when using gigabit
167:27 range is 550 meters when using gigabit ethernet
167:29 ethernet used between nodes and between buildings
167:32 used between nodes and between buildings and it's obviously more expensive than
167:34 and it's obviously more expensive than copper
167:35 copper single mode fiber has the following
167:37 single mode fiber has the following characteristics
167:39 characteristics specific installation and performance
167:41 specific installation and performance guidelines
167:43 guidelines carries a single light laser
167:46 carries a single light laser typical diameter of core is 2 to 10
167:49 typical diameter of core is 2 to 10 micrometers
167:51 micrometers bandwidth is usually up to 10 gigabits
167:54 bandwidth is usually up to 10 gigabits per second
167:55 per second range is up to 100 kilometers when using
167:58 range is up to 100 kilometers when using gigabit ethernet
168:04 but the key to remember is single mode is used between nodes and buildings for
168:06 is used between nodes and buildings for longer distances than multi-mode fiber
168:16 next let's talk about remote buildings the campus infrastructure can be spread
168:18 the campus infrastructure can be spread over a metropolitan area
168:21 over a metropolitan area or over a larger area than that so
168:23 or over a larger area than that so different parts of a city
168:25 different parts of a city and if you're dealing with distances
168:26 and if you're dealing with distances within a few miles you might focus on
168:28 within a few miles you might focus on the physical needs first you need to
168:30 the physical needs first you need to determine whether the company owns any
168:32 determine whether the company owns any of the copper lines and if it does you
168:34 of the copper lines and if it does you can build from there
168:36 can build from there but you also might need to connect an
168:37 but you also might need to connect an enterprise campus network through the
168:39 enterprise campus network through the wan block
168:41 wan block now if this is the case you should
168:43 now if this is the case you should leverage the existing telecom providers
168:45 leverage the existing telecom providers in that specific area
168:47 in that specific area then you also may want to consider using
168:50 then you also may want to consider using satellite or various wireless
168:51 satellite or various wireless technologies to connect your site as
168:54 technologies to connect your site as well
168:56 well but as the distance between the sites
168:58 but as the distance between the sites grows the following actions will occur
169:01 grows the following actions will occur connectivity costs increase
169:04 connectivity costs increase required throughput will decrease
169:07 required throughput will decrease and importance of availability will
169:10 and importance of availability will decrease
169:12 decrease next let's talk about network
169:13 next let's talk about network applications
169:15 applications another important factor when designing
169:16 another important factor when designing campus switching is considering the
169:18 campus switching is considering the network applications that will be used
169:21 network applications that will be used once the physical and geographical
169:23 once the physical and geographical aspects are clear the network designer
169:25 aspects are clear the network designer needs to characterize what types of
169:27 needs to characterize what types of applications will be processed within
169:28 applications will be processed within the network
169:30 the network the first category of applications that
169:32 the first category of applications that must be identified involves the critical
169:34 must be identified involves the critical or core applications
169:36 or core applications and the rest of the services fall under
169:37 and the rest of the services fall under the optional intelligence category
169:41 the optional intelligence category the network applications can be divided
169:43 the network applications can be divided into four types
169:44 into four types client to client applications
169:47 client to client applications client to distributed server
169:48 client to distributed server applications
169:50 applications client to server farm applications and
169:53 client to server farm applications and client enterprise edge applications
169:57 client enterprise edge applications so here's what you've learned you've
169:58 so here's what you've learned you've learned about design considerations
170:01 learned about design considerations not only for geography but also for
170:04 not only for geography but also for application types
170:06 application types and then you need to know how to break
170:07 and then you need to know how to break out
170:08 out systematically
170:10 systematically what type of design challenges are you
170:13 what type of design challenges are you facing
170:14 facing so that you just aren't trying to design
170:16 so that you just aren't trying to design generally but you're being specific
170:18 generally but you're being specific about the geographical issues you're
170:21 about the geographical issues you're facing but also the network applications
170:24 facing but also the network applications that you need to support
170:26 that you need to support i wish you the best of luck in your
170:27 i wish you the best of luck in your studies thank you
170:52 hi this is david voss ccie 11372 and in this video you're going to learn about
170:53 this video you're going to learn about layer 2 technologies
170:55 layer 2 technologies and layer 3 switching
170:58 and layer 3 switching let's begin first with layer 2
171:00 let's begin first with layer 2 technologies
171:02 technologies layer 2 technologies relate to the osi
171:04 layer 2 technologies relate to the osi data link layer
171:07 data link layer now today's modern enterprise which is a
171:09 now today's modern enterprise which is a distributed networking world of
171:12 distributed networking world of multimedia and client applications
171:16 multimedia and client applications dictates the need for greater bandwidth
171:19 dictates the need for greater bandwidth and a greater degree of control
171:22 and a greater degree of control over the past 10 years almost all
171:24 over the past 10 years almost all organizations have replaced their shared
171:26 organizations have replaced their shared networking technology such as hubs
171:30 networking technology such as hubs with switches to create switched
171:32 with switches to create switched technologies
171:37 a concept you need to understand is a collision domain and what exactly a
171:39 collision domain and what exactly a collision domain is
171:41 collision domain is a collision domain is comprised of nodes
171:44 a collision domain is comprised of nodes and devices that share the same
171:46 and devices that share the same bandwidth
171:47 bandwidth and this is called a bandwidth domain
171:50 and this is called a bandwidth domain for instance everything that is
171:51 for instance everything that is connected to a switch port via a hub is
171:54 connected to a switch port via a hub is in the same collision domain
171:56 in the same collision domain this means there is always the
171:58 this means there is always the possibility of a collision in the
172:00 possibility of a collision in the operations of that particular ethernet
172:03 operations of that particular ethernet a broadcast domain on the other hand
172:05 a broadcast domain on the other hand represents a collection of devices that
172:07 represents a collection of devices that can see each other's broadcast
172:10 can see each other's broadcast or multicast packets
172:12 or multicast packets nodes that are in the same collision
172:14 nodes that are in the same collision domain are also in the same broadcast
172:17 domain are also in the same broadcast domain
172:18 domain for example all devices associated with
172:21 for example all devices associated with the port of a router are in the same
172:23 the port of a router are in the same broadcast domain
172:26 broadcast domain and by default broadcasts do not
172:28 and by default broadcasts do not traverse a router's port interface
172:32 traverse a router's port interface when a shared technology is used such as
172:34 when a shared technology is used such as hubs
172:36 hubs all the devices share the bandwidth of
172:38 all the devices share the bandwidth of the specific network segment
172:41 the specific network segment when using switched technologies each
172:44 when using switched technologies each device in the switch port is its own
172:46 device in the switch port is its own collision domain
172:47 collision domain however all the devices are in the same
172:50 however all the devices are in the same broadcast domain
172:58 now here's some of the basics you know why land switches why did they overtake
173:00 why land switches why did they overtake the market there was a time when bridges
173:02 the market there was a time when bridges were quite popular well land switches
173:04 were quite popular well land switches have quite a few advantages over bridges
173:08 have quite a few advantages over bridges specifically they have more ports than a
173:10 specifically they have more ports than a bridge would ever be capable of
173:12 bridge would ever be capable of supporting
173:13 supporting micro segmentation allows individual
173:16 micro segmentation allows individual hosts to be connected to individual
173:18 hosts to be connected to individual ports
173:19 ports they operate at hardware speed using
173:21 they operate at hardware speed using asics versus software used by bridges
173:24 asics versus software used by bridges they support layer 3 and layer 4 packet
173:27 they support layer 3 and layer 4 packet switching by using mls features we'll
173:29 switching by using mls features we'll talk about that a little bit later
173:31 talk about that a little bit later and finally probably the most important
173:33 and finally probably the most important feature of land switching nowadays is
173:37 feature of land switching nowadays is the the vlan so they can use vlans to
173:39 the the vlan so they can use vlans to create smaller logical broadcast domains
173:42 create smaller logical broadcast domains on your network
173:46 now let's just see let's just get back to basics here land switching is a form
173:49 to basics here land switching is a form of packet switching
173:51 of packet switching which is used on local area networks
173:54 which is used on local area networks land switches provide
173:56 land switches provide and as you already know they provide
173:57 and as you already know they provide much higher port density and at a much
174:00 much higher port density and at a much lower cost than traditional bridges did
174:04 lower cost than traditional bridges did now there are three
174:05 now there are three now there are three main forwarding
174:07 now there are three main forwarding techniques that can be used by switches
174:10 techniques that can be used by switches store and forward
174:12 store and forward cut through
174:13 cut through and fragment free
174:19 let's just do a basic drawing here to better understand these concepts so
174:21 better understand these concepts so let me draw out first a frame that is
174:23 let me draw out first a frame that is passing through a switch
174:26 passing through a switch and then after i draw this frame i'm
174:29 and then after i draw this frame i'm going to draw a line here and that will
174:31 going to draw a line here and that will designate the memory of the switch so
174:34 designate the memory of the switch so if the frame is passed into memory we
174:37 if the frame is passed into memory we will designate it by going underneath
174:39 will designate it by going underneath this line
174:46 let's cover cut through switching first with cut through switching the lan
174:48 with cut through switching the lan switch
174:48 switch copies into its memory only the
174:51 copies into its memory only the destination mac address which is located
174:54 destination mac address which is located in the first six bytes of the frame
174:57 in the first six bytes of the frame the switch looks up the destination mac
175:00 the switch looks up the destination mac address in its switching table and
175:01 address in its switching table and determines the outgoing interface port
175:04 determines the outgoing interface port then forwards the frame to its
175:06 then forwards the frame to its destination through the designated
175:08 destination through the designated switch port
175:10 switch port a cut through switch reduces delay
175:11 a cut through switch reduces delay because the switch begins to forward the
175:13 because the switch begins to forward the frame as soon as it reads the
175:15 frame as soon as it reads the destination mac address
175:17 destination mac address this is in contrast to store and forward
175:20 this is in contrast to store and forward switching
175:21 switching store and forward switching means that
175:22 store and forward switching means that the lan switch copies each complete
175:25 the lan switch copies each complete frame into its switch memory buffers
175:27 frame into its switch memory buffers and then it computes a crc check for
175:30 and then it computes a crc check for errors
175:31 errors the crc check uses a mathematical
175:33 the crc check uses a mathematical formula to determine whether the frame
175:36 formula to determine whether the frame is errored and if an error is found it's
175:38 is errored and if an error is found it's discarded but if it's error free the
175:41 discarded but if it's error free the switch will forward the frame out the
175:42 switch will forward the frame out the appropriate interface port
175:45 appropriate interface port finally there's fragment free switching
175:47 finally there's fragment free switching which is also known as runtless
175:49 which is also known as runtless switching
175:50 switching basically
175:52 basically frames that are damaged which often
175:54 frames that are damaged which often happen by collisions are often shorter
175:56 happen by collisions are often shorter than the minimum valid ethernet frame
175:58 than the minimum valid ethernet frame size of 64 bytes
176:00 size of 64 bytes if a frame is smaller than 64 bytes
176:04 if a frame is smaller than 64 bytes the switch will discard that frame
176:07 the switch will discard that frame fragment free is a faster mode than
176:09 fragment free is a faster mode than storing forward but there still exists a
176:12 storing forward but there still exists a risk of forwarding bad frames
176:15 risk of forwarding bad frames because you do not have the crc check
176:19 because you do not have the crc check now land switching can be characterized
176:21 now land switching can be characterized as either symmetric or asymmetric now
176:23 as either symmetric or asymmetric now symmetric switching provides evenly
176:25 symmetric switching provides evenly distributed bandwidth to each port on
176:27 distributed bandwidth to each port on the switch this is typically used in a
176:29 the switch this is typically used in a peer-to-peer desktop environment where
176:31 peer-to-peer desktop environment where you see asymmetric switching is when
176:34 you see asymmetric switching is when we're talking about
176:35 we're talking about endpoints communicating with
176:38 endpoints communicating with bandwidth intensive services such as
176:41 bandwidth intensive services such as servers so this provides unequal
176:43 servers so this provides unequal bandwidth between ports on a switch this
176:46 bandwidth between ports on a switch this is actually the most common type of
176:47 is actually the most common type of switching and it's optimized for client
176:50 switching and it's optimized for client server environments you may have a
176:52 server environments you may have a server that demands a 10 gigabit port
176:54 server that demands a 10 gigabit port where many of your clients obviously
176:56 where many of your clients obviously don't need that much speed and may only
176:58 don't need that much speed and may only have a one gigabit port or if you have
177:00 have a one gigabit port or if you have an older switch 100 megabit port
177:09 now in the old days
177:11 in the old days basic rule of thumb in designing a local
177:13 basic rule of thumb in designing a local area network and wide area network was
177:15 area network and wide area network was that 80 of the traffic was going to
177:17 that 80 of the traffic was going to remain on the local area network thus it
177:19 remain on the local area network thus it was called the 80 20 rule 80 of the
177:22 was called the 80 20 rule 80 of the traffic stays local and you should plan
177:24 traffic stays local and you should plan for that
177:25 for that well with the advent and the with the
177:27 well with the advent and the with the popularity of the internet and server
177:30 popularity of the internet and server farms uh this has really resulted in the
177:33 farms uh this has really resulted in the flipping of those numbers now we need to
177:35 flipping of those numbers now we need to design our networks
177:37 design our networks with with the idea that probably only 20
177:40 with with the idea that probably only 20 percent of the traffic is going to stay
177:41 percent of the traffic is going to stay local
177:42 local on the local area network whereas 80
177:45 on the local area network whereas 80 percent is going to be is going to leave
177:47 percent is going to be is going to leave the local area network so this new
177:50 the local area network so this new paradigm this new 20 20 80 rule
177:53 paradigm this new 20 20 80 rule places a much greater burden on the
177:55 places a much greater burden on the network backbone
178:02 next let's talk about layer 3 switching historically land switching typically
178:04 historically land switching typically involves layer 2 switching at the access
178:06 involves layer 2 switching at the access layer and sometimes at the distribution
178:08 layer and sometimes at the distribution layer
178:09 layer layer 2 switches forward information
178:11 layer 2 switches forward information based only on the mac address that is
178:14 based only on the mac address that is the layer 2 frame address
178:16 the layer 2 frame address layer 3 switching however uses the mac
178:18 layer 3 switching however uses the mac address in addition to the layer 3
178:21 address in addition to the layer 3 address which is typically
178:23 address which is typically nowadays an ip address
178:26 nowadays an ip address the following three options exist when
178:28 the following three options exist when considering designing a switched
178:30 considering designing a switched environment
178:32 environment layer 2 switching throughout the network
178:35 layer 2 switching throughout the network a combination of layer 2 and layer 3
178:37 a combination of layer 2 and layer 3 switching
178:39 switching and then layer 3 stitching throughout
178:41 and then layer 3 stitching throughout the network
178:43 the network using layer 2 switching layer 3
178:45 using layer 2 switching layer 3 switching or a combination of the two
178:48 switching or a combination of the two also depends on the available switching
178:50 also depends on the available switching platforms
178:51 platforms as not all switches support layer 3
178:53 as not all switches support layer 3 technologies
178:59 at the heart of a switch network is the concept of vlans
179:01 concept of vlans so what exactly is a vlan well cisco
179:04 so what exactly is a vlan well cisco says it's a group of end stations with a
179:06 says it's a group of end stations with a common set of requirements
179:08 common set of requirements using vlans allows you to put
179:11 using vlans allows you to put many different devices in many different
179:13 many different devices in many different locations on the same
179:15 locations on the same logical network on the same layer 2
179:18 logical network on the same layer 2 network
179:19 network in the past without vlans
179:22 in the past without vlans you would have to rely upon
179:24 you would have to rely upon simple hardware solutions but a vlan
179:27 simple hardware solutions but a vlan allows you to virtualize your layer 2
179:29 allows you to virtualize your layer 2 segment
179:31 segment vlans are usually associated by the same
179:34 vlans are usually associated by the same subnet so normally devices on a vlan
179:38 subnet so normally devices on a vlan are are sharing the same subnet
179:40 are are sharing the same subnet and and with this in mind
179:43 and and with this in mind they're sharing the same broadcast
179:45 they're sharing the same broadcast domain that is the norm
179:48 domain that is the norm and then vlans must be routed to
179:50 and then vlans must be routed to communicate with other vlans so it is a
179:53 communicate with other vlans so it is a true layer 2 segment
179:55 true layer 2 segment a vlan is not going to be able to
179:57 a vlan is not going to be able to communicate with another vlan
179:59 communicate with another vlan unless it is passed through a layer 3
180:02 unless it is passed through a layer 3 device which can route it
180:05 device which can route it now there are two types of switch port
180:07 now there are two types of switch port types
180:08 types for vlan membership that we need to
180:10 for vlan membership that we need to understand
180:11 understand and the first is
180:12 and the first is the access port
180:14 the access port now access ports can only belong to a
180:17 now access ports can only belong to a single vlan now when you think of an
180:18 single vlan now when you think of an access port
180:20 access port it's pretty much probably what you think
180:21 it's pretty much probably what you think of it's usually for end devices like a
180:23 of it's usually for end devices like a workstation or a server
180:26 workstation or a server it is a device that is an end station
180:28 it is a device that is an end station and again accessport can only belong to
180:31 and again accessport can only belong to a single vlan
180:33 a single vlan typically used to connect end devices
180:36 typically used to connect end devices and there are two methods to assign
180:38 and there are two methods to assign ports
180:39 ports uh to vlans
180:41 uh to vlans for these access ports the first which
180:43 for these access ports the first which is by far the the most popular
180:46 is by far the the most popular is the static vlan assignment so an
180:49 is the static vlan assignment so an administrator actually doing it and then
180:51 administrator actually doing it and then dynamic vlan assignment
180:54 dynamic vlan assignment which is done by a server so let's dig a
180:56 which is done by a server so let's dig a little bit more into that into those two
180:59 little bit more into that into those two concepts
181:00 concepts so
181:01 so when we have a static vlan assignment
181:04 when we have a static vlan assignment the network administrator is actually
181:06 the network administrator is actually manually configuring a switch port to be
181:08 manually configuring a switch port to be a part of a vlan
181:10 a part of a vlan the network administrator is saying is
181:12 the network administrator is saying is programming the port to say you are
181:14 programming the port to say you are going to be an access port and you're
181:17 going to be an access port and you're going to be associated with this
181:18 going to be associated with this specific vlan now you can do this
181:21 specific vlan now you can do this dynamically and this is not as popular
181:25 dynamically and this is not as popular but there is something called a vlan
181:27 but there is something called a vlan management policy server which can
181:29 management policy server which can assign a desired vlan to users
181:31 assign a desired vlan to users connecting to a switch
181:33 connecting to a switch we don't need to get much deeper than
181:35 we don't need to get much deeper than that
181:36 that for your exam but you need to do you do
181:38 for your exam but you need to do you do need to know these two methods
181:41 need to know these two methods now there's another type of port that we
181:43 now there's another type of port that we need to understand to understand the
181:45 need to understand to understand the concept of vlans and that is trunk ports
181:48 concept of vlans and that is trunk ports and trunk ports are used to carry data
181:50 and trunk ports are used to carry data from multiple vlans
181:52 from multiple vlans so
181:53 so access ports only allow communication
181:57 access ports only allow communication from one end device over a specific vlan
182:01 from one end device over a specific vlan well ultimately if you're hosting many
182:04 well ultimately if you're hosting many vlans
182:06 vlans this traffic's going to need to be able
182:07 this traffic's going to need to be able to communicate
182:09 to communicate throughout your network so that they're
182:11 throughout your network so that they're not limited
182:13 not limited limited by a hardware device so your
182:16 limited by a hardware device so your vlan may your vlans may be spread
182:18 vlan may your vlans may be spread throughout
182:19 throughout um many floors or
182:21 um many floors or maybe even many buildings
182:23 maybe even many buildings trunk ports allow you to carry data from
182:27 trunk ports allow you to carry data from all these different vlans between all
182:29 all these different vlans between all your different hardware devices
182:32 your different hardware devices now there are some standard vlan numbers
182:34 now there are some standard vlan numbers and ranges you should know um
182:36 and ranges you should know um specifically let's focus on two to 1001
182:39 specifically let's focus on two to 1001 these vlans are created and used and
182:42 these vlans are created and used and deleted on all cisco catalyst switches
182:46 deleted on all cisco catalyst switches and another one that you should really
182:47 and another one that you should really focus in on
182:48 focus in on is the range of 1006 to 4094.
182:52 is the range of 1006 to 4094. these are
182:54 these are extended this is an extended range of
182:56 extended this is an extended range of vlans for ethernet vlans only
183:00 vlans for ethernet vlans only now you may be asked about these other
183:02 now you may be asked about these other ranges but i would focus in on
183:04 ranges but i would focus in on vlan ranges 2 to 1001
183:07 vlan ranges 2 to 1001 and 1006 to 4094.
183:15 vlan trunks are used to carry data from multiple vlans which you already know
183:17 multiple vlans which you already know now there are two methods two protocols
183:20 now there are two methods two protocols that can be used
183:22 that can be used to build these trunks and the first is
183:25 to build these trunks and the first is inner switch link or isl
183:28 inner switch link or isl and that's a cisco proprietary protocol
183:30 and that's a cisco proprietary protocol that is used to preserve the source vlan
183:33 that is used to preserve the source vlan identification information
183:35 identification information for frames that traverse trunk links
183:38 for frames that traverse trunk links and then there is i would say the more
183:41 and then there is i would say the more popular 802.1 q
183:43 popular 802.1 q which is an open standard
183:45 which is an open standard and then it performs a little bit
183:47 and then it performs a little bit differently than the cisco proprietary
183:50 differently than the cisco proprietary protocol
183:52 protocol now the reason
183:53 now the reason 802.1q is so popular is you probably
183:56 802.1q is so popular is you probably understand that for obvious reasons that
183:58 understand that for obvious reasons that if you want a trunk between
184:01 if you want a trunk between two devices like one is cisco and one is
184:03 two devices like one is cisco and one is non-cisco
184:05 non-cisco you're able to do that
184:06 you're able to do that so this standard works very effectively
184:09 so this standard works very effectively and 802.1 q is very popular but you will
184:13 and 802.1 q is very popular but you will definitely be asked about isl
184:15 definitely be asked about isl and you will definitely be asked about
184:17 and you will definitely be asked about the differences between isl and 802.1q
184:23 now so you've received a lot of information
184:26 so you've received a lot of information right now so let's go ahead and kind of
184:28 right now so let's go ahead and kind of draw out some of these concepts that
184:30 draw out some of these concepts that we've been talking about
184:32 we've been talking about so
184:35 so when we think of vlans we think first of
184:37 when we think of vlans we think first of we need to connect
184:39 we need to connect endpoints need to connect on a local
184:41 endpoints need to connect on a local area network so
184:43 area network so here we have
184:45 here we have four endpoints
184:48 four endpoints and we have one switch
184:52 and we have one switch and each of these endpoints
184:54 and each of these endpoints need to communicate and not all of them
184:56 need to communicate and not all of them need to communicate with with each other
184:59 need to communicate with with each other so let's say we have two
185:02 so let's say we have two workstations and two servers
185:06 workstations and two servers and we're gonna put this one workstation
185:08 and we're gonna put this one workstation in vlan 10 and this other workstation in
185:11 in vlan 10 and this other workstation in vlan 10
185:12 vlan 10 and then these two servers in vlan 2.
185:15 and then these two servers in vlan 2. these two servers are segmented on their
185:17 these two servers are segmented on their own vlan and as are the workstations
185:20 own vlan and as are the workstations they cannot communicate between each
185:21 they cannot communicate between each other
185:22 other between vlan 2 and 10
185:25 between vlan 2 and 10 but anything on vlan 10 can communicate
185:27 but anything on vlan 10 can communicate with vlan 10. now here's another
185:29 with vlan 10. now here's another dedicated vlan we'll say vlan 3 to a
185:32 dedicated vlan we'll say vlan 3 to a dedicated device
185:34 dedicated device now and here is a router so for any of
185:37 now and here is a router so for any of these vlans to communicate with one
185:38 these vlans to communicate with one another they need to pass through a
185:39 another they need to pass through a layer 3 device
185:41 layer 3 device so this this workstation that from vlan
185:43 so this this workstation that from vlan 10 if it wants to communicate over to a
185:46 10 if it wants to communicate over to a server it needs to be routed and go
185:48 server it needs to be routed and go through the router and passed over to
185:50 through the router and passed over to vlan 2.
185:53 vlan 2. let's say you want to keep vlan 3
185:55 let's say you want to keep vlan 3 devices
185:57 devices not accessible from the network
185:59 not accessible from the network you can prevent that
186:01 you can prevent that so here we have other devices on vlan 3
186:04 so here we have other devices on vlan 3 and we'll say let's say this is a back
186:06 and we'll say let's say this is a back end connection between two servers that
186:07 end connection between two servers that we have no need to route it vlan 3 can
186:10 we have no need to route it vlan 3 can be segmented from the entire network
186:12 be segmented from the entire network nobody can reach it so there's some
186:14 nobody can reach it so there's some security built into vlans as well
186:17 security built into vlans as well now vlans can extend
186:18 now vlans can extend obviously over to other hardware
186:20 obviously over to other hardware platforms so this router is connected to
186:23 platforms so this router is connected to another switch
186:24 another switch and on this switch let's say that's in a
186:26 and on this switch let's say that's in a different building we have another
186:27 different building we have another device on vlan 2
186:29 device on vlan 2 another device
186:31 another device another endpoint
186:32 another endpoint on an access port to vlan 10
186:35 on an access port to vlan 10 and if they want to communicate over to
186:37 and if they want to communicate over to the other building let's say vlan 2 or
186:40 the other building let's say vlan 2 or vlan 10
186:41 vlan 10 they simply go over this trunk port you
186:44 they simply go over this trunk port you know that term
186:46 know that term goes over the trunk port and can
186:47 goes over the trunk port and can communicate over to
186:49 communicate over to the other sites
186:52 the other sites when designing a full layer 2
186:54 when designing a full layer 2 environment using vlans a router might
186:56 environment using vlans a router might be used to provide routing between the
187:00 be used to provide routing between the vlans
187:01 vlans this technique is called router on a
187:03 this technique is called router on a stick because only one router interface
187:05 stick because only one router interface is used to carry all the vlans
187:09 is used to carry all the vlans exclusively using layer 2 switches and
187:12 exclusively using layer 2 switches and vlans throughout the network all the
187:14 vlans throughout the network all the policies access lists and quality
187:16 policies access lists and quality service rules
187:17 service rules will be managed at the data link layer
187:20 will be managed at the data link layer the policy capabilities are very limited
187:23 the policy capabilities are very limited at the data link layer but they are
187:25 at the data link layer but they are greatly enhanced in layer 3 switches
187:29 greatly enhanced in layer 3 switches another area in which layer 2 switches
187:31 another area in which layer 2 switches are limited is load sharing capabilities
187:33 are limited is load sharing capabilities used to ensure redundant links
187:36 used to ensure redundant links that is multiple paths throughout the
187:38 that is multiple paths throughout the network
187:40 network this is because layer 2 switches only
187:42 this is because layer 2 switches only know about mac addresses and they cannot
187:44 know about mac addresses and they cannot perform intelligent load sharing
187:46 perform intelligent load sharing for example based on a destination
187:49 for example based on a destination network
187:50 network layer 3 switches can do that
187:53 layer 3 switches can do that layer 3 switches also support dynamic
187:55 layer 3 switches also support dynamic routing protocols
187:57 routing protocols therefore with layer 2 switching the
187:59 therefore with layer 2 switching the load can be shared only on a per vlan
188:02 load can be shared only on a per vlan basis
188:03 basis in addition when using layer 2 switches
188:05 in addition when using layer 2 switches only the basis of all failures or the
188:08 only the basis of all failures or the failure domain will be isolated to the
188:10 failure domain will be isolated to the vlan only
188:11 vlan only on the other hand in a multi-layer
188:13 on the other hand in a multi-layer environment the failures can be better
188:15 environment the failures can be better isolated at the access layer to the core
188:19 isolated at the access layer to the core layer or even particular network
188:21 layer or even particular network segments
188:23 segments in a layer 2 switched environment only
188:25 in a layer 2 switched environment only stp that is spanning tree protocol
188:28 stp that is spanning tree protocol offers convergence and loop control
188:30 offers convergence and loop control however when using layer 3 switching
188:32 however when using layer 3 switching this feature can also be implemented at
188:34 this feature can also be implemented at the distribution in core layers using
188:37 the distribution in core layers using routing protocol technologies such as
188:39 routing protocol technologies such as ospf or eigrp
188:42 ospf or eigrp and when considering cost using layer 2
188:44 and when considering cost using layer 2 everywhere is the cheapest solution but
188:47 everywhere is the cheapest solution but this is also much less flexible and much
188:50 this is also much less flexible and much less manageable
188:52 less manageable using layer 3 switches throughout the
188:54 using layer 3 switches throughout the network is the most expensive option
188:56 network is the most expensive option but it's very powerful and flexible
188:59 but it's very powerful and flexible a compromise would be to implement layer
189:01 a compromise would be to implement layer 3 switches only in the distribution
189:04 3 switches only in the distribution layer
189:04 layer and then eventually as the budget allows
189:07 and then eventually as the budget allows and the network scales extend the layer
189:09 and the network scales extend the layer 3 switches into the core layer
189:11 3 switches into the core layer for full layer 3 switching at the
189:14 for full layer 3 switching at the distribution
189:15 distribution and core layers
189:21 so in this video you've learned about layer 2 technologies and layer 3
189:24 layer 2 technologies and layer 3 switching and this will
189:28 switching and this will this information will provide you with a
189:29 this information will provide you with a solid foundation to do well on your ccda
189:32 solid foundation to do well on your ccda exam thank you
189:59 hi this is david voss ccie113 and in this video we're going to be
190:00 and in this video we're going to be covering the cable specifications for
190:03 covering the cable specifications for local area networks
190:05 local area networks specifically this video is going to
190:07 specifically this video is going to review
190:08 review land media and its components
190:11 land media and its components we need to identify some of the
190:13 we need to identify some of the constraints you should consider when
190:15 constraints you should consider when provisioning various land media types
190:18 provisioning various land media types ethernet is the underlying basis for the
190:20 ethernet is the underlying basis for the technologies most widely used in local
190:22 technologies most widely used in local area networks today
190:24 area networks today in the 1980s and early 1990s most
190:27 in the 1980s and early 1990s most networks used 10 megabit per second
190:30 networks used 10 megabit per second ethernet
190:31 ethernet defined initially by digital intel in
190:34 defined initially by digital intel in xerox
190:35 xerox and then later by the ieee 802.3 working
190:39 and then later by the ieee 802.3 working group the ieee
190:42 group the ieee 802.3-2002 standard
190:44 802.3-2002 standard contains physical specifications for
190:46 contains physical specifications for ethernet technologies
190:49 ethernet technologies up to 10 gigabits per second
190:52 up to 10 gigabits per second the following table is something you
190:54 the following table is something you should know well for your ccda exam it
190:57 should know well for your ccda exam it describes
190:58 describes the physical ethernet specifications up
191:01 the physical ethernet specifications up to 100 megabits per second
191:04 to 100 megabits per second it provides scalability information that
191:06 it provides scalability information that you can use when provisioning ieee 802.3
191:09 you can use when provisioning ieee 802.3 networks
191:11 networks of these specifications the 10 base 5
191:14 of these specifications the 10 base 5 and 10 base 2 are no longer used but are
191:17 and 10 base 2 are no longer used but are included for completeness
191:19 included for completeness fast ethernet is preferred over 10 base
191:22 fast ethernet is preferred over 10 base t ethernet
191:27 let's talk about some of the 100 megabit per second
191:28 per second fast ethernet design rules
191:32 fast ethernet design rules ieee introduced ieee 802.3
191:37 ieee introduced ieee 802.3 u-1995 standard to provide ethernet
191:40 u-1995 standard to provide ethernet speeds of 100 megabit per second over
191:42 speeds of 100 megabit per second over utp and fiber cabling
191:45 utp and fiber cabling the 100 base t standard is similar to 10
191:48 the 100 base t standard is similar to 10 megabits per second ethernet
191:51 megabits per second ethernet and that it uses carrier sense multiple
191:53 and that it uses carrier sense multiple access collision detect which you
191:55 access collision detect which you probably know is csma slash cd
192:03 let's discuss the following specifications for fast ethernet
192:07 specifications for fast ethernet 100 base tx fast ethernet
192:10 100 base tx fast ethernet this specification uses cat 5 utp wiring
192:14 this specification uses cat 5 utp wiring like 10 base t fast ethernet uses only
192:17 like 10 base t fast ethernet uses only two pairs of the four pair utp wiring
192:20 two pairs of the four pair utp wiring if cat5 cabling is already in place
192:22 if cat5 cabling is already in place upgrading to fast ethernet requires only
192:25 upgrading to fast ethernet requires only a hub or a switch
192:27 a hub or a switch and any network interface card upgrades
192:30 and any network interface card upgrades because of the low cost most of today's
192:32 because of the low cost most of today's installations use switches
192:34 installations use switches the specifications for the standard are
192:36 the specifications for the standard are as follows
192:38 as follows transmission over cat5 utp
192:40 transmission over cat5 utp an rj45 connector
192:43 an rj45 connector punch down blocks in the wiring closet
192:45 punch down blocks in the wiring closet must be cat5 certified
192:48 must be cat5 certified and
192:49 and 4b5b coding
192:56 let's discuss now the 100 base t4 fast ethernet standard
192:58 ethernet standard the hunter base t4 specification was
193:01 the hunter base t4 specification was developed to support utp wiring at the
193:03 developed to support utp wiring at the cat 3 level
193:05 cat 3 level this specification takes advantage of
193:07 this specification takes advantage of higher speed ethernet without re-cabling
193:10 higher speed ethernet without re-cabling to cat5 utp
193:12 to cat5 utp this implementation is not widely
193:14 this implementation is not widely deployed
193:16 deployed but here are the specifications it can
193:18 but here are the specifications it can transmit over cat 3 4 or 5 utp wiring
193:23 transmit over cat 3 4 or 5 utp wiring three pairs are used for transmission
193:25 three pairs are used for transmission and the fourth pair is used for
193:27 and the fourth pair is used for collision detection
193:29 collision detection no separate transmit and receive pairs
193:31 no separate transmit and receive pairs are present so full duplex operation is
193:34 are present so full duplex operation is not possible
193:35 not possible and the coating is 8b 6t
193:39 and the coating is 8b 6t next let's discuss 100 base fx fest
193:43 next let's discuss 100 base fx fest ethernet
193:45 ethernet this is a specification for fiber
193:48 this is a specification for fiber it operates over two strands of
193:49 it operates over two strands of multi-mode or single more fiber cabling
193:53 multi-mode or single more fiber cabling it can transmit over greater distances
193:55 it can transmit over greater distances than copper media
193:57 than copper media it uses a media interface connector
194:00 it uses a media interface connector st stab and twist
194:02 st stab and twist or sc stab and click fiber connectors
194:05 or sc stab and click fiber connectors defined for fddi
194:08 defined for fddi and 10 base fx networks
194:17 to make 100 megabit per second ethernet work distance limitations are much more
194:20 work distance limitations are much more severe than those required for 10
194:22 severe than those required for 10 megabits per second ethernet
194:24 megabits per second ethernet repeater networks have no five hub rule
194:27 repeater networks have no five hub rule fast ethernet is limited to two
194:29 fast ethernet is limited to two repeaters
194:31 repeaters the general rule is that a hundred
194:32 the general rule is that a hundred megabit per second ethernet has a
194:34 megabit per second ethernet has a maximum diameter of 205 meters with utp
194:38 maximum diameter of 205 meters with utp cabling
194:39 cabling whereas 10 megabit per second ethernet
194:41 whereas 10 megabit per second ethernet has a maximum diameter of 500 meters
194:44 has a maximum diameter of 500 meters with 10 base t
194:46 with 10 base t and 2500 meters with 10 base 5.
194:50 and 2500 meters with 10 base 5. most networks today use switches rather
194:52 most networks today use switches rather than repeaters which limits the length
194:54 than repeaters which limits the length of 10 base t
194:55 of 10 base t and 100 base tx
194:58 and 100 base tx to 100 meters between the switch and
195:00 to 100 meters between the switch and host
195:02 host now the distance limitation imposed
195:04 now the distance limitation imposed depends on the type of repeater
195:07 depends on the type of repeater the ieee 100 base t specification
195:10 the ieee 100 base t specification defines two types of repeaters
195:13 defines two types of repeaters class 1
195:14 class 1 and class 2.
195:16 and class 2. class 1 repeaters have a latency of 0.7
195:20 class 1 repeaters have a latency of 0.7 microseconds
195:22 microseconds or less
195:23 or less only one repeater hop is allowed
195:27 only one repeater hop is allowed class 2 repeaters have a latency of 0.46
195:30 class 2 repeaters have a latency of 0.46 microseconds or less
195:32 microseconds or less and one or two repeater hops are allowed
195:42 now let's talk about gigabit ethernet design rules
195:44 design rules gigabit ethernet
195:46 gigabit ethernet was first specified by two standards
195:48 was first specified by two standards ieee 802.3z-1998
195:53 and 802.3 a b
195:56 802.3 a b 1999.
195:57 1999. the ieee 802.3z standard specifies the
196:01 the ieee 802.3z standard specifies the operation of gigabit ethernet over fiber
196:03 operation of gigabit ethernet over fiber and coax cable
196:05 and coax cable and introduces the gigabit media
196:07 and introduces the gigabit media independent interface the gmii
196:11 independent interface the gmii these standards are superseded by the
196:13 these standards are superseded by the latest revision of all the 802.3
196:15 latest revision of all the 802.3 standards included in ieee 802.3-2002
196:24 the ieee 802.3 a b standard specified the operation of
196:26 a b standard specified the operation of gigabit ethernet over cat5utp
196:30 gigabit ethernet over cat5utp gigabit ethernet still retains the frame
196:32 gigabit ethernet still retains the frame formats and frame sizes and it still
196:34 formats and frame sizes and it still uses csma cd
196:37 uses csma cd as with ethernet and fast ethernet full
196:39 as with ethernet and fast ethernet full duplex operation is possible
196:42 duplex operation is possible differences appear in the encoding
196:45 differences appear in the encoding gigabit ethernet uses eight bravo 10
196:48 gigabit ethernet uses eight bravo 10 bravo coding with simple non-return to
196:51 bravo coding with simple non-return to zero
196:52 zero because of the twenty percent overhead
196:54 because of the twenty percent overhead pulses run at one thousand two hundred
196:56 pulses run at one thousand two hundred fifty megahertz
196:58 fifty megahertz to achieve a one thousand megabits per
197:01 to achieve a one thousand megabits per second throughput
197:03 second throughput this chart you will definitely want to
197:05 this chart you will definitely want to know in preparation
197:07 know in preparation for your ccda exam
197:10 for your ccda exam let's talk about the gigabit ethernet
197:12 let's talk about the gigabit ethernet standards in detail
197:15 standards in detail the 1000 base lx that is the long
197:17 the 1000 base lx that is the long wavelength gigabit ethernet standard
197:20 wavelength gigabit ethernet standard uses long wavelength optics over a pair
197:23 uses long wavelength optics over a pair of fiber strands
197:25 of fiber strands the specifications are as follows
197:28 the specifications are as follows it uses long wave
197:29 it uses long wave on multi-mode or single mode fiber
197:32 on multi-mode or single mode fiber the maximum lengths for multi-mode fiber
197:35 the maximum lengths for multi-mode fiber are 62.5 micrometer fiber which is 450
197:39 are 62.5 micrometer fiber which is 450 meters or 50 micrometer fiber at 550
197:43 meters or 50 micrometer fiber at 550 meters
197:44 meters maximum length for single mode fiber is
197:47 maximum length for single mode fiber is 5 kilometers
197:56 the ieee 1000 base sx standard uses short wavelength
197:57 short wavelength optics over a pair of multi-mode fiber
198:00 optics over a pair of multi-mode fiber strands
198:02 strands its maximum lengths are 260 and 550
198:06 its maximum lengths are 260 and 550 meters respectively
198:09 meters respectively the ieee 1000 base dash cx standard is
198:13 the ieee 1000 base dash cx standard is for short copper runs between servers
198:16 for short copper runs between servers it runs over a pair of 150 ohm balance
198:19 it runs over a pair of 150 ohm balance coax
198:20 coax cables maximum length is 25 meters
198:24 cables maximum length is 25 meters and this is obviously mainly used for
198:26 and this is obviously mainly used for server connections
198:29 server connections and then finally the 1000 base t gigabit
198:32 and then finally the 1000 base t gigabit ethernet over utp standard
198:36 ethernet over utp standard it was approved in june 1999
198:39 it was approved in june 1999 and now included in ieee 802.3 2002
198:43 and now included in ieee 802.3 2002 this standard uses the four pairs in the
198:46 this standard uses the four pairs in the cable
198:47 cable maximum length is 100 meters encoding
198:50 maximum length is 100 meters encoding defined is a five level coding scheme
198:55 defined is a five level coding scheme and one byte is sent over the four pairs
198:58 and one byte is sent over the four pairs at
198:59 at twelve hundred and fifty megahertz
199:02 twelve hundred and fifty megahertz the ieee 802.3 ae supplement to the
199:07 the ieee 802.3 ae supplement to the 802.3 standard was published in august
199:10 802.3 standard was published in august of 2002
199:12 of 2002 and it specifies the standard for 10
199:14 and it specifies the standard for 10 gigabit ethernet
199:16 gigabit ethernet it is defined for full duplex operation
199:18 it is defined for full duplex operation over optical media
199:20 over optical media utp and copper 10 gige has several
199:24 utp and copper 10 gige has several physical media specifications
199:27 physical media specifications based on different fiber types and
199:29 based on different fiber types and encoding
199:30 encoding multimedia fiber and single mode fiber
199:32 multimedia fiber and single mode fiber are used
199:34 are used and if you look at this diagram this is
199:36 and if you look at this diagram this is something you will definitely want to
199:38 something you will definitely want to memorize in preparation for your ccda
199:41 memorize in preparation for your ccda exam
199:48 now as noted previously in this video there are several media types that are
199:50 there are several media types that are used for campus networks
199:52 used for campus networks and this chart is one you'll want to
199:53 and this chart is one you'll want to remember because it provides a good
199:55 remember because it provides a good summary of the information you'll need
199:57 summary of the information you'll need to know for the different media types
199:59 to know for the different media types and when you may want to use them
200:05 so here's what you've learned you've learned about campus lan media types and
200:09 learned about campus lan media types and this is something you will definitely be
200:10 this is something you will definitely be tested on in your ccda exam
200:14 tested on in your ccda exam you've learned about the different
200:15 you've learned about the different ethernet standards as well as the
200:18 ethernet standards as well as the different campus transmission media
200:20 different campus transmission media types
200:21 types and i'm confident if you master the
200:23 and i'm confident if you master the material in this video you'll do very
200:25 material in this video you'll do very well in this portion of your ccda exam
200:28 well in this portion of your ccda exam good luck in your studies
200:55 hi this is david voss cciu11372 and in this video you're going to learn
200:57 and in this video you're going to learn about
200:58 about analyzing traffic in preparation for
201:00 analyzing traffic in preparation for your ccda exam
201:01 your ccda exam first let's start with analyzing
201:03 first let's start with analyzing application traffic
201:05 application traffic one of the first enterprise campus
201:07 one of the first enterprise campus design issues refers to
201:09 design issues refers to analyzing the application traffic as it
201:12 analyzing the application traffic as it relates to the switched network design
201:15 relates to the switched network design the traffic patterns usually fall into
201:16 the traffic patterns usually fall into one of the following scenarios
201:19 one of the following scenarios local with a segment module and
201:23 local with a segment module and or distant
201:25 or distant remote traffic patterns this implies
201:28 remote traffic patterns this implies traversing different segments
201:30 traversing different segments or crossing sub-modules or modules in
201:33 or crossing sub-modules or modules in the campus design
201:35 the campus design networks were originally designed
201:37 networks were originally designed according to the 80 20 rule which states
201:39 according to the 80 20 rule which states that 80 percent of the traffic is
201:41 that 80 percent of the traffic is internal
201:42 internal 20 is remote
201:45 20 is remote this concept has changed with the
201:46 this concept has changed with the evolution of enterprise networking and
201:49 evolution of enterprise networking and distributed server networking
201:51 distributed server networking in modern campus networks so the ratio
201:54 in modern campus networks so the ratio now is twenty eighty
201:56 now is twenty eighty whereas twenty percent is for local
201:58 whereas twenty percent is for local traffic and eighty percent is for
202:00 traffic and eighty percent is for traffic
202:01 traffic that crosses between modules and
202:03 that crosses between modules and segments
202:04 segments this change occurred as a result of
202:07 this change occurred as a result of servers no longer sitting in the
202:08 servers no longer sitting in the workgroup areas
202:14 generally the application and backbone servers are placed in a server farm area
202:16 servers are placed in a server farm area this puts a much higher load on the
202:19 this puts a much higher load on the backbone because much of the traffic
202:21 backbone because much of the traffic from the client side is going to the
202:23 from the client side is going to the servers in the server farm through the
202:25 servers in the server farm through the core layer devices
202:28 core layer devices this changes the way you will analyze
202:30 this changes the way you will analyze application traffic
202:32 application traffic in order to exemplify the 80 20 rule
202:34 in order to exemplify the 80 20 rule consider a work group area with various
202:36 consider a work group area with various devices
202:38 devices connected to a basic layer 2 switch
202:40 connected to a basic layer 2 switch using vlans
202:42 using vlans the inner vlan routing is accomplished
202:44 the inner vlan routing is accomplished on the routers that also allow access to
202:46 on the routers that also allow access to an email server according to the eighty
202:48 an email server according to the eighty twenty rule eighty percent of traffic
202:50 twenty rule eighty percent of traffic stays within the vlan
202:52 stays within the vlan where twenty whereas twenty percent of
202:54 where twenty whereas twenty percent of the traffic is going to the email server
203:01 on the other hand for example in the modern 2080 rule consider a situation in
203:05 modern 2080 rule consider a situation in which there are multiple logical
203:07 which there are multiple logical departments
203:09 departments using common resources with applications
203:11 using common resources with applications distributed throughout the organization
203:14 distributed throughout the organization this means there are no dedicated
203:16 this means there are no dedicated servers located within the department
203:19 servers located within the department for example database or file servers
203:21 for example database or file servers all the data is stored in the server
203:23 all the data is stored in the server farm block
203:24 farm block the end user's devices connect to a
203:26 the end user's devices connect to a series of layer 2 or low end layer 3
203:29 series of layer 2 or low end layer 3 switches
203:30 switches before reaching the distribution layer
203:32 before reaching the distribution layer block
203:33 block where the high end layer 3 switches with
203:35 where the high end layer 3 switches with high availability
203:37 high availability are located
203:39 are located the data flow finally reaches the server
203:41 the data flow finally reaches the server farm block consisting of modern database
203:44 farm block consisting of modern database servers such as email
203:46 servers such as email applications databases
203:49 applications databases in this example the traffic distribution
203:51 in this example the traffic distribution reflects the 2080 rule meaning 20
203:54 reflects the 2080 rule meaning 20 percent of the network traffic stays
203:55 percent of the network traffic stays local while 80 of the traffic is moving
203:58 local while 80 of the traffic is moving across the distribution layer
204:00 across the distribution layer and backbone of the network
204:04 and backbone of the network this is the reason you want your
204:05 this is the reason you want your distribution and core layer links
204:08 distribution and core layer links to be highly available and fast in order
204:12 to be highly available and fast in order to move data across the enterprise
204:15 to move data across the enterprise quickly
204:17 quickly the diagrams presented here represent a
204:19 the diagrams presented here represent a single building
204:20 single building but in large campus enterprise you would
204:22 but in large campus enterprise you would have multiple buildings connected by the
204:24 have multiple buildings connected by the network backbone module
204:26 network backbone module the network backbone is connected to the
204:28 the network backbone is connected to the edge distribution sub-module in order to
204:31 edge distribution sub-module in order to provide external access from the network
204:38 next let's discuss analyzing multicast traffic
204:40 traffic with the incredible advances of
204:41 with the incredible advances of collaboration tools using the world wide
204:44 collaboration tools using the world wide web and the internet it is very likely
204:46 web and the internet it is very likely that the organization will have to
204:48 that the organization will have to support multicast traffic
204:50 support multicast traffic the process of multicasting opposed to
204:53 the process of multicasting opposed to the process of broadcasting
204:55 the process of broadcasting or unicasting
204:57 or unicasting has the advantage of saving bandwidth
204:58 has the advantage of saving bandwidth because it sends a single stream of data
205:02 because it sends a single stream of data to multiple nodes
205:04 to multiple nodes the multicasting concept is used by
205:07 the multicasting concept is used by every modern corporation around the
205:10 every modern corporation around the world to deliver data to groups via the
205:12 world to deliver data to groups via the following methods
205:14 following methods corporate meetings video conferencing
205:17 corporate meetings video conferencing e-learning solutions webcasting
205:19 e-learning solutions webcasting information
205:20 information distributing applications streaming news
205:23 distributing applications streaming news feeds and streaming stock quotes
205:26 feeds and streaming stock quotes multicast data is sent as a multicast
205:29 multicast data is sent as a multicast group and users receive the information
205:31 group and users receive the information by joining that group using igmp or
205:35 by joining that group using igmp or internet group management protocol
205:37 internet group management protocol cisco multicast enabled routers can be
205:40 cisco multicast enabled routers can be used
205:41 used running multicast routing protocols such
205:44 running multicast routing protocols such as pim
205:45 as pim protocol independent multicast
205:48 protocol independent multicast so that
205:49 so that they can forward the incoming multicast
205:52 they can forward the incoming multicast stream to a particular switch port
205:55 stream to a particular switch port cisco switches effectively implement
205:58 cisco switches effectively implement multicasting using two main protocols
206:01 multicasting using two main protocols cgmp which is cisco group management
206:04 cgmp which is cisco group management protocol and igmp snooping
206:08 protocol and igmp snooping cgmp allows switches to communicate with
206:10 cgmp allows switches to communicate with multicast enabled routers
206:12 multicast enabled routers to figure out whether any users attached
206:15 to figure out whether any users attached to the switches are part of any
206:16 to the switches are part of any particular multicasting groups and
206:19 particular multicasting groups and whether they are qualified to receive
206:21 whether they are qualified to receive the special stream of data
206:24 the special stream of data igmp snipping allows the switch to
206:27 igmp snipping allows the switch to intercept the monthly cash receiver
206:29 intercept the monthly cash receiver registration message and based on the
206:32 registration message and based on the gathered information it makes changes to
206:35 gathered information it makes changes to its forwarding table
206:37 its forwarding table igmp snooping works only on layer 3
206:40 igmp snooping works only on layer 3 switches because igmp is a layer 3
206:43 switches because igmp is a layer 3 protocol
206:46 protocol next let's discuss analyzing delay
206:48 next let's discuss analyzing delay sensitive traffic
206:50 sensitive traffic if using multicasting or web streaming
206:52 if using multicasting or web streaming e-commerce e-learning solutions or ip
206:54 e-commerce e-learning solutions or ip telephony the traffic involved in this
206:56 telephony the traffic involved in this process will be delay sensitive and qos
206:59 process will be delay sensitive and qos techniques might be necessary to ensure
207:01 techniques might be necessary to ensure that this type of traffic is treated
207:04 that this type of traffic is treated with priority
207:05 with priority in layer 3 applications such as frame
207:08 in layer 3 applications such as frame relay environments
207:09 relay environments using eigrp ospf or bgp
207:12 using eigrp ospf or bgp as routing protocols with the isp
207:15 as routing protocols with the isp it is very common to use qos techniques
207:18 it is very common to use qos techniques to shape and control traffic at the
207:20 to shape and control traffic at the iplayer
207:21 iplayer you can also use qos at layer 2.
207:25 you can also use qos at layer 2. when using qos or analyzing or
207:28 when using qos or analyzing or controlling delay sensitive traffic at
207:30 controlling delay sensitive traffic at layer two there are four categories of
207:33 layer two there are four categories of qos techniques as follows
207:35 qos techniques as follows tagging and traffic classification
207:38 tagging and traffic classification congestion control
207:40 congestion control policy and shaping and scheduling
207:49 as you can see in this diagram you'll see that tagging and traffic
207:50 see that tagging and traffic classification have between having
207:53 classification have between having between the end user nodes
207:55 between the end user nodes through the excess layer up to the
207:57 through the excess layer up to the distribution layer this is where packets
207:59 distribution layer this is where packets are classified grouped and partitioned
208:01 are classified grouped and partitioned based on different priority levels or
208:04 based on different priority levels or classes of service
208:10 this incurs this occurs by inspecting the layer two
208:12 this occurs by inspecting the layer two packet headers and determining the
208:14 packet headers and determining the priority of the traffic based on the
208:16 priority of the traffic based on the traffic type
208:18 traffic type in this way the traffic can be tagged
208:20 in this way the traffic can be tagged and classified
208:22 and classified the next three techniques congestion
208:24 the next three techniques congestion control policy and traffic shaping and
208:26 control policy and traffic shaping and scheduling occur in the distribution
208:29 scheduling occur in the distribution layer block and the edge distribution
208:31 layer block and the edge distribution layer
208:32 layer sub module
208:34 sub module primarily on layer 3 switches
208:36 primarily on layer 3 switches you want to avoid applying any qos
208:39 you want to avoid applying any qos technique at the core layer
208:41 technique at the core layer because you want as little overhead as
208:43 because you want as little overhead as possible on the backbone
208:45 possible on the backbone so that they can successfully achieve
208:48 so that they can successfully achieve their goals
208:49 their goals which is fast connectivity high
208:52 which is fast connectivity high availability and reliability
208:56 availability and reliability congestion control involves the
208:58 congestion control involves the interfaces of the access layer switches
209:00 interfaces of the access layer switches and the cueing mechanisms configured on
209:03 and the cueing mechanisms configured on them
209:04 them cueing techniques are used in order to
209:05 cueing techniques are used in order to deal with the congestion of packets
209:07 deal with the congestion of packets coming into and out of the switch ports
209:10 coming into and out of the switch ports this method ensures the traffic from
209:12 this method ensures the traffic from critical applications
209:14 critical applications will be forwarded properly
209:16 will be forwarded properly especially when using real-time
209:19 especially when using real-time so let's summarize what you've learned
209:21 so let's summarize what you've learned in this video you've learned about the
209:23 in this video you've learned about the different types of traffic that can
209:25 different types of traffic that can traverse a switch to network
209:28 traverse a switch to network and how to handle that traffic and some
209:30 and how to handle that traffic and some of this information's been at a higher
209:32 of this information's been at a higher level
209:33 level such as qos
209:35 such as qos but that being said this is what cisco
209:37 but that being said this is what cisco expects you to know for the ccda exam
209:39 expects you to know for the ccda exam with the understanding that things will
209:41 with the understanding that things will get quite a bit more granular in the
209:43 get quite a bit more granular in the follow-up videos
209:44 follow-up videos but also as you work your way up to ccdp
209:48 but also as you work your way up to ccdp this is a good foundation for you to
209:50 this is a good foundation for you to begin and i wish you the best of luck in
209:51 begin and i wish you the best of luck in your studies thank you
210:17 hi this is david voss ccie11372 and in this video you're going
210:19 ccie11372 and in this video you're going to learn about enterprise campus design
210:22 to learn about enterprise campus design specifically we're going to go through
210:24 specifically we're going to go through the questions that you need to ask or
210:27 the questions that you need to ask or cisco at least expects you to ask when
210:30 cisco at least expects you to ask when you are designing
210:32 you are designing the access
210:33 the access distribution
210:35 distribution and core layer
210:37 and core layer so we're going to work our way up we'll
210:38 so we're going to work our way up we'll begin with the access layer
210:44 whenever a network designer is in the process of designing the campus
210:46 process of designing the campus infrastructures access layer block
210:49 infrastructures access layer block the following important questions must
210:51 the following important questions must be answered and you may be tested on
210:53 be answered and you may be tested on this in your ccda exam
210:56 this in your ccda exam what are the current and future needs
210:59 what are the current and future needs for end users or node ports in the
211:01 for end users or node ports in the existing wiring closets of that
211:03 existing wiring closets of that particular building
211:05 particular building what kind of hardware can the company or
211:07 what kind of hardware can the company or the client afford
211:09 the client afford can afford modular devices
211:12 can afford modular devices this will determine the degree of
211:14 this will determine the degree of scalability in the access layer an
211:16 scalability in the access layer an important factor that will allow the
211:18 important factor that will allow the business to grow
211:20 business to grow is the existing cabling adequate do you
211:22 is the existing cabling adequate do you have cat
211:24 have cat 5 or cat 6 utp cabling
211:28 5 or cat 6 utp cabling can you afford fiber cabling
211:31 can you afford fiber cabling if you are moving into a new building
211:33 if you are moving into a new building you might consider installing fiber
211:35 you might consider installing fiber optic cabling
211:37 optic cabling even at the access layer
211:40 even at the access layer what are the performance and bandwidth
211:41 what are the performance and bandwidth requirements
211:44 requirements what level of high availability is
211:46 what level of high availability is needed at the access layer
211:48 needed at the access layer generally in the access layer block you
211:50 generally in the access layer block you will not need as much redundancy
211:52 will not need as much redundancy a certain degree of high availability
211:55 a certain degree of high availability might be needed if using modular network
211:57 might be needed if using modular network devices
211:59 devices what are the requirements to support
212:01 what are the requirements to support vlan vtp and stp
212:04 vlan vtp and stp in a large enterprise campus design you
212:07 in a large enterprise campus design you might not need to use multiple vlans
212:10 might not need to use multiple vlans so you can go straight to using layer 3
212:12 so you can go straight to using layer 3 technologies in the access layer to
212:15 technologies in the access layer to avoid having multiple broadcast domains
212:17 avoid having multiple broadcast domains and to decrease the complexity of stp
212:22 and to decrease the complexity of stp what are the layer two traffic patterns
212:24 what are the layer two traffic patterns for applications
212:26 for applications and what multi-casting needs and quality
212:28 and what multi-casting needs and quality of service services are necessary
212:32 of service services are necessary at layer two
212:35 at layer two next we move up to the distribution
212:37 next we move up to the distribution layer
212:38 layer the distribution layer block combines
212:40 the distribution layer block combines and aggregates the access layer block
212:42 and aggregates the access layer block components
212:43 components and it uses layer 2 and layer 3
212:45 and it uses layer 2 and layer 3 switching to break up the work groups or
212:47 switching to break up the work groups or vlans
212:48 vlans and isolate the different network
212:50 and isolate the different network segments as failure domains
212:53 segments as failure domains and it also allows for the reduction of
212:54 and it also allows for the reduction of broadcast storms
212:56 broadcast storms it acts as a transit module between the
213:00 it acts as a transit module between the access and core layers
213:02 access and core layers here are some important questions that
213:04 here are some important questions that must be answered before designing the
213:06 must be answered before designing the distribution layer block
213:09 distribution layer block should layer 2 or layer 3 switches be
213:11 should layer 2 or layer 3 switches be used
213:12 used cost is a big issue in this decision
213:15 cost is a big issue in this decision the available budget will dictate the
213:16 the available budget will dictate the hardware that's going to be used
213:19 hardware that's going to be used how many total users will you have to
213:21 how many total users will you have to support
213:22 support with a high number of users such as
213:24 with a high number of users such as greater than 500 layer 3 switching
213:26 greater than 500 layer 3 switching will be essential in the distribution
213:29 will be essential in the distribution layer
213:30 layer one of the high availability needs
213:33 one of the high availability needs are the distribution layer switches
213:34 are the distribution layer switches modular and scalable
213:37 modular and scalable what type of intelligence services will
213:39 what type of intelligence services will be used in the distribution layer
213:41 be used in the distribution layer you must consider different features
213:43 you must consider different features that will be implemented in the
213:45 that will be implemented in the distribution layer
213:46 distribution layer such as security
213:48 such as security quality of service or multicasting
213:51 quality of service or multicasting if any of these features are implemented
213:53 if any of these features are implemented layer 3 switching is mandatory
213:57 layer 3 switching is mandatory is the company prepared to manage and
213:59 is the company prepared to manage and configure the distribution layer block
214:02 configure the distribution layer block should training or consultancy be added
214:04 should training or consultancy be added to the project budget to ensure that
214:07 to the project budget to ensure that this particular block will be properly
214:09 this particular block will be properly managed
214:11 managed will advanced stp features be
214:13 will advanced stp features be implemented
214:14 implemented you should think about features such as
214:16 you should think about features such as rstp backbone fast or uplink fast when
214:20 rstp backbone fast or uplink fast when connecting to the backbone layer
214:23 connecting to the backbone layer when connecting to the backbone block
214:25 when connecting to the backbone block via layer 2.
214:27 via layer 2. these kinds of features can be found on
214:29 these kinds of features can be found on almost all high-end modern switches
214:32 almost all high-end modern switches and can help optimize and speed up the
214:34 and can help optimize and speed up the stp process
214:36 stp process if a complete layer 3 switching model is
214:39 if a complete layer 3 switching model is used you do not have to think about stp
214:42 used you do not have to think about stp or additional features
214:47 finally the campus backbone block or core layer
214:50 the campus backbone block or core layer the campus backbone design occurs very
214:53 the campus backbone design occurs very early in the overall infrastructure
214:55 early in the overall infrastructure design process
214:57 design process as such what follows are a few important
214:59 as such what follows are a few important questions you should ask yourself and
215:01 questions you should ask yourself and your customers when it is time to design
215:04 your customers when it is time to design the
215:05 the campus backbone block
215:07 campus backbone block do you have three or more separate
215:09 do you have three or more separate locations that is buildings in the
215:11 locations that is buildings in the campus
215:12 campus that are connected through an enterprise
215:13 that are connected through an enterprise campus infrastructure
215:15 campus infrastructure if you only have two buildings you might
215:17 if you only have two buildings you might not need a separate backbone block
215:20 not need a separate backbone block a possible solution in this scenario
215:22 a possible solution in this scenario would be to use high high-speed fiber
215:23 would be to use high high-speed fiber connections
215:24 connections between the two buildings distribution
215:27 between the two buildings distribution layers
215:28 layers based on the present infrastructure will
215:31 based on the present infrastructure will the solution to the campus backbone be a
215:33 the solution to the campus backbone be a layer 2
215:34 layer 2 layer 2 and 3 or just the layer 3
215:37 layer 2 and 3 or just the layer 3 switching solution
215:39 switching solution in the case of a large enterprise campus
215:42 in the case of a large enterprise campus do you have the budget for a full
215:43 do you have the budget for a full multi-layer backbone solution throughout
215:47 multi-layer backbone solution throughout is the organization ready for a high
215:49 is the organization ready for a high performance multi-layer switching
215:51 performance multi-layer switching environment
215:52 environment things to consider here are training
215:54 things to consider here are training personnel
215:56 personnel budget
215:57 budget applications
215:58 applications support services and intelligence
216:00 support services and intelligence services
216:02 services does the customer want to simplify and
216:04 does the customer want to simplify and lower the number of links between the
216:06 lower the number of links between the distribution layer switches
216:08 distribution layer switches and the server farm block edge
216:10 and the server farm block edge distribution submodule
216:12 distribution submodule if so you could make changes to or
216:15 if so you could make changes to or augment the present network
216:16 augment the present network infrastructure
216:18 infrastructure and redesign the campus backbone
216:21 and redesign the campus backbone what are the performance needs the
216:23 what are the performance needs the bandwidth needs for all the applications
216:25 bandwidth needs for all the applications and services should be analyzed
216:28 and services should be analyzed how many high capacity links or ports
216:30 how many high capacity links or ports are necessary for the campus backbone
216:33 are necessary for the campus backbone block
216:34 block and what are the high availability
216:36 and what are the high availability redundancy redundancy demands
216:38 redundancy redundancy demands multiple aspects should be taken into
216:41 multiple aspects should be taken into consideration
216:42 consideration such as redundant connections modules
216:45 such as redundant connections modules and hardware
216:46 and hardware platforms obviously in this video
216:49 platforms obviously in this video there's been a lot of questions asked
216:50 there's been a lot of questions asked but all of them are very important
216:52 but all of them are very important questions to ask we do not design in
216:55 questions to ask we do not design in ivory towers we must communicate with
216:57 ivory towers we must communicate with the customer and understand the needs
217:00 the customer and understand the needs all the questions you've learned today
217:01 all the questions you've learned today are not only questions you need to know
217:03 are not only questions you need to know to perform your job well they could be
217:05 to perform your job well they could be questions that you would be expected to
217:07 questions that you would be expected to select if cisco were to ask you on the
217:09 select if cisco were to ask you on the ccda exam how would you prepare to
217:12 ccda exam how would you prepare to design the enterprise campus network
217:15 design the enterprise campus network good luck in your studies
217:42 hi this is david voss cci11372 and in this video we are going to cover
217:44 and in this video we are going to cover data setter design considerations
217:48 data setter design considerations we are going to walk you through each of
217:49 we are going to walk you through each of the components of the data center
217:52 the components of the data center so that we can talk about
217:54 so that we can talk about the individual questions and the
217:56 the individual questions and the individual considerations that need to
217:58 individual considerations that need to be taken into account when planning out
218:00 be taken into account when planning out a data center all this is fair game for
218:03 a data center all this is fair game for the ccda exam so let's go ahead and dig
218:06 the ccda exam so let's go ahead and dig in
218:07 in the data center concept has greatly
218:09 the data center concept has greatly evolved over the last few years passing
218:12 evolved over the last few years passing through many phases because of evolving
218:14 through many phases because of evolving technology
218:16 technology at the time of their appearance data
218:17 at the time of their appearance data centers were centralized
218:19 centers were centralized and they used mainframes to manage the
218:21 and they used mainframes to manage the data
218:22 data mainframes were then managed using
218:24 mainframes were then managed using terminals which are still used in modern
218:27 terminals which are still used in modern data centers because of their resiliency
218:29 data centers because of their resiliency although they are definitely considered
218:31 although they are definitely considered legacy components of data centers now
218:34 legacy components of data centers now the third generation data centers are
218:36 the third generation data centers are focused on modern technologies such as
218:38 focused on modern technologies such as virtualization
218:40 virtualization which further reduce costs
218:42 which further reduce costs these factors make this approach more
218:44 these factors make this approach more efficient than the distributed data
218:46 efficient than the distributed data center model
218:48 center model virtualization results in higher
218:50 virtualization results in higher utilization of computing and network
218:52 utilization of computing and network resources by sharing and allocating them
218:55 resources by sharing and allocating them on a temporary basis
218:58 on a temporary basis the top layer of the data center
218:59 the top layer of the data center topology includes virtual machines that
219:02 topology includes virtual machines that are hardware abstracted into software
219:04 are hardware abstracted into software entities
219:05 entities running a guest operating system on top
219:08 running a guest operating system on top of a hypervisor
219:10 of a hypervisor below this layer are the unified
219:12 below this layer are the unified computing resources
219:14 computing resources which contain the service profiles that
219:16 which contain the service profiles that map to the identity of the server
219:19 map to the identity of the server the identity of the server contains
219:21 the identity of the server contains details such as the following
219:23 details such as the following memory
219:24 memory cpu
219:25 cpu network interfaces storage information
219:28 network interfaces storage information and boot image
219:31 and boot image the next layer which is consolidated
219:34 the next layer which is consolidated connectivity
219:35 connectivity contains technology such as 10 gigabit
219:37 contains technology such as 10 gigabit ethernet
219:38 ethernet fiber channel over ethernet and fiber
219:41 fiber channel over ethernet and fiber channel
219:42 channel and all of these are supported on the
219:44 and all of these are supported on the cisco nexus series
219:47 cisco nexus series next let's talk about server
219:49 next let's talk about server considerations
219:50 considerations some very important aspects to consider
219:52 some very important aspects to consider when deploying servers in a data center
219:54 when deploying servers in a data center include the following
219:56 include the following the required power
219:57 the required power the rack space needed
219:59 the rack space needed server security
220:01 server security virtualization support and server
220:03 virtualization support and server management
220:04 management the increasing number of servers used
220:07 the increasing number of servers used necessitates more power and this has led
220:10 necessitates more power and this has led to the need for energy efficiency in the
220:12 to the need for energy efficiency in the data center
220:14 data center rack servers usually consume a great
220:16 rack servers usually consume a great deal of energy even though they are low
220:18 deal of energy even though they are low cost and provide high performance
220:21 cost and provide high performance an alternative to standalone servers are
220:23 an alternative to standalone servers are blade servers
220:24 blade servers they provide similar computing power but
220:26 they provide similar computing power but require less space power and cabling
220:33 server virtualization is supported on both standalone and blade servers and
220:35 both standalone and blade servers and provides scalability and better
220:37 provides scalability and better utilization of hardware resources
220:40 utilization of hardware resources next let's talk about data center
220:42 next let's talk about data center facility spacing considerations
220:45 facility spacing considerations facility spacing and other
220:46 facility spacing and other considerations help to size the overall
220:48 considerations help to size the overall data center and decide where to position
220:51 data center and decide where to position the equipment in order in order to
220:52 the equipment in order in order to provide scalability
220:54 provide scalability the available space defines the number
220:56 the available space defines the number of racks that can be installed for
220:58 of racks that can be installed for servers and network equipment
221:01 servers and network equipment an important factor to consider is the
221:03 an important factor to consider is the floor loading parameters
221:05 floor loading parameters estimating the correct size of the data
221:07 estimating the correct size of the data center has great influence on costs
221:10 center has great influence on costs longevity
221:12 longevity and flexibility
221:14 and flexibility several factors must be considered
221:16 several factors must be considered including the following
221:18 including the following the number of servers
221:19 the number of servers the amount of storage equipment the
221:22 the amount of storage equipment the amount of network equipment
221:24 amount of network equipment the number of employees served by the
221:25 the number of employees served by the data center infrastructure
221:28 data center infrastructure space needed for non-infrastructure
221:30 space needed for non-infrastructure areas such as storage rooms office space
221:33 areas such as storage rooms office space and other areas the weight of the
221:35 and other areas the weight of the equipment
221:36 equipment loading
221:38 loading heat dissipation
221:40 heat dissipation and power consumption and power type
221:44 and power consumption and power type physical security is another important
221:46 physical security is another important consideration because data centers
221:48 consideration because data centers contain equipment that hosts sensitive
221:50 contain equipment that hosts sensitive company data
221:52 company data which must be secured from outsiders
221:54 which must be secured from outsiders access to the data center must be well
221:56 access to the data center must be well controlled
221:58 controlled next let's talk about data center power
221:59 next let's talk about data center power considerations
222:01 considerations the power in the data center facility is
222:03 the power in the data center facility is used to power server storage network
222:05 used to power server storage network equipment cooling devices sensors and
222:08 equipment cooling devices sensors and other additional systems
222:10 other additional systems estimating necessary power capacity
222:14 estimating necessary power capacity involves collecting the requirements for
222:15 involves collecting the requirements for all the current and future equipment
222:18 all the current and future equipment such as the following servers storage
222:21 such as the following servers storage network devices ups generators hvac
222:26 network devices ups generators hvac and lighting
222:28 and lighting next let's discuss data center cooling
222:31 next let's discuss data center cooling considerations
222:33 considerations based on the type of equipment used
222:35 based on the type of equipment used careful heating and cooling calculations
222:37 careful heating and cooling calculations must be provided
222:39 must be provided blade server deployments allow for more
222:41 blade server deployments allow for more efficient use of space
222:43 efficient use of space but increased the amount of heat per
222:45 but increased the amount of heat per server
222:46 server some cooling solutions to address
222:48 some cooling solutions to address increased heat production include the
222:50 increased heat production include the following
222:51 following increase the space between the racks
222:54 increase the space between the racks increase the number of hvac units
222:56 increase the number of hvac units increase the airflow between devices
223:04 next let's talk about data center cabling considerations
223:06 cabling considerations a passive infrastructure for the data
223:08 a passive infrastructure for the data center is essential for optimal system
223:10 center is essential for optimal system performance
223:12 performance the physical network cabling between
223:13 the physical network cabling between devices determines how these devices
223:15 devices determines how these devices communicate with one another and with
223:18 communicate with one another and with external systems the cabling
223:20 external systems the cabling infrastructure type chosen impacts the
223:22 infrastructure type chosen impacts the physical connectors
223:24 physical connectors and the media type of the connectors
223:27 and the media type of the connectors this must be compatible with the
223:28 this must be compatible with the equipment interfaces
223:30 equipment interfaces two options are widely used today copper
223:33 two options are widely used today copper and fiber optic cabling
223:36 and fiber optic cabling the advantages of fiber optics are that
223:38 the advantages of fiber optics are that they are less susceptible to external
223:40 they are less susceptible to external interfaces and they operate over greater
223:43 interfaces and they operate over greater distances than copper cables do
223:46 distances than copper cables do cabling must remain well organized in
223:48 cabling must remain well organized in order to maintain the passive
223:49 order to maintain the passive infrastructure easily
223:51 infrastructure easily cabling infrastructure usability and
223:53 cabling infrastructure usability and simplicity is influenced by the
223:55 simplicity is influenced by the following
223:56 following the number of connections
223:58 the number of connections media selection and type of cabling
224:00 media selection and type of cabling termination organizers
224:09 as with any enterprise network the enterprise data center architecture
224:11 enterprise data center architecture follows the multi-layer approach and can
224:14 follows the multi-layer approach and can be structured in the core
224:16 be structured in the core aggregation and access layers
224:20 aggregation and access layers i won't repeat all the information for
224:22 i won't repeat all the information for the data center core as you will find
224:24 the data center core as you will find much of that information in the other
224:26 much of that information in the other videos
224:27 videos and the same is true for the
224:28 and the same is true for the distribution layer or what the in the
224:30 distribution layer or what the in the data center what is considered the
224:32 data center what is considered the aggregation layer
224:33 aggregation layer where we want to focus in this video is
224:36 where we want to focus in this video is the data center access layer
224:38 the data center access layer the main purpose of the data center's
224:39 the main purpose of the data center's access layer is to provide layer 2 and
224:42 access layer is to provide layer 2 and layer 3 physical port access
224:44 layer 3 physical port access to different kinds of servers remember
224:47 to different kinds of servers remember we're talking about a data center here
224:49 we're talking about a data center here so we're not talking about pcs or phones
224:52 so we're not talking about pcs or phones per se but the actual servers that
224:54 per se but the actual servers that support them
224:56 support them this layer consists of high performance
224:58 this layer consists of high performance and low latency switches
225:00 and low latency switches most data centers are built using layer
225:02 most data centers are built using layer 2 connectivity although
225:04 2 connectivity although layer 3 is also available from a design
225:07 layer 3 is also available from a design standpoint
225:08 standpoint positive possible physical loops that
225:10 positive possible physical loops that might be presented at layer two are
225:12 might be presented at layer two are managed by a spanning tree
225:14 managed by a spanning tree so here's what you've learned you've
225:16 so here's what you've learned you've learned about the important subtopics
225:19 learned about the important subtopics within data center design
225:21 within data center design it's not just about passing packets
225:23 it's not just about passing packets anymore it's literally about providing
225:25 anymore it's literally about providing the proper environment in space and
225:28 the proper environment in space and power
225:29 power to support all of your network
225:31 to support all of your network infrastructure
225:33 infrastructure so in this video you've learned some key
225:35 so in this video you've learned some key categories or key topics within data
225:38 categories or key topics within data center planning that you definitely will
225:40 center planning that you definitely will be asked about in your ccda exam and you
225:43 be asked about in your ccda exam and you definitely will use should you plan out
225:44 definitely will use should you plan out a data center for yourself
225:47 a data center for yourself good luck in your studies
226:12 hi this is david voss cciu11372 and in this video you're going to learn
226:13 and in this video you're going to learn about data center components
226:16 about data center components specifically you're going to learn about
226:18 specifically you're going to learn about all the components you see here
226:20 all the components you see here that you can find in a data center much
226:22 that you can find in a data center much of this may look new to you especially
226:24 of this may look new to you especially if you do not work in the data center
226:26 if you do not work in the data center but you're expected to know all of it
226:28 but you're expected to know all of it for your ccda exam especially the new
226:31 for your ccda exam especially the new version of it which seems to have more
226:33 version of it which seems to have more of a focus on data center technologies
226:36 of a focus on data center technologies so we're going to go ahead and cover
226:37 so we're going to go ahead and cover fibre channel over ethernet data center
226:39 fibre channel over ethernet data center bridging
226:40 bridging unified ports
226:42 unified ports intercloud fabric
226:44 intercloud fabric fabric path
226:45 fabric path overlay transport virtualization
226:48 overlay transport virtualization fabric management and extended sand
226:52 fabric management and extended sand so let's go ahead and begin
227:00 first let's begin with fiber channel over ethernet
227:01 over ethernet a classic data center design features a
227:04 a classic data center design features a dedicated ethernet lan and a separate
227:06 dedicated ethernet lan and a separate dedicated fiber channel san
227:09 dedicated fiber channel san with fibre channel over ethernet it is
227:11 with fibre channel over ethernet it is possible to run a single converged
227:14 possible to run a single converged network
227:15 network as a standards-based protocol that
227:17 as a standards-based protocol that allows fiber channel frames to be
227:19 allows fiber channel frames to be carried over ethernet links
227:21 carried over ethernet links fiber channel over ethernet
227:23 fiber channel over ethernet obviates the need to run separate lan
227:26 obviates the need to run separate lan and san networks
227:29 and san networks fiber channel over ethernet allows an
227:31 fiber channel over ethernet allows an evolutionary approach to i o
227:34 evolutionary approach to i o consolidation
227:35 consolidation by preserving all fiber channel
227:37 by preserving all fiber channel constructs maintaining the latency
227:40 constructs maintaining the latency security and traffic management
227:41 security and traffic management attributes of fiber channel
227:44 attributes of fiber channel while preserving investments in
227:45 while preserving investments in fibrochannel tools training in sands
227:50 fibrochannel tools training in sands based on lossless reliable ethernet
227:53 based on lossless reliable ethernet fibre channel over ethernet networks
227:54 fibre channel over ethernet networks combine lan and multiple storage
227:56 combine lan and multiple storage protocols on a converged network
228:01 protocols on a converged network next let's talk about data center
228:03 next let's talk about data center bridging
228:04 bridging ieee 802.1 data center bridging is a
228:07 ieee 802.1 data center bridging is a collection of standards-based extensions
228:09 collection of standards-based extensions to classical ethernet
228:11 to classical ethernet it provides a lossless data center
228:13 it provides a lossless data center transport layer that helps enable the
228:15 transport layer that helps enable the convergence of lands and sands onto a
228:18 convergence of lands and sands onto a single unified fabric
228:21 single unified fabric in addition to supporting fibril channel
228:23 in addition to supporting fibril channel over ethernet
228:24 over ethernet data center bridging can enhance the
228:26 data center bridging can enhance the operation of iscsi network attached
228:28 operation of iscsi network attached storage
228:30 storage and other business critical storage
228:32 and other business critical storage traffic
228:39 next let's discuss unified ports as a part of the network foundation of
228:41 as a part of the network foundation of unified fabric the cisco nexus switches
228:45 unified fabric the cisco nexus switches specifically the nexus 5548 up switch
228:50 specifically the nexus 5548 up switch delivers innovative architectural
228:52 delivers innovative architectural flexibility infrastructure simplicity
228:55 flexibility infrastructure simplicity and business agility
228:57 and business agility with support for networking standards
228:59 with support for networking standards for traditional virtualized unified and
229:02 for traditional virtualized unified and high performance computing environments
229:05 high performance computing environments it offers a long list of it and business
229:08 it offers a long list of it and business advantages
229:10 advantages this includes architectural flexibility
229:13 this includes architectural flexibility such as unified ports which support
229:15 such as unified ports which support traditional ethernet fiber channel and
229:18 traditional ethernet fiber channel and fiber channel over ethernet has a common
229:20 fiber channel over ethernet has a common high density high performance data
229:22 high density high performance data center class fixed form factor platform
229:26 center class fixed form factor platform and can consolidate lan and storage
229:29 and can consolidate lan and storage business agility it meets the diverse
229:32 business agility it meets the diverse data center deployments on one platform
229:35 data center deployments on one platform next let's talk about intercloud fabric
229:38 next let's talk about intercloud fabric you can build a highly secure hybrid
229:40 you can build a highly secure hybrid clouds and extend your existing data
229:42 clouds and extend your existing data center to public clouds as needed on
229:44 center to public clouds as needed on demand with consistent network and
229:47 demand with consistent network and security policies
229:49 security policies with cisco intercloud fabric you can do
229:51 with cisco intercloud fabric you can do all this
229:52 all this cloud providers can now provide a
229:54 cloud providers can now provide a complete hybrid cloud solution
229:58 complete hybrid cloud solution cloud providers can differentiate their
230:00 cloud providers can differentiate their offerings as a premium service
230:02 offerings as a premium service and provide a robust set of cloud
230:04 and provide a robust set of cloud deployment options
230:16 next let's talk about cisco fabric path cisco fabric path is a cisco nexus
230:19 cisco fabric path is a cisco nexus operating system
230:21 operating system software innovation combining the
230:22 software innovation combining the plug-and-play simplicity of ethernet
230:25 plug-and-play simplicity of ethernet with the reliability and scalability of
230:28 with the reliability and scalability of layer 3 routing
230:30 layer 3 routing using fabric path you can build highly
230:32 using fabric path you can build highly scalable
230:33 scalable layer 2 multi-path networks without
230:36 layer 2 multi-path networks without using the spanning tree protocol
230:39 using the spanning tree protocol such networks are particularly suitable
230:41 such networks are particularly suitable for large virtualization deployments
230:44 for large virtualization deployments private clouds in high performance
230:45 private clouds in high performance computing environments
230:48 computing environments when deployed across multiple cisco
230:50 when deployed across multiple cisco nexus chassis
230:52 nexus chassis the fabric path creates a flat data
230:54 the fabric path creates a flat data center switching fabric with high
230:56 center switching fabric with high switching capacity
230:58 switching capacity high cross sectional bandwidth and low
231:01 high cross sectional bandwidth and low predictable latency
231:10 overlay transport virtualization otv or overlay transport virtualization
231:13 otv or overlay transport virtualization on the nexus 7000
231:15 on the nexus 7000 is an industry first technology that
231:17 is an industry first technology that significantly simplifies
231:19 significantly simplifies extending layer 2 applications across
231:21 extending layer 2 applications across distributed data centers
231:23 distributed data centers you can now deploy data center
231:25 you can now deploy data center interconnect between sites without
231:27 interconnect between sites without changing or reconfiguring your existing
231:30 changing or reconfiguring your existing network design
231:32 network design with otv you can deploy virtual
231:34 with otv you can deploy virtual computing resources
231:35 computing resources and clusters across geographically
231:37 and clusters across geographically distributed data centers
231:39 distributed data centers delivering transparent workload mobility
231:42 delivering transparent workload mobility business resiliency
231:44 business resiliency and superior computing resource
231:46 and superior computing resource effectiveness
231:54 next fabric management and operations cisco dynamic fabric automation or dfa
231:58 cisco dynamic fabric automation or dfa boosts network flexibility and
232:00 boosts network flexibility and efficiency
232:01 efficiency dfa innovations simplify fabric
232:04 dfa innovations simplify fabric management
232:05 management optimize fabric infrastructure and
232:08 optimize fabric infrastructure and automate provisioning across physical
232:10 automate provisioning across physical and virtual environments
232:12 and virtual environments you gain unsurpassed operational
232:14 you gain unsurpassed operational simplicities through superior
232:16 simplicities through superior integration
232:18 integration dfa offers customers a number of
232:20 dfa offers customers a number of significant advantages
232:23 significant advantages optimized fabric infrastructure for
232:25 optimized fabric infrastructure for enhanced efficiency and scale
232:28 enhanced efficiency and scale optimized spine leaf topologies provide
232:31 optimized spine leaf topologies provide enhanced forwarding in a distributed
232:33 enhanced forwarding in a distributed control plane
232:35 control plane and integrated physical and virtual
232:37 and integrated physical and virtual environments
232:39 environments the topologies help enable
232:42 the topologies help enable any network anywhere supporting
232:44 any network anywhere supporting transparent mobility for physical
232:47 transparent mobility for physical servers and virtual machines plus
232:49 servers and virtual machines plus network extensibility
232:51 network extensibility you benefit from extensible resiliency
232:54 you benefit from extensible resiliency with smaller failure domains and
232:56 with smaller failure domains and multi-tenant scale
232:59 multi-tenant scale simplified fabric management with open
233:02 simplified fabric management with open apis for ease of operations
233:05 apis for ease of operations the cisco prime data center network
233:07 the cisco prime data center network manager
233:08 manager offers centralized fabric management
233:10 offers centralized fabric management across both physical
233:12 across both physical and virtual machines
233:15 and virtual machines automated provisioning for greater
233:17 automated provisioning for greater agility
233:18 agility having complete mobility access across
233:20 having complete mobility access across the fabric dfa uses network automation
233:24 the fabric dfa uses network automation and provisioning to simplify physical
233:26 and provisioning to simplify physical server and virtual machine deployments
233:30 server and virtual machine deployments network admin defined profile templates
233:32 network admin defined profile templates are used for both physical and the
233:35 are used for both physical and the virtual machine
233:41 when a server administrator provisions virtual machine and physical servers
233:43 virtual machine and physical servers instances of network policies are
233:45 instances of network policies are automatically created and applied to the
233:48 automatically created and applied to the network leaf switch as virtual machines
233:51 network leaf switch as virtual machines move across the fabric the network
233:53 move across the fabric the network policy is automatically applied to the
233:55 policy is automatically applied to the leaf switch
234:00 extended sand extended sand service to any device
234:04 extended sand service to any device storage network managers have long been
234:06 storage network managers have long been challenges
234:16 extended sand service to any device storage network managers
234:18 storage network managers have long been challenged to deliver
234:20 have long been challenged to deliver services such as encryption
234:22 services such as encryption data migration compression and
234:23 data migration compression and acceleration
234:25 acceleration the best way to optimize data center
234:27 the best way to optimize data center resources
234:28 resources is to deploy
234:30 is to deploy high performance storage networking
234:32 high performance storage networking services using the cisco mds 9000
234:35 services using the cisco mds 9000 products as the platform
234:38 products as the platform the benefits of mds 9000 services
234:42 the benefits of mds 9000 services oriented sands are services are
234:44 oriented sands are services are integrated into the sand fabric without
234:46 integrated into the sand fabric without wasted ports
234:48 wasted ports the benefits of mds 9000 services
234:51 the benefits of mds 9000 services oriented sands are services are
234:53 oriented sands are services are integrated into the sand fabric without
234:55 integrated into the sand fabric without wasted ports re-cabling
234:57 wasted ports re-cabling sand reconfigurations or deployment
234:59 sand reconfigurations or deployment disruption
235:00 disruption deployment times are dramatically
235:02 deployment times are dramatically reduced because performance is added by
235:04 reduced because performance is added by adding service engines
235:06 adding service engines automatic load balancing and traffic
235:07 automatic load balancing and traffic redirect failure help ensure high
235:09 redirect failure help ensure high availability
235:11 availability and consolidating important tasks into
235:13 and consolidating important tasks into the fabric supports transparent
235:15 the fabric supports transparent extension
235:16 extension of any sand service to any device
235:20 of any sand service to any device intelligent fabric applications
235:23 intelligent fabric applications optimize your data center resources by
235:25 optimize your data center resources by providing integrated
235:27 providing integrated high performance applications to cisco
235:29 high performance applications to cisco storage networks
235:31 storage networks support disaster recovery security
235:34 support disaster recovery security data mobility and other heterogeneous
235:36 data mobility and other heterogeneous storage requirements without adding
235:38 storage requirements without adding appliances
235:39 appliances or using host or array resources cisco
235:42 or using host or array resources cisco mds 9000 family service at nodes provide
235:45 mds 9000 family service at nodes provide network hosted services to cisco storage
235:48 network hosted services to cisco storage networks
235:49 networks such as stand extension
235:51 such as stand extension io acceleration
235:53 io acceleration xrc acceleration
235:55 xrc acceleration storage media encryption or data
235:57 storage media encryption or data mobility manager
236:00 mobility manager network-assisted applications are
236:02 network-assisted applications are enabled through the open intelligence
236:04 enabled through the open intelligence services api
236:06 services api cisco makes this development platform
236:08 cisco makes this development platform available to original storage
236:09 available to original storage manufacturers
236:11 manufacturers and independent software vendors who
236:13 and independent software vendors who want to develop storage applications on
236:15 want to develop storage applications on the cisco storage network's platform
236:18 the cisco storage network's platform storage network administrators get
236:20 storage network administrators get flexibility to extend any service to any
236:23 flexibility to extend any service to any device in the storage network
236:25 device in the storage network i o intensive data path processing tasks
236:28 i o intensive data path processing tasks at wire speed
236:30 at wire speed transparent to host and array
236:32 transparent to host and array applications
236:33 applications and much more
236:35 and much more so here's what you've learned you've
236:36 so here's what you've learned you've learned about key components of the data
236:39 learned about key components of the data center all this you'll need to know for
236:41 center all this you'll need to know for your ccda exam
236:42 your ccda exam we covered fiber channel over ethernet
236:44 we covered fiber channel over ethernet data center bridging unified ports
236:48 data center bridging unified ports intercloud fabric fabric path
236:51 intercloud fabric fabric path overlay transport virtualization
236:53 overlay transport virtualization fabric management and extended sand you
236:56 fabric management and extended sand you can expect questions on any of these
236:58 can expect questions on any of these technologies in your ccda exam and i'm
237:01 technologies in your ccda exam and i'm confident because you've watched this
237:02 confident because you've watched this video
237:03 video that if you know it well you will be
237:05 that if you know it well you will be prepared to answer any question they may
237:08 prepared to answer any question they may pose to you good luck in your studies
237:35 hi this is david voss cci11372 and in this video you're going
237:37 cci11372 and in this video you're going to learn about cisco virtualization
237:42 to learn about cisco virtualization in this video you're going to learn
237:43 in this video you're going to learn about the advantages of virtualization
237:46 about the advantages of virtualization it's drivers
237:48 it's drivers the types of virtualization
237:50 the types of virtualization and finally the platforms that support
237:53 and finally the platforms that support virtualization
237:55 virtualization so let's begin
237:57 so let's begin the official definition of computer
237:59 the official definition of computer virtualization is the pooling and
238:01 virtualization is the pooling and abstraction of resources and services
238:05 abstraction of resources and services in a way that masks the physical nature
238:07 in a way that masks the physical nature and boundaries of those resources and
238:10 and boundaries of those resources and services
238:12 services a good example is a vlan because it
238:15 a good example is a vlan because it masks the physical nature of resources
238:19 masks the physical nature of resources the concept of virtualization dates all
238:21 the concept of virtualization dates all the way back to the 1970s with ibm
238:24 the way back to the 1970s with ibm mainframes
238:26 mainframes these mainframes were separated into
238:28 these mainframes were separated into virtual machines so that different tasks
238:31 virtual machines so that different tasks could run separately
238:33 could run separately and to prevent a process failure that
238:35 and to prevent a process failure that could affect the entire system
238:39 could affect the entire system one of the issues that i t departments
238:41 one of the issues that i t departments face today is called server sprawl
238:44 face today is called server sprawl this concept implies that each
238:46 this concept implies that each application is installed on its own
238:48 application is installed on its own server
238:49 server and every time another server is added
238:52 and every time another server is added issues such as power
238:54 issues such as power space and cooling must be
238:56 space and cooling must be addressed these are just a few of the
238:59 addressed these are just a few of the many issues and none of them are cost
239:01 many issues and none of them are cost effective
239:02 effective however these challenges can be
239:04 however these challenges can be mitigated with server virtualization
239:07 mitigated with server virtualization that allows the partitioning of a
239:09 that allows the partitioning of a physical server to work with multiple
239:12 physical server to work with multiple operating systems and application
239:14 operating systems and application instances
239:16 instances the most important advantages are
239:18 the most important advantages are improved failover capabilities
239:21 improved failover capabilities better utilization of resources and a
239:24 better utilization of resources and a smaller footprint
239:26 smaller footprint virtualization is a concept that applies
239:28 virtualization is a concept that applies to many areas in modern i.t
239:31 to many areas in modern i.t infrastructures
239:32 infrastructures and it's not limited to servers
239:39 it can include networks storage
239:40 storage applications and desktop
239:44 applications and desktop network virtualization refers to one
239:47 network virtualization refers to one physical network
239:48 physical network supporting a wide array of logical
239:51 supporting a wide array of logical topologies
239:52 topologies this allows actions such as outsourcing
239:55 this allows actions such as outsourcing by the i t department
239:57 by the i t department where a logical topology can be created
240:00 where a logical topology can be created that can be accessed by external ite
240:02 that can be accessed by external ite professionals
240:04 professionals network virtualization with cisco
240:06 network virtualization with cisco products
240:07 products is typically classified into four areas
240:11 is typically classified into four areas control plane virtualization
240:14 control plane virtualization this is making sure processes like
240:16 this is making sure processes like routing are separated
240:18 routing are separated and distinct so
240:19 and distinct so routing process failure will not affect
240:22 routing process failure will not affect the entire device
240:24 the entire device data plane virtualization
240:26 data plane virtualization this is done
240:27 this is done every time different streams of data
240:30 every time different streams of data traffic are multiplexed that is
240:33 traffic are multiplexed that is different forms of traffic are placed on
240:35 different forms of traffic are placed on the same medium
240:36 the same medium the simplest example of data plane
240:38 the simplest example of data plane virtualization is a trunk link between
240:41 virtualization is a trunk link between two devices
240:43 two devices management plane virtualization
240:46 management plane virtualization this implies the ability to make a
240:48 this implies the ability to make a software upgrade on a device without
240:50 software upgrade on a device without rebooting that device
240:57 or having it loses capabilities to communicate on the network
241:00 communicate on the network and then pooling and clustering
241:03 and then pooling and clustering this for example is used on the cisco
241:05 this for example is used on the cisco catalyst 6500
241:08 catalyst 6500 virtual switching system
241:10 virtual switching system and it works by creating pools of
241:11 and it works by creating pools of devices that act as a single device
241:20 another example is the nexus vpc or virtual port channel
241:22 virtual port channel which allows either channels to be
241:24 which allows either channels to be created that span across multiple
241:26 created that span across multiple devices
241:31 virtualization has become a critical component in most enterprise networks
241:33 component in most enterprise networks because of modern demands in it
241:36 because of modern demands in it including increasing efficiency while
241:39 including increasing efficiency while reducing capital and operational costs
241:42 reducing capital and operational costs virtualization is a critical component
241:44 virtualization is a critical component of the cisco enterprise network
241:46 of the cisco enterprise network architecture
241:48 architecture virtualization can represent a variety
241:50 virtualization can represent a variety of technologies including extracting the
241:52 of technologies including extracting the logical components from hardware or
241:55 logical components from hardware or networks and implementing them into a
241:57 networks and implementing them into a virtual environment
242:05 some of the drivers behind implementing a virtualized environment are as follows
242:08 a virtualized environment are as follows the need to reduce the number of
242:10 the need to reduce the number of physical devices that perform individual
242:12 physical devices that perform individual tasks the need to reduce operational
242:15 tasks the need to reduce operational costs
242:17 costs the need to increase productivity
242:20 the need to increase productivity the need for flexible connectivity
242:22 the need for flexible connectivity and the need to eliminate underutilized
242:25 and the need to eliminate underutilized hardware
242:26 hardware virtualization can be implemented at
242:29 virtualization can be implemented at both the network and the device level
242:31 both the network and the device level network virtualization involves the
242:33 network virtualization involves the creation of network partitions that run
242:36 creation of network partitions that run on physical infrastructure
242:38 on physical infrastructure with each logical partition acting as an
242:40 with each logical partition acting as an independent network
242:42 independent network network virtualization can include vlans
242:45 network virtualization can include vlans vsans vpns and vrfs
242:53 on the other hand device virtualization allows logical devices to run
242:55 allows logical devices to run independently of each other on a single
242:58 independently of each other on a single physical machine
243:00 physical machine virtual hardware devices are created in
243:02 virtual hardware devices are created in software and have the same functionality
243:04 software and have the same functionality as real hardware devices
243:06 as real hardware devices the possibility of combining multiple
243:09 the possibility of combining multiple physical devices into one single logical
243:11 physical devices into one single logical unit also exists
243:14 unit also exists the cisco enterprise network
243:15 the cisco enterprise network architecture contains multiple forms of
243:18 architecture contains multiple forms of network and device virtualization such
243:20 network and device virtualization such as the following
243:22 as the following virtual machines virtual switches
243:25 virtual machines virtual switches virtual lans
243:27 virtual lans virtual private networks
243:30 virtual private networks virtual storage area networks
243:32 virtual storage area networks virtual switching systems
243:35 virtual switching systems virtual routing and forwarding virtual
243:38 virtual routing and forwarding virtual port channels and virtual device
243:40 port channels and virtual device contexts
243:43 contexts device contacts allow the partitioning
243:45 device contacts allow the partitioning of a single partition into multiple
243:47 of a single partition into multiple virtual devices called contexts a
243:50 virtual devices called contexts a context acts as an independent device
243:52 context acts as an independent device with its own set of policies
243:55 with its own set of policies the majority of features implemented on
243:57 the majority of features implemented on the real device are also functional on
243:59 the real device are also functional on the virtual context
244:01 the virtual context some of the devices in the cisco
244:02 some of the devices in the cisco portfolio that support virtual contexts
244:05 portfolio that support virtual contexts include the following
244:07 include the following cisco asa
244:09 cisco asa cisco ase
244:10 cisco ase cisco ips and cisco nexus series
244:15 cisco ips and cisco nexus series server virtualization allows the
244:17 server virtualization allows the server's resources to be extracted in
244:19 server's resources to be extracted in order to offer flexibility and usage
244:22 order to offer flexibility and usage optimization in the infrastructure
244:25 optimization in the infrastructure the result is that data center
244:26 the result is that data center applications are no longer tied to
244:28 applications are no longer tied to specific hardware resources
244:30 specific hardware resources so the applications are unaware of the
244:32 so the applications are unaware of the underlying hardware
244:34 underlying hardware server virtualization solutions are
244:36 server virtualization solutions are produced by companies such as vmware
244:39 produced by companies such as vmware microsoft and citrix
244:46 now all this being said there are unique design considerations to network
244:49 design considerations to network virtualization
244:56 network solutions are needed to solve the challenges of sharing network
244:58 the challenges of sharing network resources
244:59 resources but keeping users totally separate from
245:02 but keeping users totally separate from one another
245:03 one another although the users are separate we need
245:05 although the users are separate we need to ensure that the network is highly
245:07 to ensure that the network is highly available
245:09 available secure and can scale along with business
245:12 secure and can scale along with business growth
245:13 growth network virtualization offers solutions
245:15 network virtualization offers solutions to these challenges
245:17 to these challenges and provides design considerations
245:19 and provides design considerations around access control
245:21 around access control path isolation and services edge
245:25 path isolation and services edge regarding access control access needs to
245:28 regarding access control access needs to be controlled to ensure that users and
245:30 be controlled to ensure that users and devices are identified
245:32 devices are identified and authorized for entry to their
245:34 and authorized for entry to their assigned network segment
245:36 assigned network segment security at the access layer is critical
245:38 security at the access layer is critical for protecting the network from threats
245:41 for protecting the network from threats both internal and external
245:44 both internal and external path isolation this involves the
245:47 path isolation this involves the creation of independent logical network
245:49 creation of independent logical network paths
245:50 paths over a shared network infrastructure
245:53 over a shared network infrastructure mpls vpn is an example of path isolation
245:57 mpls vpn is an example of path isolation technique where devices are mapped to a
246:00 technique where devices are mapped to a vrf to access the correct set of network
246:03 vrf to access the correct set of network resources
246:05 resources other segmentation options include vlans
246:09 other segmentation options include vlans and vsans which logically separate lands
246:12 and vsans which logically separate lands and sands
246:14 and sands the main goal when segmenting the
246:16 the main goal when segmenting the network is to improve the scalability
246:18 network is to improve the scalability resiliency and security services
246:21 resiliency and security services as with non-segmented networks
246:27 services edge the services edge refers to making
246:29 the services edge refers to making network services available to the
246:31 network services available to the intended users
246:33 intended users and devices with an enforced centralized
246:35 and devices with an enforced centralized managed policy
246:38 managed policy separate groups or devices occasionally
246:40 separate groups or devices occasionally need to share information that may be on
246:42 need to share information that may be on different vlans
246:44 different vlans each with corresponding group policies
246:52 in such cases the network should have a central way to manage the policy and
246:55 central way to manage the policy and control access to the resources
246:58 control access to the resources so here's what you've learned you've
246:59 so here's what you've learned you've learned about cisco virtualization the
247:02 learned about cisco virtualization the different types of virtualization but
247:04 different types of virtualization but also the platforms that support this
247:06 also the platforms that support this type of virtualization
247:08 type of virtualization the fact is this type of software
247:10 the fact is this type of software defined networking is radically changing
247:14 defined networking is radically changing how
247:15 how engineers
247:16 engineers are going to design their networks and
247:19 are going to design their networks and to understand this is not only important
247:21 to understand this is not only important for your ccda exam
247:23 for your ccda exam but as you go forward in your career
247:27 but as you go forward in your career good luck in your studies
247:53 hi this is david voss ccie11372 and in this video you're going
247:55 ccie11372 and in this video you're going to learn about network programmability
247:58 to learn about network programmability specifically we're going to talk about
248:00 specifically we're going to talk about cisco's implementation of scn cisco aci
248:05 cisco's implementation of scn cisco aci and we'll discuss its benefits
248:08 and we'll discuss its benefits and its attributes
248:09 and its attributes all this you should know for your ccda
248:12 all this you should know for your ccda exam
248:13 exam so let's go ahead and begin
248:21 i t departments and lines of business are looking at cloud automation tools
248:23 are looking at cloud automation tools and software-defined networking
248:24 and software-defined networking architectures
248:26 architectures to accelerate application delivery
248:28 to accelerate application delivery reduce operating costs and greatly
248:31 reduce operating costs and greatly increased business agility
248:34 increased business agility cisco application-centric infrastructure
248:37 cisco application-centric infrastructure or cisco aci
248:39 or cisco aci is a comprehensive sdn architecture
248:42 is a comprehensive sdn architecture this policy-based automation solution
248:45 this policy-based automation solution supports a business relevant application
248:47 supports a business relevant application policy language
248:49 policy language greater scalability through a
248:51 greater scalability through a distributed enforcement system and
248:53 distributed enforcement system and greater network visibility
248:56 greater network visibility these benefits are achieved through the
248:57 these benefits are achieved through the integration of physical in virtual
249:00 integration of physical in virtual environments under one policy model for
249:03 environments under one policy model for networks server storage services and
249:06 networks server storage services and security
249:07 security through cisco aci customers are reducing
249:10 through cisco aci customers are reducing application deployment times from weeks
249:12 application deployment times from weeks to minutes it also dramatically improves
249:15 to minutes it also dramatically improves i.t alignment with business objectives
249:18 i.t alignment with business objectives and policy requirements
249:21 and policy requirements cisco aci is built on the application
249:24 cisco aci is built on the application centric policy
249:25 centric policy based on cisco application policy
249:27 based on cisco application policy infrastructure controller or what is
249:29 infrastructure controller or what is known as apec
249:31 known as apec the cisco aci fabric which is based on
249:34 the cisco aci fabric which is based on the cisco nexus 9000 series switches
249:37 the cisco nexus 9000 series switches and the cisco application virtual switch
249:40 and the cisco application virtual switch and the cisco aci partner ecosystem
249:44 and the cisco aci partner ecosystem aci provides a network that is deployed
249:47 aci provides a network that is deployed monitored and managed in a way that
249:49 monitored and managed in a way that benefits different teams in the it
249:51 benefits different teams in the it organization including
249:53 organization including sdn network cloud and devops and
249:55 sdn network cloud and devops and security
249:57 security it supports rapid application change by
249:59 it supports rapid application change by reducing complexity with a common policy
250:01 reducing complexity with a common policy framework that can automate provisioning
250:04 framework that can automate provisioning and resource management
250:10 you can facilitate rapid systems integration and customization for
250:12 integration and customization for network services monitoring
250:14 network services monitoring management and orchestration
250:16 management and orchestration cisco aci is a comprehensive sdn
250:19 cisco aci is a comprehensive sdn solution making the application the
250:21 solution making the application the focal point it is delivered in an agile
250:24 focal point it is delivered in an agile open and highly secure architecture
250:26 open and highly secure architecture and its application based policy model
250:29 and its application based policy model offers speed through automation reducing
250:32 offers speed through automation reducing errors and accelerating application
250:33 errors and accelerating application deployment in it processes from weeks to
250:36 deployment in it processes from weeks to minutes
250:37 minutes application-based policies decouple
250:39 application-based policies decouple high-level application connectivity
250:41 high-level application connectivity needs from the complicated details of
250:44 needs from the complicated details of network configuration
250:46 network configuration this results in automated it processes
250:48 this results in automated it processes that simplify operations
250:51 that simplify operations aci provides transparent support of
250:54 aci provides transparent support of heterogeneous physical and virtual
250:56 heterogeneous physical and virtual endpoints such as bare metal servers and
250:59 endpoints such as bare metal servers and virtual servers on any hypervisor with
251:02 virtual servers on any hypervisor with layer 2 to 7 network services using
251:04 layer 2 to 7 network services using consistent policy
251:06 consistent policy this provides faster troubleshooting
251:08 this provides faster troubleshooting through increased visibility of the
251:10 through increased visibility of the entire infrastructure
251:12 entire infrastructure cisco aci supports open apis open source
251:16 cisco aci supports open apis open source and open standards to optimize customer
251:18 and open standards to optimize customer choice and flexibility
251:20 choice and flexibility in fact cisco contributes technology
251:22 in fact cisco contributes technology specifications to open source and
251:24 specifications to open source and standards communities
251:25 standards communities the open integration with existing data
251:27 the open integration with existing data center management tools and
251:29 center management tools and comprehensive open partner ecosystem
251:31 comprehensive open partner ecosystem helps to ensure flexibility while
251:34 helps to ensure flexibility while decreasing costs and increasing
251:35 decreasing costs and increasing innovation
251:38 innovation provisioning applications has become
251:40 provisioning applications has become easy with programmable infrastructure
251:42 easy with programmable infrastructure yet onboarding them is still difficult
251:44 yet onboarding them is still difficult cloud architects have to know what
251:46 cloud architects have to know what infrastructure design will support
251:48 infrastructure design will support frequent application changes to
251:50 frequent application changes to performance security availability and
251:52 performance security availability and scale
251:53 scale devops has to work with both application
251:56 devops has to work with both application and admin teams to understand how
251:58 and admin teams to understand how numerous application changes
252:00 numerous application changes affect the configuration of switches
252:02 affect the configuration of switches ports vlans firewalls
252:04 ports vlans firewalls security appliances load balancers and
252:07 security appliances load balancers and other application delivery functions
252:10 other application delivery functions all changes must work within a shared
252:12 all changes must work within a shared production and infrastructure
252:14 production and infrastructure without affecting existing attendance
252:17 without affecting existing attendance and applications
252:19 and applications cisco aci introduces a simple
252:21 cisco aci introduces a simple application level policy based approach
252:24 application level policy based approach application intentions are automatically
252:27 application intentions are automatically translated to infrastructure design
252:29 translated to infrastructure design without requiring knowledge of devices
252:31 without requiring knowledge of devices or the effort to translate to
252:33 or the effort to translate to configurations
252:35 configurations this helps to enable policy aware
252:37 this helps to enable policy aware resource orchestration real-time
252:39 resource orchestration real-time governance and open choice in cloud
252:42 governance and open choice in cloud software cisco aci and the apic sdn
252:46 software cisco aci and the apic sdn controller allow for security policies
252:48 controller allow for security policies down to the individual tenant
252:49 down to the individual tenant application or workload
252:52 application or workload they provide protection that meets the
252:53 they provide protection that meets the most stringent business and compliance
252:55 most stringent business and compliance requirements
252:57 requirements the whitelist model permits the
252:58 the whitelist model permits the communication only were explicitly
253:00 communication only were explicitly allowed
253:01 allowed helping to ensure that policy omissions
253:04 helping to ensure that policy omissions do not leave security vulnerabilities
253:07 do not leave security vulnerabilities through cisco aci all security device
253:09 through cisco aci all security device provisioning
253:10 provisioning and configuration can be automated
253:12 and configuration can be automated according to the centrally managed
253:14 according to the centrally managed application policies and requirements
253:17 application policies and requirements this simplifies i.t security tasks and
253:20 this simplifies i.t security tasks and accelerates application deployments
253:29 cisco nexus 9000 series switches bring new industry-leading performance power
253:31 new industry-leading performance power port density and open programming
253:33 port density and open programming innovations
253:35 innovations the products that support cisco aci are
253:37 the products that support cisco aci are the cisco nexus 9000 series
253:40 the cisco nexus 9000 series in addition the cisco application
253:42 in addition the cisco application virtual switch which provides a
253:44 virtual switch which provides a consistent virtual switch infrastructure
253:46 consistent virtual switch infrastructure between aci fabrics and the cisco nexus
253:48 between aci fabrics and the cisco nexus 1000v virtual switch
253:51 1000v virtual switch the cisco application policy
253:53 the cisco application policy infrastructure controller which
253:55 infrastructure controller which programmatically automates network
253:57 programmatically automates network provisioning and control based on
253:58 provisioning and control based on application requirements and policies
254:01 application requirements and policies and the cisco application centric
254:03 and the cisco application centric infrastructure security for data centers
254:05 infrastructure security for data centers solves many complexities in customer
254:07 solves many complexities in customer environments
254:08 environments it treats firewalls as a pool of
254:10 it treats firewalls as a pool of resources and intelligently stitches
254:13 resources and intelligently stitches them according to application network
254:15 them according to application network policies
254:16 policies aci security offers full acceleration
254:19 aci security offers full acceleration dynamically in hardware and directly
254:22 dynamically in hardware and directly integrates into cisco aci
254:26 integrates into cisco aci when considering cisco aci it's
254:28 when considering cisco aci it's important to define desired business
254:30 important to define desired business outcomes and plan each stage of the
254:32 outcomes and plan each stage of the journey
254:34 journey then you'll want to know how to
254:35 then you'll want to know how to accelerate the benefits of aci while
254:37 accelerate the benefits of aci while mitigating the risks
254:39 mitigating the risks you need to develop an aci adoption
254:41 you need to develop an aci adoption strategy based on business and
254:43 strategy based on business and technology needs
254:44 technology needs you need to provide a migration strategy
254:46 you need to provide a migration strategy and operational readiness
254:48 and operational readiness you need to deploy proof of concept to
254:51 you need to deploy proof of concept to gain experience and reduce the
254:52 gain experience and reduce the deployment risk
254:54 deployment risk and then design application-centric data
254:56 and then design application-centric data centers based on the aci fabric pods and
254:59 centers based on the aci fabric pods and policy templates
255:04 so here's what you've learned you've learned about cisco's deployment of
255:07 learned about cisco's deployment of software-defined networking
255:09 software-defined networking which is cisco aci
255:11 which is cisco aci this you'll need to know for your ccda
255:14 this you'll need to know for your ccda exam
255:15 exam but more importantly you will need to
255:17 but more importantly you will need to know this if you're going to work in the
255:19 know this if you're going to work in the future
255:20 future of network engineering
255:22 of network engineering good luck in your studies
255:47 hi this is david voss cci11372 and in this video
255:49 and in this video you're going to learn about network
255:51 you're going to learn about network resiliency
255:52 resiliency and fault domains in preparation for
255:54 and fault domains in preparation for your cisco ccda exam
255:57 your cisco ccda exam specifically you're going to learn about
256:00 specifically you're going to learn about network device and operational
256:02 network device and operational resiliency
256:04 resiliency and also the concept of fault domains
256:08 and also the concept of fault domains so let's go ahead and begin
256:18 there are three major resiliency requirements which encompass most of the
256:21 requirements which encompass most of the common types of failure conditions
256:23 common types of failure conditions depending on the land design tier the
256:26 depending on the land design tier the resiliency option appropriate for the
256:28 resiliency option appropriate for the role and network service type must be
256:30 role and network service type must be deployed
256:32 deployed there is network resiliency which
256:34 there is network resiliency which provides redundancy through physical
256:36 provides redundancy through physical link failures such as a fiber cut
256:39 link failures such as a fiber cut device resiliency which protects the
256:41 device resiliency which protects the network during abnormal mode failure
256:43 network during abnormal mode failure triggered by hardware or software
256:46 triggered by hardware or software and then operational resiliency which
256:47 and then operational resiliency which enables resiliency capabilities to the
256:50 enables resiliency capabilities to the next level
256:51 next level providing complete network availability
256:53 providing complete network availability even during planned network outages
256:56 even during planned network outages we'll talk about all of these in this
256:59 we'll talk about all of these in this video
257:03 first we'll talk about network resiliency
257:05 resiliency the most common network fault occurrence
257:07 the most common network fault occurrence in the lan network is a link failure
257:09 in the lan network is a link failure between two systems
257:11 between two systems link failures can be caused by issues
257:13 link failures can be caused by issues such as a fiber cut miswiring
257:15 such as a fiber cut miswiring line card module failure etc
257:18 line card module failure etc in the modular platform design the
257:20 in the modular platform design the redundant parallel physical links
257:22 redundant parallel physical links between distributed models in two
257:24 between distributed models in two systems
257:25 systems reduces fault probabilities and can
257:27 reduces fault probabilities and can increase network availability
257:29 increase network availability it is important to remember how multiple
257:31 it is important to remember how multiple parallel paths between two systems also
257:34 parallel paths between two systems also affect how higher layer protocols
257:37 affect how higher layer protocols into adjacencies and loop free
257:39 into adjacencies and loop free forwarding topologies
257:42 forwarding topologies deploying redundant parallel paths in
257:44 deploying redundant parallel paths in the recommended borderless campus design
257:47 the recommended borderless campus design by default develops a non-optimal
257:49 by default develops a non-optimal topology
257:50 topology that keeps the network underutilized and
257:52 that keeps the network underutilized and requires protocol-based network recovery
257:55 requires protocol-based network recovery in the same network design the routered
257:57 in the same network design the routered access module eliminates such
257:59 access module eliminates such limitations and enables full load
258:01 limitations and enables full load balancing capabilities to increase
258:03 balancing capabilities to increase bandwidth capacity and minimize
258:06 bandwidth capacity and minimize application impact during a single path
258:08 application impact during a single path failure
258:09 failure to develop consistent network resiliency
258:11 to develop consistent network resiliency service in the centralized main and
258:13 service in the centralized main and remote campus sites the following basic
258:16 remote campus sites the following basic principles apply
258:18 principles apply deploying redundant parallel paths is a
258:20 deploying redundant parallel paths is a basic requirement for network resiliency
258:23 basic requirement for network resiliency at any tier it is critical to simplify
258:26 at any tier it is critical to simplify the control plane and forwarding plane
258:28 the control plane and forwarding plane operation by bundling all physical paths
258:31 operation by bundling all physical paths into a single logical
258:33 into a single logical logical bundled interface such as ether
258:35 logical bundled interface such as ether channel
258:37 channel implement a defense in-depth approach to
258:39 implement a defense in-depth approach to failure detection and recovery
258:41 failure detection and recovery an example of this is configuring the
258:43 an example of this is configuring the udld protocol that's unidirectional link
258:46 udld protocol that's unidirectional link detection
258:47 detection which uses a layer to keep alive to test
258:50 which uses a layer to keep alive to test that the switch to switch links are
258:52 that the switch to switch links are connected and operating correctly and
258:54 connected and operating correctly and acts as a backup to the native layer 1
258:56 acts as a backup to the native layer 1 unidirectional link detection
258:58 unidirectional link detection capabilities provided by 802.3z
259:02 capabilities provided by 802.3z and
259:03 and 802.3ae standards
259:06 802.3ae standards ensure that the network design is
259:08 ensure that the network design is self-stabilizing
259:09 self-stabilizing hardware or software errors may cause
259:11 hardware or software errors may cause ports to flap which creates fault false
259:14 ports to flap which creates fault false alarms and destabilizes the network
259:16 alarms and destabilizes the network topology
259:17 topology implementing route summarization
259:19 implementing route summarization advertises a concise topology view of
259:22 advertises a concise topology view of the network
259:23 the network which prevents core network instability
259:33 next let's talk about device resiliency another major component of an overall
259:35 another major component of an overall campus high availability framework is
259:37 campus high availability framework is providing the device or node level
259:39 providing the device or node level protection
259:40 protection that can be triggered during any type of
259:42 that can be triggered during any type of abnormal internal hardware or software
259:44 abnormal internal hardware or software process within the system
259:46 process within the system some of the common internal failures are
259:49 some of the common internal failures are software triggered crash
259:51 software triggered crash power outages line card failures etc
260:01 lan network devices can be considered as a single point of failure and are
260:03 a single point of failure and are considered to be a major failure
260:04 considered to be a major failure conditions because recovery may require
260:07 conditions because recovery may require a network administrator to mitigate the
260:09 a network administrator to mitigate the failure and recover the system the
260:12 failure and recover the system the network recovery time can remain
260:13 network recovery time can remain undeterministic
260:15 undeterministic causing complete or partial network
260:17 causing complete or partial network outage depending on the network design
260:20 outage depending on the network design redundant hardware components for device
260:22 redundant hardware components for device resiliency vary between fixed
260:25 resiliency vary between fixed configuration and modular cisco catalyst
260:27 configuration and modular cisco catalyst switches
260:28 switches to protect against common network faults
260:30 to protect against common network faults or resets all critical borderless campus
260:33 or resets all critical borderless campus network devices must be deployed with a
260:36 network devices must be deployed with a similar device resiliency
260:38 similar device resiliency configuration let's talk about the basic
260:41 configuration let's talk about the basic redundant hardware deployment guidelines
260:43 redundant hardware deployment guidelines at the access layer and collapse core
260:46 at the access layer and collapse core switching platforms in the campus
260:48 switching platforms in the campus network
260:49 network redundant power system so redundant
260:52 redundant power system so redundant power supplies for network systems
260:53 power supplies for network systems protect against power outages
260:56 protect against power outages power supply failures
260:57 power supply failures and so on it is important not only to
261:00 and so on it is important not only to protect the internal network system but
261:02 protect the internal network system but also the endpoints that rely on power
261:04 also the endpoints that rely on power delivery over the ethernet network
261:07 delivery over the ethernet network redundant power systems can be deployed
261:09 redundant power systems can be deployed in the following two configuration modes
261:12 in the following two configuration modes modular switch
261:14 modular switch this is where dual power supplies can be
261:16 this is where dual power supplies can be deployed in modular switching platforms
261:18 deployed in modular switching platforms such as the cisco catalyst 6500 or 4500
261:22 such as the cisco catalyst 6500 or 4500 e-series platforms
261:25 e-series platforms by default the power supply operates in
261:27 by default the power supply operates in a redundant mode
261:29 a redundant mode offering one plus one redundant option
261:32 offering one plus one redundant option in modular catalyst and nexus switching
261:34 in modular catalyst and nexus switching systems the network administrator must
261:36 systems the network administrator must perform overall power capacity planning
261:40 perform overall power capacity planning to allow for dynamic network growth with
261:42 to allow for dynamic network growth with new line card modules
261:45 new line card modules the other option is fixed configuration
261:47 the other option is fixed configuration switch
261:48 switch depending on the switch that you're
261:49 depending on the switch that you're running fixed configuration switches
261:52 running fixed configuration switches offer a wide range of power redundancy
261:54 offer a wide range of power redundancy options
261:55 options cisco stack power can be one of them
261:58 cisco stack power can be one of them especially in the cisco catalyst
262:00 especially in the cisco catalyst 3750x series platform
262:03 3750x series platform to prevent network outages on fixed
262:05 to prevent network outages on fixed configuration catalyst switches they
262:07 configuration catalyst switches they must be deployed with power redundancy
262:16 next redundant control plane device or known resiliency in modular
262:18 device or known resiliency in modular cisco catalyst 6500e
262:20 cisco catalyst 6500e or nexus 7000 4500e in cisco stackwise
262:25 or nexus 7000 4500e in cisco stackwise plus platforms provides one plus one
262:27 plus platforms provides one plus one redundancy with enterprise class high
262:30 redundancy with enterprise class high availability and deterministic network
262:32 availability and deterministic network recovery time
262:34 recovery time the following subsections provide high
262:36 the following subsections provide high availability design details as well as
262:39 availability design details as well as graceful network recovery techniques
262:41 graceful network recovery techniques that do not impact the control plane and
262:44 that do not impact the control plane and provide constant forwarding capabilities
262:46 provide constant forwarding capabilities during failure events though
262:49 during failure events though to minimize the amount of time the
262:50 to minimize the amount of time the network is unavailable to users
262:52 network is unavailable to users following a switchover from a primary to
262:54 following a switchover from a primary to a secondary device
262:56 a secondary device the main goal is to continue forwarding
262:58 the main goal is to continue forwarding ip packets after the route processor
263:01 ip packets after the route processor switchover
263:02 switchover nsf is supported by a wide variety of
263:04 nsf is supported by a wide variety of dynamic routing protocols
263:07 dynamic routing protocols if a router is running one of these
263:08 if a router is running one of these protocols it can detect the internal
263:11 protocols it can detect the internal switchover and take the proper steps to
263:13 switchover and take the proper steps to continue forwarding network traffic
263:16 continue forwarding network traffic using and leveraging the forwarding
263:18 using and leveraging the forwarding information base
263:19 information base while recovering route information from
263:22 while recovering route information from its peer devices
263:24 its peer devices cisco nsf with sso is a mechanism of
263:27 cisco nsf with sso is a mechanism of supervisor redundancy
263:29 supervisor redundancy that is part of the ios software
263:32 that is part of the ios software and provides extremely fast supervisor
263:34 and provides extremely fast supervisor switchover at layer 2 3 and 4.
263:37 switchover at layer 2 3 and 4. sso allows the standby route processor
263:40 sso allows the standby route processor to take control of the device once a
263:42 to take control of the device once a hardware or software fault occurs on the
263:45 hardware or software fault occurs on the active route processor
263:47 active route processor sso synchronizes the following
263:49 sso synchronizes the following parameters
263:50 parameters startup configuration
263:53 startup configuration startup variables
263:55 startup variables the running configuration
263:58 the running configuration layer 2 protocol states for ports and
264:00 layer 2 protocol states for ports and trunks
264:01 trunks layer 2 and layer 3 tables
264:04 layer 2 and layer 3 tables access control lists and qos tables
264:11 next let's talk about operational resiliency
264:12 resiliency designing the network to recover from
264:14 designing the network to recover from failure events is only one aspect of the
264:16 failure events is only one aspect of the overall campus non-stop design
264:20 overall campus non-stop design converged network environments are
264:22 converged network environments are continuing to move forward requiring
264:24 continuing to move forward requiring true 7x24 by 365 availability
264:27 true 7x24 by 365 availability the borderless campus network is a part
264:29 the borderless campus network is a part of the backbone of the enterprise
264:31 of the backbone of the enterprise network and must be designed to enable
264:33 network and must be designed to enable standard operational processes
264:35 standard operational processes configuration changes and software and
264:37 configuration changes and software and hardware upgrades without disrupting
264:40 hardware upgrades without disrupting network services
264:42 network services the ability to make changes and upgrade
264:44 the ability to make changes and upgrade software and or replace or upgrade
264:46 software and or replace or upgrade hardware becomes challenging without a
264:48 hardware becomes challenging without a redundant system in the campus core
264:50 redundant system in the campus core upgrading individual devices without
264:52 upgrading individual devices without taking them out of service is similarly
264:54 taking them out of service is similarly based on having internal component
264:56 based on having internal component redundancy
264:59 redundancy the cisco in-service software upgrade
265:01 the cisco in-service software upgrade issu an enhanced fast software upgrade
265:05 issu an enhanced fast software upgrade efsu
265:06 efsu leverage nsf sso technology to provide
265:09 leverage nsf sso technology to provide continuous network availability while
265:12 continuous network availability while upgrading critical systems
265:15 upgrading critical systems this helps to greatly reduce the need
265:17 this helps to greatly reduce the need for planned service downtime and
265:19 for planned service downtime and maintenance
265:25 next let's talk about fault domains each network tier can be classified as a
265:28 each network tier can be classified as a fault domain
265:29 fault domain with the deployment of redundant
265:30 with the deployment of redundant components and systems increasing
265:32 components and systems increasing redundancy and load sharing capabilities
265:35 redundancy and load sharing capabilities however
265:36 however this introduces a new set of challenges
265:38 this introduces a new set of challenges namely higher costs and increased
265:40 namely higher costs and increased complexity in managing a greater number
265:42 complexity in managing a greater number of systems
265:43 of systems network reliability and availability can
265:46 network reliability and availability can be simplified using several cisco high
265:48 be simplified using several cisco high availability and virtual system
265:50 availability and virtual system technologies such as vss
265:53 technologies such as vss which offers complete failure
265:55 which offers complete failure transparency to end users
265:57 transparency to end users and applications during planned or
265:59 and applications during planned or unplanned network outages
266:01 unplanned network outages in this sense minor or major network
266:03 in this sense minor or major network failures are considered broad terms that
266:06 failures are considered broad terms that include several types of network faults
266:09 include several types of network faults which must be taken into consideration
266:11 which must be taken into consideration in order to implement a rapid recovery
266:14 in order to implement a rapid recovery solution
266:15 solution cisco high availability technologies can
266:18 cisco high availability technologies can be deployed based on whether platforms
266:20 be deployed based on whether platforms have critical or non-critical role in
266:22 have critical or non-critical role in the network
266:24 the network some of the high availability techniques
266:26 some of the high availability techniques can be achieved in the campus network
266:28 can be achieved in the campus network design
266:29 design without making major network changes
266:32 without making major network changes however the critical network systems
266:34 however the critical network systems that are deployed in the center of the
266:35 that are deployed in the center of the network to provide global connectivity
266:38 network to provide global connectivity may require additional hardware and
266:40 may require additional hardware and software components to offer non-stop
266:43 software components to offer non-stop communication
266:47 so here's what you've learned you've learned about network
266:49 learned about network device in operation resiliency
266:53 device in operation resiliency this is a key part of your ccda exam and
266:56 this is a key part of your ccda exam and then you also learned about the
266:57 then you also learned about the terminology of fault domains
267:00 terminology of fault domains and again this is something you could be
267:02 and again this is something you could be asked on your exam so now that you've
267:04 asked on your exam so now that you've watched this video i'm confident if
267:06 watched this video i'm confident if you're asked any questions regarding
267:08 you're asked any questions regarding resiliency or fault domains on your ccda
267:11 resiliency or fault domains on your ccda exam
267:12 exam you'll do very well good luck in your
267:14 you'll do very well good luck in your studies
267:42 hi this is david voss ccie 11372 and this video you're going to receive
267:44 and this video you're going to receive an overview of wan design we're going to
267:47 an overview of wan design we're going to cover some of the basics of wide area
267:49 cover some of the basics of wide area networking
267:51 networking so that you can properly lay a
267:53 so that you can properly lay a foundation
267:54 foundation for the topics that come up after this
267:56 for the topics that come up after this video
267:58 video so you can understand
267:59 so you can understand what specific wan technologies are out
268:01 what specific wan technologies are out there
268:02 there and where they fit within the enterprise
268:04 and where they fit within the enterprise campus
268:10 when technologies operate at the enterprise edge in the modular cisco
268:13 enterprise edge in the modular cisco enterprise infrastructure
268:15 enterprise infrastructure wands span across large geographical
268:18 wands span across large geographical distances
268:19 distances in order to provide connectivity for
268:20 in order to provide connectivity for various parts of the network
268:22 various parts of the network infrastructure
268:24 infrastructure unlike the lan environment some lan
268:27 unlike the lan environment some lan components are not owned by the specific
268:29 components are not owned by the specific enterprise
268:31 enterprise instead when equipment or connectivity
268:34 instead when equipment or connectivity can be rented or leased from service
268:36 can be rented or leased from service providers
268:38 providers most service providers are well trained
268:40 most service providers are well trained in supporting not only traditional data
268:43 in supporting not only traditional data traffic but also voice and video
268:45 traffic but also voice and video services
268:47 services in addition unlike lands winds typically
268:50 in addition unlike lands winds typically have an initial fixed cost
268:52 have an initial fixed cost and thereafter periodic recurring fees
268:55 and thereafter periodic recurring fees for services
268:56 for services which is one reason you never want to
268:58 which is one reason you never want to over provision your wide area network
269:01 over provision your wide area network because it's money down the drain
269:05 because it's money down the drain this cost and fee structure requires
269:07 this cost and fee structure requires implementing effective quality of
269:09 implementing effective quality of service mechanisms
269:11 service mechanisms in order to avoid buying additional land
269:13 in order to avoid buying additional land bandwidth when it's not necessary
269:17 bandwidth when it's not necessary when technology's design requirements
269:19 when technology's design requirements are typically derived from the following
269:22 are typically derived from the following application type
269:24 application type application availability
269:27 application availability application reliability
269:29 application reliability the costs associated with a particular
269:31 the costs associated with a particular wan technology
269:33 wan technology and usage levels for the application
269:36 and usage levels for the application all of these will dictate what type of
269:38 all of these will dictate what type of wan technology you're going to want to
269:41 wan technology you're going to want to use
269:43 use the enterprise edge represents a large
269:45 the enterprise edge represents a large block or it could be several blocks of
269:47 block or it could be several blocks of equipment
269:49 equipment this large module is typically split
269:50 this large module is typically split into smaller blocks
269:52 into smaller blocks each with a specialized functionality
269:56 each with a specialized functionality here are the following components you
269:58 here are the following components you will find in an enterprise
270:05 the wan block for branch offices and remote access connectivity
270:11 the e-commerce block which is a part of the organization and obviously serves
270:14 the organization and obviously serves the business customer facing business
270:17 the business customer facing business applications
270:19 applications the internet connectivity block which
270:21 the internet connectivity block which offers robust internet access
270:23 offers robust internet access with some level of availability and
270:25 with some level of availability and redundancy and also you'll find within
270:27 redundancy and also you'll find within this block
270:29 this block often your dmz services
270:32 often your dmz services and then the remote access or vpn block
270:34 and then the remote access or vpn block which provides secure connectivity for a
270:37 which provides secure connectivity for a large number of employees who work out
270:39 large number of employees who work out of a home office
270:48 an important topic when considering ccda certification
270:50 certification is the common categories within various
270:52 is the common categories within various wind technologies
270:53 wind technologies an essential concept is circuit switched
270:57 an essential concept is circuit switched technology
270:58 technology the most relevant example of this is the
271:01 the most relevant example of this is the pstn or public switch telephone network
271:04 pstn or public switch telephone network one of the technologies that falls under
271:06 one of the technologies that falls under this category is isdn
271:09 this category is isdn the way circuit switched wan connections
271:11 the way circuit switched wan connections function
271:12 function is by being established when needed and
271:15 is by being established when needed and terminated when they are no longer
271:17 terminated when they are no longer required
271:18 required another example that reflects the
271:20 another example that reflects the circuit switching behaviors is the
271:22 circuit switching behaviors is the old-fashioned dial-up connection
271:25 old-fashioned dial-up connection you may remember or maybe you don't
271:27 you may remember or maybe you don't using a dial-up modem analog access over
271:29 using a dial-up modem analog access over the pstn to access the internet
271:32 the pstn to access the internet in the late 1990s
271:35 in the late 1990s the opposite of circuit switched option
271:38 the opposite of circuit switched option is the least line technology
271:40 is the least line technology this is a fully dedicated connection
271:42 this is a fully dedicated connection that is permanently up and owned by the
271:44 that is permanently up and owned by the company
271:46 company examples of lease lines include
271:48 examples of lease lines include tdm or time division multiplexing based
271:52 tdm or time division multiplexing based leased lines
271:53 leased lines and these are usually very expensive
271:55 and these are usually very expensive because a single customer
271:57 because a single customer has full use of the offered connectivity
271:59 has full use of the offered connectivity and you're paying for that bandwidth
272:01 and you're paying for that bandwidth whether you're using it or not
272:05 whether you're using it or not another popular category of wide area
272:07 another popular category of wide area networking technology involves packet
272:09 networking technology involves packet switched concepts
272:11 switched concepts in a packet switch infrastructure
272:14 in a packet switch infrastructure shared bandwidth utilizes virtual
272:16 shared bandwidth utilizes virtual circuits the customer can create a
272:19 circuits the customer can create a virtual path which is similar to a
272:21 virtual path which is similar to a leased line
272:22 leased line through the service provider's
272:23 through the service provider's infrastructure cloud
272:25 infrastructure cloud this virtual circuit has a dedicated
272:27 this virtual circuit has a dedicated bandwidth even though technically it's
272:30 bandwidth even though technically it's not a real leased line
272:32 not a real leased line frame relay is an example of this type
272:34 frame relay is an example of this type of technology
272:36 of technology some legacy wand technologies you may
272:39 some legacy wand technologies you may have heard of such as x25 that's the
272:42 have heard of such as x25 that's the predecessor of frame relay
272:44 predecessor of frame relay an example of cell switch technology is
272:47 an example of cell switch technology is asynchronous transfer mode or atm
272:50 asynchronous transfer mode or atm this operates by using fixed sized cells
272:54 this operates by using fixed sized cells self-switch technologies form a shared
272:56 self-switch technologies form a shared bandwidth environment from the service
272:58 bandwidth environment from the service provider standpoint that can guarantee
273:00 provider standpoint that can guarantee customers some level of bandwidth
273:03 customers some level of bandwidth through their infrastructure
273:05 through their infrastructure broadband is another hugely growing
273:08 broadband is another hugely growing category for wide area networking and
273:10 category for wide area networking and this includes technologies such as dsl
273:13 this includes technologies such as dsl cable and wireless
273:15 cable and wireless broadband involves making a connection
273:17 broadband involves making a connection such as an old-fashioned coax cable that
273:19 such as an old-fashioned coax cable that carries tv signals and figuring out how
273:22 carries tv signals and figuring out how to use the different aspects of that
273:24 to use the different aspects of that bandwidth
273:25 bandwidth for example by using multiplexing an
273:28 for example by using multiplexing an additional data signal could be
273:30 additional data signal could be transmitted along with the original tv
273:32 transmitted along with the original tv signals
273:33 signals and obviously wireless continues to
273:35 and obviously wireless continues to expand at a rapid pace
273:42 as detailed so far there are many options when discussing when categories
273:46 options when discussing when categories all of these technologies can support
273:48 all of these technologies can support the needs of modern networks that
273:50 the needs of modern networks that operate under the 80 20 rule that is
273:53 operate under the 80 20 rule that is 80 of the network traffic
273:55 80 of the network traffic uses some kind of wan technology to
273:57 uses some kind of wan technology to access remote resources
274:01 access remote resources next let's talk about wand topologies
274:04 next let's talk about wand topologies there are three you should know of
274:06 there are three you should know of first let's talk about full mesh
274:08 first let's talk about full mesh topologies
274:10 topologies which for obvious reasons require a
274:12 which for obvious reasons require a large number of nodes and added extra
274:14 large number of nodes and added extra overhead
274:15 overhead referring back to the formula n times n
274:18 referring back to the formula n times n minus 1 divided by 2
274:20 minus 1 divided by 2 where n denotes the nodes
274:31 this obviously can get very expensive very fast
274:33 very fast that being said the full mesh topology
274:35 that being said the full mesh topology is the best option when considering
274:37 is the best option when considering availability and reliability failover
274:40 availability and reliability failover will occur on the other links and
274:42 will occur on the other links and devices assuming you have your routing
274:43 devices assuming you have your routing protocols
274:45 protocols programmed correctly
274:47 programmed correctly the downside of full mesh topology
274:49 the downside of full mesh topology obviously is the extra overhead
274:51 obviously is the extra overhead associated with building and maintaining
274:53 associated with building and maintaining all of the connections
274:55 all of the connections and the high costs required to install
274:57 and the high costs required to install all of the links
274:59 all of the links a more popular design is the hub and
275:02 a more popular design is the hub and spoke topology the hub router is usually
275:05 spoke topology the hub router is usually located at the headquarters location
275:08 located at the headquarters location and connects to branch office routers in
275:10 and connects to branch office routers in a hub and spoke fashion
275:14 a hub and spoke fashion the hub spoke topology is not the best
275:16 the hub spoke topology is not the best topology as far as redundancy and
275:18 topology as far as redundancy and availability are concerned
275:20 availability are concerned as the hub device is the most common
275:22 as the hub device is the most common point of failure
275:23 point of failure so obviously in the hub area you're
275:26 so obviously in the hub area you're going to want to have redundant systems
275:29 going to want to have redundant systems with redundant power supplies redundant
275:31 with redundant power supplies redundant route processors etc etc
275:35 route processors etc etc hub and spoke topologies are obviously
275:37 hub and spoke topologies are obviously less complex and less expensive than
275:40 less complex and less expensive than full mesh topologies so the added
275:42 full mesh topologies so the added investment in the hub site is well worth
275:45 investment in the hub site is well worth it
275:47 it next there's partial mesh this involves
275:50 next there's partial mesh this involves a combination of full mesh and hub and
275:52 a combination of full mesh and hub and spoke
275:54 spoke the partial mesh topology falls in the
275:57 the partial mesh topology falls in the middle of full mesh and hub and spoke
275:58 middle of full mesh and hub and spoke topologies in terms of availability and
276:01 topologies in terms of availability and costs
276:02 costs this topology is useful when a high
276:05 this topology is useful when a high level of availability and redundancy is
276:07 level of availability and redundancy is required only in some areas
276:14 so it's a good time to begin discussing network architecture types
276:16 network architecture types the first network architecture type is
276:18 the first network architecture type is point to point
276:20 point to point now this is rather self-explanatory as
276:23 now this is rather self-explanatory as you can see we have two network devices
276:25 you can see we have two network devices connected by a single network link
276:28 connected by a single network link the typical point-to-point connection is
276:30 the typical point-to-point connection is a serial link
276:32 a serial link the next architecture type is broadcast
276:34 the next architecture type is broadcast network
276:35 network a broadcast is sent from one of the
276:37 a broadcast is sent from one of the routers and then propagated to all other
276:39 routers and then propagated to all other routers on that segment
276:42 routers on that segment ethernet networks like the one you see
276:43 ethernet networks like the one you see below are common examples of a broadcast
276:46 below are common examples of a broadcast network
276:53 the next architecture type is nbma or non-broadcast
276:55 non-broadcast multi-access
276:56 multi-access as the name implies it does not support
276:59 as the name implies it does not support broadcasts therefore when an interface
277:02 broadcasts therefore when an interface on a router needs to send out data to
277:04 on a router needs to send out data to all other routers it must send
277:06 all other routers it must send individual messages to each router
277:09 individual messages to each router nbma
277:10 nbma also doesn't support multicast so here's
277:13 also doesn't support multicast so here's what you've learned you've learned about
277:15 what you've learned you've learned about the basics of when topologies and wide
277:19 the basics of when topologies and wide area network types all these things will
277:21 area network types all these things will help you
277:22 help you in laying this foundation you need as
277:24 in laying this foundation you need as you begin to learn about how to design
277:26 you begin to learn about how to design for wide area networks
277:28 for wide area networks laying a foundation for the terminology
277:31 laying a foundation for the terminology that you'll need to understand such as
277:33 that you'll need to understand such as hub and spoke
277:34 hub and spoke full mesh
277:36 full mesh but also as you begin to design wide
277:38 but also as you begin to design wide area networks or you're asked questions
277:40 area networks or you're asked questions about wide area networks in the ccda
277:41 about wide area networks in the ccda exam
277:43 exam this information is going to be in any
277:45 this information is going to be in any question you would receive
277:47 question you would receive because they're going to assume you
277:48 because they're going to assume you understand the topics that are covered
277:50 understand the topics that are covered in this video very well
277:53 in this video very well good luck in your studies
278:17 hi this is david voss cci11372 and in this video you're going
278:20 cci11372 and in this video you're going to learn about dial-up technology
278:24 to learn about dial-up technology we're going to do an overview of isdn
278:26 we're going to do an overview of isdn technology and then dig into some of the
278:28 technology and then dig into some of the details
278:30 details such as isdn bri and pri
278:33 such as isdn bri and pri so let's begin
278:35 so let's begin although dial-up technologies are not
278:37 although dial-up technologies are not very common in today's modern network
278:40 very common in today's modern network it is a topic you can expect to see on
278:42 it is a topic you can expect to see on the ccda certification
278:45 the ccda certification dial-up falls under the category of
278:47 dial-up falls under the category of circuit switching
278:49 circuit switching and it uses the public switch telephone
278:51 and it uses the public switch telephone network or pstn
278:54 network or pstn a connection is established when a user
278:56 a connection is established when a user wants to use the dial-up option
278:59 wants to use the dial-up option and the connection ends when the user is
279:01 and the connection ends when the user is done using the link
279:03 done using the link considering dial-up connections use an
279:05 considering dial-up connections use an analog signal users need to use a modem
279:08 analog signal users need to use a modem in order to take the digital signal from
279:10 in order to take the digital signal from the computer and then convert it into
279:13 the computer and then convert it into analog communication on the pstn and
279:16 analog communication on the pstn and vice versa
279:18 vice versa dial-up access offers very limited
279:20 dial-up access offers very limited bandwidth capabilities
279:22 bandwidth capabilities but its advantage is that it's available
279:24 but its advantage is that it's available just about everywhere
279:26 just about everywhere because obviously pstns span across
279:29 because obviously pstns span across almost every geographical location
279:32 almost every geographical location the technologies used over the pstn
279:35 the technologies used over the pstn should not utilize much bandwidth
279:37 should not utilize much bandwidth modern networks may use dial-up
279:39 modern networks may use dial-up technology as a backup connection that
279:42 technology as a backup connection that can be activated in an emergency when no
279:45 can be activated in an emergency when no other wan connection type is available
279:48 other wan connection type is available and this is one of the most popular uses
279:51 and this is one of the most popular uses of isdn or was in the past especially
279:54 of isdn or was in the past especially was as a backup connection should the
279:58 was as a backup connection should the wan connection fail
279:59 wan connection fail now isdn is a technology that allows
280:02 now isdn is a technology that allows digital communication over a traditional
280:04 digital communication over a traditional analog phone line so that both voice and
280:07 analog phone line so that both voice and data can be transmitted digitally over
280:10 data can be transmitted digitally over the pstn
280:12 the pstn isdn never reached the level of
280:13 isdn never reached the level of popularity it was expected to because it
280:16 popularity it was expected to because it emerged when alternate technologies were
280:19 emerged when alternate technologies were also being developed
280:21 also being developed the two flavors of isdn include isdn bri
280:26 the two flavors of isdn include isdn bri basic rate interface
280:28 basic rate interface and isdn pri primary rate interface
280:32 and isdn pri primary rate interface isdn bri connectivity contains two b
280:35 isdn bri connectivity contains two b bearer channels for carrying data in 1d
280:39 bearer channels for carrying data in 1d delta channel for signaling
280:41 delta channel for signaling and is abbreviated as 2b plus d
280:45 and is abbreviated as 2b plus d each of these bare channels in the isdn
280:48 each of these bare channels in the isdn operates at a speed of 64 kilobits per
280:51 operates at a speed of 64 kilobits per second
280:52 second multi-link ppp can be configured on top
280:55 multi-link ppp can be configured on top of these interfaces to allow the user to
280:58 of these interfaces to allow the user to reach a bandwidth total of 128 kilobits
281:01 reach a bandwidth total of 128 kilobits per second
281:02 per second this bandwidth is considered very low
281:05 this bandwidth is considered very low obviously
281:06 obviously according to modern network requirements
281:10 according to modern network requirements the delta channel in isd mbri is a
281:13 the delta channel in isd mbri is a dedicated 16 kilobit per second traffic
281:16 dedicated 16 kilobit per second traffic control
281:17 control there are also 48 kilobits per seconds
281:20 there are also 48 kilobits per seconds overall for framing control and other
281:23 overall for framing control and other overhead in the isdn environment
281:25 overhead in the isdn environment therefore the total isdn bandwidth for
281:27 therefore the total isdn bandwidth for pri
281:28 pri is 192 kilobits per second
281:31 is 192 kilobits per second 128 kilobits per second from the b
281:33 128 kilobits per second from the b channels plus 16 for the d channel plus
281:36 channels plus 16 for the d channel plus 48 of overhead
281:41 48 of overhead isdn pri has 23 b channels and 1d
281:45 isdn pri has 23 b channels and 1d channel
281:46 channel in the united states and japan
281:48 in the united states and japan the bare channels and the delta channels
281:51 the bare channels and the delta channels all support 64 kilobits per second
281:54 all support 64 kilobits per second including overhead
281:56 including overhead the total pri bandwidth is 1.544
281:59 the total pri bandwidth is 1.544 megabits per second
282:01 megabits per second in other parts of the world like europe
282:03 in other parts of the world like europe and australia the pr connection
282:06 and australia the pr connection is 30b channels and 1d channel and
282:09 is 30b channels and 1d channel and therefore you have more bandwidth as
282:11 therefore you have more bandwidth as well
282:12 well the isdn technologies we've been
282:14 the isdn technologies we've been describing are called tdm or time
282:17 describing are called tdm or time division multiplexing technologies
282:20 division multiplexing technologies tdm refers to being able to combine
282:22 tdm refers to being able to combine multiple channels
282:24 multiple channels over a single overall transmission
282:26 over a single overall transmission medium
282:27 medium and using these different channels for
282:29 and using these different channels for voice video and data
282:32 voice video and data time division refers to
282:34 time division refers to splitting the connection into small
282:36 splitting the connection into small windows of time for various
282:38 windows of time for various communication channels
282:41 communication channels isdn speaking devices are called
282:43 isdn speaking devices are called terminal emulation equipment and they
282:46 terminal emulation equipment and they can be categorized as either native isdn
282:49 can be categorized as either native isdn or non-native isdn equipment
282:52 or non-native isdn equipment native isdn equipment is comprised of
282:54 native isdn equipment is comprised of devices that were built to be isdn ready
282:57 devices that were built to be isdn ready and they are called te1 devices terminal
283:00 and they are called te1 devices terminal equipment one
283:02 equipment one non-native isdn equipment is comprised
283:05 non-native isdn equipment is comprised of te2 devices non-native isdn equipment
283:09 of te2 devices non-native isdn equipment can be integrated with native isdn
283:11 can be integrated with native isdn equipment by using a special ta or
283:14 equipment by using a special ta or terminal adapter
283:16 terminal adapter which only te2 devices require
283:20 which only te2 devices require the isdn service provider uses
283:22 the isdn service provider uses termination devices called
283:24 termination devices called nt1s or network termination 1 and nt2
283:27 nt1s or network termination 1 and nt2 network termination 2.
283:29 network termination 2. these are translation devices for media
283:33 these are translation devices for media transforming five wire connections
283:35 transforming five wire connections into two wire connections
283:38 into two wire connections the local loop is the two-wire
283:40 the local loop is the two-wire connection it's a two-wire link
283:42 connection it's a two-wire link for users in north america the customer
283:45 for users in north america the customer is responsible for the nt-1 device
283:47 is responsible for the nt-1 device while in other parts of the world this
283:49 while in other parts of the world this falls under the service provider's
283:51 falls under the service provider's responsibility
283:53 responsibility because of this issue some cisco routers
283:55 because of this issue some cisco routers provide built-in nt1 functionality that
283:58 provide built-in nt1 functionality that features a visible u under the port so
284:02 features a visible u under the port so the user can see this capability quickly
284:05 the user can see this capability quickly the u notation is found in the isdn
284:07 the u notation is found in the isdn reference point terminology these
284:10 reference point terminology these reference points are important for
284:12 reference points are important for troubleshooting or maintaining issues in
284:14 troubleshooting or maintaining issues in an isdn network
284:17 an isdn network the isdn switch is usually located at
284:19 the isdn switch is usually located at the service provider's location
284:23 the service provider's location the different isdn reference points are
284:25 the different isdn reference points are as follows
284:27 as follows the u reference point is between the
284:28 the u reference point is between the isdn switch
284:30 isdn switch and the nt1 device
284:32 and the nt1 device the t reference point is between the nt2
284:35 the t reference point is between the nt2 device and the nt1 device
284:38 device and the nt1 device the s reference point is between the
284:40 the s reference point is between the terminals te1 or
284:43 terminals te1 or the ta
284:44 the ta and the nt2 device
284:46 and the nt2 device the r reference point is between
284:48 the r reference point is between non-isdn native devices and tas
284:54 so here's what you've learned you've learned a basic overview of isdn
284:58 learned a basic overview of isdn you've gotten also granular enough
285:01 you've gotten also granular enough with learning about isdm bri
285:04 with learning about isdm bri and then pri and the different types of
285:06 and then pri and the different types of isdn equipment that you should be able
285:08 isdn equipment that you should be able to answer correctly any isdn related
285:11 to answer correctly any isdn related question on the ccda exam
285:14 question on the ccda exam i wish you the best of luck in your
285:15 i wish you the best of luck in your studies thank you
285:38 hi this is david voss ccie11372 and in this video you're going
285:40 ccie11372 and in this video you're going to learn about frame relay
285:43 to learn about frame relay in previous videos you learned about
285:45 in previous videos you learned about non-broadcast multi-access technologies
285:48 non-broadcast multi-access technologies well
285:49 well frame relay is a nbma technology and it
285:53 frame relay is a nbma technology and it requires
285:55 requires dealing with address resolution issues
285:58 dealing with address resolution issues except for situations in which
286:00 except for situations in which point-to-point interfaces are used
286:03 point-to-point interfaces are used the local layer 2 addresses in frame
286:06 the local layer 2 addresses in frame relay are called data link connection
286:08 relay are called data link connection identifiers or dulces
286:11 identifiers or dulces and they are only locally significant
286:14 and they are only locally significant so for example in a hub and spoke
286:16 so for example in a hub and spoke environment
286:17 environment the hub device should have a unique
286:20 the hub device should have a unique delcy to communicate to each of its
286:22 delcy to communicate to each of its spokes
286:23 spokes as you can see here
286:26 as you can see here the delcy number at the end of each link
286:28 the delcy number at the end of each link may or may not be identical
286:31 may or may not be identical the delci is the frame relay address so
286:33 the delci is the frame relay address so this needs to be resolved to a layer 3
286:35 this needs to be resolved to a layer 3 ip address
286:37 ip address another fundamental frame relay
286:39 another fundamental frame relay component is the lmi or local management
286:42 component is the lmi or local management interface
286:44 interface the service provider operates a dce
286:46 the service provider operates a dce frame relay device and this is usually a
286:48 frame relay device and this is usually a switch
286:49 switch and the customer provides a dte frame
286:53 and the customer provides a dte frame relay device and this is usually a
286:54 relay device and this is usually a router
286:56 router the lmi is a language that permits these
286:58 the lmi is a language that permits these two devices to communicate
287:00 two devices to communicate one of its duties is to report the
287:02 one of its duties is to report the status information of the virtual
287:05 status information of the virtual circuit that makes up the frame relay
287:07 circuit that makes up the frame relay communication
287:09 communication the lmi also provides the delci
287:11 the lmi also provides the delci information
287:13 information the lmi is enabled automatically when
287:15 the lmi is enabled automatically when frame relay is initiated
287:17 frame relay is initiated and when it's enabled on a cisco device
287:20 and when it's enabled on a cisco device interface
287:21 interface so when you inspect the frame relay pvc
287:24 so when you inspect the frame relay pvc or permanent virtual circuit on a cisco
287:27 or permanent virtual circuit on a cisco device you will see a status code
287:29 device you will see a status code defined by the lmi
287:31 defined by the lmi that there will be one of the following
287:33 that there will be one of the following active
287:34 active which is what you would hope for that
287:36 which is what you would hope for that everything is working correctly
287:38 everything is working correctly inactive which means there's no problems
287:41 inactive which means there's no problems on the local node but there are possible
287:43 on the local node but there are possible issues on the remote node and then
287:46 issues on the remote node and then deleted which means there is an issue on
287:48 deleted which means there is an issue on the service provider network
287:50 the service provider network the three types of lmi are cisco
287:54 the three types of lmi are cisco ansi
287:55 ansi and q933a
288:01 cisco routers are configured to try all of these lmi types automatically
288:03 of these lmi types automatically starting with the cisco lmi type
288:06 starting with the cisco lmi type and then uses the one that matches
288:08 and then uses the one that matches whatever the service provider is using
288:12 whatever the service provider is using so in this aspect should not be that
288:14 so in this aspect should not be that much of a concern in a design phase for
288:17 much of a concern in a design phase for frame relay
288:19 frame relay one of the most popular aspects that
288:21 one of the most popular aspects that must be considered in the divine pha
288:23 must be considered in the divine pha design phase is the address resolution
288:25 design phase is the address resolution methodology
288:27 methodology if you are using
288:29 if you are using multi-point interfaces in your design
288:32 multi-point interfaces in your design you need to find a way to provide the
288:35 you need to find a way to provide the layer 3 to layer 2 resolution
288:38 layer 3 to layer 2 resolution there are two options that can help you
288:40 there are two options that can help you achieve this
288:41 achieve this and you can do it dynamically
288:43 and you can do it dynamically as you can see here using inverse arp
288:46 as you can see here using inverse arp one router stating my ip address is 199
288:50 one router stating my ip address is 199 17 28 200
288:52 17 28 200 and then asking for the ip address of
288:54 and then asking for the ip address of router b
288:55 router b who then answers back
288:57 who then answers back or statically
288:59 or statically using the frame relay map command
289:03 using the frame relay map command and you can see the specific programming
289:05 and you can see the specific programming for that right here
289:09 for that right here in order to verify that layer 3 to layer
289:11 in order to verify that layer 3 to layer 2 resolution has succeeded use the show
289:15 2 resolution has succeeded use the show frame relay map command
289:17 frame relay map command on a multi-point interface inverse arp
289:19 on a multi-point interface inverse arp happens automatically
289:21 happens automatically this functionality is enabled right
289:23 this functionality is enabled right after adding an ip address on an
289:25 after adding an ip address on an interface configured for frame relay
289:28 interface configured for frame relay at that moment requests are sent out all
289:30 at that moment requests are sent out all the circuits assigned to that specific
289:32 the circuits assigned to that specific interface for any supporting protocol
289:35 interface for any supporting protocol the interface is running
289:38 the interface is running the request process can be disabled with
289:40 the request process can be disabled with the no frame relay inverse arp command
289:44 the no frame relay inverse arp command but you can never design a network that
289:45 but you can never design a network that will stop responding to requests
289:48 will stop responding to requests by design inverse arp replies cannot be
289:51 by design inverse arp replies cannot be disabled so the frame relay speaker will
289:53 disabled so the frame relay speaker will always attempt to assist anybody
289:56 always attempt to assist anybody who attempts to perform a layer 3
289:58 who attempts to perform a layer 3 to layer 2 resolution
290:00 to layer 2 resolution via frame relay inverse arp
290:03 via frame relay inverse arp the inverse art behavior in framework
290:05 the inverse art behavior in framework design assists automatically with
290:07 design assists automatically with broadcasts
290:08 broadcasts through the replicated unicast approach
290:11 through the replicated unicast approach discussed
290:12 discussed earlier
290:13 earlier therefore when using inverse our
290:15 therefore when using inverse our broadcast support exists by default
290:19 broadcast support exists by default when connecting two routers to the frame
290:20 when connecting two routers to the frame relay cloud using physical interfaces
290:24 relay cloud using physical interfaces the specific interfaces are multi-point
290:26 the specific interfaces are multi-point from a frame relay perspective
290:28 from a frame relay perspective because a physical frame relay interface
290:30 because a physical frame relay interface by default is multi-point
290:33 by default is multi-point therefore even though the connection
290:35 therefore even though the connection between the two routers appears as a
290:37 between the two routers appears as a point-to-point
290:38 point-to-point it is a formulate multi-point connection
290:42 it is a formulate multi-point connection because they are using multiple
290:44 because they are using multiple interfaces by default the two devices
290:46 interfaces by default the two devices will handle the layer three to layer two
290:48 will handle the layer three to layer two resolution dynamically
290:50 resolution dynamically using inverse arp
290:52 using inverse arp if you would like to design a solution
290:54 if you would like to design a solution that does not use infosharp then you can
290:56 that does not use infosharp then you can turn off the dynamic mapping behavior on
290:59 turn off the dynamic mapping behavior on each device
291:00 each device and then configure static frame relay
291:03 and then configure static frame relay mappings
291:04 mappings you can do so by entering in formulae
291:06 you can do so by entering in formulae map the protocol address to the dell c
291:10 map the protocol address to the dell c the protocol is usually the ip
291:13 the protocol is usually the ip address is the remote address
291:16 address is the remote address and the dell c represents the local id
291:19 and the dell c represents the local id the broadcast keyword can be added
291:21 the broadcast keyword can be added optionally in order to activate the
291:23 optionally in order to activate the replicated unicast behavior to support
291:26 replicated unicast behavior to support broadcast functionality
291:28 broadcast functionality static mapping must be configured in
291:30 static mapping must be configured in order to override or turn off the
291:33 order to override or turn off the the default dynamic inverse arp behavior
291:37 the default dynamic inverse arp behavior this helps the administrator maintain
291:39 this helps the administrator maintain full control over the layer 3 to layer 2
291:42 full control over the layer 3 to layer 2 resolution process in frame relay
291:45 resolution process in frame relay a huge error that can appear on cisco
291:47 a huge error that can appear on cisco equipment is that physical interfaces
291:50 equipment is that physical interfaces have come up an inverse arp starts to
291:53 have come up an inverse arp starts to operate
291:54 operate you can find that there are dynamic
291:56 you can find that there are dynamic mappings to
291:57 mappings to 0.0.0.0 these mappings occur
292:00 0.0.0.0 these mappings occur because of a clash of two features and
292:02 because of a clash of two features and that is inverse arp in cisco auto
292:04 that is inverse arp in cisco auto install
292:06 install to discard these mappings you issue a
292:08 to discard these mappings you issue a clear framerate in arp command
292:11 clear framerate in arp command and then the device should be restarted
292:14 and then the device should be restarted this mapping can create a failure in the
292:17 this mapping can create a failure in the communication path from framelay
292:20 communication path from framelay environment
292:21 environment point-to-point configurations are the
292:23 point-to-point configurations are the ideal choice when it comes to layer 3 to
292:26 ideal choice when it comes to layer 3 to layer 2 resolution
292:27 layer 2 resolution because the process and multi-point
292:29 because the process and multi-point configurations does not occur when such
292:32 configurations does not occur when such interface on such interface types
292:38 when configuring point-to-point frame relay use point-to-point sub-interfaces
292:41 relay use point-to-point sub-interfaces which will not get the delsi assignments
292:43 which will not get the delsi assignments from the lmi as in the multi-point
292:45 from the lmi as in the multi-point situation
292:46 situation the dlc must be assigned manually to the
292:49 the dlc must be assigned manually to the sub-interfaces with the frame relay
292:51 sub-interfaces with the frame relay interface delsi command
292:57 there is no concern about the layer 3 to layer 2 resolution because each router
292:59 layer 2 resolution because each router has only one remote device to which it
293:01 has only one remote device to which it sends data and it does this by using the
293:03 sends data and it does this by using the sub interface
293:05 sub interface associated with the delsi
293:07 associated with the delsi another option would be creating sub
293:08 another option would be creating sub interfaces and declaring them as
293:11 interfaces and declaring them as multi-point
293:12 multi-point these types of interfaces behave exactly
293:15 these types of interfaces behave exactly like the physical multiple interfaces
293:18 like the physical multiple interfaces but you need to decide on the resolution
293:20 but you need to decide on the resolution method to be used
293:22 method to be used inverse arp or static mappings
293:24 inverse arp or static mappings a combination of these can be used for
293:27 a combination of these can be used for example by implementing inverse arp on
293:29 example by implementing inverse arp on one end of the connection
293:31 one end of the connection and then defining static maps on the
293:34 and then defining static maps on the other end
293:36 other end the interface type settings and the
293:38 the interface type settings and the selected layer 3 to layer 2 resolution
293:40 selected layer 3 to layer 2 resolution method
293:41 method is only locally significant so this
293:43 is only locally significant so this means there can be all kinds of
293:45 means there can be all kinds of variations in your frame relay design
293:53 with frame relay environments for quality of service packets can be marked
293:55 quality of service packets can be marked with the d e bit and this informs a
293:58 with the d e bit and this informs a service provider that those specific
294:00 service provider that those specific packets are not that important and can
294:03 packets are not that important and can be discarded if there is congestion
294:06 be discarded if there is congestion this behavior will prioritize packets
294:08 this behavior will prioritize packets that do not have the de bit set
294:11 that do not have the de bit set other parameters that can be configured
294:13 other parameters that can be configured in the frame relay environment are
294:15 in the frame relay environment are feckin and beckons so
294:18 feckin and beckons so feckins are forward explicit congestion
294:20 feckins are forward explicit congestion notifications beckons are backward
294:23 notifications beckons are backward explicit congestion notifications
294:26 explicit congestion notifications the frame relay equipment if configured
294:29 the frame relay equipment if configured to do so can notify deficit devices of
294:31 to do so can notify deficit devices of congestion
294:32 congestion and slow down the sending rates as
294:35 and slow down the sending rates as illustrated here
294:38 illustrated here in summary if you have a chain of frame
294:40 in summary if you have a chain of frame relay nodes that supports feckins and
294:42 relay nodes that supports feckins and beckons
294:43 beckons the first device can forward a feckin
294:46 the first device can forward a feckin that informs about existing congestion
294:49 that informs about existing congestion and about the need for transmitting at a
294:51 and about the need for transmitting at a slower rate
294:52 slower rate the feckin marking is then moved
294:54 the feckin marking is then moved backward but this can cause problems
294:56 backward but this can cause problems when there is no return traffic sent
294:58 when there is no return traffic sent backwards
294:59 backwards to make sure everybody knows about the
295:01 to make sure everybody knows about the congestion use beckons with empty frames
295:03 congestion use beckons with empty frames that carry the beckon bit backward
295:06 that carry the beckon bit backward this notifies the return path about the
295:08 this notifies the return path about the congestion
295:09 congestion devices respond to seconds and beckons
295:11 devices respond to seconds and beckons by slowing down in terms of transmission
295:14 by slowing down in terms of transmission rates in order to
295:16 rates in order to to avoid further congestion
295:19 to avoid further congestion so here's what you've learned you've
295:20 so here's what you've learned you've learned about the basics of frame relay
295:23 learned about the basics of frame relay d e beckon and feckin and then the
295:25 d e beckon and feckin and then the different types of interfaces and also
295:27 different types of interfaces and also the design considerations you need to
295:29 the design considerations you need to think about when you're designing frame
295:32 think about when you're designing frame relay
295:33 relay it's a very important topic although
295:35 it's a very important topic although frame relay certainly is not as as
295:38 frame relay certainly is not as as popular as it once was it is still
295:40 popular as it once was it is still something you need to understand for
295:42 something you need to understand for your ccda exam
295:44 your ccda exam good luck in your studies
296:08 hi this is david voss ccie 1137 and in this video you're going to learn about
296:09 this video you're going to learn about mpls
296:11 mpls mpls
296:13 mpls leverages the intelligence of the ip
296:16 leverages the intelligence of the ip routing infrastructure and the
296:17 routing infrastructure and the efficiency of cisco express forwarding
296:21 efficiency of cisco express forwarding mpls functions by appending a level to
296:24 mpls functions by appending a level to any type of packet
296:26 any type of packet the packet will then be forwarded
296:27 the packet will then be forwarded through the network infrastructure based
296:29 through the network infrastructure based on this label's value
296:31 on this label's value instead of any layer 3 information
296:35 instead of any layer 3 information the ability to label a packet for
296:37 the ability to label a packet for efficient forwarding allows mpls to work
296:40 efficient forwarding allows mpls to work with a wide range of underlying
296:42 with a wide range of underlying technologies
296:44 technologies by simply adding a label to the packet
296:46 by simply adding a label to the packet header
296:47 header mpls can be used in many physical in
296:50 mpls can be used in many physical in data link
296:51 data link layer when implementation
296:54 layer when implementation the mpls label is positioned between the
296:57 the mpls label is positioned between the layer 2 header
296:58 layer 2 header and the layer 3 header
297:00 and the layer 3 header in mpls overhead is added a single time
297:04 in mpls overhead is added a single time when the packet goes into the service
297:06 when the packet goes into the service provider cloud
297:08 provider cloud after entering the mpls network packet
297:10 after entering the mpls network packet switching is performed much faster than
297:13 switching is performed much faster than in traditional layer 3 networks
297:15 in traditional layer 3 networks because it only needs to swap the mpls
297:17 because it only needs to swap the mpls label instead of stripping the entire
297:19 label instead of stripping the entire layer 3 header
297:22 layer 3 header mpls capable routers are also called
297:25 mpls capable routers are also called lsrs or label switch routers
297:28 lsrs or label switch routers and they will come in the following two
297:30 and they will come in the following two flavors edge lsr which is the pe router
297:35 flavors edge lsr which is the pe router or lsr the p router
297:39 or lsr the p router pe routers are provider edge devices
297:42 pe routers are provider edge devices that ensure label distribution the
297:44 that ensure label distribution the forward packets based on labels and are
297:46 forward packets based on labels and are responsible for label insertion and
297:49 responsible for label insertion and removal p routers are provider routers
297:51 removal p routers are provider routers and they are responsible for label
297:53 and they are responsible for label forwarding and efficient packet
297:55 forwarding and efficient packet forwarding based on labels
297:58 forwarding based on labels mpls separates the control plane from
298:01 mpls separates the control plane from the data plane
298:03 the data plane this leads to a great efficiency in how
298:05 this leads to a great efficiency in how the lsr routers work
298:08 the lsr routers work resources that are constructed for
298:10 resources that are constructed for efficient control plane operations
298:13 efficient control plane operations include the routing protocol
298:15 include the routing protocol the routing table
298:16 the routing table the exchange of labels
298:18 the exchange of labels and these are completely separated from
298:20 and these are completely separated from resources that are designed only to
298:22 resources that are designed only to forward traffic in the data plane as
298:24 forward traffic in the data plane as quickly as possible
298:31 contains a fib or forwarding information base that is a copy of the routing table
298:34 base that is a copy of the routing table information
298:35 information in the cache memory
298:37 in the cache memory and is used for quick forwarding
298:40 and is used for quick forwarding mpls contains a label forwarding
298:42 mpls contains a label forwarding information base lfib
298:45 information base lfib which is for label based traffic
298:47 which is for label based traffic exchange
298:49 exchange the term forwarding equivalence class
298:52 the term forwarding equivalence class describes a class of packets
298:54 describes a class of packets that receives the same forwarding
298:56 that receives the same forwarding treatment that is traffic forwarded
298:59 treatment that is traffic forwarded based on a specific quality of service
299:01 based on a specific quality of service marking through the service provider
299:03 marking through the service provider cloud
299:05 cloud the mpls label has a length of four
299:07 the mpls label has a length of four bytes and it is consists of the
299:09 bytes and it is consists of the following fields
299:11 following fields a 20-bit label value field
299:14 a 20-bit label value field 3-bit experimental field such as qos
299:17 3-bit experimental field such as qos marking
299:18 marking one-bit bottom of the stack field which
299:21 one-bit bottom of the stack field which can be used when multiple labels are
299:23 can be used when multiple labels are used it's set to 1 for the last label in
299:26 used it's set to 1 for the last label in the stack
299:27 the stack and then the 8-bit ttl field this helps
299:30 and then the 8-bit ttl field this helps you to avoid loops
299:32 you to avoid loops you might need to use a stack of labels
299:34 you might need to use a stack of labels when dealing with mpls
299:37 when dealing with mpls and pls vpn is the most important
299:39 and pls vpn is the most important technology that uses mpls
299:42 technology that uses mpls which was developed to serve the mpls
299:44 which was developed to serve the mpls vpn technology
299:46 vpn technology an example of an mpls vpn application
299:49 an example of an mpls vpn application would be an isp that offers mpls vpn
299:52 would be an isp that offers mpls vpn services
299:53 services the pe routers connect to different
299:55 the pe routers connect to different customers
299:56 customers with the same customer having multiple
299:58 with the same customer having multiple sites
299:59 sites each connected to a different pe router
300:02 each connected to a different pe router with the mpls approach two sites with
300:04 with the mpls approach two sites with the same customer receive transparent
300:07 the same customer receive transparent secure communication capabilities
300:10 secure communication capabilities based on the unique customer labels
300:11 based on the unique customer labels assigned
300:13 assigned the isp uses mpls to carry the traffic
300:16 the isp uses mpls to carry the traffic between the pe routers
300:18 between the pe routers through the p devices
300:21 through the p devices an important advantage of mpos vpn
300:23 an important advantage of mpos vpn technology is that its secure
300:25 technology is that its secure connectivity
300:26 connectivity is assured without the customer having
300:28 is assured without the customer having to run mpls on any device
300:31 to run mpls on any device the customer only needs to run a
300:33 the customer only needs to run a standard routing protocol with the isp
300:36 standard routing protocol with the isp because all the mpls vpn logic is
300:39 because all the mpls vpn logic is located in the isp cloud
300:42 located in the isp cloud when using mpls vpns a stack of labels
300:45 when using mpls vpns a stack of labels is used to identify the customer this is
300:48 is used to identify the customer this is the vpn identification
300:50 the vpn identification and another label is used to initiate
300:52 and another label is used to initiate the forwarding through the isp cloud
300:56 the forwarding through the isp cloud layer 3 mpls vpn technology is very
300:58 layer 3 mpls vpn technology is very powerful
301:00 powerful and a flexible option that allows
301:01 and a flexible option that allows service providers to give customers the
301:04 service providers to give customers the transparent when access connect
301:06 transparent when access connect connectivity they need
301:08 connectivity they need this is very scalable for the isp
301:11 this is very scalable for the isp because it is very easy for them to add
301:13 because it is very easy for them to add customers and sites
301:15 customers and sites mpls comes in the following two flavors
301:18 mpls comes in the following two flavors frame mode mpls and cell mode mpls
301:27 frame mode mpls is the most popular mpls type
301:28 type and in this scenario the label is placed
301:30 and in this scenario the label is placed between the layer 2 header
301:32 between the layer 2 header and the layer 3 header
301:34 and the layer 3 header this is why mpls is often considered a
301:36 this is why mpls is often considered a layer 2.5 technology
301:40 layer 2.5 technology cell mode mpls is used in atm networks
301:43 cell mode mpls is used in atm networks and uses fields in the atm header that
301:45 and uses fields in the atm header that are used as the label
301:48 are used as the label one important issue that must be solved
301:50 one important issue that must be solved with mpls is determining the devices
301:52 with mpls is determining the devices that will ensure the insertion
301:54 that will ensure the insertion and removal of labels
301:56 and removal of labels the creation of labels
301:58 the creation of labels is performed on the ingress edge lsr and
302:02 is performed on the ingress edge lsr and label removing
302:03 label removing is performed on the egress edge lsr
302:07 is performed on the egress edge lsr the lsrs in the interior of the mpls
302:10 the lsrs in the interior of the mpls topology are only responsible for label
302:13 topology are only responsible for label swapping
302:14 swapping in order to forward the traffic on a
302:16 in order to forward the traffic on a specific path
302:18 specific path the mpls devices need a way in which to
302:21 the mpls devices need a way in which to exchange the labels that will be
302:23 exchange the labels that will be utilized for making forwarding decisions
302:26 utilized for making forwarding decisions this label exchange process is executed
302:29 this label exchange process is executed using a protocol
302:31 using a protocol the most popular of these protocols is
302:34 the most popular of these protocols is ldp or label distribution protocol ldp
302:37 ldp or label distribution protocol ldp is a session based udp technology
302:40 is a session based udp technology that allows for the exchange of labels
302:43 that allows for the exchange of labels udp and multicast are used initially to
302:46 udp and multicast are used initially to set up the peering and then tcp ensures
302:49 set up the peering and then tcp ensures there is a reliable transmission on the
302:51 there is a reliable transmission on the label information
302:53 label information a technology that improves mpls
302:55 a technology that improves mpls efficiency is penultimate hot popping
302:59 efficiency is penultimate hot popping this allows for the second to last lsr
303:02 this allows for the second to last lsr in the mpls path
303:04 in the mpls path to be the one that pops out the label
303:06 to be the one that pops out the label this adds efficiency to the overall
303:09 this adds efficiency to the overall operation of mpls
303:12 operation of mpls the rd or route distinguisher is a way
303:15 the rd or route distinguisher is a way in which the isp can distinguish between
303:17 in which the isp can distinguish between the traffic of different customers
303:20 the traffic of different customers this allows different customers who are
303:22 this allows different customers who are participating in the mpls vpn to use the
303:25 participating in the mpls vpn to use the exact same ip address space
303:27 exact same ip address space for example you can have both customer a
303:29 for example you can have both customer a and customer b
303:31 and customer b using the 10.10.100.0
303:37 24 range with the traffic being differentiated between customer rds
303:41 differentiated between customer rds devices can create their own virtual
303:43 devices can create their own virtual routing tables called vpn routing and
303:45 routing tables called vpn routing and forwarding or vrfs
303:47 forwarding or vrfs so a pe router can store each customer's
303:50 so a pe router can store each customer's specific data in a separate and isolated
303:53 specific data in a separate and isolated table
303:54 table providing increased security
303:57 providing increased security prefixes are carried through the mpls
304:00 prefixes are carried through the mpls cloud by relying on m
304:02 cloud by relying on m p
304:03 p bgp
304:04 bgp or multi-protocol bgp
304:07 or multi-protocol bgp this carries the vpn version 4 prefixes
304:11 this carries the vpn version 4 prefixes the prefix that results after the rd is
304:13 the prefix that results after the rd is prepended to the normal prefix
304:16 prepended to the normal prefix you can filter customers access to each
304:19 you can filter customers access to each other's prefixes with import and export
304:22 other's prefixes with import and export targets
304:24 targets so in this video you've learned the
304:25 so in this video you've learned the basics about mpls
304:28 basics about mpls and how to design it
304:30 and how to design it these are the basics you'll need to know
304:32 these are the basics you'll need to know for your ccda exam and i'm confident if
304:35 for your ccda exam and i'm confident if you've mastered the topics in this mpls
304:37 you've mastered the topics in this mpls video you will do well on the mpls
304:40 video you will do well on the mpls questions in your ccda exam good luck in
304:44 questions in your ccda exam good luck in your studies
305:08 hi this is david voss cciu11372 and in this video we are covering land
305:10 and in this video we are covering land design considerations
305:12 design considerations we're going to talk about at a granular
305:14 we're going to talk about at a granular level things you need to consider when
305:16 level things you need to consider when designing a wide area network
305:19 designing a wide area network also we'll do a refresh of a few items
305:22 also we'll do a refresh of a few items that you'll need to remember in order to
305:25 that you'll need to remember in order to best understand the material that's
305:27 best understand the material that's presented in this video
305:32 it's important to know this information not only to be a strong engineer but
305:34 not only to be a strong engineer but obviously to pass the ccda exam
305:37 obviously to pass the ccda exam so let's begin
305:39 so let's begin now for your ccda exam
305:41 now for your ccda exam you must be aware that the enterprise
305:43 you must be aware that the enterprise edge design process
305:45 edge design process must follow the ppd io
305:48 must follow the ppd io process which is prepare plan design
305:52 process which is prepare plan design implement operate and optimize
305:55 implement operate and optimize the designer should carefully analyze
305:57 the designer should carefully analyze the following network requirements using
306:00 the following network requirements using this methodology
306:01 this methodology the types of applications and their when
306:03 the types of applications and their when requirements
306:05 requirements traffic volume
306:06 traffic volume and traffic patterns including possible
306:09 and traffic patterns including possible points of congestion
306:11 points of congestion let's do a quick refresh of the
306:14 let's do a quick refresh of the ppd-io
306:15 ppd-io methodology
306:17 methodology cisco has formalized a network's life
306:20 cisco has formalized a network's life cycle into six phases
306:23 cycle into six phases plan
306:25 plan design
306:26 design implement
306:27 implement operate and optimize
306:30 operate and optimize and these phases are collectively known
306:32 and these phases are collectively known as ppdio
306:34 as ppdio let's discuss the ppdio phases in detail
306:39 let's discuss the ppdio phases in detail first the prepare phase
306:41 first the prepare phase this phase establishes organization and
306:44 this phase establishes organization and business requirements
306:46 business requirements develops a network strategy and proposes
306:48 develops a network strategy and proposes a high level conceptual architecture to
306:52 a high level conceptual architecture to support that strategy
306:54 support that strategy technologies that support the
306:56 technologies that support the architecture are identified in this
306:58 architecture are identified in this phase
307:00 phase as well as a business case to establish
307:03 as well as a business case to establish the financial justification for the
307:05 the financial justification for the strategy
307:08 strategy the plan phase identifies the network
307:10 the plan phase identifies the network requirements based on goals facilities
307:12 requirements based on goals facilities and user needs
307:14 and user needs this phase characterizes sites and
307:16 this phase characterizes sites and assesses the network
307:18 assesses the network performs a gap analysis against best
307:20 performs a gap analysis against best practice architectures
307:22 practice architectures and looks at the operational environment
307:26 and looks at the operational environment in the design phase the network design
307:28 in the design phase the network design is developed based on the technical and
307:30 is developed based on the technical and business requirements
307:32 business requirements obtained from the previous phases
307:35 obtained from the previous phases a good design will provide high
307:37 a good design will provide high availability reliability security
307:40 availability reliability security scalability and performance
307:43 scalability and performance in the implement phase new equipment is
307:45 in the implement phase new equipment is installed and configured according to
307:48 installed and configured according to the design specifications
307:51 the design specifications in this phase any planned network
307:53 in this phase any planned network changes should be communicated in change
307:55 changes should be communicated in change control meetings and with the necessary
307:58 control meetings and with the necessary approvals to proceed
308:01 approvals to proceed the operate phase maintains the
308:03 the operate phase maintains the network's day-to-day operational health
308:07 network's day-to-day operational health operations include managing
308:09 operations include managing and monitoring network components
308:11 and monitoring network components and performing the appropriate
308:13 and performing the appropriate maintenances
308:15 maintenances and then finally the optimize phase
308:18 and then finally the optimize phase which involves proactive network
308:20 which involves proactive network management
308:21 management by identifying and resolving issues
308:24 by identifying and resolving issues before they affect the network
308:30 now there is a design methodology for the first three phases of the ppdio
308:33 the first three phases of the ppdio methodology
308:34 methodology and there are three steps to it
308:36 and there are three steps to it in step one
308:38 in step one decision makers identify the
308:40 decision makers identify the requirements and a conceptual
308:41 requirements and a conceptual architecture is proposed
308:45 architecture is proposed in step two the network is assessed
308:48 in step two the network is assessed the network is assessed on function
308:50 the network is assessed on function performance and quality
308:54 performance and quality and then in step three
308:55 and then in step three the network topology is designed
308:58 the network topology is designed to meet the requirements
309:00 to meet the requirements and close the network gaps identified in
309:03 and close the network gaps identified in the previous two steps
309:05 the previous two steps let's review these three phases in
309:07 let's review these three phases in detail
309:08 detail to obtain customer requirements
309:11 to obtain customer requirements you need not only to talk to network
309:12 you need not only to talk to network engineers but you need to talk to the
309:14 engineers but you need to talk to the business
309:16 business personnel and company managers
309:19 personnel and company managers networks are designed to support
309:20 networks are designed to support applications
309:22 applications and you want to determine the network
309:24 and you want to determine the network services that you need to support
309:26 services that you need to support both now
309:27 both now and in the future
309:29 and in the future so an example of design flexibility is
309:32 so an example of design flexibility is voip
309:33 voip considering the strict requirements of
309:35 considering the strict requirements of this technology you want to make sure
309:36 this technology you want to make sure that voip can function over the design
309:39 that voip can function over the design solution at any given time
309:41 solution at any given time even if this is not an initial
309:43 even if this is not an initial requirement from the customer
309:45 requirement from the customer but maybe a year or two or possibly even
309:48 but maybe a year or two or possibly even three years later
309:50 three years later you will want to be able to support
309:52 you will want to be able to support voice over ip
309:54 voice over ip flexibility in enterprise edge design
309:57 flexibility in enterprise edge design consists of the ability to incorporate
309:59 consists of the ability to incorporate other technologies easily at any given
310:02 other technologies easily at any given time
310:04 time other key design criteria when
310:06 other key design criteria when considering wan design include the
310:08 considering wan design include the following
310:09 following response time throughput
310:12 response time throughput reliability
310:13 reliability window size and data compression
310:17 window size and data compression response times are of great importance
310:19 response times are of great importance to the wide area network as well as to
310:21 to the wide area network as well as to its supported applications
310:23 its supported applications many modern applications will give an
310:25 many modern applications will give an indication of the necessary response
310:28 indication of the necessary response times and again voip is an excellent
310:30 times and again voip is an excellent example
310:31 example when a voip call is made over many
310:34 when a voip call is made over many network devices you should know what the
310:36 network devices you should know what the necessary response time must be
310:38 necessary response time must be for proper voice communications
310:41 for proper voice communications generally speaking one-way latency
310:43 generally speaking one-way latency should not exceed 120 milliseconds
310:47 should not exceed 120 milliseconds you can test a response time using a
310:49 you can test a response time using a feature on cisco devices called ipsla
310:53 feature on cisco devices called ipsla let's do a quick overview of ipsla for
310:56 let's do a quick overview of ipsla for you ipsla allows you to monitor analyze
310:59 you ipsla allows you to monitor analyze and verify
311:00 and verify ip service levels
311:02 ip service levels it's comprised of two components a
311:04 it's comprised of two components a source and a target
311:06 source and a target operations can broadly be categorized
311:08 operations can broadly be categorized into five functional areas
311:11 into five functional areas let's take a look at an example
311:24 you can use ipslas to monitor the performance between any area in the
311:26 performance between any area in the network core distribution and edge
311:29 network core distribution and edge without deploying a physical probe it
311:32 without deploying a physical probe it uses generated traffic to measure
311:34 uses generated traffic to measure network performance between two
311:35 network performance between two networking devices
311:37 networking devices so as we draw this out this shows how
311:39 so as we draw this out this shows how ipslas begins when the source device
311:42 ipslas begins when the source device sends a generated packet to the
311:43 sends a generated packet to the destination device
311:45 destination device after the destination device receives
311:47 after the destination device receives the packet depending on the type of
311:49 the packet depending on the type of ipsla's operation it responds with the
311:52 ipsla's operation it responds with the timestamp information for the source to
311:54 timestamp information for the source to make the calculation on performance
311:56 make the calculation on performance metrics
312:01 it then can communicate with a performance management application via
312:03 performance management application via snmp to provide real-time analysis of
312:06 snmp to provide real-time analysis of the network
312:16 it should be noticed that ipsla can communicate with any ip device on the
312:19 communicate with any ip device on the network that's enabled for these types
312:21 network that's enabled for these types of measurements
312:27 another important design parameter is overall available bandwidth or what many
312:30 overall available bandwidth or what many call throughput
312:32 call throughput this measures the amount of data that
312:33 this measures the amount of data that can be sent in a particular time frame
312:35 can be sent in a particular time frame through a special specific wan area
312:43 reliability is another aspect to consider this gives information about
312:45 consider this gives information about the health of the wan connection and its
312:47 the health of the wan connection and its resources so whether this connection is
312:50 resources so whether this connection is actually up or down
312:52 actually up or down as well as detailed information about
312:54 as well as detailed information about how often the wind functions as
312:56 how often the wind functions as efficient as efficiently as possible
313:03 window size influences the amount of data that can be sent into the wan in
313:05 data that can be sent into the wan in one chunk
313:06 one chunk tcp uses a sliding window concept that
313:09 tcp uses a sliding window concept that works by sending an amount of data
313:12 works by sending an amount of data waiting for an acknowledgement of
313:13 waiting for an acknowledgement of receipt and then increasing the amount
313:15 receipt and then increasing the amount of data until it reaches the maximum
313:17 of data until it reaches the maximum window
313:18 window in the case of a congested wan link
313:21 in the case of a congested wan link everyone in the network that is sending
313:23 everyone in the network that is sending data via tcp will start increasing the
313:25 data via tcp will start increasing the rate at which they send until the
313:27 rate at which they send until the interface starts dropping packets
313:30 interface starts dropping packets causing everyone to back off and use the
313:32 causing everyone to back off and use the sliding window
313:34 sliding window after the congestion disappears everyone
313:36 after the congestion disappears everyone will start increasing the rate at which
313:38 will start increasing the rate at which they send at the same time until a new
313:40 they send at the same time until a new congestion event occurs
313:43 congestion event occurs this process which repeats again and
313:45 this process which repeats again and again is called tcp global
313:47 again is called tcp global synchronization
313:48 synchronization this leads to a waste and bandwidth
313:50 this leads to a waste and bandwidth during the periods that all hosts
313:52 during the periods that all hosts decrease their window size
313:54 decrease their window size simultaneously
313:56 simultaneously and finally another key wan factor is
313:59 and finally another key wan factor is whether traffic can be compressed
314:02 whether traffic can be compressed if the data is already highly compressed
314:05 if the data is already highly compressed any additional compression mechanisms
314:07 any additional compression mechanisms are inefficient
314:09 are inefficient but that being said especially today
314:12 but that being said especially today with sands on other high capacity
314:15 with sands on other high capacity systems
314:17 systems compression and compression over the
314:18 compression and compression over the wind is critical to ensure
314:21 wind is critical to ensure that failover and backup services are
314:24 that failover and backup services are ready to go live with the most accurate
314:27 ready to go live with the most accurate data possible
314:29 data possible so here's what you've learned you've
314:30 so here's what you've learned you've learned about some unique land design
314:32 learned about some unique land design methodologies specifically a refresh of
314:34 methodologies specifically a refresh of the ppd-io process
314:37 the ppd-io process and then reviewing the key design
314:39 and then reviewing the key design criteria
314:40 criteria of wan design such as response time
314:43 of wan design such as response time throughput and reliability
314:45 throughput and reliability then another refresh of ipsla
314:49 then another refresh of ipsla all of this information is fair game for
314:51 all of this information is fair game for the ccda exam
314:53 the ccda exam if you know the information in this
314:55 if you know the information in this video well
314:56 video well you will do excellent on this portion of
314:59 you will do excellent on this portion of your exam
315:00 your exam good luck in your studies
315:26 hi this is david voss ccie11372 and in this video you're going to learn
315:28 and in this video you're going to learn about designing
315:30 about designing quality of service
315:32 quality of service specifically we're going to be going
315:34 specifically we're going to be going over the following categories of quality
315:37 over the following categories of quality of service classification
315:39 of service classification congestion management
315:42 congestion management link efficiency mechanisms and then
315:44 link efficiency mechanisms and then traffic shaping and policing
315:47 traffic shaping and policing now it's obvious from the ccda study
315:49 now it's obvious from the ccda study materials that cisco does not expect you
315:52 materials that cisco does not expect you to be an expert on quality of service
315:54 to be an expert on quality of service it is a huge topic
315:56 it is a huge topic they just want you to understand the
315:58 they just want you to understand the basics so do not spend too much time
316:01 basics so do not spend too much time digging into the intricacies of quality
316:03 digging into the intricacies of quality of service
316:04 of service because there will be time for that in
316:06 because there will be time for that in your advanced studies
316:08 your advanced studies for now
316:09 for now let's talk about quality of service at a
316:11 let's talk about quality of service at a higher level
316:13 higher level and then discuss the quality of service
316:15 and then discuss the quality of service concepts
316:16 concepts that cisco wants you to know for the
316:18 that cisco wants you to know for the ccda exam
316:22 ccda exam quality of service is a tool for
316:24 quality of service is a tool for managing a wins available bandwidth
316:27 managing a wins available bandwidth now quality service does not and bad ad
316:30 now quality service does not and bad ad bandwidth
316:31 bandwidth but it helps you make better use of what
316:33 but it helps you make better use of what you have
316:35 you have if you have chronic congestion issues
316:39 if you have chronic congestion issues quality of service should not be the
316:40 quality of service should not be the primary answer to resolving that problem
316:44 primary answer to resolving that problem you need to add more bandwidth
316:47 you need to add more bandwidth however
316:48 however by prioritizing traffic using quality of
316:51 by prioritizing traffic using quality of service
316:52 service you can make sure that your most
316:54 you can make sure that your most critical traffic gets the best treatment
316:57 critical traffic gets the best treatment and available bandwidth in times of
316:59 and available bandwidth in times of congestion
317:01 congestion one popular quality of service technique
317:03 one popular quality of service technique is to classify your traffic
317:06 is to classify your traffic based on a specific protocol type
317:08 based on a specific protocol type or matching access list
317:11 or matching access list and then giving a policy treatment to
317:13 and then giving a policy treatment to that specific class
317:15 that specific class you can define many classes to match or
317:18 you can define many classes to match or identify your most important traffic
317:20 identify your most important traffic classes for example video or voice
317:24 classes for example video or voice and then the remaining unmatched traffic
317:26 and then the remaining unmatched traffic then uses a default class
317:28 then uses a default class which is the traffic that can be treated
317:30 which is the traffic that can be treated as best effort
317:33 as best effort so let's begin with
317:34 so let's begin with classification for a flow to have
317:36 classification for a flow to have priority it must first be identified and
317:39 priority it must first be identified and marked
317:40 marked both of these tasks are referred to as
317:42 both of these tasks are referred to as classification
317:45 classification the following are popular technologies
317:47 the following are popular technologies which support
317:48 which support classification nbar
317:51 classification nbar it's a technology that uses deep
317:54 it's a technology that uses deep packet content inspection
317:56 packet content inspection to identify network applications
317:59 to identify network applications so an advantage of nbar is that it can
318:01 so an advantage of nbar is that it can recognize applications even when they do
318:03 recognize applications even when they do not
318:04 not use standard network ports
318:07 use standard network ports also it matches fields at the
318:09 also it matches fields at the application layer
318:12 application layer before nbar classification was limited
318:14 before nbar classification was limited to
318:15 to layer 4 tcp and udp port numbers
318:19 layer 4 tcp and udp port numbers but mbar has changed that
318:22 but mbar has changed that next is car committed access rate and
318:24 next is car committed access rate and uses an acl to set precedence and allows
318:27 uses an acl to set precedence and allows customization
318:29 customization of the precedence assignment by the user
318:32 of the precedence assignment by the user source or destination ip address or even
318:35 source or destination ip address or even application type
318:43 next let's talk about congestion management there are two types of output
318:45 management there are two types of output cues that are available on routers
318:47 cues that are available on routers hardware and software the hardware queue
318:50 hardware and software the hardware queue simply uses fifo first in first out
318:53 simply uses fifo first in first out but the software queue schedules packets
318:56 but the software queue schedules packets first and then places them in the
318:58 first and then places them in the hardware queue
319:00 hardware queue now keep in mind that the software queue
319:02 now keep in mind that the software queue is only used during periods of
319:04 is only used during periods of congestion
319:05 congestion the software queue uses quality of
319:07 the software queue uses quality of service techniques such as priority
319:09 service techniques such as priority queuing custom cueing
319:11 queuing custom cueing weighted fair queueing
319:12 weighted fair queueing class based weighted fair queuing
319:15 class based weighted fair queuing low latency queuing and traffic shaping
319:17 low latency queuing and traffic shaping and policing let's go through each of
319:19 and policing let's go through each of one of those cisco does not expect you
319:22 one of those cisco does not expect you to know each of these in detail again
319:24 to know each of these in detail again that would be later in your ccdp studies
319:28 that would be later in your ccdp studies but that being said
319:29 but that being said they want you to understand
319:31 they want you to understand what each of these are
319:34 what each of these are priority queuing is a queuing method
319:36 priority queuing is a queuing method that establishes four interface output
319:38 that establishes four interface output cues that serve different priority
319:40 cues that serve different priority levels
319:41 levels which are high medium default and low
319:44 which are high medium default and low unfortunately priority queueing can
319:46 unfortunately priority queueing can starve other cues if too much data is in
319:49 starve other cues if too much data is in one queue
319:51 one queue because higher priority queues must be
319:53 because higher priority queues must be emptied first
319:54 emptied first before lower priority queues
319:57 before lower priority queues next there is custom queuing
320:00 next there is custom queuing it uses up to 16 individual output
320:02 it uses up to 16 individual output queues
320:03 queues byte size limits are assigned to each
320:05 byte size limits are assigned to each queue so that when the limit is reached
320:07 queue so that when the limit is reached it proceeds to the next queue the
320:10 it proceeds to the next queue the network operator can customize these
320:12 network operator can customize these limits
320:14 limits and custom cueing is obviously fairer
320:16 and custom cueing is obviously fairer than priority queueing because it allows
320:18 than priority queueing because it allows some level of service to all traffic
320:21 some level of service to all traffic but this is really a legacy solution
320:23 but this is really a legacy solution because there are improvements in the
320:25 because there are improvements in the queuing methods which we'll talk about
320:27 queuing methods which we'll talk about next
320:28 next weighted fair queuing ensures that
320:30 weighted fair queuing ensures that traffic is separated into individual
320:32 traffic is separated into individual flows or sessions without requiring that
320:34 flows or sessions without requiring that you define access lists
320:37 you define access lists waited for a curing uses two categories
320:39 waited for a curing uses two categories to group sessions high and low bandwidth
320:42 to group sessions high and low bandwidth low bandwidth traffic has priority over
320:45 low bandwidth traffic has priority over high bandwidth traffic
320:47 high bandwidth traffic and high bandwidth traffic shares the
320:49 and high bandwidth traffic shares the service according to assigned weight
320:51 service according to assigned weight values
320:53 values please know that weighted fair cueing is
320:55 please know that weighted fair cueing is the default quality service mechanism on
320:57 the default quality service mechanism on interfaces below
320:59 interfaces below 2 megabits per second
321:02 2 megabits per second next is class
321:04 next is class based weighted fair queueing
321:08 based weighted fair queueing it extends waited for queueing
321:09 it extends waited for queueing capabilities by providing support for
321:11 capabilities by providing support for modular user-defined traffic classes
321:16 modular user-defined traffic classes class-based waiver fair queuing lets you
321:17 class-based waiver fair queuing lets you define traffic classes that correspond
321:20 define traffic classes that correspond to match criteria
321:22 to match criteria including acls protocols and input
321:24 including acls protocols and input interfaces
321:26 interfaces traffic that matches the class criteria
321:28 traffic that matches the class criteria belongs to that specific class and each
321:30 belongs to that specific class and each class
321:32 class has a defined queue that corresponds to
321:34 has a defined queue that corresponds to an output interface
321:36 an output interface so after traffic has been matched and
321:38 so after traffic has been matched and belongs to a specific class
321:40 belongs to a specific class you can modify its characteristics such
321:42 you can modify its characteristics such as assigning bandwidth
321:44 as assigning bandwidth maximum queue limit and weight
321:47 maximum queue limit and weight as you see in the picture here
321:49 as you see in the picture here certain classes receive higher priority
321:52 certain classes receive higher priority than other classes
321:54 than other classes as you see in the diagram here certain
321:56 as you see in the diagram here certain classes receive more bandwidth than
321:59 classes receive more bandwidth than other classes
322:01 other classes and also as you see here this is a form
322:03 and also as you see here this is a form of class based waiting for queueing but
322:06 of class based waiting for queueing but actually this is called low latency
322:08 actually this is called low latency queuing because it has a priority queue
322:11 queuing because it has a priority queue and that's the big difference
322:13 and that's the big difference the strict priority queue allows delay
322:15 the strict priority queue allows delay sensitive traffic such as voice
322:18 sensitive traffic such as voice to be sent first before other cues are
322:20 to be sent first before other cues are serviced
322:22 serviced that gives voice preferential treatment
322:24 that gives voice preferential treatment over other traffic types
322:26 over other traffic types unlike priority queuing low latency
322:28 unlike priority queuing low latency queuing provides for a maximum threshold
322:31 queuing provides for a maximum threshold on the priority queue
322:33 on the priority queue then this will prevent lower priority
322:35 then this will prevent lower priority traffic from being starved by the
322:37 traffic from being starved by the priority queue
322:38 priority queue now without low latency queuing
322:41 now without low latency queuing class based waiting for queuing would
322:42 class based waiting for queuing would not have a priority queue for real-time
322:44 not have a priority queue for real-time traffic
322:48 now that we've talked about queuing let's talk about traffic shaping and
322:51 let's talk about traffic shaping and policing
322:52 policing traffic shaping and policing are
322:55 traffic shaping and policing are mechanisms that inspect traffic and then
322:58 mechanisms that inspect traffic and then take action based on the traffic's
323:00 take action based on the traffic's characteristics such as dscp
323:03 characteristics such as dscp or ip precedence bits set in the ip
323:06 or ip precedence bits set in the ip header
323:07 header traffic shaping slows down the rate at
323:09 traffic shaping slows down the rate at which packets are sent out an interface
323:12 which packets are sent out an interface by matching certain criteria
323:14 by matching certain criteria traffic shaping uses a token bucket
323:16 traffic shaping uses a token bucket technique to release the packets into
323:18 technique to release the packets into the output queue
323:20 the output queue at a pre-configured rate
323:22 at a pre-configured rate so this helps eliminate potential
323:24 so this helps eliminate potential bottlenecks by throttling back the
323:26 bottlenecks by throttling back the traffic rate at the source
323:29 traffic rate at the source traffic shipping is used on larger
323:31 traffic shipping is used on larger networks to smooth the flow of traffic
323:33 networks to smooth the flow of traffic going out to the provider
323:36 going out to the provider this is desirable for a few reasons
323:38 this is desirable for a few reasons in provider networks it prevents the
323:40 in provider networks it prevents the provider from dropping traffic that
323:42 provider from dropping traffic that exceeds the contracted rate
323:44 exceeds the contracted rate now policing is a little bit different
323:46 now policing is a little bit different because it tags or drops traffic
323:48 because it tags or drops traffic depending on the match criteria
323:50 depending on the match criteria generally speaking policing is used to
323:52 generally speaking policing is used to set the limit of incoming traffic into
323:54 set the limit of incoming traffic into an interface
323:56 an interface and then it will drop traffic that
323:58 and then it will drop traffic that exceeds what the settings were
324:02 exceeds what the settings were one example of using policing is to give
324:04 one example of using policing is to give preferential treatment to critical
324:06 preferential treatment to critical application traffic by elevating to a
324:09 application traffic by elevating to a higher class and reducing best effort
324:11 higher class and reducing best effort traffic to a lower priority class
324:14 traffic to a lower priority class the best way to compare shaping with
324:16 the best way to compare shaping with policing is to remember
324:18 policing is to remember that shaping buffers packets
324:20 that shaping buffers packets policing does not
324:22 policing does not it can be configured to drop packets
324:25 it can be configured to drop packets our final topic is link efficiency
324:28 our final topic is link efficiency within cisco ios there are several link
324:30 within cisco ios there are several link efficiency mechanisms available
324:33 efficiency mechanisms available as you can see here
324:35 as you can see here there's lfi
324:37 there's lfi which is used to reduce delay or jitter
324:39 which is used to reduce delay or jitter on slower speed links
324:42 on slower speed links multi-link ppp
324:44 multi-link ppp which bonds multiple links together
324:46 which bonds multiple links together between no two nodes which can increase
324:48 between no two nodes which can increase available bandwidth and then rtp
324:51 available bandwidth and then rtp real-time transport header compression
324:55 real-time transport header compression which can pro which provides increased
324:57 which can pro which provides increased efficiency for applications
324:59 efficiency for applications that take advantage of rtp on slower
325:02 that take advantage of rtp on slower lengths
325:04 lengths so here's what you've learned you've
325:05 so here's what you've learned you've received a high level overview of
325:07 received a high level overview of quality of service
325:10 quality of service and then you learn about quality of
325:11 and then you learn about quality of service functions such as classification
325:14 service functions such as classification congestion management
325:17 congestion management link efficiency mechanisms and then
325:19 link efficiency mechanisms and then traffic shaping and policing
325:22 traffic shaping and policing if you know this video well you'll do
325:24 if you know this video well you'll do well on your qos portion of your ccda
325:26 well on your qos portion of your ccda exam
325:28 exam and i wish you the best of luck in your
325:29 and i wish you the best of luck in your studies
325:54 hi this is david voss ccie11372 and in this video we're going to cover
325:55 and in this video we're going to cover the remaining wand technologies or
325:58 the remaining wand technologies or considerations that you need to know for
326:01 considerations that you need to know for your ccda exam we're going to cover
326:04 your ccda exam we're going to cover remote access design
326:06 remote access design then vpns
326:09 then vpns wide area network backups
326:12 wide area network backups and then finally enterprise branch
326:14 and then finally enterprise branch module design
326:20 let's start with remote access design when designing the remote access block
326:22 when designing the remote access block you must ensure that the network users
326:24 you must ensure that the network users have transparent access to the network
326:27 have transparent access to the network from wherever they are
326:29 from wherever they are just as they are connected to the actual
326:31 just as they are connected to the actual network
326:32 network the users must be able to reach the
326:34 the users must be able to reach the resources they are authorized to use as
326:36 resources they are authorized to use as they would from the enterprise campus
326:39 they would from the enterprise campus in order to provide these services the
326:41 in order to provide these services the connection requirements must be analyzed
326:43 connection requirements must be analyzed carefully
326:44 carefully in order to ensure they are fulfilled
326:48 in order to ensure they are fulfilled typical requirements include voip
326:50 typical requirements include voip support vpn support
326:52 support vpn support high volume traffic or low volume
326:54 high volume traffic or low volume traffic permanent connection is it
326:57 traffic permanent connection is it needed or not and the type of flows
327:00 needed or not and the type of flows now vpn concentrators have often be used
327:02 now vpn concentrators have often be used to accept these external sessions but
327:06 to accept these external sessions but cisco's multi-function asa platform is
327:09 cisco's multi-function asa platform is now the standard platform for providing
327:11 now the standard platform for providing both security and vpn services to the
327:14 both security and vpn services to the raz block the raz block is normally
327:17 raz block the raz block is normally comprised of firewalls and systems that
327:20 comprised of firewalls and systems that can provide vpn and security solutions
327:23 can provide vpn and security solutions all in one
327:24 all in one or they can be broken out such as vpn
327:26 or they can be broken out such as vpn concentrators dial up networking
327:28 concentrators dial up networking services
327:29 services and of course you still want to have
327:31 and of course you still want to have your security so ids and ips solutions
327:34 your security so ids and ips solutions to actively monitor any unwanted traffic
327:37 to actively monitor any unwanted traffic or activity
327:38 or activity so let's get more granular and talk
327:40 so let's get more granular and talk about vpn network design
327:43 about vpn network design even though the vpn concept involves
327:45 even though the vpn concept involves security most of the time
327:48 security most of the time unsecured vpns exist
327:51 unsecured vpns exist a very basic example of this would be
327:53 a very basic example of this would be frame relay
327:55 frame relay vpn troubleshooting is difficult to
327:57 vpn troubleshooting is difficult to manage because of the lack of visibility
327:59 manage because of the lack of visibility into the provider infrastructure
328:02 into the provider infrastructure the service provider is usually seen as
328:04 the service provider is usually seen as a cloud that aggregates all the network
328:06 a cloud that aggregates all the network locations connections
328:09 locations connections so when performing vpn troubleshooting
328:11 so when performing vpn troubleshooting you should first take a look at the
328:13 you should first take a look at the problem on your end and make sure it
328:15 problem on your end and make sure it does not reside on your devices
328:18 does not reside on your devices and then if you are sure or as sure as
328:21 and then if you are sure or as sure as you can be
328:22 you can be reach out to your isp
328:25 reach out to your isp types of vpn technologies include the
328:27 types of vpn technologies include the following
328:28 following site-to-site vpns
328:31 site-to-site vpns these are used to connect different
328:32 these are used to connect different locations over a
328:34 locations over a public infrastructure
328:36 public infrastructure now when using peer-to-peer
328:37 now when using peer-to-peer infrastructure you can communicate
328:39 infrastructure you can communicate seamlessly
328:40 seamlessly between sites without worry about ip
328:42 between sites without worry about ip addressing overlap
328:49 remote access vpns such as in the older days uh vpdn virtual private dial up
328:52 days uh vpdn virtual private dial up network although you may still see that
328:54 network although you may still see that here and there
328:56 here and there or surely you're aware of vpn software
328:59 or surely you're aware of vpn software that you can run on your laptop nowadays
329:01 that you can run on your laptop nowadays to connect into your corporate network
329:04 to connect into your corporate network and then there's extranet vpns to
329:05 and then there's extranet vpns to connect to business partners or customer
329:08 connect to business partners or customer networks
329:14 with vpns traffic is often tunneled in order to send it over an infrastructure
329:17 order to send it over an infrastructure now the tunneling methodology for layer
329:19 now the tunneling methodology for layer 3 is called gre or generic routing
329:22 3 is called gre or generic routing encapsulation
329:24 encapsulation gre allows traffic to tunnel
329:27 gre allows traffic to tunnel but it does not provide security so
329:29 but it does not provide security so let's talk about gre and then also the
329:32 let's talk about gre and then also the options you can use to provide security
329:35 options you can use to provide security over gre
329:37 over gre gre was developed as a tunneling
329:39 gre was developed as a tunneling methodology which can carry layer 3
329:42 methodology which can carry layer 3 protocols over an ip network
329:45 protocols over an ip network in essence gre creates a private
329:48 in essence gre creates a private point-to-point connection like a vpn
329:50 point-to-point connection like a vpn except gre does not provide secure
329:53 except gre does not provide secure communications but we'll deal with that
329:55 communications but we'll deal with that a little bit later
329:57 a little bit later gre works by encapsulating payload
330:00 gre works by encapsulating payload traffic inside an ip packet
330:03 traffic inside an ip packet gre tunnel endpoints send payloads
330:06 gre tunnel endpoints send payloads through tunnels by routing encapsulated
330:09 through tunnels by routing encapsulated packets through ip
330:11 packets through ip here's what makes it work
330:13 here's what makes it work the ip routers along the way do not look
330:16 the ip routers along the way do not look at the payload they look only at the
330:18 at the payload they look only at the outer ip packet as they forward it
330:21 outer ip packet as they forward it towards the gre tunnel endpoint
330:23 towards the gre tunnel endpoint and upon reaching the tunnel endpoint
330:26 and upon reaching the tunnel endpoint gre encapsulation is removed and the
330:28 gre encapsulation is removed and the payload is forwarded along to its
330:30 payload is forwarded along to its ultimate destination
330:32 ultimate destination now this is obviously very useful since
330:34 now this is obviously very useful since a gre tunnel can encapsulate almost any
330:37 a gre tunnel can encapsulate almost any type of data you want to send out a
330:39 type of data you want to send out a physical router interface
330:42 physical router interface so let's just walk through an example of
330:44 so let's just walk through an example of gre tunneling here you have a cloud and
330:46 gre tunneling here you have a cloud and let's say you have two routers and they
330:48 let's say you have two routers and they communicate over a provider network so
330:50 communicate over a provider network so there are multiple hops over this
330:52 there are multiple hops over this network and you need to you need to
330:54 network and you need to you need to tunnel traffic that the provider does
330:56 tunnel traffic that the provider does not allow the tr the provider does not
330:58 not allow the tr the provider does not allow certain traffic over their network
331:00 allow certain traffic over their network so what you do is you create two
331:03 so what you do is you create two tunnel interfaces one on router one and
331:05 tunnel interfaces one on router one and one on router two
331:07 one on router two and these are your end points for your
331:09 and these are your end points for your gre tunnel now over this jre tunnel you
331:12 gre tunnel now over this jre tunnel you can send whatever you want over it
331:13 can send whatever you want over it because it has an ip header the provider
331:16 because it has an ip header the provider provides support for ip but you can send
331:18 provides support for ip but you can send whatever you want
331:20 whatever you want over this tr over this tunnel
331:23 over this tr over this tunnel by by encapsulating it in an ip header
331:26 by by encapsulating it in an ip header and you are adhering to their standards
331:28 and you are adhering to their standards but you're also able to send traffic
331:31 but you're also able to send traffic that you need to send over your tunnel
331:34 that you need to send over your tunnel even if it's not permitted by the
331:35 even if it's not permitted by the provider on a normal basis
331:37 provider on a normal basis gre gives you that flexibility
331:40 gre gives you that flexibility when you hear the word encapsulate
331:42 when you hear the word encapsulate now you may think of security but gre by
331:46 now you may think of security but gre by itself does not provide any security for
331:49 itself does not provide any security for the data it transmits
331:51 the data it transmits so again let's take another look at gre
331:54 so again let's take another look at gre tunneling with from a secure perspective
331:56 tunneling with from a secure perspective we have two routers
331:58 we have two routers and we're going to create a jerry tunnel
332:00 and we're going to create a jerry tunnel between both of them the traffic that is
332:03 between both of them the traffic that is traversing the
332:05 traversing the the provider is encapsulated but it's
332:07 the provider is encapsulated but it's still not secure it could be viewed if
332:10 still not secure it could be viewed if if somebody wanted uh to view it um it's
332:13 if somebody wanted uh to view it um it's still in the open so you could run ipsec
332:16 still in the open so you could run ipsec and encrypt the data on let's say router
332:19 and encrypt the data on let's say router 1
332:20 1 and as it's sent over to router 2 it
332:22 and as it's sent over to router 2 it stays encrypted over the provider
332:24 stays encrypted over the provider network and then router 2 would
332:25 network and then router 2 would unencrypt that data and then send it so
332:28 unencrypt that data and then send it so again from router tutor 1 1 would work
332:30 again from router tutor 1 1 would work as well again the encryption is on the
332:32 as well again the encryption is on the routers on our end so anytime it
332:34 routers on our end so anytime it traverses the provider that data is
332:37 traverses the provider that data is secure so ip2 and gre
332:40 secure so ip2 and gre often play hand in hand
332:42 often play hand in hand the limitation of ipsec is that it can
332:44 the limitation of ipsec is that it can only protect unicast ip packets
332:48 only protect unicast ip packets so this causes issues for routing
332:50 so this causes issues for routing protocols that use ip multicasts
332:53 protocols that use ip multicasts gre allows you to get around this
332:56 gre allows you to get around this problem because gre
332:58 problem because gre a gre tunnel can encapsulate ip
333:01 a gre tunnel can encapsulate ip multicast packets so the resulting gre
333:04 multicast packets so the resulting gre packet is an ip unicast packet but which
333:07 packet is an ip unicast packet but which can then be protected by an ipsec tunnel
333:15 next let's talk about when backup design now when connectivity can achieve backup
333:18 now when connectivity can achieve backup through the following approaches
333:20 through the following approaches dial-up backup activated when a primary
333:22 dial-up backup activated when a primary link fails used to be very popular due
333:24 link fails used to be very popular due to cost and bandwidth requirements it's
333:26 to cost and bandwidth requirements it's just simply not as popular today
333:29 just simply not as popular today secondary wan link which is used for
333:31 secondary wan link which is used for backup and or load balancing this tends
333:34 backup and or load balancing this tends to be more popular
333:35 to be more popular or a shadow vpn and this is used when
333:38 or a shadow vpn and this is used when the isp
333:39 the isp establishes a second pvc or permanent
333:42 establishes a second pvc or permanent virtual circuit
333:44 virtual circuit but the user is only charged for its
333:46 but the user is only charged for its usage
333:47 usage so this can be a
333:49 so this can be a very useful when the main pvc fails or
333:52 very useful when the main pvc fails or in situations where more bandwidth is
333:54 in situations where more bandwidth is needed
333:59 finally let's talk about the enterprise branch module
334:01 branch module branch modules are sized based on the
334:03 branch modules are sized based on the number of users it needs to accommodate
334:07 number of users it needs to accommodate for example the enterprise teleworker
334:08 for example the enterprise teleworker which is generally one user
334:11 which is generally one user single tier tens of users
334:13 single tier tens of users dual tier hundreds of users and
334:16 dual tier hundreds of users and multi-tier thousands of users
334:18 multi-tier thousands of users as the number of users in the branch
334:21 as the number of users in the branch modules grows additional layers might be
334:24 modules grows additional layers might be needed the internet block generally
334:26 needed the internet block generally serves as the gateway for your internal
334:28 serves as the gateway for your internal users to the internet if they want to
334:30 users to the internet if they want to browse perform file transfers or stream
334:33 browse perform file transfers or stream audio or video presentations
334:35 audio or video presentations their flows would go in and out of this
334:37 their flows would go in and out of this block
334:38 block now notice how the internal traffic from
334:40 now notice how the internal traffic from your users is not using the same block
334:43 your users is not using the same block as those who are coming in from the
334:45 as those who are coming in from the internet this ensures that no external
334:48 internet this ensures that no external users are trying to hijack internal
334:50 users are trying to hijack internal flows
334:51 flows that being said oftentimes the internal
334:54 that being said oftentimes the internal and e-commerce blocks can share the same
334:57 and e-commerce blocks can share the same internet pipe
334:59 internet pipe but if you prefer not to do that you can
335:01 but if you prefer not to do that you can use what is called a dual homes
335:03 use what is called a dual homes connection
335:04 connection to two separate internet service
335:06 to two separate internet service providers to make sure that that traffic
335:08 providers to make sure that that traffic is segmented
335:10 is segmented now if one internet service provider did
335:13 now if one internet service provider did fail you could then allow all traffic
335:16 fail you could then allow all traffic over the same circuit as a fail safe
335:19 over the same circuit as a fail safe the internet block is comprised of
335:21 the internet block is comprised of firewalls routers http servers smtp
335:24 firewalls routers http servers smtp servers ftp servers and dns servers to
335:27 servers ftp servers and dns servers to name a few
335:29 name a few so here's what you've learned you've
335:30 so here's what you've learned you've learned about the remaining items you
335:32 learned about the remaining items you need to know for wide area network
335:35 need to know for wide area network considerations and technologies for your
335:37 considerations and technologies for your ccda exam
335:39 ccda exam some of it is granular and some about we
335:41 some of it is granular and some about we stayed high level but we definitely
335:43 stayed high level but we definitely covered it to the level you will need to
335:45 covered it to the level you will need to know
335:45 know for your ccda exam if you know what's in
335:48 for your ccda exam if you know what's in this video you should do very well
335:50 this video you should do very well good luck in your studies
336:22 hi this is david voss ccie 11372 and in this video we're covering
336:24 this video we're covering branch office design
336:27 branch office design specifically in this video you're going
336:29 specifically in this video you're going to learn about designing for a very
336:32 to learn about designing for a very small office
336:33 small office the small office
336:36 the small office a medium-sized office 4-hour versus
336:39 a medium-sized office 4-hour versus extended service
336:42 extended service a medium-sized office layer 2
336:45 a medium-sized office layer 2 and then a large size office
336:48 and then a large size office all of these are types of branch offices
336:51 all of these are types of branch offices that you'll need to know
336:53 that you'll need to know for your ccda exam
337:05 the cisco enterprise branch architecture takes into account services such as
337:07 takes into account services such as voice data video and security
337:10 voice data video and security that customers want to deploy at their
337:12 that customers want to deploy at their endpoints
337:13 endpoints no matter how far away the endpoints are
337:16 no matter how far away the endpoints are or how they are connected
337:19 or how they are connected using borderless networks the cisco
337:21 using borderless networks the cisco enterprise branch office architecture
337:24 enterprise branch office architecture should provide seamless connectivity
337:27 should provide seamless connectivity an effective network design for
337:29 an effective network design for enterprise branches and teleworkers
337:31 enterprise branches and teleworkers requires knowledge of campus
337:34 requires knowledge of campus technologies
337:36 technologies the cisco enterprise branch architecture
337:39 the cisco enterprise branch architecture is an integrated
337:41 is an integrated flexible and secure framework
337:43 flexible and secure framework for extending headquarter applications
337:45 for extending headquarter applications in real time to remote sites
337:48 in real time to remote sites it uses the cisco network architecture
337:50 it uses the cisco network architecture for the enterprise framework
337:52 for the enterprise framework but it applies it to the smaller scale
337:55 but it applies it to the smaller scale of a branch location
337:57 of a branch location common network components that can be
337:59 common network components that can be implemented in the branch include
338:02 implemented in the branch include routers that provide wan edge
338:03 routers that provide wan edge connectivity
338:05 connectivity switches that provide the lan
338:06 switches that provide the lan infrastructure
338:08 infrastructure security appliances that defend the
338:10 security appliances that defend the branch offices
338:12 branch offices wireless access points for device
338:14 wireless access points for device mobility
338:16 mobility call processing and video equipment for
338:18 call processing and video equipment for ip telephony and video support
338:21 ip telephony and video support and end user devices including ip phones
338:25 and end user devices including ip phones and computers
338:31 cisco has developed six topologies to meet remote office requirements
338:33 meet remote office requirements each design is based on a set of
338:35 each design is based on a set of requirements which we will discuss now
338:39 requirements which we will discuss now first size the primary classification
338:42 first size the primary classification criteria is the size of the remote site
338:45 criteria is the size of the remote site the size of the remote site is based on
338:46 the size of the remote site is based on the number of ports required which is
338:48 the number of ports required which is dependent on the number of employees at
338:50 dependent on the number of employees at the site
338:51 the site and any special application supported in
338:53 and any special application supported in the remote site
338:55 the remote site some sites allocate two to four ports
338:57 some sites allocate two to four ports per employee while others allocate fewer
339:00 per employee while others allocate fewer than one port per employee
339:03 than one port per employee in addition to head count other factors
339:05 in addition to head count other factors that may impact the total poor count
339:07 that may impact the total poor count this can be such things as meeting rooms
339:10 this can be such things as meeting rooms public areas reception
339:12 public areas reception and other it devices or security cameras
339:20 next wiring closets different buildings may require only one or more than one
339:22 may require only one or more than one wiring closet
339:24 wiring closet since some cabling can only carry for
339:26 since some cabling can only carry for example 100 megabits per second fast
339:28 example 100 megabits per second fast ethernet for about 100 meters
339:30 ethernet for about 100 meters any building longer than 200 meters
339:32 any building longer than 200 meters should have more than one wiring closet
339:35 should have more than one wiring closet multi-storied buildings should also have
339:37 multi-storied buildings should also have more than one wiring closet
339:40 more than one wiring closet please note that while large and
339:41 please note that while large and multi-storey buildings often house more
339:44 multi-storey buildings often house more users and more ports that's not always
339:46 users and more ports that's not always the case
339:52 let's go ahead and take a look at some of the office types
339:54 of the office types the very small office model covers
339:56 the very small office model covers offices servicing approximately one to
339:59 offices servicing approximately one to five people
340:00 five people where service level agreements can be
340:02 where service level agreements can be negotiated around the lack of redundancy
340:04 negotiated around the lack of redundancy for data and voice networking
340:07 for data and voice networking examples of small offices include
340:10 examples of small offices include the convenient office a small office
340:12 the convenient office a small office with a client company
340:14 with a client company or a small cisco leased office with
340:17 or a small cisco leased office with shared facilities such as phones and
340:20 shared facilities such as phones and internet connection
340:27 a very small office is defined as having one or all of the following
340:29 as having one or all of the following characteristics
340:31 characteristics the maximum number of access ports to be
340:34 the maximum number of access ports to be supported at the remote site is 23.
340:37 supported at the remote site is 23. the site does not require any redundancy
340:40 the site does not require any redundancy in terms of leased switches or devices
340:42 in terms of leased switches or devices on the network
340:44 on the network voice enabled cisco isr 3845
340:48 voice enabled cisco isr 3845 router would be a good example of the
340:49 router would be a good example of the hardware you would use
340:51 hardware you would use using an etherswitch service module
340:53 using an etherswitch service module iphones and access points
340:57 iphones and access points the site can be supported by a
340:58 the site can be supported by a traditional lease line based wan or vpn
341:01 traditional lease line based wan or vpn connection over the public internet with
341:03 connection over the public internet with reduced sla
341:12 the next site we'll discuss is the small office
341:15 office the small office model is designed to
341:17 the small office model is designed to support offices with a total poor count
341:19 support offices with a total poor count not exceeding 288
341:22 not exceeding 288 the design is flexible enough to be used
341:24 the design is flexible enough to be used in implementations where either all
341:26 in implementations where either all access ports are aggregated into a
341:28 access ports are aggregated into a single wiring closet or where the access
341:31 single wiring closet or where the access ports are broken into different wiring
341:34 ports are broken into different wiring closets up to the total of
341:36 closets up to the total of five a small office is defined as one
341:40 five a small office is defined as one that has the following characteristics
341:42 that has the following characteristics maximum number of access ports 288
341:46 maximum number of access ports 288 redundancy is achieved by deploying dual
341:48 redundancy is achieved by deploying dual wind gateways each with their own when
341:51 wind gateways each with their own when circuit where more than one switch is
341:53 circuit where more than one switch is present in the same wiring closet the
341:55 present in the same wiring closet the switches are deployed in a stack
341:58 switches are deployed in a stack at minimum two switches should be
341:59 at minimum two switches should be stacked together in the core
342:02 stacked together in the core hardware a typical hardware you'd find
342:04 hardware a typical hardware you'd find would be a cisco 3845 router
342:07 would be a cisco 3845 router and up to six switches
342:09 and up to six switches using ip phones and wireless access
342:12 using ip phones and wireless access points
342:14 points it is the preference for this site to be
342:16 it is the preference for this site to be deployed using a permanent wind service
342:19 deployed using a permanent wind service but if that is not possible then a
342:21 but if that is not possible then a vpn connection over the public internet
342:24 vpn connection over the public internet can be used
342:33 the next branch office model is the medium-sized office
342:36 medium-sized office this design covers medium-sized offices
342:38 this design covers medium-sized offices where critical service is required
342:41 where critical service is required and this is where we talk about the
342:43 and this is where we talk about the cisco smartnet contract or support
342:45 cisco smartnet contract or support contract
342:47 contract this design is classified into two
342:48 this design is classified into two separate models which cisco specifically
342:51 separate models which cisco specifically refers to as four hour
342:53 refers to as four hour and four hour extended
342:55 and four hour extended for our extended model includes an
342:57 for our extended model includes an additional switch to support sites with
342:59 additional switch to support sites with a secondary communication room or wiring
343:02 a secondary communication room or wiring closet
343:03 closet a medium office 4-hour extended is
343:06 a medium office 4-hour extended is defined as one that has the following
343:07 defined as one that has the following characteristics
343:09 characteristics up to 336 switch ports
343:12 up to 336 switch ports for 4-hour model and 672 ports for the
343:15 for 4-hour model and 672 ports for the extended model
343:17 extended model one or two communication rooms or wiring
343:20 one or two communication rooms or wiring closets
343:21 closets redundancy is achieved by deploying dual
343:24 redundancy is achieved by deploying dual wind gateways each with their own wind
343:26 wind gateways each with their own wind circuit each lan switch is deployed with
343:28 circuit each lan switch is deployed with dual supervisors and dual power supplies
343:35 the site would have a cisco router with an etherswitch service module
343:38 an etherswitch service module supporting iphones and access points
343:42 supporting iphones and access points it is the preference for the site to be
343:43 it is the preference for the site to be deployed using a permanent win service
343:46 deployed using a permanent win service but if that is not possible then a vpn
343:48 but if that is not possible then a vpn connection over the public internet
343:50 connection over the public internet can be used
344:00 the next model is the medium-sized office
344:01 office this design caters for medium-sized
344:03 this design caters for medium-sized offices where the total pour cone does
344:04 offices where the total pour cone does not exceed
344:06 not exceed 1344 ports
344:08 1344 ports and where there are no more than three
344:10 and where there are no more than three wiring closets
344:12 wiring closets typically you'll find higher powered
344:15 typically you'll find higher powered dual switches that are deployed in the
344:17 dual switches that are deployed in the core
344:19 core even though they already have dual power
344:21 even though they already have dual power supplies and dual processors
344:23 supplies and dual processors this is done for offices where shipping
344:26 this is done for offices where shipping in local customs may cause replacement
344:29 in local customs may cause replacement equipment to be delayed
344:31 equipment to be delayed or where the potential impact to the
344:33 or where the potential impact to the client is far too great to implement a
344:35 client is far too great to implement a four hour model
344:43 a medium-sized office is defined as one that has the following characteristics
344:45 that has the following characteristics up to 672 switch ports for layer 2
344:49 up to 672 switch ports for layer 2 and 1 344 ports using the extended model
344:58 between one and three wiring closets redundancy is achieved by deploying dual
345:01 redundancy is achieved by deploying dual wind gateways each with their own wind
345:03 wind gateways each with their own wind circuit
345:04 circuit each lan switch is deployed with dual
345:06 each lan switch is deployed with dual supervisors and dual power supplies
345:10 supervisors and dual power supplies voice enabled router with up to four
345:13 voice enabled router with up to four high powered switches
345:14 high powered switches with dual supervisors and dual power
345:17 with dual supervisors and dual power supplies the cisco catalyst 6500 series
345:20 supplies the cisco catalyst 6500 series is the typical switch you would find in
345:22 is the typical switch you would find in the core
345:23 the core and this is supporting iphones and
345:25 and this is supporting iphones and access points
345:27 access points it's the preference for this site to be
345:29 it's the preference for this site to be deployed using a permanent wind service
345:31 deployed using a permanent wind service but again if that's not possible
345:34 but again if that's not possible then a vpn connection over the public
345:36 then a vpn connection over the public internet can be used
345:47 the next model we'll talk about is large size office
345:48 size office the large office model caters to all
345:50 the large office model caters to all remaining sites exceeding the
345:52 remaining sites exceeding the specification for the proceeding models
345:55 specification for the proceeding models typically the sites have a requirement
345:56 typically the sites have a requirement of greater than 1 344 points ports and
346:01 of greater than 1 344 points ports and or more than three wiring closets the
346:04 or more than three wiring closets the large size office has a distribution
346:05 large size office has a distribution layer to support the extended network
346:08 layer to support the extended network these sites differ from earlier
346:10 these sites differ from earlier topologies because the switches are
346:12 topologies because the switches are redundant the port capacity is larger
346:15 redundant the port capacity is larger and the business supported at these
346:17 and the business supported at these sites is critical
346:19 sites is critical within cisco i.t this model is typically
346:21 within cisco i.t this model is typically referred to as the complex model
346:25 referred to as the complex model a large size office is defined as one
346:28 a large size office is defined as one that has the following characteristics
346:32 that has the following characteristics 1344 access ports and beyond
346:35 1344 access ports and beyond no restriction on the number of wiring
346:37 no restriction on the number of wiring closets redundancy is achieved by
346:40 closets redundancy is achieved by deploying dual wind gateways
346:42 deploying dual wind gateways each with their own lan circuit each lan
346:45 each with their own lan circuit each lan switch is deployed with dual supervisors
346:47 switch is deployed with dual supervisors and dual power supplies
346:50 and dual power supplies the hardware would be a voice enabled
346:51 the hardware would be a voice enabled cisco router
346:53 cisco router with typically higher end cisco switches
346:56 with typically higher end cisco switches like the catalyst 6500
346:58 like the catalyst 6500 using dual supervisors and dual power
347:00 using dual supervisors and dual power supplies
347:02 supplies also supporting iphones and access
347:04 also supporting iphones and access points
347:05 points it is a requirement for this
347:07 it is a requirement for this type of site to be deployed using a
347:09 type of site to be deployed using a permanent win service and cisco does not
347:13 permanent win service and cisco does not suggest or it would not qualify for this
347:16 suggest or it would not qualify for this type of
347:17 type of deployment
347:18 deployment using a vpn solution over the internet
349:57 so here's what you've learned you've learned about
349:59 learned about branch office design
350:01 branch office design specifically the six different models
350:04 specifically the six different models that is the very small office small
350:06 that is the very small office small office
350:08 office medium-sized office four-hour versus
350:10 medium-sized office four-hour versus extended service
350:12 extended service medium-sized office layer two
350:14 medium-sized office layer two and the large size office
350:17 and the large size office all this information you'll need to know
350:18 all this information you'll need to know for your ccda exam
350:21 for your ccda exam but also certainly to make you a
350:22 but also certainly to make you a stronger design engineer in your
350:25 stronger design engineer in your enterprise
350:26 enterprise good luck in your studies
350:37 so [Music]
350:55 hi this is david voss ccie11372 and in this video you're going to learn
350:57 and in this video you're going to learn about ipv4
350:59 about ipv4 addressing
351:01 addressing specifically you're going to learn about
351:03 specifically you're going to learn about ipv4 addresses
351:06 ipv4 addresses subnets
351:08 subnets and then we'll finish it off
351:10 and then we'll finish it off with tcp udp and iep headers
351:15 with tcp udp and iep headers so let's go ahead and begin with a basic
351:16 so let's go ahead and begin with a basic introduction to ipv4
351:19 introduction to ipv4 addresses
351:21 addresses an ip address is a unique logical number
351:24 an ip address is a unique logical number to a network device or interface
351:27 to a network device or interface it is 32 bits in length
351:30 it is 32 bits in length and to make the number easier to read
351:32 and to make the number easier to read the dotted decimal format is used
351:35 the dotted decimal format is used the bits are combined into four 8-bit
351:38 the bits are combined into four 8-bit groups
351:39 groups each converted into decimal numbers
351:43 each converted into decimal numbers for example as you will see here this
351:45 for example as you will see here this address is 10.128.0.1
351:59 the first octet dictates which class the ip address is it
352:02 ip address is it as you see in this diagram
352:04 as you see in this diagram the beginning bits of the first octet
352:07 the beginning bits of the first octet will dictate what class the ip address
352:09 will dictate what class the ip address is
352:10 is there are five classes
352:13 there are five classes a b c d and e
352:15 a b c d and e and let's go ahead and talk about each
352:17 and let's go ahead and talk about each of those at this time
352:20 of those at this time class a addresses range from 0 to 127 in
352:24 class a addresses range from 0 to 127 in the first byte
352:26 the first byte network numbers available for assignment
352:28 network numbers available for assignment to organizations
352:29 to organizations are from 1.0.0.0
352:32 are from 1.0.0.0 to 126.0.0.0.
352:38 by default for class a addresses
352:40 for class a addresses the first byte is the network number
352:43 the first byte is the network number and then the three remaining bytes are
352:45 and then the three remaining bytes are the host number
352:48 the host number class b addresses range from 128 to 191
352:52 class b addresses range from 128 to 191 in the first byte
352:54 in the first byte network numbers assigned to companies or
352:56 network numbers assigned to companies or other organizations are from 128.0.0.0
353:10 by default for class b addresses the first two bytes are the network number
353:12 first two bytes are the network number and the remaining two bytes are the host
353:14 and the remaining two bytes are the host number
353:22 class c addresses range from 192 to 223 in the first byte
353:25 to 223 in the first byte network numbers assigned to companies
353:27 network numbers assigned to companies are from 192.0.0.0
353:33 to 223 255 255.0
353:36 255.0 the format is the first three bytes are
353:38 the format is the first three bytes are the network number and the last byte is
353:40 the network number and the last byte is the host number
353:49 class d addresses range from 224 to 239 in the first byte
353:52 to 239 in the first byte network numbers assigned to multicast
353:54 network numbers assigned to multicast groups range from 224.0.0.1
354:04 to 239 255 255 2555 please note that these addresses do not
354:06 please note that these addresses do not have a host or network portion
354:15 class e addresses range from 240 to 254 in the first byte
354:17 in the first byte these addresses are reserved for
354:19 these addresses are reserved for experimental networks
354:20 experimental networks network 255 is reversed it is reserved
354:23 network 255 is reversed it is reserved for the broadcast address
354:25 for the broadcast address such as all 255's
354:29 such as all 255's again take a look at this table and you
354:32 again take a look at this table and you will see the summary of the ipv4 address
354:35 will see the summary of the ipv4 address classes
354:37 classes each address class can be uniquely
354:39 each address class can be uniquely identified
354:40 identified in binary by the high order bits
354:47 now subnetting plays an important role in ipv4 addressing
354:49 in ipv4 addressing since you want to be able to break down
354:51 since you want to be able to break down the networks into smaller ones
354:54 the networks into smaller ones as you can see here we have a class a ip
354:56 as you can see here we have a class a ip address
354:57 address and if we were to use its default subnet
355:00 and if we were to use its default subnet mask
355:01 mask it would be a slash eight that is the
355:04 it would be a slash eight that is the first eight binary bits
355:07 first eight binary bits would be ones and the rest would be
355:09 would be ones and the rest would be zeros but this would mean we have
355:11 zeros but this would mean we have hundreds of thousands of ip addresses in
355:14 hundreds of thousands of ip addresses in this one subnet
355:15 this one subnet let's say we want to use this ip address
355:17 let's say we want to use this ip address on our internal network and simply
355:19 on our internal network and simply assign it to one small portion of our
355:22 assign it to one small portion of our network where there are 100 users
355:24 network where there are 100 users in that case we would want to assign a
355:27 in that case we would want to assign a smaller subnet let's say a slash 24
355:30 smaller subnet let's say a slash 24 so subnetting allows us to put it on a
355:33 so subnetting allows us to put it on a smaller network with fewer hosts
355:37 smaller network with fewer hosts so the subnet mask is a 32-bit number in
355:40 so the subnet mask is a 32-bit number in which the bits are set to 1
355:42 which the bits are set to 1 to identify this network portion of the
355:44 to identify this network portion of the address and the 0 then identifies the
355:47 address and the 0 then identifies the host portion of the address
355:50 host portion of the address as you can see here we will now set to 1
355:53 as you can see here we will now set to 1 the first 24 bits
355:56 the first 24 bits and that will mark off the subnet which
355:58 and that will mark off the subnet which is now a slash 24
356:01 is now a slash 24 which means
356:02 which means that 10.128
356:05 that 10.128 dot
356:07 dot 24
356:08 24 is a dedicated network that can host
356:11 is a dedicated network that can host 254 hosts
356:19 next let's briefly cover the headers for tcp ip and udp
356:23 tcp ip and udp what you see before you is the ip header
356:26 what you see before you is the ip header you will need to know the functions for
356:27 you will need to know the functions for each of the fields you see before you
356:30 each of the fields you see before you let me cover some of the functions that
356:32 let me cover some of the functions that you will most likely need to know for
356:33 you will most likely need to know for your exam and in real world
356:35 your exam and in real world troubleshooting
356:37 troubleshooting first there's the version field
356:39 first there's the version field the version field indicates that it is
356:42 the version field indicates that it is ipv4 in this instance with a value of 0
356:45 ipv4 in this instance with a value of 0 1 0
356:46 1 0 0. then there's the type of service
356:49 0. then there's the type of service field
356:50 field this field is
356:52 this field is commonly referred to as the type of
356:54 commonly referred to as the type of service byte it has eight bits used to
356:57 service byte it has eight bits used to set quality of service markings and
356:59 set quality of service markings and specifically within this field is dscp
357:03 specifically within this field is dscp the six left most bits are used for dscp
357:08 the six left most bits are used for dscp which obviously commonly is associated
357:10 which obviously commonly is associated with quality of service marking
357:13 with quality of service marking next is the ip flags field this is a
357:16 next is the ip flags field this is a three bit field
357:17 three bit field the second bit of this field is the df
357:20 the second bit of this field is the df or do not fragment fragment bit
357:23 or do not fragment fragment bit and that indicates that a packet should
357:25 and that indicates that a packet should not be fragmented
357:27 not be fragmented then there's the time to live field this
357:30 then there's the time to live field this is an 8-bit field that is decremented by
357:32 is an 8-bit field that is decremented by one each time a packet is routed from
357:34 one each time a packet is routed from one ip network to another
357:37 one ip network to another if ttl ever reaches zero the packet is
357:40 if ttl ever reaches zero the packet is discarded
357:42 discarded the protocol field which is an 8-bit
357:43 the protocol field which is an 8-bit field specifies what kind of data
357:47 field specifies what kind of data type of data is encapsulated
357:50 type of data is encapsulated in the packet
357:51 in the packet tcp and udp are common protocols
357:54 tcp and udp are common protocols identified by this field
357:56 identified by this field finally the source address field which
357:58 finally the source address field which is a 32-bit field indicating the source
358:00 is a 32-bit field indicating the source of the ipv4 packet and then the
358:02 of the ipv4 packet and then the destination address field which again is
358:04 destination address field which again is a 32-bit destination destination address
358:08 a 32-bit destination destination address which indicates the destination
358:10 which indicates the destination for that packet next let's move on to
358:12 for that packet next let's move on to the tcp segment header here are some of
358:14 the tcp segment header here are some of the fields you will certainly need to
358:16 the fields you will certainly need to know you have the source port field
358:18 know you have the source port field which is the 16-bit field indicating the
358:21 which is the 16-bit field indicating the sending port number and the destination
358:24 sending port number and the destination port field again a 16-bit field so for
358:27 port field again a 16-bit field so for example
358:28 example if you connect to
358:29 if you connect to howtonetwork.com you're connecting
358:32 howtonetwork.com you're connecting to a destination port of 80 which is the
358:35 to a destination port of 80 which is the tcp port for http the sequence number
358:38 tcp port for http the sequence number field is a 32-bit field indicating the
358:40 field is a 32-bit field indicating the amount of data sent during a tcp session
358:43 amount of data sent during a tcp session the sending party uses this field to
358:45 the sending party uses this field to make sure the receiving party actually
358:47 make sure the receiving party actually received the data
358:49 received the data the receiving party uses the sequence
358:51 the receiving party uses the sequence number from this field as the basis for
358:54 number from this field as the basis for the acknowledgment number
358:56 the acknowledgment number in the next segment that it sends back
358:58 in the next segment that it sends back to the sender and then the window field
359:00 to the sender and then the window field which is a 16-bit field it specifies the
359:03 which is a 16-bit field it specifies the number of bytes a sender is willing to
359:05 number of bytes a sender is willing to transmit
359:06 transmit before receiving an acknowledgement from
359:08 before receiving an acknowledgement from the receiver known as the round trip
359:10 the receiver known as the round trip time the other iplayer for transport
359:13 time the other iplayer for transport protocol is udp udp is considered to be
359:16 protocol is udp udp is considered to be an unreliable protocol because it lacks
359:19 an unreliable protocol because it lacks all of the features of tcp there's no
359:21 all of the features of tcp there's no sequence numbering no window size no
359:24 sequence numbering no window size no acknowledgements
359:26 acknowledgements you can see here the header is quite
359:28 you can see here the header is quite simple
359:29 simple it contains only source and destination
359:31 it contains only source and destination port numbers
359:33 port numbers and then a udp checksum and then segment
359:36 and then a udp checksum and then segment length so why use udp well it's best for
359:39 length so why use udp well it's best for servicing applications that need to
359:41 servicing applications that need to maximize bandwidth and do not require
359:44 maximize bandwidth and do not require acknowledgements such as video streams
359:46 acknowledgements such as video streams or audio and in fact the primary
359:49 or audio and in fact the primary protocol used to carry voice and video
359:51 protocol used to carry voice and video traffic over networks is
359:53 traffic over networks is rtp
359:55 rtp real-time transport protocol
359:57 real-time transport protocol and that's a layer 4 protocol that is
359:59 and that's a layer 4 protocol that is encapsulated inside of
360:02 encapsulated inside of udp so here's what you learned you
360:04 udp so here's what you learned you learned about the basics of ipv4
360:06 learned about the basics of ipv4 addressing and subnets
360:09 addressing and subnets and then you received a brief overview
360:11 and then you received a brief overview of tcp udp and ip headers
360:14 of tcp udp and ip headers all this information will come in handy
360:16 all this information will come in handy on your ccda exam good luck in your
360:19 on your ccda exam good luck in your studies
360:43 hi this is david voss ccie11372 in this video we will be
360:46 ccie11372 in this video we will be discussing ip version 6 addressing
360:49 discussing ip version 6 addressing so let's ask the basic question
360:51 so let's ask the basic question why even upgrade to ipv version 6 other
360:54 why even upgrade to ipv version 6 other than the fact that you simply get more
360:56 than the fact that you simply get more ip addresses
360:57 ip addresses well there's a lot of reasons why you
361:00 well there's a lot of reasons why you would want to upgrade to ipv version 6
361:02 would want to upgrade to ipv version 6 and here are a few of them spelled out
361:04 and here are a few of them spelled out for you which i think you'll need to
361:06 for you which i think you'll need to know for your ccnp route again exam but
361:09 know for your ccnp route again exam but please note you no longer need nat or
361:11 please note you no longer need nat or pat it has inherent ipsec support these
361:14 pat it has inherent ipsec support these are key and critical updates now once
361:16 are key and critical updates now once you've committed to using ipv6 you need
361:18 you've committed to using ipv6 you need to understand how these different ip
361:20 to understand how these different ip addresses are labeled there's a global
361:23 addresses are labeled there's a global unicast address these are unicast
361:25 unicast address these are unicast packets sent through the public internet
361:28 packets sent through the public internet with public ipa addresses
361:30 with public ipa addresses unique local which are unicast packets
361:32 unique local which are unicast packets inside one organization which is
361:34 inside one organization which is basically equal to your private ipa
361:36 basically equal to your private ipa addressing
361:37 addressing link local which are packets sent to a
361:39 link local which are packets sent to a local subnet and are not rotter audible
361:42 local subnet and are not rotter audible across networks
361:49 and and then finally take note of the loopback address which you know from
361:51 loopback address which you know from ipv4 is 127.001
361:54 ipv4 is 127.001 ipv6 also has a loopback addressing as
361:57 ipv6 also has a loopback addressing as well
361:58 well an ipv6 address has 128 bits
362:03 an ipv6 address has 128 bits broken out into 32 hexadecimal numbers
362:06 broken out into 32 hexadecimal numbers organized into eight quartets
362:08 organized into eight quartets so here is the hexadecimal numbering
362:11 so here is the hexadecimal numbering system
362:12 system which i'm sure we won't need much of a
362:13 which i'm sure we won't need much of a refresher on but we do need to use it to
362:16 refresher on but we do need to use it to understand ipv6
362:18 understand ipv6 and here is an ipv6 ip address and as
362:21 and here is an ipv6 ip address and as you can see it looks quite long mainly
362:23 you can see it looks quite long mainly because we're used to looking at ipv4
362:25 because we're used to looking at ipv4 addresses so
362:27 addresses so this ups the game a little bit and we
362:29 this ups the game a little bit and we may begin to wonder how we're going to
362:30 may begin to wonder how we're going to support this on our network or document
362:33 support this on our network or document this and we get concerned about managing
362:36 this and we get concerned about managing a network addressing this long well
362:38 a network addressing this long well there are built-in mechanisms within ib
362:40 there are built-in mechanisms within ib version 6 to help us manage it and we're
362:42 version 6 to help us manage it and we're going to cover that
362:44 going to cover that there's ways you can summarize ipv6
362:47 there's ways you can summarize ipv6 addresses to make it more manageable not
362:49 addresses to make it more manageable not only to read but to understand and
362:51 only to read but to understand and explain to other people
362:53 explain to other people so you can shorten an ipv6 by omit by
362:56 so you can shorten an ipv6 by omit by omitting the leading zeros in any any
362:58 omitting the leading zeros in any any given quartet or you can represent one
363:01 given quartet or you can represent one or more consecutive quartets
363:03 or more consecutive quartets with a double colon
363:05 with a double colon so here you see an ipv version six
363:07 so here you see an ipv version six address with many zeros in it here's how
363:10 address with many zeros in it here's how we can summarize it
363:11 we can summarize it on the left hand side you can see that
363:14 on the left hand side you can see that we used a double colon to represent the
363:16 we used a double colon to represent the first
363:17 first the second and third quartet and then we
363:21 the second and third quartet and then we summarize the remaining quartets of
363:24 summarize the remaining quartets of zeros and in the second example we did
363:27 zeros and in the second example we did the opposite we summarized the first two
363:31 the opposite we summarized the first two quartets with zeros
363:33 quartets with zeros and then use the double colon for the
363:35 and then use the double colon for the end you can only use the double colon
363:37 end you can only use the double colon once in an ipv version 6 ipa address
363:40 once in an ipv version 6 ipa address so here we see an ip version 6ip address
363:43 so here we see an ip version 6ip address and this is the subnet it's this
363:45 and this is the subnet it's this remember it's a slash 64. so we're
363:47 remember it's a slash 64. so we're matching the first 64 bits as you see
363:50 matching the first 64 bits as you see here
363:51 here and this also can be summarized you
363:54 and this also can be summarized you don't need to write out all these zeros
363:56 don't need to write out all these zeros so to explain what the subnet is to
363:58 so to explain what the subnet is to somebody you can simply write it out
364:00 somebody you can simply write it out this way
364:02 this way so ipv6 is manageable it gives you tools
364:05 so ipv6 is manageable it gives you tools to manage it
364:07 to manage it so whether you're reviewing
364:08 so whether you're reviewing documentation or holding a general
364:10 documentation or holding a general discussion about your network or simply
364:12 discussion about your network or simply logging into a cisco router to take a
364:14 logging into a cisco router to take a look at what's going on
364:16 look at what's going on understanding abbreviation is key to
364:18 understanding abbreviation is key to ipv6
364:20 ipv6 here are some other ways we can
364:21 here are some other ways we can understand ipv6 addressing
364:24 understand ipv6 addressing in our first example you'll see that
364:27 in our first example you'll see that it's 2 0 0 0 and then a double colon
364:29 it's 2 0 0 0 and then a double colon slash four
364:31 slash four the slash four would match the first
364:33 the slash four would match the first four bits and hex that would be zero
364:35 four bits and hex that would be zero zero one zero
364:38 zero one zero so all addresses whose first four bits
364:40 so all addresses whose first four bits are equal to the first four bits of the
364:42 are equal to the first four bits of the hex number
364:44 hex number two zero zero zero
364:47 two zero zero zero in the second second example we're
364:49 in the second second example we're matching all addresses whose first 20
364:51 matching all addresses whose first 20 bits match the listed hex number and you
364:54 bits match the listed hex number and you can see in red
364:56 can see in red what match that would be
364:58 what match that would be and then the final example all addresses
365:00 and then the final example all addresses whose first 32 bits match the listed hex
365:03 whose first 32 bits match the listed hex number
365:10 here's another ipv6 address how do we break it out into subnets well here you
365:12 break it out into subnets well here you have it
365:13 have it we're honoring the first 48 bits of this
365:17 we're honoring the first 48 bits of this range and then we are breaking this out
365:19 range and then we are breaking this out into smaller subnets as you can see here
365:31 so here's what you've learned you've learned about some basic ip version 6
365:34 learned about some basic ip version 6 concepts and why you may want to upgrade
365:35 concepts and why you may want to upgrade to ipv6 beyond just for the reason of
365:38 to ipv6 beyond just for the reason of obtaining more ipa addresses you've also
365:41 obtaining more ipa addresses you've also learned about the addressing and how the
365:43 learned about the addressing and how the addressing can be abbreviated
365:46 addressing can be abbreviated i wish you the best of luck in your
365:47 i wish you the best of luck in your studies thank you
366:12 hi this is david voss ccie11372 and in this video
366:14 ccie11372 and in this video we're going to cover routing protocol
366:17 we're going to cover routing protocol concepts to introduce you to routing
366:19 concepts to introduce you to routing protocols for your ccda exam cisco wants
366:22 protocols for your ccda exam cisco wants you to be able to identify the
366:24 you to be able to identify the attributes of routing protocols so you
366:26 attributes of routing protocols so you can make the correct design decisions
366:29 can make the correct design decisions the fundamental question is which
366:31 the fundamental question is which routing protocol should you use
366:33 routing protocol should you use when answering that question you must
366:35 when answering that question you must keep in mind
366:36 keep in mind the following characteristics of routing
366:38 the following characteristics of routing protocols
366:40 protocols and cisco wants you to remember all of
366:42 and cisco wants you to remember all of these
366:43 these first is scalability how large is your
366:45 first is scalability how large is your network now
366:46 network now how large will it become
366:48 how large will it become this is important because there are
366:50 this is important because there are versions of rip or actually all versions
366:52 versions of rip or actually all versions of rip have a maximum hop count of 15
366:55 of rip have a maximum hop count of 15 routers
366:56 routers ospf and eigrp scale much better and bgp
367:00 ospf and eigrp scale much better and bgp is the primary routing protocol used on
367:02 is the primary routing protocol used on the internet so obviously it scales very
367:04 the internet so obviously it scales very well and many companies in fact use bgp
367:06 well and many companies in fact use bgp internally for that reason
367:09 internally for that reason vendor interoperability
367:11 vendor interoperability will you be using all cisco routers on
367:13 will you be using all cisco routers on your network or will be a blend of cisco
367:15 your network or will be a blend of cisco and non-cisco
367:17 and non-cisco why is that important well rip and ospf
367:20 why is that important well rip and ospf work fine regardless of vendor and now
367:23 work fine regardless of vendor and now even cisco has taken steps to ensure
367:25 even cisco has taken steps to ensure eigrp can be used by any networking
367:27 eigrp can be used by any networking vendor the question is do they support
367:30 vendor the question is do they support it rip and ospf and bgp most likely
367:34 it rip and ospf and bgp most likely eigrp maybe or maybe not by non-cisco
367:37 eigrp maybe or maybe not by non-cisco vendors
367:39 vendors it staffs familiarity with the protocol
367:42 it staffs familiarity with the protocol you and the it staff at your company
367:45 you and the it staff at your company might be much more familiar with one
367:47 might be much more familiar with one routing protocol over another
367:49 routing protocol over another i worked at a company where we had an
367:51 i worked at a company where we had an internal debate over eigrp versus ospf
367:56 internal debate over eigrp versus ospf and the tipping point for the
367:57 and the tipping point for the conversation was what protocols did the
367:59 conversation was what protocols did the engineers already know or want to learn
368:01 engineers already know or want to learn better
368:02 better it was ospf
368:04 it was ospf and therefore that's what we went with
368:05 and therefore that's what we went with as far as our design decision that was
368:07 as far as our design decision that was the tipping point
368:09 the tipping point you will have the same debates
368:10 you will have the same debates internally and should be prepared for
368:12 internally and should be prepared for this in your decision making process
368:15 this in your decision making process speed of convergence
368:17 speed of convergence a benefit of dynamic routing protocols
368:19 a benefit of dynamic routing protocols over static routes is the ability for
368:22 over static routes is the ability for dynamic routing protocols to reroute
368:24 dynamic routing protocols to reroute around network failures
368:25 around network failures when this failure occurs the network
368:28 when this failure occurs the network recalculates and reaches a steady state
368:30 recalculates and reaches a steady state condition this is called the state of
368:33 condition this is called the state of being a converged network
368:35 being a converged network the amount of time for the failure to
368:37 the amount of time for the failure to occur is called the convergence time
368:40 occur is called the convergence time now some routing protocols have faster
368:42 now some routing protocols have faster convergence times than others this is
368:44 convergence times than others this is important because when a network is not
368:47 important because when a network is not in a steady state data can be dropped or
368:49 in a steady state data can be dropped or looped within the network you should
368:51 looped within the network you should know that because rip and bgp might take
368:54 know that because rip and bgp might take up to a few minutes to converge by
368:56 up to a few minutes to converge by contrast ospf and eigrp can converge in
368:59 contrast ospf and eigrp can converge in just a few seconds
369:01 just a few seconds the capability to perform summarization
369:04 the capability to perform summarization large enterprise networks can have
369:06 large enterprise networks can have routing tables with
369:08 routing tables with many route entries and network
369:09 many route entries and network summarization allows multiple routes to
369:12 summarization allows multiple routes to then be summarized into a single route
369:14 then be summarized into a single route advertisement
369:16 advertisement so it reduces the number of entries in a
369:18 so it reduces the number of entries in a router's routing table that eats up less
369:20 router's routing table that eats up less memory and also cpu because it reduces
369:23 memory and also cpu because it reduces the number of network advertisements
369:25 the number of network advertisements that need to be sent
369:27 that need to be sent and that can obviously increase
369:28 and that can obviously increase convergence time as well
369:30 convergence time as well here's a perfect example let's say we're
369:32 here's a perfect example let's say we're looking at the routing table of a core
369:34 looking at the routing table of a core router and it knows about all the branch
369:36 router and it knows about all the branch offices and let's say there are
369:38 offices and let's say there are 255 branch offices and each are a lot of
369:40 255 branch offices and each are a lot of the slash 24 and they're assigned a
369:43 the slash 24 and they're assigned a 192.168
369:45 192.168 x.04 network now sure the core router
369:49 x.04 network now sure the core router has
369:50 has individual entries for all of these
369:52 individual entries for all of these routes and knows how to reach all of
369:54 routes and knows how to reach all of them through separate interfaces or
369:56 them through separate interfaces or tunnels
369:57 tunnels but all these routes do not need to be
369:59 but all these routes do not need to be passed individually throughout the
370:00 passed individually throughout the network onto a neighbor through a route
370:02 network onto a neighbor through a route advertisement they can be summarized
370:04 advertisement they can be summarized using one summary route
370:07 using one summary route 192.16800 16. so as you can see using
370:10 192.16800 16. so as you can see using summarization we're saving a lot of
370:13 summarization we're saving a lot of memory and cpu by simply summarizing
370:17 memory and cpu by simply summarizing all of these routes
370:19 all of these routes into one single route
370:26 interior or exterior routing a key term you need to understand is as
370:28 a key term you need to understand is as which stands for autonomous system and
370:31 which stands for autonomous system and this is a network under a single
370:33 this is a network under a single administrative control
370:35 administrative control a network
370:36 a network might be a single as and when it
370:38 might be a single as and when it connects to let's say another network
370:39 connects to let's say another network let's say an internet service provider
370:41 let's say an internet service provider then it's connecting to a separate as
370:44 then it's connecting to a separate as when you're selecting a routing protocol
370:45 when you're selecting a routing protocol you need to determine is it running
370:47 you need to determine is it running inside your network or will you be
370:49 inside your network or will you be running it with somebody outside of your
370:52 running it with somebody outside of your network
370:53 network to answer the question as to what
370:54 to answer the question as to what routing protocol you should run you need
370:56 routing protocol you should run you need to understand if you need an igp an
370:59 to understand if you need an igp an interior gateway protocol or a egp an
371:02 interior gateway protocol or a egp an exterior gateway protocol an igp
371:05 exterior gateway protocol an igp exchanges routes between routers in a
371:06 exchanges routes between routers in a single as
371:08 single as common igps are eigrp or ospf
371:12 common igps are eigrp or ospf and then rip and isis are also used but
371:14 and then rip and isis are also used but not as much
371:17 not as much today the only egp in use is bgp but
371:20 today the only egp in use is bgp but please note that bgp is sometimes also
371:23 please note that bgp is sometimes also used as an interior gateway protocol as
371:25 used as an interior gateway protocol as well
371:27 well there are two types of routing protocols
371:29 there are two types of routing protocols the first type is distance vector
371:32 the first type is distance vector distance vector routing protocols send a
371:34 distance vector routing protocols send a full copy of the router's routing table
371:37 full copy of the router's routing table to directly attach neighbors
371:40 to directly attach neighbors now obviously this is not very efficient
371:42 now obviously this is not very efficient because it's sending information to a
371:44 because it's sending information to a neighbor even if the neighbor already
371:46 neighbor even if the neighbor already has that information
371:48 has that information this can lead to slower convergence time
371:51 this can lead to slower convergence time with slow convergence time you then
371:54 with slow convergence time you then can introduce routing loops the routing
371:56 can introduce routing loops the routing protocols that are considered distance
371:58 protocols that are considered distance vector are rip and eigrp
372:00 vector are rip and eigrp there are two mechanisms that you can
372:02 there are two mechanisms that you can use to deal with routing loops that
372:05 use to deal with routing loops that cisco wants you to know
372:06 cisco wants you to know the first is split horizon
372:09 the first is split horizon this prevents a route learned on an
372:11 this prevents a route learned on an interface from being advertised back out
372:14 interface from being advertised back out that same interface i'll show you a
372:16 that same interface i'll show you a diagram in a minute so this makes more
372:17 diagram in a minute so this makes more sense and then there's poison reverse
372:19 sense and then there's poison reverse which causes a route received on one
372:21 which causes a route received on one interface
372:22 interface to then be advertised out the same
372:24 to then be advertised out the same interface with an infinite metric so
372:27 interface with an infinite metric so that nobody actually wants to use it
372:29 that nobody actually wants to use it but let's go ahead and take a look at
372:31 but let's go ahead and take a look at the diagram so we can better understand
372:33 the diagram so we can better understand the issue with routing loops and
372:35 the issue with routing loops and distance vector routing protocols and
372:37 distance vector routing protocols and then what we can do about it with split
372:38 then what we can do about it with split horizon or poison reverse
372:41 horizon or poison reverse as you can see here we have a basic
372:43 as you can see here we have a basic point-to-point network router one
372:44 point-to-point network router one connecting to router two over serial
372:46 connecting to router two over serial interface
372:47 interface and then a network one nine two one six
372:49 and then a network one nine two one six eight one
372:50 eight one dot zero slash twenty four
372:53 dot zero slash twenty four which is then advertised out serial 0
372:55 which is then advertised out serial 0 over to router 1.
372:58 over to router 1. router 1 then learns that
373:00 router 1 then learns that route and places it in its routing table
373:03 route and places it in its routing table as you can see here with a metric of one
373:06 as you can see here with a metric of one one hop now what if ethernet 0 on router
373:09 one hop now what if ethernet 0 on router 2 were to go down and the network were
373:11 2 were to go down and the network were no longer available the problem with
373:13 no longer available the problem with distance vector routing
373:14 distance vector routing is that router 1 is going to send its
373:17 is that router 1 is going to send its full routing table over to router 2.
373:20 full routing table over to router 2. while router 2 does not know about
373:22 while router 2 does not know about 192.168.1.0 anymore so when it receives
373:26 192.168.1.0 anymore so when it receives the subnet advertisement
373:28 the subnet advertisement from router 1 of 192.168.1.0
373:31 from router 1 of 192.168.1.0 it's going to accept it and place it in
373:34 it's going to accept it and place it in its routing table with a metric of two
373:38 its routing table with a metric of two and this is where we introduce routing
373:40 and this is where we introduce routing loops router two will then forward
373:42 loops router two will then forward traffic over to router one router one
373:44 traffic over to router one router one thinks it can reach that network via
373:46 thinks it can reach that network via router two and traffic will then loop
373:49 router two and traffic will then loop between the two routers
373:50 between the two routers this obviously is not ideal now you've
373:53 this obviously is not ideal now you've already learned about the two solutions
373:55 already learned about the two solutions to deal with that and you'll need to
373:56 to deal with that and you'll need to know it for your ccmp exam split horizon
373:59 know it for your ccmp exam split horizon will prevent a route learned on an
374:01 will prevent a route learned on an interface but from being advertised back
374:03 interface but from being advertised back out that same interface
374:04 out that same interface and then poison reverse which causes a
374:07 and then poison reverse which causes a route received on one interface to be
374:08 route received on one interface to be advertised out that same interface with
374:11 advertised out that same interface with an infinite metric
374:17 the next type of routing protocol you need to be aware of is the link state
374:18 need to be aware of is the link state routing protocol
374:20 routing protocol routers send link state advertisements
374:23 routers send link state advertisements or lsa to advertise the networks they
374:25 or lsa to advertise the networks they know how to reach
374:27 know how to reach so they don't send the full routing
374:29 so they don't send the full routing table just the networks they know how to
374:30 table just the networks they know how to reach and only when there is a change in
374:33 reach and only when there is a change in the topology
374:35 the topology they only exchange full routing
374:37 they only exchange full routing information when two routers initially
374:39 information when two routers initially form their adjacency but from there on
374:42 form their adjacency but from there on out it's on a need to know basis
374:44 out it's on a need to know basis the routing protocols that are link
374:46 the routing protocols that are link state routing protocols are ospf and
374:48 state routing protocols are ospf and isis
374:51 isis and the final type of routing protocol
374:52 and the final type of routing protocol you need to know is path vector bgp is
374:55 you need to know is path vector bgp is path vector and it includes information
374:58 path vector and it includes information not just about the neighbor but the
375:00 not just about the neighbor but the exact path that packets take to reach a
375:03 exact path that packets take to reach a specific destination network so when you
375:06 specific destination network so when you do look at bgpu advertisements you can
375:08 do look at bgpu advertisements you can see exactly over what autonomous systems
375:12 see exactly over what autonomous systems that traffic is flowing over
375:14 that traffic is flowing over so you've learned about the role of
375:16 so you've learned about the role of routing in an enterprise network and the
375:18 routing in an enterprise network and the different layers of enterprise network
375:20 different layers of enterprise network design and then you learn the basic
375:22 design and then you learn the basic characteristics of routing protocols
375:24 characteristics of routing protocols which is really going to help you as you
375:26 which is really going to help you as you solidify your foundation
375:28 solidify your foundation and now you move forward in your ccmp
375:30 and now you move forward in your ccmp studies i'm sure you're going to do
375:32 studies i'm sure you're going to do great and continue on with the video
375:33 great and continue on with the video series and good luck to you in your
375:35 series and good luck to you in your studies
375:59 hi this is david voss ccie11372 and in this video you're going
376:02 ccie11372 and in this video you're going to learn about
376:03 to learn about rip design
376:05 rip design specifically we're going to
376:06 specifically we're going to first learn about rip version one so you
376:09 first learn about rip version one so you can lay a foundation for understanding
376:12 can lay a foundation for understanding rip version two
376:13 rip version two since that is the version most commonly
376:15 since that is the version most commonly used today and if you were to design a
376:17 used today and if you were to design a network using rip most likely that would
376:20 network using rip most likely that would be the version you would choose
376:22 be the version you would choose so let's begin with rip version one
376:26 so let's begin with rip version one now the major drawback of rip version
376:29 now the major drawback of rip version one and why many don't use it today is
376:31 one and why many don't use it today is that it has classful behavior meaning
376:34 that it has classful behavior meaning that it does not send back subnet mask
376:37 that it does not send back subnet mask information
376:39 information now if there is no subnet mask
376:41 now if there is no subnet mask information in the updates
376:43 information in the updates then it assumes that any network is
376:46 then it assumes that any network is staying within its class full boundary
376:50 staying within its class full boundary which in as you know in most networks
376:52 which in as you know in most networks today that's rare
376:54 today that's rare as you can see here each class has a
376:57 as you can see here each class has a range of ip addresses that it would
376:59 range of ip addresses that it would support
377:00 support and if it were to remain on classful
377:03 and if it were to remain on classful boundaries that would mean that you
377:04 boundaries that would mean that you would not be able to provide vlsm or
377:08 would not be able to provide vlsm or break down these
377:10 break down these assigned subnets into
377:12 assigned subnets into smaller subnets
377:14 smaller subnets so for example if you were assigned a
377:17 so for example if you were assigned a network in the class a range let's say a
377:20 network in the class a range let's say a 10 dot network you would not be able to
377:23 10 dot network you would not be able to break your 10 dot network down into
377:25 break your 10 dot network down into smaller subnets so
377:27 smaller subnets so later in this video we will talk about
377:29 later in this video we will talk about auto summarization and that if it
377:31 auto summarization and that if it summarizes on a classful boundary
377:34 summarizes on a classful boundary specifically with 10 dot networks you
377:37 specifically with 10 dot networks you can have routing problems
377:39 can have routing problems so often you will find that you will
377:41 so often you will find that you will want to turn off auto summarization in
377:43 want to turn off auto summarization in rip version 2.
377:45 rip version 2. another issue with rip version 1 is that
377:47 another issue with rip version 1 is that it broadcasts updates
377:50 it broadcasts updates so it uses unnecessary bandwidth but it
377:53 so it uses unnecessary bandwidth but it also means that routers that are not
377:55 also means that routers that are not even running rip will constantly receive
377:58 even running rip will constantly receive rip updates even though they won't
378:00 rip updates even though they won't process them
378:01 process them because routers that run rip will
378:03 because routers that run rip will broadcast and mount all interfaces
378:06 broadcast and mount all interfaces modern routing protocols use a multicast
378:09 modern routing protocols use a multicast approach in order to solve this issue
378:11 approach in order to solve this issue by sending updates only to routers that
378:13 by sending updates only to routers that really need to receive them
378:16 really need to receive them rip version 1 does not allow
378:18 rip version 1 does not allow authentication
378:20 authentication so there is no element of security that
378:21 so there is no element of security that can be added to the routing protocol
378:24 can be added to the routing protocol to ensure that it is not sending
378:25 to ensure that it is not sending information to devices that should not
378:28 information to devices that should not receive it
378:30 receive it when examining rip version 2 you can see
378:33 when examining rip version 2 you can see that many of version 1 shortcomings have
378:35 that many of version 1 shortcomings have been addressed
378:37 been addressed rip version 2 has a classless behavior
378:40 rip version 2 has a classless behavior meaning that subnet mask information is
378:42 meaning that subnet mask information is sent in updates so vlsm can be achieved
378:47 sent in updates so vlsm can be achieved version 2 also supports authentication
378:50 version 2 also supports authentication to ensure that the person you are
378:52 to ensure that the person you are sending the information to is the person
378:54 sending the information to is the person authorized to receive that information
378:58 authorized to receive that information now in addition to plain text passwords
379:00 now in addition to plain text passwords the cisco implementation
379:03 the cisco implementation provides the ability to use md5
379:05 provides the ability to use md5 authentication
379:07 authentication md5
379:08 md5 is a hashing algorithm that takes a
379:10 is a hashing algorithm that takes a variable length string of text and
379:13 variable length string of text and produces a fixed length 128 bit output
379:17 produces a fixed length 128 bit output the advantage of hashtag plain text is
379:20 the advantage of hashtag plain text is that the original message
379:21 that the original message cannot be reconstructed even with the
379:24 cannot be reconstructed even with the knowledge of the hash algorithm
379:27 knowledge of the hash algorithm now with regards to advertisements rip
379:30 now with regards to advertisements rip version 2 multicasts routing updates
379:33 version 2 multicasts routing updates instead of broadcasting them as rip
379:35 instead of broadcasting them as rip version 1 does
379:36 version 1 does so this allows for the efficient
379:38 so this allows for the efficient exchange of routing updates
379:41 exchange of routing updates another special feature of version 2 is
379:44 another special feature of version 2 is automatic summarization feature
379:47 automatic summarization feature which is applied to prefixes on classful
379:49 which is applied to prefixes on classful boundaries
379:51 boundaries this behavior is a double-edged sword
379:54 this behavior is a double-edged sword because it can induce problems in real
379:56 because it can induce problems in real world scenarios
379:58 world scenarios let's look at the following example
380:01 let's look at the following example router 1 connects to the following
380:03 router 1 connects to the following networks
380:04 networks 10.10.10.0 and 10.10.20.0
380:07 10.10.10.0 and 10.10.20.0 and
380:08 and 10.10.30.0
380:10 10.10.30.0 router 1 connects to router 2 and then
380:12 router 1 connects to router 2 and then onto router 3 which has connectivity to
380:14 onto router 3 which has connectivity to the 10.40.0
380:16 the 10.40.0 and
380:18 and 10.10.50.0 networks
380:20 10.10.50.0 networks there are also other networks between
380:21 there are also other networks between the routers such as 172.1600
380:25 the routers such as 172.1600 and 192.168.000
380:28 and 192.168.000 notice the change in classful boundaries
380:30 notice the change in classful boundaries that makes rip automatically summarize
380:32 that makes rip automatically summarize the networks behind router 1 and router
380:35 the networks behind router 1 and router 3
380:36 3 as 10.0.0.0.8
380:41 toward router 2. this can lead to a problem or it will
380:43 this can lead to a problem or it will lead to a problem router 2 will receive
380:46 lead to a problem router 2 will receive the same route from both directions
380:48 the same route from both directions if it receives a packet destin for
380:50 if it receives a packet destin for 10.10.10.0
380:53 10.10.10.0 it can send it in both directions based
380:55 it can send it in both directions based on the automatically summarized prefixes
380:57 on the automatically summarized prefixes it received
380:59 it received this problem is called discontiguous
381:02 this problem is called discontiguous subnets
381:03 subnets and it's generated by the automatic
381:05 and it's generated by the automatic summarization behavior of the routing
381:07 summarization behavior of the routing protocol that aggregates those subnets
381:11 protocol that aggregates those subnets solutions for this problem involve not
381:14 solutions for this problem involve not using discontiguous subnets in different
381:16 using discontiguous subnets in different areas in the network topology
381:19 areas in the network topology or
381:19 or disabling auto summarization
381:23 disabling auto summarization let's take a look at the rip version 2
381:25 let's take a look at the rip version 2 message format
381:26 message format the rib version 2 message format takes
381:28 the rib version 2 message format takes advantage of the unused fields in the
381:30 advantage of the unused fields in the version 1 message format by adding
381:33 version 1 message format by adding subnet masks and other information
381:36 subnet masks and other information let's go through some of the key
381:38 let's go through some of the key attributes of this message
381:42 attributes of this message the command field indicates whether the
381:44 the command field indicates whether the packet is a request or response message
381:47 packet is a request or response message the request message asks that a router
381:49 the request message asks that a router send all or part of its routing table
381:52 send all or part of its routing table response messages contain route entries
381:55 response messages contain route entries the router sends the response
381:57 the router sends the response periodically or as a reply to a request
382:01 periodically or as a reply to a request version specifies the rip version used
382:04 version specifies the rip version used 2 for rip version 2 and 1 for rip
382:06 2 for rip version 2 and 1 for rip version 1.
382:08 version 1. afi field specifies the address family
382:12 afi field specifies the address family used
382:13 used rip is designed to carry routing
382:15 rip is designed to carry routing information for several different
382:17 information for several different protocols
382:18 protocols each entry has an afi to indicate the
382:21 each entry has an afi to indicate the type of address specified
382:23 type of address specified the afi for ip is 2.
382:31 route tag route tags provide a method for distinguishing between internal
382:33 for distinguishing between internal routes which are learned by rip and
382:36 routes which are learned by rip and external routes which are learned from
382:37 external routes which are learned from other routing protocols
382:39 other routing protocols you can add this optional attribute
382:41 you can add this optional attribute during the redistribution of routing
382:43 during the redistribution of routing protocols
382:45 protocols ip address specifies the ip address of
382:48 ip address specifies the ip address of the destination
382:50 the destination subnet mask contains the subnet mask for
382:53 subnet mask contains the subnet mask for the destination now if this field is
382:55 the destination now if this field is zero no subnet mask has been specified
382:58 zero no subnet mask has been specified for the entry
383:00 for the entry next hop indicates the ip address of the
383:02 next hop indicates the ip address of the next hop where packets are sent to reach
383:04 next hop where packets are sent to reach the destination
383:06 the destination and metric indicates how many router
383:08 and metric indicates how many router hops to reach the destination
383:10 hops to reach the destination the metric is always going to be between
383:12 the metric is always going to be between 1 and 15 for a valid route
383:15 1 and 15 for a valid route since 16 would indicate an unreasonable
383:17 since 16 would indicate an unreasonable unreachable or infinite route
383:24 another aspect about rip that you need to know is that it relies on a series of
383:26 to know is that it relies on a series of timers for its operations
383:29 timers for its operations as described here
383:31 as described here the update timer this is where updates
383:33 the update timer this is where updates are sent and they're sent every 30
383:35 are sent and they're sent every 30 seconds by default
383:37 seconds by default invalid the route is invalidated if no
383:40 invalid the route is invalidated if no update was received before this timer
383:42 update was received before this timer expires
383:43 expires flush timer determines the time a route
383:45 flush timer determines the time a route gets flushed from the rip table
383:48 gets flushed from the rip table and hold down timer updates are not
383:50 and hold down timer updates are not accepted for a route that keeps getting
383:52 accepted for a route that keeps getting a bad metric
383:54 a bad metric and finally
383:56 and finally the sleep timer which can add delay to
383:58 the sleep timer which can add delay to triggered updates
384:01 triggered updates the hold down and sleep timers are cisco
384:03 the hold down and sleep timers are cisco specific and are used to enhance the rip
384:06 specific and are used to enhance the rip functionality
384:07 functionality they were not originally specified in
384:09 they were not originally specified in the rfcs for rip
384:11 the rfcs for rip in summary here are some key points
384:13 in summary here are some key points about rip version 2 that you need to
384:15 about rip version 2 that you need to memorize for your ccda exam
384:17 memorize for your ccda exam it's a distance vector protocol which
384:19 it's a distance vector protocol which uses udp port 520
384:22 uses udp port 520 it does not scale well since the maximum
384:24 it does not scale well since the maximum hop count is 15.
384:26 hop count is 15. periodic route updates are sent every 30
384:29 periodic route updates are sent every 30 seconds to a multicast address
384:32 seconds to a multicast address 25 routes are allowed per rip message or
384:34 25 routes are allowed per rip message or 24 if you're using authentication
384:37 24 if you're using authentication and obviously it supports authentication
384:40 and obviously it supports authentication subnet mask is included in every route
384:43 subnet mask is included in every route entry
384:44 entry it's a classless protocol
384:46 it's a classless protocol it does support vlsm
384:49 it does support vlsm and the metric for
384:51 and the metric for version 2 is router hop count
384:54 version 2 is router hop count now all of these points you need to
384:56 now all of these points you need to memorize for your ccda exam this video
384:58 memorize for your ccda exam this video has given you a good base foundation for
385:02 has given you a good base foundation for preparations for your ccda if you can
385:04 preparations for your ccda if you can memorize what you've learned in this
385:06 memorize what you've learned in this video you should do very well when asked
385:08 video you should do very well when asked questions about rip and how and when you
385:11 questions about rip and how and when you would use it in a network design good
385:14 would use it in a network design good luck in your studies
385:40 hi this is david voss ccie11372 and in this video you're going to learn
385:41 and in this video you're going to learn about eigrp design
385:44 about eigrp design we're going to do a high-level eigrp
385:46 we're going to do a high-level eigrp overview
385:48 overview in this video
385:49 in this video and then we're going to talk about the
385:51 and then we're going to talk about the eigrp components you're going to see
385:52 eigrp components you're going to see this constant theme of these four
385:54 this constant theme of these four components
385:56 components so first there are eigrp messages that
385:59 so first there are eigrp messages that are unique to eigrp there's a unique
386:02 are unique to eigrp there's a unique eigrp algorithm
386:05 eigrp algorithm there are tables that are again unique
386:07 there are tables that are again unique to eigrp that you need to know about
386:10 to eigrp that you need to know about and then finally you need to know that
386:12 and then finally you need to know that eigrp supports
386:15 eigrp supports independent modules
386:17 independent modules so there are multiple there's multiple
386:19 so there are multiple there's multiple support for
386:20 support for multiple different network layer
386:22 multiple different network layer protocols
386:28 now the way we're going to approach this is
386:30 the way we're going to approach this is again it's a high level overview of
386:32 again it's a high level overview of concepts that are unique to eigrp so we
386:36 concepts that are unique to eigrp so we all know that eigrp can support vlsm for
386:39 all know that eigrp can support vlsm for example but many routing protocols can
386:41 example but many routing protocols can so we're not going to dig into vlsm and
386:43 so we're not going to dig into vlsm and eigrp we're going to talk about things
386:45 eigrp we're going to talk about things that are unique to eigrp
386:47 that are unique to eigrp now for to understand eigrp we first
386:49 now for to understand eigrp we first need to understand igrp igrp came out in
386:52 need to understand igrp igrp came out in 1986
386:54 1986 it is an interior gateway protocol that
386:56 it is an interior gateway protocol that was once very popular
386:59 was once very popular distance vector a distance vector
387:01 distance vector a distance vector routing protocol
387:03 routing protocol and
387:04 and it used four key attributes to develop
387:09 it used four key attributes to develop this distance information on how to
387:11 this distance information on how to choose the best path
387:13 choose the best path so it looked at the link
387:15 so it looked at the link and then it said how much available
387:17 and then it said how much available bandwidth is there
387:19 bandwidth is there how much delay how much load and how
387:22 how much delay how much load and how much link reliability is there on this
387:24 much link reliability is there on this link path or on the multiple links to my
387:26 link path or on the multiple links to my path
387:28 path well
387:29 well e-i-g-r-p
387:32 e-i-g-r-p is still an interior gateway protocol
387:36 is still an interior gateway protocol and it is still a distance vector
387:38 and it is still a distance vector protocol although
387:40 protocol although many times in the past it had been
387:42 many times in the past it had been referred to as hybrid but those days are
387:44 referred to as hybrid but those days are pretty much gone
387:46 pretty much gone distance vector is what it's classified
387:48 distance vector is what it's classified as
387:49 as but it has can improve convergence in
387:51 but it has can improve convergence in operations so
387:53 operations so it uses the dual diffusing update
387:55 it uses the dual diffusing update algorithm and i'll show you about that
387:58 algorithm and i'll show you about that in a few minutes and then again it has
388:00 in a few minutes and then again it has multiple unique tables eigrp
388:03 multiple unique tables eigrp which assists in the operations and
388:06 which assists in the operations and enhances the operations
388:08 enhances the operations and then again it supports multiple
388:10 and then again it supports multiple network layer protocols
388:16 so how does eigrp actually work well i'll tell you what let's go ahead
388:17 well i'll tell you what let's go ahead and open up the hood and take a look
388:19 and open up the hood and take a look underneath eigrp has four basic
388:21 underneath eigrp has four basic components and these should already
388:23 components and these should already start looking familiar to you it has
388:25 start looking familiar to you it has messages so messages flow to and from
388:27 messages so messages flow to and from neighbors eigrp neighbors there's five
388:30 neighbors eigrp neighbors there's five different types we'll dig into that in a
388:32 different types we'll dig into that in a little bit
388:33 little bit eigrp has the dual algorithm the dual
388:36 eigrp has the dual algorithm the dual algorithm takes the information from
388:38 algorithm takes the information from those messages and then processes
388:41 those messages and then processes best path and possible best path
388:44 best path and possible best path then all the information from the
388:46 then all the information from the messages and the algorithms get
388:49 messages and the algorithms get put into tables so these eigrp tables
388:52 put into tables so these eigrp tables hold the data
388:54 hold the data from the algorithm and the messages and
388:56 from the algorithm and the messages and then finally the modules these protocol
388:59 then finally the modules these protocol dependent modules
389:01 dependent modules support a variety of network layer
389:03 support a variety of network layer protocols so we're not limited eigrp is
389:07 protocols so we're not limited eigrp is not limited to just ip
389:14 so with regards to messages there are different types of packet formats
389:15 different types of packet formats there's five different types of packet
389:17 there's five different types of packet formats
389:18 formats first there's the hello message a hello
389:21 first there's the hello message a hello message is basically a query out to
389:23 message is basically a query out to anybody who'll listen asking if
389:26 anybody who'll listen asking if anybody's out there so our router
389:27 anybody's out there so our router running eigrp sends hello packets by
389:30 running eigrp sends hello packets by default and it will send those packets
389:33 default and it will send those packets out and hope for a return reply and when
389:36 out and hope for a return reply and when it gets a return reply it'll get that
389:38 it gets a return reply it'll get that update and that update contains all the
389:41 update and that update contains all the messages or all the routes that want to
389:43 messages or all the routes that want to be shared via eigrp
389:45 be shared via eigrp update messages are messages with a lot
389:47 update messages are messages with a lot of routing information in them
389:50 of routing information in them and then there's the acknowledgement
389:51 and then there's the acknowledgement message which surely you know about from
389:53 message which surely you know about from other protocols but it's simply
389:54 other protocols but it's simply acknowledging that yes i've received
389:56 acknowledging that yes i've received your message
389:57 your message and that's key to the reliable nature of
389:59 and that's key to the reliable nature of eigrp which we'll talk about in a minute
390:02 eigrp which we'll talk about in a minute there's a query message so if eigrp
390:05 there's a query message so if eigrp loses a route and does not know how to
390:07 loses a route and does not know how to get there anymore it will query its
390:10 get there anymore it will query its neighbors saying do you have any
390:11 neighbors saying do you have any information about this route because i'd
390:13 information about this route because i'd like to get that information
390:16 like to get that information and then if a router does have
390:17 and then if a router does have information on that route or on that
390:19 information on that route or on that path it will reply back saying yes
390:22 path it will reply back saying yes i do have information and here it is
390:26 i do have information and here it is so these five messages can be broken out
390:29 so these five messages can be broken out into two categories some that are
390:31 into two categories some that are reliable and some that are not reliable
390:34 reliable and some that are not reliable the reliable messages are use reliable
390:36 the reliable messages are use reliable transport protocol
390:38 transport protocol and this is unique to eigrp but rtp
390:41 and this is unique to eigrp but rtp basically makes sure that packets
390:43 basically makes sure that packets get to where they're supposed to go in
390:45 get to where they're supposed to go in order so an unreliable packet is a hello
390:48 order so an unreliable packet is a hello message
390:50 message that message is not reliable but the
390:52 that message is not reliable but the update message from an eigrp router does
390:55 update message from an eigrp router does use rtp
390:57 use rtp so it is sequenced and there are
390:59 so it is sequenced and there are acknowledgments so there is an
391:01 acknowledgments so there is an acknowledgement to that message but the
391:03 acknowledgement to that message but the acknowledgement itself is not reliable
391:07 acknowledgement itself is not reliable then there's the query message remember
391:08 then there's the query message remember the query is to ask do you have
391:10 the query is to ask do you have information about this route
391:12 information about this route and that is that uses rtp and the
391:15 and that is that uses rtp and the response to that query the reply also
391:17 response to that query the reply also uses rtp
391:19 uses rtp so three different types of messages use
391:21 so three different types of messages use rtp the update the query and the reply
391:24 rtp the update the query and the reply and i think that's critical to know for
391:26 and i think that's critical to know for your exam
391:28 your exam now let's talk about the eigrp algorithm
391:30 now let's talk about the eigrp algorithm which is dual now to understand dual you
391:32 which is dual now to understand dual you need to understand what successor and
391:34 need to understand what successor and feasible successor routes are i think
391:36 feasible successor routes are i think when you think of successor just think
391:38 when you think of successor just think of success that's the best path
391:40 of success that's the best path so if eigrp loses connectivity to the
391:43 so if eigrp loses connectivity to the best path
391:44 best path it will then
391:45 it will then run the dual algorithm
391:48 run the dual algorithm and ask is there a feasible successor is
391:51 and ask is there a feasible successor is there a second best path
391:54 there a second best path and if the dual algorithm states yes
391:58 and if the dual algorithm states yes there is a feasible successor a second
392:00 there is a feasible successor a second best path it will then promote
392:03 best path it will then promote that second best path to the to to the
392:06 that second best path to the to to the best path so that becomes the successor
392:10 best path so that becomes the successor once it's it's the successor it is then
392:13 once it's it's the successor it is then installed into the routing table so for
392:16 installed into the routing table so for example it would be installed into the
392:17 example it would be installed into the ip routing table
392:19 ip routing table and then the router would begin to use
392:22 and then the router would begin to use that new path
392:23 that new path so this chart gives you an overview of
392:26 so this chart gives you an overview of base a high-level overview of how the
392:28 base a high-level overview of how the dual algorithm runs
392:30 dual algorithm runs but it's important to know these
392:32 but it's important to know these concepts
392:33 concepts of successor and feasible successor as
392:36 of successor and feasible successor as you move forward with eigrp and how dual
392:39 you move forward with eigrp and how dual uses that information
392:41 uses that information now eigrp uses specific tables to help
392:45 now eigrp uses specific tables to help make it run and one of the tables that
392:48 make it run and one of the tables that eigrp uses is called a neighbor table
392:51 eigrp uses is called a neighbor table now a neighbor table is exactly what you
392:53 now a neighbor table is exactly what you think it is it's a table that is
392:55 think it is it's a table that is comprised of a listing of all the eigrp
392:59 comprised of a listing of all the eigrp neighbors so
393:00 neighbors so for example we have a hub and spoke
393:02 for example we have a hub and spoke design here we have router a
393:04 design here we have router a router b and router c
393:06 router b and router c and router a and router b are both
393:09 and router a and router b are both running eigrp
393:11 running eigrp router a sends out a hello packet and
393:13 router a sends out a hello packet and router b responds back as well and
393:15 router b responds back as well and they've established a neighbor
393:17 they've established a neighbor relationship and router a sends out a
393:18 relationship and router a sends out a hello packet rudder c does the same and
393:21 hello packet rudder c does the same and they've established their eigrp neighbor
393:23 they've established their eigrp neighbor relationship
393:24 relationship so once that happens router a begins to
393:27 so once that happens router a begins to build out its neighbor table
393:29 build out its neighbor table by identifying each router that each
393:32 by identifying each router that each neighbor by ip address so
393:35 neighbor by ip address so for example router b is 172 16
393:38 for example router b is 172 16 1.1 and he gets placed into the neighbor
393:42 1.1 and he gets placed into the neighbor table
393:43 table and then router c is 192.168.10.2
393:50 and he is placed in the router table as well
393:52 well so
393:53 so router a now has two neighbors and they
393:55 router a now has two neighbors and they are both listed in its neighbor table
393:59 are both listed in its neighbor table but there's also other information in
394:00 but there's also other information in the neighbor table as well
394:03 the neighbor table as well and it
394:04 and it the router a also wants to know what
394:06 the router a also wants to know what interface are these routers
394:08 interface are these routers off of so router b is off of serial one
394:12 off of so router b is off of serial one router c is off of serial two so should
394:15 router c is off of serial two so should i need to forward them
394:17 i need to forward them traffic or i know exactly which
394:20 traffic or i know exactly which interface they will be exiting
394:22 interface they will be exiting and then finally
394:24 and then finally there's
394:25 there's other information that is entered into
394:27 other information that is entered into the neighbor table there's quite a bit
394:29 the neighbor table there's quite a bit actually but for the sake of this high
394:31 actually but for the sake of this high level overview let's just talk about
394:33 level overview let's just talk about hold time because this is a key concept
394:35 hold time because this is a key concept when you program hold time on a router
394:38 when you program hold time on a router it's not local you're not changing the
394:40 it's not local you're not changing the whole time locally that information is
394:42 whole time locally that information is actually forwarded over to
394:44 actually forwarded over to your neighbor router so here we have
394:46 your neighbor router so here we have router c
394:48 router c who's changed his hold time to 10
394:50 who's changed his hold time to 10 seconds he forwards that over to router
394:52 seconds he forwards that over to router a
394:53 a and here we have router b
394:55 and here we have router b and let's say he's going to change his
394:57 and let's say he's going to change his hold time
394:58 hold time this information that they're changing
395:01 this information that they're changing from the default it gets inserted into
395:03 from the default it gets inserted into the neighbor table on router a
395:06 the neighbor table on router a and remember hold time is basically
395:08 and remember hold time is basically telling the router if you don't hear
395:09 telling the router if you don't hear from me in this amount of time
395:12 from me in this amount of time consider me down and flush the routes
395:14 consider me down and flush the routes that you receive from me
395:16 that you receive from me so it's important to remember hold time
395:18 so it's important to remember hold time is configured on router c and router b
395:22 is configured on router c and router b but the actual numeric
395:24 but the actual numeric change occurs on router a in the
395:27 change occurs on router a in the neighbor table
395:28 neighbor table now there's definitely other attributes
395:30 now there's definitely other attributes that are in the neighbor table
395:32 that are in the neighbor table and we will definitely go over those in
395:33 and we will definitely go over those in future videos but on a high level
395:35 future videos but on a high level overview of eigrp you need to know about
395:39 overview of eigrp you need to know about the ip the interface and the hold time
395:41 the ip the interface and the hold time counter and just remember hold time
395:44 counter and just remember hold time defaults
395:45 defaults are is 180 seconds
395:47 are is 180 seconds for low bandwidth links and 15 seconds
395:50 for low bandwidth links and 15 seconds for t1 or higher
395:52 for t1 or higher so
395:53 so that'll come up again again and you'll
395:55 that'll come up again again and you'll probably be asked about that as well
395:57 probably be asked about that as well but there are other eigrp tables that
395:59 but there are other eigrp tables that you should also be aware of
396:02 you should also be aware of and a key table to know about is the
396:04 and a key table to know about is the topology table topology table contains
396:07 topology table topology table contains all destinations advertised by
396:08 all destinations advertised by neighboring routers
396:10 neighboring routers this includes remember the successor and
396:13 this includes remember the successor and feasible successor routes the best path
396:15 feasible successor routes the best path to a destination and the next best path
396:18 to a destination and the next best path respectively
396:19 respectively so topology table is key for eigrp to
396:23 so topology table is key for eigrp to run now remember within topology table
396:25 run now remember within topology table you can see the route tag so in eigrp
396:27 you can see the route tag so in eigrp you can actually perform route tagging
396:30 you can actually perform route tagging and all you really need to know for now
396:32 and all you really need to know for now is that you can identify routes by their
396:34 is that you can identify routes by their origination
396:35 origination which allows for custom routing so you
396:36 which allows for custom routing so you can tag those routes with a manual entry
396:40 can tag those routes with a manual entry so that's all you really need to know
396:41 so that's all you really need to know for now
396:43 for now but getting back to eigrp tables
396:46 but getting back to eigrp tables now here's an example we have again a
396:49 now here's an example we have again a hub and spoke design
396:50 hub and spoke design router a router b and router c now
396:54 router a router b and router c now router a is going to build out as soon
396:55 router a is going to build out as soon as it enables eigrp it's going to build
396:57 as it enables eigrp it's going to build out these eigrp tables and one of the
397:00 out these eigrp tables and one of the tables again is going to be this
397:02 tables again is going to be this topology table
397:05 topology table the topology table is going to contain
397:07 the topology table is going to contain critical information for eigrp to run
397:10 critical information for eigrp to run and make the choices upon what the
397:13 and make the choices upon what the best path is going to be
397:15 best path is going to be so
397:16 so in the topology table it's going to
397:18 in the topology table it's going to insert routes that it learns from router
397:21 insert routes that it learns from router b and router c and then
397:25 b and router c and then it's going to ask
397:26 it's going to ask now that i know about this route which
397:28 now that i know about this route which neighbor did i learn it from
397:30 neighbor did i learn it from and then finally it's going to say
397:34 and then finally it's going to say i know the route i know the neighbor i
397:36 i know the route i know the neighbor i learned from
397:37 learned from what metric should i assign to it which
397:39 what metric should i assign to it which way should i send traffic or forward
397:41 way should i send traffic or forward traffic
397:43 traffic so
397:44 so in this example
397:46 in this example the route itself let's say we'll do a
397:48 the route itself let's say we'll do a 10.1.1.0
397:54 24 and let's say we learn this route from
397:56 and let's say we learn this route from both router b
397:59 both router b and from router c
398:07 so this topology table is filled out with two entries
398:09 with two entries for the same route
398:11 for the same route again this is not the routing table yet
398:13 again this is not the routing table yet this is a topology table
398:15 this is a topology table and it has a metric so let's keep it
398:17 and it has a metric so let's keep it simple so the metric to router b is 10
398:20 simple so the metric to router b is 10 and their metric to router c is 20.
398:23 and their metric to router c is 20. so
398:24 so for this simple example let's just say
398:27 for this simple example let's just say that
398:28 that the router now realizes that the
398:30 the router now realizes that the successor route the best route
398:33 successor route the best route is going to be
398:34 is going to be the path
398:35 the path through
398:36 through router b
398:39 router b now once the dual algorithm has run and
398:41 now once the dual algorithm has run and it realizes this it then takes
398:44 it realizes this it then takes that route or that path
398:47 that route or that path and it places the successor route into
398:50 and it places the successor route into the routing table in this case the ip
398:53 the routing table in this case the ip routing table
398:56 routing table so now we know the successor is to
398:58 so now we know the successor is to router b and the feasible successor path
399:01 router b and the feasible successor path is to router c
399:07 so as we can see it's going to choose
399:09 it's going to choose the path out to router b
399:11 the path out to router b now what happens
399:14 now what happens if this route information is lost
399:18 if this route information is lost and
399:20 and router a no longer learns about this
399:23 router a no longer learns about this this route from router b or from router
399:26 this route from router b or from router c and it gets flushed well router a what
399:29 c and it gets flushed well router a what he's going to do
399:30 he's going to do is he's going to send a query
399:32 is he's going to send a query to router b
399:34 to router b and to router c
399:36 and to router c asking do you know
399:38 asking do you know about this route because i've lost it
399:41 about this route because i've lost it and i'm hoping you have information on
399:43 and i'm hoping you have information on it
399:44 it and
399:46 and the neighbors will respond back but
399:48 the neighbors will respond back but specifically
399:50 specifically let's say in this case
399:52 let's say in this case that router c is the only one that knows
399:54 that router c is the only one that knows about it
399:55 about it router c will respond yes i'm aware of
399:58 router c will respond yes i'm aware of it and it will send the information over
400:01 it and it will send the information over and router a will say thank you very
400:03 and router a will say thank you very much
400:04 much and router a will then insert it into
400:05 and router a will then insert it into the topology table it will become the
400:08 the topology table it will become the successor and once it's to the successor
400:10 successor and once it's to the successor it will be placed into the routing table
400:13 it will be placed into the routing table and then router a
400:14 and then router a will then begin using the path through
400:17 will then begin using the path through router c to reach that subnet
400:21 router c to reach that subnet and last but certainly not least we have
400:22 and last but certainly not least we have protocol dependent modules so eigrp
400:26 protocol dependent modules so eigrp and the dual algorithm
400:28 and the dual algorithm function in a way that protocols can run
400:30 function in a way that protocols can run and use eigrp independently of one
400:32 and use eigrp independently of one another so ip builds out its own
400:35 another so ip builds out its own neighboring topology tables ipx and
400:37 neighboring topology tables ipx and apple talk they all build out their own
400:39 apple talk they all build out their own neighbor and topology tables and dual
400:42 neighbor and topology tables and dual can work with any and all of them
400:45 can work with any and all of them so you've learned a lot in this video
400:46 so you've learned a lot in this video that will help you with eigrp design
400:49 that will help you with eigrp design we've done an overview and we've talked
400:50 we've done an overview and we've talked about the individual components of eigrp
400:53 about the individual components of eigrp messages algorithms tables and modules
400:56 messages algorithms tables and modules you'll need to know all this information
400:57 you'll need to know all this information not only to design eigrp but obviously
401:00 not only to design eigrp but obviously to do very well on the ccda exam
401:03 to do very well on the ccda exam if you study what's in this video and
401:05 if you study what's in this video and know it well i'm confident you'll do
401:06 know it well i'm confident you'll do really well in the eigrp portion of your
401:09 really well in the eigrp portion of your ccda good luck in your studies
401:32 hi this is david voss ccie11372 and in this video we're
401:34 ccie11372 and in this video we're covering ospf design
401:37 covering ospf design we're going to begin with some concepts
401:38 we're going to begin with some concepts you need to understand a baseline i
401:40 you need to understand a baseline i guess you could say prior to designing
401:43 guess you could say prior to designing ospf
401:45 ospf and then we're going to get a bit more
401:46 and then we're going to get a bit more granular in this video and dig into ospf
401:48 granular in this video and dig into ospf concepts such as administrative areas
401:51 concepts such as administrative areas virtual links router types designated
401:54 virtual links router types designated routers
401:55 routers neighbor exchange states link state
401:57 neighbor exchange states link state advertisements and
401:58 advertisements and best path selection
402:00 best path selection if you're going to design ospf properly
402:02 if you're going to design ospf properly you need to understand all of these
402:04 you need to understand all of these concepts we will not go into
402:05 concepts we will not go into configuration examples
402:07 configuration examples that you can learn in the ccnp route
402:10 that you can learn in the ccnp route exam
402:11 exam but for the ccda
402:13 but for the ccda you will need to understand these
402:15 you will need to understand these concepts so let's begin ospf is one of
402:19 concepts so let's begin ospf is one of the most complex routing protocols that
402:21 the most complex routing protocols that can be be deployed in modern networks
402:24 can be be deployed in modern networks ospf is an open standard protocol that
402:27 ospf is an open standard protocol that is it should be able to run on cisco and
402:30 is it should be able to run on cisco and non-cisco equipment
402:32 non-cisco equipment ospf is a classless routing protocol and
402:35 ospf is a classless routing protocol and this allows it to support vlsm similar
402:38 this allows it to support vlsm similar to eigrp which uses dual
402:41 to eigrp which uses dual ospf uses spf algorithm to select loop
402:45 ospf uses spf algorithm to select loop free paths throughout the topology
402:47 free paths throughout the topology ospf is designed to be very scalable
402:50 ospf is designed to be very scalable because it's hierarchical routing
402:51 because it's hierarchical routing protocol
402:53 protocol using the concept of areas to split the
402:55 using the concept of areas to split the topology into smaller sections
402:58 topology into smaller sections so it is a very popular protocol in
403:00 so it is a very popular protocol in today's enterprise networks because it
403:03 today's enterprise networks because it can scale so well
403:05 can scale so well ospf takes bandwidth into consideration
403:08 ospf takes bandwidth into consideration when calculating route metrics
403:10 when calculating route metrics in ospf it's considered the cost a
403:14 in ospf it's considered the cost a higher bandwidth generates a lower cost
403:18 higher bandwidth generates a lower cost and lower costs are preferred in ospf
403:22 and lower costs are preferred in ospf ospf supports authentication just as
403:25 ospf supports authentication just as eigrp does in rip version 2.
403:28 eigrp does in rip version 2. ospf is also very extensible it's
403:30 ospf is also very extensible it's similar to bgp and isis meaning that the
403:33 similar to bgp and isis meaning that the protocol can be modified in the future
403:35 protocol can be modified in the future to handle other forms of traffic
403:38 to handle other forms of traffic ospf discovers neighbors and exchanges
403:41 ospf discovers neighbors and exchanges topology information with its neighbors
403:44 topology information with its neighbors acting much as eigrp does in that way
403:47 acting much as eigrp does in that way based on the collected information and
403:49 based on the collected information and the link costs ospf calculates the
403:52 the link costs ospf calculates the shortest paths to each destination using
403:54 shortest paths to each destination using as we mentioned before the spf algorithm
403:58 as we mentioned before the spf algorithm the formula for calculating the
404:00 the formula for calculating the interface cost is reference bandwidth
404:02 interface cost is reference bandwidth divided by link bandwidth
404:05 divided by link bandwidth the default reference bandwidth is a
404:07 the default reference bandwidth is a hundred megabits per second but this can
404:10 hundred megabits per second but this can be modified
404:11 be modified just as the link bandwidth can be
404:13 just as the link bandwidth can be modified using the bandwidth command
404:16 modified using the bandwidth command please note that the reference bandwidth
404:18 please note that the reference bandwidth should be modified in networks that
404:20 should be modified in networks that contain a combination of 100 megabits
404:22 contain a combination of 100 megabits per second and one gigabit per second
404:25 per second and one gigabit per second links
404:26 links because by default all of these
404:28 because by default all of these interfaces will be assigned the same
404:30 interfaces will be assigned the same ospf cost
404:32 ospf cost that's obviously a big design
404:33 that's obviously a big design consideration and something you
404:35 consideration and something you certainly could be tested on
404:38 certainly could be tested on another aspect that adds to the design
404:40 another aspect that adds to the design complexity of ospf is that it can be
404:42 complexity of ospf is that it can be configured to behave differently
404:45 configured to behave differently depending on the topology in which you
404:46 depending on the topology in which you are implementing it
404:48 are implementing it ospf recognizes different network types
404:50 ospf recognizes different network types and this will control following actions
404:53 and this will control following actions such as how updates are sent
404:55 such as how updates are sent how many adjacencies are made with the
404:57 how many adjacencies are made with the ofcpf speakers
404:59 ofcpf speakers and how the next hop is calculated
405:03 and how the next hop is calculated ospf supports the following network
405:05 ospf supports the following network types broadcast
405:07 types broadcast non-broadcast
405:09 non-broadcast point-to-point
405:10 point-to-point point to multipoint
405:12 point to multipoint point to multi-point non-broadcast and
405:15 point to multi-point non-broadcast and loopback
405:16 loopback ospf automatically selects the network
405:18 ospf automatically selects the network type that is the most appropriate for
405:20 type that is the most appropriate for the given technology so for example if
405:22 the given technology so for example if you configure ospf in a broadcast based
405:25 you configure ospf in a broadcast based ethernet environment it will default to
405:28 ethernet environment it will default to the broadcast type
405:29 the broadcast type if you configure it on a frame relay
405:31 if you configure it on a frame relay interface it will default to the
405:33 interface it will default to the non-broadcast type
405:34 non-broadcast type an ospf configured on a point-to-point
405:37 an ospf configured on a point-to-point serial link will default to the
405:39 serial link will default to the point-to-point network type
405:41 point-to-point network type the only network types that you need to
405:42 the only network types that you need to manually assign would be 0.2 multi-point
405:45 manually assign would be 0.2 multi-point or point to multi-point non-broadcast
405:49 or point to multi-point non-broadcast these obviously are most appropriate for
405:51 these obviously are most appropriate for the partial mesh which is hub and spoke
405:54 the partial mesh which is hub and spoke environments and these must be
405:56 environments and these must be configured manually
405:58 configured manually so now that you have a high level
405:59 so now that you have a high level understanding of ospf let's go ahead and
406:02 understanding of ospf let's go ahead and dig into ospf concepts all of which you
406:04 dig into ospf concepts all of which you will need to know
406:05 will need to know for your ccda exam
406:08 for your ccda exam we're going to go through these one by
406:09 we're going to go through these one by one to the level of detail you need to
406:11 one to the level of detail you need to know for the ccda exam
406:13 know for the ccda exam and we're going to begin with
406:14 and we're going to begin with administrative areas
406:18 administrative areas an autonomous system is broken out into
406:20 an autonomous system is broken out into areas so areas are a group of routers
406:22 areas so areas are a group of routers that share a same area id
406:24 that share a same area id and these different areas these
406:26 and these different areas these different groupings have different
406:28 different groupings have different functions and and they know different
406:31 functions and and they know different types of information so you have
406:34 types of information so you have backbone area standard area et cetera et
406:37 backbone area standard area et cetera et cetera and each of these areas perform
406:40 cetera and each of these areas perform different functions so let's talk in
406:43 different functions so let's talk in detail about
406:44 detail about what some of these areas know
406:46 what some of these areas know and maybe what some of these areas do
406:48 and maybe what some of these areas do not know but also how ospf is designed
406:51 not know but also how ospf is designed around these these concepts of areas so
406:54 around these these concepts of areas so remember we're talking at a higher level
406:56 remember we're talking at a higher level here but as is a good rule of thumb
407:00 here but as is a good rule of thumb your backbone area in ospf
407:03 your backbone area in ospf if anybody ever refers to area 0 you
407:07 if anybody ever refers to area 0 you know they're talking about the backbone
407:08 know they're talking about the backbone area in ospf
407:11 area in ospf and this is probably the most well-known
407:13 and this is probably the most well-known area because it is required
407:17 area because it is required and all other areas
407:20 and all other areas must connect
407:22 must connect to the backbone area so if for area to
407:25 to the backbone area so if for area to area communication
407:27 area communication let's say you have an area one
407:28 let's say you have an area one communicating to an area three
407:31 communicating to an area three both of those areas must connect to the
407:33 both of those areas must connect to the backbone
407:34 backbone so let's start here with a standard area
407:38 so let's start here with a standard area now a standard area you know you know
407:40 now a standard area you know you know what does that really mean
407:42 what does that really mean well
407:43 well standard areas can be thought of
407:45 standard areas can be thought of as equal opportunity employers i guess
407:48 as equal opportunity employers i guess you could say
407:49 you could say because um
407:50 because um they know about every route in the
407:53 they know about every route in the autonomous system in the ospf network
407:57 autonomous system in the ospf network and they share their routes but they
407:58 and they share their routes but they also learn all their routes from other
408:01 also learn all their routes from other areas through the backbone
408:04 areas through the backbone and this is just fine all this route
408:06 and this is just fine all this route sharing is just fine if routers are
408:07 sharing is just fine if routers are high-powered enough
408:09 high-powered enough to store every route but also to run
408:12 to store every route but also to run these
408:13 these complex spf calculations
408:17 complex spf calculations but just know the standard areas contain
408:19 but just know the standard areas contain lsas of type 1 two three four and five
408:23 lsas of type 1 two three four and five now next you know if you think of a stub
408:26 now next you know if you think of a stub area which we'll talk about next
408:28 area which we'll talk about next if you think of a network you know you
408:29 if you think of a network you know you have leaf nodes on networks well that's
408:31 have leaf nodes on networks well that's what kind of a stub area is
408:34 what kind of a stub area is it's handy if devices are lower powered
408:36 it's handy if devices are lower powered routers are lower powered or simply do
408:39 routers are lower powered or simply do not need to know about every route a
408:40 not need to know about every route a stub area is similar to a standard area
408:43 stub area is similar to a standard area but routers in it are not aware of
408:44 but routers in it are not aware of externally sourced routes directly
408:47 externally sourced routes directly and in terms of lsas that means that
408:49 and in terms of lsas that means that type 5 lsas are not permitted in a stub
408:51 type 5 lsas are not permitted in a stub area stub areas use a default route
408:54 area stub areas use a default route to exit for traffic to exit a stub area
408:57 to exit for traffic to exit a stub area it uses a default route
409:01 it uses a default route now next would be a totally stubby area
409:04 now next would be a totally stubby area and let's take this stub area concept
409:07 and let's take this stub area concept one step further
409:09 one step further in a total stubby area in addition to
409:11 in a total stubby area in addition to the lack of type 4 and 5 lsas type 3
409:14 the lack of type 4 and 5 lsas type 3 lsas
409:15 lsas which carry information about internal
409:17 which carry information about internal routes are also prohibited
409:20 routes are also prohibited the concept of an injected default route
409:23 the concept of an injected default route still applies here just like a stub area
409:25 still applies here just like a stub area so all traffic leaving the area
409:28 so all traffic leaving the area does so using the default route
409:43 and then finally let's go over this concept of not so stubby areas so
409:47 concept of not so stubby areas so you know this is an interesting uh i
409:50 you know this is an interesting uh i guess you could say concoction because
409:52 guess you could say concoction because not so stubby areas can connect to
409:54 not so stubby areas can connect to non-ospf networks
409:57 non-ospf networks that are not a part of this autonomous
409:59 that are not a part of this autonomous system and they and they can receive
410:01 system and they and they can receive routes from those non-ospf networks
410:05 routes from those non-ospf networks or networks that are not participating
410:07 or networks that are not participating in the autonomous system
410:10 in the autonomous system and it will receive those routes through
410:12 and it will receive those routes through redistribution
410:14 redistribution and then it can
410:16 and then it can turn those type 7 lsas and kind of you
410:19 turn those type 7 lsas and kind of you know basically it's going to
410:22 know basically it's going to mask them and make them appear as type 5
410:24 mask them and make them appear as type 5 lsas
410:26 lsas and then begin sharing them onto the
410:28 and then begin sharing them onto the network
410:29 network so there's there's your ideas of
410:31 so there's there's your ideas of networks in in areas but all areas in an
410:34 networks in in areas but all areas in an ospf autonomous system must be as you
410:36 ospf autonomous system must be as you know physically connected to the
410:38 know physically connected to the backbone area
410:40 backbone area well what if you can't do that
410:42 well what if you can't do that you know what if you uh what if you
410:44 you know what if you uh what if you can't connect an area
410:46 can't connect an area to
410:47 to area zero
410:57 so let's draw out this concept of a virtual link let's imagine we have our
411:00 virtual link let's imagine we have our a company on the east coast
411:03 a company on the east coast and we have in this company we've
411:06 and we have in this company we've deployed ospf already so we have our
411:08 deployed ospf already so we have our backbone area zero
411:10 backbone area zero and then we have other areas that have
411:12 and then we have other areas that have to obviously connect into this backbone
411:14 to obviously connect into this backbone area so
411:15 area so let's say we have an area one in the
411:17 let's say we have an area one in the boston area
411:19 boston area and then an area two
411:21 and then an area two let's say in florida but let's focus in
411:24 let's say in florida but let's focus in on area one so in the boston area we
411:26 on area one so in the boston area we have area one in boston and we acquire
411:28 have area one in boston and we acquire another company in that area and it's
411:31 another company in that area and it's easy enough for us
411:32 easy enough for us to connect this new company into our
411:34 to connect this new company into our boston resources so
411:37 boston resources so we're going to connect them into our
411:38 we're going to connect them into our boston router
411:40 boston router very simply
411:42 very simply the problem is is that even though this
411:44 the problem is is that even though this company that we've acquired maybe
411:46 company that we've acquired maybe they're already running ospf and we
411:48 they're already running ospf and we convert them to ospf area 3
411:50 convert them to ospf area 3 to work within our autonomous system
411:53 to work within our autonomous system we still need to meet the requirement of
411:55 we still need to meet the requirement of ospf where an area must connect into
411:57 ospf where an area must connect into area 0.
411:59 area 0. so
412:00 so ospf allows for
412:02 ospf allows for what is called as you know the virtual
412:05 what is called as you know the virtual link we will create this virtual link
412:07 link we will create this virtual link between area three and area zero
412:10 between area three and area zero it's passing through area one
412:12 it's passing through area one and this allows us to meet the design
412:14 and this allows us to meet the design requirement of ospf so
412:17 requirement of ospf so route to area three and area 0 see this
412:20 route to area three and area 0 see this as a direct connection and things will
412:22 as a direct connection and things will work just fine thanks to the virtual
412:24 work just fine thanks to the virtual link
412:29 so there are many different ospf router types that you need to be aware of
412:30 types that you need to be aware of there's the area border router which
412:32 there's the area border router which connects one or more ospf areas to the
412:34 connects one or more ospf areas to the backbone area
412:36 backbone area there's the asbr or autonomous system
412:38 there's the asbr or autonomous system boundary router which will be located
412:41 boundary router which will be located between an ospf
412:42 between an ospf autonomous system and a non-ospf network
412:46 autonomous system and a non-ospf network and then you have your backbone router
412:49 and then you have your backbone router which is pretty straightforward a router
412:52 which is pretty straightforward a router with at least one interface connected to
412:53 with at least one interface connected to area zero
412:54 area zero and then another easy concept and
412:56 and then another easy concept and internal router a router with all
412:57 internal router a router with all interfaces in one area
413:00 interfaces in one area let's draw this out real quick let's
413:01 let's draw this out real quick let's just to drive it home
413:03 just to drive it home so
413:04 so let's draw out our area
413:06 let's draw out our area zero
413:14 and an area zero you know already is the backbone so a router within area zero is
413:17 backbone so a router within area zero is a backbone router
413:20 a backbone router and then we connect to another area
413:23 and then we connect to another area let's say area one this isn't this is an
413:26 let's say area one this isn't this is an area border router
413:29 area border router pretty straightforward concept there's
413:31 pretty straightforward concept there's your abr
413:33 your abr and let's say we have another area we're
413:36 and let's say we have another area we're connecting to there's another abr
413:46 but we are also connecting an asbr here because we have a non-ospf network that
413:48 because we have a non-ospf network that we're going to be injecting routes from
413:51 we're going to be injecting routes from into our ospf
413:53 into our ospf process so
413:54 process so we are injecting routes in through an
413:56 we are injecting routes in through an asbr converting type 7 lsas to type 5
414:00 asbr converting type 7 lsas to type 5 and those are being forwarded on to the
414:02 and those are being forwarded on to the network and then you have
414:04 network and then you have last but not least internal
414:07 last but not least internal routers which have all interfaces in the
414:10 routers which have all interfaces in the same area pretty straightforward
414:18 so in order for two ospf routers to communicate they need to go through this
414:19 communicate they need to go through this process of exchange state so you need to
414:21 process of exchange state so you need to understand a basic concept of what these
414:23 understand a basic concept of what these are
414:25 are here's the following states there's the
414:26 here's the following states there's the init state where a hello packet has been
414:29 init state where a hello packet has been sent by a router it's waiting for a
414:30 sent by a router it's waiting for a reply
414:31 reply from the establishment state where
414:34 from the establishment state where there's the discovery of that hello and
414:35 there's the discovery of that hello and then the election of a dr and
414:37 then the election of a dr and multi-access networks
414:39 multi-access networks the x start stage where a master slave
414:42 the x start stage where a master slave relationship is started between two
414:44 relationship is started between two routers the router with the high router
414:46 routers the router with the high router id becomes the master and starts the
414:48 id becomes the master and starts the exchange
414:49 exchange and as such is the only router that can
414:51 and as such is the only router that can increment the sequence number
414:53 increment the sequence number then there's the exchange state where
414:55 then there's the exchange state where the slave acknowledgement acknowledges
414:57 the slave acknowledgement acknowledges the master's packets
414:59 the master's packets and this information in this state is
415:01 and this information in this state is only lsa headers and that does it and it
415:04 only lsa headers and that does it and it describes the contents of the entire
415:06 describes the contents of the entire link state database then there's loading
415:09 link state database then there's loading where there's a request for more
415:10 where there's a request for more information in this state the actual
415:12 information in this state the actual exchange of link state information
415:14 exchange of link state information occurs and then there's full
415:16 occurs and then there's full synchronization and in this state
415:17 synchronization and in this state routers are fully adjacent with one
415:19 routers are fully adjacent with one another
415:20 another all the router and network lsas are
415:22 all the router and network lsas are exchanged and the router's databases are
415:24 exchanged and the router's databases are fully synchronized
415:26 fully synchronized now a designated router in ospf is a key
415:29 now a designated router in ospf is a key concept that you need to know
415:31 concept that you need to know because on multi-access networks a
415:33 because on multi-access networks a designated router will establish
415:35 designated router will establish adjacencies with all other routers on
415:37 adjacencies with all other routers on the multi-access network
415:39 the multi-access network learn all their routes and then share
415:41 learn all their routes and then share all the routes with all the other
415:42 all the routes with all the other routers
415:43 routers and then the the bdr the backup
415:45 and then the the bdr the backup designated router will fill in should
415:48 designated router will fill in should the dr fail and you can set the dr and
415:52 the dr fail and you can set the dr and the bdr manually and actually you most
415:55 the bdr manually and actually you most you should do it this way you should set
415:57 you should do it this way you should set it using the priority command in ospf so
416:00 it using the priority command in ospf so understanding ospf priority is key
416:03 understanding ospf priority is key because you can manually set who the dr
416:05 because you can manually set who the dr is and who the bdr is
416:07 is and who the bdr is now it's easy to talk about this and
416:10 now it's easy to talk about this and look at a look at a powerpoint and you
416:12 look at a look at a powerpoint and you may not fully appreciate how important
416:14 may not fully appreciate how important this concept really is so let's actually
416:17 this concept really is so let's actually draw it out
416:18 draw it out so on a typical multi-access network
416:21 so on a typical multi-access network let's say we have five routers
416:23 let's say we have five routers and you want to establish adjacencies in
416:25 and you want to establish adjacencies in ospf to share routes between them
416:28 ospf to share routes between them if they did the that way where they're
416:30 if they did the that way where they're all neighboring with one another and
416:32 all neighboring with one another and communicating with one another you're
416:34 communicating with one another you're gonna see that all these adjacencies are
416:35 gonna see that all these adjacencies are gonna add up pretty quickly
416:37 gonna add up pretty quickly and that's gonna that's gonna tax the
416:39 and that's gonna that's gonna tax the resources on the routers themselves but
416:41 resources on the routers themselves but it's really unnecessary we can share
416:43 it's really unnecessary we can share this information in a much more
416:45 this information in a much more efficient manner
416:46 efficient manner so what we're going to do is we elect a
416:49 so what we're going to do is we elect a dr in ospf
416:51 dr in ospf again it has this built in within the
416:54 again it has this built in within the ospf design itself
416:56 ospf design itself or a multi-access network you can elect
416:58 or a multi-access network you can elect a dr
416:59 a dr and then the dr establishes an adjacency
417:02 and then the dr establishes an adjacency with all the other routers on the
417:03 with all the other routers on the multi-access network it learns all of
417:05 multi-access network it learns all of their routes and then shares all their
417:07 their routes and then shares all their routes so now we just have four
417:09 routes so now we just have four adjacencies required now if the dr fails
417:13 adjacencies required now if the dr fails and those adjacencies fail the bdr would
417:15 and those adjacencies fail the bdr would take over
417:24 now regarding link state advertisements what you really need to know at least
417:25 what you really need to know at least just for now in ospf is that a link
417:27 just for now in ospf is that a link state advertisement
417:29 state advertisement is a packet that contains all relevant
417:31 is a packet that contains all relevant information regarding a router's links
417:34 information regarding a router's links and the state of those links
417:36 and the state of those links now there are many different types and
417:37 now there are many different types and i've listed the key types for you here
417:40 i've listed the key types for you here and we're going to dig into detail on
417:42 and we're going to dig into detail on these different types as we get into the
417:44 these different types as we get into the labs but just for now
417:46 labs but just for now know that these are these are
417:47 know that these are these are informational packets that have
417:50 informational packets that have information on a router's links and the
417:52 information on a router's links and the state of those links
417:59 so now that ospf has gathered all this information it needs to know what to do
418:01 information it needs to know what to do with it needs to choose the best path so
418:02 with it needs to choose the best path so it puts all the information in a
418:04 it puts all the information in a topology table
418:06 topology table and then ospf the metric for ospf is
418:08 and then ospf the metric for ospf is cost so cost is 10 to the power of eight
418:10 cost so cost is 10 to the power of eight divided by bandwidth
418:12 divided by bandwidth and lower costs are preferred
418:15 and lower costs are preferred so the best way to understand cost is
418:17 so the best way to understand cost is actually for us just to draw this out to
418:19 actually for us just to draw this out to see how it works
418:22 see how it works so let's draw out a six router network
418:34 and let's say we have router one which ultimately wants to communicate
418:36 which ultimately wants to communicate with a network off of router 6
418:42 with a network off of router 6 and it will have two choices two paths
418:45 and it will have two choices two paths it can possibly take
418:54 it can go via router 2 or via router 4 to this network we'll say
418:57 to this network we'll say 192.168.10 network 24.
419:06 which is hanging off router 6. now router 1
419:08 router 1 then calculates using ospf the cost
419:11 then calculates using ospf the cost for each and every link in this path
419:16 for each and every link in this path and it's going to do the same
419:18 and it's going to do the same for the path from router two and three
419:20 for the path from router two and three to six
419:23 to six and then what ospf is going to do
419:26 and then what ospf is going to do is
419:27 is add up
419:29 add up the entire cost to get to router six so
419:34 the entire cost to get to router six so from going via router 4
419:37 from going via router 4 that path has a total cost of 20.
419:44 and going via router 2 that path has a total cost of 25 and we know that ospf
419:47 total cost of 25 and we know that ospf uses
419:49 uses the lower cost to make its decision on
419:51 the lower cost to make its decision on which path to take
419:53 which path to take so the total cost of 20 wins out
419:56 so the total cost of 20 wins out and we will choose router 4.
419:59 and we will choose router 4. now that being said let's say a new
420:00 now that being said let's say a new network is introduced
420:13 and even though we have more routers or more hops through this network
420:15 or more hops through this network let's say there are four hops
420:23 if the cost is low and for this case we'll say five five one one and one
420:26 we'll say five five one one and one if the total cost here is just 13
420:30 if the total cost here is just 13 even though there's more hops ospf is
420:32 even though there's more hops ospf is going to choose this path
420:34 going to choose this path because it's more efficient
420:40 so that's cost basically explained that's cost in a
420:42 basically explained that's cost in a nutshell
420:43 nutshell so here's what you've learned you've
420:45 so here's what you've learned you've received an overview of ospf
420:48 received an overview of ospf and then we got a bit more granular to
420:50 and then we got a bit more granular to the level you'll need to know for the
420:51 the level you'll need to know for the ccda exam
420:53 ccda exam including administrative areas
420:55 including administrative areas virtual links
420:57 virtual links router types
420:58 router types designated routers
421:00 designated routers neighbor exchange states
421:02 neighbor exchange states link state advertisements and best path
421:05 link state advertisements and best path selection
421:06 selection i'm confident after watching this video
421:08 i'm confident after watching this video if you know this information well you're
421:10 if you know this information well you're going to do excellent on the ospf
421:12 going to do excellent on the ospf portion of your ccda exam
421:15 portion of your ccda exam good luck in your studies
421:18 good luck in your studies hi this is david voss ccie 11372 and in
421:22 hi this is david voss ccie 11372 and in this video you're going to learn about
421:23 this video you're going to learn about isis design
421:29 specifically you're going to learn about isis operations areas
421:32 isis operations areas addressing packet types network types
421:36 addressing packet types network types and metrics so let's begin
421:38 and metrics so let's begin in recent years the isis routing
421:40 in recent years the isis routing protocol has become increasingly popular
421:44 protocol has become increasingly popular with widespread usage among service
421:46 with widespread usage among service providers it is also a very flexible
421:48 providers it is also a very flexible protocol
421:50 protocol that's been extended to incorporate
421:51 that's been extended to incorporate leading edge features such as mpls
421:54 leading edge features such as mpls traffic engineering
421:56 traffic engineering the isis routing protocol is a link
421:58 the isis routing protocol is a link state protocol as opposed to distance
422:01 state protocol as opposed to distance vector protocols
422:03 vector protocols such as igrp and rip
422:06 such as igrp and rip isis protocol is an intra-domain
422:09 isis protocol is an intra-domain osi dynamic routing protocol isis uses a
422:13 osi dynamic routing protocol isis uses a two-level hierarchy and it's used to
422:15 two-level hierarchy and it's used to support these large routing domains
422:18 support these large routing domains a large domain may be administratively
422:20 a large domain may be administratively divided into areas
422:23 divided into areas from a high level isis operates as
422:25 from a high level isis operates as follows
422:26 follows routers running isas will send hello
422:28 routers running isas will send hello packets out all
422:30 packets out all isis-enabled interfaces
422:32 isis-enabled interfaces to discovered neighbors and establish
422:35 to discovered neighbors and establish adjacencies
422:36 adjacencies routers sharing a common data link will
422:38 routers sharing a common data link will become neighbors if their hello packets
422:41 become neighbors if their hello packets contain information that meets the
422:43 contain information that meets the criteria for forming an adjacency
422:46 criteria for forming an adjacency routers may build a link state packet
422:49 routers may build a link state packet lsp
422:50 lsp based on their local interfaces that are
422:53 based on their local interfaces that are configured for isis
422:55 configured for isis and prefixes learned from other adjacent
422:58 and prefixes learned from other adjacent routers
422:58 routers and a shortest path tree is calculated
423:01 and a shortest path tree is calculated by each is
423:03 by each is and from this
423:04 and from this spt the routing table and from this the
423:08 spt the routing table and from this the routing table is built
423:13 next let's talk about areas and the routing domain within isis so an isis
423:16 routing domain within isis so an isis routing domain is similar to bgp
423:18 routing domain is similar to bgp autonomous system a routing domain is a
423:20 autonomous system a routing domain is a collection of areas under an
423:22 collection of areas under an administration that implements routing
423:24 administration that implements routing policies within the domain
423:31 first let's talk about the backbone iss does not have a backbone area like ospf
423:34 does not have a backbone area like ospf area 0.
423:35 area 0. the iss backbone is a contiguous
423:38 the iss backbone is a contiguous collection of level 2 capable routers
423:41 collection of level 2 capable routers each of which can be in a different area
423:45 each of which can be in a different area now speaking of areas within isis an
423:47 now speaking of areas within isis an individual router is only in only one
423:50 individual router is only in only one area
423:51 area and the border between areas on the link
423:53 and the border between areas on the link that connects the two routers that are
423:55 that connects the two routers that are in different areas
423:57 in different areas and the border between areas is on the
424:00 and the border between areas is on the link that connects two routers that are
424:02 link that connects two routers that are in different areas
424:04 in different areas this obviously is in contrast to ospf so
424:07 this obviously is in contrast to ospf so as you've already heard isis has a two
424:09 as you've already heard isis has a two level hierarchy contiguous level two
424:12 level hierarchy contiguous level two capable routers from the backbone
424:14 capable routers from the backbone both level 2 and level 1 routers live in
424:17 both level 2 and level 1 routers live in areas
424:18 areas routers can be level 1 level 2 or both
424:21 routers can be level 1 level 2 or both level 1 level 2.
424:23 level 1 level 2. within the cisco ios software the
424:25 within the cisco ios software the default configuration is both level 1
424:28 default configuration is both level 1 and level 2 at the same time
424:30 and level 2 at the same time this allows isis network to run with
424:33 this allows isis network to run with minimal configuration in more of a
424:35 minimal configuration in more of a plug-and-play fashion
424:37 plug-and-play fashion level 2 capable routers connect all
424:39 level 2 capable routers connect all areas within a routing domain level two
424:42 areas within a routing domain level two routers advertise their own nsap address
424:45 routers advertise their own nsap address to other two other level two routers in
424:47 to other two other level two routers in the backbone
424:49 the backbone and all level one routers and hosts in
424:51 and all level one routers and hosts in an area must have an nsap with the same
424:54 an area must have an nsap with the same area address
424:56 area address a level 2 router may have neighbors in
424:59 a level 2 router may have neighbors in the same or in different areas
425:01 the same or in different areas but it has a level 2 link state database
425:04 but it has a level 2 link state database with all information for inter area
425:07 with all information for inter area routing
425:08 routing level 2 routers know about other areas
425:10 level 2 routers know about other areas but will not have level one information
425:13 but will not have level one information from its own area
425:16 from its own area a level one and level two router may
425:18 a level one and level two router may have neighbors in any area
425:21 have neighbors in any area it has two link state databases a level
425:24 it has two link state databases a level one link state database for intra area
425:27 one link state database for intra area routing and a level two link state
425:29 routing and a level two link state database for inter area routing
425:32 database for inter area routing next let's talk about nsap addresses
425:35 next let's talk about nsap addresses an nsap describes an attachment to a
425:38 an nsap describes an attachment to a particular service at the network layer
425:40 particular service at the network layer of a node
425:41 of a node similar to the combination of ip
425:43 similar to the combination of ip destination and ip protocol number in an
425:46 destination and ip protocol number in an ip packet
425:48 ip packet an nsap address has two major parts the
425:52 an nsap address has two major parts the idp or initial domain part and the dsp
425:55 idp or initial domain part and the dsp the domain specific part
425:58 the domain specific part the idp consists of a one byte authority
426:00 the idp consists of a one byte authority and format identifier that's the afi
426:04 and format identifier that's the afi in a variable variable length initial
426:06 in a variable variable length initial domain identifier the idi
426:09 domain identifier the idi and the dsp is a string of digits
426:12 and the dsp is a string of digits identifying a particular transport
426:14 identifying a particular transport implementation
426:15 implementation of a specified afi authority
426:18 of a specified afi authority everything to the left of the system idb
426:20 everything to the left of the system idb can be thought of as the area address of
426:23 can be thought of as the area address of a network node
426:25 a network node the big difference between end step
426:27 the big difference between end step style addressing and ip style addressing
426:30 style addressing and ip style addressing is that in general there will be a
426:32 is that in general there will be a single nsap address for the entire
426:34 single nsap address for the entire router
426:35 router all is's and es in a routing domain must
426:39 all is's and es in a routing domain must have system ids of the same length
426:46 all routers in an area must have the same area address all level 2 routers
426:49 same area address all level 2 routers must have a unique system id domain wide
426:52 must have a unique system id domain wide and all level 1 routers must have a
426:53 and all level 1 routers must have a unique system id area-wide
426:57 unique system id area-wide all ess in an area will form an
426:59 all ess in an area will form an adjacency with a level 1 router on a
427:02 adjacency with a level 1 router on a shared media segment if they share the
427:04 shared media segment if they share the same area address
427:06 same area address if multiple nets are configured on the
427:09 if multiple nets are configured on the same router they must all have the same
427:11 same router they must all have the same system id
427:17 next let's talk about packet types there are four types of packets each
427:20 there are four types of packets each type can be level one or level two
427:24 type can be level one or level two first there is the intermediate system
427:26 first there is the intermediate system to intermediate system hello packet used
427:29 to intermediate system hello packet used by routers to detect neighbors and form
427:31 by routers to detect neighbors and form adjacencies
427:33 adjacencies then there's the link state packet there
427:35 then there's the link state packet there are four types of lsps level one
427:38 are four types of lsps level one pseudonode
427:39 pseudonode level one non-pseudo node level two
427:42 level one non-pseudo node level two pseudonode and level 2 non-pseudonode
427:46 pseudonode and level 2 non-pseudonode complete sequence number pdu
427:50 complete sequence number pdu csnps contain a list of all lsps in the
427:54 csnps contain a list of all lsps in the current database
427:55 current database cnsps are used to inform other routers
427:58 cnsps are used to inform other routers of lsps that may be outdated or missing
428:01 of lsps that may be outdated or missing from their own database
428:03 from their own database this ensures all routers have the same
428:05 this ensures all routers have the same information and are synchronized
428:08 information and are synchronized and then finally partial sequence number
428:11 and then finally partial sequence number pdu
428:12 pdu psnps are used to request an lsp an
428:16 psnps are used to request an lsp an acknowledged receipt of an lsp
428:24 next let's talk about network types the types of networks that isis defines
428:26 the types of networks that isis defines include point-to-point and broadcast
428:28 include point-to-point and broadcast networks
428:30 networks point-to-point networks such as serial
428:31 point-to-point networks such as serial lines connect a single pair of routers a
428:34 lines connect a single pair of routers a router running isas will form an
428:37 router running isas will form an adjacency with the neighbor on the other
428:39 adjacency with the neighbor on the other side of a point-to-point interface
428:41 side of a point-to-point interface automatically
428:42 automatically the dis is not elected on this type of
428:45 the dis is not elected on this type of link
428:46 link the basic mechanism defined
428:48 the basic mechanism defined in the standard is that each side of a
428:51 in the standard is that each side of a point-to-point link
428:52 point-to-point link declares the other side to be reachable
428:54 declares the other side to be reachable if a hello packet is received from it
428:58 if a hello packet is received from it next there's broadcast networks such as
429:00 next there's broadcast networks such as ethernet
429:01 ethernet even token ring
429:03 even token ring these are multi-access and they are able
429:05 these are multi-access and they are able to connect more than two devices all
429:08 to connect more than two devices all connected routers will receive
429:10 connected routers will receive a packet sent by one router on broadcast
429:13 a packet sent by one router on broadcast networks one is will elect itself the
429:16 networks one is will elect itself the dis
429:18 dis the dis is responsible for flooding and
429:21 the dis is responsible for flooding and it will create and flood a new
429:22 it will create and flood a new pseudonode lsp for each routing level
429:25 pseudonode lsp for each routing level that is participating that it is
429:27 that is participating that it is participating in that is level one or
429:29 participating in that is level one or level two and for each land to which it
429:32 level two and for each land to which it is configured
429:34 is configured and connected
429:35 and connected a router can be the dis for all
429:37 a router can be the dis for all connected lands or a subset of connected
429:40 connected lands or a subset of connected lands
429:40 lands depending on the configured priority
429:44 depending on the configured priority or if no priority is configured the
429:46 or if no priority is configured the layer to address
429:48 layer to address and then finally nbma networks such as
429:52 and then finally nbma networks such as frame relay or atm or x25
429:55 frame relay or atm or x25 can connect multiple devices but have no
429:57 can connect multiple devices but have no broadcast capability
429:59 broadcast capability all of the routers attached to the
430:01 all of the routers attached to the network will not receive a packet sent
430:02 network will not receive a packet sent by this router
430:05 by this router special considerations need to be taken
430:07 special considerations need to be taken in account when configuring isis over
430:09 in account when configuring isis over these types of networks
430:11 these types of networks because isis considers these media to be
430:13 because isis considers these media to be just like any other broadcast media such
430:16 just like any other broadcast media such as ethernet or token ring
430:18 as ethernet or token ring in general it is better configure
430:20 in general it is better configure point-to-point networks on wan
430:22 point-to-point networks on wan interfaces and sub-interfaces
430:29 next let's talk about isis metrics cost is the default metric and is
430:32 cost is the default metric and is supported by all routers
430:35 supported by all routers while some routing protocols calculate
430:37 while some routing protocols calculate the link metric automatically based on
430:38 the link metric automatically based on bandwidth such as ospf
430:41 bandwidth such as ospf or bandwidth and delay such as eigrp
430:44 or bandwidth and delay such as eigrp there is no automatic calculation for
430:46 there is no automatic calculation for isis
430:48 isis using old style metrics an interface
430:51 using old style metrics an interface cost is between 1 and 63.
430:54 cost is between 1 and 63. all links use the metric of 10 by
430:56 all links use the metric of 10 by default
430:57 default the total cost to a destination is the
430:59 the total cost to a destination is the sum of all costs on an outgoing
431:01 sum of all costs on an outgoing interface
431:03 interface along a particular path from the source
431:05 along a particular path from the source to the destination
431:07 to the destination and least cost paths are preferred
431:11 and least cost paths are preferred the total path metric was limited to
431:13 the total path metric was limited to 1023
431:18 this small metric value proved insufficient for large networks
431:20 insufficient for large networks and provided too little granularity for
431:23 and provided too little granularity for new features
431:25 new features the cisco ios software addresses this
431:27 the cisco ios software addresses this issue with the support of a 24-bit
431:30 issue with the support of a 24-bit metric field
431:31 metric field the so-called wide metric
431:34 the so-called wide metric now metrics can have a maximum value of
431:37 now metrics can have a maximum value of as you can see right here
431:39 as you can see right here deploying isis on the ip network with
431:42 deploying isis on the ip network with wide metrics is recommended
431:44 wide metrics is recommended to enable finer granularity and to
431:47 to enable finer granularity and to support future applications such as
431:49 support future applications such as traffic engineering
431:51 traffic engineering so you have learned quite a bit about
431:53 so you have learned quite a bit about isis you've learned about isis areas and
431:57 isis you've learned about isis areas and router types the nsap address
432:00 router types the nsap address as well as pekka types network types
432:04 as well as pekka types network types and metrics
432:06 and metrics all this information will be needed on
432:08 all this information will be needed on your ccda exam and i'm confident if
432:10 your ccda exam and i'm confident if you've studied this video well
432:12 you've studied this video well you're going to do very well on your
432:14 you're going to do very well on your exam good luck in your studies
432:39 hi this is david voss ccie 11372 and in this video we are going to
432:41 11372 and in this video we are going to cover bgp design
432:44 cover bgp design the first thing we're going to do is do
432:46 the first thing we're going to do is do an overview of bgp and then we're going
432:49 an overview of bgp and then we're going to get a little bit more granular and
432:50 to get a little bit more granular and we'll talk about bgp path attributes
432:53 we'll talk about bgp path attributes bgpas path ebgp versus ibgp
432:57 bgpas path ebgp versus ibgp public versus private asn
433:00 public versus private asn bgp updates and how bgp advertises
433:03 bgp updates and how bgp advertises routes
433:04 routes all this information you will need to
433:06 all this information you will need to know
433:07 know to understand how to properly design bgp
433:10 to understand how to properly design bgp and do well on this portion of the ccda
433:14 and do well on this portion of the ccda exam
433:15 exam so let's go ahead and begin with an
433:17 so let's go ahead and begin with an overview of bgp bgp is an exterior
433:21 overview of bgp bgp is an exterior gateway protocol that uses autonomous
433:23 gateway protocol that uses autonomous system numbers
433:26 system numbers uses tcp 179 to communicate between
433:29 uses tcp 179 to communicate between neighbors
433:30 neighbors and it really is a protocol that
433:32 and it really is a protocol that requires manual configuration for almost
433:34 requires manual configuration for almost everything it doesn't really do anything
433:36 everything it doesn't really do anything unless you tell it to do it which i
433:38 unless you tell it to do it which i really like about the protocol
433:40 really like about the protocol now it uses path attributes which are
433:43 now it uses path attributes which are key in decision making on choosing best
433:45 key in decision making on choosing best route so
433:47 route so path attributes define information about
433:49 path attributes define information about a path
433:50 a path but also
433:52 but also this information can be used to help
433:53 this information can be used to help decide upon the best path
433:57 decide upon the best path and we will draw that out in a minute
433:59 and we will draw that out in a minute here so you can understand that better
434:01 here so you can understand that better now regarding bgp path attributes there
434:04 now regarding bgp path attributes there are some that you absolutely have to
434:06 are some that you absolutely have to know and memorize the first is weight
434:09 know and memorize the first is weight weight influences a best route for the
434:11 weight influences a best route for the local router and obviously it's manually
434:14 local router and obviously it's manually configured
434:15 configured local preference influences the best
434:17 local preference influences the best route for all routers in an autonomous
434:19 route for all routers in an autonomous system so this is a shared attribute
434:22 system so this is a shared attribute a s path
434:24 a s path lists the number of autonomous system
434:26 lists the number of autonomous system numbers in the path and this can be
434:28 numbers in the path and this can be manipulated
434:30 manipulated origin is a value implying if the route
434:32 origin is a value implying if the route is from an igp
434:34 is from an igp or an egp
434:36 or an egp and then finally the med which can
434:38 and then finally the med which can influence the best route for routers in
434:40 influence the best route for routers in another as so you can influence
434:42 another as so you can influence traffic flows into uras
434:44 traffic flows into uras by sending out the med
434:47 by sending out the med to other
434:48 to other uh other routers
434:56 so here you can see we have two routers that are in autonomous system
434:59 that are in autonomous system 700
435:00 700 and then
435:02 and then upstream
435:03 upstream we have another router and autonomous
435:05 we have another router and autonomous system 140 and autonomous system 87. so
435:08 system 140 and autonomous system 87. so here you see there are four hops
435:11 here you see there are four hops but as far as bgp is concerned it's just
435:13 but as far as bgp is concerned it's just counting ases
435:15 counting ases so it counts one two
435:18 so it counts one two three as's the as path is 700
435:21 three as's the as path is 700 140 and 87.
435:24 140 and 87. why is this important to know because
435:26 why is this important to know because here's another flow that has
435:29 here's another flow that has two routers in as700 and then one router
435:32 two routers in as700 and then one router in as87
435:34 in as87 now according to this path there's just
435:36 now according to this path there's just two as's that would be the preferred
435:38 two as's that would be the preferred path
435:40 path it's critical to understand that bgp is
435:42 it's critical to understand that bgp is concerned about aes path and not so much
435:44 concerned about aes path and not so much about hop count aspath is a key
435:47 about hop count aspath is a key attribute to understand
435:51 now internal versus external bgp
435:54 internal versus external bgp ibgp is something you would run
435:56 ibgp is something you would run basically interior to your company it's
435:58 basically interior to your company it's bgp connectivity within the same
436:00 bgp connectivity within the same autonomous system
436:03 autonomous system in this routers do not update as path
436:05 in this routers do not update as path normally they should never have to
436:07 normally they should never have to because you're running the same
436:08 because you're running the same autonomous system
436:10 autonomous system and in ibgp
436:11 and in ibgp things should always be meshed routers
436:13 things should always be meshed routers should always be fully meshed and there
436:15 should always be fully meshed and there are ways you can get around this and
436:17 are ways you can get around this and we'll talk about that in a little bit
436:19 we'll talk about that in a little bit now ebgp is external connectivity to
436:22 now ebgp is external connectivity to other ass
436:24 other ass and routers do update the as path in
436:27 and routers do update the as path in those cases
436:37 so let's say we have an autonomous system
436:39 we have an autonomous system 200
436:41 200 and in our company we're running ibgp
436:44 and in our company we're running ibgp full mesh between all routers
436:53 and let's say we have connectivity to two upstream providers
436:57 two upstream providers one is autonomous system 301 and the
437:00 one is autonomous system 301 and the other provider is autonomous system
437:02 other provider is autonomous system 450. now between ourselves and our
437:06 450. now between ourselves and our providers we are running ebgp
437:11 providers we are running ebgp because it's two different as's
437:14 because it's two different as's and internally we are running ibgp
437:17 and internally we are running ibgp because we are communicating between the
437:20 because we are communicating between the same as
437:27 now configuration between ibgp and ebgps is quite similar the main difference is
437:29 is quite similar the main difference is you're choosing to communicate with the
437:31 you're choosing to communicate with the same as or a different as
437:33 same as or a different as now let's say we want to communicate to
437:34 now let's say we want to communicate to a web server
437:36 a web server over the internet
437:38 over the internet and we have a certain amount of hops now
437:40 and we have a certain amount of hops now let's say
437:41 let's say one of those paths
437:43 one of those paths through as450 takes us through quite a
437:45 through as450 takes us through quite a few more hops
437:47 few more hops but
437:48 but it takes us through fewer as's so let's
437:51 it takes us through fewer as's so let's just say for example we go through
437:53 just say for example we go through as900 and then as100
437:58 as900 and then as100 so
437:58 so that's 450
438:02 that's 450 900
438:03 900 and 100 those are the three as we
438:05 and 100 those are the three as we traverse in order to reach that route
438:08 traverse in order to reach that route now let's see on this flow through
438:10 now let's see on this flow through autonomous system 301
438:12 autonomous system 301 we go through
438:13 we go through fewer hops but more as's
438:24 now even though there's fewer hops because there are more as's we're not
438:26 because there are more as's we're not going to prefer this route
438:28 going to prefer this route there are five as's in this path
438:31 there are five as's in this path that is not going to be preferred
438:32 that is not going to be preferred to the other path which has only three
438:35 to the other path which has only three as's so we're going to choose that path
438:38 as's so we're going to choose that path we'll choose the 3as path
438:51 now let's say we're running a web server inside of our company and we're running
438:54 inside of our company and we're running ibgp between these three routers and
438:56 ibgp between these three routers and we're connecting to two upstream
438:57 we're connecting to two upstream providers using ebgp
439:05 and let's say we have users on the internet who are trying to get to this
439:07 internet who are trying to get to this web server we can manipulate the a.s
439:10 web server we can manipulate the a.s path attribute in bgp
439:12 path attribute in bgp to make them prefer one path over the
439:15 to make them prefer one path over the other
439:16 other and the way we do that well let's say
439:18 and the way we do that well let's say our autonomous system is 50
439:20 our autonomous system is 50 we can manipulate the aspath attribute
439:24 we can manipulate the aspath attribute by adding to
439:26 by adding to the as path on one of our links so
439:30 the as path on one of our links so for example the users know that they can
439:32 for example the users know that they can reach the web server via 1as well we're
439:36 reach the web server via 1as well we're going to increase that on the top router
439:40 going to increase that on the top router and we're going to manipulate it
439:41 and we're going to manipulate it manually
439:43 manually and add
439:44 and add our as over and over again to the aspath
439:47 our as over and over again to the aspath attribute
439:49 attribute and
439:50 and the users as far as bgp is concerned
439:53 the users as far as bgp is concerned that now is a longer path
439:57 that now is a longer path and therefore the user will prefer the
439:59 and therefore the user will prefer the bottom path
440:00 bottom path because it's only one hop one as hop
440:04 because it's only one hop one as hop now if that router were to fail
440:06 now if that router were to fail users would then prefer the other path
440:09 users would then prefer the other path so you see you can manipulate
440:11 so you see you can manipulate traffic flows that way now you need to
440:13 traffic flows that way now you need to understand the concept of public and
440:15 understand the concept of public and private asn's and this shouldn't be
440:16 private asn's and this shouldn't be foreign to you because you understand
440:18 foreign to you because you understand public and private i p addressing so
440:20 public and private i p addressing so autonomous system numbers are chosen
440:22 autonomous system numbers are chosen from this pool and you can use them
440:24 from this pool and you can use them for private use or public use as need be
440:27 for private use or public use as need be but you should be aware of that chart
440:31 but you should be aware of that chart now regarding bgp updates that we
440:32 now regarding bgp updates that we receive from neighbors you can receive
440:35 receive from neighbors you can receive from your provider a default route only
440:37 from your provider a default route only which many people do
440:38 which many people do or you can receive a full bgp routing
440:41 or you can receive a full bgp routing table that is literally every route
440:42 table that is literally every route that's available on the internet
440:44 that's available on the internet or you can receive just partial updates
440:46 or you can receive just partial updates and that is maybe the provider knows
440:48 and that is maybe the provider knows about certain routes via a better path
440:51 about certain routes via a better path than most other providers you can just
440:53 than most other providers you can just receive a partial update from your
440:55 receive a partial update from your provider so you should know that you can
440:57 provider so you should know that you can receive those three different types of
440:59 receive those three different types of updates that should be known for your
441:01 updates that should be known for your ccmp route exam
441:02 ccmp route exam now regarding advertising routes
441:05 now regarding advertising routes advertising bgp routes can be done four
441:07 advertising bgp routes can be done four ways either through the manual network
441:09 ways either through the manual network command
441:10 command redistribution of bgp and igp
441:14 redistribution of bgp and igp or propagation of existing bgp routes or
441:18 or propagation of existing bgp routes or again manually using the aggregate
441:20 again manually using the aggregate address command
441:22 address command maybe the best way to explain these is
441:24 maybe the best way to explain these is to simply draw it out
441:33 now imagine we have a router with an i bgp connection and an ebgp connection to
441:36 bgp connection and an ebgp connection to an upstream provider so there's our ebgp
441:39 an upstream provider so there's our ebgp connection here's our ibgp connection
441:42 connection here's our ibgp connection and we're autonomous system let's say
441:44 and we're autonomous system let's say 400. so
441:45 400. so on a router we can advertise in four
441:47 on a router we can advertise in four different ways we can manually specify
441:49 different ways we can manually specify the network we want to advertise by
441:51 the network we want to advertise by literally typing it in
441:52 literally typing it in network
441:53 network 10.10.10.0
441:55 10.10.10.0 or
441:56 or network
441:57 network 198110
441:59 198110 and we can forward that via ibgp and or
442:02 and we can forward that via ibgp and or ebgp the other way is we can learn
442:05 ebgp the other way is we can learn routes via bgp and redistribute that
442:08 routes via bgp and redistribute that route
442:09 route into let's say an interior routing
442:11 into let's say an interior routing protocol let's say if we're running ospf
442:13 protocol let's say if we're running ospf we can take the the routes we learned
442:15 we can take the the routes we learned from our ebgp neighbor and redistribute
442:17 from our ebgp neighbor and redistribute them
442:18 them the other way is to simply pass the
442:20 the other way is to simply pass the routes we're learning from our ebgp
442:22 routes we're learning from our ebgp neighbor via bgp
442:24 neighbor via bgp internally to our ibgp neighbor
442:27 internally to our ibgp neighbor so that's just pat forwarding the the
442:29 so that's just pat forwarding the the information on
442:30 information on and finally we can again manually set an
442:33 and finally we can again manually set an aggregate address
442:34 aggregate address on the router and that's a manual
442:36 on the router and that's a manual configuration to aggregate some of the
442:38 configuration to aggregate some of the routes
442:39 routes and again that can be advertised out
442:41 and again that can be advertised out either way
442:43 either way so the rule of synchronization in bgp
442:46 so the rule of synchronization in bgp you should simply know this that bgp
442:49 you should simply know this that bgp will not advertise a route unless it
442:51 will not advertise a route unless it knows about that route via an igp
442:55 knows about that route via an igp that's what you really need to know for
442:57 that's what you really need to know for the exam now you can disable this by
443:00 the exam now you can disable this by typing no synchronization on your router
443:03 typing no synchronization on your router and then it will simply forward routes
443:04 and then it will simply forward routes that are not in the igp so here's what
443:07 that are not in the igp so here's what you've learned you received an overview
443:08 you've learned you received an overview of bgp
443:10 of bgp and we dug in a little bit on bgp path
443:13 and we dug in a little bit on bgp path attributes aspath ebgp and ibgp public
443:17 attributes aspath ebgp and ibgp public and private asns
443:19 and private asns bgp updates and then the advertisement
443:22 bgp updates and then the advertisement of routes
443:23 of routes all of this you will need to know for
443:25 all of this you will need to know for your ccda exam and if you master this
443:27 your ccda exam and if you master this material i'm confident you will do very
443:29 material i'm confident you will do very well
443:30 well on this portion of your ccda exam good
443:33 on this portion of your ccda exam good luck in your studies
443:58 hi this is david boss ccie11372 and in this video we'll be covering ip
444:00 and in this video we'll be covering ip version 6 routing protocols
444:02 version 6 routing protocols so here's what you're going to learn
444:05 so here's what you're going to learn you're going to learn about ip version 6
444:08 you're going to learn about ip version 6 routing protocols an overview of them
444:10 routing protocols an overview of them and how to enable them
444:18 to support ipv6 all of the ipv4 routing protocols had to go through adaptations
444:21 protocols had to go through adaptations each had to be changed to support longer
444:23 each had to be changed to support longer addresses and prefixes and the actual
444:26 addresses and prefixes and the actual messages used to send and receive
444:28 messages used to send and receive routing information
444:30 routing information have changed in some cases as well
444:33 have changed in some cases as well using ipv6 headers instead of v4 headers
444:36 using ipv6 headers instead of v4 headers but in particular like their ipv4
444:39 but in particular like their ipv4 versions each version 6 igp
444:42 versions each version 6 igp uses v6 multicast addresses those are
444:46 uses v6 multicast addresses those are just a few of the changes
444:48 just a few of the changes but even with those changes each ipv6
444:51 but even with those changes each ipv6 igp
444:52 igp has many more similarities than
444:54 has many more similarities than differences
444:55 differences compared to their respective version
444:58 compared to their respective version version 4 cousins
445:08 let's start with rip the overall operation of rip next
445:10 the overall operation of rip next generation closely matches that of rip
445:13 generation closely matches that of rip version 2.
445:14 version 2. routers still send periodic full updates
445:17 routers still send periodic full updates with all routes
445:19 with all routes no neighbor relationships occur
445:22 no neighbor relationships occur the continuing periodic updates also
445:24 the continuing periodic updates also serve the purpose of confirming that the
445:26 serve the purpose of confirming that the neighboring router still works
445:30 neighboring router still works the big difference between rip version 2
445:32 the big difference between rip version 2 and rip next generation configuration
445:34 and rip next generation configuration is that rip next generation discards the
445:37 is that rip next generation discards the age-old rip network command and replaces
445:40 age-old rip network command and replaces it with an enable interface sub command
445:43 it with an enable interface sub command finally rip next generation allows
445:45 finally rip next generation allows multiple rip next generation processes
445:48 multiple rip next generation processes on a single router
445:49 on a single router so an ios requires that each rip next
445:52 so an ios requires that each rip next generation process is given a text name
445:55 generation process is given a text name that identifies each rip next generation
445:58 that identifies each rip next generation process
445:59 process for that one router
446:00 for that one router and there's another difference compared
446:02 and there's another difference compared to rip version 2.
446:04 to rip version 2. let's go ahead and jump into our lab
446:07 let's go ahead and jump into our lab in our lab we're going to be working on
446:08 in our lab we're going to be working on router 2 and router 4
446:11 router 2 and router 4 and we're going to go ahead and log in
446:14 and we're going to go ahead and log in and enable rip
446:20 let's take a look at our interfaces on router 2 and we're going to be working
446:22 router 2 and we're going to be working with serial zero zero and loopback one
446:28 now the first thing we'll do on router two is we're gonna go ahead and assign
446:31 two is we're gonna go ahead and assign ip version six ip addresses so
446:34 ip version six ip addresses so on interface zero zero zero even though
446:36 on interface zero zero zero even though it has an ipv4 address we obviously can
446:39 it has an ipv4 address we obviously can still add an ipv6 address
446:42 still add an ipv6 address and again we're going to shorten that so
446:44 and again we're going to shorten that so it's a lot easier we're going to use the
446:46 it's a lot easier we're going to use the the ability to shorten that address
446:48 the ability to shorten that address using the double colon
446:51 using the double colon and then the loopback address will place
446:53 and then the loopback address will place in a different subnet
446:55 in a different subnet so we're going to use 2012 and 2017.
447:04 well let's go ahead and enable rip
447:05 rip next generation on router two and before
447:07 next generation on router two and before we can do that we need to enable
447:09 we can do that we need to enable version six routing see by default a
447:12 version six routing see by default a router will route version four but not
447:14 router will route version four but not version six so
447:16 version six so we do that by typing in ipv6 unicast
447:19 we do that by typing in ipv6 unicast routing
447:21 routing and then we can enable our routing
447:22 and then we can enable our routing protocols
447:24 protocols so next we go to each interface we want
447:26 so next we go to each interface we want to enable
447:28 to enable rip on
447:30 rip on so first we'll go to interface serial
447:31 so first we'll go to interface serial zero zero
447:34 zero zero we simply type ipv6 rip and then we need
447:37 we simply type ipv6 rip and then we need to give it a process name
447:38 to give it a process name the rip process and we can run multiple
447:42 the rip process and we can run multiple multiple processes on this router
447:45 multiple processes on this router we don't use number we will use actually
447:47 we don't use number we will use actually a name
447:48 a name and we can name it pretty much anything
447:50 and we can name it pretty much anything you want for simplicity's sake we'll
447:52 you want for simplicity's sake we'll just say our process name is routing rip
447:56 just say our process name is routing rip ipv6 rip routing rip enable so we've
447:58 ipv6 rip routing rip enable so we've enabled it on
448:00 enabled it on interface serial zero zero
448:02 interface serial zero zero we will go ahead and do it on loopback
448:05 we will go ahead and do it on loopback one as well
448:06 one as well inserting it into the same rip process
448:11 inserting it into the same rip process now rip
448:12 now rip is still not running on this router
448:14 is still not running on this router until we enable it globally
448:28 router rip and then the process name which we have chosen as routing rip
448:37 now we will verify that it is running on router 2.
448:38 router 2. so ipv6 protocols there it is and you
448:41 so ipv6 protocols there it is and you see the interfaces as well
448:43 see the interfaces as well that are inserted into the rip process
448:47 that are inserted into the rip process now that being said we're not learning
448:48 now that being said we're not learning any routes
448:50 any routes because we are not
448:52 because we are not we've not established any neighbor
448:55 we've not established any neighbor because we haven't learned any routes
448:56 because we haven't learned any routes from any other ipv6 rip routers so on
448:59 from any other ipv6 rip routers so on router 4 we're going to go ahead and
449:01 router 4 we're going to go ahead and assign ip addresses
449:03 assign ip addresses to the appropriate interfaces
449:06 to the appropriate interfaces this on serial 0 1
449:09 this on serial 0 1 is the point to point
449:10 is the point to point so we will end this ip address with a
449:13 so we will end this ip address with a dot two
449:15 dot two sharing the same subnet
449:17 sharing the same subnet and then we will insert loopback one
449:21 and then we will insert loopback one into rip ultimately
449:23 into rip ultimately and we're gonna go ahead and assign it
449:25 and we're gonna go ahead and assign it to 0 1 8 so it's different than router
449:27 to 0 1 8 so it's different than router 2.
449:28 2. router 2's ip address was 2017
449:38 and then we're going to go ahead and enable rip on this router
449:41 enable rip on this router and again we need to enable unicast
449:44 and again we need to enable unicast routing
449:45 routing for version 6.
449:52 we need to insert the interfaces into the rip process
450:10 and again we'll use routing rip as our process id and here we've enabled it and
450:13 process id and here we've enabled it and let's do the same on loopback one
450:16 let's do the same on loopback one and it's as simple as typing up arrow
450:18 and it's as simple as typing up arrow now
450:22 and then finally we will enable it globally
450:38 and now you will see when we do show ipv6 protocols that it's enabled on
450:40 ipv6 protocols that it's enabled on router 4.
450:51 and now we can take a look at ipv6 rip and this shows what interfaces are
450:53 and this shows what interfaces are participating the administrative
450:55 participating the administrative distance and update intervals
451:03 and here's our routing table so we are learning the route from router 2
451:05 learning the route from router 2 which begins in 2017 so that is actively
451:08 which begins in 2017 so that is actively being advertised via rip and so we have
451:11 being advertised via rip and so we have version 6
451:13 version 6 that is rip next generation up and
451:15 that is rip next generation up and running between router 2 and router 4.
451:17 running between router 2 and router 4. it's rather straightforward
451:19 it's rather straightforward and on router 2 you will see
451:21 and on router 2 you will see the loopback from router 6 in his
451:24 the loopback from router 6 in his routing table as well so pretty
451:26 routing table as well so pretty straightforward
451:32 next let's talk about eigrp cisco originally created eigrp to
451:35 cisco originally created eigrp to advertise routes for ipv4
451:38 advertise routes for ipv4 ipx and apple talk
451:40 ipx and apple talk this original eigrp architecture
451:43 this original eigrp architecture easily allowed for yet another layer 3
451:45 easily allowed for yet another layer 3 protocol
451:47 protocol ipv6 to be added
451:49 ipv6 to be added as a result cisco did not have to change
451:51 as a result cisco did not have to change eigrp significantly to support version 6
451:55 eigrp significantly to support version 6 so there are many similarities that
451:57 so there are many similarities that exist between version 4 and version 6
452:00 exist between version 4 and version 6 versions of eigrp
452:03 versions of eigrp that being said there are some
452:04 that being said there are some differences and i've listed what you
452:06 differences and i've listed what you really need to know for the ccnp route
452:08 really need to know for the ccnp route exam
452:13 so let's go ahead and enable eigrp between router 2 and router 4.
452:22 so we already have ipv6 up and running let's go ahead under interface serial 0
452:25 let's go ahead under interface serial 0 enable eigrp
452:28 enable eigrp ipv6 eigrp we're going to use the
452:30 ipv6 eigrp we're going to use the process id of 10
452:32 process id of 10 and under loopback 1 we will also use
452:34 and under loopback 1 we will also use the process id of 10
452:41 and then very simply we just need to enable eigrp globally
452:50 and we do that via ip version 6 router eigrp process id 10.
452:55 router eigrp process id 10. and again we have to do a no shut
452:58 and again we have to do a no shut and if we look now we under ipv6
453:01 and if we look now we under ipv6 protocols
453:03 protocols we can see eigrp is running and the
453:05 we can see eigrp is running and the interfaces that are participating
453:07 interfaces that are participating pretty straightforward but again there's
453:09 pretty straightforward but again there's no communication with any eigrp
453:11 no communication with any eigrp neighbors
453:12 neighbors so let's go ahead
453:15 so let's go ahead and you'll see here
453:16 and you'll see here the topology table for router 2
453:19 the topology table for router 2 which just shows the local routes but
453:21 which just shows the local routes but again this idea of successor and
453:23 again this idea of successor and feasible successor should look familiar
453:25 feasible successor should look familiar to you
453:27 to you as it is in
453:29 as it is in ipv4 so now on router 4
453:33 ipv4 so now on router 4 we are also going to go ahead and enable
453:41 ip or eigrp and again we're going to use eigrp
453:43 and again we're going to use eigrp process id 10
453:44 process id 10 enable it under each interface that we
453:46 enable it under each interface that we would like to participate
453:48 would like to participate and then enable it globally
453:51 and then enable it globally once we do that the neighbor
453:52 once we do that the neighbor relationship between router 2 and router
453:54 relationship between router 2 and router 4 will come up
453:56 4 will come up over this point to point link
454:03 and we will see our neighbor right here
454:06 our neighbor right here so again you can see
454:08 so again you can see we have hold time up time looks looks
454:11 we have hold time up time looks looks very familiar to ipv4
454:13 very familiar to ipv4 it should look very familiar so in many
454:16 it should look very familiar so in many ways we're kind of slaying the beast
454:17 ways we're kind of slaying the beast once you get your hands on ipv6 it
454:20 once you get your hands on ipv6 it actually begins to look pretty familiar
454:26 let's look at our topology table and we will see what we've learned not only
454:28 will see what we've learned not only locally but from our neighbor
454:37 and then finally let's take a look at our eigrp routes
454:46 and there is the loopback from router 2 which we are learning on router 4 via
454:48 which we are learning on router 4 via eigrp
454:59 now regarding ospf in order to support ipv6
455:01 ipv6 an ietf working group took the ospf
455:04 an ietf working group took the ospf version 2 standard and made changes to
455:06 version 2 standard and made changes to the protocol to support version 6
455:09 the protocol to support version 6 resulting in the new protocol named ospf
455:12 resulting in the new protocol named ospf version 3.
455:14 version 3. to migrate to ipv6
455:17 to migrate to ipv6 routers run ospf version 2 for v4
455:20 routers run ospf version 2 for v4 support in version 3 for ipv6 support
455:30 finally let's go ahead and enable ospf between router 2 and router 4.
455:34 between router 2 and router 4. so on router 2 again we're using serial
455:36 so on router 2 again we're using serial 0 0 and loopback 1.
455:39 0 0 and loopback 1. we're going to place loopback 1 in a
455:40 we're going to place loopback 1 in a different area than serial 0 though
455:43 different area than serial 0 though so
455:44 so in interface serial zero zero we're
455:45 in interface serial zero zero we're gonna make that area zero so ipv6
455:48 gonna make that area zero so ipv6 process id10 we're gonna insert it into
455:50 process id10 we're gonna insert it into area zero and loopback one we're going
455:53 area zero and loopback one we're going to insert into area 24.
456:06 so this is not done like ipv4 obviously there's a pretty big difference here
456:07 there's a pretty big difference here you're enabling it under the interface
456:09 you're enabling it under the interface itself now we do need to enable ospf
456:12 itself now we do need to enable ospf globally still though it may not be
456:14 globally still though it may not be identical to version 4 but it does need
456:16 identical to version 4 but it does need to be enabled globally
456:18 to be enabled globally so we do that by ipv6 router ospf the
456:22 so we do that by ipv6 router ospf the process id
456:24 process id and that is it now let's go ahead and
456:27 and that is it now let's go ahead and enable it on router 4 as well
456:33 and we're going to do the same it will be for serial 0 1 and loop back 1.
456:37 be for serial 0 1 and loop back 1. so again under both interfaces we enable
456:40 so again under both interfaces we enable ospf
456:42 ospf via the
456:43 via the ipv6 ospf process id
456:47 ipv6 ospf process id we're going to insert the point-to-point
456:48 we're going to insert the point-to-point interface in area 0 and the loopback
456:51 interface in area 0 and the loopback interface will assign
456:53 interface will assign to a different area which is will create
456:55 to a different area which is will create area 34.
457:08 and then we enable ospf globally again process id 10.
457:18 and let's go ahead and take a look at our
457:20 our ospf
457:21 ospf routes
457:26 and there we have learn via ospf the loopback from router 2.
457:32 we can look at our ospf neighbors there is rudder 2 as our neighbor
457:35 is rudder 2 as our neighbor again this should look pretty familiar
457:37 again this should look pretty familiar to version four
457:39 to version four version six
457:40 version six ospf support it does not look all that
457:42 ospf support it does not look all that different than version four and here you
457:44 different than version four and here you see
457:45 see the lsas
457:51 you can see the similarities between ospf version 2 and version 3. there's
457:53 ospf version 2 and version 3. there's quite a few of them and understanding
457:55 quite a few of them and understanding the concepts of version 4 will certainly
457:57 the concepts of version 4 will certainly help you in understanding how version 6
458:00 help you in understanding how version 6 works
458:02 works so here's what you've learned you've had
458:03 so here's what you've learned you've had an overview of each of the version six
458:05 an overview of each of the version six routing protocols that you'll need to
458:07 routing protocols that you'll need to know for the exam and then you've seen
458:09 know for the exam and then you've seen actually how to enable them in the lab i
458:12 actually how to enable them in the lab i wish you the best of luck in your
458:13 wish you the best of luck in your studies thank you
458:37 hi this is david voss ccie11372 and in this video you're going
458:39 ccie11372 and in this video you're going to learn about
458:41 to learn about security threats and risks
458:44 security threats and risks security is a large portion of the ccda
458:47 security is a large portion of the ccda exam so you'll need to know everything
458:49 exam so you'll need to know everything in this video
458:54 it is important to be aware of the different types of attacks that can
458:57 different types of attacks that can impact your systems on the network
459:00 impact your systems on the network security threats can be classified into
459:02 security threats can be classified into three categories
459:04 three categories reconnaissance
459:06 reconnaissance gaining unauthorized access and denial
459:08 gaining unauthorized access and denial of service
459:09 of service the goal of reconnaissance
459:11 the goal of reconnaissance reconnaissance is to gather as much
459:13 reconnaissance is to gather as much information as possible
459:15 information as possible about the target network
459:18 about the target network getting unauthorized access obviously
459:20 getting unauthorized access obviously refers to the act of actually
459:22 refers to the act of actually attacking or exploiting the network
459:26 attacking or exploiting the network or host and then denial of service
459:30 or host and then denial of service these aim to overwhelm the resources on
459:32 these aim to overwhelm the resources on the network such as memory cpu
459:35 the network such as memory cpu and bandwidth and thus impact
459:38 and bandwidth and thus impact the target system
459:39 the target system and affect the devices on the network
459:42 and affect the devices on the network negatively
459:51 reconnaissance network tools are used to gather information
459:53 gather information from hosts attached to the network and
459:56 from hosts attached to the network and they have many capabilities they can
459:58 they have many capabilities they can determine the operating system
460:00 determine the operating system identify file permissions
460:03 identify file permissions trust relationships
460:05 trust relationships and user permissions as well
460:08 and user permissions as well here are some of the popular scanning
460:10 here are some of the popular scanning tools that are used
460:13 tools that are used kismet is an 802.11
460:16 kismet is an 802.11 wireless sniffer
460:18 wireless sniffer an ids system
460:20 an ids system and it can collect traffic from
460:22 and it can collect traffic from any 802.11
460:24 any 802.11 network
460:25 network it does this by detecting wireless
460:28 it does this by detecting wireless networks
460:29 networks even when they were hidden
460:31 even when they were hidden and then it can collect packets from
460:33 and then it can collect packets from those networks
460:35 those networks netstumbler
460:37 netstumbler is another wireless network scanner
460:41 is another wireless network scanner and it can
460:42 and it can discover and scan networks even if the
460:46 discover and scan networks even if the ssid
460:47 ssid is not being broadcast
460:50 is not being broadcast and then arguably the most popular is
460:52 and then arguably the most popular is nmap or network mapper
460:55 nmap or network mapper and it's designed to scan large networks
460:57 and it's designed to scan large networks or it can actually be used to
461:00 or it can actually be used to scan a single host
461:02 scan a single host it's an open source utility and it's
461:04 it's an open source utility and it's used for network exploration
461:07 used for network exploration and security audits
461:15 now there are different types of scanners such as vulnerability scanners
461:17 scanners such as vulnerability scanners and they determine the potential
461:19 and they determine the potential exposures that are present in the
461:20 exposures that are present in the network
461:22 network here are some of the more popular tools
461:24 here are some of the more popular tools used for vulnerability scanning
461:27 used for vulnerability scanning saint which is security administrators
461:30 saint which is security administrators integrated network tool is a
461:32 integrated network tool is a vulnerability assessment application
461:35 vulnerability assessment application mbsa microsoft baseline security
461:37 mbsa microsoft baseline security analyzer is used to scan systems and
461:40 analyzer is used to scan systems and identify whether
461:41 identify whether patches are missing from windows
461:43 patches are missing from windows products
461:45 products and nessus is designed to automate
461:48 and nessus is designed to automate testing discovery
461:50 testing discovery of known vulnerabilities it's an open
461:52 of known vulnerabilities it's an open source tool that runs on a variety
461:56 source tool that runs on a variety of operating systems
462:07 hackers use several techniques to gain system access
462:09 system access one approach is when unauthorized people
462:12 one approach is when unauthorized people use usernames and passwords
462:14 use usernames and passwords to escalate the accounts privilege
462:16 to escalate the accounts privilege levels
462:17 levels some system user accounts have default
462:19 some system user accounts have default administrative username and password
462:21 administrative username and password pairings
462:22 pairings that are common knowledge
462:25 that are common knowledge in some environments
462:27 in some environments there are passwords that are well known
462:29 there are passwords that are well known i'll give you one example
462:32 i'll give you one example i was at a large
462:34 i was at a large fortune 500 company
462:37 fortune 500 company and we did a security audit
462:39 and we did a security audit and we ran a password scanning tool
462:42 and we ran a password scanning tool and we found over 50 percent of the
462:45 and we found over 50 percent of the passwords
462:47 passwords were easily cracked within minutes
462:50 were easily cracked within minutes because
462:51 because those passwords were set to the name of
462:53 those passwords were set to the name of the company
462:55 the company obviously it would be rather easy to
462:57 obviously it would be rather easy to gain access to whatever system you would
463:00 gain access to whatever system you would like
463:01 like if half the company is using the same
463:03 if half the company is using the same password which can be easily guessed
463:07 password which can be easily guessed needless to say they fixed that problem
463:09 needless to say they fixed that problem with better security policies
463:13 with better security policies but
463:14 but unauthorized access isn't just about
463:16 unauthorized access isn't just about setting the appropriate password
463:18 setting the appropriate password it can also be obtained through the use
463:20 it can also be obtained through the use of social engineering
463:23 of social engineering actually most confidential information
463:25 actually most confidential information such as badges and usernames and
463:27 such as badges and usernames and passwords
463:28 passwords can be uncovered simply by walking
463:30 can be uncovered simply by walking around an organization
463:33 around an organization in addition to social engineering
463:35 in addition to social engineering hackers can obtain account information
463:37 hackers can obtain account information by using password cracking utilities
463:40 by using password cracking utilities or capturing network traffic
463:43 or capturing network traffic these automated software tools are very
463:45 these automated software tools are very powerful and as long as you have network
463:48 powerful and as long as you have network access in any way
463:50 access in any way they can easily be run
463:52 they can easily be run and you can easily obtain the
463:54 and you can easily obtain the information you need
463:55 information you need if security is not properly implemented
464:00 if security is not properly implemented next let's talk about security risks
464:03 next let's talk about security risks to protect network resources processes
464:05 to protect network resources processes and procedures
464:07 and procedures technology needs to address several
464:09 technology needs to address several security risks
464:12 security risks important network characteristics that
464:13 important network characteristics that can be at risk from security threats
464:15 can be at risk from security threats include data confidentiality
464:18 include data confidentiality data integrity and system availability
464:20 data integrity and system availability let's talk about that now
464:23 let's talk about that now daily confidentiality should ensure that
464:25 daily confidentiality should ensure that only legitimate users can view sensitive
464:27 only legitimate users can view sensitive information
464:30 information data integrity should ensure that only
464:32 data integrity should ensure that only authorized users can change critical
464:35 authorized users can change critical information
464:36 information and system availability should ensure
464:39 and system availability should ensure uninterrupted access to critical network
464:42 uninterrupted access to critical network and computing resources
464:47 in addition the use of redundant hardware and encryption
464:49 hardware and encryption can significantly reduce the risks
464:51 can significantly reduce the risks associated with all these three
464:54 associated with all these three system availability data integrity and
464:56 system availability data integrity and data confidentiality
464:59 data confidentiality next let's discuss targets
465:02 next let's discuss targets given the wide range of threats just
465:05 given the wide range of threats just about anything on the network is
465:07 about anything on the network is vulnerable and is a potential target
465:11 vulnerable and is a potential target individual hosts are usually the number
465:13 individual hosts are usually the number one thing that hackers are looking to
465:15 one thing that hackers are looking to access
465:17 access but they're especially susceptible to
465:19 but they're especially susceptible to worms and viruses
465:22 worms and viruses other high value targets include devices
465:24 other high value targets include devices that support the network
465:26 that support the network obviously this would be routers and
465:28 obviously this would be routers and switches
465:29 switches possibly even firewalls
465:32 possibly even firewalls dhcp servers and dns servers certainly
465:36 dhcp servers and dns servers certainly and management stations such as snmp or
465:39 and management stations such as snmp or even ip phones
465:42 even ip phones next let's talk about loss of
465:43 next let's talk about loss of availability or denial of service
465:46 availability or denial of service dos attacks try to block or deny access
465:50 dos attacks try to block or deny access to impact the availability of network
465:52 to impact the availability of network services
465:53 services here are some common failure points due
465:55 here are some common failure points due to ddos attacks a network device a host
465:58 to ddos attacks a network device a host or an application fails to process large
466:00 or an application fails to process large amounts of data sent to it
466:03 amounts of data sent to it that then crashes or breaks
466:04 that then crashes or breaks communication ability for that device
466:08 communication ability for that device a host or application is unable to
466:11 a host or application is unable to handle an unexpected condition that was
466:13 handle an unexpected condition that was sent to it
466:15 sent to it and therefore
466:16 and therefore there's resource depletion or failure
466:20 there's resource depletion or failure and nearly all dos attacks are carried
466:22 and nearly all dos attacks are carried out with spoofing or flooding methods
466:28 now that being said cisco provides you many tools to deal with this
466:31 many tools to deal with this and here they are for you now
466:34 and here they are for you now dhcp snooping
466:42 dynamic arp inspection unicast reverse path forwarding
466:49 access control lists and rate limiting
466:51 and rate limiting if you study this chart and know it well
466:53 if you study this chart and know it well you will most certainly be prepared for
466:55 you will most certainly be prepared for the ccda exam
466:57 the ccda exam when it comes to how to manage against
467:00 when it comes to how to manage against denial of service attacks
467:02 denial of service attacks when attackers change sensitive data
467:05 when attackers change sensitive data without authorization it's called an
467:06 without authorization it's called an integrity violation
467:09 integrity violation so for example an attacker might access
467:11 so for example an attacker might access financial data
467:13 financial data change it or delete it
467:15 change it or delete it it's important to use restrictive access
467:17 it's important to use restrictive access controls to prevent integrity violations
467:19 controls to prevent integrity violations and confidentiality attacks
467:22 and confidentiality attacks and here are some ways you can enforce
467:24 and here are some ways you can enforce access control and reduce risks
467:27 access control and reduce risks you can separate networks using vlans
467:29 you can separate networks using vlans and packet filtering firewalls
467:32 and packet filtering firewalls restrict access with operating system
467:34 restrict access with operating system based controls
467:36 based controls limit user access by using user profiles
467:40 limit user access by using user profiles and then use encryption techniques to
467:42 and then use encryption techniques to store your data
467:49 the security policies and organization employees
467:50 employees use what are called risk assessments and
467:53 use what are called risk assessments and cost benefit analysis
467:55 cost benefit analysis to reduce security risks
468:01 the following figure shows the three components of risk assessment
468:04 components of risk assessment control refers to how do you use the
468:07 control refers to how do you use the security policy
468:08 security policy to minimize potential risks
468:11 to minimize potential risks severity describes the level of the risk
468:14 severity describes the level of the risk to the organization
468:16 to the organization and probability is the likeness that an
468:18 and probability is the likeness that an attack against the assets will occur
468:22 attack against the assets will occur a risk assessment should explain
468:25 a risk assessment should explain what assets to secure
468:27 what assets to secure the value of those assets
468:30 the value of those assets the loss that would result from an
468:32 the loss that would result from an attack
468:33 attack the severity and probability of an
468:35 the severity and probability of an attack against the assets
468:38 attack against the assets and how to use a security policy to
468:40 and how to use a security policy to minimize the risks
468:42 minimize the risks of the attack
468:44 of the attack in many cases security costs can be
468:46 in many cases security costs can be justified by describing the loss of
468:48 justified by describing the loss of productivity or revenue
468:50 productivity or revenue that could occur during security
468:52 that could occur during security incidents
468:59 a risk index is used to consider the risks of potential threats
469:02 risks of potential threats the risk index is based on the risk
469:05 the risk index is based on the risk assessment components
469:07 assessment components which are severity of loss if the asset
469:09 which are severity of loss if the asset is compromised
469:10 is compromised probability of the risk actually
469:12 probability of the risk actually occurring and ability to control and
469:14 occurring and ability to control and manage the risk
469:17 manage the risk one approach to determining a risk index
469:19 one approach to determining a risk index is to give each risk factor a value from
469:22 is to give each risk factor a value from one to three one being the lowest risk
469:24 one to three one being the lowest risk and three being the highest
469:26 and three being the highest so for example a high severity risk
469:28 so for example a high severity risk would have a substantial impact
469:31 would have a substantial impact on the users or the organization
469:34 on the users or the organization medium severity risks would have an
469:36 medium severity risks would have an effect on a single department
469:39 effect on a single department and low severity risks would have
469:41 and low severity risks would have limited impact
469:43 limited impact the risk index is calculated by
469:45 the risk index is calculated by multiplying the severity times the
469:47 multiplying the severity times the probability factor
469:48 probability factor and then dividing by the control factor
469:52 and then dividing by the control factor the following is an example of a risk
469:54 the following is an example of a risk index calculation for a typical large
469:57 index calculation for a typical large corporation
470:05 so here's what you've learned you've received a really good introduction to
470:06 received a really good introduction to security and i know there's a lot in
470:08 security and i know there's a lot in this video actually but yes it is just
470:10 this video actually but yes it is just an introduction still
470:12 an introduction still you've learned about network attacks
470:13 you've learned about network attacks reconnaissance scanners vulnerability
470:16 reconnaissance scanners vulnerability software
470:18 software security risks and targets denial of
470:20 security risks and targets denial of service
470:22 service preventing breaches
470:23 preventing breaches and performing risk assessments all of
470:26 and performing risk assessments all of these
470:27 these were basic introductions
470:29 were basic introductions but at the level you will need for your
470:31 but at the level you will need for your ccda exam
470:33 ccda exam there again is plenty to learn after
470:35 there again is plenty to learn after this but this lays a solid foundation
470:38 this but this lays a solid foundation for you moving forward in your studies
470:40 for you moving forward in your studies good luck
471:02 hi this is david voss ccie11372 and in this video we're
471:04 ccie11372 and in this video we're covering security policy and process
471:08 covering security policy and process in this video you're going to learn
471:09 in this video you're going to learn about network security elements and then
471:12 about network security elements and then we're going to dig a deep dive into
471:15 we're going to dig a deep dive into security policies including their
471:17 security policies including their purpose
471:18 purpose the development of security policies and
471:20 the development of security policies and the security policy life cycle
471:23 the security policy life cycle so let's begin
471:25 so let's begin to provide the proper levels of security
471:28 to provide the proper levels of security and increased network availability a
471:30 and increased network availability a policy a security policy
471:32 policy a security policy is a crucial element in providing secure
471:35 is a crucial element in providing secure network services
471:37 network services it's an important concept to understand
471:39 it's an important concept to understand not just for the ccda exam but
471:42 not just for the ccda exam but to function in today's environments
471:44 to function in today's environments where security is so crucial
471:47 where security is so crucial business requirements and risk analysis
471:49 business requirements and risk analysis are used in the development of security
471:51 are used in the development of security policy and it is often a balance between
471:54 policy and it is often a balance between ease of access versus the security risk
471:57 ease of access versus the security risk and cost of implementing the security
471:59 and cost of implementing the security technology when making decisions
472:02 technology when making decisions in terms of network security in the
472:03 in terms of network security in the system life cycle the business needs are
472:06 system life cycle the business needs are a key area to consider
472:08 a key area to consider these needs define what the business
472:11 these needs define what the business wants to do with the network
472:13 wants to do with the network risk analysis is another part of the
472:15 risk analysis is another part of the system life cycle which explains the
472:17 system life cycle which explains the risks and their costs
472:20 risks and their costs so business needs and risk assessment
472:22 so business needs and risk assessment feed information to formulate the
472:25 feed information to formulate the security policy
472:27 security policy the security policy describes the
472:29 the security policy describes the organization's processes procedures
472:32 organization's processes procedures guidelines and standards
472:38 finally an organization security team needs to have the processes and
472:40 needs to have the processes and procedures defined
472:42 procedures defined this information helps explain what
472:44 this information helps explain what needs to happen for instance response
472:48 needs to happen for instance response security monitoring
472:49 security monitoring maintenance
472:50 maintenance and compliance
472:53 and compliance as you can see here the concerti
472:55 as you can see here the concerti consideration
472:56 consideration is prefaced with a question
472:59 is prefaced with a question and then you can see what aspect
473:02 and then you can see what aspect of security preparation and policies and
473:04 of security preparation and policies and procedures
473:05 procedures can deal with that consideration
473:08 can deal with that consideration it's key that you memorize this chart
473:10 it's key that you memorize this chart for the ccda exam
473:19 rfc 2196 says a security policy is a formal statement of the rules by which
473:22 formal statement of the rules by which people who are given access
473:24 people who are given access to an organization's technology and
473:26 to an organization's technology and information assets must abide
473:29 information assets must abide so when you are developing security
473:30 so when you are developing security policies for an organization
473:33 policies for an organization rfc 2196 can serve as a guide
473:36 rfc 2196 can serve as a guide for developing security processes and
473:38 for developing security processes and procedures
473:40 procedures the basic approach of creating a
473:41 the basic approach of creating a security policy is to identify what you
473:44 security policy is to identify what you are trying to protect
473:46 are trying to protect determine what you're trying to protect
473:48 determine what you're trying to protect it from
473:49 it from determine how likely the threats are
473:52 determine how likely the threats are implement measures that protect your
473:54 implement measures that protect your assets in a cost effective manner
473:56 assets in a cost effective manner and then review the process continuously
473:59 and then review the process continuously and make improvements each time a
474:01 and make improvements each time a weakness is found
474:04 weakness is found one of the main purposes of a security
474:06 one of the main purposes of a security policy is to describe the roles and
474:08 policy is to describe the roles and requirements for securing technology and
474:10 requirements for securing technology and information assets
474:12 information assets the policy defines the ways in which
474:13 the policy defines the ways in which these requirements will be met
474:16 these requirements will be met there are two main reasons for having a
474:18 there are two main reasons for having a security policy first it provides the
474:20 security policy first it provides the framework for the security
474:22 framework for the security implementation
474:23 implementation and then it creates a security baseline
474:26 and then it creates a security baseline of the current security posture
474:29 of the current security posture here are some questions you might ask
474:31 here are some questions you might ask when developing a security policy
474:34 when developing a security policy what data and assets will be included in
474:36 what data and assets will be included in the policy what network communication is
474:39 the policy what network communication is permitted between hosts
474:42 permitted between hosts how will policies be implemented
474:44 how will policies be implemented and how the latest attacks impact your
474:46 and how the latest attacks impact your network in security systems
474:49 network in security systems a security policy is divided into
474:51 a security policy is divided into smaller parts that help describe the
474:53 smaller parts that help describe the overall risk management policy
474:55 overall risk management policy identification of assets and where
474:57 identification of assets and where security should be applied
475:00 security should be applied there are other documents which
475:01 there are other documents which concentrate on specific areas of risk
475:04 concentrate on specific areas of risk management
475:05 management the acceptable use policy
475:08 the acceptable use policy this document defines the roles and
475:10 this document defines the roles and responsibilities within risk management
475:12 responsibilities within risk management network access control policy
475:15 network access control policy defines access control principles used
475:17 defines access control principles used in the network
475:19 in the network and how data is classified
475:21 and how data is classified security management policy explains how
475:23 security management policy explains how to manage the security infrastructure
475:26 to manage the security infrastructure and then incident handling policy
475:27 and then incident handling policy defines the processes
475:29 defines the processes and procedures for managing security
475:31 and procedures for managing security incidents
475:34 incidents if you look at this chart and memorize
475:36 if you look at this chart and memorize it you'll do excellent on this portion
475:38 it you'll do excellent on this portion of your ccda exam
475:44 as requirements change and new technology is developed the network
475:46 technology is developed the network security policy needs to be updated to
475:48 security policy needs to be updated to reflect those changes
475:50 reflect those changes so here are some steps that are used to
475:52 so here are some steps that are used to facilitate the continuing efforts
475:54 facilitate the continuing efforts in the maintenance of security policies
475:58 in the maintenance of security policies secure monitor test and improve
476:02 secure monitor test and improve secure means identification
476:04 secure means identification authentication acls
476:06 authentication acls vpns
476:08 vpns monitor intrusion and content-based
476:10 monitor intrusion and content-based detection and response
476:12 detection and response test is assessment vulnerability
476:14 test is assessment vulnerability scanning and security auditing
476:17 scanning and security auditing and improve is for data analysis
476:19 and improve is for data analysis reporting and intelligent network
476:20 reporting and intelligent network security
476:28 today's network designs demonstrate an increased use of security mechanisms
476:31 increased use of security mechanisms and have become more tightly integrated
476:32 and have become more tightly integrated with network design
476:35 with network design trust and identity management is a part
476:36 trust and identity management is a part of the safe security reference
476:38 of the safe security reference architecture
476:40 architecture and is crucial for the development of a
476:42 and is crucial for the development of a secure network design
476:44 secure network design this management of trust and identity
476:47 this management of trust and identity defines who and what can access the
476:48 defines who and what can access the network when
476:50 network when where and how that access can occur
476:55 where and how that access can occur if you take a look at the following
476:56 if you take a look at the following diagram
476:58 diagram it shows the main three components of
477:00 it shows the main three components of trust and identity identity management
477:02 trust and identity identity management our trust
477:03 our trust identity and access control so let's
477:05 identity and access control so let's talk about each of these three
477:07 talk about each of these three trust is the relationship between two or
477:09 trust is the relationship between two or more network entities
477:10 more network entities that are permitted to communicate
477:13 that are permitted to communicate domains of trust are a way
477:16 domains of trust are a way to group network systems that share a
477:17 to group network systems that share a common policy or function
477:20 common policy or function network segments have different trust
477:21 network segments have different trust values depending on the resources they
477:24 values depending on the resources they are securing
477:25 are securing therefore domains of trust can be
477:27 therefore domains of trust can be applied
477:28 applied these types of security controls can be
477:30 these types of security controls can be applied to network segments
477:32 applied to network segments as it is important to consider the trust
477:34 as it is important to consider the trust relationships
477:35 relationships between segments
477:38 between segments here's an example of domains of trust
477:41 here's an example of domains of trust you have your internet
477:43 you have your internet internet access edge
477:45 internet access edge and then your dmz and then your internal
477:48 and then your dmz and then your internal network each of those are separate
477:50 network each of those are separate domains
477:51 domains obviously on the internal network you
477:53 obviously on the internal network you just want the appropriate internal users
477:55 just want the appropriate internal users in the dmz you're allowing a blending of
477:58 in the dmz you're allowing a blending of the two and on the internet obviously
478:00 the two and on the internet obviously you just are expecting for there only to
478:02 you just are expecting for there only to be exterior
478:04 be exterior users on that portion of the network so
478:07 users on that portion of the network so how you apply security will greatly
478:09 how you apply security will greatly depend on the domain of trust you are
478:12 depend on the domain of trust you are trying to protect
478:14 trying to protect identity is the who of a trust
478:16 identity is the who of a trust relationship these can be users devices
478:19 relationship these can be users devices or organizations or or a combination of
478:21 or organizations or or a combination of all of the above
478:23 all of the above network entities are validated by
478:25 network entities are validated by credentials and authentication of the
478:27 credentials and authentication of the identity is based on the following
478:29 identity is based on the following attributes
478:30 attributes something the subject knows such as a
478:32 something the subject knows such as a password
478:33 password something the subject has such as a
478:35 something the subject has such as a possession
478:36 possession and something the subject is such as a
478:38 and something the subject is such as a human characteristic fingerprint retina
478:41 human characteristic fingerprint retina scan etc
478:42 scan etc the first two are the most likely and
478:44 the first two are the most likely and the most popular ways of securing
478:47 the most popular ways of securing something you know and something you
478:49 something you know and something you have with you
478:51 have with you most companies are now expecting
478:52 most companies are now expecting two-factor authentication
478:57 so here's what you've learned you've learned about network security elements
479:00 learned about network security elements and then we dug into security policies
479:03 and then we dug into security policies in detail
479:05 in detail at least enough for you to know for your
479:07 at least enough for you to know for your ccda exam by digging into the purpose
479:10 ccda exam by digging into the purpose development and life cycle of security
479:12 development and life cycle of security policies
479:13 policies if you know what's in this video i'm
479:14 if you know what's in this video i'm confident you'll do well in this portion
479:16 confident you'll do well in this portion of the ccda
479:18 of the ccda good luck in your studies
479:44 hi this is david voss ccie 11372 and in this video you're going to learn about
479:47 this video you're going to learn about cisco safe
479:49 cisco safe specifically we're going to do an
479:50 specifically we're going to do an overview of cisco safe and then we will
479:53 overview of cisco safe and then we will talk about securing the individual
479:56 talk about securing the individual modules of the enterprise campus
479:58 modules of the enterprise campus so let's begin
480:00 so let's begin the cisco safe or security architecture
480:03 the cisco safe or security architecture for the enterprise
480:05 for the enterprise blueprint provides to network and
480:07 blueprint provides to network and security designers guidelines for
480:10 security designers guidelines for implementing security mechanisms for the
480:12 implementing security mechanisms for the cisco campus design
480:14 cisco campus design the safe blueprint follows the
480:16 the safe blueprint follows the enterprise composite network modular
480:18 enterprise composite network modular approach
480:19 approach presented throughout this entire
480:22 presented throughout this entire video series
480:24 video series all of the safe strategies are applied
480:26 all of the safe strategies are applied to each module and component of the
480:28 to each module and component of the enterprise architecture model's design
480:32 enterprise architecture model's design from a network design standpoint the
480:34 from a network design standpoint the safe blueprint is a security
480:36 safe blueprint is a security architecture that covers the following
480:38 architecture that covers the following aspects
480:40 aspects attack mitigation policy
480:42 attack mitigation policy enterprise-wide deployment
480:44 enterprise-wide deployment secure reporting and management
480:47 secure reporting and management authentication and authorization
480:50 authentication and authorization ids and ongoing support for emerging
480:53 ids and ongoing support for emerging technology
480:55 technology the policy for attack mitigation ensures
480:57 the policy for attack mitigation ensures that possible attacks and threats
481:00 that possible attacks and threats to the organization can be identified
481:02 to the organization can be identified and defines the countermeasures that
481:04 and defines the countermeasures that will be used against those attacks
481:07 will be used against those attacks the safe blueprint is usually applied in
481:09 the safe blueprint is usually applied in an enterprise-wide deployment
481:11 an enterprise-wide deployment not just to an isolated component
481:14 not just to an isolated component it also provides methods and mechanisms
481:16 it also provides methods and mechanisms for ensuring that the reporting
481:18 for ensuring that the reporting management and auditing
481:20 management and auditing are accomplished in a secure fashion
481:22 are accomplished in a secure fashion it includes secure authentication and
481:24 it includes secure authentication and authorization
481:26 authorization with strong encryption and digital
481:29 with strong encryption and digital signing techniques including public key
481:31 signing techniques including public key infrastructure pki
481:34 infrastructure pki it also includes intrusion detection
481:36 it also includes intrusion detection services for critical resources and
481:39 services for critical resources and networks
481:40 networks the safe blueprint provides ongoing
481:42 the safe blueprint provides ongoing support from cisco for all the emerging
481:45 support from cisco for all the emerging technologies it provides
481:51 the safe blueprint allows you to apply a systematic approach to security from a
481:54 systematic approach to security from a modular standpoint
481:56 modular standpoint risk at the internet connectivity block
481:58 risk at the internet connectivity block would include the following
482:00 would include the following reconnaissance tools
482:02 reconnaissance tools port scanning tools
482:04 port scanning tools ip mapping tools mail relay
482:08 ip mapping tools mail relay distributed denial of service
482:10 distributed denial of service and malware including malicious code
482:12 and malware including malicious code viruses
482:14 viruses trojan horses and worms
482:17 trojan horses and worms in order to secure the internet
482:19 in order to secure the internet connectivity block the safe blueprint
482:21 connectivity block the safe blueprint recommends the use of firewalls
482:23 recommends the use of firewalls router access lists and network ids to
482:26 router access lists and network ids to mitigate the risks presented
482:28 mitigate the risks presented already
482:30 already you should also consider hardening the
482:32 you should also consider hardening the network devices and servers in that
482:34 network devices and servers in that particular block
482:35 particular block you can also build dmz networks
482:38 you can also build dmz networks to isolate specific devices from the
482:40 to isolate specific devices from the network infrastructure for many
482:42 network infrastructure for many organizations the e-commerce block may
482:44 organizations the e-commerce block may get its internet connectivity through
482:46 get its internet connectivity through the internet connectivity block
482:48 the internet connectivity block or it may have its own connections to an
482:50 or it may have its own connections to an isp
482:51 isp regardless of this aspect
482:53 regardless of this aspect the risks and guidelines for the
482:55 the risks and guidelines for the e-commerce block are very similar to the
482:57 e-commerce block are very similar to the internet con connectivity block
482:59 internet con connectivity block recommendations
483:00 recommendations according to the safe blueprint in this
483:03 according to the safe blueprint in this block you should protect high profile
483:04 block you should protect high profile ecommerce servers
483:06 ecommerce servers as this is where you will also encounter
483:08 as this is where you will also encounter the defacing of web services technique
483:12 the defacing of web services technique the e-commerce block is also vulnerable
483:14 the e-commerce block is also vulnerable to denial of service and distributed
483:17 to denial of service and distributed denial of service attacks
483:20 denial of service attacks counter measures in the e-commerce block
483:22 counter measures in the e-commerce block involve using access lists filtering and
483:24 involve using access lists filtering and firewalls that protect the database
483:27 firewalls that protect the database applications
483:28 applications or transaction servers
483:31 or transaction servers the server should be hardened by using
483:33 the server should be hardened by using only the necessary applications and
483:35 only the necessary applications and ports
483:36 ports ensure that the e-commerce applications
483:38 ensure that the e-commerce applications are secure
483:39 are secure by frequently updating and patching them
483:42 by frequently updating and patching them cisco ids should also be used and the
483:45 cisco ids should also be used and the e-commerce block should be placed into a
483:48 e-commerce block should be placed into a dedicated dmz zone
483:50 dedicated dmz zone to isolate it from other blocks of the
483:52 to isolate it from other blocks of the network
483:57 the vpn and remote access block is often connected through the internet
483:59 connected through the internet connectivity block to various internet
484:01 connectivity block to various internet service providers so you should use
484:03 service providers so you should use common techniques for securing it
484:06 common techniques for securing it however
484:07 however because you will be using vpn
484:08 because you will be using vpn technologies some unique security
484:10 technologies some unique security mechanisms can be implemented
484:12 mechanisms can be implemented because remote access and vpn networks
484:14 because remote access and vpn networks often use the public internet or pstn as
484:17 often use the public internet or pstn as their carrier you should be aware of
484:19 their carrier you should be aware of possible spoofing techniques that will
484:22 possible spoofing techniques that will allow an attacker to impersonate a
484:23 allow an attacker to impersonate a legitimate client and get remote access
484:26 legitimate client and get remote access or vpn access to the enterprise network
484:29 or vpn access to the enterprise network the network becomes vulnerable to
484:31 the network becomes vulnerable to spoofing if the attacker is able to
484:33 spoofing if the attacker is able to steal credentials or guess the
484:34 steal credentials or guess the authentication key
484:37 authentication key in order to secure the remote access
484:38 in order to secure the remote access block you should carefully implement vpn
484:41 block you should carefully implement vpn technologies using dedicated equipment
484:43 technologies using dedicated equipment which includes advanced security
484:45 which includes advanced security mechanisms
484:47 mechanisms you can use the ipsec protocol to assure
484:50 you can use the ipsec protocol to assure proper authentication authorization and
484:53 proper authentication authorization and and ids and firewall equipment can be
484:55 and ids and firewall equipment can be used as well
484:58 used as well in order to secure the wam block
484:59 in order to secure the wam block according to the safe blueprint vpn
485:01 according to the safe blueprint vpn techniques are used to ensure
485:03 techniques are used to ensure point-to-point secure connections
485:06 point-to-point secure connections you should also use strong cryptography
485:08 you should also use strong cryptography methods such as triple des or aes
485:11 methods such as triple des or aes to provide the confidentiality and
485:13 to provide the confidentiality and integrity of the data packets
485:16 integrity of the data packets in addition use authentication with all
485:18 in addition use authentication with all the wan peers and harden the lan routers
485:21 the wan peers and harden the lan routers to ensure that only the necessary
485:23 to ensure that only the necessary protocols and ports are used
485:26 protocols and ports are used additional security measures including
485:28 additional security measures including using filtering techniques based on
485:30 using filtering techniques based on cisco access lists and on network
485:32 cisco access lists and on network devices
485:37 the network management sub-module must be secured and it's especially
485:38 be secured and it's especially vulnerable to inside attacks
485:41 vulnerable to inside attacks the written security policy should
485:43 the written security policy should describe the procedures that apply to
485:45 describe the procedures that apply to this sub-module
485:46 this sub-module and a best practice is using aaa
485:48 and a best practice is using aaa services these are usually based on
485:51 services these are usually based on radius or tacx servers that will provide
485:54 radius or tacx servers that will provide authentication
485:56 authentication other possible problems might involve
485:58 other possible problems might involve administrator impersonation for
486:00 administrator impersonation for individuals who might want to get
486:02 individuals who might want to get administrative level privileges
486:04 administrative level privileges that will provide them access to all the
486:07 that will provide them access to all the other blocks in the enterprise campus
486:08 other blocks in the enterprise campus module
486:10 module in order to mitigate these threats you
486:11 in order to mitigate these threats you should use strong encryption techniques
486:14 should use strong encryption techniques and ssh instead of telnet for remote
486:17 and ssh instead of telnet for remote administration
486:24 in the server farm block the main goal is to protect the servers using strong
486:26 is to protect the servers using strong and secure operating systems and
486:27 and secure operating systems and applications
486:29 applications the servers should be periodically
486:31 the servers should be periodically verified to ensure that they have all
486:32 verified to ensure that they have all the proper updates and patches
486:35 the proper updates and patches and that they are hardened
486:37 and that they are hardened the server farm block can include
486:39 the server farm block can include firewall policies that will assure
486:41 firewall policies that will assure proper access control as well as switch
486:43 proper access control as well as switch acls that will only allow certain
486:45 acls that will only allow certain traffic to flow at the data length layer
486:48 traffic to flow at the data length layer ids should also be used in this block to
486:50 ids should also be used in this block to ensure connectivity
486:52 ensure connectivity to other campus blocks
486:55 to other campus blocks the access layer block is the place
486:57 the access layer block is the place where the end hosts and the lower end
486:59 where the end hosts and the lower end access switches are located
487:01 access switches are located in order to secure them you should use
487:03 in order to secure them you should use hiddes hids technologies
487:05 hiddes hids technologies in addition to the standard hardening
487:07 in addition to the standard hardening techniques
487:08 techniques which will only allow the necessary
487:10 which will only allow the necessary application services and ports to run if
487:14 application services and ports to run if the access layer block also includes
487:16 the access layer block also includes complex ip telephony integration
487:18 complex ip telephony integration special measures must be taken to a
487:20 special measures must be taken to a secure the voip infrastructure
487:27 so here's what you've learned you've received an overview of cisco safe
487:29 received an overview of cisco safe and then you've learned about securing
487:30 and then you've learned about securing the individual modules of the enterprise
487:33 the individual modules of the enterprise campus
487:34 campus all this information you will definitely
487:36 all this information you will definitely need to know for your ccda exam good
487:39 need to know for your ccda exam good luck in your studies
488:06 and in this video you're going to learn about security management
488:09 about security management specifically you're going to learn about
488:11 specifically you're going to learn about security threats and risks
488:13 security threats and risks security targets security policies and
488:16 security targets security policies and then threat defense
488:18 then threat defense so let's begin
488:20 so let's begin the ccda candidate must understand the
488:23 the ccda candidate must understand the reasons for network security
488:26 reasons for network security including the systematic approaches to
488:27 including the systematic approaches to managing security
488:30 managing security cisco invented a concept called
488:33 cisco invented a concept called self-defending network
488:35 self-defending network which describes the network
488:36 which describes the network infrastructure and the services used
488:39 infrastructure and the services used in order for the network to respond to
488:41 in order for the network to respond to attacks
488:43 attacks first let's talk about security threats
488:45 first let's talk about security threats and risks
488:46 and risks efficient security mechanisms must
488:49 efficient security mechanisms must address organizational threats
488:51 address organizational threats and mitigate risks successfully
488:54 and mitigate risks successfully the network designer
488:56 the network designer should create a secure environment for
488:58 should create a secure environment for the organization
488:59 the organization by doing everything he can to prevent
489:01 by doing everything he can to prevent attacks
489:02 attacks while ensuring that the security
489:04 while ensuring that the security features have minimal effect on end user
489:07 features have minimal effect on end user productivity
489:09 productivity a network security implementation must
489:11 a network security implementation must mitigate multiple factors
489:13 mitigate multiple factors and accomplish the following
489:15 and accomplish the following block outside malicious users from
489:17 block outside malicious users from getting access to the network
489:19 getting access to the network allow only system hardware and
489:21 allow only system hardware and application access to authorized users
489:24 application access to authorized users prevent attacks from being sourced
489:26 prevent attacks from being sourced internally
489:28 internally support different levels of user access
489:31 support different levels of user access using an access control policy and
489:34 using an access control policy and safeguard the data from being changed
489:36 safeguard the data from being changed modified or stolen
489:40 modified or stolen the next thing we will concern ourselves
489:42 the next thing we will concern ourselves with are the targets what are the
489:44 with are the targets what are the targets on the network and this helps
489:46 targets on the network and this helps you develop a good security policy and
489:49 you develop a good security policy and posture
489:50 posture targets on the network include the
489:52 targets on the network include the following any kind of network
489:53 following any kind of network infrastructure device such as a switch
489:56 infrastructure device such as a switch router security appliance or wireless
489:58 router security appliance or wireless access point
489:59 access point network services such as dns icmp dhcp
490:04 network services such as dns icmp dhcp endpoint devices especially management
490:07 endpoint devices especially management stations that perform in-band or
490:09 stations that perform in-band or out-of-band management
490:11 out-of-band management and network bandwidth which can be
490:12 and network bandwidth which can be overwhelmed by denial of service attacks
490:16 overwhelmed by denial of service attacks the security policy is a small part of a
490:18 the security policy is a small part of a larger network security system life
490:20 larger network security system life cycle
490:21 cycle that is driven by an assessment of the
490:23 that is driven by an assessment of the business needs and comprehensive risk
490:26 business needs and comprehensive risk analysis
490:27 analysis risk assessment may also need to be
490:30 risk assessment may also need to be performed
490:31 performed using penetration testing and
490:33 using penetration testing and vulnerability scanning tools
490:36 vulnerability scanning tools the security policy
490:38 the security policy should contain written documents
490:40 should contain written documents that include the following
490:43 that include the following guidelines
490:45 guidelines processes
490:46 processes standards
490:48 standards acceptable use policies
490:51 acceptable use policies architectures and infrastructure
490:53 architectures and infrastructure elements used
490:55 elements used and then granular areas of security
490:57 and then granular areas of security policy such as internet use policy
491:00 policy such as internet use policy or access control policy
491:03 or access control policy the most important aspects covered by
491:05 the most important aspects covered by the written security policy and
491:06 the written security policy and procedures are
491:08 procedures are identifying the company's assets
491:10 identifying the company's assets determining how the organization owns
491:13 determining how the organization owns assets are used
491:15 assets are used defining communication roles and
491:17 defining communication roles and responsibilities
491:19 responsibilities describing existing tools and processes
491:22 describing existing tools and processes defining the security incident handling
491:25 defining the security incident handling process
491:26 process and then a steering committee will
491:28 and then a steering committee will review and eventually publish
491:30 review and eventually publish this security policy after all the
491:32 this security policy after all the important documents have been finalized
491:36 important documents have been finalized some of the best practices for
491:37 some of the best practices for protecting the network infrastructure
491:40 protecting the network infrastructure through trust and identity include the
491:42 through trust and identity include the following
491:43 following use
491:44 use aaa services with the cisco acs server
491:53 use 802.1x port authentication
491:55 port authentication logging using syslog
491:57 logging using syslog and
491:58 and sde this is a protocol used by cisco ids
492:03 sde this is a protocol used by cisco ids and ips sensors to send information
492:05 and ips sensors to send information to the management stations
492:08 to the management stations using ssh instead of telnet to avoid any
492:11 using ssh instead of telnet to avoid any management traffic crossing the the
492:13 management traffic crossing the the network in clear text
492:16 network in clear text using secure versions of management
492:18 using secure versions of management protocols such as snmp version 3
492:21 protocols such as snmp version 3 ntp version 3 and sftp
492:26 ntp version 3 and sftp harden all network devices by making
492:27 harden all network devices by making sure unnecessary services are disabled
492:31 sure unnecessary services are disabled use authentication between devices that
492:33 use authentication between devices that are running dynamic routing protocols
492:36 are running dynamic routing protocols use the cisco one step lockdown feature
492:39 use the cisco one step lockdown feature on network devices to harden them
492:42 on network devices to harden them use acls to restrict management access
492:45 use acls to restrict management access allowing only certain hosts to access
492:47 allowing only certain hosts to access the network devices
492:50 the network devices use ipsec as an internal encryption
492:52 use ipsec as an internal encryption method
492:53 method or external vpn solution
492:56 or external vpn solution and then use cisco network admission
492:58 and then use cisco network admission control solution
493:00 control solution which ensures that network clients and
493:02 which ensures that network clients and servers are patched and updated in an
493:05 servers are patched and updated in an automated and centralized fashion
493:14 so here's what you've learned you've learned about security threats and risks
493:17 learned about security threats and risks security targets
493:18 security targets security policies and threat defense all
493:21 security policies and threat defense all these you will need to understand
493:24 these you will need to understand not only for your ccda exam but also to
493:26 not only for your ccda exam but also to support your own network good luck in
493:28 support your own network good luck in your studies
493:50 hi this is david voss cci11372 and in this video you're going
493:53 cci11372 and in this video you're going to learn about traditional voice systems
493:55 to learn about traditional voice systems specifically we're going to do an
493:57 specifically we're going to do an overview
493:58 overview and then we'll dig into a pbx telephony
494:02 and then we'll dig into a pbx telephony signaling
494:03 signaling public switch telephone number numbering
494:05 public switch telephone number numbering plan
494:06 plan and then pstn services
494:08 and then pstn services so let's begin
494:10 so let's begin the network designer's role in voice
494:12 the network designer's role in voice solutions is very important because
494:15 solutions is very important because regardless of the infrastructure vendor
494:17 regardless of the infrastructure vendor voice transport scenarios
494:20 voice transport scenarios often suffer from poor planning and
494:22 often suffer from poor planning and implementation
494:24 implementation most large organizations choose their
494:26 most large organizations choose their voice architecture including
494:28 voice architecture including pstn and pbx solutions
494:31 pstn and pbx solutions based on the financial stability
494:34 based on the financial stability of the manufacturer
494:36 of the manufacturer the support level they offer
494:38 the support level they offer and the competitive pricing of the
494:40 and the competitive pricing of the hardware
494:41 hardware software
494:42 software and maintenance components
494:45 and maintenance components cisco is one of the main providers of
494:48 cisco is one of the main providers of emerging integrated voice and video
494:50 emerging integrated voice and video solutions
494:56 when human voice is transported digitally over a network infrastructure
494:59 digitally over a network infrastructure a process of analog to digital
495:01 a process of analog to digital conversion takes place
495:04 conversion takes place the most common conversion mechanism is
495:06 the most common conversion mechanism is pcm pulse code
495:09 pcm pulse code modulation
495:11 modulation this is the process
495:12 this is the process of digitizing analog voice signals
495:15 of digitizing analog voice signals as you see here
495:21 during the pcm process the following things occur
495:22 things occur excess noise is filtered so the only
495:25 excess noise is filtered so the only basic human voice frequency is captured
495:29 basic human voice frequency is captured a process called
495:31 a process called pam or pulse amplitude modulation
495:34 pam or pulse amplitude modulation is used to sample the analog signal the
495:38 is used to sample the analog signal the signal is digitized and transposed into
495:41 signal is digitized and transposed into a series of ones and zeros this process
495:44 a series of ones and zeros this process includes quantizing the signal and
495:47 includes quantizing the signal and companding that is compressing and
495:50 companding that is compressing and expanding the signal
495:52 expanding the signal pstn and pbx are traditionally the main
495:55 pstn and pbx are traditionally the main processes of providing voice services
495:57 processes of providing voice services throughout the industry
495:59 throughout the industry pstn is a network that provides
496:01 pstn is a network that provides residential telephony services while pbx
496:05 residential telephony services while pbx provides telephony services to users
496:07 provides telephony services to users within an organization
496:10 within an organization pbx's are business phone systems that
496:12 pbx's are business phone systems that offer the following features
496:15 offer the following features call forwarding call transferring
496:18 call forwarding call transferring call parking
496:19 call parking conference calls music on hold
496:22 conference calls music on hold call history and voicemail
496:25 call history and voicemail most pbxs are digital devices that are
496:28 most pbxs are digital devices that are used in the private sector
496:30 used in the private sector and are miniature versions of phone
496:32 and are miniature versions of phone switches
496:33 switches they can scale to thousands of phones
496:35 they can scale to thousands of phones within a company
496:37 within a company a downside of pbx technology for from an
496:40 a downside of pbx technology for from an administrator
496:42 administrator point of view
496:43 point of view is that it is generally difficult to
496:45 is that it is generally difficult to configure and maintain
496:47 configure and maintain and each vendor has a unique
496:48 and each vendor has a unique configuration process so
496:51 configuration process so special training is required when
496:52 special training is required when working with a new pbx solution
496:56 working with a new pbx solution pbx systems also connect and link to
496:58 pbx systems also connect and link to remote offices and branch offices that
497:01 remote offices and branch offices that include their own pbx systems
497:03 include their own pbx systems one of the advantages of using such a
497:05 one of the advantages of using such a technology is that phone calls between
497:08 technology is that phone calls between the same business phone systems are free
497:11 the same business phone systems are free because the entire infrastructure is
497:13 because the entire infrastructure is owned by the company
497:15 owned by the company call savings are also included
497:18 call savings are also included from the fact that the company does not
497:20 from the fact that the company does not use the entire trunk to the pstn
497:23 use the entire trunk to the pstn usually the number of phones in an
497:25 usually the number of phones in an organization is much greater than the
497:27 organization is much greater than the actual trunk size
497:29 actual trunk size or the overall call volume to the pstn
497:33 or the overall call volume to the pstn pstn is composed of a group of digital
497:36 pstn is composed of a group of digital devices used in the public sector
497:38 devices used in the public sector offered by telecommunications companies
497:42 offered by telecommunications companies pstn switches are used to connect
497:45 pstn switches are used to connect residential telephones to business users
497:48 residential telephones to business users pstns generally use open standard
497:51 pstns generally use open standard protocols for control and transparent
497:53 protocols for control and transparent communication between telephones
497:56 communication between telephones circuits switches and pbx systems pstns
498:00 circuits switches and pbx systems pstns can even link to other pstns pbx systems
498:04 can even link to other pstns pbx systems or telephones
498:07 or telephones as in pbx systems pstns aggregate t1 and
498:11 as in pbx systems pstns aggregate t1 and e1 circuits
498:12 e1 circuits but they can scale up to hundreds of
498:15 but they can scale up to hundreds of thousands of phones
498:17 thousands of phones pstns connect business pbx systems using
498:20 pstns connect business pbx systems using switches located in
498:22 switches located in telecommunication
498:24 telecommunication companies premises
498:27 companies premises the following figure is an example of an
498:30 the following figure is an example of an organization with multiple locations
498:32 organization with multiple locations that use a voice system based on pbx and
498:35 that use a voice system based on pbx and pstn technologies
498:38 pstn technologies the headquarters location has a pbx that
498:40 the headquarters location has a pbx that connects to the pstn on the outside as
498:44 connects to the pstn on the outside as well as many phones and fax machines
498:46 well as many phones and fax machines inside the network
498:48 inside the network the connection between the local pbx and
498:50 the connection between the local pbx and the pstn
498:52 the pstn can be based on one or more
498:54 can be based on one or more t1 or e1 lines
498:56 t1 or e1 lines the internal network can support a
498:58 the internal network can support a greater number of phones than the number
499:00 greater number of phones than the number of phone calls supported by the t1 or e1
499:03 of phone calls supported by the t1 or e1 line
499:04 line the reason for this is that not everyone
499:06 the reason for this is that not everyone will use the telephone at the same time
499:09 will use the telephone at the same time and some of the phone calls will be
499:11 and some of the phone calls will be between internal phones
499:14 between internal phones the regional office location also uses a
499:17 the regional office location also uses a pbx system
499:18 pbx system to connect to the pstn and it aggregates
499:21 to connect to the pstn and it aggregates a few user phones
499:23 a few user phones the branch and remote offices do not use
499:26 the branch and remote offices do not use a pbx system
499:27 a pbx system because they use very few devices
499:30 because they use very few devices which do not need special features
499:33 which do not need special features and they can connect directly to a pstn
499:36 and they can connect directly to a pstn switch
499:37 switch the branch and home office users can
499:39 the branch and home office users can have
499:40 have phone conversations with users
499:43 phone conversations with users at the headquarters or regional offices
499:45 at the headquarters or regional offices because they are all connected
499:47 because they are all connected to the
499:48 to the pstn the headquarters or the regional
499:52 pstn the headquarters or the regional office were located on the same campus
499:55 office were located on the same campus the pbx systems could have been
499:56 the pbx systems could have been connected directly through a pbx tie
499:59 connected directly through a pbx tie trunk
500:00 trunk without any link to the pstn
500:06 the connections from the internal phones to the local pbx system are also called
500:09 to the local pbx system are also called station lines
500:11 station lines the connection that connects the pstn
500:13 the connection that connects the pstn switches is called a pstn switch trunk
500:18 switches is called a pstn switch trunk voice systems also use different kinds
500:20 voice systems also use different kinds of signaling between system nodes such
500:23 of signaling between system nodes such as the following
500:24 as the following signaling between the internal phones
500:27 signaling between the internal phones and the pbx
500:28 and the pbx signaling between the pbx and the pb
500:31 signaling between the pbx and the pb pstn switch
500:33 pstn switch signaling between pstn switches
500:36 signaling between pstn switches and signaling between pbx systems
500:39 and signaling between pbx systems trunks
500:41 trunks generally use a special type of
500:42 generally use a special type of signaling called common channel
500:45 signaling called common channel signaling ccs
500:47 signaling ccs that can be divided into the following
500:49 that can be divided into the following types of signaling
500:51 types of signaling e1 signaling
500:53 e1 signaling dpn ss signaling
500:56 dpn ss signaling isdn signaling
500:58 isdn signaling qcig signaling and ss7 signaling
501:04 qcig signaling and ss7 signaling the way pstns use their numbering plans
501:06 the way pstns use their numbering plans defines the fundamental basis for
501:09 defines the fundamental basis for routing voice calls through the pstn
501:11 routing voice calls through the pstn switch
501:12 switch matrix the north american numbering plan
501:15 matrix the north american numbering plan is also known as nanp or the oneplus 10
501:19 is also known as nanp or the oneplus 10 plan the format for this numbering plan
501:22 plan the format for this numbering plan is as follows
501:24 is as follows where n is any number between 2 and 9
501:27 where n is any number between 2 and 9 and x is any number between 0 and 9.
501:31 and x is any number between 0 and 9. the number is split into the following
501:33 the number is split into the following three parts
501:34 three parts the first group of numbers represents
501:36 the first group of numbers represents the area code
501:38 the area code the second group of numbers represents
501:40 the second group of numbers represents the prefix
501:42 the prefix and the final four digits
501:44 and the final four digits represent the line number
501:50 the way phone numbers are represented determines the way they are routed
501:52 determines the way they are routed across the pstn and this is similar to
501:54 across the pstn and this is similar to the ip address representation scheme
501:57 the ip address representation scheme that determines ip routing mechanisms
502:01 that determines ip routing mechanisms pstn offers a wide variety of services
502:03 pstn offers a wide variety of services to organizations the most important
502:06 to organizations the most important services are as follows
502:08 services are as follows call center services
502:10 call center services which represent a combination of
502:12 which represent a combination of automated systems and individuals that
502:14 automated systems and individuals that take inbound calls for a wide variety of
502:17 take inbound calls for a wide variety of customer service needs
502:19 customer service needs centric solutions these are specialized
502:22 centric solutions these are specialized business solutions that can be
502:24 business solutions that can be outsourced to different organizations
502:26 outsourced to different organizations that cannot afford investing in their
502:28 that cannot afford investing in their own solution
502:30 own solution virtual private voice networks
502:33 virtual private voice networks pstn ambulance emulates pbx to pbx
502:36 pstn ambulance emulates pbx to pbx connections
502:37 connections in order to form a private network of
502:40 in order to form a private network of pbx systems
502:42 pbx systems interactive voice response this
502:44 interactive voice response this technique allows automatic response
502:46 technique allows automatic response schemes to be applied when customer
502:49 schemes to be applied when customer when customers call special numbers and
502:52 when customers call special numbers and finally voicemail
502:53 finally voicemail voicemail systems allow callers to
502:55 voicemail systems allow callers to record voice messages
503:03 so here's what you've learned you've received an overview of traditional
503:05 received an overview of traditional voice systems you've dug into detail
503:07 voice systems you've dug into detail about the importance of pbx and how it
503:09 about the importance of pbx and how it works
503:11 works we talked about telephony signaling and
503:12 we talked about telephony signaling and then the public switch telephone network
503:14 then the public switch telephone network numbering plan and services
503:17 numbering plan and services all this information will be very
503:19 all this information will be very helpful for you
503:20 helpful for you in your ccda exam good luck in your
503:23 in your ccda exam good luck in your studies
503:49 hi this is david voss ccie-113 and in this video you are going to learn
503:51 and in this video you are going to learn about integrated voice and telephony
503:53 about integrated voice and telephony systems
503:54 systems for the ccda exam
503:56 for the ccda exam so obviously we will focus in on the
503:58 so obviously we will focus in on the design aspect of video and voice
504:01 design aspect of video and voice we will specifically look at the
504:03 we will specifically look at the deployment models
504:05 deployment models and then voip control and transport
504:07 and then voip control and transport protocols and then finally because it's
504:09 protocols and then finally because it's likely you will be asked we will cover
504:12 likely you will be asked we will cover h323 protocols
504:14 h323 protocols so let's begin
504:17 so let's begin network designers must be aware of the
504:19 network designers must be aware of the following ip telephony deployment models
504:22 following ip telephony deployment models single site design
504:24 single site design multi-site centralized when call
504:26 multi-site centralized when call processing design
504:28 processing design multi-site distributed wan call
504:30 multi-site distributed wan call processing design
504:32 processing design internet ip telephony design
504:35 internet ip telephony design and call manager express deployment
504:40 and call manager express deployment the single site deployment model is used
504:42 the single site deployment model is used by enterprises that own a single large
504:45 by enterprises that own a single large building or a campus area with no voice
504:48 building or a campus area with no voice technologies being transported on the
504:51 technologies being transported on the wan links
504:52 wan links a single call manager node is deployed
504:54 a single call manager node is deployed at the enterprise campus server farm
504:57 at the enterprise campus server farm block
504:58 block the main component of a single site ip
505:00 the main component of a single site ip telephony solution is the call manager
505:03 telephony solution is the call manager node
505:04 node this is actually a server platform that
505:06 this is actually a server platform that can be installed on a wide variety of
505:08 can be installed on a wide variety of hardware devices
505:11 hardware devices the cisco ip telephony application
505:13 the cisco ip telephony application server is a high availability server
505:15 server is a high availability server platform
505:16 platform purchased by the company to be used as a
505:18 purchased by the company to be used as a platform for the cisco call manager
505:20 platform for the cisco call manager solution
505:22 solution cisco offers a compatibility matrix that
505:24 cisco offers a compatibility matrix that helps customers choose
505:26 helps customers choose the appropriate hardware platform that
505:28 the appropriate hardware platform that will be used with call manager
505:30 will be used with call manager implementation
505:32 implementation the call manager application system
505:34 the call manager application system brings enterprise telephony
505:36 brings enterprise telephony functionality and offers advanced
505:38 functionality and offers advanced features to various telephony devices
505:41 features to various telephony devices such as ip telephones
505:44 such as ip telephones media processing devices and voice over
505:46 media processing devices and voice over ipa gateways
505:49 ipa gateways other components of the single site ip
505:51 other components of the single site ip telephony design are ip telephones and
505:54 telephony design are ip telephones and switches that have inline power
505:56 switches that have inline power functionality power over ethernet
505:59 functionality power over ethernet used to power the ip phones
506:02 used to power the ip phones voice enabled routers are also present
506:04 voice enabled routers are also present in the design and they are usually
506:06 in the design and they are usually located in the same physical location
506:08 located in the same physical location with all the other devices presented
506:10 with all the other devices presented previously
506:13 previously next let's talk about multi-site
506:14 next let's talk about multi-site centralized design
506:16 centralized design centralized ip telephony is a low-cost
506:19 centralized ip telephony is a low-cost design for medium-sized enterprises
506:22 design for medium-sized enterprises that have one large location and
506:24 that have one large location and multiple remote sites
506:26 multiple remote sites the central location hosts the cisco
506:28 the central location hosts the cisco communications manager server
506:31 communications manager server in all the important applications
506:33 in all the important applications the remote locations host only voice
506:36 the remote locations host only voice switches and ip telephones
506:38 switches and ip telephones this design allows remote
506:40 this design allows remote site ip telephony functionality to be
506:43 site ip telephony functionality to be controlled from a central location
506:46 controlled from a central location without the need for a dedicated call
506:48 without the need for a dedicated call manager at each location
506:50 manager at each location all the features are managed from the
506:52 all the features are managed from the centralized site
506:54 centralized site the call manager node is deployed only
506:56 the call manager node is deployed only at the central location
506:58 at the central location and includes a multi-server cluster
507:00 and includes a multi-server cluster redundant architecture
507:02 redundant architecture the remote site ip phones register with
507:05 the remote site ip phones register with the call manager
507:06 the call manager from the main site
507:08 from the main site the pstn connection is also hosted by
507:11 the pstn connection is also hosted by the central site
507:13 the central site and the voice enabled router is
507:14 and the voice enabled router is connected through the wind to each
507:16 connected through the wind to each remote location
507:18 remote location the remote site office uses ip
507:20 the remote site office uses ip connectivity to connect to the central
507:22 connectivity to connect to the central site through the wan connection
507:24 site through the wan connection and to access all the ip telephony
507:27 and to access all the ip telephony services
507:28 services since the ip phones convert voice to ip
507:32 since the ip phones convert voice to ip the remote site router does not have to
507:34 the remote site router does not have to include any special capability
507:37 include any special capability however the router located in the
507:39 however the router located in the central location
507:40 central location must be a voice enabled router because
507:42 must be a voice enabled router because it also connects to the
507:44 it also connects to the pstn remote sites may use voice enabled
507:48 pstn remote sites may use voice enabled gateway routers with survivable remote
507:50 gateway routers with survivable remote site telephony functionality
507:52 site telephony functionality that allows them to function even if the
507:55 that allows them to function even if the connection to the central site is down
507:58 connection to the central site is down next let's talk about multi-site
508:00 next let's talk about multi-site distributed design
508:02 distributed design the multi-site distributed architecture
508:04 the multi-site distributed architecture is a solution used by large enterprises
508:07 is a solution used by large enterprises that have several large locations
508:10 that have several large locations this design involves deploying several
508:12 this design involves deploying several call manager clusters for redundancy
508:15 call manager clusters for redundancy which can include one cluster per site
508:17 which can include one cluster per site or several clusters only in the large
508:19 or several clusters only in the large sites
508:21 sites inner cluster trunks are configured to
508:23 inner cluster trunks are configured to establish communications between call
508:25 establish communications between call manager
508:26 manager nodes this deployment model is similar
508:29 nodes this deployment model is similar to the multi-site centralized deployment
508:31 to the multi-site centralized deployment type
508:32 type with ip phones
508:34 with ip phones and voice enabled switches installed at
508:36 and voice enabled switches installed at every site
508:38 every site this solution is very flexible and
508:40 this solution is very flexible and allows voice application services
508:42 allows voice application services to be deployed in a single location or
508:44 to be deployed in a single location or in every location that has a call
508:46 in every location that has a call manager cluster
508:48 manager cluster internet ip telephony is another design
508:51 internet ip telephony is another design type commonly used and it involves
508:53 type commonly used and it involves connecting the central and remote sites
508:55 connecting the central and remote sites through an isp
508:57 through an isp this ensures end-to-end ip telephony
509:00 this ensures end-to-end ip telephony across all sites
509:01 across all sites in addition there is no pstn connection
509:04 in addition there is no pstn connection at any of the enterprise sites
509:08 at any of the enterprise sites the central site still hosts the call
509:10 the central site still hosts the call manager node in application servers
509:12 manager node in application servers but regular routers are used in all
509:14 but regular routers are used in all network locations because of the lack of
509:16 network locations because of the lack of connectivity to the pstn
509:19 connectivity to the pstn all the intersight links are plain ip
509:23 all the intersight links are plain ip connections another difference from the
509:25 connections another difference from the centralized ip telephony design
509:28 centralized ip telephony design is that all the enterprise sites have
509:29 is that all the enterprise sites have their own call manager node
509:31 their own call manager node for proper voice traffic to cross
509:34 for proper voice traffic to cross between sites
509:35 between sites the isp must ensure a proper connection
509:38 the isp must ensure a proper connection with low latency and delay
509:40 with low latency and delay this can be enforced through a strict
509:42 this can be enforced through a strict sla when signing
509:44 sla when signing the internet connectivity contract
509:53 the call manager express deployment provides companies with the express
509:55 provides companies with the express version of cisco call manager
509:58 version of cisco call manager unity and contact center solutions
510:01 unity and contact center solutions call manager express and cisco unity
510:04 call manager express and cisco unity express can be installed on routers to
510:07 express can be installed on routers to provide limited functionalities of the
510:09 provide limited functionalities of the communications manager solution
510:12 communications manager solution pstn connectivity can be offered by a
510:14 pstn connectivity can be offered by a dedicated gateway router or by the cme
510:18 dedicated gateway router or by the cme router to further reduce costs
510:25 cisco call manager express supports a limited number of users
510:27 limited number of users as opposed to the enterprise level
510:29 as opposed to the enterprise level solution that can scale up to tens of
510:31 solution that can scale up to tens of thousands of users
510:32 thousands of users this is a lower cost solution for small
510:35 this is a lower cost solution for small branch offices
510:37 branch offices network designers should understand the
510:39 network designers should understand the protocols that are used for voip control
510:41 protocols that are used for voip control and transport the most important
510:43 and transport the most important protocols are
510:49 dhcp which is used to establish ip
510:50 which is used to establish ip configuration parameters for ip phones
510:54 configuration parameters for ip phones dns
510:55 dns which obtains ip addresses for the tftp
510:58 which obtains ip addresses for the tftp servers that will provide the
510:59 servers that will provide the configuration files
511:02 configuration files tftp
511:04 tftp sccp which is the skinny call control
511:07 sccp which is the skinny call control protocol
511:08 protocol used for call establishment
511:11 used for call establishment rtp
511:12 rtp which is used for voice stream or voice
511:15 which is used for voice stream or voice station to station traffic in ongoing
511:17 station to station traffic in ongoing calls
511:19 calls rtcp
511:21 rtcp which is used for voip call control
511:24 which is used for voip call control mgcp
511:26 mgcp which is used for call establishment
511:28 which is used for call establishment with gateways h323
511:32 with gateways h323 which is another call establishment
511:34 which is another call establishment protocol
511:35 protocol and sip
511:36 and sip which is session initiation protocol
511:39 which is session initiation protocol which is an alternative multimedia
511:42 which is an alternative multimedia framework to h323
511:49 now referring to h323 that is implemented in terminals such as ip
511:51 implemented in terminals such as ip phones
511:52 phones workstations
511:54 workstations with soft phones installed
511:56 with soft phones installed gateways
511:57 gateways gatekeepers and other conferencing
512:00 gatekeepers and other conferencing software
512:01 software the h323 standard uses the following
512:03 the h323 standard uses the following protocols to ensure its functionality
512:07 protocols to ensure its functionality q931 for call setup
512:09 q931 for call setup h.225 for signaling
512:12 h.225 for signaling h.245 for control
512:15 h.245 for control and h.255 for registration admission and
512:18 and h.255 for registration admission and status
512:20 status so here's what you've learned you've
512:22 so here's what you've learned you've learned about the deployment models for
512:23 learned about the deployment models for voice and video and then voip control
512:26 voice and video and then voip control and transport protocols
512:29 and transport protocols and then finally h323 protocols all of
512:31 and then finally h323 protocols all of these are fair game on the ccda exam
512:34 these are fair game on the ccda exam and if you know this video well i'm sure
512:37 and if you know this video well i'm sure you'll do
512:38 you'll do very well on this portion
512:40 very well on this portion of the exam good luck in your studies
513:08 and in this video you're going to learn about integrated video systems
513:12 about integrated video systems specifically
513:13 specifically we're going to do an overview of
513:14 we're going to do an overview of multimedia traffic design
513:17 multimedia traffic design then we'll talk about video formats
513:20 then we'll talk about video formats and then finally video design
513:21 and then finally video design considerations and challenges you may
513:23 considerations and challenges you may face but certainly all this information
513:25 face but certainly all this information you'll need to know for your ccda exam
513:28 you'll need to know for your ccda exam so let's begin
513:30 so let's begin video traffic has the same requirements
513:33 video traffic has the same requirements and design consideration as voice
513:35 and design consideration as voice traffic
513:37 traffic voice and video applications can be
513:39 voice and video applications can be grouped in the multimedia traffic
513:41 grouped in the multimedia traffic category and in many cases they should
513:43 category and in many cases they should be treated similarly by network devices
513:47 be treated similarly by network devices this involves ensuring the necessary
513:49 this involves ensuring the necessary bandwidth and providing low delay jitter
513:52 bandwidth and providing low delay jitter and packet loss
513:54 and packet loss media applications underwent a
513:56 media applications underwent a significant development process
513:58 significant development process regarding ip networks
514:00 regarding ip networks resulting in many different combinations
514:02 resulting in many different combinations of audio video and data media
514:05 of audio video and data media video streams can range from low
514:07 video streams can range from low definition webcams to high definition
514:10 definition webcams to high definition enterprise level video conferencing
514:12 enterprise level video conferencing systems
514:13 systems as demand for quality video increases
514:16 as demand for quality video increases network infrastructure requirements must
514:18 network infrastructure requirements must also increase
514:20 also increase companies might have another source of
514:22 companies might have another source of media streams on their network in the
514:25 media streams on their network in the form of unmanaged not business critical
514:28 form of unmanaged not business critical applications
514:31 applications in response to the explosion of media
514:33 in response to the explosion of media content and applications
514:35 content and applications network designers must revise their
514:37 network designers must revise their media application provisioning strategy
514:40 media application provisioning strategy without a properly selected strategy the
514:43 without a properly selected strategy the network infrastructure might not support
514:45 network infrastructure might not support all the multimedia traffic that is
514:47 all the multimedia traffic that is demanded by users
514:48 demanded by users and the network could easily become
514:50 and the network could easily become congested
514:52 congested common high resolution video formats
514:54 common high resolution video formats include 720i
514:57 include 720i 720p
514:59 720p 1080i and 1080p
515:02 1080i and 1080p the numerical value of the format
515:04 the numerical value of the format represents the number of rows in the
515:06 represents the number of rows in the frame
515:08 frame high definition video uses a 16 by 9
515:11 high definition video uses a 16 by 9 aspect ratio
515:13 aspect ratio which results in
515:15 which results in 1920 columns
515:17 1920 columns the most common video formats and
515:19 the most common video formats and typical bandwidth usages are summarized
515:23 typical bandwidth usages are summarized here
515:28 and you would do well to pause the video at this point and study this make sure
515:31 at this point and study this make sure you memorize it for your ccda exam
515:35 you memorize it for your ccda exam now we we reviewed at a high level how
515:37 now we we reviewed at a high level how video impacts the network but let's get
515:40 video impacts the network but let's get a little bit more granular so you can
515:41 a little bit more granular so you can understand how it specifically applies
515:44 understand how it specifically applies to network design
515:46 to network design and to do that we need to get a bit more
515:48 and to do that we need to get a bit more granular on the technical details of
515:50 granular on the technical details of video and what you need to take in
515:52 video and what you need to take in account when designing for video
515:56 account when designing for video there are three types of video solutions
515:59 there are three types of video solutions h323
516:01 h323 cisco unified video advantage and cisco
516:04 cisco unified video advantage and cisco telepresence
516:06 telepresence with h323
516:08 with h323 multiple third parties offer h.323 video
516:11 multiple third parties offer h.323 video conferencing systems
516:13 conferencing systems which can be used to set up a video
516:15 which can be used to set up a video conference over an ip or isdn network
516:20 conference over an ip or isdn network the cisco unified video advantage
516:22 the cisco unified video advantage product uses a pc video camera and a
516:25 product uses a pc video camera and a cisco ip phone
516:27 cisco ip phone as a video conferencing station now when
516:29 as a video conferencing station now when a voice call is placed between two users
516:32 a voice call is placed between two users running the cisco unified video
516:34 running the cisco unified video advantage product
516:36 advantage product a video call can automatically be
516:38 a video call can automatically be started
516:39 started with a video appearing on each user's pc
516:44 with a video appearing on each user's pc finally the cisco telepresence
516:47 finally the cisco telepresence this solution uses cd quality audio
516:50 this solution uses cd quality audio and high definition video
516:52 and high definition video displayed on large monitors to create
516:55 displayed on large monitors to create lifelike video conferences
517:02 now due to the bandwidth intensive and latency sensitive nature of video
517:03 latency sensitive nature of video consider the following when designing or
517:06 consider the following when designing or troubleshooting a video network
517:08 troubleshooting a video network like voice video packets need to be
517:10 like voice video packets need to be allocated an appropriate amount of
517:12 allocated an appropriate amount of bandwidth and treated with high priority
517:16 bandwidth and treated with high priority the following are qos metrics that cisco
517:18 the following are qos metrics that cisco recommends for various types of video
517:20 recommends for various types of video applications
517:22 applications one-way delay should be between 150
517:25 one-way delay should be between 150 millisecond and 500 milliseconds maximum
517:29 millisecond and 500 milliseconds maximum now please note for cisco telepresence
517:32 now please note for cisco telepresence it should be closer to 150 milliseconds
517:34 it should be closer to 150 milliseconds maximum
517:36 maximum cisco unified video advantage can be
517:38 cisco unified video advantage can be around 200 milliseconds and video
517:41 around 200 milliseconds and video surveillance can be up to 500
517:43 surveillance can be up to 500 millisecond maximum
517:45 millisecond maximum now regardless for jitter and packet
517:48 now regardless for jitter and packet loss
517:49 loss regardless of whether or not it's cisco
517:51 regardless of whether or not it's cisco unified video advantage
517:53 unified video advantage cisco telepresence or video surveillance
517:57 cisco telepresence or video surveillance all three platforms
517:59 all three platforms should be no greater than 10 millisecond
518:02 should be no greater than 10 millisecond maximum regard with regards to jitter
518:06 maximum regard with regards to jitter and 0.05 percent maximum packet loss
518:18 now if you're going to design for video you're going to have to understand the
518:20 you're going to have to understand the basics of multicast
518:23 basics of multicast the complete multicast topic itself is
518:26 the complete multicast topic itself is beyond the scope of this video
518:29 beyond the scope of this video but certain things you simply will need
518:31 but certain things you simply will need to know for the exam
518:34 to know for the exam and you can count on the fact that
518:35 and you can count on the fact that you're going to need to understand that
518:36 you're going to need to understand that there are three versions of igmp
518:40 there are three versions of igmp however only two versions are in wide
518:42 however only two versions are in wide scale deployment first is igmp version
518:46 scale deployment first is igmp version 1.
518:47 1. when a pc wants to join a multicast
518:49 when a pc wants to join a multicast group it sends an igmp report message to
518:52 group it sends an igmp report message to the router
518:53 the router letting the router know that it wants to
518:54 letting the router know that it wants to receive traffic for a specific group now
518:58 receive traffic for a specific group now every 60 seconds by default the router
519:01 every 60 seconds by default the router sends an igmp query message to determine
519:04 sends an igmp query message to determine if the pc
519:05 if the pc still wants to belong to the group
519:08 still wants to belong to the group there can be up to three a three minute
519:10 there can be up to three a three minute delay before the time the router
519:11 delay before the time the router realizes that the receiver has left the
519:14 realizes that the receiver has left the group
519:15 group the destination address of this router
519:17 the destination address of this router query is 224.0.0.1
519:26 which addresses all ip multicast hosts now there is also igmp version 2 version
519:29 now there is also igmp version 2 version 2 is similar to version 1 except that
519:32 2 is similar to version 1 except that version 2 can send queries to a specific
519:34 version 2 can send queries to a specific group
519:35 group and a leave message is supported
519:38 and a leave message is supported specifically a receiver can proactively
519:40 specifically a receiver can proactively send a leave message when it no longer
519:42 send a leave message when it no longer wants to participate
519:44 wants to participate in a multicast group
519:46 in a multicast group allowing the router to prune its
519:48 allowing the router to prune its interface earlier in an environment with
519:51 interface earlier in an environment with a version 2 router and a mixture of
519:53 a version 2 router and a mixture of version 1 and version 2 receivers
519:56 version 1 and version 2 receivers the version 1 receivers respond normally
519:58 the version 1 receivers respond normally to version 1 or version 2 however
520:02 to version 1 or version 2 however a version 2 router must ignore any leave
520:05 a version 2 router must ignore any leave message
520:06 message while version 1 receivers are present
520:09 while version 1 receivers are present because if the router processed the
520:11 because if the router processed the version 2 leave message it would send a
520:14 version 2 leave message it would send a group specific query
520:15 group specific query which would not be correctly interpreted
520:17 which would not be correctly interpreted by a version 1 receiver
520:23 if you're going to effectively troubleshoot video you need to
520:25 troubleshoot video you need to understand the concept of distribution
520:27 understand the concept of distribution trees
520:28 trees to combat the issue of receiving
520:30 to combat the issue of receiving duplicate packets cisco routers perform
520:33 duplicate packets cisco routers perform a reverse path forwarding check to
520:35 a reverse path forwarding check to determine
520:36 determine if a multicast packet is entering a
520:38 if a multicast packet is entering a router on the appropriate interface
520:41 router on the appropriate interface an rpf check examines the source address
520:44 an rpf check examines the source address of an incoming packet and checks it
520:46 of an incoming packet and checks it against the router's unicast routing
520:48 against the router's unicast routing table to see what interface should be
520:50 table to see what interface should be used to get back to the source network
520:53 used to get back to the source network if the incoming multicast packet is
520:55 if the incoming multicast packet is using that interface the rpf check
520:58 using that interface the rpf check passes and the packet is forwarded
521:01 passes and the packet is forwarded if the multicast packet is coming in on
521:03 if the multicast packet is coming in on a different interface the rpf check
521:06 a different interface the rpf check fails and the packet is discarded
521:09 fails and the packet is discarded multicast traffic flows from a source to
521:12 multicast traffic flows from a source to a destination
521:13 a destination over a distribution tree which is a loop
521:17 over a distribution tree which is a loop free path
521:18 free path now there are two types of distribution
521:20 now there are two types of distribution trees
521:21 trees a source distribution tree
521:28 this creates an optimal path between each source router and each last hop
521:30 each source router and each last hop router
521:31 router and then there's a shared distribution
521:33 and then there's a shared distribution tree
521:34 tree this creates a tree from a central
521:36 this creates a tree from a central rendezvous point or rp
521:39 rendezvous point or rp to all last top routers now please note
521:42 to all last top routers now please note cisco routers can use the protocol
521:44 cisco routers can use the protocol independent multicast protocol or pim
521:48 independent multicast protocol or pim to construct ip multicast distribution
521:50 to construct ip multicast distribution trees
521:51 trees pims protocol independence means that it
521:54 pims protocol independence means that it can run over any ip network
521:56 can run over any ip network regardless of the underlying unicast
521:59 regardless of the underlying unicast routing protocol
522:03 so here's what you've learned you received an overview of multimedia
522:05 received an overview of multimedia traffic design
522:06 traffic design we talked about the unique video formats
522:09 we talked about the unique video formats and then design considerations you need
522:12 and then design considerations you need to take into account whether preparing
522:14 to take into account whether preparing for the ccda exam or actually designing
522:17 for the ccda exam or actually designing video for your own network
522:19 video for your own network good luck in your studies
522:45 hi this is david voss ccie 11372 and in this video you're going to receive an
522:46 this video you're going to receive an introduction to wireless lans
522:50 introduction to wireless lans specifically we're going to do an
522:51 specifically we're going to do an overview of wireless lans talk about
522:53 overview of wireless lans talk about wireless lan components
522:55 wireless lan components we'll talk about the 802.11 standard in
522:58 we'll talk about the 802.11 standard in the osi model how it fits in the osi
523:00 the osi model how it fits in the osi model
523:01 model then max sub layer coordination how that
523:03 then max sub layer coordination how that applies to wireless 802.11 frame types
523:06 applies to wireless 802.11 frame types and finally
523:08 and finally wireless lan standards
523:12 wireless lan standards so wireless lans provide network
523:13 so wireless lans provide network connectivity almost anywhere surely you
523:16 connectivity almost anywhere surely you use wireless lans if
523:18 use wireless lans if if you're in technology surely you're
523:19 if you're in technology surely you're using them whether it's your mobile
523:21 using them whether it's your mobile phone or your laptop
523:23 phone or your laptop whether you're at a coffee shop or at
523:25 whether you're at a coffee shop or at your place of business doing byod
523:29 your place of business doing byod wireless lands typically can be
523:30 wireless lands typically can be implemented at much less cost than
523:32 implemented at much less cost than traditional wired lands the wired
523:35 traditional wired lands the wired infrastructure is of course based on the
523:36 infrastructure is of course based on the 802.3 standards
523:38 802.3 standards but a wireless network uses radio waves
523:40 but a wireless network uses radio waves to transmit data and can and to connect
523:43 to transmit data and can and to connect devices
523:44 devices so as you surely know our wireless
523:46 so as you surely know our wireless network uses radio waves to transmit
523:48 network uses radio waves to transmit data and connect devices
523:55 wireless lans are defined by the 802.11 standards
523:56 standards now some additional advantages of
523:58 now some additional advantages of wireless lans over wired lands include
524:01 wireless lans over wired lands include the following
524:02 the following monetary cost
524:04 monetary cost flexibility uh that you allow users to
524:07 flexibility uh that you allow users to roam in places where they normally
524:08 roam in places where they normally cannot or uh use their devices in places
524:12 cannot or uh use their devices in places they always wish they could
524:14 they always wish they could load distribution
524:16 load distribution and finally redundancy and we'll get
524:19 and finally redundancy and we'll get into this in a little bit but
524:21 into this in a little bit but using these wireless access points
524:23 using these wireless access points multiple wireless access points
524:26 multiple wireless access points in one area can provide redundancy and
524:28 in one area can provide redundancy and load distribution at a much more
524:30 load distribution at a much more affordable cost
524:32 affordable cost than wired lands
524:39 now there are there are certain components
524:40 components that make up wireless lands and let's
524:42 that make up wireless lands and let's start with the client
524:44 start with the client uh specifically you or any of our
524:46 uh specifically you or any of our customers
524:48 customers clients are basically
524:50 clients are basically an appliance that interfaces with the
524:52 an appliance that interfaces with the wireless medium now again that could be
524:55 wireless medium now again that could be a mobile device it could be a laptop it
524:57 a mobile device it could be a laptop it could be a tablet
524:59 could be a tablet it could be a pc but it's basically a
525:02 it could be a pc but it's basically a device that operates as an end user
525:04 device that operates as an end user device
525:11 an access point functions as a bridge basically between the end points
525:14 basically between the end points and the existing network backbone
525:16 and the existing network backbone so the access point is what the
525:18 so the access point is what the endpoints are actually communicating
525:21 endpoints are actually communicating with and as they roam they may change
525:23 with and as they roam they may change access points throughout the building
525:25 access points throughout the building but the access points are actually what
525:27 but the access points are actually what are getting them access
525:29 are getting them access to the network
525:31 to the network as you can see in this picture access
525:33 as you can see in this picture access points come in many different shapes and
525:36 points come in many different shapes and sizes these are just a few examples of
525:38 sizes these are just a few examples of access points
525:40 access points the distribution system plays a key role
525:44 the distribution system plays a key role in communications between the customer
525:46 in communications between the customer who's trying to get on the wireless
525:48 who's trying to get on the wireless network
525:49 network and the major wireless lan components
525:51 and the major wireless lan components that are actually switching routing the
525:53 that are actually switching routing the traffic
525:55 traffic the distribution system allows for the
525:57 the distribution system allows for the interconnection of the aps of multiple
526:00 interconnection of the aps of multiple cells
526:01 cells think of your organization if you have
526:03 think of your organization if you have one area that's considered a lab and
526:05 one area that's considered a lab and it's a wireless lab and that ultimately
526:07 it's a wireless lab and that ultimately needs to communicate with marketing on
526:10 needs to communicate with marketing on the eighth floor there's you're going to
526:12 the eighth floor there's you're going to need a distribution system to
526:14 need a distribution system to communicate between those two locations
526:17 communicate between those two locations the wireless distribution system allows
526:19 the wireless distribution system allows you to connect multiple access points
526:21 you to connect multiple access points so with wireless distribution systems
526:23 so with wireless distribution systems aps can communicate with one another
526:26 aps can communicate with one another without wires in a standardized way now
526:28 without wires in a standardized way now that being said distributions could be
526:31 that being said distributions could be wired or integrated but this capability
526:34 wired or integrated but this capability of communications between access points
526:36 of communications between access points is absolutely critical in providing a
526:38 is absolutely critical in providing a seamless experience for roaming clients
526:41 seamless experience for roaming clients and for managing multiple wireless
526:42 and for managing multiple wireless networks it can also simplify the
526:45 networks it can also simplify the network infrastructure by reducing the
526:47 network infrastructure by reducing the amount of cabling required
526:49 amount of cabling required another concept you need to understand
526:51 another concept you need to understand is the basic service set
526:53 is the basic service set the wireless architecture
526:55 the wireless architecture divides the system into cells referred
526:57 divides the system into cells referred to as basic service set
526:59 to as basic service set and it's controlled by a base station or
527:01 and it's controlled by a base station or more commonly an access point
527:04 more commonly an access point now an extended service set is a set of
527:07 now an extended service set is a set of connected bss
527:09 connected bss and then there's the independent basic
527:11 and then there's the independent basic service set which is a wireless network
527:13 service set which is a wireless network consisting of at least
527:15 consisting of at least two endpoints and no distribution system
527:20 two endpoints and no distribution system so
527:20 so let's draw this out
527:22 let's draw this out so we can get a better understanding
527:24 so we can get a better understanding of what we learned thus far
527:28 of what we learned thus far so
527:28 so in any wireless implementation you're
527:30 in any wireless implementation you're going to have endpoints that need to
527:32 going to have endpoints that need to connect so for example here's a laptop
527:35 connect so for example here's a laptop that is connecting to the wireless
527:37 that is connecting to the wireless network it connects to the wireless
527:39 network it connects to the wireless network through an access point
527:43 network through an access point the access point is sending out
527:45 the access point is sending out the radio waves which are being received
527:48 the radio waves which are being received by the laptop
527:50 by the laptop the laptop endpoint
527:54 the laptop endpoint then connects onto the wireless network
527:56 then connects onto the wireless network assuming it has the proper security
527:58 assuming it has the proper security configurations
527:59 configurations and it can then
528:01 and it can then reach the network
528:03 reach the network now access points can communicate not
528:04 now access points can communicate not only with laptops but again mobile
528:07 only with laptops but again mobile phones
528:17 and you can think of this as a basic service set
528:24 now let's say in a different area we have
528:26 let's say in a different area we have another access point
528:29 another access point which is also serving customers or users
528:36 and this again could be a server it could be a workstation could be a
528:38 could be a workstation could be a printer
528:40 printer but regardless it's servicing endpoints
528:42 but regardless it's servicing endpoints it's a different implementation
528:45 it's a different implementation different part of the building or a
528:46 different part of the building or a different building altogether but this
528:48 different building altogether but this is another basic service set
528:59 so how do these two basic service sets communicate
529:01 communicate well they use as you as you have already
529:03 well they use as you as you have already learned they use a distribution system
529:11 these two ds's can uplink in many ways via wireless or
529:14 can uplink in many ways via wireless or in this case they were looking here's a
529:16 in this case they were looking here's a wired connection
529:17 wired connection this is the distribution system
529:20 this is the distribution system that is allowing these two separate
529:22 that is allowing these two separate wireless implementations or basic
529:24 wireless implementations or basic service sets to communicate
529:43 now if we look at the big picture both of these basic service sets and the
529:45 of these basic service sets and the distribution system
529:47 distribution system the big picture this is the extended
529:50 the big picture this is the extended service set
529:52 service set this includes all of the wireless
529:54 this includes all of the wireless equipment and any equipment used to
529:56 equipment and any equipment used to connect the wireless equipment together
530:04 the ieee 802 standards define two separate layers for the data link of the
530:06 separate layers for the data link of the osi model as you know these two layers
530:09 osi model as you know these two layers are the llc and the mac sub layers
530:12 are the llc and the mac sub layers the 802.11 standards cover the operation
530:14 the 802.11 standards cover the operation of the max sublayer and the physical
530:17 of the max sublayer and the physical layer
530:19 layer the 802.11 frame consists of a 32 byte
530:22 the 802.11 frame consists of a 32 byte mac header variable length and a frame
530:24 mac header variable length and a frame check sequence
530:30 there are two types of coordinated functions
530:31 functions used to ensure collision free access on
530:33 used to ensure collision free access on a wireless network
530:35 a wireless network first distributed coordinated
530:37 first distributed coordinated coordination function
530:39 coordination function the mac sub layer technique employs the
530:42 the mac sub layer technique employs the well-known csma-ca to avoid collisions
530:45 well-known csma-ca to avoid collisions it's used to manage access to the radio
530:47 it's used to manage access to the radio frequency medium and it's composed of
530:50 frequency medium and it's composed of the following two main components inner
530:52 the following two main components inner frame spaces and random back off
530:55 frame spaces and random back off and then there's point coordination
530:57 and then there's point coordination function and the pcf is used by the ap
531:00 function and the pcf is used by the ap to coordinate communications
531:02 to coordinate communications with the wireless network
531:05 with the wireless network the 802.11 standard uses three main
531:08 the 802.11 standard uses three main types of frames control frames
531:10 types of frames control frames to control access to the medium
531:12 to control access to the medium management frames to enable stations to
531:14 management frames to enable stations to establish and maintain communications
531:17 establish and maintain communications and then data frames sent by any
531:19 and then data frames sent by any endpoint
531:20 endpoint and these contain higher layer protocol
531:22 and these contain higher layer protocol information or data
531:29 now there are many 802.11 standards but you should definitely know of these and
531:31 you should definitely know of these and you probably already do know many of
531:32 you probably already do know many of them these standards have been rolled
531:34 them these standards have been rolled out over the years and you've been on
531:36 out over the years and you've been on many of these networks
531:38 many of these networks whether it's in your home or at your
531:40 whether it's in your home or at your local coffee shop or at work
531:42 local coffee shop or at work the initial 802.11 standard was serviced
531:46 the initial 802.11 standard was serviced up to 2 megabits per second at this
531:48 up to 2 megabits per second at this point we're at the 802.11 n standard
531:52 point we're at the 802.11 n standard which theoretically can provide up to
531:54 which theoretically can provide up to 600 megabits per second
531:56 600 megabits per second of bandwidth
532:01 so here's what you've learned you we've we've done a wireless lan overview we've
532:03 we've done a wireless lan overview we've talked about wireless lan components
532:06 talked about wireless lan components and how the 802.11 standard works with
532:08 and how the 802.11 standard works with the osi model
532:10 the osi model we've talked about max sub layer
532:11 we've talked about max sub layer coordination and how that applies to
532:13 coordination and how that applies to wireless 802.11 frame types and
532:17 wireless 802.11 frame types and finally wireless lan standards good luck
532:20 finally wireless lan standards good luck with your studies
532:43 hi this is david voss ccie11372 and in this video you're going
532:45 ccie11372 and in this video you're going to learn about the cisco unified
532:48 to learn about the cisco unified wireless solution
532:51 wireless solution specifically you're going to learn about
532:53 specifically you're going to learn about access points
532:54 access points lightweight access points and
532:56 lightweight access points and lightweight access point protocol
532:59 lightweight access point protocol wireless lan controllers
533:02 wireless lan controllers discussing both the modes that it
533:04 discussing both the modes that it operates in and the interface types and
533:06 operates in and the interface types and then mobility groups so plenty to cover
533:09 then mobility groups so plenty to cover and let's begin
533:12 and let's begin the cisco unified wireless network
533:14 the cisco unified wireless network concept includes the following elements
533:16 concept includes the following elements wireless clients this includes laptops
533:19 wireless clients this includes laptops workstations etc
533:21 workstations etc access points this provides access to
533:24 access points this provides access to the wireless network
533:25 the wireless network network management this is accomplished
533:28 network management this is accomplished through network wireless control system
533:30 through network wireless control system it's a centralized management tool that
533:33 it's a centralized management tool that allows for design and control of
533:34 allows for design and control of wireless networks
533:36 wireless networks network unification
533:38 network unification the wireless lan system needs to be able
533:40 the wireless lan system needs to be able to support wireless applications by
533:42 to support wireless applications by offering unified security policies such
533:45 offering unified security policies such as quality of service
533:47 as quality of service and rf management so the the wlc's our
533:50 and rf management so the the wlc's our wireless lan controllers offer this
533:52 wireless lan controllers offer this unified integration functionality
533:55 unified integration functionality and then network services
533:57 and then network services wireless network services are also
533:59 wireless network services are also referred to as mobility services
534:01 referred to as mobility services and include guest access or voice
534:03 and include guest access or voice services location services and even
534:06 services location services and even threat detection and mitigation
534:13 stand-alone access points are also known as autonomous access points they're
534:16 as autonomous access points they're obviously very easy to install but the
534:18 obviously very easy to install but the thing is they can be difficult to manage
534:20 thing is they can be difficult to manage in large deployments they're not as
534:22 in large deployments they're not as desirable as the lightweight access
534:24 desirable as the lightweight access points
534:25 points from cisco because they must be managed
534:27 from cisco because they must be managed individually
534:29 individually in addition different parameters must be
534:31 in addition different parameters must be configured manually on each device
534:33 configured manually on each device including ssid vlan and security
534:36 including ssid vlan and security features
534:38 features the cisco unified wireless network
534:40 the cisco unified wireless network introduced the concept of lightweight
534:42 introduced the concept of lightweight access points and wireless lan
534:45 access points and wireless lan controllers that's lwaps and wlc's
534:49 controllers that's lwaps and wlc's these two types of wireless devices
534:51 these two types of wireless devices divide responsibilities and
534:52 divide responsibilities and functionalities that an autonomous
534:55 functionalities that an autonomous access point would normally perform on
534:57 access point would normally perform on its own
534:58 its own this technology adds scalability by
535:00 this technology adds scalability by separating the wireless lan data plane
535:02 separating the wireless lan data plane from the control plane into a split mac
535:05 from the control plane into a split mac design
535:07 design lightweight access points focus only on
535:09 lightweight access points focus only on the actual rf transmissions and the
535:11 the actual rf transmissions and the necessary real-time control operations
535:14 necessary real-time control operations such as beaconing probing and buffering
535:17 such as beaconing probing and buffering now wireless lan controllers manage all
535:19 now wireless lan controllers manage all non-real-time tasks such as ssid
535:22 non-real-time tasks such as ssid management vlan management
535:25 management vlan management access point association management
535:27 access point association management authentication and quality of service
535:30 authentication and quality of service when using lightweight access points
535:33 when using lightweight access points all rf traffic they receive must first
535:35 all rf traffic they receive must first go to the wireless lan controller device
535:38 go to the wireless lan controller device that manage this manages the specific
535:40 that manage this manages the specific access point
535:41 access point this changes the way in which
535:43 this changes the way in which traditional wireless lan communication
535:45 traditional wireless lan communication works even for hosts associated to the
535:48 works even for hosts associated to the same access point
535:49 same access point the rf communication between lightweight
535:52 the rf communication between lightweight access points and wireless lan
535:54 access points and wireless lan controllers is handled
535:56 controllers is handled using the lightweight access point
535:58 using the lightweight access point protocol
535:59 protocol the lightweight access point tunnel can
536:01 the lightweight access point tunnel can operate in either layer 2 or layer 3
536:03 operate in either layer 2 or layer 3 mode
536:04 mode in layer 2 mode the access point and
536:06 in layer 2 mode the access point and wireless lan controllers share the same
536:08 wireless lan controllers share the same vlan subnet and functions
536:11 vlan subnet and functions with the lightweight access point
536:13 with the lightweight access point receiving 802.11 frames and
536:15 receiving 802.11 frames and encapsulating them inside ethernet
536:18 encapsulating them inside ethernet toward the wireless lan controller
536:20 toward the wireless lan controller when the lightweight access point tunnel
536:22 when the lightweight access point tunnel operates in layer 3 mode the lightweight
536:25 operates in layer 3 mode the lightweight access point receives 802.11 frames and
536:27 access point receives 802.11 frames and encapsulates them inside of udp toward
536:30 encapsulates them inside of udp toward the wireless lan controller
536:32 the wireless lan controller so this implies that the wireless lan
536:35 so this implies that the wireless lan controller can be anywhere as long as it
536:37 controller can be anywhere as long as it is reachable by the access point
536:41 is reachable by the access point the cisco lightweight access point
536:43 the cisco lightweight access point protocol can operate in the following
536:46 protocol can operate in the following six modes
536:47 six modes local mode
536:49 local mode reap or remote edge access point mode
536:52 reap or remote edge access point mode monitor
536:53 monitor road detector mode sniffer mode in
536:55 road detector mode sniffer mode in bridge mode
536:57 bridge mode every 180 seconds the access point
536:59 every 180 seconds the access point spends 60 milliseconds on channels on
537:02 spends 60 milliseconds on channels on which it does not operate
537:05 which it does not operate during the 60 millisecond time period
537:07 during the 60 millisecond time period the access point performs noise in
537:08 the access point performs noise in interference measurements and scans for
537:10 interference measurements and scans for intrusion detection events
537:13 intrusion detection events the reap mode allows the lightweight
537:15 the reap mode allows the lightweight access point to reside across a land
537:17 access point to reside across a land link and still be able to communicate
537:19 link and still be able to communicate with the wireless lan controller and
537:21 with the wireless lan controller and provide the functionality of a regular
537:24 provide the functionality of a regular lightweight access point
537:26 lightweight access point reap mode is not supported on all
537:29 reap mode is not supported on all lightweight access point models
537:32 lightweight access point models monitor mode is a special feature that
537:33 monitor mode is a special feature that allows lightweight access point enabled
537:35 allows lightweight access point enabled aps to exclude themselves from dealing
537:38 aps to exclude themselves from dealing with data traffic between clients
537:40 with data traffic between clients instead they act as dedicated sensors
537:43 instead they act as dedicated sensors for location based services rogue ap
537:45 for location based services rogue ap detection and for ids
537:48 detection and for ids in rd mode
537:50 in rd mode the lightweight access point monitors
537:52 the lightweight access point monitors for rogue aps
537:53 for rogue aps the road the goal of this rogue
537:55 the road the goal of this rogue detection of aps
537:57 detection of aps is to see all the vlans in the network
537:59 is to see all the vlans in the network because rogue aps can be connected to
538:01 because rogue aps can be connected to any of those vlans
538:08 sniffer mode allows the lightweight access point to capture and forward all
538:09 access point to capture and forward all the packets on a particular channel to a
538:11 the packets on a particular channel to a remote machine that is running packet
538:14 remote machine that is running packet capturing software and finally bridge
538:16 capturing software and finally bridge mode typically operates on outdoor aps
538:19 mode typically operates on outdoor aps that function in a mesh topology
538:21 that function in a mesh topology this cost effective high bandwidth
538:23 this cost effective high bandwidth wireless bridging connectivity mechanism
538:26 wireless bridging connectivity mechanism includes point-to-point or multi-point
538:28 includes point-to-point or multi-point bridging
538:36 wireless lan controllers have the following three components wireless lan
538:39 following three components wireless lan interfaces and ports the wireless lan is
538:42 interfaces and ports the wireless lan is the ssid network name
538:44 the ssid network name every wireless lan is assigned to an
538:46 every wireless lan is assigned to an interface in the wireless lan controller
538:48 interface in the wireless lan controller and each wireless lan is configured with
538:50 and each wireless lan is configured with policies for rf qs and other lan
538:53 policies for rf qs and other lan attributes
538:55 attributes the interfaces are logical connections
538:57 the interfaces are logical connections that map to a vlan on the wired network
538:59 that map to a vlan on the wired network every interface is configured with a
539:01 every interface is configured with a unique ip address default gateway
539:04 unique ip address default gateway and physical ports
539:06 and physical ports wireless lan controllers support the
539:08 wireless lan controllers support the following five interface types the
539:10 following five interface types the management interface which is used for
539:12 management interface which is used for in-band management or connect
539:15 in-band management or connect connectivity to a aaa server
539:17 connectivity to a aaa server an optional service port interface for
539:19 an optional service port interface for out of band management that is
539:21 out of band management that is statically configured
539:23 statically configured the access point manager interface used
539:25 the access point manager interface used for layer 3 discovery and association
539:29 for layer 3 discovery and association dynamic interfaces these are the vlans
539:32 dynamic interfaces these are the vlans designated for wireless lan client data
539:35 designated for wireless lan client data and virtual interfaces used for layer 3
539:38 and virtual interfaces used for layer 3 security authentication dhcp relay and
539:41 security authentication dhcp relay and management of mobility features
539:45 management of mobility features one of the main features of a wireless
539:46 one of the main features of a wireless lan solution is the user's ability to
539:49 lan solution is the user's ability to access network resources from different
539:51 access network resources from different areas
539:53 areas end users most likely move from one
539:55 end users most likely move from one location to another so designers should
539:57 location to another so designers should scale the wireless network carefully to
539:58 scale the wireless network carefully to allow for client roaming
540:01 allow for client roaming wireless roaming can be divided into the
540:03 wireless roaming can be divided into the following two categories
540:05 following two categories intra controller roaming or inter
540:08 intra controller roaming or inter controller roaming
540:10 controller roaming intracontroller roaming occurs when a
540:12 intracontroller roaming occurs when a client moves its association from one ap
540:15 client moves its association from one ap to another ap controlled by the same
540:17 to another ap controlled by the same wireless lan controller
540:19 wireless lan controller inter controller roaming can operate in
540:21 inter controller roaming can operate in either layer 2 or layer 3 mode
540:24 either layer 2 or layer 3 mode in layer two inner control roaming moves
540:27 in layer two inner control roaming moves users from ap
540:29 users from ap to ap and from wlc to wlc but they
540:33 to ap and from wlc to wlc but they remain in the same subnet
540:35 remain in the same subnet layer three inner controller roaming is
540:37 layer three inner controller roaming is more difficult to implement because
540:39 more difficult to implement because users can move from ap to ap and wlc to
540:43 users can move from ap to ap and wlc to wlc from subnet to subnet as well
540:47 wlc from subnet to subnet as well in this scenario the wireless lan
540:49 in this scenario the wireless lan controllers must be configured with
540:51 controllers must be configured with mobility groups
540:57 now speaking of mobility groups you may be tested on the following communication
541:00 be tested on the following communication ports for mobility groups
541:03 ports for mobility groups the lightweight access point protocol
541:04 the lightweight access point protocol control udp
541:06 control udp one
541:07 one two
541:09 two lightweight access point protocol data
541:11 lightweight access point protocol data udp
541:13 udp 12 222
541:15 12 222 wireless lan controller exchange
541:17 wireless lan controller exchange unencrypted messages
541:19 unencrypted messages udp
541:20 udp 16660 and wireless lan controller
541:23 16660 and wireless lan controller exchange encrypted messages
541:26 exchange encrypted messages 16667
541:30 so here's what you've learned you've learned about access points
541:32 learned about access points lightweight access points and
541:33 lightweight access points and lightweight access point protocol
541:35 lightweight access point protocol wireless lan controller modes and
541:37 wireless lan controller modes and interface types as well as mobility
541:39 interface types as well as mobility groups this gives you a good foundation
541:41 groups this gives you a good foundation for the wireless portion at least for
541:43 for the wireless portion at least for unified wireless solutions and your
541:45 unified wireless solutions and your cisco's ccda exam good luck in your
541:48 cisco's ccda exam good luck in your studies
542:12 hi this is david voss ccie 11372 and in this video we're covering wireless lan
542:14 this video we're covering wireless lan design
542:16 design we're first going to learn about
542:17 we're first going to learn about redundancy and the importance of
542:18 redundancy and the importance of redundancy in wireless design
542:21 redundancy in wireless design then you'll learn about rf groups and
542:23 then you'll learn about rf groups and then we'll also talk about mesh design
542:25 then we'll also talk about mesh design so let's begin
542:28 so let's begin wireless lan controllers can be
542:29 wireless lan controllers can be configured for dynamic or deterministic
542:31 configured for dynamic or deterministic redundancy
542:33 redundancy for deterministic redundancy the ap is
542:35 for deterministic redundancy the ap is configured with a primary secondary and
542:37 configured with a primary secondary and tertiary controller
542:40 tertiary controller this requires more upfront planning but
542:42 this requires more upfront planning but allows for better predictability and
542:44 allows for better predictability and faster failover times
542:46 faster failover times deterministic redundancy is the
542:48 deterministic redundancy is the recommended best practice n plus 1
542:51 recommended best practice n plus 1 n plus n and m plus n plus 1 are
542:54 n plus n and m plus n plus 1 are examples of deterministic redundancy
543:02 with n plus one redundancy a single wireless lan controller acts as the
543:03 wireless lan controller acts as the backup of multiple wireless lan
543:06 backup of multiple wireless lan controllers
543:07 controllers the backup wlc is configured as the
543:10 the backup wlc is configured as the secondary wlc on each ap
543:13 secondary wlc on each ap one design constraint is that the backup
543:16 one design constraint is that the backup wlc might become oversubscribed if there
543:18 wlc might become oversubscribed if there are too many failures of the primary
543:20 are too many failures of the primary controllers
543:22 controllers the secondary wlc is the backup and
543:24 the secondary wlc is the backup and controller for all aps and is normally
543:27 controller for all aps and is normally placed in the data center
543:33 with n plus n redundancy an equal number of controllers back each other up for
543:36 of controllers back each other up for example a pair of wlc's on one floor
543:39 example a pair of wlc's on one floor serves as a backup to a second pair on
543:41 serves as a backup to a second pair on another floor
543:43 another floor the top wlc is primary for ap1 and ap2
543:47 the top wlc is primary for ap1 and ap2 and the secondary for ap3 and ap4
543:50 and the secondary for ap3 and ap4 the bottom wlc is the primary for ap3
543:53 the bottom wlc is the primary for ap3 and ap4 and secondary for ap1 and ap2
543:58 and ap4 and secondary for ap1 and ap2 there should be enough capacity on each
543:59 there should be enough capacity on each controller to manage a failover
544:01 controller to manage a failover situation
544:03 situation with m plus m plus one redundancy an
544:06 with m plus m plus one redundancy an equal number of controllers back each
544:07 equal number of controllers back each other up
544:09 other up plus a backup wlc is configured as the
544:12 plus a backup wlc is configured as the tertiary
544:13 tertiary m plus m plus one redundancy functions
544:16 m plus m plus one redundancy functions the same as m plus n redundancy
544:18 the same as m plus n redundancy plus a tertiary controller that backs up
544:21 plus a tertiary controller that backs up the secondary controllers
544:23 the secondary controllers the tertiary wlc is placed in the data
544:26 the tertiary wlc is placed in the data center or network operations center
544:29 center or network operations center here is a summary of wireless lan
544:32 here is a summary of wireless lan controller redundancy it would be good
544:34 controller redundancy it would be good to memorize this in preparation for your
544:36 to memorize this in preparation for your exam
544:41 next let's talk about radio management and radio groups
544:43 and radio groups the limit of available channels in the
544:45 the limit of available channels in the ism frequencies used by ieee 802.11 bgnn
544:49 ism frequencies used by ieee 802.11 bgnn standard
544:50 standard presents challenges to the network
544:52 presents challenges to the network designer
544:53 designer there are three non-overlapping channels
544:56 there are three non-overlapping channels channels 1 6 and 11.
544:58 channels 1 6 and 11. the recommended best practice is to
545:00 the recommended best practice is to limit the number of data devices
545:01 limit the number of data devices connected to each ap to 20.
545:05 connected to each ap to 20. or not more than seven concurrent voice
545:07 or not more than seven concurrent voice over wireless lan calls using g711
545:11 over wireless lan calls using g711 an rf group is a cluster of wlc devices
545:15 an rf group is a cluster of wlc devices that coordinate their rrm calculations
545:18 that coordinate their rrm calculations rf groups are formed with the following
545:20 rf groups are formed with the following process ap send out neighbor messages
545:23 process ap send out neighbor messages over the air
545:24 over the air the message includes an encrypted shared
545:26 the message includes an encrypted shared secret that is configured on the wlc and
545:29 secret that is configured on the wlc and pushed to each ap
545:31 pushed to each ap aps sharing the same secret are able to
545:33 aps sharing the same secret are able to validate messages from each other
545:36 validate messages from each other the members in the rf group elect an rf
545:38 the members in the rf group elect an rf group leader to maintain a master power
545:41 group leader to maintain a master power and channel scheme for the rf group
545:44 and channel scheme for the rf group similar to performing an assessment for
545:46 similar to performing an assessment for a wired network design
545:48 a wired network design rf surveys are done to determine design
545:51 rf surveys are done to determine design parameters for wireless lans and
545:53 parameters for wireless lans and customer requirements
545:55 customer requirements rf site surveys help determine the
545:57 rf site surveys help determine the coverage areas and check for rf
545:59 coverage areas and check for rf interference
546:00 interference this helps determine the appropriate
546:02 this helps determine the appropriate placement of wireless aps
546:04 placement of wireless aps the rf site survey has the following
546:07 the rf site survey has the following steps
546:09 steps to find customer requirements such as
546:11 to find customer requirements such as service levels and support for voip
546:13 service levels and support for voip determine devices to support
546:17 determine devices to support obtain a facility diagram to identify
546:19 obtain a facility diagram to identify the potential rf obstacles
546:22 the potential rf obstacles visually inspect the facility to look
546:24 visually inspect the facility to look for potential barriers to the
546:25 for potential barriers to the propagation of rf signals
546:29 propagation of rf signals identify user areas that may be
546:31 identify user areas that may be intensively used such as conference
546:33 intensively used such as conference rooms
546:34 rooms in areas that are not heavily used such
546:35 in areas that are not heavily used such as stairwells
546:37 as stairwells determine preliminary ap locations which
546:40 determine preliminary ap locations which need power wired network access
546:43 need power wired network access cell coverage and overlap
546:45 cell coverage and overlap not to mention channel selection
546:47 not to mention channel selection mounting locations and antennas
546:50 mounting locations and antennas let's talk about wireless mesh for
546:51 let's talk about wireless mesh for outdoor wireless
546:53 outdoor wireless traditionally outdoor wireless solutions
546:54 traditionally outdoor wireless solutions have been limited to point-to-point
546:56 have been limited to point-to-point point to multi-point bridging between
546:58 point to multi-point bridging between buildings
546:59 buildings with these solutions each ap is wired to
547:01 with these solutions each ap is wired to the network the cisco wireless mesh
547:03 the network the cisco wireless mesh networking solution eliminates the need
547:05 networking solution eliminates the need to wire each ap
547:07 to wire each ap and allows users to roam from one area
547:09 and allows users to roam from one area to another without having to reconnect
547:13 to another without having to reconnect the wireless mesh components are shown
547:15 the wireless mesh components are shown here
547:16 here the wcs
547:18 the wcs the wlc
547:20 the wlc the rap and the map
547:28 the following are cisco recommendations for mesh design
547:30 for mesh design there is under 10 millisecond latency
547:32 there is under 10 millisecond latency per hop typically two to three
547:34 per hop typically two to three millisecond
547:35 millisecond for outdoor deployment four or fewer
547:37 for outdoor deployment four or fewer hops are recommended for best
547:38 hops are recommended for best performance with a maximum of eight
547:42 performance with a maximum of eight for indoor deployment one hop is
547:43 for indoor deployment one hop is supported
547:45 supported for best performance 20 map nodes per
547:48 for best performance 20 map nodes per wrap is recommended
547:51 wrap is recommended up to 32 maps is supported per wrap
547:56 up to 32 maps is supported per wrap throughput one hop 14 megabits per
547:59 throughput one hop 14 megabits per second two hops seven megabits per
548:01 second two hops seven megabits per second
548:02 second three hops three megabit and four hops
548:05 three hops three megabit and four hops one megabits per second
548:12 as you can see here you have five primary design items number of aps
548:16 five primary design items number of aps placement of aps
548:18 placement of aps power for aps
548:19 power for aps number of wlc's and placement of wlc's
548:24 number of wlc's and placement of wlc's the following points summarize wireless
548:26 the following points summarize wireless lan design
548:28 lan design an rf site survey is used to determine a
548:30 an rf site survey is used to determine a wireless network's rf characteristics
548:32 wireless network's rf characteristics and ap placement
548:34 and ap placement outdoor wireless networks are supported
548:36 outdoor wireless networks are supported using outdoor aps and cisco wireless
548:39 using outdoor aps and cisco wireless mesh networking aps
548:41 mesh networking aps campus wireless network design provides
548:43 campus wireless network design provides rf coverage for wireless clients in the
548:45 rf coverage for wireless clients in the campus using lwp's
548:48 campus using lwp's each ap should be limited to 20 data
548:51 each ap should be limited to 20 data devices and a data
548:54 devices and a data wireless lan
548:56 wireless lan so here's what you've learned you've
548:57 so here's what you've learned you've learned about wireless redundancy rf
548:59 learned about wireless redundancy rf groups and mesh design all are key
549:02 groups and mesh design all are key points on the ccda exam
549:04 points on the ccda exam that you will need to know
549:06 that you will need to know and be able to answer not only on your
549:09 and be able to answer not only on your exam but of course if you support
549:11 exam but of course if you support wireless in your own network good luck
549:13 wireless in your own network good luck in your studies