![]() R1(config)#ip local policy route-map LocalNextHopĪnd to test it out, we will use our new friend extended traceroute: To makes things harder on my already exhausted brain, I assigned loopback names to match the IP addresses: However if we are using an extended traceroute, it is because we are simulating traffic from another network for testing the path, but as we well know Policy Routing requires an interface of the incoming traffic to Policy Route and this is where Local Policy Routing comes into play. The source IP address must be on one of our “Up” interfaces on the local router, so beine this requires a Physical or Logical interface that is in “Up” status, it sounds like Loopback interfaces is the way to go as they won’t go down unless administratively. It’s like a build your own sundae, you can just keep adding scoops of detail to your traceroute, but as can be seen highlighted in red text we have an important message. % Invalid source address- IP address not on any of our up interfaces Virtual-Template Virtual Template interface Port-channel Ethernet Channel of interfaces ![]() MFR Multilink Frame Relay bundle interface “traceroute (dest IP) source (source IP)” to simulate traffic from that networkĪlso to note on the second method, you can actually source several different ways, shown with the extended options as I fill them out, so there shall be a bit of output:.Type “traceroute” and hit enter to fill in options exactly like an extended ping.The first thing to note that I have amazingly not known at all until this video, from a router there are two ways to do extended traceroutes (like extended pings): Do NOT modify console.Still working with the same Topology seen above, I want to round off the Policy Routing videos to see if I can bring that into some scenario or freestyle lab, and see how crazy one can get with Policy Routing. Verify connectivity using an SSH session from router R1 using a destination address of 10.1.3.11. ![]() Access for user netadmin and password N3t4ccess must be set on router R3 using RSA and 1024 bits. Configure SSH connectivity from R1 to R3, while excluding access via other remote connection protocols. Interface Ethernet0/2 on R3 must be issued the IP address of 10.1.3.11 via DHCP.Ĥ. Using a single command, exclude addresses 1 - 10 from the range. Configure R1 as a DHCP server for the network 10.1.3.0/24 in a pool named NETPOOL. Set the clock on the NTP server for midnight on May 1, 2018.ģ. Configure R1 as an NTP server and R2 as a client, not as a peer, using the IP address of the R1 Ethernet0/2 interface. To verify, a ping must be successful to the R1 Loopback address sourced from R3. All source addresses must be translated from R3 to the IP address of Ethernet0/0 on R2, while using only a standard access list named PUBNET. All traffic sent from R3 to the R1 Loopback address must be configured for NAT on R2. Tasks assigned include configuration of NAT, NTP, DHCP, and SSH services.ġ. When Next is clicked, the lab closes and cannot be reopened.Ĭonnectivity between three routers has been established, and IP services must be configured in the order presented to complete the implementation.Ĝlick Next at the bottom of the screen to submit this lab and move to the next question. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |