H3C SR8800 10G Mpls Configuration Manual page 266

Core routers
Table of Contents

Advertisement

routes for each type of the address families and only takes effect for the BGP routes in the address family
view where the command is executed.
To configure common routing features for all types of subaddress families:
Step
1.
Enter system view.
2.
Enter BGP view.
3.
Configure the remote PE as
the peer.
4.
Specify the interface for TCP
connection.
5.
Enter address family view.
6.
Allow the local AS number to
appear in the AS_PATH
attribute of a received route
and set the maximum number
of repetitions.
7.
Enable a peer or peer group
for an address family and
enable the exchange of BGP
routing information of the
address family.
8.
Add a peer into an existing
peer group.
9.
Configure the system to use
the local address as the next
hop of a route to be
advertised to a specific peer
or peer group.
10.
Configure the system to be the
RR and set a peer or peer
group as the client of the RR.
11.
Enable the Outbound Route
Filtering (ORF) capability for a
BGP peer/peer group.
12.
Enable VPN target filtering for
received VPNv4 routes.
Command
system-view
bgp as-number
peer ip-address as-number
as-number
peer ip-address connect-interface
interface-type interface-number
ipv4-family vpnv4
l2vpn-family
vpls-family
peer { group-name | ip-address }
allow-as-loop [ number ]
peer { group-name | ip-address }
enable
peer ip-address group group-name
peer { group-name | ip-address }
next-hop-local
peer { group-name | ip-address }
reflect-client
peer { group-name | ip-address }
capability-advertise orf ip-prefix
{ both | receive | send }
policy vpn-target
255
Remarks
N/A
N/A
N/A
N/A
Use one of the commands as
needed.
Optional.
By default, only IPv4 routing
information is exchanged between
BGP peers.
Optional.
Optional.
By default, the system uses the local
address as the next hop of a route
to be advertised to an EBGP peer.
In the inter-AS option C solution,
you need to configure the peer
{ group-name | ip-address }
next-hop-invariable command on
the RR for multi-hop EBGP
neighbors and reflector clients to
make sure that the next hop of a
VPN route will not be changed.
Optional.
By default, no RR or RR client is
configured.
Optional.
By default, the ORF capability is
disabled on a BGP peer or peer
group.
Optional.
Enabled by default.

Advertisement

Table of Contents
loading

Table of Contents