Agenda

1. Agenda 1. QUIZ 2. PerroyClinic Bidders Conference Follow-up 3. Homework 4. Network Management 5. Network Management Models 6. Network Management in TCP and OSI 7. Remote Site Management

2. Homework Chapter 3, Problems 1, 4, 5 & 14 Chapter 4, Problems 1, 2 (easy way is via IETF) & 14

3. Network Management Network Management Standards SNMP/Internet Industry standard (IETF) Developed for Internet components--adapted to WANs Easy to implement Most widely implemented OSI/CMIP International standard (ISO/OSI) Management of data on LANs & WANs Deals with all 7 layers of the OSI stack Most complete, most structured, most complicated and most resources required to implement it

4. Network Management Network Management Standards Telecommunications Management Network International standard (ITU-T) Developed for telecommunications networks Based on OSI network management framework Addresses network and administrative aspects of management Web-based Management Web-Based Enterprise Management (WBEM) Java Management Extensions (JMX) Institute of Electrical and Electronic Engineers Adopted OSI and deals with first two layers Focused on management of LANs & WANs Internationally accepted

5. Network Management Network Management Information Model Organizational Model Communication Model Functional Model

6. Network Management • Organizational Model: • Describes components of a network management system • Focuses on functions and infrastructure • Objects are network elements such as hubs, bridges, routers, etc. • Managed elements have a process running them called an agent • Manager queries the agent, gets information, processes it and • stores it in the MIB MIB Manager Note: This is a simplified hierarchical set up agent agent Managed Objects Unmanaged Objects

7. Network Management • Information Model: • Deals with structure & organization of management information • Specifies the structure of management information (SMI) • Specifies the management information base (MIB) • SMI defines the syntax and semantics of information stored • MIB is used by the agent and management process to store info • MDB is the real database with measured or administratively • configured data on the elements in the network MIB Manager MDB agent agent Managed Objects Unmanaged Objects

8. Network Management • Communication Model: • Has three components • Management information processes that function in the • application layer • Layer management between the layers • Transport protocol is medium of exchange • Application protocol is the message format • Actual message • Layer operation within layers

9. Network Management Interface Data Unit Interface Control Info Service Data Unit Service Access Point Protocol Data Unit IDU Layer N+1 Interface Layer N ICI SDU SAP ICI SDU Header SDU N-PDU

10. Network Management Do operations, requests, responses, traps and notifications belong in red? Or do they belong in green?

11. Management In The OSI Stack Mgt Appl Process CMISE Mgt Appl Process CMISE ACSE ROSE Presentation Session Transport Network Data Link Physical ACSE ROSE Presentation Session Transport Network Data Link Physical

12. Network Management SNA OSI Internet User Apl Present Svcs Flow Control Xmt Control Path Control Data Link Physical Application Presentation Session Transport Network Data Link Physical Apl Protocol Transport TCP UDP Network

13. Common Mgt. Information Services over TCP/IP (CMOT) Mgt Appl Process CMISE Tough, really tough! ACSE ROSE Lightweight Presentation Protocol (LPP) Session TCP UDP IP Data Link Physical ACSE (Association Control Service Element) handles association establishment & release. ROSE (Remote Operations Service Element) is the application protocol used to access remote systems. LPP is effectively an abbreviated Presentation Layer.

14. Network Management • Network Management is the process of controlling • a complex data network to maximize its • efficiency and productivity. In accordance • with the OSI standard for the functional model • it should include: • Fault Management • Configuration Management • Security Management • Accounting Management • Performance Management

15. Fault Management • Detection and isolation of the problem causing • failure in a network. Fault management can: • monitor the physical or other layers • be self healing • trouble ticket based • a nightmare

16. Performance Management • Measuring Performance-Including but not limited • to: • Throughput • Response time • Percent utilization • Error rates • Availability

