CCIE Enterprise Wireless (v1.0) – Mobility Services engine – Basic VM install and configuration – Part 1

NMSP – high level overview

NMSP is a two-way protocol that can be run over a connection-oriented or a connectionless transport.Context-aware switches can use NMSP to communicate with one or more MSEs. NMSP is based upon a bidirectional system of requests and responses between the MSE and access controller. Now let’s see how to enable this communication between MSE & WLC. TCP port 16113

SOAP – high level overview

Simple Object Access Protocol (SOAP/XML)—The method of communication between the mobility services engine and WCS. This protocol is used to distribute configuration parameters to the wIPS service running on the mobility services engine. TCP port 443

Basic MSE install

Guidelines and Limitations

The information here is 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 different
  • You can use either manual or automatic failover
  • You can use either manual or automatic failback
  • Both the primary and secondary MSE must 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.

default login = root/password

Access the GUI of the MSE – https://mseip/mseui/

Note: https://mseip/mseui << will give you the error below. The correct URL is https://mseip/mseui/ the “/” is required at the end.

If you receive the message above SSH into the MSE and start the services:

Once the https service is up – log into MSE

Info from the MSE can be retrieved from the following command – getserverinfo

part 2 – adding MSE to Cisco Prime Infrastructure 3.7 can be found here

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.