Desgn20sg New

7/25/2019 Desgn20sg New

1/649

2007 Cisco Systems, Inc. All rights reserved. DESGN v2.0-1

Designing for CiscoInternetwork Solutions

(DESGN) v2.0

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,for the sole use by Cisco employees for personal study. The files or printed representations may not beused in commercial training, and may not be distributed for purposes other than individual self-study.


2/649


Designing for Cisco Internetwork Solutions v2.0

Course Introduction



3/649


Learner Skills and Knowledge

Prerequisite skills and knowledge

Cisco CCNA certification

Recommended training Introduction to Cisco NetworkTechnologies

Recommended training Interconnecting Cisco NetworkDevices

Building Cisco Multilayer Switched Networks level knowledge ofwireless and QoS topics

Recommended training Building Cisco Multilayer SwitchedNetworks

Practical experience with deploying and operating networksbased on Cisco network devices and Cisco IOS Software



4/649


Designing for Cisco Internetwork Solutions v2.0

To enable learners to gather customer internetworkingrequirements, identify solutions, and design thenetwork infrastructure and services to ensure the

basic functionality of the proposed solutions

Course Goal



5/649


Course Flow

Evaluating SecuritySolutions for the

Network

Applying aMethodology toNetwork Design

Identifying WirelessNetworking

Considerations

Lunch

Designing BasicCampus and DataCenter Networks

Day 1 Day 2 Day 3 Day 4 Day 5

Course

Introduction

A

M

P

M

Designing IPAddressing andSelecting Routing

Protocols

Identifying VoiceNetworking

Considerations

Implementing and

Operating theNetwork

Final CaseStudy

Final CaseStudy

Structuring andModularizing the

Network

Designing RemoteConnectivity



6/649


Cisco Icons and Symbols



7/649


Cisco Icons and Symbols (Cont.)



8/649


Cisco Certifications



9/649


Cisco Career Certifications

Recommended Training Through

Cisco Learning Partners

RequiredExam

Building Cisco Multilayer SwitchedNetworks

640-863DESGN

Designing for CiscoInternetwork Solutions

640-801CCNA

Interconnecting Cisco NetworkDevices

Introduction to Cisco NetworkTechnologies

DESGNCertification for

associate-level recognition in network design

CCDE

CCDP

CCDA

Professional

Associate

Expert

http://www.cisco.com/go/certifications



10/649




11/649


Designing for Cisco Internetwork Solutions (DESGN) v2.0

Applying aMethodology to

Network Design



12/649


Introducing the Cisco Service-Oriented Network Architecture

Applying aMethodology to

Network Design



13/649


Growth of Applications

Data Center

Business-to-Business Links

Branch Offices

Distribution

Extranet

Partners

Field Organizations

RemoteEnvironments

MessageBroker

LegacyApplications

Security

Business-to-Business Gateway

Transformation

EDITelephony

Business

Intelligence

BusinessRules

MobileServices

EventCapture

RFID

ComplianceLogging

DatabaseLookup

LoadBalancing

CustomProtocol

EAI

WebService

Adapters

Standards

Compression

ESB

J2EE

.Net

ASP

MQ Series



14/649


IT Evolution

From Connectivity to Intelligent Systems



15/649


New Business Requirements



16/649


Intelligence in the Network



17/649


Cisco Service-Oriented Network

Architecture Framework

SONA is an architectural framework.

SONA brings several advantages to enterprises:

Outlines how enterprises can evolve toward a more intelligentnetwork

Illustrates how to build integrated systems across a fully

converged intelligent infrastructure

Improves flexibility and increases efficiency



18/649


Cisco SONA Layers



19/649


Overview of Cisco SONA Offerings



20/649


Benefits of SONA

Provides control, performance monitoring, and fault detectionManageability

Provides responsiveness, throughput, and utilization on aper-application basis

Performance

Provides network services with reasonable operational costsand appropriate capital investment

Efficiency

Provides necessary services reliably, anywhere, anytimeAvailability

Supports growth and expansion of organizational tasksScalability

Supports organizational requirementsFunctionality

Description



21/649


Summary

Drivers for a new network architecture include these factors:

Growth of applications IT evolution from connectivity to intelligent systems

Increased business expectations for networks

Ciscos vision of intelligence in the network aligns network andbusiness requirements in three phases:

Phase 1 is integrated transport.

