[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC X.25 for OpenVMS AXP |
|
| Moderator: | OZROCK::MUGGERIDGE |
|
| Created: | Mon Jan 18 1993 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 524 |
| Total number of notes: | 2218 |
503.0. "diag A6, if x29 from alpha to alpha" by MUNICH::SCHALLER (Eva Schaller *DSC* 895-6146) Thu Mar 13 1997 18:52
The following note was placed into the wrong notesfile, so I repeat it
here. The requested information from Antonio is:
Alpha 1000 4a 233, the interface to X25 is DNSES-0-0, the used profile
is DATEXP. The trace info follows.
thanks for any help
CTF V1.0-00 Page 1
Trace started on 13-MAR-1997 09:30:37.81 Analyzed on 13-MAR-1997 09:45:49.47
Trace File [SCHALLER]TRACE.DAT;1 Output File [SCHALLER]TRACE.LIS;1
-----------+----+-----+<--------Packet-------->+------------------------------------------------------------------------------------
Time |Evnt|Data |Chn Q Type P P |Data
hh mm ss cc| |Size | M R/S R/S |
-----------+----+-----+<---------------------->+------------------------------------------------------------------------------------
09:30:37.81| Tx| 15|004 CALL |Called DTE 45821090691
| Data 01 00 00 00|
| |
| |
09:30:38.26|Rx | 16|004 CALLC |Called DTE 45821090691
| Calling DTE 4560212303
||
09:30:38.33|Rx | 14|004Q DATA 0/0 | 06 02 00 04 01 0A 00 0D 00 0F 00
09:30:38.33| Tx| 3|004 RR 1/ |
09:30:38.33| Tx| 14|004Q DATA 1/0 | 00 02 00 04 01 0A 00 0D 00 0F 00
09:30:38.34|Rx | 4|004 DATA 0/1 | 07
09:30:38.34| Tx| 3|004 RR 2/ |
09:30:38.36|Rx | 19|004 DATA 0/2 | 0D 0A 1B 5B 3B 48 1B 5B 4A 1B 5B 31 3B 31 48 0D
09:30:38.36| Tx| 3|004 RR 3/ |
09:30:38.40|Rx | 44|004 DATA 0/3 | 0A 1B 5B 31 39 3B 31 1B 23 36 20 20 20 20 20 20 20 20 20 20 20 20 42 61 68 6E 74 72
| 61 6E 73 20 41 75 67 73 62 75 72 67 0D
09:30:38.40| Tx| 3|004 RR 4/ |
09:30:38.42|Rx | 12|004 DATA 0/4 | 0A 1B 5B 32 32 3B 31 48 0D
09:30:38.42| Tx| 3|004 RR 5/ |
09:30:38.46|Rx | 15|004 DATA 0/5 | 0A 0D 55 73 65 72 6E 61 6D 65 3A 20
09:30:38.46| Tx| 3|004 RR 6/ |
09:30:38.47|Rx | 5|004 RST C=00 D=A6 |
09:30:38.48| Tx| 3|004 RSTC |
09:30:58.28|Rx | 33|004 DATA 0/0 | 0D 0A 45 72 72 6F 72 20 72 65 61 64 69 6E 67 20 63 6F 6D 6D 61 6E 64 20 69 6E 70 75
| 74 0D
09:30:58.28| Tx| 3|004 RR 1/ |
09:30:58.30|Rx | 27|004 DATA 0/1 | 0A 54 69 6D 65 6F 75 74 20 70 65 72 69 6F 64 20 65 78 70 69 72 65 64 0D
09:30:58.30| Tx| 3|004 RR 2/ |
09:30:58.32|Rx | 10|004Q DATA 0/2 | 06 02 01 04 00 0F 01
09:30:58.32| Tx| 3|004 RR 3/ |
09:30:58.32| Tx| 10|004Q DATA 3/0 | 00 02 01 04 00 0F 01
09:30:58.45|Rx | 5|004 RST C=00 D=A6 |
09:30:58.45| Tx| 3|004 RSTC |
09:31:21.99| Tx| 4|004 DATA 0/0 | 19
09:31:22.10|Rx | 5|004 RST C=00 D=A6 |
09:31:22.11| Tx| 3|004 RSTC |
09:31:28.25|Rx | 5|004 CLR C=00 D=00 |
09:31:28.25| Tx| 3|004 CLRC |
ANA TRACE.DAT/OUT=TRACE.LIS
<<< MARVIN::DISK$GENERAL:[NOTES$LIBRARY]X25PSI.NOTE;1 >>>
-< Packet Switching Products >-
================================================================================
Note 3741.0 diag code A6, x29 conn alpha to alpha 2 replies
MUNICH::SCHALLER "Eva Schaller *DSC* 895-6146" 21 lines 11-MAR-1997 15:02
--------------------------------------------------------------------------------
My customer runs OpenVMS alpha 6.2-1h2 with OSI 6.3.
He has configured native PSI on the alpha. If he connects to another
alpha, which runs the same SW, he recieves in 90% a Cause code 0,
diagostic code A6(166) and the connection hangs with USERname
displayed.
The other 10% he still sees the diag code, but communication works fine
The same connection (set host/x) to a VAX or from a VAX to this Alpha,
always works, so I don't believe, that there is an configuration error.
I couldn't find this diagnostic code, it may help for tracking down the
problem. Is somebody willing to look into a trace (I'm not very
experienced with traces) and if, which tracepoints should I use?
x25l3?
If this problem is already known or fixed, please let me know.
Otherwise I would appreciate hints, how to analyse this problem
thanks and best regards
eva
================================================================================
Note 3741.1* diag code A6, x29 conn alpha to alpha 1 of 2
MARVIN::CARLINI 14 lines 12-MAR-1997 07:49
--------------------------------------------------------------------------------
> He has configured native PSI on the alpha. If he connects to another
On the Alpha it's X25 not PSI and is a separately installable item - i.e. it
does not come as part of DECnet-Plus.
> The same connection (set host/x) to a VAX or from a VAX to this Alpha,
> always works, so I don't believe, that there is an configuration error.
What profile and physical connection are in use?
Post an X25L3 trace in OZROCK::X25_AVMS (the conference where the Alpha X.25
devos hang out).
Antonio
================================================================================
Note 3741.2 diag code A6, x29 conn alpha to alpha 2 of 2
MUNICH::SCHALLER "Eva Schaller *DSC* 895-6146" 3 lines 13-MAR-1997 08:38
-< question transfered to x25 Alpha notes >-
--------------------------------------------------------------------------------
Antonio, thanks for the answer, I will place the call in to correct
notesfile. Sorry also for the naming error..
regards eva
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 503.1 | meaning of this diag code... ? A6 | MUNICH::SCHALLER | Eva Schaller *DSC* 895-6146 | Mon Mar 17 1997 17:38 | 6 |
|
nobody around, who can help me with this call? not even hints to
get the meaning of the diagnostic code??
thanks for any help
eva
|
| 503.2 | | OZROCK::MUGGERIDGE | X.25 is 1-2-3 | Mon Mar 17 1997 17:55 | 11 |
| From my chart:
A6 = Error in traffic generator command
Lack of resources
Execution of a command to traffic generator
Flow control blocked on DTE logical channel
Sorry, I can't be of more immediate help. I will be off-air for the
next week or so.
Matt.
|
| 503.3 | Some hints | OZROCK::HARTWIG | Arthur Hartwig, TaN Engineering-Australia | Tue Mar 18 1997 06:14 | 26 |
| It often takes a few iterations to track down problems like these.
The RESETs are received and have a cause code of 0 - this suggests they
are originated by the remote DTE (a network generated reset should
have a non-zero cause code).
The reset could be originated by the X25 software or the application
dealing with the call. If originated by the x25 software, the
diagnostic code of 0xA6 indicates "D-Bit not supported" - remote
end received a packet with the D-bit set. Unfortunately the X25L3 trace
doesn't reveal the state of the D-bit. I suggest you get a trace at the
called system and display both LAPB and X25L3 and post the trace here.
It would also be helpful to monitor the "Illegal Packets Received"
counter on the matching X25 PROTOCOL DTE at the remote end of the call.
This will increment for every received D-Bit packet.
The reset could also be originated by some special software that
answers the incoming X.29 call. You could look at the the X25 ACCESS
PORT TERMINATED events to see the filter the incoming call matched
and if the filter is in use for X29 applications then the reset is
likely due to the application.
The trace will help to identify which is the most likely cause.
Good hunting,
Arthur
|
| 503.4 | D-bit negotiation failure | MUNICH::SCHALLER | Eva Schaller *DSC* 895-6146 | Fri Mar 28 1997 00:49 | 12 |
| Arthur,
thanks very much, your hint let into the correct direction.
The customer had ordered D-bit support only at his side and the
other end did not have D-bit support. The Alphas seem to be more
sensitive, since the VAXes showed the error sporadically, but
communication worked.
The Alphas usually blocked the communication.
thanks
problem solved
eva
|