TCPWARE WITH IP ADDRESSWORKS ============================ Using TCPware Servers ===================== You can use the DNS and DHCP servers from TCPware version 5.4 with IP AddressWorks version 1.1 if you are running OpenVMS version 5.5-2 or later. The information in this Read Me describes what you need to do to use TCPware with IP AddressWorks on an OpenVMS system: o Configure the IP AddressWorks Server Manager. o Run or restart the TCPware DNS, DHCP, and SNMP servers and the Server Manager. Using IP AddressWorks with TCPware ================================== TCPware v5.4 contains components that work with IP AddressWorks v1.1. These TCPware components are the Domain Name Server (DNS), Dynamic Host Configuration Protocol server (DHCPD), Simple Network Management Protocol server (SNMP), and the Server Manager. The Server Manager is the interface between the LDAP server and both the IP AddressWorks DNS server and the DHCP server. It also provides an interface between both the Management Interface (MI) and the Command Line Interface (CLI) clients and the DNS server and the DHCP server. To use IP AddressWorks with the TCPware DNS or DHCP servers on your OpenVMS system, you need to: 1 Configure the IP AddressWorks Server Manager on OpenVMS. 2 Run the DNS, DHCP, or SNMP servers (or all servers) if they are not already running. Note: If you are running OpenVMS v5.5-2, you need to install the DEC C/C++ Run-Time Components, available in the TCPware kit as follows: DIRECTORY [VAX55_DECC_RTL] AACRT060.A CRT060.RELEASE_NOTES CRT060_REF_INST.TXT Contact your OpenVMS sales representative for Compaq documentation. Importing Server Configurations =============================== Unless you have already loaded your data into IP AddressWorks, you need to import the DNS and DHCP configuration files. 1 Enabling the Server Manager =========================== You can configure the IP AddressWorks Server Manager for use on your OpenVMS system with or without TCPware running using the command procedure TCPWARE:SM_CONTROL.COM. Configure the Server Manager as described in the next table. If the Server Manager is running when you perform these steps, then the new parameter values take effect immediately. 1 Start the Server Manager configuration by entering the following at the DCL prompt: @TCPWARE:SM_CONTROL CONFIG The CONFIG parameter stores the information needed to access the LDAP database. The following prompt appears about enabling the Server Manager: "Do you want to enable the IP AddressWorks Server Manager? [YES]" 2 Press to accept the default or enter "NO" to not enable the Server Manager at this time. The current values of the configuration parameters in the configuration file appear next on your screen and you are queried for a new value for each parameter. 3 Accept the current value for each configuration parameter or supply a new value (if you do not supply a new value, the current value is used) when prompted. The configuration parameters are: LDAPSERVER This is the address or full domain name of the LDAP server system. SERVERPORT This is the port number of the LDAP server; this value should be 389 (the default) in most situations. PARTITION This is the name of an IP AddressWorks partition. USERNAME This is the log in user name to access the LDAP database. PASSWORD This is the log in password to access the LDAP database. SERVERID This is the name of the DNS server and DHCP server. It is optional to change this parameter value; usually you can accept the default host name and domain. DELAYINTERNAL This is the length of time you want the batching transaction to delay before processing. The default is 5 seconds. DELAYLIMIT This is the maximum length of time you want the batching transaction to delay before processing. The default is 64 seconds. ENABLELOG This enables any log entry to be written to a file. Also, an OPCOM broadcast is done for error messages. The default is FALSE. 2 DEBUG This value specifies whether debug messages are written to the Server Manager log file, TCPWARE:IPAW_SM.LOG. It is optional to change this value. Enter ON or accept the default of OFF. OPCOM_LOG This controls whether OPCOM of error messages is done. The default is FALSE. ENABLELOG must be ON for this to work. The configuration parameters are needed to access the IP AddressWorks data. These parameters provide the same information that is required on the Server Manager tab of the IP AddressWorks Control Panel. In particular, the Lightweight Directory Access Protocol (LDAP) server host, user name and password, and port number need to be correctly configured and must match the configuration of the LDAP database. If you move the IP AddressWorks LDAP server, or change the user name or password after you configure the Server Manager, you need to change the appropriate parameters. The configuration file (TCPWARE:IPAW_SM.CONF) contains the configuration information, the date of the most recent modification, and the user name of the person who made the changes. Configuring the SNMP IP AddressWorks Service ============================================ The IP AddressWorks components use SNMP to communicate, therefore you need to configure an SNMP subagent for this to happen. Refer to the SNMP Agent configuration procedure described in the TCPware for OpenVMS "Installation and Configuration Guide," Chapter 4, for a complete configuration example. Use the following to configure the SNMP subagent: 1 Start the SNMP Agent configuration. Enter: @TCPWARE:CNFNET SNMP Information appears on the screen about SNMP, followed by the prompt: "Do you want to activate the SNMP agent on this host [NO]:" 2 Reply Yes to activate the SNMP agent. Information appears on the screen about configuring the SNMP SMUX service, followed by the prompt: "Do you want to activate the SNMP SMUX service on this host [NO]:" 3 Respond to the SMUX service prompt as you need. SMUX is not required to use IPAW with TCPware. Information then appears on the screen about configuring an SNMP subagent, followed by the prompt: "Do you want to configure subagent(s) on this host [NO]:" 4 Respond yes to the prompt to configure a subagent (which is a shareable image). You are then prompted to enter the name of the subagent: "Enter the name of the shareable image without .EXE:" 5 Enter the following subagent name: PSC_SNMPC_TCPWARE 3 Running the IPAW-enabled TCPware Servers ========================================= For the IP AddressWorks Management Interface and LDAP server to communicate with the DNS and DHCP servers (using SNMP), you need to run the Server Manager process. When the servers or SNMP start, they verify whether the Server Manager is enabled, and then establish communication with the Server Manager. The usual way to run the TCPware servers is by starting TCPware. If TCPware has already been started, then follow this next procedure. 1 Start the IP AddressWorks Server Manager process: @TCPWARE:SM_CONTROL START 2 After configuring the IP AddressWorks SNMP subagent, you need to stop and restart the SNMP agent so the changes can take effect. a Stop the SNMP agent process: @TCPWARE:SHUTNET SNMP b Start the SNMP agent process: @TCPWARE:STARTNET SNMP 3 Restart the DNS and the DHCP servers. Enter at separate DCL prompts: $ @TCPWARE:RESTART DNS (for the DNS server) $ @TCPWARE:RESTART DHCP (for the DHCP server) Additional Parameters ===================== There are additional parameters, listed in the following table, you can use to work with IP AddressWorks, the Server Manager, and TCPware. Enter the command @TCPWARE:SM_CONTROL followed by the parameter at the DCL prompt. When you want to... Enter this parameter... --------------------------------------------------------------- Enable IP AddressWorks. ENABLE Disable IP AddressWorks and prevent DISABLE the Server Manager process from starting. Start the Server Manager, if IP START AddressWorks is enabled. Stop the Server Manager. STOP Stop the current Server Manager RESTART process and start a new process. Note: There is a slight delay while the current process exits before the new one starts. 4