OSI/AS Configuration and Management Manual

Installing and Configuring the Subsystem
OSI/AS Configuration and Management Manual—424119-001
4-43
Verifying Your Configuration
Limitations
Due to the greater number of processes, this kind of configuration is more complex to
manage.
In addition, for users of transport class 1 or class 3, the Transport Layer recovery
mechanism can possibly fail when the X.25 network is not very reliable and generates
many network disconnections. This can occur when a remote Transport Layer entity
resynchronizes a transport connection, which causes a new network connection to be
established. This new network connection does not necessarily arrive at the same TSP
process that is participating in the resynchronizing process. This problem does not occur
with class 2.
Verifying Your Configuration
You may want to check your configuration before trying to establish a connection. Using
SCF commands, you can perform the following tasks:
•
Checking the contents of the MIB
You can verify that required information for a given APPL ENTRY name is in the
MIB, and that attach request requirements are met. You can also retrieve profile,
process (server), and service information for a given APPL ENTRY name.
•
Checking connection attributes
You can determine which configuration information will be used for a connection
between two particular local and remote addresses. You can verify that connect
request requirements are met.
•
Retrieving other configuration information
You can retrieve information on all aspects of your configuration. This is discussed
in detail in Retrieving Configuration Information
on page 5-5.
Checking the Contents of the MIB
Use the CHECK ENTRY command with the PROFILES attribute to verify that all
address components, profiles (and, optionally, processes) specified in an APPL
ENTRY—and its associated SNPA, NSAP, and TSEL ENTRY objects—are in the MIB.
This command applies the same object hierarchy selection rules used by the OSI
manager process, described in Selection Hierarchy of Object Attributes
on page 2-35.
Only the existence of objects in the MIB are verified—the CHECK ENTRY command
does not verify their values. For example, the CHECK ENTRY command may verify
that a given configuration is valid: in other words, all the specified ENTRY, PROFILE,
and PROCESS objects exist in the MIB. However, one of the ENTRY objects may
specify a Layer 4 PROFILE object that, in turn, defines a Class 3 for a LAN address.
Although the appropriate objects exist in the configuration, any connection attempts will
fail.