Content

Summary

This document provides information about the Guntermann & Drunck CCGD protocol implementation for VSM.

Status of Driver	APPROVED
Component for Driver	GADGETSERVER
Release (Build) of Component	vsmGadgetserver 5.4.x or newer
Revision of Implementation	1.0.0.3

Name/Type of 3rd Party API	XML
Version of 3rd Party API
Additional 3rd Party information	KVM

Connection

Connection Type	TCP/ IP
Default Port	27994

You need to activate text-based control for full functionality. The following extract describes the required steps.

Supported Features

Routing of CPUs to consoles.

This protocol allows switching of the available CPUs to the known consoles. While the consoles are identified by their port number, the CPUs must be mapped internally. This mapping is stored by the protocol and can be seen in the web interface. It lists all known CPUs and their source index.

Supported Commands

The following commands are used by the current implementation

Logon	Requests to logon to the matrix.
Logoff	Requests to logoff from the matrix.
Connect	Connects a cpu to a console.
Disconnect	Disconnects a console.
List	Either lists all cpus, consoles or current connections.

Configuration Details

The protocol requires a username and a password, which can be entered via the web interface. The default user name is “Admin”, while the password is “4658”.

vsmGadgetServer 5.2 (protocol revision 1.0.0.2)

A blind source may be defined (default is 32) and a list of all known CPUs and their source index is displayed.

vsmGadgetServer 5.4

With this version the new XML format is used for matrix mapping.

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<mapping>
  <identifier>GuntermannDrunck.XML System</identifier>
  <children>
    <indexMappingRegion>
      <name>Console</name>
      <offset>0</offset>
      <usage>Target</usage>
      <children>
        <indexMapping>
          <identifier>0x0000417B</identifier>
          <index>0</index>
          <meta>
            <metaMapping>
              <name>Name</name>
              <description>CON 0000417B</description>
              <type>String</type>
            </metaMapping>
          </meta>
        </indexMapping>
        <indexMapping>
          <identifier>0x0000417A</identifier>
          <index>1</index>
          <meta>
            <metaMapping>
              <name>Name</name>
              <description>CON 0000417A</description>
              <type>String</type>
            </metaMapping>
          </meta>
        </indexMapping>
      </children>
    </indexMappingRegion>
    <indexMappingRegion>
      <name>Cpu</name>
      <offset>0</offset>
      <usage>Source</usage>
      <children>
        <indexMapping>
          <identifier>0x003036E5</identifier>
          <index>1</index>
          <meta>
            <metaMapping>
              <name>Name</name>
              <description>CPU-ID 003036E5</description>
              <type>String</type>
            </metaMapping>
          </meta>
        </indexMapping>
        <indexMapping>
          <identifier>0x003036E6</identifier>
          <index>3</index>
          <meta>
            <metaMapping>
              <name>Name</name>
              <description>CPU-ID 003036E6</description>
              <type>String</type>
            </metaMapping>
          </meta>
        </indexMapping>
      </children>
    </indexMappingRegion>
  </children>
</mapping>

XML

Use the <offset> tag to move whole Cpu/Console group wihtin the matrix. To move a single Cpu/Console use the corresponding <index> tag. If a device has been exchanged on the installation the vsmGadgetServer will generate new entries for the new device. To use the old matrix configuration the user must download the mapping file and adapt the new <index> values to the old values. Save the file and upload it again via the Web UI.

Guntermann & Drunck Control Center