Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
The Clariion and VNX SAN instrumentation require the installation of the the Navisphere CLI tool (naviseccli). Once installed, add both service processors (SP-A and SP-B) as devices into your account. On each of these devices set system.categories to either EMC_VNX for Clariion and VNX systems, or EMC_VNX2 for VNX2 series systems.
Also, you’ll need to ensure that statistics logging for block storage is enabled on your system.
Note that these datasources are designed such that the device instrumentation is gathered from SP-A, while monitoring of SP-B has been designed to alert when SP-A is unavailable.
Navisphere CLI is a tool provided by EMC to provide for programmatic management of block (SAN) storage systems such as Clariion and VNX series.
The LogicMonitor Collector uses this tool to gather data directly from the EMC service processors. You’ll need to install this package on each Collector from which you mean to monitor these types of EMC systems.
naviseccli -address <sp ip address> -User <operator> -Password <passwd> -Scope 0 getagent
Note: If you have multiple Clariion / VNX systems, you can set these properties either in a device group or top-level group (provided you elect to use the same operator credentials across all systems).
Before LogicMonitor can poll your EMC Clariion and VNX systems for block storage performance metrics, these systems need to be configured to collect these type of statistics. Where you set this up varies depending on your version of Navisphere/Unisphere Manager, but in general you’ll want to something along these lines:
For additional metric granularity, you may set Real Time Interval & Archive Interval to be more frequent in exchange for higher Storage Processor utilization and additional NAR/NAZ file generation. It is recommended to have Archive Interval set to 60 seconds during testing, not exceeding 300 seconds for regular monitoring.
In This Article