CCNP Enterprise ENSLD (300-420): Designing BGP Routing

6. Compare BGP Load Sharing Designs

The Border gateway protocol can achieve internet connection redundancy. When you connect your network to two different service providers, it is known as multihoming. Multihoming provides redundancy and NEC optimization. It selects the ISP that offers the best path to a resource. When you are running BGP with more than one service provider, you run the risk that your autonomous system will become a transit A. This causes Internet traffic to pass through your A s, potentially consuming all of the bandwidth and resources on your router's PU. BGP for a single home A single home topology means that you have one and only one ISP. A site with a single ISP connection is considered a single home. This is for a site that does not depend heavily on the Internet or Wan connectivity. Static or advertising sites' route to the IP can be used. Receiving a default route from the ISP is usually sufficient. uses address or provider independent address space, which is an enterprise's own autonomous term number. There is no redundancy at the provider level when planning a company's Internet connection needs All you need is a one-way connection to enable internal users to connect to sites on the Internet. A private IP address space with network address translation will be sufficient.

If you need to connect all external users to resources such as servers inside your network, you may need some public IP addresses. You can be at ease with private addresses and NAT for your users. If you need only a default route to your ISP, static routes work. The provider needs to create static roots pointing to their network and redistribute them into their inn. Proportcle BGP is a good choice. If you connect to multiple ISPs, you need to control how traffic enters or exits your company, or you need to react to Internet topology changes. Dual or Moomed BGP, a dual home site has two connections to the same ISP. The connectivity can either be from one router or two routers. One link might be the primary and the other a backup. Another option is to load balance over blinks. A static or dynamic route would work. In this case, Multihoming means connecting to more than one device at the same time. It is done for redundancy and backup if one ISP fails and for better performance. If one ISP provides, it's a better path to frequently used networks. This also gives you an ISP independence solution.

BGP is typically used with multihome connections. Dual Multihome takes it one step further with two multiple ISPs. This provides the most redundancy. BGP is used by the ISPs and can also be used internally. If you need high availability for the Internet connection only, then you can deploy a third BGP setup where one link will act as the primary link for ingress and egress traffic and the other link will stand by until the primary fails. If, on the other hand, there is a need for loadsharing, as in most cases, then you will have to use various BGP tools like local preference and A s path prepending to achieve traffic engineering to suit your needs. The use of each tool will be different for different scenarios, and the way to do this is by implementing different BGP policies. You can do a lot of fine tuning to get near the dead load sharing target, but total control over traffic load sharing is difficult to achieve due to the size and addictability of traffic flows. Reasons for multihoming single-home networks do not promote any redundancy at the ISP level. The address space can be either provider assigned or provider intim scope. It does not make any difference because your AS has only one exit point to the Internet. Multihomes provide fully redundant setups. If redundant local routers are used, there will be at least two enterprise BGP networks that will connect to them, so the use of AP address block is a must. is the most notable reason for multihoming with single homing. One connection to the internet means that work depends on the following local router configuration software.

Hardware carrier failure ISP configuration software and hardware Considerations for dualor multihome design The design of your multihome network will depend on the requirements for your traffic flow. Network design will depend on whether you need high availability and an active standby configuration, or whether you need high availability and load sharing with an active active configuration. The use of tools like LoC and asspending can be used to control the traffic. When multihoming, it is important to be careful not to become a transit network. When you connect to multiple exit points from your A, you should only announce your prefixes to the ISPs and filter the rest. As and when you peer with multiple ISPs, there is anger that by misconfiguration you advertise routes that are received from one ISP to the other. ISPs can become a transit airport for the internet traffic of other networks, which can cost you money and resources. This situation is easily avoided by advertising only yourassigned address space to all adjacent ISPs. Single-home BGP with multiple links This scenario shows how to achieve load sharing when there are equal cost links.

In a single home BGP environment, the links are terminated in one router at a local A-S-A corporate network and one router at a remote AASP. When load sharing with pallets between routers, a BGP session is established between loopback interfaces, EBGP multihop configuration, and recursive route are required. Look for the next BGP hop. NIGP does the actual load sharing using equal or unequal cost depending on IGP support. Static routing is also possible but is less resilient. The BG session is established between the loopback interfaces of the EBGP speakers. To achieve the steering ring, the EGPmultihop feature needs to be configured. Without multihop, EBGP sessions can only be established between directly connected devices. Because the two loopback interfaces can not be directly connected, the multihop feature ensures the session establishment. Load sharing in this scenario is implemented at the IGP level. There can be multiple equalcost paths between EBGP loopback interfaces, which are serving as the next BGP routes. However, since the loopback interface is not part of the link between the routers, recursive lookup will be executed on the routers to route traffic across the links.

Multiple equal-cost paths can be utilised by the router on a per packet or per destination basis, depending on the router software and hardware configurations. With IGTP multipathing, the underlying network topology does not affect the EBGP session and policy configuration. Also, there is an increase in resiliency and the total bandwidth link fault is dynamic if a GP is used, and traffic can be a black hole if static routing is used. There are other benefits to the Igpec MP. The underlying physical topology does not affect the EBGP,meaning it is only required for one link to be active and BGP will work as intended. The links can dynamir as a backup for one another, and the IGP will handle the convergence. There is increased bandwidth between GP routers for user data traffic with each additional path if IGP is not used, but you ostrate routing between loopbacks. In certain situations, this action can lead to lost traffic because there are dynamic route exchanges or, more importantly, stateful IGP neighbors. For example, instances can be faulty on the carrier side, but they could still physically be up on the corporate router side, resulting in a healthy static route that leads to a dead end. A static route will exist in the routing table and the router will root if the physical interface that the root is pointing to is up.

7. BGP Load Sharing

This scenario shows how to achieve load sharing when multiple links exist between a remote A S and a local IS. Load sharing with links to two route routers to the same ISP includes local router appears with two ISP routers and is terminated in one router at the local as a route at a remote A SB in a single home BGP environment. It involves two physical interfaces used for EebGP and full control of outbound traffic. Inbound can be influenced or overridden with policy. There are two EBGP sessions between the corporate network. Can the IE and the sessions use different physical interfaces as the session endpoints? This scenario demonstrates EC on the BGP level by using the BGP multipath feature. By default, BGP chooses one path among the possible equal-cost paths that are learned from one A S.

However, you can change the maximum number of equal-cost paths that are allowed to make this change include the maximum number of paths commandand a GP configuration with a number between one and six for the parts argument. Load sharing, ingress and egresspath selection The corporate network can fully control outbound traffic toward the ISP's. Inbound traffic cannot be controlled completely without the cooperation of the IASP. Load sharing ingress selection splits the address range and gives advertisers more specifics and aggregates. If the IP address is split, another option is to prepend the A S path or set a different med. Load-sharing egress pathshen configures BGP maximum paths on the corporate route to side or the local preference or weightfind if the number of prefixes is too large. In a scenario with two separate links going to the ISP, there are options to consider. If redundancy is the only concern, meaning one link will be active and the other in standby, then redundancy can be accomplished simply by default.

BGP configuration load sharing can be accomplished using several tools but separately for each direction. When you are considering the ingress traffic load share, it can be accomplished by splitting the corporate network address range into two or more chunks, which can each be of the approximate size. In this example, you are splitting the address range in half from 1286. The aggregate prefix and halfprefix will then be advertised to each ebgpper, making the toplink on the figure more preferred for 1286 00:17 and the bottom link preferred for 128-6612 00:17. If the address space is too small to be split,you can use A S path ending or MTP to create one preferred link for all ingress traffic. In this case, there is no load sharing because Orphic will use the one selected link. However, you can choose which link will be the primary one. for egress. You can use the BGP multipath feature on the corporate router side, which will load balance traffic based on ECMP. If you get too many prefixes and the router cannot process many routes, you can use findtier sharing with local preference or weight attributes by setting them for the arriving prefixes. In this way, the tripraph reset prefix will exit through the desired link.

If a router gets two prefixes to the same destination, the higher weight or if weight is not set, the higher local preference value will win. Dual Home to OSP with multiple routers This scenario shows how to achieve load sharing when there are multiple connections to MISP through multiple local routers. The two ISP EB GP peers are terminated on two separate routers. The two ebgppers are terminated by two separate local routers. An IBGP set is created between local routers and, by default, there is no load sharing. The outbound router will select the best path to a destination so space can be used. An extra IBGP session between local routers enables the BGP root exchange between them. Load balancing for the best destination on the two externallinks is not normally possible because BGP chooses the best path among the networks that are learned from EBGP and IBGP. Load sharing among the multiples on S 456 is the next best option. With this type of load sharing, traffic to specific networks, which are based on predefined policies, travels through both links. Also, each link acts up to the other link in case one link fails. Load sharing for ingres and egres. This scenario does not create any strict requirements for the type of address space that is used by corporate work. It enables the use of both P-A-A or P.I.Address rangers. Load pairing and ingress pathshen split the address range or advertisers with more specifics and aggregates. If an IP space cannot be split redundant, only path prepend or med can be used. Load sharing and egress path selection and use localpreference for fine tuning internally load balancing traffic; load sharing for the ingressdirection can be achieved, for example, by splitting the corporate network address range or changing the A S path ormed attribute when sending out routing updates.

