Dominion KX II User Guide Release 2.6.0 Copyright © 2014 Raritan, Inc. DKX2-v2.6.
This document contains proprietary information that is protected by copyright. All rights reserved. No part of this document may be photocopied, reproduced, or translated into another language without express prior written consent of Raritan, Inc. © Copyright 2014 Raritan, Inc. All third-party software and hardware mentioned in this document are registered trademarks or trademarks of and are the property of their respective holders.
Contents Chapter 1 Introduction 1 KX II Overview ............................................................................................................................... 2 Package Contents .......................................................................................................................... 4 KX II Device Photos and Features ................................................................................................. 5 Product Features ......................................
Contents Port Access Page (Remote Console Display) ................................................................... 38 Port Action Menu ............................................................................................................... 41 Managing Favorites ........................................................................................................... 43 Scanning Ports ................................................................................................................
Contents Virtual Media in a Mac Environment .......................................................................................... 103 Active System Partition .................................................................................................... 103 Drive Partitions ................................................................................................................ 103 Virtual Media File Server Setup (File Server ISO Images Only)................................................
Contents LAN Interface Settings ..................................................................................................... 144 Device Services ......................................................................................................................... 145 Enabling SSH .................................................................................................................. 145 HTTP and HTTPS Port Settings ......................................................................
Contents Upgrading CIMs ......................................................................................................................... 245 Upgrading Firmware .................................................................................................................. 245 Upgrade History ......................................................................................................................... 247 Rebooting the KX II .............................................................
Contents Local Console Smart Card Access ............................................................................................ 270 Smart Card Access in KX2 8xx Devices ......................................................................... 271 Local Console USB Profile Options ........................................................................................... 272 Hot Keys and Connect Keys ......................................................................................................
Contents Appendix B Dual Video Port Groups 317 Overview .................................................................................................................................... 317 Recommendations for Dual Port Video ..................................................................................... 318 Dual Video Port Group Supported Mouse Modes ..................................................................... 318 CIMs Required for Dual Video Support ...................................
Contents Virtual Media Notes .................................................................................................................... 341 Cannot Connect to Drives from Linux Clients ................................................................. 341 Cannot Write To/From a File from a Mac Client .............................................................. 342 Virtual Media via VKC and AKC in a Windows Environment ..........................................
Contents Appendix F Frequently Asked Questions 355 General FAQs ............................................................................................................................ 355 Remote Access .......................................................................................................................... 356 Universal Virtual Media ..............................................................................................................
Chapter 1 Introduction In This Chapter KX II Overview ...........................................................................................2 Package Contents .....................................................................................4 KX II Device Photos and Features ............................................................5 Product Features .......................................................................................7 KX II Client Applications ................................
Chapter 1: Introduction KX II Overview Raritan's Dominion KX II is an enterprise-class, secure, digital KVM (Keyboard, Video, Mouse) switch that provides BIOS-level (and up) access and control of servers from anywhere in the world via a web browser. Up to 64 servers can be controlled with a standard KX II. With the KX II 8-user model, up to 32 servers can be controlled with the KX2-832 and up to 64 servers can be controlled with the KX2-864. A scan feature allows you to locate and view up to 32 targets.
Chapter 1: Introduction 3
Chapter 1: Introduction Diagram key Local port access Tiering IP-based network access Extended local port Modem Mobile access via iPhone® and iPad® using CC-SG Virtual media Digital audio Smart card access at the rack CIMs Remote smart card access Cat5/6 cable Package Contents Each KX II ships as a fully-configured stand-alone product in a standard 1U (2U for DKX2-864) 19" rackmount chassis.
Chapter 1: Introduction KX II Device Photos and Features KX II KX2-808 5
Chapter 1: Introduction KX2-832 KX2-864 See KX II Dimensions and Physical Specifications (on page 287) for product specifications. See Supported Computer Interface Module (CIMs) Specifications (on page 289) for CIM specifications and images.
Chapter 1: Introduction Product Features Hardware Integrated KVM-over-IP remote access 1U or 2U rack-mountable (brackets included) Dual power supplies with failover; autoswitching power supply with power failure warning Support for tiering in which a base KX II device is used to access multiple other tiered devices. See Configuring and Enabling Tiering (on page 147) for more information on tiering.
Chapter 1: Introduction Model Remote users Ports KX II-416 4 16 KX II-232 2 32 KX II-216 2 16 KX II-132 1 32 KX II-116 1 16 KX II-108 1 8 Software 8 Virtual media support in Windows®, Mac® and Linux® environments with D2CIM-VUSB and D2CIM-DVUSB CIMs and digital CIMs Support for digital audio over USB Port scanning and thumbnail view of up to 32 targets within a configurable scan set Absolute Mouse Synchronization with D2CIM-VUSB CIM, D2CIM-DVUSB CIM and digital CIMs
Chapter 1: Introduction KX II Client Applications The following client applications can be used in the KX II: KX II 2.2 (and later): Virtual KVM Client (VKC) Active KVM Client (AKC) Multi-Platform Client (MPC) KX II (Generation 2): Virtual KVM Client (VKC) Multi-Platform Client (MPC) Java™ 1.7 is required to use the Java-based Java-based KX II Virtual KVM Client (VKC) and Multi-Platform Client (MPC).. Microsoft .NET® 3.
Chapter 2 Installation and Configuration In This Chapter Overview ..................................................................................................10 Rack Mounting .........................................................................................10 Default Login Information ........................................................................12 Getting Started ........................................................................................12 Logging in to the KX II .....
Chapter 2: Installation and Configuration 5. When connecting cables to the rear panel of the KX II drape them over the cable-support bar. Rear Mount The steps correspond to the numbers shown in the rear rackmount diagrams. 1. Secure the cable-support bar to the front end of the side brackets, near the side brackets' “ears,” using two of the included screws. 2.
Chapter 2: Installation and Configuration Default Login Information Default Value User name admin This user has administrative privileges. Password raritan The first time you start the KX II, you are required to change the default password. IP address 192.168.0.192. Important: For backup and business continuity purposes, it is strongly recommended that you create a backup administrator user name and password and keep that information in a secure location.
Chapter 2: Installation and Configuration Step 2: Configure the KVM Target Servers Target Server Video Resolutions For optimal bandwidth efficiency and video performance, KVM target servers running graphical user interfaces such as Windows ®, Linux®, X-Windows, Solaris™, and KDE may require configuration. The desktop background does not need to be completely solid, but desktop backgrounds featuring photos or complex gradients might degrade performance.
Chapter 2: Installation and Configuration Windows XP, Windows 2003, Windows 2008 Mouse Settings Configure these mouse settings in Windows XP®, Windows 2003® and Windows 2008®: Configure the Motion settings: Set the mouse motion speed setting to exactly the middle speed Disable the "Enhance pointer precision" option Disable the Snap To option Disable transition effects: Deselect the "Use the following transition effect for menus and tooltips" option Windows 2000 Mouse Settings Configure th
Chapter 2: Installation and Configuration 3. In KX II, select Device Settings > Port Configuration, then click on the target name to open the Port page. 4. Expand 'Select USB Profiles for Port' section. 5. Select 'Mac OS-X (10.4.9) and later' from the Available box, then click Add to add it to the Selected box. 6. Click on 'Mac OS-X (10.4.9) and later' in the Selected box. This automatically adds it to the Preferred Profile drop-down. 7. Select 'Mac OS-X (10.4.
Chapter 2: Installation and Configuration Step 3: Connect the Equipment A. AC Power Connect the power supply(s): 1. Attach the included AC power cord to the KX II, and plug it into an AC power outlet. 2. For dual-power failover protection, attach the second included AC power cord to the KX II, and plug it into a different power source than the first power cord. B. Modem Port (Optional) Please see the KX II Online Help for information on connecting modems. C.
Chapter 2: Installation and Configuration Enable 'Automatic Failover' on the KX II Network Configuration page. D. Local Access Port (Local PC) For access to target servers at the rack, use the KX II Local Access port. The Local Access port also provides a graphical user interface from the KX II Local Console for administration and target server access. While the Local Access port is required for installation and setup, it is optional for subsequent use.
Chapter 2: Installation and Configuration 2. Ensure that your target server's video is configured to a supported resolution and refresh rate. For Sun servers, ensure your target server's video card is set to output standard VGA (H-and-V sync) and not composite sync. 3. Attach the keyboard/mouse connector of your CIM/DCIM to the corresponding ports on your target server. Use a DCIM if you are connecting from the target server video port to the KX II. 4.
Chapter 2: Installation and Configuration Assign the KX II an IP Address To assign an IP address to the KX II: 1. Choose Device Settings > Network. The Network Settings page opens. 2. Specify a meaningful Device Name for your KX II device. Up to 32 alphanumeric and valid special characters, no spaces between characters. 3. Next, configure the IPv4, IPv6 and DNS settings. Configure the IPv4 Settings 1. In the IPv4 section, enter or select the appropriate IPv4-specific network settings: a.
Chapter 2: Installation and Configuration Configure the IPv6 Settings 1. If using IPv6, enter or select the appropriate IPv6-specific network settings in the IPv6 section: a. Select the IPv6 checkbox to activate the fields in the section and enable IPv6 on the device. b. Enter a Global/Unique IP Address. This is the IP address assigned to the KX II. c. Enter the Prefix Length. This is the number of bits used in the IPv6 address. d. Enter the Gateway IP Address. e. Link-Local IP Address.
Chapter 2: Installation and Configuration 2. If Use the Following DNS Server Addresses is selected, whether or not DHCP is selected, the addresses entered in this section is used to connect to the DNS server. Enter the following information if the Following DNS Server Addresses is selected. These addresses are the primary and secondary DNS addresses used if the primary DNS server connection is lost due to an outage. a. Primary DNS Server IP Address b. Secondary DNS Server IP Address 3.
Chapter 2: Installation and Configuration If either of these checkboxes is selected and only power input is connected, the power LED on the front of the device is Red. Configure Date/Time Settings (Optional) Optionally, configure the date and time settings. The date and time settings impact SSL certificate validation if LDAPS is enabled. Use the Date/Time Settings page to specify the date and time for the KX II. There are two ways to do this: Manually set the date and time.
Chapter 2: Installation and Configuration Step 5: Launching the KX II Remote Console Log in to your KX II Remote Console from any workstation with network connectivity that has Microsoft .NET ® and/or Java Runtime Environment™ installed. To launch the KX II Remote Console: 1. Launch a supported web browser. 2. Enter either: The URL - http://IP-ADDRESS to use the Java-based Virtual KVM Client Or http://IP-ADDRESS/akc for the Microsoft .
Chapter 2: Installation and Configuration 3. Choose Switch From in the Port Action menu. The new target server you selected is displayed. Disconnecting a Target Server To disconnect a target server: On the Port Access page, click the port name of the target you want to disconnect from, then click Disconnect on Port Action menu when it appears. Step 6: Configuring the Keyboard Language (Optional) Note: This step is not required if you are using the US/International language keyboard.
Chapter 2: Installation and Configuration Step 7: Configure Tiering (Optional) The optional tiering feature allows you to use a KX II as your base device, then connect additional KX II's to it as tiered devices. You can then access servers and PX PDUs through the base both locally and remotely. See the Device Management (on page 141) section of the KX II Help for more information on this feature. To enable tiering: 1.
Chapter 2: Installation and Configuration http://IP-ADDRESS/akc for the Microsoft .NET-based Active KVM Client IP-ADDRESS is the IP address assigned to your KX II You can also use HTTPS, or the DNS name of the KX II assigned by your administrator (if applicable). You are always redirected to the IP address from HTTP to HTTPS. 3. Enter your username and password, then click Login. 4. Accept the user agreement (if applicable). 5. If security warnings appear, accept and/or allow access.
Chapter 2: Installation and Configuration Additional Security Warnings Even after an SSL certificate is installed in the KX II, depending on your browser and security settings, additional security warnings may be displayed when you log in to KX II. It is necessary to accept these warnings to launch the KX II Remote Console.
Chapter 2: Installation and Configuration Example 1: Import the Certificate into the Browser In this example, you import the Certificate into the browser. Steps Open an IE browser, then log in to KX II. Click More Information on the first Java™ security warning. Click View Certificate Details on the More Information dialog. You are prompted to install the certificate. Follow the wizard steps.
Chapter 2: Installation and Configuration Steps Click the Content tab. Click Certificates. The Certificate Import Wizard opens and walks you through each step. File to Import - Browse to locate the Certificate Certificate Store - Select the location to store the Certificate Click Finish on the last step of the Wizard. The Certificate is imported. Close the success message. Click OK on the Internet Options dialog to apply the changes, then close and reopen the browser.
Chapter 2: Installation and Configuration Example 2: Add the KX II to Trusted Sites and Import the Certificate In this example, the KX II's URL is added as a Trusted Site, and the Self Signed Certificate is added as part of the process. Steps Open an IE browser, then select Tools > Internet Options to open the Internet Options dialog Click the Security tab. Click on Trusted Sites. Disable Protected Mode, and accept any warnings. Click Sites to open the Trusted Sites dialog.
Chapter 2: Installation and Configuration Steps Click OK on the Internet Options dialog to apply the changes, then close and reopen the browser. Next, import the Certificate. Steps Open an IE browser, then log in to KX II. Click More Information on the first Java™ security warning. Click View Certificate Details on the More Information dialog. You are prompted to install the certificate. Follow the wizard steps.
Chapter 3 Working with Target Servers In This Chapter KX II Interfaces ........................................................................................32 KX II Local Console Interface: KX II Devices ..........................................33 KX II Remote Console Interface ..............................................................33 Proxy Server Configuration for Use with MPC, VKC and AKC ...............50 Virtual KVM Client (VKC) and Active KVM Client (AKC) .........................
Chapter 3: Working with Target Servers KX II Local Console Interface: KX II Devices When you are located at the server rack, the KX II provides standard KVM management and administration via the KX II Local Console. The KX II Local Console provides a direct KVM (analog) connection to your connected servers; the performance is exactly as if you were directly connected to the server's keyboard, mouse, and video ports.
Chapter 3: Working with Target Servers KX II Interface Both the KX II Remote Console and the KX II Local Console interfaces provide a web-based interface for device configuration and administration, as well as target server list and selection. The options are organized into various tabs. After a successful login, the Port Access page opens listing all ports along with their status and availability. Four tabs are provided on the page allowing you to view by port, view by group or view by search.
Chapter 3: Working with Target Servers Left Panel The left panel of the KX II interface contains the following information. Note that some information is conditional - meaning it is displayed based on your role, features being used and so on. Conditional information is noted here. Information Description When displayed? Time & Session The date and time the current session started Always User Username Always State The current state of the application, either idle or active.
Chapter 3: Working with Target Servers Information Description When displayed? PowerIn2 Status of the power 2 outlet connection. Either on or off, or Auto-detect off Always Configured As If you are using a tiering When the KX II is part of Base or Configured configuration, this a tiered configuration indicates if the KX II you As Tiered are accessing is the base device or a tiered device.
Chapter 3: Working with Target Servers KX II Console Navigation The KX II Console interfaces provide many methods for navigation and making your selections. To select an option (use any of the following): Click on a tab. A page of available options appears. Hover over a tab and select the appropriate option from the menu. Click the option directly from the menu hierarchy displayed (breadcrumbs). To scroll through pages longer than the screen: Use Page Up and Page Down keys on your keyboard.
Chapter 3: Working with Target Servers Port Access Page (Remote Console Display) After successfully logging on to the KX II remote console, the View by Port tab on the Port Access page appears. This page lists all of the KX II ports, and the target servers, port groups, and blade chassis that are connected to those ports. The information is sorted by Port Number by default, but you can change the display to sort on any of the available columns by clicking on a column header.
Chapter 3: Working with Target Servers Status - The status of the servers - either up or down. To connect to an available target server or dual monitor target server: 1. Click on the port name. The Port Action menu opens. 2. Click Connect. Once you are connected to a target or dual monitor target server, click on the port group name and then click Disconnect to disconnect. See Port Action Menu (on page 41) for details on additional available menu options.
Chapter 3: Working with Target Servers View by Group Tab The View by Group tab displays blade chassis, 'standard' port groups, and dual video port groups. Click the Expand Arrow icon next to a group to view the ports assigned to the port group. See Device Management (on page 141) for information on creating each of these types of port groups. View by Search Tab The View by Search tab allows you to search by port name.
Chapter 3: Working with Target Servers Blade Chassis - Port Access Page The blade chassis is displayed in an expandable, hierarchical list on the Port Access page, with the blade chassis at the root of the hierarchy and the individual blades labeled and displayed below the root. Use the Expand Arrow icon next to the root chassis to display the individual blades. Note: To view the blade chassis in a hierarchal order, blade-chassis subtypes must be configured for the blade server chassis.
Chapter 3: Working with Target Servers On the local port, the KX II Local Console interface must be visible in order to perform the switch. Hot key switching is also available from the local port. Note: This option is not available from the KX II Remote Console for an available port if all connections are busy. Switch From - Switches from an existing connection to the selected port (KVM target server). This menu item is available only for KVM targets, and only when a Virtual KVM Client is opened.
Chapter 3: Working with Target Servers Managing Favorites A Favorites feature is provided so you can organize and quickly access the devices you use frequently.
Chapter 3: Working with Target Servers Enable Favorites Click Enable in the Favorite Devices section of the left panel of the KX II interface. Once enabled, the Enable button becomes a Disable button.
Chapter 3: Working with Target Servers Access and Display Favorites To access a favorite KX II device: Click the device name (listed beneath Favorite Devices). A new browser opens to that device. To display favorites by name: Click Display by Name. To display favorites by IP Address: Click Display by IP. To display favorites by the host name: Click Display by Host Name.
Chapter 3: Working with Target Servers To use the default discovery port, select the Use Default Port 5000 checkbox. To use a different discovery port: a. Deselect the Use Default Port 5000 checkbox. b. Type the port number in the Discover on Port field. c. Click Save. 3. Click Refresh. The list of devices on the local subnet is refreshed. To add devices to your Favorites List: 1. Select the checkbox next to the device name/IP address. 2. Click Add.
Chapter 3: Working with Target Servers Scanning Ports The KX II provides the port scanning feature to search for selected targets, and display them in a slide show view, allowing you to monitor up to 32 targets at one time. You can connect to targets or focus on a specific target as needed. Scans can include standard targets, blade servers, tiered Dominion devices, and KVM switch ports. Configure scan settings from either the Virtual KVM Client (VKC) or Active KVM Client (AKC).
Chapter 3: Working with Target Servers Note: MPC uses a different method for initiating a scan than the other Raritan clients. See Set Scan Group in the KVM and Serial Client Guide for details. The scan results and scan options differ between the Remote Console and the Local Console. See Scanning Ports - Local Console (on page 269). To scan for targets: 1. Click the Set Scan tab on the Port Access page. 2.
Chapter 3: Working with Target Servers Using Scan Port Options Following are options available to you while scanning targets. With the exception of the Expand/Collapse icon, all of these options are selected from the Options menu in the upper left of the Port Scan viewer. The options will return to their defaults when you close the window. Note: Configure scan settings such as the display interval from either the Virtual KVM Client (VKC) or Active KVM Client (AKC).
Chapter 3: Working with Target Servers Logging Out To quit the KX II: Click Logout in the upper right-hand corner of the page. Note: Logging out also closes any open Virtual KVM Client and serial client sessions. Proxy Server Configuration for Use with MPC, VKC and AKC When the use of a Proxy Server is required, a SOCKS proxy must also be provided and configured on the remote client PC. Note: If the installed proxy server is only capable of the HTTP proxy protocol, you cannot connect.
Chapter 3: Working with Target Servers e. On the General tab, click Network Settings. The Network Settings dialog opens. f. Select Use Proxy Server. g. Click Advanced. The Advanced Network Settings dialog opens. h. Configure the proxy servers for all protocols. IMPORTANT: Do not select 'Use the same proxy server for all protocols'. Note: The default port for a SOCKS proxy (1080) is different from HTTP proxy (3128). 4. If you are using standalone MPC, you must also do the following: i. Open the start.
Chapter 3: Working with Target Servers Virtual KVM Client (VKC) and Active KVM Client (AKC) Overview Whenever you access a target server from the Port Access page of KX II the Remote Console, a Virtual KVM Client (VKC) window opens. There is one Virtual KVM Client for each target server connected. Virtual KVM Client windows can be minimized, maximized, and moved around your computer desktop. IMPORTANT: Refreshing your browser closes the Virtual KVM Client connection, so exercise caution.
Chapter 3: Working with Target Servers Virtual KVM Client (VKC) and Active KVM Client (AKC) Shared Features The Virtual KVM Client (VKC) and Active KVM Client (AKC) are interfaces used to access remote targets.
Chapter 3: Working with Target Servers Connection Properties Dynamic video compression algorithms maintain KVM console usability under varying bandwidth constraints. The devices optimize KVM output not only for LAN use, but also for WAN use. These devices can also control color depth and limit video output, offering an optimal balance between video quality and system responsiveness for any bandwidth.
Chapter 3: Working with Target Servers 3. Choose the Color Depth from the drop-down list. The device can dynamically adapt the color depth transmitted to remote users in order to maximize usability in all bandwidths.
Chapter 3: Working with Target Servers Connection Information Open the Connection Information dialog for real-time connection information, and copy the information from the dialog as needed. This is useful if, for example, you want to gather real-time information on your current connection. See Configuring Connection Properties The following information is displayed about the current connection: KX III Name - The name of the KX III. IP Address - The IP address of the KX III.
Chapter 3: Working with Target Servers Steps Click Connection > Info... to open the Connection Info dialog. Click Copy to Clipboard. Paste the information in a file of your choosing. Connection Properties Dynamic video compression algorithms maintain KVM console usability under varying bandwidth constraints. The devices optimize KVM output not only for LAN use, but also for WAN use.
Chapter 3: Working with Target Servers 33 kb (Fast Modem) 24 kb (Slow Modem) Note that these settings are an optimization for specific conditions rather than an exact speed. The client and server always attempt to deliver video as quickly as possible on the network regardless of the current network speed and encoding setting. But the system will be most responsive when the settings match the real world environment. 3. Choose the Color Depth from the drop-down list.
Chapter 3: Working with Target Servers Button Button name Description Same as choosing Video > Color Calibrate. Target Screenshot Click to take a screenshot of the target server and save it to a file of your choosing. Audio Opens a dialog that allows you to select from a list of audio devices connected to a client PC. Once audio devices have been connected to the target, select to disconnect the devices.
Chapter 3: Working with Target Servers Audio is supported by KX II 2.4.0 (and later). Audio capture is supported by KX II 2.5.0 (and later). Audio icons Icon name Description Speaker These icons are located in status bar at the bottom of the client window. Green, blinking waves indicate an audio playback session is currently streaming. A black speaker icon is displayed when the session is muted. The icon is grayed out when no audio is connected.
Chapter 3: Working with Target Servers Import/Export Keyboard Macros Macros exported from Active KVM Client (AKC) cannot be imported into Multi-Platform Client (MPC) or Virtual KVM Client (VKC). Macros exported from MPC or VKC cannot be imported into AKC. To import macros: 1. Choose Keyboard > Import Keyboard Macros to open the Import Macros dialog. Browse to the folder location of the macro file. 2. Click on the macro file and click Open to import the macro. a.
Chapter 3: Working with Target Servers The macros are then imported. If a macro is imported that contains a hot key that already exists, the hot key for the imported macro is discarded. To export macros: 1. Choose Tools > Export Macros to open the Select Keyboard Macros to Export dialog. 2. Select the macros to be exported by checking their corresponding checkbox or using the Select All or Deselect All options. 3. Click Ok. An "Export Keyboard Macros to" dialog is displayed.
Chapter 3: Working with Target Servers Building a Keyboard Macro To build a macro: 1. Click Keyboard > Keyboard Macros. The Keyboard Macros dialog appears. 2. Click Add. The Add Keyboard Macro dialog appears. 3. Type a name for the macro in the Keyboard Macro Name field. This name appears in the Keyboard menu after it is created. 4. From the Hot-Key Combination field, select a keyboard combination from the drop-down list. This allows you to execute the macro with a predefined keystroke. Optional 5.
Chapter 3: Working with Target Servers 9. Select the new macro on the menu to run it or use the keystrokes you assigned to the macro. To use the Send Text to Target function for the macro: 1. Click the Keyboard > Send Text to Target. The Send Text to Target dialog appears. 2. Enter the text you want sent to the target. Note: Non-English characters are not supported by the Send Text to Target function. 3.
Chapter 3: Working with Target Servers Modifying and Removing Keyboard Macros To modify a macro: 1. Choose Keyboard > Keyboard Macros. The Keyboard Macros dialog appears. 2. Choose the macro from among those listed. 3. Click Modify. The Add/Edit Macro dialog appears. 4. Make your changes. 5. Click OK. To remove a macro: 1. Choose Keyboard > Keyboard Macros. The Keyboard Macros dialog appears. 2. Choose the macro from among those listed. 3. Click Remove. The macro is deleted.
Chapter 3: Working with Target Servers Video Properties Refreshing the Screen The Refresh Screen command forces a refresh of the video screen. Video settings can be refreshed automatically in several ways: The Refresh Screen command forces a refresh of the video screen. The Auto-sense Video Settings command automatically detects the target server's video settings. The Calibrate Color command calibrates the video to enhance the colors being displayed.
Chapter 3: Working with Target Servers Adjusting Video Settings Use the Video Settings command to manually adjust the video settings. To change the video settings: 1. Choose Video > Video Settings to open the Video Settings dialog. 2. Adjust the following settings as required. As you adjust the settings the effects are immediately visible: a. PLL Settings Clock - Controls how quickly video pixels are displayed across the video screen.
Chapter 3: Working with Target Servers Best possible video mode The device will perform the full Auto Sense process when switching targets or target resolutions. Selecting this option calibrates the video for the best image quality. Quick sense video mode With this option, the device will use a quick video Auto Sense in order to show the target's video sooner. This option is especially useful for entering a target server's BIOS configuration right after a reboot. 5.
Chapter 3: Working with Target Servers Screenshot from Target Command (Target Screenshot) You are able to take a screenshot of a target server using the Screenshot from Target server command. If needed, save this screenshot to a file location of your choosing as a bitmap, JPEG or PNG file. To take a screenshot of the target server: 1. Select Video > Screenshot from Target, or click the Target Screenshot button on the toolbar. 2.
Chapter 3: Working with Target Servers Mouse Options When in dual mouse mode, and provided the option is properly configured, the mouse cursors align. In dual mouse mode, when controlling a target server, the Remote Console displays two mouse cursors: one belonging to your KX II client workstation, and the other belonging to the target server. You can operate in either single mouse mode or dual mouse mode.
Chapter 3: Working with Target Servers Mouse Pointer Synchronization When remotely viewing a target server that uses a mouse, two mouse cursors are displayed: one belonging to your remote client workstation and the other belonging to the target server. When the mouse pointer lies within the Virtual KVM Client target server window, mouse movements and clicks are directly transmitted to the connected target server.
Chapter 3: Working with Target Servers Additional Notes for Intelligent Mouse Mode Be sure that there are no icons or applications in the upper left section of the screen since that is where the synchronization routine takes place. Do not use an animated mouse. Disable active desktop on KVM target servers. Synchronize Mouse In dual mouse mode, the Synchronize Mouse command forces realignment of the target server mouse pointer with Virtual KVM Client mouse pointer.
Chapter 3: Working with Target Servers Intelligent Mouse Mode In Intelligent Mouse mode, the device can detect the target mouse settings and synchronize the mouse cursors accordingly, allowing mouse acceleration on the target. Intelligent mouse mode is the default for non-VM targets. During synchronization, the mouse cursor does a “dance” in the top left corner of the screen and calculates the acceleration. For this mode to work properly, certain conditions must be met.
Chapter 3: Working with Target Servers Please note that mouse configurations will vary on different target operating systems. Consult your OS guidelines for further details. Also note that intelligent mouse synchronization does not work with UNIX targets. Absolute Mouse Mode In this mode, absolute coordinates are used to keep the client and target cursors in synch, even when the target mouse is set to a different acceleration or speed.
Chapter 3: Working with Target Servers Single Mouse Mode Single Mouse mode uses only the target server mouse cursor and the local mouse pointer no longer appears onscreen. Note: Single mouse mode does not work on Windows or Linux targets when client is running on a Virtual Machine. To enter single mouse mode, do one the following: Choose Mouse > Single Mouse Cursor. Click the Single/Double Mouse Cursor button in the toolbar.
Chapter 3: Working with Target Servers United Kingdom Korean (Korea) French (Belgium) Norwegian (Norway) Portuguese (Portugal) Danish (Denmark) Swedish (Sweden) German (Switzerland) Hungarian (Hungary) Spanish (Spain) Italian (Italy) Slovenian Translation: French - US Translation: French - US International In AKC, the keyboard type defaults to the local client, so this option does not apply. 4. Configure hotkeys: Exit Full Screen Mode - Hotkey.
Chapter 3: Working with Target Servers 5. Click OK. Keyboard Limitations Turkish Keyboards If using a Turkish keyboard, you must connect to a target server through the Active KVM Client (AKC). It is not supported by other Raritan clients. Slovenian Keyboards The < key does not work on Slovenian keyboards due to a JRE limitation.
Chapter 3: Working with Target Servers Client Launch Settings KX II users can configure client launch settings that allow you to define the screen settings for a KVM session. To configure client launch settings: 1. Click Tools > Options. The Options dialog appears. 2. Click on the Client Launch Settings tab. To configure the target window settings: a. Select 'Standard - sized to target Resolution' to open the window using the target's current resolution.
Chapter 3: Working with Target Servers Configure Scan Settings in VKC and AKC The KX II provides the port scanning feature to search for selected targets, and display them in a slide show view, allowing you to monitor up to 32 targets at one time. You can connect to targets or focus on a specific target as needed. Scans can include standard targets, blade servers, tiered Dominion devices, and KVM switch ports. Configure scan settings from either the Virtual KVM Client (VKC) or Active KVM Client (AKC).
Chapter 3: Working with Target Servers View Status Bar By default, the status bar is displayed at the bottom of the target window. To hide the status bar: Click View > Status Bar to deselect it. To restore the status bar: Click View > Status Bar to select it. Scaling Scaling your target window allows you to view the entire contents of the target server window.
Chapter 3: Working with Target Servers Full Screen Mode When you enter Full Screen mode, the target's full screen is displayed and acquires the same resolution as the target server. The hot key used for exiting this mode is specified in the Options dialog, see Tool Options (on page 75). While in Full Screen mode, moving your mouse to the top of the screen displays the Full Screen mode menu bar.
Chapter 3: Working with Target Servers Digital Audio The KX II supports end-to-end, bidirectional, digital audio connections for digital audio playback and capture devices from a remote client to a target server. The audio devices are accessed over a USB connection. Current device firmware is required.
Chapter 3: Working with Target Servers Saving Audio Settings Audio device settings are applied on a per KX II device basis. Once the audio devices settings are configured and saved on the KX II, the same settings are applied to it. For example, you can configure a Windows® audio device to us a stereo, 16 bit, 44.1K format. When you connect to different targets and use that Windows audio device, the stereo, 16 bit, 44.1K format is applied to each target server.
Chapter 3: Working with Target Servers Operating system Audio playback and capture supported by: Mac® Virtual KVM Client (VKC) Multi-Platform Client (MPC) A Speaker icon is displayed in the status bar at the bottom of the client window. It is grayed out when no audio is being used. When the Speaker icon and Microphone icon are displayed in the status bar, the session is being captured as it is streamed.
Chapter 3: Working with Target Servers Connecting to a Single Target Server from Multiple Remote Clients KX II 2.5.0 (and later) allows up to eight (8) users on different remote clients to connect to the same target server at the same time in order to listen in on audio playback. In order to use this feature, PC Share mode and VM Share mode must be enabled for the target. See Encryption & Share (on page 227) for information on enabling PC Share and VM Share modes.
Chapter 3: Working with Target Servers Connecting and Disconnecting a Digital Audio Device Audio device settings are applied on a per KX II device basis. Once the audio devices settings are configured and saved on the KX II, the same settings are applied to it. See Saving Audio Settings (on page 83) for more information.
Chapter 3: Working with Target Servers Note: The device names listed in the Connect Recording Device drop-down are truncated to a maximum of 30 characters for Java clients. 8. Select the device that you wish to connect from the drop-down list. 9. Select the audio format for the recording device from the Format: drop-down. 10. Click OK. If the audio connection is established, a confirmation message appears. Click OK. If the connection was not established, an error message appears.
Chapter 3: Working with Target Servers To disconnect from the audio device: Click the Audio icon in the toolbar and select OK when you are prompted to confirm the disconnect. A confirmation message appears. Click OK. Adjusting Capture and Playback Buffer Size (Audio Settings) Once an audio device is connected, the capture and playback buffer size can be adjusted as needed. This feature is useful for controlling the quality of the audio, which may be impacted by bandwidth limitations or network spikes.
Chapter 3: Working with Target Servers Smart Cards Using the KX II, you are able to mount a smart card reader onto a target server to support smart card authentication and related applications. For a list of supported smart cards, smart card readers, and additional system requirements, see Smart Card Minimum System Requirements, CIMs and Supported/Unsupported Smart Card Readers. Note: The USB Smart Card token (eToken NG-OTP) is only supported from the remote client.
Chapter 3: Working with Target Servers You are also able to remove or reinsert a smart card. This function can be used to provide notification to a target server OS that requires a removal/reinsertion in order to display the appropriate login dialog. Using this function allows the notification to be sent to a single target without affecting other active KVM sessions. To mount a smart card reader: 1. Click the Smart Card menu and then select Smart Card Reader.
Chapter 3: Working with Target Servers To update the smart card in the Select Smart Card Reader dialog: Click Refresh List if a new smart card reader has been attached to the client PC. To send smart card remove and reinsert notifications to the target: Select the smart card reader that is currently mounted and click the Remove/Reinsert button. To unmount a smart card reader: Select the smart card reader to be unmounted and click the Unmount button.
Chapter 3: Working with Target Servers 2. Use the Copy to Clipboard button to copy the information contained in the dialog to a clipboard file so it can be accessed later when dealing with support (if needed). About the Active KVM Client Active KVM Client (AKC) is based on Microsoft Windows .
Chapter 3: Working with Target Servers Since .NET is required to run AKC, if you do not have .NET installed or you have an unsupported version of .NET installed, you will receive a message instructing you to check the .NET version. Note: Raritan recommends Windows XP® operating system users verify you have a working version of .NET 3.5 or 4.0 already installed before you launch AKC. If you do not verify your .
Chapter 3: Working with Target Servers Multi-Platform Client (MPC) Raritan Multi-Platform Client (MPC) is a graphical user interface for the Raritan product lines, providing remote access to target servers connected to Raritan KVM over IP devices. For details on using MPC, see the KVM and Serial Access Clients Guide available on Raritan's website on the same page as the user guide. Instructions on launching MPC are provided there. Please note this client is used by various Raritan products.
Chapter 3: Working with Target Servers Note: Depending on your browser and browser security settings, you may see various security and certificate check and warning messages. It is necessary to accept the options in order to open MPC. Note: If you are using Firefox 3.0.3, you may experience problems launching the application. If this occurs, clear the browser cache and launch the application again.
Chapter 4 Virtual Media All KX II models support virtual media. Virtual media extends KVM capabilities by enabling target servers to remotely access media from a client PC and network file servers. With this feature, media mounted on client PCs and network file servers are essentially "mounted virtually" by the target server. The target server can then read from and write to that media as if it were physically connected to the target server itself.
Chapter 4: Virtual Media Remote PC VM Prerequisites Certain virtual media options require administrative privileges on the remote PC (for example, drive redirection of complete drives). Note: If you are using Microsoft Vista or Windows 7, disable User Account Control or select Run as Administrator when starting Internet Explorer. To do this, click the Start Menu, locate IE, right-click and select Run as Administrator.
Chapter 4: Virtual Media Supported Tasks Via Virtual Media Virtual media provides the ability to perform tasks remotely, such as: Transferring files Running diagnostics Installing or patching applications Complete installation of the operating system Record and playback of digital audio Supported Virtual Media Types The following virtual media types are supported for Windows®, Mac® and Linux™ clients: Internal and external hard drives Internal and USB-mounted CD and DVD drives
Chapter 4: Virtual Media Supported Virtual Media Operating Systems The following client operating systems are supported: Windows® 7 operating system Windows 8 operating system Windows XP® operating system openSUSE® 11.4 Celadon (x86_64) Fedora® 18 RHEL® 6.4 OSX Mountain Lion® 10.7 (and later) Solaris® 10 The Active KVM Client (AKC) can be used to mount virtual media types but only for Windows operating systems.
Chapter 4: Virtual Media Connecting and Disconnecting from Virtual Media Access a Virtual Media Drive on a Client Computer To access a virtual media drive on the client computer: 1. From the Virtual KVM Client, choose Virtual Media > Connect Drive, or click the Connect Drive... button Drive dialog appears. . The Map Virtual Media 2. Choose the drive from the Local Drive drop-down list. If you want Read and Write capabilities, select the Read-Write checkbox.
Chapter 4: Virtual Media Mounting CD-ROM/DVD-ROM/ISO Images This option mounts CD-ROM, DVD-ROM, and ISO images. Note: ISO9660 format is the standard supported by Raritan. However, other CD-ROM extensions may also work. To access a CD-ROM, DVD-ROM, or ISO image: 1. From the Virtual KVM Client, choose Virtual Media > Connect CD-ROM/ISO Image, or click the Connect CD ROM/ISO button . The Map Virtual Media CD/ISO Image dialog appears. 2. For internal and external CD-ROM or DVD-ROM drives: a.
Chapter 4: Virtual Media Note: If you are working with files on a Linux® target, use the Linux Sync command after the files are copied using virtual media in order to view the copied files. Files may not appear until a sync is performed. Note: If you are using the Windows 7® operating system®, Removable Disk is not displayed by default in the Window's My Computer folder when you mount a Local CD/DVD Drive or Local or Remote ISO Image.
Chapter 4: Virtual Media Drive Partitions The following drive partition limitations exist across operating systems: Windows® and Mac targets are not able to read Linux formatted partitions Windows and Linux cannot read Mac formatted partitions Only Windows Fat partitions are supported by Linux Root User Permission Requirement Your virtual media connection can be closed if you mount a CD ROM from a Linux client to a target and then unmount the CD ROM.
Chapter 4: Virtual Media Virtual Media File Server Setup (File Server ISO Images Only) This feature is only required when using virtual media to access file server ISO images. ISO9660 format is the standard supported by Raritan. However, other CD-ROM extensions may also work. Note: SMB/CIFS support is required on the file server. Use the Remote Console File Server Setup page to designate the files server(s) and image paths that you want to access using virtual media.
Chapter 5 Rack PDU (Power Strip) Outlet Control In This Chapter Overview ................................................................................................105 Turning Outlets On/Off and Cycling Power ...........................................106 Overview The KX II allows you to control Raritan PX and RPC series rack PDU (power strip) outlets connected to the KX II through a D2CIM-PWR.
Chapter 5: Rack PDU (Power Strip) Outlet Control Control - Turn outlets on or off, or cycle their power. Association - The ports associated with the outlet. Initially, when you open the Powerstrip page, the power strips that are currently connected to the KX II are displayed in the Powerstrip drop-down. Additionally, information relating to the currently selected power strip is displayed.
Chapter 5: Rack PDU (Power Strip) Outlet Control 2. Click OK on the Power Off dialog. 3. Click OK on the Power Off confirmation dialog. The outlet will be turned off and its state will be displayed as 'off'. To cycle the power of an outlet: 1. Click Cycle next to the outlet you want to cycle. The Power Cycle Port dialog opens. 2. Click OK. The outlet will then cycle (note that this may take a few seconds). 3. Once the cycling is complete the dialog will open. Click OK to close the dialog.
Chapter 6 USB Profiles In This Chapter Overview ................................................................................................108 CIM Compatibility ..................................................................................109 Available USB Profiles ...........................................................................109 Selecting Profiles for a KVM Port ..........................................................
Chapter 6: USB Profiles CIM Compatibility In order to make use of USB profiles, you must use a virtual media CIM with updated firmware. For a list of virtual media CIMs, see Supported Computer Interface Module (CIMs) Specifications (on page 289). A CIM that has not had its firmware upgraded supports a broad range of configurations (keyboard, mouse, CD-ROM, and removable drive), but will not be able to make use of profiles optimized for particular target configurations.
Chapter 6: USB Profiles USB profile Description USB enumeration will trigger whenever Virtual Media is connected or disconnected Restrictions: USB bus speed limited to full-speed (12 MBit/s) Absolute mouse synchronization not supported Virtual CD-ROM and disk drives cannot be used simultaneously BIOS Dell Optiplex 790 Keyboard Only Use this profile for Dell Optiplex 790 when using Keyboard Macros during BIOS operations. Only keyboard is enabled with this profile.
Chapter 6: USB Profiles USB profile Description BIOS Generic BIOS Generic Use this profile when Generic OS profile does not work on the BIOS. WARNING: USB enumeration will trigger whenever virtual media is connected or disconnected.
Chapter 6: USB Profiles USB profile Description BIOS Lenovo ThinkPad T61 & X61 BIOS Lenovo ThinkPad T61 and X61 (boot from virtual media) Use this profile to boot the T61 and X61 series laptops from virtual media. Restrictions: USB bus speed limited to full-speed (12 MBit/s) Generic The generic USB profile resembles the behavior of the original KX3 release. Use this for Windows 2000® operating system, Windows XP® operating system, Windows Vista® operating system and later.
Chapter 6: USB Profiles USB profile Description when using the Mac Boot Menu MAC OS X® 10.4.9 (and later) Mac OS X version 10.4.9 (and later) This profile compensates the scaling of mouse coordinates introduced in recent versions of Mac OS X. Select this if the remote and local mouse positions get out of sync near the desktop borders.
Chapter 6: USB Profiles USB profile Description Keyboard and Mouse (Type 2) first Mass Storage USB bus speed limited to full-speed (12 MBit/s) Virtual CD-ROM and disk drives cannot be used simultaneously WARNING: USB enumeration will trigger whenever virtual media is connected or disconnected.
Chapter 6: USB Profiles Mouse Modes when Using the Mac Boot Menu When working with USB profiles in, to use the Mouse in the Mac Boot Menu, you must use Single Mouse mode since Absolute Mouse Mode is not supported in the BIOS. To configure the mouse to work at the Boot menu: 1. Reboot the Mac and press the Option key during the reboot to open the Boot menu. The mouse will not respond at this point. 2. Select Single Mouse mode. The mouse now responds. Note: Mouse speed may be slow while in Single Mouse mode.
Chapter 7 User Management In This Chapter User Groups ..........................................................................................116 Users .....................................................................................................125 Authentication Settings ..........................................................................128 Changing a Password ...........................................................................
Chapter 7: User Management User Group List User groups are used with local and remote authentication (via RADIUS or LDAP/LDAPS). It is a good idea to define user groups before creating individual users since, when you add a user, you must assign that user to an existing user group. The User Group List page displays a list of all user groups, which can be sorted in ascending or descending order by clicking on the Group Name column heading.
Chapter 7: User Management 2. Type a descriptive name for the new user group into the Group Name field (up to 64 characters). 3. Select the checkboxes next to the permissions you want to assign to all of the users belonging to this group. See Setting Permissions. 4. Specify the server ports and the type of access for each user belonging to this group. See Setting Port Permissions (on page 121) 5. Set the IP ACL. This feature limits access to the KX II device by specifying IP addresses.
Chapter 7: User Management Note: Several administrative functions are available within and from the KX II Local Console. These functions are available only to members of the default Admin group.
Chapter 7: User Management Setting Permissions Important: Selecting the User Management checkbox allows the members of the group to change the permissions of all users, including their own. Carefully consider granting these permissions. Permission Description Device Access While Under CC-SG Management Allows users and user groups with this permission to directly access the KX II using an IP address when Local Access is enabled for the device in CC-SG.
Chapter 7: User Management Permission Description settings. If you are using a tiered configuration in which a base KX II device is used to access multiple other tiered devices, user, user group and remote authentication settings must be consistent across all devices. Setting Port Permissions For each server port, you can specify the access type the group has, as well as the type of port access to the virtual media and the power control. Please note that the default setting for all permissions is Deny.
Chapter 7: User Management VM access Power control access option Description Deny Deny power control to the target server Access Full permission to power control on a target server For blade chassis, the port access permission will control access to the URLs that have been configured for that blade chassis. The options are Deny or Control. In addition, each blade housed within the chassis has its own independent Port Permissions setting.
Chapter 7: User Management Use the IP ACL section of the Group page to add, insert, replace, and delete IP access control rules on a group-level basis. To add (append) rules: 1. Type the starting IP address in the Starting IP field. 2. Type the ending IP address in the Ending IP field. 3. Choose the action from the available options: Accept - IP addresses set to Accept are allowed access to the KX II device. Drop - IP addresses set to Drop are denied access to the KX II device. 4. Click Append.
Chapter 7: User Management 2. Click Delete. 3. When prompted to confirm the deletion, click OK. Important: ACL rules are evaluated in the order in which they are listed. For instance, in the example shown here, if the two ACL rules were reversed, Dominion would accept no communication at all. Tip: The rule numbers allow you to have more control over the order in which the rules are created. Modifying an Existing User Group Note: All permissions are enabled for the Admin group and cannot be changed.
Chapter 7: User Management 2. Click Delete. 3. When prompted to confirm the deletion, click OK. Users Users must be granted user names and passwords to gain access to the KX II. This information is used to authenticate users attempting to access your KX II. Up to 254 users can be created for each user group.
Chapter 7: User Management 6. To activate the new user, leave the Active checkbox selected. Click OK. View the KX II Users List The User List page displays a list of all users including their user name, full name, and user group. The list can be sorted on any of the columns by clicking on the column name. From the User List page, you can add, modify, or delete users. KX II users with User Management privileges can disconnect users from ports or log them off (force log off) as needed.
Chapter 7: User Management Username - username for user logins and target connections Access From - IP address of client PC accessing the KX II Status - current Active or Inactive status of the connection To view users by port: Choose User Management > User by Port. The Users by Port page opens. Disconnecting Users from Ports Disconnecting users disconnects them from the target port without logging them off of the KX II.
Chapter 7: User Management Modifying an Existing User To modify an existing user: 1. Open the User List page by choosing User Management > User List. 2. Locate the user from among those listed on the User List page. 3. Click the user name. The User page opens. 4. On the User page, change the appropriate fields. See Adding a New User (on page 125) for information about how to get access the User page. 5. To delete a user, click Delete. You are prompted to confirm the deletion. 6. Click OK.
Chapter 7: User Management 4. If you choose LDAP/LDAPS, read the section entitled Implementing LDAP Remote Authentication for information about completing the fields in the LDAP section of the Authentication Settings page. 5. If you choose RADIUS, read the section entitled Implementing RADIUS Remote Authentication for information about completing the fields in the RADIUS section of the Authentication Settings page. 6. Click OK to save. To return to factory defaults: Click Reset to Defaults.
Chapter 7: User Management Microsoft Active Directory. Active Directory is an implementation of LDAP/LDAPS directory services by Microsoft for use in Windows environments. 8. Type the name of the Active Directory Domain if you selected Microsoft Active Directory. For example, acme.com. Consult your Active Directive Administrator for a specific domain name. 9. In the User Search DN field, enter the Distinguished Name of where in the LDAP database you want to begin searching for user information.
Chapter 7: User Management 11. If you entered a Distinguished Name for the Administrative User, you must enter the password that will be used to authenticate the Administrative User's DN against the remote authentication server. Enter the password in the Secret Phrase field and again in the Confirm Secret Phrase field (up to 128 characters). LDAP/LDAP Secure 12. Select the Enable Secure LDAP checkbox if you would like to use SSL. This will enable the Enable LDAPS Server Certificate Validation checkbox.
Chapter 7: User Management 15. Select the Enable LDAPS Server Certificate Validation checkbox to use the previously uploaded root CA certificate file to validate the certificate provided by the server. If you do not want to use the previously uploaded root CA certificate file, leave this checkbox deselected. Disabling this function is the equivalent of accepting a certificate that has been signed by an unknown certifying authority.
Chapter 7: User Management Once the test is completed, a message will be displayed that lets you know the test was successful or, if the test failed, a detailed error message will be displayed. It will display successful result or detail error message in failure case. It also can display group information retrieved from remote LDAP server for the test user in case of success.
Chapter 7: User Management Important Notes Group Name is case sensitive. The KX II provides the following default groups that cannot be changed or deleted: Admin and . Verify that your Active Directory server does not use the same group names. If the group information returned from the Active Directory server does not match the KX II group configuration, the KX II automatically assigns the group of to users who authenticate successfully.
Chapter 7: User Management 9. The default number of retries is 3 Retries. This is the number of times the KX II will send an authentication request to the RADIUS server. 10. Choose the Global Authentication Type from among the options in the drop-down list: PAP - With PAP, passwords are sent as plain text. PAP is not interactive. The user name and password are sent as one data package once a connection is established, rather than the server sending a login prompt and waiting for a response.
Chapter 7: User Management Cisco ACS 5.x for RADIUS Authentication If you are using a Cisco ACS 5.x server, after you have configured the KX II for RADIUS authentication, complete the following steps on the Cisco ACS 5.x server. Note: The following steps include the Cisco menus and menu items used to access each page. Please refer to your Cisco documentation for the most up to date information on each step and more details on performing them.
Chapter 7: User Management Returning User Group Information via RADIUS When a RADIUS authentication attempt succeeds, the KX II determines the permissions for a given user based on the permissions of the user's group. Your remote RADIUS server can provide these user group names by returning an attribute, implemented as a RADIUS FILTER-ID. The FILTER-ID should be formatted as follows: Raritan:G{GROUP_NAME} where GROUP_NAME is a string denoting the name of the group to which the user belongs.
Chapter 7: User Management 138 Attribute Data Acct-Status (40) Stop(2) - Stops the accounting NAS-Port-Type (61) VIRTUAL (5) for network connections. NAS-Port (5) Always 0. NAS-IP-Address (4) The IP address for the KX II. User-Name (1) The user name entered at the login screen. Acct-Session-ID (44) Session ID for accounting.
Chapter 7: User Management User Authentication Process Remote authentication follows the process specified in the flowchart below: 139
Chapter 7: User Management Changing a Password To change your KX II password: 1. Choose User Management > Change Password. The Change Password page opens. 2. Type your current password in the Old Password field. 3. Type a new password in the New Password field. Retype the new password in the Confirm New Password field. Passwords can be up to 64 characters in length and can consist of English alphanumeric characters and special characters. 4. Click OK. 5.
Chapter 8 Device Management In This Chapter Network Settings ...................................................................................141 Device Services .....................................................................................145 Power Supply Setup ..............................................................................170 Configuring Ports ...................................................................................171 Connect and Disconnect Scripts ....................
Chapter 8: Device Management Assign the KX II an IP Address To assign an IP address to the KX II: 1. Choose Device Settings > Network. The Network Settings page opens. 2. Specify a meaningful Device Name for your KX II device. Up to 32 alphanumeric and valid special characters, no spaces between characters. 3. Next, configure the IPv4, IPv6 and DNS settings. Configure the IPv4 Settings 1. In the IPv4 section, enter or select the appropriate IPv4-specific network settings: a. Enter the IP Address if needed.
Chapter 8: Device Management Configure the IPv6 Settings 1. If using IPv6, enter or select the appropriate IPv6-specific network settings in the IPv6 section: a. Select the IPv6 checkbox to activate the fields in the section and enable IPv6 on the device. b. Enter a Global/Unique IP Address. This is the IP address assigned to the KX II. c. Enter the Prefix Length. This is the number of bits used in the IPv6 address. d. Enter the Gateway IP Address. e. Link-Local IP Address.
Chapter 8: Device Management 2. If Use the Following DNS Server Addresses is selected, whether or not DHCP is selected, the addresses entered in this section is used to connect to the DNS server. Enter the following information if the Following DNS Server Addresses is selected. These addresses are the primary and secondary DNS addresses used if the primary DNS server connection is lost due to an outage. a. Primary DNS Server IP Address b. Secondary DNS Server IP Address 3. When finished, click OK.
Chapter 8: Device Management Note: Because a failover port is not activated until after a failover has actually occurred, Raritan recommends that you not monitor the port or monitor it only after a failover occurs. When this option is enabled, the following two fields are used: Ping Interval (seconds) - Ping interval determines how often the KX II checks the status of the network path to the designated gateway. The default ping interval is 30 seconds.
Chapter 8: Device Management 3. Enter the SSH Port information. The standard SSH TCP port number is 22 but the port number can be changed to provide a higher level of security operations. 4. Click OK. HTTP and HTTPS Port Settings You are able to configure HTTP and/or HTTPS ports used by the KX II. For example, if you are using the default HTTP port 80 for another purpose, changing the port will ensure the device does not attempt to use it. To change the HTTP and/or HTTPS port settings: 1.
Chapter 8: Device Management Configuring and Enabling Tiering The tiering feature allows you to access KX II targets and PDUs through one base KX II device. This feature is available for standard KX II devices as well as KX2-808, KX2-832 and KX2-864 devices. Note: Base and tiered devices must all be operating with the same firmware revision. Note: Dual Video port targets attached to a tier device should only be connected via the tier device, not through the tier base device.
Chapter 8: Device Management Port configuration, including changing the CIM name, must be done directly from each device. It cannot be done from the base device for tiered target ports. Tiering also supports the use of KVM switches to switch between servers. See Configuring KVM Switches (on page 174). Enabling Tiering To enable tiering: 1. From the base KX II tier device, select Device Settings > Device Services to open the Device Service Settings page. 2. Select Enable Tiering as Base. 3.
Chapter 8: Device Management 6. In the Tier Secret field, enter the same secret word you entered for the base device on the Device Settings page. Click OK. Tiering - Target Types, Supported CIMS and Tiering Configurations Blade Chassis Blade chassis that attached directly to the base are accessible. Power Control You can power on and off targets that are a part of the tiered configuration. These targets are accessed from the Port Access page.
Chapter 8: Device Management Unsupported and Limited Features on Tiered Targets The following features are not supported on tiered targets: 150 Blade chassis on tiered devices Audio on tiered devices Smart cards on tiered devices Virtual media tiered devices MCCAT as a tiered device Port group management is limited to creating port groups of members directly attached to the base
Chapter 8: Device Management Cabling Example in Tiered Configurations The following diagram illustrates the cabling configurations between a KX II tiered device and a KX II base device.
Chapter 8: Device Management Diagram key Target server CIM from target server to the KX II tiered device KX II tiered device D2CIM-DVUSB CIM from the KX II tiered device to the KX II base device KX II base device Enabling Direct Port Access via URL Direct port access allows users to bypass having to use the device's Login dialog and Port Access page.
Chapter 8: Device Management Direct Port Access URL Syntax for the Virtual KVM Client (VKC) If you are using the Virtual KVM Client (VKC) and direct port access, use one of the following syntaxes for standard ports: https://IPaddress/dpa.asp?username=username&password=passwo rd&port=port number Or https://IPaddress/dpa.asp?username=username&password=passwo rd&portname=port name For blade chassis, the port must be designated by both the port number or name, and slot number.
Chapter 8: Device Management Direct Port Access URL Syntax for the Active KVM Client (AKC) If you are using the Active KVM Client (AKC) and direct port access, use: https://IPaddress/dpa.asp?username=username&password=passwo rd&port=port number&client=akc Or https://IPaddress/dpa.asp?username=username&password=passwo rd&port=port name&client=akc For blade chassis, the port must be designated by both the port number or name, and slot number. https://IPaddress/dpa.
Chapter 8: Device Management Enable Direct Port Access To enable direct port access: 1. Choose Device Settings > Device Services. The Device Service Settings page opens. 2. Select Enable Direct Port Access via URL if you would like users to have direct access to a target via the Dominion device by passing in the necessary parameters in the URL. 3. Click OK.
Chapter 8: Device Management Enabling the AKC Download Server Certificate Validation If you are using the AKC client, you can choose to use the Enable AKC Download Server Certificate Validation feature or opt not to use this feature. Note: When operating in IPv4 and IPv6 dual stack mode with 'Enable AKC Download Server Certificate Validation' feature, Microsoft® ClickOnce® requires that the server certificate CN should not contain a zero compressed form of IPv6 address.
Chapter 8: Device Management 2. Launch Internet Explorer® using the KX II IP address as the URL. A Certificate Error message will be displayed. 3. Select View Certificates. 4. On the General tab, click Install Certificate. The certificate is then installed in the Trusted Root Certification Authorities store. 5. After the certificate is installed, the KX II IP address should be removed from the Trusted Site zone. To enable AKC download server certificate validation: 1.
Chapter 8: Device Management 3. Select either or both Enable SNMP v1/v2c and Enable SNMP v3. At least one option must be selected. Required 4. Complete the following fields for SNMP v1/v2c (if needed): a. Community - the device's community string b. Community Type - grant either Read-Only or Read-Write access to the community users Note: An SNMP community is the group to which devices and management stations running SNMP belong. It helps define where information is sent.
Chapter 8: Device Management Configure SNMP traps on the Event Management - Settings page, which can be quickly accessed by clicking the SNMP Trap Configuration link. See Configuring SNMP Traps (on page 162)for information on creating SNMP traps and List of KX II SNMP Traps (on page 165) for a list of available KX II SNMP traps. The events that are captured once an SNMP trap is configured are selected on the Event Management - Destination page. See Configuring Event Management - Destinations (on page 169).
Chapter 8: Device Management This information is used to configure modem settings. Because different modems have different ways of settings these values, this document does not specify how to set these values, rather the user should refer to the modem to create the appropriate modem-specific string. a. Modem Settings: Enable RTS/CTS flow control Send data to the computer on receipt of RTS CTS should be configured to only drop if required by flow control.
Chapter 8: Device Management See Certified Modems (on page 307) for information on certified modems that work with the KX II. For information on settings that will give you the best performance when connecting to the KX II via modem, see Creating, Modifying and Deleting Profiles in MPC - Generation 2 Devices in the KVM and Serial Access Clients Guide. Note: Modem access directly to the KX II HTML interface is not supported. You must use standalone MPC to access the KX II via modem.
Chapter 8: Device Management Event Management The KX II Event Management feature allows you enable and disable the distribution of system events to SNMP Managers, the Syslog and the audit log. These events are categorized, and for each event you can determine whether you want the event sent to one or several destinations. Configuring Event Management - Settings Configure SNMP traps and the syslog configuration from the Event Management - Settings page. See Configuring SNMP Traps (on page 162).
Chapter 8: Device Management a. Destination IP/Hostname - the IP or hostname of the SNMP manager. Up to five (5) SNMP managers can be created Note: IPv6 addresses cannot exceed 80 characters in length for the host name. b. Port Number - the port number used by the SNMP manager c. Community - the device's community string Note: An SNMP community is the group to which devices and management stations running SNMP belong. It helps define where information is sent.
Chapter 8: Device Management Use the Link to SNMP Agent Configuration link to quickly navigate to the Devices Services page from the Event Management - Settings page. The events that are captured once an SNMP trap is configured are selected on the Event Management - Destination page. See Configuring Event Management - Destinations (on page 169). KX II supports SNMP logging for SNMP v1/v2c and/or v3. SNMP v1/v2c defines message formats and protocol operations when SNMP logging is enabled.
Chapter 8: Device Management Use the reset to factory defaults feature to remove the SNMP configuration and set the KX II to its original factory default. To reset to factory defaults: Click Reset To Defaults. WARNING: When using SNMP traps over UDP, it is possible for the KX II and the router that it is attached to fall out of synchronization when the KX II is rebooted, preventing the reboot completed SNMP trap from being logged.
Chapter 8: Device Management 166 Trap Name Description networkFailure An Ethernet interface of the product can no longer communicate over the network. networkParameterChanged A change has been made to the network parameters. passwordSettingsChanged Strong password settings have changed. portConnect A previously authenticated user has begun a KVM session. portConnectionDenied A connection to the target port was denied.
Chapter 8: Device Management Trap Name Description userForcedLogout A user was forcibly logged out by Admin userLogin A user has successfully logged into the KX II and has been authenticated. userLogout A user has successfully logged out of the KX II properly. userModified A user account has been modified. userPasswordChanged This event is triggered if the password of any user of the device is modified.
Chapter 8: Device Management Note: If you have Read-Write privileges to the MIB file, use a MIB editor to make changes to the file. SysLog Configuration To configure the Syslog (enable Syslog forwarding): 1. Select Enable Syslog Forwarding to log the device's messages to a remote Syslog server. 2. Type the IP Address/Hostname of your Syslog server in the IP Address field. 3. Click OK. Note: IPv6 addresses cannot exceed 80 characters in length for the host name.
Chapter 8: Device Management Configuring Event Management - Destinations System events, if enabled, generate SNMP notification events (traps), or can be logged to the syslog or audit log. Use the Event Management Destinations page to select the system events to track and where to send this information. Note: SNMP traps are generated only if the SNMP Logging Enabled option is selected. Syslog events are generated only if the Enable Syslog Forwarding option is selected.
Chapter 8: Device Management Power Supply Setup The KX II provides dual power supplies, and can automatically detect and provide notification regarding the status of these power supplies. Use the Power Supply Setup page to specify whether you are using one or both of the power supplies. Proper configuration ensures that the KX II sends the appropriate notifications should a power supply fail. For example, if power supply number one fails, the power LED at the front of the unit will turn red.
Chapter 8: Device Management Note: If either of these checkboxes is selected and power input is not actually connected, the power LED at the front of the unit turns red. To turn off the automatic detection: Deselect the checkbox for the appropriate power supply. To reset to factory defaults: Click Reset To Defaults. Note: The KX II does NOT report power supply status to CommandCenter. Dominion I (generation 1), however, does report power supply status to CommandCenter.
Chapter 8: Device Management Alternatively, rename ports that are currently not connected to the KX II via a CIM and, as such, have a status of Not Available. To rename a port with a status of Not Available, do one of the following: Rename the port. When a CIM is attached the CIM name will be used. Rename the port, and select 'Persist name on Next CIM Insertion'. When a CIM is attached the name that has been assigned will be copied into the CIM.
Chapter 8: Device Management Configuring Standard Target Servers To name the target servers: 1. Connect all of the target servers if you have not already done so. See Step 3: Connect the Equipment (on page 16) for a description of connecting the equipment. 2. Choose Device Settings > Port Configuration. The Port Configuration page opens. 3. Click the Port Name of the target server you want to rename. The Port Page opens. 4. Select Standard KVM Port as the subtype for the port. 5.
Chapter 8: Device Management 8. Click OK. Configuring KVM Switches The KX II also supports use of hot key sequences to switch between targets. In addition to using hot key sequences with standard servers, KVM switching is supported by blade chassis and in tiered configurations. Important: In order for user groups to see the KVM switch that you create, you must first create the switch and then create the group.
Chapter 8: Device Management Note: Only one switch will appear in the drop-down. 5. Select KVM Switch Hot Key Sequence. 6. Enter the Maximum Number of Target Ports (2-32). 7. In the KVM Switch Name field, enter the name you want to use to refer to this port connection. 8. Activate the targets that the KVM switch hot key sequence will be applied to. Indicate the KVM switch ports have targets attached by selecting ‘Active’ for each of the ports. 9.
Chapter 8: Device Management Configuring CIM Ports The KX II supports the use of standard and virtual media CIMs to connect a server to the KX II. To access a CIM to configure: 1. Choose Device Settings > Port Configuration. The Port Configuration page opens. 2. Click the Port Name of the target server you want to rename. The Port Page opens. Configure the CIM Settings 1. Select Standard KVM Port as the subtype for the port. 2. Assign a name to identify the server connected to that port.
Chapter 8: Device Management If you are using an HDMI CIM, some operating system/video card combinations may offer a limited range of RGB values. Improve the colors by selecting the DVI Compatibility Mode checkbox. Apply Selected Profiles to Other CIMs 1. Apply the profile to other CIMs by selecting them from the list in the Apply Selected Profiles to Other Ports section of the Port Configuration page. Apply a Native Display Resolution to Other CIMs 1.
Chapter 8: Device Management Connecting a Rack PDU Raritan PX series rack PDUs (power strips) are connected to the Dominion device using the D2CIM-PWR CIM. To connect the rack PDU: 1. Connect the male RJ-45 of the D2CIM-PWR to the female RJ-45 connector on the serial port of the rack PDU. 2. Connect the female RJ-45 connector of the D2CIM-PWR to any of the available female system port connectors on the KX II using a straight through Cat5 cable. 3.
Chapter 8: Device Management Naming the Rack PDU (Port Page for Power Strips) Note: PX rack PDUs (power strips) can be named in the PX as well as in the KX II. Once a Raritan remote rack PDU is connected to the KX II, it will appear on the Port Configuration page. Click on the power port name on that page to access it. The Type and the Name fields are prepopulated. Note: The (CIM) Type cannot be changed.
Chapter 8: Device Management 3. Click OK.
Chapter 8: Device Management Associating Outlets with Target Servers The Port page opens when you click on a port on the Port Configuration page. From this page, you can make power associations, change the port name to something more descriptive, and update target server settings if you are using the D2CIM-VUSB CIM. The (CIM) Type and the (Port) Name fields are prepopulated; note that the CIM type cannot be changed.
Chapter 8: Device Management Removing Power Associations When disconnecting target servers and/or rack PDUs from the device, all power associations should first be deleted. When a target has been associated with a rack PDU and the target is removed from the device, the power association remains. When this occurs, you are not able to access the Port Configuration for that disconnected target server in Device Settings so that the power association can be properly remove. To remove a rack PDU association: 1.
Chapter 8: Device Management Configuring Blade Chassis In addition to standard servers and rack PDUs (power strips), you can control blade chassis that are plugged into the KX II device port. Up to eight blade chassis can be managed at a given time. The blade chassis must be configured as a blade chassis subtype. If the blade chassis type is supported, it is automatically detected once they are connected. If the type is not supported, the blade must be configured manually.
Chapter 8: Device Management Two modes of operation are provided for blade chassis: manual configuration and auto-discovery, depending on the blade chassis capabilities. If a blade chassis is configured for auto-discovery, the Dominion device tracks and updates the following: When a new blade server is added to the chassis. When an existing blade server is removed from the chassis.
Chapter 8: Device Management Generic Blade Chassis Configuration The Generic Blade Chassis' selection provides only a manual configuration mode of operation. See Supported Blade Chassis Models (on page 198), Supported CIMs for Blade Chassis (on page 199), and Required and Recommended Blade Chassis Configurations (on page 201) for important, additional information when configuring the blade chassis.
Chapter 8: Device Management 9. In the Blade Chassis Managed Links section of the page, you are able to configure the connection to a blade chassis web browser interface if one is available. Click the Blade Chassis Managed Links icon page. to expand the section on the The first URL link is intended for use to connect to the blade chassis Administration Module GUI. Note: Access to the URL links entered in this section of the page is governed by the blade chassis port permissions. a.
Chapter 8: Device Management 13. Select the CIMs native, display resolution from the Display Native Resolution drop-down. This is the preferred resolution and timing mode of the digital CIM. Once a resolution is selected, it is applied to the CIM. If no selection is made, the default 1024x1280@60Hz resolution is used. 14. Click OK to save the configuration.
Chapter 8: Device Management c. Administrative Module Primary IP Address/Host Name - Enter the primary IP address for the blade chassis. Required for auto-discovery mode d. Port Number - The default port number for the blade chassis is 22. Change the port number if applicable. Required for auto-discovery mode e. Username - Enter the username used to access the blade chassis. Required for auto-discovery mode f. Password - Enter the password used to access the blade chassis.
Chapter 8: Device Management b. URL - Enter the URL to the interface. See Blade Chassis Sample URL Formats (on page 203) for sample configurations for the Dell M1000e. c. Username - Enter the username used to access the interface. d. Password - Enter the password used to access the interface. Note: Leave the username and password fields blank for DRAC, ILO, and RSA web applications or the connection will fail. 6.
Chapter 8: Device Management d. Port Number - The default port number for the blade chassis is 22. Not applicable. e. Username - Not applicable. f. Password - Not applicable. 2. Change the blade chassis name if needed. 3. Indicate the blades that are installed in the blade chassis by checking the Installed checkbox next to each slot that has a blade installed. Alternatively, use the Select All checkbox. If needed, change the blade server names. 4.
Chapter 8: Device Management 5. USB profiles do not apply to Dell chassis. 6. Click OK to save the configuration. IBM Blade Chassis Configuration See Supported Blade Chassis Models (on page 198), Supported CIMs for Blade Chassis (on page 199), and Required and Recommended Blade Chassis Configurations (on page 201) for important, additional information when configuring the blade chassis.
Chapter 8: Device Management f. Password - Enter the password used to access the blade chassis. Required for auto-discovery mode 2. If you want the KX II to auto-discover the chassis blades, select the Blade Auto-Discovery checkbox and then click Discover Blades on Chassis Now. Once the blades are discovered, they will be displayed on the page. 3. Change the blade chassis name if needed. If the chassis is already named, that information automatically populates this field.
Chapter 8: Device Management e. The Username Field and Password Field, which are both optional, contain the labels that are expected to be associated with the username and password entries. It is in these fields you should enter the field names for the username and password fields used on the login screen for the web application. You can view the HTML source of the login screen to find the field names, not the field labels.
Chapter 8: Device Management The first URL link is intended for use to connect to the blade chassis Administration Module GUI. Note: Access to the URL links entered in this section of the page is governed by the blade chassis port permissions. a. Active - To activate the link once it is configured, select the Active checkbox. Leave the checkbox deselected to keep the link inactive. Entering information into the link fields and saving can still be done even if Active is not selected.
Chapter 8: Device Management Tips for Adding a Web Browser Interface You can add a Web Browser Interface to create a connection to a device with an embedded web server. A Web Browser interface can also be used to connect to any web application, such as the web application associated with an RSA, DRAC or ILO Processor card. You must have DNS configured or URLs will not resolve. You do not need to have DNS configured for IP addresses. To add a web browser interface: 1.
Chapter 8: Device Management HP and Cisco UCS Blade Chassis Configuration (Port Group Management) The KX II supports the aggregation of ports connected to certain types of blades into a group representing the blade chassis. Specifically, Cisco® UCS, HP® BladeServer blades and Dell® PowerEdge™ 1855/1955 blades when the Dell PowerEdge 1855/1955 is connected from each individual blade to a port on the KX II.
Chapter 8: Device Management 3. Enter a Port Group Name. The port group name is not case sensitive and can contain up to 32 characters. 4. Select the Blade Server Group checkbox. If you want to designate that these ports are attached to blades housed in a blade chassis (for example, HP c3000 or Dell PowerEdge 1855), select the Blade Server Group checkbox.
Chapter 8: Device Management Supported Blade Chassis Models This table contains the blade chassis models that are supported by the KX II and the corresponding profiles that should be selected per chassis model when configuring them in the KX II application. A list of these models can be selected on the Port Configuration page from the Blade Server Chassis Model drop-down, which appears when the Blade Chassis radio button is selected.
Chapter 8: Device Management Supported CIMs for Blade Chassis The following CIMs are supported for blade chassis being managed through the KX II: DCIM-PS2 DCIM-USBG2 D2CIM-VUSB D2CIM-DVUSB Following is a table containing supported CIMs for each blade chassis model that the KX II supports.
Chapter 8: Device Management Blade chassis Connection method Recommended CIM(s) Both modules enable you to connect a PS/2-compatible keyboard, mouse and video monitor to the system (using a custom cable provided with the system). Source: Dell PowerEdge 1955 Owner's Manual Dell PowerEdge M1000e DCIM-USBG2 The HP c-Class Blade SUV Cable enables you to perform blade chassis administration, configuration, and diagnostic procedures by connecting video and USB devices directly to the server blade.
Chapter 8: Device Management Blade chassis Connection method Technology Recommended CIM(s) IBM BladeCenter E The current model BladeCenter E chassis (8677-3Rx) ships standard with one Advanced Management Module. DCIM-USBG2 D2CIM-DVUSB Source: IBM BladeCenter Products and Technology IBM BladeCenter T The BladeCenter T chassis ships standard with one Advanced Management Module.
Chapter 8: Device Management This table contains information on limitations and constraints that apply to configuring blade chassis to work with the KX II. Raritan recommends that all of the information below is followed. Blade chassis ® Dell PowerEdge™ M1000e Required/recommended action Disable the iKVM GUI screensaver. An authorize dialog will appear, preventing iKVM from working correctly, if this is not done. Exit the iKVM GUI menu before attaching Dell's chassis to a Raritan CIM.
Chapter 8: Device Management Blade chassis Required/recommended action Do not designate any slots for scan operations in the iKVM GUI Setup Scan menu or the iKVM may not work properly. To avoid having the iKVM GUI display upon connecting to the blade chassis, set the Screen Delay Time to 8 seconds. Recommend that 'Timed' and 'Displayed' be selected during iKVM GUI Flag Setup. This will allow you to visually confirm the connection to the desired blade slot.
Chapter 8: Device Management Blade chassis Dell 1855 ® IBM BladeCenter® E or H Sample URL format Password: calvin Password Field: password URL: https://192.168.60.33/Forms/f_login Username: root Username Field: TEXT_USER_NAME Password: calvin Password Field: TEXT_PASSWORD http://192.168.84.217/private/welcome.ssi Configuring USB Profiles (Port Page) You choose the available USB profiles for a port in the Select USB Profiles for Port section of the Port page.
Chapter 8: Device Management 2. Click the Port Name for the KVM port you want to edit. The Port page opens. To select the USB profiles for a KVM port: 1. In the Select USB Profiles for Port section, select one or more USB profiles from the Available list. Shift-Click and drag to select several continuous profiles. Ctrl-Click to select several discontinuous profiles. 2. Click Add. The selected profiles appear in the Selected list.
Chapter 8: Device Management Configuring KX II Local Port Settings From the Local Port Settings page, you can customize many settings for the KX II Local Console including keyboard, hot keys, video switching delay, power save mode, local user interface resolution settings, and local user authentication. Further, you can change a USB profile from the local port. For the KX2-808, KX2-832 and KX2-864, you are also able to configure the extended local port from the Local Port Settings page.
Chapter 8: Device Management Note: If you are using KX2-808, KX2-832 and KX2-864 as tiered devices, you must connect them to the base KX II via the extended local port. 4. If you are using the tiering feature, select the Enable Local Port Device Tiering checkbox and enter the tiered secret word in the Tier Secret field. In order to configure tiering, you must also configure the base device on the Device Services page. See Configuring and Enabling Tiering (on page 147) for more information on tiering. 5.
Chapter 8: Device Management Note: Keyboard use for Chinese, Japanese, and Korean is for display only. Local language input is not supported at this time for KX II Local Console functions. Note: If using a Turkish keyboard, you must connect to a target server through the Active KVM Client (AKC). It is not supported by other Raritan clients. 7. Choose the local port hotkey. The local port hotkey is used to return to the KX II Local Console interface when a target server interface is being viewed.
Chapter 8: Device Management 1280x1024 13. Choose the refresh rate from the drop-down list. The browser will be restarted when this change is made. 60 Hz 75 Hz 14. Choose the type of local user authentication. Local/LDAP/RADIUS. This is the recommended option. For more information about authentication, see Remote Authentication. None. There is no authentication for Local Console access. This option is recommended for secure environments only.
Chapter 8: Device Management KX2-808, KX2-832 and KX2-864 Standard and Extended Local Port Settings The KX2-808, KX2-832 and KX2-864 provide you with two local port options: the standard local port and the extended local port. Each of these port options is enabled and disabled from the Remote Console or from the Local Console on the Local Port Settings page. For more information, see Configuring KX II Local Port Settings (on page 206).
Chapter 8: Device Management Connect and Disconnect Scripts The KX II provides the ability to execute key macro scripts when connecting to or disconnecting from a target. You can create and edit your own scripts on the Connection Script page to perform additional actions when connecting to or disconnecting from targets. Alternatively, you can import existing connection scripts in XML file format. Scripts that you create in KX II can also be exported in XML file format.
Chapter 8: Device Management 3. In the Apply Selected Scripts to Ports section, select the target(s) you want to apply the script to using Select All or clicking on the checkbox to the left of each target to apply the script to only select targets. 4. Click Apply Scripts. Once the script is added to the target, it appears under the Scripts Currently in Use column in the Apply Selected Scripts to Ports section. To remove a script from targets: 1.
Chapter 8: Device Management For example, select F1-F16 to display the function key set in the Add box. Select a function key and add it to the Script box. Next, select Letters from the Key Set drop-down and add a letter key to the script. 8. Optionally, add text that will display when the script is executed. a. Click Construct Script from Text to open the Construct Script From Text page. b. Enter the script in the text box. For example, enter "Connected to Target". c.
Chapter 8: Device Management 214
Chapter 8: Device Management Modifying Scripts To modify existing scripts: 1. Click Device Settings > Connection Scripts. The Connection Scripts page opens. 2. In the Available Connection Scripts section, select the script you want to modify and click Modify. The page is then in Edit mode. 3. Make changes as needed. Click OK when finished. Importing and Exporting Scripts You are able to import and export connect and disconnect scripts that are in XML file format.
Chapter 8: Device Management 5. Click Import. The Configuration Scripts page opens and the imported scripts are displayed. To export a disconnect script: 1. Click Device Settings > Configuration Scripts. The Configuration Scripts page opens. 2. In the Available Connection Scripts section, select the script you want to export and click Export. A dialog prompting you to open or save the XML file appears. 3. Save the XML file or open it in an XML editor.
Chapter 8: Device Management Creating Port Groups The KX II supports the aggregation of multiple ports into a single port group.Port groups consist solely of ports configured as standard KVM ports. A port may only be a member of a single group. Ports that are available to be included in a port group are displayed in the Select Port for Group > Available list. Once a port is added to a port group, it is not available to add to another port group.
Chapter 8: Device Management Creating a Dual Video Port Group The dual video port groups feature allows you to group two video ports into one group. Use this feature when you need to connect to a server with two video cards/ports, and you want to access both ports from the same remote client at the same time. Note: Dual port video groups are not supported by models with only one KVM channel such as KX3-108 and KX3-116 models.
Chapter 8: Device Management Note: If a port is already a part of blade server port group, another dual video port group, or 'standard' port group, the port is not an option since ports can only belong to a single port group at a time. 3. Select the Dual Video Port Group radio button. 4. From the Select Ports for Group section, click on the port you are designating as the primary port, then click Add to add it to the Selected text box. Be sure to add the primary port first.
Chapter 8: Device Management 3. Click Apply. Click Reset Defaults to change back to English. Note: Once you apply a new language, the online help is also localized to match your language selection.
Chapter 9 Security Management In This Chapter Security Settings ....................................................................................221 Configuring IP Access Control ..............................................................232 SSL Certificates .....................................................................................234 Security Banner .....................................................................................
Chapter 9: Security Management To reset back to defaults: Click Reset to Defaults. Login Limitations Using login limitations, you can specify restrictions for single login, password aging, and the logging out idle users. Limitation Description Enable single login limitation When selected, only one login per user name is allowed at any time. When deselected, a given user name/password combination can be connected into the device from several client workstations simultaneously.
Chapter 9: Security Management Limitation Description Enter the number of days after which a password change is required. The default is 60 days. Log out idle users, After (1-365 minutes) Select the "Log off idle users" checkbox to automatically disconnect users after the amount of time you specify in the "After (1-365 minutes)" field. If there is no activity from the keyboard or mouse, all sessions and all resources are logged out.
Chapter 9: Security Management Strong Passwords Strong passwords provide more secure local authentication for the system. Using strong passwords, you can specify the format of valid KX II local passwords such as minimum and maximum length, required characters, and password history retention. Strong passwords require user-created passwords to have a minimum of 8 characters with at least one alphabetical character and one nonalphabetical character (punctuation character or number).
Chapter 9: Security Management User Blocking The User Blocking options specify the criteria by which users are blocked from accessing the system after the specified number of unsuccessful login attempts. The three options are mutually exclusive: Option Description Disabled The default option. Users are not blocked regardless of the number of times they fail authentication.
Chapter 9: Security Management Option Description Timer Lockout Users are denied access to the system for the specified amount of time after exceeding the specified number of unsuccessful login attempts. When selected, the following fields are enabled: Attempts - The number of unsuccessful login attempts after which the user will be locked out. The valid range is 1 - 10 and the default is 3 attempts. Lockout Time - The amount of time for which the user will be locked out.
Chapter 9: Security Management Encryption & Share Using the Encryption & Share settings you can specify the type of encryption used, PC and VM share modes, and the type of reset performed when the KX II Reset button is pressed. WARNING: If you select an encryption mode that is not supported by your browser, you will not be able to access the KX II from your browser. Note that performance may be impacted once encryption is applied. The extent of the performance impact varies based on the encryption mode.
Chapter 9: Security Management Encryption mode Description browser supports it, otherwise you will not be able to connect. See Checking Your Browser for AES Encryption (on page 229) for more information. AES-256 The Advanced Encryption Standard (AES) is a National Institute of Standards and Technology specification for the encryption of electronic data. 256 is the key length. When AES-256 is specified, be certain that your browser supports it, otherwise you will not be able to connect.
Chapter 9: Security Management 6. If needed, select Local Device Reset Mode. This option specifies which actions are taken when the hardware Reset button (at the back of the device) is depressed. For more information, see Resetting the KX II Using the Reset Button (on page 285). Choose one of the following options: Local device reset mode Description Enable Local Factory Returns the KX II device to the factory defaults.
Chapter 9: Security Management Enabling FIPS 140-2 For government and other high security environments, enabling FIPS 140-2 mode may be required. The KX II uses an embedded FIPS 140-2-validated cryptographic module running on a Linux® platform per FIPS 140-2 Implementation Guidance section G.5 guidelines. Once this mode is enabled, the private key used to generate the SSL certificates must be internally generated; it cannot be downloaded or exported.
Chapter 9: Security Management FIPS 140-2 Support Requirements The KX II supports the use of FIPS 140-2 approved encryption algorithms. This allows an SSL server and client to successfully negotiate the cipher suite used for the encrypted session when a client is configured for FIPS 140-2 only mode. Following are the recommendations for using FIPS 140-2 with the KX II: KX II Set the Encryption & Share to Auto on the Security Settings page. See Encryption & Share (on page 227).
Chapter 9: Security Management Configuring IP Access Control Using IP access control, you control access to your KX II. Note that IP access control restricts traffic of any kind from accessing the KX II, so NTP servers, RADIUS hosts, DNS hosts and so on must be granted access to the KX II. By setting a global Access Control List (ACL) you are ensuring that your device does not respond to packets being sent from disallowed IP addresses.
Chapter 9: Security Management 3. Choose the Policy from the drop-down list. 4. Click Insert. If the rule # you just typed equals an existing rule #, the new rule is placed ahead of the exiting rule and all rules are moved down in the list. Tip: The rule numbers allow you to have more control over the order in which the rules are created. To replace a rule: 1. Specify the rule # you want to replace. 2. Type the IP address and subnet mask in the IPv4/Mask or IPv6/Prefix Length field. 3.
Chapter 9: Security Management SSL Certificates The KX II uses the Secure Socket Layer (SSL) protocol for any encrypted network traffic between itself and a connected client. When establishing a connection, the KX II has to identify itself to a client using a cryptographic certificate. It is possible to generate a Certificate Signing Request (CSR) and install a certificate signed by the Certificate Authority (CA) on the KX II. The CA verifies the identity of the originator of the CSR.
Chapter 9: Security Management f. Country (ISO code) - The country where the organization is located. This is the two-letter ISO code, e.g. DE for Germany, or US for the U.S. g. Challenge Password - Some certification authorities require a challenge password to authorize later changes on the certificate (e.g. revocation of the certificate). Applicable when generating a CSR for CA Certification. h. Confirm Challenge Password - Confirmation of the Challenge Password.
Chapter 9: Security Management b. A message containing all of the information you entered appears. c. The CSR and the file containing the private key used when generating it can be downloaded by clicking Download CSR. d. Send the saved CSR to a CA for certification. You will get the new certificate from the CA. Note: The CSR and the private key file are a matched set and should be treated accordingly.
Chapter 9: Security Management Security Banner KX II provides you with the ability to add a security banner to the KX II login process. This feature requires users to either accept or decline a security agreement before they can access the KX II. The information provided in a security banner will be displayed in a Restricted Service Agreement dialog after users access KX II using their login credentials. The security banner heading and wording can be customized, or the default text can be used.
Chapter 9: Security Management Note: You cannot upload a text file from the local port.
Chapter 10 Maintenance In This Chapter Audit Log................................................................................................239 Device Information .................................................................................240 Backup and Restore ..............................................................................242 USB Profile Management ......................................................................244 Upgrading CIMs ..............................................
Chapter 10: Maintenance To page through the audit log: Use the [Older] and [Newer] links. Device Information The Device Information page provides detailed information about your KX II device and the CIMs in use. This information is helpful should you need to contact Raritan Technical Support. To view information about your KX II and CIMs: Choose Maintenance > Device Information. The Device Information page opens.
Chapter 10: Maintenance DCIM-SUSB D2CIM-VUSB D2CIM-DVUSB D2CIM-DVUSB-DVI D2CIM-DVUSB-HDMI D2CIM-DVUSB Note: Only the numeric portion of the serial numbers are displayed for the DCIM-USB, DCIM-PS2 and DCIM-USB G2 CIMs. For example, XXX1234567 is displayed. The serial number prefix GN is displayed for CIMs that have field configured serial numbers.
Chapter 10: Maintenance Backup and Restore From the Backup/Restore page, you can backup and restore the settings and configuration for your KX II. In addition to using backup and restore for business continuity purposes, you can use this feature as a time-saving mechanism. For instance, you can quickly provide access to your team from another KX II by backing up the user configuration settings from the KX II in use and restoring those configurations to the new KX II.
Chapter 10: Maintenance In IE 7 (and later), IE is used as the default application to open files, so you are prompted to open the file versus save the file. To avoid this, you must change the default application that is used to open files to WordPad®. 2. To do this: a. Save the backup file. The backup file is saved locally on your client machine with the name and location specified. b. Once saved, locate the file and right-click on it. Select properties. c. In general tab, click Change and select WordPad.
Chapter 10: Maintenance USB Profile Management From the USB Profile Management page, you can upload custom profiles provided by Raritan tech support. These profiles are designed to address the needs of your target server’s configuration, in the event that the set of standard profiles does not already address them. Raritan tech support will provide the custom profile and work with you to verify the solution for your target server’s specific needs.
Chapter 10: Maintenance As noted, you may delete a custom profile from the system while it is still designated as an active profile. Doing so will terminate any virtual media sessions that were in place. Handling Conflicts in Profile Names A naming conflict between custom and standard USB profiles may occur when a firmware upgrade is performed.
Chapter 10: Maintenance To upgrade your KX II unit: 1. Locate the appropriate Raritan firmware distribution file (*.RFP) on the Raritan website http://www.raritan.com on the Firmware Upgrades web page. 2. Unzip the file. Please read all instructions included in the firmware ZIP files carefully before upgrading. Note: Copy the firmware update file to a local PC before uploading. Do not load the file from a network drive. 3. Choose Maintenance > Firmware Upgrade. The Firmware Upgrade page opens. 4.
Chapter 10: Maintenance As prompted, close the browser and wait approximately 5 minutes before logging in to the KX II again. again. For information about upgrading the device firmware using the Multi-Platform Client, see Upgrading Device Firmware in the KVM and Serial Access Clients Guide. Note: Firmware upgrades are not supported via modem.
Chapter 10: Maintenance Rebooting the KX II The Reboot page provides a safe and controlled way to reboot your KX II. This is the recommended method for rebooting. Important: All KVM and serial connections will be closed and all users will be logged off. To reboot your KX II: 1. Choose Maintenance > Reboot. The Reboot page opens. 2. Click Reboot. You are prompted to confirm the action. Click Yes to proceed with the reboot.
Chapter 10: Maintenance Stopping CC-SG Management While the KX II is under CC-SG management, if you try to access the device directly, you are notified that it the device is under CC-SG management. If you are managing the KX II through CC-SG and connectivity between CC-SG and the KX II is lost after the specified timeout interval (typically 10 minutes), you are able to end the CC-SG management session from the KX II console.
Chapter 10: Maintenance 3. Click Yes to remove the device CC-SG management. Once CC-SG management has ended, a confirmation will be displayed.
Chapter 11 Diagnostics In This Chapter Network Interface Page .........................................................................251 Network Statistics Page.........................................................................251 Ping Host Page ......................................................................................253 Trace Route to Host Page .....................................................................254 Device Diagnostics ..................................................
Chapter 11: Diagnostics 252 Statistics - Produces a page similar to the one displayed here. Interfaces - Produces a page similar to the one displayed here.
Chapter 11: Diagnostics Route - Produces a page similar to the one displayed here. 3. Click Refresh. The relevant information is displayed in the Result field. Ping Host Page Ping is a network tool used to test whether a particular host or IP address is reachable across an IP network. Using the Ping Host page, you can determine if a target server or another KX II is accessible. To ping the host: 1. Choose Diagnostics > Ping Host. The Ping Host page appears.
Chapter 11: Diagnostics 2. Type either the hostname or IP address into the IP Address/Host Name field. Note: The host name cannot exceed 232 characters in length. 3. Click Ping. The results of the ping are displayed in the Result field. Trace Route to Host Page Trace route is a network tool used to determine the route taken to the provided hostname or IP address. To trace the route to the host: 1. Choose Diagnostics > Trace Route to Host. The Trace Route to Host page opens. 2.
Chapter 11: Diagnostics Device Diagnostics Note: This page is for use by Raritan Field Engineers or when you are directed by Raritan Technical Support. Device diagnostics downloads the diagnostics information from the KX II to the client machine. Two operations can be performed on this page: Execute a special diagnostics script provided by Raritan Technical Support during a critical error debugging session. The script is uploaded to the device and executed.
Chapter 11: Diagnostics a. Click Save to File. The File Download dialog opens. b. Click Save. The Save As dialog box opens. c. Navigate to the desired directory and click Save. d. Email this file as directed by Raritan Technical Support.
Chapter 12 Command Line Interface (CLI) In This Chapter Overview ................................................................................................257 Accessing the KX II Using CLI ..............................................................258 SSH Connection to the KX II .................................................................258 Logging In ..............................................................................................259 Navigation of the CLI ......................
Chapter 12: Command Line Interface (CLI) Accessing the KX II Using CLI Access the KX II by using one of the following methods: SSH (Secure Shell) via IP connection A number of SSH clients are available and can be obtained from the following locations: Putty - http://www.chiark.greenend.org.uk/~sgtatham/putty/ http://www.chiark.greenend.org.uk/~sgtatham/putty/ SSH Client from ssh.com - www.ssh.com http://www.ssh.com Applet SSH Client - www.netspace.org/ssh http://www.netspace.
Chapter 12: Command Line Interface (CLI) Logging In To log in, enter the user name admin as shown: 1. Log in as admin 2. The Password prompt appears. Enter the default password: raritan The welcome message displays. You are now logged on as an administrator. After reviewing the following Navigation of the CLI (on page 259) section, perform the Initial Configuration tasks. Navigation of the CLI Before using the CLI, it is important to understand CLI navigation and syntax.
Chapter 12: Command Line Interface (CLI) CLI Syntax -Tips and Shortcuts Tips Commands are listed in alphabetical order. Commands are not case sensitive. Parameter names are single word without underscore. Commands without arguments default to show current settings for the command. Typing a question mark ( ? ) after a command produces help for that command. A pipe symbol ( | ) indicates a choice within an optional or required set of keywords or arguments.
Chapter 12: Command Line Interface (CLI) Initial Configuration Using CLI Note: These steps, which use the CLI, are optional since the same configuration can be done via KVM. See Getting Started (on page 12) for more information. KX II devices come from the factory with default factory settings. When you first power up and connect to the device, you must set the following basic parameters so the device can be accessed securely from the network: 1. Reset the administrator password.
Chapter 12: Command Line Interface (CLI) The KX II now has the basic configuration and can be accessed remotely via SSH, GUI, or locally using the local serial port. The administrator needs to configure the users and groups, services, security, and serial ports to which the serial targets are attached to the KX II. CLI Prompts The Command Line Interface prompt indicates the current command level. The root portion of the prompt is the login name.
Chapter 12: Command Line Interface (CLI) Enter admin > config > network. Command Description help Display overview of commands. history Display the current session's command line history. interface Set/get network parameters. ipv6_interface Set/get IPv6 network parameters. logout Logout of the current CLI session. name Device name configuration. quit Return to previous menu. stop Return to the root menu.
Chapter 12: Command Line Interface (CLI) Commands Description ipv6 Set/get IPv6 network parameters. Interface Command The Interface command is used to configure the KX II network interface.
Chapter 12: Command Line Interface (CLI) Name Command The name command is used to configure the network name.
Chapter 13 KX II Local Console In This Chapter Overview ................................................................................................266 Simultaneous Users ..............................................................................266 KX II Local Console Interface: KX II Devices ........................................267 Security and Authentication ...................................................................267 Available Resolutions ............................................
Chapter 13: KX II Local Console KX II Local Console Interface: KX II Devices When you are located at the server rack, the KX II provides standard KVM management and administration via the KX II Local Console. The KX II Local Console provides a direct KVM (analog) connection to your connected servers; the performance is exactly as if you were directly connected to the server's keyboard, mouse, and video ports.
Chapter 13: KX II Local Console Port Access Page (Local Console Server Display) After you login to the KX II Local Console, the Port Access page opens. This page lists all of the KX II ports, and the target servers, port groups, and blade chassis that are connected to those ports. The Port Access page contains the same information whether accessed from the remote console or local console. Additionally, you navigate the page and access targets and port groups in the same way.
Chapter 13: KX II Local Console Scanning Ports - Local Console The KX II scanning feature is supported by the Local Console. The targets that are found during the scan are displayed on the Scan page one at a time, which is different from the Remote Console port slide show. Each target is displayed on the page for 10 seconds by default, allowing you to view the target and connect to it.
Chapter 13: KX II Local Console Local Port Scan Mode Following are options available to you to change scan options on local port. To configure the Local Console scan port settings: 1. On the Local Console, select Device Settings. 2. In the Local Port Settings section, select Local Port Scan Mode. 3. Change the display interval as needed: Display Interval - changes the scan display interval. Interval Between Ports - change interval between switching different port during scan.
Chapter 13: KX II Local Console 4. Click OK. Once the smart card reader is added, a message will appear on the page indicating you have completed the operation successfully. A status of either Selected or Not Selected will appear in the left panel of the page under Card Reader. To update the Card Readers Detected list: Click Refresh if a new smart card has been mounted. The Card Readers Detected list will be refreshed to reflect the newly added smart card reader.
Chapter 13: KX II Local Console Local Console USB Profile Options From the USB Profile Options section of the Tools page, you can choose from the available USB profiles. The ports that can be assigned profiles are displayed in the Port Name field and the profiles that are available for a port appear in the Select Profile To Use field after the port is selected. The profiles selected for use with a port appear in the Profile In Use field. To apply a USB profile to a local console port: 1.
Chapter 13: KX II Local Console Hot Keys and Connect Keys Because the KX II Local Console interface is completely replaced by the interface for the target server you are accessing, a hot key is used to disconnect from a target and return to the local port GUI. A connect key is used to connect to a target or switch between targets. The Local Port hot key allows you to rapidly access the KX II Local Console user interface when a target server is currently being viewed.
Chapter 13: KX II Local Console Standard servers Connect key action Key sequence example Disconnect from a target and return to the local port GUI Disconnect from target port 5, slot 11 and return to the local port GUI (the page from which you connected to target): Double Click Scroll Lock Special Sun Key Combinations The following key combinations for Sun™ Microsystems server’s special keys operate on the local port.
Chapter 13: KX II Local Console Returning to the KX II Local Console Interface Important: The KX II Local Console default hot key is to press the Scroll Lock key twice rapidly. This key combination can be changed in the Local Port Settings page. See Configuring KX II Local Port Settings from the Local Console (on page 279) in online help. To return to the KX II Local Console from the target server: Press the hot key twice rapidly (the default hot key is Scroll Lock).
Chapter 13: KX II Local Console US US/International United Kingdom French (France) German (Germany) JIS (Japanese Industry Standard) Simplified Chinese Traditional Chinese Dubeolsik Hangul (Korean) German (Switzerland) Portuguese (Portugal) Norwegian (Norway) Swedish (Sweden) Danish (Denmark) Belgian (Belgium) Hungarian Spanish Italian Slovenian Note: Keyboard use for Chinese, Japanese, and Korean is for display only.
Chapter 13: KX II Local Console Hot key: Take this action: Double Click Left Ctrl key Press the left Ctrl key twice quickly 4. Select the Local Port Connect key. Use a connect key sequence to connect to a target and switch to another target. You can then use the hot key to disconnect from the target and return to the local port GUI. Once the local port connect key is created, it will appear in the Navigation panel of the GUI so you can use it as a reference.
Chapter 13: KX II Local Console Note: If you initially choose not to ignore CC Manage mode on the local port but later want local port access, you will have to remove the device from under CC-SG management (from within CC-SG). You will then be able to check this checkbox. 11. Click OK.
Chapter 13: KX II Local Console Configuring KX II Local Port Settings from the Local Console The standard local port and the extended local port can be configured from the Remote Console on the Port Configuration page, or from the Local Console on the Local Port Settings page. See Configuring KX II Local Port Settings (on page 206) for details on configuring these ports. KX II Local Console Factory Reset Note: This feature is available only on the KX II Local Console.
Chapter 13: KX II Local Console IP auto configuration IP address Subnet mask Gateway IP address Primary DNS server IP address Secondary DNS server IP address Discovery port Bandwidth limit LAN interface speed & duplex Enable automatic failover Ping interval (seconds) Timeout (seconds) 3. Click Reset to continue. You will be prompted to confirm the factory reset because all network settings will be permanently lost. 4. Click OK proceed.
Chapter 13: KX II Local Console Connect and Disconnect Scripts The KX II provides the ability to execute key macro scripts when connecting to or disconnecting from a target. You can create and edit your own scripts on the Connection Script page to perform additional actions when connecting to or disconnecting from targets. Alternatively, you can import existing connection scripts in XML file format. Scripts that you create in KX II can also be exported in XML file format.
Chapter 13: KX II Local Console 3. In the Apply Selected Scripts to Ports section, select the target(s) you want to apply the script to using Select All or clicking on the checkbox to the left of each target to apply the script to only select targets. 4. Click Apply Scripts. Once the script is added to the target, it appears under the Scripts Currently in Use column in the Apply Selected Scripts to Ports section. To remove a script from targets: 1.
Chapter 13: KX II Local Console For example, select F1-F16 to display the function key set in the Add box. Select a function key and add it to the Script box. Next, select Letters from the Key Set drop-down and add a letter key to the script. 8. Optionally, add text that will display when the script is executed. a. Click Construct Script from Text to open the Construct Script From Text page. b. Enter the script in the text box. For example, enter "Connected to Target". c.
Chapter 13: KX II Local Console 284
Chapter 13: KX II Local Console Modifying Scripts To modify existing scripts: 1. Click Device Settings > Connection Scripts. The Connection Scripts page opens. 2. In the Available Connection Scripts section, select the script you want to modify and click Modify. The page is then in Edit mode. 3. Make changes as needed. Click OK when finished. Resetting the KX II Using the Reset Button On the back panel of the device, there is a Reset button.
Chapter 13: KX II Local Console 4. Continue holding the Reset button for 10 seconds. Once the device has been reset, two short beeps signal its completion.
Appendix A Specifications In This Chapter Hardware ...............................................................................................287 Software.................................................................................................
Appendix A: Specifications Dominion KX II model Description Dimensions (WxDxH) 1.75"; Weight Power and heat dissipation 47/63Hz 1A 63W 54 KCAL remote users, 1 local port for use at 439 x 290 x the rack 44mm 4.1kg DKX2-232 32 server ports, 2 17.3" x 11.4" x remote users, 1 1.75"; local port for use at 439 x 290 x the rack 44mm 9.0lbs; 4.1kg Dual Power 100V/240V 47/63Hz 0.6A 63W 54 KCAL DKX2-216 16 server ports, 2 17.3" x 11.4" x remote users, 1 1.
Appendix A: Specifications Specifications for All Dominion KX II Models Local port access Video HD15(F) VGA Keyboard/Mouse USB(F), 1 USB front, 3 USB rear Warranty Two years standard with advanced replacement* Supported Target Server Video Resolution/Refresh Rate/Connection Distance The maximum supported distance is a function of many factors including the type/quality of the Cat5 cable, server type and manufacturer, video driver and monitor, environmental conditions, and user expectations.
Appendix A: Specifications 290 CIM model Description Dimensions (WxDxH) Weight D2CIM-VUSB USB CIM for virtual media and Absolute Mouse Synchronization 1.3" x 3.0" x 0.6"; 33 x 76 x 15mm 0.20lb; 0.09kg DCIM-PS2 CIM for PS/2 1.3" x 3.0" x 0.6"; 33 x 76 x 15mm 0.20lb; 0.09kg DCIM-SUN CIM for Sun 1.3" x 3.0" x 0.6"; 33 x 76 x 15mm 0.20lb; 0.09kg DCIM-USBG2 CIM for USB and Sun USB 1.3" x 3.0" x 0.6"; 33 x 76 x 15mm 0.20lb; 0.09kg D2CIM-PWR CIM for remote power management 1.3" x 3.0" x 0.
Appendix A: Specifications CIM model Description Dimensions (WxDxH) Weight P2CIM-SER Paragon II/Dominion KX II CIM for serial (ASCII) devices 1.3" x 3.0" x 0.6"; 33 x 76 x 15mm 0.20lb; 0.09kg D2CIM-DVUSBDVI Digital CIM that provides digital-to-analog conversion and support for virtual media, smartcard/CAC, audio, Absolute and Relative Mouse Synchronization 1.7" x 3.5" x 0.8"; 43 x 90 x 19mm 0.25lb; 0.
Appendix A: Specifications CIM model Description Dimensions (WxDxH) Weight D2CIM-DVUSBDP Digital CIM that provides digital-to-analog conversion and support for virtual media, smartcard/CAC, audio, Absolute and Relative Mouse Synchronization 1.7" x 3.5" x 0.8"; 43 x 90 x 19mm 0.25lb; 0.11kg D2CIM-DVUSBHDMI Digital CIM that provides digital-to-analog conversion and support for virtual media, smartcard/CAC, audio, Absolute and Relative Mouse Synchronization 1.7" x 3.5" x 0.8"; 43 x 90 x 19mm 0.
Appendix A: Specifications Digital CIM Timing Modes Following are the default timing modes that are used when the KX II communicates with a video source via a digital CIM. The timing mode that is used is dependent on the native resolution of the video source. 1920x1080@60Hz 1600x1200@60Hz 1280x1024@60Hz (default resolution applied to digital CIMs) 1440x900@60Hz 1024x768@60Hz See Configuring CIM Ports (on page 176) information.
Appendix A: Specifications Digital CIM Established and Standard Modes The following additional established and standard resolutions and timing modes are supported by the KX II 2.5.0 (and later).
Appendix A: Specifications Digital CIM Display Native Resolution You are able to select the native resolution of the CIM on the Port Configuration page from the Display Native Resolution drop-down. This is the preferred resolution and timing mode of the digital CIM. Once a resolution is selected, it is applied to the CIM. If no selection is made, the default 1024x1280@60Hz resolution is used.
Appendix A: Specifications Supported Paragon II CIMS and Configurations The KX II supports the P2CIM-APS2DUAL and P2CIM-AUSBDUAL CIMs, which provide two RJ45 connections to different KVM switches. Support of these CIMs provides a second path to access the target in the event that one of the KVM switches is blocked or fails.
Appendix A: Specifications KX II-to-KX II Paragon CIM Guidelines The following system configuration guidelines should be followed when you are using Paragon CIMs in a KX II-to-KX II configuration: Concurrent Access Both KX II KVM switches should be configured with the same policy for concurrent access to targets - both PC-Share or both Private.
Appendix A: Specifications If a connection to the target is in place from the other KX II, the availability is checked when a connection is attempted. Access is denied or allowed consistent with the PC-Share policy in place for the KX II. Until that time, the availability is not be updated on the other KX II. If access is denied because the target is busy, a notification is displayed.
Appendix A: Specifications Paragon II operation mode Public View Mode description Supported? port can be selected and controlled by more than one user, but only one user has keyboard and mouse control at any one time. Timeout, which is configured on the Paragon II, is not supported. Both users will have concurrent keyboard and mouse control.
Appendix A: Specifications Supported Remote Connections Remote connection Details Network 10BASE-T, 100BASE-T, and 1000BASE-T (Gigabit) Ethernet Protocols TCP/IP, UDP, SNTP, HTTP, HTTPS, RADIUS, LDAP/LDAPS Network Speed Settings KX II network speed setting Network switch port setting Auto 1000/Full 100/Full 100/Half Auto 1000/Full 100/Full 100/Half 10/Full 10/Half Highest Available Speed 1000/Full KX II: 100/Full 100/Half KX II: 10/Full 10/Half 1000/Full 1000/Full No No No No Commun
Appendix A: Specifications Legend: Does not function as expected Supported Functions; not recommended NOT supported by Ethernet specification; product will communicate, but collisions will occur Per Ethernet specification, these should be “no communication,” however, note that the KX II behavior deviates from expected behavior Note: For reliable network communication, configure the KX II and the LAN switch to the same LAN Interface Speed and Duplex.
Appendix A: Specifications Target Server Requirements When using smart card readers, the basic requirements for interoperability at the target server are: The IFD (smart card reader) Handler must be a standard USB CCID device driver (comparable to the generic Microsoft® USB CCID driver). A digital CIM or D2CIM-DVUSB (Dual-VM CIM) is required and must be using firmware version 3A6E or later. Blade chassis server connections, where a CIM per blade is used, are supported.
Appendix A: Specifications Remote Client Requirements The basic requirements for interoperability at the remote client are: The IFD (smart card reader) Handler must be a PC/SC compliant device driver. The ICC (smart card) Resource Manager must be available and be PC/SC compliant. The JRE® Java™ 1.7 with smart card API must be available for use by the Raritan client application.
Appendix A: Specifications Type Vendor Model Verified USB SCM Microsystems SCR331 Verified on local and remote USB ActivIdentity® ActivIdentity USB Reader v2.0 Verified on local and remote USB ActivIdentity ActivIdentity USB Reader v3.
Appendix A: Specifications Supported Audio Device Formats The KX II supports one playback and capture device and one record device on a target at a time. The following audio device formats are supported: Stereo, 16 bit, 44.1K Mono, 16 bit, 44.1K Stereo, 16 bit, 22.05K Mono, 16 bit, 22.05K Stereo, 16 bit, 11.025K Mono, 16 bit, 11.025K Audio Playback and Capture Recommendations and Requirements Audio Level Set the target audio level to a mid-range setting.
Appendix A: Specifications Bandwidth Requirements The table below details the audio playback and capture bandwidth requirements to transport audio under each of the selected formats. Audio format Network bandwidth requirement 44.1 KHz, 16bit stereo 176 KB/s 44.1 KHz, 16bit mono 88.2 KB/s 2.05 KHz, 16bit stereo 88.2 KB/s 22.05 KHz, 16bit mono 44.1 KB/s 11.025 KHz, 16bit stereo 44.1 KB/s 11.025 KHz, 16bit mono Audio 22.
Appendix A: Specifications Audio in a Mac Environment Following are known issues in a Mac® environment. On Mac clients, only one playback device is listed on the Connect Audio panel when accessing the device through the Virtual KVM Client (VKC) and Multi-Platform Client (MPC). The device listed is the default and is displayed on the Connect Audio panel as Java Sound Audio Engine. Using audio on a Mac target through Skype® may cause the audio to be corrupted.
Appendix A: Specifications KX2 8xx Extended Local Port Recommended Maximum Distances 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 Mac Mini BIOS Keystroke Commands The following BIOS commands have been tested on Intel-based Mac® Mini target servers and Mac Lion® servers running Mac Snow Leopard®. The servers were attached to a KX II with D2CIM-DVUSB and D2CIM-VUSB CIMs.
Appendix A: Specifications Keystroke Description Virtual Media CIM Dual Virtual Media CIM Mac Lion Server HDMI CIM Press N during startup Start up from a compatible network server (NetBoot) Press T during startup Start up in Target Disk mode Press Shift during startup Start up in Safe Boot mode and temporarily disable login items Press Command-V during startup Start up in Verbose mode.
Appendix A: Specifications Port Description By default, this port is used for multiple purposes, including the web server for the HTML client, the download of client software (Multi-Platform Client (MPC) and Virtual KVM Client (VKC)) onto the client's host, and the transfer of KVM and virtual media data streams to the client.
Appendix A: Specifications Software Supported Operating Systems (Clients) The following operating systems are supported on the Virtual KVM Client (VKC) and Multi-Platform Client (MPC). Windows 7® Windows XP® Windows 2008® Windows Vista® Windows 2000® SP4 Server Windows 2003® Server Windows 2008® Server Red Hat® Desktop 5.0 Red Hat Desktop 4.0 Open SUSE 10, 11 Fedora® 13 and 14 Mac® OS X Mac® OS X Mountain Lion® 10.7.5 using Safari 6.0.5 running JRE™ 1.7.
Appendix A: Specifications Linux® The JRE™ plug-in is available for the Windows® 32-bit and 64-bit operating systems. MPC and VKC can be launched only from a 32-bit browser, or 64-bit browser. Following are the Java™ 32-bit and 64-bit Windows operating system requirements.
Appendix A: Specifications Mac OS X Mountain Lion 10.8.5 * using Safari 6.1.1 running JRE 1.7.0_51 *Note: Upon upgrading from OS X 10.8.2 to OS X 10.8.3, Safari® may block Java™. JRE Requirements and Browser Considerations for Mac Java Runtime Environment Requirements for Mac Install Java Runtime Environment 7 (JRE)® on PCs and Macs® when using the Virtual KVM Client (VKC) to access target servers via KX II.
Appendix A: Specifications Resolutions 640x480 @72Hz 1152x864 @85Hz 640x480 @75Hz 1152x870 @75.1Hz 640x480 @85Hz 1152x900 @66Hz 720x400 @70Hz 1152x900 @76Hz 720x400 @84Hz 1280x720@60Hz 720x400 @85Hz 1280x960 @60Hz 800x600 @56Hz 1280x960 @85Hz 800x600 @60Hz 1280x1024 @60Hz 800x600 @70Hz 1280x1024 @75Hz 800x600 @72Hz 1280x1024 @85Hz 800x600 @75Hz 1360x768@60Hz 800x600 @85Hz 1366x768@60Hz 800x600 @90Hz 1368x768@60Hz 800x600 @100Hz 1400x1050@60Hz 832x624 @75.
Appendix A: Specifications Video Image Appears Dark when Using a Mac If you are using a Mac® with an HDMI video port and the video seems too dark, enable DVI Compatibility Mode on the CIM to help resolve the issue. See Configuring CIM Ports (on page 176) KX II Supported Keyboard Languages The KX II provides keyboard support for the languages listed in the following table.
Appendix A: Specifications Language Regions Keyboard layout Danish Denmark Danish Swedish Sweden Swedish Hungarian Hungary Hungarian Slovenian Slovenia Slovenian Italian Italy Italian Spanish Spain and most Spanish speaking countries Spanish Portuguese Portugal Portuguese Events Captured in the Audit Log and Syslog Following is a list and description of the events that are captured by the KX II audit log and syslog: 316 Access Login - A user has logged in to the KX II Acces
Appendix B Dual Video Port Groups In This Chapter Overview ................................................................................................317 Recommendations for Dual Port Video .................................................318 Dual Video Port Group Supported Mouse Modes .................................318 CIMs Required for Dual Video Support .................................................319 Dual Port Video Group Usability Notes .................................................
Appendix B: Dual Video Port Groups Recommendations for Dual Port Video Set the target server’s primary and secondary displays to the same video resolution in order to maintain mouse synchronization and minimize having to periodically resync. Depending on the desired orientation, the top display (vertical orientation) or left display (horizontal orientation) should be the designated primary display. This display will provide active menu selection for virtual media, audio, smart card and mouse operations.
Appendix B: Dual Video Port Groups Target operating systems Supported mouse modes Comments Mouse mode is recommended. Linux® Intelligent and Standard Mouse Modes Linux® users may experience display and mouse movement issues using single mouse mode. Raritan recommends Linux users do not use Single Mouse mode. Mac® operating system Single Mouse Mode For Mac targets with multiple monitors, use a standard mouse in Single-Cursor mode.
Appendix B: Dual Video Port Groups Monitor settings will NOT be applied. Instead the Port Group Management configured 'Display Orientation' will be applied.
Appendix B: Dual Video Port Groups Example Dual Port Video Group Configuration The following is a general example. Your configuration may vary in the type of CIMs used, the port you designate as the primary port, the ports you are connecting to and so on.
Appendix B: Dual Video Port Groups Diagram key Connection from the target's primary (first) video port to the KX II Connection from the target's secondary (second) video port to the KX II IP connection between the KX II and remote client Target server - configure the display settings and launch the dual port video group Display settings are the same on the remote client and target server (recommended) Horizontal - Primary (Left) - defined on the Port Group Management page in KX II Secondary (Right) - defin
Appendix B: Dual Video Port Groups Note: If the target primary and secondary displays are set to different resolutions the mouse will not stay in sync and will need to be periodically re-synced from the top-left target window. Step 2: Connect the Target Server to the KX III Dual port video groups can be created from existing port connections, or new port connections. The steps provided here assume you are creating new connections.
Appendix B: Dual Video Port Groups Step 3: Configure the Mouse Mode and Ports Once you have connected the target server to the Raritan device through the target server video ports, it detects the connection and displays the ports on the Port Configuration page. For instructions, see Configuring Standard Target Servers (on page 173) After the ports are configured, they can be grouped in a dual video port group.
Appendix B: Dual Video Port Groups Step 5: Launch a Dual Port Video Group Once you have created the dual video port group, it is available on the Port Access page. Two KVM channels are required to remotely connect to the dual video port group by clicking primary port. If two channels are not available, the Connect link is not displayed. Session timeouts that are configured on the KX II are applied to both ports of a dual video group.
Appendix B: Dual Video Port Groups Direct Port Access and Dual Port Video Groups Direct port access allows users to bypass having to use the device's Login dialog and Port Access page. This feature also provides the ability to enter a username and password directly to proceed to the target, if the username and password is not contained in the URL. If you are accessing a target that is part of a dual port video group, direct port access uses the primary port to launch both the primary and secondary ports.
Appendix C Accessing a PX2 from the KX II In This Chapter Overview ................................................................................................327 Connecting the Paragon II to the KX II ..................................................328 Overview Connect the Paragon II system to a KX II device that is managed by CC-SG so that Paragon II is accessible from CC-SG. This diagram indicates the configuration integrating KX II.
Appendix C: Accessing a PX2 from the KX II When you access the Paragon II system from KX II or CC-SG (if the KX II is managed by CC-SG), the Paragon II OSUI login screen appears for you to log in. In this integration, you can perform any OSUI functions implemented with current Paragon II firmware or any KX II function implemented with current KX II firmware except for the virtual media feature. When accessing the Paragon II OSUI through KX II, DO NOT attempt to synchronize the mouse manually.
Appendix C: Accessing a PX2 from the KX II 329
Appendix D Updating the LDAP Schema Note: The procedures in this chapter should be attempted only by experienced users. In This Chapter Returning User Group Information ........................................................330 Setting the Registry to Permit Write Operations to the Schema ...........331 Creating a New Attribute .......................................................................331 Adding Attributes to the Class ...............................................................
Appendix D: Updating the LDAP Schema Setting the Registry to Permit Write Operations to the Schema To allow a domain controller to write to the schema, you must set a registry entry that permits schema updates. To permit write operations to the schema: 1. Right-click the Active Directory® Schema root node in the left pane of the window and then click Operations Master. The Change Schema Master dialog appears. 2. Select the "Schema can be modified on this Domain Controller" checkbox. Optional 3. Click OK.
Appendix D: Updating the LDAP Schema 3. Click New and then choose Attribute. When the warning message appears, click Continue and the Create New Attribute dialog appears. 4. Type rciusergroup in the Common Name field. 5. Type rciusergroup in the LDAP Display Name field. 6. Type 1.3.6.1.4.1.13742.50 in the Unique x5000 Object ID field. 7. Type a meaningful description in the Description field. 8. Click the Syntax drop-down arrow and choose Case Insensitive String from the list. 9.
Appendix D: Updating the LDAP Schema 2. Scroll to the user class in the right pane and right-click it. 3. Choose Properties from the menu. The user Properties dialog appears. 4. Click the Attributes tab to open it. 5. Click Add.
Appendix D: Updating the LDAP Schema 6. Choose rciusergroup from the Select Schema Object list. 7. Click OK in the Select Schema Object dialog. 8. Click OK in the User Properties dialog. Updating the Schema Cache To update the schema cache: 1. Right-click Active Directory® Schema in the left pane of the window and select Reload the Schema. 2. Minimize the Active Directory Schema MMC (Microsoft® Management Console) console.
Appendix D: Updating the LDAP Schema 3. Go to the directory where the support tools were installed. Run adsiedit.msc. The ADSI Edit window opens. 4. Open the Domain. 5. In the left pane of the window, select the CN=Users folder.
Appendix D: Updating the LDAP Schema 6. Locate the user name whose properties you want to adjust in the right pane. Right-click the user name and select Properties. 7. Click the Attribute Editor tab if it is not already open. Choose rciusergroup from the Attributes list. 8. Click Edit. The String Attribute Editor dialog appears. 9. Type the user group (created in the KX II) in the Edit Attribute field. Click OK.
Appendix E Informational Notes In This Chapter Overview ................................................................................................337 Java Runtime Environment (JRE) Notes ...............................................337 IPv6 Support Notes ...............................................................................339 Dual Stack Login Performance Issues ..................................................340 CIM Notes .................................................................
Appendix E: Informational Notes Java Not Loading Properly on Mac If you are using a Mac® and see the following message when connecting to a device from the KX II Port Access Table, Java™ is not loaded properly: "Error while getting the list of open targets, please try again in a few seconds". If this occurs, check your Java installation from this website: http://www.java.com/en/download/testjava.jsp http://www.java.com/en/download/testjava.
Appendix E: Informational Notes IPv6 Support Notes Operating System IPv6 Support Notes Java Java™ 1.7 supports IPv6 for the following: Solaris™ 10 (and later) Linux® kernel 2.1.2 (and later)/RedHat 6.1 (and later) Solaris 10 (and later) Windows XP® SP1 and Windows 2003®, Windows Vista® and Windows 7 operating systems The following IPv6 configurations are not supported by Java: J2SE does not support IPv6 on Microsoft® Windows®. Linux It is recommended that Linux kernel 2.4.
Appendix E: Informational Notes Dual Stack Login Performance Issues If you are using the KX II in a dual stack configuration, it is important you configured the domain system (DNS) correctly in the KX II in order to avoid delays when logging in. See Tips for Adding a Web Browser Interface (on page 195) for information on configuring your DNS in KX II.
Appendix E: Informational Notes Windows 2000 Composite USB Device Behavior for Virtual Media The Windows 2000® operating system does not support USB composite devices, like Raritan’s D2CIM-VUSB, in the same manner as non-composite USB devices. As a result, the “Safely Remove Hardware” system tray icon does not appear for drives mapped by the D2CIM-VUSB and a warning message may appear when disconnecting the device. Raritan has not observed any problems or issues from this message, however.
Appendix E: Informational Notes Cannot Write To/From a File from a Mac Client If you are connecting to the KX II from a Mac® 10.8.5 client running Safari® 6.1 with Java™ 1.7 and cannot write to/from a file on a target server or access virtual media, do the following to correct this: 1. In Safari, select Preferences. 2. Under the Security tab, select Manage Website Settings. 3. Click on "Website for KX2". 4. Select "Run in safe mode" from the drop-down. 5. Restart Safari.
Appendix E: Informational Notes Virtual Media via VKC and AKC in a Windows Environment Windows XP® operating system administrator and standard user privileges vary from those of the Windows Vista® operating system and the Windows 7® operating system. When enabled in Vista or Windows 7, User Access Control (UAC) provides the lowest level of rights and privileges a user needs for an application.
Appendix E: Informational Notes Virtual Media Linux Drive Listed Twice For KX II 2.4.0 (and later) and LX 2.4.5 (and later), users who are logged in to Linux™ clients as root users, the drives are listed twice in the Local Drive drop-down. For example, you will see eg /dev/sdc and eg /dev/sdc1 where the first drive is the boot sector and the second drive is the first partition on the disk.
Appendix E: Informational Notes USB Port and Profile Notes VM-CIMs and DL360 USB Ports HP® DL360 servers have one USB port on the back of the device and another on the front of the device. With the DL360, both ports cannot be used at the same time. Therefore, a dual VM-CIM cannot be used on DL360 servers. However, as a workaround, a USB2 hub can be attached to the USB port on the back of the device and a dual VM-CIM can be attached to the hub.
Appendix E: Informational Notes USB profile help appears in the USB Profile Help window. For detailed information about specific USB profiles, see Available USB Profiles (on page 109). Raritan provides a standard selection of USB configuration profiles for a wide range of operating system and BIOS level server implementations. These are intended to provide an optimal match between remote USB device and target server configurations.
Appendix E: Informational Notes Changing a USB Profile when Using a Smart Card Reader There may be certain circumstances under which you will need to change the USB profile for a target server. For example, you may need to change the connection speed to "Use Full Speed for Virtual Media CIM" when the target has problems with the "High Speed USB" connection speed.
Appendix E: Informational Notes Note: These procedures do not apply to the circumflex accent (above vowels). In all cases, the ^ key (to the right of the P key) works on French keyboards to create the circumflex accent when used in combination with another character.
Appendix E: Informational Notes Keyboard Language Preference (Fedora Linux Clients) Because the Sun™ JRE™ on Linux® has problems generating the correct KeyEvents for foreign-language keyboards configured using System Preferences, Raritan recommends that you configure foreign keyboards using the methods described in the following table.
Appendix E: Informational Notes 4. Click Close. To set the keyboard language using the Keyboard Indicator: 1. Right-click the Task Bar and choose Add to Panel. 2. In the Add to Panel dialog, right-click the Keyboard Indicator and from the menu choose Open Keyboard Preferences. 3. In the Keyboard Preferences dialog, click the Layouts tab. 4. Add and remove languages as necessary.
Appendix E: Informational Notes 3. Restart the X server. With this change, the internal video mode timing from the X server is used and corresponds exactly with the VESA video mode timing, resulting in the proper video display on the KX II. List of Supported Target Video Resolutions Not Displaying When using a CIM, there are some video resolutions, as listed in KX III Supported Target Server Video Resolutions, that may not be available by default for selection.
Appendix E: Informational Notes Audio in a Linux Environment The following are known issues when using the audio feature in a Linux ® environment. Linux® users, use the default audio device for playback. Sound may not come through if a non-default sound card is selected. SuSE 11 clients require Javas_1_6_0-sun-alsa (ALSA support for java-1_6_0-sun) to be installed via YAST. For Logitech® headsets with a built in a mic, only the Mono Capture option is available.
Appendix E: Informational Notes Proxy Mode and MPC If you are using KX II in a CC-SG configuration, do not use the CC-SG proxy mode if you are planning to use the Multi-Platform Client (MPC). Moving Between Ports on a Device If you move a between ports on the same Raritan device and resume management within one minute, CC-SG may display an error message. If you resume management, the display will be updated.
Appendix E: Informational Notes VKC and MPC Smart Card Connections to Fedora Servers If you are using a smart card to connect to a Linux® Fedora® server via Multi-Platform Client (MPC) and Virtual KVM Client (VKC) upgrade the pcsc-lite library to 1.4.102-3 or above. Note: This feature is available on the KSX II 2.3.0 (and later) and KX II 2.1.10 (and later).
Appendix F Frequently Asked Questions In This Chapter General FAQs ........................................................................................355 Remote Access .....................................................................................356 Universal Virtual Media ..........................................................................359 Bandwidth and KVM-over-IP Performance ...........................................361 Ethernet and IP Networking....................................
Appendix F: Frequently Asked Questions Question Answer How does Dominion KX II differ from remote control software? When using Dominion KX II remotely, the interface, at first glance, may seem similar to remote control software such as pcAnywhereTM, Windows® Terminal Services/Remote Desktop, VNC, etc.
Appendix F: Frequently Asked Questions Question Answer How many users can remotely Dominion KX II models offer remote connections for access servers on each up to eight users per user channel to simultaneously Dominion KX II? access and control a unique target server. For one-channel devices like the DKX2-116, up to eight remote users can access and control a single target server.
Appendix F: Frequently Asked Questions Question Answer Do you have a non-Windows KVM Client? Yes. Both the Virtual KVM Client (VKC) and the Multiplatform Client (MPC) allow non-Windows users to connect to target servers in the data center. MPC can be run via Web browsers and stand-alone and can access servers connected to both Dominion KX I and KX II switches. Please refer to Raritan’s Dominion KX II and KVM Client User Guides for more information. Do your KVM Clients have multi-language support? Yes.
Appendix F: Frequently Asked Questions Question Answer What is the file size of the applet that’s used to access Dominion KX II? How long does it take to retrieve? The Virtual KVM Client (VKC) applet used to access Dominion KX II is approximately 500KB in size. The following chart describes the time required to retrieve Dominion KX II’s applet at different network speeds: 100Mbps Theoretical 100Mbit network speed .05 seconds 60Mbps Likely practical 100Mbit network speed .
Appendix F: Frequently Asked Questions Question Answer What is required for virtual media? A Dominion KX II virtual media CIM is required: a digital CIM, D2CIM-VUSB or D2CIM-DVUSB. The D2CIM-VUSB has a single USB connector and is for customers who will use virtual media at the OS level. The D2CIM-DVUSB has dual USB connectors and should be purchased by customers who wish to utilize virtual media at the BIOS level.
Appendix F: Frequently Asked Questions Question Answer Why would I use a USB profile? USB profiles are most often required at the BIOS level where there may not be full support for the USB specification when accessing virtual media drives. However, profiles are sometimes used at the OS level, for example, for mouse synchronization for Macintosh and Linux servers.
Appendix F: Frequently Asked Questions Question Answer How is bandwidth used in KVM-over-IP systems? Dominion KX II offers next-generation KVM-over-IP technology – the very best video compression available. Raritan has received numerous technical awards, confirming its high video quality transmissions and the low bandwidth utilization.
Appendix F: Frequently Asked Questions Question Answer What factors affect bandwidth? There are many factors that determine how much bandwidth will be used. The primary factor, noted above, is the amount of change in the target server’s video display. This is dependent on the user’s task and actions. Other factors include the server’s video resolution, networking speed and characteristics, client PC resources and video card noise.
Appendix F: Frequently Asked Questions Question Answer How can I reduce bandwidth? KX II provides a variety of settings in our remote clients for the user to optimize bandwidth and performance. The default settings will provide an at-the-rack level of performance in standard LAN/WAN environments with economical use of bandwidth. Bandwidth management settings include the connection speed and color depth. To reduce bandwidth: Connection speed.
Appendix F: Frequently Asked Questions Question Answer What should I do on slower bandwidth links? The connection speed and color depth settings can be tweaked to optimize performance for slower bandwidth links. For example, in the Multiplatform Client or the Virtual KVM Client, set the connection speed to 1.5 Mb or 1 Mb; and the color depth to 8 bit. Even lower connection speeds and color depths can be used for very low bandwidth situations.
Appendix F: Frequently Asked Questions Question Answer What about servers with DVI ports? Servers with DVI ports that support DVI-A (analog) and DVI-I (integrated analog and digital) can use Raritan’s ADVI-VGA inexpensive, passive adapter to convert the server’s DVI port to a VGA plug that can be connected to a KX II CIM’s VGA plug. Servers with DVI ports that support DVI-I or DVI-D (digital) can use the new D2CIM-DVUSB-DVI CIM.
Appendix F: Frequently Asked Questions User Task Default 1Mb Speed and 15-bit Color 1Mb Speed and 8-bit Color Open Text Window 50 – 100 KB/s 25 – 50 KB/s 10 – 15 KB/s Continuous Typing 1 KB/s .5 – 1 KB/s .2 – .
Appendix F: Frequently Asked Questions Question Answer What is the speed of Dominion KX II’s Ethernet interfaces? Dominion KX II supports gigabit as well as 10/100 Ethernet. KX II supports two 10/100/1000 speed Ethernet interfaces, with configurable speed and duplex settings (either auto detected or manually set). Can I access Dominion KX II over a wireless connection? Yes. Dominion KX II not only uses standard Ethernet, but also very conservative bandwidth with very high quality video.
Appendix F: Question Answer Can the Dominion KX II use DHCP? DHCP addressing can be used; however, Raritan recommends fixed addressing since the Dominion KX II is an infrastructure device and can be accessed and administered more effectively with a fixed IP address. I’m having problems connecting to the Dominion KX II over my IP network. What could be the problem? The Dominion KX II relies on your LAN/WAN network. Some possible problems include: Ethernet auto-negotiation.
Appendix F: Question Answer What is IPv6? IPv6 is the acronym for Internet Protocol Version 6. IPv6 is the "next generation" IP protocol which will replace the current IP Version 4 (IPv4) protocol. IPv6 addresses a number of problems in IPv4, such as the limited number of IPv4 addresses. It also improves IPv4 in areas such as routing and network auto-configuration. IPv6 is expected to gradually replace IPv4, with the two coexisting for a number of years.
Appendix F: Question Answer What if my network doesn’t support IPv6? The Dominion KX II’s default networking is set at the factory for IPv4 only. When you are ready to use IPv6, then follow the above instructions to enable IPv4/IPv6 dual-stack operation. Where can I get more information on IPv6? See www.ipv6.org for general information on IPv6. The Dominion KX II user guide describes the Dominion KX II’s support for IPv6.
Appendix F: Question Answer What about mouse synchronization? In the past, KVM-over-IP mouse synchronization was a frustrating experience. The Dominion KX II’s Absolute Mouse Synchronization provides for a tightly synchronized mouse without requiring server mouse setting changes on Windows and Apple® Mac servers. For other servers, the Intelligent Mouse mode or the speedy, single mouse mode can be used to avoid changing the server mouse settings.
Appendix F: Question Answer Do I have to use hotkeys to switch between blades? Some blade servers require you to use hotkeys to switch between blades. With the Dominion KX II, you don’t have to use these hotkeys. Just click on the name of the blade server, and the Dominion KX II will automatically switch to that blade without the explicit use of the hotkey. Can I access the blade server’s management module? Yes.
Appendix F: Question Answer Is virtual media supported? This depends on the blade server. HP blades can support virtual media. The IBM BladeCenter (except for BladeCenter T) supports virtual media if configured appropriately. A virtual media CIM – D2CIM-VUSB or D2CIM-DVUSB – must be used. Is Absolute Mouse Synchronization supported? Servers with internal KVM switches inside the blade chassis typically do not support absolute mouse technology.
Appendix F: Question Answer How do I connect servers to Dominion KX II? Servers that connect to the Dominion KX II require a Dominion or Paragon CIM, which connects directly to the keyboard, video and mouse ports of the server. Then, connect each CIM to Dominion KX II using standard UTP (unshielded twisted pair) cable such as Cat5, Cat5e or Cat6. How far can my servers be from Dominion KX II? In general, servers can be up to 150 feet (45 m) away from Dominion KX II, depending on the type of server.
Appendix F: Question Answer How do I connect a serially controlled (RS-232) device, such as a Cisco router/switch or a headless Sun server, to Dominion KX II? If there are only a few serially controlled devices, they may be connected to a Dominion KX II using Raritan’s P2CIM-SER serial converter. Customers can also consider deploying the Dominion KSX II, an integrated KVM and serial switch. The DKSX-144 features four KVM-over-IP ports and four serial ports.
Appendix F: Question Answer When I am using the local port, do I prevent other users from accessing servers remotely? No. The Dominion KX II local port has a completely independent access path to the servers. This means a user can access servers locally at the rack – without compromising the number of users that access the rack remotely at the same time. Can I use a USB keyboard or mouse at the local port? Yes. The Dominion KX II has USB keyboard and mouse ports on the local port.
Appendix F: Question Answer If I use the local port to change the name of a connected server, does this change propagate to remote access clients as well? Does it propagate to the optional CommandCenter appliance? Yes. The local port presentation is identical and completely in sync with remote access clients as well as Raritan’s CommandCenter Secure Gateway management appliance.
Appendix F: Question Answer Must I use the extended local port? No. The extended local port is an optional feature and is disabled by default. Use the "Local Port Settings" page to enable it. You can also disable the standard local port if you are not going to use it for added security. Dual Power Supplies Does Dominion KX II have a dual power option? Yes. All Dominion KX II models come equipped with dual AC inputs and power supplies with automatic failover.
Appendix F: Question Answer How do I connect the PDU to The D2CIM-PWR is used to connect the the Dominion KX II? power strip to the Dominion KX II. The D2CIM-PWR must be purchased separately; it does not come with the PDU. Does Dominion KX II support Yes. Dominion KX II can be easily servers with multiple power configured to support servers with multiple supplies? power supplies connected to multiple power strips. Four power supplies can be connected per target server.
Appendix F: Question Answer How do I physically connect multiple Dominion KX II devices together into one solution? To physically connect multiple KX II devices together for consolidated local access, you can connect the local ports of multiple "tiered" (or "cascaded") KX II switches to a "base" KX II using the tiering feature of the KX II. You can then access the servers connected to your KX II devices from a single point in the data center via a consolidated port list.
Appendix F: Question Answer Do I have to physically connect Dominion KX II devices together? Multiple Dominion KX II units do not need to be physically connected together. Instead, each Dominion KX II unit connects to the network, and they automatically work together as a single solution if deployed with Raritan’s CommandCenter Secure Gateway (CC-SG) management appliance. CC-SG acts as a single access point for remote access and management.
Appendix F: Computer Interface Modules (CIMs) Question Answer What type of video is supported by Our CIMs have traditionally supported analog your CIMs? VGA video. Three new CIMs support digital video formats, including DVI, HDMI and DisplayPort. These are the D2CIM-DVUSB-DVI, D2CIM-DVUSB-HDMI and D2CIM-DVUSB-DP. Can I use computer interface modules (CIMs) from Paragon, Raritan’s analog matrix KVM switch, with Dominion KX II? Yes.
Appendix F: Question Answer Does Dominion KX II support Paragon Dual CIMs? Yes. The Dominion KX II now supports Paragon II Dual CIMs (P2CIM-APS2DUAL and P2CIM-AUSBDUAL), which can connect servers in the data center to two different Dominion KX II switches. If one KX II switch is not available, the server can be accessed through the second KX II switch, providing redundant access and doubling the level of remote KVM access.
Appendix F: Question Answer Does Dominion KX II allow encryption of video data? Or does it only encrypt keyboard and mouse data? Unlike competing solutions, which only encrypt keyboard and mouse data, Dominion KX II does not compromise security – it allows encryption of keyboard, mouse, video and virtual media data.
Appendix F: Smart Cards and CAC Authentication Question Answer Does Dominion KX II support smart card and CAC authentication? Yes. Smart cards and DoD common access cards (CAC) authentication to target servers is supported by Release 2.1.10 and greater. What is CAC? Mandated by Homeland Security Presidential Directive 12 (HSPD-12), CAC is a type of smart card created by the U.S. government and used by U.S. military and government staff.
Appendix F: Question Answer Can Dominion KX II be remotely managed and configured via Web browser? Yes. Dominion KX II can be completely configured remotely via Web browser. Note that this does require that the workstation have an appropriate Java Runtime Environment (JRE) version installed. Besides the initial setting of Dominion KX II’s IP address, everything about the solution can be completely set up over the network.
Appendix F: Documentation and Support Question Answer Where do I find documentation on the Dominion KX II? The documentation is available at raritan.com on the KX II firmware and documentation page: http://www.raritan.com/support/dominion-kx-ii. The documentation is listed by firmware release. What documentation is available? A Quick Setup Guide, User Guide and a KVM and Serial Client Guide, as well as Release Notes and other information are available. Is online help available? Yes.
Appendix F: Question Answer I changed and subsequently forgot Dominion KX II’s administrative password; can you retrieve it for me? Dominion KX II contains a hardware reset button that can be used to factory reset the device, which will reset the administrative password on the device to the default password. How do I migrate from the Dominion KX I to Dominion KX II? In general, KX I customers can continue to use their existing switches for many years.
Index A A.
Index CIMs Required for Virtual Media • 97 Cisco ACS 5.
Index Disconnecting Users from Ports • 126, 127 Discovering Devices on the KX II Subnet • 46 Discovering Devices on the Local Subnet • 45 Documentation and Support • 386 Drive Partitions • 103 Dual Port Video Configuration Steps • 316, 321 Dual Port Video Group Usability Notes • 318 Dual Port Video Groups - Port Access Page • 41 Dual Port Video Groups Displayed on the Ports Page • 325 Dual Stack Login Performance Issues • 338 Dual Video Port Group Supported Mouse Modes • 82, 317, 323 Dual Video Port Groups
Index Java Validation and Access Warning • 27 JRE Requirements and Browser Considerations for Mac • 312 K Keyboard Language Preference (Fedora Linux Clients) • 347 Keyboard Limitations • 77 Keyboard Macros • 60 Keyboard Notes • 345 Keyboard Options • 60 KX II Client Applications • 9 KX II Console Navigation • 37 KX II Device Photos and Features • 5 KX II Help • 9 KX II Interface • 34 KX II Interfaces • 32 KX II Local Console • 266 KX II Local Console Factory Reset • 279 KX II Local Console Interface KX II
Index O Operating System IPv6 Support Notes • 337 Overview • 10, 52, 105, 108, 257, 266, 316, 326, 335 P Package Contents • 4 Permissions and Dual Video Port Group Access • 219, 319 Ping Host Page • 253 Port Access Page (Local Console Server Display) • 268 Port Access Page (Remote Console Display) • 34, 38, 183, 268 Port Action Menu • 39, 41 Port Group Management • 216 Power Supply Setup • 170 Prerequisites for Using AKC • 53, 93 Prerequisites for Using Virtual Media • 96 Product Features • 7 Proxy Mode a
Index SSH Access from a Windows PC • 258 SSH Connection to the KX II • 258 SSL Certificates • 27, 234 Standard Mouse Mode • 72 Step 1 Configure the Target Server Display • 321 Configuring Network Firewall Settings • 12 Step 2 Configure the KVM Target Servers • 13 Connect the Target Server to the KX III • 322 Step 3 Configure the Mouse Mode and Ports • 323 Connect the Equipment • 16, 173, 185, 187, 191 Step 4 Configure the KX II • 18 Create the Dual Video Port Group • 323 Step 5 Launch a Dual Port Video Gro
Index V Working with Target Servers • 32, 184, 325 Version Information - Virtual KVM Client • 91 Video Image Appears Dark when Using a Mac • 313 Video Mode and Resolution Notes • 348 Video Properties • 66 View by Group Tab • 40 View by Search Tab • 40 View Options • 79 View Status Bar • 80 View the KX II Users List • 126 View Toolbar • 79 View Users by Port • 126 Viewing the KX II MIB • 157, 162, 167 Virtual KVM Client (VKC) and Active KVM Client (AKC) • 52 Virtual KVM Client (VKC) and Active KVM Client
U.S./Canada/Latin America Monday - Friday 8 a.m. - 6 p.m. ET Phone: 800-724-8090 or 732-764-8886 For CommandCenter NOC: Press 6, then Press 1 For CommandCenter Secure Gateway: Press 6, then Press 2 Fax: 732-764-8887 Email for CommandCenter NOC: tech-ccnoc@raritan.com Email for all other products: tech@raritan.com China Europe Europe Monday - Friday 8:30 a.m. - 5 p.m. GMT+1 CET Phone: +31-10-2844040 Email: tech.europe@raritan.com United Kingdom Monday - Friday 8:30 a.m. to 5 p.m.
