Table of Contents

Introduction

A protocol typically defines one or more connections through which the element running the protocol communicates with the device (or multiple devices). DataMiner supports different types of connections, such as SNMP, serial, HTTP, etc. A protocol can define multiple connections of different types (e.g. an HTTP connection and two SNMP connections).

With the Type tag, the protocol connections can be defined. The main connection is specified as the value of the Type tag, e.g. <Type relativeTimers="true">snmp</Type>. In case multiple connections are used, the additional connections need to be defined in the advanced attribute of the Type tag, indicating the type and name of each additional connection:

<Type relativeTimers="true" options="unicode" communicationOptions="smartIPHeader" advanced="smart-serial:IP Connection - POST Messages;http:HTTP Connection - Master">http</Type>

In the connector logic, it is sometimes necessary to specify to which connection particular functionality relates. This is done using an integer value denoting the connection ID. The main connection has ID 0, and every additional connection defined in the protocol corresponds to an incremented ID. (For the example above, this means that the main HTTP connection has ID 0, the smart-serial connection has ID 1, and the second HTTP connection has ID 2.)

By default, groups and actions that involve a connection always use the main connection (connection ID 0). In case another connection should be used, this must be specified in the protocol.

You can specify a connection on group level by using the connection attribute in the Group tag.

<Groups>
  <Group id="1" connection="2">
    <Name>getXmlFile</Name>
    <Description>Get XML File</Description>
    <Content>
      <Session>1</Session>
    </Content>
  </Group>
</Groups>

For some actions, you can for example use the Type@nr attribute to specify the connection.

<Actions>
  <Action id="402">
    <On id="402" nr="1">parameter</On>
    <Type>set</Type>
  </Action>
</Actions>

Element Wizard

A connection has a number of configurable port settings. It is possible to define default settings for connections. It is also possible to restrict the capabilities of a device port, and to define the format and range of the bus address, if any.

Note

We recommend specifying as many port settings as possible, because it greatly enhances the user-friendliness of the protocol during element creation.

The PortSettings tag allows the configuration of the main connection. Using the Ports/PortSettings tag, the port settings of each additional connection can be configured.

<PortSettings>
   <!- Port settings for main protocol type (serial). -->
  ...
</PortSettings>
<Ports>
   <PortSettings name="ConnectionName">
  <!- Port settings for additional protocol type (SNMP). -->
  ...
  </PortSettings>
</Ports>

For example, when an element is created or edited in DataMiner, the bus address field allows the user to provide input for the configuration of the element. In most cases, this bus address will be a slot number of a chassis. In case no bus parameter is used in the protocol, it should be disabled.

Note

The order in which the port settings are defined in the parent Ports tag determines which connections these port settings apply to. The name attribute of the PortSettings tag has no influence on this.

<PortSettings>
  <BusAddress>
     <Disabled>true</Disabled>
  </BusAddress>
</PortSettings>

The following table provides an overview of the port types DataMiner supports for the different connection types:

Connection type TCP/IP UDP/IP Serial
virtual
snmp ✔
snmpv2 ✔
snmpv3 ✔
serial ✔ ✔ ✔
serial single ✔ ✔ ✔
smart-serial ✔ ✔
smart-serial single ✔ ✔
http ✔
gpib ✔
opc ✔
sla

Port types that are not supported can be hidden from the "Type of port" box in the element editor using the Disabled child tag of the PortTypeIP, PortTypeUDP, and PortTypeSerial tag for TCP, UDP, and serial, respectively.

For example, for an HTTP connection, UDP and Serial should be disabled:

<PortSettings name="HTTP Connection">
   <BusAddress>
      <DefaultValue>bypassProxy</DefaultValue>
      <Disabled>false</Disabled>
   </BusAddress>
   <IPport>
      <DefaultValue>80</DefaultValue>
   </IPport>
   <PortTypeUDP>
      <Disabled>true</Disabled>
   </PortTypeUDP>
   <PortTypeSerial>
      <Disabled>true</Disabled>
   </PortTypeSerial>
</PortSettings>

For several connection types, some port types are already disabled by the client. The following connection types, however, require configuration in the protocol to disable a port type:

  • Serial – when using SSH: "Serial" and "UDP/IP" need to be disabled in the protocol
  • Smart-serial: "Serial" needs to be disabled in the protocol
  • Smart-serial single: "Serial" needs to be disabled in the protocol
  • HTTP: "Serial" and "UDP/IP" need to be disabled in the protocol

See also

DataMiner Protocol Markup Language:

Improve this page