Dell PowerVault TL4000 Dell PowerVault TL2000/TL4000 - Important Informatio - Page 9

Refresh Server from the Server Health Monitor tab, inside a command window, for

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

Page 9 highlights

• Linux operating system can intermittently experience EKM GUI window freezes When the EKM application is running in a Linux operating system, the EKM GUI window can intermittently freeze. There are no adverse affects to the EKM server or host. It is recommended to exit the GUI when it is not in use to avoid the problem. The workaround is to close the GUI window and re-open it. • EKM GUI display does not refresh the drive table when the user selects Refresh Server from the Server Health Monitor tab In order to view the updated drive list, the user must exit the EKM GUI (close window) then re-open it and sign in. • EKM GUI may not be capable of displaying the host IP address There are three limitations in the current EKM GUI that prevent it from displaying the EKM host IP address in the Server Health Monitor tab: a The host is configured with an IPV6 address; the EKM application will not be able to display the IP address. b The EKM application is installed in a Linux system; the EKM application displays the localhost address and not the actual active IP port. c The user made a change to the host server IP address after the EKM is installed. The EKM shows the address found during the initial EKM installation. To retrieve the actual IP address of the host system, the user must locate the IP port address by accessing the network configuration. In a Windows® system type ipconfig inside a command window, for a Linux system type ifconfig. • EKM server communication port (TCP/SSL) and library communication port must be consistent The EKM server is capable of communicating with the libraries via a TCP or SSL port. More than one library can be configured to receive keys from a single EKM. In this case, all the device libraries attached must use the same port configuration. i.e. all libraries must communicate via the TCP port or SSL only. Non-homogeneous communication port settings will result in failed backup jobs (no keys provided by the EKM). Important Information 9

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
Important Information
9
•
Linux operating system can intermittently experience EKM GUI
window freezes
When the EKM application is running in a Linux operating system, the
EKM GUI window can intermittently freeze. There are no adverse affects
to the EKM server or host. It is recommended to exit the GUI when it is
not in use to avoid the problem. The workaround is to close the GUI
window and re-open it.
•
EKM GUI display does not refresh the drive table when the user selects
Refresh Server from the Server Health Monitor tab
In order to view the updated drive list, the user must exit the EKM GUI
(close window) then re-open it and sign in.
•
EKM GUI may not be capable of displaying the host IP address
There are three limitations in the current EKM GUI that prevent it from
displaying the EKM host IP address in the Server Health Monitor tab:
a
The host is configured with an IPV6 address; the EKM application will
not be able to display the IP address.
b
The EKM application is installed in a Linux system; the EKM
application displays the localhost address and not the actual active
IP port.
c
The user made a change to the host server IP address after the EKM is
installed. The EKM shows the address found during the initial EKM
installation.
To retrieve the actual IP address of the host system, the user must locate
the IP port address by accessing the network configuration. In a
Windows
®
system type
ipconfig
inside a command window, for a
Linux system type
ifconfig
.
•
EKM server communication port (TCP/SSL) and library communication
port must be consistent
The EKM server is capable of communicating with the libraries via a TCP
or SSL port. More than one library can be configured to receive keys from a
single EKM. In this case, all the device libraries attached must use the
same port configuration. i.e. all libraries must communicate via the TCP
port or SSL only. Non-homogeneous communication port settings will
result in failed backup jobs (no keys provided by the EKM).