Cisco CCNP TSHOOT 300-135 free questions

1. What can you modify in an extended ping?

2. Gre Tunnel Header Mandatory and Optional

3. Gre tunnel Header, which one is standard, witch one Extended?

4. Select and Place:

5. Select and Place:

6. Select and Place:

7. SIMULATION

You work as Network Engineer for RADO network Ltd company. You colleague has setup POC simulating customer network to study about the behavior of BGP protocol when routes are exchanged between two different autonomous systems.

Review the topology. You need to identify and fix IBGP and EBGP issues on R1 router.

Topology Details:

AS64520

* R1, R2 and R3 are three routers on AS 64520 and OSPF is IGP routing protocol configured between them.

* IBGP configured between R1, R2, and R3 routers using peer group.

* Loopback0 address is used for IBGP peering, Loopback0 address configured on R1, R2 and R3 are advertised into BGP domain on AS64525.

AS64525

* RA and RB are two routers on AS64525 and EIGRP is IGP routing protocol configured between them.

* Loopback0 address is used for IBGP peering, Loopback0 address configured on RA and RB advertised into BGP domain on AS64525.

* R1 and RRA from EBGP neighbor relationship using physical interface address.

*R2 and RB from EBGP neighbor relationship using physical interface address.

Simulation requirements:

*Identify and fix EBGP neighbor relationship between R1 and R1 routers.

*Identify and fix IBGP neighbor relationship issue between R1 and R2, R1 and R3.

*You are allowed to remove any misconfiguration or incorrect configuration to only fix the issue and other initial configuration that not impacting the issues should not be changed.

* The Final BGP table, after fixing two issues on R1 router should display as shown below

8. Ticket 1 OSPF Authentication

TROUBLE TICKET STATEMENT:

The implementation group has been using the test bed to do a ‘proof-of-concept’ that required both client 1 and client 2 to access the Web Server at 209.65.200.241. After several changed to interface status, network addressing, routing schemes and layer 2 connectivity, at trouble ticket has been opened indicating that client 1 cannot ping the 209.65.200.241 (internet Server)

The following information needs its own show run:

Client 1 is able to ping 10.1.1.2 but not 10.1.1.1. Initial troubleshooting shows that R1 does not have any

OSPF neighbors or any OSPF routes

Configuration on R1:

router ospf 1

log-adjacency-changes

network 10.1.1.0 0.0.0.3 area 12

default-information originate always

!

interfaceSerial0/0/0/0.12 point-to-point

ip address 10.1.1.1 255.255.255.252

ip nat inside

ip ospf message-digest-key 1 md5 TSHOOT

Configuration on R2:

router ospf 1

log-adjacency-changes

network 10.1.1.0 0.0.0.3 area 12

!

interfaceSerial0/0/0/0.12 point-to-point

ip address 10.1.1.2 255.255.255.252

ip ospf authentication message-digest

ip ospf message-digest-key 1 md5 TSHOOT

On which device is the fault condition located?

9. Fault Condition is related to which technology?

10. What is the solution of the fault condition?

11. Ticket 2 IP NAT

TROUBLE TICKET STATEMENT:

The implementation group has been using the test bed to do a ‘proof-of-concept’ that required both client 1 and client 2 to access the Web Server at 209.65.200.241. After several changed to interface status, network addressing, routing schemes and layer 2 connectivity, at trouble ticket has been opened indicating that client 1 cannot ping the 209.65.200.241 (internet Server).

The following information needs its own show run:

Client 1 and Client 2 are not able to reach the WebServer at 209.65.200.241. Initial troubleshooting shows that DSW1, DSW2 and all the routers are able to reach the WebServer.

Configuration on R1

ip nat inside source list nat_pool interface s0/0/1 overload

ip access-list standard nat_pool

permit 10.1.0.0

permit 10.2.0.0

!

interface Serial0/0/1

ip address 209.65.200.225 255.255.255.252

ip nat inside

!

interface Serial0/0/0.12

ip address 10.1.1.1 255.255.255.252

ip nat inside

ip ospf message-digest-key 1 md5 TSHOOT

ip ospf authentication message-digest

On Which device is the fault condition located?

12. The Fault Condition is related to which technology?

13. What is the solution of the fault condition?

14. Ticket 3 R1ACL

TROUBLE TICKET STATEMENT:

The implementation group has been using the test bed to do a ‘proof-of-concept’ that required both client 1 and client 2 to access the Web Server at 209.65.200.241. After several changed to interface status, network addressing, routing schemes and layer 2 connectivity, at trouble ticket has been opened indicating that client 1 cannot ping the 209.65.200.241 (internet Server).

The following information needs its own show run:

Client 1 is not able to reach the WebServer at 209.65.200.241. Initial troubleshooting shows that R1 is also not able to reach the WebServer. R1 also does not have any active BGP neighbor.

Configuration on R1

!

interface Serial0/0/0/1

description link to ISP

ip address 209.65.200.224 255.255.255.252

ip access-group edge_security in

ip nat outside

ip virtual-reassembly

ntp brasdcast client

net broadcast key 1

no cdp enable

!

!

ip access-list nat_traffic permit 10.1.0.0 0.0.255.255

ip access-list nat_traffic permit 10.2.0.0 0.0.255.255

!

ip access-list edge_security deny ip 10.0.0.0 0.255.255.255 any

ip access-list edge_security deny ip 172.16.0.0 0.15.255.255 any

ip access-list edge_security deny ip 192.168.0.0 0.0.255.255 any

ip access-list edge_security deny ip 127.0.0.0 0.255.255.255 any

ip access-list edge_security permit ip host 209.65.200.241 any

On which device is the fault condition located?

15. The Fault Condition is related to which technology?

16. What is the solution of the fault condition?

17. Ticket 4 VLAN Filter

TROUBLE TICKET STATEMENT:

The implementation group has been using the test bed to do a ‘proof-of-concept’ that required both client 1 and client 2 to access the Web Server at 209.65.200.241. After several changed to interface status, network addressing, routing schemes and layer 2 connectivity, at trouble ticket has been opened indicating that client 1 cannot ping the 209.65.200.241 (internet Server).

The following information needs its own show run:

Client 1 is getting an IP address from the DHCP server but is not able to ping DSW1 or the FTP server.

vlan access-map test1 10

action drop match ip address 10

vlan access-map test1 20

action drop

matich ip address 20

vlan access-map test1 30

action forward match ip address 30

vlan access-map test 40 action forward

!

vlan filter test1 vlan-list10

vlan internal allocation policy ascending

!

access-list 10 permit 10.2.1.3

access-list 20 permit 10.2.1.4

access-list 30 permit 10.2.1.0 0.0.0.255

On which device is the fault condition located?

18. The Fault Condition is related to which technology?

19. What is the solution of the fault condition?