Guest

IBM Networking

DLSw for Multidrop SDLC with PU 2.1 and PU 2.0

Document ID: 9103



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configure
      Network Diagram
      Configurations
Verify
Troubleshoot
Related Information

Introduction

This document provides a sample configuration for Data Link Switching (DLSw) Synchronous Data Link Control (SDLC) Physical Unit (PU) 2.1 and PU 2.0 multidrop.

Prerequisites

Requirements

There are no specific prerequisites for this document.

Components Used

This document is not restricted to specific software and hardware versions.

  • Cisco IOS® Software Release 11.0

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 the Cisco Technical Tips Conventions.

Configure

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

Note: To find additional information on the commands used in this document, use the Command Lookup Tool (registered customers only) .

Network Diagram

This document uses the network setup shown in this diagram:

4-a.gif

Configurations

This document uses the configurations shown here:

RouterA

hostname RouterA
source-bridge ring-group 100
dlsw local-peer peer-id 1.1.1.11
dlsw remote-peer 0 tcp 1.1.1.12

interface TokenRing0
 no ip address
 ring-speed 16
 source-bridge 2564 1 100
 source-bridge spanning

interface Serial0
ip address 1.1.1.11 255.0.0.0

RouterB

hostname RouterB
dlsw local-peer peer-id 1.1.1.12
dlsw remote-peer 0 tcp 1.1.1.11

interface Serial0
ip address 1.1.1.12 255.0.0.0

interface Serial1
 mtu 4400
 no ip address
 encapsulation sdlc
 no keepalive
 clockrate 19200
 sdlc role primary
 sdlc vmac 4000.1234.5600
 sdlc N1 27200
 sdlc address C1
 sdlc xid C1 05DCCCC1
 sdlc partner 4001.3745.1088 C1
 sdlc address C2 xid-poll 
 sdlc partner 4001.3745.1088 C2
 sdlc dlsw C1 C2

Note: 

  • You must use the sdlc role primary command for multidrop.

  • In the sdlc address C2 xid-poll command, xid-poll indicates that this PU is a 2.1 device.

  • The sdlc vmac 4000.1234.5600 command specifies the MAC address that represents the SDLC devices as if they are on a Token Ring (Logical Link Control [LLC]) network. The SDLC address of each PU is inserted into the last two bytes of the virtual MAC address.

  • The sdlc partner 4001.3745.1088 C1 command specifies the Host Token Ring MAC address, in this case, the Front End Processor (FEP).

  • The sdlc xid C1 05DCCCC1 command generates the Exchange Identification (XID) Format 0 Type 2 (F0 T2) for PU 2.0 devices.

  • The sdlc dlsw C1 C2 command binds these PUs to the DLSw+ feature.

Verify

There is currently no verification procedure available for this configuration.

Troubleshoot

This section provides information you can use to troubleshoot your configuration.

The sdlc test serial <slot/port> <sdlc pooling address> command, for example sdlc test serial 1 C1, can be used to determine whether the controller has been configured with the correct SDLC polling address and troubleshoot an incorrect configuration.

These debugs can be used to see what traffic is passed between the controller and the router for the purposes of troubleshooting:

  • debug sdlc events

  • debug sdlc packets


Related Information



Updated: Jan 28, 2008 Document ID: 9103