For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

CP16's avatar
CP16
Icon for Nimbostratus rankNimbostratus
Dec 15, 2017

Changing Virtual Server type from Internal to Standard

We have a couple Virtual Servers for some reason are type "internal". When we first went through PS they instructed us to create the servers as standard with the the IP included and then change the t...
application delivery
LTM
security
Simon_Blakely's avatar
Simon_Blakely
Icon for Employee rankEmployee
Dec 18, 2017

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.