Changing Virtual Server type from Internal to Standard

interesting question, can't say much about 1, if support says it is the case i would believe them. you can always try to see if it fails. which version is this about btw?

 

as for 2 that is annoying, can add internal fine with TMSH, but removing seems harder. hopefully someone else can give you the solution.

 

There is currently no way (using tmsh or iControl) to correctly modify the type of a virtual server (for certain combinations of virtual type). This includes attempting to change an internal virtual to a standard virtual.

 

There is a internal change request to have this addressed in an unspecified future release.

 

I'd be interested to know the specific error that prevents the config from loading following an upgrade.

 

As far as I am aware, you should only use an internal type for ICAP profiles.

 

Thanks for the info. We are now on 12.1.2 hf2.

 

I worked with support again after the upgrade and the engineer took the information because he never experienced this problem either.

 

If we forget to change the type to standard before an upgrade the system will boot up and I can tell the problem exists because my AD credentials won't work and am forced to use my local login. When you attempt to load the sys config the following error is received

 

"Virtual Address /prod/0.0.0.0 in partition prod cannot be referenced by Virtual Server /uat/v-sp-uat-pwp-owa-all in partition uat Unexpected Error: Loading configuration process failed."

 

These virtual servers are hopefully going away soon but I appreciate the feedback.

 

Have you tested to see if those virtuals work when set to Standard?

 

Do they work as expected?

 

I can see no reason for them to be configured that way.

 

The config loading problem is that a virtual of type internal has a sort of template applied to it - for an internal virtual, this sets the destination to 0.0.0.0, overwriting the configured destination. It also sets the listening vlan to none so that no external traffic hits the vip - the traffic should be directed to the virtual via an irule (using the virtual command) or an ICAP profile.

 

The partition that your virtual is defined in does not have a 0.0.0.0 virtual address, so a 0.0.0.0 virtual address in another partition is selected, which is an invalid choice causing the config load issue.

 

K14675: Error Message: 01070726:3: virtual server in partition cannot reference virtual address in partition

 

As detailed in:

 

K15819: Overview of the internal virtual server

 

the internal virtual server is only intended to be used to configure ICAP Content adaption, and has no other purpose. I really do not understand why this has been configured in this way.

 

As you seem to be getting rid of these virtuals, I'd recommend that you do so as soon as possible. This should resolve your future upgrade issues.

 

Thanks Blakely.

 

I don't recall exactly why they set this up this way but if you change it to standard it does break so as you suggested I will be pushing to get rid of these ASAP

 

Hello, To change a VS to FastL4:

 

mplaksin@(f-f5)(cfg-sync In Sync)(/S2-green-P::Active)(/xx)(tmos) modify ltm virtual nat8 profiles replace-all-with { fastL4 }

 

To change VS to Standard: mplaksin@(f-f5)(cfg-sync In Sync)(/S2-green-P::Active)(/xx)(tmos) modify ltm virtual nat8 profiles replace-all-with { tcp { context all } }