Networking Lab Series: LAB 1 PART 2

This is the second part of the Networking Lab Series: LAB 1.

Lets start with some review questions and analysis from PART 1:

• What happened when you did the mutual redistribution CE to PE between EIGRP and BGP?
  
• Besides the "redistribute bgp xxx" under EIGRP, What was required for EIGRP to advertise the routes learned from BGP into the EIGRP domain?
  
• REASONING:
  
• EIGRP, unlike other routing protocols, use a composite metric made of 5 metrics:
  
  1. Bandwidth (minimum along path)
  2. Delay (cumulative along path)
  3. Reliability
  4. Load
  5. MTU
  
  
• When redistributing from other protocols you will need specify the metrics

• What happened when you did the mutual redistribution CE to PE between RIP and BGP?
  
  • Besides the "redistribute bgp xxx" under RIP, What was required for RIP to accept all the routes?
    
    • REASONING:
      
      • RIP is a distance vector protocol. Meaning it counts hops. After 15 hops, number 16 means infinite, and the route is discarded.
      • When redistributing from other protocols, if the metric exceed 15, you have to specify a better metric in order for the route to be accepted.

Now that we have that clear, lets continue with the final tasks for LAB 1.

Task 3: IGP Optimization

• Configure OSPF to set the "Do Not Age" flag on all locally generated LSAs between PE1 and P1
• Configure ISIS for the fastest possible detection of neighbor lost
• Configure ISIS to send the minimum amount of updates after a change in the database

Task 4: IGP and EGP Security

• Configure OSPF Area 0 with MD5 authentication, password CISCO, between ASBR1 and P1 and without password between PE1 and P1.
• Configure RIP to use authentication between CE1 and PE1 using password CISCO
• Configure ISIS with an area 2 password using password CISCO
• Configure EIGRP with MD5 password CISCO between PE2 and CE2
• Configure BGP with MD5 password CISCO

Task 5: EGP Fine Tuning

• Configure the EBGP session to converge as quickly as possible in the event of failure
• Configure BGP peering between ASBR1 and ASBR2 such that AS234 and AS567 only advertises its loopbacks and customers loopbacks to the other carrier
• Configure BGP ASBR2 to not initiate the BGP handshake with ASBR1. Only ASBR1 should send the initial handshake

Task 6: Multicast AS234

• Configure pim sparse mode Multicast inside AS234
• P1 loopback interface should be used as the RP
• Do not allow for dynamic advertisement of RP information

Task 7: Multicast AS567

• Configure pim sparse mode Multicast inside AS567
• P2 loopback interface should be used as the RP
• BSR should be used to distribute the RP information

Task 8: Multicast BGP

• Configure ASBR1 and ASBR2 to negotiate the multicast address family over eBGP
• Configure AS234 RP and AS567 RP to exchange information on active multicast sources
• Configure the RPs only to accept SA messages for groups in the range 239.1.1.0/24

Task 9: Multicast at CE

• Configure pim-sparse multicast between PE1 and CE1, and PE2 and CE2
• Join the multicast group 239.1.1.100 in CE1 and make sure CE2 is able to reach it

Well, hope you have fun up to this point. This is the last part of this lab.

THE END