Skip to main content
NetApp Knowledge Base

Virtual Storage Console (VSC): How to troubleshoot communication issues with VSC

Last Updated:

Applies to

  • Virtual Storage Console (VSC) 7.x
  • Virtual Storage Console (VSC) 9.x
  • VMware vCenter Server Appliance (VCSA) 6.x


This article describes the process for troubleshooting communication issues between Virtual Storage Console (VSC) and vCenter Server Appliance (VCSA). This procedure includes instructions for VMware's vCenter HTML5 client

By default, VSC uses designated ports to enable communication between its components, which include storage systems and VCSA. If you have firewalls enabled, you must ensure that the firewalls are set to allow exceptions.

VSC uses the following default bidirectional TCP ports:

Default port number Description
9083 When enabled, both VASA Provider and Storage Replication Adapter (SRA) use this port to communicate with the vCenter Server. This port is also required for obtaining the TCP/IP settings.

Depending on how you have configured your credentials, the VMware vCenter Server and the storage systems listen for secure communications on this port.

8143 VSC listens for secure communications on this port.
7 VSC sends an echo request to ONTAP to verify reachability and is required only when adding storage system and can be disabled later.

If you come across issues with VSC registering to VCSA such as receiving Server Error on the Registration page https://vsc_ip:8143/Register.html or VSC successfully registers to VCSA but later on the maintenance shell shows that Virtual Storage Console is running but not registered then you should test the communication between the two components.



Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support