Table of Contents
Advertisement
Step
9.
(Optional.) Configure
filtering of received
routes.
Configuring IBGP between an MCE and a PE
Step
1.
Enter system view.
2.
Enter BGP view.
3.
Enter BGP-VPN instance
view.
4.
Configure the PE as an IBGP
peer.
5.
Enter BGP-VPN IPv4 unicast
address family view.
6.
Enable BGP to exchange
IPv4 unicast routes with the
peer.
7.
Redistribute the VPN routes
of the VPN site.
8.
(Optional.) Configure filtering
of advertised routes.
9.
(Optional.) Configure filtering
of received routes.
Specifying the VPN label processing mode on the
egress PE
An egress PE can process VPN labels in either POPGO or POP mode:
•
POPGO forwarding—Pops the label and forwards the packet out of the egress interface
corresponding to the label.
•
POP forwarding—Pops the label and forwards the packet through the FIB table.
To specify the VPN label processing mode on an egress PE:
Step
1.
Enter system view.
2.
Enter BGP view.
3.
Specify the VPN label
processing mode as POPGO
forwarding.
Command
filter-policy { acl-number | prefix-list
prefix-list-name } import
Command
system-view
bgp as-number
ip vpn-instance vpn-instance-name
peer { group-name | ip-address
[ mask-length ] } as-number
as-number
address-family ipv4 [ unicast ]
peer { group-name | ip-address
[ mask-length ] } enable
import-route protocol [ process-id |
all-processes ] [ allow-direct | med
med-value | route-policy
route-policy-name ] *
filter-policy { acl-number | prefix-list
prefix-list-name } export [ protocol
process-id ]
filter-policy { acl-number | prefix-list
prefix-list-name } import
Command
system-view
bgp as-number
vpn popgo
237
Remarks
By default, BGP does not filter
received routes.
Remarks
N/A
N/A
N/A
N/A
N/A
By default, BGP does not
exchange IPv4 unicast routes
with any peer.
By default, no routes are
redistributed into BGP.
By default, BGP does not filter
advertised routes.
By default, BGP does not filter
received routes.
Remarks
N/A
N/A
The default is POP forwarding.
Advertisement
Table of Contents
