3Com 3C13636 Configuration Manual page 942

3Com Router 3000 Ethernet Family
Configuration Guide
[PE2-bgp-af-vpn] quit
[PE2-bgp] quit
# Configure ASBR-PE2 to establish EBGP peer relationship with ASBR-PE1 and IBGP
peer relationship with PE2.
[ASBR-PE2] bgp 200
[ASBR-PE2-bgp] ipv4-family vpn-instance vpna
[ASBR-PE2-bgp-af-vpn-instance] group 10 external
[ASBR-PE2-bgp-af-vpn-instance] peer 192.1.1.1 group 10 as-number 100
[ASBR-PE2-bgp-af-vpn-instance] quit
[ASBR-PE2-bgp] group 20
[ASBR-PE2-bgp] peer 202.200.1.2 group 20
[ASBR-PE2-bgp] peer 202.200.1.2 connect-interface loopback0
[ASBR-PE2-bgp] ipv4-family vpnv4
[ASBR-PE2-bgp-af-vpn] peer 20 enable
[ASBR-PE2-bgp-af-vpn] peer 202.200.1.2 group 20
[ASBR-PE2-bgp-af-vpn] quit
[ASBR-PE2-bgp] quit
After the configuration, you can find that the BGP peer relationship has been
established in Established state between PEs and between PE and CE.
Take the display results on PE1 and ASBR-PE1 as an example:
[PE1] display bgp vpnv4 all peer
Peer
--------------------------------------------------------------------
168.1.1.2
202.100.1.1
[ASBR-PE1] display bgp vpnv4 all peer
Peer
--------------------------------------------------------------------
192.1.1.2
202.100.1.2
CEs can learn interface routes from each other. CE1 and CE2 can be pinged
successfully on each other.
[CE1] display ip routing-table
Routing Table: public net
Destination/Mask
127.0.0.0/8
127.0.0.1/32
168.1.0.0/16
168.1.1.2/32
168.2.0.0/16
AS-num Ver Queued-Tx
65001 4 0
100 4 0
AS-num Ver Queued-Tx
200 4 0
100 4 0
Protocol Pre Cost
DIRECT 0 0
DIRECT 0 0
DIRECT 0 0
DIRECT 0 0
BGP 256 0
3Com Corporation
3-80
Chapter 3 BGP/MPLS VPN Configuration
Msg-Rx Msg-Tx
4 7 00:03:23 Established
1 1 00:03:14 Established
Msg-Rx Msg-Tx
5 6 00:03:38 Established
1 1 00:04:17 Established
Nexthop Interface
127.0.0.1 InLoopBack0
127.0.0.1 InLoopBack0
168.1.1.2 Ethernet1
127.0.0.1 InLoopBack0
168.1.1.1 Ethernet2/0/0
Up/Down State
Up/Down State