Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-MBGP Commands | 120.49 KB |
Chapter 1 MBGP Multicast Extension Configuration Commands
1.1 MBGP Multicast Extension Configuration Commands
1.1.2 compare-different-as-med
1.1.4 default local-preference
1.1.6 display bgp multicast group
1.1.7 display bgp multicast network
1.1.8 display bgp multicast peer
1.1.9 display bgp multicast routing-table
1.1.10 display bgp multicast routing-table as-path-acl
1.1.11 display bgp multicast routing-table cidr
1.1.12 display bgp multicast routing-table community
1.1.13 display bgp multicast routing-table community-list
1.1.14 display bgp multicast routing-table different-origin-as
1.1.15 display bgp multicast routing-table peer
1.1.16 display bgp multicast routing-table regular-expression
1.1.22 peer advertise-community
1.1.24 peer as-path-acl export
1.1.25 peer as-path-acl import
1.1.27 peer filter-policy export
1.1.28 peer filter-policy import
1.1.36 peer route-policy export
1.1.37 peer route-policy import
1.1.39 reflect between-clients
Chapter 1 MBGP Multicast Extension Configuration Commands
1.1 MBGP Multicast Extension Configuration Commands
1.1.1 aggregate
aggregate address mask [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] *
undo aggregate address mask [ as-set | attribute-policy route-policy-name | detail-suppressed | origin-policy route-policy-name | suppress-policy route-policy-name ] *
IPv4 multicast sub-address family view
Parameters
address: Address of the aggregated route.
mask: Network mask of the aggregated route.
as-set: Generates a route with AS_SET segment. This parameter is not recommended when aggregating many AS paths.
attribute-policy route-policy-name: Sets aggregate attribute.
detail-suppressed: Advertises the aggregated routes rather than the specific routes.
origin-policy route-policy-name: Filters the originate routes of the aggregate.
suppress-policy route-policy-name: Does not advertise the specific routes selected.
Use the aggregate command to create a multicast aggregated record in the BGP routing table.
Use the undo aggregate command to disable this function.
By default, no route is aggregated.
Use the aggregate command without parameters to create one local aggregated route and set atomic aggregation attributes.
Examples
# Create an aggregation entry in the MBGP routing table, with aggregated route address as 192.213.0.0.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] aggregate 192.213.0.0 255.255.0.0
1.1.2 compare-different-as-med
compare-different-as-med
undo compare-different-as-med
IPv4 multicast sub-address family view
Parameters
Use the compare-different-as-med command to enable to compare the route MED values of neighbors from different ASs.
Use the undo compare-different-as-med command to disable this function.
By default, the comparison function is disabled.
If there are multiple routes available to the same destination address, you can select the route with the smallest MED value.
This command is not recommended unless you make sure that different ASs use the same IGP and route selection modes.
Examples
# Enable to compare the route MED values of neighbors from different ASs.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] compare-different-as-med
1.1.3 debugging bgp mp-update
debugging bgp mp-update [ receive | send ] [ verbose ]
undo debugging bgp mp-update
Parameters
receive: Debugs the MBGP Update messages received.
send: Debugs the MBGP Update messages sent.
verbose: Debugs detailed information.
Use the debugging bgp mp-update command to enable to debug MBGP Update messages.
Use the undo debugging bgp mp-update command to disable the debugging.
By default, the debugging function is disabled.
Examples
# Enable MBGP Update message debugging.
<H3C> debugging bgp mp-update
1.1.4 default local-preference
default local-preference value
undo default local-preference
IPv4 multicast sub-address family view
Parameters
value: Default local precedence you configured, in the range of 0 to 4294967295. By default, it is 100. The greatest value corresponds to the highest precedence level.
Use the default local-preference command to configure the default local precedence.
Use the undo default local-preference command to restore the default value.
You can affect BGP route selection by configuring different local precedence values.
Examples
# Configure the default local precedence value as 180.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] default local-preference 180
1.1.5 default med
default med med-value
undo default med
IPv4 multicast sub-address family view
Parameters
med-value: MED value, in the range of 0 to 4294967295. By default, it is 0.
Use the default med command to configure system MED value.
Use the display bgp multicast group command to restore the default value.
Multi-exit discriminator (MED) attribute is the external metric for a route. Unlike local precedence attribute, MED is exchanged, between ASs, and one it enters an AS, it does not leave the AS. MED attribute is used in best route selection. When a device running BGP travels through different external peers and get the routes with identical destination, but different next-hop addresses, it selects these routes according to their MED values. The route with smaller MED value will be selected as the external AS route if other attributes are the same.
Examples
# Configure system MED value as 25.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] default med 25
1.1.6 display bgp multicast group
display bgp multicast group [ group-name ]
Parameters
group-name: Peer group. If no peer group is specified, the information about all peer groups will be displayed.
Use the display bgp multicast group command to view the information about peer groups.
Examples
# View the information about the peer group named my_peer.
<H3C> display bgp multicast group my_peer
1.1.7 display bgp multicast network
display bgp multicast network
Parameters
Use the display bgp multicast network command to view the routing information that MBGP advertises.
Examples
# View the network segment routing information MBGP advertises.
<H3C> display bgp multicast network
1.1.8 display bgp multicast peer
display bgp multicast peer [ peer-address ] [ verbose ]
Parameters
peer-address: Peer address, in dotted decimal format.
verbose: Displays detailed information.
Use the display bgp multicast peer command to view the MBGP peer information.
Examples
# View the MBGP peer detailed information.
<H3C> display bgp multicast peer verbose
1.1.9 display bgp multicast routing-table
display bgp multicast routing-table [ ip-address [ mask ] ]
Parameters
ip-address: IP address of the network segment whose MBGP routing information with specified IP address.
Use the display bgp multicast routing-table command to view MBGP routing information.
Examples
# Display MBGP routing information of network segment 14.1.0.0.
<H3C> display bgp multicast routing-table 14.1.0.0
1.1.10 display bgp multicast routing-table as-path-acl
display bgp multicast routing-table as-path-acl acl-number
Parameters
acl-number: Matched AS path list number, ranging from 1 to 199.
Use the display bgp multicast routing-table as-path-acl command to view routes that match an as-path acl.
Examples
# Display routes that match the as-path-acl 2.
<H3C> display bgp multicast routing-table as-path-acl 2
1.1.11 display bgp multicast routing-table cidr
display bgp multicast routing-table cidr
Parameters
Use the display bgp multicast routing-table cidr command to view the non-natural network mask, namely the classless inter-domain routing (CIDR) information.
Examples
# View CIDR routing information.
<H3C> display bgp multicast routing-table cidr
1.1.12 display bgp multicast routing-table community
display bgp multicast routing-table community [ aa:nn | no-export-subconfed | no-advertise | no-export ] * [ whole-match ]
Parameters
aa:nn: Community number.
no-export-subconfed: Does not send matched routes outside the local autonomous system.
no-advertise: Does not advertise matched routes to any peer.
no-export: Does not advertise routes outside the local autonomous system but advertise routes to other sub-autonomous systems.
whole-match: Exact match.
Use the display bgp multicast routing-table community command to view routing information of a specified MBGP community.
Examples
# Display routing information of the specified MBGP community
<H3C> display bgp multicast routing-table community 600:1
1.1.13 display bgp multicast routing-table community-list
display bgp multicast routing-table community-list community-list-number [ whole-match ]
Parameters
community-list-number: Number of the specified community list.
exact-match: Exact match.
Use the display bgp multicast routing-table community-list command to view the routing information of a specified MBGP community list.
Examples
# Display routing information of the specified MBGP community list.
<H3C> display bgp multicast routing-table community-list 1
1.1.14 display bgp multicast routing-table different-origin-as
display bgp multicast routing-table different-origin-as
Parameters
Use the display bgp multicast routing-table different-origin-as command to view AS routes of different origins.
Examples
# Display AS routes of different origins.
<H3C> display bgp multicast routing-table different-origin-as
1.1.15 display bgp multicast routing-table peer
display bgp multicast routing-table peer peer-address { received | advertised } [ network-address [ mask ] | statistic ]
Parameters
peer-address: Peer address, in dotted decimal format.
received: Routing information received from a specified peer.
advertised: Routing information advertised from a specified peer.
network-address: IP address of the destination network.
mask: Mask of the destination network.
statistic: Statistic information of the route.
Use the display bgp multicast routing-table peer command to view the routes received/advertised at/to the specified peer.
Examples
# Display routing information advertised to the peer 10.10.1.11.
<H3C> display bgp multicast routing-table peer 10.10.1.11 advertised
1.1.16 display bgp multicast routing-table regular-expression
display bgp multicast routing-table regular-expression as-regular-expression
Parameters
as-regular-expression: AS regular expression matched.
Use the display bgp multicast routing-table regular-expression command to view the routing information matching the specified AS regular expression.
Examples
# Display routing information matching AS regular expression ^600$.
<H3C> display bgp multicast routing-table regular-expression ^600$
1.1.17 filter-policy export
filter-policy { acl-number | ip-prefix ip-prefix-name } export [ protocol ]
undo filter-policy { acl-number | ip-prefix ip-prefix-name } export [ protocol ]
IPv4 multicast sub-address family view
Parameters
acl-number: Number of ACL used in matching the destination address domain of routing information, in the range of 2000 to 3999.
ip-prefix-name: Name of the IP prefix used in matching the destination address domain of routing information, in the range of 1 to 19.
Protocol: Protocol specifying which kind of routing information shall be filtered out, with options currently available include direct, ospf, ospf-ase, ospf-nssa, rip, is-is and static.
Use the filter-policy export command to set to filter the advertised routes. Only those pass through the filter can be advertised by BGP.
Use the undo filter-policy export command to cancel route filtering.
By default, filtering the advertised routes is not enabled.
The command affects route advertising by BGP. If you specify the protocol parameter, the device only filters the routes with the specified protocol imported, without influence on the routes importing other protocols. Otherwise, the device filters the routes importing any protocols.
Examples
# Filter all BGP-advertised routes using ACL 2000.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] filter-policy 2000 export
1.1.18 filter-policy import
filter-policy gateway ip-prefix-name import
undo filter-policy gateway ip-prefix-name import
filter-policy { acl-number | ip-prefix ip-prefix-name } import
undo filter-policy { acl-number | ip-prefix ip-prefix-name } import
IPv4 multicast sub-address family view
Parameters
acl-number: Number of ACL used in matching the destination address domain of routing information, in the range of 2000 to 3999.
ip-prefix ip-prefix-name: Specifies the IP prefix used in matching the destination address domain of routing information, in the range of 1 to 19.
gateway ip-prefix-name: Specifies IP prefix of the neighbor device, in the range of 1 to 19, to filter the routing information advertised by a specified neighbor device.
Use the filter-policy gateway import command to set to filter the routes advertised by a specified neighbor device. Only those pass through the filter can be advertised by BGP.
Use the undo filter-policy gateway import command to cancel route filtering.
Use the filter-policy import command to set to filter the global routes received.
Use the undo filter-policy import command to cancel route filtering.
By default, filtering the received routes is not enabled.
This configuration determines whether to add the routes into the BGP routing table.
Examples
# Filter all BGP-received routes using ACL 2000.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] filter-policy 2000 import
1.1.19 import-route
import-route protocol [ route-policy route-policy-name | med med-value ] *
undo import-route protocol
IPv4 multicast sub-address family view
Parameters
protocol: Source routing protocols that can be imported, which can be direct, ospf, ospf-ase, ospf-nssa, rip, isis and static.
med-value: Metric value loaded by an imported route, ranging from 0 to 4,294,967,295.
route-policy-name: Route policy used for importing routes.
Use the import-route command to import routing information of other protocols into MBGP.
Use the undo import-route command to cancel the importing.
By default, MBGP will not import routing information of other protocols.
Examples
# Import static routes.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] import-route static
1.1.20 ipv4-family multicast
ipv4-family multicast
undo ipv4-family multicast
BGP view, VPN instance sub-address family view, VPNv4 sub-address family view
Parameters
Use the ipv4-family multicast command to enter the IPv4 multicast sub-address family view.
Use the undo ipv4-family multicast command to exit the IPv4 multicast sub-address family view, return to the unicast view and remove all the information in multicast.
Examples
# Enter the IPv4 multicast sub-address family view.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul]
1.1.21 network
network ip-address [ address-mask ] [ route-policy route-policy-name ]
undo network ip-address [ address-mask ] [ route-policy route-policy-name ]
IPv4 multicast sub-address family view
Parameters
ip-address: Network address that BGP advertises.
address-mask: Mask of the network address.
route-policy policy-name: Route-policy applied to the routes advertised.
Use the network command to configure the network addresses to be sent by the local MBGP.
Use the undo network command to remove the configuration.
By default, the local MBGP does not send any route.
Examples
# Advertise routes to network segment 10.0.0.0/16.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] network 10.0.0.0 255.255.0.0
1.1.22 peer advertise-community
peer group-name advertise-community
undo peer group-name advertise-community
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
Use the peer advertise-community command to set to send community attributes to a peer group.
Use the undo peer advertise-community command to remove the configuration.
By default, no community attribute is sent to any peer group.
Examples
# Configure to send community attributes to peer group “test”.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test advertise-community
1.1.23 peer allow-as-loop
peer { group-name | peer-address } allow-as-loop [ number ]
undo peer { group-name | peer-address } allow-as-loop
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
peer-address: IP address of the peer.
number: Number of repetitions of local AS IDs, in the range of 1 to 10. By default, the number of repetitions is 3.
Use the peer allow-as-loop command to specify the number of repetitions of local AS IDs.
Use the undo peer allow-as-loop command to remove the configuration.
Related commands: display current-configuration, display bgp routing-table peer.
Examples
# Set the number of repetitions of local AS IDs to 2.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer 1.1.1.1 allow-as-loop 2
1.1.24 peer as-path-acl export
peer { group-name | peer-address } as-path-acl acl-number export
undo peer { group-name | peer-address } as-path-acl acl-number export
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
peer-address: IP address of the peer; uses dotted decimal notation.
acl-number: Filter list number of an AS regular expression, In the range of 1 to 199.
export: Uses the AS path list to filter the advertised routes.
Use the peer as-path-acl export command to configure filtering Policy of MBGP advertised routes based on AS path list.
Use the undo peer as-path-acl command to cancel the existing configuration.
By default, the peer group has no AS path list.
This command can only be configured on peer group.
Related commands: peer as-path-acl import, ip as-path-acl.
Examples
# Configure the peer group test to use AS path list 2 to filter the advertised routes.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test as-path-acl 2 export
1.1.25 peer as-path-acl import
peer { group-name | peer-address } as-path-acl acl-number import
undo peer { group-name | peer-address } as-path-acl acl-number import
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
peer-address: IP address of the peer.
acl-number: Filter list number of an AS regular expression, in the range 1 to 199.
import: Uses the AS path list to filter the received routes.
Use the peer as-path-acl import command to configure filtering Policy of MBGP received routes based on AS path list.
Use the undo peer as-path-acl import command to cancel the existing configuration.
By default, the peer/peer group has no AS path list.
The inbound filter policy configured for the peer takes precedence over the configurations for the peer group.
Related commands: peer as-path-acl export, ip as-path-acl.
Examples
# Set the AS path ACL of the peer group test to filter BGP received routes.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test as-path-acl 3 import
1.1.26 peer enable
peer group-name enable
undo peer group-name enable
IPv4 multicast sub-address family view
Parameters
group-name: Name of the multicast peer group.
Use the peer enable command to enable the MBGP peer group.
Use the undo peer enable command to disable the MBGP peer group.
By default, the MBGP peer group is disabled.
The device can establish the connection with a multicast peer only if the peer group is enabled.
Examples
# Enable peer group group1.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer group1 enable
1.1.27 peer filter-policy export
peer group-name filter-policy acl-number export
undo peer group-name filter-policy acl-number export
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
acl-number: Number of IP ACL ranging from 2000 to 3999. That is, you can use basic ACLs or advanced ACLs.
export: Applies the filter policy to the advertised routes. This keyword is only valid for the peer groups.
Use the peer filter-policy export command to configure the peer group to apply the ACL-based filter policy to the advertised routes.
Use the undo peer filter-policy export command to cancel the existing configuration.
By default, no ACL-based filter policy is configured.
The peer filter-policy export command can only be configured on peer groups.
Related commands: peer filter-policy import, acl.
Examples
# Configure the peer group test to use ACL 2000 to filter the advertised routes.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test filter-policy 2000 export
1.1.28 peer filter-policy import
peer { group-name | peer-address } filter-policy acl-number import
undo peer { group-name | peer-address } filter-policy acl-number import
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
peer-address: IP address of the peer.
acl-number: Number of IP ACL, ranging from 2000 to 3999. That is, you can use basic ACLs or advanced ACLs.
Use the peer filter-policy import command to configure the peer to apply the ACL-based filter policy to the received routes.
Use the undo peer filter-policy import command to cancel the existing configuration.
By default, no ACL-based filter policy is configured.
Related commands: peer filter-policy export, acl.
The inbound filter policy configured for the peer takes precedence over the configurations for the peer group.
Examples
# Configure the peer group test to use ACL 2000 to filter the received routes.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test filter-policy 2000 import
1.1.29 peer group
Syntax
peer peer-address group group-name
undo peer peer-address
View
IPv4 multicast sub-address family view
Parameters
peer-address: IP address of the peer, in dotted decimal format.
group-name: Name of the peer, consisting of one to 47 alphanumeric characters.
Description
Use the peer group command to add a peer into a peer group.
Use the undo peer group command to delete the peer.
Caution:
You must firstly add the specific peer in the peer group in BGP view and enable the peer group in IPv4 multicast sub-address family view before you can this command.
Examples
# Add peer 10.1.1.1 to EBGP peer group TEST.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] group TEST external.
[H3C-bgp] peer TEST as-number 2004
[H3C-bgp] peer 10.1.1.1 group TEST
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer TEST enable
[H3C-bgp-af-mul] peer 10.1.1.1 group TEST
1.1.30 peer ip-prefix export
peer group-name ip-prefix prefixname export
undo peer group-name ip-prefix prefixname export
IPv4 multicast sub-address family view
Parameters
group-name: Name of peer group.
prefixname: Name of the specified ip-prefix.
Use the peer ip-prefix export command to configure the route filtering policy of routes advertised by the peer group based on the ip-prefix.
Use the undo peer ip-prefix export command to cancel the route filtering policy of the peer/peer group based on the ip-prefix.
By default, the route filtering policy of the peer group is not specified.
The peer ip-prefix export command can only be configured on the peer groups.
Related commands: peer ip-prefix import.
Examples
# Configure the route filtering policy of the peer group1 based on the ip-prefix list1.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer group1 ip-prefix list1 export
1.1.31 peer ip-prefix import
peer { group-name | peer-address } ip-prefix prefixname import
undo peer { group-name | peer-address } ip-prefix prefixname import
IPv4 multicast sub-address family view
Parameters
group-name: Name of peer group.
peer-address: IP address of the peer, in dotted decimal format.
prefixname: Name of the specified ip-prefix, a character string of 1 to 19 characters.
Use the peer ip-prefix import command to configure the route filtering policy of routes received by the peer based on the ip-prefix.
Use the undo peer ip-prefix import command to cancel the route filtering policy of the peer based on the ip-prefix.
By default, the route filtering policy of the peer is not specified.
The inbound route policy configured for the peer takes precedence over the configurations for the peer group.
Related commands: peer ip-prefix export.
Examples
# Configure the route filtering policy of the peer group1 based on the ip-prefix list1.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer group1 ip-prefix list1 import
1.1.32 peer next-hop-local
peer group-name next-hop-local
undo peer group-name next-hop-local
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
Use the peer next-hop-local command to remove the processing of the next hop in routes which BGP will advertise to the peer group and set the local address as the next hop.
Use the undo peer next-hop-local command to cancel the configuration.
Examples
# Specify the local address as next-hop when advertising routes to peer group named test.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test next-hop-local
1.1.33 peer public-as-only
peer group-name public-as-only
undo peer group-name public-as-only
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
Use the peer public-as-only command to set to contain only public AS IDs in the MBGP Update message, but not private AS IDs.
Use the undo peer public-as-only command to restore the default setting, the device contains only private AS IDs in the MBGP Update message.
By default, the private AS ID is carried when BGP sends MBGP Update message.
Generally, MBGP sends MBGP Update message with the AS ID (which can be either the public AS number or private AS number) contained. To enable some egress devices to ignore the private AS ID when sending MBGP Update message, you can configure not to carry the private AS IDs when sending MBGP Update message.
Examples
# Set not to carry private AS IDs when sending MBGP Update message to peer group "test”.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test public-as-only
1.1.34 peer reflect-client
peer group-name reflect-client
undo peer group-name reflect-client
IPv4 multicast sub-address family view
Parameters
group-name: Name of the peer group.
Use the peer reflect-client command to configure a peer (group) as a client of the route reflector.
Use the undo peer reflect-client command to remove the configuration.
By default, there is no route reflector in the autonomous system.
Examples
# Configure peer group “test” as the client of the route reflector.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test reflect-client
1.1.35 peer route-limit
Syntax
peer { group-name | peer-address } route-limit route-limit-value [ route-limit-percent ] [ alter-only | idle-forever | idle-timeout timeout-value]
undo peer { group-name | peer-address } route-limit
View
IPv4 multicast sub-address family view
Parameters
peer-address: IP address of a peer group.
group-name: Name of a peer group, a string of 1 to 47 alphanumeric characters.
route-limit-value: Maximum number of routes the peer group can receive, in the range of 1 to 200,000.
route-limit-percent: Percentage of the number of received routes in the allowed maximum number of routes that triggers a warning message.
timeout-value: Length of time in seconds that must pass before a BGP connection can be re-established, in the range of 1 to 65,535.
Description
Use the peer route-limit command to configure the maximum number of routes that the specified peer group can receive.
Use the undo peer route-limit command to remove the configured limit of routes that can be received.
This command has no default settings. All the parameters need to be specified through the command line.
If alter-only is provided, a warning message is generated when the number of routes received by the specified peer group reaches the allowed maximum number, but the connection will be retained.
If idle-forever is provided, a warning message is generated when the number of routes received by the specified peer group reaches the allowed maximum number and at the same time the BGP connection is removed. The connection can be re-established only by means of the reset bgp command.
If idle-timeout is provided, a warning message is generated when the number of routes received by the specified peer group reaches the allowed maximum number, and the BGP connection is torn down at the same time. The period specified by timeout-value must pass before the connection can be re-established.
Examples
# Set the maximum number of routes that can be received by each outgoing peer in the peer group to 20000, with the following actions:
l A warning message is displayed when the number of received routes exceeds 4000;
l When the number of received routes exceeds 20000, the connection is removed;
l The BGP connection is re-established 30 seconds later.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C–bgp-af-mul] peer test route-limit 20000 20 idle-timeout 30
1.1.36 peer route-policy export
peer group-name route-policy policy-name export
undo peer group-name route-policy policy-name export
IPv4 multicast sub-address family view
Parameters
group-name: Name of peer group.
peer-address: IP address of the peer.
Use the peer route-policy export command to assign the Route-policy to the routes advertised to the peer group.
Use the undo peer route-policy export command to delete the specified Route-policy.
By default, the peer/peer group has no Route-policy association.
Related commands: peer route-policy import.
Examples
# Apply the Route-policy named test-policy to the route coming from the peer group test.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test route-policy test-policy export
1.1.37 peer route-policy import
peer { group-name | peer-address } route-policy policy-name import
undo peer { group-name | peer-address } route-policy policy-name import
IPv4 multicast sub-address family view
Parameters
group-name: Name of peer group.
peer-address: IP address of the peer.
policy-name: Name of the applied route policy.
Use the peer route-policy import command to assign the Route-policy to the route coming from the peer..
Use the undo peer route-policy import command to delete the specified Route-policy.
By default, the peer has no Route-policy association.
The inbound route policy configured for the peer takes precedence over the configurations for the peer group.
Related commands: peer route-limit.
Examples
# Apply the Route-policy named test-policy to the route coming from the peer group test.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] peer test route-policy test-policy import
1.1.38 preference
preference ebgp-value ibgp-value local-value
undo preference
IPv4 multicast sub-address family view
Parameters
ebgp-value: EBGP route priority, in the range of 1 to 256. By default, it is 256.
ibgp-value: IBGP route priority, in the range of 1 to 256. By default, it is 256.
local-value: Local route priority, in the range of 1 to 256. By default, it is 130.
Use the preference command to configure MBGP protocol priority.
Use the undo preference command to restore the default priority.
You can configure different priority values for different types of MBGP routes.
Examples
# Set the priority of EBGP, IBGP and local routes all to 170.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] preference 170 170 170
1.1.39 reflect between-clients
reflect between-clients
undo reflect between-clients
IPv4 multicast sub-address family view
Parameters
Use the reflect between-clients command to enable route reflection between clients.
Use the undo reflect between-clients command to disable route reflection between clients.
When configured, the route reflector can reflect routes of a client to other clients.
By default, all-connection is not required for the clients with route reflectors configured, since the routes are by default reflected from one client to others. For all-connection clients, route reflection is unnecessary.
Related commands: reflector cluster-id, peer reflect-client.
Examples
# Disable route reflection function.
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] undo reflect between-clients
1.1.40 reflector cluster-id
reflector cluster-id { cluster-id | address }
undo reflector cluster-id
IPv4 multicast sub-address family view
Parameters
cluster-id: Route reflector cluster ID, in integer number or IP address format, range 1 to 4294967295.
address: Route reflector cluster ID in IP address format.
Use the reflector cluster-id command to configure route reflector cluster ID.
Use the undo reflector cluster-id command to delete route reflector cluster ID.
By default, each route reflector uses its own route ID as cluster ID.
In general, one cluster has only one route reflector, and then the router ID for the route reflector can be used to identify the cluster. If a cluster has several route reflectors, for multiple route reflectors can improve network stability, then you can use this command to specify the same cluster ID for them all.
Related commands: reflect between-clients, peer reflect-client.
Examples
# Specify cluster ID for local device, one of the router reflectors.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] reflector cluster-id 80
[H3C-bgp-af-mul] peer test reflect-client
1.1.41 refresh bgp multicast
Syntax
refresh bgp { all | peer-address | group group-name } multicast { import | export }
View
User view
Parameters
all: Refreshes multicast sub-address family routes of all peers.
peer-address: Multicast sub-address family route of the specified peer.
group-name: Multicast sub-address family routes of all members of the specified peer group.
import: Sends ROUTE-REFRESH packets to request the peer to send all multicast sub-address family routes again.
export: Sends all multicast sub-address family routes again.
Description
Use the refresh bgp multicast command to request the peer to send multicast sub-address family routes again, or send multicast sub-address family routes again.
Examples
# Request all the peers to send multicast sub-address family routes again.
<H3C> refresh bgp all multicast import
1.1.42 summary
summary
undo summary
IPv4 multicast sub-address family view
Parameters
Use the summary command to set to auto-aggregate subnet routes.
Use the undo summary command to remove the configuration.
By default, subnet routes cannot be aggregated automatically.
After the summary command is executed, MBGP cannot receive the subnet routes imported by IGP. You can use this command to reduce route selection information.
Examples
# Enable subnet route auto-aggregation.
<H3C> system-view
System View: return to User View with Ctrl+Z.
[H3C] bgp 100
[H3C-bgp] ipv4-family multicast
[H3C-bgp-af-mul] summary
