Nlyte Data Center Infrastructure Management (DCIM)

Nlyte Data Center Infrastructure Management (DCIM)

Score 5.7 out of 10
Nlyte Data Center Infrastructure Management (DCIM)

Overview

What is Nlyte Data Center Infrastructure Management (DCIM)?

Nlyte, headquartered San Mateo, California offers their eponymous a data center infrastructure management (DCIM) solution.
Read more

Recent Reviews

Read all reviews
Return to navigation

Pricing

View all pricing
N/A
Unavailable

What is Nlyte Data Center Infrastructure Management (DCIM)?

Nlyte, headquartered San Mateo, California offers their eponymous a data center infrastructure management (DCIM) solution.

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Would you like us to let the vendor know that you want pricing?

10 people want pricing too

Alternatives Pricing

What is Device42?

Device42 is a comprehensive, agentless discovery system for Hybrid IT. Device42 can continuously discover, map, and optimize infrastructure and applications across data centers and cloud, in order to provide an accurate views of the IT ecosystem. Device42 intelligently groups discovered workloads by…

Return to navigation

Product Details

What is Nlyte Data Center Infrastructure Management (DCIM)?

Nlyte, headquartered San Mateo, California offers their eponymous a data center infrastructure management (DCIM) solution.

Nlyte Data Center Infrastructure Management (DCIM) Technical Details

Operating SystemsUnspecified
Mobile ApplicationNo
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

 (3)

Reviews

(1-1 of 1)
Companies can't remove reviews or game the system. Here's why
Score 8 out of 10
Vetted Review
Verified User
Nlyte is being used by the Data Center Operations group within my organization. We use Nlyte Asset Optimizer (NAO) to track every asset in our hosting centers. We also use Nlyte Energy Optimizer (NEO) to monitor the hosting center environment. These two modules can be integrated so that if an alarm occurs in NEO, NAO will show us the exact location of the asset causing the alarm.
  • Nlyte Asset Optimizer (NAO) tracks every asset in our hosting centers and when integrated with Nlyte Energy Optimizer (NEO), which monitors the hosting center environment, we can see, at a glance, the asset causing the alarm and its exact location in the hosting center. This is a strength, as it provides for faster resolution of problems if/when they occur.
  • Nlyte Asset Optimizer (NAO) has a lot of built-in reports that are great for looking at. For example, servers of a specific brand, or how many Us are taken up by servers. I see this as a strength and use this capability for capacity planning.
  • Nlyte Asset Optimizer (NAO) is currently all manual entry of assets. It would be great if NAO could provide for automated discovery of hosting center assets. This automation would be limited to ICMP and SNMP communication so not every asset can provide automated discovery, but it would be great for all IP addressable devices.
Nlyte is well suited for keeping a detailed inventory of the assets in the hosting center. With the ability to import hosting center floor plans, knowing exactly where each asset is located is a snap. When alarms occur in monitored devices, this also provides faster resolution because the exact point of alarm can be displayed on the floor plan.
Nlyte is also well suited for organizations with data center assets housed in multiple locations. In some cases, as with my organization, some of the locations are Telco rooms or closets. Again, when properly set up, a device causing an alarm can be pinpointed to its exact location.
  • Nlyte has had a positive return on investment (ROI) for my organization. A big factor in the ROI is having faster resolution times when alarms occur.
I am still using the other three products as they have features that Nlyte does not have, and that are really out of scope for Nlyte. I can give one example because this product is an in-house application. It is our CMDB application, and it interfaces with several other in-house systems to provide data that Nlyte is not designed for. Example: If we get an alarm from a server, and if there is currently a planned outage with a Request For Change (RFC), we ignore the alarm unless it exceeds the RFC window.
Return to navigation