WEBVTT

1
00:00:00.040 --> 00:00:03.120
<v Speaker 1>Hey, everyone, welcome back. Today we're taking a deep dive

2
00:00:03.240 --> 00:00:07.639
<v Speaker 1>into well, deep dives network design, deep dives at it.

3
00:00:07.759 --> 00:00:11.880
<v Speaker 1>Oh yeah, we're cracking open the Network Design cookbook Architecting

4
00:00:12.039 --> 00:00:13.160
<v Speaker 1>Cisco Networks.

5
00:00:13.160 --> 00:00:14.599
<v Speaker 2>Oh nice, I like that one.

6
00:00:14.720 --> 00:00:18.679
<v Speaker 1>Yeah. It's got it all, land, setup, security, you name it.

7
00:00:18.719 --> 00:00:21.160
<v Speaker 1>And it's super practical, which I know we both appreciate.

8
00:00:21.280 --> 00:00:23.640
<v Speaker 2>Yeah, for sure, I'm all about that real world application.

9
00:00:23.960 --> 00:00:27.239
<v Speaker 1>Me too, So ready to get our hands dirty, let's

10
00:00:27.320 --> 00:00:30.920
<v Speaker 1>do it. Okay, So first things first, why is network

11
00:00:30.960 --> 00:00:32.320
<v Speaker 1>designed such a big deal.

12
00:00:33.159 --> 00:00:36.399
<v Speaker 2>Well, it's like imagine a building, right, you don't see

13
00:00:36.399 --> 00:00:39.280
<v Speaker 2>the foundation, but it's holding the whole thing up exactly.

14
00:00:39.479 --> 00:00:41.880
<v Speaker 2>And it's the same with networks. They're the backbone of

15
00:00:42.240 --> 00:00:43.759
<v Speaker 2>well pretty much everything in it.

16
00:00:44.280 --> 00:00:46.759
<v Speaker 1>True, and when they go down, oh.

17
00:00:46.479 --> 00:00:51.439
<v Speaker 2>Man, it's a disaster. Businesses can't function, communication goes out

18
00:00:51.479 --> 00:00:54.359
<v Speaker 2>the windows, total chao, yeah, chaos. And that's where good

19
00:00:54.399 --> 00:00:58.000
<v Speaker 2>network design comes in, prevents those meltdowns exactly. And this

20
00:00:58.039 --> 00:01:00.399
<v Speaker 2>book it's great because it really that's that.

21
00:01:00.560 --> 00:01:04.879
<v Speaker 1>Yeah, and it bringges the gap between network administration and engineering, which,

22
00:01:05.239 --> 00:01:07.359
<v Speaker 1>let's be honest, a lot of us wear both hats,

23
00:01:07.439 --> 00:01:08.879
<v Speaker 1>especially in smaller setups.

24
00:01:08.879 --> 00:01:11.840
<v Speaker 2>Totally like, oh, you need me to fix the printer? Sure?

25
00:01:11.920 --> 00:01:16.040
<v Speaker 2>And also can I rebuild the entire network infrastructure while

26
00:01:16.040 --> 00:01:16.439
<v Speaker 2>I'm at it?

27
00:01:16.560 --> 00:01:17.640
<v Speaker 1>Uh huh exactly.

28
00:01:17.680 --> 00:01:20.159
<v Speaker 2>This book gets it, it does okay, But you know

29
00:01:20.200 --> 00:01:21.799
<v Speaker 2>what it really got me excited about this book?

30
00:01:21.840 --> 00:01:22.200
<v Speaker 1>What's that?

31
00:01:22.400 --> 00:01:27.680
<v Speaker 2>It's all about real world problem solving, no fluff, just solutions.

32
00:01:28.000 --> 00:01:29.840
<v Speaker 2>I don't know about you, but I've spent way too

33
00:01:29.920 --> 00:01:32.959
<v Speaker 2>much time wading through conflicting advice online.

34
00:01:33.319 --> 00:01:35.879
<v Speaker 1>Ugh, tell me about it. It's like everyone's a self

35
00:01:35.879 --> 00:01:37.760
<v Speaker 1>proclaimed expert these days, right, and then.

