ZPE Nodegrid User Manual

User Guide

Nodegrid Serial Console™

Nodegrid Services Router™

Nodegrid Bold SR™

Nodegrid Manager™

This document supports versions 4.0.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

Note: 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

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.

©2019 ZPE Systems, Inc. All rights reserved.

Table of Contents

Introduction

Product Overview

Nodegrid Serial Console

Nodegrid Serial Console - S Series

Nodegrid Serial Console - R Series

Nodegrid Serial Console - T Series

Nodegrid Services Router

Nodegrid Services Router

Nodegrid Services Router Expansion Modules

Expansion Module Compatibility Chart

Nodegrid Bold SR

Nodegrid Manager

Installation

Hardware Installation

What's in the Box?

Installation of Modules for Nodegrid Services Router

Rack Mounting

Network Connection

Connecting Power Cord(s)

Connecting Target Devices

Connecting Serial Target Devices

Connecting IP Target Devices

Connecting to a Nodegrid

Connection via Console Port

Connecting via ETH0

Connection via Wi-Fi

Connection via KVM Port

Nodegrid Manager Installation

Creating a Virtual Machine - VMWare

Installing Nodegrid Manager

Initial Network Configuration

Identify Current IP Address

Identify Current IP Address - WebUI

Identify Current IP Address - CLI

Define Static IP Address

Define Static IP Address - Web UI

Define Static IP Address - CLI

Interfaces

WebUI

CLI

Shell

API

Device Access

Device Sessions

Device Sessions - Web UI

Device Sessions - CLI

Device Information

Display Device Information - Web UI

Display Device Information - CLI

Device Views

Table View

Tree View

Node View

Map View

Image View

Search

Device Search

Global Search

Device Management (Managed Devices)

Configuration of Managed Devices

Serial Devices

Configure Serial Devices - WebUI

Configure Serial Devices - CLI

Service Processor Devices

Add Service Processor Devices - WebUI

Add Service Processor Devices - CLI

Devices with SSH

Add Devices with SSH - WebUI

Add Devices with SSH - CLI

Console Servers

Add Console Servers - WebUI

Add Console Server Ports - WebUI

Add Console Servers - CLI

Add Console Server Ports - CLI

KVM Switches

Add KVM Switches - WebUI

Add KVM Switch Ports - WebUI

Add KVM Switches - CLI

Add KVM Switch Ports - CLI

Rack PDU's

Rack PDUs - WebUI

Add Rack PDU - CLI

Cisco UCS

Add Cisco UCS - WebUI

Add Cisco UCS - CLI

Netapp

Add Netapp - WebUI

Add Netapp - CLI

Infrabox

Add Infrabox - WebUI

Add Infrabox - CLI

Virtual Machines

Add VMWare Virtual Machines - WebUI

Add VMWare Virtual Machines - CLI

Add KVM Virtual Machines - WebUI

Add KVM Virtual Machines - CLI

Auto-Discovery

Auto Discovery of Console Server and KVM Switch Ports

Auto Discovery of Console Server and KVM Switch ports - WebUI

Auto Discovery of Console Server and KVM Switch ports - CLI

Auto Discovery of Network Devices

Auto Discovery of Network Devices - WebUI

Auto Discovery of Network Devices - CLI

Auto Discovery of Virtual Machines

Auto Discovery of Virtual Machines - WebUI

Auto Discovery of Virtual Machines - CLI

Auto Discovery of DHCP Clients

Auto Discovery of DHCP Clients - Web UI

Auto Discovery of DHCP Clients - CLI

Device Settings

Hostname Detection

Configure Hostname Detection

Global Settings for Hostname Detection

Create a Probe or Match

Multi Sessions

Break Signal

Escape Sequences

Disable User Authentication

SSH / Telnet Port

Binary Socket

IP Aliases

Location

Web URL

Icon

Mode

Expiration

Device State Detection

Serial Devices

IP Devices

Run Custom Scripts on Device Status Change

Data Logging

Event Logging

Alert Strings and Custom Scripts

Custom Fields

Commands and Custom Commands

Tree View Settings

Device Types

Preferences

Power Menu Preferences

Session Preferences

Tracking

Open Sessions

Event List

System Usage

Discovery Logs

Network Statistics

Device Statistics

Scheduler

System

Licenses

System Preferences

Address Location

Session Idle Timeout

Login logo image

Login Banner

Utilization Rate

Console Port

Power Supplies

Network Boot (PXE)

Date and Time

Logging

Custom Fields

Dial-Up

System Maintenance

Shutdown and Reboot

Software Upgrade

Factory Reset

System Configuration Checksum

Load System Certificate

Network Tools

Backup and Restore

Save Settings

Restore Settings

Network

Settings

Hostname and Domain Name

Network Failover

IP Forwarding

Loopback Address

Network Connection Configuration

Bonding Interfaces

Ethernet Interfaces

Mobile Broadband GSM Interface

VLAN Interface

WIFI Interface

WIFI Access Point

WIFI Client

WIFI Settings

Bridge Interface

Analog Modem Interface

Static Routes

Manual Hostnames

DHCP Server

Network Switch Configuration

Switch Interfaces

VLAN Configuration

Untagged/Access Ports

Tagged/Trunk Ports

Backplane Ports

VPN

SSL VPN

SSL VPN Client

SSL VPN SERVER

IPSEC VPN

Authentication Methods

Pre-shared Keys

RSA Keys

X.509 Certificates

Connection Scenarios

Host to Host

Host to Site

Site to Site

Host to Multi Site

Site to Multi Site

Configuration of IPSec

Authentication

Local Accounts

Manage Local Users

Hash Format Password

Password Rules

Groups

Manage Groups

Create a User Group

Add local users to a group

Assign system permissions and settings to a group

Assign external groups

Assign device permissions

Assign power outlet permissions

External Authentication Provider

LDAP and Active Directory

TACACS +

RADIUS

Kerberos

Security

Firewall

Services

Active Services

Managed Devices

Intrusion Prevention

SSH

Web Service

Cryptographic Protocols

Cloud

Peers Overview

Cloud Settings

Enable Cloud

Automatic Enrollment

License Pool

Peer Management

Auditing Settings

Data Logging

Events

Destinations

File

Syslog

SNMP Trap

Email Notification

Monitoring

Customizing a Monitoring Template

SNMP Template

IPMI Discovery Template

Enabling Monitoring

Dashboard

Exploring Data Points

Creating a Visualization

Line Charts

Area Charts

Creating a Dashboard

Inspecting a Dashboard

Applications

Docker Applications

Docker Images

Docker Containers

Application Links

Network Function Virtualisation

Appendix

Technical Support

Submit a Support Ticket

Updates and Patches

Configuring Virtual Serial Port (vSPC) on VM Servers

DC Power

Fundamentals

Case of -48VDC supply

Case of +48VDC supply

AC Power

Serial Port Pinout

Safety

Quick Install Guide

RoHS

Data Persistency

Soft Removal

Hard Removal - Secure Erase

Credits

Introduction

The Nodegrid 4.0 User manual covers the Nodegrid Platform version 4.0 and the

supporting units like the Nodegrid Serial Console Series, Nodegrid Services Router and the

Nodegrid Bold 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

Item Description

CPU Intel x86_64 dual core 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 modules

16, 32, 48 RS-232 serial ports on RJ45 @ 230,400 bps max/port.

1 RS-232 serial console port on RJ45

1 USB 3.0 Host,1 USB 2.0 Host and 12 USB 2.0 Hosts on Type A

connector

1 HDMI

Power

Single/Dual AC 100-240 VAC, 50/60 Hz

Dual DC: 40-63 VDC

Power consumption 45 W typical

Physical

Front-Rear mounting brackets

Size (L x W x H): 443 x 312 x 43 mm (17.4 x 12.3 x 1.7 in), 1U

Weight: 4.9 kg (10.8 lb), depending on options

Front-to-Back or Back-to-Front Fans (Swappable)

Environmental

Operation: 0 to 50° C (32 to 122° F), 20-90% RH, non-cond.

Storage: -20 to 67° C (-4 to 153° F), 10-90% RH, non-cond.

Port Description

HDMI HDMI Interface

USB USB 2.0 Port

PWR Power LED

SYS System LED

RST

Reset button : <10s system reset, >10s configuration factory reset and system

reset

FAN Fan's

USB 1 x USB 2.0 Port, 12 x USB 1.1 Ports

Interfaces Front

Port Description

Power Single or Dual Power Sockets

Serial Serial Interfaces

ETH0/SFP0 Network Interface

ETH1/SFP1 Network Interface

Console Console MGMT Interface

USB 1 x USB 3.0

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 upgarde 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

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 modules

16, 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 and 2 USB 2.0 Hosts on Type A connector

1 HDMI

Power

Single/Dual AC 100-240 VAC, 50/60 Hz

Dual DC: 40-63 VDC

Power consumption 45 W (on 96 ports)

Physical

Front-Rear mounting brackets

Size (L x W x H): 443 x 312 x 43 mm (17.4 x 12.3 x 1.7 in), 1U

Weight: 4.9 kg (10.8 lb), depending on options

Environmental

Operation: 0 to 50° C (32 to 122° F), 20-90% RH, non-cond.

Storage: -20 to 67° C (-4 to 153° F), 10-90% RH, non-cond.

Port Description

HDMI HDMI Interface

USB 2 x USB 2.0 Port

PWR Power LED

SYS System LED

RST

Reset button : <10s system reset, >10s configuration factory reset and system

reset

Interfaces Front

Interfaces Back

Port Description

Power Single or Dual Power Sockets

Serial Serial Interfaces

ETH0/SFP0 Network Interface

ETH1/SFP1 Network Interface

Console Console MGMT Interface

USB USB 3.0

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

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 modules

16, 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 and 2 USB 2.0 Hosts on Type A connector

1 HDMI

Power

Single/Dual AC 100-240 VAC, 50/60 Hz

Dual DC: 40-63 VDC

Power consumption 45 W (on 96 ports)

Physical

Front-Rear mounting brackets

Size (L x W x H): 443 x 312 x 43 mm (17.4 x 12.3 x 1.7 in), 1U

Weight: 4.9 kg (10.8 lb), depending on options

Environmental

Operation: 0 to 50° C (32 to 122° F), 20-90% RH, non-cond.

