Differentiating MCSA between Windows and Linux - Developer Documentation
Skip to content

Differentiating MCSA between Windows and Linux

Network settings

All MCSA Docker containers are running in host network mode only, one MCSA container is chosen to have static IP addresses in the device configuration, if it is necessary that the IP addresses of the Linux host system is to be configured by the asset of the chosen MCSA Docker container.

Requirement

It is necessary that the host network interfaces are configured by the MCSA Docker containers which are configured with the static IP addresses, otherwise it is possible that another IP address will be assigned by DHCP during runtime.

Onboarding

In case of MCSA in Docker, the Docker container ID is being used as serial number, because the ID is quite long to be displayed and reduced in the status area of local MCSA UI.

But for onboarding the complete Docker container ID is displayed as a serial number:

mid-ui-02-onboarding

System settings

In the system settings, the file transfer is currently not available for version below V03.06.02.06 b001 & V03.06.20.00 b002, therefore the local MCSA UI will provide the possibility to change only the system time.

mid-ui-03-system-settings

File transfer

The File transfer functionality transfers the MCSA container's local file folder to the internal upload folder. File transfer is available starting from MCSA in Docker starting from version V03.06.02.07 b001 and V03.06.20.01 b001 and is available in MCSA settings as shown in below image.

File Transfer available

To change the file transfer settings of the device, follow these steps:

  1. Click "Get state" to get the current state of the file transfer service.

  2. Execute the following actions,

    • Enable or Disable the functionality to transfer files to Insights Hub.
    • Clean up the shared "filetransfer" folder manually.

  3. Click "Apply changes" to execute the changes.

Service enablement

File transfer service can be enabled or disabled by "File transfer active" check-box. By default this feature is disabled, enable to use this function.

Note

It is recommended to disconnect all the network mappings to the shared 'filetransfer' folder before disabling the file transfer service.

Clean folder

Enable "clean folder" check-box to manually clean the MCSA container's local file transfer folder in case few files are not transferred to the upload folder.

File transfer status

While retrieving the current file transfer state or changing the file transfer configuration, the current process and the execution result is shown in the file transfer status section. These execution results is also available in the MCSA tab on the diagnosis messages pane.

Transferring files to Insights Hub

Files copied to the MCSA container's local file transfer folder are immediately moved to internal upload folders when the file transfer service is enabled. This folder should not be used as file storage.

There are two sub-folders in the MCSA container's local file transfer folder where the files can be uploaded to different targets on Insights Hub:

  • fs

    • Files will be uploaded to Insights Hub's file storage (fs).
    • Maximum file size: 10MB.

  • idl

    • Files will be uploaded to Insights Hub's Integrated Data Lake (IDL).
    • Maximum file size: 200MB.

Note

  • To prevent the files exceeding the supported file size limits, use the disk space in the MCSA container's local file transfer folder.
  • Files directly located in the MCSA container's local file transfer folder will not be uploaded or deleted automatically, but they can be deleted manually using 'Clean folder" functionality.

Drop a copy to IDL

To drop a copy to IDL, following are the requirements of the file.

  • There are 2 types of IDL files, Object and Metadata.
  • IDL file names must be in the character set "[a-zA-Z0-9.!*'() _-/=]". For other limitations refer to IDL Documentation
  • Name of metadata should start with object name and end with metadata(lowercase) prefix for example, object_metadata.json. File extension of metadata should be json.
  • Metadata file association to object file is done by the "objectName" field in the json content. If this field is missing, metadata file will not be uploaded.

  • Example for metadata format:

    Metadata Format

  • Object files is uploaded to IDL as /agentId/objectName, so files can be shown under this folder on IDL Manager UI. No other sub-folders will be created.

  • Metadata files will be uploaded to IDL as attached to the object file which is specified in the json content.
  • If a new file is uploaded with a name that already exists on IDL, the previous file is overwritten.

Datasource protocols

System protocol

Following system protocol variables are not supported in MCSA Docker containers:

kernel

  • /kernel/osrelease
  • /kernel/ostype
  • /kernel/version

memory

  • /memory/cmafree
  • /memory/cmatotal
  • /memory/available

network

  • /network/pawspassive
  • /network/tcpdirectcopyfrombacklog
  • /network/tcpdirectcopyfromprequeue
  • /network/tcpfackreorder
  • /network/tcpforwardretrans
  • /network/tcphphitstouser
  • /network/tcpprequeued
  • /network/tcpprequeuedropped
  • /network/tcpschedulerfailed

disk

Affected sub categories:

  • persistent
  • persistent_appconfig
  • persistent_massdata
Last update: November 21, 2023