Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Problems with asociation of MSE with WCS

Hi everyone,

Had some problems with the association of the MSE with the WCS.
Licenses already loaded context aware and WCS-PLUS
The  two machines are within the same network segment WCS (10.16.0.28) and  MSE (10.16.0.89), including IP connectivity exists and which tests ping.
When I do a / etc / init.d / mse status throws me the following error:
root@xxxxx# /etc/init.d/msed status
STATUS:
MSE Platform is up, getting the status
Unable to get MSE status. Error: (400)Bad Request
Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Retrying status fetch -
Unable to get MSE status.       Unabled to get MSE status


But when I start the service tells me that MSE is running successfully.
Realize  a packet capture with tcpdump command on the MSE to see if the packets  of requests came from the WCS to the MSE the result was as follows:

12:27:54.026705 IP wcs-spp.bcch.local.nati-vi-server > 10.16.0.89.https: . ack 1 win 64240
12:27:54.026881 IP wcs-spp.bcch.local.nati-vi-server > 10.16.0.89.https: F 1:1(0) ack 1 win 64240
12:27:54.027330 IP 10.16.0.89.https > wcs-spp.bcch.local.nati-vi-server: P 1:8(7) ack 2 win 5840
12:27:54.027345 IP 10.16.0.89.https > wcs-spp.bcch.local.nati-vi-server: F 8:8(0) ack 2 win 5840
12:27:54.027508 IP wcs-spp.bcch.local.nati-vi-server > 10.16.0.89.https: R 2:2(0) ack 8 win 0
12:27:54.027814 IP wcs-spp.bcch.local.nati-vi-server > 10.16.0.89.https: R 2192493572:2192493572(0) win 0
12:27:54.031003 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: S 2838571124:2838571124(0) win 64240 <mss 1460,nop,nop,sackOK>
12:27:54.031010 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: S 3559864122:3559864122(0) ack 2838571125 win 5840 <mss 1460,nop,nop,sackOK>
12:27:54.031171 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: . ack 1 win 64240
12:27:54.049547 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 1:101(100) ack 1 win 64240
12:27:54.049552 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: . ack 101 win 5840
12:27:54.049793 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 1:845(844) ack 101 win 5840
12:27:54.054284 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 101:368(267) ack 845 win 63396
12:27:54.054289 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 368:374(6) ack 845 win 63396
12:27:54.054291 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 374:411(37) ack 845 win 63396
12:27:54.078083 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: . ack 411 win 6432
12:27:54.078178 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 845:851(6) ack 411 win 6432
12:27:54.078261 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 851:888(37) ack 411 win 6432
12:27:54.078619 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: . ack 888 win 63353
12:27:54.080546 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 411:699(288) ack 888 win 63353
12:27:54.080550 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 699:944(245) ack 888 win 63353
12:27:54.080699 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: . ack 944 win 8576
12:28:54.033660 IP wcs-spp.bcch.local.3365 > 10.16.0.89.https: S 2734209245:2734209245(0) win 64240 <mss 1460,nop,nop,sackOK>
12:28:54.033676 IP 10.16.0.89.https > wcs-spp.bcch.local.3365: S 3614074422:3614074422(0) ack 2734209246 win 5840 <mss 1460,nop,nop,sackOK>
12:28:54.033863 IP wcs-spp.bcch.local.3365 > 10.16.0.89.https: . ack 1 win 64240
12:28:54.033956 IP wcs-spp.bcch.local.3365 > 10.16.0.89.https: F 1:1(0) ack 1 win 64240
12:28:54.034175 IP 10.16.0.89.https > wcs-spp.bcch.local.3365: P 1:8(7) ack 2 win 5840
12:28:54.034192 IP 10.16.0.89.https > wcs-spp.bcch.local.3365: F 8:8(0) ack 2 win 5840
12:28:54.034472 IP wcs-spp.bcch.local.3365 > 10.16.0.89.https: R 2:2(0) ack 8 win 0
12:28:54.034481 IP wcs-spp.bcch.local.3365 > 10.16.0.89.https: R 2734209247:2734209247(0) win 0
12:28:54.970620 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 888:1021(133) ack 944 win 8576
12:28:54.970645 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 1021:1257(236) ack 944 win 8576
12:28:54.970789 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 1257:1283(26) ack 944 win 8576
12:28:54.970925 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: . ack 1257 win 62984
12:28:55.126506 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: . ack 1283 win 62958
12:28:56.408337 arp who-has wcs-spp.bcch.local tell srvdc-02.bcch.local
12:29:04.985283 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: P 944:967(23) ack 1283 win 62958
12:29:04.985292 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: F 967:967(0) ack 1283 win 62958
12:29:04.985431 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: P 1283:1306(23) ack 968 win 8576
12:29:04.985445 IP 10.16.0.89.https > wcs-spp.bcch.local.3364: F 1306:1306(0) ack 968 win 8576
12:29:04.985984 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: R 968:968(0) ack 1306 win 0
12:29:04.985994 IP wcs-spp.bcch.local.3364 > 10.16.0.89.https: R 2838572092:2838572092(0) win 0
12:30:46.539495 IP wcs-spp.bcch.local.3368 > 10.16.0.89.http: S 1536782747:1536782747(0) win 64240 <mss 1460,nop,nop,sackOK>
12:30:46.539524 IP 10.16.0.89.http > wcs-spp.bcch.local.3368: S 3729094158:3729094158(0) ack 1536782748 win 5840 <mss 1460,nop,nop,sackOK>
12:30:46.539697 IP wcs-spp.bcch.local.3368 > 10.16.0.89.http: . ack 1 win 64240
12:30:46.539881 IP wcs-spp.bcch.local.3368 > 10.16.0.89.http: F 1:1(0) ack 1 win 64240
12:30:46.540753 IP 10.16.0.89.http > wcs-spp.bcch.local.3368: . ack 2 win 5840
12:30:46.543466 IP wcs-spp.bcch.local.3369 > 10.16.0.89.http: S 458572270:458572270(0) win 64240 <mss 1460,nop,nop,sackOK>
12:30:46.543472 IP 10.16.0.89.http > wcs-spp.bcch.local.3369: S 3733471863:3733471863(0) ack 458572271 win 5840 <mss 1460,nop,nop,sackOK>
12:30:46.543628 IP wcs-spp.bcch.local.3369 > 10.16.0.89.http: . ack 1 win 64240
12:30:46.543904 IP wcs-spp.bcch.local.3369 > 10.16.0.89.http: P 1:268(267) ack 1 win 64240
12:30:46.543909 IP 10.16.0.89.http > wcs-spp.bcch.local.3369: . ack 268 win 6432
12:30:46.543911 IP wcs-spp.bcch.local.3369 > 10.16.0.89.http: P 268:492(224) ack 1 win 64240
12:30:46.543914 IP 10.16.0.89.http > wcs-spp.bcch.local.3369: . ack 492 win 7504
12:30:46.551367 IP 10.16.0.89.http > wcs-spp.bcch.local.3368: F 1:1(0) ack 2 win 5840
12:30:46.551519 IP wcs-spp.bcch.local.3368 > 10.16.0.89.http: . ack 2 win 64240