Phase 2 is integrated services.

Phase 3 is integrated applications.

Cisco SONA is the enterprise framework for building intelligence

in the network: Layer 1 is the integrated infrastructure layer.

Layer 2 is the interactive services layer.

Layer 3 is the application layer.



22/649




23/649


Applying a Methodology to Network Design

Identifying DesignRequirements



24/649


PPDIOO Network Life-Cycle Approach



25/649


Benefits of the Life-Cycle Approach



26/649


Design Methodology Under PPDIOO

Three steps in the design methodology:

1. Identify the customer requirements.

2. Characterize the existing network and sites.

3. Design the topology and network solutions.



27/649


Identifying Customer Requirements



28/649


Identifying Planned Applications

Video on demand

Database

Customer support

Web browsing

Groupware

E-mail

CommentsCriticality

(Critical/Important/

Unimportant)

ApplicationApplication Type



29/649


Example: Planned Applications

CriticalIP/TVVideo on demand

All data storage will be basedon Oracle.

CriticalOracleDatabase

CriticalCustomer

applicationsCustomer support

ImportantMicrosoft InternetExplorer, Opera,

NetscapeWeb browsing

We need to be able to sharepresentations and applications

during remote meetings.

ImportantCisco Unified

MeetingPlace

Groupware

ImportantMicrosoft OutlookE-mail

CommentsCriticality

(critical/important/

unimportant)

ApplicationApplication Type



30/649


Identifying Planned Infrastructure

Services

High availability

IP telephony

Mobility

Network management

QoS

Security

CommentsService



31/649


Example: Planned Infrastructure

Services

Eliminate single points of failure and use redundant paths as neededHigh availability

Want to migrate company from regular telephonyIP telephony

Need client laptop guest access along with mobility of employee PCsMobility

Use centralized management tools where appropriate and pointproduct management as required

Network management

Give priority to delay-sensitive voice traffic and other important trafficQoS

Deploy security systematically, including firewalls, intrusion detectionsystems (IOSs), and access control lists (ACLs)

Security

CommentsService



32/649


Identifying Organizational Goals

List future desired servicesList current customer servicesAdd new customer services

Point out possible steps toimprove customer support

List current customer supportImprove customer support

Point out cost-reductionpossibilities

List current expensesReduce costs

Point out possibilities toincrease competitiveness

List competitive organizationsand their abilities

Increase competitiveness

CommentsGathered DataOrganizational Goal



33/649


Example: Organizational Goals

Secure web-based orderingSecure web-based

confirmations

Telephone and fax orders;

telephone and fax confirmation

Add new customer services

Web-based order trackingWeb-based customer

technical support tools

Order tracking and technicalsupport supported by individuals

Improve customer support

Single data-entry pointEasy-to-learn applicationSimple data exchange

Enter data multiple times;time-consuming tasks

Reduce costs

Better productsReduce costs

Corporation Y, Corporation ZIncrease competitiveness

CommentsGathered Data(Existing Situation)

Organizational Goal



34/649


Assessing Organizational Constraints

Use tools for resourceassignment, milestones, critical-path analysis

Specify time frameScheduling

Determine if the organization iswilling to buy equipment fromnew vendor

List preferred standards,protocols, vendors, applications

Policy

Specify the number of networkengineers who have to attend

the additional training

List available personnel andtheir expertise

Personnel

Identify the amount of moneythe organization is willing tospend

Amount of money to spendBudget

CommentsGathered DataOrganizational Constraint



35/649


Example: Organizational Constraints

New applications includevideo conferencing, groupware,and IP telephony

Plans to introduce newapplications in the next ninemonths

Scheduling

Current equipmentCisco;prefers to stay with it

Prefers single vendor andstandardized protocols

Policy

Plans to hire new engineers inthe network department; needtechnical development plan

Engineers with Cisco CCNA

certificates and Cisco CCNP

certificatesPersonnel

Budget can be extended bymaximum $78,000

$650,000Budget

CommentsGathered Data(Existing Situation)

Organizational Constraint



36/649


Identifying Technical Goals

Scalability

100Total

Adaptability

Security

Manageability

Availability

Responsiveness andthroughput

CommentsImportanceTechnical Goals



37/649


Example: Technical Goals

Scalability is critical25Scalability

100Total

10Adaptability

Security for critical data transactions is extremelyimportant

