NeelSeshan
asked on
Hitachi SAN through Web browser
We have an old Hitachi 9200 DF500 Dual SAN in our network which is connected to one of AIX server.
I am not familiar with this device, I recently had the Disk Array management software installed on my system to connect to this device and by using this I changed the ipaddress of the 2 controllers of this device. I am successful in connecting through Disk array management & it seems to be fine.
But recently i found that twice the device went down connectivity with the server & i had to do a manual shutdown & restart of the device. But the device were pinging, I need to know how i could enable SSH on this device & also I need to know which port is used by this device for connecting through web browser.
I am not familiar with this device, I recently had the Disk Array management software installed on my system to connect to this device and by using this I changed the ipaddress of the 2 controllers of this device. I am successful in connecting through Disk array management & it seems to be fine.
But recently i found that twice the device went down connectivity with the server & i had to do a manual shutdown & restart of the device. But the device were pinging, I need to know how i could enable SSH on this device & also I need to know which port is used by this device for connecting through web browser.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
..
The only way to control the array, that is, to view it's settings in detail and make changes to those settings, is through the DAMP program. You can use the GUI or the CLI, but either way the DAMP program runs on *YOUR* computer. There is no telnet, no ssh, and whether or not the controllers are pingable has no bearing on if the FC ports are up and serving data to your AIX host. If you lose IP connectivity to the controller, you can't make changes with the DAMP program but your server stays up via the FC ports just fine.
You mentioned that the "device went down." The 9200 is designed for 99.999% uptime and should never go down for anything short of a catastrophic failure. If your server is losing access to the LUNs, then most likely there's a SAN design issue (i.e. single-fabric, or no redundan LUN mapping on controller) or server configuration issue (i.e. multipathing not configured). All microcode issues had been resolved years ago (around 2003 was end of life, 2007 I think was end of support)
You also speak of having to do a "manual shutdown and restart" of the device. This should *never* be required. Typically a 9200 is installed, powered-up, runs for three to five years with *no* reboots, then powered-down for de-installation. If you need to manually power-cycle your 9200 then there's something seriously wrong and it needs to be fixed before you lose your server's data.