Not sure if this is an issue, but on a new MCCIP with two C60 clusters connected with Cisco Nexus switches and 100G ISL, when we create a new SVM via the web GUI it triggers errors in the event log like: dm.vserver.mcc.rebaselinefailed: Vserver configuration resynchronization failed for Vserver... and vsdr.net.LifNotReachable: The LIF lif_NFS_4736 in DR partner Vserver of Vserver NFS-mc is not reachable from the local cluster.
The web GUI doesn't show any errors, and the SVM's seems OK... also in "metrocluster vserver show" everything looks OK...
So maybe this is just an error that occors when creating a new SVM? Thre doesn't seem to be any other errors..
We are on ONTAP 9.17.1P5
#MCCIP SVM Creation triggers resync errors...
lusty moss
south coral
the LIF not reachable error means that Layer 2 connectivity to the other cluster is not working correctly, so in the case of a switchover you might lose access to your SVM. It can be a false positive though (some switches filter out the L2 pings)
lusty moss
the LIF not reachable error means that Layer 2 connectivity to the other cluster...
I guess we will find out as we test everything... the first error about the resync came after about 10-15 secs. of "creating" the SVM.. (this was a simple NFS SVM, so no CIFS AD etc.. ) but no error in the GUI... I was just wondering why it took so long and noticed the error... I think we will keep trucking on and see if we have issues as we test everything...
About the L2... the frontend is setup as one ifgroup with LACP (100G links) against Cisco Nexus equipment.. then a few VLANs are tagged on top.. pretty standard... everything in default ipspace but with broadcast domains with both 1500 and 9000 MTUs...
south coral
yeah, we have seen this message a few times and it was inalmost all cases a false positive, and everything worked fine after a switchover
lusty moss
Just created another one and it takes "longer then normal" but this time we didn't get any errors... my guess it that there is some resync-timeout values that is tripped...
hmm the metrocluster check complains about the LIFs on one of the SVMs... : "Discovery of LIF with address 172.26.15.62 failed from destination cluster Ensure that the destination cluster has ports that have connectivity to the LIF on the source cluster" but I have doublechecked and everything should be OK... same broadcast domains etc.. strange
half patio
you can always try 'net l2ping ' to see if you can actually reach remote mac addresses between site svm's
lusty moss
that all seems to work.. I can ping the mac of the ifgrp...
half patio
i was thinking more about individual macs within vlans, if you're using vlans. Mostly to eliminate switch configuration errors.
lusty moss
i was thinking more about individual macs within vlans, if you're using vlans. M...
they all have the same mac...
half patio
but you would be "l2ping'ing" within a different collision domain
lusty moss
We have a NFS SVM within the same VLAN on both clusters .. I am able to ping between them no problems...
tempted to just try a switchover to see what happens...
also.. a "metrocluster check run" from the commandline complets OK.. but in the GUI it comlains about the LIF configuration...
I will try to tear down the SVM and re-create it