PROBLEM:
In the original Nimble Storage Array signature included with Traverse 9.3, I/O latency metrics reported by the device do not match what is reported by Nimble WebUI.
SOLUTION:
As a workaround, a new signature is included in this KB (now included in 9.5.060) to discover the metrics used in conjunction with the below instructions to match the latency data from the Nimble WebUI:
- Download attached signature and replace the file (now included in 9.5.060) <TRAVERSE_HOME>/etc/typedef/95_ent_nimble.xml on the BVE server
- Log into your Traverse UI as superuser or admin level user
- Navigate to Superuser --> Health --> left click on the gear icon for the BVE server and select 'Reload Config Files'. *Repeat for all server entries on this page.*
- Discover (or re-discover) the following metrics (with the updated signature):
I/O Read Time
I/O Write Time
I/O Reads for Latency
I/O Writes for Latency
- To monitor Read Latency:
- Create a composite test for the device (ADMINISTRATION > DEVICES > Create New Advanced Tests)
- Name the test 'Read Latency'
- Add child tests where T1 = I/O Read Time and T2 =I/O Reads for Latency
- Set the expression to T1 / T2 or to match (I/O Read Time) / (I/O Reads for Latency)
- Check mark the box and click 'Provision Tests'
- To monitor Write Latency:
- Create a composite test for the device (ADMINISTRATION > DEVICES > Create New Advanced Tests)
- Name the test 'Write Latency'
- Add child tests where T1 = 'I/O Write Time' and T2 = 'I/O Writes for Latency'
- Set the expression to T1 / T2 or to match (I/O Write Time) / (I/O Writes for Latency)
- Check mark the box and click 'Provision Tests'