Network Services Troubleshooting Lab4

Download Lab: GNS3 

Previous Next

Network Services Troubleshooting Lab4


Prerequisites:
 Cisco IOSv        (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
 Cisco IOSvL2    (vios_l2-adventerprisek9-m.03.2017.qcow2)


Notice:
This lab is based on the Complex_Network_Services_CCNP_Lab_1, it’s highly recommended that you complete that lab before you proceed on this one.


Introduction:
Troubleshooting skills are one of the most if not the most imperative abilities, any IT person has to master them to perform well at the job. These problem-solving lab series aim to improve Cisco’s network engineer’s skills by presenting the broken network topology in which you have to analyze the issues, propose a solution and then eliminate the configurational mistakes.


Scenario:
Commercial buildings management agency rented out three floors of its brand new building to the companies which concern with the business of healthcare, insurance, and banking industries. Agency hosting at this location Internet access and data center services to its tenants. Building management has two contracts with ISPs to provide high-speed Internet. To comply with government standards, the strict requirements defined, to logically separate each company's internet and local traffic, vrf instances will be used.

Since property management does not have in house IT department, it outsourcing its technology needs to the small IT firm where you as lead network engineer help your customers resolve problems. Trouble tickets below indicate what are you working on today.


Topology:
 
Ticket1:
Property management has been concerned with security since recent data breach occurred in the ISP network. Yesterday a team of network security engineers was working in the data closet to install some firewalls and other security appliances. They made some configurational changes to existing networking. This morning company_C’s employee said that the Internet is down and some of his coworkers reported the same problem. The security team is gone but the issue is still present, you, network engineer has been assigned to fix this inconvenience. Company_C is financing firm and requires high priority in this matter.


 Ticket2:
HTTP application down user at Company_B reports. He uses srv1.com:80 for processing clients insurance claims but newer application which uses HTTPS is working, nonetheless, he wants you to fix old HTTP based system.


Note: Before you start any troubleshooting verify that end devices have ip addresses already assigned to them otherwise use ip dhcp command to obtain one.