Learn F5 Technologies, Get Answers & Share Community Solutions Join DevCentral

Filter by:
  • Solution
  • Technology
Answers

adding new Vlans

I'm having an issue with a new vlan I added.

We currently have a 1600 HA pair. I added the new Vlan to the Vlans under "Network" I added it to the Trunk The Vlan is added to the switch also. I added the Vlan to the Internal_IP_Forwarding server. I added the floating IP and Self IP addresses for the new Vlan I added a new server to this new 10.0.151.0/24 network. I can ping my workstation (on a different network) and I can also ping that server from my workstation but I'm unable to connect to it. I unable to telnet to 3389 and can't connect to any services running on that server. The server's gateway is set to the floating IP of the F5.. just like the other working Vlans we have on this F5

I'm trying to mirror the same setup as the Internal_Big-ip network that is currently setup. Are there any steps I'm missing? I ran a tcp dump from the F5 while trying to telnet to 3389 from my workstation to a server running @ 10.0.151.10. Viewing the log I see there are TCP 3WHS rejected. See the image below. 10.0.144.106 is my local IP Image Text

0
Rate this Question

Answers to this Question

placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

I don't see a SYN packet in the capture. Is there another route from your workstation to the 10.0.151.0 network?

If the SYN did not come through the BIG-IP it will send a reset on the return packets. This behavior can be changed by enabling loose initiate in the fast L4 profiles assigned to the forwarding virtual server, or correct the asynchronous routing.

0
placeholder+image
USER ACCEPTED ANSWER & F5 ACCEPTED ANSWER

Thanks for that help. It did turn out to be a routing issue. After looking at everything again I needed both the VIP Vlan and Node Vlan in the forwarding server. We also removing some interfaces at the switch also. 3 way handshakes are working!

0