[previous] Clear Spacer [next]

Configuring SDLC and HDLC Tunneling for SNA Networks

This chapter describes how to configure tunneling for synchronous data link control (SDLC) and high-level data link control (HDLC) traffic using the IBM Data Link Switching (DLSw) protocol.

For conceptual information on how SDLC and HDLC tunneling works, see "How SDLC and HDLC Tunneling Works" later in this chapter. For information about the SHDlc Service parameter, see the SDLC Service Parameters chapter in Reference for Enterprise OS Software.


Configuring SDLC and HDLC Tunneling

This section describes how to configure the bridge/router for SDLC and HDLC tunneling, by referring to Figure 233. The figure shows an IBM host connected to an IBM controller through NETBuilder bridge/routers and an IP network.

Prerequisites

Before beginning this procedure, complete the following tasks:

Procedure

Configure ports, paths, SDLC and HDLC tunneling, and data link switching by referring to the example in Figure 233 and completing the steps under "Configuring Router A" and "Configuring Router B." Table 67 lists the commands used in these steps.

Figure 233 SDLC and HDLC Tunneling Example

Table 67 Commands to Configure SDLC and HDLC Tunneling and Data Link Switching

Commands Entered on Bridge/Router A

Commands Entered on Bridge/Router B

SHow -PORT CONFiguration

SHow -PORT CONFiguration

SETDefault !1 -IP NETaddr = 129.213.1.1

SETDefault !1 -IP NETaddr = 129.213.1.2

SETDefault !7 -PORT OWNer = SHDlc

SETDefault !2 -PORT OWNer = SHDlc

SETDefault !7 -PATH CLock = External

SETDefault !2 -PATH CLock = External

SETDefault !7 -PATH CONNector = RS232

SETDefault !2 -PATH CONNector = RS232

SETDefault !7 -PATH LineType = Leased

SETDefault !2 -PATH LineType = Leased

SETDefault !7 -PATH BAud = 19.2

SETDefault !2 -PATH BAud = 19.2

SETDefault !7 -PATH DUplex = Full

SETDefault !2 -PATH DUplex = Full

SETDefault -TCP CONTrol = KeepAlive

SETDefault -TCP CONTrol = KeepALive

SETDefault -TCP KeepALive = 3

SETDefault -TCP KeepALive = 3

SETDefault -DLSw Interface = 129.213.1.1

SETDefault -DLSw Interface = 129.213.1.2

SETDefault -DLSw CONTrol = (EnableSNA, DisableNetBIOS)

SETDefault -DLSw CONTrol = (EnableSNA, DisableNetBIOS)

SETDefault !7 -PATH CONTrol = Enable

SETDefault !2 -PATH CONTrol = Enable

ADD !1 -DLSw PEer 129.213.1.2

ADD !1 -DLSw PEer 129.213.1.1

SystemInfo

SHow -SYS MacAddrFormat

SETDefault !2 -SYS MacAddrFormat = Noncanonical

SHow -PATH MacAddress

SHow -PATH MacAddress

SETDefault !7 -SHDlc PEer = %10005A265BED

SETDefault !2 -SHDlc PEer = %00608C26C1B5

Configuring Router A

To configure router A, follow these steps:

1 .   Display the port configuration by entering:

SHow -PORT CONFiguration

The display shows the ownership status of each port.

2 .   Define the IP address for the port through which the router is going to tunnel by entering:

SETDefault !1 -IP NETaddr = 129.213.1.1

3 .   Set the port ownership of serial port 7 to SHDlc by entering:

SETDefault !7 -PORT OWNer = SHDlc

When you use a WAN port, you need to configure the port owner. SDLC and HDLC tunneling use only WAN ports.

The number of SHDlc ports a NETBuilder II bridge/router can support is the number of WAN paths it can operate simultaneously.

4 .   Display attributes for all available paths by entering:

SHow -PATH CONFiguration

5 .   Set the attributes for the SHDlc line by entering:

SETDefault !7 -PATH CLock = External
SETDefault !7 -PATH CONNector = RS232
SETDefault !7 -PATH LineType = Leased
SETDefault !7 -PATH BAUD = 19.2
SETDefault !7 -PATH DUplex = Full

If you use a single- port WAN adapter, set the -PATH ENCoding parameter to NRZ.

SHDLC only supports full-duplex operation.

After configuring values using the PATH Service, you may receive a message telling you to re-enable the path. If you receive this message, re-enable the path with the SETDefault !<path> -PATH CONTrol = Enable command.

6 .   Enable the transmission of TCP keepalive packets by entering:

SETDefault -TCP CONTrol = KeepAlive

TCP keepalive packets notify the bridge/router when the TCP connection has ended. Without TCP keepalive packets, the bridge/router will not detect that the TCP connection is down due to an abnormal situation. The data link switching sessions may remain active even though the corresponding TCP session has ended.

7 .   Specify the number of contiguously missed keepalive packets that brings down the TCP session.

For example, if you want three retries, enter:

SETDefault -TCP KeepAliveLimit = 3

8 .   Configure an IP address to connect traffic to and from the router.

