Downloads |
Document ID: 12278
Contents
Introduction
Prerequisites
Requirements
Components Used
Conventions
Configure
Network Diagram
Configuration
Verify
Prior to Connection Being Established
After the connection is Established
Debug Captures During the STUN Activation
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information
Introduction
This document provides a sample configuration for Serial Tunnel (STUN) local. The relevant states in the show stun command output and the state changes in the debug stun event/packet command output are shown in the Configure section.
The beginning of the configuration displays the inoperable (INOP) state for the Front-End Processor (FEP) side of the multidrop STUN local connection. When displayed, the STUN state in the router does not reveal any Transmitted (Tx) or Received (Rx) packets, which is normal. After the line and the Physical Units (PUs) on the FEP side are activated for the controllers, Tx and Rx packet counters start to increment. At this point, STUN connections for both controllers are active.
Prerequisites
Requirements
There are no specific requirements for this document.
Components Used
The information in this document is based on the Cisco IOS® Software Release 12.0(8).
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Conventions
Refer to Cisco Technical Tips Conventions for more information on document conventions.
Configure
In this section, you are presented with the information to configure the features described in this document.
Note: Use the Command Lookup Tool ( registered customers only) to find more information on the commands used in this document.
Network Diagram
This document uses this network setup:
Configuration
This document uses this configuration:
|
STUN Local |
|---|
cloclo#show running-config Building configuration... Current configuration: ! version 12.0 no service pad service timestamps debug datetime msec service timestamps log datetime msec no service password-encryption ! hostname cloclo ! boot system flash rsp-aejsv-mz.120-8 logging buffered 64000 debugging no logging console enable password cisco ! microcode CIP flash slot0:cip27-3 microcode reload ip subnet-zero no ip domain-lookup ip cef ! ! stun peer-name 10.10.10.10 stun protocol-group 3 sdlc ! ! ! ! interface Loopback0 ip address 10.10.10.10 255.255.255.0 no ip directed-broadcast ! interface Serial0/0 no ip address no ip directed-broadcast encapsulation stun no ip mroute-cache clockrate 9600 stun group 3 stun route address 1 interface Serial0/1 direct stun route address 2 interface Serial0/2 direct ! interface Serial0/1 ip address 10.2.1.1 255.255.255.0 no ip directed-broadcast encapsulation stun no ip mroute-cache stun group 3 stun route address 1 interface Serial0/0 direct ! interface Serial0/2 no ip address no ip directed-broadcast encapsulation stun no ip mroute-cache clockrate 125000 stun group 3 stun route address 2 interface Serial0/0 direct ! interface Serial0/3 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Serial0/4 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Serial0/5 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Serial0/6 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Serial0/7 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Ethernet1/0 ip address 10.1.1.1 255.255.255.0 no ip directed-broadcast no ip mroute-cache shutdown ! interface Ethernet1/1 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Ethernet1/2 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! interface Ethernet1/3 no ip address no ip directed-broadcast no ip mroute-cache shutdown ! router eigrp 100 network 10.0.0.0 ! ip classless ! ! ! line con 0 exec-timeout 0 0 transport input none line aux 0 line vty 0 4 password cisco login ! end cloclo# |
Verify
Use this section to confirm that your configuration works properly.
The Output Interpreter Tool ( registered customers only) (OIT) supports certain show commands. Use the OIT to view an analysis of show command output.
-
debug —diagnoses and resolves internetworking problems
-
show —displays a variety of system diagnostic information
Prior to Connection Being Established
cloclo#show stun
This peer: 10.10.10.10
*Serial0/0 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
1 IF Serial0/1 direct 0 0 0
2 IF Serial0/2 direct 0 0 0
Serial0/1 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
1 IF Serial0/0 direct 0 0 0
Serial0/2 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
2 IF Serial0/0 direct 0 0 0
After the connection is Established
cloclo#show stun
This peer: 10.10.10.10
*Serial0/0 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
1 IF Serial0/1 direct 78 78 0
2 IF Serial0/2 direct 48 48 0
Serial0/1 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
1 IF Serial0/0 direct 81 81 0
Serial0/2 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
2 IF Serial0/0 direct 55 55 0
cloclo#
cloclo#
cloclo#show stun
This peer: 10.10.10.10
*Serial0/0 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
1 IF Serial0/1 direct 106 106 0
2 IF Serial0/2 direct 76 76 0
Serial0/1 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
1 IF Serial0/0 direct 107 107 0
Serial0/2 (group 3 [sdlc])
state rx_pkts tx_pkts drops poll
2 IF Serial0/0 direct 81 81 0
Debug Captures During the STUN Activation
cloclo#show log
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 174 messages logged
Trap logging: level informational, 36 message lines logged
Log Buffer (64000 bytes):
*Nov 3 14:20:32.415: %LINK-3-UPDOWN: Interface Serial0/0, changed state to up
*Nov 3 14:20:33.415: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Serial0/0, changed state to up
*Nov 3 14:20:39.587: STUN sdlc: 00:05:06 Serial0/0
SDI: (001/008) U: SNRM PF:1 00:05:06
*Nov 3 14:20:40.787: STUN sdlc: 00:00:01 Serial0/0
SDI: (001/008) U: SNRM PF:1
*Nov 3 14:20:40.787: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) U: UA PF:1
*Nov 3 14:20:40.807: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:000
*Nov 3 14:20:40.811: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) S: RR PF:1 NR:000
*Nov 3 14:20:40.987: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:000
*Nov 3 14:20:40.987: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) S: RR PF:1 NR:000
*Nov 3 14:20:41.019: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) I: PF:0 NR:000 NS:000
*Nov 3 14:20:41.187: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:000
*Nov 3 14:20:41.191: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) I: PF:1 NR:001 NS:000
*Nov 3 14:20:41.387: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:001
*Nov 3 14:20:41.387: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) S: RR PF:1 NR:001
*Nov 3 14:20:41.427: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) I: PF:0 NR:001 NS:001
*Nov 3 14:20:41.587: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:001
*Nov 3 14:20:41.591: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) I: PF:1 NR:002 NS:001
*Nov 3 14:20:41.787: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:002
*Nov 3 14:20:41.787: STUN sdlc: 00:00:00 Serial0/1
SDI: (001/008) S: RR PF:1 NR:002
*Nov 3 14:20:41.983: STUN sdlc: 00:00:00 Serial0/0
SDI: (001/008) S: RR PF:1 NR:002
Troubleshoot
There is currently no specific troubleshooting information available for this configuration.
NetPro Discussion Forums - Featured Conversations
| NetPro Discussion Forums - Featured Conversations for IBM |
| Network Infrastructure: Enterprise Data Centers |
Related Information
| Updated: Feb 28, 2007 | Document ID: 12278 |