MSA2000 Cannot contact Web or CLI

[Matt_HS]

I've an SA MSA2000 which I'm unable to connect to.
Have read about default addresses being 10.0.0.2 and .3 but get no response from these.
I have a network in the service port.
DHCP hasn't issued any address either.
I have an AJ808A controller (one).
Also tried via CLI with hyper terminal but again nothing. All lights on the back.
Really struggling with lack of information anywhere.
Any ideas??!!

[Johan Guldmyr]

To the CLI - which bit rates etc did you use?

http://h30499.www3.hp.com/t5/Disk-Array/How-to-connect-onto-the-MSA-2000-model-2012fc/m-p/4192647#M26990

For which ones should work.

The normal reference guide confirmst hat 10.0.0.2 and 10.0.0.3 is the right one.
The host you are trying to access them from, is that in 10.0.0.0/255.255.255.0 subnet?

Links here:

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual〈=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=12169&prodSeriesId=3758996

Has the addresses of the management port been changed maybe?

[Lesley Persyn]

When you tried with CLI, it was connected with the special serial cable?

I have a similar issue i can't reach it anymore through ip. no telnet/webpage...
cli serial works.

[Johan Guldmyr]

Oh yeah, that's a good one - hope you kept the one that should have come with the MSA :)

[Matt_HS]

Yes, I have used the provided cable and also been in the correct adddress range.

[Johan Guldmyr]

Has it ever worked?

Do you know if the machine you are connecting from can connect via serial to something else?

Have you tried to restart/reboot/reseat controller and see if anything happens via the serial interface?

[Matt_HS]

Hi, no I have never connected, only now becoming pressing as looking to configure!

[Johan Guldmyr]

Ok.

The lights on the back that are on - any error lights? Maybe you can try the controller in the other slot?

Have you contacted hp support?

[Matt_HS]

No error lights.
Good shout about tring controller in the other slot.
I'mm in touch with HP, but so far just the basics already gleaned from forums and from googling the issue.
It now appears I have connected via Hyper terminal ans set network-paramterers as it states "Success: Command completed successfully - Network parameters were changed. However, I cannot ping the address I have set. I will try rebooting.

[Johan Guldmyr]

How are you connecting to the MSA controller? By a laptop or through a switch? Maybe the problem is on one of them.

[Matt_HS]

The good news is I have connected.
After installing HyperTerminal through windows (was previously using a downloaded version as didn't have server disks to install) I was able to connect and receive a prompt.
Tried to set the ip address and was told "command completed successfully - network parameters changed". However, this was not the case as I was setting for a non present Controller A as opposed to my Controller B. Seems strange that I wouldn't get an error message if there is no A present.
Anyway, using show network-parameters, I got the following:

Network Parameters Controller A
-------------------------------
IP Address: Not Present
Gateway: Not Present
Subnet Mask: Not Present
MAC Address: Not Present
Addressing Mode: Not Present

Network Parameters Controller B
-------------------------------
IP Address: 10.0.15.153
Gateway: 10.0.0.1
Subnet Mask: 255.255.0.0
MAC Address: 00:C0:FF:DA:C7:83
Addressing Mode: Manual

Strange thing is the address for Controller B. Where did that come from? States Manual.

Anyway, from here I reassigned to my preferred address, could ping and connect via the web interface.

I'm now moving on to look to configure correctly for VMWare and will post in another thread for this.

Ultimately, my problem was 1) HyperTerminal program & 2) Controller A attempting to be configured instead of B and 3)The question of where the manual address for B had come from - still a mystery.

Thank you for the replies

Matt

[Johan Guldmyr]

Good work matt !
Was it brand new? Maybe your reseller/supplier tested it before sending it to you. Or maybe a mistake from factory.

It's possible to close threads when they've been resolved.

[Matt_HS]

Johan,

I think you're right with regards to the reseller testing or setting the address!

Anyway, now on to the configuring!

Thanks again for your input, much appreciated,

Matt

[Matt_HS]

The solutions / issues have been detailed in earlier posts.