Forum Discussion
AltostratusAdding a Second Subnet for Virtual Server IP's
Our LTM configuration in our network is as follows. We have an External VLAN and several Internal VLAN's. The External VLAN contains the subnet 1.1.1.0/24. So, the IP's of the virtual servers are in the 1.1.1.0 subnet. We have several Internal VLAN's, for example, one contains the subnet 1.1.4.0/24. So, any nodes behind the LTM will use an IP from 1.1.4.0. So, the flow would be as follows.
VS1 (1.1.1.4) -> Pool (member nodes are 1.1.4.1 and 1.1.4.2) -> Node (1.1.4.1 or 1.1.4.2)
We are running out of virtual server IP's in the 1.1.1.0 subnet. I want to add another subnet for virtual servers, for example 1.1.2.0. What is the best way to configure this on the LTM? Can I add the 1.1.2.0 subnet to the existing External VLAN and create the self IP's (the LTM ports are trunked to our switch so multple VLAN's are allowed)? Do I need to create a separate VLAN for the new subnet? Any other configurations needed?
2 Replies
JT3Nimbostratus
We have a more complicated way to add the vLANs and it's my first time to add a new subnet. I see tagging and external vlans. I see also new subnets on the F5 for self IP and float since we have two Big IPs and HA. Where can I find a step by step procedure since I've never done this before? I added the Self IPs self and float. created a external vlan for new subnet. New vlan showed in the route domain list. Something however is reflecting the new pool with Node in the new subnet not reachable
AneshCirrostratus
You mentioned "the LTM ports are trunked to our switch", so are the interfaces tagged? Then creating a separate VLAN would be sufficient
