Endpoint Protection

 View Only
Expand all | Collapse all

Will SEPM update globallist.xml with the new ip address if GUP changes IP

  • 1.  Will SEPM update globallist.xml with the new ip address if GUP changes IP

    Posted Jun 27, 2011 02:51 AM

    We currently use hostnames for GUP, will the globallist.xml automatically get updated with the IP address if the IP of the GUP has changed ? I believe, the SEPM looks at the GUP in its group check its IP and then update the globallist.xml . Can someone clarify this for me please ?



  • 2.  RE: Will SEPM update globallist.xml with the new ip address if GUP changes IP

    Posted Jun 27, 2011 03:22 AM

    yes



  • 3.  RE: Will SEPM update globallist.xml with the new ip address if GUP changes IP

    Broadcom Employee
    Posted Jun 27, 2011 06:29 AM

    Hello,

    This is expected behaviour in multiple GUP environment.

    Whatever you have mentioned is correct.



  • 4.  RE: Will SEPM update globallist.xml with the new ip address if GUP changes IP
    Best Answer

    Posted Jun 27, 2011 08:34 AM

    The SEPM updates the list of GUPs to reflect which GUPs meet the configured criteria every time the GUP checks in.

    The SEPM stores this list of GUPs in the following locations:
     

      32bit Servers
      C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\gup

      64Bit Servers
      C:\Program Files(x86)\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\gup.


    This information is also stored in a database table. The file, globallist.xml, is protected from tampering via checksum.
    The list is published with GUP IP addresses in ascending order.

    The clients run a routine called GetGUPList (viewable in sylink.log) that gets the current list of GUPs whenever they need a content update.

    The client applies a “Network Subnet Match” filter to the IP address information in the GUP list. This filter is constructed using each of the clients network interfaces to compare subnet masks.
    Any GUPs with a subnet mask matching the clients are placed in a new local GUP list created by the client. This new 'local' list is stored in RAM only.

    Note: The local GUP list is in ascending order which means that a predefined GUP will always be last on the list, preventing unnecessary WAN traffic.

    Clients will receive the list of GUPs in a file called globallist.xml.