The procedures in this section explain how to configure your bridge/router as a network node and configure node information to initiate APPN routing. The minimum tasks required to configure the APPN network node are separated into the following procedures:

• Setting up the bridge/router as a network node (also referred to as the local node when working directly at that node)

• Defining links from your system to adjacent network nodes

• Configuring dependent LU support if you have PU 2.0 nodes and PU 2.1 nodes with dependent LUs in your network

• Enabling the network node

Figure 141 provides a flowchart of the basic steps to configure the bridge/router so that it will operate as an APPN network node.

Figure 141 Basic APPN Configuration Steps

Setting Up Your System as a Network Node

The first task in setting up the APPN environment is to configure the local bridge/router (referred in this section as "local node") to serve as a network node. The NETBuilder II system can be configured as a network node only; because the bridge/router does not provide any application programs on the SNA network, it cannot act as an end node or LEN end node. Viewed from the SNA network, the bridge/router network node has only one LU for handling CP-CP sessions.

Prerequisites

Before beginning this procedure, complete the following tasks:

• Log on to the system with Network Manager privilege.

• Set up the ports and paths of your bridge/router according to the procedures described in the Configuring Basic Ports and Paths chapter and the Configuring Advanced Ports and Paths chapter.

• If necessary, use LAN Address Administration (LAA) to reassign MAC addresses for paths that will be sending and receiving APPN traffic.

  You must perform this configuration before starting APPN. For more information on configuring LAA, see the Configuring LAN Address Administration chapter.

• If you are planning to support both APPN and DECnet on the same bridge/router, you must configure DECnet before configuring APPN. Configuring DECnet can change MAC addresses, which will affect any existing APPN configuration. For more information on configuring DECnet, see the Configuring DECnet Routing chapter.

• If necessary, configure the Logical Link Control type 2 (LLC2) data link interface or the data link switching (DLSw) interface for the ports you will use for APPN traffic. For more information on configuring the LLC2 data link interface, see the Configuring the LLC2 Data Link Interface chapter. For more information on configuring DLSw, see the Configuring Data Link Switching for SNA and NetBIOS Networks chapter.

  APPN is affected by parameter settings in other services. For more information, see the Configuring the LLC2 Data Link Interface chapter.

• If you will be sending APPN traffic over SDLC lines, configure the bridge/router for SDLC operation first. For more information on SDLC configuration, see the Configuring Synchronous Data Link Control Connectivity chapter.

• If you will be sending APPN traffic over Frame Relay, configure the Frame Relay interface before configuring the APPN network node. For more information on configuring Frame Relay, see the Configuring Wide Area Networking Using Frame Relay chapter.

• If you are not familiar with APPN routing concepts, see "How APPN ISR Routing Works" later in this chapter.

• See the IBM documents describing APPN architecture listed in "IBM APPN References" later in this chapter.

To set up the bridge/router as a network node, follow these steps:

1 .   Assign a name to the local node using:

SETDefault -APPN LocalNodeName = <netid.cpname> [node_id]

This command creates the fully qualified control point (CP) name by combining the network ID with the CP name you create to identify the node. The fully qualified CP name identifies the network node throughout the APPN network. (When the CP name is used without the network ID, it is called a not fully qualified CP name.) For more information on CP name formats, see "Fully Qualified and Not Fully Qualified CP Name Formats" later in this chapter.

For example, to assign the local node name consisting of the network ID US3COMHQ plus the CP name NB2SF011, enter:

SETDefault -APPN LocalNodeName = US3COMHQ.NB2SF011

CAUTION: Every fully qualified CP name on the APPN network must be unique.

Optionally, you can add a node ID following the network ID. This node ID is used in XID negotiations. For more information, see the description of the LocalNodeName parameter in the APPN Service Parameters chapter in Reference for Enterprise OS Software.

2 .   If desired, change the resistance value of the local node using:

SETDefault -APPN LocalNodeResist = <node_resistance> (0-255)

