21
Task Command Remarks
Display the BGP VPNv4 routing
information of a specific VPN
instance.
display bgp vpnv4 vpn-instance
vpn-instance-name routing-table
[ network-address [ { mask | mask-length }
[ longer-prefixes ] ] | as-path-acl
as-path-acl-number | cidr | community
[ aa:nn ]&<1-13> [ no-advertise |
no-export | no-export-subconfed ] *
[ whole-match ] | community-list
{ basic-community-list-number
[ whole-match ] |
adv-community-list-number }&<1-16> |
dampened | dampening parameter |
different-origin-as | flap-info
[ network-address [ { mask | mask-length }
[ longer-match ] ] | as-path-acl
as-path-acl-number ] | peer ip-address
{ advertised-routes | received-routes } |
statistic ] [ | { begin | exclude | include }
regular-expression | [ flap-info ]
regular-expression as-regular-expression ]
Available in any view.
Clear the route flap dampening
information of a VPN instance.
reset bgp vpn-instance vpn-instance-name
dampening [ network-address [ mask |
mask-length ]
Available in user view.
Clear route flap history information
about a BGP peer of a VPN
instance.
reset bgp vpn-instance vpn-instance-name
ip-address flap-info
reset bgp vpn-instance vpn-instance-name
flap-info [ ip-address [ mask |
mask-length ] | as-path-acl
as-path-acl-number | regexp
as-path-regexp ]
Available in user view.
For commands to display information about a routing table, see Layer 3—IP Routing Command
Reference.
MCE configuration examples
This section describes examples for configuring MCE.
Using OSPF to advertise VPN routes to the PE
Network requirements
As shown in Figure 6, the MCE device is connected to VPN 1 through VLAN-interface 10 and to VPN 2
through VLAN-interface 20. RIP runs in VPN 2.
Configure the MCE device to separate routes from different VPNs and advertise the VPN routes to PE 1
through OSPF.