Hi, A S Parameswara Rao, first at all you need to check how the Etcd was started, go to the Etcd1 server and run:

kube-etcd-ha1:~# netstat -ntlp 
Active Internet connections (only servers) 
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name 
tcp 0 0 127.0.0.1:10248 0.0.0.0:* LISTEN 737/kubelet 
tcp 0 0 127.0.0.1:10250 0.0.0.0:* LISTEN 737/kubelet 
tcp 0 0 xx.xx.xx.xx:2379 0.0.0.0:* LISTEN 22075/etcd 
tcp 0 0 xx.xx.xx.xx:6443 0.0.0.0:* LISTEN 820/haproxy 
tcp 0 0 xx.xx.xx.xx:2380 0.0.0.0:* LISTEN 22075/etcd 
tcp 0 0 127.0.0.1:10255 0.0.0.0:* LISTEN 737/kubelet 
tcp 0 0 127.0.0.1:46837 0.0.0.0:* LISTEN 737/kubelet 

So you will check are your etcd installation was Ok, then you can try to connect to the 2379 port for example from other etcd node by telnet for example:

kube-etcd-ha2:~# telnet xx.xx.xx.xx 2379 
Trying xx.xx.xx.xx… 
Connected to xx.xx.xx.xx. 
Escape character is ‘^]’.

and make sure that you can access to this port, same way you can check all other ports.

This example port list output was done on Etcd1 of the well running mine kubernetes clusters.