Overview
The network preparing and style methodology describes a procedure with 9 certain methods 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 design to name a couple of examples. The methodology begins with examining business small business needs. It is absolutely critical that you know the firm home business model, business drivers and how they are growing from a company perspective. That will create the foundation for a style proposal that serves the business enterprise, technical and operational needs of the firm.
STEP 1: Enterprise Specifications
Any style project starts with an understanding of what the organization does and what they have to have to accomplish from a home business perspective. This begins with an understanding of their company model, which truly describes how their business works from an operational and organization perspective to produce revenues and decrease expenses. Lots of vendors these days have conducted their own return on investment (ROI) studies for new implementations such as Unified Communications and Telephony. It is an effective sales tool that illustrates the expense advantages compared with investment more than a specified period of time.
This is a list of some common enterprise drivers:
• Cut down Operating Expenses
• Create Income
• Client Satisfaction
• Employee Productivity
This is a list of some standard project business specifications:
• Budget Constraints
• Workplace Consolidations
• Company Mergers and Acquisitions
• Business Partner Connectivity
• Telecommuter Remote Access
• Implement New Offices and Workers
• New Information Center Applications
• Lower Network Outage Costs
• Cost Productive Network Management
• Vendor Contracts
STEP 2: Design Needs
Now that you understand the simple organization specifications of the firm, you can establish the normal and distinct style requirements. The design specifications method is focused on defining needs from a technical perspective. Those specifications along with the home business specifications will build the framework that is utilized to define infrastructure, security and management. Design requirements are defined as common and miscellaneous. The common design needs are generic and represent those deemed with various style projects. Miscellaneous specifications are those that are not defined with any of the standard specifications.
Standard Design Requirements
• Performance
• Availability
• Scalability
• Standards Compatibility
• Rapid Deployment
STEP 3: NETWORK ASSESSMENT
A network assessment is conducted immediately after we have finished the business enterprise and design requirements of the business. A network assessment gives a quick snapshot of the current network with an examination of the infrastructure, efficiency, availability, management and security. That info is utilized for producing helpful strategy recommendations and style proposals to the client concerning particular info systems modifications. The network assessment model has 3 sequential activities, which are assessment, analysis and recommendations. The existing network is examined using five main surveys: infrastructure, efficiency, availability, management and security. When the surveys are completed, the facts collected is then reviewed for trends, challenges and issues that are negatively affecting the network.
STEP 4: INFRASTRUCTURE Selection
Immediately after doing an network assessment we are ready to start off deciding on specific infrastructure components for the network design. This phase begins making the infrastructure with a distinct sequence that promotes efficient equipment selection and design. It is valuable that you give consideration to business requirements, style needs and the network assessment when making your infrastructure.
The following numbered list describes the precise infrastructure components and their particular sequence.
1. Enterprise WAN Topology
two. Campus Topology
3. Site visitors Model
4. Equipment Selection
five. Circuits
6. Routing Protocol Design
7. Addressing
8. Naming Conventions
9. IOS Services
10. Domain Name Services
11. DHCP Services
STEP five: SECURITY Method
We need to now define a security technique 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, organization partners and new enterprise acquisitions. The security needs and network assessment recommendations ought to drive the selection of security equipment, protocols and processes. It identifies what assets need to be protected, what users are allowed access and how those assets will be secured.
STEP 6: NETWORK MANAGEMENT Method
This section will define a network management method for managing all equipment defined from infrastructure and security. It is important to define how the equipment is going to be monitored and identify if the present management method is adequate or if new applications, equipment, protocols and processes ought to be identified. Management components are then integrated with infrastructure and security to finish making the proposed design. These main components comprise any nicely-defined management technique and should really be considered when developing your method.
• 7 Management Groups
• SNMP Applications
• Monitored Devices and Events
STEP 7: PROOF OF Concept
All infrastructure, security and management elements should now be tested with a proof of idea strategy. It is necessary to test the existing design, configuration and IOS versions in a non-production atmosphere or on the production network with restricted disruption. Implementation of newer network modules at a router, for instance, could require that you adjust the existing IOS version that is implemented. Producing those changes could impact WAN or campus modules already installed at production routers. That is the actual value of carrying out a proof of concept and certifying that the new equipment and IOS versions integrate with every single device as nicely as the network. The following list describes the positive aspects of carrying out a proof of idea with your network style. The proof of idea test results must be examined and utilised to modify present infrastructure, security and management specifications ahead of producing a design proposal. The proof of concept model recommended here entails prototype design, equipment provisioning, defining tests, making equipment scripts and examining test results.
1. Prototype Design
two. Provision Equipment
three. Define Tests
four. Create Equipment Scripts
5. Review Test Results
STEP 8: Design PROPOSAL/Assessment
With the proof of concept finished, you are now prepared to create a design proposal for the design evaluation meeting. Your intended audience could be the Director, CIO, CTO, Senior Network Engineer, Consultant or any individual that is approving a spending budget for the project. It is crucial to present your concepts with clarity and professionalism. If a presentation is needed, energy point slides function well and could be made use of to support concepts from the design proposal document. The concentrate is on what comprises a common design proposal and the sequence for presenting that information and facts.
The operating design proposal is presented to the client just after addressing any concerns from proof of idea assurance testing. The design review is an opportunity for you to present your design proposal to the client and talk about any issues. It is an opportunity for the client to identify concerns they have and for the design engineer to clarify issues. The concentrate is to agree on any modifications, if necessary, and make changes to the infrastructure, security and management prior to implementation starts. Home business and style needs can modify from when the project started which at times will necessitate adjustments to infrastructure, security and management specifications. Any alterations should certainly then go by way of proof of idea testing again prior to final modifications to the design proposal.
STEP 9: IMPLEMENTATION
The final step will have us defining an implementation method for the specified style. This describes a suggested implementation methodology of the proposed style, which need to have minimal disruption to the production network. As properly it ought to be effective and as cost successful as feasible. As with previous methodologies there is a sequence that will need to be utilized as effectively.
As soon as the implementation is completed, there is monitoring of the network for any issues. Style and configuration modifications are then made to address any problems or concerns. The Book Network Organizing and Design Guide, is accessible at amazon.com and ebookmall.com
Copyright 2006 Shaun Hummel All Rights Reserved
No comments:
Post a Comment