#  SAMPLE PARTITION FILE
#
#  When CCC components need to communicate across a firewall that
#  performs ip address translation (NAT), a CCC component must be able
#  to retrieve an ip address of the other component that is valid on its
#  side of the firewall. To support this capability, the location broker
#  namespace is logically divided into partitions with unique partition
#  id's. Partition id's are specified via the KDC_PARTITION environment
#  variable. The partition file is the means to insert appropriate ip
#  address into the location broker namespaces.
#
#  When a CCC component performs a location broker lookup operation, the
#  partition id of its partition will automatically be supplied. The
#  location broker will only return addresses that have been defined for
#  that partition namespace and no other. In effect, the CCC component
#  will only see addresses that are valid for its partition.
#
#  A partition file is a standard text file (like this one) and is
#  defined to the system via the KDC_PARTITIONFILE environment variable.
#  Within this file, each line describes a partition name with its
#  constituent ip address(es) using space delimited tokens. The format
#  is as follows:
#
#        PARTITION-ID  IP.PIPE:nn.nn.nn.nn  IP.PIPE:nn.nn.nn.nn
#
#  The first token on each line is used as a case-insensitive partition
#  id. The partition id can be any alphanumeric string with a maximum
#  length of 32 characters.  Subsequent tokens specified are treated as
#  interface addresses in standard NCS format (address-family:address).
#  For communication across firewalls, only IP.PIPE should be used for
#  address-family.
#
#  Lines beginning with a '#' are treated as comments and are ignored.
#
#  Note: Do not specify a line that starts with an '*' as it might
#        prevent the proper functioning of CCC.
#
############################################################
#  Procedure to edit this sample partition file.
############################################################
#
#  To create a CMS partition file for a typical CCC scenario (CMA/CMW
#  outside of a NAT firewall connecting to a CMS behind the firewall).
#  Do the following:
#
#  1) Replace the "$OUTSIDE-PID$" with the partition id of your CMA/CMW
#  2) Replace the "$OUTSIDE-CMS-HOST-ADDRESS$" with the ip address of
#     the CMS host outside of the firewall.
#  3) Add additional IP.PIPE:nn.nn.nn.nn addresses on a single line for
#     multiple Network Interface Cards (NICs) as in the format above.
#     Separate entries with 2 spaces.  Lines can be continued by placing
#     a backslash ('\') char at the end of the line.
#  4) Delete the leading "#" on the line to uncomment it.  The partition id
#     must begin in the first column of the line.
#
##############################################################################
#$OUTSIDE-PID$  IP.PIPE:$OUTSIDE-CMS-HOST-ADDRESS$
