tag:blogger.com,1999:blog-22834383577251652042024-03-20T16:23:20.368-07:00Networktut TSHOOTNetworktut.xyzjcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.comBlogger29125tag:blogger.com,1999:blog-2283438357725165204.post-17594756264743844262015-07-16T16:12:00.000-07:002015-07-16T16:12:00.486-07:00VLAN Routing<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
In this article we will discuss about the configuration on the switches of the TSHOOT Demo ticket. We post the topology here for your reference.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Layer2/3 topology</strong></div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<img alt="Layer2_topology.jpg" class="aligncenter" height="459" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/VLAN_routing/Layer2_topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="501" /></div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<span id="more-308"></span>Main Configuration on DSW1 and ASW1</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><div style="margin-bottom: 10px; padding: 0px;">
<strong>DSW1:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
ip routing<br />vtp mode transparent<br />!<br />vlan 10<br />name CLIENT_VLAN<br />!<br />vlan 98<br />name NATIVE_VLAN<br />!<br />vlan 99<br />name PARKING_LOT<br />!<br />interface range Fa1/0/2 – 18, Fa1/0/20 – 48, Gi1/0/1 – 4<br />switchport access vlan 99<br />switchport mode access<br />shutdown<br />!<br />interface FastEthernet1/0/1<br />description Link to R4<br />no switchport<br />ip address 172.16.1.14 255.255.255.252<br />!<br />interface FastEthernet1/0/19<br />description Trunk to ASW1<br />switchport access vlan 99<br />switchport trunk encapsulation dot1q<br />switchport trunk native vlan 98<br />switchport trunk allowed vlan 10,98<br />switchport mode trunk<br />!<br />interface Vlan10<br />ip address 172.16.2.1 255.255.255.0<br />!<br />router eigrp 16<br />network 172.16.1.0 0.0.0.255<br />network 172.16.2.0 0.0.0.255<br />passive-interface default<br />no passive-interface FastEthernet0/1</div>
</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><div style="margin-bottom: 10px; padding: 0px;">
<strong>ASW1:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
vtp mode transparent<br />!<br />vlan 10<br />name CLIENT_VLAN<br />!<br />vlan 98<br />name NATIVE_VLAN<br />!<br />vlan 99<br />name PARKING_LOT<br />!<br />interface FastEthernet1/0/1<br />switchport access vlan 10<br />switchport mode access<br />spanning-tree portfast<br />!<br />interface FastEthernet1/0/2<br />switchport access vlan 10<br />switchport mode access<br />spanning-tree portfast<br />!<br />interface range Fa1/0/3 – 18, Fa1/0/20 – 48, Gi1/0/1 – 4<br />switchport access vlan 99<br />switchport mode access<br />shutdown<br />!<br />interface FastEthernet1/0/19<br />description Link to DSW1<br />switchport trunk encapsulation dot1q<br />switchport trunk native vlan 98<br />switchport trunk allowed vlan 10,98<br />switchport mode trunk</div>
</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
From the output above we learn that:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ VTP is disabled on both switches.<br />+ DSW1: running EIGRP (Layer 3 switch) while ASW1 is pure layer 2 switch<br />+ Configuration VLANs on both switches as follows:<br />a) VLAN 10: CLIENT_VLAN (two computers are assigned to this VLAN)<br />b) VLAN 98: NATIVE_VLAN (no ports are assigned to this VLAN. This VLAN exists just to make sure traffic from other VLANs are tagged)<br />c) VLAN 99: PARKING_LOT (unused ports are assigned to this VLAN)<br />+ Fa1/0/19 is the trunking port between two switches<br />+ Only VLAN 10 and 98 are allowed to go through 2 switches.<br />+ Default gateway on two PCs are 172.16.2.1 which is the IP address of Interface VLAN 10 on DSW1.<br />+ EIGRP updated is only sent and received on fa1/0/1 which connects from DSW1 to R4<br />+ On ASW1, spanning-tree PortFast feature is enabled on fa1/0/1 & fa1/0/2 which are connected to two PCs.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: On DSW1, under interface Fa1/0/19 we can see this command:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>switchport access vlan 99</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
but this port is set as trunk port (switchport mode trunk) so how can a command for access port be there? Well, in fact we have set this port to trunk mode so the <strong>switchport access vlan 99</strong> command has no effect at all. It only affects when you change this port to an access port and this port would be assigned to VLAN 99.</div>
<div style="margin-bottom: 10px; padding: 0px;">
The IP address of interface VLAN 10 (172.16.2.1/24) is set as the default gateway on Host 1 & Host 2. In general, a Switch Virtual Interface (SVI) represents a logical Layer 3 interface on a switch and it can be used to interconnect Layer 3 networks using routing protocols (like RIP, OSPF, EIGRP…). When packets reach this SVI, the Layer 3 switch will look up in its routing table to see if there is an entry to route the packets to the destination. In this case, packets sent from Host 1 & 2 reach 172.16.2.1 (because this IP is also the default gateway set on Host 1 & 2), then DSW1 looks up in its routing table for a suitable entry to the destination.</div>
<table border="0" style="background: rgb(255, 255, 204); border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><div style="margin-bottom: 10px; padding: 0px;">
<strong>Quick reminder:</strong> VLAN interfaces or switched virtual interfaces (SVI) are logical layer 3 routable interface. Generally, SVIs are often used to accomplish InterVLAN routing on a Layer 3 switch. From there, you would point the client devices to the VLAN interface to use as it’s default gateway. When a packet arrives on that interface, the Layer 3 switch will do a routing table lookup and perform routing process like a normal packet.</div>
</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
In the next part we will try to do above topology in Packet Tracer. But Packet Tracer does not understand redistribute static route into EIGRP so we simplify the configuration by running EIGRP on all routers.</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<strong>Physical topology</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="VLAN_topology.jpg" class="aligncenter" height="336" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/VLAN_routing/VLAN_topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="427" /></div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Tasks in the lab:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ VTP is disabled on both switches.<br />+ DSW1: running EIGRP (Layer 3 switch) while ASW1 is pure layer 2 switch<br />+ Configuration VLANs on both switches as follows:<br />a) VLAN 10: CLIENT_VLAN (two computers are assigned to this VLAN)<br />b) VLAN 98: NATIVE_VLAN (no ports are assigned to this VLAN. This VLAN exists just to make sure traffic from other VLANs are tagged)<br />c) VLAN 99: PARKING_LOT (unused ports are assigned to this VLAN)<br />+ Fa0/19 is the trunking port between two switches<br />+ Only VLAN 10 and 98 are allowed to go through 2 switches.<br />+ Default gateway on two PCs are 172.16.2.1 which is the IP address of Interface VLAN 10 on DSW1.<br />+ EIGRP updated is only sent and received on fa0/1 which connects from DSW1 to R4<br />+ On ASW1, spanning-tree PortFast feature is enabled on fa0/1 & fa0/2 which are connected to two PCs.</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<strong>Configuration</strong></div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td align="left" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>ASW1</strong><br />hostname ASW1<br />!<br />vtp mode transparent<br />!<br />vlan 10<br />name CLIENT_VLAN<br />!<br />vlan 98<br />name NATIVE_VLAN<br />!<br />vlan 99<br />name PARKING_LOT<br />!<br />interface FastEthernet0/1<br />switchport access vlan 10<br />switchport mode access<br />spanning-tree portfast<br />!<br />interface FastEthernet0/2<br />switchport access vlan 10<br />switchport mode access<br />spanning-tree portfast<br />!<br />interface FastEthernet0/19<br />description Link to DSW1<br />switchport trunk encapsulation dot1q<br />switchport trunk native vlan 98<br />switchport trunk allowed vlan 10,98<br />switchport mode trunk</td><td align="left" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>DSW1</strong><br />hostname DSW1<br />ip routing<br />!<br />vtp mode transparent<br />!<br />vlan 10<br />name CLIENT_VLAN<br />!<br />vlan 98<br />name NATIVE_VLAN<br />!<br />vlan 99<br />name PARKING_LOT<br />!<br />interface FastEthernet0/1<br />description Link to R4<br />no switchport<br />ip address 172.16.1.14 255.255.255.252<br />no shutdown<br />!<br />interface FastEthernet0/19<br />description Trunk to ASW1<br />switchport access vlan 99<br />switchport trunk encapsulation dot1q<br />switchport trunk native vlan 98<br />switchport trunk allowed vlan 10,98<br />switchport mode trunk<br />!<br />interface Vlan10<br />ip address 172.16.2.1 255.255.255.0<br />!<br />router eigrp 16<br />network 172.16.1.0 0.0.0.255<br />network 172.16.2.0 0.0.0.255<br />passive-interface default<br />no passive-interface FastEthernet0/1</td></tr>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R0</strong><br />hostname R0<br />!<br />interface FastEthernet0/0<br />ip address 172.16.1.13 255.255.255.252<br />no shutdown<br />!<br />interface FastEthernet0/1<br />ip address 209.65.200.225 255.255.255.252<br />no shutdown<br />!<br />router eigrp 16<br />network 172.16.0.0<br />network 209.65.200.0</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R1</strong><br />hostname R1<br />!<br />interface FastEthernet0/0<br />ip address 209.65.200.226 255.255.255.252<br />no shutdown<br />!<br />router eigrp 16<br />network 209.65.200.0</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
Also configure IP addresses and default gateways of the two computers as follows:</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>PC0</strong><br />IP: 172.16.2.3/24<br />Default gateway: 172.16.2.1</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>PC1</strong><br />IP: 172.16.2.4/24<br />Default gateway: 172.16.2.1</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
Now two hosts can ping 209.65.200.226.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-5892840908125229262015-07-16T16:11:00.000-07:002015-07-16T16:11:07.413-07:00EIGRP over Frame Relay and EIGRP Redistribute Lab<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
In the previous <a href="http://tshoott.blogspot.com/2015/07/frame-relay-point-to-point-subinterface.html" style="color: #2970a6; text-decoration: none;" target="_blank">Frame Relay Point-to-Point Subinterface lab</a> we have set up Layer 2 connection via Frame Relay but only adjacent routers can ping each other. For example R1 can ping R2 and R2 and ping R3 but R1 cannot ping R3. This is because R2 connects with R1 and R3 via point-to-point interfaces and they use separate subnets. In this lab we will use EIGRP to advertise these routes so that “remote” routers can ping each other.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="topology.jpg" class="aligncenter" height="367" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="638" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
IOS used in this lab: <strong>c3640-jk9s-mz.124-16.bin</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">Tasks for this lab:</span><br />+ Configure EIGRP so that R1, R2, R3 and R4 can see and ping each other<br />+ Configure default route on R1 to 209.65.200.226 of R6<br />+ Advertise that default route to other routers via EIGRP so that every router can go to the Internet</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span id="more-292"></span></div>
<div class="pinkandbold" style="color: magenta; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Configure EIGRP on R1, R2, R3 and R4</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R1</strong><br />router eigrp 16<br />network 172.16.0.0</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R2</strong><br />router eigrp 16<br />network 172.16.1.0 0.0.0.255</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R3</strong><br />router eigrp 16<br />network 172.16.1.4 0.0.0.3<br />network 172.16.1.9 0.0.0.0</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R4</strong><br />router eigrp 16<br />network 172.16.1.0 0.0.0.25</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
The configuration of EIGRP is simple but please keep in mind that the “network” command really doesn’t advertise the network in that command. It enables EIGRP on the interface matched by the “network” command. For example, on R2 the “network 172.16.1.0 0.0.0.255″ command instructs R2 to search all of its active interfaces (including subinterfaces) and R2 finds out the IP addresses of s0/0.12 and s0/0.23 subinterfaces belong to “172.16.10 0.0.0.255″ network so R2 enables EIGRP on these subinterfaces. Another example is on R3, the “network 172.16.1.4 0.0.03″ will enable EIGRP on s0/0.23 subinterface only. Without the “network 172.16.1.9 0.0.0.0″ command, EIGRP would not be enabled on s0/0.34 subinterface. You can verify which interfaces are running EIGRP by the <strong>show ip eigrp interfaces</strong> command.</div>
<div style="margin-bottom: 10px; padding: 0px;">
So any mask you put in your network command, as long as it matches or includes the IP address on a particular interface than you are good to go. And if you are lazy, just put the “network 0.0.0.0 255.255.255.255″ command on each router, this will tell that router “enable EIGRP on all of my active interfaces (regardless what their IP addresses), please” because the wildcard 255.255.255.255 indicates that the router does not care about what network is using.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: The “network” command also works in the same way for OSPF, RIP and other Interior Gateway Protocol (IGP) routing protocols, except for BGP (which is an EGP routing protocol). In BGP, the function of a network statement is to tell the router to search the IP routing table for a particular network, and if that network is found, originate it into the BGP database.</div>
<div style="margin-bottom: 10px; padding: 0px;">
After typing the configuration above we can ping remote routers now. For example the ping from R1 to R4 will be successful.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_ping172.16.1.10.jpg" height="117" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/R1_ping172.16.1.10.jpg" style="border: 0px; max-width: 940px;" width="654" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
And the routing table of R1 contains all networks in this topology:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_show_ip_route.jpg" height="269" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/R1_show_ip_route.jpg" style="border: 0px; max-width: 940px;" width="711" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Other routers’ routing tables are the same so I will not post them here.</div>
<div class="pinkandbold" style="color: magenta; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Redistribute static route into EIGRP</div>
<div style="margin-bottom: 10px; padding: 0px;">
In this part we will learn how default route to Internet (or to ISP router) should be advertised. Suppose R6 in the topology is the ISP router.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="ISP_topology.jpg" class="aligncenter" height="132" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/ISP_topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="351" /></div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R1</strong><br />interface s0/1<br />ip address 209.65.200.225 255.255.255.252<br />no shutdown</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R6</strong><br />interface s0/0<br />ip address 209.65.200.226 255.255.255.252<br />no shutdown<br />!<br />interface Loopback0<br />ip address 209.65.200.241 255.255.255.252</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
You can’t run an IGP routing protocol (like OSPF, EIGRP) on the ISP router so the most simple way to send traffic to the ISP router is to use static route. So on R1 we will set up a static route to R6, we can do it via 3 ways:</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
R1(config)#ip route 0.0.0.0 0.0.0.0 s0/1</div>
<div style="margin-bottom: 10px; padding: 0px;">
or</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
R1(config)#ip route 0.0.0.0 0.0.0.0 209.65.200.226</div>
<div style="margin-bottom: 10px; padding: 0px;">
or</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
R1(config)#ip route 0.0.0.0 0.0.0.0 s0/1 209.65.200.226</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: Just for your information about static route, the paragraph below is quoted from<a href="http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/route_static.html" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/en/US/docs/security/asa/asa82/configuration/guide/route_static.html</a>.</div>
<div style="margin-bottom: 10px; padding: 0px;">
“Static routes remain in the routing table even if the specified gateway becomes unavailable. If the specified gateway becomes unavailable, you need to remove the static route from the routing table manually. However, static routes are removed from the routing table if the specified interface goes down, and are reinstated when the interface comes back up”.</div>
<div style="margin-bottom: 10px; padding: 0px;">
I want to notice that in all three cases of the ip route statements above, the static route will be removed in the routing table when s0/1 of R1 or s0/0 of R6 goes down. In other word, if you point a static route to a broadcast interface, the route is inserted into the routing table only when the broadcast interface is up.</div>
<div style="margin-bottom: 10px; padding: 0px;">
As you see the third case use both the local outgoing interface and the next-hop IP address. In fact in the topology above it has no more effect than the second case (only use next-hop IP address). The third case is only better in the case the remote interface goes down and next-hop IP can be reachable through a recursive route (but I haven’t test it).</div>
<div style="margin-bottom: 10px; padding: 0px;">
For more information about “ip route” command, please read the following link:<a href="http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00800ef7b2.shtml" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00800ef7b2.shtml</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
Ok, now R1 knows where to throw the packets when it can’t find a suitable destination for them. The routing table of R1 now shows the default route to 209.65.200.226. Notice that by default, static routes have an Administrative Distance of 1.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_show_ip_route_added_static_route.jpg" height="319" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/R1_show_ip_route_added_static_route.jpg" style="border: 0px; max-width: 940px;" width="709" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
But R2, R3 and R4 still do not know! We can configure a static route on each of them but it is not a good thing to do. A better way to advertise this static route to R2, R3 and R4 is via the configured EIGRP. How can we do that? Ahh, we will redistribute this static route into EIGRP and EIGRP will advertise it for us. On R1:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">router eigrp 16<br />redistribute static metric 64 100 100 100 1500</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: The ip route command is not automatically carried in routing updates like the ip default-network command (in some routing protocols). You must redistribute the static command into a routing protocol for it to be carried.</div>
<div style="margin-bottom: 10px; padding: 0px;">
The 5 parameters are used for redistribution into EIGRP are <strong>Bandwidth, Delay, Reliability, Load, MTU</strong>. For example the redistribution above is corresponding to <strong>Bandwidth = 64Kbit, Delay = 1000ms, Reliability=100, Load=100, MTU=1500 bytes</strong>. Notice that the unit of Delay used in the redistribution into EIGRP is tens of microsecond so we must divide Delay (in millisecond) by 10.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Now the routing tables of other routers (than R1) also learn this default route as an EIGRP external route (marked with <strong>D*EX</strong>). For example the routing table of R2:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R2_show_ip_route_after_redistribute.jpg" height="272" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/R2_show_ip_route_after_redistribute.jpg" style="border: 0px; max-width: 940px;" width="709" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
The default administrative distance for EIGRP externals (routes redistributed into EIGRP) is 170.</div>
<div style="margin-bottom: 10px; padding: 0px;">
By default, K1 = 1, K2 = 0, K3 = 1, K4 = 0, K5 = 0 so the metric formula for EIGRP is:</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
metric = (10<sup>7</sup> / Slowest Bandwidth of all interfaces[Kbit] + Sum of delay[ten-of-millisecond] ) * 256</div>
<div style="margin-bottom: 10px; padding: 0px;">
You can check the total delay and minimum bandwidth used to calculate EIGRP metric via the “show ip route <route>” command:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R2_show_ip_route_0.0.0.0.jpg" height="188" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/R2_show_ip_route_0.0.0.0.jpg" style="border: 0px; max-width: 940px;" width="833" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Therefore the EIGRP metric here should be:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">metric = (10</span><sup class="blueandbold" style="color: #3333cc; font-weight: bold;">7</sup><span class="blueandbold" style="color: #3333cc; font-weight: bold;"> / 64 + 2100) * 256 = 40537600</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: We are not sure why the unit of delay here is microsecond. But if we consider “microsecond” millisecond we will get the correct metric, otherwise we never get the correct result. And the unit of sum of delay used to calculate EIGRP metric is ten-of-millisecond so we have to divide the total delay by 10 (21000 / 10 = 2100).</div>
<div style="margin-bottom: 10px; padding: 0px;">
We can verify R4 has learned the default route, too:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R4_show_ip_route_after_redistribute.jpg" height="286" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/EIGRP_over_Frame_Relay/R4_show_ip_route_after_redistribute.jpg" style="border: 0px; max-width: 940px;" width="706" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
R4 also knows it has to route unknown traffic to 172.16.1.9. Also notice 172.16.1.9 now becomes the “gateway of last resort” of R4.</div>
<div style="margin-bottom: 10px; padding: 0px;">
The GNS3 initial and final configs can be downloaded here:</div>
<div style="margin-bottom: 10px; padding: 0px;">
Initial Configs: <a href="http://eigrp_over_frame_relay_tshoot_demo_initial.zip/" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">EIGRP_over_Frame_Relay_TSHOOT_Demo_initial.zip</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
Final Configs: <a href="http://www.networktut.com/download/EIGRP_over_Frame_Relay_TSHOOT_Demo_finalConfigs.zip" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">EIGRP_over_Frame_Relay_TSHOOT_Demo_finalConfigs.zip</a></div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-34657893865963341242015-07-16T16:09:00.001-07:002015-07-16T16:09:22.770-07:00Frame Relay Point-to-Point SubInterface GNS3 Lab<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
In this lab we will try to run a Frame Relay topology same as the one posted in TSHOOT demo ticket. The logical and physical topologies of this lab are shown below:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Logical topology:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="Topology_logical.jpg" class="aligncenter" height="380" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/Topology_logical.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="514" /></div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Tasks in this lab:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Configure static mappings on R1 and R4.<br />+ Configure point-to-point subinterface on R2 & R3.<br />+ All routers must be able to ping themselves.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span id="more-282"></span></div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Physical topology:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="Topology.jpg" class="aligncenter" height="366" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/Topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="467" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
IOS used in this lab: <strong><strong>c3640-jk9s-mz.124-16.bin</strong></strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
We will use a router (R5) to simulate the Frame Relay switch instead of using a Frame Relay Switch in GNS3. First we will configure the Frame Relay switch with the DLCIs shown above. In fact the DLCIs in the topology are not very logical, especially DLCIs 304 & 403 for the links between R1 & R2, but well… let’s configure them.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: If you are not sure about Frame Relay theory, please read <a href="http://www.ccna.ma/2015/07/frame-relay-tutorial.html" style="color: #2970a6; text-decoration: none;" target="_blank">Frame Relay tutorial</a> first.</div>
<div class="pinkandbold" style="color: magenta; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Configuration</div>
<div class="pinkandbold" style="color: magenta; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<strong>Configure Frame Relay Switch:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
We should change the name of R5 to FRSW (Frame Relay Switch).</div>
<div style="margin-bottom: 10px; padding: 0px;">
R5(config)#<strong>hostname FRSW</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
The very first command to turn on the frame relay switching feature on FRSW:</div>
<div style="margin-bottom: 10px; padding: 0px;">
FRSW(config)#<strong>frame-relay switching</strong></div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top">FRSW(config)#int s0/0<br />FRSW(config-if)#encapsulation frame-relay<br />FRSW(config-if)#frame-relay intf-type dce<br />FRSW(config-if)#clock rate 64000<br />FRSW(config-if)#frame-relay route 403 interface serial 0/1 304<br />FRSW(config-if)#no shutdown</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">FRSW(config)#int s0/1<br />FRSW(config-if)#encapsulation frame-relay<br />FRSW(config-if)#frame-relay intf-type dce<br />FRSW(config-if)#clock rate 64000<br />FRSW(config-if)#frame-relay route 304 interface serial 0/0 403<br />FRSW(config-if)#frame-relay route 302 interface serial 0/2 203<br />FRSW(config-if)#no shutdown</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">FRSW(config)#int s0/2<br />FRSW(config-if)#encapsulation frame-relay<br />FRSW(config-if)#frame-relay intf-type dce<br />FRSW(config-if)#clock rate 64000<br />FRSW(config-if)#frame-relay route 203 interface serial 0/1 302<br />FRSW(config-if)#frame-relay route 201 interface serial 0/3 102<br />FRSW(config-if)#no shutdown</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><div style="margin-bottom: 10px; padding: 0px;">
FRSW(config)#int s0/3<br />FRSW(config-if)#encapsulation frame-relay<br />FRSW(config-if)#frame-relay intf-type dce<br />FRSW(config-if)#clock rate 64000<br />FRSW(config-if)#frame-relay route 102 interface serial 0/2 201<br />FRSW(config-if)#no shutdown</div>
</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
+ The <span class="blueandbold" style="color: #3333cc; font-weight: bold;">frame-relay intf-type dce</span> command specifies the interface to handle LMI like a Frame Relay DCE device. This command also enables FRSW to function as a switch connected to a router. And the clock rate is necessary on the DCE end of the connection so we have to put it here (but in fact not all IOS versions require this, you can check or verify the DCE and clock rate with the <strong>show controller serial x/y</strong> command).</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ The <span class="blueandbold" style="color: #3333cc; font-weight: bold;">frame-relay route 403 interface serial 0/1 304</span> command means frame-relay traffic comes to FRSW which has a DLCI of 403 will be sent to interface Serial0/1 with a DLCI of 304.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Also please notice that there is no IP address configured on the Frame Relay Switch.</div>
<div style="margin-bottom: 10px; padding: 0px;">
We can verify the configuration of the FRSW with <strong>show frame-relay route</strong> command:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="FRSW_show_frame_route.jpg" height="127" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/FRSW_show_frame_route.jpg" style="border: 0px; max-width: 940px;" width="566" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: The output above is taken after all routers have been configured so if you do this command in your lab at this moment the <strong>Status</strong> would be <strong>Inactive</strong>because you have not turned on the Serial interfaces on R1, R2, R3, R4.</div>
<div class="pinkandbold" style="color: magenta; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<strong>Configure R1, R2, R3 and R4:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
First I show all the configuration but you should type them manually to see how it works instead of pasting all of them at the same time.</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R1:</strong><br />interface s0/0<br />ip address 172.16.1.1 255.255.255.252<br />encapsulation frame-relay<br />no frame-relay inverse-arp<br />frame-relay map ip 172.16.1.1 403 broadcast<br />frame-relay map ip 172.16.1.2 403<br />no shutdown<br />(good to explain first broadcast: <a href="https://learningnetwork.cisco.com/thread/35698" style="color: #2970a6; text-decoration: none;" target="_blank">https://learningnetwork.cisco.com/thread/35698</a>)</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R2:</strong><br />interface Serial0/0<br />no ip address<br />encapsulation frame-relay<br />no shutdown<br />!<br />interface Serial0/0.12 point-to-point<br />description Link to R1<br />ip address 172.16.1.2 255.255.255.252<br />frame-relay interface-dlci 304<br />!<br />interface Serial0/0.23 point-to-point<br />description Link to R3<br />ip address 172.16.1.5 255.255.255.252<br />frame-relay interface-dlci 302</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R3:</strong><br />interface Serial0/0<br />no ip address<br />encapsulation frame-relay<br />no frame-relay inverse-arp<br />no shutdown<br />!<br />interface Serial0/0.23 point-to-point<br />description Link to R2<br />ip address 172.16.1.6 255.255.255.252<br />frame-relay interface-dlci 203<br />!<br />interface Serial0/0.34 point-to-point<br />description Link to R4<br />ip address 172.16.1.9 255.255.255.252<br />frame-relay interface-dlci 201</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R4:</strong><br />interface Serial0/0<br />description Link to R3<br />ip address 172.16.1.10 255.255.255.252<br />encapsulation frame-relay<br />frame-relay map ip 172.16.1.9 102 broadcast<br />frame-relay map ip 172.16.1.10 102<br />no frame-relay inverse-arp<br />no shutdown</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
There are somethings I wish to explain. For example on R1 under interface s0/0 we see the command:</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
<strong>frame-relay map ip 172.16.1.1 403 broadcast</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
The <strong>frame-relay map</strong> command performs static addressing mapping and it disables Inverse ARP on the specified DLCI. This command is supported on the physical interface and it should be used when the far end Frame Relay device does not support Inverse ARP. If we choose to disable Inverse ARP, we must perform a static mapping of L2 to L3, as well as associate the DLCI to the interface.</div>
<div style="margin-bottom: 10px; padding: 0px;">
The IP address 172.16.1.1 is the IP address of R1 itself so why do we need this command? The answer is: without this command, you cannot ping from R1 to itself (ping to it own IP address may be a lab requirement, a fun test…) because that IP address does not exist in the Frame Relay map table and Frame Relay does not know which DLCI it should use to send the frames to this destination. You can check this with the “debug frame-relay packet” command to see the error <strong>Serial0/0:Encaps failed–no map entry link 7(IP)</strong>. By adding a static map to the DLCI used for a neighbor, when we ping to itself, the router will send ICMP to that neighbor and the neighbor will reply back to R1.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Now let’s discuss about the <strong>broadcast</strong> keyword in the above command. First, please notice that the “broadcast” keyword here is used for both multicast and broadcast traffic. By default, Frame Relay is a non-broadcast multiple access (NBMA) network and does not support broadcast or multicast traffic. So without the <strong>broadcast</strong> keyword, dynamic routing protocols such as EIGRP, OSPF and RIPv2 would not be able to advertise multicast route updates over the corresponding DLCI. Therefore we should always add this keyword in the “frame-relay map” command. But remember this: we only use one <strong>broadcast</strong>keyword for each DLCI regardless how many IP addresses are used along with. So the commands below:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>frame-relay map ip 172.16.1.1 403 broadcast</strong><br /><strong>frame-relay map ip 172.16.1.2 403</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
are same as:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>frame-relay map ip 172.16.1.1 403</strong><br /><strong>frame-relay map ip 172.16.1.2 403 broadcast</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
You should never use more then one broadcast keyword for one DLCI like this:</div>
<div style="margin-bottom: 10px; padding: 0px;">
frame-relay map ip 172.16.1.1 403 broadcast<br />frame-relay map ip 172.16.1.2 403 broadcast</div>
<div style="margin-bottom: 10px; padding: 0px;">
or you will end up with multiple copies of the packets being transported and received.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Configuring static map statements (like <strong>frame-relay map ip</strong> command) automatically disables Inverse ARP so in the configuration of R1, the <strong>no frame-relay inverse-arp</strong> command is in fact not necessary.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: Physical interfaces have Inverse ARP enabled by default</div>
<div style="margin-bottom: 10px; padding: 0px;">
That is all explanation for R1. Next we will discuss about the configuration of R2 and R3 (they are very identical). Under subinterface (like Serial0/0.12 point-to-point on R2) we see the command:</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
frame-relay interface-dlci 304</div>
<div style="margin-bottom: 10px; padding: 0px;">
We notice that in this command only the DLCI is specified and this command just associates the DLCI with the subinterface. This is because point-to-point network only connects with one remote destination. Therefore this command is mostly used under point-to-point subinterface (but it can be still used on physical interface although it has no effect because all unassigned DLCIs belong to that physical interface by default). On point-to-point subinterface, Inverse ARP requests are not sent out regardless if it is enabled on the physical interface or not. It is also not required to enable or disable Inverse ARP, because there is only a single remote destination on a PVC and discovery is not necessary. Also notice that the <strong>frame-relay map</strong> command is not allowed on a point-to-point subinterface.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: Using subinterface can avoid the split-horizon problem.</div>
<div style="margin-bottom: 10px; padding: 0px;">
We can check which type of mapping was configured with the command “show frame-relay map”:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ <strong>Dynamic</strong> means the mapping was done using Inverse ARP.<br />+ <strong>Static</strong> means the mapping was done manually.</div>
<div style="margin-bottom: 10px; padding: 0px;">
For example on R1 static mapping is being used:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_show_frame-relay_map.jpg" height="64" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R1_show_frame-relay_map.jpg" style="border: 0px; max-width: 940px;" width="493" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Let’s check R2:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R2_show_frame-relay_map.jpg" height="80" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R2_show_frame-relay_map.jpg" style="border: 0px; max-width: 940px;" width="588" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Hmm, on R2 we don’t see the word “static” or “dynamic”. There are some confusions about the “frame-relay interface-dlci” command if it belongs to dynamic mapping or static mapping. But there is an opinion saying that point-to-point does not use the principle of static or dynamic mapping so it is not listed here. Well, the decision is yours.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Also you can notice that no Layer 3 addresses are shown in above command.</div>
<div style="margin-bottom: 10px; padding: 0px;">
On the “show frame-relay map” outputs above you can see the Frame Relay’s statuses are all <strong>active</strong>. There are 4 PVC statuses:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ <strong>Active</strong>: Both sides of the PVC are up and communicating.<br />+ <strong>Inactive:</strong> Local router received status about the DLCI from the frame-switch, the other side is down.<br />+ <strong>Deleted</strong>: Indicates a local config problem. The frame-switch has no such mapping and responded with a “deleted message”.<br />+ <strong>Static</strong>: Indicates that LMI was turned off with the “no keepalives”.</div>
<div style="margin-bottom: 10px; padding: 0px;">
The outputs of the show frame-relay map command on R3 & R4 are very identical to R1 & R2, I also post here just for your reference:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R3_show_frame-relay_map.jpg" height="79" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R3_show_frame-relay_map.jpg" style="border: 0px; max-width: 940px;" width="579" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R4_show_frame-relay_map.jpg" height="63" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R4_show_frame-relay_map.jpg" style="border: 0px; max-width: 940px;" width="480" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
That’s all I wish to explain, let’s check if the pings work…</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_ping_172.16.1.2.jpg" height="93" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R1_ping_172.16.1.2.jpg" style="border: 0px; max-width: 940px;" width="571" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R2_ping_172.16.1.1_172.16.1.6.jpg" height="190" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R2_ping_172.16.1.1_172.16.1.6.jpg" style="border: 0px; max-width: 940px;" width="574" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R3_ping 172.16.1.5_172.16.1.10.jpg" height="193" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R3_ping%20172.16.1.5_172.16.1.10.jpg" style="border: 0px; max-width: 940px;" width="573" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R4_ping_172.16.1.9.jpg" height="95" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R4_ping_172.16.1.9.jpg" style="border: 0px; max-width: 940px;" width="571" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
So all the pings to the neighbors are working. On R1 you can try pinging itself and it will successful too. If you disable the <strong>frame-relay map ip 172.16.1.1 403 broadcast</strong> command (use <strong>no frame-relay map ip 172.16.1.1 403 broadcast</strong>), R1 cannot ping itself anymore:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_ping_172.16.1.1_itself.jpg" height="95" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/Frame_Relay/R1_ping_172.16.1.1_itself.jpg" style="border: 0px; max-width: 940px;" width="537" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
In this Frame Relay lab we only set path for adjacent routers. We can’t ping between R1 to R3 for example. There are two solutions so that R1 can ping R3:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Use multipoint subinterfaces on R2 (disable Inverse ARP and set two static frame-relay mappings on both R1 and R3)<br />+ Enable a routing protocol (static routing, EIGRP, OSPF, RIP…)</div>
<div style="margin-bottom: 10px; padding: 0px;">
The GNS3 initial and final configs can be downloaded here:</div>
<div style="margin-bottom: 10px; padding: 0px;">
Initial Configs:<a href="http://www.networktut.com/download/Frame_Relay_TSHOOT_demo_initial.zip" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">Frame_Relay_TSHOOT_demo_initial.zip</a><br />Final Configs: <a href="http://www.networktut.com/download/Frame_Relay_TSHOOT_demo_finalConfigs.zip" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">Frame_Relay_TSHOOT_demo_finalConfigs.zip</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
————————————————————————————————————————————-</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-65291978349610330372015-07-16T16:05:00.004-07:002015-07-16T16:05:47.015-07:00HSRP IP Route Tracking<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
In this article we will discuss about HSRP and do a lab on it.</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Quick reminder about HSRP</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Hot Standby Router Protocol (HSRP) is a Cisco proprietary protocol.<br />+ With HSRP, two or more devices support a virtual router with a fictitious MAC address and unique IP address<br />+ Hosts use this IP address as their default gateway and the MAC address for the Layer 2 header<br />+ The virtual router’s MAC address is 0000.0c07.ACxx , in which xx is the HSRP group. Multiple groups (virtual routers) are allowed.<br />+ The Active router forwards traffic. The Standby router is backup and monitors periodic hellos (multicast to 224.0.0.2,<br />UDP port 1985) to detect a failure of the active router.<br />+ The active router is chosen because it has the highest HSRP priority (default priority is 100). In case of a tie, the router<br />with the highest configured IP address wins the election<br />+ A new router with a higher priority does not cause an election unless it is configured to preempt.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">HSRP States</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Initial: HSRP is not running.<br />+ Learn: The router does not know the virtual IP address and is waiting to hear from the active router.<br />+ Listen: The router knows the IP and MAC of the virtual router, but it is not the active or standby router.<br />+ Speak: Router sends periodic HSRP hellos and participates in the election of the active router.<br />+ Standby: Router monitors hellos from active router and assumes responsibility if active router fails.<br />+ Active:Router forwards packets on behalf of the virtual router.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Load balancing traffic across two uplinks to two HSRP routers with a single HSRP group is not possible. The trick is to use two<br />HSRP groups:<br />+ One group assigns an active router to one switch.<br />+ The other group assigns another active router to the other switch.</div>
<div style="margin-bottom: 10px; padding: 0px;">
(Reference: SWITCH official Certification Guide)</div>
<div style="margin-bottom: 10px; padding: 0px;">
That is all for the boring HSRP theory, let do a lab to understand more about HSRP! We will use the topology below for this lab:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_Topology.jpg" class="aligncenter" height="433" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_Topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="319" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span id="more-324"></span></div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>IOS used: c3640-jk9s-mz.124-16.bin</strong></div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Tasks in this lab:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Configure IP addresses as shown and run EIGRP on R2, R3, R4<br />+ Configure HSRP: R2 is the Active HSRP while R3 is the Standby HSRP<br />+ Tracking route to 4.4.4.4, traffic should goes to R3 once the route to 4.4.4.4 is lost in R2 or the metric to R4’s loopback interface increases.</div>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
IP Address and EIGRP Configuration</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R1</strong> (configured as a host)<br />no ip routing<br />ip default-gateway 123.123.123.254 //This is the virtual IP of HSRP group<br />interface FastEthernet0/0<br />ip address 123.123.123.1 255.255.255.0<br />no shutdown</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R2</strong><br />interface FastEthernet0/0<br />ip address 123.123.123.2 255.255.255.0<br />no shutdown<br />!<br />interface FastEthernet1/0<br />ip address 24.24.24.2 255.255.255.0<br />no shutdown<br />!<br />router eigrp 1<br />network 24.0.0.0<br />network 123.0.0.0</td></tr>
<tr><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R3</strong><br />interface FastEthernet0/0<br />ip address 123.123.123.3 255.255.255.0<br />no shutdown<br />!<br />interface FastEthernet1/0<br />ip address 34.34.34.3 255.255.255.0<br />no shutdown<br />!<br />router eigrp 1<br />network 34.0.0.0<br />network 123.0.0.0</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R4</strong><br />interface Loopback0<br />ip address 4.4.4.4 255.255.255.0<br />!<br />interface FastEthernet0/0<br />ip address 24.24.24.4 255.255.255.0<br />no shutdown<br />!<br />interface FastEthernet1/0<br />ip address 34.34.34.4 255.255.255.0<br />no shutdown<br />!<br />router eigrp 1<br />network 4.0.0.0<br />network 24.0.0.0<br />network 34.0.0.0</td></tr>
</tbody></table>
<div class="blueandbold" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
HSRP Configuration</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R2</strong><br />interface FastEthernet0/0<br />standby 10 ip 123.123.123.254<br />standby 10 priority 200<br />standby 10 preempt</td><td align="" dir="" id="" lang="" scope="" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="top"><strong>R3</strong><br />interface FastEthernet0/0<br />standby 10 ip 123.123.123.254<br />standby 10 priority 150<br />standby 10 preempt</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
Note: The virtual IP address of HSRP group must be in the same subnet of the IP address on this interface (Fa0/0)</div>
<div style="margin-bottom: 10px; padding: 0px;">
After entering above commands we will see R2 takes <strong>Active</strong> state after going from <strong>Speak</strong> to <strong>Standby</strong>:</div>
<table border="1" style="background: rgb(255, 255, 204); border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">%HSRP-5-STATECHANGE: FastEthernet0/0 Grp 10 state Speak -> Standby<br />*Mar 1 00:10:22.487: %HSRP-5-STATECHANGE: FastEthernet0/0 Grp 10 state Standby -> Active<br />*Mar 1 00:10:22.871: %SYS-5-CONFIG_I: Configured from console by console</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
The “show standby” command on R2 confirms its state:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_standby.jpg" height="239" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_standby.jpg" style="border: 0px; max-width: 940px;" width="636" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Now R2 is in HSRP Active state with virtual MAC address of 00000c07.ac<span style="text-decoration: underline;">0a</span>. Notice that the last two numbers of the MAC address (0a) is the HSRP group number in hexadecimal form (0a in hexa = 10 in decimal)</div>
<div style="margin-bottom: 10px; padding: 0px;">
The “show standby” command on R3 reveals it is in<strong> Standby</strong> state:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R3_show_standby.jpg" height="238" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R3_show_standby.jpg" style="border: 0px; max-width: 940px;" width="627" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Now we will see what happens if we turn off interface Fa0/0 on R2:<br /><strong>R2(config)#interface fa0/0</strong><br /><strong>R2(config-if)#shutdown</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_standby_interface_down.jpg" height="221" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_standby_interface_down.jpg" style="border: 0px; max-width: 940px;" width="543" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R3_show_standby_interface_R2_down.jpg" height="236" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R3_show_standby_interface_R2_down.jpg" style="border: 0px; max-width: 940px;" width="541" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
As we can see, the HSRP state of R2 went back to <strong>Init</strong> while the HSRP state of R3 moved to <strong>Active</strong>.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">HSRP Tracking IP Route</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
In this part instead of tracking an interface going up or down we can track if the metric of a route to a destination changes or not. In particular we will try to track the route to the loopback interface of R4 (4.4.4.4). First we should check the routing table of R2:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_ip_route.jpg" height="340" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_ip_route.jpg" style="border: 0px; max-width: 940px;" width="710" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
We learn that the metric to the loopback interface of R4 (4.4.4.4) is 156160 and is summarized to 4.0.0.0/8 prefix because EIGRP summarizes route by default.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Now add tracking ip routing to R2</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>R2(config)#track 1 ip route 4.0.0.0 255.0.0.0 metric threshold</strong><br /><strong>R2(config-track)#threshold metric up 61 down 62</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
and on interface fa0/0 add these commands to apply the track:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>R2(config)#interface fa0/0</strong><br /><strong>R2(config-if)#standby 10 track 1 decrement 60</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
The command <strong>track ip route metric threshold</strong> is used to track the metric change of a route. For example in this case the second command <strong>threshold metric up 61 down 62</strong> specifies the low and high thresholds.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>up</strong>: Specifies the up threshold. The state is up if the scaled metric for that route is less than or equal to the up threshold. The default up threshold is 254.<br /><strong>down</strong>: Specifies the down threshold. The state is down if the scaled metric for that route is greater than or equal to the down threshold. The default down threshold is 255.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Then, how do we indicate the <strong>up</strong> value should be 61 and <strong>down</strong> value should be 62? This is because EIGRP routes are scaled by means of 2560 so if we divide the EIGRP metric (156160 in this case) by 2560 we will get 61 (156160 / 2560 = 61). 2560 is the default metric resolution value for EIGRP and can be modified by the <strong>track resolution</strong> command (for example: track resolution ip route eigrp 400). The table below lists the metric resolution for popular routing protocols.</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>Routing protocol</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>Metric Resolution</strong></td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">Static</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">10</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">EIGRP</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">2560</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">OSPF</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">RIP</td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">is scaled directly to the range from 0 to 255 because its maximum metric is less than 255</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
In this case if the metric for route to 4.0.0.0/8 in the routing table is less than or equal to 61 then the state is up. If the metric is greater or equal to 62, the state is down. We can verify if the track is working correctly by the <strong>show track</strong> command.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_track.jpg" height="151" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_track.jpg" style="border: 0px; max-width: 940px;" width="411" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
When the state is Down, R2’s priority will be deduced by 60: 200 – 60 = 140 which is less than the priority of R3 (150) -> R3 will take the Active state of R2.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_standby_down_state.jpg" height="254" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_standby_down_state.jpg" style="border: 0px; max-width: 940px;" width="625" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R3_show_track_no_route.jpg" height="238" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R3_show_track_no_route.jpg" style="border: 0px; max-width: 940px;" width="633" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
A very important note we wish to mention here is: the route for tracking should be exactly same as displayed in the routing table or the track would go down because no route is found. For example if we try tracking the route to the more specific route 4.4.4.0/24 or 4.4.4.4/24 the track would go down because EIGRP summarizes route by default before advertising through another major network. Let’s try this!</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>R2(config)#no track 1 ip route 4.0.0.0 255.0.0.0 metric threshold</strong><br /><strong>R2(config)#<strong>track 1 ip route 4.4.4.0 255.255.255.0 metric threshold<br /><strong>R2(config-track)#threshold metric up 61 down 62</strong></strong></strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
Now check if the track is working or not:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong><img alt="HSRP_Tracking_R2_show_track_no_route.jpg" height="154" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_track_no_route.jpg" style="border: 0px; max-width: 940px;" width="452" /></strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
The track on R2 goes down so R2’s priority is reduced by 60 which causes R3 takes the Active state.</div>
<div style="margin-bottom: 10px; padding: 0px;">
In this case if we wish to bring up the track route to 4.4.4.0/24 we just need to use the “no auto-summary” command on R4 which causes R4 to advertise the more specific route of 4.4.4.0/24.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>R4(config)#router eigrp 1</strong><br /><strong>R4(config-router)#no auto-summary</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
Now R4 advertises the detailed 4.4.4.0/24 network and it matches with our tracking process so the tracking process will go up.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_ip_route_no_auto-summary.jpg" height="374" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_ip_route_no_auto-summary.jpg" style="border: 0px; max-width: 940px;" width="707" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="HSRP_Tracking_R2_show_track_no_auto-summary.jpg" height="153" src="http://www.networktut.com/images/TSHOOT/GNS3Lab/HSRP_Tracking/HSRP_Tracking_R2_show_track_no_auto-summary.jpg" style="border: 0px; max-width: 940px;" width="447" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
The GNS3 initial and final configs can be downloaded here:</div>
<div style="margin-bottom: 10px; padding: 0px;">
Initial Configs: <a href="http://www.networktut.com/download/HSRP_initial.zip" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">HSRP_initial.zip</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
Final Configs: <a href="http://www.networktut.com/download/HSRP_finalConfigs.zip" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">HSRP_finalConfigs.zip</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
(Good reference: <a href="http://www.cisco.com/en/US/docs/ios/12_2sb/feature/guide/sbaiptrk.html" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/en/US/docs/ios/12_2sb/feature/guide/sbaiptrk.html</a>)</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-82534391716999876442015-07-16T16:04:00.003-07:002015-07-16T16:04:27.222-07:00Practice TSHOOT Tickets with Packet Tracer<h1 style="background-color: white; color: #333333; font-family: 'Segoe UI', Arial, Helvetica, sans-serif; font-size: 24px; margin: 0px; padding: 0px;">
Practice TSHOOT Tickets with Packet Tracer</h1>
<div>
<br /></div>
<div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Special thanks to <span class="pinkandbold" style="color: magenta; font-weight: bold;">Buddy </span>who sent us these files. Please say thanks to him. Now you can practice most TSHOOT Tickets with Packet Tracer v6.1. Please download all the tickets in one file here: <a href="http://www.networktut.com/download/Cisco_PT_6_1_TSHOOT_Package.zip" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">Cisco_PT_6_1_TSHOOT_Package.zip</a>. All the guides were included in that file.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Note: Please use at least the final Packet Tracer v6.1 (STUDENT Release) or above to open them. Below is a screenshot of the pkt files:</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEguhJUZzn4F4fJ1f2SxgpXeJ1XR8MKuWYll01EW5DFOzaUNOIsk7SosTPgjdi2cwftGjA02hbPRhzuGgTqdPpVAUZ4O6CISSvqeab6AJYCzfjsqtDxFp2EkWDn1AHo2Bo44qpcyH2qU6R0y/s1600/TSHOOT_Tickets_PT61.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="330" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEguhJUZzn4F4fJ1f2SxgpXeJ1XR8MKuWYll01EW5DFOzaUNOIsk7SosTPgjdi2cwftGjA02hbPRhzuGgTqdPpVAUZ4O6CISSvqeab6AJYCzfjsqtDxFp2EkWDn1AHo2Bo44qpcyH2qU6R0y/s640/TSHOOT_Tickets_PT61.jpg" width="640" /></a></div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<br /></div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-46357088026578601742015-07-16T16:01:00.000-07:002015-07-16T16:01:39.398-07:00A guide for the TSHOOT Exam<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
For the TSHOOTv2 exam we will encounter:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ <a href="http://tshoott.blogspot.com/search/label/Simlets" style="color: #2970a6; text-decoration: none;" target="_blank">Some Simlets</a> (small troubleshooting sims)<br />+ <a href="http://tshoott.blogspot.com/2015/07/multiple-choice-questions.html" style="color: #2970a6; text-decoration: none;" target="_blank">Multiple Choice Questions</a><br />+ 13/16 Troubleshooting Tickets (check them at the right-side menu)</div>
<div style="margin-bottom: 10px; padding: 0px;">
Below is a summary of 16 Tickets you will see in the exam:</div>
<table align="center" border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr style="background-color: #99ff99;"><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>Device</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>Error Description</strong></td></tr>
<tr><td align="center" rowspan="3" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;" valign="middle"><strong>ASW1</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1. Access port not in VLAN 10</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">2. Port Channel not allowing VLAN 10</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">3. Port Security</td></tr>
<tr><td rowspan="2" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>DSW1</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1. HSRP track 10</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">2. VLAN filter</td></tr>
<tr><td rowspan="4" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R1</strong><strong><br /></strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1. Wrong IP of BGP neighbor</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">2. NAT – Access list mis-configured</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">3. WAN access-list statement missing</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">4. OSPF Authentication</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R2</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1. IPv6: enable OSPF</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R3</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1. IPv6: remove “tunnel mode ipv6″</td></tr>
<tr><td rowspan="5" style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><strong>R4</strong></td><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">1. EIGRP – wrong AS</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">2. Redistribute (“to” & -> )</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">3. DHCP Range mis-configured</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">4. EIGRP Passive Interface</td></tr>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">5. missing Redistribution from RIPng to OSPFv3</td></tr>
</tbody></table>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;"><span class="blueandbold" style="color: #3333cc; font-weight: bold;">Special note:</span> In the old TSHOOT exam there were some tickets in which Client 1 & 2 got APIPA addresses (169.254.x.x) because they used DHCP to request their IP addresses. In the new TSHOOTv2 exam, Client1 & 2 IP addresses are statically assigned so you will not see APIPA addresses any more. Client1 & 2 always have IP addresses of 10.2.1.3 & 10.2.1.4.</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
Notice that in the exam, the tickets are randomly given so the best way to troubleshooting is to try pinging to all the devices from nearest to farthest from the client until you don’t receive the replies.</div>
<div style="margin-bottom: 10px; padding: 0px;">
In each ticket you will have to answers three types of questions:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Which device causes problem<br />+ Which technology is used<br />+ How to fix it</div>
<div style="margin-bottom: 10px; padding: 0px;">
One more thing to remember: you can only use “show” commands to find out the problems and you are not allowed to make any changes in the configuration. In fact, in the exam you can not enter the global configuration mode!</div>
<div style="margin-bottom: 10px; padding: 0px;">
Screenshots for your reference:</div>
<div style="margin-bottom: 10px; padding: 0px; text-align: center;">
<img alt="Layer2_3_Topology_small.jpg" height="438" src="http://www.networktut.com/images/TSHOOT/Labsim/Layer2_3_Topology_small.jpg" style="border: 0px; max-width: 940px;" width="600" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px; text-align: center;">
<img alt="IPv4Layer3Topology_networktut.com_small.jpg" src="http://www.networktut.com/images/TSHOOT/Labsim/IPv4Layer3Topology_networktut.com_small.jpg" style="border: 0px; max-width: 940px;" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
(Please visit <a href="http://tshoott.blogspot.com/2015/07/share-your-tshoot-v20-experience.html" style="color: #2970a6; text-decoration: none;" target="_blank">Share your TSHOOT v2.0 Experience </a>for bigger images)</div>
<div style="margin-bottom: 10px; padding: 0px;">
Also you can find more information about TSHOOT exam in <a href="http://tshoott.blogspot.com/2015/07/tshoot-faqs-tips.html" style="color: #2970a6; text-decoration: none;">TSHOOT FAQs and Tips</a>.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-40434624475593710692015-07-16T15:54:00.000-07:002015-07-16T15:54:11.186-07:00Share your TSHOOT v2.0 Experience<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
The TSHOOT 300-135 (TSHOOT v2.0) exam has been used to replace the old TSHOOT 642-832 exam so this article is devoted for candidates who took this exam sharing their experience. <span class="pinkandbold" style="color: magenta; font-weight: bold;">Please tell with us what are your materials, the way you learned, your feeling and experience after taking the TSHOOT v2.0 exam…</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Your posts are warmly welcome!</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">Exam’s Structure:</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Some Multiple choice questions<br />+ Some Simlets<br />+ 13 lab-sim Questions with the same network topology (13 troubleshooting tickets or you can call it one “big” question). Each lab-sim is called a ticket and you can solve them in any order you like.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">Topics of the lab-sims:</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
1- IPv6<br />2- OSPF<br />3- OSPFv3<br />4- Frame Relay<br />5- GRE<br />6- EtherChannel<br />7- RIPng<br />8- EIGRP<br />9- Redistribution<br />10- NTP<br />11- NAT<br />12- BGP<br />13- HSRP<br />14- STP<br />15- DHCP</div>
<div style="margin-bottom: 10px; padding: 0px;">
The problems are rather simple. For example wrong IP assignment, disable or enable a command, authentication…</div>
<div style="margin-bottom: 10px; padding: 0px;">
In each tickets you will have to answers three types of questions:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Which device causes problem<br />+ Which technology is used<br />+ How to fix it</div>
<div style="margin-bottom: 10px; padding: 0px;">
When you press Done to finish each case, you can’t go back.</div>
<div style="margin-bottom: 10px; padding: 0px;">
A demo of the TSHOOT Exam can be found at: <a href="http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_demo.html" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_demo.html</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Note:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
+ In the new TSHOOTv2, you cannnot use the “Abort” button anymore. Therefore you cannot check the configuration of another ticket before completing the current ticket.</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ We have gathered many questions about TSHOOT exam and posted them at <a href="http://www.networktut.com/tshoot-faqs-tips" style="color: #2970a6; text-decoration: none;" target="_blank">TSHOOT FAQs & Tips</a>, surely you will find useful information about the TSHOOT exam there!</div>
<div style="margin-bottom: 10px; padding: 0px;">
Below are the topologies of the real TSHOOT exam, you are allowed to study these topologies before taking the exam. It surely saves you some invaluable time when sitting in the exam room (Thanks <span class="pinkandbold" style="color: magenta; font-weight: bold;">rrg</span> for sharing this).</div>
<h2 style="border-bottom-color: rgb(204, 204, 204); border-bottom-style: solid; border-bottom-width: 1px; font-family: Verdana, 'BitStream vera Sans'; font-size: 16px; margin: 10px 0px 0px; padding: 0px 5px 3px;">
IPv4 Layer 3 Topology</h2>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="IPv4Layer3Topology_networktut.com.jpg" height="480" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/Labsim/IPv4Layer3Topology_networktut.com.jpg" style="border: 0px; max-width: 940px;" width="640" /></div>
<h2 style="border-bottom-color: rgb(204, 204, 204); border-bottom-style: solid; border-bottom-width: 1px; font-family: Verdana, 'BitStream vera Sans'; font-size: 16px; margin: 10px 0px 0px; padding: 0px 5px 3px;">
<strong>IPv6 Layer 3 Topology</strong></h2>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="IPv6Layer3Topology_networktut.com.jpg" height="556" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/Labsim/IPv6Layer3Topology_networktut.com.jpg" style="border: 0px; max-width: 940px;" width="640" /></div>
<h2 style="border-bottom-color: rgb(204, 204, 204); border-bottom-style: solid; border-bottom-width: 1px; font-family: Verdana, 'BitStream vera Sans'; font-size: 16px; margin: 10px 0px 0px; padding: 0px 5px 3px;">
<strong>Layer 2-3 Topology</strong></h2>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="Layer2_3_Topology.jpg" height="516" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/Labsim/Layer2_3_Topology.jpg" style="border: 0px; max-width: 940px;" width="640" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
You can download the Metodo strategy to pass the exam here (specially thanks to <span class="pinkandbold" style="color: magenta; font-weight: bold;">David</span> who created this strategy):</div>
<div style="margin-bottom: 10px; padding: 0px;">
<a href="http://www.networktut.com/download/TSHOOT_Metodo.pdf" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">TSHOOT_Metodo.pdf</a></div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-68111223652905611982015-07-16T15:53:00.000-07:002015-07-16T15:53:00.164-07:00Ticket 16 – IPv6 RIPng OSPFv3 Redistribution<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Problem: Loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2 (2026::102:1).</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R4:</strong><br />ipv6 router ospf 6<br /> log-adjacency-changes<br />!<br />ipv6 router rip RIP_ZONE<br /> redistribute ospf 6 metric 2 include-connected<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Answer:</strong><br />Ans1) R4<br />Ans2) Ipv6 OSPF Routing<br />Ans3) Under ipv6 ospf process add the ‘redistribute rip RIP_Zone include-connected’ command</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-83118438740951769312015-07-16T15:52:00.005-07:002015-07-16T15:52:30.879-07:00Ticket 15 – IPv6 GRE Tunnel<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Problem: Loopback address on R1 (2026::111:1) is not able to ping the loopback address on DSW2 (2026::102:1).</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R3:</strong><br />!<br />interface Tunnel34<br /> no ip address<br /> ipv6 address 2026::34:1/122<br /> ipv6 enable<br /> ipv6 ospf 6 area 34<br /> tunnel source Serial0/0/0.34<br /> tunnel destination 10.1.1.10<br /> tunnel mode ipv6<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R4:</strong><br />interface Tunnel34<br /> no ip address<br /> ipv6 address 2026::34:2/122<br /> ipv6 enable<br /> ipv6 ospf 6 area 34<br /> tunnel source Serial0/0/0<br /> tunnel destination 10.1.1.9<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer:<br />Ans1) R3<br />Ans2) Ipv4 and Ipv6 Interoperability<br />Ans3) Under the interface Tunnel34, remove ‘tunnel mode ipv6′ command</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-72963710665586906832015-07-16T15:52:00.002-07:002015-07-16T15:52:13.050-07:00Ticket 14 – EIGRP Passive Interface<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
the neighborship between R4 and DSW1 wasn’t establised. Client 1 can’t ping R4<br /><strong>Configuration on R4:</strong><br />router eigrp 10<br /> passive-interface default<br /> redistribute ospf 1 route-map OSPF->EIGRP<br /> network 10.1.4.4 0.0.0.3<br /> network 10.1.4.8 0.0.0.3<br /> network 10.1.21.128 0.0.0.3<br /> default-metric 10000 100 255 1 10000<br /> no auto-summary</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer 1) R4<br />Answer 2) IPv4 EIGRP Routing<br />Answer 3) enter no passive interface for interfaces connected to DSW1 under EIGRP process (or in Interface f0/1 and f0/0, something like this)</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: There is a loopback interface on this device which has an IP address of 10.1.21.129 so we have to include the “network 10.1.21.128 0.0.0.3″ command.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
* Just for your information, in fact Clients 1 & 2 in this ticket CANNOT receive IP addresses from DHCP Server because DSW1 cannot reach 10.1.21.129 (an loopback interface on R4) because of the “passive-interface default” command. But in the exam you will see that Clients 1 & 2 can still get their IP addresses! It is a bug in the exam.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-91977590340676403412015-07-16T15:51:00.008-07:002015-07-16T15:51:54.410-07:00Ticket 13 – DHCP Range<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
In this ticket, if you see the “ip dhcp exclude 10.2.1.1-1.10.2.1.253″ then the DHCP range has been misconfigured.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration on R4:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
!<br /> ip dhcp excluded-address 10.2.1.1 10.2.1.253<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R4<br />Ans2) IP DHCP Server<br />Ans3) on R4 delete ip dhcp excluded-address 10.2.1.1 10.2.1.253 and apply ip dhcp excluded-address 10.2.1.1 10.2.1.2</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com1tag:blogger.com,1999:blog-2283438357725165204.post-12410570192439353682015-07-16T15:51:00.005-07:002015-07-16T15:51:37.912-07:00Ticket 12 – IPv6 OSPF<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
DSW1 & R4 can’t ping R2’s loopback interface or s0/0/0.12 IPv6 address.<br />R2 is not an OSPFv3 neighbor on R3<br />Situation: ipv6 ospf was not enabled on R2’s serial interface connecting to R3. (use ipv6 Layer 3)</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R2</strong><br />ipv6 router ospf 6<br /> router-id 2.2.2.2<br />!<br />interface s0/0/0.23<br /> ipv6 address 2026::1:1/122</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R3</strong><br /> ipv6 router ospf 6<br /> router-id 3.3.3.3<br />!<br />interface s0/0/0.23<br /> ipv6 address 2026::1:2/122<br /> ipv6 ospf 6 area 0</div>
<div class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold; margin-bottom: 10px; padding: 0px;">
Answer:</div>
<div style="margin-bottom: 10px; padding: 0px;">
In interface configuration mode of s0/0/0.23 on R2:<br />ipv6 ospf 6 area 12</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R2<br />Ans2) IPv6 OSPF Routing<br />Ans3) on the serial interface of R2, enter the command <strong>ipv6 ospf 6 area 0</strong> (notice that it is “area 0″, not “area 12″)</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-57226369945141687362015-07-16T15:51:00.002-07:002015-07-16T15:51:11.772-07:00Ticket 11 – OSPF to EIGRP<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 is not able to ping the Webserver<br />DSW1 can ping fa0/1 of R4. However clients and DSW1 can’t ping R4′s S0/0/0.34 interface (10.1.1.10)</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>On R4 in router eigrp:</strong><br />router eigrp 10<br /> network 10.1.4.5 0.0.0.0<br /> no auto-summary<br /> redistribute ospf 1 metric 100 10 255 1 1500 route-map OSPF_to_EIGRP<br />!<br />router ospf 1<br /> network 10.1.1.8 0.0.0.0 area 34<br /> redistribute eigrp 10 subnets<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
route-map OSPF->EIGRP<br /> match ip address 1</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer:change in router eigrp router-map name</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R4<br />Ans2) IPv4 Route Redistribution<br />Ans3) Under the EIGRP process, delete the <strong>redistribute ospf 1 route-map OSPF_to_EIGRP</strong> command and enter the <strong>redistribute ospf 1 route-map OSPF->EIGRP</strong> command.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-27926083248513879832015-07-16T15:49:00.009-07:002015-07-16T15:49:58.194-07:00Ticket 10 – EIGRP AS<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 is not able to ping the Webserver<br />DSW1 can ping fa0/1 of R4 but can’t ping s0/0/0.34</div>
<div style="margin-bottom: 10px; padding: 0px;">
Check ip eigrp neighbors from DSW1 you will not see R4 as neighbor.(use ipv4 Layer 3)<br />‘Show ip route’ on DSW1 you will not see any 10.x.x.x network route.</div>
<div style="margin-bottom: 10px; padding: 0px;">
On DSW1 & DWS2 the EIGRP AS number is 10 (router eigrp 10) but on R4 it is 1 (router eigrp 1)</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer: change router AS on R4 from 1 to 10</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R4<br />Ans2) EIGRP<br />Ans3) Change EIGRP AS number from 1 to 10</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-75493884879270191362015-07-16T15:49:00.006-07:002015-07-16T15:49:36.405-07:00Ticket 9 – Switchport trunk<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 & 2 can ping each other but they are unable to ping DSW1 or FTP Server (Use L2/3 Diagram)<br /><strong>Configuration of ASW1</strong><br />interface PortChannel13<br />switchport mode trunk<br />switchport trunk allowed vlan 1-9<br />!<br />interface PortChannel23<br />switchport mode trunk<br />switchport trunk allowed vlan 1-9<br />!<br />interface FastEthernet1/0/1<br />switchport mode access<br />switchport access vlan 10<br />!<br />interface FastEthernet1/0/2<br />switchport mode access<br />switchport access vlan 10</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer: on port channel 13, 23 disables all vlans and give <strong>switchport trunk allowed vlan 10,200</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1)ASW1<br />Ans2)Switch to switch connectivity<br />Ans3)int range portchannel13,portchannel23<br />switchport trunk allowed vlan none<br />switchport trunk allowed vlan 10,200</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-81773806398546940652015-07-16T15:49:00.003-07:002015-07-16T15:49:13.029-07:00Ticket 8 – Switchport VLAN 10<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 & 2 can’t ping DSW1 or FTP Server but they are able to ping each other.<br /><strong>Configuration of ASW1</strong><br />interface FastEthernet1/0/1<br />switchport mode access<br />switchport access vlan 1<br />!<br />interface FastEthernet1/0/2<br />switchport mode access<br />switchport access vlan 1</div>
<div style="margin-bottom: 10px; padding: 0px;">
On ASW1, on interfaces fa0/1, fa0/2 switchport access vlan 1</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer: on ASW1 change <strong>switchport access vlan 1</strong> to <strong>switchport access vlan 10</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1)ASW1<br />Ans2)Vlan<br />Ans3)give command: interface range fa1/0/1-/2 & switchport access vlan 10</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-32293210851667185272015-07-16T15:48:00.005-07:002015-07-16T15:48:42.047-07:00Ticket 7 – Port Security<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 is unable to ping Client 2 as well as DSW1. The command ‘sh interfaces fa1/0/1′ will show following message in the first line<br />‘FastEthernet1/0/1 is down, line protocol is down (err-disabled)’</div>
<div style="margin-bottom: 10px; padding: 0px;">
On ASW1 port-security mac 0000.0000.0001, interface in err-disable state</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of ASW1</strong><br />interface fa1/0/1<br /> switchport access vlan 10<br /> switchport mode access<br /> switchport port-security<br /> switchport port-security mac-address 0000.0000.0001</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> on ASW1 delele port-security & do on interfaces shutdown, no shutdown</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) ASW1<br />Ans2) Port security<br />Ans3) In Configuration mode, using the interface range Fa1/0/1 – 2, then no switchport port-security, followed by shutdown, no shutdown interface configuration commands.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-30522577553625576592015-07-16T15:48:00.002-07:002015-07-16T15:48:19.475-07:00Ticket 6 – VLAN filter<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 is not able to ping the server. Unable to ping DSW1 or the FTP Server(Use L2 Diagram).</div>
<div style="margin-bottom: 10px; padding: 0px;">
Vlan Access map is applied on DSW1 blocking the ip address of client 10.2.1.3</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration on DSW1</strong><br />vlan access-map test1 10<br />action drop<br />match ip address 10<br />vlan access-map test1 20<br />action drop<br />match ip address 20<br />vlan access-map test1 30<br />action forward<br />match ip address 30<br />vlan access-map test1 40<br />action forward<br />!<br />vlan filter test1 vlan-list 10<br />!<br />access-list 10 permit 10.2.1.3<br />access-list 20 permit 10.2.1.4<br />access-list 30 permit 10.2.1.0 0.0.0.255<br />!<br />interface VLAN10<br />ip address 10.2.1.1 255.255.255.0</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) DSW1<br />Ans2) VLAN ACL/Port ACL<br />Ans3) Under the global configuration mode enter no vlan filter test1 vlan-list 10 command.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: After choosing DSW1 for Ans1, next page (for Ans2) you have to <span style="text-decoration: underline;">scroll down</span> to find the VLAN ACL/Port ACL option. The scroll bar only appears in this ticket and is very difficult to be seen.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-85457459261136063072015-07-16T15:47:00.005-07:002015-07-16T15:47:53.218-07:00Ticket 5 – R1 ACL<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client is not able to ping the server. no one can ping the server.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Problem:on R1 acl blocking ip<br /><strong>Configuration on R1</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
interface Serial0/0/1<br /> description Link to ISP<br /> ip address 209.65.200.224 255.255.255.252<br /> ip nat outside<br /> ip access-group edge_security in<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
ip access-list extended edge_security<br /> deny ip 10.0.0.0 0.255.255.255 any<br /> deny ip 172.16.0.0 0.15.255.255 any<br /> deny ip 192.168.0.0 0.0.255.255 any<br /> deny 127.0.0.0 0.255.255.255 any<br /> permit ip host 209.65.200.241 any<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer: add <strong>permit ip 209.65.200.224 0.0.0.3 any</strong> command to R1’s ACL</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R1<br />Ans2) IPv4 Layer 3 Security<br />Ans3) Under the <strong>ip access-list extended edge-security</strong> configuration add the <strong>permit ip 209.65.200.224 0.0.0.3 any</strong> command</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note:<br />+ This is the only ticket the extended access-list edge_security exists. In other tickets, the access-list 30 is applied to the inbound direction of S0/0/1 of R1.<br />+ Although host 209.65.200.241 is permitted to go through the access-list (permit ip host 209.65.200.241 any) but R1 cannot ping the web server because R1 cannot establish BGP session with neighbor 209.65.200.226.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-36354923417292481622015-07-16T15:47:00.002-07:002015-07-16T15:47:22.830-07:00Ticket 4 – NAT ACL<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Client 1 & 2 are not able to ping the web server 209.65.200.241, but all the routers & DSW1,2 can ping the server.</div>
<div style="margin-bottom: 10px; padding: 0px;">
NAT problem. (use ipv4 Layer 3)<br />problem on R1 Nat acl</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R1</strong><br />ip nat inside source list nat_pool interface s0/0/1 overload</div>
<div style="margin-bottom: 10px; padding: 0px;">
ip access-list standard nat_pool<br />permit 10.1.0.0<br />!<br />interface serial0/0/1<br />ip address 209.65.200.225 255.255.255.252<br />ip nat outside<br />!<br />interface Serial0/0/0.12<br />ip address 10.1.1.1 255.255.255.252<br />ip nat inside<br />ip ospf message-digest-key 1 md5 TSHOOT<br />ip ospf authentication message-digest</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer:add to acl 1 permit ip 10.2.1.0 0.0.0.255</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R1<br />Ans2) NAT<br />Ans3) Add the command <strong>permit 10.2.0.0 </strong>in the nat_pool access-list</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-11015022929733058472015-07-16T15:46:00.005-07:002015-07-16T15:46:54.819-07:00Ticket 3 – BGP Neighbor<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
Problem: Client 1 is able to ping 209.65.200.226 but can’t ping the Web Server 209.65.200.241.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R1:</strong><br />router bgp 65001<br />no synchronization<br />bgp log-neighbor-changes<br />network 209.65.200.224 mask 255.255.255.252<br />neighbor 209.56.200.226 remote-as 65002<br />no auto-summary</div>
<div style="margin-bottom: 10px; padding: 0px;">
check bgp neighborship. **** show ip bgp sum****<br />The neighbor’s address in the neighbor command is wrong under router BGP. (use ipv4 Layer 3)</div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer: need change on router mode on R1 neighbor 209.65.200.226</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R1<br />Ans2) BGP<br />Ans3) delete the wrong neighbor statement and enter the correct neighbor address in the neighbor command (change “neighbor 209.<strong>56</strong>.200.226 remote-as 65002″ to “neighbor 209.<strong>65</strong>.200.226 remote-as 65002″)</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-76660392358699611422015-07-16T15:46:00.002-07:002015-07-16T15:46:28.390-07:00Ticket 2 – HSRP Track<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
HSRP was configured on DSW1 & DSW2. DSW1 is configured to be active but it does not become active.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of DSW1:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
track 1 ip route 10.2.21.128 255.255.255.224 metric threshold<br />threshold metric up 1 down 2<br />!<br />track 10 ip route 10.1.21.128 255.255.255.224 metric threshold<br />threshold metric up 63 down 64<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
interface Vlan10<br />ip address 10.2.1.1 255.255.255.0<br />standby 10 ip 10.2.1.254<br />standby 10 priority 200<br />standby 10 preempt<br />standby 10 track 1 decrement 60</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Answer: (use IPv4 Layer 3 Topology)</div>
<div style="margin-bottom: 10px; padding: 0px;">
On DSW1 interface vlan 10 mode, type these commands:<br />no standby 10 track 1 decrement 60<br />standby 10 track 10 decrement 60<br />(ip for track command not exact for real exam)</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: 10.1.21.129 is the IP address of a loopback interface on R4. This IP belongs to subnet 10.1.21.128/27.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) DSW1<br />Ans2) HSRP<br />Ans3) delete the command with track 1 and enter the command with track 10 (standby 10 track 10 decrement 60).</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-11800528327254239582015-07-16T15:45:00.002-07:002015-07-16T15:45:42.456-07:00Ticket 1 – OSPF Authentication<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
1.Client is unable to ping R1’s serial interface from the client.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Problem was disable authentication on R1, check where authentication is not given under router ospf of R1. (use ipv4 Layer 3)</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R1:</strong></div>
<div style="margin-bottom: 10px; padding: 0px;">
interface Serial0/0/0<br /> description Link to R2<br /> ip address 10.1.1.1 255.255.255.252<br /> ip nat inside<br /> encapsulation frame-relay<br /> ip ospf message-digest-key 1 md5 TSHOOT<br /> ip ospf network point-to-point<br />!<br />router ospf 1<br /> router-id 1.1.1.1<br /> log-adjacency-changes<br /> network 10.1.2.0 0.0.0.255 area 12<br /> network 10.1.10.0 0.0.0.255 area 12<br /> default-information originate always<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
<strong>Configuration of R2:</strong><br />interface Serial0/0/0.12 point-to-point<br /> ip address 10.1.1.2 255.255.255.252<br /> ip ospf authentication message-digest<br /> ip ospf message-digest-key 1 md5 TSHOOT<br />!</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">Answer:</span> on R1 need command <strong>“</strong>ip ospf authentication message-digest”</div>
<div style="margin-bottom: 10px; padding: 0px;">
Ans1) R1<br />Ans2) IPv4 OSPF Routing<br />Ans3) Enable OSPF authentication on the s0/0/0 interface using the “ip ospf authentication message-digest” command.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-35461488322972625212015-07-16T15:44:00.004-07:002015-07-16T15:44:58.789-07:00Multiple Choice Questions<div class="content" style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin: 0px; overflow: hidden; padding: 5px 0px 0px 5px;">
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaquestionsnumber" style="color: #ff3300; font-weight: bold;">Question 1</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Exhibit:</div>
<table border="1" style="background-attachment: initial; background-clip: initial; background-image: initial; background-origin: initial; background-position: initial; background-repeat: initial; background-size: initial; border-collapse: collapse; border: 2px solid rgb(204, 204, 204); margin: 5px 0px 10px;"><tbody>
<tr><td style="border: 1px solid rgb(204, 204, 204); padding: 3px 10px; vertical-align: top;">RouterA#<strong>debug eigrp packets</strong><br />……<br />01:39:13: EIGRP: Received HELLO on Serial0/0 nbr 10.1.2.2<br />01:39:13: AS 100, Flags 0x0, Seq 0/0 idbQ 0/0 iidbQ un/rely 0/0 peerQ un/rely 0/0<br />01:39:13: K-value mismatch</td></tr>
</tbody></table>
<div style="margin-bottom: 10px; padding: 0px;">
A network administrator is troubleshooting an EIGRP connection between RouterA, IP address 10.1.2.1, and RouterB, IP address 10.1.2.2. Given the debug output on RouterA, which two statements are true? (Choose two)</div>
<div style="margin-bottom: 10px; padding: 0px;">
A. RouterA received a hello packet with mismatched autonomous system numbers.<br />B. RouterA received a hello packet with mismatched hello timers.<br />C. RouterA received a hello packet with mismatched authentication parameters.<br />D. RouterA received a hello packet with mismatched metric-calculation mechanisms.<br />E. RouterA will form an adjacency with RouterB.<br />F. RouterA will not form an adjacency with RouterB.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> D F</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaexplanation" style="color: #66ff00; font-weight: bold;">Explanation</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
From the last line “K-value mismatch” we learn that the K values of two EIGRP routers are mismatched and EIGRP neighborship between two routers will not be formed.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Note: EIGRP K values are the metrics that EIGRP uses to calculate routes. Mismatched K values can prevent neighbor relationships from being established. By default K1 & K3 are set to 1 while K2, K4 and K5 are set to 0. We can change the EIGRP K values via the “<strong>metric weights</strong><em> tos k1 k2 k3 k4 k5</em>” command under EIGRP router mode (tos: type of service must always be zero). For example:</div>
<div style="margin-bottom: 10px; padding: 0px;">
Router(config-router)#metric weights 0 20 10 50 40 40</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaquestionsnumber" style="color: #ff3300; font-weight: bold;">Question 2</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
When troubleshooting an EIGRP connectivity problem, you notice that two connected EIGRP routers are not becoming EIGRP neighbors. A ping between the two routers was successful. What is the next thing that should be checked?</div>
<div style="margin-bottom: 10px; padding: 0px;">
A. Verify that the EIGRP hello and hold timers match exactly.<br />B. Verify that EIGRP broadcast packets are not being dropped between the two routers with the show ip EIGRP peer command.<br />C. Verify that EIGRP broadcast packets are not being dropped between the two routers with the show ip EIGRP traffic command.<br />D. Verify that EIGRP is enabled for the appropriate networks on the local and neighboring router.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> D</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaexplanation" style="color: #66ff00; font-weight: bold;">Explanation</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
The following list of parameters must match between EIGRP neighbors in order to successfully establish neighbor relationships:</div>
<div style="margin-bottom: 10px; padding: 0px;">
+ Autonomous System number.<br />+ K-Values (look at the previous lesson).<br />+ If authentication is used both: the key number, the password, and the date/time the password is valid must match.<br />+ The neighbors must be on common subnet (all IGPs follow this rule).</div>
<div style="margin-bottom: 10px; padding: 0px;">
Therefore we don’t need to check EIGRP hello and hold timers because they don’t have to match. We should check if appropriate networks are included in the “network …” command of EIGRP on both routers.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaquestionsnumber" style="color: #ff3300; font-weight: bold;">Question 3</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Refer to the exhibit.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="show_ip_route.jpg" height="325" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/MCQ/show_ip_route.jpg" style="border: 0px; max-width: 940px;" width="578" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
How would you confirm on R1 that load balancing is actually occurring on the default-network (0.0.0.0)?</div>
<div style="margin-bottom: 10px; padding: 0px;">
A. Use ping and the show ip route command to confirm the timers for each default network resets to 0.<br />B. Load balancing does not occur over default networks; the second route will only be used for failover.<br />C. Use an extended ping along with repeated show ip route commands to confirm the gateway of last resort address toggles back and forth.<br />D. Use the traceroute command to an address that is not explicitly in the routing table.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> D</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaexplanation" style="color: #66ff00; font-weight: bold;">Explanation</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
For example in the topology below, R1 learned the Loopback0 interface of R6 via two equal paths R2-R4 and R3-R5:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="traceroute_load_balance_topology.jpg" class="aligncenter" height="232" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/MCQ/traceroute_load_balance_topology.jpg" style="border: 0px; display: block; margin-left: auto; margin-right: auto; max-width: 940px;" width="550" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
The routing table of R1 is shown below:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_show_ip_route.jpg" height="99" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/MCQ/R1_show_ip_route.jpg" style="border: 0px; max-width: 940px;" width="452" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
And the traceroute command from R1 to R6’s loopback0:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<img alt="R1_traceroute.jpg" height="315" id="__wp-temp-img-id" src="http://www.networktut.com/images/TSHOOT/MCQ/R1_traceroute.jpg" style="border: 0px; max-width: 940px;" width="226" /></div>
<div style="margin-bottom: 10px; padding: 0px;">
Traceroute works by sending packets with gradually increasing Time-To-Live (TTL) value, starting with TTL value of 1. The first router receives the packet, decrements the TTL value and drops the packet because it then has TTL value zero. The router sends an ICMP Time Exceeded message back to the source. The next set of packets are given a TTL value of 2, so the first router forwards the packets, but the second router drops them and replies with ICMP Time Exceeded. Proceeding in this way, traceroute uses the returned ICMP Time Exceeded messages to build a list of routers that packets traverse, until the destination is reached and returns an ICMP Echo Reply message.</div>
<div style="margin-bottom: 10px; padding: 0px;">
The “1”, “2” and “3” in the traceroute output stands for the hop number. Therefore with the first hop (TTL is set to 1) we can see the packets are sent through 12.12.12.2 (R2) and 13.13.13.3 (R3). For the second hop (TTL is set to 2) they are 35.35.35.5 (R5) and 24.24.24.4 (R4)…</div>
<div style="margin-bottom: 10px; padding: 0px;">
In conclusion we can use the traceroute command to check if the load-balancing is actually occurring.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaquestionsnumber" style="color: #ff3300; font-weight: bold;">Question 4</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Which IPsec mode will encrypt a GRE tunnel to provide multiprotocol support and reduced overhead?</div>
<div style="margin-bottom: 10px; padding: 0px;">
A. 3DES<br />B. multipoint GRE<br />C. tunnel<br />D. transport</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> D</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaexplanation" style="color: #66ff00; font-weight: bold;">Explanation</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
IPSec transport mode (encrypting an IP GRE tunnel) is a commonly deployed option because it provides all the advantages of using IP GRE, such as IP Multicast protocol support (and, thus, also the support of routing protocols that utilize IP Multicast) and multiprotocol support. Furthermore, this option saves 20 bytes per packet over IPSec tunnel mode (encrypting an IP GRE tunnel) because an additional IP header is not required.</div>
<div style="margin-bottom: 10px; padding: 0px;">
Reference: <a href="http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND/QoS-SRND-Book/IPSecQoS.html#pgfId-56035" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/QoS_SRND/QoS-SRND-Book/IPSecQoS.html#pgfId-56035</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaquestionsnumber" style="color: #ff3300; font-weight: bold;">Question 5</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Which three features are benefits of using GRE tunnels in conjunction with IPsec for building site-to-site VPNs? (Choose three)</div>
<div style="margin-bottom: 10px; padding: 0px;">
A. allows dynamic routing over the tunnel<br />B. supports multi-protocol (non-IP) traffic over the tunnel<br />C. reduces IPsec headers overhead since tunnel mode is used<br />D. simplifies the ACL used in the crypto map<br />E. uses Virtual Tunnel Interface (VTI) to simplify the IPsec VPN configuration</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> A B D</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaexplanation" style="color: #66ff00; font-weight: bold;">Explanation</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
IPSec alone does not support multicast which many dynamic routing protocols use. GRE tunnels helps IPSec overcome this disadvantage by handling the transportation of multiprotocol and IP multicast traffic (from site-to-site VPNs, for example).</div>
<div style="margin-bottom: 10px; padding: 0px;">
With the p2p GRE over IPsec solution, all traffic between sites is encapsulated in a p2p GRE packet before the encryption process, simplifying the access control list used in the crypto map statements. The crypto map statements need only one line permitting GRE (IP Protocol 47).</div>
<div style="margin-bottom: 10px; padding: 0px;">
Reference:</div>
<div style="margin-bottom: 10px; padding: 0px;">
<a href="http://www.cisco.com/c/en/us/td/docs/security/vpn_modules/6342/vpn_cg/6342site3.html" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/c/en/us/td/docs/security/vpn_modules/6342/vpn_cg/6342site3.html</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
<a href="http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/P2P_GRE_IPSec/P2P_GRE_IPSec/2_p2pGRE_Phase2.html" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/WAN_and_MAN/P2P_GRE_IPSec/P2P_GRE_IPSec/2_p2pGRE_Phase2.html</a></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaquestionsnumber" style="color: #ff3300; font-weight: bold;">Question 6</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
Which statement is true about an IPsec/GRE tunnel?</div>
<div style="margin-bottom: 10px; padding: 0px;">
A. The GRE tunnel source and destination addresses are specified within the IPsec transform set.<br />B. An IPsec/GRE tunnel must use IPsec tunnel mode.<br />C. GRE encapsulation occurs before the IPsec encryption process.<br />D. Crypto map ACL is not needed to match which traffic will be protected.</div>
<div style="margin-bottom: 10px; padding: 0px;">
<br /></div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnacorrectanswers" style="color: #3333cc; font-weight: bold;">Answer:</span> C</div>
<div style="margin-bottom: 10px; padding: 0px;">
<span class="ccnaexplanation" style="color: #66ff00; font-weight: bold;">Explanation</span></div>
<div style="margin-bottom: 10px; padding: 0px;">
With the p2p GRE over IPsec solution, all traffic between sites is encapsulated in a p2p GRE packet before the encryption process, simplifying the access control list used in the crypto map statements.</div>
</div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com0tag:blogger.com,1999:blog-2283438357725165204.post-67299042276445843152015-07-06T06:50:00.001-07:002015-07-06T06:50:37.538-07:00TSHOOT FAQs & Tips<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
TSHOOT is one of the three exams in the CCNP certification. The TSHOOT exam is a chance for you to review your knowledge about ROUTE & SWITCH exams and test your troubleshooting skill. From the comments here and other places, this article tries to summarize all the TSHOOT frequently asked questions to save you some time. Please feel free to ask anything that you are unclear about TSHOOT so that all of us can help you. I will update this article frequently to bring you the newest information about this exam.</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
1. How much does the TSHOOT Exam 300-135 cost? And the passing score of TSHOOT?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
It now costs $250.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
The passing score of TSHOOTv2 is 846/1000</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
2. Please tell me how many questions in the real TSHOOT exam, and how much time to answer them?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Unlike other Cisco exams, the TSHOOT exam tests your ability to troubleshoot the problem so in this exam you have to solve 3 multiple choice questions (or 2 multiple choice questions and 1 drag and drop question) and troubleshooting 13 “tickets”. Each ticket is a problem about a specific technology used in Cisco routers or switches.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
You will have 135 minutes to answer them. If your native language is not English, Cisco allows you a 30-minute exam time extension (165 minutes in total).</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
3. Am I allowed to study the topology used in the real exam and where can I find it ?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Yes, you are! Because the purpose of this exam is testing a candidate’s ability to troubleshoot issues, not to understand a complex topology so Cisco publicizes the topology used in the real TSHOOT exam. You can find the topologies at http://www.networktut.com/share-your-tshoot-v2-0-experience.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
To save time on the exam, and to better understand the topology used in all of the trouble tickets, you should spend time familiarizing yourself with the topology used in the exam.</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
4. Where can I find the demo of this exam?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
There is a very good demo of TSHOOT exam published by Cisco and you can find it at<a href="http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_demo.html" rel="nofollow" style="color: #2970a6; text-decoration: none;" target="_blank">http://www.cisco.com/web/learning/le3/le2/le37/le10/tshoot_demo.html</a>. But notice that the topology in this link is not the topology used in the real exam. This demo is also a good practical topology and we also explained about the configuration of this demo in four articles: Frame Relay Point-to-Point SubInterface GNS3 Lab, EIGRP over Frame Relay and EIGRP Redistribute Lab, VLAN Routing and HSRP IP Route Tracking.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<span class="pinkandbold" style="color: magenta; font-weight: bold;">5. During the exam, we must only identify the problem or we must also make the correct configuration?</span></div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
We only need to identify each problem without having to make the correct configuration. But you have to answer three types of questions:</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
+ Which device causes problem<br />+ Which technology is used<br />+ How to fix it</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
6. Can someone please tell me in the real exam it gives the ticket names just like in this site (for example “Ticket 1 – OSPF Authentication “) or is it going to say ticket 1 , ticket 2 only?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
It only says ticket 1, ticket 2 only. In most cases you have to use the “show running-config” command to find out the wrong configuration.</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
7. Please give me some guideline when using the TSHOOT simulator.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Below is some guideline when using the TSHOOT simulator in the exam</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<img alt="demo_TSHOOT_1.jpg" height="373" src="http://www.networktut.com/images/TSHOOT/demo_TSHOOT_1.jpg" style="border: 0px; max-width: 940px;" width="640" /></div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<img alt="demo_TSHOOT_2.jpg" height="372" src="http://www.networktut.com/images/TSHOOT/demo_TSHOOT_2.jpg" style="border: 0px; max-width: 940px;" width="640" /></div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
7. Can I go back in the TSHOOT exam?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
As shown in the above question, you can press “Previous Question” to go back to previous questions in the same ticket only. If you press “Done” button then you can’t come back to this ticket anymore.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">Note: In TSHOOT 300-135 (TSHOOTv2), the “Abort” button no longer exists. That means you cannot cancel a ticket after choosing it. You have to complete that ticket before moving to another one.</span></div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
8. Can we take TSHOOT exam before the ROUTE or SWITCH exam?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Yes, you can. There is no order to take these exams. But the TSHOOT exam tests your skills to troubleshoot router & switch errors so I highly recommend you take the ROUTE and SWITCH exams first. The TSHOOT exam is very good to review your knowledge of what you learned in ROUTE & SWITCH.</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
9. Can I solve the tickets in any order I want, for example, I solve Ticket 8 first, then Ticket 3, Ticket 1…?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
Yes, you can solve them in any order until you click Done button. After clicking Done you cannot go back to this ticket again. Also notice that when you entering a Ticket, you have to solve it (answer all 3 questions) before moving to another ticket.</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
10. As I see there are 3 topologies in the exam. My question is to how to find which topology to use when doing a trouble ticket. Does it clearly state in exam whether to use this topology (layer 2 or layer 3, for example)?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
In the exam, it doesn’t say clearly which topology you need to use. But a reader on networktut.com has shared this tip:</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
“There is no really best way to choose which topology to use.<br />This is my style:<br />Most of the time I was using the ipv4 topology as it contains most of the nodes with ip addresses and in the cause of your troubleshooting and you discovered that you need more details on the ASW1 & 2 switches that is when I used the Layer 2 topology except for the ipv6 topology.<br />Any node on IPV4 topology that is in Layer 2 topology have same configuration irrespective of where you click on the nodes.<br />Study all tickets here and use the following elimination style below:<br />List out all the trouble ticket on the white little board you will be giving and tick each ticket as you answer them because this will let you know which tickets are remaining to look out for.”</div>
<div class="pinkandbold" style="background-color: white; color: magenta; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; font-weight: bold; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
11. In the exam can I use “traceroute” or “tracert” command?</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
According to some reports, “tracert” commands cannot be used on Clients but “traceroute” command can be used on DSW1. But of course you can use “ping” command. According to some candidates’ reports on the exam, maybe you should not believe too much on the output of the traceroute command in the exam.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<span class="pinkandbold" style="color: magenta; font-weight: bold;">12. Please let me know in the exam can we issue “pipe” commands such as: sh run | section eigrp; sh run | begin router?</span></div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
No, you cannot use “pipe” commands in the TSHOOT exam.</div>
<div style="background-color: white; color: #333333; font-family: Verdana, 'BitStream vera Sans', Tahoma, Helvetica, sans-serif; font-size: 12px; line-height: 17.3999996185303px; margin-bottom: 10px; padding: 0px;">
<span class="blueandbold" style="color: #3333cc; font-weight: bold;">If you have any questions about the TSHOOT exam, please don’t hesitate to ask. All of us will help you!</span></div>
jcreatorhttp://www.blogger.com/profile/17926347588908332596noreply@blogger.com1