RAMP Version 3.11

DATE: 8.February.2018

Contents of the Release

File

Description

manager-31100.zip

A zipped file containing all files necessary for installation of RAMP Manager, RAMP Data Analyzer and SNMP Trap Listener for 3.11.0

dataCollector-31100.zip

A zipped file containing all files necessary for installation of RAMP Data Collector 3.11.0

Images.msi

Windows MSI file containing images for all the devices supported in RAMP 3.11.0

RFCodeSync-31100.zip

Optional. A zipped file containing all files necessary to install the RFCodes synchronization feature.

New Features

  • Introduction of a new type of location: Cloud Location and a new device type: Cloud Server.

    Cloud Location: is a location that contains Cloud Servers. An example of a Cloud Location could be AWS or Google Cloud.

    Cloud Server: a cloud server is a virtual server running in a public cloud. Currently three types of Cloud server are supported: AWS, Google Cloud and Microsoft Azure.

Cloud Location Behavior

Feature

Cloud Location

Location

Can be a child of a Location

Yes

Yes

Can be a child of a Cloud location

No

No

Can contain Physical Servers

No

Yes

Can contain Blade Servers

No

Yes

Can contain Virtual Servers

No

No. A Virtual Server must be child of a physical Server

Can contain Cloud Server

Yes

Yes

Refer to RAMP 3.11 User Guide for additional information on using Cloud Location and Cloud Server.

Changes in Behavior

Prior to RAMP Release 3.11.0: when synchronizing a Rack already present in Asset Vue with a Rack already present in RAMP, for the device synchronization to be successful, the Rack was required to have a Serial Number (S/N).

Starting with RAMP Release 3.11.0: a Rack present in both Asset Vue and RAMP will be successfully synchronized if either (i) the Rack has same display Name (not case-sensitive) in both Asset Vue and RAMP or (ii) if the Rack has same S/N in both Asset Vue and RAMP.

Supported Upgrade Path

Direct or one-step migration of RAMP Database from prior RAMP software releases to RAMP 3.11.0 are supported for following RAMP software releases:

  • RAMP 3.9

  • RAMP 3.10

Resolved Issues

Issue

Removed ability to retire virtual machines

Fixed inability of power users to edit global settings

Fixed translations for clipboard

Fixed invalid characters in the EULA

Fixed multiple rack select on view to appear in all locations

Fixed RAMP to provide warning when device limit is 95% reached

New Devices Supported

IBM - BladeCenter HS23

Liebert - STA0400P10S7972

IBM - IBM System x3630 M4

Liebert - HIAUL

IBM - System x3620 M3

Racktivity - ES2124-30

HP - DL380 Gen10

Dataire - GICW-03012

APC - NBRK0200

HP -S1324

HP - DL360 gen9 (Rear Image)

HP - S2324

Liebert - DH192GUAAEI

HP - S348

Liebert - DS105ASA0EI973A

HP - S340

Liebert - LTM1000

HP - 3500-24G-PoE+ yl Switch

Liebert - 38SA080A0A00

Brocade - M8428-k

Liebert - PPA200C

HP - J9729A

Server Technology - STV-4501C

Jacarta - interseptorPro

Server Technology - STV-6502M

Eaton - Pulsar STS 16

Known Issues

Issue

Workaround

6585 - Advanced Search does not filter on AssetVue properties

None

6586 - Advanced Search does not filter on Cloud Server or Cloud Location

None

6487 - Cannot delete an asset that has been part of a Planned Move

Retire the asset, will be fixed in a future version

6422 - SNMP Traps cannot be forwarded to RAMP from the data collector if RAMP manager is on HTTPS and the SSL certificate is not trusted

Install a trusted SSL certificate

Changes in Version 3.11.1

New Features

  • RAMP responds to BACnet WHO IS requests with Device Name and Vendor ID

  • Improved the API documentation for authentication and authorization

Device Support

  • Lenovo - RPDU - 00WC557

  • NetApp - SAN - DS2246

  • Juniper - NET - 4550

  • Lenovo - RPDU - 00WC557

  • NetApp - SAN - DS2246

  • Juniper - NET - 4550

Bug Fixes

  • Fixed spelling issue for Modbus definition upload

  • Enhanced device data pruning script so only the last 5 records are kept