IPv6 prefixes being announced with IPv4-mapped IPv6 next hop after network configuration. Fixed apply_settings handling the number of built-in USB ports incorrectly. Configuring 5GHz WiFi with Region 00 is now disallowed. ZPE Cloud: Fixed the issue where the device failed to reconnect to ZPE Cloud once the connection was closed from the server side. ZPE Cloud: Fixed an issue where some features from ZPE Cloud might fail if certain services on Nodegrid were restarted (CCM). ZPE Cloud: Fixed known issue from v6.0.10: ZPE Cloud: DASHBOARD :: CELLULAR DATA screen does not report any cellular data usage. ZPE Cloud: Fixed the issue related to connection to Nodegrid configuration manager, preventing the collection of configurations from the Nodegrid in case the Nodegrid configuration manager is restarted. ZPE Cloud: Fixed an issue from v6.0.10 preventing the device from reconnecting to ZPE Cloud EU after downgrading to a

User groups combine multiple local and remote users into a single local group. Members are assigned group-specific roles/permissions. Members have access to devices assigned to that group. Groups which are authenticated against an external authentication provider are mapped to local groups. When a user is assigned to a group, that user received the combined access rights. Administrators can add and delete groups, as well as change permissions. On the device's original configuration, two default groups are available: Admin and Users. The Admin group grants full system and target access.

This sub-tab provides an overview of the Network Ranges configured in the Nodegrid DHCP server. For each range, it shows the number of leased IPs, the maximum number of leases possible in that range, the number of leases currently available, and the Router IP. If any number is above 1000, it will show as "1000+".

The Nodegrid Serial Console (T Series) fits into environments that still utilize legacy devices and can be a direct replacement for any legacy console server. Features include: For Legacy Devices 16/32/48/96 Serial Ports 1U 19" Standard Unit Single AC, Dual AC, and Dual DC Nodegrid Serial Console - T Series Hardware Specifications Item Description CPU Intel Atom x86_64 dual core @ 1.75 GHz CPU Memory & Storage 4 GB of DDR3 DRAM 32 GB mSATA SSD Interfaces 2 Gigabit (10/100/1000BT) Ethernet interfaces on RJ45 or 2 SFP+ Fiber interfaces compatible with 1Gb 2.5Gb / 10Gb modules16, 32, 48, 96 RS-232 serial ports on RJ45 @ 230,400 bps max/port 1 RS-232 serial console port on RJ45 1 USB 3.0 Host 2 USB 2.0 Hosts on Type A connector HDMI Power Single/Dual AC 100-240 VAC, 50/60 Hz Dual DC: 40

Libreswan 4.12 New Features and Enhancements Remote cluster device access now proxies through cluster peers (including multi-cluster), being able to reach isolated subnetworks Integrated UI support for FRR configuration Improved UI for wireless modem diagnostics, adding capability to run advanced troubleshooting commands from the UI System will drop old sessions and generate events in case the session table becomes full, preventing lock-out Masking of possibly sensitive data on Diagnostic Data is now optional User is automatically logged-out of WebUI when session expires Added progress bar and improved disk space check for file downloads greater than 1MB from “Local Computer”, such as in software upgrade Any interface is now selectable on Firewall Rule UI Support for changing Docker data-root location to a different disk or partition in Security :: Services Improved “Save Settings” UI to show a list of available backups. Backups are now also accessible via

Your browser does not support PDF. Click here to download.

Nodegrid Version 5.10.7 Release November 03, 2023 Supported Products Nodegrid Manager Nodegrid Serial Console Nodegrid Bold SR Nodegrid Gate SR Nodegrid Link SR Nodegrid Net SR Nodegrid Hive SR Nodegrid Mini SR Upgrading Instructions Upgrade methods from Web Interface, CLI, USB, and Network Boot are supported. UEFI mode and Secure Boot must be disabled prior to downgrading to v5.0 or older. Upgrade from v4.x versions is only supported starting at v4.2.4. Upgrade from v3 versions is only supported for NSC devices at v3.2.54 and will erase existing data in /var directory. Software Components Information Component Filename MD5 Checksum Software ISO Nodegrid_Platform_v5.10.7_20231102.iso f7e3ddb229b4efe3fb798a93e3694ff0 Network Boot Nodegrid_NetBoot_v5.10.7_20231102.tar.gz c571a55e00826822b76fdfe882dc1622 SNMP MIB Nodegrid_MIB_v5.10.7_20231102.zip 07f94240024b4df38c8920fc40e8ece7 Security Fixes Upgraded OpenSSL to v3.0.12 (CVE-2023-5363) Upgraded curl

Upgraded Apache2 to v2.4.58 (CVE-2023-31122, CVE-2023-43622) Upgraded dnsmasq to v2.89 (CVE-2022-0934, CVE-2023-28450) Upgraded libmodbus to v3.1.10 (CVE-2022-0367) Upgraded sqlite to v3.44.2 (CVE-2023-7104) Upgraded ffmpeg v6.1 (CVE-2023-47470) Upgraded vim to v9.0.2130 (CVE-2023-5535) Patched perl v5.30.1 (CVE-2023-47100) Patched qtbase v5.15 (CVE-2023-51714) New Features and Enhancements LLDP support for bridge connections Bug Fixes Fixed LTE Modem not connecting when using Verizon SIM card Fixed creation of bridge between one ethernet interface and one VLAN over bonding connection Fixed some API queries for DHCP returning error 500 Fixed API endpoint system/toolkit/files/execute failing to execute CLI commands Fixed running a playbook via API in Central management Fixed “Interface” in VLAN connection being read-only Fixed LLDP settings being ignored

Nodegrid Gate SR supports two digital I/O ports (DIO0, DIO1), one digital output port (OUT0) and one relay port (1A@24V). Nodegrid Link SR supports two digital I/O ports (DIO0, DIO1) and two digital output ports (OUT0, OUT1). DIO0 and DIO1 can be independently configured as input or output. The DIO0 and DIO1 are open-drain digital I/O ports with TTL level (5.5V max @ 64mA). ESD protection exceeds JESD 22. When DIO port is configured as input: contact is open, senses High (1) contact is closed, senses Low (0) NOTE DIO0 and DIO1 port configuration as input is ideal for dry contact applications (door close, vibration, water, smoke sensors). When DIO port is configured as output: set to high, outputs TTL high set to low, outputs TTL low NOTE DIO0 and DIO1 port configuration as output can control low voltage/current applications. The OUT0 and OUT1

This allows enrollment of the device in ZPE Cloud. Displays this dialog. Enable Cloud Enrollment Go to System :: Toolkit . Click Cloud Enrollment icon (displays dialog) In the Cloud Enrollment  menu: Enter URL  (of the Cloud application). Enter  Customer Code. Enter Enrollment Key. Click Save . CLI Procedure On the Access table, click Console . On the CLI window, enter these parameters, then use “show” to confirm the configuration. [admin@nodegrid /]# cloud_enrollment [admin@nodegrid {toolkit}]# cancel commit enroll ls set show [admin@nodegrid {toolkit}]# set customer_code= enrollment_key= url= [admin@nodegrid {toolkit}]# set customer_code=12341234 [admin@nodegrid {toolkit}]# set enrollment_key=12341234 [admin@nodegrid {toolkit}]# set url=https://zpecloud.com [admin@nodegrid {toolkit}]# show status: Enrolled at https://zpecloud.com url = https://zpecloud.com customer_code = 12341234 enrollment_key = ******** [admin@nodegrid {toolkit}]# commit For EU region: [admin@nodegrid /]# cloud_enrollment [admin@nodegrid {toolkit}]# cancel commit enroll ls set show [admin

This section provides information on how to validate the platform certificate. Before the validation ensure that the following requirements are met: The commands on this guide are to be executed on a trusted Linux system that has these commands available: tpm2_makecredential, curl, jq, scp It assumes "nodegrid" is the hostname of the device to be attested, for example defined in /etc/hosts. "nodegrid" can be changed to the device's IP instead. An active Nodegrid API ticket is stored in the variable $ticket . This command can be used to get a ticket: # Create a Nodegrid API ticket, assuming the password is in variable $NG_ADMIN_PASSWORD ticket=$(\ curl -s -X POST \ https://nodegrid/api/v1/Session \ --insecure \ -H 'Content-Type: application/json' \ -H 'accept: application/json' \ -d '{"username": "admin", "password": "'"$NG_ADMIN_PASSWORD"'"}' | \ jq -r .session \ ) See the following sections for information about certificate validations: Validate the Platform

Administrators can configure SNMP settings here. 

The Central management allows an admin user to run Ansible Playbooks on a set of peers in the cluster. This can only be done from the Coordinator device.

(read only) This displays information in MAC settings. 

