Cisco Cisco 3365 Mobility Services Engine Troubleshooting Guide
Contents
Introduction
Problem:
Devices Used:
Commands used:
Verify:
Via 3850 CLI:
Via MSE GUI
Troubleshoot:
Debugs:
Failure Scenario:
Success Scenario:
Related Cisco Support Community Discussions
Introduction
Network Mobility Services Protocol (NMSP) manages communication between the Mobility
Services Enginer(MSE) and the Wireless LAN Controller(WLC).
Services Enginer(MSE) and the Wireless LAN Controller(WLC).
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.
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.
Here we have used 3850 (IOS based WLC) & MSE for this post.
Problem:
Issues in establishing NMSP tunnel between 3850 & MSE.
Devices Used:
MSE: Virtual MSE 8.0.110 (MR1)
WLC: 3850 3.3.5SE
Prime Infrastructure(PI): 2.2.1
Since NMSP works over SSL(Secure Socket Layer), you have to configure MSE credential at
WLC. MSE use its MAC address & Key Hash, so WLC should be aware of these two parameters.
You can obtain this detail via MSE CLI as shown below
WLC. MSE use its MAC address & Key Hash, so WLC should be aware of these two parameters.
You can obtain this detail via MSE CLI as shown below
[root@robin ~]# cmdshell