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

Similar Messages

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 ...

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 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

DLSw+ local switching, Ethernet to QLLC

In the following url:
http://www.cisco.com/en/US/partner/tech/tk331/tk336/technologies_configuration_example09186a0080093fba.shtml
there is an example of using DLSw+ for connecting an ethernet device and a x.25 (QLLC) FEP. Is the opposite connection valid? For example, if the x.25 is at the branch level and ethernet at the Mainframe (OSA card), can DLSW+ still be used for connecting the device?
I am asking this, because we have a case where various servers in various sites are connected with x.25 lines to the IBM 3745. The scope is to replace this IBM 3745 with a cisco router and OSA card.
However, a change in all x.25 servers is out of the question (for the time being).

yes, the scenario you describe is possible. In general everything you can do with dlsw local switching can also be done remote via dlsw.
It is always a matter of working out the specific details how to configure qllc. If you need specific assistance with a configuration open a case with the tac and the issue will be worked on.
thanks...
Matthias

URPF (ip verify unicast reachable) command not found on Cat3550

Hello,
I can't find "ip verify unicast ~~" command on cat3550 with 12.1(22)EA1a.
Os code name is c3550-i5q3l2-mz.121-22.EA1a.
but i found that command on Cat3550 with 12.1(11)EA1, it's code name is c3550-i5q3l2-mz.121-11.EA1.
Cisco do not support higher version?
Regard,
John.

Hi John,
uRPF has never been supported on the 3550. The hardware cannot perform the function. The command was included in the CLI in older versions, but was eventually removed to prevent confusion.
HTH,
Bobby
*Please rate helpful posts.

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 Background process

I have this problem in my router 7206VXR (NPE400) with IOS c7200-a3js-mz.121-5.T12.bin :
%SYS-3-CPUHOG: Task ran for 9052 msec (4512/71), process =
DLSw Background, PC = 60638020.
%SYS-2-MALLOCFAIL: Memory allocation of 788 bytes failed f
rom 0x605E1730, pool I/O, alignment 32
-Process= "TCP Driver", ipl= 4, pid= 103
-Traceback= 60629D10 6062B1A0 605E1738 605E1A80 605E2000 606FE94C 6070619C 60706
53C 607D823C 607D8D6C 607D8FD4 60620664 60620650
and after the router crash.I didn't find bugs for this problem .
Could any help me?
Thanks
Regards
Roberto

Looks like the router has a bug called a memory leak. This is where a process is failing to return memory to the free memeory pool so the router eventually runs out.
The following URL gives guidelines for troubleshooting memory problems -
http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1831/products_tech_note09186a00800a6f3a.shtml

DlSW/SDLC 1841 ROUTER.

I have just tried to implement by first 1841 router.
I used the same template that I have for over 400 sites ( 1600 , 1700 , 2500 and 3600 series routers )
I get the dlsw peers established no problem.
The problem is on the serial interface in the router.
It is an IBM 5494 controller .
Here is the configuration that I have for the serial interface.
I have added the routers configuration.
Any ideas??? Is there something that I need to add to the serial interface on the 1841's that was not required before ???
My IOS is (C1841-ENTBASE-M), Version 12.3(11)T2
tks.

Hi,
please open a case with the tac. There have been a few problems with sdlc and 12.3T, also there are some issues depending on the hardware you are using.
The Tac will help you to collect all the needed information to understand your problem and then guide you to a resolution.
thanks...
Matthias

DLSW drop sporadically

Setup
6509 (IOS 12.1(13)E6) running standard DLSW ( i.e. non ethernet redundancy)over FastEthernet to 7513 (12.1(14)) connected to Mainframe over CIP2/IBM Channel.
1.
Our PC running LU6.2 over ethernet connected to the 6509 spordic loose thier connection due to the DLSW peer drops. (on the DLSW peer there is max 100 circuits)
2.
The 6509 have orther DSLW peers that run to other routers that are unaffected by the dropping peer.
3.
Likewise the 7513 that is the peer for the dropping DLSW connection has other peers that are unaffected.
4.
On a DLSW debug I see that the drop is caused due to failed DLSW keepalives.
5. As I found the CSCdw58350 I would appreciate some details how to determine if its the CSCdw58350 thats causing my problems ?? Or any other suggestions for the cause - thanks.
Regards
Gert Schaarup

