User Guide

Nodegrid Serial Console™

Nodegrid Services Router™

Nodegrid Gate SR™

Nodegrid Bold SR™

Nodegrid Link SR™

Nodegrid Manager™

This document supports versions 4.1.x.

U.S. Notification

WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment.

NOTE: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his/her own expense.

Canadian Notification

This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.

European Union Notification

This is a class A product. In a domestic environment, this product may cause radio interference in which case the user may be required to take adequate measures.

Japan Notification

この装置は、クラスA情報技術装置です。 この装置を 家庭環境で使用すると電波妨害を引き起こすことが あります。
この場合には使用者が適切な対策を講ずるよう要求されることがあります。VCCI - A

All other marks are the property of their respective owners. This document may contain confidential and/or proprietary information of ZPE Systems, Inc., and its receipt or possession does not convey any right to reproduce, disclose its contents, or to manufacture or sell anything that it may describe. Reproduction, disclosure, or use without specific authorization from ZPE Systems, Inc. is strictly prohibited.

©2013-2019 ZPE Systems, Inc. All rights reserved.

Table of Content

Introduction

The Nodegrid 4.1 User manual covers the Nodegrid Platform version 4.1 and the supporting units like the Nodegrid Serial Console Series, Nodegrid Services Router, Nodegrid Gate SE, Nodegrid Bold SR and Nodegrid Link SR.

Product Overview

Nodegrid Serial Console

Nodegrid Serial Console product line consolidates and manages attached devices via Serial Port Connection including servers, network routers and switches, storage, PDUs, UPSs, and any other device with a serial port.

Nodegrid Serial Console - S Series

NODEGRID SERIAL CONSOLE (S Series) is made to fit any modern and legacy mixed environment. With auto-sensing ports, you can use the S Series Console Servers within any environment whether using straight-through cables or with legacy adapters.

• Auto-Switching (Cisco or Legacy Pin-out)
• 16/32/48 Serial Ports
• Additional USB ports
• Factory Upgradable CPU and RAM
• 1U 19" Rack Standard Unit
• Single AC, Dual AC, and Dual DC

Hardware Specifications

Interfaces Front

Interfaces Back

Nodegrid Serial Console - R Series

NODEGRID SERIAL CONSOLE (R Series) is made to fit into major hardware environments like Cisco, Arista, Dell, Palo Alto Networks, and Juniper. R Series Serial Consoles are perfect for retrofits and to upgrade Rack Standards of existing builds.

• For Cisco Pin-out Devices
• 16/32/48/96 Serial Ports
• 1U 19" Rack Standard Unit
• Single AC, Dual AC , and Dual DC

Hardware Specifications

Interfaces Front

Interfaces Back

Nodegrid Serial Console - T Series

NODEGRID SERIAL CONSOLE (T Series) is made to fit into environments still utilizing legacy devices and can be a direct replacement of the legacy console server.

• For Legacy Devices
• 16/32/48/96 Serial Ports
• 1U 19" Standard Unit
• Single AC, Dual AC , and Dual DC

Hardware Specifications

Interfaces Front

Interfaces Back

Nodegrid Services Router Family

The Nodegrid Services Router is a platform appliance designed for software-defined networking (SDN), out of band (OOB) management, DevOps, cellular failover, docker, SD-WAN, remote/branch offices, retail locations, and network function virtualization (NFV) capabilities.

Nodegrid Services Router

NODEGRID SERVICES ROUTER is a modular open platform appliance designed for software-defined networking (SDN), out of band (OOB) management, DevOps, cellular failover, docker, SD-WAN, remote/branch offices, retail locations, and network function virtualization (NFV) capabilities.

• Open Framework, Modular Services Router
• Plugable Expansion Modules - 5 slots available
• Modules for GbE, Serial, SFP+ 10GbE, PoE+, USB, M.2/SATA + Antenna, Storage, Extra Compute
• 1U 19" Standard Unit
• Separation of Control Plane and Data Plane

Hardware Specifications

Interfaces Front

Interfaces Back

Nodegrid Services Router Expansion Modules

Nodegrid Services Router has up to five slots for modules that provides extreme flexibility for function expansion.

Module	Picture	Specification
16-Port 1GbE		1000BASE-T Cat5e or better
16-Port SFP 1GbE		Supports all SFP Modules
8-Port SFP+ 10GbE		Supports all SFP+ Modules
8-Port PoE+		25.5W max power per port Total max 150W PoE+ available Configurable power budget
16-Port Serial		RJ45 Serial Rolled port max 230,400 bps
16-Port USB		USB 2.0 interfaces Type A
M.2 Cellular + Antenna		For up to 2x 4G/LTE modems
M.2 SATA		For up to 2x mSATA storage modules
Storage		For 2.5" SATA (HDD/SDD) storage
Compute		Compute module (server on a card), provides independent compute capabilities.

Expansion Module Compatibility Chart

Note:

(*) The Nodegrid Services Router supports a maximum of 2 SATA drives, which can be divided into 2 Storage cards or in one M.2 SATA card

(**) The Secure Isolated Mode allows for the management of the cards as if they would be located in a normal Slot, but the network traffic is isolated from any other slot.

Nodegrid Gate SR

Nodegrid Gate SR brings agility to the network. Perfect for both the data center and branch, Nodegrid Gate SR packs tremendous power in a small form factor, resulting in a truly robust and dynamic, secure infrastructure management solution. Configure and manage Nodegrid Gate SR via the ZPE Cloud.

• Secure, fast and consistent deployments across your branches with the ZPE Cloud
• Software Defined Networking, Network Function Virtualization, Guest OS, Kubernetes, and Docker capabilities
• Minimizes MTTR, downtime and expenses with secure, centralized remote device access & control
• Increases site reliability with open industry standard hardware, and easy-to-use software
• Zero Touch Provisioning (ZTP) for fast and easy setup in remote locations
• Integrates with ZPE Cloud and ZPE Systems Nodegrid Manager vendor-neutral, unified management solution
• Direct Linux shell, HTML5 cross-device web access and command line interface
• Modern 64-bit Linux Kernel for fast security patching and widespread software availability
• Kubernetes and Docker-optimized for quick, flexible script and application integration
• Extended Automation based on actionable real-time data
• Failover to 4G/LTE modem
• Gateway and multi-routing table capability
• SSL VPN and IPsec
• DHCP server – extra IPs for your remote site or replace your current router altogether
• Firewall – built-in and turns on with a checkbox
• Secure – selectable encrypted cryptographic protocols and cipher suite levels, configuration checksum™
• Power control and monitoring – get alerts on suboptimal IT device health before malfunctions occur and solve problems automatically
• Orchestration - Puppet, Chef, Ansible, RESTful and ZPE Cloud
• Wi-Fi hotspot ready via internal card or add your AP (Access Point) via PoE+ port
• High density and flexible interfaces for greater connectivity

Hardware Specifications

Interfaces Front

Interfaces Back

Nodegrid Bold SR

Nodegrid Bold SR is an open platform appliance designed for secure access and control over remote and IoT devices at the EDGE of your network. Bold SR supports cellular failover, Network Function Virtualization (NFV) and Software Defined Networking with a focus on SD-WAN.

• 1U high, compact size, high processing power
• Ideal for Software Defined Networking
• Network Function Virtualization
• Cellular failover
• Wi-Fi hotspot & client
• Multi Interfaces

Hardware Specifications

Interfaces Front

