www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / Design / CCDP / Chapter 1: The Cisco Enterprise Architecture Model / PPDIOO Lifecycle Methodology

PPDIOO Lifecycle Methodology

In addition to knowing the essential features of a flexible network, a network designer should also follow a methodology that guides the entire lifecycle of the design process. In this regard, Cisco developed the PPDIOO methodology. PPDIOO is a succession of phases that every network implementation will experience during its operational lifetime.

From a business perspective, one common goal of the PPDIOO lifecycle and SONA is lowering the TCO. This can be achieved in the early phases of the process, in which technology requirements are evaluated and validated, and changes in the infrastructure and requirements for resources are properly planned. These early phases also improve network availability by using a solid network design and validating network operations. This process makes the business more agile as it establishes business requirements and technology strategies and adjusts them on a regular basis. It also speeds access to applications and services by improving the following features:

  • Availability
  • Scalability
  • Performance
  • Reliability
  • Security

PPDIOO is a six-phase model:

  1. 1.       Prepare
  2. 2.       Plan
  3. 3.       Design
  4. 4.       Implement
  5. 5.       Operate
  6. 6.       Optimize

1.2

Figure 1.2 – PPDIOO Model

The network lifecycle might not go through all of these six phases in the order shown in Figure 1.2 above without some type of iterative process, where the flowchart can be modified based on changing technologies, budget, infrastructure, business needs, or business structure. For example, after the implement phase, the network designer might need to go back to the Plan phase or the Design phase and make changes at that level. Unplanned actions can happen, especially in the Operate phase. The following sections offer a more detailed description of each phase in the PPDIOO lifecycle:

  • Prepare phase: The first phase of the PPDIOO lifecycle is the Prepare phase, in which business requirements and goals are established. The IT and the network/security infrastructure must always be in line with these business requirements and goals. In this phase a network strategy and high-level architecture to support that strategy are developed, and possible technologies that can support the architecture are identified. A business case must also be established to justify the budget for the overall network strategy. Representatives from the company’s board of directors (i.e., CIO, COO, etc.) might be involved in this phase.
  • Plan phase: The Plan phase, which includes identifying the decision makers and policy makers and determining the fundamental network requirements (i.e., who needs what services and when), is the most underutilized phase in the PPDIOO process. This phase involves information gathering and identifying the network/security requirements and the legislation to which the company or its customers must adhere (e.g., SOX, HIPAA, etc.). The network security system lifecycle must be carefully analyzed. This includes evaluating the company’s needs, risk analysis, security policies, guidelines and processes, the security system that is in place, and possible security system acquisitions in the future, such as a Cisco ASA device. The Plan phase also includes examining best practices and case studies and establishing security and response operations, monitoring, and compliance.

The network management processes must be considered in this phase because they are closely related to the network infrastructure. These processes include fault management, which detects and corrects specific problems; configuration management, which establishes a network baseline and develops a configuration tracking process (for networking appliances and devices); accounting management, which keeps track of circuits for billing of services; performance management, which monitors the network’s effectiveness in delivering packets; and security management, which includes Authentication, Authorization, and Accounting (AAA) and RADIUS/TACACS protocols.

The Plan phase characterizes the network and performs an analysis against best-practice architectures, and it looks at the operational environment overall. A project plan must be created to help manage tasks, identify responsible parties or individuals, set milestones, and identify the resources needed for the design and implementation of the project. This generated project plan must be followed through the remaining phases of the PPDIOO lifecycle.

Note:    Remember, security is a top-priority consideration in every phase.
  •  Design phase: The next phase involves designing the network according to the company’s policies, procedures, goals, available budget, and technologies. The design phase also might entail meeting with the policy makers, team leaders, and end-users to gather and analyze data and audit all of the key activities. Results from the Design phase are the basis for the approach taken in the next phase, which is implementing the network infrastructure. The focus of the Cisco design blueprint is on the first three PPDIOO phases – Prepare, Plan, and Design – among which the Design phase is the most complex; as such, this phase will be examined in detail in this chapter and in the rest of the book.
  • Implement phase: The competitive nature of business and the rush to market products and services forces many organizations to skip the first two phases and start with the Implement phase. Many times those companies get stuck in this phase because of the lack of planning and design. The Implement phase involves constructing the network infrastructure with the best affordable technologies based on all of the design specifications.

