Manage Devices

Add Device

1. Go to Managed Devices :: Devices.

2. Click Add (displays dialog). 

   

3. Enter Name.

4. In the Type drop-down, select one.

   • Service Processor devices (ilo, imm, drac, drac6, idrac7, ilom, ipmi_1.5, ipmi_2.0, intel_bmc, openbmc)
     IP Address (reachable by the Nodegrid Platform)

   • Switch devices (switch_edgecore)
     IP Address (reachable by the Nodegrid Platform)

   • Infrabox devices (infrabox)
     IP Address (reachable by the Nodegrid Platform)

   • Netapp devices (netapp)
     IP Address (reachable by the Nodegrid Platform)

   • Cisco UCS Blade devices (cimc_ucs)
     IP Address (reachable by the Nodegrid Platform)
     ChassisID

     Blade ID

   • Virtual Console KVM devices (virtual_console_kvm)
     IP Address (reachable by the Nodegrid Platform)
     Port

   • Console Server devices (console_server_nodegrid, console_server_acs, console_server_acs6000, console_server_lantronix, console_server_opengear, console_server_digicp, console_server_raritan, console_server_perle)
     IP Address (reachable by the Nodegrid Platform)
     Port

   • PDU devices (pdu_apc, pdu_baytech, pdu_digital_logger, pdu_eaton, pdu_mph2, pdu_pm3000, pdu_cpi, pdu_raritan, pdu_geist, pdu_servertech, pdu_enconnex, pdu_cyberpower, pdu_rittal, pdu_hpe_g2)
     IP Address (reachable by the Nodegrid Platform)

   • KVM Virtual Machine devices (virtual_console_kvm)
     Name (must match the hypervisor name)
     IP Address (reachable by the Nodegrid Platform)

   • KVM devices (kvm_dsr, kvm_mpu, kvm_aten, kvm_raritan)
     IP Address (reachable by the Nodegrid Platform)

5. Address Location (a valid address for the device location).
   Coordinates (Lat, Lon) (if GPS is available, click Compass icon) or manually enter GPS coordinates.

6. Web URL
   Launch URL via HTML5 checkbox (expands options). In Method menu, select one: 

   

   Internet Browser radio button
   Browser Extension Forwarder radio button (read note) 

   

7. Username
   In the Credential menu, select one:
   Set Now radio button. Enter the Password and Confirm the Password.

   Ask During Login radio button (user credentials are entered during login).

8. Select checkboxes, as needed:

   1. Allow Pre-shared SSH Key checkbox.

   2. Enable device state detection based on network traffic (icmp) checkbox

   3. Enable Hostname Detection checkbox

   4. Multisession checkbox

   5. Read-Write Multisession checkbox

   6. Enable Send Break checkbox

9. Select Icon. On the pop-up dialog, select an icon. 

   

10. Mode drop-down, select one (Enabled, On-demand, Disabled).

11. On the Expiration menu, select one:

    1. Mode drop-down, select one (Enabled, On-demand, Disabled).

    2. Expiration menu, select one:

       1. Never radio button

       2. Date radio button. Enter Date (YYYY-MM-DD)

       3. Days radio button. Enter Duration.

12. On Type drop-down:

    1. If openbmc is selected, the FRU menu displays (below the Expiration menu). 

       

       NOTE

       The OpenBMC platform contains various Field Replaceable Units (FRUs) like Side Plane Board (spb), OCP Mezzanine Card, and four 1S server boards.

    2. In the FRU menu, select one:
       Side Plane Board radio button
       Server Board radio button (expands dialog). For Slot Number, specify which 1 of 4 1S server boards to control.

    3. If console_server_xxx is selected, the Endpoint menu displays (below the Expiration menu).

       NOTE

       Depending on the selection of the console server, the Expiration and End Point radio button selections can change.

       From the End Point menu, select one:
       Appliance radio button, enter Port Number

       Serial Port radio button, enter Port Number

       USB Port radio button (if available), enter Port Number

       KVM Port radio button, enter Port Number

13. In the End Point menu, select one (not available for service processors, virtual consoles);

    1. Appliance radio button, enter Port Number

    2. Serial Port radio button, enter Port Number

    3. USB Port radio button (if available), enter Port Number

    4. KVM Port radio button, enter Port Number

14. In the Inbound Access menu:

    1. Skip Authentication to access device (NONE authentication) checkbox (if unselected, enter the following details).
       Escape Sequence (prefix for Console commands – i.e., “^Ec.” to close Console)

       Power Control Key (Power Control menu for the device displays)

    2. Show Text Information checkbox

    3.  Enable IP Alias checkbox (expands dialog) IP Address

       Interface drop-down, select one (eth0, eth1, loopback, loopback1)

       Browser Action drop-down, select one (console, web)

    4. Allow Telnet Protocol checkbox, enter TCP Socket Port

    5. Allow Binary Socket checkbox, enter TCP Socket Port

    6. (optional) Enable Second IP Alias checkbox
       IP Address

       Interface drop-down, select one (eth0, eth1, loopback, loopback1)

       Browser Action drop-down, select one (console, web)

    7. Allow Telnet Protocol checkbox, enter, enter TCP Socket Port

    8. Allow Binary Socket checkbox, enter TCP Socket Port

    9. Allow SSH protocol checkbox, enter SSH Port

    10. At this location: 

        

        Allow Telnet Protocol. checkbox, enter TCP Socket Port

        Allow Binary Socket checkbox, enter TCP Socket Port

15. Click Save.

CLI Procedure

1. Go to /settings/devices.

2. Use the add command to create a new device.

