- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: 3PAR Management Console 4.7.3.2 vs port 5783
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-27-2019 07:39 AM
06-27-2019 07:39 AM
3PAR Management Console 4.7.3.2 vs port 5783
Port 5783 to our 3PAR is open, our 3PAR is listening on 5783, and I can confirm the app is successfully establishing a TCP connection on this port. But for some reason the app immediately falls back to port 2550 (which fails because our 7400 isn't listening on this port) then fails to connect altogether. Non-secure on port 5782 works fine. Any ideas on what to try?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-29-2019 04:15 AM
06-29-2019 04:15 AM
Re: 3PAR Management Console 4.7.3.2 vs port 5783
I am an HPE Employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-01-2019 08:59 AM - edited 07-01-2019 09:00 AM
07-01-2019 08:59 AM - edited 07-01-2019 09:00 AM
Re: 3PAR Management Console 4.7.3.2 vs port 5783
Our 3PAR isn't listening on 2550. It's a 7400 running 3.2.2. Should it be?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2019 07:12 AM
07-02-2019 07:12 AM
Re: 3PAR Management Console 4.7.3.2 vs port 5783
Hello rmay_bk,
No, if this is on 3.2.2, port 2550 not necessary. And it will only try to connect to that port when the connection to 5783 fails and it might be toggling between these ports.
This require detailed network troubleshooting.
I am an HPE Employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-02-2019 07:37 AM
07-02-2019 07:37 AM
Re: 3PAR Management Console 4.7.3.2 vs port 5783
5783 is definitely open. I can telnet to that port successfully. I can also see (via netstat) that imc.exe is successfully opening a TCP connection to 5783. But it immediately falls back to trying 2550.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-04-2019 12:47 AM
07-04-2019 12:47 AM
Re: 3PAR Management Console 4.7.3.2 vs port 5783
Hello rmay_bk,
This might require a detailed analysis from network side. And for that purpose a root connection is preferred.
By the way, could you change the network master node and check (setnet changenode <node number>)? Another option is to restart the netc/netcc services (but that needs a root connection as well).
Another wild guess is there may be a duplicate IP in the network. Can you change the IP temporarily and try?
I am an HPE Employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]