NCC Failure on vstore mappings | Nutanix Community
Skip to main content
Hi,

When running NCC on one of the customers cluster, the following output is generated...



FAIL: Remote site: HQ-NTNXNumber of vstores mapped for the local site on the remote site are not same.Refer to KB 3335 (http://portal.nutanix.com/kb/3335) for details on remote_site_config_check or Recheck with: ncc health_checks data_protection_checks remote_site_checks remote_site_config_check



Why is it so important to have the same number of mappings? When we are replication from site A to site B, we can use different mappings than when replication is executed from site B to site A.



Regards,

Bart
What version of AOS and NCC are you running?
Hi Jon,



The cluster I ran NCC on is of AOS 4.7.2 and the latest NCC, provided with AOS 4.7.2.



The remote site is a 4.7.1 cluster, which will be upgraded very soon.



Bart
Hrmm, I dont see any obvious bugs in our bug DB that jumped out at me for this. Can you submit a support ticket and we can dig into the details with you over email/webex?



Thanks,

Jon
Hi Jon,



I don't think it is a bug... If NCC is checking if the number of mappings is the same at the configured remote site, the check has the correct output.



I am just wondering why the number of mappings must be equal on both sides?

That doesn't make any sense to me...



Regards,

Bart
I'm not saying its a bug either, I'm saying its a funky behavior issue.



The general thought here is that if you have mappings that occur at source that dont occur at target, reverse failback for things might be affected. There could be other reasons that I'm not thinking of off the top of my head.
Hi Jon,



You are right about the failback... I did not think about that.



Then I am in a little trouble, beause I created a mapping for replication of a server template to remote locations... I don't need a replication back to HQ for that...



So I have to live with a fail on that particular NCC check...



Regards,

Bart
I figured as much, which is why I'd love to collect this feedback via a support ticket, so our NCC folks can perhaps spruce up the check to cover this
I figured as much, which is why I'd love to collect this feedback via a support ticket, so our NCC folks can perhaps spruce up the check to cover this
Hi Jon,



I will file a support ticket next time I am at the customers site.



Bart
Terms & Conditions