- 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
Adding assets¶
Assets are typically bulk-imported or discovered. You can also add assets manually, one at a time.
Power Users and above can bulk import and manually add assets. Certain asset types can only be added using a particular method:
Power Meter and Unknown asset types are discovery-only.
Location and Rack asset types can only be added manually.
This topic covers bulk importing and manually adding assets. For a complete list of asset types, see Supported asset types. To discover assets, refer to Discoveries and related topics.
Bulk importing assets¶
You can bulk import assets using a CSV template that you can download from the application.
Note
You cannot bulk import Location or Rack type assets.
Go to Assets → Bulk Import → Download Template File → Assets. A CSV template for bulk importing assets will be downloaded to your browser’s default download directory. Rename and move the file to a different folder as needed.
Update the file for assets that you wish to import. Available columns are:
Column
Description
Requirement
Name
The name of the asset you are importing
Required
LifecycleState
The asset lifecycle state (Active, Planned, Procurement, Staging, or Retired)
Optional
AssetType
The asset type, such as Server, PDU, etc (but not Rack or Location)
Required
Manufacturer
The asset manufacturer name
Required
Model
The asset model name
Required
SerialNumber
The asset serial number
Required for non-rack assets (optional for Rack)
RackName
The name of the rack where the asset will be placed
Optional (only allowed for rackable assets)
RackUNumber
The number of the rack unit where the asset will be placed
Optional (only relevant for non-Zero U assets)
RackSide
The rack side (Front, Rear, or Unknown) where the asset will be placed
Required for Zero U assets (not allowed for unplaced rackable assets)
RackPosition
The rack position (Left, Right, Top, Bottom, Above, Below, or Unknown) where the asset will be placed
Required for Zero U assets (not allowed for unplaced rackable assets)
Save the updated file.
Click Select Location and File. Provide values as follows:
Select the “Assets” template.
Select the target location for the assets. The default location is All.
Select or drag the updated CSV file to upload.
Once the file is uploaded, verify the list of assets. Troubleshoot, update, and re-upload the file as needed.
Click Import.
The import process may take several minutes or more if you are importing a large number of assets. Upon import, the assets will appear in the Asset Hierarchy under your specified location.
Manually adding an asset¶
You can manually add an asset in Hyperview from one of the following places:
The Add New page (Assets → Add New)
The Asset Hierarchy context menu (right-click → Add New Asset or Add New Location)
Asset dashboards (asset → Actions → Add New)
Adding an asset from the Add New page¶
Go to Assets → Add New.
Select a Type. Relevant fields will appear.
Note
Available asset types will depend on the parent asset. The asset type in turn primarily dictates what fields are surfaced.
Enter values as appropriate. Depending on your inputs additional fields may appear.
Note
While selecting a rack, Rack Side and Rack U are required for rackable assets. For Zero U assets, Rack Side and Rack Position are required.
Tip
Create a Data Collector before adding an asset with a BACnet/IP or Modbus TCP sensor monitoring profile. See Prerequisites for instructions.
Click Add and Continue to start with blank fields for subsequent entries, or Add and Reset to repeat your entered values (except for Name) for subsequent entries.
A success message will be shown. The asset will appear in the Asset Hierarchy under the specified location.
Adding an asset from the Asset Hierarchy context menu¶
You can add a location or non-location asset directly from the Asset Hierarchy’s right-click context menu. Simply right-click the intended parent location or asset, and select Add New Asset or Add New Location as appropriate.
The rest of the process is identical to what’s described in the previous subsection, with one addition: in step 4, you can also click Add → Add to finish adding the asset (without having to continue with new or same values).
Adding an asset from another asset’s dashboard¶
You can also add child assets directly from the parent asset record:
From the parent asset’s Dashboard, click Actions → Add New. Proceed to add an asset as you would from the Asset Hierarchy.