The Implement phase includes configuring the network using the Command Line Interface (CLI) or graphical tools (e.g., SDM, ASDM, etc.), installing new equipment, maintenance, and so on. Old devices might be replaced with new devices or some components (e.g., memory, operating systems, etc.) might be upgraded. The project plan must be followed during the Implement phase. Planned network changes should occur here and they should be communicated through control channels in meetings and receive the appropriate approvals.

Each step in the Implement phase should have a description, detailed implementation guidelines, a time estimate, and instructions for falling back to a previous state in case something goes wrong. The Implement phase will also combine additional reference information from RFCs, white papers, case studies, or other Cisco documentation. Any changes implemented in this phase should be tested before moving to the Operate phase, which is next in the PPDIOO lifecycle.

  • Operate phase: The Operate phase is the final proof that the network design was implemented properly. Performance monitoring, fault detection, and operational parameters will be confirmed in this phase. This will also provide the data used for the last phase.

This phase involves maintaining the day-to-day operational maintenance and health of the network infrastructure. This includes managing and monitoring the network components, analyzing and creating reports, routine maintenance, managing system upgrades (hardware, software, or firmware), managing the network’s performance, and identifying and correcting any network faults or security incidences. In analyzing the actual operations of the implemented network system, this is the final test of the design process. Network management stations (NMSs) should monitor the network’s health parameters through Simple Network Management Protocol (SNMP) traps (and certain thresholds reached) or other real-time monitoring solutions.

  • Optimize phase: Optimizing involves proactive and aggressive management and control over the network. Problems need to be identified quickly so troubleshooting can be engaged for fault detection. This phase is crucial because it is often followed by another planning or design session to redesign the implementation. This makes the first two phases all the more important. Much time and money could be spent in the Optimize phase if failures occur in the initial Plan and Design phases.

Optimization entails identifying and resolving issues before they move throughout the entire network. The Optimize phase might also generate a modified network design if too many problems appear in the Implement and Operate phases, which may require going back to the Design phase to solve those problems and implement new solutions.

The next section will focus on the primary goals of a network designer in terms of the Design phase and will analyze some of the design methodologies used in the PPDIOO process.

Note:    A seventh phase actually exists in the PPDIOO lifecycle: the retirement phase. This phase is implemented when equipment needs to be taken out of production.

A proven method for network design is necessary because it provides consistency to the design process, it offers a framework to work within, and it assures the network designer that no steps will be left out of the design process.

Design Phase Methodology

Like the other phases in the PPDIOO lifecycle, the Design phase is based on the requirements of the company as they align with the technical requirements. The Design phase includes the following features:

  • High availability
  • Assurance of redundancy
  • Failover and fallback mechanisms, both at the software level and the hardware level under network-enabled devices
  • Scalability (i.e., the ability to grow the project based on future growth models)
  • Security
  • Performance models and goals

These features can also be considered the goals of the network design phase. In this particular phase the team involved in the design process might request input from different areas of the company, from security professionals, or from various department leaders. The information gathered will be compiled, logical and physical diagrams will be created, and analysis and reports will be generated based on the conclusions. The initiated project plan will be modified, updated, and eventually finalized during the Design phase, as the next phase involves implantation and no more modifications should be made to the plan during that phase.

The design methodology is comprised of three steps:

  1. 1.       Identifying network requirements: This will be done with the help of the decision makers, the stakeholders, or the steering committee. Proposals for the conceptual architecture must be defined, followed by another Prepare phase.
  2. 2.       Characterizing the existing network: The existing network must be assessed to determine the necessary infrastructure and to meet the requirements defined previously. This step will define what resources exist and what resources need to be procured to meet the goals of the project plan. The network should be assessed based on functionality, performance, and quality.
  3. 3.       Designing the network topology and solutions: The network topology should be designed to meet all the business and technical requirements. A detailed design document will be generated in this phase, based on the project plan. This will include design solutions for the network infrastructure, Voice over IP (VoIP), security, content networking, and intelligent network services (e.g., Cisco NetFlow).

