Post reply

How do I bind the TCP Ports on SQLCLU2 to the TCP Port on SQLCL1 port 1433?

  • April 5, 2010 at 10:00 am

    #217524

    Background Information

    1. I do not have a Test Cluster to test on.

    2. I’m supposed to have a 2 instance cluster: (SQLCLU1 - Active) and (SQLCLU2).

    3. Currently, SQLCLU2 is not part of the Cluster.

    4. SQLCLU1 currently has the following drives: R, S, T and U.

    5. I have a client who wants to put a large database on drives T and U – therefore it will become an Active/Passive node.

    6. The Network/Web Admin setup the firewall to only allow my client access to port 1433 on SQLCLU2 and will not change the firewall port.

    7. When SQLCLU2 was recreated, the Netstat –an does not show a port 1433.

    a. SQLCLU1’s Public IP Address is 10.5.1.26:1433 Status is Listening

    b. SQLCLU2’s Public IP Address is 10.5.1.29:2301 Status is Listening

    c. SQLCLU1’s Private IP Address is 192.168.137

    d. SQLCLU2’s Private IP Address is 192.168.0.138

    8. Under SQL Server Configuration Manager (SQLCLU2), there are the following:

    IP1 ActiveYes EnabledNo IP Address 10.5.1.29 TCP Dynamic Ports0

    TCP Portblank

    IP 2 ActiveYes EnabledNo IP Address 192.168.0.138 TCP Dynamic Ports0

    TCP Portblank

    IP3 ActiveYes EnabledNo IP Address 127.0.0.1 TCP Dynamic Ports0

    TCP Portblank

    IP ALL TCP Dynamic Ports4061 TCP Portblank

    9. The only commonality between the SQLCLU1 and SQLCLU2 Netstat –an listening ports are the following: SQLCLU1 192.168.0.137:2301/2381 and SQLCLU2 192.168.0.138:2301/2381.

    10. Do you need additional information?

    Here is my question: Once I add SQLCLU2 to the Cluster, how do I bind the TCP Ports on SQLCLU2 to the TCP Port on SQLCL1 port 1433?

    Thanks,

    Ron

  • April 5, 2010 at 10:16 am

    #1145832

    Add the second node.

    Under configuration mgr, go to TCP/IP properties, make sure that each SQL Server is listening on 1433 on the public address (don't worry at all about the loopback address or the private address)

    Done.

    With SQL 2005 or later, all instances of SQL in a cluster (provided that each instance is a unique cluster group) can listen on port 1433, as each cluster group can have it's own IP address.

    /* ----------------------------- */
    Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!

  • April 5, 2010 at 10:25 am

    #1145839

    Thanks for your help GregoryF

    Ron

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply