SDLC - DLSW - EE(SNASW) question
I have very little background knowledge of DLSW or SNASwitching, but here goes...
I am currently trying to migrate an existing connection from SDLC -> DLSW ->token ring mainframe connection to SDLC -> DLSW -> SNASW EE. My EE connection from the cisco router to hte mainframe is up and active, but I am unable to get the DLSW connection to work. I have been able to get the Peers to CONNECT, but I do not have any DLSW circuits.
Remote Router
dlsw local-peer peer-id 192.168.105.84
dlsw remote-peer 0 tcp 10.248.3.36
dlsw remote-peer 0 tcp 192.168.105.46
dlsw remote-peer 0 tcp 192.168.105.47
interface Ethernet0/0
ip address 192.168.105.84 255.255.255.0
interface Serial0/0
no ip address
shutdown
interface BRI0/0
no ip address
shutdown
interface Serial1/0
description MPSM - MPS SDLC connection to MPS9 gateway
bandwidth 19200
no ip address
encapsulation sdlc
no keepalive
sdlc role primary
sdlc vmac 4534.0000.0900
sdlc address C1
sdlc xid C1 05310170
sdlc partner 4800.0000.0000 C1
sdlc dlsw C1
interface Serial1/1
description MPSM MT80MPS7 - IP80GG73
bandwidth 19200
no ip address
encapsulation sdlc
no keepalive
sdlc role primary
sdlc vmac 4534.0000.0700
sdlc address C1
sdlc xid C1 05310172
sdlc partner 4800.0000.0000 C1
sdlc dlsw C1
interface Serial1/2
description MPSM MT80MPS5 - IP80GG53
bandwidth 19200
no ip address
encapsulation sdlc
no keepalive
sdlc role primary
sdlc vmac 4534.0000.0500
sdlc address C1
sdlc xid C1 05310174
sdlc partner 4800.0000.0000 C1
sdlc dlsw C1
RTGRAMIHQMPSM01#sho dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts TCP uptime
TCP 10.248.3.36 CONNECT 58648 59193 conf 0 0 0 2w6d
TCP 192.168.105.46 CONNECT 1085642 1212360 conf 0 2 0 2w6d
TCP 192.168.105.47 CONNECT 58492 58492 conf 0 0 0 2w6d
Total number of connected peers: 3
Total number of connections: 3
RTGRAMIHQMPSM01#sho dlsw circ
Index local addr(lsap) remote addr(dsap) state uptime
1929380244 4534.0000.05c1(04) 4800.0000.0000(04) CONNECTED 2w6d
2969567635 4534.0000.07c1(04) 4800.0000.0000(04) CONNECTED 2w6d
Total number of circuits connected: 2
Data Center Router
source-bridge ring-group 336
dlsw local-peer peer-id 10.248.3.36
dlsw remote-peer 0 tcp 192.168.105.84
dlsw remote-peer 0 tcp 192.168.105.85
interface Loopback0
ip address 10.210.136.65 255.255.255.255
interface GigabitEthernet0/1
description VLAN526 to XWGRAMIDCFPIP01
ip address 10.248.3.36 255.255.255.248
duplex full
speed 100
media-type rj45
negotiation auto
interface FastEthernet0/2
no ip address
shutdown
duplex auto
speed auto
interface GigabitEthernet0/2
description VLAN529 to XWGRAMIDCFPIP02
ip address 10.248.3.44 255.255.255.248
duplex full
speed 100
media-type rj45
negotiation auto
interface GigabitEthernet0/3
no ip address
shutdown
duplex auto
speed auto
media-type rj45
negotiation auto
snasw pdlog information
snasw dlctrace buffer-size 10000
snasw cpname NETMPS.GRSNAS01
snasw dlus NETMPS.XD81
snasw port SNSWPORT hpr-ip GigabitEthernet0/1
snasw port DLSWPORT vdlc 336 mac 4800.0000.0000 conntype nohpr
snasw link SW01XD81 port SNSWPORT ip-dest 204.90.2.14
RTGRAMIDCSNAS01#sho dlsw peer
Peers: state pkts_rx pkts_tx type drops ckts TCP uptime
TCP 192.168.105.84 CONNECT 58652 58649 conf 0 0 0 2w6d
TCP 192.168.105.85 CONNECT 58578 58578 conf 0 0 0 2w6d
Total number of connected peers: 2
Total number of connections: 2
RTGRAMIDCSNAS01#sho dlsw circ
RTGRAMIDCSNAS01#
Like I said, I have little background knowledge about this connectivity. If there is additional information that I could provide, please let me know. Any help would be greatly appreciated.
Thanks,
Dave
To answer one of your questions, as far as I know, SNASw performance might not be same as that of HPR/IP
Similar Messages
-
How to handle DLSw for SDLC and token-ring to same remote peer
We have the need to have SDLC and token-ring connections from one local router to a the same remote site. Currently we have a remote peer for token-ring:
dlsw port-list 10 TokenRing0/0
dlsw remote-peer 10 tcp a.b.c.d lf 1500
We have an SDLC link on a serial port. I understand that SDLC is part of group 0. How do I also get the SDLC traffic to the same remote peer? Is it as simple as adding another remote peer statement to the same IP?
dlsw remote-peer 0 tcp a.b.c.d lf 1500Do you have your token ring configuration complete to bridge to DLSW ?
for example;
source-bridge ring-group 2000
dlsw local-peer peer-id 150.150.10.1
dlsw remote-peer 0 tcp 150.150.10.2
interface loopback 0
ip address 150.150.10.1 255.255.255.0
interface serial 0
ip address 150.150.11.1 255.255.255.192
interface serial 1
description PU2 with SDLC station role set to secondary
no ip address
encapsulation sdlc
no keepalive
clockrate 9600
sdlc role primary
sdlc vmac 4000.9999.0100
sdlc address 01
sdlc xid 01 05d20006
sdlc partner 4000.1020.1000 01
sdlc dlsw 1
interface serial 2
description Node Type 2.1 with SDLC station role set to negotiable or primary
encapsulation sdlc
sdlc role prim-xid-poll
sdlc vmac 1234.3174.0000
sdlc address d2
sdlc partner 1000.5aed.1f53 d2
sdlc dlsw d2
interface tokenring 0
no ip address
ring-speed 16
source-bridge 100 1 2000
source-bridge spanning
If your SDLC link is working through DLSW (it is in DLSW ring group 10 according to your first configuration statement and port list statement and must match at both ends), it should be an easy modification to add the token ring configuration to join the bridge to the remote DLSW router.
See;
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm_c/bcfpart2/bcfdlsw.htm#1003756
best of luck -
hi
i have a RS232 device that connect to 2600 router and the router configuration is:
interface Serial0/1
no ip address
encapsulation sdlc
no keepalive
nrzi-encoding
clockrate 19200
sdlc role primary
sdlc vmac 4000.0018.6600
sdlc address A5
sdlc xid A5 05D018A5
sdlc partner 6600.0000.9918 A5
sdlc line-speed 19200
sdlc dlsw default
This is a cisco router with DLSW configuration and i have a problem with the work speed of the device,any operations took many time more than the same device how connect to ibm router,why that maybee configuration or ios.
please answer me.
it very urgent.
Thanks.This question was also posted on the WAN Routing and Switching forum where it has gotten some responses. I suggest that we consolidate the discussion on the WAN forum.
HTH
Rick -
The network topology that I have is two MSFCs and two external routers at central site and two MSFCs and two external routers at the remote site.
DLSW is activated on the external routers. In regards to DLSW+ ER at the central site, only one translational or transparent bridge can be active at a time. Manual intervention is required to cause a router to take over for the other router. Is there any other way to have some means of dlsw redundancy (w/o manual intervention) at the central site (for ethernet environment only)?
Second, DLSW ER+ cannot be deployed easily at the central site, since you need a lot of dlsw mapping. On the other hand, you also need local SNA PUs to be able and reach the CIP (both located at the central site) but reside on a different broadcast domain. Any ideas?
ThanksHi,
on the central side, host end, there are a couple of things you can do.
The potential solutions mentioned below are in the order that cisco would prefer.
1.
The most clean thing to do is to upgrade and configure the mainframe for appn and allow hpr/ip between the host end router and the host.
You will need to run dlsw/vdlc/snasw in the host end routers to be able to do this.
It also requires that you have ip connectivity to the mainframe.
If you do this than the mac address, the remote devices connect to, is configured as a snasw vdlc port in the routers. Both of them are active all the time, the remotes will learn the remote mac address over both peers and as such you have automatic, non manual intervention, redundancy, loadbalancing. The mac addresses in this case only exist in the central router. Nowhere else. The remote device does not know anything about this change.
Each of the head end dlsw/vdlc/snasw routers will have at least one hpr/ip uplink to the host. This is routed ip traffic into the mainframe.
In that case you can also define the physical ethernets as snasw ports, do hsrp on it and configure a hsrp mac address, this mac address would then be used as dmac for local clients connecting to the host.
2.
If for some reason you can not do the appn/snasw configuration you still have some options.
If you are using cisco cip's with csna today than you most likely have on path into the mainframe today for each mac address.
You can configure multiple vlans between the dlsw router and the cip router, i.e. dot1q trunk, and on the cip router you can configure multiple virtual ring groups and more than one csna path statement into the host. At the end you attach each vlan to one of the channel path, configure srtlb for each vlan into a unique vring, and then configure a different adapter number on each of the internal tokenring lans with the same mac address.
On the dlsw router you can configure multiple bridge groups into dlsw and each of those bridge groups goes to a different vlan. If you do this with two dlsw routers going to the same cip router you then end up with two channel access's and one vlan on each of the dlsw routers. If you do it to two cip routers you need 4 vlans. Just make sure that you dont bridge the vlans together.
The remotes learn than the remote mac address over both peers and your redundancy is established.
For the local clients this solution has the draw back that you need to pick a vlan where to connect them. There is no automatic redundancy, like hsrp in the first example, for those.
3.
You can enable both dlsw routers towards a single bridge-group and apply a mac address filter inbound to the bridge group only allowing the mac address/es of the hosts as source mac address.
That way you kill the potential loop on the head end. You will also need to put on as much restrictive filtering as possible to only allow the traffic that is wanted.
thanks...
Matthias -
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 ieeeMy 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 over WAN to Ethernet to Token Ring
Currently, a 3745 in Portland is token ring attached and SNA traffic travels that ring to an IBM 2210 router.
That IBM router connects to a second token ring, which a Cisco 2613 is also connected to. From there
the traffic travels DLSw over the WAN (3 T1s, Multilink PPP bundle) to a 7507 in Cincinnati where a 3745
is connected via serial.
3745-TIC<->TR<->2210<->TR<->2613(DLSw)<->WAN<->(DLSw)7507<->LIC-3745
The 7507 serial port is configured as follows:
interface Serial4/3
description 3745 LIC connection for Fred Meyer DLSW
mtu 4400
no ip address
encapsulation sdlc
no ip mroute-cache
no keepalive
serial restart-delay 0
clockrate 125000
sdlc vmac 4000.3745.0000
sdlc N1 35200
sdlc address 29 seconly
sdlc partner 4000.0910.0008 29
sdlc dlsw 29
The 2613 has an ethernet. The folks in Portland want to move off of the TR and on to Ethernet.
They will replace the IBM router with one that has both TR and ENET.
If we move to the ethernet, the result will be:
3745-TIC<->TR<->2210<->ENET<->2613(DLSw)<->WAN<->(DLSw)7507<->LIC-3745
Should I change the MTU size on the serial port to 1500 (Ethernet)?
Are there any changes that should occur on the 3745/Mainframe side?
Do you see any other issues?You cannot increase the MTU for ethernet larger than 1500 bytes because 802.3 (the standard for ethernet) does not allow that.
You may see issues. The problem is that both 3745 does not know the existance of the ethernet. If either 3745 sends a packet larger than 1500 bytes, the 2613 will drop the packet. (I am not an expert on 2210, I do not know if the 2210 is smart enough to segment the SNA packet into 2. I doubt it does, but please confirm it with IBM.) This causes the remote FEP detects a gap in SDLC, LLC2, or TH sequence number. No matter which layer detects the problem. The end result is still the same. The DLSw circuit will be disconnected.
There are several suggestions to your problem:
1. Make sure the both FEP will not send any PIU larger than 1500 bytes. This can be done either on the NCP gen or modtab. Checking the modtab is tough because your system programmers have to know all application running over the link. Then, they have to check the corresponding modtab entry for the applications.
2. run DLSw between 7507 to IBM 2210
3. directly connect the 2613 to the TIC (3745) -
I'm trying to do QLLC TO SDLC conversion for this setup:
Remote units using SDLC PADs to access a public x.25 network come to a x25 access in a Cisco router. From the router I have an SDLC connection to the Host.
It is working fine for one device, but I cannot make it working for 2 remote units at the same time. I cannot define more than 1 partner under the "qllc dlsw vmacaddr 0302.0302.10c1 3 partner 0303.0303.10c1". I know that I can use the subaddress field but this will not help as all the remote devices are calling the same addresses and there is no subaddress field.
Please advice,
Thanks,
Florin
version 11.2
service timestamps debug datetime
service timestamps log datetime
service password-encryption
no service udp-small-servers
no service tcp-small-servers
hostname QLLC_TEST
enable secret 5 <removed>
enable password 7 <removed>
no ip routing
source-bridge ring-group 999
dlsw local-peer
interface Serial0
no ip address
encapsulation x25
no ip route-cache
no ip mroute-cache
x25 address 99999999
x25 htc 5
x25 win 3
x25 wout 3
x25 ips 256
x25 ops 256
x25 map qllc 0302.0302.10c2 22222222 accept-reverse
x25 map qllc 0302.0302.10c3 33333333 accept-reverse
x25 map qllc 0302.0302.10c1 11111111 accept-reverse
qllc dlsw vmacaddr 0302.0302.10c1 3 partner 0303.0303.10c1
interface Serial1
no ip address
encapsulation sdlc
no ip route-cache
no ip mroute-cache
no keepalive
clockrate 2400
sdlc role secondary
sdlc vmac 0303.0303.1000
sdlc address C1
sdlc partner 0302.0302.10c1 C1
sdlc address C2
sdlc partner 0302.0302.10c2 C2
sdlc address C3
sdlc partner 0302.0302.10c3 C3
sdlc dlsw C1 C2 C3
interface TokenRing0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
ring-speed 16
no ip classless
logging buffered 80000 debugging
bridge 1 protocol dec
line con 0
password 7 <removed>
login
line aux 0
line vty 0 4
password 7 <removed>
login
end
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-IS-L), Version 11.2(15a)P, P RELEASE SOFTWARE (fc1
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Tue 25-Aug-98 00:28 by kpma
Image text-base: 0x03030170, data-base: 0x00001000
ROM: System Bootstrap, Version 11.0(10c)XB1, PLATFORM SPECIFIC RELEASE SOFTWARE
(fc1)
BOOTFLASH: 3000 Bootstrap Software (IGS-BOOT-R), Version 11.0(10c)XB1, PLATFORM
SPECIFIC RELEASE SOFTWARE (fc1)
QLLC_TEST uptime is 5 days, 8 hours, 1 minute
System restarted by power-on at 09:01:00 UTC Thu Jun 27 2002
System image file is "flash:c2500-is-l.112-15a.p", booted via flash
cisco 2525 (68030) processor (revision J) with 6144K/2048K bytes of memory.
Processor board ID 08868334, with hardware revision 00000000
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
5-in-1 module for Serial Interface 0
5-in-1 module for Serial Interface 1
32K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102I do not see any way you can do this without using subaddresses which will enable you to map to multiple partner mac addresses.
-
Vtam OSA---Router7200------telco circuit----------Adapter SDLC SNAServ
Hi, I have this situation: Vtam OSA---Router7200------telco circuit----------Adapter SDLC SNAServerCLEO----- Does Somebody have a sample of configuration to VTAM and to SNA Server? This is a cofiguration to the router 7200. But i don´t know if is correct.
interface Serial0/1/2
description PU 2.1
mtu 4400
no ip address
encapsulation sdlc
sdlc role primary
sdlc vmac 0200.4e00.9000
sdlc address C1
sdlc xid c1 05d61000
sdlc partner 2000.4000.5000 C1
sdlc saps C1 0C 0C
sdlc dlsw C1
Help me please.
Thank you in advance.
WmattaWimatta,
i think you can start here:
http://www.cisco.com/en/US/partner/tech/tk331/tk336/technologies_configuration_example09186a00801434cd.shtml
this is an example describing dlsw local switching between sdlc and ethernet. It has configuration examples for both pu2.0 and pu2.1.
Note:
Your example says in the description PU 2.1 but the configuration example you provided is for PU 2.0.
thanks...
Matthias -
Can't capture frame.
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 - -
Design question about SNASw, DLSW and VDLC
Hello,
I have a question about Ethernet redundancy in an APPN environment.
Let's have an example with 3 routers running SNASw that are on the SAME LAN (no vlans) as the Mainframe's OSA (one OSA only). APPN is configured on the Mainframe.
Using DLSw+, all downstream PUs are connected to the 3 routers. Can I define in the VDLC interface of each router the SAME MAC address, and this MAC address be the destination MAC of the downstream PUs?Hi,
yes, headend routers are the ones in front of the OSA/mainframe.
If you replace a tokenring with ethernet in the data center/headend, than the snasw dlsw solution is almost perfect for you. If you use hpr/ip to connect upstream to the host you are all set.
In that case you dont advertise any mac addresses on the local ethernet between the snasw/dlsw routers and the osa since it is hpr/ip. Basicaly ip routing only.
From the clients perspective, they dont really know that there is a change since you replicate the old tokenring mac address as vdlc mac address/snasw port and the end systems still connect to them like they did before.
In respect to dlsw ethernet redundancy we have to be a bit carefull not to mix the scenarios.
Dlsw ethernet redundancy is designed for the branch. Not the data center.
If you use dlsw ethernet redundancy with ethernet switches, and in almost all cases today ethernet means ethernet switches, you configure a mac address mapping between artificiall local mac addresses and your real remote mac address of the host.
On each router you configure a unique local mac address. Than you point half of your end systems dmac to the local mac address configured on router1 and the other half to the local mac address configured on router2. That way you achive load balancing.
The two routers exchange their mapping and in case router1 looses the connection to router2, router1 will activate the mapping it learned from router2 aswell and then take over those circuits additional.
If you decide that you configure on router1 the local mac address equal to the remote mac address, because you have a large number of clients and can not simply change the damc's on all of them, than you need to configure a "dummy" mapping on router2 and router1 will get all the circuits in this example. router2 would be purely for redundancy in case router1 goes down.
If you think about this than it is clear why dlsw ethernet redundancy is designed for the branch. In the branch we map local to remote mac addresses and the remote mac addresses are the hosts. Typically there are only a limited number of host mac addresses to map.
If you turn this around and put dlsw ethernet redundancy on the host end than you have to map all clients. If you have only one or two clients this is certainly doable. But if you have a large nuber of clients this is simply not manageable.
thanks...
Matthias -
Hi all,
I would like to connect a 3174 controller on my roouter as follows:
3174---[SDLC on serial]---RTR---[SNAsw using HPR/IP]---OSA on MVS.
i have 3 questions:
1/ the 3174 use LLC2. So do i use sdllc command instead of sdlc command ?
2/ do i implement sdlc/sdllc xid C1 <IDBLK_IDNUM>?
2/ my MVS engineer said me that EE do not understand that SNA over LLC2 using SNAsw from router?
If it is possible, what is the VTAM configuration...
Thanks for answersHi ,
thanks it works. Therefore, i got an error when i simulate a VTAM crash.
*** 00012660 - EXCEPTION 512:276 (0) ****
Abnormal UNBIND request received
Sense code = 0x08A00008
Local LU name = TEST.ROUTER
Partner LU name = TEST.MVSA
Mode name = CPSVRMGR
UNBIND RU :
32FE08A0 0008601A CA5F93F0 AEC67B90 11C6D9E2 C9C3F0F0 F14BC6D9 E2C9C3F0
F0C33519 08A00008 000011C6 D9E2C9C3 F0F0F14B C6D9E2C9 C3F0F0C3 0093F0AE
C67B9012 04C6D9E2 C9C3F0F0 F14BC6D9 E2C9C3F0 F0C30010 C6D9E2C9 C3F0F0F1
4BD5E2C7 F0E7F2F5 601ACA5F 93F0AEC6 7B9011C6 D9E2C9C3 F0F0F14B C6D9E2C9
C3F0F0C3 2B340101 32461980 1510C6D9 E2C9C3F0 F0F14BD5 E2C7F0E7 F2F52180
00000203 88801483 10C6D9E2 C9C3F0F0 F14BD5E2 C7F0E7F2 F5002C0A 0708E2D5
C1E2E5C3 D4C73246 19801510 C6D9E2C9 C3F0F0F1 4BD5E2C7 F0E7F2F5 21800000
02038880 148310C6 D9E2C9C3 F0F0F14B D5E2C7F0 E7F2F500 2C0A0708 E2D5C1E2
E5C3D4C7 33333A32 352E3233 3920474D 542B313A 20333130 37373320 3A204D55
203A202D 2D283029 202D3E20 48505228 32313030 30303029 20512031 300A2A4D
61722020 35203034 3A33333A 32352E32 33392047 4D542B31 3A203331 30373734
203A204D 55203A20 48505228 32313030 30303029 202D3E20 52545028 32384130
30303029 20512031 0A2A4D61 72202035 2030343A 33333A32 352E3233 3920474D
542B313A 20333130 37373520 3A204D55 203A202D 2D283029 202D3E20 52545028
32384130 30303029 20512031 0A2A4D61 72202035 2030343A 33333A32 352E3233
3920474D 542B313A 20333130 37373620 3A204E4C 50203A20 52545028 32384130
sh snasw pu
Number of DLUR PUs 1
SNA DLUR PUs
PU Name PU ID State DLUS Name
1> P00004 017A0006 Pend DACTPU rsp
*Mar 5 06:50:23.830 GMT+1: %SNASW-6-RTP_LOG_1: INFO - 12912 - RTP Connection has disconnected
The SNAsw router wait DACTPU command to desactivate the 3174 sessions. How can i parameters the DACTPU timeout on the SNAsw router to reset the 3174 status on SDLC links ?
regards
SIlvere -
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 -
Very newbie question: SNASW on Catalyst
Hi to all,
I've got a very basic question on snasw.
Can SNASW be implemented on a Catalyst 6500 in any way, for example using a particular model of supervisor engine?
Thanks.Hi Marco,
No, the SNASw feature is not available on any version of the Catalyst 6500. The reasoning is that SNASw is heavily process bound, the Catalyst 6500 is optimized for IP packet forwarding, and combining the two is too great a compromise. We suggest using a one armed router attached to the Catalyst 6500, so that the SNA processing is not in the direct path of the IP packet forwarding.
Rgds, Dan -
Hi all,
this is related to discussion:
http://forums.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Network%20Infrastructure&topic=LAN%2C%20Switching%20and%20Routing&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.1dd82da4
I opened this new one since my question was answered.
Our Topology:
Server---L2 switch---L3 Dist switch---Firewall---L3 switch(Core)--Firewall--CLOUD--IBM host
The server would generate both IP and SNA traffic (port LU6.2). All media are ethernet. The L3 switches are DLSw+ capable. I don't know much about the firewalls and I don't have control in the cloud because its under a different administrator.
Questions:
1. if I would use DLSw+, I need to bridge the ethernet port of the L3 Dist switch connecting the Server side. But, the server's connection is part of a VLAN, so, in the config of L3 Dist Switch, I would need to bridge the VLAN to DLSw. Would this setup impact the original behaviour of my VLAN? The VLAN is a Switched VLAN interface routed to another VLANs also.
2. Is it possible to control the port that would be used where the DLSW+ would pass through? I think I would have problems w/ our Firewall which requires source-destination ports and IPs to pass traffic.
Any suggestions/opinions are very much welcome... thanks!!!
rodneyHi,
if you are using vlan interfaces already than your configuration would look similar to this:
dlsw local-peer peer-id 10.10.10.1
dlsw remote-peer tcp 0 20.20.20.1
dlsw bridge-group 10
interface loopback 0
ip address 10.10.10.1 255.255.255.0
interface vlan 234
ip address ...
bridge-group 10
bridge 10 protocol vlan-bridge
that would allow you to bridge sna traffic into dlsw.
It assumes that 20.20.20.1 is the local peer configured on the partner router in front of the host.
The local peer tied to the loopback interface is just an example.
If you have i.e. more than one vlan you want to bridge than you can create multiple bridge-groups and you can configure multiple dlsw bridge-group statements. This way you bridge multiple vlans into dlsw but you dont bridge them together.
If you know the sap's you are using for sna, default is 4 as far as i know. Most commonly known are 4,8,12 than you can create an access list like this:
access-list 200 permit 0x0000 0x0d0d
and apply it to the bridge-group command on the interface.
interface vlan 234
bridge-group 10
bridge-group 10 input-sap-list 200
that allows only sap's 0,4,8,12 with and without the response bit set into the bridge group and effectively blocks all other traffic.
In respect to the tcp ports that dlsw is using over the WAN. Dlsw version 1, RFC1795, that is what cisco is using, opens always two tcp sessions at startup.
This router starts the connection, it opens a tcp connection on the destination port 2065, source port is a random port above 11000.
Now the receiving end is also opening a tcp session back to the first router. Destination port 2065, local, source port is a random port above 11000.
Next the dlsw capabilities exchange happens and the two peers exchange their information. Once they detected that they both are cisco devices and that they both support the usage of only one tcp session in both directions the one with the "numerically higher ip address" will drop its connection on the local tcp port 2065.
The remaining tcp connection is used for dlsw traffic in both directions.
this is described in detail in RFC1795, section 7.6.7.
thanks...
Matthias -
Hello all,
I am not familiar with SNASw and I would like to understand some things, in order to troubleshoot a problem we are facing.
We have two routers 7206 acting as SNA switches (A & B). Say that half of the remote branch routers perform dlsw peering to router A and the others to router B. (if A fails then connections are sent to B and vice versa).
Part of the configuration on router A is:
snasw port VDLSW vdlc 50 mac 400a.3746.2112 sap 0x08 conntype nohpr
snasw port VDLSW3 vdlc 50 mac 0042.0042.0042 conntype nohpr
snasw port VDLSW4 vdlc 50 mac 0042.0042.0000 conntype nohpr
Part of the configuration on router B is:
snasw port VDLSW vdlc 100 mac 400a.3746.2112 sap 0x08 conntype nohpr
snasw port VDLSW3 vdlc 100 mac 0042.0042.0000 conntype nohpr
snasw port VDLSW4 vdlc 100 mac 0042.0042.0042 conntype nohpr
It seems that when the application tries to connect to mac 0042.0042.0000 through router A, everything works fine. If it goes to router B, then it fails. Does the fact that the configuration for snasws ports isn't identical on both routers, have anything to do with it (namely VDLSW3 & VDLSW4)???? I suppose that there would be the same issue if anyone tried to connect to mac 0042.0042.0042 on router B, but I don't see any such connections taking place.
The configuration for snasw port VDLSW is identical on both routers and truly enough no-one has a problem with mac 400a.37746.2112.
I am sorry if I have not used the correct terminology to describe the problem, but my knowledge on SNASw is limited.
Any help would be highly appreciated.
Thank you in advance,
KaterinaThen the following is the basic steps to configure your TC for port mapping:
To setup port mapping on a Time Capsule (TC), either connect to the TC's wireless network or temporarily connect directly, using an Ethernet cable, to one of the LAN port of the TC, and then use the AirPort Utility, in Manual Setup, to make these settings:
1. Reserve a DHCP-provided IP address for the host device.
Internet > DHCP tab
o On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
o Description: <enter the desired description of the host device>
o Reserve address by: MAC Address
o Click Continue.
o MAC Address: <enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the host computer>
o IPv4 Address: <enter the desired IP address>
o Click Done.
2. Setup Port Mapping on the TC.
Advanced > Port Mapping tab
o Click the "+" (Add) button
o Service: <choose the appropriate service from the Service pop-up menu>
o Public UDP Port(s): <enter the appropriate UDP port values>
o Public TCP Port(s): <enter the appropriate TCP port values>
o Private IP Address: <enter the IP address of the host server>
o Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
o Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
o Click "Continue"
Maybe you are looking for
-
I have been trying to work out how to use email address lists in the past few months. I recently managed to import all my contacts from Windows Mail on the old PC. They are now in "Address Book", there were a few in "Personal Address Book" but most w
-
Re: Running servlets automatically.
this is the Continuation of my previous post Running servlets automatically. Hi everybody tnx for ur replies. I will explain my problem in detail here,so that somebody can suggest me an suitable solution. i need to update one table in DB for every si
-
Set the command "close" in an action to answer "no" to save changes. (CS5)
I am using a command now which I want to at the end of the command close the new file it opened. I tried recording the action and clicking 'no' while recording but this is not carried over into the action. How can I solve this?
-
I try to conect to the itune store but it said that i have an invalid addres
when connecting to the itune store keeps telling me that i have an invalid addres. what should i do?
-
Yosemite iSight not working on Macbook Pro
My early 2011 Macbook Pro 13" 's iSight stop working properly after upgrading to Yosemite. The facetime app is working properly but it only shows black. Same as photobooth. I only gets black photos with photobooth. Please advies.