
PROBLEM: (LACCH0001, 86076) (PATCH ID: TCR520-008)
********
This patch fixes multiple networking issues within a cluster environment:
  - cluster member loses connectivity with clients on remote subnets
  - aliasd not handling multiple virtual aliases in a subnet and/or IP
    aliases
  - allow cluster members to route for an alias without joining it
  - aliasd writing illegal configurations into gated.conf.memebrX
  - default route not being restored after network connectivity issues
  - fix a race condition between aliasd and gated.
  - fix a problem with a hang caused by an incorrect /etc/hosts entry


PROBLEM: (88980) (PATCH ID: TCR520-037)
********
Fix to aliasd_niff to allow EVM restart


PROBLEM: (90026) (PATCH ID: TCR520-019)
********
Enablers for Huron Packaged Database Solution


PROBLEM: (BE_G03730/QAR) (PATCH ID: TCR520-195)
********
The aliasd daemon will now include interface aliases when determining
whether or not an interface is appropriate for use as the ARP address
for a cluster alias when selecting the proxy ARP master. Prior to this
change, only the interface address was used in making this determination.


PROBLEM: (HPAQ31W0P) (PATCH ID: TCR520-196)
********
It was possible that with multiple members booting simultaneously that
aliasd would become deadlocked when trying to select the proxy ARP
master for cluster aliases. As a result, some aliases could become
unreachable since there would be no proxy ARP master.


PROBLEM: (92178) (PATCH ID: TCR520-182)
********
Fix for aliasd message "NIFF parameters for interface are too lax".


PROBLEM: (85864) (PATCH ID: TCR520-273)
********
In a cluster member where there is at least 
one cluster alias is configured to be virutal 
(virtual=t) without subnet mask specified, if
all interfaces are down, aliasd will coredump.


PROBLEM: (95652) (PATCH ID: TCR520-274)
********
For command:

         cluamgr -r enable=ee0

aliasd ignores the requested interface.  It purges
all interfaces from the excluded_interfaces list.
Thereby, all interfaces will be enabled instead of
just enabling the requested interface.

Besides, while purging the excluded_interfaces, 
aliasd just free the pointers in the excluded_interfaces.
It does not NULL out the correspondent entry of the
excluded_interfaces array.  Other parts of the aliasd
continues to use these pointers.  Unexpected results 
will occur.

Another problem is that for command

          cluamgr -r disable=ee0

aliasd would simply allocate a buffer to hold this
requested interface and place it in the excluded_interfaces
without checking whether the list already has this
interface.  This also will cause undesirable results.


PROBLEM: (TKT448727, HPAQG25RW, DE_G06830, TKT466559) (PATCH ID: TCR520-277)
********
       When an interface goes away, NIFF_DOWN event triggers
       the deletion of all addresses of that interface.  As
       a result, all routes going through that interface are
       also removed.  When that interface comes back up 
       again, all related addresses are restore.  However,
       all static routes are forever gone.  This fix restores
       static routes described in the /etc/routes.


PROBLEM: (96098, BE_G06840) (PATCH ID: TCR520-269)
********
     In some rare situation, gated forked off a child process.  There
     were more than one gated process.  Since kill_gated() only looks
     for it once, it won't be able to find the other one to clean 
     up.