36
00:01:37.719 --> 00:01:39.640
<v Speaker 2>You try to piece it all together and it's just

37
00:01:39.680 --> 00:01:40.640
<v Speaker 2>a mess totally.

38
00:01:40.959 --> 00:01:44.079
<v Speaker 1>But this book, it's like having a roadmap. It's clear,

39
00:01:44.319 --> 00:01:47.120
<v Speaker 1>structured and it doesn't overwhelm you with jargon.

40
00:01:47.319 --> 00:01:49.640
<v Speaker 2>Exactly. It's what I needed like yesterday.

41
00:01:49.760 --> 00:01:53.159
<v Speaker 1>Uh huh. Well, I think you'll appreciate the seven step

42
00:01:53.319 --> 00:01:54.280
<v Speaker 1>design process.

43
00:01:54.280 --> 00:01:57.599
<v Speaker 2>They lay out seven steps. That sounds manageable.

44
00:01:57.840 --> 00:02:00.680
<v Speaker 1>It is. It breaks down this huge task into bite

45
00:02:00.719 --> 00:02:01.519
<v Speaker 1>sized pieces.

46
00:02:01.760 --> 00:02:04.480
<v Speaker 2>Okay, I'm intrigued. Walk me through it. What's step one?

47
00:02:04.920 --> 00:02:08.759
<v Speaker 1>Step one is all about understanding the why why are

48
00:02:08.800 --> 00:02:10.879
<v Speaker 1>you building this network in the first place? What are

49
00:02:10.879 --> 00:02:14.120
<v Speaker 1>the business needs? The technical goals. It's about seeing the

50
00:02:14.159 --> 00:02:18.159
<v Speaker 1>big picture before you even start thinking about cables and routers.

51
00:02:18.280 --> 00:02:21.560
<v Speaker 2>Okay, so define the why first, that makes sense. Then what?

52
00:02:22.080 --> 00:02:25.080
<v Speaker 1>Then you move on to choosing the right solutions for

53
00:02:25.159 --> 00:02:30.479
<v Speaker 1>your needs. Are we talking land wand specific security tools.

54
00:02:31.080 --> 00:02:32.879
<v Speaker 1>It's like picking the right tools for a job.

55
00:02:33.080 --> 00:02:35.719
<v Speaker 2>So like choosing between a hammer and a screwdriver. Yeah,

56
00:02:35.719 --> 00:02:38.080
<v Speaker 2>you need to know what you're building before you grab.

57
00:02:37.840 --> 00:02:40.639
<v Speaker 1>A tool, exactly. And then step three and four are

58
00:02:40.680 --> 00:02:43.639
<v Speaker 1>where you actually get into the design of those solutions,

59
00:02:43.639 --> 00:02:46.039
<v Speaker 1>the needy gritty. But what I think is really cool

60
00:02:46.240 --> 00:02:49.039
<v Speaker 1>and what you might find helpful is how much emphasis

61
00:02:49.120 --> 00:02:51.439
<v Speaker 1>they put on gathering the right requirements early on.

62
00:02:51.599 --> 00:02:54.599
<v Speaker 2>Oh yeah, getting the requirements right can make or break

63
00:02:54.639 --> 00:02:56.840
<v Speaker 2>a project. I've definitely learned that the hard way.

64
00:02:57.120 --> 00:03:01.199
<v Speaker 1>It's huge, and this book it stresses asking the right questions,

65
00:03:01.240 --> 00:03:04.080
<v Speaker 1>not just the obvious ones. They even give you example, Oh,

66
00:03:04.240 --> 00:03:06.199
<v Speaker 1>like what so instead of just asking what kind of

67
00:03:06.199 --> 00:03:09.599
<v Speaker 1>internet speed do you need, which, let's be real, everyone

68
00:03:09.639 --> 00:03:12.800
<v Speaker 1>wants the fastest, they suggest asking about the types of

69
00:03:12.840 --> 00:03:15.680
<v Speaker 1>applications they use, how many users they have, if they're

70
00:03:15.719 --> 00:03:19.240
<v Speaker 1>doing a lot of video conferencing, even their technical preferences

71
00:03:19.240 --> 00:03:19.919
<v Speaker 1>and dislikes.