In this example, you are splitting the address range in half from one 2866-16 to one 2866-17 and 12861 2817.Then you will advertise the aggregate prefix and one-half prefix to each ebgpper, which will make the toplink on the figure more preferred for one 2866 00:17 For one 2866 17, the bottom link is preferred. Again, if the aesth's path or met is used instead of a split address range, then lowering is not an option and there is just path selection for all traffic. Egress traffic load sharing can be accomplished either internally or externally by manipulating BGP ABS routers by setting a local preference for prefixes as they arrive to achieve a 50% split distribution of the sending traffic across the two links. The prefixes that have a higher local preference on the torrated edge router will have a lower local preference on the bottom router and vice versa. Load balancing of ticks can also be done internally before it gets to the edge routers.

Ufhrp can be used to distribute outbound traffic within the corporate A s, which will then load balance traffic to the edge routers in roughly equal percentages. Once the traffic hits either of the edge BGP routers,it is routed across the link to the AP. So it is a matter of how FRP will distribute the load to get the desired load sharing ratios. Examples of Fhrp's, Rhsrp's and GLBP load sharing by usingIGPEC MP achieved by redistributing zero over zero from BGP into IGP and then the internal network with two equalcost default routes toward the edged BGP routers. multihomed with two Is plus a single local router. Load balancing to a destination is not an option in a multi-homed environment, so you can only do load sharing. You cannot do load balancing because BGP selects only a single best path to a destination. Among the BGP routes that are learned from the different Aasns, the idea is to set a betem for certain routes that are learned from ISP one, and a bettermetric for other routes that are learned from ISP two. Connecting to two ISPs for redundancy via BGP. Multipath is not an option. It is necessary to announce your Pi to both ISPs.

Be cautious not to become an a-transit agent due to misconfiguration. Multihoming requires the corporate network to USP. Ip address space is advertised to both ISPs according to the rules that you are directly connected to. If you advertise routes received from ISP one and SP two by mistake, and the ISP two policy is not restrictive enough, your A s will begin to participate. Internet Traffic Exchange It might happen that A SX figure decides, because of a shorter A S path, that the path to ISP one from A SX is shorter via your network and therefore starts sending fin that is destined for ISP on to your router. Your router will route the traffic to ISPOne, but the problem with this extracted traffic might leave your users with no bandwidth for themselves. And there are also the costs of routing that tick to.Consider load sharing for ingress traffic.

The P iced space and advertise specifics and aggregates were used to enable load sharing for ingress traffic. This provides redundancy only for ingress traffic. The PIIP space cannot be split. Use the A's path prepend to prevent becoming a transit air. It would tie only your prefixes. In this scenario, load sharding for the ingressdirection is possible by splitting the address space and announcing different chunks to the ISPs. The aggregate is always announced as a best practise as it serves as a backup mechanism in the event of a link failure. If your assigned address space is smaller, then the best thing you can do is have an active standby setup by prepending the A s part said I.In this way, you achieve redundancy but without load sharing to prevent your network from beinga transit A s advertisement connects only your Pi address space to both ISPs. It can be easily achieved by outbound route filtering. When you are load balancing by splitting the PI space, advertising half of the prefixes to one service provider and the other half to the other service provider is usually not a good decision. You should split the prefixes between the ISPs based on the business or policy decisions of each ISP and on quality. If you just split the prefixes evenly, you should check whether the load balance is equal and then make a choice accordingly.

Load sharing for egress traffic is provided by splitting incoming prefixes in half and assigning local preference. Set local preference to 200 forprefix received from ISP One. Set local preference to 200 for ISP two prefixes 129x and 254x. If traffic distribution is uneven, assign more prefixes to one side. When east, traffic is multihomed to two ISPs. Load sharing is possible by configuring the local preference of Halus for preferred routes coming from preferred links. In this case, you receive the full internet routing table from peers at your corporate router. Then the finest tuning of egress traffic can be done empirically. The number of destinations per link can be modified until the desired traffic ratio is achieved by trial and error. Method There are many methods of splitting the prefixes. You can split them in half based on the first oct. You can also split them by odd and even numerals and so on. If you are receiving the default routes and a limited number of prefixes from the ISPs, then load sharing,while still possible, will not be as precise. Two local routers peering with two ISPs emerged as the most resilient solution when multihomed with two ISPs and multiple local routers. It is redundant at all key points.

