1 / 15

King Fahd University of Petroleum And Minerals Computer Engineering Dept. COE – 444

King Fahd University of Petroleum And Minerals Computer Engineering Dept. COE – 444 Internetwork Design & MGT A structured Data Network Design and Upgrade for CCSE Network “Server Placement”. Group#11. Muhammad Al-Abdul-Hadi 205169 Ahamd Mosaic 208601

luke-hubbard
Download Presentation

King Fahd University of Petroleum And Minerals Computer Engineering Dept. COE – 444

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. King Fahd University of Petroleum And Minerals Computer Engineering Dept. COE – 444 Internetwork Design & MGT A structured Data Network Design and Upgrade for CCSE Network “Server Placement”

  2. Group#11 • Muhammad Al-Abdul-Hadi 205169 • Ahamd Mosaic 208601 • Amjad Muslih 208503 • Haider A. Al-Mubarac 203749 • Muhammad AL-Saeed 995238

  3. OUTLINE • Recommendations for Server Placement • Main Factors in Security Aspect • New Proposed Design • Problems Faced

  4. Recommendations for Server Placement • CCSE-PSRV2 (Student print server, Antivirus server) • Remove it from VLAN 67(administration). • Put it in VLAN 172 (Student). • VLSI (COE Faculty Printer Server) • no need to place in the shared VLAN • suggest to place it in Faculty subnet, VLAN 65. • place it on 3Com335-1-156 since it connects all faculty switches together.

  5. Recommendations for Server Placement (Cont.) • CCSE-DBP2 (Student publishing and database platform) • used mainly by students. • Remove from VLAN67 • Place it in students VLAN172 • CCSE-DBP1 (Database platform; publishing setup) • Remove it from VLAN67 • place on VLAN 65 • assuming it will be used mainly by faculty.

  6. Recommendations for Server Placement (Cont.) • MAKKAH (CCSE web server): • Remove from VLAN64 • Place in VLAN172 • frequently accessed by student • CCSE-MATERIAL (MatLab Server): • traffic of 51% (peak hour). • Replace the 100 Mbps with 1 Gbps & connect it to switch 3Com335-1-102/103. • CCSE-SOFTWARE: • traffic of 45% (peak hour). • replace the 100 Mbps with 1 Gbps. • Upgrade server

  7. Recommendations for Server Placement (Cont.) • KUZAMA, Bareed (mail server): • Old Workstation used as a server. • Upgrade it to a higher performance server

  8. Recommendations for Server Placement (Cont.) • Soldier(POP3 Server, Mailbox Server, CCSE Network Time server): • Peak traffic 84.4%(high) • seems to be a loaded all the time. • Keep it in faculty VLAN65 • Duplicate one to VLAN172

  9. Main Factors in Security Aspect • Physical Access. • Physical place restricted to authorized people. • Administrative Delegation. • Deciding who will have administrative authority over the server • User Authentication. • To verify that users are who they declare themselves to be. • User Authorization. • Regulating what users have access to log on and what server resources they can access.

  10. Main factors in security aspect • System Privileges and Restrictions. • Setting the access permissions to the applications. • Application Privileges and Restrictions. • Access to the applications on a server should be restricted to a subset of users based on their job function. • System Auditing. • Needed for monitoring effectiveness of the configuration. • Security Patches Management. • Poor patch management can be particularly damaging to a server environment.

  11. Security • From the above assessment it can be seen that the security used in CCSE servers is good and does not need any further improvement.

  12. VLAN 64 (Administration and Monitoring) VLAN 172 (Student/Labs)

  13. VALN 64 (UNIX Servers)

  14. Problems • Lack of information: • Who uses what? • How many users use the application? • How frequently the application is needed by users? • Delay in getting the requiredinformation. • The traffic analysis doesn’t help in making decisions.

  15. ?

More Related