Technical Notes

Port Numbers Used by Verastream Integration Broker
Technical Note 10036
Last Reviewed 04-Nov-2004
Applies To
Verastream Integration Broker version 9.5 or higher
Summary

This technical note lists the inbound ports used by Verastream Integration Broker (VIB). This information may be helpful if you are configuring your firewall to allow Verastream Integration Broker access. This information supersedes the product documentation.

Ports Used by Verastream Integration Broker

The following table lists the port numbers used by Verastream Integration Broker inbound connections.

Note: Your implementation of VIB may use additional ports for web servers, databases, message queues, etc.

Default incoming (listening) port	Protocol	Service name (from /etc/services or equivalent)	Parameter (environment variable in sn.ini [default])	Explanation
1700	TCP	sndedic (previously called nova, fours)	SNTCPDEDIC (previously called TCP4S_DS)	Data Server, application partitioning, dedicated services
1701	TCP	snvcp	SNTCPVCP	VCP services by sntcpd daemon
1705	TCP	sndirsv (previously called novadirsrv, foursdirsrv)	SNTCPDIRSV (previously called TCP4S_DSV)	Directory server (The sntcpd daemon tracks the registration and runtime status of server components.)
Arbitrary*	TCP	N/A	N/A	VCP server components
Arbitrary*	TCP	N/A	N/A	Component server switch (CSX)
1702***	TCP	snrecov***	SNTCPRECOV ***	Replication recovery by sntcpd daemons
1700	UDP	snsnmp	SNUDPSNMP	SNMP communication between sntcpd daemon and engine
1701	UDP	snrepl	SNUDPREPL	Replication broadcasts (or unicasts configured with SNDAEMONPEERS) by sntcpd daemons**

*See Specifying Fixed Component Ports, below.

**Replication cannot be performed with firewalls that perform NAT or proxy function (IP masquerading).

*** Version 9.7 only. Earlier versions used a non-configurable arbitrary port number.

Specifying Fixed Component Ports

By default, an arbitrary TCP port is used by VCP (Verastream Component Protocol) server components and CSX switches (Component Server Switch); however, these port numbers can be "hardcoded," allowing Verastream to communicate through a firewall.

Use one of the following methods to hardcode these ports.

• For VCP components not using CSX, modify the ADDRESS property using the syntax ADDRESS='tcpip:localhost:port', where port is the desired port number.
• For VCP components in a CSX pool, you must configure the CSX switch port as follows.

1. Open the CSX Configuration utility and select your CSX component pool.
2. On the Advanced tab, change the value in the "Use fixed port on all switches" field from 0 to an unused port number.

1. Open the CSX Configuration utility and select your CSX component pool.
2. Click Edit > Export CSX Pool to File, and then enter a file name.
3. Edit the exported file to change the PORT-NUMBER value to an unused port number. (Leave "ONLY-LOCAL no" unchanged.)
4. If you will be communicating through a firewall that performs NAT or proxy function (IP masquerading), change the HOST-ALIAS value to the IP address or host name of the proxy server. Otherwise, leave this value unchanged ("-").
5. Import the edited file. (In the CSX Configuration utility, click Edit > Import CSX Pool from File, and then select the file name.)

Deprecated and Unsupported Services

The following ports were used in earlier versions of Verastream Integration Broker but are no longer used or supported. They are listed here for historical purposes, and to clarify the product documentation.

Default incoming (listening ) port	Protocol	Service name (from /etc/services or equivalent)	Parameter (environment variable in sn.ini [default])	Explanation
1701	TCP	snshrsv	SNTCPSHSV	Shared services, server side. No longer supported
1702	TCP	snshrcl	SNTCPSHRCL	Shared services, client side. No longer supported.
1703	TCP	snwwwsv, novaservice, foursservice	SNTCPWWWSV, TCP4S_SRV	Deprecated, succeeded by WWW components. No longer supported.
1704	TCP	snagent, novaagsuper, foursagsuper	SNTCPAGENT, TCP4S_AS	Deployment agent service. No longer used or supported.
1706	TCP	snssl	SNTCPSSL	Application partitioning via encrypted Secure Sockets Layer. No longer supported.

Related Technical Notes

10031	Troubleshooting VCP Exception COMM_FAILURE
10035	Verastream Integration Broker and the Microsoft Windows Firewall (Included in XP Service Pack 2)