Forum Discussion
NimbostratusCANNOT ACCESS F5 VIRUAL SERVER GUI
NimbostratusHello Paulius,
Thanks for the prompt response.
Do you mean a screenshot of the virtual server configuration page on the GUI? I can share that when next I connect w/ the client.
As for the tcp dump you stated above, is that the format of the command I will run as you posted? And I'm guessing that can be done via putty ssh into the management address? I will run that when next I connect with the client.
However, I should also note that the client does not want to change the gateway of the nodes (servers) to the F5 IP as this will mean loss of connection to the server. Is this a must to do? As this is a 2-arm configuration? Or must it be changed to 1-arm?
I look forward to your response.
MVPAdeyinka The following are your questions and my answers.
1q. Do you mean a screenshot of the virtual server configuration page on the GUI?
1a. A screenshot would work of each piece but a CLI output would be even better.
2q. As for the tcp dump you stated above, is that the format of the command I will run as you posted? And I'm guessing that can be done via putty ssh into the management address?
2a. The tcpdump above is the exact format and the only piece you would have to swap is the < > and what is between them.
3q. However, I should also note that the client does not want to change the gateway of the nodes (servers) to the F5 IP as this will mean loss of connection to the server. Is this a must to do? As this is a 2-arm configuration? Or must it be changed to 1-arm?
3a. As long as you have SNAT enabled, preferrably snat pool list rather than automat you should be fine without any gateway changes. If you aren't going to have the F5 as the gateway you should just configure it in one-arm mode instead of in path. If you intend to eventually make the F5 the gateway then you can leave it in path.
