H3C LS-3100-52P-OVS-H3 Operation Manual page 865

Static route
RIP
OSPF
IS-IS
EBGP
This introduces the cooperation of routing protocols and MCE in brief. For details on routing protocols,
see the IPv4 Routing module of this manual.
Static routes
A CE can communicate with a site through static routes. As static routes configure for traditional CEs
take effect globally, address overlapping between multiple VPNs remains a problem till the emergence
of MCE. MCE allows static-route-to-VPN-instance binding, which isolates the static routes of different
VPNs.
RIP
An S5500-EI switch can bind RIP processes to VPN instances. With the same binding configured on CE
and site, private network routes of different VPNs can be exchanged between CEs and sites through
different RIP processes, thus isolating and securing VPN routes.
OSPF
An S5500-EI switch can bind OSPF processes to VPN instances and isolate the routes of different
VPNs.
Note that:
For an OSPF process bound to a VPN instance, the router ID of the public network configured in system
view is invalid. So you need to specify the router ID when creating an OSPF process.
An OSPF process can be bound to only one VPN instance, however, a VPN instance can use multiple
OSPF processes for private network route transmission. To make sure routes can be advertised
properly, you need to configure the same domain ID for all the OSPF processes bound to a VPN
instance.
1-6