Search For Downloads

Custom Search


The network planning and form methodology describes a process with 9 specific steps and a sequence for those activities. As mentioned it is an engineering life cycle that supports technical initiatives such as Windows migration, IP telephony and wireless produce to name a few examples. The methodology begins with examining company business requirements. It is absolutely important that you understand the company business model, business drivers and how they are growing from a business perspective. That will develop the foundation for a gain proposal that serves the business, technical and operational requirements of the company.


Any develop project starts with an idea of what the company does and what they need to attain from a business perspective. This begins with an idea of their business model, which really describes how their company works from an operational and business perspective to generate revenues and carve costs. Many vendors today have conducted their acquire return on investment (ROI) studies for modern implementations such as Unified Communications and Telephony. It is an effective sales tool that illustrates the cost benefits compared with investment over a specified period of time.

This is a list of some typical business drivers:

• slash Operating Costs

• Generate Revenue

• Client Satisfaction

• Employee Productivity

This is a list of some typical project business requirements:

• Budget Constraints

• Office Consolidations

• Company Mergers and Acquisitions

• Business Partner Connectivity

• Telecommuter Remote Access

• Implement unusual Offices and Employees

• current Data Center Applications

• lop Network Outage Costs

• Cost Effective Network Management

• Vendor Contracts


Now that you understand the basic business requirements of the company, you can settle the standard and specific execute requirements. The earn requirements process is focused on defining requirements from a technical perspective. Those requirements along with the business requirements will create the framework that is ragged to interpret infrastructure, security and management. form requirements are defined as standard and miscellaneous. The standard gain requirements are generic and describe those considered with many manufacture projects. Miscellaneous requirements are those that aren't defined with any of the standard requirements.

Standard build Requirements

• Performance

• Availability

• Scalability

• Standards Compatibility

• hasty Deployment


A network assessment is conducted after we have finished the business and create requirements of the company. A network assessment provides a fleet snapshot of the recent network with an examination of the infrastructure, performance, availability, management and security. That information is utilized for making effective strategy recommendations and create proposals to the client concerning specific information systems modifications. The network assessment model has 3 sequential activities, which are assessment, analysis and recommendations. The novel network is examined using five necessary surveys: infrastructure, performance, availability, management and security. When the surveys are completed, the information unexcited is then reviewed for trends, problems and issues that are negatively affecting the network.


After doing an network assessment we are ready to open selecting specific infrastructure components for the network make. This phase starts building the infrastructure with a specific sequence that promotes effective equipment selection and form. It is vital that you contemplate business requirements, get requirements and the network assessment when building your infrastructure.

The following numbered list describes the specific infrastructure components and their particular sequence.

1. Enterprise WAN Topology

2. Campus Topology

3. Traffic Model

4. Equipment Selection

5. Circuits

6. Routing Protocol Design

7. Addressing

8. Naming Conventions

9. IOS Services

10. Domain Name Services

11. DHCP Services


We must now justify a security strategy for securing the infrastructure. The need for enterprise network security shouldn't be ignored with the proliferation of the Internet. Companies are continuing to leverage the public infrastructure for connecting national and international offices, business partners and original company acquisitions. The security requirements and network assessment recommendations should drive the selection of security equipment, protocols and processes. It identifies what assets must be protected, what users are allowed access and how those assets will be secured.


This piece will explain a network management strategy for managing all equipment defined from infrastructure and security. It is critical to clarify how the equipment is going to be monitored and decide if the unusual management strategy is adequate or if modern applications, equipment, protocols and processes must be identified. Management components are then integrated with infrastructure and security to achieve building the proposed effect. These significant elements comprise any well-defined management strategy and should be considered when developing your strategy.

• 7 Management Groups

• SNMP Applications

• Monitored Devices and Events

STEP 7: PROOF OF understanding

All infrastructure, security and management components must now be tested with a proof of notion idea. It is vital to test the new invent, configuration and IOS versions in a non-production environment or on the production network with small disruption. Implementation of newer network modules at a router, for instance, could require that you change the new IOS version that is implemented. Making those changes could affect WAN or campus modules already installed at production routers. That is the precise value of doing a proof of notion and certifying that the unique equipment and IOS versions integrate with each plot as well as the network. The following list describes the advantages of doing a proof of thought with your network make. The proof of view test results should be examined and frail to modify modern infrastructure, security and management specifications before generating a perform proposal. The proof of understanding model suggested here involves prototype execute, equipment provisioning, defining tests, building equipment scripts and examining test results.

1. Prototype Design

2. Provision Equipment

3. justify Tests

4. accomplish Equipment Scripts

5. Review Test Results


With the proof of plan finished, you are now ready to fabricate a compose proposal for the do review meeting. Your intended audience could be the Director, CIO, CTO, Senior Network Engineer, Consultant or anyone that is approving a budget for the project. It is vital to point to your ideas with clarity and professionalism. If a presentation is required, power point slides work well and could be worn to serve concepts from the invent proposal document. The focus is on what comprises a standard invent proposal and the sequence for presenting that information.

The working form proposal is presented to the client after addressing any concerns from proof of plan assurance testing. The create review is an opportunity for you to point to your beget proposal to the client and discuss any issues. It is an opportunity for the client to identify concerns they have and for the develop engineer to interpret issues. The focus is to agree on any modifications, if required, and produce changes to the infrastructure, security and management before implementation starts. Business and manufacture requirements can change from when the project started which sometimes will necessitate changes to infrastructure, security and management specifications. Any changes should then go through proof of understanding testing again before final changes to the do proposal.


The final step will have us defining an implementation process for the specified earn. This describes a suggested implementation methodology of the proposed construct, which should have minimal disruption to the production network. As well it should be efficient and as cost effective as possible. As with previous methodologies there is a sequence that should be utilized as well.

Once the implementation is finished, there is monitoring of the network for any problems. develop and configuration modifications are then made to address any problems or concerns. The Book Network Planning and obtain Guide, is available at and


Search For Downloads

Custom Search