Guest

IBM Networking

Reverse SDLLC with DLSW for Ethernet

Document ID: 62842



Contents

Introduction
Prerequisites
      Requirements
      Components Used
      Conventions
Configure
      Network Diagram
      Configurations
Verify
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides a sample configuration for defining SDLC attached devices going to an LLC Ethernet attached Host.

Prerequisites

Requirements

No specific requirements were used for this configuration.

Components Used

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

The information in this document was created from the devices in a specific lab environment. All 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: For more information on the commands used in this document, use the Command Lookup Tool ( registered customers only) .

Network Diagram

This document uses this network setup:

paws62842.gif

Configurations

This document uses these configurations:

  • SDLC side of the network

  • Router B

SDLC side of the network

dlsw local-peer peer-id 172.16.252.1
dlsw remote-peer 0 tcp 172.16.250.1
!
interface Loopback0
description Logical interface used to map remote peers
ip address 172.16.252.1 255.255.255.0
!
interface Serial0
description Serial Connection to PG Mainframe
no ip address
encapsulation sdlc
no keepalive
clockrate 56000
sdlc role secondary
sdlc vmac 4000.0000.0100
sdlc address C1 
sdlc partner 0020.AF27.EE4E C1 
sdlc address C2 
sdlc partner 0080.5F14.3407 C2 
sdlc address C3 
sdlc partner 0001.fa2b.c1fa C3 
sdlc dlsw C1 C2 C3 

Router B

dlsw local-peer peer-id 172.16.250.1 
dlsw remote-peer 0 tcp 172.16.252.1 
dlsw bridge-group 1 
! 
interface Loopback0 
description Logical interface used to map remote peers 
ip address 172.16.250.1 255.255.255.0 
!
interface Ethernet0 
description First production ethernet segment 
ip address 172.16.1.1 255.255.255.0 
bridge-group 1 
bridge 1 protocol ieee

Notes:

  • This configuration requires exchange identification (XID) from a LAN-attached device to initiate a session.

  • IP routing and WAN configurations are not shown in this configuration for simplicity, but are required.

  • If the router is acting as the DCE device, clocking is required on the serial interfaces

  • The MAC address on the Ethernet is in Least Significant Bit (LSB) first (canonical), and the Token Ring is Most Significant Bit (MSB) first (non-canonical). DLSw normally uses the non-canonical format of the address. This means that the vmac address must be the bitswapped version of the address in the host, and the partner address must be the bitswapped version of the host's Ethernet MAC address.

    For example, 0020.AF27.EE4E represents the bitswapped version of 0004.F5E4.7772. The end device must be configured to send test frames to 0200.0000.8000, which is the bitswapped version of 4000.0000.0100.

  • This configuration works for either PU 2.0 or 2.1 device

Verify

Verification procedures are not yet available for this configuration.

The Output Interpreter Tool ( registered customers only) allows you to view an analysis of show command output.

Troubleshoot

Troubleshooting information is not yet available for this configuration.

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.
NetPro Discussion Forums - Featured Conversations for IBM
Network Infrastructure: Enterprise Data Centers

Related Information



Updated: Jan 18, 2008Document ID: 62842