NAT not working after software update
Hi there,
long time ago, that I had a question here.
I'm currently working on a F5 project, where we have to perform a hardware refresh including a software update.
The old environment consists of two LTM-pairs, one without Route Domains and the second with two Route Domains. The old platform is running on 10.2.4.
The new environment consists only of one LTM-pair now with three Route Domains (all consolidated into one cluster). The new platform is running on 14.1.1.
All VS, NATs and floating-IPs are identical, means we first isolated the old environment (by disabling the tmm-interfaces) and then enabled the new environment.
During migration our pain point was, that the configured NATs were not working correctly and I'm now wondering of there is maybe a change in behavior or if we made something wrong. As an example, we saw the following result with tcpdump.
Configured NAT xxx.189.21.151 origin 192.168.35.51
Old working environment:
03:22:10.884644 IP xxx.189.5.152 > 192.168.35.51: ICMP echo request, id 15796, seq 980, length 64
03:22:10.884920 IP xxx.189.21.151 > xxx.189.5.152: ICMP echo reply, id 15796, seq 980, length 64
New not working environment:
03:21:14.934663 IP xxx.189.5.152 > xxx.189.21.151: ICMP echo request, id 15796, seq 125, length 64 in slot1/tmm0 lis=
03:21:15.940626 IP xxx.189.5.152 > xxx.189.21.151: ICMP echo request, id 15796, seq 126, length 64 in slot1/tmm0 lis=
So from this output it looks like, that the ICMP echo request will not correctly translated to the origin address.
Is this true or how can I interpret this? How can I verify that NATing is correctly working? Or do I have to check any additional (new) settings?
Or is this maybe any kind of ARP-issue (how can I force the new LTMs to propagate its new MAC-addresses)?
In case you require more details about the setup, please let me know.
Thank you!
Ciao Stefan :)