2-11
Configure to Use EBGP between a MCE and a PE
To use EBGP to exchange routing information between a MCE and a PE, you need to configure the
peer end as a peer in the BGP-VPNs on both ends, import VPN routes in the site to the MCE, and then
advertise these routes to the PE.
Follow these steps to configure EBGP between a MCE and a PE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp as-number
—
Enter BGP-VPN instance
view
ipv4-family vpn-instance
vpn-instance-name
Required
Configure the PE as a
VPN peer
peer
{
group-name | ip-address
}
as-number
as-number
Required
Import routes of the local
site
import-route
protocol
[
process-id
]
[
med
med-value
|
route-policy
route-policy-name
] *
Required
The MCE device must import
routes of the local site to the
VPN routing table in order to
advertise these routes to the
PE device.
Apply a filter policy for
routes to be advertised
filter-policy
{
acl-number
|
ip-prefix
ip-prefix-name
}
export
[
direct | isis
process-id
|
ospf
process-id
|
rip
process-id
|
static
]
Optional
By default, no filter policy is
applied.
Apply a filter policy for
received routes
filter-policy
{
acl-number
|
ip-prefix
ip-prefix-name
}
import
Optional
By default, no filter policy is
applied.
Displaying and Maintaining MCE
To do…
Use the command…
Remarks
Display the IP routing
tables associated with a
VPN instance
display ip routing-table vpn-instance
vpn-instance-name
[
verbose
]
Available in any view
Display the information
about a VPN instance
display ip vpn-instance
[
instance-name
vpn-instance-name
]
Available in any view
Display information about
a specified BGP VPNv4
peer group
display bgp vpnv4
vpn-instance
vpn-instance-name
group
[
group-name
]
Available in any view
Display information about
BGP VPNv4 routes
injected into a specified
VPN instance
display bgp vpnv4
vpn-instance
vpn-instance-name
network
Available in any view
Display BGP VPNv4 AS
path information
display bgp vpnv4 vpn-instance
vpn-instance-name paths
[
as-regular-expression
]
Available in any view
Summary of Contents for S7906E - Switch
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist...
Page 598: ...ii...
Page 1757: ...4 9...
Page 1770: ...6 4...
Page 2017: ...2 11 Figure 2 3 SFTP client interface...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002...