HP TCP/IP Services for OpenVMS
Management
Previous Contents Index

8.5.3.3 The Groups Tab

An include group is a collection of parameters to be passed to a set of workstations or other computers on the network which can be on different subnets. Use the Groups tab to configure include groups.

8.5.3.3.1 Using group parameters

You can define a group so that a set of workstations, possibly on different subnets, has the same configuration values. For example, you might want a group to include specific lease time information for your network environment and you want this lease information to be used for all of your clients. You can define an include group holding this lease information and make your subnet groups members of this include group. The alternative would be to duplicate the lease information in each individual subnet group entry which is more difficult and error prone. Include groups can be members of other include groups. This allows you to create hierarchies of available network services across many clients.

8.5.3.3.2 Defining a group

To define an include group using the Groups tab, use the following procedure. For a description of the group parameters, see Section 8.5.3.4.

  1. Click the Groups tab.
  2. Choose [New Record].
  3. Enter the name of the include group in the Value field. This name is a tag for internal use of the DHCP server only. For more information see Section 8.5.3.4.1.
  4. Choose Member of Group (optional). Enter the name of an include group that the include group is joining. Use this feature to create hierarchies of groups and minimize duplication elsewhere.
  5. Choose Group Members (optional).
    Enter the names of subnets, nodes, or other groups that are to be members of the group, that will pull in this group's parameters. If you have already created a node or subnet group or groups that are members of the include group you are entering the DHCP GUI will display the names of these groups in the Group Members field. If you want to include a new member or delete an existing member you can do so here in the group's Group Members field or under the Subnets or Nodes tab in the Member of Group field of the groups pulling in this group.
  6. Set up key information:
    Enter the vendor class (for example, TCPVMS or JOIN) that identifies the DHCP client vendor class to which this entry should apply. Note that you can have multiple include groups with the same name if they have different vendor class key values. If the entry should apply to any vendor class or you are not using vendor classes leave the vendor class field blank.
  1. Choose from the lists of DHCP parameters on the drop-down list.
    Different lists of DHCP parameters are available on the drop down list. Choose either BASIC DHCP Parameters or DHCP Parameters.
  2. As appropriate, enter information for Network, Lease, Time, BOOTP, NetBIOS, X Window, TCP, IP, and Link parameters. For more information about these parameters, refer to Section 8.5.3.4.
  3. Choose Update from the File menu.

The new configuration takes effect immediately.

8.5.3.3.3 Removing a group record

To remove a group record:

  1. Click the Groups tab.
  2. Choose DHCP Parameters from the drop-down list.
  3. Choose the Group record you want to delete.
  4. Click Delete.

Changes to the database take effect immediately.

8.5.3.4 Nodes, Subnets, Group Parameters

This section describes the subnet, group, and node parameters. The parameters are grouped by the following categories:

For any parameter, list the values in order of preference.

8.5.3.4.1 Name/ID parameters

Name and identification parameters determine the name of the configuration and information that identifies which client or clients are being configured by this record.

Name

Specifies the name for this subnet, node, or include group configuration. The names used here are tags for the internal use of the DHCP server. You can name them as you choose but do not use the same name more than once except where you use a different vendor class for the duplicate names.

Group Members

