Notifications Issue with Cisco MSE and WCS | Troubleshooting Guide

Troubleshooting Cisco MSE and WCS Notifications

Prev Question Next Question

Question

You are developing a context-aware application with customized middleware.

The Cisco MSE is configured to send northbound notifications to the middleware as well as to the Cisco WCS via SOAP/XML.

You created the notification definitions via the WCS and see notifications coming in on the middleware, but you do not see notification messages showing up in the WCS.

What could be causing this problem?

Answers

A. The notification receiver is not correctly configured in the WCS. Make sure the WCS is correctly configured with a northbound notification receiver using SNMPv2 and the correct community string.

B. The notification group does not have an MSE assigned and the MSE is not synchronized.

C. The WCS does not understand SOAP/XML. To correct this, change the transport protocol to SNMP/plain text.

D. The WCS does not understand SOAP/XML. To correct this, change the transport protocol to SNMP/XML.

E. The WCS does not understand SOAP/XML. To correct this, change the transport protocol to Syslog/plain text.

F. The WCS does not understand SOAP/XML. To correct this, change the transport protocol to Syslog/XML.

Show Answer

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E. F.

This question is related to the integration between Cisco Mobility Services Engine (MSE), Wireless Control System (WCS), and a customized middleware for a context-aware application. The scenario involves sending notifications from MSE to both the middleware and WCS using SOAP/XML protocol. However, the problem reported is that while the middleware is receiving notifications, the WCS is not.

The likely cause of this problem is that the notification receiver in WCS is not correctly configured to receive SOAP/XML notifications from MSE. This means that the issue is not related to the transport protocol or synchronization of MSE, as mentioned in options B, C, D, E, and F.

To solve the issue, the administrator needs to check the configuration of the notification receiver in WCS. The notification receiver needs to be configured correctly with the correct community string and the appropriate SNMP version (in this case SNMPv2) to receive notifications from MSE using SOAP/XML.

Once the configuration of the notification receiver is correct, WCS should start receiving notifications from MSE. It is important to note that the middleware is receiving notifications, which means that the problem is not with MSE or the notifications themselves. Rather, it is a configuration issue with the WCS notification receiver.

In conclusion, option A is the correct answer to this question.

Prev Question Next Question