Table of Contents

Meinberg LANTIME IMS-HPS API V10

The HPS (High Precision Synchronization) provides a future-proof platform for your IEEE 1588 / SyncE / Carrier Grade NTP infrastructure. The high-performance dual-core processor, the 1-step master clock and 1 GE interface with SFP slot can support a very large number of PTP clients. The HPS can support up to 2048 PTP clients in Unicast (at 128 sync/delay requests per second), as well as more than 250 000 delay requests per second in Multicast or Hybrid mode, or more than 400 000 NTP requests per second, due to a powerful FPGA-based packet generator engine.

An NTP software service (NTPD) can also be started on the HPS board. This service can process up to 15 000 NTP requests per second. The NTPD software service can also run parallel to the PTP service.

About

Version Info

Range Key Features Based On System Impact
1.0.0.x [SLC Main] Initial version. - Minimum required DataMiner version is 10.0.9.0 - 9385 due to dynamic units.

Product Info

Range Supported Firmware REST API Version Supported Types
1.0.0.x 7.06.x
7.08.x
10.x.y
16.x.y
HPS100

System Info

Range DCF Integration Cassandra Compliant Linked Components Exported Components
1.0.0.x Yes Yes DataMiner connector:
- Meinberg LANTIME Modular API V10
DataMiner connector:
- Meinberg LANTIME IMS-HPS API V10 - PTPv2 Instance

Configuration

Connections

HTTP Main Connection

This connector uses an HTTP connection and requires the following input during element creation:

HTTP CONNECTION:

  • IP address/host: The polling IP or URL of the destination.
  • IP port: The IP port of the destination.
  • Bus address: If the proxy server has to be bypassed, specify bypassproxy.

Initialization

Slot ID

The DataMiner element will not know which slot it needs to represent until the slot ID has been provided.

On the General page, the slot ID must be configured.

REST API

The HTTP communication uses a REST API, which needs to be enabled.

On the device's web interface, make sure the Enable REST API option is selected under the general settings on the System page.

HTTP Credentials

The HTTP communication will not be up and running until the necessary HTTP credentials have been provided.

On the Credentials page of the element, the user name and password must be configured.

Web Interface

The web interface is only accessible when the client machine has network access to the product.

How to Use

REST (Representational State Transfer) calls are used to retrieve the device information.

HTTP Communication

On the HTTP Communication page, you can track the HTTP sessions used for communicating with the device.

This makes it possible to follow the communication flow and provides some useful statistics, e.g. request time, response time, time span (RTT), etc.

  • HTTP Sessions State: If you enable this setting, the active HTTP sessions will be tracked.
  • HTTP Sessions Max Count: This determines the maximum number of HTTP sessions that will be tracked.

Inter App

On the Inter App page, an overview is provided that allows you to track the inter application communication and the related handlers.

Inter App Communication

Overview of the inter application communication events and messages.

The state of a communication object indicates whether it is waiting to be processed, being processed, executed successfully, or failed.

Inter App Handlers

Overview of the inter application handlers of the received events and messages.

Every communication object will be represented by a related handler. The handler is responsible for taking the necessary actions depending on the related communication object.