The peering links and different providers' local router and ISP redundancy. API address space is required. This is the most resilient solution. The outbound route control is similar to dual localrouters with a single ISP local route appearing with the router in a different A as each and there is an IBGP session between them. The IBD session will make sure that both routers fully converge. In the event of an ISP link or router failure, access to a destination is not possible. In a multihomed environment with two ISPs, BGP's select the single best path to a destination among the BGP paths that are learned from different autonomous systems, which makes load balancing impossible. But load sharing is possible in such multihome BGP networks. Predetermined policies, the traffic floor is controlled with different BGP attributes. Load sharing for ingress traffic, as with all multihome deployments using multiple ISPs, is required. Split the P I space and advertise specifics and aggregates for redundancy.

If it is possible to split the time, advertise specifics and aggregates for redundancy. If it is not possible, split prefixes are prepared for link redundancy. No load sharing. The med is not useful. In this scenario, load sharing foringress traffic is possible by splitting the addressspace into different chunks for the ISPs. The aggregate is always announced as a best practise because it serves as a backup mechanism if there is a link failure. The difference is that there is another IBGPsession between the lowautors to ensure best convergence in cases of link or router failures, which may make it a highly available setup. If your assigned address space is smaller, then the best thing you can do is to have an actuan bisetupby prepending the S path several times with your ASN. Hence, you achieve redundancy. Med is not useful here as a tool for load sharing because there are two distinct ISPs. Load sharing for egress traffic uses localpreference for fine tuning or internally balance.The trick is to not use local preference. Redistribute the default route into IGP from both edge routers toward the edge routers and BGP works from there. Local routers need a way to select a link for a destination. The goal is accomplished by selectively setting local preferences for the routes as they are traffic flows. In this scenario, when there are no failures in the network, follow the routes in the figure that appear at the very top and at the very bottom.

For example, if on the bottom router some traffic is received from the inside for a destination network in the range of one to one hundred, this traffic will be routed to the top router and sent through the top link to ISP one. In the event of the failure of the top link, ora router or ISP one, the traffic that is destined to one to 1128 will be sent to ISP two. If you are using BGP and local preference to distribute the egress traffic, you might consider balancing the traffic early toward the edge routers by using FHRP or redistributing the default route into IGP. The edge routers should have a simplepolicy that sends out whatever they receive via the link to their respective ISPs. This policy is often the one you get by default in BGP due to the path selection mechanism. If not, such a policy can be achieved on corporate edge routers by sending a higher weight value for any route that is received from the Ispb GP versus the lowerdefault weight of routes that are received from IBT.

CCNP Enterprise ENSLD (300-420): BGP Address Families and Attributes

1. BGP Address Families and Attributes

Hello and welcome to UnderstandingBGP address families and attributes. The purpose of this video is to give you not only an idea of the topics that are covered in this section but also the understanding you will achieve by buying the information regarding the recommendations and suggestions offered, including example configurations, case study scenarios, and the detailed descriptions and explanations of how Multiprotocol BGP works. 4760 defined extensions to BGP to make it capable of simultaneously capping more than IP traffic. This is known as multiprotocol BGP or MPBP. BGP is also used on CiscoNxos to support multiple address families.

Depending on family, multiprotocol BGP will carry different sets of routes, so let's look at the topics that will be covered. BGP is used to pair with service providers with the primary goal of providing global reachability and fault-tolerant traffic routing. This is accomplished by how BGP carries each type of traffic, which is referred to as an address family and is explained in the first topic, which covers multicast and unicast prefixes along with virtual route forwarding instances (VRF).The discussion includes IPV six enhancements with network layer reachability information and LRI, as well as how routing sessions are identified in the VPN version four multicast, which you learned uses a protrude descriptor. There is a detailed discussion of how this impacts companies that move business applications to their intranets to extend over a wide area network. The topic goes into even further detail. We learned about several important BGP acronyms, including virtual Forwarding Instance, VFI Address, and family.

