Exam 640-441: Cisco Certified Design Associate
· Performance Requirements
- Identify any issues concerning network latency and response times
- Find out if there is high utilization on LAN segments or WAN links
- Determine how often the WAN links go down
· Application Requirements
- Find out what new applications have been introduced to the network
- Determine the number of users using the applications
- Find out the traffic flow for these applications
- Identify what new protocols are being introduced to the network
- Determine what applications are used during the daytime/nighttime hours
- Determine the time of day that represents the peak usage hours of apps
· Network Management Requirements (FCAPS)
- Determine how the network is managed
- Determine whether there is a NMS to view network performance and faults
- Ascertain whether there are any accounting and security requirements
- Find out whether the staff is training on the network management apps
- Find out whether there is a station for configuration management
· Security Requirements
- Determine what type of security is required
- Find out what external connections are present and why
- Determine whether additional security is required on Internet connections
Business and Political Constraints: Consider the following and ascertain whether they are constraints in your design:
· Ascertain budget or resource limitations for the project
· Determine the timeline to complete the project
· Determine whether any internal politics play a role in the decision-making process. Find out what different sources or groups are providing input.
· Make sure the client’s staff is able to operate and manage the new network
· Find out whether the customer wants to reuse or trade in existing equipment
Small to Medium-Sized Network Design Framework
Protocol Problems ŕ Use routing
Media Contention ŕ Use LAN Switching
Transport Bandwidth ŕ Use Fast Ethernet Switching or ATM (for large)
STEPS FOR NETWORK DESIGN
1. Gather information to support business and technical requirements
2. Assess the current network
3. Consider the applications involved
4. Design the LAN
5. Design the WAN
6. Design for specific protocols
7. Create the design document and select Cisco network management apps
8. Test the design
1. GATHER INFORMATION TO SUPPORT CUSTOMER REQUIREMENTS
Step 1: Characterize the customer’s business constraints
· Document the customer’s budget
· List the resources available for this project, the staffing, the training level and the timelines
Step 2: Identify the security requirements
· Determine the security concerns of the customer
· Document how much security the customer needs and who will be affected
· List the type of security the customer needs - firewalls, access lists etc.
· Document the type of authentication required
· List how much node security is required, as well as info on passwords, physical security and access rights
Step 3: Document the customers manageability requirements
· Identify the specific needs of FCAPS
Step 4: Extract the customers application requirements
· Document the application requirements
· Document any new applications, including users and information flow
· List any new protocols required
Step 5: Characterize the new network traffic
· Characterize new network traffic using analysis tools
· Capture parameters such as traffic load and behavior
Step 6: Characterize the performance requirements
· Document the customers requirements in the following areas:
- Response time, time it takes for response service request to a node
- Accuracy, useful traffic to transmission errors
- Availability, amount of time the network is running
- Maximum network utilization, maximum network capacity
- Throughput, quantity transferred between nodes in seconds
- Efficiency, effort required to produce certain amount of data throughput
- Latency, time between being ready for transmission and completing transmission
Step 7: Identify specific customer needs
· Document any other customer requirements or needs
Characterizing Network Traffic
Five areas are covered:
- Broadcast behavior
- Frame size
- Windowing
- Flow control
- Error-recovery mechanisms
2. ASSESS THE CURRENT NETWORK
Assess the Customers Corporate Profile Information
· Business goals and business type
· Corporate structure
· Geographical structure
· Current and future staffing
· Policies and politics
Assessing the customers technical information
· Performance Assessment
- Is there any latency?
- What is causing that latency?
- When do the performance problems occur?
- How will performance be affected by the proposed design?
- How much traffic flows between segments?
- Are there new applications, networks or segments that will add to the traffic?
Perform a baseline on the critical segments
· Applications Assessment
- Applications, current apps and plans for future apps, who uses what apps
- Information flows, analyze where the traffic is and how different apps affect that flow
- Shared data, where shared data resides and who uses it
- Categorize data, determine type of data passed along the network eg. routed protocols, nonrouted protocols and routing protocols.
· Network Management Assessment
- Who manages the network?
- What type of network management is the client looking to implement
- What type of notification does the client want to warn if performance or fault issues
- Who in the company knows how to perform network management tasks
· Security Assessment
- What security risks concern the customer?
- What security risks are priorities to the customer?
- Are there any existing security policies? Are they documented?
- What are the different access levels a user can have?
- What is the physical security f the network?
Documenting the Existing Network
Step 1: Characterize the customer’s applications
Field
Definition
Application
Identify each application that runs over the network
Application Type
Characterize as a database, groupware, Internet etc.
Number of Users
Document the number of users for each application
Number of hosts or servers
Identify how many provide each application
Segment
Locate the segments the application runs on
Comments
Write any comments that could be useful later
Step 2: Characterize the Network Protocols
Field
Definition
Protocol
Identify each protocol that runs over the network
Protocol Type
Characterize as routing, LAN, server protocol etc.
Number of Users
How many users exist for each application
Number of hosts or servers
Number that use each application
Comments
Any comments that could be useful later
Step 3: Document the Customer’s Current Network
· Documenting the network topology
· Documenting the addressing schemes
· Documenting concerns about the network
Step 4: Identify Potential Bottlenecks
Step 5: Identify the Business Constraints and Inputs into your Network Design
Step 6: Characterize the Existing Network Availability
· What are the critical or fragile segments?
· Does any MTBF documentation exist on any segment?
· What caused the network failure for those segments?
· How long were the network failures?
· What is the cost by department for a network outage (per hour)?
· What is the cost to the company or organization for a network outage (per hour)?
Step 7: Characterize the Network Performance
· Measure response time between hosts
Step 8: Characterize the Existing Network Reliability
Use a protocol analyzer to document the following values:
· Total MB
· Total number of frames
· Total number of CRC errors
· Total number of MAC-layer errors
· Total number of broadcasts/multicast frames
Step 9: Characterize the Network Utilization
Field
Description
Relative Network Utilization
Percentage of each type of protocol on a segment
Absolute Network Utilization
Bandwidth use of each segment
Average Frame Size
Average frame size for each segment
Broadcast/Multicast Rates
Divide total broadcast/multicast by total frames
Step 10: Characterize the Status of the Major Routers
Show interfaces
Statistical information on all interfaces, type, ID, up or down
Show processes
Displays active processes, including CPU processes
Show buffers
Show info in main system memory to identify overutilization
Step 11: Characterize the Existing Network Management Tools
Step 12: Summarize the Health of the Existing Network
Topology
Healthy if:
Shared Ethernet
No more than 40% utilization; Less than 0.1% of packets should be collisions
Token Ring
No more than 70% utilization; Less than 0.1% of packets should be soft errors
FDDI
No more than 1 ring operation per hour
WAN
No more than 70% utilization
General
Response time should be less than 100 milliseconds
Segments
Should have less than 20% broadcasts/multicasts; Less than 1 CRC error per million bytes of data
Routers
Should have 5-minute CPU utilization under 75%; Number of output queue lengths less than 100 in an hour
3. CONSIDER THE APPLICATIONS INVOLVED
IBM Networking
Source-Route Bridging (SRB): Designed to bridge between Token Ring LAN’s. Source determines the route to arrive at the destination node before sending an information frame to it. Unlike Ethernet where the bridge would determine the route. It does this using explorer frames. SRB is inherently loop-free and doesn’t rely on the Spanning-Tree protocol to form loop-free paths. It is a flat network topology in the data-link layer so it is limited. Has a maximum hop count of 7 bridges. Routers can help overcome this limit.
Advanced Peer-to-Peer Networking: Upgraded version of SNA, but uses a peer-based hierarchy rather than mainframes.
Data-Link Switching Plus (DLSw+): Designed to overcome limitations on SRB networks. Link-layer acknowledgements and keep-alive messages do not have to travel through the WAN. Can be rerouted around link failures and can be prioritized on WAN links. End systems can attach to the DLSw+ from Token Ring, Ethernet, FDDI, QLLC and SDLC networks.
Microsoft Windows Networking
NT Protocols: NT uses the session-layer protocol NetBIOS protocol for file and print sharing, messaging and name resolution. NetBIOS can be run over NetBEUI, IPX or TCP/IP (preferred). NetBIOS broadcasts run on TCP port 137.
DHCP and WINS
Multimedia Networking
Packet Voice: converges voice and data communications for companies to save toll charges on voice telephone calls. Voice is converted to packets, cells or frames sent as data and transferred back to analog voice at the destination. PSTN processes calls outside of the intranet. With Voice over IP (VoIP) technology voice is digitized into IP packets. In VoIP RTP is used to transport audio streams. RTP runs over UDP, no port assigned though.
Video Streams: Video applications fall into two types: bi-directional and unidirectional. When multicasting IGMP is used to determine who to multicast the message too.
Novell Application Services
SAP: In a Novell IPX network, resources advertise their services using SAP. Routers build SAP tables and every 60 seconds forwards to information to other routers. This can produce a lot of traffic, Methods to reduce this traffic are:
· Use IPX SAP filters
· Use NLSP for routing IPX: Novell’s link-state routing protocol for routing IPX traffic, similar to OSPF.
· Use EIGRP: sends updates only when changes occur. Must still use IPX RIP on the WAN and EIGRP on the WAN.
AppleTalk Services
Uses the concept of zones to form a logical grouping of nodes. Zones allow users to find resources in their workgroup, despite their physical location. Zones control broadcast traffic. The Zone Information Protocol (ZIP) maintains the network-to-zone mappings in AppleTalk routers. ZIP maintains a Zone Information Table (ZIT) that can be viewed on the router.
Firewall Services
Usually implemented in a 3-layer design. On the outside is a filtering router that implements access lists. In the isolation LAN, hosts are installed to provide Web, FTP, DNS services, these are named bastion hosts. An internal filtering router permits access to the internal LAN.
Mail Application Flow
Messaging application servers are usually deployed throughout the enterprise. Usually a hierarchy is used to deploy mail servers. E-mail traffic will follow the hierarchy and be bi-directional. The SMTP gateway will reside somewhere near the top of the hierarchy, providing transport to Internet messaging
Future Application Plan
Document the application characteristics (see step 1 of “Documenting the existing network).
Attempt to document the application traffic flow as one of the following:
· Terminal/Host: apps with low-volume character traffic, Telnet
· Client/Server: traffic flow is bidirectional and asymmetric. NT
· Peer/Peer: traffic flow is bidirectional and symmetric. NFS
· Server/Server: traffic between file/e-mail servers etc.
4. DESIGN THE LAN
LAN Topology Design
The different network topology models: - Hierarchical models
- Redundant models
- Secure models
Hierarchical Models
Enable you to design internetworks in layers. Benefits:
- Cost savings
- Ease of understanding
- Easy network growth
- Improved fault isolation
A Hierarchical network design has 3 layers:
Core Layer: provides optimal transport between sites. The high-speed switching backbone of the network, should have the following characteristics:
- Offer high reliability
- Provide redundancy and fault tolerance
- Adapt to changes quickly
- Offer low latency and good manageability
- Avoid slow packet manipulation caused by filters or processes
- Have a limited and consistent diameter
Distribution Layer: provides policy-based connectivity. The demarcation point between the access and core layers of the network. The following functions can be performed at this layer:
- Policy and security
- Address or area aggregation or summarization
- Departmental or workgroup access
- Broadcast/multicast domain definition
- Routing between VLAN’s
- Media translations
- Redistribution between routing domains
- Demarcation between static and dynamic routing protocols
Several Cisco IOS software features can be used to implement policy:
- Filtering by source or destination address
- Filtering on input or output ports
- Hiding internal network numbers by route filtering
- Static routing
- Quality of service mechanisms
Access Layer: provides workgroup/user access to the network. Characterized by switched and shared bandwidth LAN’s in a campus environment. Provides access for remote sites into the corporate network by using WAN technologies such as ISDN, Frame Relay and leased lines.
Redundant Models
Design for customers who have critical systems, services or network paths. Consider the following types of redundancy:
Workstation-to-Router Redundancy: possible ways a workstation can discover the address of a router when needing to send data to another network segment:
- ARP - Explicit configuration
- RDP - RIP
- IPX - AppleTalk
- HSRP
Server Redundancy: mirroring or duplexing
Route Redundancy: load balancing and minimizing downtime (mesh)
Media Redundancy: use of backup links, also minimizes downtime
Secure Models
Often designed using a firewall. Most common implementation is the three-part firewall system. Rules for the three-part firewall are:
· The inside packet filter router should allow inbound TCP packets from established sessions
· The outside packet filter router should allow inbound TCP packets from established TCP sessions
· The outside packet filter router should allow packets to specific TCP or UDP ports going to specific bastion hosts.
· Always block traffic from coming in from between the firewall routers and hosts and the internal network.
LAN Types
Large Building LAN: large number of users, data center, segmented by floors or departments, floor closet switches
Campus LAN’s: High speed backbone switching, connects two or more buildings near each other
Small/Remote Site LAN’s: small number of users, small hubs/switches, usually connect back to the corporate network via a small router.
LAN Media
Ethernet CSMA/CD Based
Specification
Speed (Mbps)
Max segment (m)
Encoding
Media
10Base5
10
500
Manchester
Thicknet
10Base2
10
185
Manchester
Thinnet
10BaseT
10
100
Manchester
UTP
100BaseT
100
100
4B/5B
UTP
1000BaseT
1000
100
5-level
Cat 5 UTP
1000BaseLX
1000
550
8B/10B
Fiber
1000BaseSX
1000
220, 500
8B/10B
Fiber
1000BaseCX
1000
25
8B/10B
copper
Token Access Based
Type
Speed (Mbps)
Ring Types
Encoding
Media
Token Ring
4/16
Unidirectional single ring
Differential Manchester
UTP/STP
FDDI
100
Dual counter rotation rings
4B/5B with NRZI
Fiber
LAN Hardware
Device
OSI Layer
Protocol
Domains
Understands
Repeaters
Physical
Transparent
Amplify signal
Bits
Hubs
Physical
Transparent
Amplify signal
Bits
Bridges
Data link
Transparent
Collision domain
Frames
Switches
Data link
Transparent
Collision domain
Frames
Routers
Network
Aware
Broadcast domain
Packets
Layer 3 switches
Network
Aware
Broadcast domain
Packets
5. DESIGN THE WAN
Steps for Designing the WAN
1. List the requirements for the WAN design
2. Select a WAN technology
3. Select the WAN hardware
4. Provision the WAN
Listing the Requirements for the WAN Design
WAN designs should meet the following criteria:
- reliable service
- minimize the cost of bandwidth
- optimize the efficiency of bandwidth
· Reliable Service: reliable service can be achieved through redundancy.
Star Topology: common for packet-switched networks such as frame relay. Single point of failure at the core router. The core router must be able to support the performance level needed.
Fully Meshed Topology: provides the most redundancy, each router added though will add to the traffic of the existing routers. Each router must be able to support the performance level needed. Costly in equipment and WAN connections.
Partially Meshed Topology: often called redundant star configuration. Provides a fair amount of redundancy with limited amount of meshing and without the negatives associated with fully meshed topologies.
· Minimizing the Cost of Bandwidth: choose a technology such as ISDN, where you only pay for what you use, if usage is infrequent. In the case of frame relay you pay a reoccurring fee for T1 or partial T1 access to the carrier’s frame relay network.
· Optimizing the Efficiency of Bandwidth: multiplexing or combining multiple services over the same bandwidth improves efficiency. A critical component of sharing bandwidth is using Quality of Service techniques.
Quality of Service: a method of measuring and maintaining a level of service needed to support technologies such as voice and video.
Selecting a WAN Technology
WAN Technology
Applications
Analog modem
Used by telecommuters and dial-up mobile users Average usage is less than 2 hours per day Line speeds of 56kbps or less Used for backup for another type of link Can be attached to network devices such as routers for RAS Customer is charged for usage
DSL
Uses existing copper telephone lines to usually provide up to 1.544 mbps speeds to home or office xDSL refers to the family of DSL technologies
Cable modem
Data connections through the same line as cable TV, up to 27 mbps, depending on bandwidth
Leased line
Used in point-to-point networks and star Fractional T1, T1 or T3 Backup for other high speed links T1’s commonly used for corporate Internet access Customers pay for dedicated line
ISDN
BRI composed of two 64 kbps B channels and one 16 kbps D channel Cost effective remote access Supports voice and video Backup for leased line and frame relay links Customer charged for usage of line
Frame Relay
Cost effective, high speed, low latency mesh or star For remote offices and LAN’s Fractional T1 or T1 Both private and carrier-provided networks Customer charged for usage
X.25
WAN circuit or backbone layer 3 reliability features Support for legacy applications
ATM
Support for accelerating bandwidth requirements Support for multiple QoS classes for differing application requirements for delay and loss Supports voice, video and data Used on top of T3, SONET and other high speed lines Customer pays for dedicated line
Other WAN Technology and Design Factors
There are three basic WAN technology categories:
· Leased line: also known as point-to-point links, permanent connections established between two customer end points through a carrier’s WAN. Usually for private use by the customer for duration of their lease.
· Circuit Switched: technology used by ISDN, carrier establishes a physical circuit for the length of the session, similar to a phone call.
· Packet Switched: used by ATM, Frame Relay, SMDS and X.25, can share a single physical connection through the carrier network. Broadcast traffic can largely affect performance. X.25 and SMDS are known as nonbroadcast multi-access networks (NBMA). Frame Relay and ATM are called multi-access networks.
Selecting the WAN Hardware
Checklist for selecting WAN Hardware:
· Cost
· Functionality
· Redundancy
· Scalability
Router Switching Modes
Process Switching: packets destination causes the router to look up the path in its routing table. The packet is processed in main memory. Will occur if a router has an access list. Encryption and compression require process switching
Fast Switching: incoming packets are passed based on previously cached route information derived from previous packets. These caches are stored in main memory.
Silicon Switching: passes packets on 7000 series routers only, using information in the SSE of the SSP module. The SSP will make the forwarding decision without interrupting the CPU.
Optimum Switching: available only on Route Switch Processor (RSP), because of enhancements to the caching capability, almost twice as fast as silicon switching.
NetFlow Switching: creates traffic flows using process switching, it will review the following packets for the same source, destination, encryption etc. and will pass them to the destination port. Has a flow cache that makes it possible to process access lists faster than process switching, also supports detailed traffic reporting that can be used for network management, planning and chargebacks.
Network Design Guidelines: some common network designs are suboptimal in terms of performance; most of these are based on media mismatch.
Provisioning the WAN
Provisioning the WAN means preparing to receive WAN services. First you need to understand the different WAN speeds:
Line Type
Signal Standard
Number of DS0’s
Bit Rate (Mbps)
T1
DS1
24
1.544
T3
DS3
672
44.736
E1
2M
30
2.048
E3
3M
480
34.064
J1
Y1
30
2.048
After choosing a signaling standard you need to review the components of the WAN you want to implement. Different WAN technologies require very different steps. Frame Relay’s steps are as shown:
CIR: Committed Information Rate, a connections minimum bandwidth in kbps.
1. Choose a CIR based on realistic, anticipated traffic rates
2. Aggregate all CIR’s to determine core bandwidth requirements
3. Determine the link speed and number of interfaces required on the core router
4. Choose a router platform that can handle the job
6. DESIGN FOR SPECIFIC PROTOCOLS
IP Addressing
Class
High-Order bits
Range
A
0
1 - 126
B
10
128 - 191
C
110
192 - 223
D
1110
224 - 239
E
1111
240 - 255
IPX and AppleTalk Address Formats
Protocol
Network
Host
Format
IPX
32 bits
48 bits (MAC)
00001EAC.0010.0040.6678
AppleTalk
16 bits
8 bits + 8 (socket)
10.5.7
Routing Protocols per Protocol Family
Routed protocol
Routing Protocol
IP
RIP, IGRP, OSPF, IS-IS, EIGRP
IPX
IPX RIP, NLSP, EIGRP
AppleTalk
RTMP, AURP, EIGRP
Routing Protocol Category
Category
Routing Protocol
Distance Vector
IP RIP, IGRP, IPX RIP, RTMP
Link-State
OSPF, NLSP, IS-IS
Hybrid
EIGRP
All support VLSM except RIPv1 and IGRP
Distance Vector Update Timers
Routing Protocol
Default Update Time (seconds)
IP RIP
30
IP IGRP
90
AppleTalk RTMP
10
IPX RIP
60
XNS
30
DECnet IV
40
IPX SAP
60
Vines VRTP
90
OSPF
Router Types:
· Internal Router: interfaces belong to the same OSPF area, only one link-state database
· Area Border Router (ABR): connected to more than one area, maintain link-state database for each area they belong
· Autonomous System Boundary Router (ASBR): inject external link-state advertisements into the OSPF database. External routers
· Backbone Router: at least one interface attached to area 0
AURP: AppleTalk routing protocol used over TCP/IP based networks
Bridging Protocols
Transparent Bridging: Ethernet, implements spanning-tree protocol
Source-route Bridging (SRB): Token Ring, forwards explorer packets
Translational Bridging: Translates from Ethernet to Token Ring
Source-route Transparent Bridging (SRT): Bridge functions as a transparent and SRB bridge
Source-route Translational Bridging (SR/TLB): Bridge functions as a source-routing and a transparent bridge, bridging between the two
Cisco IOS Software Features
· Access Lists
· Encryption
· Proxy services
· Compression
· Traffic shaping
· Queuing
Access Lists
Type of Access List
Range
IP standard
1 to 99
IP extended
100 to 199
Bridge type code
200 to 299
DECnet standard and extended
300 to 399
XNS standard
400 to 499
XNS extended
500 to 599
AppleTalk zone
600 to 699
Bridge MAC
700 to 799
IPX standard
800 to 899
IPX extended
900 to 999
IPX SAP
1000 to 1099
Bridge extended
1100 to 1199
NLSP route aggregation
1200 to 1299
Encryption: Cisco Encryption Technology (CET) or IPSec
Proxy Services: - Resource discovery on Serverless LAN’s
- Traffic reduction on bridged networks and WAN’s
- Improved performance for time-sensitive applications
Traffic Shaping: - Generic traffic shaping
- Frame Relay traffic shaping
Queuing Services:
Priority Queuing: useful for SNA and time-sensitive, mission-critical protocols. Ensures one type of traffic will get through at the expense of all other types of traffic.
Custom Queuing: handles traffic in a round-robin fashion, more fair than priority queuing.
Weighted Fair Queuing: handles traffic as first come first served, and therefore is the most fair of the three. Main problem is that sessions using large packets can impeded sessions using small packets.
7. CREATE THE DESIGN DOCUMENT AND SELECT CISCO NETWORK MANAGEMENT APPLICATIONS
Design Document Components
Executive Summary: directed to decision makers. Provides an explanation of the purpose of the project, a list of strategic recommendations and a description of how the solution meets the customers requirements.
Design Requirements: shows current topology, current applications and current network health. Lists performance and scalability requirements, business requirements and constraints and expected performance.
Design Solution: shows the proposed network topology, selected hardware and media, suggested routing protocols and proposed network management tools.
Summary: provides a concise summary of the solution and a description of how the solution meets the requirements.
Appendixes: lists contacts and provides additional information about products, circuit information and prototype results.
Cost (Optional): provides an itemized and detailed cost listing of equipment to be purchased.
Proactive Network Management: monitoring the network before problems occur. The client must gather network statistics and document those as a baseline of the current status of the network. The baseline should include:
- Segment utilization
- Router CPU utilization
- Response time tests
- Define acceptable service goals for the network
Network Management Processes (FCAPS)
Fault
Refers to detecting, isolating and correcting problems
Configuration
Refers to baselining, modifying and tracking configuration changes of network devices
Accounting
Refers to tracking the usage of segments to determine usage-based billing of service
Performance
Refers to the measurement of network behavior and effectiveness to deliver frames, packets, segments
Security
Refers to the maintenance and distribution of authentication and authorized information
Network Management Architecture
Managed device
Is a router or switch with agent software
Agent
Gather statistics
NMS
Runs network management applications. Polls devices for SNMP information and configuration
Network Management Products
CiscoWorks Blue: suite of products designed to simplify management of a consolidated SNA and IP network.
CiscoWorks for Windows: suite of integrated network management tools designed to simplify the administration and maintenance of small-to-medium sized business networks or workgroups. Runs on NT.
CiscoView: GUI-based device management software application that provides dynamic status, statistics and comprehensive configuration information for Cisco systems internetworking products. Displays a graphical real-time physical view of Cisco devices.
Netsys Connectivity Service Manager: tool for collecting actual router configuration data and creating multiprotocol topologies so that you can visually navigate your network and gain a complete understanding of how it works.
Netsys Performance Service Manager: modeling tool that enables you to define, monitor and optimize performance service levels to make the most efficient use of existing network resources and to diagnose and solve network performance problems.
Netsys Baseliner for Windows NT: tool that displays, debugs and validates your network configuration. Tests configurations and changes offline before committing them to the live network.
Cisco ConfigMaker: an easy-to-use Microsoft Windows application used to configure a small network of Cisco routers, switches, hubs and other network devices from a single PC, without requiring knowledge of Cisco IOS.
Cisco FastStep: a Microsoft Windows 95, 98 and NT4 based software tool that simplifies the set up, monitoring and troubleshooting of Cisco routers for home and small offices.
CiscoWorks2000: a family of products based on Internet standards for managing Cisco enterprise networks and devices. It includes Resource Manager Essentials and CWSI Campus. It runs on UNIX or Windows NT.
8. TEST THE DESIGN
Determining the Appropriate Testing Plan
Pilot
Prototype
Size of the network design
Small designs, with few segments or simple WAN networks
Subset of a large network that spans both LAN’s and WAN
Demonstration of functionality
Basic functionality, such as connectivity
Prove complex functionality, connectivity, applications and routing
Cost
Small, due to simplicity of test
Costly
Customer requirements
Used for small test of the design
Needs proof of functionality of the design
Steps for Building a Prototype
Step 1: Review the Customers Requirements
- determine the customers major goals
- outline proof required to demonstrate the design works
- determine possible problem areas that might affect the design
Step 2: Determine the Extent of the Prototype
- determine how much of the design must be built
- identify tools you can use to simplify the prototype
Step 3: Understand your Competition
- work with your sales team to determine their proposal
- if unavailable, speculate what it could be
- research your competition
Step 4: Develop a Test Plan
- draw a network diagram
- list tools for the test
- list the plan scheduling, resources and milestones
- prepare the demonstrations
- determine how each test proves the design meets its goals
- identify how the design shows Cisco’s strengths
- determine how each test will show the competitor is not ideal
Step 5: Purchase and Prepare Equipment
- network simulation tools
- protocol analyzers
- industry tests
- Cisco hardware and software
- Routers, switches
- Network management tools
- Non-Cisco hardware and software
- Application and file servers
Step 6: Practice
- practice the demonstration to include necessary elements
Step 7: Conduct Final Tests and Demonstrations
- test your configuration using the following tools:
- Cisco IOS software commands
- Protocol analyzers
- Simulation tools
Steps for Creating a Pilot
· Step 1: Test the design
· Step 2: Review the competitions proposal
· Step 3: Script the demonstration
· Step 4: Practice
· Step 5: Schedule time and present the demonstration to the customer
Testing the Prototype or Pilot
Cisco IOS Software Commands
Show interface
Shows data link layer errors, router errors and broadcast rates
Show processes
Shows router CPU usage and CPU time used by processes
Show buffers
Shows buffer usage and misses
Ping and traceroute
Used to troubleshoot connectivity and performance problems
Show protocol route
Lists protocol routing table to troubleshoot routing problems
Show access-lists
Displays access lists to help troubleshoot security problems
Debug*
Used to troubleshoot and verify packets sent and received
* debug command could cause severe performance issues on routers
Protocol Analyzers: flexible tools that provide a wide range of data collection and traffic analysis methods. Functions are:
- configure for the correct LAN and WAN media
- capture data
- test the prototype or pilot
- demonstrate security
Simulation tools: test the functionality of critical devices on the network, such as firewalls. Vulnerability scanners.
Demonstrate your Finding to the Customer
After completing the tests you need to provide proof of the results to your customer. Sample format:
· Publish your findings in a concise but comprehensive report. Focus on customer requirements and include diagrams and some of the raw data collected.
· Add the results of your test to the network design document.
· Create slides that graphically demonstrate the correlation between your test results and the customers requirements.
· Meet with the customer to present your findings. Use different presentation methods for effectiveness.
· Meet with the customer and reproduce tests while the customer is watching. Do this only after you have had a chance to practice.
Recommended Maximum number of Non-routed Workstations
Protocol
Max # of WS
AppleTalk
200
Mixed
200
NetBIOS
200
IP
500
IPX
300
Standard Administrative Distances for IP Routes
IP Route
Administrative Distance
Directly connected interface
0
Static route using connected interface
0
Static route using IP address
1
EIGRP summary route
5
External BGP route
20
Internal EIGRP route
90
IGRP route
100
OSPF route
110
IS-IS route
115
RIP route
120
EGP route
140
External EIGRP route
170
Internal BGP route
200
Route of unknown origin
255
How Long Does it Take to Detect a Failed Link?
1. immediate if carrier detect (CD) lead loops
Serial Lines
2. otherwise, between 2-3 keepalives
3. keepalive timer default = 10 seconds
Token Ring or FDDI
Almost immediate due to beaconing ability
1. between 2-3 keepalives
Ethernet
2. keepalive default = 10 seconds
3. immediate if caused by transceiver or local interface failure
The material on this web site is not sponsored by, endorsed by or affiliated with Cisco Systems, Inc. Cisco®, Cisco Systems®, CCDA™, CCNA™, CCDP™, CCNP™, CCIE™, CCSI™, the Cisco Systems logo and the CCIE logo are trademarks or registered trademarks of Cisco Systems, Inc. in the United States and certain other countries. All other trademarks are trademarks of their respective owners.
|