Interfaces Back

Nodegrid Link SR

Nodegrid Link SR brings agility to the branch network, packing tremendous power in a compact design – Truly robust and dynamic, secure infrastructure management – Configure and manage Link SR via the ZPE Cloud to get your Branch / IoT / M2M / Kiosk / ATM / Remote Locations up and running quickly and easily.

• Secure, fast and consistent deployments across your branches with the ZPE Cloud
• Combines Cellular gateway and Wi-Fi Access Point (AP) with power input via PoE or Power Adapter
• Software Defined Networking, Network Function Virtualization, Guest OS, Kubernetes, and Docker capabilities
• Minimizes MTTR, downtime and expenses with secure, centralized remote device access & control
• Increases site reliability with open industry standard hardware, and easy-to-use software
• Zero Touch Provisioning (ZTP) for fast and easy setup in remote locations
• Integrates with ZPE Cloud and ZPE Systems Nodegrid Manager vendor-neutral, unified management solution
• Direct Linux shell, HTML5 cross-device web access and command line interface
• Modern 64-bit Linux Kernel for fast security patching and widespread software availability
• Kubernetes and Docker-optimized for quick, flexible script and application integration
• Extended Automation based on actionable real-time data
• Failover to 4G/LTE modem
• Linkway and multi-routing table capability
• SSL VPN and IPsec
• DHCP server – extra IPs for your remote site or replace your current router altogether
• Firewall – built-in and turns on with a checkbox
• Secure – selectable encrypted cryptographic protocols and cypher suite levels, configuration checksum™
• Power control and monitoring – get alerts on suboptimal IT device health before malfunctions occur and solve problems automatically
• Orchestration - Puppet, Chef, Ansible, RESTful and ZPE Cloud
• High density and flexible interfaces for greater connectivity

Hardware Specifications

Top

Interfaces Front

Interfaces Back

Nodegrid Manager

Nodegrid Manager provides you with a unified solution to control compute, network, storage, and smart power assets.

Hardware Requirements

Installation

Hardware Installation

Please refer to Appendix - Quick Install Guide provided along with the unit in the box for quick instructions on how to start your box.

What is in the box

Each unit is shipped with multiple accessories. The below table lists the content of the box.

Model	Mounting Brackets	Power Cables	Loop-Back Adapter	Console Adapter	Network Cable	QuickStart Guide & Safety Sheet
Nodegrid Serial Console - T Series	Yes	Yes	Legacy	Z000036	Yes	Yes
Nodegrid Serial Console - R Series - TxxR	Yes	Yes	Cisco	Z000015	Yes	Yes
Nodegrid Serial Console - S Series - TxxS	Yes	Yes	Legacy/Cisco	Z000015 Z000036	Yes	Yes
Nodegrid Services Router	Yes	Yes	Legacy/Cisco	Z000014 Z000015	Yes	Yes
Nodegrid Bold Services Router	No	External Power Supply	Legacy/Cisco	Z000014 Z000015	Yes	Yes

Installation of Modules for Nodegrid Services Router

The Nodegrid Services Router supports different modules. These need to be installed before the unit is powered up. The modules should be installed in an ESD protected environment, to avoid damage to any of the components. To install a card follow the following steps.

• Ensure that the Nodegrid Services Router is powered off
• Turn off the power supplies on the Nodegrid Services Router
• Unscrew the blanking panel which covers the slot in which the module should be installed
• Unbox the card and insert it into the appropriate slot
• Fix the card with the provided screw bolds
• The Nodegrid Services Router can now be turned on

Note: The blanking panel should be kept for later use. For thermal efficiency and safety, each unused slot needs to be covered with a blanking panel.

Note:

(*) The Nodegrid Services Router supports a maximum of 2 SATA drives, which can be divided into 2 Storage cards or in one M.2 SATA card

(**) The Secure Isolated Mode allows for the management of the cards as if they would be located in a normal Slot, but the network traffic is isolated from any other slot.

Rack Mounting

All units which are shipped with rack mounting brackets can be mounted to fit in the standard 19" rack. Two rack mounting brackets are provided in the box as outlined in Section (What is in the box). The remainder of this document will refer to "rack or cabinet" as "rack".

• Install the rack mounting brackets with provided screws (5 for each bracket) to the Nodegrid unit.

Note: Some units are actively cooled by fans, these units must be properly mounted into the rack, to ensure that the fans blow into the correct direction. The fan direction can be determined from the part number of the unit.

Model	Part Number	Cooled	Air Flow
Nodegrid Serial Console - T Series	NSC-Txx-xxxx-xxx	Passive	N/A
Nodegrid Serial Console - R Series	NSC-TxxR-xxxx-xxx	Passive	N/A
Nodegrid Serial Console - S Series	NSC-TxxS-xxxx-xxx-F	Active	Front-Back (air in)
Nodegrid Serial Console - S Series	NSC-TxxS-xxxx-xxx-B	Active	Back-Front (air out)
Nodegrid Services Router	NSR-xxxx-xxx	Active	Front-Back (air out)
Nodegrid Services Router	NSR-xxxx-xxx	Active	Back-Front (air in)
Nodegrid Bold Services Router	BSR-xx-xxxx	Passive	N/A

• Place the unit into the allocated space in the rack.
• Secure the unit by tightening the appropriate rack screws (not provided).

Network Connection

Depending on the model and version the unit will either have a minimum of 2 copper Ethernet ports or 2 SFP+ ports. Connect the desired network cables (CAT5e, CAT6, CAT6A) from your network switch port to any of the available network ports of the unit. For models with SFP+ ports install the SFP+ module before the unit is turned on and connect the appropriate cables.

Connecting power cord(s)

The Nodegrid unit includes one or multiple power supplies (AC or DC). Connect all the power supplies with appropriate cables to an available power source, like a Rack PDU. In case your unit is shipped with one power supply then no redundancy for power failure is available. unit with two power supplies provides redundancy against power failures. Both power supplies should be connected to two independent power sources.

Note - Nodegrid Services Router with PoE: On the Nodegrid Services Router with PoE support, the 2nd power supply is used to provide power for the PoE feature and can not be used to provide redundancy for a power outage.

After all the power supplies are appropriately connected to a power source turn the power supplies on.

(See Appendix - DC Power for information on the DC power supply ports).

Connecting target devices

Connecting serial target devices

Note: To avoid EMC issues use good quality network cable for all port connections.

The cabling and adapters that you may need to use between the unit serial ports and the serial devices’ console port will depend on their pinouts.

Latest serial devices such as routers, switches, and servers will have either a DB9, RJ45 or USB port as their console ports. See the manufacturer’s manual of your serial device console for the port pinout. In case of an RJ45 port console port, it will likely use the Cisco-like pinout.

See table below for cabling you need to use depending on your unit serial ports and Serial Devices’ console port.

If the serial device’s RJ45 does not have the Cisco-like pinout, or if you have any questions on connecting your serial device to the unit, please contact ZPE Systems Technical Support for assistance.

Connecting IP target devices

Note: To avoid EMC issues use good quality network cable for all port connections.

All IP based target device can be either directly connected to a network interface on a Nodegrid unit or through an existing network infrastructure. In case target devices are directly connected, standard network cables (CAT 5, CAT6, CAT6e) can be used for Ethernet connections or appropriate fiber cables can be used.

Connecting to a Nodegrid

Connection through the Console port

