4 Replies Latest reply on Nov 15, 2010 4:01 PM by andymease

    Linux wakeup port

      Has anyone else used the Linux agent (4.5.0.1470) with a non-standard wakeup port?  It seems the agent doesn't ever report that port back and it stays at 8081.  All wakeups from ePO then fail...

       

      Andrew

        • 1. Re: Linux wakeup port

          We're using 4.5.0.1470 with a non-standard port.  The port [incorrectly] shows up in ePO as 8081, but the wakeup call works fine.

          • 2. Re: Linux wakeup port

            Unfortunately this is what happens when I send one (name and IP replaced):

             

            11/11/10 5:13:15 PMStarting agent wakeup for SERVER
            11/11/10 5:13:15 PMWaking up agent SERVER using DNS name
            11/11/10 5:13:15 PMUnknown error contacting agent
            11/11/10 5:13:15 PMWaking up agent SERVER using NetBIOS
            11/11/10 5:13:15 PMUnknown error contacting agent
            11/11/10 5:13:15 PMWaking up agent at IP address X.X.X.X
            11/11/10 5:13:15 PMUnknown error contacting agent
            11/11/10 5:13:15 PMWakeup agent failed
            11/11/10 5:14:33 PMExpired

             

            The DNS name of the server is resolvable as well...

             

            Andrew

            • 3. Re: Linux wakeup port

              Can you telnet from the ePO server to the agent over the wakeup port?  You should get back a blank screen or garbled text (anything but "Connect failed").  If not, it could be a firewall issue -- or the agent isn't really listening on the port that you think it is.

               

              Else, I'd look for any sign in the agent log that it's receiving communication (default at /opt/McAfee/cma/scratch/etc/log).

              • 4. Re: Linux wakeup port

                Yeah the ports are open but the wakeup is not being sent on the correct port...I'll be entering an SR for this.


                Andrew