46 CHAPTER 2: ACCESSING THE CENTRAL MANAGER AND GLOBAL DIRECTORY
In the previous section (Manually Resynchronizing the Global Directory),
the global directory at the Boston office was resynchronized. To manually
load this updated global directory database, log on to the primary VCX
server in Boston using the cworks account and enter these commands:
cd /opt/3com/VCX/vcxdata/globaldir/bin
./forceGDBLoad.pl
Uploading a User
Directory to Multiple
Regional Offices
You can push a user directory to all other configured regional offices so
that data upload does not need to be performed individually at all the
regional offices that have been added using option 101.
For example, Boston, Chicago, and Los Angeles have each been
configured using option 101 so that users at each site have a global
directory that includes users at the other two sites. If the Boston office
adds or deletes users, the Chicago and Los Angeles offices would have to
either automatically or manually resynchronize their user directory
databases. Alternatively, the Boston office can upload its changes to both
Chicago and Los Angeles.
To upload the user directory to all other deployed regional offices:
1Log on to the primary VCX server in Boston using the cworks account and
enter these commands:
cd /opt/3com/VCX/vcxdata/globaldir/bin
./config.sh
2At the prompt, enter 107.
Boston’s global directory is uploaded to all other configured peer regional
offices (in this example, Chicago and Los Angeles) immediately.
3Press Enter.
You are returned to the main menu.
Global Directory
Requirements for
Replicated Regions
with Branch Offices
This section describes global directory configuration requirements when
database replication is enabled between two regions, and each region
includes branch offices.
If replication is enabled between two regions, the entries in the global
directory depend on your location.