OSI/MHS Configuration and Management Manual

Troubleshooting Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
9-13
Problem Examples
Sometimes a connection failure can be caused by a mismatch between the OSI/MHS
configuration and the OSI/AS configuration. In such cases, one of the following event
messages is produced:
ZMHS-EVT-BAD-OSI-CONFIG - event message 22
ZMHS-EVT-BAD-OSI-RESOURCE - event message 23
ZMHS-EVT-FTL-OSI-CONFIG - event message 24
ZMHS-EVT-FTL-OSI-RESOURCE - event message 25
Each of these messages includes an OSI/AS API error code, followed by a subcode.
A complete list of the error codes is in the OSI/AS Programming Manual. Table 9-3 is
a partial list of the OSI/AS API subcodes.
If the subcode in the event message is in the range 103-106, check the specified
attribute in the definition of the MTA object and the underlying OSI configuration. If the
subcode is in the range 107-113, check the configuration and status of the underlying
subsystem and its components. TAPS refers to OSI/AS, TSP to OSI/TS, and NSP to
X25AM, or TLAM or PAM. The layer 3 and 4 profiles are defined in commands to
OSI/AS.
If the problem is not caused by a mismatch between the OSI/MHS and OSI/AS
addresses or the omission of OSI/AS addresses from the configuration, then check for
a lower layer connection problem, such as rejected packet-switch network call
requests. To determine whether the problem is at a lower layer, run a trace of the RTS
process and examine it using the PTrace utility. Use the statistics counters of the RTS
processes to identify and verify which processes are having the connection problem.
The following steps could be used to identify the problem in this example: a
connection that cannot be made because of a validation failure. The steps include:
1. Using SCF to display RTS process statistics
Table 9-3. OSI/AS Subcodes
Subcode No. Description
LOCAL-NSAP 103 Local NSAP not configured
REMOTE-NSAP 104 Remote NSAP not configured
LOCAL-TSEL 105 Local TSEL not configured
LOCAL-SNPA 106 Local SNPA not configured
NSP-NOT-AVAIL 107 NSP process not available
TSP-NOT-AVAIL 108 TSP process not available
TAPS-NOT-AVAIL 109 TAPS process not available
ADD-TSP-FS-ERR 110 File-system error attempting to add TSP subdevice
ADD-TSP-SPI-ERR 111 SPI error attempting to add TSP subdevice
L3-PROFILE 112 Layer 3 profile not available
L4-PROFILE 113 Layer 4 profile not available