04-09-2020 05:53 AM - edited 05-01-2020 02:34 PM
Replication Configuration: Not able to perform CLUSTER PAIRING & getting failed to Paired
I configured network for replication & test passed from both side properly but Custer paring not working
Getting following msg
When I tried from Cluster A
"Replication Peer not added"
When I tried from Cluster B
"Failed to get cluster properties"
####################################
Also getting this error
admin@SpringpathControllerssffs:~$ stcli dp peer add --name Test-RP1 --description hxrp --mgmtIp
output:
Enter peer-cluster's password:
DP Peer add failed
'NoneType' object has no attribute 'read'
@@@@@@@@@@
^CTraceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 174, in _run_module_as_main
"__main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
File "/opt/springpath/storfs-mgmt-cli/stCli-1.0-py2.7.egg/stCli/stCli.py", line 11130, in <module>
File "/opt/springpath/storfs-mgmt-cli/stCli-1.0-py2.7.egg/stCli/stCli.py", line 11118, in run
File "/opt/springpath/storfs-mgmt-cli/stCli-1.0-py2.7.egg/stCli/stCli.py", line 11091, in dispatch
File "/opt/springpath/storfs-mgmt-cli/stCli-1.0-py2.7.egg/stCli/stCli.py", line 5130, in dp_peer_add_action
File "/opt/springpath/storfs-mgmt-cli/stCli-1.0-py2.7.egg/com/storvisor/sysmgmt/stDataSvcMgr/StDataSvcMgr.py", line 2991, in pairCluster
File "/opt/springpath/storfs-mgmt-cli/stCli-1.0-py2.7.egg/com/storvisor/sysmgmt/stDataSvcMgr/StDataSvcMgr.py", line 3002, in send_pairCluster
File "build/bdist.linux-x86_64/egg/thrift/transport/THttpClient.py", line 106, in _f
File "build/bdist.linux-x86_64/egg/thrift/transport/THttpClient.py", line 145, in flush
File "/usr/lib/python2.7/httplib.py", line 1211, in getreply
response = self._conn.getresponse()
File "/usr/lib/python2.7/httplib.py", line 1136, in getresponse
response.begin()
File "/usr/lib/python2.7/httplib.py", line 453, in begin
version, status, reason = self._read_status()
File "/usr/lib/python2.7/httplib.py", line 409, in _read_status
line = self.fp.readline(_MAXLINE + 1)
File "/usr/lib/python2.7/socket.py", line 480, in readline
data = self._sock.recv(self._rbufsize)
KeyboardInterrupt
###################################
Solved! Go to Solution.
05-14-2020 07:52 AM - edited 05-14-2020 07:53 AM
Solution - not available since
Before beginning the HyperFlex Hardware Acceleration Cards installation process, note the following:
Installation is only supported on NEW deployments.
Installation is only supported on the following HX 240 M5 servers:
HXAF240C-M5SX Cisco HyperFlex HX240c M5 All Flash
HX240C-M5SX Cisco HyperFlex HX240c M5
HX240C-M5L HyperFlex HX240c M5 LFF
Installation is not supported in Hyper-V and is not supported for stretched clusters.
All nodes in the HX cluster must contain the HyperFlex Hardware Acceleration Cards.
Note | If any nodes do not contain an acceleration card during validation, the installer fails to proceed and an error message appears. |
The cluster type must be All Flash/Hybrid ESXi.
Installation is only supported on HX 240 M5 servers.
Hardware Acceleration Cards do not work with Cisco HX Data Replication.
04-15-2020 03:09 AM
Greetings.
Have you by chance done a cluster expansion in the past?
I've seen a few cases with similar messages for clusters that had gone through expansion, and the internal zookeeper database was not updated with the node information. See https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvp60476
Can you check the output of stcli cluster info for both clusters, and look under the Node IP Settings, to confirm all your Nodes are listed?
Kirk...
04-15-2020 07:44 AM
Thanks a lot Kirk for helping into this issue
We installed two new HX-Cluster in same vCenter & expanded to recently
I just verified that we have all new nodes are listed under IP.
thanks again for helping. let me know if other area needs to check. I can share output too
04-15-2020 08:40 AM
Also we have 6 conversed & 12 Compute node on both Cluster
05-01-2020 11:23 AM - edited 05-01-2020 11:27 AM
I reinstalled both cluster without expanding cluster -during creation no error. So just wondering that Hyperflex replication configuration is broke in 3.5(2h) or just me facing this issue. anyone has similar issue
05-14-2020 07:52 AM - edited 05-14-2020 07:53 AM
Solution - not available since
Before beginning the HyperFlex Hardware Acceleration Cards installation process, note the following:
Installation is only supported on NEW deployments.
Installation is only supported on the following HX 240 M5 servers:
HXAF240C-M5SX Cisco HyperFlex HX240c M5 All Flash
HX240C-M5SX Cisco HyperFlex HX240c M5
HX240C-M5L HyperFlex HX240c M5 LFF
Installation is not supported in Hyper-V and is not supported for stretched clusters.
All nodes in the HX cluster must contain the HyperFlex Hardware Acceleration Cards.
Note | If any nodes do not contain an acceleration card during validation, the installer fails to proceed and an error message appears. |
The cluster type must be All Flash/Hybrid ESXi.
Installation is only supported on HX 240 M5 servers.
Hardware Acceleration Cards do not work with Cisco HX Data Replication.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: