Cisco Cisco IOS Software Release 12.0(7a) White Paper
the flow for more detailed information about that step.
Solution Requirements
Gathering requirements is the first and most important step in successfully deploying a new network solution.
We'll look at the following necessary steps in gathering requirements:
We'll look at the following necessary steps in gathering requirements:
Required Features or Services
•
Performance Service−Level Agreements and Metrics
•
Solution Scalability Objectives
•
Availability Objectives
•
Interoperability with Existing Environment
•
Solution Comparison
•
Documented Network Design
•
Required Features or Services
Gathering network features or services requires an understanding of applications, basic traffic flows, and user
and site counts. You can use this information to create a logical design and feature set that will help network
architects understand requirements such as bandwidth, interface requirements, connectivity, configuration,
and physical device requirements. This step does not include how you determine performance, manageability,
availability, or interoperability of the network.
and site counts. You can use this information to create a logical design and feature set that will help network
architects understand requirements such as bandwidth, interface requirements, connectivity, configuration,
and physical device requirements. This step does not include how you determine performance, manageability,
availability, or interoperability of the network.
Performance Service−Level Agreements and Metrics
Use performance service−level agreements (SLAs) and metrics to define and measure the performance of new
network solutions to ensure that new solutions meet performance requirements. You can use performance
monitoring tools or a simple ping across the proposed network infrastructure. The performance SLAs should
include the average expected volume of traffic, peak volume of traffic, average response time, and maximum
network solutions to ensure that new solutions meet performance requirements. You can use performance
monitoring tools or a simple ping across the proposed network infrastructure. The performance SLAs should
include the average expected volume of traffic, peak volume of traffic, average response time, and maximum