Import

The Import page lets you import data from multiple different sources, and in multiple formats.

Figure 1. Import page

Import page

Import nodes

This feature lets you bind fields from a comma-separated value (CSV) files to Nozomi Networks fields so that you can add nodes (flag create non-existing nodes), or enrich existing ones. For each modified node, the file must include a row with columns that specify the additional data.
Note: Some special fields and confirmed media access control (MAC) addresses are restricted to specific values and so they might not be overwritten.

Import variables

This feature lets you add new variables (flag create non-existing variables), or to enrich existing variables. For each modified variable, the file must include a row with columns that specify the additional data.

Import asset types

This feature lets you enlarge the built-in set of asset types with a set of new custom types. The CSV file should include a header row labeled Name and the list of asset type names in the following rows, one per row. A name identifies each asset type. This means that, during the import process, duplicate names are ignored and notified.

Default asset types

  • actuator
  • audio_video
  • AVR
  • barcode_reader
  • camera
  • computer
  • controller
  • digital_io
  • drone
  • DSL_modem
  • firewall
  • gateway
  • HMI
  • IED
  • infusion_system
  • inverter
  • IO_module
  • IOT_device
  • light_bridge
  • media_converter
  • medical_imager
  • meter
  • mobile_phone
  • network_security_appliance
  • OT_device
  • other
  • PDU
  • PLC
  • power_generator
  • power_line_carrier
  • printer_scanner
  • radio_transmitter
  • robot
  • router
  • RTU
  • sensor
  • server
  • switch
  • tablet
  • time_appliance
  • UPS
  • VOIP_phone
  • WAP

Import configuration / project file

This feature lets you import a project file. The information written in the project file is added to the asset data.
Note: For XML Profinet GSDML, you can import an eXtensible Markup Language (XML) Profinet GSDML file that describes a physical device. Information in the file lets Guardian extract and display information about the device configuration when device configuration packets are displayed in traffic.
Table 1. Supported file types for configuration / project files
Supported file type Imported fields
Allen-Bradley

ip, firmware version, product name, modules (i.e. port, address, product code, firmware version, product name, vendor)
Honeywell TDS label, vendor
IEC 61850 SCL/SCD

ip, VLAN, product name, asset type, vendor, AppID, data model

Note: Importing this file changes the knowledge of the IEC 61850 data model in use in the system, thus improving Guardian's ability to accurately extract variables. Existing variables related to this protocol are deleted to avoid inconsistencies with those extracted from traffic after the import.
Profinet IOCM

modules (i.e. slot, subslot, vendor, software release, hardware release). It might also extract variables
Rockwell Harmony ip, product name
Siemens

ip, mac address, vendor, product name, label, modules (i.e. rack, slot, subslot, product code, module code)
Triconex ip, label, vendor
Yokogawa Centum

ip, label, vendor, product name, modules (i.e. slots, each with vendor, product name, firmware version)

Import content pack

You can use the Export page to export data in content packs and then you can use the Import page of a different machine to import them. For more details, see Export.

Import Arc data archive

When Arc is in Offline mode, the data is collected locally and then exported in an archive file from the machine. The archive file can then be manually imported into Central Management Console (CMC), Guardian, or Vantage.