Forum Discussion
Jason_Keating
Nov 14, 2010Altostratus
Hi 10.162.134.183
I was a little confused about it to, so I read the TMOS guide again and again on Self IP's trying to determine if I needed one.
According to the text I only want a Self IP for a VLAN if I want to route to destination servers based on self ip (as a means to identify VLAN and therefore interface of egress), I have a default gateway for all destinations. Or for SNAT'ing thereby ensuring responses are routed back through the LTM, I am snatting most of my traffic with everything coming back to
Here is my config, I can add self ip's but did not see anything stating I must.
Thanks for having a look
stp instance 0 {
interfaces {
1.1 {
external path cost 20000
internal path cost 20000
}
1.2 {
external path cost 20000
internal path cost 20000
}
}
vlans {
internal_A
internal_B
internal_C
}
}
vlan internal_A {
tag 4094
interfaces 1.1
}
vlan internal_B {
tag 214
interfaces tagged 1.2
}
vlan internal_C {
tag 645
mac masq 40:017:B2:25:44
interfaces tagged 1.2
}
self 10.162.134.181 {
netmask 255.255.255.0
vlan internal_A
allow default
}
self 10.162.134.183 {
netmask 255.255.255.0
unit 1
floating enable
vlan internal_A
allow default
}
route default inet {
gateway 10.162.134.1
}
snatpool myfloating_SNAT {
members 10.162.134.183
}
virtual virtual_1 {
snatpool myfloating_SNAT
pool pool_1
destination 10.162.134.187:http
ip protocol tcp
profiles {
http {}
tcp {}
}
}
virtual virtual_2 {
snatpool myfloating_SNAT
pool pool_2
destination 10.162.142.2:https
ip protocol tcp
vlans internal_B enable
}
virtual virtual_3 {
snatpool myfloating_SNAT
pool pool_3
destination 10.162.146.173:ldap
ip protocol tcp
vlans internal_C enable
}