The resistance value advertises the desirability of routing through the node. Using different values, you can fine-tune your network to set different resistance rates on different nodes so that more traffic is routed over specific nodes.

The value of the LocalNodeResist parameter ranges from 0 to 255. A value of 0 indicates that routing is highly desirable through this node, while a value of 255 indicates routing is not desirable through the node. The default value is 128, or the median. Changing the value is optional.

3 .   Define each local port on the system that will send and receive APPN traffic using:

SETDefault !<port> -APPN PortDef = <DLC type> (LLC2|FR|PPP|DLSW|SDLC|UNdef) <max_btu_size>(99-8192) [ActLimit=<limit>(1-512)] [TGprof=<name>] [HPR=(Yes|No)] [ErrorRecovery=(Yes|No)] [DatMode=(Half|Full)] [ROle=(Neg|Pri|Sec)]]

Use this command to define the type of traffic being sent over the port (DLC type), as well as the maximum basic transmission unit (BTU) size the port will allow. To define the DLC type, enter LLC2 for token ring, Ethernet, FDDI and PPP links. Enter FR for Frame Relay, or DLSw for using Data Link Switching over an IP network. If you specify the DLC type as DLSw, the port number specified must be !0. Do not specify !0 if using a DLC type other than DLSw. Enter SDLC if you will be sending traffic to and from SDLC devices. Enter UNdef to remove a previously-defined port definition DLC type.

If a port has already been defined for a particular DLC type, the port definition must be removed by setting the DLC type to UNdef before it can be changed to another DLC type.

To determine the maximum BTU size to use, first determine the appropriate request/response unit (RU) size, then add an additional nine bytes (three bytes for the request header (RH) plus six bytes for the transmission header (TH) ). The RU size plus the additional nine bytes comprise the BTU size. For more information on the values for the PortDef parameter, see the APPN Service Parameters chapter in Reference for Enterprise OS Software.

For more information about setting the maximum BTU size, see "Setting the Maximum BTU Size" later in this chapter.

Optionally, you can set the activation limit (total number of LLC2 sessions for the port), and if desired, a transmission group (TG) profile for the port. For more information on TG profiles you can use, see the description of the AdjLinkSta parameter in the APPN Service Parameters chapter in Reference for Enterprise OS Software.

CAUTION: The PortDef parameter has an option to provide support for High Performance Routing. The default value for the HPR option is Yes, meaning that HPR is automatically enabled. If you want the port to perform Intermediate Session Routing (ISR) only, you must disable the HPR option by typing HPR=No as part of the command. If you want the port to perform HPR, do not change the HPR value, but note that the functionality and routing methods of HPR may be different from ISR. If you have links between two network nodes with HPR enabled, this configuration will create an HPR subnet in your ISR network. For more information about HPR, see the APPN High Performance Routing chapter.

For example, to configure port 7 as an APPN ISR port to handle Frame Relay traffic with a maximum BTU size of 1033, an activation limit of 128, and to use the TG profile SER256, enter:

SETDefault !7 -APPN PortDef = FR 1033 ActLimit=128 TGprof=SER256 HPR=No

If you specify synchronous data link control (SDLC) as your DLC type, you can specify the DatMode value to either half duplex or full duplex, and you can specify whether the SDLC port will be the primary or secondary device in session negotiation, or whether the role will be negotiable. If you set your DLC type to SDLC, when configuring SDLC devices as adjacent link stations or as DLUr link stations you must use the SdlcAdjLinkSta or SdlcDlurLinkSta parameters, respectively.

For example, to configure port 6 as an APPN ISR port to handle SDLC traffic you can set the following attributes: maximum BTU size of 1033, activation limit of 254, TG profile of Ser19.6, and full duplex data transmission mode. To configure these attributes and set the local node as the primary device in session negotiation, enter:

SETDefault !6 -APPN PortDef = SDLC 1033 ActLimit=254 TGProf=Ser19.2 HPR=No DatMode=Full ROle=Pri

Repeat this step for each port on the system used to send and receive APPN sessions.