15Security

5Manageability

Should be 99.9 percent25Availability

Important of the central site, less important in branchoffices

20Performance

CommentsImportanceTechnical Goals



38/649


Example: Technical Constraints

Make sure new networkequipment supports IPv6.

IPv6 based applicationsApplication compatibility

Upgrade speeds; consider

another service provider withadditional services to offer.

64-kbps WAN linksBandwidth availability

Replace existing coaxialcabling. Use twisted-pair todesktop and fiber optics foruplinks and in the backbone.

Coaxial cablingExisting wiring

CommentsGathered DataTechnical Constraints



39/649


Summary

The PPDIOO approach reflects the life cycle phases of a standardnetwork.

The design methodology under PPDIOO includes theseprocesses:

Identifying customer requirements

Characterizing the existing network and sites Designing the network topology and solutions

Key steps in identifying customer requirements include these:

Identifying network applications and services

Defining organizational goals and constraints

Defining technical goals and constraints



40/649




41/649



Characterizing theExisting Networkand Sites



42/649


Characterizing the Existing Network

and Sites

Gather documentation and query the organization.

Perform a site and network assessment to help detail the network.

Consider performing traffic analysis on the existing network andapplications.



43/649


Identifying Major Features of the Network

Collect the information about the planned and existing networkinfrastructure:

Site contact information

Network topology such as network devices, physical andlogical links, external connections, encapsulations,bandwidths, IP addressing, routing protocols

Network services such as security, QoS, high availability,IP telephony, storage, and wireless

Network applications such as unified communications andvideo delivery

Collect the information about expected network functionality.

Identify network modules based on the given information.



44/649


Sample Site Contact Questions

What is the site location or name?

What is the site address?

What is the shipping address?

Who is the site contact?

Is this site owned and maintained by the customer?

Is this a staffed site?

What are the hours of operation?

What are the building or room access procedures?

Are there any special security or safety procedures? Are there any union or labor requirements or procedures?

What are the locations of the equipment cabinets and racks?



45/649


Example: Customer Network Diagram



46/649


Network Assessment Information

Sources



47/649


Example: Network Assessment



48/649


Network Assessment Tools

Manual assessment:

Use monitoring commands on network devices on small networks. Use scripting tools to collect information on large networks.

Use existing management and auditing tools:

CiscoWorks

Third-party tools such as WhatsUp Gold, Castle Rock SNMPc,open source Cacti, Netcordia NetMRI, and NetQoS NetVoyant

Use other tools to collect relevant information for the network devices:

Third-party tools such as Network General Sniffer, AirMagnetsoftware and devices, and WildPackets AiroPeek


C d f M l I f ti


49/649


Commands for Manual Information

Collection


E l M l I f ti


50/649


Example: Manual Information

CollectionRouter CPU Utilization


E l M l I f ti


51/649


Example: Manual Information

CollectionRouter Memory Utilization


Example: Automatic Information


52/649



CollectionCacti Device List




53/649



CollectionNetMRI Inventory



54/649


Network Traffic Analysis

Use organizational input to identify the applications used in theexisting network and their relative importance.

Perform a traffic analysis to reveal additional applications used inthe network.

Use the results and organizational input to define QoS andsecurity-related requirements for discovered applications.



55/649


Steps in Analyzing Network Traffic



56/649


Example: Traffic Analysis

Application No. 8:

Description: Accounting software

Protocol: TCP port 5151

Servers: 2

Clients: 50

Scope: Campus

Importance: High

Average rate: 50 kbps with 10-second bursts to 1

Mbps



57/649


Network Analysis Tools

Cisco IOS Software analysis capabilities:

NBAR NetFlow

Cisco software-based network analyzers:

Cisco CNS NetFlow Collection Engine

Third-party tools, such as: Open source Cacti

Network General Sniffer

WildPackets EtherPeek and AiroPeek

SolarWinds Orion

Wireshark

RMON probes



58/649


Example: NBAR Printout



59/649


Example: Cisco IOS NetFlow Printout



60/649


Example: Cacti Graph



61/649


Example: Solarwinds Orion



62/649


Summary Report

Characterization of the existing network results in a

summary report that is used to: Describe the software features required in the network

Describe possible problems in the existing network

Identify the actions needed to prepare the network for the

implementation of the required features

Influence the customer requirements



63/649


