DLSW Problem...

Have a problem trying to stablish a circuit between two VMS systems. It was working and one day it didn't work anymore.
The circuit stucks at CKT_START (any idea of what we have to do ?):
3741319329 4000.1347.4124(04) 4000.1347.4151(04) CKT_START -
PCEP: 62FD7218 UCEP: 623400FC
Port:TB1 peer 192.168.210.188(2065)
Flow-Control-Tx CW:20, Permitted:0; Rx CW:20, Granted:0; Op: Repeat
Congestion: Low(02), Flow Op: Half: 0/0 Reset 0/0
RIF = --no rif--
Bytes: 0/0 Info-frames: 0/0
XID-frames: 0/0 UInfo-frames: 0/0

Hi,
the first thing i would do if you need help in troubleshooting is to open a Service Request with cisco's tac.
If things used to work and suddenlly stopped to work than the question always is what has changed??
There are lots of potentiall issues in the chain one can look at. I would advice to open a SR and work the issue with the tac until conclusion.
thanks...
Matthias

Similar Messages

Dlsw+ problem with SNI connection

We have a cisco 1603 router using dlsw+ to peer with a Nortel ASN.
at the cisco end it is x21 connection from the FEP
at the Nortel end it is token ring to an OSA
when we try and start a JES node we get an IBM sense code 800A0000 and the session drops.
The sense code states the transmission was truncated by the receiving node
because the PIU (path information unit) was to large or there was no buffer space available
has anyone seen a similar problem ?
This link was working I am told there have been no changes to the routers, only thing I can think of is that the network reconverged and it is now taking a different path between the two sites. I am asking for trace routes and trying to check if that is right.
Am I going in the right direction ?

Apparently this is strictly a configuraiton problem on the host. There is nothing wrong with the Cisco or Nortel routers.
Please me explain to you the data flow. Assume that the FEP sends a packet to the 1603. (The following applies to a packet from the OSA to the FEP) If the packet is too large for the 1603 to handle, the 1603 will drop the packet. As a result, the SDLC link will go down. Otherwise, the 1603 adds a DLSw header (16 bytes I think), a TCP header (normally 20 bytes), and an IP header (20 bytes). The 1603 uses TCP to tranport the packet with TCP/IP header. Depending upon your TCP setting, TCP may segment the packets into a number of different segments. Then, TCP uses IP to deliver the segment(s) to the Nortel router. If the TCP segments are too big for any routers between the DLSw peer, the router may either fragment the TCP segments or send an ICMP message, according to RFC 1191, to the 1603. The ICMP causes the 1603 to lower the TCP segment size. If any routers between the DLSw peers do not support RFC1191, the routers will drop the TCP segment. This will cause TCP detecting a gap in TCP sequence number. Eventually, TCP will disconnect the virtual circuit, which cause the peer go down.
Once all the TCP segments for the orignal SNA packet arrive at the Nortel router, the TCP stack on the Nortel router assemble the original SNA packet and put in on the token ring interface.
From the description, it looks like that the SNA packet reaches destination VTAM. VTAM finds out that the PIU is too large. If there is any problem on the IP path, I expect to see either:
1. a disconnect on the LLC2 or SDLC circuit. In other words, a DLSw circuit disconnect
or
2. a DLSw peer disconnect
Please check the modtab and find out the max RU size inside the bind. Make sure both VTAMs can handle the RU size.

DLSw problem whith two connection to the host

