QUESTION:
We are trying to make X.25 call from 3090/3745/NPSI to RISC.
The Xmonitor trace shows:
PR CALL dN 1a:10 1f:0 1d:1 AA3106001983310600198400C3
FS 0 RR 3 0 4
PS 0001 ERROR 1:5 10 01 13
PR 0001 CF CLEAR
Any idea what the problem could be? CUD C3 is for 1980 X.25 which both
ends support and I think even if RISC is configured for 1984, it should
be backwards compatible -- right? So maybe it is something else.
---------- ---------- ---------- --------- ---------- ----------
A: For SNA, the 1980 CCITT standard uses CUD C3, and the 1984 CCITT
standard uses CUD CB. They are not backwards compatible - you must
configure the same on both sides of the connection.
The RISC's X.25 adapter defaults to the CCITT 1984 X.25 standard;
however, since you are receiving CUD C3, the RISC should be configured
to the 1980 standard.
The ERROR packet that the RISC is sending to the mainframe does not
specify what the particular problem is or its cause.
So, to determine the cause of the problem we have to analyze the CALL
packet sent from the 3745. The CALL packet is interpreted as
follows:
PR - Packet Receive (no problem, indicates packet being received
on the RISC.)
CALL - The packet type is CALL. (no problem, indicates that a remote
system is attempting to establish communication with the RISC.)
dN - Indicates no D bit. (no problem, indicates not to use delivery
confirmation)
la:10 - Length of addresses (calling and called) in octets (decimal)
(no problem, the RISC can handle this length)
lf:0 - Length of facilities (no problem)
ld:1 - Length of CUD (no problem)
AA - Indicates that the calling address is of length 10, and the
called address is of length 10 also. (no problem, the RISC
can handle these lengths)
3106001983 - Called address. (no problem, the RISC can handle this
type of address
3106001984 - Calling address. (also no problem)
00 - Indicates length of facilities is 0. (no problem)
C3 - Indicates that the CCITT 1980 standard CUD is being used.
(This is a problem if the RISC is not configured for the
1980 standard. If the RISC is using 1984, then the packet
will be rejected)
The packet could also be rejected if the RISC is not configured for
allowing the calling address to be in the packet. In other words, if
the RISC only expects to see the called address in the packet, but
both are present, an error will occur since the RISC does not
understand the packet.
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q610704 BVSDT
Additional search words:
BVSDT CALL COMMUNICATIO ERR ERROR FAIL FAILURE IX JAN93 MESSAGE
MONITOR MONITORING MSG NPSI REJECTED RISC RISCSYSTEM SOFTWARE TRACE
X.25 X25 3745
WWQA: ITEM: RTA000027415 ITEM: RTA000027415
Dated: 11/1996 Category: RISCL
This HTML file was generated 99/06/24~12:43:10
Comments or suggestions?
Contact us