3. Use the set command to define the following settings, and save the changes with commit.

   [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

Configure Rack PDU

This process requires two steps:

• Add the PDU device. See Add Device.

• Configure the PDU with the procedure below.

1. Go to Managed Devices :: Devices.

2. Locate and click the Name of the newly added Rack PDU.

3. On the Commands tab, Command column, click Outlets.

   

4. On the Outlet dialog, Protocol drop-down, select SNMP.

   

5. Click Save.

6. On the Management tab, in the SNMP menu, update values to match the Rack PDU settings (see manufacturer’s manual).

7. This will modify the default settings, enabling the "private" community to handle both read and write operations.
   

   NOTE:
   When you select the type as PDU HPE G2, by default, the HPE G2 PDU is set up with the public community for read-only access and the private community for write-only access. This setup means the private community can't be used for reading and writing. To fix this, you may need to change the PDU's configuration to allow the private community to have both read and write access. Here's how you do it:

   1. Log in to the PDU's management interface.

   2. Go to the SNMP settings.

   3. Change the "private" community permissions to allow both reading and writing.

   4. Save the configuration.

8. Click Save.

   NOTE

   Use SNMP settings to provide read and write access. Read-only credentials can not control power outlets.

The Rack PDU Outlets are automatically discovered (may need a few minutes, depending on the Rack PDU).

CLI Procedure

1. Go to /settings/devices/<device name>/commands/outlet.

2. Change the protocol to SNMP.

3. Go to /settings/devices/<device name>/management.

4. Enable SNMP and select the desired SNMP version and details.

5. Save the changes with commit.

   NOTE

   Use SNMP settings to provide read and write access. Read-Only credentials can not control power outlets.

The Rack PDU Outlets are automatically discovered (may need 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

Edit Device

1. Go to Managed Devices :: Devices.

2. In the Name column, locate device and select checkbox.

3. Click Edit (displays dialog).

   NOTE

   If the device type is USB OCP, this additional field displays. Modify OCP Command Key as needed. (available in v5.8+)

   

4. Make changes, as needed.

5. Click Save.

Delete Device

1. Go to Managed Devices :: Devices.

2. In the Name column, locate the device and select the checkbox.

3. Click Delete.

4. On the Confirmation dialog, click OK.

Managing devices individually

1. Go to Managed Devices :: Devices. All the devices are listed on this page.

2. Click the link to any device.
   

   

3.  You can update any device configuration. For example, rename a device by overwriting a new name in the Name field.
   

4. Once you make changes the Save button becomes active. Click Save to save the changes.

5. The Return button takes you back to the Devices tab page where all the devices are listed. 

6. Click Info, and the user is directed to Access :: Table  to view the device description and additionally perform the actions as described in the TableTab section.

Launching the Local Application field

The Console drop-down list is visible only when you enable the Launch Local Application for the selected device. You can select the Launch Local Application option when you want to launch the local ssh or telnet instead of opening a new browser tab to handle the connection.
To enable the Console option and Launch Local Application, perform the following actions :

1. Go to Managed Devices> Devices, and select the required device from the list.

2. Go to the Commands tab.

3. Select the Launch Local Application field.

4. Click Save.

    

Rename Device

1. Go to Managed Devices :: Devices.

2. In the Name column, locate the device and select the checkbox.

3. Click Rename (displays dialog). Enter New Name. 

   

4. Click Save.

Clone Device

1. Go to Managed Devices :: Devices.

2. In the Name column, locate the device and select the checkbox.

3. Click Clone (displays dialog). 

   

4. Enter Name.

5. In Copy configuration to Local Serial Devices section:
   Select from the left-side panel, click Add► to move to the right-side panel.
   To remove from the right-side panel, select, and click ◄Remove.

6. Click Save.

Enable Device

1. Go to Managed Devices :: Devices.

2. In the Name column, locate the device and select the checkbox.

3. Click Enable.

Disable Device

1. Go to Managed Devices :: Devices.

2. In the Name column, locate device and select checkbox.

3. Click Disable.

Set Device to On-Demand

1. Go to Managed Devices :: Devices.

2. In the Name column, locate device and select checkbox.

3. Click On-Demand.

Set Device as Default

1. Go to Managed Devices :: Devices.

2. In the Name column, locate device and select checkbox.

3. Click Default.

Run Bounce DTR

This puts the DTR and RTS pins DOWN – waits 500ms, then put those pins UP.

1. Go to Managed Devices :: Devices.

2. In the Name column, locate device and select checkbox.

3. Click Bounce DTR.

Configure Chatsworth (CPI) eConnect PDU 

(available in v5.6+)

This unit must be physically connected to a serial port or USB port of a Nodegrid device. This PDU can merge IT devices to PDU outlets for more intuitive power control. Console access is included. Activities are recorded on the serial data log. Features include Outlet Auto Discovery and Outlet Control (Power On, Off, Cycle, Status).

1. Go to Managed Devices :: Devices.

2. Click on the serial device the PDU is connected.

   1. On Type drop-down, select pdu_cpi_serial

   2. Enter Username.

   3. Enter Password and Confirm Password

   4. (as needed) Review and adjust serial configuration details (Baud Rate, Parity, etc.)

3. Click Save.

Auto Discovery

Auto-Discovery automatically detects the CPI PDU. The CPI PDU details are available in device's Outlets sub-tab.

1. Go to Auto-Discovery :: Discover Now.

2. Select PDU serial device name checkbox.

3. Click Discover Now.

4. To confirm, go to Access :: Table.

5. Click on the PDU serial device name and check the Discovered Outlets in the table.

Merged Outlets

To see merged outlets.

1. Go to Managed Devices :: Devices :: <device name> :: Commands.

2. Review Merged panel details (this example shows eConnect PDU attached with two devices).