RE: ensure port is free upon failover
- From: Linchi Shea <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 2 Jun 2009 03:13:01 -0700
also, when I connect to the instance using SSMS i connect using
"sqlCluserName\InstanceName,PortNumber"
how can I connect using just "sqlCluserName\InstanceName" - I guess that sql
server must have a way of determining the port that an instance of sq server
is listening on.
That is what SQL Browser is for. When you connect with
sqlCluserName\InstanceName, the client will talk to SQL Browser over UDP and
obtain the necessary TCP port number.
Linchi
"Martin" wrote:
Hi,.
I have just installed a two node active/active cluster.
everything is fine, however I have a question about the ports.
a first instance is installed with "box A" being the preferred node for
"instance A"
the second instance is installed with "box B" being the preferred node for
"instance B"
instance A is listening on TCP port 60615.
so I've made an exception in the firewall on "box A" for port 60615.
however in a failover situation where instance A fails-over to box B the
instance will still be listening on port 60615.
how can I be sure that any future software installed on box b will not take
port 60615.
also, when I connect to the instance using SSMS i connect using
"sqlCluserName\InstanceName,PortNumber"
how can I connect using just "sqlCluserName\InstanceName" - I guess that sql
server must have a way of determining the port that an instance of sq server
is listening on.
many thanks in advance
martin.
- Follow-Ups:
- RE: ensure port is free upon failover
- From: Manpreet Singh
- RE: ensure port is free upon failover
- Next by Date: RE: Tempdb on non clustered disk
- Next by thread: RE: ensure port is free upon failover
- Index(es):
Relevant Pages
|