harting haiic mica administrator guide...haiic mica administrator guide 4 harting it software...

HARTING HAIIC MICA Administrator Guide

日本語

HAIIC MICA Administrator Guide

2 HARTING IT Software Development

1. Edition 2017, 11/17

© HARTING IT Software Development, Espelkamp

翻訳を含むすべての権利が留保されています。

このマニュアルのいかなる部分も、HARTING Electric GmbH & Co. KG, Espelkampの書面による許可なく、電子システムを使用して、いかなる形態（印刷、コピー、マイクロフィルムまたはその他のプロセス）でも複製、加工、複製、配布することはできません。

予告なく変更することがあります。

このAdministrator Guideは、MICAのコンフィギュレーションについて記述しています。ファームウェアベースバージョンは、V1.4.0を参照しています。


HAIIC MICA Administrator Guide, Edition 2017 3

目次ファームウェアのインストール/アップグレード ................................................... 4

ネットワークコンフィギュレーション ................................................................ 4

ユーザー管理 ....................................................................................................... 7

ファームウェアリセット ............................................................................. 8

コンテナのインストール/リセット/エクスポート/重複/構成/更新 ......................... 8 各コンテナのストレージスペース消費量とアクセス可能な

空きディスクスペースのベースへの表示 .................................................... 9

時間設定の構成 ...................................................................................................... 10

WebGUIを介してベースからコンテナへのデバイスの追加と削除 ............................. 11 ベストプラクティス ......................................................................................... 12



この「MICA Administrator Guide 」では、MICAを設定し、ネットワークに接続し、基本的な操作を実行する方法について説明しています。

ファームウェアのインストール/アップグレードファームウェアを新しいバージョンにアップグレードするには、ファームウェアのtarアーカイブをクライアントにダウンロードする必要があります。その後、MICAに管理者としてログインし、Setting下でFirmware updateを実行する必要があります。選択ウィンドウでファームウェアtarアーカイブを選択し、Updateボタンをクリックします。その後、MICA

がリブートするまで待ちます。ファームウェアを次の上位バージョンにアップグレードできます。下位バージョンにダウングレードしたり、アップグレード時にバージョンをスキップすることはできません。詳細は、リリースノートを確認してください。ダウングレードは通常推奨されません。

ネットワークコンフィギュレーションYou can now access the MICA base system using the network information printed on the

bottom label of the device.

Under Windows, the device can be reached under https://devicename (LLMNR). If your

computer is using mDNS (Linux, Mac) the device home page can be reached at https://de-

vicename.local. You might be prompted to accept the device’s security certificate or to ig-

nore a certificate error depending on your network’s security policy.

In case you cannot reach the MICA at all, you should try accessing the base system over

the IPv4 address 10.10.10.10. Put your PC in the same subnet first by selecting the IP ad-

dress 10.10.10.11 (in case this is not yet assigned) and a subnet mask 255.255.0.0. Also

check if a VPN client is installed on your PC. In this case attach the MICA to a PC without

VPN client, as the VPN client may interfere with the access over IPv6 which should work by

default.

Figure 1: Bottom Label of the MICA

https://devicename/

https://devicename.local/

https://devicename.local/



The MICA is always accessible over the default IPv6 link local address. This can be calcu-lated from the hardware data in the following way:

Take the serial number s/n from the MICA label. Calculate this in hexadecimal representa-tion. Take the last six digits and attach them to the base’s epc to receive the MICA’s epc:

30-2d-96-4a-31-20-00-40-00-XX-XX-XX.

You can calculate the MICA link local IPv6 address from the last five digits of the epc:

fe80:0000:0000:0000:<OUI><last five digits of the epc>:<0 for the basis, counting up for the containers>.

Example:

Serial number: 46925873218

Serial number in hexadecimal representation: AED000042

EPC: 30-2d-96-4a-31-20-00-40-00-00-00-42

OUI (organizationally unique identifier) is always “000a:ed” for the MICA.

IPv6-address: fe80::a:ed00:042:0

You may also use a freeware tool like “network scanner” to search the MICA name and the IPv4 address.

MICA applications run in virtual machines called containers. You can download the contain-

ers from the MICA download page http://www.harting-mica.com/downloads/. In case you

use the MICA device under IPv4 you can also configure the address statically or over

DHCP.

The following table gives an overview of base and container access under different operat-

ing systems.

Table 1: Base System

Name Resolu-

tion Protokoll

Adressformat Windows Vista+6 Linux Ubuntu 15.04 Mac OS X

pin

g

IE 1

0+

Fire

fox

Chro

me

pin

g

Fire

fox

Chro

me

pin

g

Fire

fox

Chro

me

LLMNR (IPv6)

hostname X X - X - - - - - -

mDNS (IPv6

LL)

hostname.local X1 X1 X5 X5 X3,4 - - X X -

LLMNR (IPv4) hostname X X X X X2 - X2 - - -

mDNS (IPv6

ULA)

hostname.local - - - - - - - - - -

IPv6 ULA fd96:8d76:d432:0:a:ed0

0:f:0

X X X X X X X X X X

IPv4 172.16.15.0 X X X X X X X X X X

1 "Bonjour printing services for Windows" must be installed 2 Samba name service must be configured and installed 3 mDNS name resolution for IPv6 must be configured 4 Only with specification of the Zone ID 5 Only without specification of the Zone ID 6 For versions older than Windows Vista only accessible with DHCP in the network

http://www.harting-mica.com/downloads/



Table 2: Container

Name

Resolution

Protocol

Adressformat Windows Vista+6 Linux Ubuntu

15.04

