13. Best Practices for Discovery in RAMP

RAMP can be configured to execute device discoveries - an exercise in which RAMP Data Collector finds a device in the network (based on the device’s IP address) and attempts to log into the device using one or more standard communication protocols. A device discovery consists of:

  • one or more communication protocols and the user credentials for each communication protocol
  • a single IP address, address range or class-C address.

When configuring Discoveries, based on our experience we recommend the following:

  • Configure only those communication protocols that are known to be supported by the device
  • Where possible, avoid configuring discoveries with class-C or large IP address ranges. Instead configure smaller IP address ranges with the goal to keep the possible number of discovered devices (based on the configured IP address range) to a manageable size. The objective is to have more smaller discoveries as opposed to a few large discoveries.

The preceding recommendation is based on the premise that it is more manageable to troubleshoot a discovery with a small number of unidentified or misidentified devices, as opposed to troubleshooting a discovery containing hundreds (or worse: thousands) of unidentified or misidentified devices.

Additionally, a discovery with a large number (IE hundreds or thousands) of devices may take hours to complete. When discovering Virtual Machines (VMs), do not create discoveries with the IP address(es) of the VM(s). Instead create a discovery that RAMP Data Collector will use to contact the Host machine. RAMP Data Collector will use the hypervisor (VMware or WMI), to discover all of the VMs managed by the hypervisor.

13.1. RAMP Protocol Descriptions

IPMI (iDRAC)
  • Asset Type: Servers
  • Port: 623
  • Information: Hardware Properties
  • Credentials: Username & Password
  • Point of Contact: Individual Assets
iLO
  • Asset Type: HP Servers
  • Port: 443
  • Information: Hardware Properties
  • Credentials: Username & Password
  • Point of Contact: Individual Assets
SNMP
  • Asset Type: All
  • Port: 161, 162
  • Information: Anything contained in manufacturer MIB and RAMP device definitions.
  • Credentials: Community String (v1 & v2c), Authentication (v3)
  • Point of Contact: Individual Assets
SSH
  • Asset Type: Linux OS Servers & Network Equipment
  • Port: 22, 222, 2222
  • Information: Hardware and OS Properties
  • Credentials: Username & Password, Certificate
  • Point of Contact: Individual Assets
UCS
  • Asset Type: Cisco Blade Enclosures, Cisco Network Equipment, Cisco
  • Port: Configurable
  • Information: Everything pertaining to UCS Manager
  • Credentials: Username & Password
  • Point of Contact: UCS Manager
VMware SDK
  • Asset Type: Virtual Servers
  • Port: Configurable
  • Information: Anything pertaining to VMWare Virtual Machines
  • Credentials: Username & Password
  • Point of Contact: vCenter Host, vSphere Host
WMI
  • Asset Type: Windows OS Servers
  • Port: 135
  • Information: Windows OS Properties
  • Credentials: Windows Login
  • Point of Contact: Individual Devices
BACnet IP
  • Asset Type: Facility Equipment (UPS, PDU, RPP, CRAC, CRAH, Chiller, InRow Cooling, Generator)
  • Port: 47808
  • Information: Custom built from protocol definition. Varies per unit.
  • Credentials: None
  • Point of Contact: BACnet Controller, Each Device
  • Notes: Custom definition created within RAMP. not an auto discoverable protocol
Modbus TCP
  • Asset Type: Facility Equipment (UPS, PDU, RPP, CRAC, CRAH, Chiller, InRow Cooling, Generator)
  • Port: 502
  • Information: Custom built from protocol definition. Varies per unit.
  • Credentials: None
  • Point of Contact: Modbus Master, Modbus Gateway, or Each Device
  • Notes: Custom definition created within RAMP. not an auto discoverable protocol
Protocol Breakdown Per Device Type
  • Blade Enclosure – SNMP, UCS
  • Blade Network – SNMP, UCS, SSH
  • Blade Server – SNMP, UCS, SSH, WMI
  • Blade Storage – SNMP, UCS, SSH
  • Busway – BACnet, Modbus
  • Camera - SNMP
  • Chiller – BACnet, Modbus
  • CRAC – BACnet, Modbus
  • CRAH – BACnet, Modbus
  • Environmental Monitor - SNMP
  • Generator – BACnet, Modbus
  • InRow Cooling – BACnet, Modbus
  • Network – SNMP, SSH, UCS
  • Network Storage – SNMP, SSH
  • PDU/RPP – SNMP, BACnet, Modbus
  • Power Meter - SNMP
  • Rack PDU - SNMP
  • Rack or Tower UPS – SNMP
  • Server – SNMP, SSH (Linux OS), WMI (Windows OS), IPMI (iDRAC for Dell), iLO (HP)
  • Transfer Switch – SNMP, BACnet, Modbus
  • UPS – SNMP, BACnet, Modbus
  • Virtual Server – SNMP, VMware SDK