Confluence Docs 3.0 : Recommended network topology This page last changed on Aug 15, 2008 by smaddox. Atlassian recommends a network topology similar to the one shown below, to get the best results from a Confluence Clustered deployment. The number of Confluence nodes in the deployment is adjustable — select the number which suits your own requirements. The most important aspect is that cluster, database and HTTP (client) traffic are all carried on separate subnets. It is possible, on a sufficiently fast network, to carry cluster and database traffic on the same subnet but we do strongly recommend that HTTP traffic be always confined to a separate subnet on production deployments. Confluence Clustered does not support clustered communication over WAN, VLAN or VPN. All Confluence Clustered nodes must be on the same local subnet, ideally networked via an ethernet hub or simple switch. The cluster communication network must also support multicast IP networking.
| Use this example as a basis for your own network diagram When you are considering a Confluence Clustered deployment, you should prepare a network diagram like the one on this page. This will facilitate discussion with Atlassian Support and help with your own planning. Please refer to the cluster checklist for more guidance on planning your clustered deployment.
Attachments: Network topology (text/xml) Network topology (text/xml) Network topology (text/xml) Network topology (text/xml) Network topology84961.jpg (image/jpeg)

Document generated by Confluence on Nov 05, 2009 23:26