EMC AX100i Release Notes - Page 19

Navisphere Express problems fixed in version 02.19.100.5.018, Navisphere Express problems fixed - ax100 sp

Page 19 highlights

Fixed problems A thread deadlock within Navisphere Express is being caused by a thread not releasing a lock during an error situation. This will cause Navisphere Express to hang. The only remedy is to reboot the SP. Frequency: Rarely under a rare set of circumstances. [141362] Locking is now done through objects that release locks based on scope and that do not require all code paths to correctly release the lock Navisphere Express problems fixed in version 02.19.100.5.018 Problem Details The Dismiss button for the Attention Required message: A Hot Spare is currently not allocated on the storage system. Creation of a Hot Spare is highly recommended. does not work correctly. Selecting the Dismiss button will not remove the display of this message. [127711] Navisphere Express will now accept the Dismiss button and remove the display of the Attention Required for Hot Spare message. A memory leak within Navisphere Express may cause an SP to be unmanaged or for operations to start failing. Navisphere Express should return to normal operation within a few minutes. [129228] Fixed the memory leak. Sometimes Navisphere Express will hit its connection limit and not allow any additional connections. [130535] Connections are now shut down correctly when a user exits the browser running Navisphere Express. This stops the application from hitting its connection limit. Navisphere Express problems fixed in version 02.19.100.5.014 Problem Details Incorrect use of a system API within Navisphere Express may cause an SP to be unmanaged or operations to start failing. If the situation does not recover in a few minutes, the only solution is to reboot the SP. [129924] Call the correct system API to avoid getting stuck during shutdown. The string "0x" is being added to the beginning of all event codes sent through event monitor's email notification service. [131913] Fixed event monitor to no longer add "0x" to the event codes. EMC AX100-Series Integrated Management Software Release Notes 19

  • 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

19
Fixed problems
EMC AX100-Series Integrated Management Software Release Notes
A thread deadlock within Navisphere Express is
being caused by a thread not releasing a lock during
an error situation. This will cause Navisphere
Express to hang. The only remedy is to reboot the
SP.
Frequency: Rarely under a rare set of
circumstances.
[141362]
Locking is now done through objects that release locks based
on scope and that do not require all code paths to correctly
release the lock
Navisphere Express problems fixed in version 02.19.100.5.018
Problem
Details
The Dismiss button for the Attention Required
message:
A Hot Spare is currently
not allocated on the storage
system. Creation of a Hot
Spare is highly recommended.
does not work correctly. Selecting the Dismiss
button will not remove the display of this message.
[127711]
Navisphere Express will now accept the Dismiss button and
remove the display of the
Attention Required
for Hot Spare
message.
A memory leak within Navisphere Express may
cause an SP to be unmanaged or for operations to
start failing. Navisphere Express should return to
normal operation within a few minutes.
[129228]
Fixed the memory leak.
Sometimes Navisphere Express will hit its
connection limit and not allow any additional
connections.
[130535]
Connections are now shut down correctly when a user exits
the browser running Navisphere Express. This stops the
application from hitting its connection limit.
Navisphere Express problems fixed in version 02.19.100.5.014
Problem
Details
Incorrect use of a system API within Navisphere
Express may cause an SP to be unmanaged or
operations to start failing. If the situation does not
recover in a few minutes, the only solution is to
reboot the SP. [129924]
Call the correct system API to avoid getting stuck during
shutdown.
The string “0x” is being added to the beginning of
all event codes sent through event monitor’s email
notification service.
[131913]
Fixed event monitor to no longer add “0x” to the event codes.