As mentioned earlier, the methodology in the Design phase focuses on the first three phases of the PPDIOO process: Prepare, Plan, and Design.

Identifying Network Requirements

Step one of the design phase methodology is to define the network requirements. This process can be carried out for a company or for a customer, and it is part of the Prepare phase in the PPDIOO lifecycle. This phase will identify both current and future applications and their importance in the organization. For example, e-mail is considered a critical system, but different applications have different priorities in the organization. These applications and services must be analyzed, along with the data plane traffic (i.e., traffic that moves from client to client or client to server, not traffic destined to network devices).

The next step is to see how the identified network applications and services map to the organization’s goals. These goals must align with the IT infrastructure, and they should include improving customer support in the case of Internet service providers (ISPs) or improving service desk support if internal users are served. Among the objectives that must be analyzed in this phase are decreasing costs and increasing competitiveness in a specific field or industry.

Next, the network designer must define the possible constraints to meeting the organization’s goals, including the following:

  • Budget constraints
  • Personnel constraints (the Prepare, Plan, and Design phases might have less resources allocated to them compared to the Implement and Operate phases)
  • Organizational policy constraints
  • Security policy constraints (open source solutions may be preferred to proprietary solutions, such as EIGRP)
  • Need for external contractors  and consultants
  • Scheduling constraints (i.e., timeframe)
Note:    The Design phase is one of the most commonly overlooked phases in the PPDIOO lifecycle. Failing to complete this phase might result in a waste of time and money in the end.

After defining the constraints, the technical goals must be defined. These should be aligned with the organization’s goals and they typically consist of the hardware and software needed to meet those goals. The response and throughput of the network should be improved while decreasing network failures and downtime that can affect corporate productivity. Network management should be simplified so results and analysis can be obtained quicker and more time can be allocated to incidents and troubleshooting instead of wasting it on management. The network security, availability, and reliability of mission-critical applications (e.g., e-mail or database) should also be improved. Outdated technologies should be updated according to a well-defined plan that should include milestones. Network scalability should also be improved as the system evolves and grows.

The technical goals mentioned above have some constraints, such as a lack of proper wiring capacity to support all of the applications and the lack of bandwidth (e.g., FastEthernet links instead of GigabitEthernet or 10-GigabitEthernet links). Other constraints would be having legacy equipment that does not support newer features or legacy applications that cannot be replaced and need to be accommodated within the network infrastructure. The following techniques must be mastered in the design process:

  • Scope assessment: The network designer must decide whether to start with a new network implementation or to build upon an existing network infrastructure. If the network implementation is new, step two of the design phase methodology (i.e., characterizing the existing network) can be skipped. Another important aspect is to decide whether to design the entire Enterprise Network or just a subset of it (e.g., specific departments), which is a modular network design concept. The technologies used must also be determined (e.g., LAN, WAN, VoIP, and security). The scope assessment technique is closely related to analyzing the Open Systems Interconnection (OSI) model because it must be determined whether the scope will cover just the Physical Layer, Layer 3 technologies (i.e., addressing, NAT, routing, etc.), or the Application Layer.
  • Gathering the necessary data: Design information is generally extracted from certain documents called RFPs (requests for proposals) or RFIs (requests for information). An RFP is a more formal document sent to vendors, suppliers, or strategic partners to ask them for proposals to help meet the organization’s needs by using their products or services. On the other hand, the RFI is a more informal document used to gather ideas and information from vendors and partners about a specific project or a specific area of implementation. These different proposals and requests are used for different reasons, including gathering information from existing and potential customers (initial requirements) and creating draft documentation that will describe the initial design requirements. This information must be verified by customers, management, and vendors. This data gathering process will be revised as necessary as things change within the organization. All of the documents (i.e., RFPs, RFIs, customer queries, etc.) can be modified based on the feedback received from the stakeholders.
  • Identifying the organization’s goals: Identifying the organization’s goals must always precede the process of establishing the technical goals and means. A network designer must understand what the management considers a success and a failure. In addition, customer expectations must be determined, along with the organization’s short-term and long-term goals. Most companies want to use IT and networking tools to lower their expenses, increase their applications and services, and obtain a competitive advantage. From a business standpoint, the infrastructure must be as flexible and as reliable as possible. Some of the common goals most companies have, no matter their size, are as follows:
    • Utilizing available resources efficiently
    • Maximizing profits and revenue
    • Reducing development and production cycles
    • Increasing competitiveness
    • Improving availability of data
    • Enhancing interdepartmental communications
    • Boosting customer support and customer satisfaction
    • Broadening the information infrastructure to stakeholders
  • Identifying the organization’s limits: This step usually covers four different categories:
    • Budget
    • Personnel
    • Policies
    • Timeframe