Specifies the names of subnet, node, and include groups that are members of the group (that is, those that inherit this group's parameters).

Member of Group

Specifies the name of the group that the subnet, node, or include group is joining.
8.5.3.4.1.1 Limitations on Group Hierarchies

The hierarchies provided for with member groups do not support multiple inheritance. An include group can have multiple members, but an include, subnet, or node group can be a member of only one group. For example, you can make Group_A with members Group_B and Group_C, but you can not make Group_A a member of Group_B and Group_C.

8.5.3.4.2 Key Parameters

Key parameters identify the keys for the configuration record. The Key parameters include Hardware Address/Client ID, Hardware Type, Net or Subnet IP Address, and Vendor Class.

Hardware Address/Client ID

This parameter specifies the hardware address (MAC address) of the node. Enter the hardware address in the format xx:xx:xx:x:xx:xx, for example, 00:08:C7:08:E3:63. The hardware address is assigned during manufacturing and usually is displayed when you turn on or reboot your workstation.

Hardware Type

This field takes a string of characters and specifies the network type associated with this node, such as Ethernet or token ring.

Enter either the symbol or the actual number as shown in Table 8-6. For example, to specify Ethernet as the hardware type, enter either the symbol ether or the number 1.

Net or Subnet IP Address

Specifies the address of the subnet record (if its a Subnet configuration record). Enter the IP address that identifies this subnet portion of the network, for example, 129.84.3.0.

Vendor Class

A DHCP client can pass a vendor class string to the server to identify the client vendor implementation. For example, TCPVMS for the TCP/IP Services DHCP client. The DHCP server uses the vendor class string as part of the key lookup when determining which groups of configured parameters apply to the client. The information is a string of octets, usually ASCII, that the server interprets.

8.5.3.4.3 BOOTP Parameters

The server version of DHCP fully supports the following BOOTP parameters. If a BOOTP client makes a request of the server, it acts as a BOOTP server.

Boot File

Specifies the fully qualified path name of the client's default boot image.

Boot File Server Address

Specifies the server address of the boot file.

Boot File Server Name

Specifies the host name of the server with the boot file.

Boot File Size

Specifies the length in 512-octet blocks of the default boot image for the client. Specify the file length as a number.

Cookie Servers

Specifies a list of RFC 865 cookie servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

DNS Domain Name

Specifies the domain name the client should use when resolving host names through the Domain Name System.

DNS Servers

Specifies a list of DNS (STD 13, RFC 1035) name servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

Extensions Path

Specifies a string which identifies a file, retrievable through TFTP, that contains information that the server can interpret in the same way as the 64-octet vendor-extension field in the BOOTP response. There is no limit on the length of this file.

Home Directory

Specifies the directory where the boot file resides, if it is not specified in the boot file name.

Also specifies the name of the client. The name can or can not be qualified with the local domain name. See RFC 1035 for character-set restrictions.

Host IP Address (BOOTP only)

Specifies the host IP address for BOOTP clients.

Host Name

Specifies the host name parameter if you are setting up a configuration for a single client identified by its MAC address.

Also specifies the name of the client. The local domain name can or can not qualify the client name. See RFC 1035 for character-set restrictions.

IEN-116 Name Servers

Specifies a list of IEN-116 name servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

Impress Servers

Specifies a list of Imagen Impress servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

Log Servers

Specifies a list of MIT-LCS UDP log servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

LPR Servers

Specifies a list of RFC 1179 line-printer servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

Merit Dump File

Specifies the path name of a file to which the client's core image should be dumped in the event the client fails. The path is formatted as a character string consisting of characters from the NVT ASCII character set.

Resource Location Servers

Specifies a list of RFC 887 resource location servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

Root Path

Specifies the path name that contains the client's root directory or partition. The path is formatted as a character string consisting of characters from the NVT ASCII character set.

Routers

Specifies the list of IP addresses for routers (gateways) on the client's subnet. If you specify a default gateway of 0.0.0.0, the server uses the client's IP address as the default gateway address.

Use this format: ddd.ddd.ddd.ddd.

Subnet Mask

Specifies the client's subnet mask as described in RFC 950.

A subnet mask allows the addition of subnetwork numbers to an address, and provides for more complex address assignments.

If you specify both the subnet mask and the router option in a DHCP reply, the subnet mask option must be first.

Use this format: ddd.ddd.ddd.ddd.

Send Client's Host Name

Specifies whether the server should send the client's host name to the client in the reply.

The following are valid values:
False: Do not send the client's host name. Default.
True: Send the client's host name.

Swap Server

Specifies the IP address of the client's swap server.

Use this format: ddd.ddd.ddd.ddd.

TFTP Root Directory

Specifies the root directory for Trivial File Transfer Protocol (TFTP).

Time Offset

Specifies the offset of the client in seconds from Universal Coordinated Time (UTC).

Time Servers

Specifies a list of RFC 868 time servers available to the client. Enter the servers in order of preference.

Use this format: ddd.ddd.ddd.ddd.

Vendor Magic Cookie

Specifies a vendor magic cookie for the client.

8.5.3.4.4 IP parameters

IP layer parameters affect the operation of the IP layer on a per-host basis.

Broadcast Address

Specifies the broadcast address in use on the client's subnet.

Forward Nonlocal Datagrams

Specifies whether the client should configure its IP layer to allow forwarding of datagrams with nonlocal source routes.

The following are valid values:
False: Disable forwarding of datagrams with nonlocal source routes.
True: Enable forwarding.

IP Forwarding

Specifies whether the client should configure its IP layer for packet forwarding.

The following are valid values:
False: Disable IP forwarding.
True: Enable IP forwarding.

IP Time-to-Live

Specifies the default time-to-live that the client should use on outgoing datagrams. Specify time-to-live as an octet.
Minimum value 1
Maximum value 255

Interface MTU

Specifies the maximum transmit unit (MTU) to use on this interface. Specify the MTU as a 16-bit unsigned integer.

Minimum legal value is 68.

Maximum Reassembly Size

Specifies the maximum size datagram that the client should be prepared to reassemble. Specify the size as a 16-bit unsigned integer.

Minimum legal value is 576.

MTU Plateaus

Specifies a table of MTU sizes to use when performing Path MTU Discovery as defined in RFC 1191. The table is formatted as a list of 16-bit unsigned integers, ordered from smallest to largest.

The minimum value cannot be smaller than 68.

PMTU Timeout

Specifies the timeout to use when aging Path MTU values discovered by the mechanism defined in RFC 1191. Specify the timeout in seconds as a 32-bit unsigned integer.

Perform Mask Discovery

Specifies whether the client should perform subnet mask discovery using the Internet Control Message Protocol (ICMP).

The following are valid values:
False: Client should not perform mask discovery.
True: Client should perform mask discovery.

Perform Router Discovery

Specifies whether the client should solicit routers using the Router Discovery mechanism defined in RFC 1256.

The following are valid values:
False: Client should not perform router discovery.
True: Client should perform router discovery.

Policy Filters

Specifies policy filters for nonlocal source routing. The filters consist of a list of IP addresses and masks that specify destination/mask pairs with which to filter incoming source routes.

The client should discard a source-routed datagram whose next-hop address does not match one of the filters.

Use this format: ddd.ddd.ddd.ddd.

Solicit Router

Specifies the IP address to which the client should transmit router solicitation requests.

Use this format: ddd.ddd.ddd.ddd.

Static Routes

Specifies a list of static routes that should be installed in the client's routing table. If you specify multiple routes to the same destination, list them in descending order of priority.

The routes consist of a list of IP address pairs. The first address is the destination address, and the second address is the router for the destination.

Note
The default route (0.0.0.0) is an illegal destination for a static route.

Use this format: ddd.ddd.ddd.ddd.

Subnets Are Local

Specifies whether the client can assume that all subnets of the IP network to which the client is connected use the same MTU (maximum transmit unit) as the subnet of the network to which the client is directly connected.

The following are valid values:
False: The client should assume that some subnets of the directly connected network can have smaller MTUs.
True: All subnets share the same MTU.

Supply Masks

Specifies whether the client should respond to subnet mask requests using the Internet Control Message Protocol (ICMP).

The following are valid values:
False: Client should not respond.
True: Client should respond.

8.5.3.4.5 Lease parameters

Lease parameters allow you to change information about the IP lease times. Lease times determine the length of time a client can use an IP address.

DHCP Rebinding Time

Specifies the time interval in seconds from address assignment until the client requests a new lease from any server on the network.

DHCP Renewal Time

Specifies the time interval in seconds from address assignment until the client attempts to extend the duration of its lease with the original server.

DHCP Lease Time

The client uses this option in a client request (DHCPDISCOVER or DHCPREQUEST) message to request a lease time for the IP address.

The server uses this option in a server reply (DHCPOFFER) message to specify the lease time it is willing to offer.

Enter the time in months, days, hours, minutes, and seconds; for example, 2 months 5 days 45 minutes. By default, the server interprets the lease in seconds. For an infinite lease for a BOOTP client, specify a -1.

8.5.3.4.6 Link Parameters

Link Layer parameters affect the operation of the Link layer on a per-host basis.

ARP Cache Timeout

Specifies the timeout in seconds for ARP cache entries. The time is specified as a 32-bit unsigned integer.

Ethernet Encapsulation

If it is an Ethernet interface, use this option to specify whether the client should use Ethernet Version 2 (RFC 894) or IEEE 802.3 (RFC 1042) encapsulation.

The following are valid values:
False: Use RFC 894 encapsulation.
True: Use RFC 1042 encapsulation.

Trailer Encapsulation

Specifies whether the client should negotiate the use of trailers (RFC 893) when using the ARP protocol.

The following are valid values:
False: Client should not attempt to use trailers.
True: Client should attempt to use trailers.

8.5.3.4.7 NetBIOS Parameters

NetBIOS parameters configure NetBIOS related parameters on a per-host basis.

NetBIOS Datagram Distribution Server

Specifies a list of RFC 1001/1002 NBDD servers listed in the order of preference.

Use this format: ddd.ddd.ddd.ddd.

NetBIOS Name Server/WINS Server

Specifies a list of RFC 1001/1002 NBNS name servers listed in the order of preference.

Use this format: ddd.ddd.ddd.ddd.

NetBIOS Node Type

Allows you to configure NetBIOS-over-TCP/IP clients as described in RFC 1001/1002. Specify the value as a single octet (from 0 to 255) that identifies the client type as shown in Table 8-7.

Table 8-7 NetBIOS Node Type and Value
Node Type Value (hexadecimal)
B-node 1
P-node 2
M-node 4
H-node 8

Note
The NetBIOS over TCP/IP clients must be configurable.

NetBIOS Scope

The NetBIOS scope option specifies the NetBIOS scope text parameter for the client as specified in RFC 1001/1002. There can be character-set restrictions.

8.5.3.4.8 Network Parameters

Network parameters allow you to change basic network configuration information.

Finger Servers

Specifies a list of finger servers available to the client. List the servers in the order of preference.

IRC Servers

Specifies a list of IRC (Internet Relay Chat) servers available to the client. List the servers in the order of preference.

Mobile IP Home Agents

Specifies a list of IP addresses indicating mobile IP home agents available to the client. List the agents in the order of preference.

NNTP Servers

Specifies a list of Network News Transfer Protocol (NNTP) servers available to the client. List the servers in the order of preference.

NetWare Domain

Specifies the NetWare domain name.

NetWare Options

Specifies a list of NetWare servers.

POP3 Servers

Specifies a list of Post Office Protocol 3 (POP3) servers available to the client. List the servers in the order of preference.

SMTP Servers

Specifies a list of Simple Mail Transfer Protocol (SMTP) servers available to the client. List the servers in the order of preference.

STDA Servers

Specifies a list of StreetTalk Directory Assistance (STDA) servers available to the client. List the servers in the order of preference.

StreetTalk Servers

Specifies a list of StreetTalk servers available to the client. List the servers in the order of preference.

WWW Servers

Specifies a list of World Wide Web servers available to the client. List the servers in the order of preference.

8.5.3.4.9 TCP Parameters

TCP parameters affect the operation of the TCP layer on a per-host basis.

Keep Alive Interval

Specifies the interval that the client should wait before sending a keepalive message on a TCP connection.

A value of 0 (zero) indicates that the client should not generate keepalive messages on connections unless an application requests them.

Specify the time in seconds as a 32-bit unsigned integer.

Keep Alive Octet

This parameter specifies whether the client is to send TCP keepalive messages with a garbage octet for compatibility with older implementations.

The following are valid values:
False: Do not send a garbage octet.
True: Send a garbage octet. (Sets the compatibility mode.)

TCP Default Time-to-Live

This option specifies the default time-to-live that the client uses when sending TCP segments.

Minimum value is 1.

Previous Next Contents Index