As you can see the WCS about consulting, but the MSE is not responding.
Within the network there is any kind of filter.
I tried uninstalling the MSE service again and again but always with the same results.
When  you configure the name, IP address and password WCS (which I've let the  default and also changed) the message I delivered the browser (I use  Internet Explorer 7, Mozilla and Google Chrome) is as follows:

"No response from server. it may be unreachable, or server is down or HTTPS connection to server failed."

I thank showing me what else to do because my client needs this solution  thank you very much.

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Problems with asociation of MSE with WCS

Hi ,

For some pointers:

1)Please can you mention the WCS/MSE versions, we would need to have version compatibility between WCS/MSE:

http://www.cisco.com/en/US/partner/docs/wireless/wcs/release/notes/WCS_RN7_0.html#wp138889

2)What do we have from "getserverinfo" from MSE cli

3)As the output you included has HTTPS communication, did you also verify with using HTTP.

4)If IP connectivity exists and you can ping between WCS-MSE, you will need to verify if you have the right WCS-MSE communication password configured.

Including document links which may help you:

http://www.cisco.com/en/US/partner/products/ps9742/products_tech_note09186a00809d1529.shtml#add-mse

http://www.cisco.com/en/US/partner/docs/wireless/mse/3350/7.0/CAS/configuration/guide/msecg_ch2_CAS.html#wp1011511

