Vpn-Target - 3Com 8807 Command Reference Manual

8800 series
Hide thumbs Also See for 8807:
Table of Contents

Advertisement

758
C
40: BGP/MPLS VPN C
C
HAPTER
ONFIGURATION
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
CAUTION: OSPF processes will set up all its neighbors again after this command is
executed.
Example
# 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

Syntax
vpn-target vpn-target-ext-community [ import-extcommunity |
export-extcommunity | both ]
undo vpn-target vpn-target-ext-community [ import-extcommunity |
export-extcommunity | both ]
View
VPN-instance view
Parameter
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.

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

88148810

Table of Contents