| Previous | Contents | Index |
The following is sample output for configuring the domain:
HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: 1
DOMAIN Configuration
Enter Internet domain:
|
After you enter the domain name, the display resembles the following:
DOMAIN Configuration Enter Internet domain: sqa.tcpip.zko.hp.com Communication domain updated in configuration database |
The interface and address menus allow the configuration and management of both the permanent database as well as the live system. The menu supports multi-homed systems, which have multiple addresses and/or interfaces. The menus are context sensitive, so the menu options change according to the state of the system.
The following is sample output for configuring the Internet interface:
Checking TCP/IP Services for OpenVMS configuration database files.
HP TCP/IP Services for OpenVMS Configuration Menu
Configuration options:
1 - Core environment
2 - Client components
3 - Server components
4 - Optional components
5 - Shutdown HP TCP/IP Services for OpenVMS
6 - Startup HP TCP/IP Services for OpenVMS
7 - Run tests
A - Configure options 1 - 4
[E] - Exit configuration procedure
Enter configuration option: 1 [Return]
HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: 2 [Return]
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=Not Configured, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps)
2 - IE0 Menu (EIA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option:
|
In this example, no changes are made to the interface. The systems TCP/IP hostname is displayed as Not Configured. This is automatically configured the first time an IP address is configured. The assigned systems TCP/IP hostname may be changed using the menu options for configuring addresses.
Additional information is provided for each interface name. For
instance, the TCP/IP interface named WE0 corresponds to the OpenVMS
device EWA0: and is twisted-pair.
If you want to configure a standby interface for failSAFE IP failover
support, see Section 3.4.4.4; otherwise, skip to Section 3.4.4.5.
3.4.4.3 Interface IP Address Configuration
To configure an interface, select the option of the desired interface, then select Option 1 - Add a primary address on <chosen interface>, and answer the prompts for the IP address, netmask and hostname information.
For example:
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=Not Configured, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps)
2 - IE0 Menu (EIA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option: 1
|
This menu allows the configuration of a primary or an alias address as well as giving control to DHCP-client for address assignment. The primary address is considered the most often used address for this interface, whereas an alias address is considered a secondary address. By default, data sent via an interface with a primary and an alias address is transmitted with the IP source address set to the primary address.
The following example shows that WE0 is configured with a primary IP address of 10.0.0.1 and an alias address of 10.0.1.1. The menus are driven as follows, after selecting option 1 from the previous menu.
HP TCP/IP Services for OpenVMS Interface WE0 Configuration Menu
Configuration options:
1 - Add a primary address on WE0
2 - Add an alias address on WE0
3 - Enable DHCP client to manage address on WE0
[E] - Exit menu
Enter configuration option: 1
IPv4 Address may be entered with CIDR bits suffix.
E.g. For a 16-bit netmask enter 10.0.1.1/16
Enter IPv4 Address []: 10.0.0.1
Default netmask calculated from class of IP address: 255.0.0.0
IPv4 Netmask may be entered in dotted decimal notation,
(e.g. 255.255.0.0), or as number of CIDR bits (e.g. 16)
Enter Netmask or CIDR bits [255.0.0.0]: 16
Enter hostname []: liam
|
The system displays the information entered. If it is correct, press Return to accept it.
The following output is displayed, showing all information entered and then the Interface and Address menu again to display the change you have just made, configuration, and interface.
Requested configuration:
Address : 10.0.0.1/16
Netmask : 255.255.0.0 (CIDR bits: 16)
Hostname : liam
* Is this correct [YES]:
Added hostname liam (10.0.0.1) to host database
NOTE:
The system hostname is not configured.
It will now be set to liam (10.0.0.1).
This can be changed later via the Interface Configuration Menu.
Updated system hostname in configuration database
Added address WE0:10.0.0.1 to configuration database
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=liam, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps)
2 - 10.0.0.1/16 liam Configured
3 - IE0 Menu (EIA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option:
|
In this example, Interface WE0 with 10.0.0.1 was configured as the address, 16 CIDR bits (255.255.0.0) as the netmask, and the hostname as LIAM.
The address may be entered with the number of CIDR bits or a netmask. This example used 16 CIDR-bits, which is equivalent to a netmask of 255.255.0.0.
Because this is the first address configured on the system, it automatically becomes the TCP/IP hostname, as is displayed under the NOTE: text.
The address 10.0.0.1 with a name of LIAM has automatically been assigned as the system's TCP/IP hostname. This automatic assignment occurs only when no other addresses are configured on the system.
After configuring an address the menu returns to the Interface and Address Configuration menu. It now displays the address 10.0.0.1/16 configured on WE0. The newly created address has its own menu option (2), which allows further modification of the specific address. Note that menu options for configuring the other interfaces have been incremented compared to the first screen capture.
The state of the address is described as Configured.
3.4.4.4 failSAFE IP Address Configuration
To provide high availability of an IP address, you can configure it on multiple interfaces on a node or across a cluster, then enable the failSAFE IP service. Note that only one instance of the address is active; the others are in standby mode. The failSAFE IP service continually monitors the health of interfaces and upon detecting an interface failure, the address is deactivated on the failed interface and a standby address becomes active.
When the failed interface recovers, failSAFE IP detects this and can return its IP address.
Configure the standby IP address as follows:
For information on configuring failSAFE IPv6 addresses, see Section 4.3. |
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=liam, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps)
2 - 10.0.0.1/16 liam Configured
3 - 10.10.1.1/16 abby Configured
4 - IE0 Menu (EIA0: TwistedPair 100mbps)
[E] - Exit menu
Enter configuration option: 3
HP TCP/IP Services for OpenVMS Address Configuration Menu
WE0 10.10.1.1/16 abby Configured WEA0
Configuration options:
1 - Change address
2 - Set "abby" as the default hostname
3 - Delete from configuration database
4 - Add standby aliases to configuration database (for failSAFE IP)
[E] - Exit menu
Enter configuration option: 4
Address 10.10.1.1/16 is currently configured on:
WE0
Interfaces available for failover are:
IE0
Enter an interface for failSAFE IP: IE0
Added alias address IEA0:10.10.1.1 to configuration database
The failSAFE IP service, which monitors the health of interfaces,
is not currently enabled. Refer to the Optional Components Menu
to configure the service.
Press <ENTER> key to continue...
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu
Hostname Details: Configured=liam, Active=Not Configured
Configuration options:
1 - WE0 Menu (EWA0: TwistedPair 1000mbps)
2 - 10.0.0.1/16 liam Configured
3 - 10.10.1.1/26 abby Configured
4 - IE0 Menu (EIA0: TwistedPair 100mbps)
5 - 10.10.1.1/26 abby Configured
[E] - Exit menu
Enter configuration option:
|
HP TCP/IP Services for OpenVMS Interface & Address Configuration Menu Hostname Details: Configured=liam, Active=liam Configuration options: 1 - WE0 Menu (EWA0: TwistedPair 1000mbps) 2 - 16.116.93.75/26 liam Configured,Active 3 - 10.10.1.1/26 abby Configured,Active 4 - IE0 Menu (EIA0: TwistedPair 100mbps) 5 - 10.10.1.1/26 abby Configured,Active-Standby [E] - Exit menu Enter configuration option: |
HP TCP/IP Services for OpenVMS Address and Configuration Menu
WE0 10.10.1.1/26 abby Configured,Active-Standby WE01
Configuration options:
1 - Change address
2 - Set "abby.sqa.tcpip.zko.hp.com" as the default hostname
3 - Delete from configuration database
4 - Remove from live system
5 - Add standby aliases to configuration database (for failSAFE IP)
[E] - Exit menu
Enter configuration option:
|
You can also manually configure the failSAFE IP address using the TCP/IP management SET INTERFACE command or the ifconfig utility. The ifconfig utility provides a greater degree of management control and is recommended for more complex environments. For more information, refer to the HP TCP/IP Services for OpenVMS Management manual. |
The following is sample output for configuring dynamic routing:
DYNAMIC ROUTING Configuration
Dynamic routing has not been configured.
You may configure dynamic ROUTED or GATED routing.
You cannot enable both at the same time. If you want
to change from one to the other, you must disable the
current routing first, then enable the desired routing.
If you enable dynamic ROUTED routing, this host will use the
Routing Information Protocol (RIP) - Version 1 to listen
for all dynamic routing information coming from other
hosts to update its internal routing tables.
It will also supply its own Internet addresses to
routing requests made from remote hosts.
If you enable dynamic GATED routing, you will be able to
configure this host to use any combination of the following
routing protocols to exchange dynamic routing information
with other hosts on the network:
Routing Information Protocol (RIP) - Version 1 & 2
Router Discovery Protocol (RDISC)
Open Shortest Path First (OSPF)
Exterior Gateway Protocol (EGP)
Border Gateway Protocol (BGP-4)
Static routes
* Do you want to configure dynamic ROUTED or GATED routing [NO]: YES [Return]
* Do you want to enable GATED routing configuration [NO]: [Return]
ROUTED option
If you enable the 'supply' option of dynamic routing,
this host will supply dynamic routing information to
other hosts on the network whether it is acting as an
internetwork gateway or not.
* Do you want this host to supply its dynamic routing information [NO]: [Return]
|
* Do you want to configure dynamic ROUTED or GATED routing [NO]: [Return]
A default route has not been configured.
* Do you want to configure a default route [YES]: [return]
Enter your Default Gateway host name or address: cisco64net.sqa.tcpip.zko.hp.com
cisco64net.sqa.tcpip.zko.hp.com is not in the local host database.
Enter Internet address for cisco64net.sqa.tcpip.zko.hp.com: 16.116.93.65
|
To configure the BIND resolver, select Option 4 from the Core Environment menu, enter the BIND server name and address, as shown in the following example:
HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: 4
BIND RESOLVER Configuration
A BIND resolver has not been configured.
HP TCP/IP Services for OpenVMS supports the Berkeley Internet Name
Domain (BIND) resolver. BIND is a network service that enables clients
to name resources or objects and share information with other objects
on the network.
Before configuring your system as a BIND resolver, you should
first be sure that there is at least one system on the network
configured as either a BIND primary or secondary server for
this domain.
You can specify a BIND server by its address or name;
however, if specified by name, an entry for it must
exist in the TCPIP$HOST database.
You will be asked one question for each server.
Press Return at the prompt to terminate the list.
Enter your BIND server name: odessy
odessy is not in the local host database.
Enter Internet address for odessy: 16.116.93.66
Enter next BIND server name:
HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option:
|
To view the current BIND resolver configuration, select Option 4 from the Core Environment menu. Press Return to accept the default if you do not want to reconfigure the BIND resolver, as shown in the following example:
HP TCP/IP Services for OpenVMS Core Environment Configuration Menu
Configuration options:
1 - Domain
2 - Interfaces
3 - Routing
4 - BIND Resolver
5 - Time Zone
A - Configure options 1 - 5
[E] - Exit menu
Enter configuration option: 4
BIND RESOLVER Configuration
A BIND resolver has already been configured.
BIND Resolver Configuration
Transport: UDP
Domain: sqa.tcpip.zko.hp.com
Retry: 2
Timeout: 5
Servers: odessy
Path: No values defined
* Do you want to reconfigure BIND [NO]:
|
The following is sample output for configuring the BIND resolver:
A BIND resolver has already been configured. BIND Resolver Configuration Transport: UDP Domain: budget.acme.com Retry: 4 Timeout: 4 Servers: island.budget.acme.com Path: No values defined * Do you want to reconfigure BIND [NO]: [Return] |
In this example, no changes are made to the BIND resolver.
3.4.4.7 Time Zone Configuration
The following is sample output for configuring the time zone:
TCPIP uses timezone information provided by the OpenVMS Operating System. No additional timezone configuration is needed for TCPIP when the operating system is configured correctly. This section verifies the current OpenVMS timezone configuration. A warning message (TCPIP-W-) indicates that corrective action should be taken. TCPIP will appear to operate but components may display either the wrong time or a time inconsistent with other applications. %TCPIP-I-INFO, Logical name SYS$TIMEZONE_RULE found. -TCPIP-I-INFO, Software for automatic Summer/Winter time (TDF) change -TCPIP-I-INFO, is present. -TCPIP-I-INFO, Further action to ensure TDF change is not necessary. %TCPIP-I-NORMAL, timezone information verified Press Return to continue ... |
After you configure the core environment, press Return or choose option
E to exit from the Core Environment menu. If you chose option A from
the Main Configuration menu to configure all the TCP/IP Services
components, the Client Components Configuration menu displays next;
otherwise, the procedure returns to the the Main Configuration menu.
3.4.5 Configuring the Client Environment
To display the Client Components Configuration menu, choose option 2 (Client components) from the Main Configuration menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Client Components Configuration menu displays automatically after you finish configuring the core environment services.
From the Client Components Configuration menu, choose option A to configure all the client services. Alternatively, you can configure one client service at a time. The sample output in the following sections show the progression of the procedure when you choose option A.
HP TCP/IP Services for OpenVMS Client Components Configuration Menu
Configuration options:
1 - DHCP Client Disabled Stopped
2 - FTP Client Enabled Stopped
3 - NFS Client Enabled Started
4 - REXEC and RSH Enabled Started
5 - RLOGIN Enabled Started
6 - SMTP Enabled Started
7 - SSH Client Enabled Stopped
8 - TELNET Enabled Started
9 - TELNETSYM Disabled Stopped
A - Configure options 1 - 9
[E] - Exit menu
|
Note that the sample Client Components Configuration menu shows most clients enabled and all of them stopped. Clients are enabled for startup if they have been enabled in the TCP/IP Services configuration database (TCPIP$CONFIGURATION.DAT). The enabled services are started the next time TCP/IP Services is started. You can also start (or stop) a specific service, without having to restart TCP/IP Services, by choosing the Start service option from that service's configuration menu. In addition, you can use command procedures to start or stop a specific service, as explained in Section 3.11.3.
The initial status of the services depends on whether you have other TCP/IP Services installations in place on the system, and whether the software or individual services have been started. On a new system, all the services would be disabled (the default). The status of services is also affected by the selections you made from the Core Environment menu.
To minimize resource consumption, enable and start only those services that you are sure to use. Disable those you do not plan to use.
To configure all the client services, choose option A.
The following is an example of the output for configuring an FTP client. The configuration output for other clients might vary. Note that after you configure a client (such as FTP) that has an associated server, the configuration prompts you about whether to configure the corresponding server.
Enter configuration option: 2 [Return]
FTP CLIENT Configuration
Service is enabled on specific node.
Service is stopped.
FTP CLIENT configuration options:
1 - Disable service on this node
2 - Start service on this node
[E] - Exit FTP_CLIENT configuration
Enter configuration option: 1 [Return]
The FTP SERVER is enabled.
* Do you want to configure the FTP SERVER [NO] ? [Return]
|
In the preceding example, the FTP client was originally enabled, and option 1 disables it. The configuration procedure indicates that the FTP server is enabled and asks whether you want to configure it as well.
The following example shows the configuration output that you might see if you want to enable an FTP client that had been disabled.
FTP CLIENT Configuration
Service is not enabled.
Service is stopped.
FTP CLIENT configuration options:
1 - Enable service on this node
2 - Enable & Start service on this node
[E] - Exit FTP_CLIENT configuration
Enter configuration option: 2 [Return]
|
In this example, as with the previous one, the TCP/IP Services software has already been started, so you have the choice of starting the client as well as enabling it. If you choose option 1, the FTP service is enabled and FTP starts the next time TCP/IP Services is started. If you choose option 2, the FTP service is started immediately and then every time the TCP/IP Services is started.
If the TCP/IP Services software is not already started, then the FTP Client Components Configuration menu gives you only the option of enabling the service, as in the following example:
1 - Enable service on this node
[E] - Exit FTP_CLIENT configuration
|
After you configure the client service environment, press Return or choose option E to exit from the Client Components menu. If you chose option A from the Main Configuration menu to configure all the TCP/IP Services components, the Server Components Configuration menu displays next; otherwise, the procedure returns to the the Main Configuration menu.
| Previous | Next | Contents | Index |