72
00:03:20.199 --> 00:03:23.280
<v Speaker 2>Because those little details can actually make a huge difference

73
00:03:23.319 --> 00:03:24.000
<v Speaker 2>down the line.

74
00:03:24.080 --> 00:03:27.800
<v Speaker 1>Exactly. It's all about tailoring the solution to their specific needs,

75
00:03:28.240 --> 00:03:31.280
<v Speaker 1>not just throwing something generic at them and hoping it sticks.

76
00:03:31.520 --> 00:03:34.000
<v Speaker 2>I'm loving this book already. So we've got our requirements

77
00:03:34.080 --> 00:03:35.479
<v Speaker 2>nailed down, what's next.

78
00:03:35.599 --> 00:03:37.879
<v Speaker 1>That's where we get to the fun part, using the

79
00:03:37.919 --> 00:03:40.800
<v Speaker 1>hardware to bring it all together. And this is where

80
00:03:40.800 --> 00:03:43.280
<v Speaker 1>the Cisco focus really comes in handy.

81
00:03:43.080 --> 00:03:46.280
<v Speaker 2>Right, Cisco specific, but even if someone's not a Cisco expert,

82
00:03:46.479 --> 00:03:48.439
<v Speaker 2>the principles still apply right absolutely.

83
00:03:49.039 --> 00:03:51.960
<v Speaker 1>The key is understanding how to match the hardware to

84
00:03:52.039 --> 00:03:55.639
<v Speaker 1>your design goals. For example, they talk about how Cisco's

85
00:03:55.680 --> 00:03:59.439
<v Speaker 1>Catalyst switches have models for everything from small businesses to

86
00:03:59.560 --> 00:04:00.960
<v Speaker 1>huge general prizes.

87
00:04:00.800 --> 00:04:03.879
<v Speaker 2>So it's not a one size fits all approach to hardware,

88
00:04:04.120 --> 00:04:07.280
<v Speaker 2>which again makes sense, but I imagine there are often

89
00:04:07.400 --> 00:04:10.280
<v Speaker 2>multiple ways to design a network, right, Like, how does

90
00:04:10.319 --> 00:04:11.159
<v Speaker 2>this book handle that?

91
00:04:11.599 --> 00:04:13.680
<v Speaker 1>Yeah, you're spot on. There are usually a bunch of

92
00:04:13.680 --> 00:04:15.680
<v Speaker 1>different ways you could go about it, and that's where

93
00:04:15.680 --> 00:04:17.199
<v Speaker 1>it can get you a little overwhelming.

94
00:04:17.279 --> 00:04:21.079
<v Speaker 2>Oh yeah, for sure, too many choices, analysis, paralysis, all.

95
00:04:21.000 --> 00:04:25.199
<v Speaker 1>That, exactly, But this book is great at laying out

96
00:04:25.240 --> 00:04:28.600
<v Speaker 1>those different options and then walking you through the good

97
00:04:28.639 --> 00:04:31.399
<v Speaker 1>and the bad of each one helps you avoid those

98
00:04:31.439 --> 00:04:32.360
<v Speaker 1>decision spirals.

99
00:04:32.399 --> 00:04:36.120
<v Speaker 2>Okay, good, because I'm all about avoiding spirals whenever possible.

100
00:04:36.600 --> 00:04:39.000
<v Speaker 2>So how does it help you choose? Give me an example.

101
00:04:39.079 --> 00:04:41.079
<v Speaker 1>Okay, let's say you're trying to decide between a twenty

102
00:04:41.120 --> 00:04:43.319
<v Speaker 1>four port switch and a forty eight port switch.

103
00:04:43.360 --> 00:04:45.199
<v Speaker 2>Okay, I see where you're going with this, right.

104
00:04:45.480 --> 00:04:49.680
<v Speaker 1>So the forty eight port might seem like overkill it first,

105
00:04:49.759 --> 00:04:52.399
<v Speaker 1>But what if your business takes off Suddenly You've got

106
00:04:52.439 --> 00:04:55.800
<v Speaker 1>a ton of new devices and need more ports. That's

107
00:04:55.800 --> 00:04:57.720
<v Speaker 1>where thinking about scalability comes in.

