VMware Cloud Community
vmmerlin
Hot Shot
Hot Shot
Jump to solution

EMC Celerra VSA and SRA 4.0.22 - discoverLuns fails

Hi,

During the Setup for a SRM Lab Environment, I encountered an error during the "discoverLuns" Command which is part of the Configuration of the Array Manager.

Software: vSphere 4.1, VMware-srm-4.1.0-267817, EMC_Celerra_Replicator_SRA_v4.0.22, Celerra VSA running DART 6.0.36-4 (most recent version from EMC Powerlink)

The two Celerra are running fine. They are configured for replication. The ESXi can see the Celerra iSCSI LUN.

Array Manager Software (SRA) is installed.

The two SRM Servers are configured and they can see each other. (Connection established).

If I like to configure "Array Managers", I click Add and the wizard likes to know some details. After clicking "Connect" SRM detects the Celerra. After selecting the Celerra and clicking OK, SRM tries to find replicated LUNs on the array. This is the step that fails with error message: Error while executing 'discoverLuns' command.

The SRA writes a logfile, which reveals the XML-Code of the discoverLuns command and the commands sent to the celerra:

2011-02-01 11:30:49,674 [com.emc.celerra.sra.engine.SrmTransaction]: SRM Version Registry String: HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware Site Recovery Manager
InstalledVersion    REG_SZ    4.1.0.3438
2011-02-01 11:30:49,846 [com.emc.celerra.sra.engine.SrmTransaction]: [Version=4.0.22] Begin SRM transaction: discoverLuns
2011-02-01 11:30:49,871 [com.emc.celerra.sra.engine.SrmTransaction]:
Command Input:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Command>
    <Name>discoverLuns</Name>
    <OutputFile>C:\Windows\TEMP\vmware-SYSTEM\dr-sanprovider1216-0</OutputFile>
    <ConnectSpec>
        <Name>Celerra</Name>
        <Address>10.10.20.224</Address>
        <Username>nasadmin</Username>
        <Password>**********</Password>
    </ConnectSpec>
    <ArrayId>BB005056AD377E0000-server_2</ArrayId>
    <LogLevel>trivia</LogLevel>
</Command>
2011-02-01 11:31:00,056 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Executing command:  /nas/bin/nas_version
2011-02-01 11:31:00,258 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Command result: 6.0.36-4
2011-02-01 11:31:00,263 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Executing command:  /nas/bin/nas_cel -query:IsLocal==True -format:%s -fields:CelerraID
2011-02-01 11:31:00,380 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Command result: BB005056AD377E0000
2011-02-01 11:31:00,380 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Executing command:  /nas/bin/nas_cel -interconnect -query:* -format:'%s`%s|' -fields:Name,DstMoverName
2011-02-01 11:31:00,529 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Command result: loopback`server_2|dr_to_pr`server_2|
2011-02-01 11:31:00,533 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Executing command:  /nas/bin/nas_replicate -report  -fields  id,name,remoteSystem,object,localRole,sourceMover,destinationMover,sourceStatus,destinationStatus,curTransferRateKB,curTransferTotalSizeKB,curTransferRemainSizeKB,curTransferEstEndTime,destinationFilesystem,sourceFilesystem,dartInterconnect,peerInterconnect,sourceLun,destinationLun,sourceTarget,destinationTarget -noheader
2011-02-01 11:31:00,661 [com.emc.celerra.sra.engine.net.SSHConnection]: 10.10.20.224 Command result: "fs11_T1_LUN1_BB000C29B6901B0000_fs11_T1_LUN1_BB000C29B6901B0000","iscsi_repl","2","iscsiLun","source","server_2","server_2","OK","OK","0","0","0","","","","20003","20003","1","1","iqn.1992-05.com.emc:bb005056ad377e0000-1","iqn.1992-05.com.emc:bb005056ad73620000-1"
2011-02-01 11:31:00,672 [com.emc.celerra.sra.engine.ReplicationSession]: Parsing replciation session: fs11_T1_LUN1_BB000C29B6901B0000_fs11_T1_LUN1_BB000C29B6901B0000
2011-02-01 11:31:00,673 [com.emc.celerra.sra.engine.DiscoverLuns]: com.emc.celerra.sra.exception.InvalidArrayIdException: Invalid array ID: -server_2 was supplied. in com.emc.celerra.sra.engine.SraArrayID.<init>(SraArrayID.java:41)
com.emc.celerra.sra.engine.ReplicationSession.setRemoteArrayId(ReplicationSession.java:338)
com.emc.celerra.sra.engine.ReplicationSession.<init>(ReplicationSession.java:127)
com.emc.celerra.sra.engine.parser.ReplicationProperties.getRepV2Sessions(ReplicationProperties.java:151)
com.emc.celerra.sra.engine.Collector.getReplicationSessions(Collector.java:413)
com.emc.celerra.sra.engine.DiscoverLuns.buildResponse(DiscoverLuns.java:87)
com.emc.celerra.sra.engine.DiscoverLuns.<init>(DiscoverLuns.java:60)
com.emc.celerra.sra.engine.SrmTransaction.beginSrmTransaction(SrmTransaction.java:139)
com.emc.celerra.sra.engine.SrmTransaction.<init>(SrmTransaction.java:63)
com.emc.celerra.sra.Main.main(Main.java:81)

2011-02-01 11:31:00,710 [com.emc.celerra.sra.engine.DiscoverLuns]:
DiscoverLuns Output:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Response>
    <ReturnCode>4</ReturnCode>
</Response>
2011-02-01 11:31:00,710 [com.emc.celerra.sra.engine.SrmTransaction]: End SRM transaction

The blue line indicates the error. It seems, that the SRA has an error in parsing the response from the previously executed command "/nas/bin/nas_replicate". It also seems, that only the Celerra ID from the remote (recovery site) Celerra is missing. In my case the remote Array ID should be "BB005056AD73620000-server_2" instead of "-server_2".

Unfortunately I cannot edit the Java-Byte Code (the SRA is written in Java, the Perl "command.pl" is used to start the java program with XML Input).

Any suggestions?

Thank you!

Reply
0 Kudos
1 Solution

Accepted Solutions
Sittichai
VMware Employee
VMware Employee
Jump to solution

Hi

Has your problem been solved?

I just setup my SRM lab using the same SRA version.

I initially had the same problem but that because I changed my data mover name from default "server_2" to "vsa01-server_2".

The problem is gone after changing the name back to server_2.

I searched EMC powerlink and found  an issue with older SRA version regarding the name of interconect cannot contain '_'.

From your log, the name of interconnect is 'dr_to_pr'.

You might want to try to change it to "dr-to-pr'.

View solution in original post

Reply
0 Kudos
1 Reply
Sittichai
VMware Employee
VMware Employee
Jump to solution

Hi

Has your problem been solved?

I just setup my SRM lab using the same SRA version.

I initially had the same problem but that because I changed my data mover name from default "server_2" to "vsa01-server_2".

The problem is gone after changing the name back to server_2.

I searched EMC powerlink and found  an issue with older SRA version regarding the name of interconect cannot contain '_'.

From your log, the name of interconnect is 'dr_to_pr'.

You might want to try to change it to "dr-to-pr'.

Reply
0 Kudos