02-04-2011 12:10 PM - edited 03-04-2019 11:19 AM
Hi,
We are migrating some access from Decnis into TCP/IP at X.25 links and we have XOT configured at our router.
The point is that for 4 of 5 accesses this is working fine but at one of them not, and the following log is shown:
Feb 3 14:46:51.138 MET: From (12): 141271158400 To (8): 14182077
Feb 3 14:46:51.138 MET: Facilities: (6)
Feb 3 14:46:51.138 MET: Packet sizes: 128 128
Feb 3 14:46:51.138 MET: Window sizes: 3 3
Feb 3 14:46:51.138 MET: Call User Data (16): 0x00000000 (x25-multiprotocol)
Feb 3 14:46:51.138 MET: Serial0/0/0: X.25 O R1 Call (29) 8 lci 6
Feb 3 14:46:51.138 MET: From (8): 14127115 To (8): 14182077
Feb 3 14:46:51.138 MET: Facilities: (0)
Feb 3 14:46:51.138 MET: Call User Data (16): 0x00000000 (x25-multiprotocol)
Feb 3 14:46:51.450 MET: Serial0/0/0: X.25 I R1 Call Confirm (5) 8 lci 6
Feb 3 14:46:51.450 MET: From (0): To (0):
Feb 3 14:46:51.450 MET: Facilities: (0)
Feb 3 14:46:51.450 MET: [172.26.93.31,58315/10.216.8.91,1998]: XOT O P3 Call Confirm (11) 8 lci 4093
Feb 3 14:46:51.450 MET: From (0): To (0):
Feb 3 14:46:51.450 MET: Facilities: (6)
Feb 3 14:46:51.450 MET: Packet sizes: 128 128
Feb 3 14:46:51.450 MET: Window sizes: 3 3
Feb 3 14:46:56.329 MET: Serial0/0/0: X.25 I D1 Reset (5) 8 lci 6
Feb 3 14:46:56.329 MET: Cause 5, Diag 1 (Local procedure error/Invalid P(S))
Feb 3 14:46:56.329 MET: Serial0/0/0: X.25 O D3 Reset Confirm (3) 8 lci 6
Feb 3 14:46:56.329 MET: [172.26.93.31,58315/10.216.8.91,1998]: XOT O D1 Reset (5) 8 lci 4093
Feb 3 14:46:56.329 MET: Cause 3, Diag 1 (Remote procedure error/Invalid P(S))
Feb 3 14:46:56.661 MET: Serial0/0/0: X.25 I D1 Reset (5) 8 lci 6
Feb 3 14:46:56.661 MET: Cause 0, Diag 0 (DTE originated/No additional information)
Feb 3 14:46:56.661 MET: Serial0/0/0: X.25 O D3 Reset Confirm (3) 8 lci 6
Feb 3 14:47:01.157 MET: [172.26.93.31,58315/10.216.8.91,1998]: XOT I P4 Clear (5) 8 lci 4093
Feb 3 14:47:01.161 MET: Cause 0, Diag 0 (DTE originated/No additional information)
Feb 3 14:47:01.161 MET: Serial0/0/0: X.25 O R1 Clear (5) 8 lci 6
Feb 3 14:47:01.161 MET: Cause 0, Diag 0 (DTE originated/No additional information)
Feb 3 14:47:01.221 MET: Serial0/0/0: X.25 I R1 Clear Confirm (3) 8 lci 6
Feb 3 14:47:01.221 MET: <detached>: XOT O P7 Clear Confirm (3) 8 lci 4093
Feb 3 14:47:06.173 MET: [172.26.93.31,58322/10.216.8.91,1998]: XOT I P/Inactive Call (37) 8 lci 4093
Looking at X.25 documentation it wasn't clear to me what exactly could be the source of this problem, so could somebody help me with that? If found this kind of problem?
The destination that doesn't work is 14182077.
Rds,
Luiz
PS: Here is the routing configuration:
Solved! Go to Solution.
02-11-2011 11:58 AM
interface Serial0/0/0
no ip address
encapsulation x25
x25 version 1988
x25 address 14127115
x25 htc 10
x25 win 3
x25 wout 3
x25 use-source-address
x25 pad-access
The information above says the packet window is 3; the link layer window
is probably 7, not 3, please check this.
also confirm check in the line if you need x25 map... or translate.
02-11-2011 11:58 AM
interface Serial0/0/0
no ip address
encapsulation x25
x25 version 1988
x25 address 14127115
x25 htc 10
x25 win 3
x25 wout 3
x25 use-source-address
x25 pad-access
The information above says the packet window is 3; the link layer window
is probably 7, not 3, please check this.
also confirm check in the line if you need x25 map... or translate.
02-19-2011 08:45 PM
Hi Sakella,
You've really got the point because we found out that historically used the window size as 3 but at SP it was set as 2.
For other 3 suppliers it never became a serious problem or even was noted because when this happens, communications was resetted and channels was cleared retrying until get to transmit the message that is very small(text file). But now when we were migrating this specific suppliers router used the default X.25 timer to clear the channel that is around 3 minutes, and how application tried to retransmit before this time, channel was busy and the error was show.
This router specifically has a problem and had to be replaced, but showed us this other old problem that wasn't being seen for us or the SP support until we requested them to use analyzers at L2 and 3 of X.25.
But your lecture was really correct, thanks for the answer.
Luiz
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide