Zero-footprint: System Requirements

FlexNet Manager Suite 2020 R1 (On-Premises)

These details apply to the use of the FlexNet inventory core components installed as standard on each inventory beacon server (as part of the installation of FlexNet Beacon). In this configuration, the FlexNet inventory core components use remote execution techniques to gather inventory from separate targets (the techniques are naturally different for Windows and UNIX-like platforms, and are detailed in Zero-footprint: Normal Operation). Therefore, there are two sets of requirements that become important in this Zero-footprint case:

• The requirements on the inventory beacon server itself
• Any impacts on the target inventory devices.

Note: At the risk of confusion, we should note that an inventory beacon can also be a managed device, a computer for which you want to collect its own inventory. This uses a separate code collection. For the remainder of this topic, we are overlooking this aspect, and focusing exclusively on the capacity of the FlexNet Beacon code installed on the inventory beacon to remotely collect inventory from other target inventory devices, excluding itself.

Supported platforms

On the inventory beacon itself, the FlexNet inventory core components impose no limits on the supported platforms. The FlexNet Beacon code (including the FlexNet inventory core components) can be installed on the following platforms:

• Windows Server 2012, 2012 R2, 2016, 2019
• Windows 8 x64, 10 x64
• Window 8, 10.

For remote inventory collection in the Zero-footprint case, inventory can be gathered from the following platforms:

Windows Server 2003 SP1 and SP2, 2008 R2 x64, 2012, 2012 R2, 2012 R2 SP1, 2016, 2019 Windows Server Core 2008, 2008 R2 x64, 2012, 2012 R2 Windows Server Standard (previously known as Windows Server Core) 2016, 2019 Windows Vista x64, 7 x64, 8 x64, 10 x64 Windows Vista, 7, 8, 10.

• AIX 7.1 LPARs, 7.2
• Amazon Linux 2
• CentOS (x86, 32-bit and 64-bit): 6-7.5; (x86 64-bit only): 7.6-7.7 (lower versions); 8.0-8.1 (higher versions)
• Debian Linux 7–10.2 (x86, 32-bit and 64-bit), 10.3 (x86 64-bit only)
  Note: For Debian Linux 9.4, 9.5 and 10 (both 32-bit and 64-bit), minimal installations of the OS core omit the ifconfig command. This prevents collection of the IP address and MAC address in inventory. The root user can use the following command to restore this functionality:

       apt-get install net-tools  -y

• Fedora Linux 25-30 (x86, 32-bit and 64-bit); 27-31 (x86 64-bit only)
• HP-UX 11i v3, vPars/nPars
• macOS 10.6–10.15
• OpenSuSE Leap 42.2, 42.3 (x86, 32-bit and 64-bit); 15-15.1 (x86 64-bit only)
• Oracle Linux 4.5–6.10 (x86, 32-bit and 64-bit); 7.0-8.0 (x86 64-bit only)
• Red Hat Enterprise Linux (RHEL) (x86, 32-bit and 64-bit) 5.0–6.10; (x86 64-bit only) 7.0-7.8 (lower versions); 8.0-8.2 (higher versions)
• Photon OS 3.0
• Red Hat Linux 8–9 (x86 only)
• Solaris 8–11 (SPARC), Zones for versions 10–11
• Solaris 9–11.4 (x86), Zones for versions 10–11
• SuSE Linux Enterprise Server 11 (x86, 32-bit and 64-bit); 12 SP3, 12 SP4, 12 SP5, 15, 15 SP1 (x86 64-bit only)
• Ubuntu 12–17.04 (x86, 32-bit and 64-bit); 17.10-18.4.4 (x86 64-bit only).

Disk space requirements

On the inventory beacon itself, the FlexNet inventory core components are included in the disk space requirement for FlexNet Beacon:

• 1 GB of free disk space for each 10,000 devices from which FlexNet inventory is collected.

On target inventory devices (in the Zero-footprint process), the following are platform-specific disk space requirements:

• Windows: Where the target device is a typical workstation, in the order of 2MB; and for an Oracle server, in the order of 5MB.
• UNIX-like platforms: The downloaded code is approaching 23MB, and it then looks for an additional 16MB of working disk space in either (in priority order):
  1. The home directory of the account running the inventory (unless that directory is /)
  2. /var/tmp.
  Where this space is not available, inventory collection is not attempted.

After Zero-footprint inventory collection, the following (non-executable) files are left on the target inventory device as a potential aid to process validation or trouble-shooting, and are all replaced at the next iteration of the same process:

• An uncompressed inventory (.ndi) file is left:
  • For Windows devices, in %ProgramData%\ManageSoft Corp\ManageSoft\Tracker\ZeroTouch
  • For UNIX-like devices, when inventory collection is (as usual) run as root, in /var/tmp/flexera/tracker; or if inventory collection is run as another user, in /var/tmp/flexera.userName/tracker.
• Log files are saved on the target inventory device:
  • For Windows devices, in C:\Windows\temp\ManageSoft
  • For UNIX-like devices, when inventory collection is (as usual) run as root, in /var/tmp/flexera/log; or if inventory collection is run as another user, in /var/tmp/flexera.userName/log.

The following log file is available on the target inventory device in the Zero-footprint case:

• tracker.log — Generated by the inventory component, ndtrack

Memory requirements

On the inventory beacon itself, the memory demands in the Zero-footprint inventory collection process are negligible, and entirely covered by the standard specification for the inventory beacon of 1GB minimum RAM, 2GB or higher recommended.

On target inventory devices, the memory requirements are:

• Minimum RAM: 512 MB
• Recommended RAM: 2 GB

In general, through a cycle of inventory gathering and upload, the memory demand is in the order of 5-30 MB.

Communication protocols and ports

All ports used in Zero-footprint discovery and inventory collection are configurable to any value either through preference settings or by including the port number in URL settings.

The default ports used for discovery depend on what the inventory beacon is tasked to discover:

• ICMP is used for ping discovery of networked computers
• 135 (default) on the target device for WMI-based discovery of Hyper-V or XenDesktop (other ports depend on your configuration of WMI)
• 80 (with HTTP), 443 (with HTTPS) for VMware ESX/VCenter (default values, and of course using TCP)
• 1433 for Microsoft SQL Server (default)
• 1521, 2483 for Oracle DB (default)
• 137 for NetBIOS discovery of networked computers (default)
• 161 for SNMP discovery of networked computers (default)

The default ports for communications required for the Zero-footprint inventory case are:

• Windows: Outbound from inventory beacon to set up the service: for SMB, port 445; and for NetBIOS, port 139
• UNIX-like platforms: Outbound from inventory beacon to establish secure connection and copy the FlexNet inventory core components (in self-installing form): port 22
• Additional ports outbound from inventory beacon to an Oracle Database: ports 1521 and 2483
• Additional ports outbound from inventory beacon to a virtual machine under either ESX or VCenter: 80 and 443
• Windows and UNIX: Inbound from FlexNet inventory core components on target device: File upload using HTTP protocol: port 80
• Windows only: Inbound from FlexNet inventory core components on target device: File upload using HTTPS protocol: port 443
  Tip: HTTPS is not supported for UNIX-like platforms in the Zero-footprint case.
• Additional ports may be required if supporting a proxy.

Supported packages to inventory

FlexNet inventory can include data from most package technologies supported by the operating systems, and some additional third-party packaging technologies:

Platform	Supported package technologies
All platforms	InstallAnywhere (IA), InstallShield Multiplatform (ISMP), BEA/Oracle Installer (BEA), Oracle Universal Installer (OUI), IBM Installation Manager (IIM)
AIX	LPP, RPM
HP-UX	Software Distributor SD-UX Package
Linux	RPM (Red Hat, CentOS, Oracle, SuSE, Fedora, etc), DPKG (Debian, Ubuntu).
macOS	Mac Application Bundle, Mac Package Bundle
Solaris	Sys V Package (pkg), IPS
Windows	MSI, Add/Remove Programs Registry Key

However, FlexNet inventory cannot collect data from some of the less common or newer operating system technologies and many third-party technologies. Some known examples include:

• All platforms — IBM InstallStream, IBM Tivoli Netcool Installer
• macOS — Mac flat package.

System load benchmarks

The following notes reflect observed behavior on sample target inventory devices during collection of FlexNet inventory:

Task	Run duration (seconds)	CPU usage (seconds)	CPU usage (% of single core)	Memory usage	Network load
Inventory collection	13 to 240 s	5 to 130 s	10% to 50%	4 MB to 20 MB	10 KB to 200 KB per upload