ghost interfaces?

Hi everyone, I had a similar issue last week, where as I momentarily installed a blade into slot 4 and removed it having to end up with "ghost interfaces" showing up.

4/1.1 miss 0 0 0 0 0 0 none 4/1.2 miss 0 0 0 0 0 0 none 4/1.3 miss 0 0 0 0 0 0 none 4/1.4 miss 0 0 0 0 0 0 none 4/1.5 miss 0 0 0 0 0 0 none 4/1.6 miss 0 0 0 0 0 0 none 4/1.7 miss 0 0 0 0 0 0 none 4/1.8 miss 0 0 0 0 0 0 none 4/1.9 miss 0 0 0 0 0 0 none 4/1.10 miss 0 0 0 0 0 0 none 4/1.11 miss 0 0 0 0 0 0 none 4/1.12 miss 0 0 0 0 0 0 none 4/1.13 miss 0 0 0 0 0 0 none 4/1.14 miss 0 0 0 0 0 0 none 4/1.15 miss 0 0 0 0 0 0 none 4/1.16 miss 0 0 0 0 0 0 none 4/2.1 miss 0 0 0 0 0 0 none 4/2.2 miss 0 0 0 0 0 0 none 4/2.3 miss 0 0 0 0 0 0 none 4/2.4 miss 0 0 0 0 0 0 none 4/mgmt miss 0 0 0 0 0 0 none

I then noticed that interfaces belonging to this blade were still showing in the bigip_base.conf file and tried editing this to completely remove them, also tried disabling the blade. -< Nothing helped tried to reboot blade/chassis hoping that might fix things, and failed again. I was left w/ no other choice but to contact the F5 support which gave me the following answer: "The reason the interfaces display is a design feature. " Obviously that is not a what i needed to hear, as the customer and I explicitly didn't want to see interfaces which don't exit as part of the config and can cause future confusion. After insisting on this I was given the following working explanation/solution:

If mcpd sees a blade plugged into a slot, it remembers it in memory. Mcpd also saves it's memory config to an XML file, so that when you reboot, mcpd can quickly load it's config, so it boots quicker. This is why when you rebooted before, you could still see the phantom interfaces. By running:-

before we rebooted, forces mcpd to load it's config from the config files, which is why this resolved your issue. note: that is to be applied after manually editing the bigip_base.conf file and modifying what needs to.

Hope this helps anyone in the near future, since i was unable to find any thing related to this issue here on devcentral.

Regards, V.Z