4 .   If desired, define the characteristics of each APPN port configured in the previous step using:

SETDefault !<port> -APPN PortCHar = [EffectCap=<string>] [ConnectCost=<0-255>] [ByteCost=<0-255>] [Security=<string>] [PropDelay=<string>] [Usd1=<0-255>] [Usd2=<0-255>] [Usd3=<0-255>]

Using this parameter, you can specify optional settings for the port's effective capacity, connection cost, byte cost, propagation delay, and three user-configurable settings. For more information on the PortCHar parameter, see the APPN Service Parameters chapter in Reference for Enterprise OS Software.

5 .   Repeat this procedure for each bridge/router functioning as a network node in your APPN network.

After you have set up the bridge/router as a network node, you must then define the links to other network nodes in the APPN network. Proceed to the next section.

Defining Links to Other Network Nodes

After you have performed the basic configuration of the local node, the next step is to define the adjacent link stations to other network nodes. An adjacent link station is the local information regarding a link to an adjacent node. The adjacent link station is the link definition, or the representation of the link as seen by the network node.

Two network nodes that connect and exchange data are called partner nodes. To configure an adjacent network node as a partner node, you must configure an adjacent link station to the other node; in this situation, the other network node does not need to configure an adjacent link station to your local node. Only one of the partner nodes needs to configure the other as an adjacent link station.

You can add links to other network nodes dynamically after the network node is enabled. For more information on dynamic configuration, see "Dynamic Configuration Options" later in this chapter.

Figure 142 is an example of a network with three different network nodes, each with its own local network, on a larger FDDI ring. In this topology, network nodes A and B are partner nodes to each other, network nodes A and C are partner nodes, and network nodes B and C are partner nodes.

For each of these partner node pairs, only one network node needs to configure its partner as an adjacent link station if both nodes are NETBuilder II bridge/routers. If one of the partner nodes is not a NETBuilder II bridge/router, the links may need to be configured in both directions, depending on the device.

For example, if network node A configures node B as an adjacent link station, then network node B does not also need to configure node A as an adjacent link station. If both partner nodes are 3Com bridge/routers, this situation applies. You can configure links in both directions, but it is not required.

Figure 142 Network Nodes as Adjacent Link Stations (Example)

Procedure

To define adjacent link stations to partner network nodes, follow these steps:

1 .   If you set the port DLC type (configured with step 3 of the previous procedure) to LLC2, FR, PPP, or DLSw, go to step a. If you set the port DLC type to SDLC in the previous procedure, go to step b.

a .   If you previously set the port DLC type to LLC2, FR, PPP, or DLSW, define the adjacent link station using:

ADD !<port> -APPN AdjLinkSta <type>(NN|EN|Learn) <max_btu_size>(99-8912) [[Cmac|Ncmac] dest media addr] [Sap=<num>] [CPName=[netid.]cpname] [Nodeid=<ID>] [LinkName=<name>] [TGprof=<name>] [AutoStart=(Yes|No)] [CPSess=(Yes|No)] [HPR=(Yes|No)] [ErrorRecovery=(Yes|No)]

Make sure you specify the node type as NN. In addition, specify the maximum BTU byte size and the media address of the destination node (or DLCI if running Frame Relay over a virtual port). Optionally, you can set the following for the destination node: the CP name and the node name, the node ID, the link name, the TG profile, whether the link will support AutoStart, and whether control point-to-control point (CP-CP) sessions will be activated with the adjacent node. For more information on the AdjLinkSta parameter, see the APPN Service Parameters chapter in Reference for Enterprise OS Software.

CAUTION: The AdjLinkSta parameter has an option to provide support for High Performance Routing. The default value for the HPR option is Yes, meaning that HPR is automatically enabled. If you want the link station to support Intermediate Session Routing (ISR) only, you must disable the HPR option by typing HPR=No as part of the command, and you also must disable HPR on the port by specifying HPR=No as part of the SETDefault !<port>-APPN PortDef command. If you only disable HPR on the adjacent link station but not the port, then HPR will not be totally disabled for APPN connections. If you want the link station to support HPR, do not change the HPR value, but note that the functionality and routing methods of HPR may be different from ISR. For more information about HPR, see the APPN High Performance Routing chapter.

