Advertisement
BinLiu

Untitled

Feb 1st, 2018
89
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. there are there nodes, use "knet_link_get_link_list" to get num_links, use "knet_link_get_status" to get link status
  2.  
  3. here is the ip addr
  4. node1(10.67.19.168, 10.67.18.84, 10.67.18.52)
  5. node2(10.67.19.210, 10.67.18.53, 10.67.18.88)
  6. node3(10.67.18.247, 10.67.19.238, 10.67.19.178)
  7.  
  8. I disabled "10.67.19.168" first, then corosync on node1 switched to "10.67.18.84", and when I re-enabled "10.67.19.168", corosync switched back to ""10.67.19.168", these are expected.
  9.  
  10. but when I debug corosync: totemknet_ifaces_get(), here is the link status of knet.
  11.  
  12. node 1:
  13. num_links = 1
  14. 10.67.19.168 -> 10.67.19.168
  15.  
  16. node 2:
  17. num_links = 3
  18. 10.67.19.168 -> 10.67.19.210
  19. 10.67.18.84 -> 10.67.18.53
  20. 10.67.18.52 -> 10.67.18.88
  21.  
  22. node 3:
  23. num_links = 3
  24. 10.67.19.168 -> 10.67.18.247
  25. 10.67.18.84 -> 10.67.19.238
  26. 10.67.18.52 -> 10.67.19.178
  27.  
  28. what I want to say is the link normal? shouldn't and in this way, not all elements can be updated, this is why there are two 'n' in the output of 'corosync-cfgtool -s -b'
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement