NA Device Diagnostics comparison should ignore whitespace, tab and special characters.

Idea ID 2686181

NA Device Diagnostics comparison should ignore whitespace, tab and special characters.

After the switch is upgraded, the output of MAC Addresses contains an extra whitespace. While comparing it shows something has changed and that change is only the whitespace.

Customer requires the whitespace to be ignored and since there is no change. Customer is reasoning that an automation tool should show only if there is a actual change of data i.e. ip address, mac address and in production that switch will have thousands of mac address which they have to compare manually then what is the use of automation.

Additionally customer wanted option to be provided in NA to ignore whitespace, tab and special characters. Customer gave reference of diffchecker.com

 

3 Comments
Cadet 3rd Class
Cadet 3rd Class

Hi,

   I support this idea, as it is very important for customers to validate the changes after the upgrade. If unnecessary NA showing changes for whitespace then it is a waste of time for customers.

Best Regards,

Sultan

Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

The idea has received an initial review to ensure adherence to our idea submission and community guidelines. More information may be needed at this stage, and we expect the community to help prioritize the idea with comments and community support (votes/kudos).

 

Fleet Admiral
Fleet Admiral

Hi

 

just to step in to support the idea, and to add that side-by-side configuration comparison should also be enhanced in this way. Also, a simple line-by-line comparison is not good enough if i.e. after a device upgrade, a configuration block is positioned somewhere else in the config. We have a POC customer mentioning that if the configuration before and after a SW upgrade might actually be the same but the parts of the config are placed in different positions, that comparison would show a config change because the config might literally be different but logically it might not be different... We did not actually experience this kind of behavior but looking at the simple POC system, we anticipate (along with the customer) that this might be an inconvenience. If however, current NA config mechanism is able to recognize that the config piece is "the same" even if it is placed somewhere else in the config, please confirm this is the case and ignore this remark. I still support the original idea.

regards

Marko

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.