Configuring inter-as option c, Network requirements – H3C Technologies H3C SR8800 User Manual
Page 321
310
# Configure interface Loopback 0 and start IS-IS on it.
[PE2] interface loopback 0
[PE2-LoopBack0] ip address 5.5.5.9 32
[PE2-LoopBack0] isis enable 1
[PE2-LoopBack0] quit
# Create VPN instance vpn1 and configure the RD and VPN target attributes.
[PE2] ip vpn-instance vpn1
[PE2-vpn-instance-vpn1] route-distinguisher 12:12
[PE2-vpn-instance-vpn1] vpn-target 1:1 2:2 3:3 import-extcommunity
[PE2-vpn-instance-vpn1] vpn-target 3:3 export-extcommunity
[PE2-vpn-instance-vpn1] quit
# Bind the interface connected with CE 1 to the created VPN instance.
[PE2] interface GigabitEthernet 4/1/1
[PE2-GigabitEthernet4/1/1] ip binding vpn-instance vpn1
[PE2-GigabitEthernet4/1/1] ip address 20.0.0.1 8
[PE2-GigabitEthernet4/1/1] quit
# Start BGP on PE 2.
[PE2] bgp 600
# Configure IBGP peer 4.4.4.9 as a VPNv4 peer.
[PE2-bgp] peer 4.4.4.9 as-number 600
[PE2-bgp] peer 4.4.4.9 connect-interface loopback 0
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-af-vpnv4] peer 4.4.4.9 enable
[PE2-bgp-af-vpnv4] quit
# Redistribute direct routes to the VPN routing table of vpn1.
[PE2-bgp] ipv4-family vpn-instance vpn1
[PE2-bgp-vpn1] import-route direct
[PE2-bgp-vpn1] quit
[PE2-bgp] quit
5.
Verify your configurations
# After you complete the configurations, ping PE 1 from PE 2. The ping operation is successful.
[PE2] ping –vpn-instance vpn1 30.0.0.1
# Ping PE 2 from PE 1. The ping operation is successful.
[PE1] ping –vpn-instance vpn1 20.0.0.1
Configuring inter-AS option C
Network requirements
•
Site 1 and Site 2 belong to the same VPN. Site 1 accesses the network through PE 1 in AS 100 and
Site 2 accesses the network through PE 2 in AS 600.
•
PEs in the same AS run IS-IS.
•
PE 1 and ASBR-PE 1 exchange labeled IPv4 routes by MP-IBGP.
•
PE 2 and ASBR-PE 2 exchange labeled IPv4 routes by MP-IBGP.
•
PE 1 and PE 2 are MP-EBGP peers.