Okay. I have a server.
It's a Domino server.
It's a Domino server running 6.5.5.
It's a Domino server in my primary Domino domain.
It's a server running Windows 2000.
It's a server that is in a cluster.
It's the failover server, so it just sits there and looks pretty all day.
It's a server that also accepts all incoming smtp mail.
It's a server that doesn't do much else. Besides accept mail and look pretty.
It's a server that has two NIC's in it.
It's a server that is configured with the FQDN in the Ports-Notes Network Ports section.
It's a server that is configured with the Cluster name also in the Ports-Notes Network Ports section.
It's a server that has had Sametime 6.5.1 installed on it recently.
It's a server that when I start Sametime, it things that the HTTP port is the Cluster port, and not the physical network FQDN port.
It's a server that is a pain in the butt right now.
Any ideas?
2 comments:
Looking through the Admin Help (that F1 thingy...) I see a topic titled "Setting up a private LAN for a cluster"
Check to see if you have anything for the CLUSTER_TcpIPAddress parameters in your notes.ini:
If you have ports named TCPIP and CLUSTER, for example, these lines might be:
TCPIP_TcpIPAddress=0,192.114.32.5:1352
CLUSTER_TcpIPAddress=0,192.168.64.1:1352
8. Do one of the following:
Reorder the ports so that the cluster port is first.
This ensures that all cluster traffic uses this port for cluster traffic. Be sure that all other traffic is assigned to use other ports.
Add the following line to the NOTES.INI file:
Server_Cluster_Default_Port=Cluster Port
where Cluster Port is the port you created for the cluster. In this example, this line would be:
Server_Cluster_Default_Port=CLUSTER
This ensures that all cluster traffic uses this port for cluster communications no matter what order the ports are in.
Hey dude,
Yup, had all of the above already in the notes.ini file. Lotus support suggested that I try to switch the order of
TCPIP_TcpIPAddress=0,192.114.32.5:1352
CLUSTER_TcpIPAddress=0,192.168.64.1:1352
so that TCPIP was first. That didn't do it either. It's a bugger alright. Thanks for the input!!
Post a Comment