231
To do… Use the command… Remarks
Enable the non-standard ORF
capability for a BGP peer/peer
group
peer { group-name | ipv6-address
} capability-advertise orf non-
standard
Optional
By default, standard BGP ORF
capability defined in RFC 5291
and RFC 5292 is supported.
If this feature is not enabled, you
need to configure this command.
For more information about the
command, see the Layer 3—IP
Routing Command Reference.
Enter MBGP address family view ipv4-family multicast —
Enable the ORF IP prefix
negotiation capability for a BGP
peer/peer group
peer { group-name | ip-address }
capability-advertise orf ip-prefix {
both | receive | send }
Optional
Not supported by default.
Table 8 Description of the both, send, and receive parameters and the negotiation result
Local
arameter Peer
arameter Ne
otiation result
send
receive
The ORF sending capability is enabled locally
and the ORF receiving capability is enabled on
the peer.
both
receive
send
The ORF receiving capability is enabled locally
and the ORF sending capability is enabled on the
peer.
both
both both
Both the ORF sending and receiving capabilities
are enabled locally and on the peer, respectively.
Configuring the maximum number of MBGP routes for load
balancing
Follow these steps to configure the number of MBGP routes for load balancing:
To do… Use the command… Remarks
Enter system view system-view
—
Enter BGP view bgp as-number
—
Enter IPv4 MBGP address family
view
ipv4-family multicast
—
Configure the maximum number
of MBGP routes for load
balancing
balance number
Required
Not configured by default.
To Next Page
Loading...
Need help?
General