Example: Equipment Summary Report

The network uses 895 routers:

655 routers use Cisco IOS Software Release 12.2(10).

240 routers use an older Cisco IOS Software version.


Example: Summary Report


64/649


p y p

Problem Statement

Requirement: Queuing in the WAN

Identified problem:

Existing Cisco IOS Software version does not support newqueuing technologies.

15 out of 19 routers with older Cisco IOS Software are in theWAN.

12 out of 15 routers do not have enough memory to upgrade toCisco IOS Software Release 12.3 or later.

5 out of 15 routers do not have enough flash memory toupgrade to Cisco IOS Software Release 12.3 or later.


Example: Summary Report


65/649


p y p

Recommendations

Recommended action:

12 memory upgrades to 64 MB 5 flash memory upgrades to 16 MB

Options:

Replace hardware and software to support queuing.

Find an alternative mechanism for that part of the network.

Find an alternative mechanism and use it instead of queuing.

Evaluate the consequences of not implementing the requiredfeature in that part of the network.



66/649


Documenting an Existing Network


Network Characterization Hour


67/649


Estimates

132180

48

8

24

16

8

8

8

12

288384

80

16

40

80

16

16

24

16

8698

32

4

16

8

6

6

6

8

4448

16

4

4

4

4

4

4

4

80483216i) Prepare report stating conclusions

j) Incrementally prepare network diagrams

f) Allow tools to gather data

4024168g) Analyze captured data

321684h) Prepare high level Layer 3 diagrams

48

8

12

12

12

Large Network200800

Switches/Routers

1664d) Set up network discovery tool

160164e) Resolve SNMP access and similar problems

Estimated manpower in hours

1664c) Review documentation

2464b) Interview network team

1684a) Interview management team

Huge Network>800

Switches/Routers

Medium Network20200

Switches/Routers

Small Network120

Switches/Routers



68/649


Summary

Characterizing an existing network entails gathering as muchinformation about the network as possible. Organization input, a

network audit, and traffic analysis provide the key information thatyou need.

Identifying major features of the network involves gatheringnetwork documentation and querying the organization.

The auditing process adds detail to the initial networkdocumentation that you created from existing documentation andcustomer input.

You can manually audit a small network, but you typically need

automated tools to audit a large network. Traffic analysis verifies the set of applications and protocols used

in the network and determines the traffic patterns of theapplications.



69/649


Summary (Cont.)

Tools used for traffic analysis range from manual identificationof applications using Cisco IOS Software commands in

combination with NBAR or NetFlow to those where dedicatedsoftware- or hardware-based analyzers capture live packets orSNMP data.

The result of the network characterization is a summary report

describing the health of the network.



70/649




71/649



Using the Top-DownApproach to NetworkDesign



72/649


Top-Down Design Practices

Start your design here.

Design down the OSI model.


Top-Down and Bottom-Up


73/649


Approach Comparison

Implements little orno notion of actualorganizational requirements

May result in inappropriatenetwork design

Incorporates organizationalrequirements

Disadvantages

Allows a quick responseto a design request

Facilitates design basedon previous experience

Incorporates organizationalrequirements

Gives the big picture toorganization and designer

Benefits

Bottom-Up ApproachTop-Down Approach



74/649


Example: Top-Down Voice Design



75/649


Creating a Network Decision Table

Decide which network layer requires decisions.

Gather possible options for a given situation.

Create a table that includes possible options andgiven requirements.

Match given requirements with specific properties ofgiven options.

Select the option with the most matches as the mostappropriate one.



76/649


Example: Selecting a Routing Protocol

Options

YesYesYesYesSupports Cisco Routers(Yes/No)

YesYesYesYesUse of VLSM(Yes/No)

YesNoYesYesEnterprise-Focused(Yes/No)

Good

Large

EIGRP

Fair

Large

OSPF

GoodPoorNetwork Support Staff Knowledge(Good/Fair/Poor)

LargeVery LargeSize of Network(Small/Medium/Large/Very Large)

RequiredNetwork

ParametersBGPParameters


Assessing the Scope of the Network


77/649


Design Process

Solutions to overcome bottlenecksWAN

Redundant equipment and links

Addition of wireless client mobilityCampus

All branch office LANs upgraded to support Fast Ethernet technologyEntire network

CommentsScope of Design


Example: Assessing the Scope of the


