Answer: F

Answer: J

Explanation:

On DSW1, VALN ACL, Need to delete the VLAN access-map test1 whose action is to drop access-list 10; specifically 10.2.1.3

Answer: C

Explanation:

Cisco routers prioritize log messages into 8 levels (0-7), as shown below: LevelLevel NameDescription

0 Emergencies System is unusable 1 Alerts Immediate action needed 2 Critical Critical conditions

3 Errors Error conditions

4 Warnings Warning conditions

5 Notifications Informational messages

6 Informational Normal but significant conditions 7 Debugging Debugging messages

When you enable logging for a specific level, all logs of that severity and greater (numerically less) will be logged. In this case, when you enable console logging of warning messages (level 4), it will log levels 0-4, making the correct answer warnings, errors, critical, alerts, and emergencies.

Answer: A

Explanation:

The BGP neighbor statement is wrong on R1.

Topic 10, Ticket 5 : NAT ACL

Topology Overview (Actual Troubleshooting lab design is for below network design)

u2711 Client Should have IP 10.2.1.3

u2711 EIGRP 100 is running between switch DSW1 & DSW2

u2711 OSPF (Process ID 1) is running between R1, R2, R3, R4

u2711 Network of OSPF is redistributed in EIGRP

u2711 BGP 65001 is configured on R1 with Webserver cloud AS 65002

u2711 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 ISPu2021s network. Because the companyu2021s 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 R4u2021s 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 u2021proof-of-conceptu2021 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. Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

Client is unable to ping IP 209.65.200.241

Solution

Steps need to follow as below:-

u2711 When we check on client 1 & Client 2 desktop we are not receiving DHCP address

from R4

Ipconfig ----- Client will be receiving IP address 10.2.1.3

u2711 IP 10.2.1.3 will be able to ping from R4 , R3, R2, R1

u2711 Look for BGP Neighbourship

Sh ip bgp summary ----- State of BGP will be in established state & will be able to receive I prefix (209.65.200.241)

u2711 As per troubleshooting we are able to ping ip 10.2.1.3 from R1 & BGP is also receiving prefix of webserver & we are able to ping the same from R1. Further troubleshooting needs to be done on R1 on serial 0/0/1

u2711 Check for running config. i.e sh run for interface serial 0/0/1..

!

!

From above snapshot we are able to see that IP needs to be PAT to serial 0/0/1 to reach web server IP

(209.65.200.241). But in access-list of NAT IP allowed IP is 10.1.0.0/16 is allowed & need

10.2.0.0 /16 to

u2711 As per troubleshooting we are able to ping ip 10.2.1.3 from R1 & BGP is also receiving prefix of web server & we are able to ping the same from R1. Its should be checked further for running config of interface for stopping

u2711 Change required: On R1 we need to add the client IP address for reachability to server to the access list that is used to specify which hosts get NATed.

Answer: D,E,F

Answer: E

Explanation:

On R4, in the redistribution of EIGRP routing protocol, we need to change name of route- map to resolve the issue. It references route-map OSPF_to_EIGRP but the actual route map is called OSPF->EIGRP.

Topic 14, Ticket 9 : EIGRP AS number

Topology Overview (Actual Troubleshooting lab design is for below network design)

u2711 Client Should have IP 10.2.1.3

u2711 EIGRP 100 is running between switch DSW1 & DSW2

u2711 OSPF (Process ID 1) is running between R1, R2, R3, R4

u2711 Network of OSPF is redistributed in EIGRP

u2711 BGP 65001 is configured on R1 with Webserver cloud AS 65002

u2711 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 ISPu2021s network. Because the companyu2021s 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 R4u2021s 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 u2021proof-of-conceptu2021 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. Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

=====================================================================

Client is unable to ping IP 209.65.200.241

Solution

Steps need to follow as below:-

u2711 When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4

ipconfig ----- Client will be receiving IP address 10.2.1.3

u2711 From Client PC we can ping 10.2.1.254

u2711 But IP 10.2.1.3 is not able to ping from R4, R3, R2, R1

u2711 This clearly shows problem at R4 Kindly check routes in EIGRP there are no routes of eigrp.

u2711 Check the neighborship of EIGRP on R4; there are no neighbor seen from DSW1

