From: Yves Fauser (Yves@xxxxxxxxx)
Date: Fri Aug 10 2001 - 13:56:33 GMT-3
You answered your own questions,
Cisco dlsw+ to dlsw+ use 2 bi-directional tcp sessions, both sourced on Port 20
65 on each side initially, from which one is teared down after CapExchange.
Cisco dlsw v2 to ibm dlsw v2 use 2 bi-directional tcp session from 2065 and 206
7, but I never traced it, so I'm not 100% sure.
Read : http://publib-b.boulder.ibm.com/Redbooks.nsf/9445fa5b416f6e32852569ae00
6bb65f/d214bd2179ecc24d852568570050821a?OpenDocument&Highlight=0,SG24-5865-00
Yves
"ElleJf(Yahoo)" wrote:
> In RFC2166, it says "RFC 1795 defines the use of two unidirectional TCP/IP se
ssions between any pair of DLSw peers using read port number 2065 and write por
t number 2067."
>
> "6.2.1.1 TCP Port Numbers
>
> DLSws implementing these enhancements will use a TCP destination port of 2067
(as opposed to RFC 1795 which uses 2065) for single session TCP conections."
>
> But as we do DLSw+, always use a destination port 2065 for TCP. Never saw ro
uter use port 2067. So in DLSw+, only destination port 2065 will be used for T
CP?
>
> When Cisco router interoperate with non-Cisco, RFC2166 compliant router, will
Cisco behave as RFC2166 specified? That is, use 2067 as suggested?
>
> |:"f
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:48 GMT-3