DEVICE and LINK - LAN Channel Station and OSA devices statement

Use the DEVICE statement to specify the name and hexadecimal device number of IBM® Ethernet OSA.

Use the LINK statement to define an Ethernet network LCS LINK statement.

Requirement: You must use a separate LINK statement for each link associated with an LCS device.

Each network interface on the OSA is considered a separate DEVICE. For example, if you are using both ports on the OSA-2 card, you need to code a DEVICE and LINK pair for each port. For more information about missing interrupt handler (MIH) considerations with TCP/IP devices, see Missing interrupt handler factors.

Syntax

Rule: Specify the parameters in the order shown here.

Read syntax diagramSkip visual syntax diagramDEVicedevice_nameLCSdevice_numberNONETMANNETMANIOBUFFERSIZE 20480IOBUFFERSIZE  buffer_sizeNOAUTORESTARTAUTORESTART

Parameter

device_name
The name of the device. The maximum length is 16 characters. The same name is specified on the LINK statements.
LCS
Specifies the device is a LAN Channel Station.
device_number
The hexadecimal device number (in the range 0 - FFFF) of the LCS. device_number +1 is also used by the TCP/IP address space.
NETMAN
Specifies that this device is a 3172 that supports the IBM Enterprise-specific MIB variables for 3172.

Requirement: NETMAN must be coded before IOBUFFERSIZE.

NONETMAN
Specifies that this device is not used for NETMAN data retrieval.
IOBUFFERSIZE buffer_size
Specifies the I/O buffer size. The buffer size must be 20K, 20 480, 32K, or 32 768.
Guidelines:
  • The configured I/O buffer sizes for the host and for the device must match. A buffer size mismatch can cause packet loss or I/O errors, which results in the deactivation of the LCS connection.
  • If the LCS device supports an option to configure a 32K buffer size, then configuring both the device and the TCP/IP profile to 32K provides the best performance. If the device does not support this option, then specify (or default) to 20K in the TCP/IP profile.
AUTORESTART | NOAUTORESTART
Controls device failure reactivation behavior.
NOAUTORESTART
For most device failures, specifying the NOAUTORESTART value indicates that the TCP/IP address space does not attempt to reactivate this device.
AUTORESTART
In the event of a device failure, the TCP/IP address space attempts to reactivate the device. For more information, see Recovering from device failures.

LINK statement for Ethernet network LCS

This LINK statement is used to define an Ethernet link on an IBM 3172 Interconnect Controller and IBM 8232 LAN Channel Station (LCS) or OSA device.

Syntax

Rule: The optional parameters on the LINK statement following the device_name parameter can be specified in any order.

Read syntax diagramSkip visual syntax diagramLINKlink_nameETHERNet802.3ETHEROR802.3link_numberdevice_nameIFSPEED 4000000IFSPEED  ifspeedIFHSPEED  ifhspeedSECCLASS 255SECCLASS  security_classNOMONSYSPLEXMONSYSPLEX

Parameter

link_name
The name of the link. The maximum length is 16 characters.
ETHERNET
Standard Ethernet protocol only.
802.3
IEEE 802.3 protocol only.
ETHERor802.3
Both standard Ethernet and IEEE 802.3 protocols. When ETHERor802.3 is specified, address resolution packets (ARP) for both protocols are generated. All devices on the network must be able to process or discard these packets.
link_number
The relative adapter number (0 for the first Ethernet protocol network in the LCS, 1 for the second Ethernet protocol network, and so on). If defining OSA, this value is the port number on the OSA.
device_name
The device_name must be the same name as specified in the DEVICE statement. The maximum length is 16 characters.
IFSPEED ifspeed
An optional estimate of the interface's current bandwidth in bits per second. The minimum value that can be specified for ifspeed for an LCS link is 0, the maximum value is 2 147 483 647. The default is 4 000 000. This value is accessible to SNMP for management queries, but has no effect on operation of the device.
IFHSPEED ifhspeed
An optional estimate of the interface's current bandwidth in one million bits per second units. The minimum value that can be specified for ifhspeed for an LCS link is 0, the maximum value is 2147. The default is 4. This value is accessible to SNMP for management queries, but has no effect on operation of the device.
SECCLASS security_class
Use this parameter to associate a security class for IP filtering with this interface. In order for traffic over the interface to match a filter rule, the filter rule must have the same security class value as the interface or a value of 0. Filter rules can be specified in the TCP/IP profile or in an IP Security policy file read by the Policy Agent. Filter rules can include a security class specification on the IpService statement in an IP Security policy file or on the SECCLASS parameter on the IPSEC statement in the TCP/IP profile.

