Jump to content

Recommended Posts

Posted

hello everyone

 

I have inherited a network and for the life of me cannot find the management IP of the SAN

i believe its a HP MSA 2040

The servers connect to the ISCSI port on 192.168.20.253 and 192.168.20.252

but

 

There are no vlans on the switches

the switches are all on the same LAN (yes i know)

the SAN is plugged into the switch via 2 x 10GB DAC and 2 x 1GB ethernets

 

any ideas? i have scanned the network for ports 20,21,22,23,80,443 and still cannot find this san ?

Posted

there are no DHCP reservations :-( (this network needs a bit of work doing)

nmap doesn't show it.

 

the only assumption i can think of its been put on a sperate IP/subnet without using vlans

Posted
Have you tried using superscan? Worked great for me when i took over and the chaps had static IPs with no documentation [emoji20]
Posted

If its similar to our HP MSA 2000, you can also connect to it via a USB console cable and use Putty to connect and find these out.

 

I had to do that when we switched our ranges and had to get them an allocation on the new DHCP as it went a bit wrong, I had to console in and then reset the two management network adapters using the CLI on our unit.

Posted (edited)

We have just installed a new MSA2040 and ran into the same issue.

 

You need to just look in the DHCP Address Leases as both controllers will be listed as 'HP_MSA20xx' in there.

 

P.S. You might need to Putty in to the unit and restart the management service on the controllers.

Edited by Gardinho
Posted

There is not DHCP res starting HP_*

 

i see the micro USB now on the back , do i need a special micro usb to usb cable/com port adaptor

Posted (edited)

It is likely that your san will be static addressed so wont show up in dhcp.

Try angry ip to scan for live ip's then it will be a matter of process of elimination. If you can narrow down the ip range as much as you can it will reduce the labour of checking every ip that it returns.

 

Assuming once you find the ip you have the credentials to log on to it. Good luck

Edited by dapaulio
Posted

If you can narrow down the ip range as much as you can it will reduce the labour of checking every ip that it returns.

If you get the portscanner to just check the port that you are looking for it will speed things up immensely. nmap will do this.

Posted (edited)
I'm sure OP mentioned somewhere nmap didnt work for him

 

yes I see that now. If it is on a network then nmap will find it, given the correct options.

 

* caveat being the management interface has to be plugged into the same network!

Edited by CyberNerd

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...