78/649


Network Design Process

ApplicationDesigning voice transport

NetworkDesigning routing, addressing

Physical, data linkChoosing connectiontype



79/649


Structured Design Principles



80/649


Cisco SONA Offerings



81/649


Network Design Tools



82/649


Planning an Implementation

If a design is composed of multiple complex components:

Implement each component separately; do not implementeverything at once.

Incremental implementation:

Reduces troubleshooting in case of failure

Reduces time needed to revert to previous statein case of failure



83/649


Major Implementation Components

Each step should contain the following information:

Description Reference to design sections

Detailed implementation guidelines

Detailed roll-back guidelines in case of failure

Estimated time for implementation



84/649


Example: Summary Implementation Plan

Section 6.2.3.3Complete cablingStep 3

Section 6.2.5.1Complete connections toexisting network

Step 1

Section 6.2.5.2Verify connectivityStep 2

Section 6.2.5Launch campus updates intoproduction04/05/2007Phase 5

Section 6.2.4.4Verify connectivityStep 4

Section 6.2.4.3Configure routingStep 3

Section 6.2.3.4Verify data link layerStep 4

Section 6.2.4Configure campus hardware04/03/2007Phase 4

Section 6.2.4.1Configure VLANsStep 1

Section 6.2.4.2Configure IP addressingStep 2

Section 6.2.3.2Install routersStep 2

Section 6.2.3.1Connect switchesStep 1

Section 6.2.3Install campus hardware04/02/2007Phase 3

CompleteImplementationDetails

DescriptionDate, Time



85/649


Example: Detailed Implementation Plan

Section 6.2.7.3, Configure routing protocols in the WANnetwork module:

Number of routers involved is 50.

Use template from section 4.3.1, EIGRP details.

Per router configuration:

Use passive-interface command on all nonbackbone LANs.

(See section 4.2.3, EIGRP details.)

Use summarization according to the design. (See section 4.2.3,EIGRP details, and section 4.2.2, Addressing details.)

Estimated time is 10 minutes per router.

Roll-back procedure is not required.



86/649


Pilot vs. Prototype Networks

The pilot or prototype network is used as proof of conceptfor the design:

A pilot network tests and verifies the design before thenetwork is launched.

A prototype network tests and verifies a redesign in anisolated network before it is applied to the existing network.

Results:

Success

Failure


E l P t t N t k


87/649


Example: Prototype Network


D t il d St t f D i D t


88/649


Detailed Structure of a Design Document


S


89/649


Summary

Designing an enterprise network is a complex project.Top-down design facilitates the process by dividing it into smaller,

more manageable steps. Decision tables facilitate the selection of the most appropriate

option from many possibilities.

In assessing the scope of a network design, determine whether

the design is for a new network or is a modification of the entirenetwork, a single segment or module, a set of LANs, a WAN,or a remote-access network.

The output of the design should be a model of the complete

system. To achieve this, the top-down approach is highlyrecommended.


S (C t )


90/649


Summary (Cont.)

When the design is complete, you are ready to document theimplementation and migration in as much detail as possible.

After a design is complete, you should verify it. You can testthe design in an existing or live network (pilot) or in a prototypenetwork that will not affect the existing network.

A design document lists the design requirements, documents

the existing network, documents the network design, identifiesthe proof-of-concept strategy, and details an implementation plan.



91/649



Module Summary


92/649


Module Summary

Cisco SONA is the enterprise framework for implementingintelligent networks and maps business requirements to network

requirements. The design methodology under PPDIOO includes these tasks:

Identifying customer requirements

Characterizing the existing network and sites

Designing the network topology and solutions

The result of network characterization is a summary reportdescribing the health of the network.

Top-down design facilitates network design.



93/649



Structuring and


94/649


Designing for Cisco Internetwork Solutions (DESGN) v2.0

Structuring andModularizing theNetwork



95/649


Structuring and Modularizing the Network

Designing theNetwork Hierarchy


Layers in the Hierarchical Model


96/649


Layers in the Hierarchical Model


Example: Hierarchical Network


97/649


Example: Hierarchical Network


Access Layer


98/649


Access Layer

Concentration point at which clients access the network

Layer 2 switching in the access layer: Defines a single broadcast

domain

Multilayer switching in the campus access layer: Optimallysatisfies the needs of a particular user through routing, filtering,authentication, security, or quality of service

