Planning Routing Services

1. Creating an Implementation Plan and Documenting the Implementation Planning Routing Services

2. Implementing Routing in the Network • Ad-hoc approach • Identify the need for the implementation • Implement routing in the network • Structured approach • Create an implementation plan • Implement the solution • Document the implementation

3. Structured Approach • Well-known models and methodologies that can aid in structuring the network implementation tasks include the following: • Cisco Lifecycle Services (PPDIOO) • IT Infrastructure Library (ITIL) • Fault, Configuration, Accounting, Performance, and Security (FCAPS) • Telecommunications Management Network (TMN) • Choose a model with elements that fit your organization as well as its business and technical needs.

4. Models and Tools • Select the implementation model • Adapt the model to your organization’s needs • Select the tools supporting the model • Create the implementation plan

5. Create the Implementation Plan • Identify the required information for the plan: • Network-specific information, activities, and tasks • Dependencies of the existing installation • Recommended resources • Create the implementation plan • Implement the solution • Verify the implementation • Create the documentation

6. Identify the Required Network Information • Existing topology, equipment, and software version • IP addressing plan • Scalability configuration (summarization, stub areas, and so on) • List of advertized networks • Link utilization • Metric requirements for primary and backup links

7. Identify Other Requirements • Site specific implementation requirements • Dependencies on existing installation • Configuration and verification commands • Implementation schedule and resources • Tools Online Resources

8. Create the Implementation Plan • Plan the work tasks • Select the site-specific tools and configurations • Configure and coordinate work with specialists • Create verification tests

9. Implementation Plan Documentation • Good documentation is a result of good processes and procedures. • Documentation must be: • Correct • Up-to-date • Accessible • Documentation must support: • Future upgrades and changes • Troubleshooting • Reporting

10. What to Document? • Network information • Tools • Resources • Implementation plan tasks • Verification tasks • Performance measurement and results • Screenshots and photos

11. Example: Implementation Plan • Identify the existing situation and requirements • Follow these steps to create an implementation plan: • Plan • Select the tools and resources • Coordinate the work with specialists • Verify • Interpret the performance results • Document the baseline, performance, and recommendation

12. Enterprise Network Topology Required

13. Identify Network Information and Requirements • Existing topology, equipment, and software version • IP addressing plan, configuration, and link utilization • Requirements for: • Connectivity and configuration • Protection and optimization • Security and remote access

14. Creation of the Implementation Plan • Create an implementation plan and document it • Project contact list • Location information • Tasks and detailed descriptions • Verification steps • Representation of the results

15. Summary • Using well known models and methodologies can aid in structuring the network implementation tasks and creating an implementation plan. • An implementation plan consists of the project and network overview, required tools, and information, as well as the implementation tasks. • The tasks in the implementation plan provide a detailed explanation of all actions that must be taken in order to configure the network according to requirements. • Good documentation is a result of good processes and procedures, and includes performance testing and documentation of results.