06 MBGP Configuration

8/13/2019 06 MBGP Configuration

1/19

i

Table of Contents

1 MBGP Configuration 1-1MBGP Overview1-1Protocols and Standards1-2MBGP Configuration Task List1-2Configuring MBGP Basic Functions1-2

Prerequisites1-2Configuration Procedure1-3

Controlling Route Advertisement and Reception1-3Prerequisites1-3Configuring MBGP Route Redistribution1-3Configure Default Route Redistribution into MBGP 1-4Configuring MBGP Route Summarization1-4Advertising a Default Route to an IPv4 MBGP Peer or Peer Group 1-5Configuring Outbound MBGP Route Filtering 1-5Configuring Inbound MBGP Route Filtering1-6Configuring MBGP Route Dampening 1-7

Configuring MBGP Route Attributes 1-7Prerequisites1-7Configuring MBGP Route Preferences 1-8Configuring the Default Local Preference 1-8Configuring the MED Attribute1-8Configuring the Next Hop Attribute1-9Configuring the AS-PATH Attribute1-9

Tuning and Optimizing MBGP Networks 1-10Prerequisites1-10Configuring MBGP Soft Reset1-10Configuring the Maximum Number of MBGP Routes for Load Balancing 1-11

Configuring a Large Scale MBGP Network1-12Prerequisites1-12Configuring IPv4 MBGP Peer Groups1-12Configuring MBGP Community 1-12Configuring an MBGP Route Reflector 1-13

Displaying and Maintaining MBGP 1-14Displaying MBGP 1-14Resetting MBGP Connections1-15Clearing MBGP Information 1-15

MBGP Configuration Example1-15


2/19

1-1

1 MBGP Configuration

The term router refers to a router or a Layer 3 switch in this document.

When configuring MBGP, go to these sections for information you are interested in:

MBGP Overview

Protocols and Standards

MBGP Configuration Task List

Configuring MBGP Basic Functions

Controlling Route Advertisement and Reception

Configuring MBGP Route Attributes

Tuning and Optimizing MBGP Networks

Configuring a Large Scale MBGP Network

Displaying and Maintaining MBGP

MBGP Configuration Example

MBGP Overview

BGP-4 is capable of carrying routing information for IPv4 only. IETF defined multiprotocol BGP

extensions to carry routing information for multiple network layer protocols.

For a network, the multicast topology may be different from the unicast topology. To meet the

requirement, the multiprotocol BGP extensions enable BGP to carry the unicast Network Layer

Reachability Information (NLRI) and multicast NLRI separately, and the multicast NLRI is used to

perform reverse path forwarding (RPF) exclusively. In this way, route selection for a destination through

the unicast routing table and through the multicast routing table will have different results, ensuring

normal unicast and multicast routing.

Multi-protocol BGP is defined in RFC 2858 (Multiprotocol Extensions for BGP-4).

Multi-protocol BGP for IP multicast is referred to as Multicast BGP (MBGP) for short.

This document covers configuration tasks related to multiprotocol BGP for IP multicast only. For

information about BGP, refer to BGP Configurationin the IP Routing Volume.

For information about RPF, refer to Multicast Routing and Forwardingin the IP Multicast Volume.


3/19

1-2

Protocols and Standards

RFC2858: Multiprotocol Extensions for BGP-4

RFC3392: Capabilities Advertisement with BGP-4

draft-ietf-idmr-bgp-mcast-attr-00: BGP Attributes for Multicast Tree Construction

MBGP Configuration Task List

Complete the following tasks to configure MBGP:

Task Remarks

Configuring MBGP Basic Functions Required

Configuring MBGP Route Redistribution Optional

Configure Default Route Redistribution into MBGP Optional

Configuring MBGP Route Summarization Optional

Advertising a Default Route to an IPv4 MBGP Peer or PeerGroup Optional

Configuring Outbound MBGP Route Filtering Optional

Configuring Inbound MBGP Route Filtering Optional

Controlling Route

Advertisement andReception

Configuring MBGP Route Dampening Optional

Configuring MBGP Route Preferences

Configuring the Default Local Preference

Configuring the MED Attribute

Configuring the Next Hop Attribute

Configuring MBGPRoute Attributes

Configuring the AS-PATH Attribute

Optional

Configuring MBGP Soft Reset OptionalTuning andOptimizing MBGPNetworks Configuring the Maximum Number of MBGP Routes Optional

