CCNP TSHOOT 300-135 Ticket 050
Previous Next
Download Lab: GNS3
Download Lab: GNS3
Prerequisites:
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Cisco IOSvL2 (vios_l2-adventerprisek9-m.03.2017.qcow2)
Note:
Since prerequisites for these labs are Cisco VIRL images, Frame Relay Cloud in original topology from the Cisco will be replaced by IOSvL2 switch and configured appropriately to imitate sub-interfaces for the point-to-point links. Access to the Cloud not available. All interfaces on the Cloud are configured as 802.1q Trunk, permitting VLAN 12,23,34.
Objectives:
Multiple problems were reported by the company's employees, some users unable to access web-server and teleworkers unable to save files on the FTP server. Tickets are open and ready to be solved, you as lead networking expert has been tasked to assist.
Topology:


Instruction:
Determine why Clients in VLAN 10 unable to access web-server, use " ip dhcp" command to get an ip address.
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Cisco IOSvL2 (vios_l2-adventerprisek9-m.03.2017.qcow2)
Note:
Since prerequisites for these labs are Cisco VIRL images, Frame Relay Cloud in original topology from the Cisco will be replaced by IOSvL2 switch and configured appropriately to imitate sub-interfaces for the point-to-point links. Access to the Cloud not available. All interfaces on the Cloud are configured as 802.1q Trunk, permitting VLAN 12,23,34.
Objectives:
Multiple problems were reported by the company's employees, some users unable to access web-server and teleworkers unable to save files on the FTP server. Tickets are open and ready to be solved, you as lead networking expert has been tasked to assist.
Topology:


Instruction:
Determine why Clients in VLAN 10 unable to access web-server, use " ip dhcp" command to get an ip address.
Some modifications to topology were made to accommodate
teleworking, Remote-PC has been installed and attached to the ISP cloud,
it has the ip address of 209.65.200.234/29 DG is 209.65.200.233. From
this client use " ping 209.65.200.225 -P 6 -p 21 and ping 209.65.200.225 -P 6 -p 20 to simulate the access to the FTP server.
Validation:
Both clients' PCs in VLAN10 have to be able to ping web-server.
On Remote-PC, the output of command mentioned above should be like this:
VPCS> ping 209.65.200.225 -P 6 -p 21
Connect 21@209.65.200.225 timeout
Connect 21@209.65.200.225 seq=2 ttl=58 time=22.365 ms
SendData 21@209.65.200.225 seq=2 ttl=58 time=20.228 ms
Close 21@209.65.200.225 seq=2 ttl=58 time=20.634 ms
VPCS> ping 209.65.200.225 -P 6 -p 20
Connect 20@209.65.200.225 timeout
Connect 20@209.65.200.225 seq=2 ttl=58 time=22.201 ms
SendData 20@209.65.200.225 seq=2 ttl=58 time=19.256 ms
Close 20@209.65.200.225 seq=2 ttl=58 time=21.320 ms
Validation:
Both clients' PCs in VLAN10 have to be able to ping web-server.
On Remote-PC, the output of command mentioned above should be like this:
VPCS> ping 209.65.200.225 -P 6 -p 21
Connect 21@209.65.200.225 timeout
Connect 21@209.65.200.225 seq=2 ttl=58 time=22.365 ms
SendData 21@209.65.200.225 seq=2 ttl=58 time=20.228 ms
Close 21@209.65.200.225 seq=2 ttl=58 time=20.634 ms
VPCS> ping 209.65.200.225 -P 6 -p 20
Connect 20@209.65.200.225 timeout
Connect 20@209.65.200.225 seq=2 ttl=58 time=22.201 ms
SendData 20@209.65.200.225 seq=2 ttl=58 time=19.256 ms
Close 20@209.65.200.225 seq=2 ttl=58 time=21.320 ms
Comments
Post a Comment