108
00:04:57.920 --> 00:05:00.720
<v Speaker 2>Right, planning for the future, not just the right now.

109
00:05:01.000 --> 00:05:03.600
<v Speaker 1>Exactly, And this book really helps you do that.

110
00:05:03.600 --> 00:05:06.480
<v Speaker 2>That's super helpful. What about things that people might not

111
00:05:06.519 --> 00:05:08.480
<v Speaker 2>even think about? Like, what are some of the less

112
00:05:08.519 --> 00:05:10.399
<v Speaker 2>obvious things that this book covers.

113
00:05:11.000 --> 00:05:14.079
<v Speaker 1>Well, it gets into power and cooling considerations, which are,

114
00:05:14.360 --> 00:05:15.920
<v Speaker 1>believe it or not, super.

115
00:05:15.600 --> 00:05:18.279
<v Speaker 2>Important power and cooling. Okay, oh min those aren't usually

116
00:05:18.279 --> 00:05:19.920
<v Speaker 2>the first things that come to mind when I think

117
00:05:19.920 --> 00:05:21.079
<v Speaker 2>about networks, I know.

118
00:05:21.160 --> 00:05:24.480
<v Speaker 1>Right, But think about it, all those switches and servers

119
00:05:24.759 --> 00:05:27.720
<v Speaker 1>they generate heat. You don't want to overload your circuits

120
00:05:27.920 --> 00:05:30.040
<v Speaker 1>or even worse. Fry your equipment.

121
00:05:30.199 --> 00:05:32.680
<v Speaker 2>Yeah, freight equipment is no good, not good at all.

122
00:05:32.920 --> 00:05:36.759
<v Speaker 1>The book even has this little tip about not exceeding

123
00:05:36.920 --> 00:05:40.040
<v Speaker 1>seventy five percent of a power circuit's capacity when you're

124
00:05:40.040 --> 00:05:42.920
<v Speaker 1>hooking up network gear, just like a safety buffer.

125
00:05:43.120 --> 00:05:47.079
<v Speaker 2>Smart. Okay. So it's really thinking about all those practical considerations.

126
00:05:47.240 --> 00:05:49.560
<v Speaker 1>Yes, And that's what I love about it. It's not

127
00:05:49.680 --> 00:05:52.839
<v Speaker 1>just about the techie stuff. It's about understanding the bigger

128
00:05:52.920 --> 00:05:55.959
<v Speaker 1>picture of how to build a network that's going to last.

129
00:05:56.160 --> 00:05:58.279
<v Speaker 2>Yeah, building it to last, building it right.

130
00:05:58.639 --> 00:06:01.480
<v Speaker 1>And one thing that often gets overlooked but is so

131
00:06:01.560 --> 00:06:04.800
<v Speaker 1>important for long term success is documentation.

132
00:06:05.279 --> 00:06:09.240
<v Speaker 2>Oh documentation. Okay, so not the most exciting topic.

133
00:06:09.000 --> 00:06:11.800
<v Speaker 1>But I know, I know, but trust me, it's crucial.

134
00:06:11.839 --> 00:06:14.800
<v Speaker 2>Okay, I'm listening. Why is documentation so important?

135
00:06:14.879 --> 00:06:19.360
<v Speaker 1>Okay? Imagine trying to troubleshoot a problem without any documentation.

136
00:06:20.040 --> 00:06:23.439
<v Speaker 1>It's like you're trying to solve a puzzle but half

137
00:06:23.480 --> 00:06:24.439
<v Speaker 1>the pieces are missing.

138
00:06:25.199 --> 00:06:26.920
<v Speaker 2>Oh yeah, that sounds frustrating.

139
00:06:27.000 --> 00:06:29.839
<v Speaker 1>It's a nightmare. Good documentation is like having a roadmap

140
00:06:29.879 --> 00:06:33.000
<v Speaker 1>for your entire network. You can see how everything is connected,

141
00:06:33.040 --> 00:06:35.319
<v Speaker 1>how it's supposed to work, and it just makes everything

142
00:06:35.439 --> 00:06:36.199
<v Speaker 1>so much easier.

143
00:06:36.480 --> 00:06:38.759
<v Speaker 2>So it's like if your network was a car, the

