Operational Defect Database
BugZero updated this defect 58 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 359934
VoyenceControl: Unable to interact with duplicate device, receive error: NoSuchDeviceException: No such device idx
Last update date:
3/22/2024
Affected products:
Smart Assurance - NCM
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
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=1DEV 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.