Use the provided CAT5e and RJ45-DB9 Z000036 adapter/cable to communicate with the Nodegrid unit. Connect one end of the CAT5e cable to the Nodegrid console port. Connect the other end to the RJ45-DB9 adapter, and then plug it to your laptop or PC's DB9 COM port (if your laptop or PC does not have DB9 COM port, use a USB-DB9 adapter (not provided)).

Have a serial application (such as xterm, TeraTerm, Putty, SecureCRT) running on your laptop/PC to open a terminal session to that COM port (see the system information about the COM port to be used) with 115200bps, 8 bits, No parity, 1 stop bit, and no flow control settings.

Connecting through ETH0

The ETH0 interface is by default configured to listen to DHCP requests. In case no DHCP Server is available, the unit will use a default IP address of 192.168.160.10. The unit can be accessed using a browser on https://[DHCP ASSIGNED IP] or on https://192.168.160.10, alternatively, can the unit be accessed with an ssh client.

Connection through Wi-Fi

The Nodegrid is pre-configured to act as a Wi-Fi hotspot in case an appropriate Wi-Fi device is connected. This can either be a built-in Wi-Fi module or a USB Wi-Fi adapter.

The Nodegrid will automatically be presenting a Wi-Fi network with the SSID Nodegrid. The default WPA Shared key is Nodegrid. The Nodegrid will not automatically provide an IP address to clients. Configure the client to have a valid IP address in the 192.168.162.1/24 range. The unit can now be accessed using a browser on https://192.168.162.1 or through ssh.

Connection through KVM Port

The Nodegrid unit can be directly configured and managed through it's KVM interfaces. Connect a Monitor with an HDMI cable to the units HDMI interface.

The Nodegrid Bold SR provides a VGA port instead of an HDMI interface.

Note: HDMI to DVI-D adapters can be used and allow the connections of a DVI-D Monitor.

Connect a USB Keyboard and Mouse to the available USB ports.

Note: The keyboard and mouse need to be supported under Linux, Windows only devices are not supported. This limitation mostly affects devices which use a USB wireless dongle.

The login prompt will be presented.

I/O Ports (GPIO)

The Nodegrid Gate SR supports two digital I/O ports (DIO0, DIO1), one digital output port (OUT0) and one relay port (1A@24V).
The Nodegrid Link SR supports two digital I/O ports (DIO0, DIO1) and two digital output port (OUT0, OUT1).

Both 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) and ESD protection exceeding JESD 22.
When DIO port is configured as an input, it will sense:

• as high or digital ‘1’ when the contact is open;
• as low or digital ‘0’ when the contact is closed.

Note: Configuring DIO0 and DIO1 ports as input are ideal for dry contact applications like door close, vibration, water, smoke sensors.

When DIO port is configured as an output, it will output:

• as TTL high, when set to high;
• as TTL low, when set to low.

Note: Configuring DIO0 and DIO1 ports as output can be used to control low voltage/current applications.

The OUT0 and OUT1 are high voltage digital output. Each port is internally attached to a Signal MOSFET. The output port is normally open (NO) and capable of supporting voltage range from 2.5V to 60V @ 500mA. When OUT port is:

• set to high, it will be enabled/active and it will pull the output OUT to ground.
• set to low, it will be disabled/inactive and it will keep the output OUT open.

Note: The OUT0 and OUT1 can be used to pull a power connected line to ground, like a relay circuit.

The RELAY port on Nodegrid Gate SR is a normally closed (NC) relay, with derated values of max 24V @ 1A. However, per RELAY's specification, it supports maximum switching power of 60W, 125VA; maximum switching voltage of 220VDC, 250VAC; maximum switching current of 2A, with restive load.
The primary function of the RELAY is to work as a Power Source Control Alarm. When the RELAY is close, it indicates that Nodegrid Gate SR is either being powered by a single power source or it does not have power at all. Therefore, if the Nodegrid Gate SR is being powered by both power input sources, when this RELAY is close, it indicates FAILURE on at least one of the power input sources.
Optionally, the RELAY function can be changed to follow software control (Open / Close), in order to control an external device. The following are the possible relay states:

• open, it will open the relay contact.
• close, it will close the relay contact.

The I/O Port configuration is under System :: I/O Ports. The status of the I/O Ports, along with other hardware information is under Tracking :: HW Monitor.

For Safety Reasons, do not exceed max voltage or current defined on each port.

Nodegrid Manager Installation

Nodegrid Manager software is installed from an ISO file. The installation procedure is a three-stage process:

• Creating a virtual machine
• Booting from the ISO file/CD in order to install the software
• Restarting and booting from the newly created virtual machine.

Minimum Requirements

• ESXi 4.1 or above
• 32 GB hard drive (connected through LSI Logic Parallel Controller)
• 4 GB memory (8GB recommended)
• 2 Network adapters (recommended E1000 adapters)

Creating a Virtual Machine - VMWare

• From the ESXi vSphere screen, click on Create a new virtual machine link
• For the virtual machine configuration, click on Create a new virtual machine and then click Next

• Choose an appropriate "Name" for your Nodegrid Manager virtual machine and select as "Guest OS family" Linux and "Guest OS version" Other Linux (64-Bit) then, click Next

• Select the data storage volume on which you wish to create for the new virtual machine, then click Next

• In the "Customize settings" screen, provide the following settings:
  CPU: 2
  Memory: 4GB
  hard disk: 32GB
  SCSI Controller:LSI Logic Parallel
  network adapters: 2 of type E1000
  click Next

Note: the values are minimum settings and should be adjusted as needed

• Click Finish to complete the configuration of the virtual machine on the ESXi server.

Installing Nodegrid Manager

To install your Nodegrid Manager software:

• Click on the Console tab from the summary screen of the virtual machine
• Turn on the power. The virtual machine will fail to boot since there is no operating system installed
• Click on the CD/DVD icon and select the location of Nodegrid Manager ISO file in your system
• Reboot the virtual machine by clicking on CTL-ALT-INSERT in the console area
• The virtual machine console server software will start with a boot prompt. At the boot prompt, you can hit ENTER or wait. The image will be decompressed and then loaded
• Once the image has booted, follow the instructions on the console. You must accept the EULA to proceed with the installation, type accept

• The installation process will copy the files into the virtual machine and automatically reboot the system in order to start Nodegrid Manager. Click ENTER to boot the image or wait for the image to boot automatically.

• After booting the image, your new copy of Nodegrid Manager will be available and ready to be configured.

Initial Network Configuration

After the Nodegrid Platform is turned on, boot messages will be displayed, and the login prompt will be displayed.

The default administrator username is admin and the default password is admin. Admin users can access the Nodegrid Platform via a console port, through the web interface (HTTPS) or CLI (SSH). Other access methods can be enabled.

The superuser is root and the default password is root. The root user has SHELL access to the Linux OS, but not to the Web Interface.

By default, Nodegrid Platform is set up with DHCP IP configuration enabled.

Note: The Nodegrid Platform will respond on ETH0 at 192.168.160.10 if your DHCP server fails or is unavailable.

Identify the current IP address

To identify the currently assigned IP address/es login to the Nodegrid Platform as an admin user and navigate to the Network Connections screen.

Identify current IP address - WebUI

• Login as admin user with the default password admin
• Navigate to Network :: Connections

Identify current IP address - CLI

• Login as admin user with the default password admin
• display the current settings with show /system/network_statistics/

Example Output:

