
Configuring DLSw Services
3-10
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 RFC 1434-compliant peer in your TCP/IP network.
You define each configured peer by its unique IP address on the TCP/IP network.
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.
Simplifying the Peer IP Table
Bay Networks provides two mechanisms for reducing the number of required
entries in the DLSw Peer IP Table. These are
• Broadcast peers
• Unconfigured peers
Broadcast Peers
Any DLSw slot that receives a broadcast will forward that frame to all other
DLSw slots in this same router. Therefore, it is not necessary to enter more than
one peer (per remote router) into the Peer IP Table. The entry representing the
remote router is the broadcast peer for that router.
Unconfigured Peers
A Bay Networks router running DLSw can respond to requests from remote
routers to initiate DLSw sessions, even if the remote peer is not defined in the
local router’s Peer IP Table. Once a DLSw session is established to a remote slot,
that slot is dynamically added to the list of known peers. Any remote DLSw peer
that the router learns dynamically is an unconfigured peer. These peers are not
listed in a router’s Peer IP Table.
Unconfigured peers are supported only if the DLSw Reject Unconfigured Peers
parameter is set to Accept.
Comentários a estes Manuais