Unsolved
This post is more than 5 years old
3 Posts
0
6391
September 26th, 2014 12:00
How to confirm opening the outbound ports(8443,443)
As a subject, I just wonder how to confirm opened outbound ports(8443, 443)
For ESRS service, Opening the outbound ports(8443, 443) is essential about 19 IP address as below.
I always request to customer opening the oubound ports(8443,443) about 19 IP address.
and then, customer said to me, status is "any connect" but, it cannot be connect EMC whenever I installed ESRS package through provisioning tool.
Let me know how to confirm? such as command or another method.
Santa Clara
- Øesrgscprd01.emc.com 137.69.120.170
- Øesrgscprd02.emc.com 137.69.120.171
- Øesrgscprd03.emc.com 137.69.120.172
Cork
- Øesrgckprd01.emc.com 152.62.177.11
- Øesrgckprd02.emc.com 152.62.177.12
- Øesrgckprd03.emc.com 152.62.177.13
Singapore
- Øesrgspprd01.emc.com 152.62.45.11
- Øesrgspprd02.emc.com 152.62.45.12
- Øesrgspprd03.emc.com 152.62.45.13
Hopkinton
- Øesrghoprd01.emc.com 168.159.209.11
- Øesrghoprd02.emc.com 168.159.209.12
- Øesrghoprd03.emc.com 168.159.209.13
Westboro
- Øesrgweprd01.emc.com 128.221.204.210
- Øesrgweprd02.emc.com 128.221.204.211
- Øesrgweprd03.emc.com 128.221.204.213
• ESRS UI server
- ØProd: esrs.emc.com 128.221.192.13
DR: esrs-dr.emc.com 168.159.218.20
•ESRS Core (for GW Pings) server
- ØProd: esrs-core.emc.com 128.221.192.14
- ØDR: esrs-coredr.emc.com 168.159.218.21
No Events found!
K_R_6b1375
1 Message
0
December 11th, 2014 11:00
did you fix it ? i have the same issue now
Cal-IF4UI
56 Posts
0
January 21st, 2015 13:00
Please
Confirm if Customer has Cisco Switches which uses AnyConnect Feature,
also look in the switch logs for any error codes and troubleshoot zones, one
issue that is common is “Can’t use AnyConnect and/or the regular Cisco client after
a Windows 7 update? Seeing an error 440? If you experience this problem, go
to Start-Control Panel-Programs and Features. Look for the Cisco
client(s) listed there and do a right click to Uninstall it.
Once it is gone from the list, reboot your computer and try again. other than above look at
KB article which tends to be a older solution 000015028 How to test connectivity whent CECT tool connecting to the provisioning fails. Other than that check the CECT logs in install folder, and its counterpart in Virtual Edition