www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / 101 CCNP LABS / CCNP Lab 054: Cisco Policy Based Routing Lab

CCNP Lab 054: Cisco Policy Based Routing Lab

Lab Objective:

The focus of this lab is to understand Cisco Policy Based Routing (PBR) implementation and configuration in Cisco IOS routers. Additional technologies include path control.

Lab Topology:

The lab network topology is illustrated below:

department654

 

 

IMPORTANT NOTE

If you are using the www.howtonetwork.net racks, please bring up the LAN interfaces connected to the routers by issuing the no shutdown command on the connected switches. If you are using a home lab with no
Switches, you can bring up the LAN interfaces using the following configurations on your routers:

interface fastethernet 0/0
no keepalive
loopback
no shutdown

Alternately, you can simply connect the interfaces to a hub or switch if you have one available in your own lab.

 

Task 1

Configure hostnames, IP addressing on all routers as illustrated in the network topology.

Task 2

Enable EIGRP using AS 254 on all routers as illustrated in the topology. Do NOT enable EIGRP on the link between R2 and R3. EIGRP packets should not be sent out of the FastEthernet 0/0 interfaces of either R2 or R3. Verify the EIGRP configuration using the appropriate commands.

Task 3

Management has requested that traffic sourced from the 150.1.1.0/24 subnet that has a packet size between 0 and 500 bytes and between 1000 and 1500 bytes and is destined to the 150.3.3.0/24 subnet be sent via R2. All other traffic should following the normal routing path. Verify and test your configuration using the appropriate commands.

Task 4

Management has requested that in the event that the R1-R3 link fails, all traffic sourced from the 150.3.3.0/24 subnet destined to the 150.1.1.0/24 and 150.2.2.0/24 subnets be forwarded via the R2-R3 link. This should ONLY happen when the R1-R2 link is down. Ensure that the 150.3.3.0/24 subnet can reach the 150.1.1.0/24 and 150.2.2.0/24 subnets and vice-versa when you complete this task. You are NOT allowed to configure static routes on R3 to complete this task. Additionally, to minimize device configuration, you MUST use a single ACL with a single entry or line. Verify and test your configuration using the appropriate commands.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.