Jump to content

Recommended Posts

Posted
We have just put a new server and core switch in to replace what the poor network we inherited. When we put the new core switch in we lost access to the Dell SAN as the old NM had put the SAN on this weird 192 range. All data was moved last week but typically something was missed and now we need access. Anyway i can access the SAN to get the old work back?
Posted
The SAN would be on it's own range our network is in the 10 range but the SAN is on a 192 range that connects to the hyperv servers
Posted
The SAN would be on it's own range our network is in the 10 range but the SAN is on a 192 range that connects to the hyperv servers

 

Couple of ideas i have been floating.

 

1. Change the IP in the dell storage management console.

 

2. Stick the old core switch in and plug a pc with vsphere on and then plug the old san and the old servers in and see if it picks up on the old storage server.

 

3. put a laptop on the 192 range and see if i can mount the data (not sure how to mount the san though.)

Posted

It depends how it was setup really though, like data wise is it straight off a SAN? Is it VMDKs? etc etc

 

If you have it all still I'd try to keep the old stuff separate to the new one, just plug back in the SAN/Core/Server separate to the main network and get what you want. There isn't any reason you couldn't just plug it into your new core, and setup a temporary VLAN for it etc but if it's the 192 range it's normally going to be an iscsi setup etc so you'd need to reconfigure all that which just seems more hassle than it's worth if you have a perfectly good old switch setup already. (Again if it's something like old VMware, and new hyperV would get even more fun :p)

 

Steve

Posted
It depends how it was setup really though, like data wise is it straight off a SAN? Is it VMDKs? etc etc

 

If you have it all still I'd try to keep the old stuff separate to the new one, just plug back in the SAN/Core/Server separate to the main network and get what you want. There isn't any reason you couldn't just plug it into your new core, and setup a temporary VLAN for it etc but if it's the 192 range it's normally going to be an iscsi setup etc so you'd need to reconfigure all that which just seems more hassle than it's worth if you have a perfectly good old switch setup already. (Again if it's something like old VMware, and new hyperV would get even more fun :p)

 

Steve

 

So you say plug the old san back into the old core switch. Plug the old server in and load up our storage server and it should pick up?

Posted

Well yeah I mean if nothing at all has been changed on the old san/server/switch, they should still work as fine as normal. Your new server/san/switch must be running on the new setup by the sounds of it?

 

But what I don't get unless I missed part of this is how you transferred your old data to the new SAN if it's not been connected up at once with the old and new running side by side? Or was the old san/server and new san/server all connected into the old core? Then it broke when you put the new core in?

 

Steve

Posted
Well yeah I mean if nothing at all has been changed on the old san/server/switch, they should still work as fine as normal. Your new server/san/switch must be running on the new setup by the sounds of it?

 

But what I don't get unless I missed part of this is how you transferred your old data to the new SAN if it's not been connected up at once with the old and new running side by side? Or was the old san/server and new san/server all connected into the old core? Then it broke when you put the new core in?

 

Steve

 

We put a new core and server in. We are not using the old SAN anymore and not using a SAN in the new setup. I migrated the core data before the engineers took the old core out. The issue was that there was some folders which were missed and we need access to them.

Posted

Aye in that case then should be quick job just to replug the old san/server into the old switch back in it's old ports etc, and check you can get in that way. Then depending how much data it is, either just plug external drive in etc if you don't want to change whole setup on new switch, or put a 192 port/VLAN on the new core and just do a temp uplink to the new one. (Just remember to be careful with the uplink settings if both switches are gonna be same IP etc as you only want the 192 side linked)

 

Steve

Posted
Aye in that case then should be quick job just to replug the old san/server into the old switch back in it's old ports etc, and check you can get in that way. Then depending how much data it is, either just plug external drive in etc if you don't want to change whole setup on new switch, or put a 192 port/VLAN on the new core and just do a temp uplink to the new one. (Just remember to be careful with the uplink settings if both switches are gonna be same IP etc as you only want the 192 side linked)

 

Steve

 

Think i will go with the external hard drive way on the old setup

Posted

Can you get onto the SAN management GUI?

 

If so you should be able to connect a laptop to the SAN, Mount it in iSCSI and then get the data off.

 

You may need the GUI in case any infinity groups or VLANs were configured on the SAN

Posted
Can you get onto the SAN management GUI?

 

If so you should be able to connect a laptop to the SAN, Mount it in iSCSI and then get the data off.

 

You may need the GUI in case any infinity groups or VLANs were configured on the SAN

 

Yes the PC in the server room can connect to the SAN as it shows Dell management software

Posted

Dunno not a Dell guy so not sure what their management tool is like.

 

Normally a SAN will have its own IP for management rather than through any tool

Posted

It'll say the iscsi addresses, but you'd still need to setup the laptop with the initiators and potentially vsphere if it's linked to a vmdk etc etc, thus if everything else is already setup would be a lot quicker to plug that in personally (At least you know that works 100% from before)

 

Normally it'd have the 3 addresses, 2 iscsi for each controller, potentially 4 if using MPIOs but then the management one but as you said you can get to it it's not gonna be on the 192 range

 

Steve

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...