Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

VoyenceControl: Unable to interact with duplicate device, receive error: NoSuchDeviceException: No such device idx (359934)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 1612Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Unable to interact with duplicate device, receive error: NoSuchDeviceException: No such device idx

Unable to unmanage duplicate device

Duplicate device is not found in cflist.cgi output

Duplicate device is not listed under Device Server in System Administration

Device is duplicated

ERROR:

com.powerup.configmgr.deviceservice.NoSuchDeviceException: No such device idx:

Resolution

To cleanly remove the duplicate device that causes the error you will need to create a temporary entry in the infrastructure database by cloning the working device entry, then proceed to remove the duplicate device as normal:

Note the Device idx numbers for the working device and the non-working duplicate device (See Note).

On the Application Server, change directory to $VOYENCE_HOME/cgi-bin.

Source the /etc/voyence.conf file:

source /etc/voyence.conf

Output the infrastructure database to a file with the following command:

./cflist.cgi > output.txt

Open the output.txt file for editing.

Locate the DEV entry line for the working device (in this example, the working device is idx 1002):

DEV 1002 "my_device" ElemList= PopParent=1000 EmsParent= : UID="04813603" HOSTNAME="my_device.lab.company.com" DOMAINNAME="lab.company.com" SYSOBJECTID="1.3.6.1.4.1.9.1.17" ADDR="10.6.231.3" PACKAGE=1 PACKAGE_IS_SET=0 CM_MANAGED=1 CREATE_DATE=1233348104 AUTO_DISCOVERED=1

Duplicate this line and change the idx number to the idx of the non-working duplicate device as follows (in this example, the non-working duplicate device is idx 1001):

DEV 1002 "my_device" ElemList= PopParent=1000 EmsParent= : UID="04813603" HOSTNAME="my_device.lab.company.com" DOMAINNAME="lab.company.com" SYSOBJECTID="1.3.6.1.4.1.9.1.17" ADDR="10.6.231.3" PACKAGE=1 PACKAGE_IS_SET=0 CM_MANAGED=1 CREATE_DATE=1233348104 AUTO_DISCOVERED=1
DEV 1001 "my_device" ElemList= PopParent=1000 EmsParent= : UID="04813603" HOSTNAME="my_device.lab.company.com" DOMAINNAME="lab.company.com" SYSOBJECTID="1.3.6.1.4.1.9.1.17" ADDR="10.6.231.3" PACKAGE=1 PACKAGE_IS_SET=0 CM_MANAGED=1 CREATE_DATE=1233348104 AUTO_DISCOVERED=1

Locate the POP entry line for the Device Server that the working device is in.  Add the non-working duplicate device idx to the DevList:

POP 1000 "voyence-ds" NetList= RsrcList= DevList=1002,1001 EmsList= : ADDR="192.168.1.12" AGE_DAYS=730 CLEANUP_DAYS=90 AD_ENABLE=0 AD_ARPCACHE=0 AD_DFLTROUTE=0 AD_AUTO_RESOURCE=0 AD_DEFAULT_POLL=0 SNMP_TIMEOUT=500 SNMP_RETRY=3 CM_DEBUGSESSION=1 SORTCONFIG=1 CM_MAXMAINTASKS=20 CM_PULLTIMER=1200 MAX_COMM_ATTEMPTS="5" AD_BATCHSIZE=50 AD_NUMHOP=10 RECORDVER="1.0"

Save your changes and exit.

Write your changes to the infrastructure database with the following command:

./cfwrite.cgi < output.txt

In the VoyenceControl Application, unmanage and remove the duplicate device as normal.

Related Information

The Device ID column is found in the Network Device Table, and is often referred to as the Device idx.  You may need to add the column to see it.

The $VOYENCE_HOME variable is a reference to the install directory of VoyenceControl.  By default this is /opt/voyence.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - NCM

Take Our Survey

Support Assistant