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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

stun problem

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!

2 REPLIES
New Member

Re: stun problem

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

!

Bronze

Re: stun problem

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.

170
Views
0
Helpful
2
Replies