Configuring L3VPN Access over VCs (Multiple Base Stations Are Located on Different Network Segments)
This section describes how to configure Layer 3 virtual private network (L3VPN) access over virtual circuits (VCs) to implement end-to-end Ethernet service bearing when multiple base stations are located on different network segments.
Context
When multiple base stations are located on different network segments, you must bind a Remote-AP interface to an L3VPN instance and assign an IP address to this interface on a master to implement L3VPN access over VCs.
Prerequisites
- Configure an Interior Gateway Protocol (IGP) to implement the interworking between a master and a radio network controller site gateway (RSG).
- Configure multiprotocol label switching traffic engineering (MPLS TE) or MPLS Label Distribution Protocol (LDP) to provide a public tunnel for the L3VPN.
- Configure basic L3VPN functions on the master.
- Configure IP RAN virtual cluster access.
Procedure
- Run system-view
The system view is displayed.
- Run interface remote-ap interface-number
The Remote-AP interface view is displayed.
- Run ip binding vpn-instance vpn-instance-name
The Remote-AP interface is bound to a specified VPN instance.
- Run ip address ip-address { mask | mask-length }
An IP address is assigned to the Remote-AP interface.
- The IP addresses of a Remote-AP interface and its bound AC interface must be on the same network segment.
- To prevent route recalculations during a primary/secondary master switchover and implement a rapid switchover, configure the same IP address for the primary and secondary masters' Remote-AP interfaces that have been bound to the same AC interface.
- Run commit
The configuration is committed.
Verifying the Configuration
Run the ping command to check network continuity. The command output shows that the master and RSG can ping each other.
Run the display ip routing-table vpn-instance command to view routing information. The command output shows that the master and RSG have available routes to each other.