If you do not define a link name, then the local network node will assign a unique link name to the link. (You will need the link name to complete step 2. If you do not assign a link name, you can obtain the link names assigned by the system using the SHow -APPN LinkStaCONTrol command.)

For example, to add a link to an ISR network node named "FINANCE" to port 3 with a maximum BTU size of 1033 (specifying the appropriate MAC address and SAP) and a fully-qualified CP name "HQ.Finance" (with a link named FINANCE3), profile SER64, and to activate a CP-CP session when the node comes up, enter:

ADD !3 -APPN AdjLinkSta NN 1033 N100040C08ACE Sap=08 CPName=HQ.FINANCE LinkName=FINANCE3 TGprof=SER64 CPSess=Yes HPR=No

For information on how to obtain the MAC address of the node, see the documentation for the end node device or applications.

To obtain the MAC address of another 3Com bridge/router acting as a network node, enter the SHow -SYS Configuration command on the second bridge/router. Enter the MAC address of the port number over which the link is established, making sure to enter the address in the correct format.

If you set the -SYS MacAddrFmt parameter to noncanonical, then you do not need to precede the MAC address with N or Ncmac. If you do not change the -SYS MacAddrFmt parameter, then the default will be canonical, and you will need to precede the MAC address with N for noncanonical format. If the -SYS MacAddrFmt parameter is set to Default, then the system will assume that the MAC address is in noncanonical format for token ring and FDDI ports, and canonical format for all other port types. For more information on MAC address format options for APPN, see "MAC Address Format Options for APPN" later in this chapter.

b .   If you previously set the port DLC type to SDLC, define the SDLC adjacent link station using:

ADD !<port> -APPN SdlcAdjLinkSta <type>(NN|EN|Learn) <max_btu_size>(99-8912) <station addr>(Hex 1-FE) [CPName=<[netid.]cpname] [Nodeid=<ID>] [LinkName=<name>] [TGprof=<name>] [AutoStart=(Yes|No)] [CPSess=(Yes|No)] [HPR=(Yes|No)] [ErrorRecovery=(Yes|No)] [SendWindow=<num>] [ContactTimer=<num>] [NoRspTimer=<num>] [NoRspTimRetry=<num>]

Make sure you specify the node type as NN. In addition, specify the maximum BTU byte size and the station address of the destination node. Optionally, you can set the CP name of the destination node and the node name, the node ID, the link name, the TG profile, whether the link will support AutoStart, and whether CP-CP sessions will be activated with the adjacent node. You can also set the SDLC SendWindow, ContactTimer, NoRspTimer, and NoRspTimRetry values. You can enter these options in any combination. The default value for AutoStart is yes, which means when you enable the network node, the link will be activated automatically. For the SDLC connection to take place, both SDLC partner nodes must be configured as SDLC adjacent link stations using the SdlcAdjLinkSta parameter.

For more information on the SdlcAdjLinkSta parameter, see the APPN Service Parameters chapter in Reference for Enterprise OS Software.

CAUTION: The SdlcAdjLinkSta parameter has an option to provide support for High Performance Routing. The default value for the HPR option is Yes, meaning that HPR is automatically enabled. If you want the link station to support Intermediate Session Routing (ISR) only, you must disable the HPR option by typing HPR=No as part of the command, and you must also disable HPR on the port by specifying HPR=No as part of the SETDefault !<port>-APPN PortDef command. If you only disable HPR on the adjacent link station but not the port, then HPR will not be totally disabled for SDLC connections. If you want the link station to support HPR, do not change the HPR value, but note that the functionality and routing methods of HPR may be different from ISR. Note also that for HPR over SDLC to work properly, HPR must be configured on both partner network nodes. For more information about HPR, see the APPN High Performance Routing chapter.

