Domain Controller Down (VM)

wirestyle22

Alright, so I'm going to need to fix some DNS issues which I think @JaredBusch informed me of yesterday. When I perform nslookup on my file server and printer server it kicks back an error stating:

DNS request timed out.
Default Server: Unknown
Address: 192.168.10.16 <-- IP of my domain controller (2003)

scottalanmiller

@dafyre said in Domain Controller Down (VM):

@Dashrender said in Domain Controller Down (VM):

@wirestyle22 inherited that nightmare.

This is true... But getting some training is rarely a bad thing. 8-)

I agree. Training and documentation are key once this fire is fully out.

hobbit666

WOW it's taken me most of the afternoon to get through all that thread! No back to the normal threads...........hold one it's home time

scottalanmiller

@hobbit666 said in Domain Controller Down (VM):

WOW it's taken me most of the afternoon to get through all that thread! No back to the normal threads...........hold one it's home time

You made it through?

BRRABill

@hobbit666 said in Domain Controller Down (VM):

WOW it's taken me most of the afternoon to get through all that thread! No back to the normal threads...........hold one it's home time

Man you'll be BURIED if you stay away all weekend!

scottalanmiller

@BRRABill said in Domain Controller Down (VM):

@hobbit666 said in Domain Controller Down (VM):

WOW it's taken me most of the afternoon to get through all that thread! No back to the normal threads...........hold one it's home time

Man you'll be BURIED if you stay away all weekend!

NO kidding.

Dashrender

I miss 90% of the stuff that's written on the weekends.

scottalanmiller

@Dashrender said in Domain Controller Down (VM):

I miss 90% of the stuff that's written on the weekends.

That's the one time I normally keep up best.

Dashrender

@wirestyle22
Things to do.
Replace the core switch with 1 GB or better
Fix DHCP so it gives out two DNS hosts
Make sure both (or more) DNS servers are working/syncing

Dashrender

@scottalanmiller said in Domain Controller Down (VM):

@Dashrender said in Domain Controller Down (VM):

I miss 90% of the stuff that's written on the weekends.

That's the one time I normally keep up best.

Less normal daily work I'm guessing for you. I'm just not on the computer or phone much on the weekends.

DustinB3403

So what was the status of this from yesterday?

IPOD
VM Restored and powers on
Still having DNS/DHCP issues?

scottalanmiller

@Dashrender said in Domain Controller Down (VM):

@wirestyle22
Things to do.
Replace the core switch with 1 GB or better
Fix DHCP so it gives out two DNS hosts
Make sure both (or more) DNS servers are working/syncing

Document everything.
Replace the SAN.

Dashrender

@scottalanmiller said in Domain Controller Down (VM):

@Dashrender said in Domain Controller Down (VM):

@wirestyle22
Things to do.
Replace the core switch with 1 GB or better
Fix DHCP so it gives out two DNS hosts
Make sure both (or more) DNS servers are working/syncing

Document everything.
Replace the SAN.

Replace, or re-engineer the storage?

DustinB3403

@scottalanmiller said in Domain Controller Down (VM):

@Dashrender said in Domain Controller Down (VM):

@wirestyle22
Things to do.
Replace the core switch with 1 GB or better
Fix DHCP so it gives out two DNS hosts
Make sure both (or more) DNS servers are working/syncing

Document everything.
~~Replace~~ Remove the SAN.

FTFY

JaredBusch

@DustinB3403 said in Domain Controller Down (VM):

~~Replace~~ Remove the SAN.

No, that is not the correct solution.

scottalanmiller

@Dashrender said in Domain Controller Down (VM):

@scottalanmiller said in Domain Controller Down (VM):

@Dashrender said in Domain Controller Down (VM):

@wirestyle22
Things to do.
Replace the core switch with 1 GB or better
Fix DHCP so it gives out two DNS hosts
Make sure both (or more) DNS servers are working/syncing

Document everything.
Replace the SAN.

Replace, or re-engineer the storage?

Well the issue with that is that it's a major change. That's a great idea, but it's a major change and one he is not prepared to do. Replacing the SAN is a drop in replacement and he could move from a device that isn't plausible to use in a scenario like this to one that is. It's a huge amount of money, but that's a spend that they committed to before he was there. Moving to an HDS, EMC, 3PAR or Nimble is a drop in change that would fix a lot of things.

Dashrender

@scottalanmiller said in Domain Controller Down (VM):

... but that's a spend that they committed to before he was there.

it's a plan that the previous IT was committed to. Management only because they were probably sold a bill of goods because they put their trust in the wrong person. But we don't actually know any of those details.

hobbit666

@scottalanmiller said in Domain Controller Down (VM):

Moving to an HDS, EMC, 3PAR or Nimble is a drop in change that would fix a lot of things.

I'm interested in hearing why these would make a good alternative to the SAN and IPOD?

prcssupport

@hobbit666 said in Domain Controller Down (VM):

@scottalanmiller said in Domain Controller Down (VM):

Moving to an HDS, EMC, 3PAR or Nimble is a drop in change that would fix a lot of things.

I'm interested in hearing why these would make a good alternative to the SAN and IPOD?

I have read this entire thread (albeit over a lot of time) I don't know the piece of equipment "IPOD" as it is referenced in this thread. I figure it is not an Apple device. Could someone clarify?

DustinB3403

@prcssupport said in Domain Controller Down (VM):

@hobbit666 said in Domain Controller Down (VM):

@scottalanmiller said in Domain Controller Down (VM):

Moving to an HDS, EMC, 3PAR or Nimble is a drop in change that would fix a lot of things.

I'm interested in hearing why these would make a good alternative to the SAN and IPOD?

I have read this entire thread (albeit over a lot of time) I don't know the piece of equipment "IPOD" as it is referenced in this thread. I figure it is not an Apple device. Could someone clarify?

An IPOD is an architectural system design. Where you have 1 storage node (usually a SAN) and two servers. The entire setup is configured so that the servers sit up at the top, with no storage capabilities, and the SAN at the bottom.

Often the two servers are connected together with two switches and then the servers are connected to the single SAN.

The term IPOD means Inverted Pyramid of Doom, the term refers to the fact that if the connection to the SAN or the SAN its self goes belly up, you lose all functionality of the system.

It's a commonly sold design because it has huge profit margins, two compute only servers, the switches, and the SAN.