Valid security classes are identified as a number in the range 1 - 255. The default value is 255. For more information about security class values, see z/OS Communications Server: IP Configuration Guide.

Restriction: The TCP/IP stack ignores this value if IPSECURITY is not specified on the IPCONFIG statement.

MONSYSPLEX | NOMONSYSPLEX
Specifies whether or not sysplex autonomics should monitor the link's status.
NOMONSYSPLEX
Specifies that sysplex autonomics should not monitor the link's status. This is the default value.
MONSYSPLEX
Specifies that sysplex autonomics should monitor the link's status.

Restriction: The MONSYSPLEX attribute is not in effect unless the MONINTERFACE keyword is specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement. The presence of dynamic routes over this link is monitored if the DYNROUTE keyword is also specified on the GLOBALCONFIG SYSPLEXMONITOR profile statement.

Steps for modifying

See Modifying DEVICE and LINK statements for modifying information.

Examples

  • In this example, LCS1 is an Ethernet adapter. 
    DEVICE LCS1 LCS BA0
LINK ETH1 ETHERNET 1 LCS1
  • This example shows how you might code DEVICE, LINK, and related statements for an LCS connection. 
    DEVICE LCS1 LCS BA0

LINK ETH1 ETHERNET 0 LCS1
HOME

128.50.17.1 ETH1
GATEWAY
;
; Network First hop Driver Packet size Subnet mask Subnet value

128.50 = ETH1 1500 0.0.240.0 0.0.16.0
DEFAULTNET 128.50.17.2 ETH1  DEFAULTSIZE 0
;
; link maxmtu metric subnet mask dest addr
; BSDROUTINGPARMS false

; ETH1 1500 0 255.255.240.0 0
; ENDBSDROUTINGPARMS
;
START LCS1
In this example of an OSA-2 card,  LCS2 is an
ETHERNET Port 1.

DEVICE LCS2 LCS BA2
LINK ETH1 ETHERNET 1 LCS1
  • In this example of an OSA-2 card, LCS2 is an ETHERNET Port 1. 
    DEVICE LCS2   LCS           BA2
LINK ETH1  ETHERNET 1 LCS1

Usage notes

When an OSA-Express® feature is being shared between multiple stacks (OSA port sharing), you need to consider how to configure the OSA address table (OAT). Use the OAT definitions to control the stack to which OSA sends datagrams and ARP packets for specific destination IP addresses. OSA also allows two TCP/IP stacks sharing the port to act as IP routers: a PRIMARY stack and a SECONDARY stack. When an OAT is configured, OSA processes inbound packets as follows:

  • If the IP address is configured for a given stack in the OAT, then OSA sends the packet to that stack.
  • Otherwise, if a PRIMARY entry is defined in the OAT, then OSA sends the packet to the stack configured as PRIMARY (if active).
  • Otherwise, if a SECONDARY entry is defined in the OAT, then OSA sends the packet to the stack configured as SECONDARY (if active).
  • Otherwise, OSA discards the packet.

Guideline: Configure the OAT as follows:

  • Always configure an OAT entry containing the TCP/IP HOME address associated with the LINK defined in the TCP/IP Profile.
  • If you are using Virtual IP Addressing (VIPA) on the LAN, configure OAT entries containing the TCP/IP stack's Virtual IP Addresses.
  • If the stack has multiple OSAs onto the same LAN, then configure an OAT entry for the HOME IP address of each of these OSAs. This enables you to take advantage of the fault tolerance provided by the interface takeover (ARP takeover) function.
  • To enable a TCP/IP stack to act as a router, configure one of the OAT entries as PRIMARY, and enable IP forwarding (IPCONFIG DATAGRAMFWD in the TCP/IP Profile) on the TCP/IP stack acting as PRIMARY. Likewise, to enable a second stack to back up the PRIMARY router, configure one of the OAT entries as SECONDARY, and enable IP forwarding on the stack acting as SECONDARY. For more information, see Open Systems Adapter-Express Customer's Guide and Reference.

Related topics