NTP reduces security risks associated with time synchronization. With authentication, there is assurance a generated response is from an expected source (rather than maliciously generated or intercepted). Authentication applies a list of agreed keys (passwords) between a server and a client. Communication between server and client is encrypted with one of the agreed keys appended to the messages. The appended key is un-encrypted to ensure it matches one of the agreed keys. Only then is action taken.  Configure Key Number Set This requires Admin privileges. Repeat the process for each key number set. Go to System :: Date and Time :: NTP Authentication . Click Add (displays dialog).  Enter Key Number  (any unsigned integer (range: 1 to 2 32  – 1). On  Hash Algorithm drop-down, select one (MD5, RMD160, SHA1, SHA256, SHA384, SHA512, SHA3-224, SHA3-256, SHA3-384, SHA3-512). Enter Password  character string (space character not allowed). Alternatively, enter a

Create an Area Chart (Configuration Example) The area chart is useful for stacking measurements for different but related entities. NOTE Become familiar with the Line Chart procedure before creating an Area Chart. Go to Dashboard :: Visualize . On the Visualize side-tab, click Create Visualization ,  Click the New Visualization dialog, click the Line icon.  Click the Area  icon. On the dialog, click logstash- *. In metrics section, click on Y-Axis icon. In Aggregation drop-down, select Sum . On Buckets menu, X-Axis, on Aggregation pop-up, select Data Histogram . In Interval drop-down, select Custom then enter value (i.e., 30s). Click Add Filter and click Add sub-buckets . On the Select buckets type menu, click Split Series .  On Sub Aggregation drop-down, select Filters . In Filter 1 , enter value. Click Add Filter . In Filter 2 , enter a search expression for the elements to visualize. (as needed) Click Add Filter and

(read only) This displays information for each IPsec tunnel connection.  To appear on the IPsec list, Monitoring must be enabled for each IPsec tunnel.

Settings are provided with individual sections on the page. Configure Nodegrid Device Preferences Go to System :: Preferences . In the Nodegrid Location menu, enter details: Enter Address Location  (a valid address for the device location). Enter  Coordinates (Lat, Lon) (if GPS is available, click Compass icon or manually enter GPS coordinates). For Help Location , if applicable, enter alternate URL location for the User Guide. ( The administrator can download the documentation from ZPE (HTML5 or PDF, as preferred) to be available for users (when Help icon is clicked.) In the Session Idle Timeout  menu (number of seconds of session inactivity until the session times out and logs the user off.) This setting applies to all telnet, SSH, HTTP, HTTPS, and Console sessions. In Timeout (seconds) , enter a value: zero  (0) – the session will never expire Enter a value greater than or equal to 90. The default unit is seconds. Once the session

Nodegrid_NetBoot_v6.0.1_20231214.tar.gz ceeb4c1c6d969ee74ac171bfebd81218 SNMP MIB Nodegrid_MIB_v6.0.1_20231214.zip 4fcbcf31e15db1efcc25031ad8ec3f28 Security Fixes Upgraded FRR to v9.1 (CVE-2023-38406, CVE-2023-41361, CVE-2023-41360, CVE-2022-37032, CVE-2023-41359, CVE-2023-3748, CVE-2023-38407, CVE-2023-47235, CVE-2023-47234, CVE-2023-41909, CVE-2023-38802, CVE-2023-41358) Upgraded OpenVPN to v2.6.8 (CVE-2023-46850) Upgraded perl to v5.38.2 and perl-cross to v1.5.2 (CVE-2023-47100) Upgraded vim to v9.0.2130 (CVE-2023-5535) Upgraded Firefox to v121.0b5 (CVE-2023-49060) Upgraded binutils to v2.41 (CVE-2023-25584, CVE-2022-44840, CVE-2022-45703, CVE-2022-47673, CVE-2022-47695, CVE-2022-47696) Fixed Issues Fixed problems resulting from incomplete installation in some Nodegrid Managers (VMs) due to network card not recognized in early installation process

This tool creates a report on the system status of the Nodegrid device. The contents help investigate the device's functionality. A series of commands output the state of the system, collect various log files, and copy the important configuration files. The output compacted file helps debug the system in case of any error or unexpected behavior. The generated file is saved at: /home/admin/logs/collection_nodegrid_XXXX-XX-XX_XX-XX-X.tar.gz  Step 1 – Initiate Diagnostic Data This runs the Diagnostic Data tool. The results are accessible in the File System or in the File Manager tool.   Go to Systems :: Toolkit . Click the Diagnostic Data icon. (Optionally) Uncheck the Apply Masking to Sensitive Information  box to not mask the sensitive information in case support needs raw data for troubleshooting.    Click Generate. The tool will run the diagnostics. When done, click Finish (returns to the Toolkit page