User guide

Dominion KX II Version 2.5 Release Notes 13
DominionKXIIReleaseNotes2.5  255-62-4026-00-0P RoHS
9. In a CC-SG environment, once a blade chassis type port has been configured on the KX II, the blade chassis should not be
moved to another port.
10. The blade server feature is not currently supported by the Dominion KX II-101 and the KSX II products.
11. When blade chassis type ports are connected to the KX II, the User Management Group page must be edited remotely, rather
than from the local port.
12. CC-SG 4.1 (or later) is required for use with Release 2.2 and the blade server feature. If you use a previous release of CC-SG,
then for blade server chassis with internal KVM switches, you will see the individual blade servers displayed as standard KVM
ports, but you will not have blade server functionality. For blade servers directly connected to CIMs, they will be displayed and
can be connected to as standard KVM ports, but without the “Port Management” grouping and blade server functionality. Use
CC-SG 4.1 for full blade server support.
13. Contact the Dominion KX II documentation, CIM Guide and Blade Configuration Guide or technical support for more information.
Release 2.0.X Important Notes and Information:
1. Both power supplies are monitored by default. If only one power input is plugged in, then the front panel LED will light red.
Configure it for a single power input using the “Power Supply Setup” function on the “Device Settings” menu.
2. For reliable network communication, configure the KX II and LAN Switch to the same LAN Interface Speed and Duplex. For
example, configure both the KX II and LAN Switch to Autodetect (recommended) or set both to a fixed speed/duplex such as
100Mbps/Full.
3. There are several prerequisites for Virtual Media: (1) a D2CIM-VUSB or D2CIM-DVUSB must be connected to the server’s USB
port, (2) the operating system (OS) or BIOS must support USB connected devices, and (3) the user must have the required
administrator permissions on the client, target and the KX II.
4. Not all servers and operating systems support all virtual media options. In general, modern Windows
®
OS’ do, including
Windows Vista
™
, 2003 Server, XP and Windows 2000 with the latest patches. Target Servers running Linux and Mac OS’,
when accessed from a Windows client, will generally mount CD/DVD drives, USB drives and ISO images. As of Release 2.4,
Mac
®
and Linux clients can now mount these types of media also, subject to the notes above. Other UNIX based OS’
generally do not support virtual media.
5. In general, due to varying BIOS implementations of the USB 2.0 standard regarding virtual media, it is not always possible to
boot from a virtual media drive at the BIOS level. The D2CIM-DVUSB CIM is recommended for customers who plan to use
virtual media at the OS and BIOS levels. Use D2CIM-VUSB for virtual media at the OS level and for the BIOS level when
supported by the particular BIOS or with an applicable BIOS USB profile. Please note that some BIOS do not support USB
devices as boot devices and hence virtual media is not possible.
6. For Windows OS’, do not use the “Safely Remove Hardware” function in the system tray on the target server to disconnect a
mounted virtual media drive. Disconnect using the “Disconnect” command on the virtual media menu.
7. Please note that the user at the local port can not change the active USB profile. If required, change from one of the remote
clients.
8. Absolute Mouse Synchronization requires support from the OS. Windows and Mac OS’ generally support it. Linux and UNIX
based OS’ (AIX, HP-UX, Solaris) generally do not.
9. When a panel is opened in the Virtual KVM Client (VKC), the client, as well as related browser tabs and windows, will wait for
user input until the panel is closed.
10. Be careful of the web browser refresh or reload function/button, which has the side-effect of closing VKC sessions.
11. D2CIM-PWR must be separately ordered. It is not included with the powerstrip.
12. To use AES encryption, first ensure that your web browser supports this stronger encryption – not all browsers do. For AES, set
the “Encryption mode” on the “Security Settings” panel to “AES,” not “Auto” which generally results in RC4 encryption. 128 bit
and 256 bit AES encryption are supported.
13. For the best possible video quality, adhere to these distance guidelines from the CIM to the KX II: