topic Re: stun problem in Server Networking

stun problem

c.chunxia — Thu, 11 Apr 2002 00:45:02 GMT

I have a connection like this:

pu 2.0---r1--r---r----r------r2----390

r1#sh stun

This peer: 10.1.1.2

*Serial6/1 (group 1 [sdlc])

state rx_pkts tx_pkts drops poll

C8 TCP 10.1.2.1 close * 6752 4023 0

SDLC Local Acknowledgement:

*Serial6/1 (group 1 [sdlc])

slack_state conn disc iframe_s iframe_r

C8 TCP 10.1.2.1 disconnect 11 10 668 754

r1#ping 10.1.2.1

Success rate is 100 percent (5/5), round-trip min/avg/max = 128/130/132 ms

I don't know why my pu is down even if ip connection is correct.(There is none operation on 390 and pu2.0)

thank you!

Re: stun problem

c.chunxia — Thu, 11 Apr 2002 00:49:54 GMT

r1 configuration is:

stun peer-name 10.1.1.2

stun protocol-group 1 sdlc

stun remote-peer-keepalive

interface Serial6/1

no ip address

encapsulation stun

nrzi-encoding

clockrate 64000

stun group 1

stun sdlc-role primary

sdlc address C8

stun route address C8 tcp 10.1.2.1 local-ack

Re: stun problem

rsissons — Thu, 11 Apr 2002 00:56:12 GMT

You need to have traffic on the connection before the STUN peer will come up so the mainframe side will have to initiate the connection. A 'debug stun pac' at the mainframe end will tell you if the mainframe is currently trying to activate the PU.