HARTING HAIIC MICA Administrator Guide

Transcription

1 HARTING HAIIC MICA Administrator Guide

2 1. Edition 2017, 11/17 HARTING IT Software Development, Espelkamp All rights reserved, including those of the translation. No part of this manual may be reproduced in any form (print, photocopy, microfilm or any other process), processed, duplicated or distributed by means of electronic systems without the written permission of HARTING Electric GmbH & Co. KG, Espelkamp. Subject to alterations without notice. This Administrator Guide explains administration and configuration of the MICA. The following text refers to Firmware Base Version V HARTING IT Software Development

3 Contents Firmware Installation / Upgrade... 4 Network Configuration... 4 User Administration... 7 Firmware Reset... 8 Container Installation/ Reset/ Export/ Duplicate / Config/ Update... 8 Display of the Storage Space Consumption of each Container and the Accessible Free Disc Space on the Base... 9 Configuration of the Time Settings Adding and Removing Devices to Containers from the Base over the WebGUI Best Practices HAIIC MICA Administrator Guide, Edition

4 This MICA Administrator Guide explains how to set up the MICA, connect it to your network and perform basic operations. Firmware Installation / Upgrade To upgrade the firmware to a newer version the firmware tar-archive needs to be downloaded onto the client. Afterwards one should log in on the MICA as admin and perform a Firmware-Update under Settings. Select the firmware tar-archive in the selection window and click the button Update. Then wait until the MICA reboots. You can upgrade the firmware to the next higher version. It may not be possible to downgrade to a lower version or to skip versions when upgrading. Please check the release notes for further details. A downgrade is usually not recommended. Network Configuration You can now access the MICA base system using the network information printed on the bottom label of the device. Figure 1: Bottom Label of the MICA Under Windows, the device can be reached under (LLMNR). If your computer is using mdns (Linux, Mac) the device home page can be reached at You might be prompted to accept the device s security certificate or to ignore 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 Put your PC in the same subnet first by selecting the IP address (in case this is not yet assigned) and a subnet mask 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. 4 HARTING IT Software Development

5 Chrome Firefox ping Chrome Firefox ping Chrome Firefox IE 10+ ping HAIIC MICA Administrator Guide The MICA is always accessible over the default IPv6 link local address. This can be calculated from the hardware data in the following way: Take the serial number s/n from the MICA label. Calculate this in hexadecimal representation. Take the last six digits and attach them to the base s epc to receive the MICA s epc: 30-2d-96-4a 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: Serial number in hexadecimal representation: AED EPC: 30-2d-96-4a 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 containers from the MICA download page 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 operating systems. Table 1: Base System Name Resolution Protokoll Adressformat Windows Vista+ 6 Linux Ubuntu Mac OS X LLMNR (IPv6) mdns (IPv6 LL) hostname X X - X hostname.local X 1 X 1 X 5 X 5 X 3,4 - - X X - LLMNR (IPv4) hostname X X X X X 2 - X 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 IPv 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 HAIIC MICA Administrator Guide, Edition

6 Chrome Firefox ping Chrome Firefox ping Chrome Firefox IE 10+ ping HAIIC MICA Administrator Guide Table 2: Container Name Resolution Protocol Adressformat Windows Vista+ 6 Linux Ubuntu Mac OS X LLMNR (IPv6) Hostname/Containername X X X X mdns (IPv6 LL) LLMNR hostname.local/containerna X 1 X 1 X 5 X 5 X 3,4 - - X X - me hostname/containername X X X X X 2 - X (IPv4) 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 IPv 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: (mdns) resp. (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. 6 HARTING IT Software Development

7 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 settings 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 webservices of the device Rights delegated by the container Reading rights on all webservices of the device Rights delegated by the container Reading rights on all webservices of the device Rights delegated by the container HAIIC MICA Administrator Guide, Edition

8 Starting, stopping, resetting, exporting, configurating containers Starting, stopping, resetting, exporting, configurating containers Adding and removing devices to and from containers Setting time on base and containers Duplicate, install, delete, rename containers Modify network settings on the base Firmware Reset The rights are included in each other in the following manner: admin containeradmin user 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 resp. An IPv4 address is assigned in DHCP configurated 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 without decompressing it. Activate the container by a right mouse click and the selection of Start App. Figure 3: Installation of a New Containers 8 HARTING IT Software Development

9 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 system 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 HAIIC MICA Administrator Guide, Edition

10 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 10 HARTING IT Software Development

11 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 container 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 containers by the admin. Figure 7: Devices Can Be Added and Removed to Selected Container HAIIC MICA Administrator Guide, Edition

12 The feature Add Device to Container adds a device persistently from the base to a container. On the left-hand side base devices that are not blacklisted are shown. On the righthand side the container wishlist is shown, not all devices in the container. The device remains 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 exporting 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. 12 HARTING IT Software Development