| Previous | Contents | Index |
Use the configuration procedure TCPIP$CONFIG to enable dynamic routing and configure your host to receive routing protocol messages as follows:
Do you want to enable GATED routing configuration? |
To disable dynamic routing:
Do you want to reconfigure dynamic ROUTED or GATED routing [NO]: Y Do you want to disable dynamic ROUTED or GATED routing configuration [NO]: Y |
When you disable GATED routing, the GATED routes are preserved. To
disable GATED and remove all GATED routes from the routing table, enter
the command STOP ROUTING/GATED.
4.4 Configuring GATED
You must configure the GATED protocols before starting GATED routing. Edit a copy of the sample file TCPIP$GATED.TEMPLATE (located in the SYS$SYSDEVICE:[TCPIP$GATED] directory) to add statements that select routing protocols, manage routing information, manage independent system routing, and control tracing options.
If you do not format the configuration file correctly, GATED terminates.
For specific information about how to edit the GATED configuration
file, see Appendix A.
4.4.1 Datagram Reassembly Time
Reassembly is the process of reconstructing a complete data message from received fragments. The reassembly timer determines the length of time allowed for the reassembly process. You can modify the reassembly timer to ensure that IP datagram fragments are optimally reassembled at the destination host.
Consider the following when setting the reassembly timer:
Enter the following commands to reset the reassembly timer:
TCPIP> SET PROTOCOL IP /REASSEMBLY_TIMER=n |
TCPIP> SET CONFIGURATION PROTOCOL IP /REASSEMBLY_TIMER=n |
In the following example, the first command changes the IP reassembly time to 20 seconds on the running system. This new setting remains in effect until the next TCP/IP Services startup.
The second command makes the change permanent by modifying the configuration database, TCPIP$CONFIGURATION.DAT.
TCPIP> SET PROTOCOL IP /REASSEMBLY_TIMER=20 TCPIP> SET CONFIGURATION PROTOCOL IP /REASSEMBLY_TIMER=20 |
To enable packet forwarding between networks, enter the following TCP/IP management command:
TCPIP> SET PROTOCOL IP /FORWARD |
To ensure this is set up the next time TCP/IP Services is restarted, enter the following command:
TCPIP> SET CONFIGURATION PROTOCOL IP /FORWARD |
Display the setting using the following command:
TCPIP> SHOW PROTOCOL /PARAMETERS |
Or use the sysconfig utility to enable forwarding. First, define foreign commands:
$ @SYS$MANAGER:TCPIP$DEFINE_COMMANDS.COM |
Enter the following sysconfig command:
$ sysconfig -r inet ipforwarding=1 ipgateway=1 |
To make sure forwarding is enabled after restarting TCP/IP Services, define these attributes in the SYSCONFIGTAB.DAT database file, as described in the HP TCP/IP Services for OpenVMS Tuning and Troubleshooting guide.
To view the setting, use the following command:
$ sysconfig -q inet ipforwarding ipgateway |
When multiple networks share the same physical media and the host has just one interface, it is still possible to forward packets between these networks by creating a network alias, as described in Section 2.3.3.
For example, consider a network in which two networks have network addresses of 16.20.1/24 and 16.20.2/24, and the host address is 180. If the host has a single ethernet interface, WE0, create the interface and pseudointerfaces as follows:
TCPIP> SET CONFIGURATION INTERFACE WE0 /HOST=16.20.1.180 - _TCPIP> /NETWORK_MASK=255.255.255.0 /BROADCAST_MASK=16.20.1.255 TCPIP> SET CONFIGURATION INTERFACE WEA0 /HOST=16.20.2.180 - _TCPIP> /NETWORK_MASK=255.255.255.0 /BROADCAST_MASK=16.20.2.255 TCPIP> SET CONFIGURATION PROTOCOL IP /FORWARD |
When TCP/IP Services is restarted, the host will forward packets between these networks.
Alternatively, you can add the following commands to TCPIP$SYSTARTUP.COM and then restart TCP/IP Services:
$ ifconfig we0 aliaslist 16.20.1-2.180/24 $ sysconfig -r inet ipforwarding=1 ipgateway=1 |
To use extended routing, define pseudointerfaces. A pseudointerface is a data structure that extends routing. Like an interface, the name of an internet pseudointerface is three alphabetic characters, followed by the pseudointerface unit number in the range of 0 through 255.
The first two characters are the same as the two characters in the internet interface name (interface type and interface class). See Section 2.3.1 for more information about interface names.
The third character identifies the controller letter that corresponds to the OpenVMS hardware controller.
For example, for an OpenVMS Alpha system with two Ethernet controllers, EZA0 and EZB0, you can define the following internet interfaces and pseudointerfaces:
To extend routing, follow these steps:
TCPIP> SET NOINTERFACE interface TCPIP> SET INTERFACE interface /HOST=host - _TCPIP> /NETWORK_MASK=mask /BROADCAST_MASK=b_mask TCPIP> SET CONFIGURATION INTERFACE interface /HOST=host - _TCPIP> /NETWORK_MASK=mask /BROADCAST_MASK=b_mask |
TCPIP> SET NOINTERFACE FFA0 TCPIP> SET INTERFACE FFA0 /HOST=KESTREL /NETWORK_MASK=255.255.0.0 - _TCPIP> /BROADCAST_MASK=128.30.0.0 |
TCPIP> SET CONFIGURATION INTERFACE FFA0 /HOST=KESTREL - _TCPIP> /NETWORK_MASK=255.255.0.0 /BROADCAST_MASK=128.30.0.0 |
If you have a configuration in which multiple networks share the same physical LAN, you can communicate directly with hosts in other networks without the need of a pseudointerface for each network.
You can use a broadcast address to designate an interface route, also called a metric 0 route.
To create interface routes, follow these steps:
For example, network 99.0.0.0 is on the same cable as network 192.199.199.0. On host 99.1.2.3, specify network 192.199.199.0 as directly reachable:
TCPIP> SET ROUTE 192.199.199.0 /NETWORK /GATEWAY=99.1.2.3 |
On the hosts in network 192.199.199.0, enter:
TCPIP> SET ROUTE 99.0.0.0 /NETWORK /GATEWAY=192.199.199.255 |
Network hosts require manual configuration of a hardware address for a remote IP address under the following conditions:
For example, to map the Ethernet address AA-02-04-05-06-07 of host ROOK, add the hardware address to the ARP table by entering the following command:
TCPIP> SET ARP AA-02-04-05-06-07 ROOK |
failSAFE IP is an optional service provided by TCP/IP Services to allow IP addresses to fail over when interfaces cease functioning on a system where multiple interfaces have been configured. When the same IP address is configured on multiple interfaces, network connections can be maintained when:
This chapter reviews key concepts and describes:
The failSAFE service monitors an interface and takes appropriate action upon detecting interface failure or recovery. failSAFE IP provides IP address redundancy by requiring the same IP address to be configured on multiple interfaces. Only one instance of each IP address is active at any time; the other duplicate IP addresses are in standby mode.
Standby IP addresses can be configured on multiple interfaces within the same node or across an OpenVMS Cluster. The interfaces are monitored by the failSAFE IP service. When an interface fails, each active IP address on the failed interface is removed and the standby IP address becomes active. If an address is not preconfigured with a standby, then the address is removed from the failed interface until it recovers.
Static routes on the failed interface are also removed and are configured on any interface where their network is reachable.
When an interface recovers, it can request that its IP addresses be returned to it when the interface is configured as the home interface for one or more addresses. When the home interface recovers, it requests that the current holder of the address give it up. (For more information about home interfaces, see Section 5.2.3.)
The current holder of an address does not release an address if this action will result in dropped connections, or if the current holder is also designated as a home interface for that address.
Management intervention can be taken to force the removal of an address.
5.2 Configuring failSAFE IP
Configuring failSAFE IP requires two steps:
A failSAFE IP address can be configured by using the TCPIP$CONFIG.COM command procedure, or manually by using the TCP/IP management command SET INTERFACE.
For instance, to create an IP address of 10.10.10.1 on interface IE0 and a standby alias address on interface IE1 (pseudointerface IEB0), use the following commands:
$ TCPIP TCPIP> SET INTERFACE IE0/HOST=10.10.10.1 TCPIP> SET INTERFACE IEB0/HOST=10.10.10.1 |
Alternatively, you can use the ifconfig utility to configure an interface manually. For example:
$ ifconfig ie0 10.10.10.1 $ ifconfig ie1 alias 10.10.10.1 |
To view the standby addresses, use the ifconfig utility. For example:
$ ifconfig -a
IE0: flags=c43<UP,BROADCAST,RUNNING,MULTICAST,SIMPLEX>
*inet 10.10.10.1 netmask ff000000 broadcast 10.255.255.255
IE1: flags=c03<UP,BROADCAST,MULTICAST,SIMPLEX>
failSAFE IP Addresses:
inet 10.10.10.1 netmask ff000000 broadcast 10.255.255.255 (on HUFFLE IE0)
|
In this example, interface IE1 displays a failSAFE IP address that is active on node HUFFLE, interface IE0.
In an OpenVMS Cluster, an IP address with active connections cannot be reassigned to another node in the cluster. Therefore, you should always configure a standby interface on the same node as the home interface. |
DNS-controlled primary addresses should be placed under the control of the BIND/DNS load broker to make sure that the DNS alias continues to be available.
The ifconfig utility provides greater control of failSAFE IP addresses. Table 5-1 describes the ifconfig options that support failSAFE IP.
| Option | Description |
|---|---|
| [ - ] fail | Forces an interface to fail. You can recover the interface using the -fail command. |
| [ - ] home | Forces an alias address to be created with a home interface. This option is used used when creating IP addresses. By default, all primary IP addresses are created with a home interface. |
| [ - ] fs | Creates an address that is not managed by failSAFE IP. All IP addresses are created as failSAFE addresses by default, except for addresses assigned to the loopback interface LO0 (for instance, the local host address 127.0.0.1). |
By default, the failSAFE IP service monitors all TCP/IP interfaces on a system, periodically polling each interface using default polling intervals. You can override the defaults by editing the configuration file. To change the name or location of the configuration file, define the logical name TCPIP$FAILSAFE. Be sure to include the /SYSTEM and /EXECUTIVE qualifiers, and make sure that the failSAFE process is stopped, or your changes will not take effect. By default, the configuration file name and location are:
SYS$SYSDEVICE:[TCPIP$FSAFE]TCPIP$FAILSAFE.CONF |
Table 5-2 describes the configuration parameters.
| Parameter | Description | Default |
|---|---|---|
| GENERATE_TRAFFIC |
Enables failSAFE IP to periodically generate either MAC-level
broadcasts or gratuitous ARP packets. ARP traffic requires an active IP
address on the NIC. MAC-level traffic is sent regardless of the NIC
configured with IP. You can also use this parameter to turn off traffic
generation.
This parameter allows three settings:
For example,to generate periodic ARP packets, enter the following
parameter in the configuration file:
|
MAC |
| MAC_PTY |
If MAC-level broadcast traffic is being generated, the MAC protocol
type may also be specified as a two-byte hexadecimal number. For
example, from the Web site,
http://www.iana.org/assignments/ethernet-numbers, the DEC Diagnostic
protocol type has a value of 6005.
For example, to generate MAC protocol packets of the DEC Diagnostic protocol, enter the following parameter in the configuration file: MAC_PTY: 6005 |
If this parameter is not specified, an available protocol type is selected. |
| LOGFILE |
Specifies the name and location of the log file. The logical name
TCPIP$FAILSAFE_LOGFILE points to the log file. For example, to specify
an alternate location, enter the following parameter in the
configuration file:
LOGFILE: DEV1:[STATS]FAILSAFE.LOG |
SYS$SYSDEVICE:[TCPIP$FSAFE] - |
| INTERFACE_LIST | The list of interfaces that failSAFE monitors. | All interfaces |
| INFO_POLL | Specifies the polling interval used when the interface is known to be functional. It requires two INFO_POLL timeouts to determine that an interface is not responding, at which time the polling frequency is set to the WARN_POLL period. | 3 seconds |
| WARN_POLL | Specifies the polling interval used when the interface first stops responding. It will continue polling the interface for RETRY_WARN attempts before the interface is deemed to be malfunctioning, at which time the polling frequency is set to ERROR_POLL and failover occurs. | 2 seconds |
| RETRY_WARN | Specifies the number of warning polls before the interface is deemed to be malfunctioning and the IP addresses associated with it are removed. A value of zero skips the WARN_POLL cycle. | 1 retry |
| ERROR_POLL | Specifies the polling interval used when the interface is deemed to be malfunctioning. failSAFE monitors a malfunctioning interface at this frequency until it determines that the interface has recovered, at which time the polling frequency is set back to the INFO_POLL period. | 30 seconds |
| Previous | Next | Contents | Index |