Start of change

Example details: iSeries server to iSeries server connection using Enterprise Extender (HPRIP)

This example shows the matching parameters between an iSeries™ server connecting to another iSeries server using Enterprise Extender. The following table describes the relationships shown in Figure 8 between the local iSeries system values and the remote iSeries values. The values shown and described here are example values.

Table 10. Local iSeries system value relationships to remote iSeries system values
Local iSeries system (ALPHA) parameter name and value iSeries parameter value description Remote iSeries (BETA) system values
Controller description: CTLD = BETACTL The value for this local iSeries parameter matches the name for the remote iSeries name, and vice versa. Controller description: CTLD = ALPHACTL
Controller description: LINKTYPE = *HPRIP The values for iSeries parameter LINKTYPE must be *HPRIP on both systems to use Enterprise Extender. Controller description: LINKTYPE = *HPRIP
Controller description: RMTINTNETA = 9.18.34.223 The value for this local iSeries parameter matches the value for the remote iSeries IP address, and vice versa. Controller description: RMTINTNETA = 9.18.33.40
Controller description: RMTCPNAME = BETA The value for this local iSeries parameter matches the value for the remote iSeries CP name, and vice versa. Controller description: RMTCPNAME = ALPHA
Controller description: RMTNETID = ALPHA The value for this local iSeries parameter matches the value for the remote iSeries network ID if they are in the same network. Controller description: RMTNETID = ALPHA
Controller description: DSAP = 04 The value for this local iSeries parameter matches the value for the remote iSeries parameter SSAP. Controller description: DSAP = 04
Controller description: SSAP = 04 The value for this local iSeries parameter matches the value for the remote iSeries parameter DSAP. Controller description: SSAP = 04
Note: The following fields are added for Enterprise Extender:
  • RMTINTNETA : Remote internet address. An IPv4 internet address in the format of xxx.xxx.xxx.xxx..
  • LCLINTNETA: Local internet addresss. An IPv4 internet address in the format of xxx.xxx.xxx.xxx. If the value of *SYS is not selected, the output traffic for this controller will go through the defined IP address. Otherwise, the output traffic will use the TCP/IP routing tables to determine the best interface to send the data.
  • LDLCTIMR: LDLC timers. These will control the timers required by the LDLC protocol to retry a send, the number of retries, and how often a test frame will be sent to the remote. A test frame will only be sent to the remote system if data hasn't been received from the remote system during that time period.
  • LDLCLNKSPD: This gives the APPN value of link speed. Possible values are: *CAMPUS (4 Mbps), *WAN (56 kbps), 10 Mbps, 4 Mbps, 16 Mbps, 100 Mbps, *MAX (greater than 100Mbps), and *MIN (less than 1200 bps). APPN uses this value to calculate the weight of this particular link when calculating the path of any request.
  • LDLCTMSGRP: The rest of the APPN values are used to calculate the link weight: cost per connection, cost per byte, link security, and propagation delay. All of these values are used by APPN to calculate the best route to a remote host. These values only appear when the LDLCLNKSPD parameter has a value other than the default.
End of change