ā09-23-2014 06:28 PM
Hi all,
I got the error message "Config mismatch between VSM and VPath" on my Nexus VSM but I could not see any detail regarding this bug ID due to permission issue. Has anyone else got access to see this bug detail and able to share? I need to know if this bug is critical or just cosmetic. Thanks
regards,
Robin
ā09-24-2014 08:23 AM
Hi Robin,
This DDTS was Junked. But here's the workaround that is mentioned:
1. Deleting the vservice config (no vservice) & reconfiguring vservice, will get rid of this mismatch issue.
2. Toggling the port-profile should also work.
I see couple of other DDTS as well related to this and i would suggest to ask this question in "Other Data Center Subjects" forum for detailed and quick answer.
CSCtz36835 :Config mismatch on VSM and Vpath after deleting service vlan
Regards,
Kanwal
Note: Please mark answers if they are helpful.
ā09-25-2014 09:11 PM
hi kanwal. Thanks for your comment.
I tried the suggested methods but the error kept happening as long as I associated with either NetScaler 1000v or vWAAS VPATH. For VSG is totally fine. The Prime NSC also gave error "fail-to-apply". all services nodes are registered and associated with Prime NSC 3.2.2b.
I tried to remove NetScaler 1000v config on VSM and redo the NS1000v setup from Prime NSC but still same issue. Do you have any good documentation for implementing NetScaler 1000v using Prime NSC? I cannot find this so far as this technology is pretty new to Cisco I believe. Hopefully internal Cisco team can help me here. Thanks
ā11-05-2014 09:40 PM
I managed to fix that error by upgrading the VSM to the latest version so it was compatibility issue although PNSC shows all good.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide