Cisco 300-135 - CCNP Troubleshooting and Maintaining Cisco IP Networks (TSHOOT v2.0) Exam
Page: 3 / 30
Total 147 questions
Question #11 (Topic: Question Set 4)
Scenario:
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-72_1.png]
[Cisco-300-135-1.0/xmlfile-73_1.jpg]
[Cisco-300-135-1.0/xmlfile-74_1.jpg]
[Cisco-300-135-1.0/xmlfile-75_1.jpg]
[Cisco-300-135-1.0/xmlfile-76_1.jpg]
[Cisco-300-135-1.0/xmlfile-77_1.png]
[Cisco-300-135-1.0/xmlfile-78_1.png]
The OSPF neighbor relationship has been lost between R1 and R3. What is causing this problem?
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-72_1.png]
[Cisco-300-135-1.0/xmlfile-73_1.jpg]
[Cisco-300-135-1.0/xmlfile-74_1.jpg]
[Cisco-300-135-1.0/xmlfile-75_1.jpg]
[Cisco-300-135-1.0/xmlfile-76_1.jpg]
[Cisco-300-135-1.0/xmlfile-77_1.png]
[Cisco-300-135-1.0/xmlfile-78_1.png]
The OSPF neighbor relationship has been lost between R1 and R3. What is causing this problem?
A. The serial interface in R1 should be taken out of the shutdown state.
B. A neighbor statement needs to be configured in R1 and R3 pointing at each other.
C. The R1 network type should be changed to point-to-multipoint non-broadcast.
D. The hello, dead and wait timers on R1 need to be reconfigured to match the values on R3.
Answer: C
Question #12 (Topic: Question Set 4)
Scenario:
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-82_1.png]
[Cisco-300-135-1.0/xmlfile-83_1.jpg]
[Cisco-300-135-1.0/xmlfile-84_1.jpg]
[Cisco-300-135-1.0/xmlfile-85_1.jpg]
[Cisco-300-135-1.0/xmlfile-86_1.jpg]
[Cisco-300-135-1.0/xmlfile-87_1.png]
[Cisco-300-135-1.0/xmlfile-88_1.png]
Connectivity from R3 to R4, R5 and R6 has been lost. How should connectivity be reestablished?
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-82_1.png]
[Cisco-300-135-1.0/xmlfile-83_1.jpg]
[Cisco-300-135-1.0/xmlfile-84_1.jpg]
[Cisco-300-135-1.0/xmlfile-85_1.jpg]
[Cisco-300-135-1.0/xmlfile-86_1.jpg]
[Cisco-300-135-1.0/xmlfile-87_1.png]
[Cisco-300-135-1.0/xmlfile-88_1.png]
Connectivity from R3 to R4, R5 and R6 has been lost. How should connectivity be reestablished?
A. Configure R4 with a virtual link to 192.168.13.2
B. Change the R3 and R4 hello-interval and retransmit-interface timers to zero so the link won't go down.
C. Add an OSPF network statement for 4.4.4.4 0.0.0.0 area 1 in R3
D. Add an OSPF network statement for 192.168.34.3 0.0.0.255 area 2 in R3
E. Add an OSPF network statement for 192.168.34.0 0.0.0.255 area 1 in R3
Answer: E
Question #13 (Topic: Question Set 4)
Scenario:
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-91_1.png]
[Cisco-300-135-1.0/xmlfile-92_1.jpg]
[Cisco-300-135-1.0/xmlfile-93_1.jpg]
[Cisco-300-135-1.0/xmlfile-94_1.jpg]
[Cisco-300-135-1.0/xmlfile-95_1.jpg]
[Cisco-300-135-1.0/xmlfile-96_1.png]
[Cisco-300-135-1.0/xmlfile-97_1.png]
After resolving the issues between R3 and R4. Area 2 is still experiencing routing issues. Based on the current router configurations, what needs to be resolved for
routes to the networks behind R5 to be seen in the company intranet?
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-91_1.png]
[Cisco-300-135-1.0/xmlfile-92_1.jpg]
[Cisco-300-135-1.0/xmlfile-93_1.jpg]
[Cisco-300-135-1.0/xmlfile-94_1.jpg]
[Cisco-300-135-1.0/xmlfile-95_1.jpg]
[Cisco-300-135-1.0/xmlfile-96_1.png]
[Cisco-300-135-1.0/xmlfile-97_1.png]
After resolving the issues between R3 and R4. Area 2 is still experiencing routing issues. Based on the current router configurations, what needs to be resolved for
routes to the networks behind R5 to be seen in the company intranet?
A. Configure R4 and R5 to use MD5 authentication on the Ethernet interfaces that connect to the common subnet.
B. Configure Area 1 in both R4 and R5 to use MD5 authentication.
C. Add ip ospf authentication-key 7 BEST to the R4 Ethernet interface that connects to R5 and ip ospf authentication-key 7 BEST to R5 Ethernet interface that connects to R4.
D. Add ip ospf authentication-key CISCO to R4 Ethernet 0/1 and add area 2 authentication to the R4 OSPF routing process. D
Answer: Explanation
Question #14 (Topic: Question Set 4)
Scenario:
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-100_1.png]
[Cisco-300-135-1.0/xmlfile-101_1.jpg]
[Cisco-300-135-1.0/xmlfile-102_1.jpg]
[Cisco-300-135-1.0/xmlfile-103_1.jpg]
[Cisco-300-135-1.0/xmlfile-104_1.jpg]
[Cisco-300-135-1.0/xmlfile-105_1.png]
[Cisco-300-135-1.0/xmlfile-106_1.png]
The 6.6.0.0 subnets are not reachable from R4. How should the problem be resolved?
A customer network engineer has edited their OSPF network configuration and now your customer is experiencing network issues. They have contacted you to
resolve the issues and return the network to full functionality.
[Cisco-300-135-1.0/xmlfile-100_1.png]
[Cisco-300-135-1.0/xmlfile-101_1.jpg]
[Cisco-300-135-1.0/xmlfile-102_1.jpg]
[Cisco-300-135-1.0/xmlfile-103_1.jpg]
[Cisco-300-135-1.0/xmlfile-104_1.jpg]
[Cisco-300-135-1.0/xmlfile-105_1.png]
[Cisco-300-135-1.0/xmlfile-106_1.png]
The 6.6.0.0 subnets are not reachable from R4. How should the problem be resolved?
A. Edit access-list 46 in R6 to permit all the 6.6.0.0 subnets
B. Apply access-list 46 in R6 to a different interface
C. Apply access-list 1 as a distribute-list out under router ospf 100 in R4
D. Remove distribute-list 64 out on R6
E. Remove distribute-list 1 in ethernet 0/1 in R4
F. Remove distribute-list 1 in ethernet 0/0 in R4 D
Answer: Explanation
Question #15 (Topic: Testlet 1)
Instructions
The main screen consists of two parts; the Main scenario and the Topology tabs. The main scenario describes TSHOOT.com test bed. The Topology tabs allow
you to display the appropriate and select the trouble ticket.
To complete the item, you will first need to familiarize yourself with the TSHOOT.com test bed by clicking on the master scenario first and then the topologies tabs.
Once you are familiar with the test bed and the topologies, you should start evaluating the trouble ticket. You will be presented with a Trouble Ticket scenario that
will describe the fault condition. You will need to determine on which device the fault condition is located, to which technology the fault condition is related, and the
solution to each trouble ticket. This will be done by answering three questions.
Ticket Selection
To begin, click on the Ticket on the Topology tabs.
Some of the questions will require you to use the scroll bar to see all options.
Please note.
Fault Isolation
Read the ticket scenario to understand the fault condition.
Open the appropriate topology, based upon the ticket scenario.
Open the console of the desired device by clicking on that device in the topology, based upon your troubleshooting methodology.
Use the supported show, ping and trace commands to begin your fault isolation process.
Move to other devices as need by clicking on those devices within the topology.
Fault Identification
The trouble ticket will include three questions that you will need to answer:
1. Which device contains the fault
2. Which technology the fault condition is related to
3. What is the solution to the issue
To advance to the next question within the ticket click on “Next Questionâ€.
When you click “DONEâ€, the trouble ticket will turn RED and will no longer be accessible.
You may also use the “Previous Question†button to review questions within that specific ticket.
To complete a trouble ticket, answer all three questions and click “DONEâ€. This will store your response to the questions. Do not click on “DONE†unless you
have answered all questions within the ticket.
Item Completion
Click the NEXT button on the bottom of the screen once a ticket is RED. This action moves you to the next item.
Topology Overview (Actual Troubleshooting lab design is for below network design)
Client Should have IP 10.2.1.3
EIGRP 100 is running between switch DSW1 & DSW2
[Cisco-300-135-1.0/xmlfile-109_15.png]
OSPF (Process ID 1) is running between R1, R2, R3, R4
Network of OSPF is redistributed in EIGRP
BGP 65001 is configured on R1 with Webserver cloud AS 65002
HSRP is running between DSW1 & DSW2 Switches
The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.
This network consists of four routers, two layer 3 switches and two layer 2 switches.
In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.
DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.
R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP’s network. Because the company’s address space is in
the private range.
R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network.
ASW1 and ASW2 are layer 2 switches.
NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.
The client workstations receive their IP address and default gateway via R4’s DHCP server.
The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.
In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.
DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.
The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistrution is enabled where
necessary.
Recently the implementation group has been using the test bed to do a ‘proof-of-concept’ on several implementations. This involved changing the configuration on
one or more of the devices. You will be presented with a series of trouble tickets related to issues introduced during these configurations.
Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution.
Each ticket has 3 sub questions that need to be answered & topology remains same.
Fault is found on which device,
Question-1
Fault condition is related to,
Question-2
What exact problem is seen & what needs to be done for solution
Question-3
[Cisco-300-135-1.0/xmlfile-111_1.jpg]
[Cisco-300-135-1.0/xmlfile-112_1.png]
[Cisco-300-135-1.0/xmlfile-113_1.jpg]
[Cisco-300-135-1.0/xmlfile-114_1.png]
[Cisco-300-135-1.0/xmlfile-115_1.png]
[Cisco-300-135-1.0/xmlfile-116_1.png]
[Cisco-300-135-1.0/xmlfile-117_1.png]
[Cisco-300-135-1.0/xmlfile-118_1.png]
[Cisco-300-135-1.0/xmlfile-119_1.png]
[Cisco-300-135-1.0/xmlfile-120_1.png]
Client is unable to ping IP 209.65.200.241
Solution
Steps need to follow as below:-
1. When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4
Ipconfig ----- Client will be getting 169.X.X.X
2. On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IP address 10.2.1.0/24
Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2
====================================================
interface FastEthernet1/0/1
switchport mode access
switchport access vlan 10
interface FastEthernet1/0/2
switchport mode access
switchport access vlan 10
====================================================
3. We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 & 200 but not VLAN 10 so that switch could not get DHCP IP address
and was failing to reach IP address of Internet
[Cisco-300-135-1.0/xmlfile-121_1.png]
On ASW1 below change is required for switch-to-switch connectivity.
4. Change required:
int range portchannel13,portchannel23
switchport trunk allowed vlan none
switchport trunk allowed vlan 10,200
The implementations group has been using the test bed to do a ‘proof-of-concept’ that requires both Client 1 and Client 2 to access the WEB Server at
209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, and FHRP services, a trouble ticket has been
opened indicating that Client 1 cannot ping the 209.65.200.241 address.
Use the supported commands to Isolated the cause of this fault and answer the following questions.
On which device is the fault condition located?
The main screen consists of two parts; the Main scenario and the Topology tabs. The main scenario describes TSHOOT.com test bed. The Topology tabs allow
you to display the appropriate and select the trouble ticket.
To complete the item, you will first need to familiarize yourself with the TSHOOT.com test bed by clicking on the master scenario first and then the topologies tabs.
Once you are familiar with the test bed and the topologies, you should start evaluating the trouble ticket. You will be presented with a Trouble Ticket scenario that
will describe the fault condition. You will need to determine on which device the fault condition is located, to which technology the fault condition is related, and the
solution to each trouble ticket. This will be done by answering three questions.
Ticket Selection
To begin, click on the Ticket on the Topology tabs.
Some of the questions will require you to use the scroll bar to see all options.
Please note.
Fault Isolation
Read the ticket scenario to understand the fault condition.
Open the appropriate topology, based upon the ticket scenario.
Open the console of the desired device by clicking on that device in the topology, based upon your troubleshooting methodology.
Use the supported show, ping and trace commands to begin your fault isolation process.
Move to other devices as need by clicking on those devices within the topology.
Fault Identification
The trouble ticket will include three questions that you will need to answer:
1. Which device contains the fault
2. Which technology the fault condition is related to
3. What is the solution to the issue
To advance to the next question within the ticket click on “Next Questionâ€.
When you click “DONEâ€, the trouble ticket will turn RED and will no longer be accessible.
You may also use the “Previous Question†button to review questions within that specific ticket.
To complete a trouble ticket, answer all three questions and click “DONEâ€. This will store your response to the questions. Do not click on “DONE†unless you
have answered all questions within the ticket.
Item Completion
Click the NEXT button on the bottom of the screen once a ticket is RED. This action moves you to the next item.
Topology Overview (Actual Troubleshooting lab design is for below network design)
Client Should have IP 10.2.1.3
EIGRP 100 is running between switch DSW1 & DSW2
[Cisco-300-135-1.0/xmlfile-109_15.png]
OSPF (Process ID 1) is running between R1, R2, R3, R4
Network of OSPF is redistributed in EIGRP
BGP 65001 is configured on R1 with Webserver cloud AS 65002
HSRP is running between DSW1 & DSW2 Switches
The company has created the test bed shown in the layer 2 and layer 3 topology exhibits.
This network consists of four routers, two layer 3 switches and two layer 2 switches.
In the IPv4 layer 3 topology, R1, R2, R3, and R4 are running OSPF with an OSPF process number 1.
DSW1, DSW2 and R4 are running EIGRP with an AS of 10. Redistribution is enabled where necessary.
R1 is running a BGP AS with a number of 65001. This AS has an eBGP connection to AS 65002 in the ISP’s network. Because the company’s address space is in
the private range.
R1 is also providing NAT translations between the inside (10.1.0.0/16 & 10.2.0.0/16) networks and outside (209.65.0.0/24) network.
ASW1 and ASW2 are layer 2 switches.
NTP is enabled on all devices with 209.65.200.226 serving as the master clock source.
The client workstations receive their IP address and default gateway via R4’s DHCP server.
The default gateway address of 10.2.1.254 is the IP address of HSRP group 10 which is running on DSW1 and DSW2.
In the IPv6 layer 3 topology R1, R2, and R3 are running OSPFv3 with an OSPF process number 6.
DSW1, DSW2 and R4 are running RIPng process name RIP_ZONE.
The two IPv6 routing domains, OSPF 6 and RIPng are connected via GRE tunnel running over the underlying IPv4 OSPF domain. Redistrution is enabled where
necessary.
Recently the implementation group has been using the test bed to do a ‘proof-of-concept’ on several implementations. This involved changing the configuration on
one or more of the devices. You will be presented with a series of trouble tickets related to issues introduced during these configurations.
Note: Although trouble tickets have many similar fault indications, each ticket has its own issue and solution.
Each ticket has 3 sub questions that need to be answered & topology remains same.
Fault is found on which device,
Question-1
Fault condition is related to,
Question-2
What exact problem is seen & what needs to be done for solution
Question-3
[Cisco-300-135-1.0/xmlfile-111_1.jpg]
[Cisco-300-135-1.0/xmlfile-112_1.png]
[Cisco-300-135-1.0/xmlfile-113_1.jpg]
[Cisco-300-135-1.0/xmlfile-114_1.png]
[Cisco-300-135-1.0/xmlfile-115_1.png]
[Cisco-300-135-1.0/xmlfile-116_1.png]
[Cisco-300-135-1.0/xmlfile-117_1.png]
[Cisco-300-135-1.0/xmlfile-118_1.png]
[Cisco-300-135-1.0/xmlfile-119_1.png]
[Cisco-300-135-1.0/xmlfile-120_1.png]
Client is unable to ping IP 209.65.200.241
Solution
Steps need to follow as below:-
1. When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4
Ipconfig ----- Client will be getting 169.X.X.X
2. On ASW1 port Fa1/0/ 1 & Fa1/0/2 access port VLAN 10 was assigned which is using IP address 10.2.1.0/24
Sh run ------- & check for running config of int fa1/0/1 & fa1/0/2
====================================================
interface FastEthernet1/0/1
switchport mode access
switchport access vlan 10
interface FastEthernet1/0/2
switchport mode access
switchport access vlan 10
====================================================
3. We need to check on ASW 1 trunk port the trunk Po13 & Po23 were receiving VLAN 20 & 200 but not VLAN 10 so that switch could not get DHCP IP address
and was failing to reach IP address of Internet
[Cisco-300-135-1.0/xmlfile-121_1.png]
On ASW1 below change is required for switch-to-switch connectivity.
4. Change required:
int range portchannel13,portchannel23
switchport trunk allowed vlan none
switchport trunk allowed vlan 10,200
The implementations group has been using the test bed to do a ‘proof-of-concept’ that requires both Client 1 and Client 2 to access the WEB Server at
209.65.200.241. After several changes to the network addressing, routing scheme, DHCP services, NTP services, and FHRP services, a trouble ticket has been
opened indicating that Client 1 cannot ping the 209.65.200.241 address.
Use the supported commands to Isolated the cause of this fault and answer the following questions.
On which device is the fault condition located?
A. R1
B. R2
C. R3
D. R4
E. DSW1
F. DSW2
G. ASW1
H. ASW2
Answer: G