Hello every one,
My name's Mostafa CHAKIR,I am a technical ingeneer in the CBI Networks Morocco.
We have a dual connection to a IBM Host via two 7206 routers called CPA1 and CPA2 in the central site.
In the remote site we have a 2610 routers connected with Public Frame-Relay, and anohter link with ISDN as backup.
Two peers dlsw from the remote site are configured, the first with CPA2 and its backup with CPA1 ( as you will see in the configuration).
when the link go down (FR), the peers stay in stat connected in both site until there is a SNA trafic, and the ddr is made from the remote site.
The problem is when the two link go down, the Host always see that the remote site is connected, the router CPA2 don't breack the circuit, and when the ISDN link come UP first, it open a circuit with a CPA1 even if the CPA2 is active, the HOST don't accept the second circuit cause it says that there is another circuit opened in the CPA2 with the same IDNum IDBlock. I tried to resolve that with the "dlsw timer sna-cahe-timeout" command but it have no effect.
i search some solution to this problem.
******************CPA1 Configuration**************************
source-bridge ring-group 2000
dlsw timer sna-cache-timeout
dlsw local-peer peer-id 1.1.1.1 keepalive 0 promiscuous
dlsw icanreach mac-exclusive
dlsw icanreach mac-address 4000.0e02.7206 mask ffff.ffff.ffff
dlsw icanreach mac-address 4000.0e13.7206 mask ffff.ffff.ffff
interface Loopback0
ip address 1.1.1.1 255.255.255.255
interface FastEthernet0/0
ip address 192.168.6.1 255.255.255.248
duplex full
speed 100
interface FastEthernet0/1
no ip address
shutdown
duplex auto
speed auto
interface Channel1/0
ip address 130.114.2.2 255.255.255.0 secondary
ip address 130.114.1.2 255.255.255.0
no ip redirects
no ip mroute-cache
no keepalive
llc2 dynwind
claw 0122 12 130.114.2.1 DEVL WCPA1 TCPIP TCPIP
claw 0111 02 130.114.1.1 PROD WCPA1 TCPIP TCPIP
csna 0111 00 maxpiu 65535 length-delay 0
csna 0122 10 maxpiu 65535 length-delay 0
max-llc2-sessions 1024
lan TokenRing 1
source-bridge 1000 1 2000
adapter 0 4000.0e02.7206
adapter 1 4000.0e13.7206
*******************CPA2 configuration*****************************
source-bridge ring-group 2200
dlsw timer sna-cache-timeout
dlsw local-peer peer-id 2.2.2.2 keepalive 0 promiscuous
dlsw icanreach mac-exclusive
dlsw icanreach mac-address 4000.0e02.7206 mask ffff.ffff.ffff
dlsw icanreach mac-address 4000.0e13.7206 mask ffff.ffff.ffff
interface Loopback0
ip address 2.2.2.2 255.255.255.255
interface FastEthernet0/0
ip address 192.168.6.2 255.255.255.248
duplex full
speed 100
interface FastEthernet0/1
no ip address
shutdown
duplex full
speed 100
interface Channel1/0
ip address 130.114.2.3 255.255.255.0 secondary
ip address 130.114.1.3 255.255.255.0
no ip redirects
no ip route-cache cef
no ip mroute-cache
no keepalive
llc2 dynwind
claw 0122 32 130.114.2.1 DEVL WCPA2 TCPIP TCPIP
claw 0111 22 130.114.1.1 PROD WCPA2 TCPIP TCPIP
csna 0111 20 maxpiu 65535 length-delay 0
csna 0122 30 maxpiu 65535 length-delay 0
max-llc2-sessions 1024
lan TokenRing 2
source-bridge 1100 1 2200
adapter 2 4000.0e02.7206
adapter 3 4000.0e13.7206
*******************Remote Site Configuration************************
dlsw local-peer peer-id 192.1.120.100 keepalive 0
dlsw remote-peer 0 tcp 2.2.2.2 timeout 90
dlsw remote-peer 0 tcp 1.1.1.1 backup-peer 2.2.2.2 timeout 90 linger 5
dlsw bridge-group 1
Thank You for your response.

Hello,
Thank you for your response.
If i remove the keepalive 0 from the configuration of the remote site's router, the ddr will be made immediately after the primary link goes down (FR), it will stay active all time, because the dlsw is the intersting trafic for the ddr :access-
access-list 101 deny icmp any any
access-list 101 deny eigrp any any
access-list 101 permit tcp any any eq 2065
access-list 101 permit udp any any eq 2065
access-list 101 permit udp any any eq 2067
dialer-list 1 protocol ip list 101
I tested it before, and the only solution is to configure keepalive 0.
Thank you