Thanks
1. I will go for the IOS upgrade, but do I need to upgrade both ends of the dlsw peer ? (i.e. the 7513 with the CIP and the 6500 with the LU6.2 workstations)
2. After we moved some of the LU6.2 client to Token Ring (i.e. direct SNA to the host) the dlsw peer seems to stay up but we still see that dlsw circuits gets disconnected and shortly after reconnect without direct loss of LU6.2 data.
3. I do see some few half flow op and reset (like Half: 6/2 Reset 1/0) but could you please comment following output (taken 4 and 9 July when the peer is up, as the peer hasnt gone done since we moved some of the load) to see if these confirm that it is the bug that is the problem. - Thanks
07:54:01.231 PDT Fri Jul 4 2003
At the 7513 end:
CIP-Slot4#llc stat all
Maximum connections = 1200
Highest connections = 169
Current connections = 59
Connections rejected = 0
Connect requests = 5615
Connect responses = 0
Connect confirms = 5615
Connect indications = 0
Disconnect confirms = 207
Disconnect indications = 5128
Flow off terminated conn = 0
Session timeouts = 99
FRMRs sent = 1
FRMRs received = 1
SABMEs sent = 5632
SABMEs received = 0
DISCs sent = 542
DISCs received = 5027
UAs sent = 5027
UAs received = 5811
DMs sent = 0
DMs received = 10
IDLE connections = 0
Connection thresheld = 1200
Frames transmitted = 130903182
Transmit completes = 130903182
Frames received = 124105764
Flow offs sent = 43844
Flow ons sent = 43810
Flows (on/off) cancel = 180
Flow offs received = 0
Flow ons received = 0
CCB indications sent = 92883
CCB indications freed = 92883
Unexpected events = 36
Ack Timer Missed = 0
Frames ignored = 4
Data requests = 101195500
Data requests freed = 101193980
Aggregate data req qlen = 0
Maximum data req qlen = 0
Data indications = 87183015
Data indications freed = 87183015
Aggregate data ind qlen = -1457917659
Maximum data ind qlen = 87183015
Polls sent = 152722
Finals sent = 18591962
Polls rcvd = 18625036
Finals rcvd = 158403
RR polls sent = 152722
RNR polls sent = 0
REJ_polls sent = 0
RRs sent = 29607348
RRs received = 36878480
RNRs sent = 80011
RNR received = 27452
REJs sent = 1487
REJs received = 4178
Bad PDUs received = 0
Bad N(r)s received = 5
Bad N(s)s received = 1747
Out-of-seq N(s)s received = 38
Acknowledgements delayed = 81673676
Iframes transmitted = 101203134
Iframes retransmitted = 9115
Retries = 7507
Local busy entered = 96226
Local busy exited = 96226
Remote busy entered = 9737
Remote busy exited = 9429
Unexpec Ack = 0
Adapter registered = 4
SAPs registered = 1
CEPs registered = 59
Msgs to entity mgr = 31
Msgs to PSAP = 58712
Msgs to PCEP = 101206483
Msgs to DLU = 87346909
Invalid handles = 0
SAPs activated = 8
Deactivate SAP requests = 5
Deactivate SAP confirms = 5
SAPs reset by user = 2
SAPs reset by network = 0
SAP deact/reset completed = 7
SAPs deact/reset w/ CCBs = 2
SAPs frame drops = 0
Hash buckets used = 3439
Hash table collisions = 2181
Hash table lookups = 124174704
Hash table caparisons = 198849566
Hash table lookups failed = 58305
Longest collistion chain = 19
Receive erroneous frame = 0
DMA write operations = 130999946
DMA write completions = 130999946
DMA write errors = 0
DMA write waits = 0
DMA read notifications = 124534436
DMA read operations = 124534436
DMA read completions = 124534435
DMA read errors = 0
DMA reads discarded = 0
DMA reads discarded small = 0
DMA read chains freed = 0
Frames exceed MAX frameSZ = 0
Timer ticks (100ms) = 222075154
Timeouts = 6502680
Timers started = 275098246
Timers stopped = 268595506
T1 timers expired = 7607
Idle timers expired = 91521
T2 timers expired = 6403552
Longest timeout chain = 58
P/F timer started = 163700
P/F timer stopped = 158403
Ack timer started = 66234646
Ack timer stopped = 58411329
Busy timer started = 13354
Idle timer started = 145383718
T2 timer started = 63301341
T2 timer stopped = 63301340
Reject timer started = 1487
Reject timer stopped = 1589
LLC Stack locked = 363336715
LLC Stack delayed events = 101
LLC stack pending events = 0
LLC stack most pndng evnts= 1
LLC stack not locked.
15:17:44.199 PDT Wed Jul 9 2003
At the 7513 end:
CIP-Slot4#llc stat all
Maximum connections = 1200
Highest connections = 169
Current connections = 69
Connections rejected = 0
Connect requests = 10778
Connect responses = 0
Connect confirms = 10778
Connect indications = 0
Disconnect confirms = 301
Disconnect indications = 10216
Flow off terminated conn = 0
Session timeouts = 118
FRMRs sent = 1
FRMRs received = 1
SABMEs sent = 10815
SABMEs received = 0
DISCs sent = 628
DISCs received = 10096
UAs sent = 10096
UAs received = 11037
DMs sent = 0
DMs received = 12
IDLE connections = 0
Connection thresheld = 1200
Frames transmitted = 153147701
Transmit completes = 153147701
Frames received = 146574711
Flow offs sent = 52506
Flow ons sent = 52472
Flows (on/off) cancel = 198
Flow offs received = 0
Flow ons received = 0
CCB indications sent = 115314
CCB indications freed = 115314
Unexpected events = 103
Ack Timer Missed = 0
Frames ignored = 4
Data requests = 119159228
Data requests freed = 119157594
Aggregate data req qlen = 0
Maximum data req qlen = 0
Data indications = 102290655
Data indications freed = 102290655
Aggregate data ind qlen = -2074303823
Maximum data ind qlen = 102290655
Polls sent = 182235
Finals sent = 21206449
Polls rcvd = 21242583
Finals rcvd = 193195
RR polls sent = 182235
RNR polls sent = 0
REJ_polls sent = 0
RRs sent = 33862716
RRs received = 44225534
RNRs sent = 93378
RNR received = 30175
REJs sent = 2075
REJs received = 4686
Bad PDUs received = 0
Bad N(r)s received = 5
Bad N(s)s received = 2441
Out-of-seq N(s)s received = 69
Acknowledgements delayed = 95797452
Iframes transmitted = 119167992
Iframes retransmitted = 10275
Retries = 7696
Local busy entered = 108966
Local busy exited = 108966
Remote busy entered = 11023
Remote busy exited = 10715
Unexpec Ack = 0
Adapter registered = 4
SAPs registered = 1
CEPs registered = 69
Msgs to entity mgr = 35
Msgs to PSAP = 85729
Msgs to PCEP = 119180620
Msgs to DLU = 102514497
Invalid handles = 0
SAPs activated = 9
Deactivate SAP requests = 6
Deactivate SAP confirms = 6
SAPs reset by user = 2
SAPs reset by network = 0
SAP deact/reset completed = 8
SAPs deact/reset w/ CCBs = 2
SAPs frame drops = 0
Hash buckets used = 8529
Hash table collisions = 2283
Hash table lookups = 146676148
Hash table caparisons = 224807587
Hash table lookups failed = 80517
Longest collistion chain = 19
Receive erroneous frame = 0
DMA write operations = 153281642
DMA write completions = 153281642
DMA write errors = 0
DMA write waits = 0
DMA read notifications = 147050284
DMA read operations = 147050284
DMA read completions = 147050284
DMA read errors = 0
DMA reads discarded = 0
DMA reads discarded small = 0
DMA read chains freed = 0
Frames exceed MAX frameSZ = 0
Timer ticks (100ms) = 226558498
Timeouts = 7361429
Timers started = 324359028
Timers stopped = 316997530
T1 timers expired = 7815
Idle timers expired = 109334
T2 timers expired = 7244280
Longest timeout chain = 58
P/F timer started = 203551
P/F timer stopped = 193195
Ack timer started = 78970086
Ack timer stopped = 68892536
Busy timer started = 14376
Idle timer started = 170688653
T2 timer started = 74480287
T2 timer stopped = 74480287
Reject timer started = 2075
Reject timer stopped = 2229
LLC Stack locked = 426985053
LLC Stack delayed events = 120
LLC stack pending events = 0
LLC stack most pndng evnts= 1
LLC stack not locked.