[admin@nodegrid /]# show /settings/network_connections/
  name        status      type      interface   carrier state  ipv4 address       ipv6 address                 mac address        description
  ==========  ==========  ========  ==========  =============  =================  ===========================  =================  ===========
  BACKPLANE0  connected   ethernet  eth0        up             192.168.10.252/24  fe80::290:fbff:fe5b:72bc/64  e4:1a:2c:5b:72:bc
  ETH0        connected   ethernet  backplane0  up             192.168.29.3/24    fe80::290:fbff:fe5b:72bd/64  e4:1a:2c:5b:72:bd
  hotspot     not active  wifi                  down

Define Static IP Address

• If no DHCP server is available on your network, or you want to change from dynamic to static IP, configure the network parameters.

Note: The below examples use IPv4 for communication. IPv6 is fully supported on the Nodegrid Platform and appropriate settings are available in the same menus.

Define Static IP Address - Web UI

• Navigate to Network:: Connections
• Click on the Interface which should be configured
• Provide the desired details

• Click on Save

Define Static IP Address - CLI

• Navigate to the desired network Interface

xxxxxxxxxx
[admin@Nodegrid /]# cd settings/network_connections/ETH0/

• Configure the Network interface

xxxxxxxxxx
[admin@Nodegrid ETH0]# set ipv4_mode=static
[admin@Nodegrid ETH0]# set ipv4_address=<IP_ADDRESS> ipv4_bitmask=<BITMASK> ipv4_gateway=<GATEWAY>
[admin@Nodegrid ETH0]# commit

Example:

xxxxxxxxxx
[admin@Nodegrid /]# cd settings/network_connections/ETH0/
[admin@Nodegrid ETH0]# set ipv4_mode=static
[admin@Nodegrid ETH0]# set ipv4_address=10.0.0.10 ipv4_bitmask=24  ipv4_gateway=10.0.0.1
[admin@Nodegrid ETH0]# show
name: ETH0
type: ethernet
ethernet_interface = eth0
connect_automatically = yes
set_as_primary_connection = no
enable_lldp = no
ipv4_mode = static
ipv4_address = 10.0.0.10
ipv4_bitmask = 24
ipv4_gateway = 10.0.0.1
ipv4_dns_server =
ipv4_dns_search =
ipv6_mode = address_auto_configuration
ipv6_dns_server =
ipv6_dns_search =
[admin@Nodegrid ETH0]# commit

Follow the same steps for other interfaces as required.

Interfaces

WebUI

The Nodegrid platform can be accessed via its build in WebUI. The interface allows for full access to all target devices and configuration and management of the platform.

The Web UI supports all modern browsers with HTML5 support including mobile browsers. Regularly tested browsers include Internet Explorer 11, Edge, Chrome and Firefox.

The WebUI provides the following general structure.

Menu	Icon	Description
Access		The access menu provides easy access for all users to managed devices. It allows users with the appropriate permissions to start sessions, control power and review the device logging details
Tracking		The tracking menu provides an overview of general statistics and system information, like system utilization and serial port statistics besides others.
System		The system's menu allows administrators to perform general administrative tasks on the Nodegrid Platform, for example, Firmware updates, backups and restores and licenses
Network		The Network menu allows access and administration to all network interfaces and features
Managed Devices		Through this menu can administrators add, configure and remove devices which should be managed through the Nodegrid platform
Cluster		The Cluster menu allows administrators to administrate the Nodegrid Cluster feature
Security		The Security menu provides configuration options which control user access and general security of the Nodegrid platform
Auditing		This menu allows administrators to administrate auditing levels and locations as well as some global logging settings.
Dashboard		The Dashboard allows users and administrators to create and view dashboards and reports.
Applications		The applications' menu is only visible if a valid Virtualization license is available. With a proper license, it allows administrators to manage and control NFV's and Docker applications

CLI

The Nodegrid platform can be accessed through a CLI interface. The CLI is accessed by connecting to the platform using an ssh client or through its console port. The interface allows for access to all console target sessions and configuration and management of the platform. The CLI structure follows mostly the structure of the WebUI.

The CLI provides the following general structure.

While the CLI provides many commands and options, can the general usage of the CLI be broken down to a few basic commands from where a user or administrator can start from.

Examples

xxxxxxxxxx
[admin@nodegrid /]# ls
access/
system/
settings/
[admin@nodegrid /]# show
[admin@nodegrid /]# show /access/
  name                   status
  =====================  =========
  Device_Console_Serial  Connected
[admin@nodegrid /]# set settings/devices/ttyS2/access/ mode=on-demand
[+admin@nodegrid /]# set settings/devices/ttyS2/access/ rs-232_signal_for_device_state_detection=
CTS   DCD   None
[+admin@nodegrid /]# set settings/devices/ttyS2/access/ rs-232_signal_for_device_state_detection=DCD enable_hostname_detection=yes
[+admin@nodegrid /]# commit
[admin@nodegrid /]#

Shell

The Nodegrid platform provides direct access to the operating systems shell. This access is by default only available to the root user (directly) and admin user (from CLI). Direct shell access can be granted to users of specific groups (See Groups section). This can be useful for users which are used for system automation processes and which require direct shell access for this. The Nodegrid supports for these uses as well authorization through ssh key authorization. It is recommended to review the requirement for shell access and to limit access to it as required. Shell access is provided for advanced use cases and should be used with caution. Changes made to the configuration of the Nodegrid platform through the Shell can have a negative impact on the general workings of the platform.

Device Access

The Access page provides an overview of all available target devices. It allows users to easily connect to managed devices as well as review their current device status and search for target devices. The displayed target devices will be determent by the user's permissions as well as by the current state of Nodegrid Cluster nodes.

Device Sessions

The first view which is available to a user after login into the Web UI is the Access View. This view provides an overview of all available targets to which the user has access to. Each target will indicate its current connection status as well as the available connection types.

Connection Status is:

State	Indicator Color	Icon	Description
Connected	Green		Nodegrid can successfully connect to the target device and it is available for sessions
In-Use	Blue		The Device is currently in use
Disconnected	Orange		Nodegrid could not successfully connect to the target device and it is not available for sessions
Unknown	Grey		The connection status is unknown. This is the default state for target devices with the connection mode On-Demand or for new target devices for which the discovery process is not completed.

Device sessions can be directly be started from this location.

Device Sessions - Web UI

A user has multiple options to start a device session from the WebUI. In the Access screen, the user will directly see the available target sessions and can start a new session by just clicking on the connection button.

This will start a new window in which the target session will be established.

At the bottom of the window, the user is presented with buttons which allow the user to further control the target session and target device. The options available will depend on the connection type and device configuration.

Options	Description
	The Info option will display the current device details
	The Fullscreen will expand the window to use the full screen. The session window itself will not expand beyond its maximum size change size
	The Power Off option will perform a power off on the target devices through a connected Rack PDU or IPMI device
	The Power On option will perform a power on on the target devices through a connected Rack PDU or IPMI device
	The Reset option will perform a power cycle on the target devices through a connected Rack PDU or IPMI device
	The Power Status will display the current power status of a device as returned by a connected Rack PDU or IPMI device
	This option closes the currently active session
	The plus sign expands or minimizes the command line options at the bottom of the screen

By closing the window with the session to the target device will be closed.

Copy & Paste

Nodegrid supports Copying & Pasting text between the HTML5 graphical device session window and the desktop environment, similar to any other application.

