We currently have Cisco Proximity Software (versions 188.8.131.52 and 3.0.1) on our Windows 10 SOE fleet, endpoints are randomly attempting to establish external connections through proximity.exe to 184.108.40.206:8089;
Port 8089 is TCP for Splunk Daemon Management. Name: ec2-34-230-180-181.compute-1.amazonaws.com Address: 220.127.116.11
Navigating to ec2-34-230-180-181.compute-1.amazonaws.com displays Splunk > Cloud
My understanding is that this is expected and Cisco does indeed collect logs via Splunk Cloud;
I would like to know if there will be any impact to the Proximity software if we disable/block outbound connections from proximity.exe going through to: ec2-34-230-180-181.compute-1.amazonaws.com Address: 18.104.22.168<http://22.214.171.124> ?
Apologies for the belated reply. There have been some updates to how well we handle Splunk not being reachable, so if you want to do this I strongly suggest you not run an older version of Cisco Proximity. Otherwise, no, the software works fine without its metrics server.
Cisco Proximity 2.0.8 includes some changes to the Windows installation package to facilitate mass deployment. None of these changes break backwards compatibility. The changes are these added msi properties:
LAUNCHPROXIMITY (Default: 1)
If set to 0, pr...
The Cisco Technical Support mobile application for iOS and Android devices provides access to our most frequent support tools and information while you are on the go. Several features are freely accessible by anyone including access to the Cisco...
Cisco Proximity Troubleshooting Guide v3.0
Cisco Proximity is a technology that allows the user to control an endpoint, receive content (presentation) directly onto a mobile device and share content wireless from a PC o...