Guest

Cisco Mobility Services Engine

MSE Software Release 7.2 High Availability Configuration and Deployment Guide

Cisco - MSE Software Release 7.2 High Availability Configuration and Deployment Guide

Document ID: 113462

Updated: Mar 13, 2012

   Print

Introduction

Cisco Mobility Services Engine (MSE) Software Release 7.2 adds High Availability (HA) support to physical and virtual appliances. This document provides configuration and deployment guidelines, as well as troubleshooting tips for those that add the MSE High Availability and run Context Aware Services and/or Adaptive wIPS to a Cisco Unified WLAN. The purpose of this document is to explain the guidelines for MSE High Availability and to provide HA deployment scenarios for MSE.

Note: This document does not provide configuration details for the MSE and associated components that do not pertain to MSE HA. This information is provided in other documents, and references are provided. See the Related Information

Related Cisco Support Community Discussions section for a list of documents about the configuration and design of Context Aware Mobility Services. Adaptive wIPS configuration is also not covered in this document.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

This document is not restricted to specific software and hardware versions.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Background Information

The MSE is a platform that is capable of running multiple related services. These services provide high-level service functionality. Therefore, consideration for HA is critical in maintaining the highest service confidence.

With HA enabled, every active MSE is backed up by another inactive instance. MSE HA introduces the health monitor in which it configures, manages, and monitors the high availability setup. A heartbeat is maintained between the primary and secondary MSE. The health monitor is responsible for setting up database, file replication, and monitoring the application. When the primary MSE fails and the secondary takes over, the virtual address of the primary MSE is switched transparently.

This setup (see figure 1) demonstrates a typical Cisco WLAN deployment that includes Cisco Mobility Services Engine (MSE) enabled for High Availability. HA support is available on MSE-3310, MSE-3350/3355, and Virtual Appliance on ESXi.

Figure 1. Deploying MSE in High Availability

mse-ha-config-dg-01.gif

Guidelines and Limitations

Here is information about the MSE HA architecture:

  • MSE Virtual Appliance supports only 1:1 HA.

  • One secondary MSE can support up to two primary MSEs. See the HA pairing matrix (figures 2 and 3).

  • HA supports Network Connected and Direct Connected.

  • Only MSE Layer-2 redundancy is supported. Both the health monitor IP and virtual IP must be on the same subnet and accessible from the Network Control System (NCS). Layer-3 redundancy is not supported.

  • Health monitor IP and virtual IP must be be different.

  • You can use either manual or automatic failover.

  • You can use either manual or automatic failback.

  • Both the primary and secondary MSE should be on the same software version.

  • Every active primary MSE is backed up by another inactive instance. The secondary MSE becomes active only after the failover procedure is initiated.

  • The failover procedure can be manual or automatic.

  • There is one software and database instance for each registered primary MSE.

Figure 2. MSE HA Support Pairing Matrix

mse-ha-config-dg-02.gif

Figure 3. MSE HA N:1 Pairing Matrix

mse-ha-config-dg-03.gif

HA Configuration Scenario for MSE Virtual Appliance (Network Connected)

This example shows the HA configuration for the MSE Virtual Appliance (VA) (see figure 4). For this scenario, these settings are configured:

  • Primary MSE VA:

    • Virtual IP – [10.10.10.11]

    • Health Monitor interface (Eth0) – [10.10.10.12]

  • Secondary MSE VA:

    • Virtual IP – [None]

    • Health Monitor interface (Eth0) – [10.10.10.13]

Note: An activation license (L-MSE-7.0-K9) is required per VA. This is required for HA configuration of the VA.

Figure 4. MSE Virtual Appliance in HA

mse-ha-config-dg-04.gif

Refer to Cisco documentation on MSE Virtual Appliance for more information.

Here are the general steps:

  1. Complete the VA installation for MSE and verify that all network settings are met.

    mse-ha-config-dg-05.gif

  2. Initial the Setup Wizard at first login.

    mse-ha-config-dg-06.gif

  3. Enter the required entries (host name, domain, etc.). Enter YES at the step to Configure High Availability.

    mse-ha-config-dg-07.gif

  4. Enter the following:

    1. Select Role – [1 for Primary].

    2. Health Monitor interface – [eth0]*

      *Network settings mapped to Network Adapter 1 (see sample screenshot)

      mse-ha-config-dg-08.gif

      mse-ha-config-dg-09.gif

  5. Select direct connect interface - [none].

    mse-ha-config-dg-10.gif

  6. Enter the following:

    1. Virtual IP address – [10.10.10.11]

    2. Network Mask – [255.255.255.0]

    3. Start MSE in recovery mode – [No]

      mse-ha-config-dg-11.gif

  7. Enter the following:

    1. Configure Eth0 - [Yes]

    2. Enter Eth0 IP address– [10.10.10.12]

    3. Network Mask – [255.255.255.0]

    4. Default Gateway – [10.10.10.1]

      mse-ha-config-dg-12.gif

  8. The second Ethernet interface (Eth1) is not used.

    Configure eth1 interface - [skip]

    mse-ha-config-dg-13.gif

  9. Continue through the Setup Wizard.

    1. It is critical to enable the NTP server in order to synchronize the clock.

    2. The preferred time zone is UTC.

      mse-ha-config-dg-14.gif

      mse-ha-config-dg-15.gif

      This summarizes the MSE Virtual Appliance Primary setup:

      -------BEGIN--------
      Role=1, Health Monitor Interface=eth0, Direct connect interface=none
      Virtual IP Address=10.10.10.11, Virtual IP Netmask=255.255.255.0
      Eth0 IP address=10.10.10.12, Eth0 network mask=255.0.0.0
      Default Gateway=10.10.10.1
      -------END--------
  10. Enter [YES] to confirm that all setup information is correct.

    mse-ha-config-dg-16.gif

  11. A reboot is recommended after set up.

    mse-ha-config-dg-17.gif

  12. After a reboot, start the MSE services with the /init.d/msed start command.

    mse-ha-config-dg-18.gif

  13. After all services have started, confirm MSE services are working properly with the getserverinfo command.

    Operation status must show Up.

    mse-ha-config-dg-19.gif

These steps are part of the setup for the secondary MSE VA:

  1. After new install, the initial login starts the Setup Wizard. Enter the following:

    1. Configure High Availability – [Yes]

    2. Select role – [2] which indicates Secondary

    3. Health Monitor Interface – [eth0] same as Primary

      mse-ha-config-dg-20.gif

  2. Enter the following:

    1. Direct Connection – [None]

    2. IP address eth0 – [10.10.10.13]

    3. Network mask – [255.255.255.0]

    4. Default Gateway – [10.10.10.1]

      mse-ha-config-dg-21.gif

  3. Configure eth1 interface – [Skip]

    mse-ha-config-dg-22.gif

  4. Set the Time Zone - [UTC]

    mse-ha-config-dg-23.gif

  5. Enable NTP server.

    mse-ha-config-dg-24.gif

  6. Complete the remaining steps of the Setup Wizard and confirm the setup information in order to save the configuration.

    mse-ha-config-dg-25.gif

  7. Reboot and start the services the same as the previous steps for the Primary MSE.

    mse-ha-config-dg-26.gif

The next steps show how to add the Primary and Secondary MSE VA to the NCS. Perform the normal process of adding an MSE to the NCS. See the configuration guide for help.

  1. From the NCS, go to Systems > Mobility Services and choose Mobility Services Engines.

    mse-ha-config-dg-27.gif

  2. From the pull-down, choose Add Mobility Services Engine. Then, click Go.

    mse-ha-config-dg-28.gif

  3. Follow the NCS configuration wizard for MSE. In this document's scenario, the values are:

    1. Enter Device Name – e.g. [MSE1]

    2. IP address – [10.10.10.12}

    3. Username and Password (per initial setup)

    4. Click Next.

      mse-ha-config-dg-29.gif

  4. Add all available licenses, then click Next.

    mse-ha-config-dg-30.gif

  5. Select MSE services, then click Next.

    mse-ha-config-dg-31.gif

  6. Enable tracking parameters, then click Next.

    mse-ha-config-dg-32.gif

  7. It is optional to assign maps and synchronize MSE services. Click Done to complete adding the MSE to the NCS.

    mse-ha-config-dg-33.gif

    mse-ha-config-dg-34.gif