Multilayer switching in the WAN access layer: Helps control WANcosts using dial-on-demand routing (DDR) and static routing


Example: Access Layer Connectivity in

the Campus LAN


99/649


the Campus LAN

Workstations are attached to VLANs with Layer 2 switches.

Recommended practice: Implement one VLAN (IP subnet) per access switch.

Access switches connect Layer 3 links (if only one VLAN per access switch)or via VLAN trunk.

If needed, distribution routers route between VLANs.


Distribution Layer


100/649


Distribution Layer

Provides multilayer switching between access and core layers:

Provides media transitions

Aggregates bandwidth by concentrating multiple low-speed access links into ahigh-speed core link

Determines department or workgroup access

Provides redundant connections for access devices

Implements policy-based decisions:

Filtering by source or destination address

Filtering on input or output ports

Hiding internal network numbers by route filtering

Static routing

Security Quality of service mechanisms


Example: Distribution Layer in the

Routed Campus Network


101/649


Routed Campus Network


Core Layer


102/649


Core Layer

The function of the core layer is to provide fast andefficent data transport that:

Forms a high-speed backbone with fast transport services

Provides redundancy and fault tolerance

Offers good manageability

Note: Core layer should avoid packet manipulationfor filtering or access list checking.


Example: Multilayer Switching in the

Campus Core


103/649


Campus Core


Example: Routing in the WAN Network


104/649



Summary


105/649


The hierarchical network model provides a modular view of anetwork, making it easier to design and build a network.

The purpose of the access layer is to grant end-user access tonetwork resources.

The distribution layer provides aggregation for the access layerdevices and uplinks to the core layer. It is also used to enforce

policy within the network. The core layer provides a high-speed, highly available backbone

designed to switch packets as fast as possible.



106/649



Using a ModularA h i


107/649



gApproach inNetwork Design


Service-Oriented Network Architecture


108/649



Example: Cisco Enterprise CampusArchitecture


109/649



Cisco Enterprise Architecture


110/649



Example: Dividing the Network intoAreas


111/649



Enterprise Campus InfrastructureModule


112/649



Building Access Layer


113/649



Building Distribution Layer


114/649



Campus Core Layer


115/649



Server Farm Module


116/649



Enterprise Edge Modules


117/649



E-Commerce Module


118/649



Internet Connectivity Module


119/649



Remote Access and VPN Module


120/649



WAN and MAN and Site-to-SiteVPN Module


121/649



Enterprise Edge Guidelines

1 D t i th ti it d d t th I t t


122/649


1. Determine the connectivity needed to the Internet.

2. Create the e-commerce module ID needed.

3. Design the remote access and VPN module if needed.

4. Design the WAN module to support connections to remoteenterprise locations if needed.


Service Provider Modules


123/649



Enterprise Remote Modules


124/649



Enterprise Branch Module


125/649



Enterprise Data Center Module


126/649



Enterprise Teleworker Module


127/649



Summary

Based on SONA the Cisco Enterprise Architecture provides a


128/649


Based on SONA, the Cisco Enterprise Architecture provides amodular enterprise-wide hierarchical approach for providingnetwork infrastructure and services to all places in the network.

The enterprise campus infrastructure module includes thecampus infrastructure module and the server farm module.

The enterprise edge modules include the e-commerce module,the Internet connectivity module, the remote access and VPNmodule, and the WAN and MAN and site-to-site modules.

The remote enterprise modules include the remote branches,data centers, and teleworkers.



129/649



Using InfrastructureServices


130/649



Services


Explaining the Role of InfrastructureServices


131/649



Modularizing Internal Security


132/649



Reasons for Internal Security

The enterprise campus is protected by security functions in the


133/649


enterprise edge:

If the enterprise edge security fails, the unprotected enterprisecampus is vulnerable.

The potential attacker can gain physical access to theenterprise campus.

Some network solutions require indirect external access to theenterprise campus.

All vital elements in the enterprise campus must be protectedindependently.


External Threats


134/649


The PDF files and any printed representation for this material are the property of Cisco Systems, Inc.,for the sole use by Cisco employees for personal study. The files or printed representations may not beused in commercial training, and may not be distributed

Date post:	01-Mar-2018
Category:	Documents
Upload:	billing
View:	214 times
Download:	0 times

Desgn20sg New

Documents