17. Configuration Management • Configuration Management consists of the • following steps: • 1. Gather information about current network. • 2. Use that data to modify the configuration • of the network device. • 3. Store the data, maintain an up-to-date • inventory of all network components and • produce carious reports.

18. Configuration Management Data Collection: 1. Manually log on to each device and record the serial number and address assignments in a notebook, spreadsheet ASCII file or database--then manually update with every configuration change. 2. Use autodiscovery to list devices: a. Send a query (e.g., ICMP Echo{ping}) to every address and then collect information using a management protocol. b. Take one device and use the network management protocol to discover all the devices with which it has communicated recently--then query each device similarly

19. Configuration Management Data Storage: Centrally store the notebook, spreadsheet ASCII file or database at the help desk or in the network control center. ASCII DBMS Easy to access Stores data efficiently Easy to read Uses its own format Simple to maintain Can automatically sort stored data Easy to change Can usually restore lost data Fosters analysis of different data

20. Accounting Management • Should track server utilization: • Is a delicate balance • Involves internal and external issues • Is the most political of the management • issues

21. Security Management • The Security Management process includes the • following steps: • Identify the sensitive information. • Find the access points. • Secure the access points. • Maintain the secure access points.

22. Security Management • Locating the access points: • Wires & applications (easy to say hard to do) • Remote Login and File Transfer access points • Services offered by the computer/network • The network management system

23. Security Management • Securing the access points: • Physical & Data Link Levels--Encryption • Network Level--packet filters • Application Level--host authentication, user • authentication and key authentication • Popular Level--Firewalls & VPNs

24. Remote Site Management • Review your systems and infrastructure • Develop a roadmap • Where you want your remote support to be • Likely obstacles • Remote systems to be used • Remote tools to be used Note 1: Unless you’re a start-up, you’ve probably inherited an infrastructure and systems built on top of it.) Note 2: Do it right (attention to detail) the first time. Note 3: Require cross functional teams for system review and selection.

25. Remote Site Management • Review your systems and infrastructure • Develop a roadmap • Where you want your remote support to be • Likely obstacles • Remote systems to be used • Remote tools to be used Note 1: Unless you’re a start-up, you’ve probably inherited an infrastructure and systems built on top of it.) Note 2: Do it right (attention to detail) the first time. Note 3: Require cross functional teams for system review and selection.

26. Remote Site Management • “Can remote management be established?” is not one question, it’s three questions: • How much money can we spend? • Initially • On a continuing basis • What equipment and people will be made available? • For installations • For continuing management • For maintenance & repair • How much time do we have to deliver? Note: Things are seldom as economical as they appear to be.

27. Remote Site Management • The most significant issue will just about always be people & skill sets required: • Geographical location & time zones: can a centralized support group cover the distance and time of day variations? • Language differences: do any exist? • Business requirements: how best to meet special business unit needs, e.g., on-site printer support? • Standardization: are corporate and industry standards defined and followed? Are multi protocol environments necessary? • Convergence: are data and voice groups integrated? • Architecture: Simplify whenever possible. • Do you need redundancy in critical components? • Will you define new applications & support them or get ones that fit into existing systems.

28. Remote Site Management • The most significant cost will generally always be long haul communications services • Many newcomers think a VPN is all you need. • You need a business analysis that determines • Required throughput • Required speed of service (maximum latency) • Required availability • You need a service level agreement (SLA) that guarantees the above.

29. Remote Site Management Remote Branch Steps to Success • Gather requirements from current systems and infrastructure. • Communicate with business units to determine their requirements, loads and future enhancements. • Factor in technology enhancements and loads. • Review geographic locations with vendors and suppliers to determine available technologies. • Analyze the data and formulate a plan & road map detailing corporate systems migrations, obsolescence and enhancements. • Implement standards if you do not already have them. • Document, distribute, communicate and adhere to policies and procedures. • Include remote-site support reviews in every IT functional area decision. • Plan, review, plan, monitor, plan project, plan execute and plan some more to keep abreast. • Go back to number 1.