Displaying and maintaining ipv6 mce, Ipv6 mce configuration example, Network requirements – H3C Technologies H3C S12500-X Series Switches User Manual
Page 359
348
Step Command
Remarks
5.
Enter BGP-VPN IPv6
unicast address family
view.
address-family ipv6 [ unicast ]
N/A
6.
Enable BGP to exchange
IPv6 unicast routes with
the peer.
peer { group-name | ipv6-address } enable
By default, BGP does not
exchange IPv6 unicast routes
with any peer.
7.
Redistribute the VPN
routes of the VPN site.
import-route protocol [ process-id [ med
med-value | route-policy
route-policy-name ] * ]
By default, no routes are
redistributed into BGP.
8.
(Optional.) Configure
filtering of advertised
routes.
filter-policy { acl6-number | prefix-list
ipv6-prefix-name } export [ protocol
process-id ]
By default, BGP does not filter
advertised routes.
9.
(Optional.) Configure
filtering of received
routes.
filter-policy { acl6-number | prefix-list
ipv6-prefix-name } import
Optional.
By default, BGP does not filter
received routes.
Displaying and maintaining IPv6 MCE
Execute display commands in any view.
Task Command
Display information about a
specified VPN instance or all VPN
instances.
display ip vpn-instance [ instance-name vpn-instance-name ]
Display BGP peer group information
for a VPN instance.
display bgp group ipv6 vpn-instance vpn-instance-name [ group-name ]
Display BGP peer information for a
VPN instance.
display bgp peer ipv6 vpn-instance vpn-instance-name [ group-name
log-info | ipv6-address { log-info | verbose } | verbose ]
For commands that display information about a routing table, see Layer 3—IP Routing Command
Reference.
IPv6 MCE configuration example
Network requirements
As shown in
, the MCE device is connected to VPN 1 through VLAN-interface 10 and to VPN
2 through VLAN-interface 20. RIPng runs in VPN 2.
Configure the MCE to separate routes from different VPNs and advertise VPN routes to PE 1 through
OSPFv3.