The use of the routing information base ribbon helps you understand. These last three mechanisms are immense when connecting geographically separate sites with a mesh topology with auto discovery mechanisms. The following topic takes you through listing the main, or should I say, the most widely used BGProute selection criteria in the order of the most influential, the ones with the most impact, along with a detailed discussion of each first one in the list as the BGP weight attribute. The next is the BGP local preference attribute, followed by the GPA's autonomous system path attribute. Remember that each of these topics includes a brief detrition of the attribute, including a reference diagram that takes you through how BGP utilises this, as well as recommendations for the use of this particular attribute. You will see an A spot depending on IGL that takes you through how traffic flows. When multiple connections between providers are required, you will be asked some questions with ideas and considerations. You will then be introduced to the next attribute, multiexit discriminant Med, which influencespart selection in A S neighbors.

The section then transitions to BGPs and describes how these are used to tag routes to ensure consistent filtering and route selection. Policy Ur provided a very nice detailed explanation of how communities work, along with several case studies outlining some design schemes, touching on BGPpolicy, access control, list tags, and so forth. The final topic discusses a dual stack multi-protocol BGPS study loading deployment considerations, example configurations, router outputs, and explanations of the information detailed in those router outputs in very informal descriptions referencing the example cases. And as you can see, this section provides not only relevant, helpful recommendations and suggestions, but also fairly in-depth descriptions regarding the mechanics of multi-protocol BGP. That is our overview of understandingBGP address families and attributes. Thank you.

2. BGP ADDRESS FAMILY MODEL

BGP has a long history as the routing protocol of the Internet. Therefore, think of BGP as the IPV4-routing protocol used by service providers. The primary key goals during the design of IPV Four were to provide global reachability and fault tolerant traffic routing. The nature of the Internet creates a need to provide intelligence of traffic differential for varying levels of traffic, through quality of service, enhanced security requirements, improved address administration, a larger address space, and more efficient day-to-day handling in the forwarding path. The development of IPV Six began in an attempt to resolve the potential exhaustion of the IPVFour address space and developed into the foundation for the next generation Internet. IPV Six is cool, providing a worldwide communication and commerce medium. The migration to IPV Six is the most significant transition of the Internet and corporate networks to date. Modern BGP is very comprehensive and is capable of so much more than IPV four routes. Each type of traffic that BGP can carry is referred to as an S family address.

These include IPV Four and IPV Six unicast and multitask routes Lituvpn or Ltwo VPN information such as VPLs or Vpnvpnv Six-layer-three VPN information known as MPLS VPN The tunnel's subsequent address Family Identifier.was introduced. Multipoint tunnelling IPV. Four routing sessions in Cisco IOS released twelve zero nine seconds. The Multicast distribution tree was introduced to support multi-VPN architectures in Cisco. On December 12th, iOS was released. The tunnel Safi was introduced to support multiple point tunnelling IPV Cisco iOS released twelve new four-route sessions. multicast distribution tree. Safi was introduced to support multicast VPN architectures. IPV Four-Address Family The IPV Four address families are used by BGTP to identify routing sessions that use standard IP Version Four address prefixes. Multicast or unicast prefixes can be specified with the IPV Four address family. The VRF instance can also be associated with IPV Four Address family configuration mode commands to configure MEGP on a Cisco device using the Address family IPV Four command. It places the router in the adramali configuration mode, so you can configure routing sessions that use the standard four address prefixes. Typing will leave the Address family configuration mode and return to outer configuration mode by default. Routing information for Address family IPversion four is available.

When you configure a BGP routing session using the neighbour remoters command, This default can be changed, barring the no BGP default. IPV4 unicast command used to configure BGP between two IPV4s that must exchange IPV4 VR information due to their presence in a VPN. This family configured here is the IPVFour VRF address family, and the configuration is done at routerbautonus system m 45. In this figure, a relationship is created with the neighbor192 at the router in autonomous system 400 and with the neighbor192-6832 at the router A in autonomous system 500. The IPV Six family IPP BGP is the supported exterior gateway protocol for IPV Six. Multiprotocol BGP extensions for IPV6 support many of the same options and features as IPV four. Six enhancements to multiprotocol BGP support for BGP IPV IPV six address family and network layer reachability information for the next device in the path to the destination, IPV six GProuting process, and BGP router ID.