Configuring IPv4 MBGP Peer Groups Optional

Configuring MBGP Community OptionalConfiguring aLarge ScaleMBGP Network

Configuring an MBGP Route Reflector Optional

Configuring MBGP Basic Functions

Prerequisites

Before configuring MBGP, make sure neighboring nodes can access each other at the network layer.


4/19

1-3

Configuration Procedure

Follow these steps to configure MBGP basic functions:

To do Use the command Remarks

Enter system view system-view

Enter BGP view bgpas-number

Specify a peer or peer groupand its AS number

peer{ group-name|ip-address} as-numberas-number

Required

Not specified by default.

Enter IPv4 MBGP addressfamily view

ipv4-family multi cast Required

Enable a peer or peer groupcreated in IPv4 unicast view

peer { group-name|ip-address} enable

Required

Not enabled by default

Specify a preferred value forroutes from an IPv4 MBGP

peer or peer group

peer{group-name |ip-address} preferred-value

value

Optional

The default preferred value is 0.

Controlling Route Advertisement and Reception

Prerequisites

You need to configure MBGP basic functions before configuring this task.

Configuring MBGP Route Redistribution

MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing

information from IGP into its routing table rather than learns the information by itself.

Follow these steps to configure MBGP route redistribution:





ipv4-family mult icast

Redistribute routes fromanother routing protocol

import-routeprotocol[ process-id[ med med-value| route-policyroute-policy-name ] * ]

Inject a network into the MBGProuting table

networkip-address[ mask |mask-length ] [ short-cut|route-policyroute-policy-name]

At least one of theseapproaches is required.

No route redistributionis configured by default.


5/19

1-4

The Origin attribute of routes redistributed into the MBGP routing table with the import-route

command is Incomplete.

The Origin attribute of routes injected into the MBGP routing table with the networkcommand is

IGP.

The networks to be injected must exist in the local IP routing table, and using a route policy makes

route control more flexible.

Configure Default Route Redistribution into MBGP

You cannot use the import-route command to configure MBGP to redistribute default routes from other

protocols. Instead, use the following commands:

Follow these steps to configure MBGP to redistribute default routes from other protocols




Enter MBGP address familyview

ipv4-family multi cast

Redistribute routes fromanother routing protocol

import-routeprotocol[ process-id[ med med-value|route-policyroute-policy-name] * ]

Required

No route redistribution isconfigured by default.

Enable default routeredistribution into the MBGProuting table

default-route importedRequired


Configuring MBGP Route Summarization

To reduce the routing table size on medium and large MBGP networks, you need to configure route

summarization on peers. MBGP supports two summarization modes: automatic and manual.

Automatic summarization: Summarizes subnets redistributed from IGP. With the featureconfigured, MBGP advertises only summary natural networks rather than subnets. The default

routes and routes injected with the networkcommand are not summarized.

Manual summarization: Summarizes MBGP local routes. A manual summary route has a higher

priority than an automatic one.

Follow these steps to configure MBGP route summarization:



Enter BGP view bgpas-number Enter IPv4 MBGP address family view ipv4-family mult icast


6/19

1-5


Enable automaticroutesummarization

summary automatic

ConfigureMBGP route

summarization Configure manualroutesummarization

aggregateip-address {mask |mask-length }[ as-set|attribute-policy

route-policy-name|detail-suppressed |origin-policy route-policy-name|suppress-policyroute-policy-name] *

Required

No routesummarization isconfigured by default.

Choose either as

needed; if both areconfigured, themanual routesummarization takeseffect.

Advertising a Default Route to an IPv4 MBGP Peer or Peer Group

Follow these steps to advertise a default route to an MBGP peer or peer group:






Advertise a default route to anMBGP peer or peer group

peer{ group-name |ip-address }default-route-advertise[ route-policy route-policy-name ]

Required

Not advertised by default

With the peerdefault-route-advertise command executed, the router sends a default route with the

next hop being itself to the specified MBGP peer or peer group, regardless of whether the default route

is available in the routing table.

Configuring Outbound MBGP Route Filtering

If several filtering policies are configured, they are applied in the following sequence:

filter-policy export

peer fil ter-policy export

peer as-path-acl export

peer i p-prefix export

peer route-policy export

Only the routes that have passed all the configured policies can be advertised.


7/19

1-6

Follow these steps to configure BGP route distribution filtering policies:




Enter IPv4 MBGP address

family view


Configure the filtering ofredistributed routes