144
00:06:38.800 --> 00:06:40.839
<v Speaker 2>documentation is the owner's manual.

145
00:06:41.040 --> 00:06:44.759
<v Speaker 1>Yes, yeah, exactly. And it's not just for troubleshooting either.

146
00:06:45.160 --> 00:06:48.639
<v Speaker 1>Documentation is also super important for compliance.

147
00:06:48.240 --> 00:06:51.199
<v Speaker 2>Oh right, compliance, because there are all those rules and

148
00:06:51.240 --> 00:06:53.959
<v Speaker 2>regulations about data security and all that, exactly.

149
00:06:53.680 --> 00:06:56.759
<v Speaker 1>And having good documentation can be the difference between passing

150
00:06:56.759 --> 00:06:59.480
<v Speaker 1>an audit and well not passing an audit.

151
00:06:59.560 --> 00:07:01.519
<v Speaker 2>And we all know which side of that equation we'd

152
00:07:01.600 --> 00:07:03.000
<v Speaker 2>rather be on for sure.

153
00:07:03.120 --> 00:07:05.519
<v Speaker 1>And the cool thing is this book it actually gives

154
00:07:05.560 --> 00:07:08.279
<v Speaker 1>you the tools and like the frameworks you need to

155
00:07:08.279 --> 00:07:09.519
<v Speaker 1>create good documentation.

156
00:07:09.879 --> 00:07:11.000
<v Speaker 2>Oh that's really helpful. Yeh.

157
00:07:11.000 --> 00:07:12.759
<v Speaker 1>It helps you figure out what information you need to

158
00:07:12.800 --> 00:07:15.519
<v Speaker 1>record and how to organize it all. So it's actually useful.

159
00:07:15.560 --> 00:07:16.279
<v Speaker 1>It's really cool.

160
00:07:16.399 --> 00:07:18.519
<v Speaker 2>So it's not just about the what, it's about the how.

161
00:07:19.079 --> 00:07:20.480
<v Speaker 1>Yes, precisely.

162
00:07:20.680 --> 00:07:23.439
<v Speaker 2>I love that. It's like, this book isn't just trying

163
00:07:23.480 --> 00:07:26.079
<v Speaker 2>to teach you about network design. It's trying to teach

164
00:07:26.120 --> 00:07:28.439
<v Speaker 2>you how to think like a network architect.

165
00:07:28.720 --> 00:07:31.639
<v Speaker 1>Yes, one hundred percent. It's about taking that step back

166
00:07:32.199 --> 00:07:35.839
<v Speaker 1>and thinking about all the factors involved and designing a

167
00:07:35.879 --> 00:07:39.879
<v Speaker 1>network that's not just a functional but also sustainable in

168
00:07:39.920 --> 00:07:41.040
<v Speaker 1>the long run totally.

169
00:07:41.639 --> 00:07:44.720
<v Speaker 2>And on that note, I have to say, I'm really

170
00:07:44.759 --> 00:07:50.160
<v Speaker 2>impressed with how this book manages to be super comprehensive.

171
00:07:50.240 --> 00:07:52.279
<v Speaker 2>You know, it really gets into the details, but it's

172
00:07:52.319 --> 00:07:54.040
<v Speaker 2>still so accessible.

173
00:07:54.240 --> 00:07:55.839
<v Speaker 1>Right, it's not one of those books that's just going

174
00:07:55.879 --> 00:07:56.560
<v Speaker 1>to go right.

175
00:07:56.360 --> 00:07:58.439
<v Speaker 2>Over your head exactly. It doesn't feel like you need

176
00:07:58.439 --> 00:08:00.360
<v Speaker 2>a PhD in networking to underst stand it.

177
00:08:00.519 --> 00:08:02.519
<v Speaker 1>I know. It's actually kind of fun to read.

178
00:08:02.720 --> 00:08:04.319
<v Speaker 2>It is. It's making me want to go out and

179
00:08:04.360 --> 00:08:05.839
<v Speaker 2>design a network from scratch.

180
00:08:06.120 --> 00:08:08.920
<v Speaker 1>Uh huh, Right, it's getting those creative juices flowing.