The IPV six BGProuting process can be configured with an optional BGP routerID for a BGP speaking device. The BGP router ID is a 32-value that is often represented by an IPV4 address. BGP uses this router ID to identify BGP-speaking peers. By default, the router ID is set to the IPV4 address of a loopback interface on the device. If no loopback interface is configured on the device, then the software chooses the highest address configured to a physical interface on the device. To represent the BGP router ID on a device that is enabled only for IPV six, the device that does not have an IPV four address must manually configure the BGP router ID for the device. The BGP router ID must be used on the BGP of the device. This router ID is represented as a 32-bit value using an IP or address syntax. In this network, router A connects to two different service providers, SP and SP bombing multihoming, where 101O'n 64 and 22 are received from two different ASAs, 202 and 303.

Dremel L two VPN The VPN v4 multicastad press family is used to identify routing sessions for BGP VPN version four address prefixes Unicast address prefixes are the default when Vpnv addresses are configured. Vpnv four routes are the same as IPV four routes, but Vpnv fours have a rootdescriptor that allows for replication of the prefixes. It is possible to assert every road with a different VPN. Each VPN needs its own set of prefixes. IPVPN is used by companies as the foundation for administering and deploying value-added services, including applications and data hosting networkcommerce, as well as telephone services to business customers in private la. IP-based intranets have changed the way companies conduct their business. Companies are moving business applications to their intranets to extend over a van. They are also addressing the needs of their suppliers, customers, and partners by using extranets. An intranet encompasses multiple businesses. A service provider network connects several sites seamlessly. One service provider network is subwivral Ipvpns. Each appears to its users as a private network separate from all other networks. The VPN address space is isolated from the global address space. VGP distributes reachable information for VPN IPV four prefixes for each VPN using the VPN v four multi-protocol extensions to ensure that routes for a VPN are learned only by other members of that VPN, which enables members of the VPN to communicate with each other.

Cisco added support for the L2 VPNaddress family. iOS released twelve 233 and later, twoVPN, as a secure nook that operates inside an unsecured network by using an encryption technology such as generic routing insulation. In this example, the Pay router NPE three is configured with a layer two router ID, a Vpenid, a VPLSID, and is enabled to automatically discover the other Pay routers that are part of the same VPLs domain. A BGP session is created to activate neighbours in the L2 VPN address family. If a root reflector notice is provisioned for a newWolf forwarding instance, BGP will announce the entire table from the L 2 VPN address family identifier to the L 2 Vpnx connect database. To make sure that the virtual circuits are active, the L2 VPN address family is configured in BGP routingconfiguration mode within the L2 VPN address family. The VPLs of Sarfy are supported. VGP supports an auto-discovery-based mechanism for the L two VPN address families. It distributes L2VPN endpoint provisioning information. BD uses a separate L2 VPN routing information base. This is updated each time any layer two VPN is configured with path and prefix information stored in the L2-VPN database. The database allows BGP to make the best-path decisions. BGP distributes the end provisioning information in an update message to all its BGP neighbors. The endpoint information is used to set up a pseudo via mesh. The mesh is used to support two VPS-based services. The autodiscovery mechanism facilitates the setting up of two VPN services, which are a part of the Cisco iOS virtual triunserviced VPLs feature.

High-speed Ethernet in a robust and scalable IP environment allows for the flexibility in deploying services by connecting graphically separate sites as a large LAN over high-speed Ethernet in a robust and scalable IP.MPLS perk multiprotocol BGP for Vpnv four. BGP is also used on Sysxos to support multiple address families. Depending on the address family protocol, BGP will carry different sets of routes. For example, BGP can carry one set of routes,four unicast routes, and one set of routes.

For IPV four multicast routing, mpbg can be used for reverse path forwarding checks in IP multicast networks. Multicast BD does not propagate multicast state information. Therefore, you will need a multicast protocol such as Proticast Pimp to support multiprotocol. All BGP configurations use the router's neighbor address family configuration modes. Mpbgp will maintain separate ribs for each configured family, such as a unicast rib and a multicast rib for BGP. This is an illustration. MP Bgpvp envious four prefix exchange between gateway provider and autonomous system borrowers. A multi-protocol BGP network is backwardcompatible and does not support multiprotocol extensions. It cannot forward routing information such as address family information that the multiprotocol extensions can carry.

Prepared by Top Experts, the top IT Trainers ensure that when it comes to your IT exam prep and you can count on ExamSnap Designing Cisco Enterprise Networks (ENSLD) certification video training course that goes in line with the corresponding Cisco 300-420 exam dumps, study guide, and practice test questions & answers.