filter-policy{acl-number|ip-prefixip-prefix-name}export [ direct |isisprocess-id| ospf process-id| ripprocess-id| static]

Apply a route policy toadvertisements to an IPv4MBGP peer/peer group

peer{group-name |peer-address }route-policyroute-policy-nameexport

Reference an ACL to filteradvertisements to an IPv4MBGP peer/peer group

peer{ group-name | ip-address}filter-policyacl-numberexport

Reference an AS path ACL tofiler route advertisements to anIPv4 MBGP peer/peer group

peer{ group-name | ip-address}as-path-aclas-path-acl-numberexport

Reference an IP prefix list tofiler route advertisements to anIPv4 MBGP peer/peer group

peer{ group-name | ip-address}ip-prefixip-prefix-nameexport

At least one of theseapproaches isrequired. Nooutbound routefiltering is configured

by default

Configuring Inbound MBGP Route Filtering

By configuring MBGP route reception filtering policies, you can filter out unqualified routes from an

MBGP peer or peer group.

If several filtering policies are configured, they are applied in the following sequence:

filter-policy import

peer filter-policy import

peer as-path-acl import

peer ip-prefix import

peer route-policy import

Only the routes that have passed all the configured policies can be advertised.

Follow these steps to configure MBGP route reception filtering policies:







8/19

1-7


Filter incoming routes using anACL or IP prefix list

filter-policy {acl-number | ip-prefixip-prefix-name}import

Reference a route policy toroutes from an IPv4 MBGPpeer/peer group

peer{ group-name | ip-address}route-policypolicy-nameimport

Reference an ACL to filterrouting information from anIPv4 MBGP peer/peer group

peer{ group-name | ip-address}filter-policyacl-numberimport

Reference an AS path ACL tofilter routing information froman IPv4 MBGP peer/peer group

peer{ group-name | ip-address}as-path-aclas-path-acl-numberimport

Reference an IP prefix list tofilter routing information froman IPv4 MBGP peer/peer group

peer{ group-name | ip-address}ip-prefixip-prefix-nameimport

At least one of theseapproaches is required.

No inbound route filteringis configured by default.

Specify the maximum numberof routes that can be received

from an IPv4 MBGP peer/peergroup

peer{group-name |ip-address }

route-limitlimit[ percentage ]

Optional

The number is unlimitedby default.

Members of a peer group can have different route reception filtering policies from the peer group.

Configuring MBGP Route Dampening

By configuring MBGP route dampening, you can suppress unstable routes from being added to the

MBGP routing table or being advertised to MBGP peers.

Follow these steps to configure BGP route dampening:






Configure BGP routedampening parameters

dampening [half-life-reachablehalf-life-unreachable reuse suppress ceiling |route-policyroute-policy-name ] *

Required

Not configured bydefault

Configuring MBGP Route Attributes

You can modify MBGP route attributes to affect route selection.

Prerequisites

Before configuring this task, you need to configure MBGP basic functions.


9/19

1-8

Configuring MBGP Route Preferences

You can reference a route policy to set preferences for routes matching it. Routes not matching it use

the default preferences.

Follow these steps to configure MBGP route preferences:




Enter IPv4 MBGP address familyview

ipv4-family mul ticast

Configure preferences forexternal, internal, local MBGProutes

preference{ external-preferenceinternal-preferencelocal-preference |route-policyroute-policy-name}

Optional

The default preferences ofmulticast MBGP eBGP, MBGPiBGP, and local MBGP routesare 255, 255, and 130respectively.

Configuring the Default Local Preference

Follow these steps to configure the default local preference:




Enter IPv4 MBGP address family view ipv4-family mult icast

Configure the default local preferencedefault local-preferencevalue

Optional

100 by default.

Configuring the MED Attribute

When other conditions of routes to a destination are identical, the route with the smallest MED is

selected.

Follow these steps to configure the MED attribute:




Enter IPv4 MBGP address family view ipv4-family multi cast


10/19

1-9


Configure the defaultMED value

default med med-valueOptional

0 by default.

Enable thecomparison of theMED of routes from

different ASs

compare-different-as-medOptional


Enable thecomparison of theMED of routes fromeach AS

bestroute compare-medOptional


Configurethe MEDattribute

Enable thecomparison of theMED of routes fromconfederation peers

bestroutemed-confederation

Optional


Configuring the Next Hop Att ribute

