3 Replies Latest reply on May 12, 2013 1:07 PM by jwierzchowski

    node unreachable/unmanaged

    jwierzchowski

      Hey Everyone,

       

      Thisis my first post in this forum. I recently took over EPO at my company. I amgetting the hang of some things. I am a bit stumped with this one though. Wehave a number of domains, with each having its own container in the systemtree.

      In a particular container Icame across one node which shows as unmanaged. When I look on the computer(win2k8r2) I see agent is installed. When I try to ping it, it showsunreachable. I can ping it by fqdn from the epo server. The issue if found isthat epo is not using fqdn but the netbios name to try to reach it.

      I also tried wake up agent forthe system since it has an agent, which runs successfully, and log says thatthe properties are updated, but It still shows unmanaged.

       

      The server log excerpt is asfollows: (one for server that works the other for the non-working one)

       

      5/11/13 10:25:03 PM  Waking up agent AS003 through Agent Handlerca2av001.mgmt.local. 

      5/11/13 10:25:03 PM  Waking up agent as003.v052.os33.net using DNSname 

      5/11/13 10:25:03 PM  Wakeup agent was successful 

      ….

      /11/13 10:24:32 PM  Waking up agent AS004 through Agent Handlertx2av101.mgmt.local. 

      5/11/13 10:24:32 PM  Waking up agent AS004 using NetBIOS 

      5/11/13 10:24:32 PM  Unable to resolve address of remotesystem 

      5/11/13 10:24:32 PM  Wakeup agent failed 

      5/11/13 10:24:33 PM  Waking up agent AS004 using NetBIOS 

      5/11/13 10:24:33 PM  Wakeup agent was successful 

        • 1. Re: node unreachable/unmanaged
          mbauman8

          hi

           

          can you check if agenthandler Handlertx2av101.mgmt.local. can resolve AS004 ( as Handlerca2av001.mgmt.local. can do it with as003.v052.os33.net )

           

          I think the DNS resolution is you Problem.

           

          secund thing I woud test is if the ports are open to agenthandler / ePO

           

          please give feedback of this first

          martin

          • 2. Re: node unreachable/unmanaged
            jwierzchowski

            can't believe i didn't see that! that makes perfect sense. I need to figure out what controlls which superagent is used, and use the ca one. Will post update when I figure it out.

            • 3. Re: node unreachable/unmanaged
              jwierzchowski

              quick correction this was not the server log, this wa the server task log in the console

               

              The container has the right handler configured, the server is in the right container. for some reason its still using the wrong agent handler. additionally it shows succesful... but the system tree still shows as unmanaged:

              5/12/13 12:01:05 PM  Waking up agent AS004 through Agent Handler tx2av101.mgmt.local. 

              5/12/13 12:01:05 PM  Waking up agent AS004 using NetBIOS 

              5/12/13 12:01:05 PM  Unable to resolve address of remote system 

              5/12/13 12:01:05 PM  Wakeup agent failed 

              5/12/13 12:01:18 PM  Waking up agent AS004 using NetBIOS 

              5/12/13 12:01:18 PM  Unable to resolve address of remote system 

              5/12/13 12:01:18 PM  Wakeup agent failed 

              5/12/13 12:01:31 PM  Waking up agent AS004 using NetBIOS 

              5/12/13 12:01:31 PM  Unable to resolve address of remote system 

              5/12/13 12:01:31 PM  Wakeup agent failed 

              5/12/13 12:01:37 PM  Waking up agent AS004 using NetBIOS 

              5/12/13 12:01:37 PM  Unable to resolve address of remote system 

              5/12/13 12:01:37 PM  Wakeup agent failed 

              5/12/13 12:01:41 PM  Waking up agent AS004 using NetBIOS 

              5/12/13 12:01:41 PM  Wakeup agent was successful 

               

              ...

              so i uninstalled the agent manually, deleted the node... and re synchronized the group... and now it shows as managed... but i dont see agent in installed programs now!

              so i reboot and delete the node from the directory, re sync and see it as unmanaged, im deplying agent and selected the right super agent for deployment.

              the task completed succesful... but still showing unmaged. ran wake up agent, which failed as expired, but now seeing as managed and deplying vse 8.8, which succeeded.  running wake up agent again which completed real quick, and now seeing vse 8.8 as isntalled. Thanks for the help again!

              I guess there are some nuances which i have to figure out.