When NFA is paired with NetOps Portal, you may encounter a strange issue where 'Admin' or 'Poweruser' privileged level users CAN see all interfaces in NFA while 'User' privileged users CAN'T see all interfaces. You may also experience an issue where you can see the interface in NetOps Portal but when you click on the interface to view it in NFA directly, the page will display a message that the interface could not be found.
NFA
This issue will occur when interfaces exist in 1 database table but not another. Once those extra interfaces sync up to NetOps Portal, NetOps Portal will not know how to group them properly as they do not belong in the system anymore. Luckily there is an easy fix for this.
For NFA 9.1 - 9.3.3:
1. RDP to NFA Console Server
2. Open a CMD Prompt and type:
3. On each harvester fun these commands:
4. Go to NetOps Portal and select the Administration Page > Data Sources
5. Select the NFA data source and do a FULL resync.
6. After the resync completes the issue will be resolved.
For 9.3.6+:
1. RDP to NFA Console Server
2. Open a CMD Prompt and type:
3. On each harvester run these commands:
4. Go to NetOps Portal and select the Administration Page > Data Sources
5. Select the NFA data source and do a FULL resync.
6. After the resync completes the issue will be resolved.
NFA 21.2.8+
NFA 21.2.8 adds a new mysql password to the database. So, in order to run these commands we're going to need to specify a password now. By default the mysql password is 'root@123'. So, in 21.2.8, we can run the commands like this:
1. RDP to NFA Console Server
2. Open a CMD Prompt and type:
3. On each harvester run these commands:
4. Go to NetOps Portal and select the Administration Page > Data Sources
5. Select the NFA data source and do a FULL resync.
6. After the resync completes the issue will be resolved.
If the issue still isn't resolved, check to see if the router in question has duplicate agents (licensed interfaces with the same ifindex). If they do, go to Physical and Virtual and merge the interfaces. Do a full sync in NetOps Portal and the issue should be gone.
Please also see the following KB Article if the above does not resolve the issue:
https://knowledge.broadcom.com/external/article?articleId=108589