Forum Discussion
NimbostratusIapp template for exchange update, flush old application
Hi, I've done an upgrade and uploaded a new iapp template for exchange. I chose to create a new application and new virtual servers, pools, profiles etc. This went all fine.
But now I'd like to flush the previous application with all referenced virtual servers, pools, profiles, monitors etc. It looks like this is almost undoable because it's referenced with virtual server, pools etc. Error messages pops up every time i'd click on delete.
Is there a way to get rid of the old stuff by using CLI perhaps?
Thanks, Erik
9 Replies
Hi Erik, did you deploy the previous application using the iApp? If so you should be able to delete the application service from the Application Service List screen.
heskez_36146Yes I did, deleting the application service immediately brings out an error message, Bla bla referenced VS / Pool etc.
- This is almost always the result of disabling strict-updates and putting the iapp out of sync with your BIG-IP configuration. If you work within the iapp and do not disable strict-updates, the iapp will delete cleanly.
If there are any objects on the BIG-IP that weren't created by that iApp but depend on objects that were created by it (profiles, monitors, pools, etc), you will need to remove those dependencies before you can delete the iApp.
There's no way to do that automatically, AFAIK. You can search /config/bigip.conf for references to the first iApp name and then go back and remove those references manually.
- heskez_36146
Thanks, It seems that every object related to this iapp is created together with the installation of this iapp. Nevertheless I still have to manually track all references to this iapp and remove them manually? I tried but then I get an error message that I've to delete the object by the application interface.
The iApp only knows about the objects it creates and "owns" (which ones are tagged with the app-service property and live in the iApp's folder).
Sounds like someone came along after the iApp was deployed and configured other objects (either manually or using another iApp deployment) to point to its objects. When you deployed the second iApp, did you select any objects that were created by the first?
At any rate, you shouldn't need to modify any of the first iApp's objects to get it to delete. You need to look for the non-iApp objects that reference it and reconfigure them manually, or reconfigure the second iApp to create new objects instead of reusing ones from the first iApp.
- heskez_36146
When you deployed the second iApp, did you select any objects that were created by the first?
Yes, I did, but afterwards I've created new objects through the second Iapp.
- heskez_36146
I followed your advice concerning searching for references on the old iapp (2010) within /config/bigip.conf. they're off-course not to be found, the search on the new iapp (2013) however delivers me all references.
But when I want to manually delete the old VS (2010) It's popping up this annoying error message again:
The application service (/Common/Exchange_2010.app/Exchange_2010) has strict updates enabled, the object (virtual server /Common/Exchange_2010.app/Exchange_2010_combined_http) must be updated using an application management interface.
- heskez_36146
Got it! The order is like this:
- First remove all linked irules
- Profiles
- monitors
- Pools
- Virtual servers
- Iapp is gone! :)
