Forum Discussion
mikeshimkus_111
Apr 15, 2016Historic F5 Account
Hi Misty, that's an odd error message to be getting considering we don't do anything with portal mode in the iApp. Was the APM configuration modified after these were deployed?
- Misty_SpillersApr 15, 2016NimbostratusThe older ones are modified but this one I can't even create it. I get that message after I answer the questions and click "Finished" I even tried an older iApp 1.4.0 and still got that error message. I thought it was weird too
- Fred_Slater_856Apr 15, 2016Historic F5 AccountThe apm access profile name is fixed ("exch"), so if you are running the new iapp on a device that has the older version running, there could be some interplay.
- mikeshimkus_111Apr 15, 2016Historic F5 AccountMisty, you should probably open a support case. Once you upload a qkview to iHealth, I'd be happy to take a look. It's nearly impossible to say what's going on without being able to see the configuration.
- Misty_SpillersApr 15, 2016Nimbostratusopened case C2095245 and uploaded a qkview to ihealth
- mikeshimkus_111Apr 15, 2016Historic F5 AccountI just looked at your config. The APM access profile you are trying to assign to the Exchange deployment is also used by another virtual server that calls rewrite and connectivity profiles. These aren't supported by the any version of the iApp out of the box, so someone must have done significant customizing on your old deployment. If you want to duplicate the previous deployment, you'll need to run the new iApp, then disable strictness and assign the correct connectivity, rewrite, and access profiles. Strictness would have to remain off on the new deployment after that.
- Misty_SpillersApr 15, 2016NimbostratusI'm the only one who has used iApps and I've never customized them that much. is it possible you can give me an example of what you mean? Also not sure how I can run the iApp when it can't get past the error. Thanks so much for you time!
- mikeshimkus_111Apr 15, 2016Historic F5 AccountWhen I look at the commands that the iApp was running when you tried to deploy it, I see that you were trying to assign a pre-existing APM profile to the virtual server. I looked at the profile and also at the existing virtual server where it was applied, and it looks like that is running in APM portal mode. Portal mode is not supported by the iApp, so that must have been customized after it was deployed. In order to re-apply the customizations, you'd need to run the new iApp without trying to attach the existing APM profile. You'd select "Create a new Access Profile" and enter in the required info, then you could disable strictness and modify the virtual server to use the existing access profile instead.
- Misty_SpillersApr 15, 2016NimbostratusOhhhhh, I see what I did. I was trying to reuse an "AAA server" group, but instead chose the policy instead, like several times .... Geez. Thanks for your help!
- mikeshimkus_111Apr 15, 2016Historic F5 AccountNo problem.