Re: AS/400 to Two 5494 controllers using STUN

tholmes · ‎11-23-2004

Hello,

I've configured STUN between an AS/400 and 2 x 5494 controllers across a serial link using two 2621 routers

I've pretty much copied the configuration from the example web site which shows this exactly as we have it

http://www.cisco.com/en/US/partner/tech/tk827/tk369/technologies_tech_note09186a00800b451e.shtml

The IBM engineer is saying the RTS lines never drop so he is not able to activate either controller.

Can you give the config a quick look and possibly tell me where I'm going wrong please

Many thanks

Tony

hostname Site_A

stun peer-name 172.16.1.1

stun protocol-group 1 sdlc

stun remote-peer-keepalive 10

!

interface Loopback0

ip address 172.16.1.1 255.255.255.0

!

interface Serial0/0

description *** Kink to Site B ***

bandwidth 960000

ip address 192.168.200.2 255.255.255.252

priority-group 1

!

interface Serial0/1

description *** Link to AS/400 ***

no ip address

encapsulation stun

idle-character marks

nrzi-encoding

clockrate 19200

stun group 1

stun sdlc-role secondary

sdlc K 1

sdlc address 01

sdlc address 02

stun route address 1 tcp 172.16.2.1 local-ack

stun route address 2 tcp 172.16.2.1 local-ack

ip route 0.0.0.0 0.0.0.0 192.168.0.1

!

priority-list 1 protocol stun high

priority-list 1 protocol ip medium tcp 1990

priority-list 1 protocol ip normal tcp 1991

priority-list 1 protocol ip low tcp 1992

priority-list 1 protocol stun high address 1 1

priority-list 1 protocol stun high address 1 2

!

-------------------------------------

hostname Site_B

!

stun peer-name 172.16.2.1

stun protocol-group 1 sdlc

stun remote-peer-keepalive 10

!

interface Loopback0

ip address 172.16.2.1 255.255.255.0

!

interface Serial0/0

description *** Serial Link to Site A ***

bandwidth 960000

ip address 192.168.200.1 255.255.255.252

no ip route-cache

no ip mroute-cache

priority-group 1

!

interface Serial0/1

description Serial Link to 5494 Controller 01

no ip address

encapsulation stun

no ip route-cache

no ip mroute-cache

nrzi-encoding

clockrate 19200

stun group 1

stun sdlc-role primary

sdlc address 01

stun route address 1 tcp 172.16.1.1

!

interface Serial0/2

description Serial Link to 5494 Controller 02

no ip address

encapsulation stun

no ip route-cache

no ip mroute-cache

nrzi-encoding

clockrate 19200

stun group 1

stun sdlc-role primary

sdlc address 02

stun route address 2 tcp 172.16.1.1

!

ip route 0.0.0.0 0.0.0.0 192.168.200.2

priority-list 1 protocol stun high address 1 1

priority-list 1 protocol stun high address 1 2

!

mbinzer · ‎11-23-2004

Hi,

not sure but my best guess would be that it makes not much sense to have local-ack on routera but not on routerb. Either on both or on none.

thanks...

Matthias

tholmes · ‎11-23-2004

Thanks Matthias, I think it's a locally significate configuration, might be worth looking at

Regards Tony

tblancha · ‎11-23-2004

No, it is not only locally significant. It is either local-ack or not per stun group on both sides

jihicks · ‎11-23-2004

Hi Tony,

The first thing is that this line has clock rate configured, which must mean it is DCE ( has a DCE cable attached ). This means RTS comes from the AS/400 and not the router. CTS would come from the router. If you want this to work as half duplex, add half-duplex to the serial interface configuration. Also, you should add the global command, "stun quick-response" on the AS/400 side router only. Local-ack is by STUN group, all of none. "Stun quick-response" is only valid with local-ack. It prevents the AS/400 from taking the line down if one of the remote controllers is down. This allows the other to stay up. The router will respond with DM for the controller that is down.

Best regards,

Jim