Deploying Network Modules – Resiliency Module

A. Scenario: The Great Canadian Widget Company (GCWC) is the top manufacturer and distributor of widgets in the country. They have a Head Office in Toronto with Primary Manufacturing and Distribution facilities in addition to company-wide Executive and Engineering resources. There are 4 Regional Offices housing secondary manufacturing, distribution, warranty and second line management responsible for each of 4 regions: Calgary (Western Canada), Montreal (Central Canada), Halifax (Eastern Canada) and Head Office acting as a Regional (SW Ontario). Each region is responsible for branch sales and customer support offices as follows: Toronto Head Office Serves as Regional Office (SW Ontario) for: Branch: Hamilton, Kitchener, London, Windsor Montreal – Central Region Branch: Ottawa, Thunder Bay, Sudbury, Sherbrook, Quebec City Halifax – Atlantic Region Branch: Fredericton, Charlottetown, St John’s Calgary – Western Region Branch: Vancouver, Kelowna, Edmonton, Regina, Winnipeg The company is retiring the old, full mesh Frame Relay network and building new network infrastructure to run over the Internet using VPN technology. The company will keep its existing high speed Private Line that connects Toronto Data Center to the back up / mirror data centre in Markham, Ontario. You are to design the network layout prior to acquiring any new ISP services, facilities, equipment or software. B: The work! 1. Using cloud modules create a module inventory suitable for Head Office, Regional and Branch Offices. Each module will have a control plane (routes) and data plane (switches) so you should come up with some Cisco models to use in these architectural positions. The User Connection module should include examples of end-user equipment including, at the minimum, a desktop PC, a laptop PC, a wireless access-point and a VoIP phone. Ensure that the following module types are noted: •User Connection •Service Connection •Traffic Aggregation •Traffic Forwarding •Control Plane Aggregation INFO-6033 Enterprise Network Design 2. Create and ensure that the following functional VLANs can switch for departments: Management (includes Accounting and HR) (by Region only) Sales and Marketing (shared between all locations) Customer Service (shared between all locations) Manufacturing / Engineering (by Region only) Distribution and Product Service (by Region only) Add VLANS for the functions of Voice (by Region), Data Systems – all hosts, WiFi (by Region), Data Back- up – all hosts. Document all these VLANs on the diagram 3. Provide a conceptual layout using Visio to show how the cloud modules can service each location, is location type sensitive (HO, Region, Branch, Data Centre (4 Visio diagrams), and are utilizing the standard module types you designed in Step 1 above. Identify the Failure Domains where apparent for each diagram (may be more than 1) 4. Create one more Visio diagram that will act as an overview high-level drawing slide for your “reveal” meeting that shows the existing IT staff that they still have 3 layers in the network and the redundancy and security in your design (Layers within layers). This diagram must contain all components from the beginning of Part 3 (HO, Region, Branch and Data Centre) cloud modules can be used represent them at this point. Use the minimum number of redundant paths to provide resiliency without full mesh connections. The company does not require full redundancy to Branches, but does between Regions and to HO. Recommend the routing protocols you feel are necessary to support your design. 5. Create a simple PowerPoint presentation for Management and IT staff showing a high-level overview of your design. It should logically walk through the plan from module to site to whole company and include the important aspects such as redundant links, modularity for simple expansion and proof of your 3-tiered design. Diagrams are good! You can probably use mostly just the diagrams from your Visio document but be creative if you wish