Avaya Aura Session Border Controller High Availability Configuration. Abstract

Transcription

1 Avaya Aura Session Border Controller High Availability Configuration Abstract These Application Notes detail the requirements and configuration steps necessary to implement a High Availability (HA) 1+1, Active / Standby, solution for the Avaya Aura Session Border Controller. 1 of 21

2 Contents: 1. Introduction Reference Configuration Equipment and Software Validated Pre-requisite checklist Cluster Configuration Cluster Virtual Router Redundancy Protocol (VRRP) Configuration Configure vinterfaces Configure vx0 and vx2 routing vx0 routing vx2 routing Configure vx2 kernel-filter allow-rule deny-rule Master Services Configuration Link Heartbeat Configuration (optional) System Initialisation for High Availability Avaya Aura Session Border Controller box Avaya Aura Session Border Controller box Verification Steps Avaya Aura Session Border Controller GUI Avaya Aura Session Border Controller CLI Initiate Avaya Aura Session Border Controller system failover Conclusion Additional References Change History of 21

3 1. Introduction The Avaya Aura Session Border Controller (AA-SBC) is a Virtual Machine that is installed on the Avaya Aura System Platform and is based on an OEM version of the Acme Packet Net-Net OS-E Session Border Controller (Net-Net 2600). These Application Notes detail the requirements and configuration steps necessary to implement a High Availability (HA) 1+1, Active / Standby, solution for the Avaya Aura Session Border Controller using native functionality. Note, the Avaya Aura Session Border Controller HA option uses native functionality and not the Avaya Aura System Platform HA mechanism Reference Configuration Figure 1: Interface connections (physical) for AA-SBC High Availability Server Physical Interface Port 1, eth0 Avaya Aura Session Border Controller Virtual Interface eth0 Port 2, eth1 Port 3, eth2 Port 4, eth3 eth1 eth2 Function Shared Management and AASBC Private Interface Avaya Services port AA-SBC HA intra-cluster link AA-SBC Public Interface Table 1: Mapping between physical and virtual interfaces 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Software Avaya Common server, HP ProLiant DL360 G7* Avaya Aura System Platform version Avaya Aura Session Border Controller version of 21

4 *Note: this configuration is also applicable to the Dell PowerEdge R610 and IBM System x3550 M2 servers. 3. Pre-requisite checklist Check Requirement Ensure identical version of Avaya Aura System Platform is installed and running on both servers. Ensure identical version of Avaya Aura Session Border Controller is installed and running on both servers, each installed with the same configuration options, e.g. the same Service Provider configuration. Note the identifier (AA-SBC eth0 MAC address) of box2: Log in to the Avaya Aura Session Border Controller box2 GUI using an account that has admin privileges, e.g. sbcadmin or init Select the Configuration tab In the left-hand pane, expand cluster by clicking on the + symbol and then select box <hostname>. Make a note of the box2 identifier. Where applicable, take a backup of the currently running Avaya Aura Session Border Controller before making any changes. Connect a Cat5 Ethernet cross-over cable between port 3 of the servers (eth2) for the AA-SBC intra-cluster link, see Reference Configuration. Additional IP addresses for the Avaya Aura Session Border Controller High Availability solution are required as follows: o Without arp-heartbeat* defined on the AA-SBC public interface 3 x private mgmt addresses (box1, box2 and shared cluster) 1 x intra-cluster link address, e.g. use standard linklocal address, x.x 1 x private sip / media address 1 x public sip / media addresses (shared cluster) With arp-heartbeat* defined on the AA-SBC public interface 3 x private mgmt addresses (box1, box2 and shared cluster) 1 x intra-cluster link address, e.g. use standard linklocal address, x.x 1 x private sip / media address 3 x public sip / media addresses (box1, box2 and shared cluster) o *arp-heartbeat can be used to detect link failures in order to trigger a failover. This requires an IP address on the physical interface of each applicable link of each server. See Link Heartbeat Configuration (optional) for further information. 4 of 21

5 4. Cluster Configuration The cluster configuration detailed below should be applied via box1 s Avaya Aura Session Border Controller s GUI interface. This can be accessed via the spanner on box1 s Avaya Aura System Platform webconsole or manually via a web browser using the following link: Box1 Mgmt IP address> Figure 2: Avaya Aura System Platform webconsole, spanner for sbc highlighted 1. Log in to box1 s Avaya Aura Session Border Controller GUI using an account that has admin privileges, e.g. sbcadmin or init. Select the Configuration tab In the left-hand pane, select cluster. 4. Set share-signaling-entries and mirror-media-streams to true on the Configure cluster page. 5. Click the Set button at the top of the page. 5 of 21

