Request to simplify the generation of a new ud_unique_id on UNIX systems and document the steps

Idea ID 1660911

Request to simplify the generation of a new ud_unique_id on UNIX systems and document the steps

This is a request to simplify the process of generating new UD Unique ID.

- A short description of the present behaviour
The generation of a new ud_unique_id is not documented well and not user friendly. Currently when you want to generate a new unigue id (uda) on unix you need to:
- Go through unclear documentation
- Use 2 different commands (with confusing names discagent and discagnt)
- Switch between different folders

- Steps to reproduce the behaviour/issue
Example for Linux systems (but is relevant for all UNIXes)
1) Log in using the user account that is used to run the UD Agent (e.g. root)
2) Navigate to the directory that contains the UD Agent executable files (for Linux    /opt/microfocus/Discovery)
3) Stop UDA agent ./discagent stop
4) Switch to folder /opt/microfocus/Discovery/bin
5) Generate a new unigue id by running  ./discagnt --newuniqueid
5) Navigate back to the directory  /opt/microfocus/Discovery
6) Start the agent by running  ./discagent start

- The behaver you desire in a future release
Simply enhance current script discagent to support parameter newid
Extend the current shell command  discagent with new parameter to perform newunigueid operation. Now the shell command supports only parameters start, stop, restart and status. Add a new option for example newid
So the simple command ./discagent newid  would generate a new unique id (it would stop the agent, generate new unigue id, start the agent).
Generally discagent should be the only "wrapper/handler" to perform all actions with UDA agent for administrators. 

- Impact on the production
Simplify the support of cloning and imagining. Better UDA management. Less confusing. Faster to adopt by administrators in UNIX world.

- Whether you can’t wait for a future release and require a hotfix
We can wait for the next release

- Business justification if a hotfix is requested
Hot -fix is not required

1. Simplify the steps, preferably consider single command rather than two
2. Document the clear steps in a guide

Outstanding Contributor.
Outstanding Contributor.

A lot of people have been asking for easier ways to generate a new UD id:

The issue is not just on Unix systems.  We see it across platforms.

Outstanding Contributor.
Outstanding Contributor.

It would be even better if there were a discovery job that would generate new ud_unique_id for the input devices. I have been looking for a way to fix devices with duplicate ud unique id.

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 voting

Honored Contributor.. Honored Contributor..
Honored Contributor..


indeed. Now the clonning and imagining of systems is normal way of IT operation and we deal with it every day. 

Micro Focus Expert
Micro Focus Expert
Status changed to: Under Consideration

This idea received enough votes and comments from the community and been reviewed by Micro Focus for strategic fit. These ideas are continually monitored and considered for prioritization in our development planning.

Micro Focus Expert
Micro Focus Expert
Status changed to: Accepted

Great news, this idea has been accepted on our product roadmap. Subscribe to receive updates. (This is not a formal commitment, and subject to change)

Micro Focus Expert
Micro Focus Expert
Status changed to: Delivered

This idea has been implemented in product release CMS 2019.05. Check out the release notes for details. Thanks to all of our contributors for helping us continue to improve our products!

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.