This is a case study-based work and not coding based. Please read the scenario and answer accordingly.

This is a case study-based work and not coding based. Please read the scenario and answer accordingly.

This is a case study-based work and not coding based. Please read the scenario and answer accordingly.

Complete the following steps: Step 1 Hospital Omega is a nearby hospital that has been having financial difficulties. It is facing large licensing and application development costs to bring its financial and other applications up to date. To cut costs and stabilize finances, Hospital Omega will merge with ACMC. All data services will move to the ACMC data center and gradually migrate to the modern applications that ACMC already has in place. The Hospital Omega network was deployed between seven and ten years ago, and in many cases, the equipment vendors no longer exist. The following are some details about Hospital Omega: - Hospital Omega does not use DHCP. - Hospital Omega consists of one building of ten floors, with fewer than 250 computers per floor. - Hospital Omega uses static routes. - The Hospital Omega network is flat and Layer 2 switched. The switching equipment is from a third-party vendor and is seven and ten years old. - The Hospital Omega network uses old copper and fiber cabling that was added by various people in a random manner over the years. For any given closet, about 50 percent of the cable (copper or fiber) goes to unknown locations and is of unknown quality. - Servers are scattered around the building in random closets near the department that originally installed them. - Hospital Omega accesses the Internet via the University Research Group. Figure 10-25 shows the Hospital Omega network. Figure 10-25 Hospital Omega Network Figure 10-25 Hospital Omega Network The CIO wants a design to modernize the Hospital Omega network and allow robust access to the ACMC data center. Hospital Beta is another nearby hospital. ACMC and Hospital Beta overlap in several areas of medical expertise and feel that pooling talent and facilities should lead to better depth of medical expertise and better patient care. Sharing financial and other applications should also reduce overhead costs. The following are some details about Hospital Beta: - Hospital Beta uses DHCP. - Hospital Beta consists of four buildings. each with four large floors (with fewer than 250 Ethernet users - Hospital Beta uses DHCP. - Hospital Beta consists of four buildings, each with four large floors (with fewer than 250 Ethernet users and ports each). Each floor uses eight 24-port Cisco Catalyst 3560 switches in intermediate distribution frame closets, with dual uplinks to the distribution layer switches. The data center and Internet complex is on one floor of one of the four be - Each building uses two Cisco Catalyst 6506 switches at the distribution layer. The switches are dualhomed via single-mode fiber at 10Gbps to the core switches. - The two Cisco Catalyst 6506 core switches are interconnected with 10-Gbps links and have dual connections to two Cisco Catalyst 4948 switches for the servers. - The campus network is based on high-speed Layer 3 Cisco switches. - Wireless is supported using Cisco WLAN controllers (WLC). - The hospital has a DMZ, dual firewalls in each of two layers, IPS monitoring for the DMZ, and so forth. - Cisco IP telephony is in place. - Hospital Beta has a connection to the University Research Group. Figure 10-26 shows the Hospital Beta network. - The two Cisco Catalyst 6506 core switches are interconnected with 10-Gbps links and have dual connections to two Cisco Catalyst 4948 switches for the servers. - The campus network is based on high-speed Layer 3 Cisco switches. - Wireless is supported using Cisco WLAN controllers (WLC). - The hospital has a DMZ, dual firewalls in each of two layers, IPS monitoring for the DMZ, and so forth. - Cisco IP telephony is in place. - Hospital Beta has a connection to the University Research Group. Figure 10-26 shows the Hospital Beta network. Figure 1D-26 Hospital Beta Network Figure 1D-26 Hospital Beta Network Figure 1D-26 Hospital Beta Network Figure 1D-26 Hospital Beta Network Based on the scenario above, please answer the questions below from doing your research: 1. Identify any issues you have with this merger and what design you would propose to the CIO. 2. What is the key security issue for the Hospital Omega network? How could this issue be resolved? 3. The CIO wants to consolidate servers in the ACMC data center. What issues need to be examined before proceeding with such a migration? 4. Suppose that inexpensive Metro Ethernet is available between ACMC and Hospital Beta. How does this change your answer to the question in the previous step? 5. Hospital Beta already has deployed a Cisco Unified Communications Manager, IP phones, voice gateways, and so forth. Should the Cisco Unified Communications Manager and Cisco Unity servers be moved to the ACMC data center? Why or why not? If not, how should they interact with a Cisco Unified Communications Manager on the ACMC campus? 6. Should the WLCs at Hospital Beta be moved to the ACMC campus? 7. Hospital Omega uses static routes on its one Internet router. Hospital Beta uses the Intermediate System-to-Intermediate System (IS-IS) routing protocol. Make a recommendation for overall routing protocol and routing design for the merged networks. 8. The CIO at ACMC is concerned about HIPAA compliance and general security. She and you agree on running all Internet connectivity through ACMC and Hospital Beta. Assume that firewalls, firewall rules, DMZs, and properly configured IPsec VPN access are all in place. What additional steps can be taken to improve security in the combined ACMC-Omega-Beta network