6 6. In the left-hand pane, navigate to ip inside by expanding cluster, box <hostname> and then interface eth0 by clicking on the + symbols. 7. Delete the sip and media-ports objects. 8. Click the Set button at the top of the page. 9. In the left-hand pane, navigate to ip outside by expanding cluster, box <hostname> and then interface eth2 by clicking on the + symbols. 10. Delete the sip, media-ports, kernel filter and routing objects. Note, if arp-heartbeat isn t to be configured on the Public Interface, ip outside should be deleted. 11. Click the Set button at the top of the page. 12. Click on Add interface for interface and select eth1 for name and then click on the Create button. 13. Click the Set button at the top of the page. 14. Click on Add ip for ip, set name to intra-cluster link and assign a static ip-address (e.g. use address from the standard link-local address range, e.g /24) and then click on the Create button. 15. Click the Set button at the top of the page. 16. Configure ssh, ntp-server, bootp-server, icmp, vrrp-advertisements and messaging with default values. 17. Click the Set button at the top of the page. 18. In the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 19. Click OK twice, first to update and then to save the live configuration. 6 of 21

7 20. With the Configuration tab selected, in the left-hand pane, expand cluster and select box <hostname>. Then in the central pane, click on the Copy button at the top of the page. This will create configuration for a second box in the cluster. 7 of 21

8 21. Modify all the new box information to align it with the configuration for the second box. Make sure that the box number is 2 and change the parameter values* as appropriate for box2, i.e. as detailed in the table below. Parameter Value Number Hostname Name Identifier ntp-client \ server cli \ prompt interface eth0 \ ip-address 2 <hostname of box2> <name of box2> <identifier of box2> <as defined for box2> <name of box2> <box2 management IP address, must remain the same as configured for box2 installation> <box2 trap-target IP address> <box2 IP address for intra-cluster link, e.g /24> <box2 IP address for outside interface, required for arp-heartbeat function> interface eth0 \ ip inside \ snmp interface eth1 \ ip-address interface eth2 \ ip-address Changed to box2 value? *Note: after updating each of the values in the table below, ensure that the Set button at the top of each page is selected before modifying another value. Table 2: Cluster box2 configuration values 22. Once all values have been updated, in the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 23. Click OK twice, first to update and then to save the live configuration. 5. Cluster Virtual Router Redundancy Protocol (VRRP) Configuration The Virtual Router Redundancy Protocol (VRRP) provides redundancy of IP interfaces within an AA-SBC cluster. It also provides redundancy of master services within a cluster. Each master service, including directory, database, and accounting, can be configured with a list of locations (box numbers within the cluster). The first location, such as box 1, is the primary; the second location (box 2) takes over if the primary fails Configure vinterfaces 1. Log in to box1 s Avaya Aura Session Border Controller GUI using an account that has admin privileges, e.g. sbcadmin or init. Select the Configuration tab. In the left-hand pane, select cluster. In the central pane, click on Configure for vrrp. For sip-dead-groups, select Edit sip-dead-groups and set to 1. Click the Set button at the top of the page. 8 of 21

9 7. Click on Add vinterface for vinterface and add vinterfaces* as follows: vinterface group host-interface name ip vx0 1 cluster\box 1\interface eth0 cluster\box 2\interface eth0 virtual inside <static IP address> Preempt (advanced) true vx2 1 cluster\box 1\interface eth2 cluster\box 2\interface eth2 virtual outside <static IP address> true vx10 2 cluster\box 1\interface eth0 cluster\box 2\interface eth0 cluster management <static IP address> true *Note: ensure that the Set button at the top of each page is selected before modifying another value. **Note: see below for details on configuring these objects. Table 3: vinterfaces configuration 8. Once all vinterfaces have been defined, in the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 9 of 21 object sip media-ports routing** sip media-ports routing** kernel-filter** ssh web

10 5.2. Configure vx0 and vx2 routing vx0 routing 1. In the left-hand pane, navigate to ip virtual inside by expanding cluster, vrrp and vinterface vx0 by clicking on the + symbols. In the central pane, click on Configure for routing. Select Add route. Set route-name, e.g. Default-sip-media. Select default destination type. Set IP address for gateway. Click on the Create button. Click the Set button. In the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 10. Click OK twice, first to update and then to save the live configuration vx2 routing 1. In the left-hand pane, navigate to ip virtual outside by expanding cluster, vrrp and vinterface vx2 by clicking on the + symbols. In the central pane, click on Configure for routing. Select Add route. Set route-name, e.g. external-sip-media-1 Select host destination type. Set destination address. 10 of 21

