22Task Command RemarksDisplay the BGP VPNv4 routinginformation of a specific VPNinstance.display bgp vpnv4 vpn-instancevpn-instance-name routing-table[ network-address [ { mask | mask-length }[ longer-prefixes ] ] | as-path-aclas-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-aclas-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 viewClear the route flap dampeninginformation of a VPN instance.reset bgp vpn-instance vpn-instance-namedampening [ network-address [ mask |mask-length ]Available in user viewClear route flap history informationabout a BGP peer of a VPNinstance.reset bgp vpn-instance vpn-instance-nameip-address flap-inforeset bgp vpn-instance vpn-instance-nameflap-info [ ip-address [ mask |mask-length ] | as-path-aclas-path-acl-number | regexpas-path-regexp ]Available in user viewFor commands to display information about a routing table, see Layer 3—IP Routing CommandReference.MCE configuration examplesUsing OSPF to advertise VPN routes to the PENetwork requirementsAs shown in Figure 6, the MCE device is connected to VPN 1 through VLAN-interface 10 and to VPN 2through 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 1through OSPF.
