Interface Name Alias do not match Interface Name

Document ID : KB000124010
Last Modified Date : 28/12/2018
Show Technical Document Details
Issue:
The "Interface name alias" field does not match the "Interface Name" field for a few different devices. When creating groups and search by interface it is the second column listed and is confusing some of our users.

Example: 
        Interface Name - Gi1/0/1     -    Interface Name Alias - Gi1/2

 
Environment:
CA Performance Center 3.6
Cause:
Devices were replaced, and old aliases were apparently kept, which didn't line up with new interface names
Resolution:
1. Verify that alternatename is being used for "Interface Alias Name" by getting a count
 
select count(*) from t_interface where itemname != alternatename;

(this will return a number, for example; 2248)

2. Set alternatename to equal itemname, as follows
 
update t_interface set alternatename = itemname;

3. Clear Item and Group cache, by running the following curl commands
 
 curl -v -X PUT -H 'Content-Type: application/xml' -d '<emptybody/>' -u admin:<adminPW> http://<CAPCHOST>:8181/pc/center/webservice/invalcache/ITEM
 curl -v -X PUT -H 'Content-Type: application/xml' -d '<emptybody/>' -u admin:<adminPW> http://<CAPCHOST>:8181/pc/center/webservice/invalcache/GROUP


   
   
Additional Information:
If using HTTPS, you can use the -k switch to accept insecure certs, as follows

curl -v -k -X PUT -H 'Content-Type: application/xml' -d '<emptybody/>' -u admin:admin https://<CAPCHOST>:8182/pc/center/webservice/invalcache/GROUP