- Hyperview
- Quickstart
- Asset Management
- Product Catalog Management
- Discoveries
- Supported protocols
- What kind of data is collected?
- Setting up Data Collectors
- Adding or deleting discoveries
- Configuring discoveries
- Running discoveries
- Reviewing discovery reports
- Maintaining Data Collectors
- Best practices
- Settings
- Search Features
- Extracting Data
- Licensed Features
- AssetTracker
- Document Management
- Firmware Management
- Rack Security
- User Accounts
- Release Notes
- Hyperview 3.5 (May 3 2022)
- Hyperview 3.4 (April 6 2022)
- Product catalog management
- New licensed feature: Firmware Management
- Linux Data Collector enhancements
- New bulk actions: Update Access Policy, Update Model
- New Delta-T and average temperature sensors for racks
- Miscellaneous improvements
- API changes
- Deprecations
- New AvailableFirmwareVersions endpoint (licensed feature)
- New Bulk endpoints
- New FirmwareDownload endpoints (licensed feature)
- New FirmwareVersions endpoints (licensed feature)
- New Manufacturers endpoints
- New PduBreakers endpoint
- New ProductProperties endpoints
- New ProductPropertyKeys endpoint
- New Products endpoints
- New UserProductImages endpoints
- Notable bug fixes
- Known issues
- Hyperview 3.3 (January 17 2022)
- Hyperview 3.2 (November 18 2021)
- Hyperview 3.1 (September 17 2021)
- New bulk actions
- Heat map and environmental sensor visualizations
- New computed sensors
- New Network Components page for assets
- New asset type and asset property
- Sensor graph improvements
- Advanced Search improvements
- Miscellaneous improvements
- API changes
- Notable bug fixes
- Known issues
- Changes in version 3.1.1
- Changes in version 3.1.2
- Changes in version 3.1.3
- Changes in version 3.1.4
- Hyperview 3.0 (August 24 2021)
- Hyperview 2.6 (July 26 2021)
- Hyperview 2.5 (July 14 2021)
- Hyperview 2.4 (June 18 2021)
- Hyperview 2.3 (May 21 2021)
- Hyperview 2.2 (April 28 2021)
- Hyperview 2.1 (March 16 2021)
- Hyperview 2.0 (February 25 2021)
- Hyperview 1.6 (February 01 2021)
- Hyperview 1.5 (December 22 2020)
- Hyperview 1.4 (November 27 2020)
- Hyperview 1.3 (October 21 2020)
- Hyperview 1.2 (August 31 2020)
- Watched assets
- PDU breaker decorations
- New Assets By Location view
- New Assets by Type view and related changes
- Control credentials for rack PDUs
- Reachability monitoring
- Layout enhancements
- Discovery enhancements
- Rack Security enhancements (licensed feature)
- Other notable improvements
- API changes
- Known issues
- Notable bug fixes
- Changes in version 1.2.1
- Changes in version 1.2.2
- Changes in version 1.2.3
- Hyperview 1.1 (July 17 2020)
- Hyperview 1.0 (May 28 2020)
- RAMP3
- Release Notes
- RAMP Version 3.16
- RAMP Version 3.15
- RAMP Version 3.14
- RAMP Version 3.13
- RAMP Version 3.12
- RAMP Version 3.11
- RAMP Version 3.10
- RAMP Version 3.9
- RAMP Version 3.8
- RAMP Version 3.7
- RAMP Version 3.6
- RAMP Version 3.5
- RAMP Version 3.4
- Installation Guide
- Upgrade Guide
- User Guide
- Introduction
- Typical RAMP DCIM Deployment Scenarios
- Launching RAMP DCIM
- Application Menu
- Status
- Search
- Logs & Reports
- Action Menu
- Asset Information
- Software
- Operating Systems
- Retired Assets
- Adding Devices
- Add New
- Bulk Load
- Discoveries
- Tasks & Workflows
- Tasks
- Workflows
- Workflow Templates
- Planned Moves
- Notifications
- All Notifications
- Notification Methods
- Users
- Users
- Active Directory Groups
- Models
- Manage Documents
- Contracts
- End of Life
- BACnet Definitions
- Modbus Definitions
- Modbus Slave Mappings
- License Keys
- Locale and Units Settings
- Global Settings
- Asset Vue Settings
- RAMP Services Status
- Help
- Background jobs
- Tools
- Logout
- Visual Navigation Control
- Tree Navigation Control
- Performing a Tree Search
- Dragging and Dropping Using the Tree Control
- Device Types
- Blade Enclosure
- Blade Server
- Camera
- Environmental Monitor
- Expansion Module
- Generator
- In Row Cooling
- Network
- Other Devices
- Patch Panel
- PDU/RPP
- Rack
- Rack PDU
- Rack / Tower UPS
- Server
- Transfer Switch
- Undefined
- UPS
- Utility
- Virtual Server
- Logical Groups
- Tab Navigation
- Asset Views
- Cloud Support
- Location View
- Using AssetTracker
- Contacting Technical Support
- Appendix 1: Setting Up Monitoring for VMware
- Appendix 2: Email Configuration
- FAQ
- 1. Data Collector Configuration Fails with Unable to Register Error
- 2. Manager Configuration fails with Domain Authentication Error
- 3. Manager Configuration fails with IIS 7 Error
- 4. Manager Configuration fails with SQL Authentication Error
- 5. Data Collector process freezes at startup
- 6. Login issue for users authenticating using Windows AD
- 7. Requirements for Discovering Linux, FreeBSD and Windows Instances (Physical, virtual and cloud)
- 8. Managing Your Asset Limit
- 9. Report Device Count to Hyperview
- 10. RAMP licensing
- 10.1. What are the different types of licenses and how do they behave?
- 10.2. What does RAMP report?
- 10.3. Which assets are billable and which assets are not?
- 10.4. What URL does RAMP communicate with to send billing reports?
- 10.5. How often does RAMP report back home?
- 10.6. What happens when the number of assets change midterm?
- 11. Data Collector is Unable to Register URL
- 12. RAMP Device Types
- 13. Best Practices for Discovery in RAMP
- 14. End of Life and Support Policy
- Videos
- Integrations
- Release Notes
7. Requirements for Discovering Linux, FreeBSD and Windows Instances (Physical, virtual and cloud)¶
7.1. Linux¶
Please ensure the following packages are installed on your machines
Dmidecode
ifconfig (For RAMP versions less than or equal to 3.14)
ssh server
sudo
ip
Ensure that the ssh instances is configured properly, started and is allowing connections from the RAMP Data Collector.
To allow the RAMP Data Collector to accurately retrieve data with minimal impact on your system, please create a new user on your machines with the username ‘ramp’.
Once created, please assign ‘/bin/bash’ as the default shell for the ‘ramp’ user.
In order to gather certain hardware information such as the device’s serial-number, the RAMP Data Collector will need to temporarily gain root privileges.
The file below will allow the ramp user to temporarily gain root privileges when running specific commands.
Add the following 2 lines to /etc/sudoers.d/ramp
# Allow Data Collector to execute dmidecode without needing password
ramp ALL=(ALL) NOPASSWD: /usr/sbin/dmidecode
If you have a large number of instances that will be discovered and monitored by RAMP, you may want to consider using an automation tool such as Ansible or Puppet to make these additions.
Note that for virtual and cloud Linux instances some hardware information will not be collected due to the virtual nature of the asset.
Expected missing data for Virtual and Cloud Linux instances
Service Pack
Memory Speed: Memory Name may or may not be found depending on the hypervisor used
Logical Storage Status
Cloud instances will not display information about physical storage
7.2. FreeBSD¶
Please ensure the following packages are installed or enabled on your machines
Dmidecode
ifconfig (For RAMP versions less than or equal to 3.14)
ssh server
sudo
gawk
gsed
Ensure that the ssh instances is configured properly, started and is allowing connections from the RAMP Data Collector.
To allow the RAMP Data Collector to accurately retrieve data with minimal impact on your system, please create a new user on your machines with the username ‘ramp’.
Once created, please assign ‘/usr/local/bin/bash’ as the default shell for the ‘ramp’ user.
In order to gather certain hardware information such as the device’s serial-number, the RAMP Data Collector will need to temporarily gain root privileges.
The file below will allow the ramp user to temporarily gain root privileges when running specific commands.
Add the following 2 lines to /etc/local/sudoers.d/ramp
# Allow Data Collector to execute dmidecode without needing password
ramp ALL=(ALL) NOPASSWD: /usr/local/sbin/dmidecode
If you have a large number of instances that will be discovered and monitored by RAMP, you may want to consider using an automation tool such as Ansible or Puppet to make these additions.
7.3. Note for SSH Discovery Using a Certificate Credential¶
As of OpenSSH version 7.8, the default format of RSA keys generated using ssh-keygen has changed.
Prior to version 7.8, generated keys would display the following header:
-----BEGIN RSA PRIVATE KEY-----
As of version 7.8, generated keys display the following header:
-----BEGIN OPENSSH PRIVATE KEY-----
The new format is currently not supported for discovery. You can generate RSA keys in a compatible format using the following command:
ssh-keygen -m PEM -t rsa -b 4096
7.4. Windows¶
The RAMP Data Collector requires network access to the Windows machine targeted for discovery. More details on this are available here.
RAMP requires credentials (local or domain user) with privileges to query and read WMI information. More details on this are available here.
The RAMP data collector required the target Windows machine to be fully resolved in DNS. If this is not possible, the target machine’s IP information can be added to the RAMP data collector’s HOSTS file as a workaround.