Ports that are used by Veritas Storage Foundation for Windows and Storage Foundation HA for Windows

Problem

Ports that are used by Veritas Storage Foundation for Windows and Storage Foundation HA for Windows

Solution

The following table contains a list of ports that are used by Storage Foundation for Windows (SFW) and Storage Foundation HA for Windows (SFW-HA).

Figure 1 - Ports that are used by SFW and SFW-HA
 
Port NumberProtocolDescription
4888TCPVeritas Scheduler Service (SFW 5.1 and above)
1556TCP/UDPPrivate Branch Exchange (SFW 5.0 and above)
2148 / 3207TCP/UDPVeritas Enterprise Administrator (VEA) Server (vxsvc.exe)
2821* Note 1TCP/UDPVeritas Security Services (VxSS)
3207TCP/UDPVEA (vxsvc.exe)
4145UDPVCS heartbearts
7419TCPUsed by many Symantec wizards
14151 / 8181 / 8443TCP/UDPVRTS Web Administration (vrtsweb.exe)
8199TCPVolume Replicator Administrative Service (VRAS)
5634HTTP/HTTPSVeritas Storage Foundation Messaging Service (xprtld.exe)
8989TCPvxrserver (vxrsyncd)
14141TCPVCS Engine (had.exe)
14144TCP/UDPVCS Notification
14145TCP/UDPGlobal VCS Cluster Manager (VCS 2.x and earlier)
14150TCP/UDPVCS Command Server - use override environment variable VCS_CMDSERVER_PORT_ENV to change from default port used
14153TCP/UDPVCS Cluster Simulator
14155TCPVCS Global Cluster Option (SFW-HA 4.1 and later)
14300TCP/UDPVRTSWeb Admin
15550 - 15558TCP/UDPVCS Cluster Simulator
49152 - 65535TCP/UDPVolume Replicator Packets, VCS Cluster heartbeat
14145 / 14994 / 14443TCP/UDPVeritas Cluster Server Management Console Web Server Veritas Cluster Server Management Console Web Server Veritas Cluster Server Management Console Web Server
   


Note 1: In addition to port 2821, if the Root Broker is behind a firewall, TCP ports 135, 1253 and 445  must be opened as well. These ports are used by Microsoft Remote Administration.

Port Conflicts

In some cases, another process or application will attempt to use a port that is already being used by SFW.  This may cause the application, or SFW to function incorrectly. Some customers have successfully managed port conflicts by following the steps found in the following Microsoft article:  

Note: The steps found in this article have not been tested by Symantec. This link is provided as a reference:

 http://support.microsoft.com/kb/812873
 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)