Runbook · Most common issue #7

Data sharing and K-IMS integration failures

Integration

Symptom

Crane data not flowing to third-party systems: the customer's K-IMS or SCADA shows no values, stale values, or cannot connect to the OPC UA / Modbus endpoints.

Investigate

Split the path in three: (1) datasharing container up and listening on the VLAN 40 NIC, (2) firewall allows the customer host to 4840/502, (3) tag mapping matches what K-IMS subscribes to. Test each from the Maxedge side before involving the customer.

Fix

docker ps | grep datasharing
docker logs --tail 200 datasharing
ss -tlnp | grep -E '4840|502'
# which customer hosts are connecting?
ss -tn state established '( sport = :4840 or sport = :502 )'
# firewall counters, customer → datasharing
show security policies from-zone customer to-zone datasharing

K-IMS typically subscribes over OPC UA with a fixed node-id list. Renamed or removed tags after a config change show as BadNodeIdUnknown on their side — not as a connection error.

Steps

docker ps → datasharing Up and ss -tlnp shows 4840 and 502 listening on the 192.168.40.x NIC. Not listening → logs, restart (runbook).
No established connection from the customer host → firewall or their side. Check the customer → datasharing policy counters; confirm the K-IMS host IP is the one in the unit's Masterdata integration sheet.
Connected but no / stale values → tag mapping. Compare Dashboard → Configuration → History with the K-IMS node list; restore the previous config if tags were dropped (guide).
Certificate errors in K-IMS (OPC UA security) → the Maxedge server certificate rotated; hand the new cert from Dashboard → Datasharing → Security to the customer to trust.
Verify end to end with an OPC UA client from the VLAN 40 side, then ask the customer to confirm in K-IMS.

Not resolved? Escalate to Product Engineering with docker ps -a, the relevant docker logs and the unit's Masterdata link.