IP NAT Troubleshooting. Solutions. Luke Bibby, CCIE #45527
|
|
- Debra Harrell
- 6 years ago
- Views:
Transcription
1 IP NAT Troubleshooting Solutions Luke Bibby, CCIE #45527
2 Quick Overview of Scenario Solutions Scenario #1 R2 s E0/0 should be NAT inside not NAT outside ACL 100 is configured incorrectly NAT policy missing the inside keyword Scenario #2 RIP is not enabled on on R1 NAT policy missing the inside keyword NAT policy has the inside local and inside global addresses around the wrong way Scenario #3 R1 s Loopback0 needs to be configured as NAT inside NAT policies are referencing non-existant ACLs; should be referencing route maps The route maps have the interfaces configured incorrectly
3 Scenario #1 Solutions The first thing we should test is that the connectivity between R1 and R3 is infact actually not working using ping. R1#ping Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds:... Success rate is 0 percent (0/5) Do we have NLRI for or a default? R1#show ip route % Network not in table R1#show ip route Routing entry for /0, supernet Known via "static", distance 1, metric 0, candidate default path Routing Descriptor Blocks: * Route metric is 0, traffic share count is 1 And is the next-hop reachable? R1#ping Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds:.!!!! Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
4 At this point we can deduce that there is no apparent problem between R1 and R2 so let s now focus on R2. Let s make sure the inside and outside interfaces are up according to the diagram. R2#show ip interface brief exclude una down Any interface listed with OK? value "NO" does not have a valid configuration Interface IP-Address OK? Method Status Protocol Ethernet0/ YES manual up up Ethernet0/ YES manual up up Let s eliminate a connectivity problem between R2 and R3 using ping. R2#ping Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds:!!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms And lastly let s confirm that R3 has no NLRI for the internal private network of R1-R2. R3#show ip route begin Gateway Gateway of last resort is not set /16 is variably subnetted, 2 subnets, 2 masks C L /24 is directly connected, Ethernet0/ /32 is directly connected, Ethernet0/0 Because we are trying to route traffic from a network with a private address space out towards the provider (R3 in this case) we need NAT to translate the private IP addresses into the public IP address space allocated by the provider, in this case. Obviously from the title of this workbook the problem will be with NAT but in the real lab exam Cisco is not going to tell you what
5 the problem is so it is always good practice to go through the process to identify where the problem might be even if you are told what the problem actually is. The most basic component of a NAT configuration is specifying which interfaces are the inside interfaces and which ones are the outside interfaces (unless NVI is used in which case you just simply enable NAT under the interface). The following command will confirm which interfaces are enabled for NAT. R2#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Peak translations: 0 Outside interfaces: Ethernet0/0, Ethernet0/1 Inside interfaces: Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Outside Destination [Id: 1] access-list 100 interface Ethernet0/1 refcount 0 Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0 Both interfaces are specified as being NAT outside interfaces? Doesn t it make sense that E0/0 should be an inside interface and E0/1 is the outside interface rather than them both being NAT outside interfaces? Let s hypothesize that this is part of the problem and test whether changing the E0/0 configuration to be a NAT inside interface fixes the problem. R2(config)#int e0/0 R2(config-if)#no ip nat outside
6 R2(config-if)#ip nat inside Then verify our configuration. R2#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Peak translations: 0 Outside interfaces: Ethernet0/1 Inside interfaces: Ethernet0/0 Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Outside Destination [Id: 1] access-list 100 interface Ethernet0/1 refcount 0 Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0 This looks better, let s test out hypothesis from R1. You may be tempted to look for more problems for each ticket on the real lab but in my opinion you should try to do the minimum amount of changes to get solve the problem. Don t go looking for faults that aren t there. R1#ping Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds:... Success rate is 0 percent (0/5)
7 Still nothing. Let s run a debug on R2 for NAT (note that this command wasn t supported for me on CSR1KV but it works on IOU). R2#debug ip nat IP NAT debugging is on Then try to ping from R1 again. R1#ping repeat 1 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to , timeout is 2 seconds:. Success rate is 0 percent (0/1) However no debug output showed up on R2 meaning that R2 could not identify a translation policy that matched R1 s traffic to R3. Let s look at the policy on R2. R2#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Peak translations: 0 Outside interfaces: Ethernet0/1 Inside interfaces: Ethernet0/0 Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Outside Destination [Id: 1] access-list 100 interface Ethernet0/1 refcount 0
8 Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0 If you don t look at this output very often you may miss it but the problem has become apparently when we looked at what the configured NAT translation policy is doing. The configured one is for Outside Destination whereas we want to translate the source IP address from inside local to inside global. If you need a refresher on these terms you can look at the following document. Before we create a new NAT policy (or change the existing policy), let s confirm that the ACL 100 is matching the traffic that we want. R2#show access-list 100 Extended IP access list permit ip any Isn t the R1-R2 network /24 though? This ACL will never match that traffic. Let s create a new ACL that matches the traffic we actually want, which is IP traffic going from /24 to any destination. We could parse the config for any more references to this ACL (class maps, packet filtering, etc) to confirm that this ACL is not used by any other IOS functions, or we could simply just create a new ACL. Before creating it, let s confirm that we are not adding to an existing ACL as follows. R2#show access-list 101 Then create the new ACL. R2(config)#access-list 101 permit ip any
9 Seeing as we now believe the problem to be with the NAT policy configuration, we can use a show run to grab the existing the NAT policy, copy it to notepad (incase it is not actually the fix and you need to reapply the configuration), remove it, and add our new configuration. R2#show run s ip nat ip nat inside ip nat outside ip nat source list 100 interface Ethernet0/1 overload Then remove the configuration. R2(config)#no ip nat source list 100 interface Ethernet0/1 overload Then think about what we want to do: we want to translate the source IP address of inside traffic, which is /24, going to any destination out of the outside interface, which is E0/1 (we could also use a pool but its extra configuration that is unnecessary to fix this problem. Using these key pieces of information, we can configure the following (given that we have already configured a new ACL). R2(config)#ip nat inside source list 101 interface Ethernet0/1 overload Let s run the debug on R2 again. R2#debug ip nat IP NAT debugging is on Then try to ping from R1 to R3. R1#ping repeat 1 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to , timeout is 2 seconds:
10 ! Success rate is 100 percent (1/1), round-trip min/avg/max = 5/5/5 ms And on R2 we notice the following debug output. *Jan 17 02:08:36.626: NAT*: s= > , d= [17] *Jan 17 02:08:36.628: NAT*: s= , d= > [17] This is a good because it is showing us that R2 is translating (inside local) to (inside global), and then back again on the return packet. At this point we can consider this ticket solved!
11 Scenario #2 Solutions The acceptance criteria of this ticket from the perspective of R3 is that it can connect to on TCP port 80 and have the web server present some HTTP response (in this case, we can simply just use GET for the document root). Let s try to test this acceptance criteria as follows. R3#telnet Trying , % Connection refused by remote host The remote end (R2 in this case) sent back a RST so we can already confirm that connectivity is working to R2, so we can assume basic things like routing, ARP, etc, is working okay. Let s now confirm on R1 that the HTTP service is running and it has NLRI to the outside network. R1#show ip route Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP + - replicated route, % - next hop override Gateway of last resort is to network R* /0 [120/1] via , 00:00:24, Ethernet0/ /32 is subnetted, 1 subnets C is directly connected, Loopback /8 is variably subnetted, 2 subnets, 2 masks C L /24 is directly connected, Ethernet0/ /32 is directly connected, Ethernet0/0
12 And now check that the HTTP service is running. R1#show control-plane host open-ports Active internet connections (servers and established) Prot Local Address Foreign Address Service State tcp *:23 *:0 Telnet LISTEN tcp *:8080 *:0 HTTP CORE LISTEN The above command didn t work on CSR1KV but did on IOU, so an alternative command you can use to verify that the port is listening is as follows. R1#show ip http server status HTTP server status: Enabled HTTP server port: 8080 HTTP server active supplementary listener ports: HTTP server authentication method: enable HTTP server digest algorithm: md5 HTTP server access class: 0 HTTP server base path: HTTP server help root: Maximum number of concurrent server connections allowed: 5 Server idle time-out: 180 seconds Server life time-out: 180 seconds Maximum number of requests allowed on a connection: 1 HTTP server active session modules: ALL HTTP secure server capability: Present HTTP secure server status: Disabled HTTP secure server port: 443 HTTP secure server ciphersuite: 3des-ede-cbc-sha des-cbc-sha rc4-128-md5 rc sha HTTP secure server client authentication: Disabled HTTP secure server trustpoint:
13 HTTP secure server active session modules: ALL At this point we know two things: 1. R1 is listening on TCP port R3 is attempting to connect to the web service on TCP port 80 using the IP address From this information we can deduce that R2 needs is configured to translate the destination IP address of and TCP port 8080 to R1 on TCP port 80. This is referred to as port address redirection or port forwarding. As we did with the last scenario, let s confirm that there are NAT inside and outside interfaces, or that NVI is configured. R2#show ip nat statistics Total active translations: 1 (1 static, 0 dynamic; 1 extended) Peak translations: 1, occurred 00:00:06 ago Outside interfaces: Ethernet0/1 Inside interfaces: Ethernet0/0 Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0
14 According to the diagram and the original HTTP connectivity test we did at the start, this looks okay. We also notice that a static NAT policy exists so let s see what that looks like as follows. R2#show ip nat translations Pro Inside global Inside local Outside local Outside global tcp : :80 This is saying that R2 is configured to translate between the outside local address of and TCP port 8080 to the outside global address of and TCP port 80. Referring to the documentation and remembering our NAT terms for inside, outside, local, and global, does this configuration make sense? Aren t the addresses (R1 s loopback) and (R2 s interface connected to the R2-R3 network) both considered inside from the perspective of NAT? At this point we can deduce that there is a mistake in the configuration and I am going to purposely use show run here to show why this is often a bad idea to troubleshoot using that command. R2#show run s ip nat ip nat inside ip nat outside ip nat outside source static tcp extendable Your instincts might be to assume that the sole problem of this configuration is the outside keyword in the NAT policy and that the fix is to replace that keyword with inside. This is because you what you are translating from is usually listed first in the configuration and what you are translating to is listed second. R2(config)#no ip nat outside source static tcp extendable R2(config)#ip nat inside source static tcp extendable Now we verify our configuration. R2#show ip nat translations Pro Inside global Inside local Outside local Outside global tcp : :
15 But this doesn t make sense because is not an address assigned by a provider that represents one or more private hosts to the outside world is. More specifically, is not an inside global address and is not an inside local address; is the inside local address and is the inside global address. Once again, if you used the configuration solely to isolate this problem then you may miss this. The correct configuration is actually as follows. R2(config)#no ip nat inside source static tcp extendable R2(config)#ip nat inside source static tcp? A.B.C.D Inside local IP address R2(config)#ip nat inside source static tcp ? A.B.C.D Inside global IP address interface Specify interface for global address R2(config)#ip nat inside source static tcp extendable Now verify the configuration. R2#show ip nat translations Pro Inside global Inside local Outside local Outside global tcp : : This is looking much better. Let s run the following debug on R2 before testing it out from R3. R2#debug ip nat IP NAT debugging is on Then test from R3.
16 R3#telnet Trying , % Connection timed out; remote host not responding This is different to what we saw earlier; we are timing out the connection request rather being refused. Let s see what the debugs on R2 look like. R2# *Jan 17 03:03:07.213: NAT*: TCP s=48361, d=80->8080 *Jan 17 03:03:07.213: NAT*: s= , d= > [42624] R2# *Jan 17 03:03:09.213: NAT*: TCP s=48361, d=80->8080 *Jan 17 03:03:09.213: NAT*: s= , d= > [42624] R2# *Jan 17 03:03:13.213: NAT*: TCP s=48361, d=80->8080 *Jan 17 03:03:13.213: NAT*: s= , d= > [42624] R2# *Jan 17 03:03:21.213: NAT*: TCP s=48361, d=80->8080 *Jan 17 03:03:21.213: NAT*: s= , d= > [42624] We already confirmed earlier that R1 should has a default route so reachability back to shouldn t be a problem. Can we reach R1 s loopback from R2? R2#show ip route % Network not in table R2#show ip route % Network not in table We could add a static route to R1 s loopback but the scenario already told us that we couldn t do that. We also noticed earlier that R1 was receiving a default route via RIP from R2 so let s see what R1 itself is advertising via RIP.
17 R1#show ip protocols *** IP Routing is NSF aware *** Routing Protocol is "rip" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Sending updates every 30 seconds, next due in 6 seconds Invalid after 180 seconds, hold down 180, flushed after 240 Redistributing: rip Default version control: send version 2, receive version 2 Interface Send Recv Triggered RIP Key-chain Ethernet0/0 2 2 Automatic network summarization is not in effect Maximum path: 4 Routing for Networks: Routing Information Sources: Gateway Distance Last Update :00:03 Distance: (default is 120) As it turns out, RIP is the only IGP we are running and it is not advertising the /32 network, therefore R2 has no knowledge of how to get to after it translates the destination IP address from to Therefore, it is important to understand here that the NAT operation works but the routing does not. Let s enable RIP on all subnets in /8. R1(config)#router rip R1(config-router)#network Wait for the flash update to occur on R1 and for R2 to process and act on the update and once this occurs we can confirm that R2 has NLRI to /32
18 R2#show ip route Routing entry for /32 Known via "rip", distance 120, metric 1 Redistributing via rip Last update from on Ethernet0/0, 00:00:19 ago Routing Descriptor Blocks: * , from , 00:00:19 ago, via Ethernet0/0 Route metric is 1, traffic share count is 1 Now we can retry the test on R3. R3#telnet Trying , Open GET / HTTP/ Bad Request Date: Sat, 17 Jan :16:20 GMT Server: cisco-ios Connection: close Accept-Ranges: none 400 Bad Request [Connection to closed by foreign host] At this point we can consider this ticket solved too!
19 Scenario #3 Solutions The troubleshooting ticket has already indicated that basic connectivity between R1 to R2, and from R1 to R3 is working correctly. The problem occurs when R1 sources a ping from its loopback to either of these routers and we are not allowed to simply advertise the /24 through a routing protocol or use static routing to fix the problem. More specifically, the problem occurs when we are trying to source the ping from a private network to a public address space. We can confirm this as follows. R1#ping source loopback0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of Success rate is 0 percent (0/5) R1#ping source loopback0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of Success rate is 0 percent (0/5) Just like in the other scenarios, we first verify which interfaces are configured as NAT inside and outside, or whether NVI has been configured. R1#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Peak translations: 0 Outside interfaces: Ethernet0/0, Ethernet0/1 Inside interfaces: Hits: 0 Misses: 0
20 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Inside Source [Id: 1] access-list ISPR2 pool ISPR2_POOL refcount 0 pool ISPR2_POOL: netmask start end type generic, total addresses 1, allocated 0 (0%), misses 0 [Id: 2] access-list ISPR3 pool ISPR3_POOL refcount 0 pool ISPR3_POOL: netmask start end type generic, total addresses 1, allocated 0 (0%), misses 0 Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0 Immediately we see a problem: there are no inside interfaces. We need to first enable R1 s loobpack0 interface as a NAT inside interface. R1(config)#interface loop0 R1(config-if)#ip nat inside Then verify the result of our configuration. R1#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Peak translations: 0 Outside interfaces: Ethernet0/0, Ethernet0/1
21 Inside interfaces: Loopback0 Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Inside Source [Id: 1] access-list ISPR2 pool ISPR2_POOL refcount 0 pool ISPR2_POOL: netmask start end type generic, total addresses 1, allocated 0 (0%), misses 0 [Id: 2] access-list ISPR3 pool ISPR3_POOL refcount 0 pool ISPR3_POOL: netmask start end type generic, total addresses 1, allocated 0 (0%), misses 0 Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0 Let s see if this has fixed the problem using a general NAT debug and ping. R1#debug ip nat IP NAT debugging is on R1#ping source loopback0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of Success rate is 0 percent (0/5)
22 However we saw nothing in the debug output so this is leaning us towards a problem with the NAT policy configuration. You are probably getting sick of this command already but it is useful for troubleshooting NAT! R1#show ip nat statistics Total active translations: 0 (0 static, 0 dynamic; 0 extended) Peak translations: 0 Outside interfaces: Ethernet0/0, Ethernet0/1 Inside interfaces: Loopback0 Hits: 0 Misses: 0 CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings: -- Inside Source [Id: 1] access-list ISPR2 pool ISPR2_POOL refcount 0 pool ISPR2_POOL: netmask start end type generic, total addresses 1, allocated 0 (0%), misses 0 [Id: 2] access-list ISPR3 pool ISPR3_POOL refcount 0 pool ISPR3_POOL: netmask start end type generic, total addresses 1, allocated 0 (0%), misses 0 Total doors: 0 Appl doors: 0 Normal doors: 0 Queued Packets: 0
23 If we consider the first one isolation (ID of 1), it is referencing an ACL called ISPR2 for matching traffic and is translating it to an IP address in the pool called ISPR2_POOL. We can already see from above that the ISPR2_POOL has the range of to , which is the IP address configured on R1 s E0/0 interface. Let s confirm the ACL now. R1#show access-list ISPR2 Noting shows up. Do we have any access-lists at all (i.e. maybe they are configured but are referenced incorrectly)? R1#show access-lists So we have multiple NAT pools but do not have any criteria to select which one to use. The answer to this fix is route maps. The NAT policy configuration should be referencing route maps here, selecting on the ACLs or the outgoing interface. Because we cannot configure any new ACLs, we must use route maps where we can match on the outgoing interface or next-hop of the traffic to select which NAT pool to use. Let s confirm whether any route maps have been configured. R1#show route-map route-map ISPR2, permit, sequence 10 Match clauses: interface Ethernet0/1 Set clauses: Policy routing matches: 0 packets, 0 bytes route-map ISPR3, permit, sequence 10 Match clauses: interface Ethernet0/0 Set clauses: Policy routing matches: 0 packets, 0 bytes
24 We can see what the network administrator has done here. They have referenced ISPR2 and ISPR3 as an ACL when they should have been referenced as a route map. Let s grab the configuration and change the reference to an ACL to reference a route map. R1#show run s ip nat ip nat inside ip nat outside ip nat outside ip nat pool ISPR2_POOL netmask ip nat pool ISPR3_POOL netmask ip nat inside source list ISPR2 pool ISPR2_POOL ip nat inside source list ISPR3 pool ISPR3_POOL Then remove the existing policies. R1(config)#no ip nat inside source list ISPR2 pool ISPR2_POOL R1(config)#no ip nat inside source list ISPR3 pool ISPR3_POOL Then we simply use the same commands as above except that we change the list keyword to route-map. R1(config)#ip nat inside source route-map ISPR2 pool ISPR2_POOL R1(config)#ip nat inside source route-map ISPR3 pool ISPR3_POOL Now we run a generalised NAT debug and try to test the original pings again. R1#debug ip nat IP NAT debugging is on R1#ping source loopback0 repeat 1 Type escape sequence to abort.
25 Sending 1, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of Success rate is 0 percent (0/1) *Jan 17 03:58:04.926: NAT: s= > , d= [20] Hmm, that didn t work. Let s see what happens when we try to ping R3. R1#ping source loopback0 repeat 1 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of Success rate is 0 percent (0/1) *Jan 17 03:59:34.822: NAT: s= > , d= [21] Can you see what the problem is? If you aren t used to the above debug output maybe the following will make it clearer on R2. R2#debug ip icmp ICMP packet debugging is on Then run the test again on R1 to R2. R1#ping source loopback0 repeat 1 Type escape sequence to abort. Sending 1, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of Success rate is 0 percent (0/1)
26 And observe the debug output on R2. R2# *Jan 17 04:01:48.323: ICMP: echo reply sent, src , dst , topology BASE, dscp 0 topoid 0 The source IP address on R1 is being translated from to , which is the IP address on the R1-R3 segment, and a similar thing is happening when R1 pings R3 because the source IP address is being translated from to which is the IP address configured on R1 s E0/0 interface on the R1-R2 segment. That is, the route map is configured incorrectly. R1#show route-map route-map ISPR2, permit, sequence 10 Match clauses: interface Ethernet0/1 Set clauses: Policy routing matches: 0 packets, 0 bytes route-map ISPR3, permit, sequence 10 Match clauses: interface Ethernet0/0 Set clauses: Policy routing matches: 0 packets, 0 bytes If we compare this to the IP addresses configured on the interfaces, which are as follows. R1#show ip interface brief exc una down Interface IP-Address OK? Method Status Protocol Ethernet0/ YES manual up up Ethernet0/ YES manual up up Loopback YES manual up up NVI YES unset up up
27 We can see that the route maps have the wrong outgoing interfaces. The ISPR2 route map should be referencing E0/0 and the ISPR3 route map should be referencing E0/1. Let s fix this as follows. R1(config)#route-map ISPR2 permit 10 R1(config-route-map)#no match interface R1(config-route-map)#match interface E0/0 R1(config)#no route-map ISPR3 permit 10 R1(config)#route-map ISPR3 permit 10 R1(config-route-map)#match interface E0/1 Note that there are a few ways you can change the configuration. Let s now verify the configuration on R1 when it tries to ping R2 and R3 sourcing the packet from its loopback interface. R1#ping source loopback0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R1#ping source loopback0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to , timeout is 2 seconds: Packet sent with a source address of !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms Then as a final check verify the NAT translation table as follows. R1#show ip nat translations
28 Pro Inside global Inside local Outside local Outside global icmp : : : :11 icmp : : : :12 Which looks good!
LAB5: OSPF IPv4. OSPF: Stub. Disclaimer
Page1 LAB5: SPF IPv4 Disclaimer This onfiguration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material
More informationRouting Information Protocol Version 2.0
Routing Information Protocol Version 2.0 RIPv2 Objective: onfigure RIPv2 between R1 and R2 to obtain connectivity between Networks Directions onfigure R1's interface F0/0 with the IP address 10.1.0.1/16
More informationEIGRP Lab / lo1. .1 lo / /30
EIGRP Lab 172,16,1.0/24.1 lo1 192.168.20.0/30.2.1 Merida fa0 fa0 Vargas lo2.1 lo2.5.1 lo1 192.168.30.0/24 172.16.2.0/24 192.168.20.4.0/30 Scenario: Loopback0 is used for RouterID Loopback1 is a virtual
More informationContents. Introduction. Prerequisites. Requirements
Contents Introduction Prerequisites Requirements Components Used Configure Network Diagram Configurations Verify Inheritence with EIGRP Named mode Route Replication with EIGRP name mode Routing Context
More informationChapter 7 Lab 7-2, Using the AS_PATH Attribute
Chapter 7 Topology Objectives Use BGP commands to prevent private AS numbers from being advertised to the outside world. Use the AS_PATH attribute to filter BGP routes based on their source AS numbers.
More informationLab 2.8.1: Basic Static Route Configuration
Topology Diagram Addressing Table Device Interface IP Address Subnet Mask Default Gateway R1 Fa0/0 172.16.3.1 255.255.255.0 N/A S0/0/0 172.16.2.1 255.255.255.0 N/A Fa0/0 172.16.1.1 255.255.255.0 N/A R2
More informationGRE Tunnel with VRF Configuration Example
GRE Tunnel with VRF Configuration Example Document ID: 46252 Contents Introduction Prerequisites Requirements Components Used Conventions Configure Network Diagram Configurations Verify Troubleshoot Caveats
More informationStep 1: IP Configuration: On R1: On R2: On R3: R1(config)#int s1/2 R1(config-if)#ip addr R1(config-if)#no shu
Step 1: IP Configuration: n R1: R1(config)#int s1/2 R1(config-if)#ip addr 12.1.1.1 255.255.255.0 R1(config-if)#no shu R1(config-if)#int lo0 R1(config-if)#ip addr 1.1.1.1 255.0.0.0 R1(config-if)#int lo1
More informationImplement Static Routes for IPv6 Configuration Example
Implement Static Routes for IPv6 Configuration Example Document ID: 113361 Contents Introduction Prerequisites Components Used Conventions Configure Network Diagram Configurations Verify Related Information
More informationConfiguration and Management of Networks
Configuring BGP using the AS_PATH attribute Topology Objectives Background Use BGP commands to prevent private AS numbers from being advertised to the outside world. Use the AS_PATH attribute to filter
More informationThis document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and
This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and exclusive use by instructors in the CCNA Exploration:
More informationChapter 4 Lab 4-2, Redistribution Between EIGRP and OSPF
Chapter 4 Lab 4-2, Redistribution Between EIGRP and OSPF Topology Objectives Review EIGRP and OSPF configuration. Redistribute into EIGRP. Redistribute into OSPF. Summarize routes in EIGRP. Filter routes
More informationEasy Virtual Network Configuration Example
Easy Virtual Network Configuration Example Document ID: 117974 Contributed by Fabrice Ducomble, Cisco TAC Engineer. Aug 04, 2014 Contents Introduction Prerequisites Requirements Components Used Background
More informationDistance vector Routing protocols. 2000, Cisco Systems, Inc. 9-1
Distance vector Routing protocols 2000, Cisco Systems, Inc. 9-1 IP Routing Configuration Tasks Router configuration Select routing protocols Specify networks or interfaces RIP Network 172.16.0.0 IGRP,
More informationBuilding the Routing Table. Introducing the Routing Table Directly Connected Networks Static Routing Dynamic Routing Routing Table Principles
Building the Routing Table Introducing the Routing Table Directly Connected Networks Static Routing Dynamic Routing Routing Table Principles Introducing the Routing Table R1# show ip route Codes: C - connected,
More informationChapter 1 Lab 1-1, Basic RIPng and Default Gateway Configuration
Chapter 1 Lab 1-1, Basic RIPng and Default Gateway Configuration Topology Objectives Configure IPv6 addressing. Configure and verify RIPng on R1 and R2. Configure IPv6 static routes between R2 and R3.
More informationAS 100 AS 300. Lab -1 Private Communities - II .1 S1/2. Task 1. On R1: / / /24. Configure the above topology.
Lab -1 Private Communities - II AS 100.1 R1 S1/2 12.1.1.0/24 S1/1.2 R2 S1/3 S1/3 13.1.1.0/24 23.1.1.0/24 S1/1.3 R3 S1/2 Lo0 6.6.6.0/24 Lo1 7.7.7.0/24 AS 300 Task 1 Configure the above topology. On R1:
More informationRealCiscoLAB.com. Chapter 6 Lab 6-2, Using the AS_PATH Attribute. Topology. Objectives. Background. CCNPv6 ROUTE
RealCiscoLAB.com CCNPv6 ROUTE Chapter 6 Lab 6-2, Using the AS_PATH Attribute Topology Objectives Background Use BGP commands to prevent private AS numbers from being advertised to the outside world. Use
More informationThis chapter covers the following subjects:
This chapter covers the following subjects: Configuring and Testing Static Routes Distance Vector Concepts Configuring RIP and IGRP C H A P T E R 5 RIP, IGRP, and Static Route Concepts and Configuration
More informationChapter 7 Lab 7-1, Configuring BGP with Default Routing
Chapter 7 Topology Objectives Configure BGP to exchange routing information with two ISPs. Background The International Travel Agency (ITA) relies extensively on the Internet for sales. For this reason,
More informationLab: Basic Static Route Configuration
Lab: Basic Static Route onfiguration Topology Diagram Addressing Table Device Interface IP Address Subnet Mask Default Gateway R1 Fa0/0 172.16.3.1 255.255.255.0 N/A S0/0/0 172.16.2.1 255.255.255.0 N/A
More informationLab 5-3 Redistribution Between EIGRP and IS-IS
Lab 5-3 Redistribution Between EIGRP and IS-IS Learning Objectives Review basic configuration of EIGRP and IS-IS Redistribute into EIGRP Redistribute into IS-IS Use a standard access list to select routes
More informationLAB8: OSPF IPv4. OSPF: Virtual Link. Disclaimer
Page1 AB8: OSPF IPv4 Disclaimer This onfiguration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material
More informationDynamic Multipoint VPN (DMVPN) Troubleshooting Scenarios
Dynamic Multipoint VPN (DMVPN) Troubleshooting Scenarios Luke Bibby, CCIE #45527 Introduction This small workbook is meant to provide additional practice with troubleshooting Dynamic Multipoint VPN (DMVPN)
More informationRealCiscoLAB.com. Chapter 2 Lab 2-2, EIGRP Load Balancing. Topology. Objectives. Background. CCNPv6 ROUTE
RealCiscoLAB.com CCNPv6 ROUTE Chapter 2 Lab 2-2, EIGRP Load Balancing Topology Objectives Background Review a basic EIGRP configuration. Explore the EIGRP topology table. Identify successors, feasible
More informationLAB1: BGP IPv4. BGP: Initial Config. Disclaimer
Page1 LAB1: BGP IPv4 Disclaimer This Configuration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material
More informationLab Configuring IPv4 Static and Default Routes (Solution)
(Solution) Topology Addressing Table Device Interface IP Address Subnet Mask Default Gateway R1 G0/1 192.168.0.1 255.255.255.0 N/A S0/0/1 10.1.1.1 255.255.255.252 N/A R3 G0/1 192.168.1.1 255.255.255.0
More informationAdapted from the Synchronization example in g/case/studies/icsbgp4.html
Adapted from the Synchronization example in http://www.cisco.com/en/us/docs/internetworkin g/case/studies/icsbgp4.html When an AS provides transit service to other ASs when there are non-bgp routers in
More informationLayer3 VPN with OSPF Protocol between CE-PE
MPLS Layer3 VPN with OSPF Protocol between CE-PE Disclaimer This Configuration Guide is designed to assist members to enhance their skills in particular technology area. While every effort has been made
More informationChapter 6 Lab 6-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED
Chapter 6 Lab 6-3, Configuring IBGP and EBGP Sessions, Local Preference, and MED Topology Objectives Background For IBGP peers to correctly exchange routing information, use the next-hop-self command with
More informationLab 2-3 Summarization and Default Network Advertisement
Lab 2-3 Summarization and efault Network Advertisement Learning Objectives Review basic EIGRP configuration onfigure and verify EIGRP auto-summarization onfigure and verify EIGRP manual summarization Learn
More informationLab Configuring Port Address Translation (PAT) (Instructor Version)
(Instructor Version) Instructor Note: Red font color or gray highlights indicate text that appears in the instructor copy only. Topology Addressing Table Objectives Device Interface IP Address Subnet Mask
More informationChapter 4 Lab 4-1, Redistribution Between RIP and OSPF
hapter 4 Lab 4-1, Redistribution Between RIP and OSPF Topology Objectives Review configuration and verification of RIP and OSPF. onfigure passive interfaces in both RIP and OSPF. Filter routing updates
More informationLab 3.5.1: Basic Frame Relay
Lab 3.5.1: Basic Frame Relay Topology Diagram Addressing Table Device Interface IP Address Subnet Mask R1 R2 Default Gateway Fa0/0 192.168.10.1 255.255.255.0 N/A S0/0/1 10.1.1.1 255.255.255.252 N/A S0/0/1
More informationBasic Router Configuration
This section includes information about some basic router configuration, and contains the following sections: Default Configuration, on page 1 Configuring Global Parameters, on page 2 Configuring Gigabit
More informationCIS 83 LAB 3 - EIGRP Rich Simms September 23, Objective. Scenario. Topology
CIS 83 LAB 3 - EIGRP Rich Simms September 23, 2006 Objective The objective of this lab is to become familiar setting up and configuring EIGRP on three routers. EIGRP is a Cisco proprietary distance-vector
More informationThe information in this document is based on Cisco IOS Software Release 15.4 version.
Contents Introduction Prerequisites Requirements Components Used Background Information Configure Network Diagram Relevant Configuration Verify Test case 1 Test case 2 Test case 3 Troubleshoot Introduction
More informationChapter 4 Lab 4-2, Controlling Routing Updates. Topology. Objectives. CCNPv7 ROUTE
Chapter 4 Lab 4-2, Controlling Routing Updates Topology Objectives Filter routes using a distribute list and ACL. Filter routes using a distribute list and prefix list. Filter redistributed routes using
More informationFailover with EIGRP Using VRF Configuration Example
Failover with EIGRP Using VRF onfiguration Example ocument I: 113446 ontents Introduction Prerequisites Hardware and Software Versions onventions onfigure Network iagram onfigurations Verify Show ommands
More informationChapter 6: Network Layer
Chapter 6: Network Layer Introduction to Networks Intro to Networks v5 Network Layer Intro to Networks v5 2 The Network Layer End to End Transport processes Addressing end devices Encapsulation of Packets
More informationAntonio Cianfrani. Routing Protocols
Antonio Cianfrani Routing Protocols Routing protocols A routing protocol provides a communication channel among routers to exchange reachability information about networks Routing tables are properly configured
More informationLab - Troubleshooting Connectivity Issues
Lab - Troubleshooting Connectivity Issues Topology Addressing Table R1 ISP Objectives Device Interface IP Address Subnet Mask Default Gateway G0/1 192.168.1.1 255.255.255.0 N/A S0/0/0 10.1.1.1 255.255.255.252
More informationv5.0 Narbik Kocharians CCSI, CCIE #12410 R&S, Security, SP Physical or Logical
CCIE Foundation v5.0 www.micronicstraining.com Narbik Kocharians CCSI, CCIE #12410 R&S, Security, SP Physical or Logical R&S Foundation by Narbik Kocharians CCIE R&S Foundation v5.0 Page 1 of 90 LAB 2
More informationRIPv2. Routing Protocols and Concepts Chapter 7. ITE PC v4.0 Chapter Cisco Systems, Inc. All rights reserved. Cisco Public
RIPv2 Routing Protocols and Concepts Chapter 7 1 Objectives Encounter and describe the limitations of RIPv1 s limitations. Apply the basic Routing Information Protocol Version 2 (RIPv2) configuration commands
More informationSTUDENT LAB GUIDE CCNA ( )
STUDENT LAB GUIDE CCNA (640-802) Developed By, Router Infotech Career Academy LAB: 09 Static Route Configuration Objective: To configure & implement Static Route successfully on said devices and test its
More informationLAB8: Named EIGRP IPv4
Page1 AB8: Named EIGRP IPv4 isclaimer This onfiguration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material
More informationChapter 4 Lab 4-1, Redistribution Between EIGRP and OSPF. Topology. Objectives. CCNPv7 ROUTE
hapter 4 Topology Objectives Review EIGRP and OSPF configuration. Summarize routes in EIGRP. Summarize in OSPF at an ABR. Redistribute into EIGRP. Redistribute into OSPF. Summarize in OSPF at an ASBR.
More informationLAB11: EIGRP IPv4. EIGRP: Stub. Disclaimer
Page1 AB11: EIGRP IPv4 isclaimer This onfiguration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material
More informationLab Configuring Dynamic and Static NAT (Solution)
(Solution) Topology Addressing Table Objectives Device Interface IP Address Subnet Mask Default Gateway Gateway G0/1 192.168.1.1 255.255.255.0 N/A S0/0/1 209.165.201.18 255.255.255.252 N/A ISP S0/0/0 (DCE)
More informationLab Configuring Static NAT
Lab 10.5.1 Configuring Static NAT Objective Configure Network Address Translation (NAT) static translation to provide reliable outside access to three shared company servers. Scenario Step 1 The International
More informationLab Configuring Port Address Translation (PAT) Topology
Topology Addressing Table Objectives Device Interface IP Address Subnet Mask Default Gateway Gateway G0/1 192.168.1.1 255.255.255.0 N/A S0/0/1 209.165.201.18 255.255.255.252 N/A ISP S0/0/0 (DCE) 209.165.201.17
More informationCCNA Exploration: Routing Protocols and Concepts Chapter 8 Case Study
Objectives: Consolidate routing table reading skills. Introduce the idea of more than 1 routing protocol running into the same router. Explain the use of routes to Null0 interface. Intro: Connex Inc. is
More informationChapter 6 Lab 6-4, BGP Route Reflectors and Route Filters
Chapter 6 Lab 6-4, BGP Route Reflectors and Route Filters Topology Objectives Background Configure IBGP routers to use a route reflector and a simple route filter. The International Travel Agency maintains
More informationTELECOMMUNICATION MANAGEMENT AND NETWORKS
QUAID-E-AWAM UNIVERSITY OF ENGINEERING SCIENCE AND TECHNOLOGY, NAWABSHAH TELECOMMUNICATION MANAGEMENT AND NETWORKS LAB # 3 CONFIGURING INTERFACES OF ROUTER AND SWITCH Topology Diagram Addressing Table
More informationDMVPN Topology. Page1
DMVPN DMVPN Topology Page1 LAB 2: Configure EIGRP over DMVPN: Task 1: Configure EIGRP over DMVPN Process Step 1 In the configuration mode of router configure EIGRP over DMVPN by following command: R1:
More informationCCNP ROUTE LAB MANUAL
CCNP ROUTE 300-101 UNiNets CCNP Cisco Certified Network Professional ROUTE LAB MANUAL CCNP TOPOLOGY Lab: ibgp Synchronization TASK Configure BGP per the diagram to obtain connectivity from AS 1 to R4 and
More informationLab Configuring Dynamic and Static NAT (Instructor Version Optional Lab)
(Instructor Version Optional Lab) Instructor Note: Red font color or gray highlights indicate text that appears in the instructor copy only. Optional activities are designed to enhance understanding and/or
More informationLAB15: EIGRP IPv4. LAB 15: Diagram. Disclaimer
AB15: EIGRP IPv4 isclaimer This onfiguration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material is as
More informationRR> RR> RR>en RR# RR# RR# RR# *Oct 2 04:57:03.684: %AMDP2_FE-6-EXCESSCOLL: Ethernet0/2 TDR=0, TRC=0 RR#
RR> RR> RR>en *Oct 2 04:57:03.684: %AMDP2_FE-6-EXCESSCOLL: Ethernet0/2 TDR=0, TRC=0 term len 0 show run Building configuration... Current configuration : 2568 bytes version 15.4 service timestamps debug
More informationShortcut Switching Enhancements for NHRP in DMVPN Networks
Shortcut Switching Enhancements for NHRP in DMVPN Networks Routers in a Dynamic Multipoint VPN (DMVPN) Phase 3 network use Next Hop Resolution Protocol (NHRP) Shortcut Switching to discover shorter paths
More informationHow to Configure a Cisco Router Behind a Non-Cisco Cable Modem
How to Configure a Cisco Router Behind a Non-Cisco Cable Modem Document ID: 19268 Contents Introduction Prerequisites Requirements Components Used Conventions Configure Network Diagram Configurations Verify
More informationLab- Troubleshooting Basic EIGRP for 1Pv4
Lab- Troubleshooting Basic EIGRP for 1Pv4 Topology G0/0 G0/0 PC-A PC-C 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 27 Addressing Table efault Gateway
More informationRIP. Table of Contents. General Information. Summary. Specifications
RIP Document revision 1 (Wed Mar 24 12:32:12 GMT 2004) This document applies to V2.8 Table of Contents Table of Contents General Information Summary Specifications Related Documents Additional Documents
More informationChapter 8 Lab 8-3, Configuring 6to4 Tunnels
Chapter 8 Lab 8-3, Configuring 6to4 Tunnels Topology Objectives Configure EIGRP for IPv4. Create a 6to4 tunnel. Configure static IPv6 routes. Background In this lab, you configure EIGRP for full connectivity
More informationChapter 5: Maintaining and Troubleshooting Routing Solutions
Chapter 5: Maintaining and Troubleshooting Routing Solutions CCNP TSHOOT: Maintaining and Troubleshooting IP Networks Course v6 1 Troubleshooting Network Layer Connectivity 2 Routing and Routing Data Structures
More informationLab Configuring Basic RIPv2 (Solution)
(Solution) Topology 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. Page 1 of 15 Addressing Table Objectives Device Interface IP Address Subnet Mask Default Gateway
More informationLab Configuring IGRP Instructor Version 2500
Lab 7.3.5 Configuring IGRP Instructor Version 2500 Objective Setup IP an addressing scheme using class C networks. Configure IGRP on routers. Background/Preparation Cable a network similar to the one in
More informationChapter 3 Lab 3-2, Multi-Area OSPFv2 and OSPFv3 with Stub Area
Chapter 3 Topology Objectives Configure multi-area OSPFv2 for IPv4. Configure multi-area OSPFv3 for IPv6 Verify multi-area behavior. Configure stub and totally stubby areas for OSPFv2. Configure stub and
More informationCCNA Exploration: Routing Protocols and Concepts Chapter 11 Case Study
bjectives: Consolidate SPF knowledge. Describe the operation of SPF multi-area. Introduce the concept of route summarization with SPF. Introduce the concept of SPF optimization. Intro: Trevni Inc. needed
More informationFlexVPN HA Dual Hub Configuration Example
FlexVPN HA Dual Hub Configuration Example Document ID: 118888 Contributed by Piotr Kupisiewicz, Wen Zhang, and Frederic Detienne, Cisco TAC Engineers. Apr 08, 2015 Contents Introduction Prerequisites Requirements
More informationLab- Configuring Basic Single-Area OSPFv2
Lab- onfiguring Basic Single-Area OSPFv2 Topology G0/0 G0/0 2013 isco and/or its affiliates. All rights reserved. This document is isco Public. Page 1 of 29 Addressing Table Objectives Device Interface
More informationEIGRP on SVTI, DVTI, and IKEv2 FlexVPN with the "IP[v6] Unnumbered" Command Configuration Example
EIGRP on SVTI, DVTI, and IKEv2 FlexVPN with the "IP[v6] Unnumbered" Command Configuration Example Document ID: 116346 Contributed by Michal Garcarz and Olivier Pelerin, Cisco TAC Engineers. Sep 18, 2013
More informationMPLS Troubleshooting. Contents. Prerequisites. Document ID: Requirements. Components Used
MPLS Troubleshooting Document ID: 12492 ontents Introduction Prerequisites Requirements omponents Used onventions Troubleshoot Procedures Verify That Routing Protocol Runs Verify EF Switching Verify MPLS
More information3 ROUTER SETUP WITH FRAME RELAY CONFIGURATION OF FRAME RELAY ROUTER
3 ROUTER SETUP WITH FRAME RELAY R2 s0 Network 192.168.1.0 s1 DCE * Frame Relay Network * s0 192.168.1.0 s0 DCE R1 Hardware Requirement: 1 Router with t 2 Serials 2 Router with 1 Serial 2 DTE/DCE Serial
More information2016 Braindump2go Valid Cisco Exam Preparation Materials:
2016 NEW Cisco CCNP Routing and Switching 300-101: Implementing Cisco IP Routing (ROUTE) Exam Questions and Answers RELEASED in Braindump2go.com Online IT Study Website Today! 2016 Braindump2go Valid Cisco
More informationThis document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and
This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and exclusive use by instructors in the CCNA Exploration:
More informationFinal exam study Guide
Final exam study Guide K-1A * In relationship to the OSI layer model and encapsulation/decapsulation process, what happen to a packet that travels through multiple hops of routers? - What happen to the
More informationMultihoming with BGP and NAT
Eliminating ISP as a single point of failure www.noction.com Table of Contents Introduction 1. R-NAT Configuration 1.1 NAT Configuration 5. ISPs Routers Configuration 3 15 7 7 5.1 ISP-A Configuration 5.2
More informationCase Study 2: Frame Relay and OSPF Solution
Case Study 2: Frame Relay and OSPF Solution Objective In this case study, you troubleshoot a complex scenario involving Frame Relay and Open Shortest Path First (OSPF). Figure 2-1 shows the topology for
More informationKIM DONNERBORG / RTS. Cisco Lab Øvelse Af Kim Donnerborg / RTS. Side 0 af 8
KIM DONNERBORG / RTS Side 0 af 8 INDHOLDSFORTEGNELSE Lab: Basic Router Configuration... 2 Topology Diagram... 2 Addressing Table... 2 Learning Objectives... 2 Scenario... 2 Task 1: Cable the Network....
More informationMPLS for R&S CCIE Candidates
MPLS for R&S CCIE Candidates Johnny Bass CCIE #6458 2 About the Presenter Johnny Bass Networking industry since the late 1980s CCIE R&S #6458 CCSI 97168 Cisco 360 R&S Master Instructor Course director
More informationChapter 2 Lab 2-1, EIGRP Configuration, Bandwidth, and Adjacencies
Chapter 2 Lab 2-1, EIGRP Configuration, Bandwidth, and Adjacencies Topology Objectives Background Configure EIGRP on multiple routers. Configure the bandwidth command to modify the EIGRP metric. Verify
More informationLab 1 BGP Automatic-tag, AS-path tag and Table-map
Lab 1 BGP Automatic-tag, AS-path tag and Table-map Lo0 1.1.1.1 /24 AS 100.1 R1 S1/3 13.1.1.0/24 S1/1 S1/2 AS 300 AS 400.3 R3 34.1.1.0/24 S2/0 S1/3.4 R4 Lo0 2.2.2.2 /24.2 R2 AS 200 S1/3 23.1.1.0/24 Task
More informationAdvanced Troubleshooting CCIE Routing & Switching v5.0
Advanced Troubleshooting CCIE Routing & Switching v5.0 www.micronicstraining.com Narbik Kocharians CCSI, CCIE #12410 R&S, Security, SP Switching-I Questions & Answers CCIE R&S by Narbik Kocharians Advanced
More informationShooting Trouble with IP
C H A P T E R 3 Shooting Trouble with IP This chapter focuses on a number of objectives falling under the CCNP Troubleshooting guidelines. Understanding basic TCP/IP troubleshooting principles not only
More informationscope scope {global vrf vrf-name} no scope {global vrf vrf-name} Syntax Description
Multi-Toplogy Routing Commands scope scope To define the scope for a Border Gateway Protocol (BGP) routing session and to enter router scope configuration mode, use the scope command in router configuration
More informationNetwork Layer Week 5. Module : Computer Networks Lecturer: Lucy White Office : 324
Network Layer Week 5 Module : Computer Networks Lecturer: Lucy White lbwhite@wit.ie Office : 324 1 Network Layer Network Layer Protocols Common Network Layer Protocols Internet Protocol version 4 (IPv4)
More informationInformation About Routing
19 CHAPTER This chapter describes underlying concepts of how routing behaves within the adaptive security appliance, and the routing protocols that are supported. The chapter includes the following sections:,
More informationDraft Manuscript Draft M. Manuscript Draft Ma. t Manuscript Draft Manu. ipt Draft Manuscript Dra. anuscript Draft Manuscri
M aft Ma CHAPTER 5 ript Dra RIP Version 1 Objectives aft Ma Upon completion of this chapter, you should be able to answer the following questions: What are the functions, characteristics, and operation
More informationRouting Overview. Information About Routing CHAPTER
21 CHAPTER This chapter describes underlying concepts of how routing behaves within the ASA, and the routing protocols that are supported. This chapter includes the following sections: Information About
More informationConfiguration and Management of Networks
EIGRP Summarization and efault Network Advertisement The lab is built on the topology: Topology Objectives Review a basic EIGRP configuration. onfigure and verify EIGRP auto-summarization. onfigure and
More informationChapter 4: Manipulating Routing
: Manipulating Routing Updates CCNP ROUTE: Implementing IP Routing ROUTE v6 1 Objectives Describe network performance issues and ways to control routing updates and traffic (3). Describe the purpose of
More informationConfiguring FlexVPN Spoke to Spoke
Last Published Date: March 28, 2014 The FlexVPN Spoke to Spoke feature enables a FlexVPN client to establish a direct crypto tunnel with another FlexVPN client leveraging virtual tunnel interfaces (VTI),
More informationGetCertkey. No help, Full refund!
GetCertkey http://www.getcertkey.com No help, Full refund! Exam : 300-101 Title : Implementing Cisco IP Routing Vendor : Cisco Version : DEMO Get Latest & Valid 300-101 Exam's Question and Answers 1 from
More informationCisco 360 CCIE R&S Advanced Workshop 2 Assessment Lab 1
CIERSASSESS-5-AK Cisco 360 CCIE R&S Advanced Workshop 2 Assessment Lab 1 The Cisco 360 CCIE Routing and Switching (R&S) Advanced Workshop 2 is a five-day course for CCIE candidates who are ready to attempt
More informationLab 2.5.1: Basic PPP Configuration Lab
Topology Diagram Addressing Table Device Interface IP Address Subnet Mask R1 R2 R3 Default Gateway Fa0/1 192.168.10.1 255.255.255.0 N/A S0/0/0 10.1.1.1 255.255.255.252 N/A Lo0 209.165.200.225 255.255.255.224
More informationConfiguring PPP over Ethernet with NAT
CHAPTER 3 The Cisco Secure Router 520 Ethernet-to-Ethernet routers support Point-to-Point Protocol over Ethernet (PPPoE) clients and network address translation (NAT). Multiple PCs can be connected to
More informationLayer3 VPN with RIP protocol between CE-PE
MPLS Layer3 VPN with IP protocol between E-PE Disclaimer This onfiguration Guide is designed to assist members to enhance their skills in particular technology area. While every effort has been made to
More informationLAB16: Named EIGRP IPv4
AB16: Named EIGRP IPv4 isclaimer This onfiguration Guide is designed to assist members to enhance their skills in respective technology area. While every effort has been made to ensure that all material
More informationTroubleshooting LSP Failure in MPLS VPN
Troubleshooting LSP Failure in MPLS VPN Document ID: 23565 Contents Introduction Prerequisites Requirements Components Used Conventions Network Diagram Router Configurations Problem Cause of the LSP Failure
More information