IBM Networking

Document ID: 12291

Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configure
      Configurations
      Matching DLSw Configuration Statements
Verify
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides a sample configuration for IBM 5494 and 5394 with T2.1 RPQ.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

An IBM 5394 installed with IBM RPQ 8Q0775 acts as a Physical Unit 2.1 (PU2.1) device.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

For more information on document conventions, refer to Cisco Technical Tips Conventions.

Configure

In this section, you are presented with the information to configure the features described in this document.

Note: In order to find more information on the commands used in this document, use the Command Lookup Tool ( registered customers only) .

Configurations

In order to create definitions manually, configure the following under the operate LAN line resource:

CRTCTLAPPC CTLD(RMT5394C) LINKTYPE(*LAN) ONLINE(*NO) +
RMTCPNAME(CP5394) EXCHID(05F000C3) +
ADPTADR(4000549400C3) NODETYPE(*CALC)
  


!--- The block ID that gets passed through in the exchange identification 
!--- (XID) is a 073 for the IBM 5494, and is a 05F for the 5394. The idnum  
!--- portion is 000 + C3 = 000C3, where the C3 is the SDLC station 
!--- address of the 5394 or 5494.


CRTDEVAPPC DEVD(RMT5394D) RMTLOCNAME(CP5394) +
ONLINE(*NO) CTL(RMT5394C) MODE(QPCSUPP)
CRTCTLRWS CTLD(RWS5394C) TYPE(5394) MODEL(1) +
LINKTYPE(*NONE) ONLINE(*NO) +
RMTLOCNAME(CP5394)
 


!--- You are able to specify a RMTLOCNAME by specifying a LINKTYPE(*NONE) 
!--- on the RWS controller. 
!--- This is how the 5394 controller  
!--- (T1.0 PU) is tied to the APPC controller. The connection  
!--- is made through the APPC device (ILU) that you created.


CRTDEVDSP DEVD(RWS5250D) DEVCLS(*RMT) TYPE(3486) +
MODEL(BA) LOCADR(00) ONLINE(*NO) +
CTL(RWS5394C) DROP(*NO)

On the IBM 5394 configuration, you need to match fields 11 through 16:

field 11: NETID must match the NETID in the "DSPNETA"
field 12: LU name of the 5394 must match RMTLOCNAME
field 13: CP name of the 5394 must match RMTCPNAME
field 14: Mode used by 5394 must match MODE
field 15: NETID must match the NETID in the "DSPNETA"
field 16: LU name of AS/400 must match LOCLOCNAME in "DSPNETA"

Note: The configuration also works when you set the CP and LU to the same name. This is sometimes easier when trying to bring the node up initially.

Matching DLSw Configuration Statements

Enter the following to get the connection started:

sdlc role prim-xid-poll   ()



!--- A null is initially sent. However, the XID of the 5394 
!--- gets passed directly through after the initial response (05F000C3 
!--- in this case).
 

sdlc vmac xxxx.xxxx.xxxx plus the sdlc address yy = xxxx.xxxx.xxyy

This must match ADPTADR(4000549400C3).

Notes:

• Set field 3, sub-field 3 to 1 (point-to-point). If field 3, sub-field 3 is set to 0 (multipoint ), the 5394 does not respond to the null-XID; the null-XID is sent to a broadcast address, FF. When set to multipoint, the 5394 only responds to its SDLC address. RTS is also down when the controller is not transmitting, even though field 3 subfield 2 is set to 1 for full duplex (check the serial interface display). If set to duplex and point-to point, RTS is up continuously.

• Be aware that field 2 on the first 5394 configuration screen is the SDLC station address, and needs to match the sdlc address yy. The sdlc address and vmac are combined to form the dummy MAC address of the virtual LAN-attached controller or PU seen by the AS/400. The sdlc address and vmac must match the ADPTADR(4000549400C3) under the APPC controller description.

  sdlc partner xxxx.xxxx.xxxx
  

  This must match the MAC address configured in the LAN line description under which the controller is built.

Verify

There is currently no verification procedure available for this configuration.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

NetPro Discussion Forums - Featured Conversations

Related Information

• Troubleshooting DLSw
• Technical Support - Cisco Systems