SLB using DNAT Challenge Lab 3
Server load balancing using Dynamic NAT Challenge Lab 3
Previous Next
Download Lab: GNS3
Prerequisites:
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Cisco IOSvL2 (vios_l2-adventerprisek9-m.03.2017.qcow2)
Topology for this lab created in the GNS3 VM server running on the VMware ESXi 6.5.0
Introduction:
Despite elaborate instructions with multiple steps in the previous lab, configurations are incomplete and more tweaking is required because there are still some issues in the topology causing the users in the HQ office and Remote location troubles to access the services. You would have to implement solutions to the problems multiple employees facing in the corporation.
Topology:
Challenge 1:
Users from both VLANs 10 and 20 successfully communicate with HQ office but when network security engineer tried to implement VPN solution he reported that he was not able to establish connection to the HQ router CD1, he attempted to ping server using its domain name in the network off router CD1's interface g0/1 but the ping failed. Investigate why router R1 is not able to communicate with router CD1 or its subnets and implement a solution.
PC-2> ping cd1.corporate.loc
cd1.corporate.loc resolved to 10.1.1.1
84 bytes from 10.1.1.1 icmp_seq=1 ttl=61 time=6.934 ms
84 bytes from 10.1.1.1 icmp_seq=2 ttl=61 time=5.320 ms
R1#ping cd1.corporate.loc
Translating "cd1.corporate.loc"...domain server (255.255.255.255)
% Unrecognized host or address, or protocol not running.
Challenge 2:
While software engineers working on the developing new application, they notice that there is a communication issue between servers in the HQ office and the Datacenter, HTTP and HTTPS protocols are not responding. Using your knowledge of the topology, troubleshoot what could possibly prevent HQ servers from accessing Web servers in DC and then come up with a solution to fix the problem.
VPCS> ping http-balancer.loc -P 6 -p 80
Cannot resolve http-balancer.loc
VPCS> ping http-balancer.loc -P 6 -p 443
Cannot resolve http-balancer.loc
Previous Next
Download Lab: GNS3
Prerequisites:
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Cisco IOSvL2 (vios_l2-adventerprisek9-m.03.2017.qcow2)
Topology for this lab created in the GNS3 VM server running on the VMware ESXi 6.5.0
Introduction:
Despite elaborate instructions with multiple steps in the previous lab, configurations are incomplete and more tweaking is required because there are still some issues in the topology causing the users in the HQ office and Remote location troubles to access the services. You would have to implement solutions to the problems multiple employees facing in the corporation.
Topology:
Challenge 1:
Users from both VLANs 10 and 20 successfully communicate with HQ office but when network security engineer tried to implement VPN solution he reported that he was not able to establish connection to the HQ router CD1, he attempted to ping server using its domain name in the network off router CD1's interface g0/1 but the ping failed. Investigate why router R1 is not able to communicate with router CD1 or its subnets and implement a solution.
PC-2> ping cd1.corporate.loc
cd1.corporate.loc resolved to 10.1.1.1
84 bytes from 10.1.1.1 icmp_seq=1 ttl=61 time=6.934 ms
84 bytes from 10.1.1.1 icmp_seq=2 ttl=61 time=5.320 ms
R1#ping cd1.corporate.loc
Translating "cd1.corporate.loc"...domain server (255.255.255.255)
% Unrecognized host or address, or protocol not running.
Challenge 2:
While software engineers working on the developing new application, they notice that there is a communication issue between servers in the HQ office and the Datacenter, HTTP and HTTPS protocols are not responding. Using your knowledge of the topology, troubleshoot what could possibly prevent HQ servers from accessing Web servers in DC and then come up with a solution to fix the problem.
VPCS> ping http-balancer.loc -P 6 -p 80
Cannot resolve http-balancer.loc
VPCS> ping http-balancer.loc -P 6 -p 443
Cannot resolve http-balancer.loc
Comments
Post a Comment