HP XP24000 HP Replication Adapter for VMware vCenter Site Recovery Manager Adm - Page 45

RAID Manager command errors in rmsra20.exe

Get HP XP24000 PDF manuals and user guides View all HP XP24000 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

1301 : [RMSRA20][Time]: [command_main] : XML length over -> [ XML parameter strings ... ]. Cause: A parameter in XML was input from SRM to the SRA, but it exceeds the defined length for the SRA specification. Action: Confirm that SRM was passed appropriate parameters in XML from the SRM log message. 1302: 1303 : [RMSRA20][Time]: [command_main] : Parameter in XML was NOT enough Cause: A parameter in XML was input from SRM to the SRA, but it could not be found in any parameters. Action: Confirm that SRM was passed appropriate parameters in XML from the SRM log message. 1304 : [RMSRA20][Time]: [command_discoverDevices] : NO ArrayId or NO PeerArrayId in XML. Cause: A parameter in XML (discoverDevices) was input from SRM to the SRA, but it could not be found in the array ID. Action: Confirm that SRM was passed an Array ID parameter in XML (discoverDevices) from the SRM log message. 1305 : [RMSRA20][Time]: [command_naming] : NO ArrayId or NO DeviceKey and GroupKey in XML. Cause: A parameter in XML (naming) was input from SRM to the SRA, but it could not be found in the TargetDevice Key (LDEV# of CA_SVOL), or Target Group Key (dev_group in HORCM). Action: Confirm that SRM was passed TargetDevice Key parameter in XML (naming) from the SRM log message. 1305 : [RMSRA20][Time]: [command_naming] : NO ArrayId or NO PeerArrayId or NO DeviceKey and GroupKey in XM. Cause: A parameter in XML (naming) was input from SRM to the SRA, but it could not be found in SourceDevice ID (LDEV# of CA_SVOL), or Consistency Group ID (dev_group in HORCM). Action: Confirm that SRM was passed SourceDevice ID parameter in XML (naming) from the SRM log message. 1306 : [RMSRA20][Time]: [command_naming] : Unsupported command 'command naming' in XML. Cause: A command name was input from SRM to the SRA, but it could not be supported. Action: Confirm that SRM was passed an appropriate command name in XML from the SRM log message. 1251 : [RMSRA20][Time]: [command_main] : Can't be connected to HORCMINST=X@... with error(0x000000fc). Cause: A connection address in XML was input from SRM to the SRA, but it could not be found HORCM instance #X. Action: Confirm that the HORCM instance# is running , or that a connection address (IPaddress), specified in the configuration of Array Manager, is appropriate. RAID Manager command errors in rmsra20.exe 1307 : [RMSRA20][Time]: [" XML OUTPUT file name"] : fopen : "system error message" Cause: A parameter in XML was input from SRM to the SRA, but it could not be created as an XML OUTPUT file name. Error Messages on SRM log files 45

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
1301 : [RMSRA20][Time]: [command_main] : XML length over –> [ XML parameter strings
… ].
Cause:
A parameter in XML was input from SRM to the SRA, but it exceeds the defined length for
the SRA specification.
Action:
Confirm that SRM was passed appropriate parameters in XML from the SRM log message.
1302: 1303 : [RMSRA20][Time]: [command_main] : Parameter in XML was NOT enough
Cause:
A parameter in XML was input from SRM to the SRA, but it could not be found in any
parameters.
Action:
Confirm that SRM was passed appropriate parameters in XML from the SRM log message.
1304 : [RMSRA20][Time]: [command_discoverDevices] : NO ArrayId or NO PeerArrayId
in XML.
Cause:
A parameter in XML (discoverDevices) was input from SRM to the SRA, but it could not be
found in the array ID.
Action:
Confirm that SRM was passed an Array ID parameter in XML (discoverDevices) from the
SRM log message.
1305 : [RMSRA20][Time]: [command_naming] : NO ArrayId or NO DeviceKey and
GroupKey in XML.
Cause:
A parameter in XML (naming) was input from SRM to the SRA, but it could not be found in
the TargetDevice Key (LDEV# of CA_SVOL), or Target Group Key (dev_group in HORCM).
Action:
Confirm that SRM was passed TargetDevice Key parameter in XML (naming) from the SRM
log message.
1305 : [RMSRA20][Time]: [command_naming] : NO ArrayId or NO PeerArrayId or NO
DeviceKey and GroupKey in XM.
Cause:
A parameter in XML (naming) was input from SRM to the SRA, but it could not be found in
SourceDevice ID (LDEV# of CA_SVOL), or Consistency Group ID (dev_group in HORCM).
Action:
Confirm that SRM was passed SourceDevice ID parameter in XML (naming) from the SRM
log message.
1306 : [RMSRA20][Time]: [command_naming] : Unsupported command 'command naming'
in XML.
Cause:
A command name was input from SRM to the SRA, but it could not be supported.
Action:
Confirm that SRM was passed an appropriate command name in XML from the SRM log
message.
1251 : [RMSRA20][Time]: [command_main] : Can't be connected to HORCMINST=X@…
with error(0x000000fc).
Cause:
A connection address in XML was input from SRM to the SRA, but it could not be found
HORCM instance #X.
Action:
Confirm that the HORCM instance# is running , or that a connection address (IPaddress),
specified in the configuration of Array Manager, is appropriate.
RAID Manager command errors in rmsra20.exe
1307 : [RMSRA20][Time]: [“ XML OUTPUT file name”] : fopen : “system error message”
Cause:
A parameter in XML was input from SRM to the SRA, but it could not be created as an XML
OUTPUT file name.
Error Messages on SRM log files
45