Avaya Configuring DLSw Services User Manual download pdf (Page 109)

Customizing DLSw Services

304233-A Rev. 00

4-17

You typically define as configured peers:

• One slot in each DLSw-capable remote Bay Networks router in your TCP/IP

network to which broadcast traffic must be forwarded

• Any other peer in your TCP/IP network that complies with RFC 1434,

RFC 1795, or DLSw Version 2

You define each configured peer by specifying its unique IP address on the

TCP/IP network.

With RFCs 1434 and 1795, once you initialize DLSw services, the local router

establishes two TCP connections (one for transmitting, one for receiving) between

each local DLSw-capable slot and every configured peer in the TCP/IP network.

Remote DLSw peers on the network follow the same procedure. DLSw uses TCP

ports 2065 and 2067.

Peer Types

For DLSw V2.0, you can define a specific transport type to a DLSw peer,

specifically:

•TCP

• UDP

• Unknown

Peers that you define as TCP or UDP will cause the local router to use TCP or

UDP explorer frames respectively and exclusively to establish connections with

the peer router. A peer that you define as Unknown causes the local router to use

UDP explorer frames to locate the destination MAC address of the peer before

establishing the TCP connection. If the TCP connection cannot be made, or if

there is no UDP response, DLSw performs fallback attempts to earlier RFC

protocols to establish the connection. If all connection attempts fail regardless of

the RFC used, a connection can be made to a configured DLSw backup peer,

described in the next section.

For information about configuring peer types and fallback attempts, refer to the

Transport Type and SNA Fallback Attempts parameters in Appendix A, “DLSw

Service Parameters.”

1 2 ... 104 105 106 107 108 109 110 111 112 113 114 ... 271 272

No comments

Avaya Configuring DLSw Services User Manual Page 109