Accounting & Financial Services Corporation

1. Accounting & Financial Services Corporation Accounting & Financial Services Network Design By Michael J. Smith Nov. 14, 2011

2. Network Objectives • Security. Prevent unauthorized access. • Speed. Bandwidth must meet demand. • Reliability. Contain redundancy. • Scalability. Sustain scalability without the need to rebuild entire network.

3. Design Assumptions • AFS does not have a network. • Departments reside on a separate floors. • AFS does not share buildings with any other businesses. • AFS wants to use MS Windows & Office. • 100Base-TX for LANs and 1000Base-FX for the WAN will suffice. • The network design must only ensure that it is logically secure.

4. Network Needs • Accommodate file sharing, including text files, graphic-heavy files, and database information. • Accommodate 1,600 users across seven locations. • Accommodate web-based applications. • Prevent authorized access.

5. AFS Network Design One wide-area-network connecting all the offices to AFS headquarters using a star architecture. A backbone network that will connect all the LANs in each branch office to the WAN. Several department local-area-networks that will connect workstations in departments together. AFS Network will not be meshed to save money.

6. AFS Wide-Area-Network • Each location has a router. • Each location is connected to AFS HQ using 1GbE over fiber cables. (1000Base-FX). • Each location has a media converter. • All Internet traffic is routed to AFS HQ to limit entry points. • The Dublin office contains redundancy, should the connection to AFS HQ experience problems. • Both AFS HQ and Dublin have firewalls and anomaly detection systems. • Each location has a L3 switch.

7. AFS WAN Diagram

8. AFS Branch Office BN Diagram

9. AFS Backbone Network • 100Base-TX over Cat 5e will be used in the AFS BN. • Each AFS location needs one L2 switch for each department LAN and one for the DMZ. • Each location needs one L3 switch to connect core layer to distribution layer. • The BN will not contain any security beyond the DMZ, as security will be handled by the anomaly detector and firewall at HQ.

10. AFS HQ BN Diagram

11. AFS HQ MDF Diagram • HQ will contain a firewall and anomaly detector. • HQ will have a web server in its DMZ. • HQ has two more departments than branch offices.

12. AFS HQ MDF Diagram

13. AFS HQ Local-Area-Network • 100Base-TX over Cat 5 will be used. • Department LANs will be dedicated server networks with a star topology. • Multipoint circuits will be employed.

14. AFS HQ LAN Diagrams

15. AFS HQ LAN Diagrams

16. AFS HQ LAN Diagrams

17. Branch Office MDF • The Dublin office will contain network redundancy. • Each MDF will contain one L3 switch and six L2 switches. • Branch Office department LANs will have DMZs that contain email server.

18. AFS Dublin MDF Diagram

19. Branch Office LANs • Each department has its own database, file, and print server. • Department LANs will require a patch panel and an L2 switch.

20. Dublin Office LAN Diagrams

21. Dublin Office LAN Diagrams

22. Dublin Office LAN Diagram

23. Location IP Addresses

24. IP Addressing • IP addresses were assigned consistently across branch offices. • Should allow technicians to identify servers by IP address. • For example: A server with IP 150.15.84.10 is located in Burbank, CA. • The “8” in “84” tells us it is in Burbank because it falls in the range 150.15.80.1 – 150.15.95.254. • The “4” in “84” tells us that the server belongs to the Customer Service department because it falls in the range 150.15.84.1 – 150.15.84.254. • The “10” tells us that it is a file server because all branch office file servers end in 10.

25. IP Addresses Cont’d.

27. AFS Network Cost Total Network Cost for Configuration #1: $14,173,439.48 Total Network Cost for Configuration #2: $15, 370,624.86