Server Management Suite

 View Only
  • 1.  agentless port check

    Posted Jan 07, 2014 10:40 AM

    Good morning.

    I am trying to configure an agentless/external SSH availability check for our environment. This serves dual purpose: if the port is open but times out or actively refused then the host is up but has issues; if the port is unreachable (as in host is not on the network) then the host is down and needs investigation.

    The only problem is that I can't get it to behave properly. I cloned a generic port open metric and pointed it at 22, interval is 10min, timeout is 2min, thread is 'status poll'. Metric evaluation is set for 'all' aggregation, no statistics, condition set for 'is not equal to' and a status of 'open'.

    So far out of 250 hosts it seems about 80% functional - as there are alerts being generated for a good 30 or so hosts where:

    • I know ssh is alive and running just fine
    • the altiris server itself is able to access that network segment
    • none of the client systems use firewall/filtering to block traffic

    Looking through the logs of the systems with a constant alert, there are signs of ssh connections being opened by the Altiris server and yet the alert still comes up. What am I missing?



  • 2.  RE: agentless port check

    Broadcom Employee
    Posted Jan 08, 2014 04:43 AM
      |   view attached

    Hi Norman-McLane,

    I see that you're using a 7.5 release build.

    Try to use this an agentless monitor policy which will monitors '22' port (I've attached it)

    Import this attached agentless policy on your server and include 2 different Linux servers where:

    • 1st Linux server has SSH 22 port closed
    • 2nd Linux server has SSH 22 port opened

    To make sure that rule will be correctly triggered and only 1 alert will be raised in Event Console only for 1st Linux Server, since it has 22 port closed.

    Thanks,

    IP.

     

    Attachment(s)