The next screenshot shows that the Primary MSE VA has been added. Now, complete these steps in order to add the Secondary MSE VA:

  1. Locate the Secondary Server column, and click the link to configure.

    mse-ha-config-dg-35.gif

  2. Add the Secondary MSE VA using the configuration in this scenario:

    1. Secondary Device Name – [mse2]

    2. Secondary IP Address – [10.10.10.13]

    3. Secondary Password* – [default or from setup script]

    4. Failover Type* – [Automatic, or Manual]

    5. Fallback Type*

    6. Long Failover Wait*

    7. Click Save.

      *Click the information icon or refer to MSE documentation if required.

      mse-ha-config-dg-36.gif

  3. Click OK when the NCS prompts to pair up the two MSEs.

    mse-ha-config-dg-37.gif

    The NCS takes a few seconds to create the configuration.

    mse-ha-config-dg-38.gif

    The NCS will prompt if the Secondary MSE VA requires an activation license (L-MSE-7.0-K9).

    mse-ha-config-dg-39.gif

  4. Click OK and locate the License File to activate Secondary.

    mse-ha-config-dg-40.gif

  5. Once the Secondary MSE VA has been activated, click Save to complete the configuration.

    mse-ha-config-dg-41.gif

  6. Navigate to NCS > Mobility Services > Mobility Services Engine.

    The NCS displays this screen where the Secondary MSE appears in the column for Secondary Server:

    mse-ha-config-dg-42.gif

  7. In order to view the High Availability status, navigate to NCS > Services > High Availability.

    mse-ha-config-dg-43.gif

    In the HA status, you can see the current status and events by the MSE pair.

    mse-ha-config-dg-44.gif

    It can take a few minutes for the initial synchronization and data replication to be set up. The NCS provides the progress % indication until the HA pair is fully active as shown above.

    mse-ha-config-dg-45.gif

A new command introduced with MSE software release 7.2 relating to HA is gethainfo. This output shows the Primary and Secondary:

[root@mse1 ~]#gethainfo

Health Monitor is running. Retrieving HA related information

----------------------------------------------------
Base high availability configuration for this server
----------------------------------------------------

Server role: Primary
Health Monitor IP Address: 10.10.10.12
Virtual IP Address: 10.10.10.11
Version: 7.2.103.0
UDI: AIR-MSE-VA-K9:V01:mse1
Number of paired peers: 1

----------------------------
Peer configuration#: 1
----------------------------

Health Monitor IP Address 10.10.10.13
Virtual IP Address: 10.10.10.11
Version: 7.2.103.0
UDI: AIR-MSE-VA-K9:V01:mse2_666f2046-5699-11e1-b1b1-0050568901d9
Failover type: Manual
Failback type: Manual
Failover wait time (seconds): 10
Instance database name: mseos3s
Instance database port: 1624
Dataguard configuration name: dg_mse3
Primary database alias: mseop3s
Direct connect used: No
Heartbeat status: Up
Current state: PRIMARY_ACTIVE


[root@mse2 ~]#gethainfo

Health Monitor is running. Retrieving HA related information

----------------------------------------------------
Base high availability configuration for this server
----------------------------------------------------

Server role: Secondary
Health Monitor IP Address: 10.10.10.13
Virtual IP Address: Not Applicable for a secondary
Version: 7.2.103.0
UDI: AIR-MSE-VA-K9:V01:mse2
Number of paired peers: 1

----------------------------
Peer configuration#: 1
----------------------------

Health Monitor IP Address 10.10.10.12
Virtual IP Address: 10.10.10.11
Version: 7.2.103.0
UDI: AIR-MSE-VA-K9:V01:mse1_d5972642-5696-11e1-bd0c-0050568901d6
Failover type: Manual
Failback type: Manual
Failover wait time (seconds): 10
Instance database name: mseos3
Instance database port: 1524
Dataguard configuration name: dg_mse3
Primary database alias: mseop3s
Direct connect used: No
Heartbeat status: Up
Current state: SECONDARY_ACTIVE

