- Hyperview
- Quickstart
- Asset Management
- Discoveries
- User Management
- Settings
- Search Features
- Extracting Data
- Licensed Features
- Document Management
- Rack Security
- Release Notes
- Hyperview 3.1 (September 17 2021)
- 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
Maintaining Data Collectors¶
Data Collectors must be up-to-date and communicating consistently with the Hyperview platform. This is crucial because sensors are assigned to Data Collectors. Using a stale or non-functioning Data Collector will result in incorrect sensor data and therefore an inaccurate representation of your assets in Hyperview.
Tracking stale and outdated Data Collectors¶
The Last Communicated column in the Data Collectors grid indicates the UTC datetime when a particular Data Collector last communicated with Hyperview. The Version column shows the Data Collector version number.
Distinct alarm event messages are generated for the All location (Asset Hierarchy → All → Events) if:
- a Data Collector has not communicated with Hyperview within 2x the usual polling frequency; or
- the Data Collector version is out of date.
Consult your IT department to address any connectivity issues, and/or update the Data Collector accordingly.
Updating Data Collectors¶
To install the latest Data Collector, first uninstall the existing Data Collector, then proceed to set up the new Data Collector.
Re-registering Data Collectors¶
To re-register a Data Collector, simply repeat the steps outlined in Registering Data Collectors.
Retiring a Data Collector¶
You may want to retire a Data Collector for various reasons, such as:
- The server hosting the Data Collector is no longer operational.
- A faster server is available.
- The current Data Collector server needs to temporarily go offline for maintenance.
- A new server has been set up that is geographically closer to the assets you intend to monitor.
Retiring a Data Collector will permanently remove it from the system. During the retirement process, you must specify a substitute Data Collector that will take over the responsibilities of the Data Collector you are retiring. If you only have one Data Collector, you cannot retire it unless you add a substitute.
- Log in to your Hyperview instance as an Administrator.
- Go to Discoveries → Data Collectors.
- Click the Retire button for the intended Data Collector. The “Retire Data Collector” modal will open.
- Select the substitute Data Collector from the dropdown and click Save.