#vserver peering (na_ontap_vserver_peer) works only to peer first vserver/FSX instance..

1 messages · Page 1 of 1 (latest)

inner valve
#

Hello All.

netapp.ontap.na_ontap_vserver_peer API to an FSX instance works only for first vserver peering to another FSX while it doesn't create vserver peering to any another FSX instances after.

so looks like running : na_ontap_vserver_peer in an FSX instance(fsx1) with svm:fsx in it works fine to peer vserver in another fsx instance fsx2 with svm:fsx but it does NOT works to peer it with any another fsx instances say fsx3 with svm:fsx in it.

fsx1 cluster with svm fsx --> vserver peering to : fsx2 with svm fsx = works fine as expected.
next,
fsx1 cluster with svm fsx --> vserver peering to : fsx3 with svm fsx -- doesn't creates any vserver peering.

netapp.ontap.na_ontap_vserver_peer:
  state: present
  hostname: <<fsx1_ip>>
  username: fsxadmin
  password: <<fsx1_pw>>
  vserver: fsx
  validate_certs: no
  https: true
  use_rest: always 
  peer_cluster: <<Fsx2Id>>
  peer_vserver: fsx
  local_name_for_peer: <<fsx2>>
  local_name_for_source: <<fsx1>>
  applications: 
    - 'flexcache'
  peer_options:
    hostname: <<fsx2_ip>>
    username: fsxadmin
    password: <<fsx2_pw>>
    validate_certs: no
    https: true
    use_rest: always

above is only working to peer first fsx instance while doesn't work to vserver peer for any fsx clusters after (while they have same vserver name as : fsx)..

ontap collection :
netapp.ontap 22.9.0

any thoughts/help would be much appreciated please. Thanks..