High Level Design TemplateVersion 3.0

Prerequisites:The successful completion and validation of the Solution Requirements Document and subsequent Pre-Design Closeout Analysis are required prior to proceeding with this document. It is recommended that you utilize both Solutions Expert and your assigned AM/SE while developing the high level design.

Solutions Expert: http://apps.cisco.com/sx/introduction.sx?actionParam=viewIntroduction

Document Instructions: The below content is formatted using Styles: 1. Header One, 2. Text and 3. Bulleted information. “Fields” are used in the following manner:

o TOC - Update the Table of Contents by right clicking in TOC and choosing “Update Field”, “Update Entire Table”.

o “Title” and “SaveDate”– contained in the footer of the document. The “Title” is located in File, properties – change to match asset that is being created. Revised date is the “SaveDate” field. To update either field: switch to view header/footer mode; right click field, choose update.

Where applicable replace <Partner Logo> with your logo graphic, otherwise delete that reference. This header page should be deleted; it is intended to provide instructional value only. Note: Text in Red provides the partner with instruction for the respective section of the Template. This instruction

should be removed and replaced with partner, customer, and Solution-specific information customized to the particular engagement opportunity.

Document Owner: The recommended owner of this document is partner “Sales Engineer”.

Version ControlThis document will be kept current on the Lifecycle Services Web site. It is recommended that rather than archiving this document, you download it each time you need it.

Document Owner(s) Version Number Date Nature of Update

Changes are logged in the revision history at the end of the document. A minor update involves minor corrections or adjustments to language. A major

update involves the introduction of new content, or a significant substantive change to existing content.

Document History

Version Release Date

Description of Change

TM

Core Network Services (CNS)

High Level Design

Version 3.0

<Customer Name><Insert Partner Logo>

<Partner Address>

<Partner Website>

CiscoCorporate Headquarters170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

00 553-NETS (6387)Fax: 408 526-4100

Service Practice Templates for Partners

TM

TM

3

<Partner Logo>

Table of Contents

Legal Disclaimer 4

Document Overview 5

Technical Solution Overview 6

Data Gathering 6

Example: 6

Logical Solution Design 7

Bill of Materials 10

3rd Party Elements 11

Professional Services 12

Solution Assumptions 13

OSPF Specific 13

EIGRP Specific 13

Switch Specific 14

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

4

<Partner Logo>

Legal Disclaimer

The Templates that accompany this Terms of Use document may be used by a Cisco-authorized reseller solely in connection with reseller’s activities to promote and sell Cisco services. Reseller’s use of such Templates is subject the reseller’s systems integrator agreement or indirect channel partner agreement (ICPA), between reseller and Cisco.

Cisco owns and shall continue to own all right, title and interest in and to the Templates. Reseller may modify the templates to suit particular business opportunities; however, Cisco assumes no responsibility for the accuracy of the information in the Templates or of any modifications made by reseller to such templates. Cisco reserves the right to change the programs or products covered by the Templates at any time without notice. Mention of non-Cisco products or services is for information purposes only and constitutes neither an endorsement nor a recommendation.

ALL TEMPLATES ARE PROVIDED "AS IS" WITH ALL FAULTS AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. CISCO AND ITS SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO’S LIABILITY WITH REPSECT TO THE TEMPLATES EXCEED THE AMOUNTS PAID FOR THE TEMPLATES BY YOU. CISCO AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR REVENUES WHETHER ARISING IN CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE.

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

5

<Partner Logo>

Document Overview

This document is intended to assist the partner in the creation of a high-level, conceptual CNS design that addresses business and technical needs and creates the foundation for solution deployment. As the partner you will migrate through the Lifecycle Services process leading up to a full understanding of your customer’s business and technological requirements. This high-level design should include generating a logical topology map and the identification of preliminary products and services. In this exercise you will include specifications for availability, capacity, and security to meet the customer’s service requirements.

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

6

<Partner Logo>

Technical Solution Overview

Data Gathering Current physical and logical topology of the corporate Internet module

Up to date configurations for the Cisco security devices deployed

Information on Cisco software running on these devices

Network management deployed for corporate Internet module

WWW, DNS, SMTP, FTP etc. services deployment details including host specific information such as OS, Applications

Content network filtering deployment

Details of corporate Internet module connectivity to other parts of the corporate network

Details on ISP connectivity

<The partner should use this section to summarize, in a high level, the technical solution strategy aligning the solution with the underlying business drivers.>

Example:

<Customer X> is experiencing significant business growth and seeks to expand nationwide within the next 12 months. CNS is becoming paramount as these sites will have access to important company data. They have engaged <Partner> to design and propose a CNS solution that:

Is adaptable to support their near term and long term growth yet maintaining available, stable network.

Will secure multiple, geographically dispersed locations.

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

7

<Partner Logo>

Logical Solution Design

<Based on the specific requirements gathered and validated in the Solutions Requirements Document, the partner should create and insert a high-level Visio diagram providing a complete logical solution design. It is recommended that you utilize Solutions Expert to generate the deliverable for this section.

Routing algorithms often have one or more of the following design goals:

Optimality

Optimality refers to the capability of the routing algorithm to select the best route, which depends on the metrics and metric weightings used to make the calculation. For example, one routing algorithm may use a number of hops and delays, but it may weigh delay more heavily in the calculation. Naturally, routing protocols must define their metric calculation algorithms strictly.

Simplicity

Routing algorithms also are designed to be as simple as possible. In other words, the routing algorithm must offer its functionality efficiently, with a minimum of software and utilization overhead. Efficiency is particularly important when the software implementing the routing algorithm must run on a computer with limited physical resources.

Robustness and Stability

Routing algorithms must be robust, which means that they should perform correctly in the face of unusual or unforeseen circumstances, such as hardware failures, high load conditions, and incorrect implementations. Because routers are located at network junction points, they can cause considerable problems when they fail. The best routing algorithms are often those that have withstood the test of time and that have proven stable under a variety of network conditions.

Rapid convergence

In addition, routing algorithms must converge rapidly. Convergence is the process of agreement, by all routers, on optimal routes. When a network event causes routes to either go down or become available, routers distribute routing update messages that permeate networks, stimulating recalculation of optimal routes and eventually causing all routers to agree on these routes. Routing algorithms that converge slowly can cause routing loops or network outages.

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

8

<Partner Logo>

Flexibility

Routing algorithms should also be flexible, which means that they should quickly and accurately adapt to a variety of network circumstances. Assume, for example, that a network segment has gone down. As many routing algorithms become aware of the problem, they will quickly select the next-best path for all routes normally using that segment. Routing algorithms can be programmed to adapt to changes in network bandwidth, router queue size, and network delay, among other variables.

Algorithm Types

Routing algorithms can be classified by type. Key differentiators include these:

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

9

<Partner Logo>

Static versus dynamic

Single-path versus multipath

Flat versus hierarchical

Host-intelligent versus router-intelligent

Intradomain versus interdomain

Link-state versus distance vector

Figure 1 Diagram

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

10

<Partner Logo>

Bill of Materials

<Based on the specific requirements gathered and validated in the Solutions Requirements Document, the partner should create and insert a Bill of Materials for each of the required Cisco Solution elements. The Bill of Materials should include all applicable Cisco hardware and software components as well as the applicable Smartnet services (unless the partner provides their own commensurate maintenance services) required to ensure customer satisfaction. It is recommended that you utilize Solutions Expert to generate the deliverable for this section.>

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

11

<Partner Logo>

3rd Party Elements

<Based on the specific requirements gathered and validated in the Solutions Requirements Document, the partner should insert the details of any required 3rd Party Elements such as call recording, call accounting, overhead paging, custom ISV integration, or CRM applications. It is recommended that the partner demonstrate their ‘value-add’ by providing the customer with an ‘end-to-end’ solution document and subsequent business case. Such 3rd Party Elements should include 3rd Party professional services for implementation and integration as well as the appropriate 3rd Party maintenance and ongoing support coverage.>

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

12

<Partner Logo>

Professional Services

<Based on the specific requirements gathered and validated in the Solutions Requirements Document, as well as the partner’s methodology for solution design, implementation, and ongoing support, the partner should provide an overview of their Professional Services and detail a breakdown of their services associated with providing the proposed solution. This is often the partner’s specific ‘value-add’ and the basis for their own competitive differentiation.>

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

13

<Partner Logo>

Solution Assumptions

<Based on the specific requirements gathered and validated in the Solutions Requirements Document, the partner should document any assumptions made when determining the solution strategy and overall design. Such assumptions should be validated with the customer and, if not addressed prior to the Business Case submission, will provide for a ‘safety net’ in the event a portion of the solution does not fully address a customer requirement. In many instances, the customer will direct the partner to make an assumption for the sake of budgetary pricing or a present unknown circumstance. It is recommended that all assumption be documented in this section, in the Business Case, when prepared, scope of work, statements of work, and in other applicable documents where the solution is presented or discussed.>

OSPF SpecificThe maximum number of routers per area depends on several factors, including the following:

What kind of area do you have?

What kind of CPU power do you have in that area?

What kind of media?

Will you be running OSPF in NBMA mode?

Is your NBMA network meshed?

Do you have a lot of external LSAs in the network?

Are other areas well summarized?

EIGRP Specific Advertise only remote networks to the core.

Use Distribute- list or EIGRP Stub routing feature to prevent remote office routers to advertise back to a core router, the routes learned from another core router, thus preventing the remote office to be used as a transit path for core routers.

If the interface bandwidth configuration cannot be changed because of routing policy considerations, or for any other reason, the bandwidth-percent command should be used to control the EIGRP bandwidth, corresponding to the actual interface/PVC bandwidth.

On T1 or slower, low-speed interfaces, raising the available bandwidth for EIGRP above the default of 50 percent is advisable in order to improve convergence.

The passive-interface default1 command is recommended on the routers with specific “no passive-interface” commands corresponding to the interfaces

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

14

<Partner Logo>

where EIGRP needs to pursue neighbor relationship. This is strongly recommended on a switched LAN environment.

The Cisco IOS® neighbor command should be used with caution, after understanding the EIGRP Neighbor discovery and maintenance mechanism.

Switch Specific Do not disable Spantree

Ensure you have configured Root and Secondary. This is important in case of spanning tree outage.

Enable Backbonefast. This helps with eliminating MaxAge Time.

Enable Uplinkfast only on edge switches that are not used as transit devices by other switches.

Enable UDLD to help reduce STP outage.

March 2008

Company Confidential. A printed copy of this document is considered uncontrolled.

TM

<Partner Logo>