If you do not define a link name, then the local network node will assign a unique link name to the link. (You will need the link name to complete step 2. If you do not assign a link name, you can obtain the link names assigned by the system using the SHow -APPN LinkStaCONTrol command.)

For example, to add an SDLC link named "SDLC001" on port 4 to a network node named "HQ.FINANCE" you can set the following attributes: a station address of hex FE, maximum BTU size of 1033, TGprofile SER64, activation of a CP-CP session when the node comes up, no support for HPR, SendWindow size of 4, ContactTimer setting of 2 seconds, NoRspTimer setting of 2000 milliseconds, and a NoRspTimRetry setting of 6. To add this link and configure the attributes, enter:

ADD !4 -APPN SdlcAdjLinkSta NN 1033 FE CPName=HQ.FINANCE LinkName=SDLC001 TGprof=SER64 CPSess=Yes HPR=No SendWindow=4 ContactTimer=2 NoRspTimer=2000 NoRspTimRetry=6

The ContactTimer, NoRspTimer and NoRspTimRetry values are valid only if the local network node is the primary station on the SDLC link. Also, The SDLC link must be configured before configuring APPN over SDLC. For more information on SDLC, see the Configuring Synchronous Data Link Control Connectivity chapter.

APPN over SDLC connections is supported on all types of HSS 3-Port modules, including V.35, RS-232, and RS-449.

When you configure SDLC adjacent link stations for APPN, if an active link becomes inactive and you change the port definition using the PortDef parameter, the link remains inactive. If you try to reactivate the link using the SET -APPN LinkStaCONTrol command, the link will reactivate within 30 seconds. To activate the link immediately, you must enable the APPN port using the SET -APPN PortControl = Enable command.

2 .   After you have defined the link to the adjacent network node, you define the characteristics of the link using:

SETDefault -APPN LinkStaCHar = <LinkStation name> [EffectCap=<string>] [ConnectCost=<0-255>] [ByteCost=<0-255>] [Security=<string>] [PropDelay=<string>] [Usd1=<0-255>] [Usd2=<0-255>] [Usd3=<0-255>]

Set attributes such as byte cost, security, connection cost, and capacity for the adjacent link station with the LinkStaCHar parameter. You can set any number of these options in any combination when entering the command. For more information on configuring this parameter, see the APPN Service Parameters chapter in Reference for Enterprise OS Software.

For example, to define the characteristics of the link named "FINANCE3" for an effective capacity of 9600, a byte cost of 128, and a security value of SECurcnd, enter:

SETDefault -APPN LinkStaCHar = FINANCE3 EffectCap=9600 ByteCost=128 Security=SECurcnd

CAUTION: If you change any of the default characteristics for a link to a network node, the characteristic must also be changed on the partner network node. For example, if you set the security level of the TG as GUarded on the local node, then you must also configure the security level as GUarded on the partner node. Other- wise, the characteristic will be valid in one direction only, from the local node to the partner node; the characteristic on the link in the opposite direction will not match.

3 .   Repeat steps 1 and 2 for each network node that will establish direct connections (or links) with the local network node.

If you did not assign link names using the AdjLinkSta parameter, the system will assign them. To obtain a list of link names assigned, enter:

SHow -APPN LinkStaCONTrol

You can configure two or more links to the same node using parallel TGs. For more information on configuring parallel TGs, see "Configuring Parallel Transmission Groups" later in this chapter.

If you need to configure support for dependent LUs, proceed to the next section. If you do not need to do so, proceed to "Enabling the Network Node and Activating Links" later in this chapter.

Dependent logical unit support is required where you have PU type 2.0 or 2.1 nodes in the local network node's domain that will access a host via LU types dependent on the SSCP. LU types that are dependent on a Session Services Control Point (SSCP) are types 1, 2 ,3, or type 6.2. Configuring dependent LU support on the network node enables the network node to act as a Dependent LU Requestor (DLUr) to enable a PU type 2.0 or 2.1 node to access the host, which acts as the Dependent LU Server (DLUs). You can have many PUs with dependent LUs accessing one primary DLUs and one backup DLUs.

