Forum Discussion

pcoelho_259389's avatar
pcoelho_259389
Icon for Nimbostratus rankNimbostratus
Mar 09, 2017
Solved

Unable to connect to anything from within SSH terminal

I tried to validate an LDAP monitor query by connecting through putty and running it from the console. But was unable to establish a connection to the LDAP server. I tried ping, unable to connect. So, I tried pinging the IP of other servers and the two F5's. Tried traceroute and even a simple curl GET on a pool. (7) couldn't connect to host. Even tried creating a passthrough fastforwarding(IP) virtual server and trying those tests again, no joy.

 

I'm a bit of a noob and the F5 was setup years before I touched it. Before playing with the LDAP monitor I want to make sure I can test from the console. What do I need to do so I can get to the point that I can ping and execute curl commands from an SSH terminal?

 

running software version: 12.1.0

 

application delivery
BIG-IP
LTM
  • pcoelho_259389's avatar
    pcoelho_259389
    Mar 10, 2017

    Answer to the initial question was to use the "rdsh" command to specify the id of the route domain. This made it possible to ping and execute ldapsearch from within the SSH console.

     

    the answer for the sub question why doesn't curl connect, was "curl is the wrong tool." If you are connected to the SSH console remotely, TMSH is available, there is no need to use Curl to make a remote REST call from the remote terminal.

     

2 Replies

Sort By
  • Leonardo_Souza's avatar
    Leonardo_Souza
    Icon for Cirrocumulus rankCirrocumulus
    Mar 09, 2017

    You should be able to test the access from the F5 to the backend server using the command line.

     

    Is the server in the same network as the F5? If not, do you have routing to the server?

     

    If you use a TCP monitor, does it marks the pool member green?

     

    Do you use route domains? If yes, you need to some commands before.

     

    About route domain:

     

    https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/tmos-routing-administration-13-0-0/8.html

     

    https://support.f5.com/csp/article/K13472

     

  • pcoelho_259389's avatar
    pcoelho_259389
    Icon for Nimbostratus rankNimbostratus
    Mar 10, 2017

    Answer to the initial question was to use the "rdsh" command to specify the id of the route domain. This made it possible to ping and execute ldapsearch from within the SSH console.

     

    the answer for the sub question why doesn't curl connect, was "curl is the wrong tool." If you are connected to the SSH console remotely, TMSH is available, there is no need to use Curl to make a remote REST call from the remote terminal.