Unfortunately, network designers are often forced to find the most affordable solution instead of the optimal technical solution. This means that certain features might need to be compromised, such as scalability, manageability, performance, or availability. The available budget should include all the purchases, equipment, licenses, and training needed for the project. Budgets should be the final decision, but in most cases it is the primary consideration. Network designers must find areas in which they can make compromises to improve the overall goals of a specific project and obtain an effective solution.

Another limitation concerns the personnel involved in the project and what kind of expertise they have. Additional training might be necessary if they are not very technically skilled. The number of contractors and the level of outsourcing in the project should also be analyzed. For implementation and maintenance, an adequately trained technical staff must exist to fulfill the organization’s goals.

The organization’s limits are also dictated by its policies and procedures. This includes what vendors are being used, what standards are in place (open standards or closed standards), policies about protocols, and different applications.

The last category is the timeframe, particularly the deadlines that must be met. This limitation can make the network designer’s job either easier or more complicated. This includes how long it will take to deploy applications and to train users. This category is typically the concern of the project manager, who must create milestones for the design and implementation processes.

  • Identifying applications and services: The next phase is finding out what applications and services will be used. After discussions with key decision makers, a detailed analysis must be made that will take into consideration the following aspects:
    • Application category (e-mail, productivity, database, security, Web browsers, management, etc.)
    • Application choices for each category (low, medium, high, critical)
    • The application’s or service’s level of importance

All of this information can be identified during a brainstorming session with the stakeholders or team leaders to determine the necessary applications and their level of importance.

  • Reaching technical goals: This technique involves isolating and reaching the technical goals. The network designer should be an expert in determining what these goals should be and how to achieve them under the limitations of budget, personnel, time, procedures, and policies. Common technical goals include the following:
    • Maximize performance and productivity
    • Enhance security
    • Achieve reliability for critical core applications (99.9% for most organization)
    • Reduce downtime
    • Update obsolete hardware and software (depending on budget constraints)
    • Boost network scalability (modular solutions)
    • Simplify network management
  • Identifying technical restraints: A successful design engineer must recognize the technical obstacles and restraints in the network design. This usually falls under the following categories:
    • Limitations of existing equipment (updates might be required)
    • Availability of bandwidth (mostly related to WAN connections)
    • Compatibility of applications (the use of a single vendor might be required)
    • Adequacy of trained personnel (more training might be required)

 

Characterizing the Existing Network

Step two in the design phase methodology is characterizing or classifying the network. This is where the network designer identifies the major features and characteristics of the network and defines the tools used to analyze, audit, and monitor network traffic. Information gathering always occurs in an early phase in any multi-step process, such as developing applications or designing the security model. The information gathering process consists of three steps:

  1. 1.       Compile all existing information and documentation.
  2. 2.       Conduct a network audit.
  3. 3.       Perform traffic analysis.

Information gathering involves compiling all of the existing information in any form of documentation. This must happen first to avoid duplicating tasks, especially those that have already been completed by somebody else.

The second step is conducting a network audit with as much pre-information as possible. The network audit might need to be performed by a Certified Information System Auditor (CISA) or other certified professionals. Network auditing tools should be used along with the necessary documentation and network management tools (e.g., Cisco Prime Tivoli) that will provide information about the network’s device inventory, configuration, and status. The audit must provide information about the version of the software used, the Internetwork Operation System (IOS), the management software (e.g., ASDM, SDM, etc.), the configuration on the devices, Layer 1 and Layer 2 information and topologies, interface speeds, CPU and memory utilization, Wide Area Network (WAN) types, and Virtual Private Network (VPN) types. Manual auditing of the network devices will involve using a wide variety of “show” commands on Cisco devices, such as “show tech-support” (which will generate a huge report on individual systems), “show version”, or “show running-config”. Other tools that might be used in the auditing phase are as follows:

  • Packet sniffers (e.g., Wireshark)
  • SNMP tools
  • Network analysis tools:
    • Network-Based Application Recognition (NBAR) from Cisco, an IOS tool that helps identify well-known applications, protocols, and services
    • NetFlow (a very popular solution that runs on Cisco and third-party devices), a reporting tool that records information about traffic patterns that cross devices

