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

Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
May 15, 2014

Basically, you can't have an IP on the management interface that overlaps a VLAN subnet. If you were to try to do it in the management GUI but in reverse, assign a VLAN subnet that's in the same space as the management interface, it would actually generate a error message. Assuming you're doing this because you only have one subnet to work with, here are two potential options:

 

  1. You've basically taken a /24 and cut it in half (1-127 and 128-254), so if you were to cut one of those in half, say the internal VLAN, such that the internal and management are on /26 subnets, then that should work. It's probably a huge waste of addresses, but there shouldn't be any overlap.

     

  2. Don't use the management interface for management. You can define a self-IP to allow management traffic. If you were going to do this, you'd probably want to do it on the internal VLAN. Once you've established management access to the self-IP, you can set the management interface IP to something outside the subnet and then disconnect it.