181
00:08:09.240 --> 00:08:12.480
<v Speaker 2>It really is. Okay, so we've talked about the big

182
00:08:12.480 --> 00:08:16.680
<v Speaker 2>picture of network design. We've talked about planning and gathering requirements.

183
00:08:17.399 --> 00:08:20.439
<v Speaker 2>Now I'm ready to see it all come together. Tell

184
00:08:20.480 --> 00:08:24.160
<v Speaker 2>me about these real world examples. How do they actually

185
00:08:24.160 --> 00:08:27.399
<v Speaker 2>put these seven steps into practice?

186
00:08:27.600 --> 00:08:30.279
<v Speaker 1>Okay, so real world examples. Let's see how this actually

187
00:08:30.360 --> 00:08:31.319
<v Speaker 1>works in practice.

188
00:08:31.639 --> 00:08:34.360
<v Speaker 2>Yeah, they've got some great examples in here, different businesses,

189
00:08:34.399 --> 00:08:37.600
<v Speaker 2>different scenarios. It's really helpful, like what kinds of things. Well,

190
00:08:37.639 --> 00:08:40.320
<v Speaker 2>one thing I found really interesting was how they handled

191
00:08:40.320 --> 00:08:43.879
<v Speaker 2>decisions where there isn't like a single right answer.

192
00:08:44.120 --> 00:08:45.919
<v Speaker 1>Oh, I know. You mean, like when you've got multiple

193
00:08:46.000 --> 00:08:47.720
<v Speaker 1>options and they all have their pros and.

194
00:08:47.679 --> 00:08:49.960
<v Speaker 2>Costs exactly, and you have to figure out the best

195
00:08:50.000 --> 00:08:52.240
<v Speaker 2>fit for that specific situation, right, Like is.

196
00:08:52.240 --> 00:08:55.440
<v Speaker 1>It better to go with a traditional land setup or

197
00:08:55.480 --> 00:08:58.519
<v Speaker 1>a unified topology or do you go all out with

198
00:08:58.600 --> 00:08:59.639
<v Speaker 1>a virtualized land?

199
00:09:00.600 --> 00:09:03.240
<v Speaker 2>And this book does a great job of like walking

200
00:09:03.279 --> 00:09:05.919
<v Speaker 2>you through those thought processes. Like, let's say you're working

201
00:09:05.960 --> 00:09:08.559
<v Speaker 2>with a mid size company and they're growing like crazy.

202
00:09:08.639 --> 00:09:10.840
<v Speaker 1>Okay, I can see where this is going, right, So

203
00:09:10.879 --> 00:09:14.039
<v Speaker 1>they need something that's scalable they can grow with them,

204
00:09:14.159 --> 00:09:16.440
<v Speaker 1>but they don't want something super complicated to manage.

205
00:09:16.600 --> 00:09:19.039
<v Speaker 2>Yeah, finding that balance is key totally.

206
00:09:19.440 --> 00:09:21.639
<v Speaker 1>So in that case, they might recommend going with a

207
00:09:21.720 --> 00:09:22.679
<v Speaker 1>unified topology.

208
00:09:22.879 --> 00:09:26.080
<v Speaker 2>Unified topology okay, and remind me what that is again.

209
00:09:26.360 --> 00:09:29.960
<v Speaker 1>So basically, instead of having separate access and distribution layers,

210
00:09:30.320 --> 00:09:34.000
<v Speaker 1>you're kind of bundling those access switches into the core switch.

211
00:09:34.200 --> 00:09:35.919
<v Speaker 2>It's more streamlined.

212
00:09:35.600 --> 00:09:39.679
<v Speaker 1>Exactly, less hardware, easier to manage, and as much easier

213
00:09:39.679 --> 00:09:41.080
<v Speaker 1>to expand as your needs grow.

214
00:09:41.320 --> 00:09:44.519
<v Speaker 2>Okay, that makes sense, but what about security? Wouldn't a

215
00:09:44.559 --> 00:09:47.799
<v Speaker 2>more traditional setup with those separate layers give you more

216
00:09:47.840 --> 00:09:49.480
<v Speaker 2>control over network traffic.

217
00:09:49.840 --> 00:09:52.440
<v Speaker 1>That's a great point. Security is super important, and the