11 7. Set IP address for gateway. 8. Click on the Create button. 9. Click the Set button. 10. In the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 11. Click OK twice, first to update and then to save the live configuration Configure vx2 kernel-filter allow-rule 1. In the left-hand pane, navigate to ip virtual outside by expanding cluster, vrrp and vinterface vx2 by clicking on the + symbols. In the central pane, click on Configure for kernel-filter Select Add allow-rule. 4. Set name, e.g. allow-sip-udp-from-peer Set source-address/mask, i.e. this needs to match the Telco source network. 6. Click on the Create button. 7. Set destination-port, e.g Select protocol, e.g. udp. 9. Click the Set button. 10. In the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 11. Click OK twice, first to update and then to save the live configuration deny-rule 11 of 21

12 1. In the left-hand pane, navigate to ip virtual outside by expanding cluster, vrrp and vinterface vx2 by clicking on the + symbols. 2. In the central pane, click on Configure for kernel-filter. 3. Select Add deny-rule. 4. Set name, e.g. deny-all-sip. 5. Set source-address/mask to /0. 6. Click on the Create button. 7. Set destination-port, e.g Set protocol to all. 9. Click the Set button. 10. In the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 11. Click OK twice, first to update and then to save the live configuration. 6. Master Services Configuration In addition to their regular functions, Master Services also handle cluster-wide distribution of state information. For example, the Cluster Master pushes out configuration changes to each cluster member and manages the config files. It is therefore important to only make changes to the configuration on the box that is the current Cluster Master; otherwise, changes made to a local box config will be lost at the next reboot. The preempt property should be set to true (advanced property) for the Database service. This property ensures that, if the Database service fails over, and then the original box comes back up, the Database will move back to the original box, keeping as many database records together on one box as possible. Note, if one service in a group is set to preempt, then all of them should. 1. Master Services should be configured as detailed in the following table. master-service group host-box preempt (advanced 12 of 21

13 cluster-master 2 call-failover 3 Accounting 4 Database 5 Sampling 5 cluster\box 2 cluster\box 1 cluster\box 2 cluster\box 1 cluster\box 2 cluster\box 1 cluster\box 2 cluster\box 1 cluster\box 2 cluster\box 1 property) False False False True True Table 4: Master Services configuration 2. Log in to box1 s Avaya Aura Session Border Controller GUI using an account that has admin privileges, e.g. sbcadmin or init. Select the Services tab In the left-hand pane, select master-services. 5. In the central pane, click on Configure for each of the required Master Services in turn that hasn t yet been enabled. Select Edit host-box Tick the boxes for cluster\box 1 and cluster\box 2. Click the up arrow of cluster\box 2 to make it the preferred server. If preempt needs to be set, click on the Show advanced button at the top of the page and set preempt true. 10. Click the Set button. 11. In the left-hand pane, select Configuration from the top menu bar and click on Update and save configuration. 12. Click OK twice, first to update and then to save the live configuration. 13 of 21

14 7. Link Heartbeat Configuration (optional) In previous releases, in a VRRP implementation, the AA-SBC would not always receive a link down event when the AA-SBC lost connectivity to the network. A new configuration object, arp-heartbeat, has been introduced in order to detect these link down events and trigger a failover. When arp-heartbeat is configured on an interface, in addition to the AA-SBC sending periodic VRRP advertisements across the messaging interface, it will also send ARP requests across the interface to another system on the same local network. If the ARP probe times out, the master AA-SBC knows that its connection to the network is broken. It then transitions into a link-down state and notifies the backup AASBC to take over. While in the link-down state, the AA-SBC periodically sends an ARP probe to continue checking the link. The AA-SBC stays in this state until it gets an ARP response. The AA-SBC is then able to change back to the original box if required. Note, arp-heartbeat should only be configured on physical interfaces with an assigned IP address, i.e. must be configured on each physical interface that requires link down detection. 1. Log in to box1 s Avaya Aura Session Border Controller GUI using an account that has admin privileges, e.g. sbcadmin or init. Select the Configuration tab In the left-hand pane, expand cluster by clicking on the + symbol and then select box <hostname>. In the left-hand pane, navigate to ip <name> by expanding cluster, box <hostname> and then interface <interface name> by clicking on the + symbols. In the central pane, click on Configure for arp-heartbeat. 14 of 21