A network checklist is useful in the auditing phase. This should include available topology segments, IP addressing schemes, and WAN connections.

All of the tools presented above can be used in the third step of the information gathering phase, which is performing traffic analysis. In this phase the designer should investigate the following:

  • Network response time
  • Available bandwidth
  • QoS mechanisms used, especially when using VoIP
  • Security features implemented, such as segmenting the network using Virtual Local Area Networks (VLANs)

Network designers are often in a situation where the network infrastructure is already in place and the new design will cover only the restructuring or the upgrading of the existing network. The network designer must review the existing network documentation and diagrams that the company has, get input from different IT personnel, perform some kind of network auditing, define and describe the existing topology, and analyze the traffic. Five different components that describe the network are as follows:

  • Layer 3 topology
  • Layer 2 topology
  • Network services
  • Applications
  • Network modules

The first step in the process is to obtain a Layer 3 topology of the network from the existing documentation or diagrams. Analyzing Figure 1.3 below, the Core Layer (backbone) of the network is made up of high-end routers. Other network areas include the internal server zone, the network management area, the WAN connection, the Public Switched Telephone Network (PSTN) connection, the Internet connection, and the Demilitarized Zone (DMZ, for Web servers).

1.3

Figure 1.3 – Network Components

Important information that can be gathered at Layer 3 are the routing protocols (e.g., Enhanced Interior Gateway Routing Protocol – EIGRP and Open Shortest Path First – OSPF) used in the network core or at the edge, the Internet connection capacity, and applications that are accessed through the Internet.

The Layer 2 topology can be a separate map or it can be built by adding elements onto the existing Layer 3 topology. The recommendation is to isolate and document the network areas based on the shared bandwidth capacity (e.g., GigabitEthernet, FastEthernet, etc.) and the switching infrastructure used at different layers (Access, Distribution, or Core). Layer 2 technologies also include the WAN connections (e.g., Frame Relay or Asynchronous Transfer Mode – ATM) that connect the company’s branch offices.

The next step is to isolate the network services and map them onto a separate document that should include the following:

  • Domain name services (Domain Name System – DNS)
  • Network management services (SNMP, Trivial File Transfer Protocol – TFTP)
  • Security services (Terminal Access Controller Access Control System – TACACS, Access Control Lists – ACLs – on the routers, IP Security – IPsec, Network Address Translation – NAT)
  • Routed protocols (Internet Protocol – IP, Internet Packet Exchange – IPX)
  • Routing protocols (EIGRP, OSPF)
  • Quality of Service
  • Multicast services

The fourth aspect includes the applications that run on the network:

  • File sharing applications (File Transfer Protocol – FTP)
  • Web applications
  • E-mail applications
  • Instant Messaging
  • Unified Communications
  • Microsoft Exchange

Once the Layer 2 and Layer 3 network topologies, the network services, and the applications have been identified, the information gathered must be divided into logical submodules to obtain a modular design. Based on Figure 1.4 below, the following submodules might be of interest:

  • Backbone
  • Network management
  • PSTN access
  • Corporate Internet
  • Public access
  • WAN
  • Internal server farm
  • LAN (Access Layer)

1.4

Figure 1.4 – Modular Network Map

The next step is identifying the components and properties for each network device (e.g., router, switch, firewall, etc.), such as the following:

  • Device model
  • CPU/memory
  • Resource utilization
  • IOS version
  • Device configuration
  • Routing tables
  • Interfaces
  • Modules/slots

This information can be obtained from the IT staff or it can be gathered individually by accessing the NMS and connecting to each network device in the topology.

Note:    The process of gathering configuration and performance information about a specific network device is also called device auditing. The Cisco solution for network auditing and monitoring is called CiscoWorks.

