forked from docs/doc-exports
Zheng, Xiu
5b5876528a
Reviewed-by: Pruthi, Vineet <vineet.pruthi@t-systems.com> Co-authored-by: Zheng, Xiu <zhengxiu@huawei.com> Co-committed-by: Zheng, Xiu <zhengxiu@huawei.com>
14 lines
1.1 KiB
HTML
14 lines
1.1 KiB
HTML
<a name="css_02_0083"></a><a name="css_02_0083"></a>
|
|
|
|
<h1 class="topictitle1">Do Ports 9200 and 9300 Both Open?</h1>
|
|
<div id="body1587038134114"><p id="css_02_0083__p1888832520148">Yes. Port 9200 is used by external systems to access CSS clusters, and port 9300 is used for communication between nodes.</p>
|
|
<p id="css_02_0083__p10717171016176">The methods for accessing port 9300 are as follows:</p>
|
|
<ul id="css_02_0083__ul219141711714"><li id="css_02_0083__li1793215154187">If your client is in the same VPC and subnet with the CSS cluster, you can access it directly.</li><li id="css_02_0083__li58711625191815">If your client is in the same VPC with but different subnet from the CSS cluster, apply for a route separately.</li><li id="css_02_0083__li181951718170">If your client is in the different VPCs and subnets from the CSS cluster, create a VPC peering connection to enable communication between the two VPCs, and then apply for routes to connect the two subnets.</li></ul>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="css_02_0082.html">Ports</a></div>
|
|
</div>
|
|
</div>
|
|
|