What is the solution to the fault condition?

###BeginTicket16###
Ticket 16: IPv6 Routing Issue 3
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
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.
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


###EndTicket16###

The implementation group has been using the test bed to do an IPv6 ‘proof-of-concept1. After
several changes to the network addressing and routing schemes, a trouble ticket has been
opened indicating that the loopback address on R1 (2026::111:1) is not able to ping the loopback
address on DSW2 (2026::102:1).
Use the supported commands to isolate the cause of this fault and answer the following
question.
What is the solution to the fault condition?

###BeginTicket16###
Ticket 16: IPv6 Routing Issue 3
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
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.
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


###EndTicket16###

The implementation group has been using the test bed to do an IPv6 ‘proof-of-concept1. After
several changes to the network addressing and routing schemes, a trouble ticket has been
opened indicating that the loopback address on R1 (2026::111:1) is not able to ping the loopback
address on DSW2 (2026::102:1).
Use the supported commands to isolate the cause of this fault and answer the following
question.
What is the solution to the fault condition?

A.
Under the interface Tunnel34 configuration delete the tunnel mode ipv6 command.

B.
Under the interface Serial0/0/0.34 configuration enter the ipv6 address 2026::34:1/122
command.

C.
Under the interface Tunnel34 configuration enter the ip address unnumbered Serial0/0/0.34
command.

D.
Under the interface Tunnel34 configuration delete the tunnel source Serial0/0/0.34 command
and enter the tunnel source 2026::34:1/122 command.

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. We need to remove the “tunnel mode
ipv6” command under interface Tunnel34



Leave a Reply 3

Your email address will not be published. Required fields are marked *


Chris Glaister

Chris Glaister

Wrote 300-135 exam few days ago and passed with 960/1000! Still no new questions, 13 Tickets(IPv4, IPv6), 6 MCQs, 2 Sims(HSRP and EIGRP).

All questions were from valid passleader 300-135 dumps (I used vce dumps here: https://tr.im/zdG4m)

BTW, please take the 300-135 exam as soon as possible in case of Cisco updating the exam!!!

tech_stream

tech_stream

Generic Routing Encapsulation (GRE) is a tunneling protocol developed by Cisco Systems that can encapsulate a wide variety of network layer protocols inside virtual point-to-point links over an Internet Protocol network.

In computer networks, a tunneling protocol allows a network user to access or provide a network service that the underlying network does not support or provide directly. One important use of a tunneling protocol is to allow a foreign protocol to run over a network that does not support that particular protocol; for example, running IPv6 over IPv4. Another important use is to provide services that are impractical or unsafe to be offered using only the underlying network services; for example, providing a corporate network address to a remote user whose physical network address is not part of the corporate network.

BigDaddy

BigDaddy

All tickets questions on this site aren’t given completely that makes it hard to comprehend their answers… however it just gives an idea about what may be coming in exam. Do anybody know detailed tickets so it can be checked thoroughly? Please email.
Thanks