Design Life Cycle — Transcript

Full transcript

1. 0:04hi hello there
2. 0:05welcome to design life cycle
3. 0:10on this video lecture we are going to
4. 0:12cover
5. 0:13business driven network next would be
6. 0:16the pbm
7. 0:17network lifecycle approach or the plan
8. 0:20build and manage approach and
9. 0:24what are the project deliverables let's
10. 0:27get started business driven network
11. 0:34so designing a network can be compared
12. 0:36to designing a building
13. 0:37so before designing a building an
14. 0:40architect has to consider many factors
15. 0:43like how will the building be used
16. 0:46would it be for commercial or
17. 0:48residential
18. 0:51what are the needs of the people using
19. 0:52this building
20. 0:54so basically in a building we need
21. 0:57electricity
22. 0:59we need water supply telecommunications
23. 1:02and
24. 1:02others are there any special requirement
25. 1:06well if it is a building we have to
26. 1:08consider the organization
27. 1:11okay so similarly a network engineer has
28. 1:15to consider factors such as
29. 1:17which business functions the network
30. 1:19will support
31. 1:22if we are going to consider for instance
32. 1:23a university
33. 1:25so we have to consider having a learning
34. 1:27management system
35. 1:29or lms the enrollment system might be
36. 1:32running over the infrastructure
37. 1:34payment and other services
38. 1:37the various types of users who will
39. 1:40access the network
40. 1:41again if it is in a university setup we
41. 1:44have to consider the students
42. 1:47the faculty personnel and
43. 1:50guests who might be using the network
44. 1:53and how the network will affect by
45. 1:56future growth
46. 1:59so we have to consider the number of
47. 2:01users in the future
48. 2:03the growth of user means
49. 2:06we need a higher bandwidth to consider
50. 2:08on the network infrastructure
51. 2:13so business driven network is a network
52. 2:15design
53. 2:16leaning towards the organization's
54. 2:18business objectives
55. 2:20as a network architect you have to rely
56. 2:23on business needs
57. 2:24when choosing the best technologies and
58. 2:26design patterns
59. 2:28for your network you have to consider
60. 2:32how the technology that you will choose
61. 2:35will affect the business in the future
62. 2:38if you want to build a network that
63. 2:40serves as a business enabler
64. 2:43not a cost center you must gather
65. 2:45accurate
66. 2:46business requirements and information
67. 2:48from the customer
68. 2:51[Music]
69. 2:53so first we need to understand the
70. 2:55company
71. 2:57a good way to start gathering
72. 2:59information is to understand the company
73. 3:02so here are the few questions that you
74. 3:04could ask
75. 3:05okay so that you might want to start
76. 3:07with first
77. 3:09you have to ask how big is the network
78. 3:12is it a lan is it a one will it cover
79. 3:16a geographical network will it connect
80. 3:20network from different cities different
81. 3:22country
82. 3:23okay so you have to know that you have
83. 3:25to know the size of the network
84. 3:28also how many users are connected
85. 3:32okay how many devices per user will be
86. 3:34considered
87. 3:36and where are the users located
88. 3:39so all of this should be gathered before
89. 3:42designing a network
90. 3:44and all of this should be considered
91. 3:46before designing a network
92. 3:50next is we have to know the end users
93. 3:54so who are the end users of the network
94. 3:57infrastructure
95. 3:58so when you think about the users who
96. 4:00will access the network
97. 4:02you have to consider internal external
98. 4:06and guest users you must also understand
99. 4:10the end points as well as
100. 4:11the people so here are some of the few
101. 4:14questions that you could ask
102. 4:17so are the end points static or mobile
103. 4:20so we're we're talking about the
104. 4:23computers or the workstations
105. 4:25okay so is it fixed or are we going to
106. 4:29consider mobility
107. 4:30okay which computing environments
108. 4:34are the users accustomed to
109. 4:37are the users willing to adapt to
110. 4:39changes
111. 4:40so this has been a challenge for a
112. 4:43network
113. 4:43uh engineers and network managers
114. 4:47do the users travel a lot so we are
115. 4:50thinking of the mobility of the users
116. 4:53so there might be some roaming users in
117. 4:55the organization
118. 4:58so which types of communications are
119. 5:00used
120. 5:01within the company and which are used
121. 5:04for external partners
122. 5:10next is you have to consider the
123. 5:12technological aspects of the company
124. 5:15okay so which are another major
125. 5:17influence on the network design
126. 5:19so here are some of the questions that
127. 5:22you could ask or you should explore
128. 5:24so which applications are in use
129. 5:28at the company are there any existing
130. 5:31problems
131. 5:33with any of the applications that is
132. 5:36being used
133. 5:37or how many data or how much data
134. 5:41does the network produce okay
135. 5:44so are there any special requirements
136. 5:46regarding the data path
137. 5:49so again in considering the business
138. 5:51driven network
139. 5:52we have to consider all of these
140. 5:54components here you have to know the
141. 5:56company
142. 5:57company overview you have to know the
143. 5:59goals
144. 6:00competitors changes in the market
145. 6:04you also have to know the company's
146. 6:06network
147. 6:07okay so the current operations of the
148. 6:10network
149. 6:11including the size the number of users
150. 6:13number of devices
151. 6:15the applications being used on the
152. 6:17network
153. 6:18okay so the problems encountered in the
154. 6:20network all of those should be
155. 6:22considered
156. 6:23in network design also
157. 6:26you have to know your users so internal
158. 6:29users external users
159. 6:32guests endpoints and people should be
160. 6:35considered on the network design
161. 6:37and when designing a network we should
162. 6:39not design a network based on today's
163. 6:42needs you have to consider at all costs
164. 6:46okay so the future expansion of the
165. 6:49network
166. 6:54pbm network life cycle approach
167. 6:58pbm stands for plan build and
168. 7:01manage this is one of the cisco's life
169. 7:05cycle model
170. 7:06which was created as a simplified way to
171. 7:09engage customers
172. 7:10on their projects so the ppdio
173. 7:15or the prepare plan design
174. 7:18implement operate and optimize spaces
175. 7:22are still relevant but they map to three
176. 7:25simple pieces so it has been simplified
177. 7:27with plan build and manage or
178. 7:31epm so this is easier for customer
179. 7:35engagement
180. 7:36so different teams companies or
181. 7:39consultants
182. 7:40can even handle different sections of
183. 7:43the project for
184. 7:44example consultant a is designing the
185. 7:47solution
186. 7:49so this is the plan section
187. 7:52internal id is implementing the solution
188. 7:55so that is a build section
189. 7:58okay and a managed services team
190. 8:01operates the solution
191. 8:03so that is a managed section
192. 8:09okay so the pbm network lifecycle
193. 8:11approach reflects the life cycle basis
194. 8:14of the standard network
195. 8:16so the model consists of three phases as
196. 8:19mentioned earlier
197. 8:21okay so the plan build and manage
198. 8:25let's focus on the plan okay
199. 8:28so the plan section includes strategy
200. 8:31and analysis
201. 8:32assessment of the current network you
202. 8:34have to know the current situation
203. 8:36the current operations of the
204. 8:38organization
205. 8:40including the current setup and
206. 8:42designing
207. 8:44of the revised network
208. 8:47so under planning strong planning is
209. 8:50critical
210. 8:50in order to deliver the specific
211. 8:52outcomes that you need
212. 8:54the plan pace involves setting
213. 8:57expectations correctly
214. 8:59developing an architectural strategy
215. 9:02building the transformational roadmap
216. 9:04and design
217. 9:06and defining a plan
218. 9:09for tracking results and impacts
219. 9:15so the next one is build
220. 9:18so the build section employs deployment
221. 9:21of the network or new network design
222. 9:25migration of the new network and
223. 9:28validation
224. 9:28of the new network so with build
225. 9:32after you design the network
226. 9:35and after the design has been approved
227. 9:38the implementation of the network begins
228. 9:41so the network is built or extra
229. 9:43components are incorporated
230. 9:45according to the design specification
231. 9:48the goal is to integrate
232. 9:50devices into different network
233. 9:53components
234. 9:54or shall we say the existing network
235. 9:56with a minimal disruption
236. 9:59so after the deployment you will perform
237. 10:03a series of operational tests
238. 10:05to validate the design that is under
239. 10:08the build base
240. 10:12so the last one would be the manage
241. 10:13space
242. 10:15okay so the manage section includes
243. 10:18product support
244. 10:19solution optimization and operations
245. 10:22management
246. 10:23so once your network is built you must
247. 10:26maintain an operational excellence
248. 10:28and efficiency maintenance involves
249. 10:31proactive
250. 10:32management of the network so that you
251. 10:35can identify
252. 10:37and resolve issues before they affect
253. 10:40the organization
254. 10:42so maintenance also involves fine-tuning
255. 10:46your infrastructure and applications
256. 10:49on an ongoing basis to maximize the
257. 10:52network performance
258. 10:56now let's get into the details of each
259. 11:00of this pieces here so the first step
260. 11:04was planning okay so strategy and
261. 11:08analysis
262. 11:09identifying the company business
263. 11:11requirements and technology strategy
264. 11:14so the first step of the plan phase is
265. 11:17to identify the company business
266. 11:18requirements
267. 11:20and the technology strategy
268. 11:23so you must review the current business
269. 11:25conditions
270. 11:26and make sure that the new requirements
271. 11:29and technologies
272. 11:30fit into the existing state so strategic
273. 11:34analysis
274. 11:35is a process that involves researching
275. 11:38an
276. 11:38organization's business environment
277. 11:41within which it operates you also have
278. 11:45strategic analysis
279. 11:47okay so which is essential to formulate
280. 11:49strategic planning
281. 11:50for decision making and smooth working
282. 11:54of that organization
283. 12:00so the next one is assessment
284. 12:03so the next step is to assess the
285. 12:05current state
286. 12:06and if necessary help project managers
287. 12:09to create
288. 12:10a project plan so the need for a project
289. 12:13plan
290. 12:14depends on whether there is an existing
291. 12:16network
292. 12:17so if there is an existing network you
293. 12:20will have to audit the existing
294. 12:22infrastructure and
295. 12:23operational environment now auditing
296. 12:27ensures
297. 12:28that the changes you make will not
298. 12:30adversely impact the network usability
299. 12:33helping you avoid costly delays
300. 12:37so assessment means assessing the
301. 12:39current state of the organization
302. 12:44the third step in the plan phase is to
303. 12:47develop or update the comprehensive
304. 12:48network design
305. 12:50so the design should meet all the
306. 12:52business requirements
307. 12:53that were gathered in the strategy and
308. 12:56analysis spaces
309. 12:58so design includes developing or
310. 13:00upgrading a comprehensive network design
311. 13:05let's get into the details of the build
312. 13:07phase
313. 13:09let's start with the validation process
314. 13:12the validation process helps you to
315. 13:14confirm that the solution
316. 13:16meets customers requirements
317. 13:20the deployment process helps you to
318. 13:23successfully deploy
319. 13:25new network solutions
320. 13:28and the migration process accelerates
321. 13:31new deployments
322. 13:32and helps you to control costs improve
323. 13:36operational excellence and mitigate
324. 13:38risks
325. 13:40when refreshing your network
326. 13:44so with a build phase
327. 13:48you can use many different
328. 13:49implementation methods
329. 13:51so regardless of which method that you
330. 13:53choose
331. 13:54it is always good to set up a test
332. 13:58environment
333. 13:59that you will use to simulate different
334. 14:01network designs
335. 14:03so using test environment gives you the
336. 14:05ability to find
337. 14:07any potential problems which can be
338. 14:10resolved
339. 14:11before the real implementation so once
340. 14:14you have tested
341. 14:15the network design the real
342. 14:17implementation
343. 14:18can take place so depending on the size
344. 14:21of the implementation
345. 14:23you may run into some logistical
346. 14:25problems like deployment
347. 14:28configuration testing and so on
348. 14:32so after the network is built you should
349. 14:35run a series of
350. 14:36verification tests to confirm that the
351. 14:39network is operating as expected
352. 14:42so if there is a problem you should fix
353. 14:44it
354. 14:45as soon as possible one of the quickest
355. 14:48ways to fix an operational issue
356. 14:51is to roll the network back to a working
357. 14:56state
358. 14:58next would be the manage space so the
359. 15:02product support process
360. 15:04offers automated network equipment
361. 15:07inventory management
362. 15:10next would be the solution support
363. 15:12process
364. 15:13which provides uh priority access to
365. 15:16dedicated resources
366. 15:18to manage and troubleshoot issues within
367. 15:21the network
368. 15:23next would be optimization process the
369. 15:26optimization process
370. 15:28helps you optimize your network
371. 15:30infrastructure
372. 15:31and applications and
373. 15:34operational management processes the
374. 15:37operations
375. 15:38management process simplifies network
376. 15:41and i.t operation with proactive
377. 15:44monitoring
378. 15:45and management of your network
379. 15:49so during the space the company manages
380. 15:52the network
381. 15:53which includes proactive and reactive
382. 15:56monitoring
383. 15:57as well as security management so minor
384. 16:01moves
385. 16:02ads or changes can occur during this
386. 16:06phase as part of the optimization of the
387. 16:08network
388. 16:10so optimization is normally the result
389. 16:13of a change in business or
390. 16:16technical requirements
391. 16:20now if you are going to map the pbm
392. 16:24with the ppg io as shown here below
393. 16:28each section still maps to ppdio
394. 16:32the themes in each pbm pace can refer to
395. 16:35their relevant
396. 16:36pgio tasks like
397. 16:39for planning so that includes
398. 16:42preparation
399. 16:43plan and design okay you've got the ppd
400. 16:47there
401. 16:48and then for build you've got
402. 16:50implementation and deployment
403. 16:53okay for manage you've got optimize
404. 16:56and operate
405. 17:01project deliverables
406. 17:06you should document every stage of the
407. 17:08network design process
408. 17:10so the following are some of the most
409. 17:12common documents
410. 17:14you've got the hld or the high level
411. 17:16design documents
412. 17:17this includes the bill of materials or
413. 17:21the bom
414. 17:23also you've got the lld or the low level
415. 17:26design document
416. 17:27which includes the network migration
417. 17:30plan
418. 17:31you also have the nip or the network
419. 17:33implementation plan
420. 17:35and the nrfu or the network ready for
421. 17:38use
422. 17:38test plan let's get into the details of
423. 17:42each of these deliverables
424. 17:45high level design the hld
425. 17:49is an overview of the entire network
426. 17:51solution
427. 17:52so one of the most important part of the
428. 17:54hld
429. 17:55is the bill of materials
430. 17:58so it provides the business and
431. 18:00technical requirements of the design
432. 18:03details the new services that can be
433. 18:06provided
434. 18:08and gives an architectural overview
435. 18:11so as mentioned here one of the most
436. 18:14important part
437. 18:15of the hld is the bill of materials
438. 18:19bom is a comprehensive inventory of
439. 18:22raw materials assemblies sub-assemblies
440. 18:26parts and components as well as
441. 18:28quantities of each
442. 18:30needed to manufacture a product
443. 18:33in a nutshell it is the complete list
444. 18:36of all the items that are required to
445. 18:39build
446. 18:40a network so the hld serves as a
447. 18:43reference
448. 18:44for both the designer and the
449. 18:47organization or the company
450. 18:52lld or low level design
451. 18:55the basis for the lld is the hld
452. 18:58which is updated with all the intricate
453. 19:01details
454. 19:02required to successfully deploy the
455. 19:04design
456. 19:05so it includes network topology and
457. 19:08hardware platforms
458. 19:10hardware and software protocols and
459. 19:12functions
460. 19:14addressing and routing strategy
461. 19:17scalability and redundancy security
462. 19:20considerations
463. 19:21vlans and so on so if there is a
464. 19:24migration plan
465. 19:26the nmp is also part of the
466. 19:30lld so nmp or the network migration plan
467. 19:35is a base requirement for successful
468. 19:37migration plan
469. 19:39is that of shared responsibilities
470. 19:42between the network team
471. 19:44or engineering team and the service
472. 19:46delivery function to arrive
473. 19:48at a collective decision on inventory
474. 19:51customer expectations and network
475. 19:54requirements
476. 19:55so doing so arrest snags cost due to
477. 19:58inventory mismatches readiness to make
478. 20:02alterations to the network
479. 20:05meeting customer expectations and
480. 20:07inventory management
481. 20:09so they typically lead to post migration
482. 20:12hiccups like service outage issues
483. 20:14unmet requests for upgrade and downgrade
484. 20:19missing deadline set by the customers
485. 20:21and lack of services uranus support
486. 20:23to the customer so if this is just
487. 20:26persists
488. 20:27the account teams are disabled from
489. 20:29staying updated
490. 20:30on the status of their customers on the
491. 20:33network
492. 20:34so for example the number of active
493. 20:37services
494. 20:38bandwidth of services and whether or not
495. 20:40the collections teams
496. 20:43is lockstep with services provided
497. 20:51migration plan testing so one of the
498. 20:53most challenging and critical aspects
499. 20:56of networking project is the migration
500. 20:58of users and services
501. 21:00to a new network infrastructure so even
502. 21:03the best network designs
503. 21:05are distinct for failures if they cannot
504. 21:08be implemented without causing extended
505. 21:10service outages
506. 21:11yet despite the risks many network
507. 21:14architects spends
508. 21:16a disproportionate amount of time
509. 21:19focused on the end state
510. 21:22of their network designs developing
511. 21:24migration plans
512. 21:25as an afterthought if at all
513. 21:29so a good migration plan should address
514. 21:32how routing protocols and applications
515. 21:35will interact
516. 21:36with a network that is partially
517. 21:38migrated
518. 21:40so providing success indicators and back
519. 21:42out plan
520. 21:44when unexpected behavior is encountered
521. 21:46during the migration
522. 21:49so testing of a migration plan is an
523. 21:51essential part of the design process
524. 21:54for networking projects of any scale
525. 21:57so it is sometimes a requirement for
526. 21:59implementation or operation groups
527. 22:02responsible for making changes to the
528. 22:04network
529. 22:06so in some instances a migration plan
530. 22:10can be developed during a design
531. 22:11verification lab test
532. 22:13effort by repeating the baseline and
533. 22:16performance test
534. 22:17on the interim topology consisting of
535. 22:20the old
536. 22:21and the new network
537. 22:24so a high-level migration plan
538. 22:27um tests the network backbone
539. 22:31that might look like this okay so we
540. 22:34have several steps
541. 22:35actually we have eight here okay so the
542. 22:38first one would be
543. 22:40build a prototype of the old and the new
544. 22:43network backbone topologies
545. 22:46second you have to run a baseline test
546. 22:49using known traffic patterns from the
547. 22:52existing
548. 22:53and new networks third
549. 22:56physically and logically interconnect
550. 22:58the old and the new network backbone
551. 23:00topologies
552. 23:02as they will be connected during the
553. 23:03migration
554. 23:05if this will take multiple steps each
555. 23:08entering topology should be tested
556. 23:12fourth run the same set of baseline
557. 23:15tests
558. 23:16on the interim network that you run on
559. 23:18the old network
560. 23:20you also have to simulate device and
561. 23:22circuit failure scenarios
562. 23:24in each entry step of the migration in
563. 23:27order to understand the impact
564. 23:29on test traffic and whether any
565. 23:31collateral damage occurs
566. 23:34sex would be disconnect the old person
567. 23:37of the network
568. 23:39or reprovision it on the new backbone
569. 23:43so this should be done the same way as
570. 23:46the migration plan will be done
571. 23:48so if this will be done in multiple
572. 23:50steps in your plan
573. 23:53then you should test each one of them
574. 23:57seventh repeat the set of baseline tests
575. 24:01and last one would be run a set of new
576. 24:05tests
577. 24:06that exercise any new features or
578. 24:08services
579. 24:09to be offered by the new network
580. 24:13so a migration test would be considered
581. 24:16to be successful when the baseline test
582. 24:19results
583. 24:19meter exceeded the performance of the
584. 24:21old network
585. 24:23and the features offered by the new
586. 24:26network are
587. 24:27verified
588. 24:30nip or the network implementation plan
589. 24:33so the network implementation plan
590. 24:35service provides you with
591. 24:36expert project planners who review the
592. 24:39high level design
593. 24:40and detailed design and prepare a
594. 24:43network implementation plan document
595. 24:46that will implement the plan change in
596. 24:48most efficient manner
597. 24:50with a minimum disruption to your
598. 24:52existing services
599. 24:54so the designated consultants will
600. 24:56provide guidance
601. 24:58okay on synchronizing the plan
602. 24:59deliverables into your existing project
603. 25:02plan
604. 25:02in case this network change is part of a
605. 25:05wider project rollout
606. 25:07so leveraging experts from the team will
607. 25:10minimize your risk
608. 25:11and ensuring quality deployment with a
609. 25:13faster turn up
610. 25:15of the new infrastructure elements
611. 25:18network implementation plan review is
612. 25:20also necessary
613. 25:21so having an expert review an existing
614. 25:24network implementation plan document
615. 25:26will definitely help identify any gaps
616. 25:29or risks
617. 25:30that may have not been highlighted so
618. 25:32the network implementation plan review
619. 25:34service
620. 25:35provides this additional level of
621. 25:37diligence
622. 25:38needed to ensure project tasks are
623. 25:40optimally planned
624. 25:42and deliver on the promise with minimum
625. 25:45risks
626. 25:46so after the implementation plan review
627. 25:50the network design validation testing is
628. 25:52also a good practice
629. 25:54so the goal is to identify any
630. 25:56interoperability issues
631. 25:58faster and with proven testing processes
632. 26:00before sending the equipment
633. 26:02to the field sites so you have to do it
634. 26:04remotely or
635. 26:06on site so the network design validation
636. 26:09and testing service
637. 26:10leverage the network implementation plan
638. 26:12to build configure
639. 26:14and test system at any location
640. 26:17okay so based on the document test plans
641. 26:20and laboratory topologies
642. 26:22because you have to simulate it before
643. 26:24you implement it that's a good practice
644. 26:26in network design
645. 26:27okay so the team performs intensive
646. 26:30system-wide and sub-system testing
647. 26:33to proactively identify and make design
648. 26:36modifications if
649. 26:38needed so this team
650. 26:41will generate the test reports okay
651. 26:44documenting the
652. 26:45findings and then the organization can
653. 26:48benefit
654. 26:48immensely from this service that will
655. 26:51enable a plug-and-play
656. 26:52installation at the field sites based on
657. 26:55the detailed system integration
658. 26:58testing documentation provided
659. 27:01so proven best practices shows
660. 27:04that having issues identified saves
661. 27:08customers time and money when it comes
662. 27:10to getting your network solution online
663. 27:16nrfu or network ready for use
664. 27:19test plan so a network ready for use
665. 27:23or the nrfu
666. 27:27on a new greenfield network
667. 27:29infrastructure as a last step
668. 27:31in certifying that it is ready to carry
669. 27:34production traffic
670. 27:36okay so during the nrfu test
671. 27:39network devices are methodically checked
672. 27:43to ensure
673. 27:44that they have been implemented
674. 27:46according to the design
675. 27:47specifications and are running
676. 27:50in an error free state so some of the
677. 27:53tests
678. 27:54that are commonly associated with the
679. 27:57nrfu
680. 27:58includes device tests hardware software
681. 28:02inventory uh power
682. 28:05syslog error okay circuit
683. 28:08tests like throughput delay
684. 28:11jitter errors if there are errors
685. 28:14you also have to perform some sort of
686. 28:16routing tests
687. 28:18adjacencies routing table consistency
688. 28:22okay traffic tests end-to-end traffic
689. 28:25testing
690. 28:27the network service tests like the
691. 28:29multicast
692. 28:30the quality of service one acceleration
693. 28:34okay you also have to perform
694. 28:36application testing
695. 28:38management network management software
696. 28:41and
697. 28:41security tests in some cases
698. 28:46the nrfu testing extends to a limited
699. 28:49production pilot
700. 28:50where a low risk site or portion of the
701. 28:53network is cut
702. 28:55over to the new network and monitored
703. 28:57closely
704. 28:58for a probationary period of time
705. 29:02all right so that's the end of this
706. 29:05video lecture
707. 29:07see you on the next video