Steps a prototype network be implemented and tested

1. In a lab environment as a test network.
2. Gradually integrated into the production network and tested during off-hours.
3. Gradually integrated into the production network and tested during normal business hours.

Replacing the current network and testing the new design during off-hours or peak hours represents testing of undesired extremes. The former may provide a false sense of design integrity, while the latter may result in complete network disruption and failure.

Pilot

1. Test the Design.
2. Investigate what competitors will be proposing.
3. Write a script for a demonstration of the test results.
4. Practice the demonstration.
5. Schedule time with the customer and present the demonstration.

Prototype

Unless the customer has specified that the entire prototype must be built prior to migration, it can be more cost effective to utilize network simulation tools to determine how well the design can be expected to perform, then gradually migrate groups of users in phases as the new network is built.

1. Review customer requirements.
2. Define prototype scale.
3. Investigate competitors.
4. Develop a test plan.
5. Purchase and configure equipments.
6. Practice demonstrations.
7. Final tests and demonstrations.

By reviewing the work before doing anything else the consultant avoids hardware expenditures and commitment of human resources on items which might prove unnecessary later on. The review period can also be used to list ideas for demonstrations that will please the customer. Similarly, as the review proceeds, the consultant can identify those areas which might cause a negative reaction by the customer during the demonstration.

IOS Command

• show interfaces
  • Shows a variety of useful statistics for checking the health of an existing network and planning an upgrade to it.
  • Show the past five minutes of data input and output measured in packets and bytes.
  • One of the most frequently used to perform basic checks during troubleshooting, such as whether the interface or line protocol is up or down.
• show processes
  • The first line of output displays the utilization percentage in three intervals.
  • Useful for viewing the current status of routers to determine if a network structure meets the customer’s performance and scalability goals.

Documentation should first Respond to a customer's RFP (Request for Purchase). The Cisco's documentation standard could be included:

1. Executive Summary
   • Purpose of the project.
   • Brief design information.
   • Implementation issues
     • Business constraints.
     • Technical constraints.
   • Benefits of the solution.
   • Strategic recommendations.
2. Design Requirements
   • Customer requirements (network).
     • Identify security requirements.
     • Identify business constraints.
     • Characterize the new network traffic requirements of the Oracle patient record server.
     • Discover and review any plans for new applications.
     • Discuss how the client intends to manage the network.
   • Characterization of the existing network (current applications and protocols).
     • Number/type of servers.
     • Type of email in use.
     • The current functions of a link.
     • Number of users of a system.
     • Customer's policies and strategic directions do not apply to current applications. They apply in one way or another to the future.
   • Expectation for the new network.
   • High-level topology map of the current network.
   • High-level topology map of the proposed network.
3. Design Solution
   • Topology issues.
   • Hardware recommendations.
   • Network addressing scheme.
   • Routing protocols.
   • Bridging protocols.
   • IOS software features.
   • Network management solutions.
4. Summary
5. Appendix
   1. Project contacts.