Dynamic circuits, Virtual routing node name, Dynamic circuits virtual routing node name – Visara LINCS Configuration User Manual

Page 150

Advertising
background image

132

LINCS Configuration

707023-003

Dynamic Circuits

This field defines the number of adjacent PU 2.1 nodes that can establish dynamic connections
with this APPN node, using this APPN line and protocol. By default, CP-CP sessions will be
supported for any dynamic connection to a Network or End Node.

The number of Dynamic Circuits should include both the number of adjacent nodes that will
dynamically connect (because this is their network node server), and an allowance for dynamic
connections from the connection network. For example:

ENa——NNa

|

ENb——NNb

|

ENc

The top four nodes are on the same token ring, and are all part of a connection network. If
ENa wants a session with ENc, NNa would tell ENa to use a direct path to NNb in order to
reach ENc. This requires a dynamic connection with NNb, even though NNa is ENa’s network
node where the CP-CP sessions are maintained.

The default is 0, which means no dynamic connections will be established using this APPN
line.

Virtual Routing Node Name

This optional field allows this node to participate in an APPN Connection Network. All nodes
using the same Virtual Routing Node name will be on the same Connection Network. There
can be more than one Connection Network on the same LAN.

Connection Networks allow End Nodes on the same or different Connection Networks to
communicate directly, instead of routing through the Network Node. The Network Node
directs the End Node to End Node communication, but does not need to be a part of the
Connection Network. LEN nodes cannot be part of a connection network, because their limited
APPN capabilities.

If the media and protocol that the nodes are using allows them ALL to communicate directly
with each other (including bridging), then this medium is called a Shared Access Transport
Facility (SATF). Token Ring and Ethernet LLC are currently the only SATF that APPN
recognizes. Network Nodes direct other nodes to talk to each other directly by passing them
the necessary MAC/SAP information.

Since each line can be connected to a different LAN, each panel can have a different Virtual
Routing Node name. If the same name is used on two different panels, the lines should be
attached to the same LAN.

Note: This field will not appear for HSC lines, since connection networks are not supported
with Frame Relay, and this field has not been defined by IBM for X.25 APPN circuits.

Advertising