From 91d9da62ce95a14264950aaf2c100e089c455646 Mon Sep 17 00:00:00 2001 From: Prasanna Kumar Kalever Date: Thu, 24 Aug 2017 12:13:39 +0530 Subject: rpc: use port 24010 for all gluster-blockd management It looks like 24006 port is already registered by some other service, and from [1] it looks like 24007 - 24241 are unassigned. Currently, 24007 -> glusterd (tcp) 24008 -> glusterd (rdma) 24009 -> glustereventsd so for gluster-blockd communications lets choose port 24010 [1] https://goo.gl/B2A4RU Change-Id: I7d9f14b9897e479cececd2271ebf8a975d26ef71 Signed-off-by: Prasanna Kumar Kalever --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'README.md') diff --git a/README.md b/README.md index 7f66080..1205a20 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,7 @@ managing the command ring buffers ------ **Prerequisites:** *this guide assume we already have* - [x] *A gluster volume with name 'block-test'* -- [x] *Open 24007(for glusterd) 24006(gluster-blockd) 3260(iscsi targets) 111(rpcbind) ports and glusterfs service in your firewall* +- [x] *Open 24007(for glusterd) 24010(gluster-blockd) 3260(iscsi targets) 111(rpcbind) ports and glusterfs service in your firewall* Daemon: run gluster-blockd on all the nodes ```script -- cgit