Dlsw and 802.1q

Will DLSw and 802.1q ever be supported together or are there some technical issues that will always force you to use isl trunking with dlsw instead of 802.1q?
problem is that there are switches that don't support isl.

DLSW support matrix documentation at:
http://www.cisco.com/warp/public/cc/pd/ibsw/ibdlsw/tech/dls24_rg.htm
in table B-3 and note 5, clearly states that 802.1q is not supported.
If you configure, it might work but it's not supported by TAC as it has not been dev-tested for this function

Dlsw spanning-tree

Hi, my name is fabio and i´ve a problem with dlsw.
When i´ve configured de dlsw in a router 3600 the router 7206 that has the conection with mainframe, the same lost the comunication e appears the messagem in 3600 router, look at below:
Note: A random Spanning Tree Bridge Identifier address of 0000.0cfe.6628
has been chosen for Bridge Group 50 since there is no mac address
associated with the selected interface.
I´am putting the scheme in .ppt.
Can i sending configurations of 3600 and 7200 to help you.
thanks

Fabio
I'm not sure what the issue is here. The mac-address of the end-stations will not be visible in the 4948 as the SNA traffic is encaps'd in ip. Can you supply sh vers, sh runn, sh dlsw pe, sh dls reach, sh dls circuit, sh bri from the 3640 and the 7206. What is the mac-address of the end-station to which mac-address is it trying to connect ?
Matthew

DLSW and 4510

Hi,
We are trying to configure dlsw on a Cat4510R switch that is connected to 2 routers for redundancy. DLSW is not supported on the 4500 switches. What is the best way to configure DLSW in this situation? Looking for configuration assistance.
Thanks,
Greg

You don't need to do anything in the switch.
The routers must be configured properly, and the details are dependant by the topology and applications.
In case of doubts, I recommend you engage a reputable consultant or certified partner with proven SNA-specific experience.

Dlsw on cat3550

Similar Messages

Maybe you are looking for