Notice, however, that due to peculiarities of Operating Systems, the copy and paste operations require a distinct combination of keys to activate the copy and paste functions, as below.

• In Windows and Linux, use Ctrl+Ins to copy and Shift+Ins to paste.
• In Mac, use Cmd+C to copy, and Cmd+V to paste.

Highlight the text and right-click to open the menu, or use the shortcuts.

Device Sessions - CLI

The access view is available in the CLI through the access menu, a user can directly navigate to this menu with cd /access. To see the currently available targets the user can use the command show.

Example:

xxxxxxxxxx
[admin@nodegrid access]# show
  name                   status
  =====================  =========
  Device_Console_SSH     Connected
  Device_Console_Serial  InUse
  IPMI                   Connected
  RPDU                   Connected
  usbS2                  Connected

A device session can be directly started from here with the connect command. Use: connect <target name>

Example:

​x
[admin@nodegrid access]# connect Device_Console_Serial
[Enter '^Ec?' for help]
[Enter '^Ec.' to cli ]
​
login:

Note: Only console sessions or sessions which provide a text-based interface can be started from the CLI.

After a connection is established the user use the Escape sequence ^Ec or ^O to further control the session.

Note: the Escape sequences can be changed in the device settings.

The following options are available.

Power Control options are available on targets which are connected to a managed Rack PDU or provide power control through IMPI. The power menu can be started with ^O

xxxxxxxxxx
Power Menu - Device_Console_Serial
Options:
1. Exit
2. Status
3. On
4. Off
5. Cycle
​
Enter option: 

Device Information

Each device maintained by the Nodegrid platform has a multitude of device information stored in the system. This information is visible to users and fully searchable in the system. This is specifically useful when users are trying to identify specific targets.

The stored information is a combination of automatically discovered values, values which have been set during the device configuration and additional information which have been associated with a device by an administrator.

The device information can be displayed in the Access view for a specific device, by clicking on a target name in the WebUI or by navigating to the device in the CLI.

Display Device Information - Web UI

• Navigate to Access:: Table
• Click on the Target Name to display Device Details

Display Device Information - CLI

• Navigate to cd /access/
• use the show command to display the device details

xxxxxxxxxx
[admin@nodegrid /]# cd /access/
[admin@nodegrid access]# show Device_Console_Serial/
name: Device_Console_Serial
status: Connected

Device Views

The WebUI offers multiple ways to view and access target devices. By default, all users have displayed the Table view, which provides easy access to all targets. Other views are available and improve the accessibility or visualization of the current device status easier. The following views are available:

• Table View
• Tree View
• Node View
• Map View
• Image View

Each user can change the default view which will be displayed after login. For this, the user opens the preferred view and uses the Pin It button.

Note: The Table view is the only view which is available on the CLI.

Table View

The table view allows for easy access to all target device and their device sessions. It provides a table view which outlines easily the current status for each device. The view will display all devices currently connected to the unit as well as all other targets which are available through the Cluster feature.

The view supports filtering the current list by current device status and other search criteria. In order to filter by current device status Click on the device status icons in the top right-hand corner. The following example filters the devices by Connection State (Connected and In-Use)

More advanced search options are available through the Search field. See Device Search for more details.

Tree View

The Tree view displays all targets based on the physical hierarchies of the Nodegrid setup and allows starting connections for each target. It allows for easy access to targets devices based on their location, like Nodegrid name, city name, data center name, row and rack, and others. The View section offers filters, based on location and device types.

More advanced search options are available through the Search field. See Device Search for more details.

Node View

The Node View arranges all target devices around their connected Nodegrid units and makes it easy to get a complete overview of all targets and Nodegrid units in a Cluster. The View allows access to target device information and connections by clicking on the target nodes.

More advanced search options are available through the Search field. See Device Search for more details.

Map View

The Map View allows you to see the current status of your devices on a global map to get a complete overview of all targets and Nodegrid units in a Cluster. The Map View allows displaying precise location details down to a building level. The View allows accessing target device information and connections by clicking on the target nodes.

Global View

Street View

More advanced search options are available through the Search field. See Device Search for more details.

Image View

The Image View allows customers to display a custom view of there Nodegrid units and target devices and associated information. The implementation requires Professional Services implementation. Contact Customer Support [email protected] for additional information.

Search

The Nodegrid Platform provides advanced search capabilities which allow users to easily search and access the information and target devices they require.

Device Search

The Device Search is available on all Device views and provides an easy method to search and filter the Target devices in each view.

The Device Search can be accessed in the WebUI through the search field in the top left-hand corner of each view and on the CLI with the search command in the access menu. The NodeIQ™ Natural Language Search allows users to search for device property fields, including custom fields. This function works naturally with stand-alone units as well across all Nodegrid units in a Cluster configuration. The System automatically updates all the information about device changes and newly added devices and their properties in the background.

The Search filed supports the following keywords:

Note: The keywords AND, OR and NOT are case-sensitive "and", "or", "not" will be identified as search strings.

To search for standard and custom field data (including groups, such as “admin” group), IP addresses or a specific device, follow the examples below:

Example with AND

“PDU AND IPMI”

xxxxxxxxxx
[admin@nodegrid search]# search "PDU AND IPMI"
​
search: PDU AND IPMI
results: 1 result
page: 1 of 1
​
[admin@nodegrid search]# show
  name  status  action
  ====  ======  ======
  IPMI  -

Example with OR

"PDU OR IPMI"

xxxxxxxxxx
[admin@nodegrid access]# search "PDU OR IPMI"
​
search: PDU OR IPMI
results: 4 results
page: 1 of 1
​
[admin@nodegrid search]# show
  name                   status  action
  =====================  ======  ======
  IPMI                   -
  RPDU                   -
  Device_Console_SSH     -
  Device_Console_Serial  -

"PDU IPMI"

xxxxxxxxxx
[admin@nodegrid access]# search "PDU IPMI"
​
search: PDU IPMI
results: 4 results
page: 1 of 1
​
[admin@nodegrid search]# show
  name                   status  action
  =====================  ======  ======
  IPMI                   -
  RPDU                   -
  Device_Console_SSH     -
  Device_Console_Serial  -

Example with NOT

"PDU AND NOT IPMI"

xxxxxxxxxx
[admin@nodegrid search]# search "PDU AND NOT IPMI"
​
search: PDU AND NOT IPMI
results: 3 results
page: 1 of 1
​
[admin@nodegrid search]# show
  name                   status  action
  =====================  ======  ======
  RPDU                   -
  Device_Console_SSH     -
  Device_Console_Serial  -

Example with Field Name

"name:PDU"

xxxxxxxxxx
[admin@nodegrid search]# search "name:PDU"
​
search: name:PDU
results: 1 result
page: 1 of 1
​
[admin@nodegrid search]# show
  name  status  action
  ====  ======  ======
  RPDU  -

Global Search

A Global Search option is available in the WebUI. The Search field is located at the top of the screen beside the current user information and logs out option. The global search works in the same way as the Device Search and supports the same keywords. The Search is available from all screens and allows easy access to all target devices and target sessions.

Device Management (Managed Devices)

The Managed Devices Section allows users to configure, create and delete target devices. The Nodegrid Platform supports target devices which are connected through a serial, USB, or network connection. The following protocols are currently supported for network-based devices Telnet, SSH, HTTP/S, IMPI variations and SNMP.

The user has multiple options to enable or create and new target devices. They can be manually enabled/created or can be discovered.

Each managed device added in the system uses one license from the pool. Each unit is shipped with enough perpetual licenses to cover the number of physical ports and no further licenses are required to utilize the physical ports. Additional licenses can be added to a unit to allow it to manage additional devices. If licenses expire or are deleted from the system, the devices exceeding the total licenses will have their status changed to “unlicensed”. While their information will be retained in the system, the unlicensed devices will not show up in the access page preventing the user from connecting to them. Only licensed devices are listed on the access page and are available for access and management. The top right corner of the Managed Devices view shows the total licenses in the system, total in use and total available licenses. See Licenses for more details.

The Nodegrid platform supports the following managed device types.

• Console connections utilizing RS232 protocol. Supported on Nodegrid Console Server and Nodegrid Services Router family.

• Service Processor Devices using:

  • IPMI 1.5
  • IPMI 2.0
  • HP iLO
  • Oracle/SUN iLOM
  • IBM IMM
  • Dell DRAC
  • Dell iDRAC

• Console Server connections utilizing ssh protocol

• Console Server connections utilizing

  • Vertiv ACS Classic family
  • Vertiv ACS6000 family
  • Lantronix Console Server family
  • Opengear Console Server family
  • Digi Console Server family
  • Nodegrid Console Server family

• KVM (Keyboard, Video, Mouse) Switches utilizing

  • Vertiv DSR family
  • Vertiv MPU family
  • Atem Enterprise KVM family
  • Raritan KVM family
  • ZPE Systems KVM module

• Rack PDUs from

  • APC
  • CPI
  • Cyberpower
  • Baytech
  • Eaton
  • Enconnex
  • Vertiv (PM3000 and MPH2)
  • Raritan
  • Ritttal
  • Servertech

• Cisco UCS

• Netapp

• Infrabox

• Virtual Machine sessions from

  • VMWare
  • KVM

• Sensors

  • ZPE Systems Temperature and Humidity Sensor

Configuration of Managed Devices

New devices can be added to the Devices menu. The menu offers the options to:

• enable, disable, configure and reset devices connected to physical ports
• add, delete and configure devices connected through a network connection
• rename existing devices/ports
• clone existing devices
• to quickly change the connection mode to On-Demand
• To Bounce DTR signal for serial ports

To perform any of these tasks either click on the button or select first a device and then click the button in the WebUI or use the command in the CLI.

WebUI Enable Port 1 example

CLI rename port 2 example

xxxxxxxxxx
[admin@nodegrid devices]# rename ttyS2
[admin@nodegrid {devices}]# set new_name=Port2
[admin@nodegrid {devices}]# commit
​

Serial Devices

The Nodegrid Platform supports RS-232 Serial connections thought the available Serial and USB interfaces. The ports are automatically detected and displayed in the Devices menu and can directly be used. Each port needs to be enabled and configured to provide access to the target device.

Before configuring the Nodegrid port check the console port settings of the target device with the manufacturer. Most devices use settings of 9600,8,N,1, which is the default for the port

The Nodegrid Console Server S Series supports advanced auto-detection which simplify the configuration process, by automatically detecting the cable pinout (Legacy and Cisco) and connection speed.

Configure Serial Devices - WebUI

• Navigate to Managed Devices:: Devices

• Click on the port or select the port and click on Edit. Multiple Ports can be selected

• Confirm the values for:

  • Baud Rate set it to the correct speed matching the target device settings or to Auto
  • Parity possible values are: None (default), Odd, or Even
  • Flow Control possible values are: None (default), Software, Hardware
  • Data Bits possible values are: 5,6,7,8 (default)
  • Stop Bits possible values are: 1
  • RS-232 signal for device state detection possible values are: DCD (default), None, CTS
  • Mode possible values are: Enabled, On-Demand, Disabled

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details

Configure Serial Devices - CLI

• Navigate to /settings/devices

• use the edit command with the port name to change the port configuration. Multiple ports can be defined

• use the show command to display the current values

• use the set command adjust the values for:

  • baud_rate set it to the correct speed matching the target device settings or to Auto
  • parity possible values are: None (default), Odd, or Even
  • flow_control possible values are: None (default), Software, Hardware
  • data_bits possible values are: 5,6,7,8 (default)
  • stop_bits possible values are: 1
  • rs-232_signal_for_device_state_detection possible values are: DCD (default), None, CTS
  • mode possible values are: Enabled, On-Demand, Disabled

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details

• use the commit command to change the settings.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# edit ttyS2
[admin@nodegrid {devices}]# show
name: ttyS2
type: local_serial
address_location =
coordinates =
web_url =
launch_url_via_html5 = yes
baud_rate = 9600
parity = None
flow_control = None
data_bits = 8
stop_bits = 1
rs-232_signal_for_device_state_detection = DCD
enable_device_state_detection_based_in_data_flow = no
enable_hostname_detection = no
multisession = yes
read-write_multisession = no
icon = terminal.png
mode = disabled
skip_authentication_to_access_device = no
escape_sequence = ^Ec
power_control_key = ^O
show_text_information = yes
enable_ip_alias = no
enable_second_ip_alias = no
allow_ssh_protocol = yes
ssh_port =
allow_telnet_protocol = yes
telnet_port = 7002
allow_binary_socket = no
data_logging = no
[admin@nodegrid {devices}]# set mode=enabled baud_rate=Auto
[admin@nodegrid {devices}]# commit

Service Processor Devices

The Nodegrid platform supports multiple IPMI based Service Processors like IPMI 1.5, IMPI 2.0, Hewlett Packard ILO's, Oracle/SUN iLOM's, IBM IMM's, Dell DRAC and iDRAC.

In order to manage these devices, the Nodegrid requires a valid network connection to the target device. This can be through a dedicated network interface on the Nodegrid itself or through an existing network connection.

The Nodegrid supports the following features for Service Processors.

Note: Some features might not be available depending on the Service Processor capabilities.

• Serial Over LAN (SOL)
• Web Interface
• KVM sessions
• support for Virtual Media
• Power Control
• Data Logging
• Event Logging
• Power Control through Rack PDU

For console access via SOL, you must also enable BIOS console redirect and OS console redirect (typically for Linux OS) on the server.

Add Service Processor Devices - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system. For the purpose of this example, provide the following information:
• Enter the name of the server you want to add.
• Enter the IP address of the service processor. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the service processor in use. Possible values are: ipmi1.5,ipmi2.0, ilo, ilom, imm, drac, idrac6
• Enter the username and password of the service processor, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Add Service Processor Devices - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: ipmi1.5,ipmi2.0, ilo, ilom, imm, drac, idrac6
  • ip_address
  • username and password of the service processor, or select Ask During Login option if you want to provide user credentials during the login time

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=IPMI
[admin@nodegrid {devices}]# set type=ipmi_2.0
[admin@nodegrid {devices}]# set ip_address=192.168.10.11
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Devices with SSH

The Solution supports the management of target devices through SSH. The Nodegrid supports the following features for these devices:

• Console Session
• Data Logging
• Custom Commands
• Web Sessions
• Power Control through Rack PDU

Add Devices with SSH - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the server you want to add.
• Enter the IP address of the device. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the ssh or telnet in use. Possible values are: device_console
• Enter username and password of the ssh server, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Add Devices with SSH - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: device_console
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Device_Console_SSH
[admin@nodegrid {devices}]# set type=device_console
[admin@nodegrid {devices}]# set ip_address=192.168.10.252
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Console Servers