HA Configuration with Direct Connected

Network Connected MSE HA uses the network, whereas the Direct Connect configuration facilitates use of a direct cable connection between the Primary and Secondary MSE servers. This can help reduce latencies in heartbeat response times, data replication and failure detection times. For this scenario, a primary physical MSE connects to a secondary MSE on interface eth1, as seen in figure 5. Note that Eth1 is used for the direct connect. An IP address for each interface is required.

Figure 5: MSE HA with direct connect

mse-ha-config-dg-46.gif

  1. Set up the Primary MSE.

    Summary of configuration from setup script:

    -------BEGIN--------
    Host name=mse3355-1
    Role=1 [Primary]
    Health Monitor Interface=eth0
    Direct connect interface=eth1
    Virtual IP Address=10.10.10.14
    Virtual IP Netmask=255.255.255.0
    Eth1 IP address=1.1.1.1
    Eth1 network mask=255.0.0.0
    Default Gateway =10.10.10.1
    -------END--------
  2. Set up the Secondary MSE.

    Summary of configuration from setup script:

    -------BEGIN--------
    Host name=mse3355-2
    Role=2 [Secondary]
    Health Monitor Interface=eth0
    Direct connect interface=eth1
    Eth0 IP Address 10.10.10.16
    Eth0 network mask=255.255.255.0
    Default Gateway=10.10.10.1
    Eth1 IP address=1.1.1.2, 
    Eth1 network mask=255.0.0.0
    -------END--------
  3. Add the Primary MSE to the NCS (see previous examples, or refer to configuration guide).

    mse-ha-config-dg-47.gif

  4. Set up the Secondary MSE from NCS > configure Secondary Server.

    1. Enter Secondary Device Name - [mse3355-2]

    2. Secondary IP address – [10.10.10.16]

    3. Complete remaining parameters and click Save.

    mse-ha-config-dg-48.gif

  5. Click OK to confirm pairing up the two MSEs.

    mse-ha-config-dg-49.gif

    The NCS takes a moment to add the Secondary Server configuration.

    mse-ha-config-dg-50.gif

  6. When completed, make any changes to the HA parameters. Click Save.

    mse-ha-config-dg-51.gif

  7. View the HA status for real-time progress of the new MSE HA pair.

    mse-ha-config-dg-52.gif

  8. From NCS > Services > Mobility Services > Mobility Services Engines, confirm that the MSE (direct connect) HA is added to the NCS.

    mse-ha-config-dg-53.gif

  9. From the console, confirmation can also be seen with the gethainfo command.

    Here is the Primary and Secondary output:

    [root@mse3355-1 ~]#gethainfo
    
    Health Monitor is running. Retrieving HA related information
    
    ----------------------------------------------------
    Base high availability configuration for this server
    ----------------------------------------------------
    
    Server role: Primary
    Health Monitor IP Address: 10.10.10.15
    Virtual IP Address: 10.10.10.14
    Version: 7.2.103.0
    UDI: AIR-MSE-3355-K9:V01:KQ37xx
    Number of paired peers: 1
    
    ----------------------------
    Peer configuration#: 1
    ----------------------------
    
    Health Monitor IP Address 10.10.10.16
    Virtual IP Address: 10.10.10.14
    Version: 7.2.103.0
    UDI: AIR-MSE-3355-K9:V01:KQ45xx
    Failover type: Automatic
    Failback type: Manual
    Failover wait time (seconds): 10
    Instance database name: mseos3s
    Instance database port: 1624
    Dataguard configuration name: dg_mse3
    Primary database alias: mseop3s
    Direct connect used: Yes
    Heartbeat status: Up
    Current state: PRIMARY_ACTIVE
    
    [root@mse3355-2 ~]#gethainfo
    
    Health Monitor is running. Retrieving HA related information
    
    ----------------------------------------------------
    Base high availability configuration for this server
    ----------------------------------------------------
    
    Server role: Secondary
    Health Monitor IP Address: 10.10.10.16
    Virtual IP Address: Not Applicable for a secondary
    Version: 7.2.103.0
    UDI: AIR-MSE-3355-K9:V01:KQ45xx
    Number of paired peers: 1
    
    ----------------------------
    Peer configuration#: 1
    ----------------------------
    
    Health Monitor IP Address 10.10.10.15
    Virtual IP Address: 10.10.10.14
    Version: 7.2.103.0
    UDI: AIR-MSE-3355-K9:V01:KQ37xx
    Failover type: Automatic
    Failback type: Manual
    Failover wait time (seconds): 10
    Instance database name: mseos3
    Instance database port: 1524
    Dataguard configuration name: dg_mse3
    Primary database alias: mseop3s
    Direct connect used: Yes
    Heartbeat status: Up
    Current state: SECONDARY_ACTIVE