You can use the peer next-hop-localcommand to specify the local router as the next hop of routes

sent to a MBGP iBGP peer/peer group. If load balancing is configured, the router specifies itself as the

next hop of route advertisements to the multicast iBGP peer/peer group regardless of whether the peer

next-hop-local command is configured.

In a third party next hop" network, that is, the local router has two multicast eBGP peers in a broadcast

network, the router does not specify itself as the next hop of routing information sent to the eBGP peers

unless the peer next-hop-localcommand is configured.

Follow these steps to specify the router as the next hop of routes sent to a peer/peer group:






Specify the router as the next

hop of routes sent to a peer/peergroup

peer{ group-name |

ip-address }next-hop-local

Optional

By default, the next hop of routessent to a MBGP eBGP peer/peergroup is the advertising router,while that of routes sent to a MBGPiBGP peer/peer group is not.

Configuring the AS-PATH Attribute

In general, MBGP checks whether the AS_PATH attribute of a route from a peer contains the local AS

number. If yes, it discards the route to avoid routing loops.


11/19

1-10

Follow these steps to configure the AS-PATH attribute:




Enter IPv4 MBGP address family

view


Specify the maximumnumber of times thelocal AS number canappear in routes fromthe peer/peer group

peer { group-name |ip-address } allow-as-loop [ number ]

Optional

By default, the local ASnumber can not appear inroutes from a peer/peergroup.

Disable BGP fromconsidering theAS_PATH during bestroute selection

bestroute as-path-neglect

Optional

By default, BGP considersAS_PATH during bestroute selection.

ConfiguretheAS_PATHattribute

Configure updates toa peer/peer group tonot keep private ASnumbers

peer{ group-name |ip-address} public-as-only

OptionalBy default, BGP updatescarry private AS numbers.

Tuning and Optimizing MBGP Networks

This task involves resetting MBGP connections and configuring load balancing.

Prerequisites

You need to configure BGP basic functions before configuring this task.

Configuring MBGP Soft Reset

After modifying a route selection policy, you have to reset MBGP connections to make it take effect,

causing short time disconnections.

After the route-refresh capability is enabled on all MBGP routers in a network, when a route selection

policy is modified on a router, the local router can perform dynamic route updates without tearing down

MBGP connections.

If the peer does not support route-refresh, you can save all route updates from the peer. When the route

selection policy changes, you can refresh the MBGP routing table and apply the new policy without

tearing down MBGP connections.

Soft reset through route-refresh

If the peer is enabled with route-refresh, when the MBGP route selection policy is modified on a router,

the router advertises a route-refresh message to its MBGP peers, which resend their routing information

to the router after receiving the message. Therefore, the local router can perform dynamic route update

and apply the new policy without tearing down MBGP connections.

Follow these steps to configure MBGP soft reset through route-refresh:


12/19

1-11




Enable BGP route refresh for apeer/peer group

peer{ group-name| ip-address}capability-advertiseroute-refresh

Optional

Enabled by default

Perform a manual soft reset

If the peer does not support route-refresh, you can use the peer keep-all-routes command to save all

the route updates from the peer, and then use the refresh bgp ipv4 multicast command to soft-reset

MBGP connections to refresh the MBGP routing table and apply the new policy without tearing down

MBGP connections.

Follow these steps to configure MBGP manual soft reset




Disable BGP route-refresh andmulti-protocol extensions for apeer/peer group

peer{ group-name| ip-address}capability-advertise conventional

Optional

Enabled by default


ipv4-family mult icast

Keep all original routes from apeer/peer group regardless of

whether they pass the inboundfiltering policies

peer{ group-name| ip-address}

keep-all-routes

Required

Not kept by default

Return to user view return

Soft-reset MBGP connectionsmanually

refresh bgp ipv4 multicast {all |ip-address| group group-name|external| internal } { export |import }

Optional

Configuring the Maximum Number of MBGP Routes for Load Balancing

Follow these steps to configure the number of MBGP routes for load balancing:






Configure the maximum

number of MBGP routes forload balancing

balancenumberRequired

Not configured by default.


13/19

1-12

Configur ing a Large Scale MBGP Network

Prerequisites

Before configuring this task, you need to make peering nodes accessible to each other at the network

layer.

Configuring IPv4 MBGP Peer Groups

In a large-scale network, configuration and maintenance become difficult due to large numbers of

MBGP peers. You can configure peer groups to make management easier and improve route

distribution efficiency.

