OSI/AS Configuration and Management Manual

Management Environment

OSI/AS Configuration and Management Manual—424119-001

2-15

TSEL ENTRY Objects

Registering Remote NSAP Addresses

You also add NSAP ENTRY objects to your subsystem to do the following:

•

outgoing connections, but optional if your application is waiting for incoming

connections.)

•

Assign a remote Transport Layer profile (a Layer 4 subdevice configuration) that

characterizes all transport connections that use this remote NSAP address.

If a remote application runs on an open system that is attached to an X.25 subnetwork

other than your own, enter the NSAP address of the remote application and the SNPA

address of the remote end system. If you are using ES-IS routing exchange protocol, you

enter only the NSAP address of the remote application. The SNPA is not needed in this

case, since the address is determined by the ES-IS routing exchange protocol.

SNPA-address assignments are not required for remote NSAP addresses.

An NSAP ENTRY is required for each remote NSAP address.

Each remote NSAP address can be assigned to at most one remote SNPA address. The

same remote SNPA address, however, can have more than one remote NSAP address

assigned to it.

TSEL ENTRY Objects

You use TSEL ENTRY objects to configure TAPS processes. You add a TSEL ENTRY

object to your subsystem to do the following:

•

Assign a TAPS process to handle all connections that use this TSEL.

•

Assign a Session Layer profile (a Layer 5 subdevice configuration) that

characterizes all session connections that use this TSEL.

If you choose to specify the TAPS process (the server) and the Layer 5 profile in the

APPL ENTRY object, the TSEL ENTRY object needs to specify only the TSEL name.

A TSEL ENTRY object is required for each local TSEL.

Each TSEL that you register can be assigned to at most one TAPS process. A single

TAPS process, however, can have several TSELs assigned to it.