The address must be one that has been defined in the router using the SETDefault !<port> -IP NETaddr syntax. This address is the only address used for data link switching.

If you are configuring your NETBuilder II bridge/router as an IP router, the port associated with this IP address must be active before any packets can be sent to or received by this IP address. Select an IP address associated with a port that is always up or is the most reliable, such as a LAN port.

To map the specified DLSw tunnel to the local IP address of bridge/router A, enter:

SETDefault -DLSw Interface = 129.213.1.1

All Internet addresses for connected bridge/routers must be known in the local bridge/router's routing table, either dynamically through RIP or OSPF, or statically configured in the IP routing tables.

9 .   Enable data link switching for SNA traffic on the port by entering:

SETDefault -DLSw CONTrol = (EnableSNA, DisableNetBIOS)

This setting allows SNA traffic to flow through the data link switch and disables NetBIOS traffic. SNA traffic must be enabled for SDLC and HDLC tunneling to work.

If you are going to use the prioritization feature of DLSw, see "Prioritizing DLSw Traffic" in the Configuring Data Link Switching for SNA and NetBIOS Networks chapter before proceeding to the next step.

10 .   Configure the DLSw tunnel peer IP connection by entering the following command. You also must specify the tunnel ID, a peer network address, and optionally, a name for the tunnel connection.

ADD !1 -DLSw PEer 129.213.1.2

When configuring the Internet address for the tunnel peer, you do not specify the port number of the bridge/router where the connection will be made. When a tunnel connection is made, the bridge/router determines the port through which the peer Internet address can be reached. When a peer has been defined and enabled, the system continuously retries to connect to the peer until a TCP connection is established between the system and the peer.

11 .   From the peer router, display the format of the peer MAC address by entering:

SHow -SYS MacAddrFormat

12 .   To display the local MAC address on the SuperStack bridge/router, enter:

SystemInfo

13 .   To convert the MAC address to noncanonical format, you must enter the MacAddrConvert command on a NETBuilder II bridge/router. This command is not available on the SuperStack bridge/router.

14 .   Display the peer router MAC address by entering:

SHow -PATH MacAddress

With this display, you can obtain the peer router MAC address that you configure in the next step.

15 .   Set the MAC address for the peer serial port that the local SDLC port is communicating with by entering:

SETDefault !7 -SHDlc PEer = %10005A265BED

Configuring Router B

To configure router B, repeat steps 1-11 in the preceding procedure, then continue with the following steps (performed on a NETBuilder II bridge/router):

1 .   If the peer MAC address displayed is in canonical format, set it to noncanonical by entering:

SETDefault !7 -SYS MacAddrFormat - Noncanonical

2 .   Display the peer router MAC address by entering:

SHow -PATH MacAddress

With this display, you can obtain the peer router MAC address that you configure in the next step.

3 .   Set the MAC address for the peer serial port that the local SDLC port is communicating with using:

SETDefault !<port> -SHDLc PEer

Verifying the Configuration

After you have configured a tunnel connection using data link switching, you can display information to verify the connection.

To display complete configuration information, enter:

SHow -DLSw CONFiguration

The display shows the settings you have configured.

To display the peer information, enter:

SHow -SHDLc -PEer

The following display is an example of this information:

----------------------------SHDlc PEer-----------------------------
Local Port Local MacAddress Circuit State Peer MacAddress
!4 %1000405011DC CONNECTED %100040605D8A

When shown in the display, SAP E8 represents an HDLC tunnel.

Displaying Circuits

To display the status of circuits, enter:

SHow -DLSw CIRcuits

Information similar to the following is displayed:

---------------------------------------Circuits----------------------------------
Local Name/Address
DL Corr.
Port
Peer Name/Address
DL Corr.
State
Peer IP Address
%00608C26C1B5
04
376B008E
4
%10005A265BED
04
37250047
CONNECTD
129.213.1.2
%0020AF00DCC8
04
171A00C9
6
%40000003172A
04
86FA0013
CONNECTD
200.200.1.254
%100040600B03
00
00000000
?
%100040A0E8E1
00
00000000
DISC
200.200.1.254
%400001111111
08
00000000
?
%400002222222
08
00000000
DISC
200.200.1.254
%400011600000
04
00000000
?
%0020AF00B940
04
00000000
DISC
200.200.1.254
%400011600000
34
00000000
?
%0020AFEE9630
34
00000000
DISC
200.200.1.254


How SDLC and HDLC Tunneling Works

The SDLC and HDLC tunneling features enable NETBuilder II bridge/routers to send SDLC or HDLC frames across IP networks through DLSw tunnels. Two bridge/routers interconnect a point-to-point SDLC or HDLC link. They encapsulate SDLC or HDLC frames sent between the two end points and tunnel them through an IP network.

A typical use of SDLC and HDLC tunneling is to connect a host computer and a remote terminal or controller. In Figure 233, two end points of an SDLC link (a 3174 controller and a host) are interconnected by two intermediary bridge/routers. The 3174 controller is connected to port 7 on router A, and the host FEP is connected to port 2 on router B.

[previous] Clear Spacer [next]