Domain Controller Down (VM)
-
@Dashrender unsure of the IP of that host. It has nothing running on it typically, but I can just assume that.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender unsure of the IP of that host. It has nothing running on it typically, but I can just assume that.
Assumptions are the mother of all *(&)&-ups.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender unsure of the IP of that host. It has nothing running on it typically, but I can just assume that.
Or it is running the replicas and shit is semi up right now.
This is important.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender unsure of the IP of that host. It has nothing running on it typically, but I can just assume that.
Hit what you think it might be on 443, you should be greeted with the ESXi landing page.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender unsure of the IP of that host. It has nothing running on it typically, but I can just assume that.
In that case do the webex with John - NOW he can look through you system and help yo ufind the IPs of that server and make sure it's not running over there.
assuming it's part of this cluster -
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
-
FYI, John works for VMWare
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
You're welcome!
-
Well and with that I'm going to drive home.
I'll hope back on from there.Ciao.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
This is the reason we all like and are part of ML.
-
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
You would have been here a lot sooner had you told people to go away and leave you alone. the time gaps in this thread are telling.
-
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
You would have been here a lot sooner had you told people to go away and leave you alone. the time gaps in this thread are telling.
He would've been here even sooner had he rebooted hours ago rather than waiting...
-
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
You would have been here a lot sooner had you told people to go away and leave you alone. the time gaps in this thread are telling.
He would've been here even sooner had he rebooted hours ago rather than waiting...
True, but that is dangerous. he could have lost a lot more because we did not even know there was a SAN involved.
-
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
You would have been here a lot sooner had you told people to go away and leave you alone. the time gaps in this thread are telling.
He would've been here even sooner had he rebooted hours ago rather than waiting...
True, but that is dangerous. he could have lost a lot more because we did not even know there was a SAN involved.
That is true, when did the SAN discovery come to light, I had to head out for a bit. I did see it, just didn't correlate a time frame to it.
-
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@DustinB3403 said in Domain Controller Down (VM):
@JaredBusch said in Domain Controller Down (VM):
@wirestyle22 said in Domain Controller Down (VM):
@Dashrender I am. Thanks everyone. You guys really banded together to help me. I really really appreciate it.
You would have been here a lot sooner had you told people to go away and leave you alone. the time gaps in this thread are telling.
He would've been here even sooner had he rebooted hours ago rather than waiting...
True, but that is dangerous. he could have lost a lot more because we did not even know there was a SAN involved.
That is true, when did the SAN discovery come to light, I had to head out for a bit. I did see it, just didn't correlate a time frame to it.
Not until after the switch was rebooted, which was after the host was rebooted.
-
Thanks to @John-Nicholson for the help! A lot of great information.
-
@wirestyle22 said in Domain Controller Down (VM):
Thanks to @John-Nicholson for the help! A lot of great information.
The problem is now that we stepped up to help a member of our community and the bosses know nothing of how much this should have cost you to get repaired.
-
Looks like an ipod... This is going to be interesting in the long term. Those Cisco chassis can do some expending though so you may be able to get to a more reliable system with what you have.
-
@coliver said in Domain Controller Down (VM):
Looks like an ipod... This is going to be interesting in the long term. Those Cisco chassis can do some expending though so you may be able to get to a more reliable system with what you have.
Not looks. Is.
-
@wirestyle22 said in Domain Controller Down (VM):
@John-Nicholson
I am definitely interested in any education you are willing to offer but I think we are actually almost finished with this currently. Are you willing to sit with me for literally any amount of time tomorrow? I am a very eager learner.
A bit tied up with prep for VMworld Barcelona but might find a few minutes to talk.
One thing is as soon as humpty is back together again is run RVTools against the vCenter. Get a XLS dump. The health tab on the end will find all kinds of fun misconfigurations but I can go over it with you (or if you can sanitize it and post it hear I can give you a tear down).
Next up your on essentials Plus. You can have 24/7 production support, use it. GSS likes to help.
100Mbps switching is NOT supported for storage or vMotion.
Get some real storage. [email protected] can help you get a small FC DAS HUS with good support to avoid a lot of this mess.Upgrade to the VCSA (use the migrate2VCSA tool!), and 6.x ESXi. ESXi 5.1 is not in general support anymore as of last week or so.
Before you do that upgrade the BIOS/FIrmware on those UCS boxes.
Fix the NTP serve config to start the service, and make sure to have 3 (not 2!) NTP servers so you can fix drift.
Get into the UCS CIMC (Set that up!) and fix the clocks if needed.Get a pair of cheap but fast/good TOR 1Gbps switches. ICX 6450's Brocade's are solid, speak proper RSTP, and fast enough to handle iSCSI for the migration, and vMotion once done.
Get Veeam for backups. Possibly beef up the backup storage.
Replace that Gen6 HP. Its out of support, and unsupportable.Don't worry a lot on resource balance, your CPU and memory usage are good and those cisco hosts (M3's) are current enough. Check the smartness' on them though, and get CIMC alerting setup.
All in FC, labor (week at 10K) Host, migration of a few VM's Veeam setup, small host, switches, upgrade, your looking 50-60K?
Still got other challenges (banish 2003, get VDI deployed, replace campus switching) but I'd give Howard a ring. He's seen worse I promise...
Other people to talk to if your in the SW, Sigma (Nigel Hickey's a good guy there). Does a lot of VDI work.