Storage: -20 to 67° C (-4 to 153° F), 10-90% RH, non-cond.

Port Description

HDMI HDMI Interface

USB 2 x USB 2.0 Port

PWR Power LED

SYS System LED

RST

Reset button : <10s system reset, >10s configuration factory reset and system

reset

Interfaces Front

Interfaces Back

Port Description

Power Single or Dual Power Sockets

Serial Serial Interfaces

ETH0/SFP0 Network Interface

ETH1/SFP1 Network Interface

Console Console MGMT Interface

USB USB 3.0

Nodegrid Services Router

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

Pluggable 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

Item Description

CPU Intel Multi-core x86_64 CPU

Memory & Storage 8 GB of DDR4 DRAM, 32 GB mSATA SSD (Factory Upgradeable)

Interfaces

2 SFP+ Ethernet

2 Gigabit Ethernet

1 RS-232 serial console port on RJ45

1 USB 3.0

1 USB 2.0

1 HDMI

Power

Single/Dual AC 100-240 VAC, 50/60 Hz

Dual DC: 36-75 VDC

Power Consumption 90W typical

Physical

Front-Rear mounting brackets

Size (L x W x H): 438 x 332 x 43mm (17.2 x 13.1 x 1.7 in), 1U

Weight: 4.9 kg (10.8 lb), depending on options

Air Exhaust or Air Intake Fans (Swappable)

Environmental

Operation: 0 to 45° C (32 to 113° F), 5-95% RH, non-cond.

Storage: -20 to 67° C (-4 to 153° F), 10-90% RH, non-cond.

Interfaces Front

Port Description

Slot 1 Slot for Module

Slot 2 Slot for Module

Slot 3 Slot for Module

SFP+ 0 Network Interface

SFP+ 1 Network Interface

ETH0 Network Interface

ETH1 Network Interface

Console Console MGMT Interface

USB USB 3.0

RST

Reset button : <10s system reset, >10s configuration factory reset and

system reset

Port Description

Slot 4 Slot for Module (depending on the Model)

Slot 5 Slot for Module (depending on the Model)

USB 2 x USB 2.0 Port

HDMI HDMI Interface

PWR Power LED

SYS System LED

FAN Fan's

Power Socket Dual Power Sockets

Power Single or Dual Power Sockets

Interfaces Back

Nodegrid Services Router Expansion Modules

Module Picture Specification

16-Port

1GbE

1000BASE-T

Cat5e or better

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 upto 2x 4G/LTE

modems

M.2

SATA

For upto 2x mSATA storage

modules

Storage

For 2.5" SATA (HDD/SDD)

storage

Compute

Compute module (server

on a card), provides

independent compute

capabilities.

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

for function expansion.

Expansion Card

Slot1Slot2Slot

3

Slot4 Slot5

16-Port GbE

Ethernet

✔ ✔ ✔

Secure Isolated

Mode **

Secure Isolated

Mode **

16-Port Serial ✔ ✔ ✔ ✔ ✔

16-Port USB ✔ ✔ ✔ ✔ ✔

M.2 Cellular / Wi-

Fi

✔ ✔ ✔ ✔ ✔

8-Port SFP+ ✔ ✔ ✔

Secure Isolated

Mode **

Secure Isolated

Mode **

8-Port POE+ ✔ ✔ ✔ – –

Compute ✔ ✔ ✔

Secure Isolated

Mode **

Secure Isolated

Mode **

Storage * – – – ✔ ✔

M.2 SATA * – – – ✔ ✔

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 managment of the cards as if they would

be located in a normal Slot, but the network traffic is isolated from anyother slot.

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

Item Description

CPU Intel Multi-core x86_64 CPU

Memory &

Storage

4 GB of DDR3 DRAM, 32 GB mSATA SSD (Upgradeable)

Interfaces

1 Gigabit (10/100/1000BT) Ethernet interfaces on RJ45

4 Gigabit (10/100/1000BT) Ethernet interfaces on RJ45 with Built-in

Switch

8 RS-232 serial ports on RJ45

1 RS-232 console port on RJ45

USB 3.0 Host on Type A

2 USB 2.0 Hosts on Type A

1 Wi-Fi – optional

2 Cellular Slots with Dual SIM – Optional

1 VGA port

Power

12 VDC via external 100–240 VAC, 50/60 Hz adapter

12 VDC via external 48 VDC adapter

Power consumption 25 W typical

Physical

Front-Rear mounting brackets

Size (L x W x H): 142 x 201 x 44 mm (5.5 x 7.9 x 1.73 in)

Weight: 1.2 kg (2.6 lb)

Environmental

Operation: -20°C to 50°C (-4 to 122° F), 20-90% RH, non-cond.

Storage: -20 to 67° C (-4 to 153° F), 10-90% RH, non-cond.

Network Function Virtualization

Cellular failover

Wi-Fi hotspot & client

Multi Interfaces

Hardware Specifications

Interfaces Front

Port Description

Channel A Signal Strength indicator for Channel A

Channel B Signal Strength indicator for Channel B

Console Console MGMT Interface

PWR Power LED

SYS System LED

Power

Switch

Power Switch

RST

Reset button : <10s system reset, >10s configuration factory reset and

system reset

Port Description

PWR IN Power Socket for external Power Supply

