Forum Discussion
NimbostratusChanging Virtual Server type from Internal to Standard
EmployeeHave 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.
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.
