Cisco Cisco 3365 Mobility Services Engine
26
Release Notes for Cisco Mobility Services Engine, Release 7.6.100.0
OL-30651-01
Caveats
CSCuj12261
Headline: Notification for missing client is repeatedly sent every 5 minutes.
Symptom: Having the following notification configuration for probing clients that
are tracked by the CAS or MSE. The notification over SOAP/Syslog is seen
repeatedly every 5 minutes even though this Notification has Non Recurring as
frequency configuration.Conditions: This happens to the notification having
following configurations:
are tracked by the CAS or MSE. The notification over SOAP/Syslog is seen
repeatedly every 5 minutes even though this Notification has Non Recurring as
frequency configuration.Conditions: This happens to the notification having
following configurations:
•
Condition Type: Missing
•
Trigger If: 180 min.
•
Frequency: Non Recurring
•
Apply To: Clients
•
Match By: MAC Address Like
Workaround: None.
CSCuj31226
Headline: ESXi Level 4 MSE has latency of 38 seconds after running for 48 hours.
Symptom: MSE has high latency after running for 48 hours with 64K Client or tag
mix.
mix.
Condition: This happens when 64,000 elements are covered by Level 4 MSE for
48 hours.
48 hours.
Workaround: Reduce the element count to 70-80% of capacity.
CSCuj75734
Headline: MSE communication credentials are not saved on an upgraded box.
Symptom: When upgrading the MSE from an earlier version to 7.5.102.101, the
Prime Infrastructure communication credentials are always shown as not
configured.
Prime Infrastructure communication credentials are always shown as not
configured.
Conditions: This is observed only on an upgrade scenario.
Workaround: Run the setup script and configure the Prime Infrastructure
communication credentials.
communication credentials.
CSCuj86038
Headline: CMX engage BBX is not working on some Web sites.
Symptom: CMX engage BBX is not working on some Web sites for a customer.
Condition: None.
Workaround: None
CSCuj98104
Headline: Failback fails due to timeout.
Symptom: MSE 7.2.110.0 experiences Failback timeout failure.
Condition: This happens when the MSE 7.2.110.0 is in High Availability mode
and the secondary MSE is running in failover.
and the secondary MSE is running in failover.
Workaround: None.
Table 6
Open Caveats (continued)
ID Number
Caveat Title