Cisco Cisco 3365 Mobility Services Engine 릴리즈 노트
27
Release Notes for Cisco Mobility Services Engine, Release 7.6.100.0
OL-30651-01
Caveats
CSCul17995
Headline: MSE Analytics and CAS services on separate servers.
Symptom: When the MSE Analytics and CAS services are run on two separate
MSEs, and Analytics MSE is pointing to CAS MSE, it collects data from the time
Analytics MSE is configured to pull data from Location MSE. If CAS or Location
MSE has old data before this configuration, Analytics will not pull this data.
MSEs, and Analytics MSE is pointing to CAS MSE, it collects data from the time
Analytics MSE is configured to pull data from Location MSE. If CAS or Location
MSE has old data before this configuration, Analytics will not pull this data.
Symptom: When the MSE Analytics and CAS or Location services are running on
two separate MSEs and Analytics MSE is pointing to CAS MSE, it collects data
only from the time the Analytics MSE is configured to pull the data from location
MSE. If CAS or Location MSE has old data before this configuration, the
Analytics will not retrieve this data.
two separate MSEs and Analytics MSE is pointing to CAS MSE, it collects data
only from the time the Analytics MSE is configured to pull the data from location
MSE. If CAS or Location MSE has old data before this configuration, the
Analytics will not retrieve this data.
Conditions: When Analytics and CAS are running on two different MSEs and
Analytics MSE is pointed to this CAS MSE from the Prime Infrastructure.
Analytics MSE is pointed to this CAS MSE from the Prime Infrastructure.
Workaround:
•
Disable Analytics Service from the Prime Infrastructure.
•
Copy the “#!/bin/bash# * # *” script to /root on Analytics MSE.
•
Once copied, do the following on the Analytics MSE
–
cd /root
–
chmod +x removeCache.sh
–
./removeCache.sh
•
Enable Analytics Service from PI.
CSCul40269
Headline: CMX Connect - Social login client to be classified as Basic guest.
Symptom:CMX Connect - Social login client to be classified as Basic guest.
Condition: This happens when the client is connected as social user.
Workaround: Once you modified the social connectors on BBX dashboard UI, the
submit splash template triggers the cache to be synchronbized with the database.
submit splash template triggers the cache to be synchronbized with the database.
For 7.6 Release, if a client logs in with LinkedIn account, the redirection does not
happen. This problem is fixed in 7.6 demo.
happen. This problem is fixed in 7.6 demo.
CSCul74644
Headline: Browser engage service stops working after failover in VM HA setup.
Symptom: Browser engage service stopped working after failover in VM HA
setup.
setup.
Condition: Browse Engage and Vistor Connect service is not supported in HA
mode
mode
Workaround: None
Table 6
Open Caveats (continued)
ID Number
Caveat Title