PU type 2.0 nodes are nodes which do not have a control point. As a result, LUs on these nodes are "dependent" on SSCP services provided by the DLUs. PU type 2.1 nodes can have both independent and dependent LUs. The dependent LUs require the SSCP services from the host, while independent LUs do not.

Figure 143 is an example of PU type 2.0 and 2.1 nodes accessing a host DLUs with a bridge/router acting as the DLUr. In the configuration, the DLUs is upstream from the network node bridge/router, while the PU 2.0 and 2.1 nodes are downstream from the network node.

Figure 143 DLUr and DLUs Environment

This section is divided into two procedures:

• Defining your DLUs

• Configuring links to nodes requesting DLUr services

  If the DLUs will be accessed over a WAN using Frame Relay, you also will need to configure the APPN Frame Relay interface.

Figure 144 is an example of a DLUr and DLUs configuration. In the configuration, the downstream physical unit (DSPU) defined in the host configuration must match the DSPU name configured on the network node using the DlurLinkSta parameter. For the PU 2.x to access the host, the MAC address of the local node must be configured as the host address on the PU. The PU thinks the host address is for the remote host providing the service, but the network node address is used to establish the session to the network node. The network node then establishes the SSCP-LU and SSCP-PU sessions with the host.

Figure 144 DLUs and DLUr Configuration

Defining the Default DLUs and Backup DLUs

When you define the DLUs on the network node, you are configuring the default DLUs and backup DLUs that the local node (acting as the DLU requestor) will send the SSCP traffic to. The DLUs does not need to be directly connected to the local network node, and there can be multiple network nodes in between.

When a dependent LU makes a session request to the local network node for a dependent LU server, the local node tries to find the DLUs using the following hierarchy of steps:

• The system first looks for the DLUs assigned to the DLUr link station using the DlurLinkSta parameter (see "Defining Downstream Links to Nodes with Dependent LUs").

• If that DLUs is unavailable or no DLUs was assigned to the DLUr link station, then the system tries to use the backup DLUs assigned using the DlurLinkSta parameter.

• If the backup DLUs is unavailable or no backup DLUs was assigned to the DLUr link station, then the local node tries the default DLUs configured using the DlurDefaults parameter.

• If the default DLUs is unavailable, then the local node tries the default backup DLUs configured using the DlurDefaults parameter.

To configure the default DLUs and backup DLUs, use:

SETDefault -APPN DlurDefaults [Dlus=(<name>|UNdef)] [Backup=(<name>|UNdef)]

This command specifies the default DLUs and the backup DLUs. You can configure one default DLUs and one default backup DLUs on the local network node.

For example, to configure a primary DLUs named "VTAM1" and a backup DLUs named "VTAM2," enter:

SETDefault -APPN DlurDefaults = DLUS=VTAM1 BACKUP=VTAM2

To change the name of a primary or backup DLUs, repeat the command and enter a different name. To remove the name of a primary or backup DLUs, enter the command but specify "UNdef." For example, to remove VTAM2 as the backup DLUs, enter:

SETDefault -APPN DLurDefaults = BACKUP=UNdef

You can have any number of intermediate network nodes in your APPN network between the local network node DLUr and the DLUs host. To define the upstream link for the path to the DLUs, you configure the upstream network node as a normal adjacent link station. No special configuration is required. The only requirement is that you must be able to establish 6.2 LU to LU sessions between the local network node DLUr and the DLUs host.

Defining Downstream Links to Nodes with Dependent LUs

If you have PU 2.0 nodes or PU 2.1 nodes with dependent LUs in the network node domain, then you must configure DLUr link stations to each of these nodes. Because these nodes function differently from normal APPN nodes, you cannot configure DLUr link stations and normal adjacent link stations to the same node. However, a node can have CP-CP sessions and still require DLUr. If that is the case, add these nodes using this procedure.

