258Configuring routing between PEsStep Command Remarks1. Enter system view. system-view N/A2. Enter BGP view. bgp as-number N/A3. Configure the remote PE asthe peer.peer { group-name | ip-address }as-number as-number N/A4. Specify the source interfacefor route updates.peer { group-name | ip-address }connect-interface interface-typeinterface-numberBy default, BGP uses the sourceinterface of the optimal routeupdate packet.5. Enter BGP-VPNv4 subaddressfamily view. ipv4-family vpnv4 N/A6. Enable the exchange ofBGP-VPNv4 routinginformation with the specifiedpeer.peer { group-name | ip-address }enableBy default, BGP peers exchangeIPv4 routing information only.Configuring routing features for BGP VPNv4 subaddress familyWith BGP VPNv4 subaddress family, there are a variety of routing features that are the same as those forBGP IPv4 unicast routing. You can select any of the features as required.Configuring common routing features for all types of subaddress familiesFor VPN applications, BGP address families include BGP VPN-IPv4 address family, BGP-L2VPN addressfamily, and VPLS address family. Every command in the following table has the same function on BGProutes for each type of the address families and only takes effect for the BGP routes in the address familyview where the command is executed.To configure common routing features for all types of subaddress families:Step Command Remarks1. Enter system view. system-view N/A2. Enter BGP view. bgp as-number N/A3. Configure the remote PE asthe peer.peer ip-address as-numberas-number N/A4. Specify the interface for TCPconnection.peer ip-address connect-interfaceinterface-type interface-number N/A5. Enter address family view.ipv4-family vpnv4Use one of the commands asneeded.l2vpn-familyvpls-family6. Allow the local AS number toappear in the AS_PATHattribute of a received routeand set the maximum numberof repetitions.peer { group-name | ip-address }allow-as-loop [ number ] Optional.