Monitor VGA Interface

ETH0 Network Interface (WAN)

USB

2 x USB 2.0 Port

2 x USB 3.0 Port

ETH1 Network Interface (NET)

ETH2 Network Interface (NET)

ETH3 Network Interface (NET)

ETH4 Network Interface (NET)

Serial Serial Interfaces 1-8

Interfaces Back

Nodegrid Manager

Item Description

CPU min. 2 x Intel Multi-core x86_64 CPU

Memory & Storage 4 GB RAM, min 32 GB HDD

Interfaces min 1 Gigabit Ethernet interface

Supported Hypervisors VMWare ESX, Linux KVM, Oracle Virtualbox -- Linux OS

Nodegrid Manager provides you with a unified solution to control compute, network,

storage, and smart power assets.

Hardware Requirements

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

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's in the Box?

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

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

Expansion Card

Slot1Slot2Slot

3

Slot 4 Slot 5

16-Port GbE

Ethernet

✔ ✔ ✔

Secure Isolated

Mode **

Secure Isolated

Mode **

16-Port Serial ✔ ✔ ✔ ✔ ✔

16-Port USB ✔ ✔ ✔ ✔ ✔

M.2 Cellular / Wi-

Fi

✔ ✔ ✔ ✔ ✔

8-Port SFP+ ✔ ✔ ✔

Secure Isolated

Mode **

Secure Isolated

Mode **

8-Port POE+ ✔ ✔ ✔ – –

Compute ✔ ✔ ✔

Secure Isolated

Mode **

Secure Isolated

Mode **

Storage * – – – ✔ ✔

M.2 SATA * – – – ✔ ✔

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 managment of the cards as if they would

be located in a normal Slot, but the network traffic is isolated from anyother 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".

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

Install the rack mounting brackets with provided screws (5 for each bracket) to the

Nodegrid unit.

Note: Some units are actively cooled by fans, it is important these units are getting

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.

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 a 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 is likely that it will 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.

Model

Port

Type

Pinout

Device

Port -

RJ45

(Legacy)

Device Port -

RJ45 (Cisco)

Device Port -

DB9

Device

Port -

USB

Nodegrid

Serial

Console - T

Series

RJ45 Legacy

CAT5e

cable

CAT5e cable

plus Z000039

crossover

adapter

CAT5e cable

plus Z000036

crossover

adapter

USB

Nodegrid

Serial

Console - R

Series

RJ45 Cisco - CAT5e cable

CAT5e cable

plus Z000015

crossover

adapter

USB

Nodegrid

Serial

Console - S

Series

RJ45

Auto-Sensing

(Legacy/Cisco)

CAT5e

cable

CAT5e cable

CAT5e cable

plus Z000015

crossover

adapter

USB

Nodegrid

Services

Router

RJ45 Cisco - CAT5e cable

CAT5e cable

plus Z000015

crossover

adapter

USB

Nodegrid

Bold

Services

Router

RJ45 Cisco - CAT5e cable

CAT5e cable

plus Z000015

crossover

adapter

USB

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 via 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)).

Setting Value

DHCP enabled

fallback IP yes

Default IP 192.168.160.10/24

Default URL https://192.168.160.10

Default ssh ssh admin@192.168.160.10

Setting Value

SSID Nodegrid

WPA Shared key Nodegrid

Default Network 192.168.162.1/24

Default URL https://192.168.162.1

Default ssh ssh admin@192.168.162.1

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 via 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 via 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 via 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.

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 in order 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 Current IP Address

To identify the currently assigned IP address/es login to the Nodegrid Platform as 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:

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

