User guide

Dominion KX II Version 2.5 Release Notes 12
DominionKXIIReleaseNotes2.5  255-62-4026-00-0P RoHS
c. P2-UST: V5-1FE - P2 4.5 GA release version or later
d. P2-EUST: EUST-3F0 - P2 4.5 GA release version or later
4. The recommended distance between the extended local port station and the Dominion KX II is given in the table below. The
distance can vary according to the type of user station, the video resolution, cable type/quality and environmental conditions.
Extended Device 1024x768, 60 hz 1280x1024, 60 hz
Paragon II UMT using EUST 1000 900
Paragon EUST 500 400
URKVM 650 250
Paragon UST 500 200
Extended Local Port Recommended Maximum Distances
Release 2.1 (Blade Server) Important Notes and Information:
1. Blade server support is dependent on the particular blade server manufacturer and model. In general, there are two types: (1)
connect a CIM to each blade and (2) connect a CIM to the blade server chassis’ internal KVM switch or management module.
The module must be configured to work with the KX II. Consult the documentation or technical support for instructions. The
Dominion KX II Blade Configuration guide contains detailed instructions and screenshots for Dell and IBM blade servers.
2. When connecting to individual Dell 1855/1995 blades, the “USB Front Dongle for Dell PowerEdge 1855/1955” cable is required;
manufacturer part number N8138 and Dell part number 310-6484. For HP c3000 and c7000, the “HP c-Class Blade SUV
Cable” is used; part # is 416003-001. Use the Port Group Management feature to group the ports. Note: the internal KVM
module for the HP c3000 is not supported in this release.
3. Paragon blade server CIMs are not used with the Dominion KX II. Use the appropriate KX II CIM according to the type of ports
on the blade server (PS2 or USB) and whether the advanced features (e.g. virtual media) are wanted and supported. See the
Dominion KX II CIM Guide for more information.
4. Virtual media and advanced mouse synchronization is supported on blade servers where a CIM is connected to each blade,
assuming the operating system on the blade supports it. Virtual media is also supported on the IBM Blade Center E and H
chassis when using the D2CIM-DVUSB connected to the front and rear of the chassis, with auto-discovery enabled.
5. For blade server chassis with internal KVM switches, for performance and reliability reasons, there is a limit of 8 blade servers
per KX II. If you connect a CIM to each individual blade server, then there is no limit.
6. For the IBM BladeCenter, the Advanced Management Module (AMM) is supported. The older Management Module has not
been certified in this release. The KX II only supports auto-discovery for AMM[1] as the acting primary management module.
7. The following IBM BladeCenter minimum AMM firmware is recommended:
Management Module Firmware
Main application: BPET36K
Released: 04-22-08
Name: CNETMNUS.PKT
Rev: 54
8. When connecting to a blade server in the IBM BladeCenter, you should wait a few seconds after seeing the video before moving
the mouse. If not, then the mouse may be out of synch and you should manually synchronize it.