PMDF Installation Guide
Tru64 UNIX Edition


Previous Next Contents Index


Chapter 15
PMDF-XGS Example Configuration

Figure 15-1 Sample PMDF-XGS Site EXAMPLE.COM


Figure 15-2 through Figure 15-4 show an example of configuring a PMDF-XGS gateway at EXAMPLE.COM on node naples, and Example 15-1 shows a corresponding checklist file. The sample site EXAMPLE.COM, shown in Figure 15-1, has a PMDF mailhub system, naples, and has PC-LAN based cc:Mail users and WordPerfect Office users connected through PMDF-LAN and considered to be in the domains ccmail.example.com and wpo.example.com, respectively. EXAMPLE.COM also has connections to the Internet over TCP/IP. EXAMPLE.COM has an OS/2 system, with TCP/IP name bridge.example.com and SNADS name PMDF, that will act as the transport bridge between the SNADS side and the PMDF side. EXAMPLE.COM's SNADS nodes are BLUE, INDIGO, AZURE, and LAPIS, which will be known as blue.example.com, indigo.example.com, azure.example.com, and lapis.example.com, respectively, to the non-SNADS (e.g., Internet) world.

For this example, PMDF-MTA, PMDF-LAN, and PMDF-XGS have been installed on naples. PMDF-MTA and PMDF-LAN have been configured previously, during a separate configuration session on naples. The SNADS nodes have been configured to know about the PMDF-XGS transport bridge and the naples system. The PMDF-XGS transport bridge component has been installed and configured on the transport bridge system, and is using the default TCP/IP ports for communicating with the PMDF system naples.

Remember that the values entered in this sample are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual configuration.


Previous Next Contents Index