HA Configuration Scenario for MSE Physical Appliance

Based on the pairing matrix, the maximum in the HA configuration is 2:1. This is reserved for the MSE-3355, which in secondary mode, can support a MSE-3310 and MSE-3350. Direct connect is not applicable in this scenario.

mse-ha-config-dg-54.gif

  1. Configure each of these MSEs to demonstrate 2:1 HA scenario:

    MSE-3310 (Primary1)
    Server role: Primary
    Health Monitor IP Address (Eth0): 10.10.10.17
    Virtual IP Address: 10.10.10.18
    Eth1 – Not Applicable
    
    MSE-3350 (Primary2)
    Server role: Primary
    Health Monitor IP Address: 10.10.10.22
    Virtual IP Address: 10.10.10.21
    Eth1 – Not Applicable
    
    MSE-3355 (Secondary)
    Server role: Secondary
    Health Monitor IP Address: 10.10.10.16
    Virtual IP Address: Not Applicable for a secondary
  2. After all MSEs are configured, add Primary1 and Primary2 to the NCS.

    mse-ha-config-dg-55.gif

  3. Click to configure Secondary Server (as shown in previous examples). Start with either one of the Primary MSEs.

    mse-ha-config-dg-56.gif

  4. Enter the parameters for the Secondary MSE:

    1. Secondary Device Name: for example, [mse-3355-2}

    2. Secondary IP address – [10.10.10.16]

    3. Complete the remaining parameters.

    4. Click Save.

      mse-ha-config-dg-57.gif

  5. Wait a brief moment for the first secondary entry to be configured.

    mse-ha-config-dg-58.gif

  6. Confirm that the Secondary Server is added for the first Primary MSE.

    mse-ha-config-dg-59.gif

  7. Repeat steps 3 to 6 for the second Primary MSE.

    mse-ha-config-dg-60.gif

  8. Finalize with HA parameters for the second Primary MSE.

    mse-ha-config-dg-61.gif

  9. Save the settings.

    mse-ha-config-dg-62.gif

  10. Check the status for progress for each of the Primary MSEs.

    mse-ha-config-dg-63.gif

  11. Confirm that both Primary1 and Primary2 MSEs are set up with a Secondary MSE.

    mse-ha-config-dg-64.gif

  12. From NCS > Services > Mobility Services, choose High Availability.

    mse-ha-config-dg-65.gif

    Note that 2:1 is confirmed for the MSE-3355 as a secondary for MSE-3310 and MSE-3350.

    mse-ha-config-dg-66.gif

    Here is a sample output of the HA setup from the console of all three MSEs when the gethainfo command is used:

    [root@mse3355-2 ~]#gethainfo
    
    Health Monitor is running. Retrieving HA related information
    
    ----------------------------------------------------
    Base high availability configuration for this server
    ----------------------------------------------------
    
    Server role: Secondary
    Health Monitor IP Address: 10.10.10.16
    Virtual IP Address: Not Applicable for a secondary
    Version: 7.2.103.0
    UDI: AIR-MSE-3355-K9:V01:KQ45xx
    Number of paired peers: 2
    
    ----------------------------
    Peer configuration#: 1
    ----------------------------
    
    Health Monitor IP Address 10.10.10.22
    Virtual IP Address: 10.10.10.21
    Version: 7.2.103.0
    UDI: AIR-MSE-3350-K9:V01:MXQ839xx
    Failover type: Manual
    Failback type: Manual
    Failover wait time (seconds): 10
    Instance database name: mseos3
    Instance database port: 1524
    Dataguard configuration name: dg_mse3
    Primary database alias: mseop3s
    Direct connect used: No
    Heartbeat status: Up
    Current state: SECONDARY_ACTIVE
    
    
    ----------------------------
    Peer configuration#: 2
    ----------------------------
    
    Health Monitor IP Address 10.10.10.17
    Virtual IP Address: 10.10.10.18
    Version: 7.2.103.0
    UDI: AIR-MSE-3310-K9:V01:FTX140xx
    Failover type: Manual
    Failback type: Manual
    Failover wait time (seconds): 10
    Instance database name: mseos4
    Instance database port: 1525
    Dataguard configuration name: dg_mse4
    Primary database alias: mseop4s
    Direct connect used: No
    Heartbeat status: Up
    Current state: SECONDARY_ACTIVE

    Final validation for HA in the NCS shows the status as fully Active for both the MSE-3310 and MSE-3350.

    mse-ha-config-dg-67.gif

    mse-ha-config-dg-68.gif