The Solution supports multiple 3rd party Console Servers from different vendors, including console servers from Avocent and Servertech. These devices can be added to the Nodegrid Platform and the system will then allow using the connected targets as if they had been directly connected to a Nodegrid appliance. Adding 3rd party Console Servers is a two-step process, in the first step the 3rd party appliance is added to the Nodegrid and in a 2nd step, all enabled ports will be added to the platform.

The Nodegrid supports the following features for these devices:

• Console Session
• Data Logging
• Custom Commands
• Web Sessions
• Power Control through Rack PDU

Add Console Servers - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the console server you want to add.
• Enter the IP address of the console server. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the console server. Possible values are: console_server_nodegrid,console_server_acs,console_server_acs6000,console_server_lantronix,console_server_opengear,console_server_digicp_
• Enter username and password of the console server, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Add Console Server Ports - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the console server port you want to add.
• Enter the IP address of the console server. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the console server. Possible values are: console_server_nodegrid,console_server_acs,console_server_acs6000,console_server_lantronix,console_server_opengear,console_server_digicp
• Enter username and password of the console server, or select Ask During Login option if you want to provide user credentials during the login time
• Select as End Point Serial Port and enter the port number
• click the Save button.

Note: Ports can be automatically detected and added see Auto Discovery Section for details

Add Console Servers - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: console_server_acs, console_server_acs6000,console_server_lantronix,console_server_opengear,console_server_digicp_
  • ip_address
  • username and password of the device or select Ask During Login option if you want to provide user credentials during the login time
  • endpoint should be defined as appliance

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Console_Server
[admin@nodegrid {devices}]# set type=console_server_acs6000
[admin@nodegrid {devices}]# set ip_address=192.168.2.151
[admin@nodegrid {devices}]# set end_point = appliance
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Add Console Server Ports - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: console_server_acs, console_server_acs6000,console_server_lantronix,console_server_opengear,console_server_digicp_
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time
  • endpoint should be defined as serial_port
  • port_number should be defined as the port number

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Note: Ports can be automatically detected and added see Auto Discovery Section for details

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Console_Server_Port_5
[admin@nodegrid {devices}]# set type=console_server_acs6000
[admin@nodegrid {devices}]# set ip_address=192.168.2.151
[admin@nodegrid {devices}]# set end_point = serial_port
[admin@nodegrid {devices}]# set port_number = 5
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

KVM Switches

The Solution supports multiple 3rd party KVM Switches from different vendors, including products from Avocent and Raritan. These devices can be added to the Nodegrid Platform and the system will then allow using the connected targets as if they had been directly connected to a Nodegrid appliance. Adding 3rd party KVM Switches is a two-step process, in the first step the 3rd party appliance is added to the Nodegrid and in a 2nd step, all enabled ports will be added to the platform.

The Nodegrid supports the following features for these devices:

• KVM Session
• Web Sessions
• Power Control through Rack PDU

Add KVM Switches - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the KVM switch you want to add.
• Enter the IP address of the KVM switch. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the KVM switch. Possible values are: kvm_dsr, kvm_mpu,kvm_aten,kvm_raritan
• Enter username and password of the KVM switch, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Add KVM Switch Ports - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the KVM switch port you want to add.
• Enter the IP address of the KVM switch. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the KVM switch. Possible values are: kvm_dsr, kvm_mpu,kvm_aten,kvm_raritan
• Enter username and password of the KVM switch, or select Ask During Login option if you want to provide user credentials during the login time
• Select as End Point KVM Port and enter the port number
• click the Save button.

Note: Ports can be automatically detected and added see Auto Discovery Section for details

Add KVM Switches - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: kvm_dsr, kvm_mpu,kvm_aten,kvm_raritan
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time
  • endpoint should be defined as appliance

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=KVM_Switch
[admin@nodegrid {devices}]# set type=kvm_aten
[admin@nodegrid {devices}]# set ip_address=192.168.2.151
[admin@nodegrid {devices}]# set end_point = appliance
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Add KVM Switch Ports - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: kvm_dsr, kvm_mpu,kvm_aten,kvm_raritan
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time
  • endpoint should be defined as serial_port
  • port_number should be defined as the port number

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Note: Ports can be automatically detected and added see Auto Discovery Section for details

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Console_Server_Port_5
[admin@nodegrid {devices}]# set type=kvm_aten
[admin@nodegrid {devices}]# set ip_address=192.168.2.151
[admin@nodegrid {devices}]# set end_point = kvm_port
[admin@nodegrid {devices}]# set port_number = 1
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Rack PDU's

The Solution supports multiple 3rd party Rack PDUs from different vendors, including products from APC, Avocent, Baytech,CPI, Cyberpower, Eaton, Enconnex, Geist, Liebert, Raritan, Rittal, and Servertech. These devices can be added to the Nodegrid Platform and the system will then allow users to connect to the Rack PDU and control the power outlets should this function be supported by the Rack PDU. Outlets can then be associated to specific target devices, which allows users to directly control the specific power outlets for this target device.

The Nodegrid supports the following features for these devices:

• Console Sessions
• Data Logging
• Custom Commands
• Web Sessions
• Power Control of outlets

Note: The Power Control feature needs to be supported by the Rack PDU. Check the manual of the Rack PDU if the feature is available on a specific model.

Rack PDUs - WebUI

• Navigate Managed Devices:: Devices
• click the Add button to add a device to the system.
• Enter the name of the Rack PDU you want to add.
• Enter the IP address of the Rack PDU. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the Rack PDU. Possible values are: pdu_apc, pdu_baytech,pdu_eaton,pdu_mph2,pdu_pm3000,pdu_cpi,pdu_raritan,pdu_geist,pdu_servertech,pdu_enconnex,pdu_cyberpower,pdu_rittal
• Enter username and password of the Rack PDU, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Note: By default will Nodegrid communicate with the Rack PDU using ssh/telnet. The reaction time of Rack PDUs using these interface is typically very slow. It is therefore recommended to use SNMP for the communication with the Rack PDU if possible.

• Navigate Managed Devices:: Devices
• Click on the Name of the newly added Rack PDU
• Navigate to the Commands menu and click on Outlets

• Change the Protocol to SNMP and click on Save

• Navigate to the Management menu and update the SNMP values to match the settings on the Rack PDU, click on Save

Note: Use SNMP details which provide read and write access. With Read-Only credentials can the Nodegrid Platform not control the power outlets.

• The Rack PDU Outlets will be automatically discovered, this process can take a few minutes, depending on the Rack PDU.

Add Rack PDU - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: pdu_apc, pdu_baytech,pdu_eaton,pdu_mph2,pdu_pm3000,pdu_cpi,pdu_raritan,pdu_geist,pdu_servertech,pdu_enconnex,pdu_cyberpower,pdu_rittal
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time
  • endpoint should be defined as appliance

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Note: By default will Nodegrid communicate with the Rack PDU using ssh/telnet. The reaction time of Rack PDUs using these interface is typically very slow. It is therefore recommended to use SNMP for the communication with the Rack PDU if possible.

• Navigate to /settings/devices/<device name>/commands/outlet
• Change the protocol to SNMP
• Navigate to /settings/devices/<device name>/management
• Enable SNMP and select the desired SNMP version and details
• Save the changes with commit

Note: Use SNMP details which provide read and write access. With Read-Only credentials can the Nodegrid Platform not control the power outlets.

