Forum Discussion
nitass_89166
Dec 29, 2013Noctilucent
i did a bit test (below) but it did not work. so, it seems you have to modify configuration file directly (i.e. bigip_base.conf and bigip.conf) and then force mcpd to reload the configuration.
existing pool
root@ve10(Active)(tmos) list ltm pool foo
ltm pool foo {
members {
200.200.200.101:http { }
}
}
existing connected subnet
root@ve10(Active)(tmos) list net self 200.200.200.16/24
net self 200.200.200.16/24 {
allow-service default
vlan internal
}
new vlan
root@ve10(Active)(tmos) create net vlan newvlan interfaces add { 1.2 { tagged } }
new selfip
root@ve10(Active)(tmos) create net self 222.222.222.16/24 vlan newvlan allow-service default
new route but error
root@ve10(Active)(tmos) create net route 200.200.200.0/24 gw 222.222.222.254
01070666:3: Static route duplicates Self IP 200.200.200.0 / 255.255.255.0 implied route
delete selfip but error
root@ve10(Active)(tmos) delete net self 200.200.200.16/24
01070605:3: Cannot delete IP 200.200.200.16 because it would leave a pool member (pool foo) unreachable.
- Frankie_John-LeSep 01, 2014NimbostratusChange the Subnet Mask on the Self-IP from a /24 to a /32 (255.255.255.255). This will then allow you to delete the Self-IP from the configuration
- epJun 14, 2016NimbostratusThis was perfect, exactly what I needed. Thanks Frankie John-Lewis!
- swtbeerJun 22, 2016NimbostratusGreat Frankie !! It worked for me.
- Siva_SrinivasanMar 16, 2017Nimbostratus
I tried this and I could delete the Self-IP, but the LTM doesn't seem to be able to communicate to any of the Real Servers which were reachable by the Directly connected Internal VLAN. That subnet is now routed via the External VLAN. Checked the Upstream Routers and the Big-IP's External and Internal VLANs are directly connected Networks so no routes are needed there. Am I missing anything.