Basic Troubleshooting of MSE HA

When adding the Secondary MSE, you can see a prompt such as this:

mse-ha-config-dg-69.gif

It is possible there was an issue during the setup script.

  • Run the getserverinfo command to check for proper network settings.

  • It is also possible that the services have not started. Run the /init.d/msed start command.

  • Run through the setup script again if required (/mse/setup/setup.sh) and save at the end.

The Virtual Appliance for MSE also requires an activation license (L-MSE-7.0-K9). Otherwise, the NCS prompts when adding the Secondary MSE VA. Obtain and add the activation license for the MSE VA.

mse-ha-config-dg-70.gif

If switching HA role on the MSE, make sure that the services are fully stopped. Therefore, stop services with the /init.d/msed stop command, then run the setup script again (/mse/setup/setup.sh).

mse-ha-config-dg-71.gif

Use the gethainfo command to Get High Availability Information on the MSE. This provides useful information in troubleshooting or monitoring HA status and changes.

[root@mse3355-2 ~]#gethainfo

Health Monitor is running. Retrieving HA related information

----------------------------------------------------
Base high availability configuration for this server
----------------------------------------------------

Server role: Secondary
Health Monitor IP Address: 10.10.10.16
Virtual IP Address: Not Applicable for a secondary
Version: 7.2.103.0
UDI: AIR-MSE-3355-K9:V01:KQ45xx
Number of paired peers: 2

----------------------------
Peer configuration#: 1
----------------------------

Health Monitor IP Address 10.10.10.22
Virtual IP Address: 10.10.10.21
Version: 7.2.103.0
UDI: AIR-MSE-3350-K9:V01:MXQ839xx
Failover type: Manual
Failback type: Manual
Failover wait time (seconds): 10
Instance database name: mseos3
Instance database port: 1524
Dataguard configuration name: dg_mse3
Primary database alias: mseop3s
Direct connect used: No
Heartbeat status: Up
Current state: SECONDARY_ACTIVE


----------------------------
Peer configuration#: 2
----------------------------

Health Monitor IP Address 10.10.10.17
Virtual IP Address: 10.10.10.18
Version: 7.2.103.0
UDI: AIR-MSE-3310-K9:V01:FTX140xx
Failover type: Manual
Failback type: Manual
Failover wait time (seconds): 10
Instance database name: mseos4
Instance database port: 1525
Dataguard configuration name: dg_mse4
Primary database alias: mseop4s
Direct connect used: No
Heartbeat status: Up
Current state: SECONDARY_ACTIVE

In addition, the NCS High Availability View is a great management tool in order to get visibility to the HA setup for MSE.

mse-ha-config-dg-72.gif

Related Information

Updated: Mar 13, 2012
Document ID: 113462