Forum Discussion

sltjr_85808's avatar
sltjr_85808
Icon for Nimbostratus rankNimbostratus
Oct 19, 2007

Specific Service Node Monitoring.

Specific Service Node Monitoring.

 

Does any one use there F5's to load balance NDM Servers? That use services 1364 or 11364? What I am trying to find out is there a way to create Monitor for those services that does not generate error in the NDM Log Directory when the F5 are monitoring them? I am currently using a tcp monitor with the specific service field filled in with *:1364 & *:11364.

6 Replies

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Hi,

     

     

    This might be possible using an external monitor. If you can write a script in Perl or shell which connects to the service, verifies it's available, and returns a value if it's down, you could then reference that script as an external monitor. A quick search for network data mover and perl didn't return anything useful though. Maybe you could capture a tcpdump of an exchange between a real NDM client and then reproduce the request using netcat?

     

     

    SOL7444 (Click here) has details on writing an external monitor. Deb also added some examples in the Advanced config codeshare (Click here).

     

     

    Aaron
  • I am not really familiar with writing script in Perl or Shell???

     

    Do know if there is an Exapmle of one that would perform this type of Monitor

     

    !

     

    [root@ed2lb1-prodio:Active] ~ telnet 172.17.2.11 1364

     

     

    Trying 172.17.2.11...

     

    Connected to 172.17.2.11.

     

    Escape character is '^]'.

     

    ^]

     

    telnet> q

     

    Connection closed.

     

    !

     

    [root@ed2lb1-prodio:Active] ~ telnet 172.17.2.10 1364

     

    Trying 172.17.2.10...

     

    Connected to 172.17.2.10.

     

    Escape character is '^]'.

     

    ^]

     

    telnet> q

     

    Connection closed.
  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Do you get an error on the server when you telnet to the port and then close the connection? How about if you try 'netcat 172.17.2.11 1364' and then close the connection?

     

     

    Basically, you need to figure out a way from the BIG-IP command line to connect to the server and not generate an error. Perl is pre-installed on the BIG-IP. You also have 'bash' for shell scripting. Once you figure out how to connect to the server without generating an application error, you can wrap that process in a script and reference the script in an external monitor.

     

     

    I don't have an NDM server so I can't test this. And in a very quick google search didn't find any type of open source client package that would allow you to establish a connection with an NDM server.

     

     

    Aaron
  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    It looks like you just need to verify the socket is answering. If that's the case, you might want to look at the tcp or tcp_half_open monitor types.

     

     

    I just published a Tech Tip about that yesterday (Click here), and will be covering a couple of other options in the upcoming weeks.

     

     

    I'd first try the tcp type with a send string of just "q", and if that doesn't work try tcp_half_open.

     

     

    HTH

     

    /deb
  • The Send Strings I beleive are the creditentials to get access to wed page. And the Receive Strings are what you would expect to get back if the page works properly. SLT