Dell PowerStore 5200T EMC PowerStore Release Notes for PowerStore OS Version 3 - Page 23

Operating Normally status. Admins should, Data Protection

Page 23 highlights

Issue ID MDT-242915 MDT-220994 MDT-133408 MDT-333618 MDT-362662 MDT-362070 MDT-289908 MDT-286236 MDT-263147 MDT-190232 MDT-117061 Functional Area Description Workaround/Resolution Data Protection Data Protection Data Protection Discovery Hardware Hardware Hardware Hardware Hardware Hardware Hardware When replication destination cluster loses connectivity to source cluster, the system issues specific alerts/events, but the state of the replication session may still display Operating Normally status. Admins should check the alerts issued by the remote system and resolve the connectivity issues to recover replication sessions. The replication session may not be deleted once a Protection Policy is unassigned from the storage resource. When a volume group is created with member volumes and is protected by a protection policy that includes a replication rule, the volume group members may be delayed in being replicated to the remote system until the next RPO cycle. The default replication rule RPO value in PowerStore Manager is one hour, but it can range from five minutes to 24 hours. In certain network environment configurations, the system is unable to discover unconfigured appliances through the network when using static IP addresses for appliance discovery. A node may remain powered down after a reboot and require another reboot. After a dual node reboot, if one node comes up 120 seconds before the other node, the first node may reboot again to start autorecovery. A newly inserted disk remains locked, and the rebuild of the PowerStore appliance times out. In rare cases, a node that has been powered off does not remain powered off. If you add an appliance to a cluster when another appliance in the cluster is powered off, the add appliance operation will fail. The "svc_node shutdown" script may reboot the node instead of powering it off. When beginning cluster creation, the hardware status is incorrectly indicated as not configured for clustering. None To delete the replication session, do the following: 1. If Protection Policy is not assigned to the storage resource, reassign the same Protection Policy that was previously assigned to the storage resource. 2. Unassign the Protection Policy from the storage resource. If the remote system connection is healthy, the member volumes should automatically be replicated to the destination during the next RPO cycle. To update the member volumes on the destination before the next RPO cycle, navigate to Protection-> Replication, select the volume group session and perform a "Synchronize" operation. The initial discovery of PowerStore appliances will work with either the native Zeroconf-capable browser such as Bonjour or through the PowerStore Discovery Tool. Reboot the halted node again. None Restart the node. Power off the node again. None Run the "svc_node shutdown" script again when the node has finished rebooting. Wait a few minutes and try again. Known Issues 23

  • 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

Known Issues
23
Issue ID
Functional Area
Description
Workaround/Resolution
MDT-242915
Data Protection
When replication destination cluster loses
connectivity to source cluster, the system
issues specific alerts/events, but the state of
the replication session may still display
Operating Normally status. Admins should
check the alerts issued by the remote
system and resolve the connectivity issues
to recover replication sessions.
None
MDT-220994
Data Protection
The replication session may not be deleted
once a Protection Policy is unassigned from
the storage resource.
To delete the replication session, do the
following:
1. If Protection Policy is not assigned to
the storage resource, reassign the same
Protection Policy that was previously
assigned to the storage resource.
2. Unassign the Protection Policy from the
storage resource.
MDT-133408
Data Protection
When a volume group is created with
member volumes and is protected by a
protection policy that includes a replication
rule, the volume group members may be
delayed in being replicated to the remote
system until the next RPO cycle. The default
replication rule RPO value in PowerStore
Manager is one hour, but it can range from
five minutes to 24 hours.
If the remote system connection is
healthy, the member volumes should
automatically be replicated to the
destination during the next RPO cycle. To
update the member volumes on the
destination before the next RPO cycle,
navigate to Protection-> Replication,
select the volume group session and
perform a "Synchronize" operation.
MDT-333618
Discovery
In certain network environment
configurations, the system is unable to
discover unconfigured appliances through
the network when using static IP addresses
for appliance discovery.
The initial discovery of PowerStore
appliances will work with either the native
Zeroconf-capable browser such as Bonjour
or through the PowerStore Discovery
Tool.
MDT-362662
Hardware
A node may remain powered down after a
reboot and require another reboot.
Reboot the halted node again.
MDT-362070
Hardware
After a dual node reboot, if one node comes
up 120 seconds before the other node, the
first node may reboot again to start auto-
recovery.
None
MDT-289908
Hardware
A newly inserted disk remains locked, and
the rebuild of the PowerStore appliance
times out.
Restart the node.
MDT-286236
Hardware
In rare cases, a node that has been powered
off does not remain powered off.
Power off the node again.
MDT-263147
Hardware
If you add an appliance to a cluster when
another appliance in the cluster is powered
off, the add appliance operation will fail.
None
MDT-190232
Hardware
The “svc_node shutdown” script may reboot
the node instead of powering it off.
Run the “svc_node shutdown” script again
when the node has finished rebooting.
MDT-117061
Hardware
When beginning cluster creation, the
hardware status is incorrectly indicated as
not configured for clustering.
Wait a few minutes and try again.