Dell Unity 500 EMC Unity Family 5.0.8.0.5.007 Release Notes - Page 182

Internal Error Error Code:0x9881 error.

Get Dell Unity 500 PDF manuals and user guides View all Dell Unity 500 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 182 highlights

Known issues Issue Problem description number Workaround / Resolution Exists in version 970078 972002 973979 974999 975192 976994 977423 SPA (LUN owner SP) unexpectedly reboots and there is Wait for SPA (owner SP) reboot to finish a sync session with a source LUN owned by SPA and then create sync session or with I/O to created on SPB, and the session fails with "Replication create session (this will trigger trespass). Internal Error (Error Code:0x9881)" error. 4.4.0.1534750794 and later When a security hardened (STIG-enabled) array is reinitialized using a USB stick, STIG will be enabled during the re-initialization processing. The expected behavior is that STIG would no longer be enabled after the re-initialization. Workaround: To insure STIG is disabled 4.4.0.1528950819 after the USB re-initialization, disable STIG and later prior to running the re-initialization. When you create a file system named \"\', the SMB share page in the GUI does not display the proper description for the shares associated with file system named \"\' and the UEMCLI does not display the proper values for the shares associated with file system named \"\'. Do not name file system \"\". All versions When opening or deleting a locked file from an FLRenabled file system on a Windows client, sometimes there are several additional log events generated in the FLR activity log. This issue will not happen on NFS client, 4.5.0.0.5.096 and and it just generates some additional log later events, which can be seen by administrator. Ignore these log events. When automatic file locking is enabled on an FLRenabled file system, the file on the SMB share can be locked automatically, that is, the customer can find the file's state is locked by the FLR Toolkit. However, the file's mode property is not READ-ONLY though it is locked. Use the FLR Toolkit to determine whether the file is automatically locked or not on the SMB client. Do not rely on the file's READONLY mode. 4.5.0.0.5.096 and later Root FS of NAS server is inaccessible with CIFS user, leading to unsuccessful FTP login. The modification of NAS server DNS list requires a time window (about 5 seconds) to take effect. As a workaround, set the default home directory to root of a NAS server file system in FTP settings. Wait for 5 seconds and refresh GUI DNS page again. All versions 4.5.0.0.5.096 and later 979348 980000 980005 User failback many VDM replication sessions and associated file system replication sessions in parallel, sometimes some VDM sessions' failback operation will be rejected with the following error message: "Failed: Operation failed to validate the remote system connection. The time skew between the local and remote systems may be more than 10 minutes, or there is a network communication issue. (Error Code:0x650013e)" Retry to failback the VDM session after other failback operations are completed. Please do not failback more than 64 sessions in parallel. The service account can be locked after three failed login attempts when the array is security hardened; that is, STIG is enabled. If the service account is locked when the NMI button is pressed, the service account password will not be reset to the default password. Unlock the service account using the uemcli /user/account command before resetting the password. SRM user will see 'reprotect' failure and underlying VMFS unprotected. Workaround is to reboot array. 4.4.0.1528950819 and later 4.2.2.9632250 and later 4.5.0.0.5.096 and later 980007 On Unisphere GUI performance dashboard, when adding real-time performance charts for synchronous replication session destination file systems, error "Failed to setup the real time query collection for : Unknown internal metrics error has occurred. (Error Code:0x7d14013)" is displayed. Don't add real-time performance charts for synchronous replication session destination file systems. 4.5.0.0.5.096 and later 980928 After making the changes in LDAP configuration, the custom schema file ldap.conf gets regenerated with modified values but the file must not be modified. 182 Dell EMC Unity™ Family Release Notes There is no fix in this release. After changing the configuration the user needs to upload the custom schema file again so that the correct schema configuration is 4.5.0.0.5.096 and later

  • 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
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
Known issues
182
Dell EMC Unity
™
Family Release Notes
Issue
number
Problem description
Workaround / Resolution
Exists in version
970078
SPA (LUN owner SP) unexpectedly reboots and there is
a sync session with a source LUN owned by SPA
created on SPB, and the session fails with "Replication
Internal Error (Error Code:0x9881)" error.
Wait for SPA (owner SP) reboot to finish
and then create sync session or with I/O to
create session (this will trigger trespass).
4.4.0.1534750794
and later
972002
When a security hardened (STIG-enabled) array is
reinitialized using a USB stick, STIG will be enabled
during the re-initialization processing. The expected
behavior is that STIG would no longer be enabled after
the re-initialization.
Workaround: To insure STIG is disabled
after the USB re-initialization, disable STIG
prior to running the re-initialization.
4.4.0.1528950819
and later
973979
When you create a file system named \"\', the SMB
share page in the GUI does not display the proper
description for the shares associated with file system
named \"\' and the UEMCLI does not display the proper
values for the shares associated with file system named
\"\'.
Do not name file system \"\".
All versions
974999
When opening or deleting a locked file from an FLR-
enabled file system on a Windows client, sometimes
there are several additional log events generated in the
FLR activity log.
This issue will not happen on NFS client,
and it just generates some additional log
events, which can be seen by administrator.
Ignore these log events.
4.5.0.0.5.096 and
later
975192
When automatic file locking is enabled on an FLR-
enabled file system, the file on the SMB share can be
locked automatically, that is, the customer can find the
file's state is locked by the FLR Toolkit. However, the
file's mode property is not READ-ONLY though it is
locked.
Use the FLR Toolkit to determine whether
the file is automatically locked or not on the
SMB client. Do not rely on the file's READ-
ONLY mode.
4.5.0.0.5.096 and
later
976994
Root FS of NAS server is inaccessible with CIFS user,
leading to unsuccessful FTP login.
As a workaround, set the default home
directory to root of a NAS server file system
in FTP settings.
All versions
977423
The modification of NAS server DNS list requires a time
window (about 5 seconds) to take effect.
Wait for 5 seconds and refresh GUI DNS
page again.
4.5.0.0.5.096 and
later
979348
User failback many VDM replication sessions and
associated file system replication sessions in parallel,
sometimes some VDM sessions
’
failback operation will
be rejected with the following error message:
“
Failed:
Operation failed to validate the remote system
connection. The time skew between the local and
remote systems may be more than 10 minutes, or there
is a network communication issue. (Error
Code:0x650013e)
”
Retry to failback the VDM session after
other failback operations are completed.
Please do not failback more than 64
sessions in parallel.
4.4.0.1528950819
and later
980000
The service account can be locked after three failed
login attempts when the array is security hardened; that
is, STIG is enabled. If the service account is locked
when the NMI button is pressed, the service account
password will not be reset to the default password.
Unlock the service account using the
uemcli /user/account
command
before resetting the password.
4.2.2.9632250
and later
980005
SRM user will see 'reprotect' failure and underlying
VMFS unprotected.
Workaround is to reboot array.
4.5.0.0.5.096 and
later
980007
On Unisphere GUI performance dashboard, when
adding real-time performance charts for synchronous
replication session destination file systems, error "Failed
to setup the real time query collection for : Unknown
internal metrics error has occurred. (Error
Code:0x7d14013)" is displayed.
Don't add real-time performance charts for
synchronous replication session destination
file systems.
4.5.0.0.5.096 and
later
980928
After making the changes in LDAP configuration, the
custom schema file ldap.conf gets regenerated with
modified values but the file must not be modified.
There is no fix in this release. After
changing the configuration the user needs
to upload the custom schema file again so
that the correct schema configuration is
4.5.0.0.5.096 and
later