ITM 600 Study Guide - Final Guide: Network Planning And Design, Network Performance, Protocol Analyzer

• School: Ryerson University
• Department: Information Technology Management
• Course: ITM 600
• Professor: Christopher West

Document Summary

Chapter 1: (cid:862)co(cid:374)(cid:374)e(cid:272)t-the-dots(cid:863) desig(cid:374) skips the steps of a(cid:374)al(cid:455)zi(cid:374)g a (cid:272)usto(cid:373)e(cid:396)(cid:859)s (cid:396)e(cid:395)ui(cid:396)e(cid:373)e(cid:374)ts, good (cid:374)et(cid:449)o(cid:396)k desig(cid:374) (cid:373)ust (cid:396)e(cid:272)og(cid:374)ize that a (cid:272)usto(cid:373)e(cid:396)(cid:859)s requirements embody many business and technical goals, including requirements for availability, scalability, affordability, An enterprise network is also called an internetwork: 1 = extremely critical, 2 = somewhat critical, 3 = not critical, business constraints: budget, staffing, schedule, politics and. Network should not fail more often than once every 4000 hours: mttr goal is 1 hour. This will help you determine what changes need to be made to meet performance goals: network performance goals are tightly linked to. Pps: wire speed = internetworking devices can forward packets at the theoretical max, some networking vendors refer to. Fcaps acronym to help with network management functions: fault management = detecting, isolating, and correcting problems. Controlling, operating, identifying, and collecting data from managed devices: accounting management =