If MSE is detected as unreachable from the WCS perspective, possible reasons can be these:

    *The API login credentials in WCS are configured incorrectly. The appliance has two sets of credentials: one is for the appliance shell interface and another for the API credentials. WCS needs the API credentials when it adds MSE. Refer to Appendix A of this document.
    * Route and Firewall connectivity rules block connectivity between WCS and MSE. Refer to the “Verify Network Connectivity” section in this document.
    *The WCS Background task “Mobility Service Status” has been disabled. Enable it in WCS through Administration > Background Tasks > Other Background Tasks > Mobility Service Status .
    * The MSE Service Context Aware is enabled and up from the MSE CLI.
    * In rare situations, HTTPS can have a connectivity issue. You can enable the HTTP option under MSE General Properties in WCS. Refer to the “WCS/MSE Communication” section of this document for details.
    * MSE has crashed. On MSE, CLI “getserverinfo” cannot return an output. Collect all logs under/opt/mse/logs directory and contact Cisco TAC.

HTH,

Alex

3 REPLIES
Cisco Employee

Re: Problems with asociation of MSE with WCS

Hi ,

For some pointers:

1)Please can you mention the WCS/MSE versions, we would need to have version compatibility between WCS/MSE:

http://www.cisco.com/en/US/partner/docs/wireless/wcs/release/notes/WCS_RN7_0.html#wp138889

2)What do we have from "getserverinfo" from MSE cli

3)As the output you included has HTTPS communication, did you also verify with using HTTP.

4)If IP connectivity exists and you can ping between WCS-MSE, you will need to verify if you have the right WCS-MSE communication password configured.

Including document links which may help you:

http://www.cisco.com/en/US/partner/products/ps9742/products_tech_note09186a00809d1529.shtml#add-mse

http://www.cisco.com/en/US/partner/docs/wireless/mse/3350/7.0/CAS/configuration/guide/msecg_ch2_CAS.html#wp1011511

If MSE is detected as unreachable from the WCS perspective, possible reasons can be these:

    *The API login credentials in WCS are configured incorrectly. The appliance has two sets of credentials: one is for the appliance shell interface and another for the API credentials. WCS needs the API credentials when it adds MSE. Refer to Appendix A of this document.
    * Route and Firewall connectivity rules block connectivity between WCS and MSE. Refer to the “Verify Network Connectivity” section in this document.
    *The WCS Background task “Mobility Service Status” has been disabled. Enable it in WCS through Administration > Background Tasks > Other Background Tasks > Mobility Service Status .
    * The MSE Service Context Aware is enabled and up from the MSE CLI.
    * In rare situations, HTTPS can have a connectivity issue. You can enable the HTTP option under MSE General Properties in WCS. Refer to the “WCS/MSE Communication” section of this document for details.
    * MSE has crashed. On MSE, CLI “getserverinfo” cannot return an output. Collect all logs under/opt/mse/logs directory and contact Cisco TAC.

HTH,

Alex

New Member

Re: Problems with asociation of MSE with WCS

Thank for the answer,

The problem was the password of wcs and MSE,  so am changed this password when configure the MSE and a put the same password in the WCS configuration and also it does't work, so am changed the password to default in the WCS and MSE and work. So be carefull when you change this password may be can work but in my case does't work.

good luck and thank

New Member

Problems with asociation of MSE with WCS

I have a similar issue my MSE Cli responds that Starting MSE Platform, waiting to check the status. about 15 times and give the final message 'FAiled to get the status'.

I stopped the msed service and restarted still the same message. I had rebooted the server MSE and still the same results.

Any idea that you could suggest.

Thanks

3522
Views
5
Helpful
3
Replies
CreatePlease login to create content