3com 8807 참조 가이드

C

HAPTER

 40: BGP/MPLS VPN C

ONFIGURATION

 C

OMMANDS

they both support multi-VPN-instance, Multi-VPN-Instance CE does not necessarily 
support BGP/OSPF interoperability.

When an OSPF process is bound to a VPN instance, the default OSPF router is PE 
router. This command will remove the default setting and change a router into a 
Multi-VPN-Instance CE. . After the configuration, OSPF processes will reestablish 
all its neighbors. DN bits and Route-tag will not be checked in routing calculation. 
To prevent route loss, routing loop test is disabled on PE routes. MGP/OSPF 
interoperability is also disabled to save system resources.

After the display ospf brief command is executed successfully, the system 
prompts the following information:

Multi-VPN-Instance enable on CE router. 

c 

# Configure OSPF process 100 as Multi-VPN-Instance CE.

[3Com-ospf-100] vpn-instance-capability simple 

# Restore the OSPF process 100 as PE.

[3Com-ospf-100] undo vpn-instance-capability 

vpn-target vpn-target-ext-community [ import-extcommunity | 
export-extcommunity | both ]

undo vpn-target vpn-target-ext-community [ import-extcommunity | 
export-extcommunity | both ]

VPN-instance view

import-extcommunity: Specifies ingress route information from the extended 
community of target VPN.

export-extcommunity: Specifies egress route information to the extended 
community of target VPN.

both: Imports both ingress and egress route information to the extended 
community of target VPN.

vpn-target-ext-community: VPN-target extended community attributes to be 
added to the ingress and egress of VPN-instance or the VPN-target extended 
community list of ingress and egress.