Comments
-
Ack! I just found this posting after trying to figure out why my edits disappeared. Since I was making the change "outside the lines", I didn't expect it to get wiped out... especially by CWiz, since the first fix suggestion is "take 2 CWiz and call me in the morning." Definitely needs to be persistent.
-
Never mind, I figured it out... although the Metadata for Orion.UDT.Port says CanUpdate is False, the URI is actually using Orion.Nodes. So, I was able to write a script to update ports selectively.
-
I have the same problem with ip access-groups on NX-OS devices: in and out are reversed between running and startup. The issue is that you don't know why the config is diffferent unless you look at each one... I know it's tricky to solve since order matters in some commands and not in others but it's still annoying.
-
Did anybody figure this out? Since it already appears to be ignoring the hex cert contents lines ok, I thought I'd just add the following exemption: \snvram:[A-Za-z0-9#]*\.cer$ That should ignore the nvram file reference at the end of the certificate line, right? But, it's not working... these two lines still show up as…
-
I have the same plus "Mismatched MS updates: Cannot get IP address for the following servers..." which includes the MPE itself. After triple-checking that everything was correctly matched, I opened a tech support case where the tech told me "yeah, I can't get my lab servers straightened out either." Other suggestions were…