Follow these steps to configure an IPv4 MBGP peer group:




Create a BGP peer groupgroupgroup-name[ external|internal ]

Required

Not created by default.

Add a peer into the peer grouppeerip-addressgroupgroup-name[ as-numberas-number]

Required

No peer is added by default.



Enable the IPv4 unicast peergroup

peer group-nameenable Required

Add an IPv4 MBGP peer to thepeer group

peerip-addressgroupgroup-name

Required


To configure an MBGP peer group, you need to enable the corresponding IPv4 BGP unicast peer

group in IPv4 MBGP address family view.

Before adding an MBGP peer to an MBGP peer group, you need to add the corresponding IPv4

unicast peer to the IPv4 BGP peer group.

Configuring MBGP Community

The community attribute can be advertised between MBGP peers in different ASs. Routers in the same

community share the same policy.

You can reference a route policy to modify the community attribute for routes sent to a peer. In addition,

you can define extended community attributes as needed.

Follow these steps to configure MBGP community:


14/19

1-13




Enter IPv4 MBGP address family view ipv4-family mul ticast

Advertise the

community attributeto an MBGPpeer/peer group

peer{group-name |

ip-address }advertise-communityAdvertise the

communityattribute to anMBGP peer/peergroup

Advertise theextendedcommunity attributeto an MBGPpeer/peer group

peer{group-name |ip-address }advertise-ext-community

Required


Apply a route policy to routes advertisedto an MBGP peer/peer group

peer{group-name |ip-address } route-policyroute-policy-nameexport

Required


When configuring MBGP community, you need to reference a route policy to define the specific

community attributes, and apply the route policy for route advertisement.

For route policy configuration, refer to Route Policy Configurationin the IP Routing Volume.

Configuring an MBGP Route Reflector

To guarantee the connectivity between multicast iBGP peers in an AS, you need to make them fully

meshed. But this becomes unpractical when there are large numbers of multicast iBGP peers.

Configuring route reflectors can solve this problem.

Follow these steps to configure an MBGP route reflector:



Enter BGP view bgpas-number Enter IPv4 MBGP addressfamily view


Configure the router as a routereflector and specify an MBGPpeer/peer group as its client

peer{ group-name |peer-address } reflect-client

Required


Enable route reflectionbetween clients

reflect between-clientsOptional

Enabled by default.

Configure the cluster ID of the

route reflector reflector cluster-id cluster-id

Optional

By default, a route reflector

uses its router ID as the clusterID.


15/19

1-14

In general, it is not required that clients of a route reflector be fully meshed. The route reflector

forwards routing information between clients. If clients are fully meshed, you can disable route

reflection between clients to reduce routing costs.

In general, a cluster has only one route reflector, and the router ID of the route reflector is used to

identify the cluster. You can configure multiple route reflectors to improve network stability. In this

case, you need to specify the same cluster ID for these route reflectors to avoid routing loops.

Displaying and Maintaining MBGP

Displaying MBGP


Display the IPv4 MBGP routingtable

display ip mult icast routing-table[verbose]

Available in anyview

Display the IPv4 MBGP routinginformation matching thespecified destination IPaddress

display ip multicast routing-tableip-address[ mask-length | mask ][ longer-match ] [ verbose]


Display MBGP peer groupinformation

displaybgpmulticast group[ group-name]


Display the advertisednetworks

display bgp multicast network Available in anyview

Display AS path informationdisplay bgp multicastpaths[ as-regular-expression ]


Display MBGP peer/peer groupinformation

displaybgpmulticast peer[ ip-address{log-info| verbose} | group-namelog-info | verbose]


Display MBGP routinginformation

display bgp multicastrouting-table[ ip-address[ { mask| mask-length }[ longer-prefixes ] ] ]


Display MBGP routinginformation matching the AS

path ACL

display bgpmulticast routing-table

as-path-acl as-path-acl-number

Available in any

view

Display MBGP CIDR routinginformation

display bgpmulticast routing-table cidrAvailable in anyview

Display MBGP routinginformation matching thespecified BGP community

display bgpmulticast routing-tablecommunity[ aa:nn& ][ no-advertise| no-export|no-export-subconfed] * [ whole-match ]


Display MBGP routinginformation matching an MBGPcommunity list

display bgpmulticast routing-tablecommunity-list{ basic-community-list-number[ whole-match] |adv-community-list-number}&


Display MBGP dampenedrouting information

display bgp multi cast routing-tabledampened



16/19

1-15


Display MBGP dampeningparameter information

display bgp mult icast routing-tabledampening parameter


Display MBGP routinginformation originating fromdifferent ASs

display bgp multicast routing-tabledifferent-origin-as


Display IPv4 MBGP routing flapstatistics

display bgp multicastrouting-tableflap-info [ regular-expressionas-regular-expression | as-path-aclas-path-acl-number| ip-address[ { mask |mask-length} [ longer-match ] ] ]


Display IPv4 MBGP routinginformation sent to or receivedfrom an MBGP peer

display bgpmulticast routing-tablepeer ip-address{ advertised-routes |received-routes } [ network-address[mask |mask-length] | statistic]


Display IPv4 MBGP routinginformation matching an ASregular expression

display bgpmulticast routing-tableregular-expression as-regular-expression


Display IPv4 MBGP routingstatistics

display bgp multicast routing-tablestatistic


Resetting MBGP Connections


Reset specified MBGPconnections

reset bgpipv4multicast { all |as-number| ip-address| group

group-name| external| internal}

Available in userview

Clearing MBGP Information


Clear dampened routinginformation and releasesuppressed routes

reset bgp ipv4 multicast dampening [ ip-address[ mask| mask-length] ]


Clear MBGP route flapstatistics

reset bgp ipv4 multicast flap-info[ regexpas-path-regexp | as-path-aclas-path-acl-number|ip-address [mask|mask-length ] ]


MBGP Configuration Example

Network requirements

As shown in the following figure:

PIM-SM 1 is in AS 100 and PIM-SM 2 is in AS 200. OSPF is the IGP in the two ASs, and MBGP

runs between the two ASs to exchange multicast route information.

The multicast source belongs to PIM-SM 1, and the receiver belongs to PIM-SM 2.


17/19

1-16

It is required that the respective Loopback 0 of Switch A and Switch B be configured as the C-BSR

and C-RP of the respective PIM-SM domains.

Router A and Router B establishes an MSDP peer relationship through MBGP.

Network diagram

Figure 1-1 Network diagram for MBGP configuration

Vlan-in

t102

Vla

n-int103

Vla

n-in

t103 V

lan-in

t102 V

lan-in

t200

Device Interface IP address Device Interface IP addressSource 10.110.1.100/24 Switch C Vlan-int200 10.110.2.1/24Switch A Vlan-int100 10.110.1.1/24 Vlan-int102 192.168.2.2/24

Vlan-int101 192.168.1.1/24 Vlan-int104 192.168.4.1/24Loop0 1.1.1.1/32 Loop0 3.3.3.3/32

Switch B Vlan-int101 192.168.1.2/24 Switch D Vlan-int103 192.168.3.2/24

Vlan-int102 192.168.2.1/24 Vlan-int104 192.168.4.2/24Vlan-int103 192.168.3.1/24 Loop0 4.4.4.4/32Loop0 2.2.2.2/32

Configuration procedure

1) Configure IP addresses for interfaces as shown in the above figure (omitted).

2) Configure OSPF (omitted).

3) Enable IP multicast routing, PIM-SM and IGMP, and configure a PIM-SM domain border.

# Enable IP multicast routing on Switch A, and enable PIM-SM on each interface.

sys t em- vi ew

[ Swi t chA] mul t i cast r out i ng- enabl e

[ Swi t chA] i nt er f ace vl an- i nt er f ace 100

[ Swi t chA- Vl an- i nt er f ace100] pi m sm

[ Swi t chA- Vl an- i nt er f ace100] qui t


[ Swi t chA- Vl an- i nt er f ace101] pi m sm


The configuration on Switch B and Switch D is similar to the configuration on Switch A.

# Enable IP multicast routing on Switch C, enable PIM-SM on each interface, and enable IGMP on the

host-side interface VLAN-interface 200.

sys t em- vi ew


18/19

1-17

[ Swi t chC] mul t i cast r out i ng- enabl e

[ Swi t chC] i nt er f ace vl an- i nt er f ace 102

[ Swi t chC- Vl an- i nt er f ace102] pi m sm

[ Swi t chC- Vl an- i nt er f ace102] qui t






[ Swi t chC- Vl an- i nt erf ace200] i gmp enabl e


# Configure a PIM domain border on Switch A.


[ Swi t chA- Vl an- i nt er f ace101] pi m bsr - boundar y


# Configure a PIM domain border on Switch B.

[ Swi t chB] i nt er f ace vl an- i nt er f ace 101

[ Swi t chB- Vl an- i nt er f ace101] pi m bsr - boundar y

[ Swi t chB- Vl an- i nt er f ace101] qui t

4) Configure Loopback 0 and the position of C-BSR, and C-RP.

# Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch A.

[ Swi t chA] i nt er f ace l oopback 0

[ Swi t chA- LoopBack0] i p address 1. 1. 1. 1 32

[ Swi t chA- LoopBack0] pi m sm

[ Swi t chA- LoopBack0] qui t

[ Swi t chA] pi m

[ Swi t chA- pi m] c- bsr l oopback 0

[ Swi t chA- pi m] c- r p l oopback 0

[ Swi t chA- pi m] qui t

# Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch B.

[ Swi t chB] i nt er f ace l oopback 0

[ Swi t chB- LoopBack0] i p address 2. 2. 2. 2 32

[ Swi t chB- LoopBack0] pi m sm

[ Swi t chB- LoopBack0] qui t

[ Swi t chB] pi m

[ Swi t chB- pi m] c- bsr l oopback 0

[ Swi t chB- pi m] c- r p l oopback 0

[ Swi t chB- pi m] qui t

5) Configure BGP, specify the MBGP peer and enable direct route redistribution.

# On Switch A, configure the MBGP peer and enable direct route redistribution.

[ Swi t chA] bgp 100

[ Swi t chA- bgp] r out er - i d 1. 1. 1. 1

[ Swi t chA- bgp] peer 192. 168. 1. 2 asnumber 200

[ Swi t chA- bgp] i mpor t - r out e di r ect

[ Swi t chA- bgp] i pv4- f ami l y mul t i cast


19/19

[ Swi t chA- bgp- af - mul ] peer 192. 168. 1. 2 enabl e

[ Swi t chA- bgp- af - mul ] i mpor t - r out e di r ect

[ Swi t chA- bgp- af - mul ] qui t

[ Swi t chA- bgp] qui t

# On Switch B, configure the MBGP peer and enable route redistribution from OSPF.

[ Swi t chB] bgp 200

[ Swi t chB- bgp] r out er - i d 2. 2. 2. 2

[ Swi t chB- bgp] peer 192. 168. 1. 1 asnumber 100

[ Swi t chB- bgp] i mport - r out e ospf 1

[ Swi t chB- bgp] i pv4- f ami l y mul t i cast

[ Swi t chB- bgp- af - mul ] peer 192. 168. 1. 1 enabl e

[ Swi t chB- bgp- af - mul ] i mpor t - r out e ospf 1

[ Swi t chB- bgp- af - mul ] qui t

[ Swi t chB- bgp] qui t

6) Configure MSDP peer

# Specify the MSDP peer on Switch A.

[ Swi t chA] msdp

[ Swi t chA- msdp] peer 192. 168. 1. 2 connect - i nt erf ace vl an- i nt erf ace 101

[ Swi t chA- msdp] qui t

# Specify the MSDP peer on Switch B.

[ Swi t chB] msdp

[ Swi t chB- msdp] peer 192. 168. 1. 1 connect - i nt erf ace vl an- i nt erf ace 101

[ Swi t chB- msdp] qui t

7) Verify the configuration

You can use the display bgp multicast peer command to display MBGP peers on a switch. For

example, display MBGP peers on Switch B.

[ Swi t chB] di spl ay bgp mul t i cast peer

BGP l ocal r out er I D : 2. 2. 2. 2

Local AS number : 200

Tot al number of peers : 3 Peers i n est abl i shed st at e : 3

Peer V AS MsgRcvd MsgSent Out Q Pr ef Rcv Up/ Down St at e

192. 168. 1. 1 4 100 56 56 0 0 00: 40: 54 Est abl i shed

You can use the display msdp brief command to display MSDP peers on a switch. For example,

display brief information about MSDP peers on Switch B.

[ Swi t chB] di spl ay msdp br i ef

MSDP Peer Br i ef I nf or mat i on of VPN- I nst ance: publ i c net

Conf i gured Up Li st en Connect Shut down Down

1 1 0 0 0 0

Peer ' s Addr ess St at e Up/ Down t i me AS SA Count Reset Count

192. 168. 1. 1 Up 00: 07: 17 100 1 0

06 MBGP Configuration

Documents

Transcript of 06 MBGP Configuration