A network designer might also need to use network analysis tools to find information about traffic flows, Quality of Services techniques, security information, traffic profiles, and the way certain applications and protocols use the available traffic. Some of the tools that can be used in this regard are Cisco NetFlow analyzer tools or the Wireshark packet capturing tool (sniffer). The screenshot below is an example of a Wireshark FTP capture session:

1.5

Figure 1.5 – FTP Packet Capture Session

The last step in describing the existing network is combining the created Layer 2 and Layer 3 topology maps with the discovered services and applications and creating a summary report that can be presented to key decision makers and policy makers within the organization. This document can include the following:

  • Number and types of devices
  • IOS version used
  • Memory capacity and upgrade recommendations
  • Discovered points of congestion and recommendations
  • Suboptimal paths and recommendations
  • Routed and routing protocols and upgrade recommendations
  • Survey of applications and services
  • Impact assessment (cost, personnel, time)

 

Designing the Network Topology and Solutions

The third step of the design phase methodology is designing the network topology and solutions. An effective approach for this step is a structured design (see Figure 1.6 below) that allows the development of a complete system, with optimum design at the lowest cost, while meeting all the company’s requirements in the following areas:

  • Performance
  • Functionality
  • Flexibility
  • Capacity
  • Availability
  • Scalability

1.6

 

Figure 1.6 – Designing the Network Topology and Solutions

The network designer’s goal in this phase should be to develop a systematic approach that takes into consideration the organization’s needs, goals, policies and procedures, technical goals and constraints, and the existing and future network infrastructure. This includes physical models, logical models, and functional models.

The best approach in this phase, and the one recommended by Cisco for a medium-sized network to a large Enterprise Campus design, is the top-down approach. Using this approach presents an overview of the design before getting down to the design details. This entails beginning with the Application Layer (Layer 7) of the OSI model and then moving down through the Presentation Layer, the Session Layer, the Transport Layer, the Network Layer, the Data-link Layer, and, finally, the Physical Layer (Layer 1).

The network and physical infrastructure should be adapted to the needs of the network applications and services. In other words, do not choose network devices or hardware and software technologies until the requirements for the applications are fully analyzed and met. The concepts of SONA and IIN should also be incorporated into the design process, combined with the organization’s requirements. This includes considering organizational and technical constraints.

The top-down approach is usually a very time-consuming process and is a bit more costly, but it is preferred over bottom-up solutions, where typically the design is based on previous experience and a quick fix or solution. The problem with the bottom-up approach is an inappropriate design in the medium to long term, and the organization’s requirements and constraints are not included. This would cause trouble and possible process rollback during later project phases.

Note:    To learn more about the Cisco top-down network design approach, read Top-Down Network Design, 3rd Edition, published by Cisco Press (2010).

Figure 1.7 below is an example of the top-down network approach methodology:

1.7

 

Figure 1.7 – Example of the Top-Down Approach

Figure 1.7 starts at the top with the applications and services, which includes the Application, Presentation, and Session Layers. Based on the requirements for the applications and the way they match the organization’s goals, a network infrastructure design and an infrastructure services design to meet the application requirements of the organization should be applied. This includes the data, the types of traffic and services, and what types of design and network services will meet the needs of those applications.

Once the goals are met, the network should be modularized, taking a modular approach and including the Core, Distribution, and Access Layers of the network, the data center, the server farm, the branches, and the Internet connectivity layer. Next, apply the decisions made for the infrastructure and services to different modular areas of the network by dealing with certain segments of the network at a time.

The next step is to take this modular implementation and create logical subdivisions that will be addressed on a project-by-project basis. Looking at them from a project management or steering committee standpoint, these will be logical subprojects. Different subprojects might exist for the following circumstances:

  • Choosing the technology, acquisitions, and provisioning
  • Physical topology design (implementing the design in different layers)
  • Addressing the design scheme, including NAT solutions
  • Routing selection and design
  • Quality of Service design (traffic management)
  • Security design
  • IP multicast design (for video and audio streaming)
  • IPv6 provisioning design

 

Design Process: Final Steps

