- Hyperview
- Quickstart
- Asset Management
- Discoveries
- User Management
- Settings
- Search Features
- Licensed Features
- Release Notes
- Hyperview 2.2 (DRAFT PREVIEW)
- 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
Appendix 1: Setting Up Monitoring for VMware¶
VMware vSphere 6.5¶
Setting up monitoring for your VMware infrastructure with vSphere version 6.5 will require access to the CIM counters for the user account that has been set for the object. Here’s a step-by-step guide on how to setup a user account with read-only access to the CIM counters, i.e. minimum rights for monitoring.
Login to vSphere Web Client as administrator.
Select Home > Administration > Users and Groups
Add a new user called cimuser.
Navigate to Roles (Home > Administration > Access Control > Roles).
Add a new Role called CIM Only. Give the role CIM privileges only. Note: This is the minimum level that is required for RAMP to monitor.
Add user permissions at the Hosts and Clusters view.
Click add user button.
Select the cimuser from the list, then click add, then click OK.
Select the role for the cimuser called CIM Only.
You have created a user called cimuser with CIM Only access to vSphere. Use this set of credentials on RAMP discoveries to begin monitoring servers from the vCenter host.
VMware vSphere 6.0 (& older)¶
Setting up monitoring for your VMware infrastructure requires access to the CIM counters for the user account that has been set for the object. Here’s a guide on how to setup a user account with read-only access to the CIM counters, i.e. minimum rights for monitoring.
Using the vSphere Client, log on to your ESXi host > Click the Local Users & Groups tab.
To add a new user, right-click the white area and choose “Add…”
To set up the permissions, go to Inventory -> Administration -> Roles or click Ctrl+Shift+R
Right-click on any white space and choose “Add…”. Name the role and select only the privileges as in the example below (CIM interaction).
Go back to the main screen and choose the “Permissions” tab.