• The Rack PDU Outlets will be automatically discovered, this process can take a few minutes, depending on the Rack PDU.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Rack_PDU
[admin@nodegrid {devices}]# set type=pdu_servertech
[admin@nodegrid {devices}]# set ip_address=192.168.2.39
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
[admin@nodegrid /]# cd /settings/devices/Rack_PDU/commands/outlet
[admin@nodegrid outlet]# set protocol=snmp
[admin@nodegrid outlet]# cd /settings/devices/Rack_PDU/management/
[admin@nodegrid management]# set snmp=yes
[+admin@nodegrid management]# snmp_version = v2
[+admin@nodegrid management]# snmp_commmunity = private
[+admin@nodegrid management]# commit

Cisco UCS

The Solution supports the management of Cisco UCS through there Console Ports as well as there management interfaces. The Nodegrid supports the following features for these devices:

• Console Session
• Data Logging
• Event Logging
• Power Control through Cisco UCS appliance
• Web Session
• Custom Commands

Add Cisco UCS - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the Cisco UCS Blade to be added.
• Enter the IP address of the Blade Chassis. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the appliance. Possible values are: cimc_ucs
• Enter the Chassis ID and the Blade ID which represent the blade
• Enter username and password of the Blade Chassis, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Add Cisco UCS - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name of the blade to be added
  • type, possible values are: cimc_ucs
  • ip_address of the blade chassis
  • chassis_id of the blade chassis
  • blade_id of the blade server
  • username and password of the blade chassis, or select Ask During Login option if you want to provide user credentials during the login time

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Cisco-UCS
[admin@nodegrid {devices}]# set type=cimc_ucs
[admin@nodegrid {devices}]# set ip_address=192.168.10.151
[admin@nodegrid {devices}]# set chassis_id=1 blade_id=1s
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Netapp

The Solution supports the management of Netapp appliances through there management interfaces. The Nodegrid supports the following features for these devices:

• Console Session
• Data Logging
• Event Logging
• Power Control through Netapp appliance
• Web Session
• Custom Commands
• Power Control through Rack PDU

Add Netapp - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the appliance you want to add.
• Enter the IP address of the device. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the NetApp appliance. Possible values are: netapp
• Enter username and password, or select Ask During Login option if you want to provide user credentials during the login time
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

Add Netapp - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: netapp
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Netapp
[admin@nodegrid {devices}]# set type=netapp
[admin@nodegrid {devices}]# set ip_address=192.168.10.250
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​

Infrabox

The Solution supports the Smart Access Control for Rack's solution appliances (Infrabox) from InfraSolution. The Nodegrid supports the following features for these devices:

• Door Control
• Web Session
• Power Control through Rack PDU

Note: Communication to the appliances requires SNMP to be configured on the appliances

Add Infrabox - WebUI

• Navigate Managed Devices:: Devices,
• click the Add button to add a device to the system.
• Enter the name of the appliance you want to add.
• Enter the IP address of the device. Make sure the IP address is reachable by the Nodegrid platform.
• In the Type field, select a type that matches the Infrabox appliance. Possible values are: infrabox
• Select Ask During Login and do not provide user credentials
• click the Save button.
• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

• Navigate to the Management menu and update the SNMP values to match the settings on the appliance
• click on Save

Add Infrabox - CLI

• Navigate to /settings/devices

• use the add command to create a new device

• use the set command to define the following settings

  • name
  • type, possible values are: infrabox
  • ip_address
  • username and password of the device, or select Ask During Login option if you want to provide user credentials during the login time

• save the changes with commit

• Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.

• Navigate to /settings/devices/<Device>/management/

• use the set command to define the SNMP values

  • snmp_version
  • snmp_community

• save the changes with commit

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/devices
[admin@nodegrid devices]# add
[admin@nodegrid {devices}]# set name=Infrabox
[admin@nodegrid {devices}]# set type=infrabox
[admin@nodegrid {devices}]# set ip_address=192.168.10.250
[admin@nodegrid {devices}]# set credential=ask_during_login
​
or
​
[admin@nodegrid {devices}]# set credential=set_now
[admin@nodegrid {devices}]# set username=admin password=admin
​
[admin@nodegrid {devices}]# commit
​
[admin@nodegrid outlet]# cd /settings/devices/Infrabox/management/
[admin@nodegrid management]# set snmp=yes
[+admin@nodegrid management]# snmp_version=v2
[+admin@nodegrid management]# snmp_commmunity=private
[+admin@nodegrid management]# commit
​

Virtual Machines

The solution supports the management of VMWare virtual machines as well a KVM Virtual Machines. The Nodegrid supports the following features for these devices:

• MKS Sessions (for VMWare machines only)
• Virtual Serial console session (for VMWare machines only)
• Console session (for KVM machines only)
• Power Control through the hypervisor
• Web Session to the device

The system supports connection to ESX directly or VSphere servers. In case a connection is made directly the ESX server has to support the "vCenter agent for VMware Host" feature, which can be enabled through an ESX server license. To check if the ESX server supports this feature, login to the ESX host and navigate to the License Feature section. Here are the available licenses and features listed which are supported by the host.

Note : In order to utilize the vSPC option with VMWare virtual machines the port needs to be configured on the Virtual Machine. See Appendix A: Configuring Virtual Serial Port (vSPC) on VM Servers

Add VMWare Virtual Machines - WebUI

• Define a VM Manager

  • Navigate to Managed Devices :: Auto Discovery :: VM Managers
  • Click on Add to define a new VM Manager
  • Provide the vCenter/ESXi IP or FQDN in VM Server field
  • define the Username and Password for the server
  • adjust the HTML console port if needed
  • Click on Save

​

Install VMRC - WebUI

Click on "Install VMRC" (VMware Remote Console) in Managed Devices::Auto Discovery::VM Managers to provide properly working graphical device connection and console access to virtual machines.

• Create a Device

  • Navigate to Managed Devices:: Devices
  • click the Add button to add a device to the system.
  • Enter the name of the Virtual Machine to be managed. The name has to match the name on the hypervisor
  • Optional: enter the IP address of the Virtual Machine
  • In the Type field, select a type that matches the Virtual Machine type. Possible values are: virtual_console_vmware
  • In VM Manager field select the correct hypervisor o which the machine runs
  • click the Save button.

Add VMWare Virtual Machines - CLI

• Define a VM Manager

  • Navigate to /settings/auto_discovery/vm_managers/

  • use the add command to create a VM Manager

  • use the set command to define the following settings

    • vm_server : Provide the vCenter/ESXi IP or FQDN
    • define username and password
    • adjust the html_console_port if needed

  • save the changes with commit

xxxxxxxxxx
[admin@nodegrid /]# cd /settings/auto_discovery/vm_managers/
[admin@nodegrid vm_managers]# add
[admin@nodegrid {vm_managers}]# set vm_server=vCenter
[admin@nodegrid {vm_managers}]# set username=admin
[admin@nodegrid {vm_managers}]# set password=password
[admin@nodegrid {vm_managers}]# commit
​

• Create a Device

  • Navigate to /settings/devices

  • use the add command to create a new device

  • use the set command to define the following settings

    • name
    • type, possible values are: virtual_console_vmware
    • optional, ip_address as of the target device
    • vm_manager, set to a existing VM Manager

  • save the changes with commit

  • Optional, settings which control the display and behavior of the device can be adjusted at this time. See Device Settings for more details.