...if you have two or more servers using Windows clustering, them move them to a new data center, and accidentally plug the cluster <--> cluster "private" CAT5 into your production VLAN and plug the production side into the cluster <--> cluster that your cluster will become unhappy, even if you correct the wiring mistake?
Hint: The solution is to go into the cluster admin and if you can't connect to the cluster by name, use a period and you'll get the local cluster admin. Hint 2: Then go into the IP resource properties of your cluster resource(s)and tell it to use the correct network - in my case it blanked out the selection and I simply used the drop down to say "oh yeah, THAT one". This is for 2003 Server, not idea if they've made 2003 R2 and later more idiot-proof. Yeah, that was one of my test questions today that was disguised as a datacenter move, it was open book/open resource and gave my SAN guy more time to troubleshoot FAStT 900 questions, also disguised as a datacenter move... And if you've been following along, I somehow got rave reviews on my 2008 R2 RDS deployment that was used for the first time Friday, w00t w00t!!! David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ________________________________ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
