Naviseccli XML output not in standard format

Which commands are you using with the -XML switch? Do all commands not output correctly?

glen

I used getsp, getlun etc. Marked the strings with red which doesn't fit into the correct XML format..

Here are the  sample outputs:

SP A

SPE3

1774304

1745004

3.26.20.5.016

CF2MP064900736

2048

0

SP B

SPE3

1745004

1774304

3.26.20.5.016

CF2MP064200108

2048

0

0

true

CLIProvider

success

GETLUN:

100

1

2048

60:06:01:60:E0:12:1B:00:D4:BB:D7:F8:97:00:DD:11

Bus 0 Enclosure 0  Disk 5  Queue Length:               23
Bus 0 Enclosure 0  Disk 6  Queue Length:               23
Bus 0 Enclosure 0  Disk 7  Queue Length:               23
Bus 0 Enclosure 0  Disk 8  Queue Length:               23
Bus 0 Enclosure 0  Disk 9  Queue Length:               23
Bus 0 Enclosure 0  Disk 5  Hard Read Errors:           0
Bus 0 Enclosure 0  Disk 6  Hard Read Errors:           0
Bus 0 Enclosure 0  Disk 7  Hard Read Errors:           0
Bus 0 Enclosure 0  Disk 8  Hard Read Errors:           0
Bus 0 Enclosure 0  Disk 9  Hard Read Errors:           0
Bus 0 Enclosure 0  Disk 5  Hard Write Errors:          0
Bus 0 Enclosure 0  Disk 6  Hard Write Errors:          0
Bus 0 Enclosure 0  Disk 7  Hard Write Errors:          0
Bus 0 Enclosure 0  Disk 8  Hard Write Errors:          0
Bus 0 Enclosure 0  Disk 9  Hard Write Errors:          0
Bus 0 Enclosure 0  Disk 5  Soft Read Errors:           0
Bus 0 Enclosure 0  Disk 6  Soft Read Errors:           0
Bus 0 Enclosure 0  Disk 7  Soft Read Errors:           0
Bus 0 Enclosure 0  Disk 8  Soft Read Errors:           0
Bus 0 Enclosure 0  Disk 9  Soft Read Errors:           0
Bus 0 Enclosure 0  Disk 5  Soft Write Errors:          0
Bus 0 Enclosure 0  Disk 6  Soft Write Errors:          0
Bus 0 Enclosure 0  Disk 7  Soft Write Errors:          0
Bus 0 Enclosure 0  Disk 8  Soft Write Errors:          0
Bus 0 Enclosure 0  Disk 9  Soft Write Errors:          0

Bus 0 Enclosure 0  Disk 5   Enabled

Bus 0 Enclosure 0  Disk 6   Enabled

Bus 0 Enclosure 0  Disk 7   Enabled

Bus 0 Enclosure 0  Disk 8   Enabled

Bus 0 Enclosure 0  Disk 9   Enabled
YES

Unknown

Not Available

Not Available

0

true

CLIProvider

success

This is the output from the getsp - using the latest naviseccli on my workstation (Windows XP) and on the array  04.29.000.5.003 (CX4-960) - is this correct?

From the Release Notes for Navisphere CLI:

Navisphere Host Agent_CLI and Utilities Release Notes  6.29 A03 .pdf

All
Navisphere Secure CLI
Issuing a getlun command with the –xml switch does not always return properly formatted xml.

Frequency of occurrence:
Infrequently under a specific set of circumstances.
Severity:
Low

Issuing a getlun command with the –xml switch will return improperly formatted xml if you have specified subcommands that require stats logging to be enabled on the storage system when it is not enabled. The disk information will be compounded together rather than each disk having its own element.

Exists in versions:
6.26.0.2.24
6.26.1.0.17
6.26.2.0.2
6.26.5.0.95
6.26.7.0.81
6.26.9.0.51
6.26.10.0.61
6.26.30.0.99
6.28.0
6.29.0
Fixed in version:
6.29.5.0.66

Glen

Right so in the output you pasted if you see SPA and SPB strings are not inside any tag. So my XML parser won't be able to parse these strings. This will lead to confusing the output as if for which SP does it actually belong (SPA or SPB).

Similarly for the getlun output (plz check the output i pasted earlier), the BUS and enclosure informations are not inside any tag so XML parser will miss them.

I am using 6.29.5.0.66.

Does it mean that even 6.29.5.0.66 version doesn't give properly formatted output?

[ Thanks Glen for helping me with pointers here ]

--Ashit

OK, not really knowing anything about xml, I can now see what you mean - the lines that are just SPA and SPB - nothing around these two. I'll ask engineering about this - thanks for pointing this out.

glen

Did you open a service request for this issue?

glen

Found that the =xml getlun is fixed in the latest flare 29 update 006 - just tested that.

Getsp is a bug

Found that the -xml getlun is fixed in the latest flare 29 update 006  - just tested that. The -xml getsp is a bug and will be fixed in a later update.

Found out that most xml fixes are in flare and not CLI.

Thanks for pointing this out.

glen

I have opened SR

35301546

Thanks and regards

Ashit

Case has been opened. So this discussion can be closed.

For everyone's information this bug still exists and EMC have failed to address these issues in current FLARE or naviseccli code.  The XML produced in naviseccli is riddled with arbitrary string content which breaks XML parsing.  This occurs when requesting any XML that is less than the full configuration of the array, which takes some minutes to return.

I will endeavour to raise this with EMC.

As EMC/customers sometimes discover issues with XML, the best suggestion is to open a case with EMC with the issue. Please provide the details (as in the original posting above), outputs from the commands, the version of Flare on the array, the version of naviseccli and any other logs (such as spcollects) when you open the case. Be sure that all software is running the most current version.

glen

Thanks Glen.  Upon closer inspection it appears that a fix was added to very recent versions of VNX-2 FLARE code (version 33.8.5.119 includes the fix which correctly tags the items which were previously bare text) but there is no fix available for VNX.  I have logged an SR with the hope of getting a bugfix out for VNX.