To configure an Epipe site for BGP multi-homing

Prerequisites

Configure an Epipe site for BGP multi-homing to allow for multi-homed connectivity to G.8031 Ethernet tunnels between two CEs. G.8031 resiliency is used on the edges and then pseudowires are allowed to reach the far end, where G.8031 can again be used in a multi-chassis mode.

G.8031 is created on two CEs which are multi-homed to two PEs. Using BGP and CFM, PE routers enable or disable the CE-PE SAPs. The core is IP/MPLS and Epipe is used for transport between the PEs. The Ethernet tunnels are created on the CEs and the Epipe service on the CEs uses these tunnels.

Steps
 
1 

Before you configure a site for BGP multi-homing, you must either:

  1. Enable BGP on the routing instance of each NE in the Epipe BGP multi-homing configuration. See To enable BGP on a routing instance for more information.

  2. Configure global-level BGP on each NE in the Epipe BGP multi-homing configuration. See To configure global-level BGP for more information. The following items are required:

    • Enable the L2 VPN parameter on:

      • the VPN tab of the BGP site form

      • the VPN tab of the BGP Peer Group form, which contains the peers that are involved in the BGP multi-homing

    • Create a peer group under BGP. This peer group is used to collectively define the peers involved in the Epipe BGP multi-homing configuration.

    • Create the required peers under the peer group. These peers are the NEs involved in the Epipe BGP multi-homing configuration.

    Note: For optimal processing while a BGP multi-homing site is activated or de-activated, or the system is rebooted, you should also:

    • Enable the L2 VPN parameter in the Rapid Update Address Family panel on the BGP site VPN tab.

    • Enable the Enable Rapid Withdrawal parameter on the BGP site Behavior tab.

2 

Choose Manage→Service→Services from the NFM-P main menu. The Manage Services form opens.

3 

Choose a VLL service and click Properties. The Epipe Service (Edit) form opens.

4 

On the service navigation tree, right-click on Epipe Service and choose Create Epipe Site, or right-click on a site and choose Properties. The Epipe Site (Create|Edit) form opens.

Note: You can see a list of all current Epipe multi-homing service sites by viewing the BGP Multi-homing tab on the service configuration form.

5 

Configure the general BGP parameters:

  1. Click on the BGP tab, then on the General tab, and enable the Enable BGP parameter.

  2. Configure the Route Distinguisher parameter in the RD panel. Enabling the Show Format checkbox displays a list of acceptable formats and value ranges.

    Note:

    An RD or RT configured under the BGP of an Epipe site cannot be removed as long as there is a multi-homing site configured that uses these and whose administration state is up.

  3. Configure the Import Route Target and Export Route Target parameters in the RT panel. Enabling the Show Format checkbox displays a list of acceptable formats and value ranges.

    You can also configure the Export Route Target to be the same as the Import Route Target by enabling the Same as Import checkbox.

6 

To configure multi-homing:

  1. Click on the Multi-homing tab.

  2. Click Create. The BGP Multi-homing Site (Create) form opens.

  3. Configure the required parameters.

    You cannot turn up a BGP multi-homing site without specifying a Multi-homing ID. In addition, the Multi-homing ID of the site can only be removed at a later time when the site is shutdown.

  4. Select a SAP for the BGP multi-homing in the Enable BGP Multi-homing to SAP panel.

    You cannot turn up a BGP multi-homing site without specifying a SAP. The SAP configured under this site can be part of an endpoint, but the only other object allowed in the endpoint is an ICB spoke-SDP. In addition, an assigned SAP can only be removed at a later time when the BGP multi-homing site is shutdown.

  5. Configure the parameters in the Timer panel.

    If you enable either the Use Node Level Boot Timer and/or Use Node Level Site Activation Timer parameters, then the associated Boot Timer (seconds) and/or Activation Timer (seconds) parameters are not configurable. These parameter values are inherited from the network element configuration.

    The Boot Timer (seconds) and Activation Timer (seconds) parameters can be configured for an NE on the BGP Multi-homing sub-tab under the Redundancy tab in the Network Element (Edit) form. See To modify NE properties for more information about how to change device properties.

    If you enable the Use Node Level Site-Down Minimum Timer parameter, the Site-Down Minimum Timer (seconds) parameter and Site-Down Minimum Timer Remaining (seconds) parameters are ignored and the values configured on the NE are used.

  6. Configure the Administrative State parameter in the States panel.

  7. Save the changes and close the form.

7 

Save the changes and close the forms.

End of steps