Mac OS X

pin

g

IE 1

0+

Fire

fox

Ch

rom

e

pin

g

Fire

fox

Ch

rom

e

pin

g

Fire

fox

Ch

rom

e

LLMNR (IPv6)

Hostname/Containername X X X X - - - - - -

mDNS

(IPv6 LL)

hostname.local/Containerna

me

X1 X1 X5 X5 X3,4 - - X X -

LLMNR

(IPv4)

hostname/Containername X X X X X2 - X2 - - -

mDNS

(IPv6

ULA)

hostname.local/Containerna

me

- - - - - - - - - -

IPv6 ULA fd96:8d76:d432:0:a:ed00:f:0 X X X X X X X X X X

IPv4 172.16.15.0 X X X X X X X X X X

1 "Bonjour printing services for Windows" must be installed 2 Samba name service must be installed and configured 3 Zone ID cannot be specified, works with LL-Address 4 Name server must be installed in container (standard for HARTING containers) 5 Only with specification of the Zone ID 6 For versions older than Windows Vista DHCP needs to be installed

Containers can be reached after installation under for example:

https://mica-hsmup.local/#1_https://mica-hsmup.local/GPIO (mDNS) resp. https://mica-hsmup/#1_https://mica-hsmup/GPIO (LLMNR) The MICA- / containername must of course be adjusted.

Over ssh or scp you can reach the container for example by:

GPIO-mica-hsmup

The MICA- / Containername must be adapted of course.

https://mica-hsmup.local/#1_https://mica-hsmup.local/GPIO

https://mica-hsmup/#1_https://mica-hsmup/GPIO



Figure 2: Configuration of the Network Settings

User Administration

Three different user roles can be defined: user, containeradmin and admin. The defaul

password for the admin is printed on the MICA label. The default passwords for the roles

are user, containeradmin and admin. Change the password after the firste login in the set-

tings dialogue window to ensure security. Note the password in a safe place; it can only be

reset by a complete firmware reset.

Table 4: User Roles

admin containeradmin user

Reading rights on all web-

services of the device





Rights delegated by the

container


container


container



Starting, stopping, resetting,

exporting, configurating

containers

Starting, stopping, resetting,

exporting, configurating

containers

Adding and removing de-

vices to and from containers

Setting time on base and

containers

Duplicate, install, delete, re-

name containers

Modify network settings on

the base

The rights are included in each other in the following manner:

admin ⊃ containeradmin ⊃ user

Firmware Reset

A firmware reset sets the firmware back to the state of the last firmware updates. Passwords

are reset to the default passwords admin, containeradmin and user. A statically configured

IPv4 address is reset to 10.10.10.10 resp. An IPv4 address is assigned in DHCP configur-

ated networks in acase the option „DHCP“ has been selected. All containers are stopped ,

the data last saved on them and their configuration remains intact, however.

Container Installation/ Reset/ Export/ Duplicate / Config/ Update

New containers can be installed under “Install”. Upload the selected container archive with-

out decompressing it. Activate the container by a right mouse click and the selection of

“Start App”.

Figure 3: Installation of a New Containers



Containers consist of a root file system and an overlay file system.

When updating the container the filesystem is exchanged, the newly created data in the

overlay system remains untouched however. In this way the modifications of the user are

adopted (e.g. network settings) and the base system remains consistent.

When resetting the container all user generated data of the container is deleted in the file

system. The file system of the original container remains untouched. The whole container is

returned to the original state of the last installation/update.

When duplicating a container both parts of the container are exactly duplicated and added

to the running system so that two functionally equivalent containers are installed on the sys-

tem afterwards.

When exporting a container a backup container is created with the same configuration and

the same data as the original container.

Display of the Storage Space Consumption of each Container and the Accessible Free Disc Space on the Base

The storage space consumption of each container in the root file system and the user space

and the accessible free disc space on the base is displayed.

Figure 4: Display of Storage Space Consumption



Configuration of the Time Settings

To ensure a smooth running of your applications you can set the time over the “Time and

Date” settings on the WebGUI.

Figure 5: Time and Date Settings on WebGUI

Figure 6: Time and Date Configured by NTP Server



Alternatively you can synchronize the base’s and containers’ time and date with an NTP

server of your choice by switching the “Use NTP” server option to “on” and selecting a list of

NTP servers of your choice in the NTP server list. Again, the time on the base and the con-

tainer will be the UTC time.

Adding and Removing Devices to Containers from the Base over the WebGUI

Access rights for selected devices of the base system can be granted and removed to con-

tainers by the admin.

Figure 7: Devices Can Be Added and Removed to Selected Container



The feature „Add Device to Container“ adds a device persistently from the base to a con-

tainer. On the left-hand side base devices that are not blacklisted are shown. On the right-

hand side the container wishlist is shown, not all devices in the container. The device re-

mains in the container after container export. The feature „Delete Device“ removes devices

from the container and from the wishlist as long as the device exists in the base. When ex-

porting a container the wishlist is exported; when installing a container a query asks if the

devices in the wishlist should be added.

Figure 8: Device Query When Installing a Container

Best Practices

Change the passwords for admin, containeradmin and user after login. Note the passwords

in a safe place.

Document Version

1.2 Contains decription of device management via WebGUI. Contains description

of time setting via WebGUI.

1.3 Contains more detailed description how to initially access the MICA and how

to calculate the default IPv6 address from the Mica’s serial number. Container

URL is described. IPv4 name resolution now over LLMNR instead of NetBIOS.

harting haiic mica administrator guide...haiic mica administrator guide 4 harting it software...

Documents