Tools for validation, prototyping, and testing

The Mirror Platform & the Local Toolset

The 5GinFIRE Mirror Platform

To enable experimenters and developers to carry out a first validation of their Network Services (NS) and Virtualized Network & Vertical Functions (VxFs), 5GinFIRE provides a functional replica of the MANO platform currently in production state. This replica, referred to as the mirror platform in this page, provides platform users with access to an OSM installation that supports the following functionalities:

  1. Onboarding of VxFs.
  2. Onboarding of NSes.
  3. Access to OSM logs, to get information on any onboarding errors.

This way, the mirror platform allows platform users to verify if an NS or VxF can be onboarded to OSM, before formally requesting the onboarding of the component to the production MANO platform through the 5GinFIRE Portal. Its main purpose is to agilely detect errors in NS/VxF package specifications early in the experimentation process. This way, users can autonomously do a preliminary validation of their NS/VxF packages, making sure that they are compliant with the OSM software and can effectively be onboarded to the production OSM platform. This allows reducing potential interaction cycles and delays that would otherwise be necessary to set up an experiment with new NS/VxFs, optimizing the experimentation process.

When using the mirror platform, please take into account the following considerations:

  1. The mirror platform does not attach any VIM tenant, hence it cannot be used to test the deployment of a NS.
  2. The mirror platform may be restarted with certain periodicity, and data may be deleted for maintenance purposes. Users are encouraged to not consider this as a stable platform to keep copies of their NS/VxFs.

Preliminary steps

To access the mirror platform, you need to connect to the 5GinFIRE VPN. You can request VPN credentials to access the 5GinFIRE network infrastructure by creating a ticket to [5GinFIRE Operations] (

Accessing the mirror platform

After obtaining VPN credentials and connecting to the VPN (a tutorial to connect to the 5GinFIRE VPN can be found here), you can access the Graphical User Interface (GUI) of the mirror platform through this link:

  • (using Chrome is recommended)
  • User and password details to be provided on demand.

Osm Lwb Ui Login
Image extracted from the ETSI OSM Wiki

Onboarding a NS/VxF

The process to onboard a VNF is detailed in the ETSI OSM Wiki. You just need to click on the Onboard VNFD button of the VNF Packages open list, and drag & drop the VNF package file.

800 Px Vnfd Onboard R 4
Image extracted from the ETSI OSM Wiki

A similar approach can be followed to import a NS package, selecting Onboard NSD instead of Onboard VNFD.

Accessing the logs

If the onboarding fails, you can access the OSM logs to get more information about the error. To do that, access via ssh to the mirror platform, i.e., using the IP address

  • User and password details to be provided on demand

> ssh user@

OSM Release FOUR includes several components in its architecture (e.g., a LifeCycle Management (LCM), a Resource Orchestrator (RO), and VNF Configuration and Abstraction (VCA) modules among others). Each of these components is executed in a Docker container. You can see the information regarding these containers with the following command:

> docker service list


To get information on the specific failure produced by the onboarding attempt, you will need to access the LCM and the RO logs.

The LCM logs are available at the osm_lcm container. The log can be verified from the host using the following command:

> docker service logs osm_lcm

The RO logs can be found at the osm_ro container. You can get check the RO log with the following command:

> docker service logs osm_ro

The local toolset

In addition to the mirror platform, 5GinFIRE partners have also prepared a local toolset that provides a complete and functional orchestration environment to support prototyping and testing. This toolset includes:

  • An installation of OSM Release FOUR
  • A VIM emulator solution, Vim-emu.

The local toolset is provided as a single virtual machine, which can be downloaded by experimenters and other interested users from the 5GinFIRE website. With this toolset, experimenters may also test if a NS or VxF can be onboarded to OSM (and hence to the 5GinFIRE MANO system).

On the other hand, Vim-emu is capable of emulating the functionality of a VIM and an NFVI, providing a network emulation framework and supporting the deployment of VNFs as Docker containers. This way, the local toolset also complements the functionalities of the 5GinFIRE Portal, providing a mechanism to assist experimenters in the prototyping and testing of NSes.

The virtual machine of the local toolset can be downloaded here. As a final note, the requirements needed to execute this virtual machine are the following:

  • 1 vCPU.
  • 4 GB of memory.
  • 65 GB of storage.
  • A network interface with Internet connectivity.