Highlighted
Not applicable

Navi cli doesn't return some metrics

Hi.

Have issues with returning LUN data using NaviCLI-Linux-64-x86-en_US.7.33.9.2.31 for storages CX4-120 and VNX5200.

naviseccli -h 192.168.10.10 getall

VNX5200:

Private LUNs which are part of metalun always return "0" for metrics "Number of arrivals with non-zero queue" and "Sum queue lengths by arrivals". For user LUNs which are not part of metalun everything returns fine.

CX4-120:

Private LUNs which are part of metalun always return "0" for metrucs "Read Requests", "Write Requests", "Number of arrivals with non-zero queue" and "Sum queue lengths by arrivals"

FOR ALL METALUN ON BOTH STORAGES:

for metaluns navicli doesn't return metrics "read requests", "write requests", "Blocks read", "blocks written", "Sum queue lengths by arrivals", "Number of arrivals with non-zero queue"

Labels (1)
0 Kudos
5 Replies
Highlighted
5 Rhenium

Re: Navi cli doesn't return some metrics

Pretty sure that's by design - depending on the family (CX, VNX) some of the metrics are not supported for the getall command. Check the CLI manual, there is usually some text that talks about what is supported on what array model/

glen

0 Kudos
Highlighted
Not applicable

Re: Navi cli doesn't return some metrics

Sorry for late answer. Studied CLI user manual didn't find any mention about not supported metrics

0 Kudos
Highlighted
5 Rhenium

Re: Navi cli doesn't return some metrics

For metaLUNs, the private LUNs (component LUNs) will not display metrics with the getall command. from CLI manual:

=======================================

getall


-lun

Displays only information about each logical unit (host and system) in the system. This is a composite of information displayed by getsniffer, storagegroup, and getlun commands.


getlun


Note

If statistics logging is disabled, some fields are not printed (switches marked with * below). Other switches must be used with the -disk switch (switches marked with ** below).


If the target LUN is a metaLUN, We recommend that you use the metalun -list command (see metalun -list) instead of the getlun command to return information about the metaLUN. If you use the getlun command, only the following fields report data that apply to metaLUNs — Name, Current owner, Default owner, LUN Capacity (Megabytes), LUN Capacity (Blocks), UID, Is Private, Snapshot List, MirrorView Name if any.


If you target the LUNs that make up a metaLUN, all fields apply

=======================================

glen

0 Kudos
Highlighted
Not applicable

Re: Re: Navi cli doesn't return some metrics

Thank you for answer.

For metaLUNs, the private LUNs (component LUNs) will not display metrics with the getall command

Didn't find any info about this in cli guide. Why do getall return private Luns (part fo metalun) metric partly? For cx4_120 only MB\s for VNX52000 doesn't return "Number of arrivals with non-zero queue" "Sum queue lengths by arrivals". Doesn't return i mean return "0" in that fields. I am confused here cause getall actually return metalun's luns metrics but partly and for cx and vnx return different set of them. This behavior makes me suppose that this is an issue.

Using navicli it's not possible to monitor metalun performance. And it's not an issue it's by design. Am i right?

0 Kudos
Highlighted
5 Rhenium

Re: Navi cli doesn't return some metrics

For metaLUNs, the correct way to look at performance is at the metaLUN level, not at the component layer. The metrics for the components can be confusing at times. If a particular metric is not shown that is most likely by design. The archive file does contain the component LUN's metrics that are needed for correct metaLUN calculations.

glen

0 Kudos