15 6. Configure heartbeat-system with a local IP address for a system on the subnet to query with arps. 7. Click the Set button. 8. In the left-hand pane, select Configuration from the top menu bar and click on Update and save 9. configuration. Click OK twice, first to update and then to save the live configuration. 8. System Initialisation for High Availability Avaya Aura Session Border Controller box1 1. Log in to box1 s Avaya Aura Session Border Controller GUI using an account that has admin privileges, e.g. sbcadmin or init. Select the Tools tab In the left-hand menu, select Download saved configuration file to save the configuration of box Avaya Aura Session Border Controller box2 1. Log in to box2 s Avaya Aura Session Border Controller GUI using an account that has admin privileges, e.g. sbcadmin or init. 2. Select the Tools tab. 3. In the left-hand menu, select Upload file and in the central pane Browse for the configuration File previously downloaded from box1. 4. Set Destination Path to /cxc. 5. Select Overwrite Existing File and set Destination Name to cxc.cfg. 15 of 21

16 Click the Update button to upload box1 s configuration file to box2. Select the Actions tab. In the left-hand menu, select restart and select operation mode cold from the drop down list. Click the Invoke button and then wait for box2 to reboot (approximately 1 minute). When box2 returns it should be in vrrp-state: Backup. 9. Verification Steps The state of the servers can be verified on either the Avaya Aura Session Border Controller s GUI Home tab or via the CLI Avaya Aura Session Border Controller GUI 1. Log in to the Avaya Aura Session Border Controller GUI using the cluster management address 2. Select the Home tab. 3. Select Cluster from the Get summary for drop down list. 4. At the bottom of the page click on active-vrrp-interfaces Avaya Aura Session Border Controller CLI 1. Log in to each of the box s Avaya Aura Session Border Controller CLI. 2. Enter command: show vrrp vrrp-state will indicate whether the box is Master or Backup for each vx interface. 3. Enter command: show interfaces op-state will be up for the box that is the Master. 4. Enter command: show groups active state will be true for the box that is the Master Initiate Avaya Aura Session Border Controller system failover To test the configuration, a failover to the Standby server can be initiated by stopping the Active server. The following steps show how this can be done. 16 of 21

17 1. Verify that the vrrp-state of box1 is Master by using the Avaya Aura Session Border Controller GUI or CLI as described in the previous sections. 2. Log in to the Avaya Aura System Platform webconsole for the Cluster Master using an account that has admin privileges, e.g. admin. 3. Click on sbc in the Manage page. 4. Click on the Stop button and wait for the State to change to Stopped. 5. Log in to the Avaya Aura Session Border Controller GUI using the cluster management address. 6. Select the Home tab. 7. Select Cluster from the Get summary for drop down list. 8. At the bottom of the page click on active-vrrp-interfaces, verify that box2 is now Master for each vrrp-interface. 17 of 21

18 9. Return to the Avaya Aura System Platform webconsole for the Stopped Avaya Aura Session Border Controller. 10. Restart this Avaya Aura Session Border Controller by clicking on the Start button. 11. Wait for the State and the Application State to change to Running. 12. Log in to the Avaya Aura Session Border Controller GUI using the cluster management address. 13. Select the Home tab. 14. Select Cluster from the Get summary for drop down list. 15. At the bottom of the page click on active-vrrp-interfaces, verify that box1 is now Master for each vrrp-interface. 18 of 21

19 10. Conclusion These Application Notes demonstrate how the Avaya Aura Session Border Controller can be configured for a High Availability (HA) 1+1, Active / Standby, solution. Once an Avaya Aura Session Border Controller (AA-SBC) HA configuration has been implemented, changes to any of the AA-SBC s IP addresses must only be done on the AA-SBC Cluster Master. If changes are made to the AA-SBC Cluster Standby, these changes will be lost when the AA-SBC Cluster Master synchronises its configuration. Use the cluster management address for accessing the AASBC s CLI or GUI to ensure changes are made on the AA-SBC Cluster Master. If link failure detection is required, arp-heartbeat needs to be configured on each applicable interface of each server, see Link Heartbeat Configuration. 11.Additional References 1. Avaya Aura Session Border Controller Release Notes 2. Avaya Aura Session Border Controller System Administration 12. Change History I Dat e 22/ 12/ / 12/ / Auth or Colin Kidg ell Reason Colin Kidg ell Updated following Toolkit review. Colin Updated for AA-SBC version and Updated following review in AA-SBC status meeting. Document approved with comments. 19 of 21

20 0 0 12/ / 10/ / 08/ Kidg ell reformatted. Rob Geor ge Updated sections on wizard design and manual configuration issues. Rob Geor ge Initial draft. 20 of 21

21 Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya DevConnect Program at 21 of 21