Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

DLSw local and remote on the same router

Does Cisco support DLSw local and remote on the same router ?

Following is the sample scenario:

AS/400-LAN--R1(with S0)---IP coud---R2--Serial--5494

R1 should establish DLSw peer with R2.

R1 should also establish local DLSw session with its S0 (SDLC) link simultaneoulsy.

2 ACCEPTED SOLUTIONS

Accepted Solutions
Cisco Employee

Re: DLSw local and remote on the same router

Hi,

I assume that both serial links in your topology are sdlc links.

In that case the configuration of the sdlc interface on R1 follows the same guidelines than the one on R2. dlsw does local switching between sdlc interfaces and either ethernet/tokenring lans, aswell as remote switching between sdlc and tokenring or ethernet lans.

Configuration examples are on cco. Just search for

"dlsw local switching" and you find numerous links.

a starting point could be here:

http://www.cisco.com/en/US/partner/tech/tk331/tk336/tech_configuration_examples_list.html

In short what you need to do:

dlsw local-peer peer-id a.b.c.d

dlsw remote-peer 0 tcp d.e.f.g

dlsw bridge-group x

( if you configure a pure local switching router, lan and sdlc interfaces on the same router, all you need is "dlsw local-peer" )

int ser x

encapsulation sdlc

sdlc role secondary ( assuming a pu2.0)

sdlc address c1

sdlc vmac 0000.1111.1100 ( the router inserts the sdlc address in the last two digits to allow for multidrop configurations. the vmac + sdlc address,

in this case 0000.1111.11C1 is the mac address for this connection on the lan end of your connection.)

sdlc xid C1

sdlc partner 0000.1234.5678 C1 (partner is the mac address of the lan attached AS/400 in your case. You need to be carefull if you have the AS/400 on ethernet. In that case you need to configure the partner address bitswapped since dlsw sees all addresses in tokenring format.)

sdlsw dlsw c1 (this ties the sdlc address c1 and its configuration into dlsw.)

interface ethernet y

bridge-group x

bridge x protocol ieee

this configuration is the same for the sdlc interface local on R1 and remote on R2. DLSw will find the correct connection based on the uniqueness of the mac addresses choosen. In dlsw a dlsw circuit is uniquely identified by dmac/smac/dsap/ssap.

If you do this for a pu2.1 you need to alter the configuration a little bit but there are multiple examples out on www.cisco.com.

thanks...

Matthias

Cisco Employee

Re: DLSw local and remote on the same router

hi,

if your controler needs connections to different as/400's than you need to define multiple sdlc addresses on your sdlc line and configure the router for sdlc multidrop. you can have multiple connections up and running even at the same time to different as/400's. I.e. one local-switched on the same router and one to an as/400 behind a dlsw remote peer.

On the sdlc line every connection is a separate sdlc address. If you configure multiple sdlc addresses the router makes unique mac addresses out of it by using the configured vmac address and inserting the sdlc address in the last two digits. Also you configure a sdlc partner mac address per sdlc address. The partner is always the as/400 you want to talk to.

In regards to the dlsw peers you just must make sure that you have a dlsw peer connected when the as/400 you want to talk to is remote. It doesnt matter if you define it as a backup peer, in that case you only use it as pure backup in case the main peer goes down, or if you have two peers up all the time.

If you want to only allow the connection to the local as/400 in case the remote one is down than you might have to do some manual activation of the sdlc config on the as/400.

Dlsw has no mechanism to do the local switching only in case the remote device is not reachable.

thanks...

Matthias

5 REPLIES
Cisco Employee

Re: DLSw local and remote on the same router

Hi,

I assume that both serial links in your topology are sdlc links.

In that case the configuration of the sdlc interface on R1 follows the same guidelines than the one on R2. dlsw does local switching between sdlc interfaces and either ethernet/tokenring lans, aswell as remote switching between sdlc and tokenring or ethernet lans.

Configuration examples are on cco. Just search for