& DSW2 check the running config of EIGRP protocol it shows EIGRP AS 1 processu2026. Now check on DSW1 & DSW2

On DSW1 only one Eigrp neighbour is there with DSW2 but its not with R4u2026

u2711 From above snapshot & since R4 has EIGRP AS number 1 due to which neighbour is not happening.

u2711 Change required: On R4, IPV4 EIGRP Routing, need to change the EIGRP AS number from 1 to 10 since DSW1 & DSW2 is configured to be in EIGRP AS number 10.

Answer: D

Explanation:

Start to troubleshoot this by pinging the loopback IPv6 address of DSW2 (2026::102:1). This can be pinged from DSW1, and R4, but not R3 or any other devices past that point. If we look at the diagram, we see that R4 is redistributing the OSPF and RIP IPV6 routes. However, looking at the routing table we see that R4 has the 2026::102 network in the routing table known via RIP, but that R3 does not have the route:

Screen Shot 2015-03-11 at 4

Screen Shot 2015-03-11 at 4

When we look more closely at the configuration of R4, we see that it is redistributing OSPF routes into RIP for IPv6, but the RIP routes are not being redistributed into OSPF. That is why R3 sees R4 as an IPV6 OSPF neighbor, but does not get the 2026::102 network installed.

Screen Shot 2015-03-11 at 4

So, problem is with route redistribution on R4.

Answer: D

Explanation: Port security is causing the connectivity issues. On ASW1, we need to remove port-security under interface fa1/0/1 & fa1/0/2.

Topic 13, Ticket 8 : Redistribution of EIGRP to OSPF

Topology Overview (Actual Troubleshooting lab design is for below network design)

u2711 Client Should have IP 10.2.1.3

u2711 EIGRP 100 is running between switch DSW1 & DSW2

u2711 OSPF (Process ID 1) is running between R1, R2, R3, R4

u2711 Network of OSPF is redistributed in EIGRP

u2711 BGP 65001 is configured on R1 with Webserver cloud AS 65002

u2711 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 ISPu2021s network. Because the companyu2021s 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 R4u2021s 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 u2021proof-of-conceptu2021 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. Question-1 Fault is found on which device,

Question-2 Fault condition is related to,

Question-3 What exact problem is seen & what needs to be done for solution

=====================================================================

Client is unable to ping IP 209.65.200.241

Solution

Steps need to follow as below:-

u2711 When we check on client 1 & Client 2 desktop we are not receiving DHCP address from R4

ipconfig ----- Client will be receiving IP address 10.2.1.3

u2711 IP 10.2.1.3 will be able to ping from R4 , but cannot ping from R3, R2, R1

u2711 This clearly shows problem at R4 since EIGRP is between DSW1, DSW2 & R4 and OSPF protocol is running between R4, R3, R2, R1 so routes from R4 are not propagated to R3, R2, R1

u2711 Since R4 is able to ping 10.2.1.3 it means that routes are received in EIGRP & same needs to be advertised in OSPF to ping from R3, R2, R1.

u2711 Need to check the routes are being advertised properly or not in OSPF & EIGRP

vice-versa.

u2711 From above snap shot it clearly indicates that redistribution done in EIGRP is having problem & by default all routes are denied from ospf to EIGRPu2026 so need to change route-map name.

u2711 Change required: On R4, in the redistribution of EIGRP routing protocol, we need

to change name of route-map to resolve the issue. It references route-map OSPF_to_EIGRP but the actual route map is called OSPF->EIGRP.

-------------------------------------------------------------------------------------------------------------------------

Answer: D

Explanation:

As explained earlier, the problem is with route misconfigured tunnel modes on R3. R3 is using tunnel mode ipv6, while R4 is using the default of GRE.

Topic 22, Mix Questions Set 2

83.In what situation would the command ip helper-address be required? (Choose the best answer.)

A. Only when there is a duplicate IP address caused by a combination of static and

dynamic IP address allocations

B. On each router that exists between the client and the server

C. Only when a router separates the client from the server

D. Only if the DHCP sever issues a DHCPNAK to the initial request

E. Only when the client is on the same subnet as the server

F. Only when the DHCP pool is out of IP addresses

Answer: E