To add a link to PU 2.0 and 2.1 nodes that require DLUr services, follow these steps:

1 .   Select one of the following:

a .   If you are running normal APPN traffic to and from DLUr link stations, define each DLUr link station using:

ADD !<port> -APPN DlurLinkSta <max_btu_size(256-8912)> <[Cmac | Ncmac] dest media addr> <dspu name> [Sap=<num>] [Nodeid=<ID>] [LinkName=<name>] [Dlus=<[netid.]name|UNdef>] [Backup=<[netid.]name|UNdef>] [TGprof=<name>] [AutoStart=(Yes|No)] [CPSess=(Yes|No)] [PU2=(Yes|No)] [HPR=(Yes|No)] [ErrorRecovery=(Yes|No)]

Using this command, you specify the maximum BTU size, the destination address of the DLUr link station, and the DSPU name of the PU 2.0 device. If the host will activate the session with the DLUr link station, then the DSPU name you configure here must match the name on the host configuration.

You also specify the primary DLUs and backup DLUs that the DLUr link station will access. If a primary and/or backup DLUs is not specified, then the default primary and backup DLUs configured using the DlurDefaults parameter will be used. The default for AutoStart is No. If you want the link to automatically be activated when the network node is enabled, specify AutoStart=Yes.

b .   If you set the port DLC type to SDLC to run SDLC traffic to and from DLUr link stations, define each SDLC DLUr link station using:

ADD !<port> -APPN SdlcDlurLinkSta <max_btu_size>(265-8912) <station addr>(Hex 1-FE) <dspu name> [Nodeid=<ID>] [LinkName=<name>] [Dlus=[netid.]name] [Backup=[netid.]name] [TGprof=<name>] [AutoStart=(Yes|No)] [PU2=(Yes|No)] [HPR=(Yes|No)] [CPSess=(Yes|No)] [SendWindow=<num>] [ContactTimer=<num>] [NoRspTimer=<num>] [NoRspTimRetry=<num>]

Using this command, you specify the maximum BTU size, the destination address of the DLUr link station, and the DSPU name of the PU 2.0 device. If the host will activate the session with the DLUr link station, then the DSPU name you configure here must match the name on the host configuration.

You also specify the primary DLUs and backup DLUs that the DLUr link station will access. If a primary and/or backup DLUs is not specified, then the default primary and backup DLUs configured using the DlurDefaults parameter will be used. You can also specify SDLC attributes such as the SendWindow, ContactTimer, NoRspTimer, and NoRspTimRetry values. For more information on these values, see the APPN Service Parameters chapter in Reference for Enterprise OS Software.

APPN over SDLC connections is supported on all types of HSS 3-Port modules, including V.35, RS-232, and RS-449.

2 .   Repeat the previous step for each PU 2.0 or 2.1 node that will access a DLUs through the local network node.

Using VTAM Program Temporary Fixes

VTAM Program Temporary Fixes (PTFs) are required on a mainframe when APPN DLU services are used. Mainframe network management (NetView) services will not function for downstream physical units (PUs) if the PTFs are not installed. VTAM Version 4.2 requires PTF #UW20787. VTAM Version 4.3 requires PTF #UW20788.

Symptoms of this problem result from a lack of network management data for PUs that are downstream of a NETBuilder II using APPN DLU services. The NetView message "AAU251I AAUDRTIB 02 UNEXPECTED SENSE CODE X'1002' ENCOUNTERED FOR TARGET=pu_name" is printed in the log file when this problem occurs.

Enabling the Network Node and Activating Links

After you have set up the bridge/router as a network node and defined links to other network nodes you can now enable the network node and activate the links you defined in the previous sections.

To enable the network node and activate the links, follow these steps:

1 .   To enable the bridge/router to function as an APPN network node, enter:

SETDefault -APPN CONTrol = Enable

When you enable the APPN network node, you will receive a message similar to the following:

Wed Dec 31 16:11:15 1995 LOCAL NETWORK NODE US3COMHQ.GOLD IS STARTED