"dlsw local switching" and you find numerous links.

a starting point could be here:

http://www.cisco.com/en/US/partner/tech/tk331/tk336/tech_configuration_examples_list.html

In short what you need to do:

dlsw local-peer peer-id a.b.c.d

dlsw remote-peer 0 tcp d.e.f.g

dlsw bridge-group x

( if you configure a pure local switching router, lan and sdlc interfaces on the same router, all you need is "dlsw local-peer" )

int ser x

encapsulation sdlc

sdlc role secondary ( assuming a pu2.0)

sdlc address c1

sdlc vmac 0000.1111.1100 ( the router inserts the sdlc address in the last two digits to allow for multidrop configurations. the vmac + sdlc address,

in this case 0000.1111.11C1 is the mac address for this connection on the lan end of your connection.)

sdlc xid C1

sdlc partner 0000.1234.5678 C1 (partner is the mac address of the lan attached AS/400 in your case. You need to be carefull if you have the AS/400 on ethernet. In that case you need to configure the partner address bitswapped since dlsw sees all addresses in tokenring format.)

sdlsw dlsw c1 (this ties the sdlc address c1 and its configuration into dlsw.)

interface ethernet y

bridge-group x

bridge x protocol ieee

this configuration is the same for the sdlc interface local on R1 and remote on R2. DLSw will find the correct connection based on the uniqueness of the mac addresses choosen. In dlsw a dlsw circuit is uniquely identified by dmac/smac/dsap/ssap.

If you do this for a pu2.1 you need to alter the configuration a little bit but there are multiple examples out on www.cisco.com.

thanks...

Matthias

New Member

Re: DLSw local and remote on the same router

Hi,

Many thanks for the very clear answer !

In fact, I am having remote DLSw switching working fine at the moment. I just wanted to add "local switching" to the same setup.

Thanks again !

Cisco Employee

Re: DLSw local and remote on the same router

Hi,

when you test the newly added local switched sdlc connection make sure you do a

show dlsw local-circuit

you will not see this connection in the

show dlsw circuit

Besides that the debugging and troubleshooting is almost the same.

Matthias

New Member

Re: DLSw local and remote on the same router

I need just one more help.

I am trying to schieve following;

as400(backup)-R1(DLSw local)-WAN- R2-as400(main)

|

|

R3 ( DLSw remote)

R3 will connect with R2 for main connection and R1 for backup connection as follwos;

"dlsw remote peer R1

dlsw remote peer R2 backup peer R1"

But there is a controller attahced to R1 and it should connect with R2 as main peer ( remote DLSw switching).

For backup scenario, it should also be attahced to as400 backup machine (DLSw local switching).

( hope that the above scenario is clear)

Is there any way to achieve this?

Cisco Employee

Re: DLSw local and remote on the same router

hi,

if your controler needs connections to different as/400's than you need to define multiple sdlc addresses on your sdlc line and configure the router for sdlc multidrop. you can have multiple connections up and running even at the same time to different as/400's. I.e. one local-switched on the same router and one to an as/400 behind a dlsw remote peer.

On the sdlc line every connection is a separate sdlc address. If you configure multiple sdlc addresses the router makes unique mac addresses out of it by using the configured vmac address and inserting the sdlc address in the last two digits. Also you configure a sdlc partner mac address per sdlc address. The partner is always the as/400 you want to talk to.

In regards to the dlsw peers you just must make sure that you have a dlsw peer connected when the as/400 you want to talk to is remote. It doesnt matter if you define it as a backup peer, in that case you only use it as pure backup in case the main peer goes down, or if you have two peers up all the time.

If you want to only allow the connection to the local as/400 in case the remote one is down than you might have to do some manual activation of the sdlc config on the as/400.

Dlsw has no mechanism to do the local switching only in case the remote device is not reachable.

thanks...

Matthias

306
Views
0
Helpful
5
Replies
CreatePlease to create content