Designing Network Management Services © 2004 Cisco Systems, Inc. All rights reserved. Designing the Network Management Architecture ARCH v1.24-1

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Network Management Infrastructure Considerations Is a single network management station or are multiple management stations required? Is it best to have a centralized or distributed deployment of network management stations? Is a hierarchical design required to mirror the network infrastructure? Does network management require a dedicated network or can it be part of the campus network? Which management tools are required: element management tools or end-to-end policy-based tools? How do NAT and firewalls affect the network management strategy?

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Network Management Data Collection and Management Considerations Is polling required or will the solution be event-driven? What data should be collected? How long should the data be stored? How much bandwidth is required to support data collection, particularly across low-bandwidth WAN links? What issues regarding management protocols such as SNMP and RMON should you address? What issues regarding access protocols such as HTTP and Telnet should you address? Is out-of-band management or in-band management required?

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Network Management Station Sizing Considerations Determine the number of managed devices. Determine which operating systems are used in the enterprise (Windows NT or Solaris). Select the appropriate CPU type and speed. Consider the amount of RAM and swap space required for polling. Consider the amount of hard disk space required for polling data and reporting data.

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v System Management Resource Considerations Management systems –Servers –Agents –Monitors Bandwidth and connectivity Staffing

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Single-Server Deployment

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Multiserver, Split Applications Single Management Domain

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Multiple Management Domains

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Centralized WAN Management with Local LAN Management

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Key Questions to Consider How many network management servers are needed? What specific bundles and products will be deployed? What components and functions of the products are most important to the network managers? What other management tools will be present? Will any other applications be installed on a CiscoWorks network management server, for example? How many users will the network management tools have? How many of them will use the tools simultaneously? In the case of very large networks, what are the administrative groupings of the network devices and network management users? Is a separate network required for network management?

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Small Site Network Management Design Single system with CiscoWorks LMS and RWAN solutions Single instance of Resource Manager Essentials

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Medium Site Network Management Design Two servers with LMS and RWAN components Single instance of Resource Manager Essentials

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Example: Medium Site Network Management Design

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Large Site Network Management Design Design includes four servers with LAN and WAN management components. Consider dividing the enterprise into different domains with independent systems to manage each domain.

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Example: Large Site Network Management Design

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Summary Network management must be an integral part of the overall network design, since network management can adversely affect network performance. For networks that require more than a single workstation or server, you may need to use multiple workstations for a single management domain (a single managed network) by distributing applications across multiple workstations. The result will be better performance and maximum scaling. When designing a small or large network management solution, you will consider number of management stations, functionality requirements, resource utilization, and many other factors.

© 2004 Cisco Systems, Inc. All rights reserved. ARCH v Learning Activities Case Study: OCSIC Bottling Company Develop a network management strategy for the company Provide justification for each design decision