Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Subscribe
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
CCNP Route 642-902 Implementing Cisco IP Routing
Rating: 4.6 out of 5(860 ratings)
17,278 students

CCNP Route 642-902 Implementing Cisco IP Routing

includes everything you will need to fully prepare for your CCNP Route certification
Created bySikandar Shaik, Shaik Gouse Moinuddin
Last updated 2/2026
English

What you'll learn

  • Upon completing this course, you will be able to meet these objectives:
  • Plan routing services to meet requirements
  • Implement an EIGRP-based solution
  • Implement a scalable multiarea network OSPF-based solution
  • Implement an IPv4-based redistribution solution
  • Implement path control
  • Implement and verify a Layer 3 solution using BGP to connect an enterprise network to an ISP

Course content

10 sections • 86 lectures • 24h 28m total length

  • Introduction to CCNP Certifications9:12
  • How to access this Course on udemy9:18
  • How to setup GNS3 for Labs Part 123:55

    About GNS3 Simulation Tool

      ·GNS3 is an open source software that simulate complex networks while being as close as possible to the way real networks perform. All of this without having dedicated network hardware such as routers and switches.

      ·GNS3 is an excellent alternative or complementary tool to real labs for network engineers, administrators and people studying for certifications such as Cisco CCNA, CCNP and CCIE as well as Juniper JNCIA, JNCIS and JNCIE. Open source networking is supported too!

      ·It can also be used to experiment with features or to check configurations that need to be deployed later on real devices.

      ·To use GNS3 you first need to provide your own copy of a network operating system, like Cisco IOS, PIX, ASA, IPS or Juniper JunOS.

      ·You can download GNS3 software from http://www.gns3.net/download/ …

  • How to setup GNS3 for Labs Part 227:02

      ·To use GNS3 you first need to provide your own copy of a network operating system, like Cisco IOS, PIX, ASA, IPS or Juniper JunOS.

      ·You can download GNS3 software from http://www.gns3.net/download/ …

  • Feasibility Condition part 116:32

    FD of current successor route > AD of feasible successor

    Feasible Successor= Second best AD < FD of Successor

  • Feasibility Condition part 214:20
  • EIGRP Load Balancing22:14

    EIGRP supports both

      1.equal-cost load balancing

      2.unequal-cost load balancing

      ·Routes with lowest equal metric are installed in the routing table by default

      ·When a router learns a same route from different neighbors with the same metric it install both the routes in the routing table and does load balancing, this is called equal cost load balancing.

      ·Note:- It does equal cost load balancing automatically. whereas unequal cost is not automatic.

      ·For unequal cost load balancing we need to enable "variance"

      ·EIGRP can load share up to six paths. (The default is four paths)

  • LAB: EIGRP Load Balancing24:53

    EIGRP Unequal-Cost Load Balancing Allows the router to include routes with a metric smaller than the multiplier value times the metric of successor

      ·Variance is configured for unequal cost load balancing

      ·Variance is the multiplier to FD of successor

      ·Default is 1(equal cost load balancing)

    Router(config)# router eigrp 100

    Router(config-router)# variance

  • EIGRP Stubs13:32

    EIGRP STUB

    • Stub routingis one way to limit queries. A stub router is one that is connected to no more than two neighbors and should never be a transit router.
    • The EIGRP stub routing feature improves network stability, reduces resource utilization, and simplifies remote router (spoke) configuration.
    • Stub routing is commonly used in a hub-and-spoke topology.
    • A stub router sends a special peer information packet to all neighboring routers to report its status as a stub router.
    • A neighbor that receives a packet informing it of the stub status does not query the stub router for any routes.
  • LAB: EIGRP Stubs24:49

    Configuring EIGRP Stub

    Router(config-router)# EIGRP stub [receive-only|connected|static|summary]

    ·receive-only: Prevents the stub from sending any type of route.

    ·connected: Permits stub to send connected routes
    (may still need to redistribute).

    ·static: Permits stub to send static routes
    (must still redistribute).

    ·summary: Permits stub to send summary routes.

    Default is connected and summary.

  • LAB: NSSA & Totally NSSA39:45
  • OSPF LSA Types16:31

  • LAB : BGP Authentication7:37

    Configuring BGP Authentication on Cisco IOS:

      ·Border Gateway Protocol (BGP) supports authentication mechanism using Message Digest 5 (MD5) algorithm.

      ·When authentication is enabled, any Transmission Control Protocol (TCP) segment belonging to BGP exchanged between the peers is verified and accepted only if authentication is successful.

      ·For authentication to be successful, both the peers must be configured with the same password.

      ·If authentication fails, the BGP neighbor relationship is not be established.

      Router(config-router)#neighbor {ip-address | peer-group-name} <password string>

  • using PeerGroups11:44

    Peer groups

      ·Peer groups are defined to efficiently apply same policies to multiple neighbors:

      ·Peer groups are useful when many neighbors have the same outbound policies.

      ·Members can have a different inbound policy.

      ·Updates are generated once per peer group.

      ·Configuration is simplified.

    Router(config-router)# neighbor peer-group

    This command creates a peer group.

    Router(config-router)# neighbor < peer-group peer-group-name>

  • Route Reflectors19:44

    In order to get the routes to be learned we have two Solutions:

      1.Full mesh neighborship ( which the requirement says not to use here )

      2.Route reflector

    To Configure Route-reflector

      ·All Clients should establish neigbbor with only servers

      ·Clients will not establish neigbor with any other clinet

      ·In case if you have 2 servers ( server establish neigbbor with other servers and clients )

  • LAB : Basic EBGP Configuration7:58
  • Understanding Next-hop-Self17:57

    When EBGP ---sends an update to another EBGP neighbor -------------changes the next hop

    When IBGP ---sends an update to another IBGP neighbor ------------- the next hop remains same (not change)

  • EBGP using Loopbacks ( EBGP Multil-hop)16:55

    BGP neighbor ebgp-multihop Command

      ·This command increases the default of one hop for EBGP peers.

      ·It allows routes to the EBGP loopback address (which will have a hop count greater than 1).

      ·Ebgp-multihop tells to neighbor that the 12.0.0.1 is not directly connected and it is multiple hops away

      ·Increases the default TTL value from 1 to 255

  • Understanding BGP Synchronization Rule11:43

    Synchronization rule:

      ·Do not use or advertise to an external neighbor a route learned by IBGP until a matching route has been learned from an IGP

      ·Ensures consistency of information throughout the AS.

      ·Safe to have it off only if all routers in the transit path in the AS are running full-mesh IBGP;

      ·off by default in Cisco IOS software release 12.2(8)T and later

      ·BGP synchronization is often disabled for autonomous systems which do not act as a transit AS.

      ·Safe to have it off only if all routers in the transit path in the AS are running full-mesh IBGP; off by default in Cisco IOS software release 12.2(8)T and later

    Router (config-router)# no synchronization

    ·The above command Disables BGP synchronization so that a router will advertise routes in BGP without learning them in an IGP

    Router (config-router)# synchronization

  • The Above Command enables BGP synchronization so that a router will not advertise routes in BGP until it learns them in an IGP
  • BGP Attributes10:09

    BGP ATTRIBUTES

    BGP chooses a route to a network based on the attributes of its path. Four categories of attributes exist as follows:

      ·Well-known mandatory:

      oMust be recognized by all BGP routers, present in all BGP updates, and passed on to other BGP routers. For example, AS path, origin, and next hop.

      ·Well-known discretionary:

      oMust be recognized by all BGP routers and passed on to other BGP routers but need not be present in an update, for example, local preference.

      ·Optional transitive:

      oMight or might not be recognized by a BGP router but is passed on to other BGP routers.

      oIf not recognized, it is marked as partial, for example, aggregator, community.

      ·Optional non-transitive:

      oIf the BGP process does not recognize the attribute then it can ignore the update and not advertise the path to its peers

      ofor example, Multi-Exit Discriminator (MED), originator ID.

  • BGP Attributes : AS-Path , Next Hop, Origin18:32

    AS Path

      ·AS Path is Well known, mandatory attribute

      ·List of AS through which updates has traversed.

      ·Path with shortest AS path list is more desirable.

    Next Hop

      ·The next-hop attribute is well-known, mandatory.

      ·BGP is AS by AS routing Protocol

      ·Next hop ≠ next router

      ·Next hop = IP to reach next AS

    The IP address of the next AS to reach a given network:

    • Router A advertises network 172.16.0.0 to router B in EBGP, with a next hop of 10.10.10.3.
    • Router B advertises 172.16.0.0 in IBGP to router C, keeping 10.10.10.3 as the next-hop address.

    ORIGIN

      ·Origin informs all AS in Internetwork how network got introduced into BGP.

      oIGP (i) advertised in BGP using network command

      oEGP (e) Redistributed from EGP

      oIncomplete (?) Redistributed in to BGP from IGP or static

      ·The origin attribute is well-known, mandatory, and transitive.

      ·“I” is better then “E” and “e” is better then “?”

  • LAB : Weight Attribute20:51

    TASK:

    Configure R1 to prefer exit path via R4 to reach all the Networks.

    By default R1 prefer via R2 (1.1.1.2) to reach 20.0.0.0/30.0.0.0 network as it has less number of AS path.

  • BGP Attributes : Weight & Local Preference12:40

    WEIGHT

      ·Weight is Cisco’s attribute.

      ·Tells how to exit the AS

      ·Path with the highest weight is more desirable.

      ·Local to the router ( not advertise to the other routers in the AS )

      ·Weight is partial attribute.

      ·Default weight = 0 for learned routes, 32,768 for locally injected routes)

    LOCAL PREFERENCE

      ·Local preference defines how data traffic should exit from an AS.

      ·Path with highest preference value is more desirable.

      ·It is advertised only to IBGP neighbor within an AS.

      ·Default value is 100

      ·Local preference is well known, discretionary attribute.

  • LAB : Weight Attribute using Routemaps17:06

    TASK:

    ·Make sure that only 12.0.0.0 and 12.0.1.0 both networks should prefer via R4 where as the remaining should use the default route via R2 :

    R1(config)#access-list 12 permit 12.0.0.0 0.0.0.255

    R1(config)# access-list 12 permit 12.0.1.0 0.0.0.255

    R1(config)# route-map WEIGHT permit 10

    R1(config-route-map)# match ip address 12

    R1(config-route-map)# set weight 5000

    R1(config-route-map)# exit

    R1(config)# route-map WEIGHT permit 20

    R1(config-route-map)#end

    R1(config)#router bgp 500

    R1(config-router)#neighbor 4.4.4.1 route-map ?

    WORD Name of route map

    R1(config-router)#neighbor 4.4.4.1 route-map WEIGHT ?

    in Apply map to incoming routes

    out Apply map to outbound routes

    R1(config-router)#neighbor 4.4.4.1 route-map WEIGHT in

    R1(config-router)#end

    R1#clear ip bgp *

  • Understanding IN OUT7:16

    IN Bound

    Out Bound

    ·In bound Route-map Changes the local Router Path selection process.

    ·outbound Route-maps influence some other Routers Decision

    ·In Bound Route-maps apply changes to BGP updates recived from that specific Neighbor

    ·Out Bound Route-maps apply changes routes advertised to that specific Neighbor

    ·Applying inbound influence outbound Traffic

      ·Applying outbound influence inbound Traffic

  • LAB : Local Preference Attribute18:37

    TASK:

      · All the routes going from AS 600 to reach as -700 ( 40.0.0.0 ) by default prefers out via R3

      ·Make sure that R2 and R3 (all the routers in the as 600 should prefer use path via R2 /R1/R4 using local preference.)


  • LAB : Local Preference Attribute using Routemaps14:41

    TASK:

      ·Configure AS 600 such that only routes ( 14.0.0.0 and 14.0.1.0 ) both networks prefer via R2 to exit the AS

      ·All the remaining networks should use the default exit ( via R3)

    R2

    R2(config)#access-list 14 permit 14.0.0.0 0.0.0.255

    R2(config)# access-list 14 permit 14.0.1.0 0.0.0.255

    R2(config)# route-map LOCAL permit 10

    R2(config-route-map)# match ip add 14

    R2(config-route-map)# set local-preference 2000

    R2(config-route-map)# exit

    R2(config)# route-mapLOCAL permit 20

    R2(config-route-map)# exit

    R2(config)# router bgp 600

    R2(config-router)# neighbor 1.1.1.1 route-map LOCAL in

    R2(config-router)#end

  • BGP path selection process16:23

    Route Selection Decision Process

    Consider only (synchronized) routes with no AS loops and a valid next hop, and then:

    1. Prefer highest weight (local to router).
    2. Prefer highest local preference (global within AS).
    3. Prefer route originated by the local router (next hop = 0.0.0.0).
    4. Prefer shortest AS path.
    5. Prefer lowest origin code (IGP < EGP < incomplete) i > E > ? .
    6. Prefer lowest MED (exchanged between autonomous systems).
    7. Neighbor Type (Prefer eBGP over iBGP)
    8. IGP metric to NEXT_HOP (Smaller value preferred)
    9. Prefer oldest route for EBGP paths.
    10. Prefer the path with the lowest neighbor BGP router ID.
    11. Prefer the path with the lowest neighbor IP address.

    • Requirements

    Description

    Course Description – CCNP (Cisco Certified Network Professional)

    The Cisco Certified Network Professional (CCNP) certification validates the ability of networking professionals to plan, implement, verify, and troubleshoot both local and wide-area enterprise networks. It is designed for engineers who are ready to advance their technical skills and work independently on complex network solutions within medium to large enterprise environments.

    Engineers who achieve CCNP certification demonstrate strong practical knowledge and are qualified for a wide range of professional roles, including:

    • Network technician

    • Support engineer

    • Systems engineer

    • Network engineer

    The CCNP curriculum focuses on the real-world skills required by enterprise network engineers. These include routing and switching technologies, troubleshooting methodologies, security fundamentals, wireless and mobility concepts, and best practices for building reliable and scalable network infrastructures. CCNP-certified engineers are expected to design end-to-end network solutions, optimize existing architectures, implement redundancy mechanisms, and ensure secure communication across distributed networks.

    This course is structured to provide detailed explanations, hands-on configuration practice, and scenario-based troubleshooting that mirrors real production environments. Whether you are preparing for certification or upgrading your enterprise networking skill set, this course offers the depth and clarity needed to confidently handle professional networking responsibilities.

    By completing this training, learners will be equipped with the practical knowledge required to excel in enterprise networking roles and progress toward higher-level certifications, including CCIE.

    Who this course is for:

    • anyone wanting to prepare for the ROUTE 642-902 exam.
    • students who want to build on their CCNA level skill set to further a career in computer networking.
    • experienced networking professionals who are ready to advance their core routing, switching, and network troubleshooting skills and students with Cisco CCNA-level knowledge

    Report abuse