Error: Command already active - Mapping failed

[Dermot1]

Hello,

Vendor Name: HP StorageWorks
Product ID: P2000 G3 FC
Product Brand: MSA Storage
SCSI Vendor ID: HP
SCSI Product ID: P2000 G3 FC
Enclosure Count: 2

I cannot give any hosts access to any volumes. Whenever I try the `map volume` command I get

# map volume access rw lun 5 host 500143800566a0f0 sftp-vdb
Error: Command already active. (sftp-vdb) - Mapping failed. Host 500143800566a0f0 was not mapped for volume sftp-vdb.

Error: Command failed. () - At least one of the volumes was not mapped successfully.

Error: Command failed. (sftp-vdb) - Mapping failed. Host 500143800566a0f0 was not mapped for volume sftp-vdb.

It does not seem to matter what volume or what host, I get the same error.  If I try the `unmap volume` command I get the same message too.

Does anyone know what this error means or how I might find what command is already active?

Thanks in advance,

Dermot

[SUBHAJIT KHANBARMAN_1]

@Dermot1 

Did you tried from SMU (GUI mode) ?

Is there any volume successfully presented before in this system to any hosts ever ?

You better check if Host details are correct or not. You try to change Host name and then present volume.

You can check below outputs,

show hosts

show host-maps

show volume-maps

show system

show unwritable-cache

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

*************************************************************************

[Dermot1]

Hi,

I've tried this from the web UI and from the CLI.

There is one volume that reports itself as un-mapped but is present on a host.

Version:TS230P007
# show hosts
Host ID           Name     Discovered Mapped Profile   Host Type
-----------------------------------------------------------------
500143801874e216  polaris  Yes        Yes    Standard  FC
500143801874e21c  proxima  Yes        Yes    Standard  FC
10000090fab3f699  pollux   Yes        Yes    Standard  FC
500143800566a0f0  canopus  No         Yes    Standard  FC
10000000c959ebba  helios   No         Yes    Standard  FC
10000000c966faa5  antares  No         Yes    Standard  FC
10000090fab3f3c1           No         Yes    Standard  FC
-----------------------------------------------------------------
Success: Command completed successfully.

The host I am concerned with is `canopus`. It is showing as not-discovered! All my mapping are showing as empty

Host View [ID (500143801874e216) Name (polaris) Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------

Host View [ID (500143801874e21c) Name (proxima) Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------

Host View [ID (10000090fab3f699) Name (pollux) Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------

Host View [ID (500143800566a0f0) Name (canopus) Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------

Host View [ID (10000000c959ebba) Name (helios) Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------

Host View [ID (10000000c966faa5) Name (antares) Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------

Host View [ID (10000090fab3f3c1) Name () Profile (Standard) ] Mapping:
   Name Serial Number                    LUN   Access       Ports
   ---------------------------------------------------------------


Success: Command completed successfully.

Also note that I have had to do a power-cycle on this system down. See this thread for details.

# show unwritable-cache
Error: Unable to communicate with Storage Controller. Please retry the command.

The last command fails repeatedly.

Dermot

[SUBHAJIT KHANBARMAN_1]

@Dermot1 

First of all your P2000 running with expired or inactive firmware TS230P007 which is almost 20 versions old. The latest firmware is TS252P005. Please check the below link and go to last Tab which is P2000 G3,

https://h41111.www4.hpe.com/storage/msafirmware.html

It's impossible to troubleshoot controllers or predict behavior because of 20 version old firmware. There could be so many reasons and it's impossible to go thorugh all 20 firmware release notes manually and match this behaviour and look for the fix.

Regarding your concern about Host "canopus" or other two hosts named "helios" and "antares" shows Discovered as "No" which means someone manually created this Host entry. However for host named "polaris" and "proxima" got discovered automatically because of SAN Switch zoning.

My suggestion would be to properly shutdown the MSA and then wait for sometime so that all drives will be spun down. Then power it up. Refer section "Power cycle" in SMU guide for more details. Don't just unplug the power cable and re-plug it. That's not the way.

If still you get same result and you are sure that you have successfully mapped volumes earlier to couple of hosts and you did transaction as well then stop Host IO and disconnect all hosts from this MSA. Then update firmware for all components of the MSA. Then reconnect back all hosts and check.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

*************************************************************************

[Dermot1]

Thanks for the advice. I have already asked my reseller to try and find me a support agreement so I can update the firmware. I will chase him again.

[Dermot1]

For the suggestion to shutdown, I have a job to expand a vdisk, that has been running for days but is stuck at 0%. I suspect it will prevent a clean shutdown. Is there a way to abort that job?

Thanks,

Dermot

Moderator Edit: Post edited and removed the Serial Number for Privacy. 

[SUBHAJIT KHANBARMAN_1]

@Dermot1 

Any activity to try in this system can produce uneven behavior because of inactive very old firmware in controllers.

Hope you have followed all best practices before start of vdisk expansion like data backup otherwise vdisk expansion can't be stopped, it can only be deleted, recreated and restore from backup.

You can try restarting management controller of Controller B and check if the vdisk expansion can restart again.

# restart mc b

If still same issue persists, then go for Storage controller restart of B,

# restart sc b

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

***********************************************************************************