Virtual SEM: one location
Virtual SEM is typically tied to a single server and a single location per installation.
From SEM to MSEM
This page is intended to inform installation partners about the planned transition from Secure Edge Module (SEM) to Micro Secure Edge Module (MSEM), explain the differences between the two, and outline the expected transition path.
We also want to use this period to collect feedback. If you see any issues with removing existing SEM installations and replacing them with MSEM installations, please let us know as soon as possible by contacting Sander van Mook, Product Owner Connect, at sander.vanmook@nordomatic.com.
What Is The Difference
SEM and MSEM solve the same job with different assumptions.
Feature
Virtual SEM
Micro SEM
Installation:
Windows application
Windows application
Locations per installation:
1
Multiple
Tunnel creation:
Connect / CLI
Built-in UI / CLI
Best for:
Single server / single location
Multi-site or integrator setup
Scalable deployment:
Limited
Full
MSEM keeps the same core purpose as SEM, but is designed for broader,
more scalable deployments. It also now supports tunnel creation
directly in the MSEM UI, in addition to CLI-based setup.
Micro SEM: multiple locations
Micro SEM can serve multiple locations from one installation, which makes it better suited for larger or distributed setups.
In iBOS Connect, a location refers to how environments are organized
in the dashboard. A location does not have to mean a physically
separate site. It can also be used to divide different parts of the
same network or deployment into separate logical areas.
Why We Want To Drop SEM
Drop support of unused functionalities
What SEM contains
SEM still carries both the active parts and older functionality that is no longer needed.
- Link Needed for link creation between SEM and Connect.
- Tunnel Needed for tunnel creation between SEM and connected devices.
- Miscellaneous Still used to support Link and Tunnel behavior.
- Building Model Deprecated Yanzi room-building logic that should be removed.
- Yanzi Sensors Legacy Yanzi-specific sensor operation that is no longer needed.
What MSEM contains
MSEM keeps the parts still needed in production and leaves the old, unused SEM functionality behind.
- Link Still supports creating the link between module and Connect.
- Tunnel Still supports creating tunnels to the devices you connect.
- Miscellaneous Retained only where it supports the active module scope.
Less legacy functionality
SEM includes a broader module scope than we need today. In addition to Link and Tunnel, it also carries older parts that increase complexity without adding value for the current direction of the product.
Cleaner support model
MSEM keeps the parts that are still relevant: Link, Tunnel, and Miscellaneous support. Legacy SEM-specific functions such as the old building model and Yanzi sensor handling are no longer part of the target architecture.
Customer impact
By moving to MSEM, customers get a more focused module with less legacy scope to maintain. That makes the solution easier to support, easier to understand, and better aligned with how the platform is used today.
Migration
How to move from SEM to MSEM
If you want to start migrating SEM installations to MSEM installations today, we have you covered. On the iBOS documentation page below, you can find the MSEM manual and the installer needed to replace SEM.
Timeline
A step by step transition
Transition announced
Both SEM and MSEM remain available and supported. MSEM will receive a new web UI for easier administration. During this period, we will collect feedback and verify that MSEM does not introduce customer-impacting gaps compared with SEM. For new installations, we recommend using MSEM only.
SEM installer is no longer available
You can no longer download the SEM installer.
SEM is no longer supported
We have no active way to disconnect running SEM installations, but SEM will no longer be supported. Issues and bugs related to SEM will no longer be fixed.