Dlsw problem : stuck in WAIT_CAP

Hi all
we had a great problem with some snasw/dlsw routers.
About all dlsw peers remained in WAIT_CAP state( except few resources where dlsw connection ok ) while no ip issues were present between central routers and dlsw remote routers....
The appn snasw links seemed to be ok ( seeing the snasw link command )
A question : there is a relationship between dlsw peer state and snasw link , ie there is an interaction between the 2 processes that could block dlsw peering establishement if there is a mistake on snasw=appn process??
Thanks for feedbacks
Stefano R.

Stefano,
the debugging is telling us that the tcp write and read pipe was opened. Ok so far. Next the router is sending his cap_ex message and then this router waits for the cap_ex from the peer. Which never arrives.
So why is the cap exchange not arriving? It would be very much needed to see the debug from the other end at the same time to have a chance to understand what goes on.
Feb 1 09:12:25.524: DLSw: START-TPFSM (peer 10.237.88.136(2065)): event:ADMIN-OPEN CONNECTION state:DISCONN
Feb 1 09:12:25.524: DLSw: dtp_action_a() attempting to connect peer 10.237.88.136(2065)
Feb 1 09:12:25.528: DLSw: END-TPFSM (peer 10.237.88.136(2065)): state:DISCONN->WAIT_WR
Feb 1 09:12:26.037: DLSw: Async Open Callback 10.237.88.136(2065) -> 11241
Feb 1 09:12:26.037: DLSw: START-TPFSM (peer 10.237.88.136(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR
Feb 1 09:12:26.037: DLSw: dtp_action_f() start read open timer for peer 10.237.88.136(2065)
Feb 1 09:12:26.041: DLSw: END-TPFSM (peer 10.237.88.136(2065)): state:WAIT_WR->WAIT_RD
Feb 1 09:12:26.726: DLSw: passive open 10.237.88.136(28757) -> 2065
Feb 1 09:12:26.726: DLSw: START-TPFSM (peer 10.237.88.136(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD
Feb 1 09:12:26.726: DLSw: dtp_action_g() read pipe opened for peer 10.237.88.136(2065)
Feb 1 09:12:26.726: DLSw: CapExId Msg sent to peer 10.237.88.136(2065)
Feb 1 09:12:26.726: DLSw: END-TPFSM (peer 10.237.88.136(2065)): state:WAIT_RD->WAIT_CAP
Here you see when the write pipe opens, when the read pipe goes up, the tcp connection from the other router came back to us and this router is sending his CapExId to the peer but we dont get a response and time out.
thanks...
Matthias

DLSw redundancy problem

| |
****** ******** | |
* *--CPA1--*7206-1*--| ******** |
*IBM * ******** |--*7206-3*--|
* * | ******** |
*HOST* | |
* * ******** |--******** |
* *--CPA2--*7206-2*--| *7206-4*--|
****** ******** | ******** |
| |
7206-1 and 7206-2 manage the the connection to the IBM host with a CPA card eich other.
7206-3 and 7206-4 manage the connection between the central site and the remotes sites via frame-relay network, they are border peer and DLSw load balancing coded. also manage the connection between a LAN of the central site and with bridge-group to reach an IBM HOST via 7206-1 and 7206-2.
The following is the configurations:
7206-3:
dlsw local-peer peer-id 3.3.3.3 group 3 border keepalive 0 promiscuous
dlsw load-balance round-robin
dlsw remote-peer 0 tcp 1.1.1.1 timeout 90
dlsw remote-peer 0 tcp 2.2.2.2 timeout 90
dlsw cache-ignore-netbios-datagram
dlsw bridge-group 1
7206-4:
dlsw local-peer peer-id 4.4.4.4 group 3 border keepalive 0 promiscuous
dlsw load-balance round-robin
dlsw remote-peer 0 tcp 1.1.1.1 timeout 90
dlsw remote-peer 0 tcp 2.2.2.2 timeout 90
dlsw cache-ignore-netbios-datagram
dlsw bridge-group 1
The probleme is:
In the central site, i see a slowness in the connection, and it is random, sometime a connction is very fast, other time it is very slow, and it can take up to 1,5 minute to connect.
After all that, i coded a dlsw redundancy in the 7206-3 and 7206-4 FastEthernets, the problem still exist in the LAN, and it cause a trouble in some remotes sites connected with frame-relay, that loose a connection to HOST.
Thank You for your help.

1. To make load balancing work you will have to add the following commands:
dlsw timer explorer-wait-time ...
source-bridge ring-group ...
Ring-group number must be the same on 7206-3 & 7206-4 - it prevents unnecessary explorer flooding.
2. If bridge-group 1 on 7206-3 & 7206-4 shares the same Ethernet domain you must use DLSw+ Ethernet Redundancy feature.
3. Border peers in the same group must be in full-mesh and all members in the group must peers with all border peers in this group. On 7206-3 & 7206-4 you will have to add the following commands:
(7206-3)# dlsw remote-peer 0 tcp 4.4.4.4 ...
(7206-4)# dlsw remote-peer 0 tcp 3.3.3.3 ...

Problem establishing SNA session over DLSw link

We are experiencing sporadic problems establishing an SNA session over a DLSw tunnel. The session is between a Tandem host and a CICS region on OS/390. A Cisco 7500 router performs one end of the DLSw link; that same router is channel-attached to the OS/390 mainframe using CIP and uses CSNA for SNA traffic.
The connection is initiated by the SNA software on the Tandem box, but it rarely works on the first attempt. The session goes into a pending state and has to be cancelled and re-tried. This has to be repeated until such time it is successful. Once the session is started it works without problem.
At the point of attempting to start the session all the components are in the 'correct' state, i.e.
-DLSw tunnel is connected
-Host PU is in 'connectable' (CONCT) state
-Host XCA defining CIP SNA and virtual lines are active
No action needs to be taken on the OS/390 end of the link (or anywhere else for that matter) between start attempts on Tandem.
From device traces on OS/390 my suspicion is that the session requests are not actually getting to VTAM on OS/390 for some reason. DLSw traces on 7500 appear the same in both case of success or fail of session start.
Has anyone experienced this, or know of problems in this area that may explain what we are seeing?
Thanks.
Keith

Mary,
thanks for the extra information.
I would advice at this point the following:
Open a case with the Tac. Provide the information you have at that point and agree on a action plan, i.e. what to look at what trace to take, when you are able to recreate the problem.
What i can see from the documents you attaches is the following:
I only see sna circuits in the dlsw circuit history.
In you show dlsw reach there are quite some netbios names aswell and a large number of mac addresses learned from the remote peer.
You may want to discuss some filter options with the tac to make sure we cut down on the size of the reach cache and to make sure we advertise only those mac addresses which are really needed.
From the show version, 12.1(17) should be fine for dlsw in the way you described it.
From the show dlsw circuit history detail we have a couple of times that circuits are disconnecting.
Most of the time these circuits are up for a long time and they get the following sequence before terminating:
Index local addr(lsap) remote addr(dsap) remote peer
1157627904 4000.0410.0001(08) 0800.8e00.9708(08) 10.19.2.124
Created at : 12:02:55.115 GMT Mon Nov 29 2004
Connected at : 12:02:55.447 GMT Mon Nov 29 2004
Destroyed at : 22:04:01.158 GMT Wed Dec 1 2004
Local Corr : 1157627904 Remote Corr: 3321888773
Bytes: 140092/145133 Info-frames: 1748/2327
XID-frames: 1/2 UInfo-frames: 0/0
Flags: Remote created, Local connected
Last events:
Current State Event Add. Info Next State
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED ADM WanFailure 0x0 HALT_NOACK_PEND
HALT_NOACK_PEND DLC DiscCnf 0x0 CLOSE_PEND
CLOSE_PEND DLC CloseStnCnf 0x0 DISCONNECTED
this circuit was up for more than a month and the reason for disconnection was ADM WAN failure which means the dlsw peer went away at some point.
Some other circuits get these sequence:
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN halt-dl 0x0 HALT_PENDING
WAN halt-dl means the other end tells us to disconnect. No information on this end why. Most of the time it is a legitimate disconnect. but you would need to look at the dlsw peer to get information who terminated the session.
I dont see anything specific in a sense that a circuit did not go to connect at all. In the information you supplied.
Again my advice open a case with the tac and then you can work the issue to completion.
thanks...
Matthias

DLSW and Tunnel Interfaces problem

We have a pair of routers with tunnel interfaces and DLSW between them.
Some times the tunnel interface goes down thus loosing service trough DLSW.
Is there any problem reported between DLSW and this kind of tunel interfaces ?

Hi,
i assume you are using dlsw tcp peers.
In general dlsw does not know over what infrastucture the connection really runs. Dlsw gives data to tcp and tcp is responsible for doing the actual transmission.
I dont know of any problems with dlsw and tunnel interfaces in general.
Some more information might help to understand the problem.
What type of tunnel are you using? GRE?
What version of ios are you running?
Do you use additional encapsulation overhead like ipsec ect?
Does tcp on this router use path mtu discovery?
thanks...
Matthias

Dlsw vmac translation problem

I have topo like this:
(390)--sdlc---(router a)-------wan------(router b)---ethernet----(as400)
appc session can't established,so I capture frame on router b's ethernet,but I found the test frame:
smac=0200.0000.2083
dmac=4242.4242.0640
ssap=0
dsap=4
I don't know why(ios bug or ???),I think the correct frame maybe like this:
smac=0200.0000.2083
dmac=2424.2424.0640
ssap=0
dsap=4
the ios version is :
router a: c2600-is-mz.122-7b.bin
router b:rsp-a3jsv-mz_121-4.bin
following is config of router:
router a:
dlsw local-peer peer-id 10.1.1.1
dlsw remote-peer 0 tcp 10.8.1.1
interface Serial0/1
no ip address
encapsulation sdlc
no ip mroute-cache
no keepalive
sdlc role secondary
sdlc vmac 4000.0000.0400
sdlc address C1 xid-passthru
sdlc partner 4242.4242.6002 C1
sdlc dlsw C1
router b:
dlsw local-peer peer-id 10.8.1.1 promiscuous
dlsw bridge-group 13
interface FastEthernet6/1/0
no ip address
ip route-cache distributed
full-duplex
bridge-group 13
bridge 13 protocol ieee

My as/400 eth's mac is 4242.4242.0640,so I think the correct config of dlsw partner is
2424.2424.6002. If I config 2424.2424.6002,the mac can't be found. if I config
4242.4242.6002,the mac can be found. Like something is error,DLSw is try to chang my MAC
addresses between canonical format and noncanonical format, but it only change the last two byte. And you can see,dlsw can translate correctly the destionation of as/400 0200.0000.4080 to router's vmac 4000.0000.0201.
interface Serial0/0
no ip address
encapsulation sdlc
no ip mroute-cache
no keepalive
sdlc role secondary
sdlc vmac 4000.0000.0200
sdlc address 01 xid-passthru
sdlc partner 4242.4242.6002 01
sdlc dlsw 1
interface Serial0/1
no ip address
encapsulation sdlc
no ip mroute-cache
no keepalive
sdlc role secondary
sdlc vmac 4000.0000.0400
sdlc address C1 xid-passthru
sdlc partner 2424.2424.6002 C1
sdlc dlsw C1
router a#sh dlsw rea mac
DLSw Local MAC address reachability cache list
Mac Addr status Loc. port rif
4000.0000.0201 FOUND LOCAL Serial0/0 --no rif--
4000.0000.04c1 FOUND LOCAL Serial0/1 --no rif--
4242.4242.6002 SEARCHING LOCAL
DLSw Remote MAC address reachability cache list
Mac Addr status Loc. peer
4242.4242.6002 FOUND REMOTE 10.8.1.1(2065)
2424.2424.6002 SEARCHING REMOTE
router a#sh dlsw cir
Index local addr(lsap) remote addr(dsap) state uptime
3556770440 4000.0000.0201(04) 4242.4242.6002(04) CKT_ESTABLISHED -

Dlsw - circuit problem

Hi. all
I have several routers with dlsw feature.
Routers works properly yesterday but not today.
Someone complained to me why sna communication be delayed today?
So i tried to check such as dlsw peer, circuit.
i found instatble of the Circuit.
circuit's uptime be reset...
How can i check this symtom..?
Regard.
John

Thank you for replying.
The Topology is below.
HOST HOST
| |
|
4006 Switch
|
| |
Router1 Router2
| |
ATM ATM
| |
Router3
|
L2 Switch
|
SNA G/W
There are dlsw peer between Router1 and Router 3 and
Router 2 and Router3.
The Router 3 was configured loadbalancing(circuit-count) for sna traffic.
Acually, i found some abnormal history by using "show dlsw circuit history detail".
469762913 0060.9436.d70a(04) 4848.2424.1212(04) 172.20.52.231
Created at : 10:59:11.230 KST Mon Dec 13 2004
Connected at : 10:59:11.314 KST Mon Dec 13 2004
Destroyed at : 11:46:50.699 KST Mon Dec 13 2004
Local Corr : 469762913 Remote Corr: 704643190
Bytes: 86335174/88147104 Info-frames: 106541/108372
XID-frames: 5/4 UInfo-frames: 0/0
Flags: Local created, Remote connected
Last events:
Current State Event Add. Info Next State
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN ifcm 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED DLC DataInd 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN infoframe 0x0 CONNECTED
CONNECTED WAN halt-dl 0x0 HALT_PENDING
HALT_PENDING DLC DiscCnf 0x0 CLOSE_PEND
CLOSE_PEND DLC CloseStnCnf 0x0 DISCONNECTED

Problem with SNA Traffic (AS-400)

I have a problem my frame-relay point-to-point network: Actually, the primary site equipment is a Cisco 2801 ISR and the remote site is Cisco 1005 and with this deployment full service working satisfactory but when I do change the 1005 router por Cisco 1841 one at remote site (technological innovation) any service of the network no working. The configuration on the routers 1005 and 1841 are same with the normal exceptions in OS. What can be happened it? At primary site and the remote site there are AS-400 platform.

did you check feature set of both old and new version?
Maybe there are some DLSW issues.
Ivan

Dlsw using port channel

I have 2 dlsw router at head quater office, named dlswA and dlswB.
From branches router, dlswA is a primary peer and dlswB is a backup peer.
Both dlswA and B have 2 fast ethernet interfaces.
The current configuration of dlswA and dlswB are 1 port as IP port and other port as sna/bridge port.
With this configuration the problem is when SNA port at dlswA problem, then dlsw circuit will have the problem, because dlsw peer from branches still connected to dlswA.
if I configure 2 fast ethernet port become a port channel. And configure IP and bridge group at port channel interface (IP and SNA at the same interfaces), so when the port channel is down, then branches will connect to dlswB as a backup peer
Are the port channel configuration will solve the problem ? How about the stability of this configuration?

Thank Matthias for your reply.
Both of head end routers are on the same vlan and the host is using same mac address.
As far as i know if from branch have 2 active peer with cost setup, there will loops posibility because both head end routers are using ethernet with same vlan and same host mac address.
I test the port channel within my LAB using netbios, seem works as expected. when single port at port channel down, branch circuit still remain at dlswA router, when all port channel member down, the branch peering move to dlswB.
Here are the config:
hostname dlswA
dlsw local-peer peer-id 192.168.255.1 promiscuous
dlsw bridge-group 1
interface Port-channel10
ip address 192.168.255.1 255.255.255.248
bridge-group 1
interface FastEthernet0/0
no ip address
duplex auto
speed auto
channel-group 10
interface FastEthernet0/1
no ip address
duplex auto
speed auto
channel-group 10
end
hostname dlswB
dlsw local-peer peer-id 192.168.255.10 promiscuous
dlsw bridge-group 1
interface Port-channel11
ip address 192.168.255.10 255.255.255.248
bridge-group 1
interface FastEthernet0/0
no ip address
duplex auto
speed auto
channel-group 11
interface FastEthernet0/1
no ip address
duplex auto
speed auto
channel-group 11
end
Hostname Branch
dlsw local-peer peer-id 172.16.0.1
dlsw remote-peer 0 tcp 192.168.255.1
dlsw remote-peer 0 tcp 192.168.255.10 backup-peer 192.168.255.1 linger 0
dlsw bridge-group 1
interface Loopback0
ip address 172.16.0.1 255.255.255.255
interface FastEthernet0/1
no ip address
duplex auto
speed auto
bridge-group 1
But I'm not sure this scenario will work for sna application like ATM machine, and SNA SAA gateway.
Please kindly advised, Is there any alternatif ?

Dlsw circuits random disconnect

Hello!!
Could somebody help me with this?
We have a dlsw network of almost 1600 remote dlsw peers.
We have six central peer routers.
Sometimes we saw some SNA PU´s down, and after 1 to 3 min return to "CONNECTED" (dlsw circuit). We dont´n see any dlsw peer down, only dlsw circuit falls.
On branch office router we saw by the command "show dlsw ciscuits history detail", that the event before disconnect is
Event
WAN halt-dl
What does this mean?
It is possibly a problem with the Central Peer Router?
The Carrier confirm us no problem with the WAN Network.
The Central Routers are Cisco7200VXR NPE400 512DRAM and IOS 12.4(4)T1
The branch office routers are Cisco1760 IOS 12.3(9).
Thanks for help!!
Pedro.

I'd look into monitoring the CPU usage (as well as the amount of memory used by DLSw Process) of the 1700 series branch routers. It may be that these TCP based connections from the 6 central routers are overwhelming them.
(i.e., http://www.cisco.com/warp/public/63/highcpu_processes.html#tcp_timer)
Especially if the remote routers are pushing a fair amount of traffic with process switching turned on the intfs (i.e., ACLs with the 'log' option on) or if you have stuff like SNMP polls from network mgmt software going.
Also...................
"Disconnectphase. When an LLC end station wishes
to terminate one of its existing connections, it sends
a disconnect (DISC) frame to the other end station,
which responds with UA. The same frame types are
defined for SDLC. With DLSW, these frames are reflected
between partners using the SSP messages
halt-dl (halt data link) and dl-halted (data link halted)
and the circuit is then disconnected. Another DLSW
disconnect scenario is the loss of a transport connection
due to intermediate router failure. When
a DLSw node detects such a failure, it performs a
local disconnect of all connected data links that
were using the failed transport connection."
from: http://www.research.ibm.com/journal/sj/343/gayek.pdf
**Hope this helps**
Based on your earlier statement...
"On branch office router we saw by the command "show dlsw ciscuits history detail", that the event before disconnect is
Event
WAN halt-dl
What does this mean? "
I'd look into the process utilization on the Branch routers

Problem with SNA Gate eWay

Hi,
We are having a problem with SNA eWay.
In our project, with an single interface, the invoking program TP (Transaction Program) in mainframe will invoke program TP (Transaction Programs) in SeeBeyond. This is fine and running well when only one interface is deployed and tested.
The problem is when we deploy more than one interface in logical host, the TP to TP communication is mismatching. The actual invoked TP by SNA gateway server is not starting in SeeBeyond. It is actually running randomly the TPs (jcds) deployed and active in the logical host.
Can any one please show some light on this.
Thanks In Advance.

did you check feature set of both old and new version?
Maybe there are some DLSW issues.
Ivan

Dlsw on cat3550

hi,
i've this problem
i have a catalyst 3550 that work at layer 2 / layer 3
i need to implement a datalink switch with another layer3 switch , but my cat 3550 don't have a CLI for enable the dlsw.
Do you know if this product support this features or what is the version of IOS that support that.
Thanks
FCostalunga

I have checked using the Software Advisor on the Cisco web site and I do not find any version of software for the 3550 that shows support for DLSw. I think you will need a different box to get the DLSw support.
HTH
Rick

DLSW peer takes 20 min. to establish..Please Help !!!

I have configured a Cisco 7304 with DLSW and the remote peer is not a Cisco router. When the local peer in the Cisco is not configured as promiscuous, it takes about 20min to 1h30min for the peers to get connected.
If the local peer is configured as promiscous, it works good, but we dont want to use this configuration becasuse we want to control the connections on each router.
What can I do in order to solve this problem ?
Attached is the router configuration and the output of a "debug dlsw peers"

Hi,
based on the debug dlsw peer:
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:ADMIN-OPEN CONNECTION state:DISCONN
00:02:00: DLSw: dtp_action_a() attempting to connect peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:DISCONN->WAIT_WR
00:02:00: DLSw: Async Open Callback 172.25.252.254(2065) -> 11004
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:TCP-WR PIPE OPENED state:WAIT_WR
00:02:00: DLSw: dtp_action_f() start read open timer for peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_WR->WAIT_RD
00:02:00: DLSw: passive open 172.25.252.254(2067) -> 2065
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:TCP-RD PIPE OPENED state:WAIT_RD
00:02:00: DLSw: dtp_action_g() read pipe opened for peer 172.25.252.254(2065)
00:02:00: DLSw: CapExId Msg sent to peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_RD->WAIT_CAP
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP
00:02:00: DLSw: dtp_action_j() cap msg rcvd from peer 172.25.252.254(2065)
00:02:00: DLSw: Recv CapExId Msg from peer 172.25.252.254(2065)
00:02:00: DLSw: Pos CapExResp sent to peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_CAP->WAIT_CAP
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:SSP-CAP MSG RCVD state:WAIT_CAP
00:02:00: DLSw: dtp_action_j() cap msg rcvd from peer 172.25.252.254(2065)
00:02:0
Torrejon0#0: DLSw: Recv CapExPosRsp Msg from peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_CAP->WAIT_CAP
00:02:00: DLSw: Processing delayed event:SSP-CAP EXCHANGED - prev state:WAIT_CAP
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:SSP-CAP EXCHANGED state:WAIT_CAP
00:02:00: DLSw: dtp_action_k() cap xchged for peer 172.25.252.254(2065)
00:02:00: DLSw: closing read pipe tcp connection for peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:WAIT_CAP->PCONN_WT
00:02:00: DLSw: Processing delayed event:TCP-PEER CONNECTED - prev state:PCONN_WT
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:TCP-PEER CONNECTED state:PCONN_WT
00:02:00: DLSw: dtp_action_m() peer connected for peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:PCONN_WT->CONNECT
at this point the dlsw peer is in state CONNECTED
However you always get a tcp rst or fin right afterwards. Tcp tells dlsw to disconnect the peer.
This can have two potential sources.
The tcp stack on this router or the tcp stack on the remote router has closed the session.
00:02:00: DLSw: dlsw_tcpd_fini() for peer 172.25.252.254(2065)
00:02:00: DLSw: tcp fini closing connection for peer 172.25.252.254(2065)
00:02:00: DLSw: START-TPFSM (peer 172.25.252.254(2065)): event:ADMIN-CLOSE CONNECTION state:CONNECT
00:02:00: DLSw: dtp_action_b() close connection for peer 172.25.252.254(2065)
00:02:00: DLSw: END-TPFSM (peer 172.25.252.254(2065)): state:CONNECT->DISCONN
so the question really is where does the tcp rst come from? Who is closing the tcp connection?
This sequence repeats itself over and over again until it finally stays up.
You can do a
debug ip tcp driver
debug ip tcp transaction
this will show you if you get a disconnect or if this router is sending one. However you have to be a bit carefull with the debugging if you have a lot of tcp activity going on in this router.
Alternative is to take a sniffer trace on the WAN and find out who is sending the tcp reset/fin in that case.
thanks...
Matthias

DLSW Problem...

Similar Messages

Maybe you are looking for