[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 00:90:fb:5b:72:bc

ETH0 connected ethernet backplane0 up

192.168.29.3/24 fe80::290:fbff:fe5b:72bd/64 00:90:fb:5b:72:bd

hotspot not active wifi down

Click on Save

Define Static IP Address - CLI

Navigate to the desired network Interface

Configure the Network interface

Example:

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

[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

[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

Follow the same steps for other interfaces as required.

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

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 statics

beside 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

Cloud

The Cloud menu allows administrators to administrate the

Nodegrid Cloud feature

Security

The Security menu provide configuration options which controls

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 Virtualisation

license is available. With a proper license, it allows administrators

to manage and control NFV's and Docker applications

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

Folder 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

/system

The folder provides the combined functions of the Tracking and System

menu from the web UI. The tracking features provide an overview of general

statistics and system information, like system utilization and serial port statics

beside others. The system's features allow administrators to perform general

administrative tasks on the Nodegrid Platform, for example, Firmware

updates, backups and restores and licenses

/settings

The folder provides access to the system, security, auditing, and managed

devices settings and configuration options

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 a large number of 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.

CLI

Command

Description

TAB TAB

The key combination of a double TAB provides a list of all available

commands, settings or options which are currently valid

ls The ls command list the current folder structure

show

The show command when valid will display the current settings in a tabular

view

set

All changes and settings are initiated with the set command in the general

form of set option=value multiple setting can be combined by

providing additional option=value pairs, like set option1=value1

option2=value2

commit

Most changes are not directly saved and activated, changes to the

configuration can be reviewed with the show command before they get

saved and activated with the commit command. That changes are not

active yet and require to be saved is indicated in the CLI by a + sign in

front of the command promt, like: [+admin@nodegrid /]#

cancel

or

revert

In case setting should not be committed and saved, the cancel or

revert command can be used to revert the changes.

Examples

[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

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). 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.

API

The Nodegrid platform provides a RESTful API, which can be used to read and change and

Nodegrid configuration. The API documentation is embedded on Nodegrid and it is

available under System > Toolkit > API or from the pull down USER menu at the top right

corner of the main WEB page.

Note: The API documentation can be found on each Nodegrid platform under

https://<Nodegrid IP>/api_doc.html

[admin@nodegrid /]#

State

Indicator

Colour

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 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 Cloud 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:

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.

Options Description

The Text Input option allows a user to past larger text items directly into a

session.

The Clipboard options allows to for highlighted lines in the session to be

copied out by a user

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

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.

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

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:

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

connect <target name>

Example:

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.

[admin@nodegrid access]# show

name status

===================== =========

Device_Console_SSH Connected

Device_Console_Serial InUse

IPMI Connected

RPDU Connected

usbS2 Connected

[admin@nodegrid access]# connect Device_Console_Serial

[Enter '^Ec?' for help]

[Enter '^Ec.' to cli ]

login:

Option

Escape

Sequence

Description

. ^Ec. disconnect the current session

g ^Ecg displays the current user group information

l ^Ecl sends the break signal as defined in the device settings

w ^Ecw displays the currently connected users

<cr> ^Ec<cr> sends a ignore/abort command signal

k ^Eck serial port(speed data bits parity stop bits flow)

b

^Ecb

sends a broadcast message, a message can be typed after the

escape sequence sent.

i ^Eci displays the current serial port information

s ^Ecs changes the current session to read-only mode

a ^Eca changes the current session to read-write mode

f ^Ecf forces the current session to read-write mode

z ^Ecz disconnect a specific connected user session

?

^Ec?

print this message

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

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.

Power Menu - Device_Console_Serial

Options:

1. Exit

2. Status

3. On

4. Off

5. Cycle

Enter option:

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 Web UI 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

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:

Tabel 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 Cloud 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)

[admin@nodegrid /]# cd /access/

[admin@nodegrid access]# show Device_Console_Serial/

name: Device_Console_Serial

status: Connected

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 to start 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 Cloud. 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 Cloud. 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 [e-mail] 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 Cloud configuration. The System automatically updates all the

information about device changes and newly added devices and their properties in the

background.

Keyword Description

[Search

String]

a search string which represents part of or a compleat string to be searched

for

AND Combines multiple search strings with an AND

OR

Combines multiple search strings with an OR. Default search behaviour for

more than one search string

NOT Any targets matching the search string will NOT be returned

[Field

Name]

Allows limit of the Search String to a specific Field Name

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”

Example with OR

"PDU OR IPMI"

[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 -

"PDU IPMI"

Example with NOT

"PDU AND NOT IPMI"

[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 -

[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 Field Name

"name:PDU"

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.

[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 -

[admin@nodegrid search]# search "name:PDU"

search: name:PDU

results: 1 result

page: 1 of 1

[admin@nodegrid search]# show

name status action

==== ====== ======

RPDU -

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 perpertual licenses to cover the amount 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 Consol Server

and Nodegrid Services Router family.

Service Processor Devices utilising:

IPMI 1.5

IPMI 2.0

Hewleat Peckard 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 fimily

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

Baytech

Eaton

Enconnex

Vertiv (PM3000 and MPH2)

Raritan

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

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,N which is the default for the

port

The Nodegrid Console Server S Series support 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

[admin@nodegrid devices]# rename ttyS2

[admin@nodegrid {devices}]# set new_name=Port2

[admin@nodegrid {devices}]# commit

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 possiable values are: None (default), Odd, or Even

flow_control possiable values are: None (defualt), Software, Hardware

data_bits possiable values are: 5,6,7,8 (default)

stop_bits possiable values are: 1

rs-232_signal_for_device_state_detection possiable values are: DCD

(default), None, CTS

mode possiable values are: Enabled, On-Demand, Disabled

Optional, settings which controll the display and behavior of the device can be

adjusted at this time. See Device Settings for more details

use the commit command to chang the settings

[admin@nodegrid /]# cd /settings/devices

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.

[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

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 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 behaviour 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 behaviour of the device can be

adjusted at this time. See Device Settings for more details.

[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.

[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 would have

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_acs,

console_server_acs6000,console_server_lantronix,console_server_opengear,console_s

erver_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_acs,

console_server_acs6000,console_server_lantronix,console_server_opengear,console_s

erver_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 , possiable values are: console_server_acs,

console_server_acs6000,console_server_lantronix,console_server_opengear,cons

ole_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 controll the display and behavior of the device can be

adjusted at this time. See Device Settings for more details.

[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 , possiable values are: console_server_acs,

console_server_acs6000,console_server_lantronix,console_server_opengear,cons

ole_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 controll 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

[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 would have 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.

[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

[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 Avocent, Raritan, 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_raritan,pdu_servertech,pdu_en

connex

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 , possiable values are: pdu_apc,

pdu_baytech,pdu_eaton,pdu_mph2,pdu_pm3000,pdu_raritan,pdu_servertech,pd

u_enconnex

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 controll 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>/managment

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.

[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 behaviour of the device can be

adjusted at this time. See Device Settings for more details.

[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 a 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 behaviour 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 behaviour of the device can be

adjusted at this time. See Device Settings for more details.

[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 behaviour of the device can be

adjusted at this time. See Device Settings for more details.

Navigate to the Managment 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 behaviour 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

[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 abled through a 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

Create a Device

Navigate to Managed Devices:: Devices

click the Add button to add a device to the system.

Enter a name of the Virtual Mashine 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

[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 , possiable values are: virtual_console_vmware

optional, ip_address as of teh target device

vm_manager , set to a existing VM Manager

save the changes with commit

Optional, settings which controll the display and behavior of the device can be

adjusted at this time. See Device Settings for more details.

[admin@nodegrid /]# cd /settings/devices

[admin@nodegrid devices]# add

[admin@nodegrid {devices}]# set name=Virtual_Machine

[admin@nodegrid {devices}]# set type=virtual_console_vmware

[admin@nodegrid {devices}]# set ip_address=192.168.2.151

[admin@nodegrid {devices}]# set vm_manager=192.168.10.11

[admin@nodegrid {devices}]# commit

Add KVM Virtual Machines - WebUI

Create a Device

Navigate to Managed Devices:: Devices

click the Add button to add a device to the system.

Enter a name of the Virtual Machine to be managed. The name has to match the

name on the hypervisor

enter the IP address of the KVM hypervisor

provide the username and password for the KVM hypervisor

In the Type field, select a type that matches the Virtual Machine type. Possible

values are: virtual_console_kvm

click the Save button.

Add KVM Virtual Machines - CLI

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 or the virtual mashine, this has to match teh name of the machine on

teh hypervisor

type , possiable values are: virtual_console_kvm

ip_address of the KVM hypervisor

provide username and password for the KVM hypervisor

save the changes with commit

Optional, settings which controll the display and behavior of the device can be

adjusted at this time. See Device Settings for more details.

[admin@nodegrid /]# cd /settings/devices

[admin@nodegrid devices]# add

[admin@nodegrid {devices}]# set name=virtual_machine_kvm

[admin@nodegrid {devices}]# set type=virtual_console_vmware

[admin@nodegrid {devices}]# set ip_address=192.168.10.11

[admin@nodegrid {devices}]# set username=root

[admin@nodegrid {devices}]# set password=password

[admin@nodegrid {devices}]# commit

Auto-Discovery

The Nodegrid Platform is able to automatically discover and add network devices, enabled

ports on console servers, KVM switches and Virtual Serial Ports (VMWare) and Virtual

Machines (VMWare).

This feature clones discovered devices from existing devices matching their profile and

build dynamic access groups. For best results with this feature, make sure the device to be

used as a reference in the cloning process is correctly configured. Verify that username,

password and IP address are correct by accessing the device. Verify that the data logging

and event logging settings are correct by auditing the log files. Verify that events are being

detected based on data logging and event logging by simulating events and checking if

any notification was created. Verify that the device is in the desirable authorization group

with correct access rights.

The Auto Discovery follows the below general process:

Create a template device, this device will be used to clone all the settings, with the

exception of the connection details to the discovered devices. It is there for beneficial

to configure all settings as they should appear on the end devices.

Note: For each target device type a template device needs to be created.

For network devices create a Network Scan

For virtual machines create a Virtual Manager

for all devices create a Discovery Rule , this step will link the template device with

the discovery rules, which makes the decision which action will be taken with every

discovered device

Start the discovery process. This step is automatic depending on the added device

types. The Discovery Process is automatically started when an appliance is added to

the platform and can manually be started at any point from Managed Devices::

Auto Discovery:: Discover Now in the WebUI or

/settings/auto_discovery/discover_now/ from CLI

Auto Discovery of Console Server and KVM Switch Ports

The Auto Discovery process can be used to automatically add and configure managed

devices for 3rd party console server ports and KVM Switch ports. The process will discover

all enabled ports on a managed appliance. The Console Server appliance and KVM

Switches can be discovered using the Network Devices process see Auto Discovery of

Network Devices.

Auto Discovery of Console Server and KVM Switch ports - WebUI

Create Template Device

Navigate to Managed Devices:: Devices

click the Add button to add a device to the system.

Enter a name of the template you want to add

Enter 127.0.0.1 for the IP address

In the Type field, select a type that matches the console server. Possible values

are: console_server_acs,

console_server_acs6000,console_server_lantronix,console_server_opengear,cons

ole_server_digicp_

Select Ask During Login

Select as End Point as either Serial Port or KVM Port and enter the port number

Select as Mode Disabled, this will ensure that the device is not displayed in the

access page

click the Save button.

Optional, settings which control the display and behaviour of the device can be

adjusted at this time. See Device Settings for more details.

Create Discovery Rule

Navigate to Managed Devices:: Auto Discovery:: Discovery Rules

click on Add to add a new Discovery Rule

Enter a Name for the Discovery Rule

Select a Status for the discovered rule, possible values are: Enabled, Disabled

As Discovery Method select either Console Server Ports or KVM Ports

For Port List provide a list of ports which should be scanned, examples are

1,3,5,10-20

The Host or VM Identifier parameter can be used to further apply a filter if

a value is provided then part of the port name has to match the value

For Action select an action which should be performed when a new device is

discovered, possible values are: Clone (Mode:Enabled),Clone (Mode:On-

Demand),Clone (Mode:Discovered),Discard discovered Devices

In the Clone from field select the template device which was created earlier

Click on Save to create the rule

Create a Console Server or KVM Switch appliance, see Add Console Servers for more

details.

After the appliance was created the Nodegrid Platform will automatically start

discovering attached devices based on the created Discovery Rules . This process

will take a few minutes to complete.

Auto Discovery of Console Server and KVM Switch ports - CLI

Create Template 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 , possiable values are: console_server_acs,

console_server_acs6000,console_server_lantronix,console_server_opengear,

console_server_digicp_

ip_address as 127.0.0.1

set user authentication to Ask During Login

endpoint should be defined as serial_port or kvm_port

port_number should be defined as the port number

set mode to disabled

save the changes with commit

Optional, settings which controll the display and behavior of the device can be

adjusted at this time. See Device Settings for more details.

[admin@nodegrid /]# cd /settings/devices

[admin@nodegrid devices]# add

[admin@nodegrid {devices}]# set name=Console_Server_Port_Template

[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=1

[admin@nodegrid {devices}]# set credential=ask_during_login

[admin@nodegrid {devices}]# set mode=disabled

[admin@nodegrid {devices}]# commit

Create Discovery Rule

Navigate to /settings/auto_discovery/discovery_rules/

use the add command to create a Discovery Rule

use the set command to define the following settings

rule_name for the Discovery Rule

status for the discovered rule, possiable values are: enabled, disabled

method set to either console_server_ports or kvm_ports

port_list provide a list of ports which should be scanned, examples are

1,3,5,10-20

host_identifier parameter can be used to further apply a filter, if a value

is provided then part of the port name has to match the value

For action select an action which should be performed when a new device is

discovered, possiable values are: clone_mode_enabled,clone_mode_on-

demand,clone_mode_discovered,discard_device

clone_from set to the template device which was created earlier

save the changes with commit

[admin@nodegrid /]# cd /settings/auto_discovery/discovery_rules/

[admin@nodegrid discovery_rules]# add

[admin@nodegrid {discovery_rules}]# set

rule_name=Console_Server_Ports

[admin@nodegrid {discovery_rules}]# set status=enabled

[admin@nodegrid {discovery_rules}]# set method=console_server_ports

[admin@nodegrid {discovery_rules}]# set port_list=1-48

[admin@nodegrid {discovery_rules}]# set action=clone_mode_enabled

[admin@nodegrid {discovery_rules}]# set

clone_from=Console_Server_Ports_Template

[admin@nodegrid {discovery_rules}]# commit

Create a Console Server or KVM Switch appliance, see Add Console Servers for more

details.

After the appliance was created the Nodegrid Platform will automatically start

discovering attached devices based on the created Discovery Rules . This process

will take a few minutes to complete.

Auto Discovery of Network Devices

Network appliances can be automatically discovered and added to the Nodegrid Platform.

This includes appliances which support Telnet, SSH, ICMP, Console Servers, KVM Switches or

IMPI protocols besides others. Appliances can be discovered through 3 separate method's,

which can be combined or used independently:

Similar Devices (select one of the devices from the drop-down menu),

Port Scan and enter a list of ports in the Port List field,

Ping

Auto Discovery of Network Devices - WebUI

Create Template Device

Navigate to Managed Devices:: Devices

click the Add button to add a device to the system.

Enter a name of the template you want to add

Enter 127.0.0.1 for the IP address

In the Type field, select a type that matches the console server. Possible values

are: device_console,

ilo,imm,drac,idrac6,ipmi1.5,impi2.0,ilom,cimc_ucs,netapp,infrabox,pdu*

Enter username and password , or select Ask During Login option if you

want to provide user credentials during the login time

Select as Mode Disabled, this will ensure that the device is not displayed in the

access page

click the Save button.

Optional, settings which control the display and behaviour of the device can be

adjusted at this time. See Device Settings for more details.

Create a Network Scan

Navigate to Managed Devices:: Auto Discovery:: Network_Scan

click on Add to create a new Network Scan

Enter a name for Scan ID

Define an IP Range to be scanned with IP Range Start and IP Range End

Select and define one or more of the three scan methods:

for Similar Devices select an existing template which will be used to

identify devices

for Port Scan define a list of porta which should be reachable on the

device

for ping no further settings are required

Enable Scanning to enable the rule and define a Scan Interval which can

range in minutes

Create Discovery Rule

Navigate to Managed Devices:: Auto Discovery:: Discovery Rules

click on Add to add a new Discovery Rule

Enter a Name for the Discovery Rule

Select a Status for the discovered rule, possible values are: Enabled, Disabled

As Discovery Method select Network Scan

For Scan ID select the Network Scan ID which was created

The Host or VM Identifier parameter can be used to further apply a filter if

a value is provided then part of the port name has to match the value

For Action select an action which should be performed when a new device is

discovered, possible values are: Clone (Mode:Enabled),Clone (Mode:On-

Demand),Clone (Mode:Discovered),Discard discovered Devices

In the Clone from field select the template device which was created earlier

Click on Save to create the rule

the Nodegrid Platform will automatically start discovering devices based on the

created Discovery Rules . This process will take a few minutes to complete.

Auto Discovery of Network Devices - CLI

Create Template 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 , possiable values are: device_console,

ilo,imm,drac,idrac6,ipmi1.5,impi2.0,ilom,cimc_ucs,netapp,infrabox,pdu*

ip_address as 127.0.0.1

set username and password , or select Ask During Login option if you

want to provide user credentials during the login time

set mode to disabled

save the changes with commit

Optional, settings which controll the display and behavior of the device can be

adjusted at this time. See Device Settings for more details.

[admin@nodegrid /]# cd /settings/devices

[admin@nodegrid devices]# add

[admin@nodegrid {devices}]# set name=Network_Template

[admin@nodegrid {devices}]# set type=device_console

[admin@nodegrid {devices}]# set ip_address=127.0.0.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}]# set mode=disabled

[admin@nodegrid {devices}]# commit

Create a Network Scan

Navigate to /settings/auto_discovery/network_scan/

use the add command to create a Network Scan

use the set command to define the following settings

scan_id enter a name for the Network Scan

define a Network range which should be scanned with ip_range_start

and ip_range_end

set enable_scanning to yes to enable the scan

define one or more of the three scan methods:

to use similar_devices set device to match one of the existing

devices or templates

to use port_scan set port_list to a list of ports which should be

reachable on the device

to use ping no further settings are required

set scan_interval which can range in minutes

[admin@nodegrid /]# cd /settings/auto_discovery/network_scan/

[admin@nodegrid network_scan]# add

[+admin@nodegrid {network_scan}]# set scan_id=SSH_Console

[+admin@nodegrid {network_scan}]# set ip_range_start=192.168.10.1

[+admin@nodegrid {network_scan}]# set ip_range_end=192.168.10.254

[+admin@nodegrid {network_scan}]# set enable_scanning=yes

[+admin@nodegrid {network_scan}]# set similar_devices=yes

[+admin@nodegrid {network_scan}]# set device= network_template

[+admin@nodegrid {network_scan}]# set port_scan=yes

[+admin@nodegrid {network_scan}]# set port_list=22

[+admin@nodegrid {network_scan}]# set ping=no

[+admin@nodegrid {network_scan}]# set scan_interval=100

[+admin@nodegrid {network_scan}]# commit

Create Discovery Rule

Navigate to /settings/auto_discovery/discovery_rules/

use the add command to create a Discovery Rule

use the set command to define the following settings

rule_name for the Discovery Rule

status for the discovered rule, possible values are: enabled, disabled

method set to network_scan

scan_id select a Network Scan ID which was created earlier

host_identifier parameter can be used to further apply a filter if a value

is provided then part of the port name has to match the value

For action select an action which should be performed when a new device is

discovered, possible values are: clone_mode_enabled,clone_mode_on-

demand,clone_mode_discovered,discard_device

clone_from set to the template device which was created earlier

save the changes with commit

[admin@nodegrid /]# cd /settings/auto_discovery/discovery_rules/

[admin@nodegrid discovery_rules]# add

[admin@nodegrid {discovery_rules}]# set rule_name=Network_Scan

[admin@nodegrid {discovery_rules}]# set status=enabled

[admin@nodegrid {discovery_rules}]# set method=network_scan

[admin@nodegrid {discovery_rules}]# set scan_id=SSH_Console

[admin@nodegrid {discovery_rules}]# set action=clone_mode_enabled

[admin@nodegrid {discovery_rules}]# set clone_from=Network_Template

[admin@nodegrid {discovery_rules}]# commit

The Nodegrid Platform will automatically start discovering devices based on the

created Discovery Rules . This process will take a few minutes to complete.

Auto Discovery of Virtual Machines

Virtual Machines which are managed by VMWare VCenter or run on ESXi can be discovered

and managed. The process will regularly scan VCenter or the ESXi host and detect newly

added Virtual Machines. The virtual machines can either be added as type

virtual_console_vmware or virtual_serial_port. See Appendix A: Configuring Virtual Serial

Port (vSPC) on VM Servers

Note: ESXi free version is not supported.

Auto Discovery of Virtual Machines - WebUI

Create Template Device

Navigate to Managed Devices:: Devices

click the Add button to add a device to the system.

Enter a name of the template you want to add

Enter 127.0.0.1 for the IP address

In the Type field, select a type that matches the Virtual Machine type. Possible

values are: virtual_console_vmware

Enter username and password , or select Ask During Login option if you

want to provide user credentials during the login time

Select as Mode Disabled, this will ensure that the device is not displayed in the

access page

click the Save button.

Optional, settings which control the display and behaviour of the device can be

adjusted at this time. See Device Settings for more details.

Create Discovery Rule

Navigate to Managed Devices:: Auto Discovery:: Discovery Rules

click on Add to add a new Discovery Rule

Enter a Name for the Discovery Rule

Select a Status for the discovered rule, possible values are: Enabled, Disabled

As Discovery Method select VM Manager

Optional use the fields Datacenter and Cluster to filter the scan to these

specific entries

The Host or VM Identifier parameter can be used to further apply a filter if