Designing Remote Connectivity Part 03 — Transcript

Full transcript

1. 0:04designing the enterprise
2. 0:05branch
3. 0:09enterprise branch and teleworker design
4. 0:13this section describes design
5. 0:15considerations
6. 0:16for the enterprise branch and enterprise
7. 0:19teleworker architectures
8. 0:23enterprise branch architecture so recall
9. 0:26that the cisco enterprise architecture
10. 0:28based on the cisco sauna includes branch
11. 0:32modules that focus on the remote places
12. 0:35in the network
13. 0:36so enterprises are seeking opportunities
14. 0:39to protect
15. 0:40optimize and grow their businesses by
16. 0:43increasing security
17. 0:45consolidating voice and video and data
18. 0:48onto a single ip network
19. 0:49and investing in applications that will
20. 0:52improve
21. 0:53productivity and operating efficiencies
22. 0:57now this services provides an
23. 0:59enterprises
24. 1:00with new opportunities to reduce costs
25. 1:04improve productivity and safeguard
26. 1:07information assets
27. 1:09in all their locations the cisco
28. 1:12enterprise branch architecture
29. 1:14takes into account the services that
30. 1:15enterprises want to deploy
31. 1:17at their endpoints no matter how far
32. 1:20the end points are or how they are
33. 1:23connected
34. 1:25now on this figure here it illustrates
35. 1:28how branch services relate to other
36. 1:31parts
37. 1:32of the cisco enterprise architectures
38. 1:34you've got the branch one
39. 1:36or branch of one branch campus branch
40. 1:39branch
41. 1:40and so on
42. 1:43enterprise branch architecture the cisco
43. 1:46enterprise
44. 1:47branch architecture illustrated on this
45. 1:49diagram here
46. 1:50is an integrated flexible and secure
47. 1:53framework
48. 1:54for extending headquarters applications
49. 1:56in real time
50. 1:58to remote sites the cisco enterprise
51. 2:01branch architecture applies the sauna
52. 2:03framework
53. 2:04to the smaller scale of branch location
54. 2:08so common network components that might
55. 2:10be implemented in the enterprise branch
56. 2:12includes
57. 2:13the following so first you've got the
58. 2:16routers providing one edge connectivity
59. 2:19okay switches providing the lan
60. 2:22infrastructure
61. 2:24security appliances defending the branch
62. 2:26devices
63. 2:28and wireless access points for device
64. 2:31mobility
65. 2:34characterizing the branch so enterprise
66. 2:38branch design so requirements
67. 2:42differ with the size of the branch
68. 2:44offices
69. 2:45consider the following questions when
70. 2:47designing the enterprise branch
71. 2:50so first would be how many branch
72. 2:52locations
73. 2:54need to be supported second would be
74. 2:58how many existing devices including end
75. 3:01users
76. 3:02hosts and network infrastructures
77. 3:06are to be supported at each location the
78. 3:09number of devices supported is limited
79. 3:12by the number of physical uh
80. 3:15ports available okay
81. 3:18next would be how much growth is
82. 3:21expected at each location
83. 3:24and therefore what level of scalability
84. 3:27is required
85. 3:30next would be what are the high
86. 3:32availability requirements
87. 3:34at each location what are the level of
88. 3:38security
89. 3:39okay should the security be managed
90. 3:42locally
91. 3:42or through the central location
92. 3:46are there any requirements for local
93. 3:48server farms
94. 3:49or network between the internal network
95. 3:52and external network for example in a
96. 3:55demilitarized
97. 3:56zone or dmz okay
98. 4:00next would be should the network
99. 4:01management be supported locally or via
100. 4:03the central location
101. 4:06what wireless services are needed and
102. 4:10how will they be used by the clients
103. 4:12what effect will the network and the
104. 4:15environment have
105. 4:16on the wireless devices okay
106. 4:19and then the last one would be what is
107. 4:21the approximate budget available
108. 4:24so the key point here is branch offices
109. 4:28can be categorized based on the number
110. 4:30of users
111. 4:32okay so a small office up to 50 users
112. 4:35using a single tier design
113. 4:38for medium office between 50 and 100
114. 4:41users
115. 4:42using a dual tier design and for large
116. 4:45offices
117. 4:46between 100 and 200 users using a
118. 4:49three-tier
119. 4:50design
120. 4:55small branch office design so small
121. 4:58branch office designs combines
122. 5:00an isr access router with layer 2
123. 5:03switching
124. 5:04and end user devices phones
125. 5:07printers and so forth okay a typical
126. 5:10design is illustrated
127. 5:12on this figure here okay so
128. 5:16you've got one services one services are
129. 5:19typically provided by a t1 primary link
130. 5:23the internet is used as a one backup
131. 5:25accessed by
132. 5:27an adsl connection okay
133. 5:30now for the network services the eigrp
134. 5:33routing protocol is used
135. 5:35so high availability across the one is
136. 5:38provided
137. 5:39by the floating static routes across the
138. 5:42adsl internet connection
139. 5:44and the qos mechanism include
140. 5:47or the traffic shaping and policy okay
141. 5:50and the implementation of the scavenger
142. 5:52class of traffic
143. 5:53applied on both the switch and the isrs
144. 6:00now for the medium branch office design
145. 6:03a typical medium branch of this topology
146. 6:06is illustrated
147. 6:07on this figure here okay this is similar
148. 6:10to the small office topology except that
149. 6:12the one edge devices are larger
150. 6:15typically
151. 6:16two routers were used here okay and the
152. 6:19access switches for land connectivity
153. 6:20are external stackable switches
154. 6:23now for the one services one services
155. 6:27are typically provided by a private one
156. 6:29for example
157. 6:30with dual uh one
158. 6:33technology okay so in this example
159. 6:37well the old frame relay links you've
160. 6:40got the network
161. 6:41services okay like the use of the eigrp
162. 6:45routing protocol
163. 6:46high availability across the one is
164. 6:48provided by dual routers
165. 6:51running router redundancy protocols such
166. 6:54as
167. 6:55hsrp or the hot standby router protocol
168. 6:59vrrp or the virtual router redundancy
169. 7:02protocol
170. 7:02and the glbp which is a gateway load
171. 7:05balancing protocol
172. 7:07so qos mechanism
173. 7:10okay used include traffic shaping and
174. 7:14policing
175. 7:15and the implementation of the scavenger
176. 7:17class of traffic applied on both
177. 7:19the switch and the isrs
178. 7:24now for the large branch office design
179. 7:27in a typical large branch office design
180. 7:29as illustrated in this figure here
181. 7:32dual isrs are used for redundancy at the
182. 7:35one edge
183. 7:37so firewall functionality is provided by
184. 7:39dual adaptive security appliances
185. 7:42or the isas and dual multi-layer
186. 7:45switches
187. 7:46stackable or modular are deployed at the
188. 7:48distribution layer
189. 7:50now for the one services in this typical
190. 7:53design
191. 7:55provided by an mpls network with dual
192. 7:57connections
193. 7:59and network services eigrp routing
194. 8:02protocol is used
195. 8:04so high availability across the one is
196. 8:06provided by dual routers running
197. 8:08the redundancy protocols such as the
198. 8:10hsrp
199. 8:13vrrp and glb you also have the asa
200. 8:18failover functionality and object
201. 8:20tracking
202. 8:21now the qos mechanisms used include
203. 8:23traffic shaping and policing
204. 8:26and the implementation of the scavenger
205. 8:28class of traffic applied on both the
206. 8:30switch
207. 8:31and the isrs
208. 8:36comparison of teleworking options now in
209. 8:39contrast
210. 8:40enterprise teleworkers can be
211. 8:42differentiated from other forms
212. 8:44of a work at home or telecommuting
213. 8:47scenarios
214. 8:48in that the emphasis is on delivering
215. 8:50seamless
216. 8:51managed accessibility to full range of
217. 8:53applications and services
218. 8:55critical to the operational
219. 8:57effectiveness of the enterprises
220. 8:59okay as shown here in this diagram now
221. 9:02the cisco enterprise teleworker
222. 9:03architecture is part of an
223. 9:05overall secure cisco enterprise
224. 9:07architecture infrastructure
225. 9:09it companies the capability to integrate
226. 9:14and securely manage their remote workers
227. 9:17within the corporate network
228. 9:18while simultaneously providing a high
229. 9:21quality
230. 9:22end user experience supporting a full
231. 9:25range
232. 9:26of enterprise applications for the
233. 9:28enterprise
234. 9:29teleworkers
235. 9:34the enterprise teleworker typically
236. 9:36connects to an isp through
237. 9:38a dsl or cable modem or broadband and
238. 9:40might use an analog dial-up session to
239. 9:42backup this connection
240. 9:45the enterprise teleworker solution is
241. 9:47implemented
242. 9:48with the small isr routers okay so with
243. 9:50integrated switch ports
244. 9:52connected behind the broadband modem as
245. 9:55shown in this
246. 9:56figure here okay
247. 9:59now this solution uses a transparent
248. 10:02always on vpn channel back to the
249. 10:04enterprise
250. 10:06so within this architecture centralized
251. 10:09management
252. 10:09means that the enterprise applies
253. 10:11security policies
254. 10:13push-us configurations and periodically
255. 10:15test the connection to
256. 10:16the broadband cloud and back to the
257. 10:20corporate office to determine the
258. 10:21latency
259. 10:22jitter and packet loss experienced at
260. 10:25any time
261. 10:26this solution supports advanced
262. 10:28applications such as
263. 10:30voice and video as part of the full suit
264. 10:33of enterprise services for the end
265. 10:36user for example a teleworker can access
266. 10:40a central
267. 10:41office ip telephone system from home
268. 10:44with comparable voice quality and can
269. 10:47derby
270. 10:49take advantage of a higher function ip
271. 10:51telephony
272. 10:52capabilities instead of using the pstn
273. 10:55so an alternative solution is an
274. 10:58unmanaged
275. 10:59vpn approach in which the end user
276. 11:01implements a software vpn from a pc
277. 11:04across a generic broadband router access
278. 11:07point and hub appliances
279. 11:10this solution typically cannot support
280. 11:12the level of feature
281. 11:13integration the quality of service
282. 11:16the managed support needed to reliably
283. 11:19deliver the voice
284. 11:21video multimedia and traditional data to
285. 11:24the end user
286. 11:25but it might be appropriate for
287. 11:27occasional remote users
288. 11:29with lighter application requirements
289. 11:33designing the enterprise one summary
290. 11:37so the cisco enterprise branch
291. 11:38architecture provides
292. 11:40enterprise services to remote users
293. 11:44you should characterize each branch
294. 11:46location to develop a suitable design
295. 11:49so a small branch office design
296. 11:51typically uses a single one access
297. 11:53router
298. 11:54with one or two access switches to
299. 11:56support up to 50 users
300. 11:59medium branch office design typically
301. 12:01uses two one access routers
302. 12:04with multiple access switches to support
303. 12:06up to 100 users
304. 12:09branch office design typically uses two
305. 12:12one access routers
306. 12:14one or more multi-layer distribution
307. 12:16switches
308. 12:17and multiple access switches to support
309. 12:20up to 100 to 1000 users
310. 12:25an enterprise teleworker design can use
311. 12:27a small isr
312. 12:29with integrated switch ports
313. 12:32and an always on vpn to support
314. 12:35one teleworker
315. 12:40designing remote connectivity so remote
316. 12:43connectivity design
317. 12:44review so analyze the network
318. 12:47requirement
319. 12:48so type of applications the traffic
320. 12:52volume and traffic patterns redundancy
321. 12:55and backup
322. 12:56is necessary characterize the existing
323. 12:59networking sites
324. 13:00so technology used the location of hosts
325. 13:04servers terminals and
326. 13:07other endnotes develop
327. 13:10one in branch network design so select a
328. 13:13one
329. 13:14and branch technology to support the
330. 13:16requirements
331. 13:18and select hardware and software
332. 13:19components to support
333. 13:21requirements now to summarize the module
334. 13:26designing remote connectivity
335. 13:29network application and connectivity
336. 13:31requirements influence
337. 13:32one design the cisco enterprise
338. 13:35man and one architecture provides
339. 13:37integrated qos
340. 13:40network security reliability and
341. 13:42manageability
342. 13:44on private ones isp service
343. 13:47through site to site and remote access
344. 13:49vpns
345. 13:50service provider managed ip or mpls vpns
346. 13:55the cisco enterprise branch architecture
347. 13:57supports small
348. 13:59medium large intel worker locations
349. 14:04so this is the end of this video lecture
350. 14:06have a great day
351. 14:08see you on the next video