The final steps of the design process within the PPDIOO lifecycle include the following:

  • Plan the network implementation process: This step involves a high degree of documentation and diagramming. A step-by-step procedure must be established for each aspect of the modular design. This must be well documented and detailed, must describe every step (with references to the different documents, diagrams, or reports created), and must include a detailed guideline for the implementation of the network. In case of a pitfall or a design failure, the network designer must have a rollback plan in place. In addition, an estimation of the time needed for the implementation process should be provided, and project managers and other staff members must be consulted. Testing should be performed at every step in the process, and complex procedures must be broken down into smaller pieces using teams of people. This might be the case when implementing complex technologies like IP Telephony.
  • Pilot and prototype testing: The network designer must be sure to verify the design once this step is completed. This can be done with a prototype or a pilot network, meaning a sample implementation that will help test the solution. Depending on the solution, some organizations might implement both pilot and the prototype testing, or just one of them.

A pilot site is a live location that serves as a test site before the solution is deployed. This is a real-world approach to discovering problems before deploying the network design solution to the rest of the internetwork. A pilot network is used to test and verify the design before the network is implemented or launched. The design should also be tested on a subset of the existing network infrastructure. The pilot test might be done within a particular module or a particular building or access area before extending the network to other areas.

A prototype is a subset of the full design tested in an isolated environment, unlike the pilot test, which is implemented in the production network. The benefit of using a prototype is that it allows full testing of the network design before it is deployed, without having any negative effects on the production network. A prototype test is often used before applying a redesign to an existing network. The results of the pilot or prototype tests will be documented in a proof of concept section in the final design document.

Like in other phases, the company’s requirements must always be at the top of the priority list. The prototype or pilot network implementation has two possible results: it is either successful or it fails the design goals. If the prototype does not meet all of the objectives, corrections must be made. A success means it is proving the concept of the actual network design.

Successful testing will prove that the Plan, Preparation, and Design phases are on target and will facilitate moving on to the Implement phase. Sometimes a success in this step concludes the network designer’s job, who will then hand over the project to the personnel or outside consultants who will handle the implementation of the hardware and software solutions.

A failure in this phase does not mean the entire project has failed. It simply means that some corrections must be made to the actual design, after which the prototype/pilot test must be repeated until it is considered a success. Any failures that happen during the testing phase require going back to the iterative process and correcting the planning, preparation, or design aspects and repeating the pilot/prototype test to correct any weaknesses that might have a negative effect on the implementation process.

  • Fully document the design: The design document, which is complementary to the planning document, is the final document that will be created. The design document should include the following components:
    • Introduction (description of project goals)
    • Design requirements, including the organizational and technical constraints
    • Existing network infrastructure (logical Layer 3 topology diagram, physical topology diagram, audit and analysis results, routing protocols, applications and services summary, device list, configuration, and description of any issues identified)
    • Design section (specific design information, logical topology design, physical topology design, IPv4 and IPv6 design, routing protocols, and security configurations)
    • Proof of concept (conclusion of the pilot/prototype testing phase)
    • Implementation plan (useful in the next phase of the PPDIOO process; presents the steps that must be followed by the implementation team to successfully implement the new system or the network upgrade)
    • Appendix (white papers, case studies, additional information, and configurations)

An example of the design document structure is presented below:

1. Introduction
2. Requirements for the Design
3. Existing Infrastructure
3.1     Layer 1 Topology
3.2     Layer 2 Topology
3.3     Layer 3 Topology
3.4     Audit Results
3.5     Recommendations
4. Intelligence Services
4.1     Applications
4.2     Services
4.3     Analysis
4.4     Recommendations
5. Solution Design
5.1     Design Summary
5.2     Design Details
5.3     Implementation Details
5.4     Recommendations
6. Prototype Network
6.1     Prototype Details
6.2     Prototype Results
6.3     Recommendations
7. Implementation Plan

This document might be cross-referenced with other documents used during the design process to fully describe the proposed solution.

To summarize, the design steps presented below in Figure 1.8 are structured as an eight-step methodology:

1.8

Figure 1.8 – Eight-Step Design Methodology

From a technical standpoint, in the eight-step design methodology, step 6 and step 7 represent the separation between the network designers and the network engineers who will take care of the network implementation process. In context of the CCDP, only the first six steps are of interest. Step 7 and step 8 should be of interest for implementation engineers, not for network designers.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.