218
00:09:52.480 --> 00:09:55.399
<v Speaker 1>book talks about that too. How even with a unified topology,

219
00:09:55.960 --> 00:10:00.320
<v Speaker 1>you can still implement strong security measures. Oh okay, good, Yeah,

220
00:10:00.320 --> 00:10:03.440
<v Speaker 1>like using VLANs to segment your traffic, create those separate

221
00:10:03.480 --> 00:10:07.600
<v Speaker 1>security zones right vlands exactly, and you can use access

222
00:10:07.639 --> 00:10:11.039
<v Speaker 1>control lists to get really specific about who has access

223
00:10:11.080 --> 00:10:11.279
<v Speaker 1>to what.

224
00:10:11.559 --> 00:10:13.480
<v Speaker 2>So it's not an either you can kind of have

225
00:10:13.559 --> 00:10:15.759
<v Speaker 2>the best of both worlds exactly.

226
00:10:15.840 --> 00:10:18.879
<v Speaker 1>It's about finding the right balance for that particular organization.

227
00:10:19.240 --> 00:10:22.080
<v Speaker 2>I love that, and I love that this book emphasizes that.

228
00:10:22.480 --> 00:10:25.120
<v Speaker 2>Because there are so many variables, it's never going to

229
00:10:25.120 --> 00:10:27.480
<v Speaker 2>be a one size fits all solution exactly.

230
00:10:27.519 --> 00:10:29.559
<v Speaker 1>And I think that's what makes this book so valuable.

231
00:10:29.679 --> 00:10:31.600
<v Speaker 1>It doesn't just give you the answers. It teaches you

232
00:10:31.639 --> 00:10:34.440
<v Speaker 1>how to think critically and make those decisions for yourself.

233
00:10:34.639 --> 00:10:36.759
<v Speaker 2>It's like that saying, give a man a fish he

234
00:10:36.799 --> 00:10:38.919
<v Speaker 2>eats for a day, teach a man the fish he

235
00:10:38.960 --> 00:10:40.000
<v Speaker 2>eats for a lifetime.

236
00:10:40.159 --> 00:10:45.399
<v Speaker 1>Yeah, exactly. It's about empowering you to become a network architect. Yeah,

237
00:10:45.440 --> 00:10:47.000
<v Speaker 1>not just someone who follows instructions.

238
00:10:47.120 --> 00:10:50.600
<v Speaker 2>Yes, I love that. Well, this has been an incredible

239
00:10:50.639 --> 00:10:53.039
<v Speaker 2>deep dive. It has I feel like we've covered so

240
00:10:53.159 --> 00:10:57.639
<v Speaker 2>much ground. We talked about the importance of planning, gathering requirements,

241
00:10:57.960 --> 00:11:01.279
<v Speaker 2>choosing the right solutions, and of course all those crucial

242
00:11:01.320 --> 00:11:06.159
<v Speaker 2>details like power management, security and documentation. It's all connected,

243
00:11:06.440 --> 00:11:08.840
<v Speaker 2>it really is, and I hope our listeners are feeling

244
00:11:08.879 --> 00:11:12.279
<v Speaker 2>inspired and equipped to tackle their own network design challenges.

245
00:11:12.440 --> 00:11:17.600
<v Speaker 1>Me too. And remember, learning never stops. There's always something

246
00:11:17.720 --> 00:11:19.639
<v Speaker 1>new to discover in the world of network design.

247
00:11:19.919 --> 00:11:23.080
<v Speaker 2>That is so true. Technology waits for no one. But

248
00:11:23.159 --> 00:11:25.960
<v Speaker 2>for now, we're going to hit pause on this deep dive.

249
00:11:26.360 --> 00:11:30.679
<v Speaker 2>Big thanks to the Network design cookbook Architecting Cisco Networks

250
00:11:30.720 --> 00:11:31.480
<v Speaker 2>for being our guide.

251
00:11:31.639 --> 00:11:32.440
<v Speaker 1>Such a good book.

252
00:11:32.600 --> 00:11:35.559
<v Speaker 2>It is all right everyone. That's it for today. Until

253
00:11:35.600 --> 00:11:36.840
<v Speaker 2>next time, Happy networking,