After the network node is enabled, the bridge/router can communicate with other APPN network nodes, and can accept incoming link requests from end nodes.

You can totally disable the network node, or you can dynamically disable the network node so that when you reboot the bridge/router, the network node automatically is re-enabled. For more information on disabling the network node, see "Disabling the Network Node" later in this chapter.

2 .   If you configured adjacent link stations and you set AutoStart to No or configured DLUr link stations and did not set AutoStart to Yes, activate these links using:

SET -APPN LinkStaCONTrol = <LinkName> Activate

Repeat this step for each of the links you defined in the previous sections. After you have enabled the network node and activated your basic links, the basic network node will be operating. Other network nodes will be able to initiate sessions with the local node and receive sessions from the local node. In addition, end nodes in the local node's domain will be able to initiate session requests with the network node.

For additional configuration, see "Customizing the APPN Router" later in this chapter.

After the network node is enabled, you can configure different options such as adjacent link stations, transmission group (TG) characteristics, and port characteristics. Depending on the task, you can configure these options without disabling the network node or disrupting sessions on ports or TGs not affected. Table 35 lists some of the APPN entities that you can and cannot dynamically configure while the network node is operating.

Table 35 APPN Dynamic Configuration Options

Configuration Option	Parameter	Dynamic Configuration Allowed	Additional Information
Predefine LEN end node LUs	AdjLenDef	Yes
Add or delete adjacent link stations	AdjLinkSta	Yes	Port the link station is mapped to can be enabled while configuring. Must activate link using LinkStaCONTrol parameter to take effect. To delete link station, must deactivate it first.
Adjacent link station characteristics	LinkStaCHar	Yes	Cannot make changes if link is active. You must first deactivate the link and then reactivate it after making the change.
Create a customized class of service, and change node row and TG row values	ConfigCos COSNodeRow COSTgRow	Yes	See the Configuring APPN Class of Service chapter for more information.
Enable connection network	ConnNetworkDef	Yes	The port the connection network is added to can be enabled when configuring.
Define a customized class of service to the system	CosDef	Yes	See the Configuring APPN Class of Service chapter for more information.
Add or delete directory entries	DirectoryEntry	Yes
Set the default DLUs and backup DLUs	DlurDefaults	Yes
Define DLUr link stations	DlurLinkSta	Yes	If the link is active, you cannot make changes. Deactivate the link before making changes.
Activate and deactivate link stations	LinkStaCONTrol	Yes
Set the local node name and resistance	LocalNodeName LocalNodeResist	No	Must be configured before enabling the network node.
Map mode names to a class of service	ModetoCosMap	Yes	See the Configuring APPN Class of Service chapter for more information.
Change APPN port characteristics and define the APPN port	PortCHar PortDef	Yes	If port is activated, must first deactivate the port using PortCONTrol parameter before changing characteristics or definitions. Port must then be reactivated after making changes.
Activate and deactivate APPN port	PortCONTrol	Yes
Set queue priority	QueuePriority	Yes	See the Prioritizing Multiprotocol Data chapter for more information.
Add or delete adjacent SDLC link stations	SdlcAdjLinkSta	Yes	Port the link station is mapped to can be enabled while configuring. Must activate link using LinkStaCONTrol parameter to take effect. To delete link station, must deactivate it first.
Define SDLC DLUr link stations	SdlcDlurLinkSta	Yes	If the link is active, you cannot make changes. Deactivate the link before making changes.

Configuring the APPN Router for Wide Area Networks

To configure your APPN router to perform routing over Frame Relay, see the Configuring Wide Area Networking Using Frame Relay chapter. APPN routing over SMDS and X.25 is not supported unless you are using DLSw. For information on routing over PPP connections, see the Configuring Wide Area Networking Using PPP chapter. For information on wide area networking using ISDN, see the Configuring Wide Area Networking Using ISDN chapter. For more information on data link switching, see the Configuring Data Link Switching for SNA and NetBIOS Networks chapter.

APPN routing over ATM is not supported.