- 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
Configuring discoveries¶
Click the Details button for the discovery in the Discoveries grid. The Basic Settings page will open.
Proceed to configure the discovery as per the following subsections. At a minimum, you will need to specify IP addresses and protocol credentials.
Updating basic settings¶
The Basic Settings page lets you update the base record for the discovery. You can:
Update the Discovery Name
Update the Data Collector for the discovery
Update the Location where discovered assets will be added
Toggle a setting to “Monitor newly discovered assets by default”
Click the Save button to retain your changes.
Note
You cannot update the Discovery Type (General, VMware, or IxOS). Updating the Location value will have no effect on already-discovered assets — they will remain at their current location.
Adding IP addresses¶
Click the IP Addresses tab to open the IP Addresses page for your discovery. By default, no IP addresses are added to new discovery records.
You can specify IP addresses to include or exclude from your discovery as follows:
Click on the corresponding Add button.
Provide details as follows:
Specify the Type (Single IP Address, IP Range, CIDR Range, or List).
Provide a Description (optional).
Specify the IP address or range using relevant Type-specific fields.
Note
We recommend keeping the total number of IP addresses in a discovery under 1,000 to keep the discovery runtime manageable. It is also best practice to separate discoveries by asset type and protocol to keep discoveries organized and simplify any troubleshooting scenarios.
Updating protocol settings¶
Click Protocol Settings → Protocols to open the Protocol Settings page. By default, all discovery-supported protocols are enabled.
To disable a certain protocol, click the toggle switch.
To open protocol-specific settings pages for IPMI, SNMP, SSH, or WMI, click on the corresponding Edit button on the Protocol Settings page. Alternatively, click on the page link from the Protocol Settings dropdown. You will need to provide protocol access credentials.
Click Add → provide protocol-specific credential values → Save.
Alternatively, click Add → Existing Credential → select credentials → Save.
Tip
You can also add protocol credentials from Discoveries → Credentials, which you can select for subsequent discoveries.
Relevant port numbers are automatically added for each protocol upon discovery creation (note: not relevant to WMI as it uses dynamic ports).
To add a different port, click Add → enter port number → Save.
To delete a port, click Delete → Delete.
Adding a discovery schedule¶
Click the Schedules tab to open the Schedule page, which lets you specify a runtime schedule for your discovery. By default the Schedule value is set to None, which implies that the discovery will only be run manually.
Select Daily, Weekly, or Monthly from the Schedule dropdown.
Provide values and click Save.
Note
Discovery runtime schedules are in UTC.