SummaryIf importing configuration between devices, it is possible to see 'ghost' interfaces and bridges - those that do not actively exist in the current hardware setup.
OverviewWhen migrating or importing config to different hardware, the configuration file involves bridge and interface information. If importing the configuration from a binary file, it will import fully - including that port information that does not exist in the hardware. In latest versions, Exinda gets into reporting issues when such things happens.
To check how many interfaces the system has, go to Configuration-->System-->NICs and see how many bridges and interfaces are there.
Then go to Configuration-->System-->Maintenance. There is an option there to "Load Running Config". Once it is loaded, there are sections for "Bridging configuration" and/or "Network Interface Configuration" sections. This will list more than there is in the NICs page.
To remove these from the configuration (XX is the bridge number, YY is the LAN interface number and ZZ is the WAN interface number):
exinda# conf t
exinda(config)# no bridge brXX
exinda(config)# no interface ethYY create
exinda(config)# no interface ethZZ create
exinda(config)# no interface brXX create
Preform all of those commands for however many bridges and interfaces do not exist. Then re-load the running config to ensure those command lines are no longer there. The system might ask you to Restart the Optimizer (which is actually a good sign). Restart the Optimizer and Save the changes.
Additional InformationTips To Avoid Getting Non Existing Bridges & Interfaces In Configuration File:
Avoid migrating configuration files from one Exinda to the other using the configuration file in binary format. Instead, download the text version (click on the floppy disk icon on Configuration > System > Maintenance next to the active running config) and then copy and paste pieces of the configuration file onto System-->Maintenance-->Import Config. While doing this, simply copy and paste lines that are part of the configuration of Network Objects, Schedule Objects, Applications, App-groups, policies and circuits (among others) and avoid pasting referrals to hardware (for example the "Bridging configuration" and/or "Network Interface Configuration" sections)