Troubleshooting tools
Troubleshooting for TCP/IP connections
Troubleshooting encountered problems with serial port connection
Troubleshooting for phone dialing connections
Troubleshooting for frame relay connections
Troubleshooting for X.25 connection
Troubleshooting to connect to IBM host
------------------------------------------------------------
Troubleshooting tools
There are many types of Troubleshooting tools, which can be used to use router diagnostic commands, Cisco Network Management Tools (CiscoWorks) and Procedure Analyzer, etc. Below we mainly introduce router diagnostic commands.
There are four types of router diagnostic commands:
Use the show command
Use the debug command
Use the ping command
Use the trace command
Use the show command
Show is a very useful tool for monitoring commands and solving system problems. Here are a few commonly used show commands:
show interface----Show interface statistics.
Some commonly used show interface commands:
show interface ethernet
show interface tokenring
show interface serial
show controllers---Show interface card controller statistics.
Some commonly used show controllers commands:
show controllers cxbus
show controllers e1
show running-config---Show the configuration currently running by the router.
show startup-config---Show NVRAM configuration exists.
show flash---Flash memory content.
show buffers---Show buffer pools statistics in the router.
show memory---Statistics of the router's memory usage, including idle pool statistics.
show processes---Router activity process information.
show version---Show system hardware, software version, configuration files and startup system images.
Use the debug command
The debug command in superuser mode can provide port transmission information, error messages generated by nodes, diagnostic protocol packages and other useful troubleshooting data.
Note: When using the debug command, be careful, it will occupy system resources and cause some unpredictable phenomena. Please use the no debug all command to terminate the use of the debug command.
The Debug command is displayed on the console port by default. You can use the log buffer command to direct the output to buffers. If it is telnet, you can use Router#terminal monitor to monitor the console information.
Use the ping command
Ping confirms network connectivity.
Use the trace command
Trace command tracks router packet transmission.
------------------------------------------------------------
Troubleshooting for TCP/IP connections
Phenomenon: The Ethernet port from the host to the local router is not connected
Suggestion: We can regard the Ethernet port of the router as an Ethernet card of an ordinary host, which has become a LAN connection problem.
Use the show interface ethernet number command
Router#show interface ethernet 0
Ethernet is up,line protocol is down
If Ethernet is down, please connect the cable (coaxial cable or twisted pair). If it has been connected and the ethernet is still down, please contact your agent.
If Ethernet is admsinstratively down.
Router#conf t
Router(config)#interface ethernet 0
Router(config-if)#no shutdown
Router(config-if)#^Z
Router#
If Ethernet is up, and line protocol is down.
The host 10M network card is connected to the Ethernet port of the router 100M, and it is not adaptive (current version). Otherwise, there is no problem.
If it is a coaxial cable, please check whether the cable, T-head, terminal, and whether it is connected correctly.
If it is a twisted pair, please check whether the cable is correct and whether it is connected through HUB in the middle. If it is directly connected to the host, use a cross wire.
If it is a 100BaseTX interface, it is necessary to use five-class twisted pair cables.
If an interface provides two physical media, such as thick cable AUI and UTPRJ45, the default is AUI. To use RJ45, it is required:
Router#conf t
Router(config)#interface ethernet 0
Router(config-if)#media-type 10baset
Router(config-if)#^Z
[1][2] [3] [4] [5] [6] [7] [8] [9] [10] Next page
Article entry: csh Editor in charge: csh
Router#
If Ethernet is up, line protocol is up; but the ping cannot be done.
Please check the IP address of the router's Ethernet port and whether it is on the same network segment as the host's IP address.
After the above steps, the problem has not been resolved. Please contact your agent.
Phenomenon: The host does not connect to the other router's WAN or Ethernet port.
Suggestion: Assume that the Ethernet port from the host to the local router is already open.
Check whether the two WAN ports are connected on the router. If they are not connected, please see the troubleshooting of WAN below.
If the router has two wide area network ports connected.
Use the "netstat -rn" command to find routes on the host. If not, please use "route add" to join.
Take SCO UNIX as an example:
#netstat -rn
#route add Destination segment mask gateway 1
or
#vi /etc/gateways
net destination network segment gateway local router Ethernet address metric 1 passive
If there is a default gateway on the host, check the router routing protocol configuration.
Router#show ip route
Router#show running-config
.
.
.
router eigrp 1
network ...
network ...
Whether the routing protocols of the routers on both ends are consistent, and whether they are in an autonomous system. Is the network segment added by "network" correct?
Phenomenon: The host does not work to the other party's destination host.
Suggestion: Follow the steps below to solve it.
Check the Ethernet port from the host to the local router.
Check the two WAN ports.
Check the host to the other router's WAN port.
Check the host to the Ethernet port of the other router.
Use the telnet command to remotely log in to the other party's router, and check the other party's LAN connection by checking the Ethernet port of the local host to the local router.
Repeat 3 and 4 to check the other party’s local situation.
After the above steps, the problem has not been resolved. Please contact your agent.
------------------------------------------------------------
Troubleshooting encountered problems with serial port connection
Phenomenon: When connecting the dedicated line, the two wide-area network ports directly connected to the router are blocked.
Suggestion: We can divide the two routers' WAN ports into three sections, as shown in the figure:
Router A--1--MODEMA---2--MODEMB--3--Router B
Our task is to check which section is not working and solve it.
Use the show interface serial number command
If Serial is down, it means that there is no carrier signal CD between the router and the local MODEM.
Connect the serial port and MODEM and turn on MODEM. Check whether the MODEM sending light TD is on. The TD light is on, which means that the router has a signal sent to the light. If it doesn't light, please check the MODEM, cable (preferably equipped with Cisco) and port. You can use another serial port and try it.
If Serial is up, but line protocol is down. There are several possibilities:
a. The local router is not configured.
b. The remote router is not turned on or is not configured.
Both ends of the router need to configure the same protocol packaging method. For example: Router A packages HDLC and Router B packages PPP, then the line protocol of the two routers is always down. Change the packaging method:
Router#conf t
Router(config)#interface serial 0
Router(config-if)#encapsulation ppp
Router(config-if)#^Z
Router#
c. If you use Newbridge's 26XX and 27XX DTU devices, it does not send CD signals, please set them on the router:
Router#configure terminal
Router(config)#int serial 0
Router(config-if)#ignored-dcd
Router(config-if)#^Z
Router#
If there is no connection between the two, the dedicated line will not be connected.
Solution: Use a test loop. Ask the Telecommunications Bureau to help determine which section of the line is the specific problem. If the loop is successful, the line protocol will become up(looped).
If Serial is up, but line protocol is up(looped).
Use show running-config to see if the port has loopback configuration, and if it is deleted.
Whether MODEM has undergone a loop test.
Whether the dedicated line has undergone a loop test.
If Serial is admsinstratively down, line protocol is down.
Router#conf t
Router(config)#interface serial 0
Router(config-if)#no shutdown
Router(config-if)#^Z
Router#
------------------------------------------------------------
Troubleshooting for phone dialing connections
To solve the problem of connecting with a dial-up network using a telephone, the first thing to do is:
Make sure that the router is connected to the MODEM
Understand the meaning of show line output
Make sure that the router is connected to the MODEM
We use the reverse Telnet Session to MODEM on the router to determine the connection between the router and MODEM. That is to say, you can use AT instructions to configure it by reverse logging into MODEM. The specific steps are as follows:
Previous page [1][2][3] [4] [5] [6] [7] [8] [9] [10] Next page
Article entry: csh Editor in charge: csh
On the router console, use commands
telnet ip-address 20yy
where ip-address is the address of an active port, and yy is the line connecting to MODEM. For example, the following example is to connect to the auxiliary port using the IP address 192.169.53.52:
telnet 192.169.53.52 2001
If the connection is denied, there may be other users connecting to the port. Use the show users EXEC command to decide whether it is occupied. If so, clear line to clear it; if not, try anti-Telnet again.
If the connection is still rejected, confirm that the MODEM control modem inout.
Make sure that the router txspeed and rxspeed are consistent with the MODEM settings.
After the anti-Telnet login is successful, the AT command confirms that the answer is OK.
Understand the meaning of show line output
Show line line-number EXEC is a very useful trobbleshooting command.
Phenomenon: There is no connection between MODEM and the router. There is no response when trying to log in or the user receives the "Connection Refused by Foreign Host" message.
suggestion:
Use show line to see if the MODEM column is "inout". If not, on the router:
Router#conf t
Router(config)#line aux 0
Router(config-line)#modem inout
Router(config-line)#^Z
Router#
Determine the correct cable.
For hardware issues, please contact your agent.
Phenomenon: MODEM does not dial.
Suggestion: MODEM does not dial, and the possibility of removing hardware and cables is:
Packages that are not interested. Use show running-config to check the router configuration, whether the dialer-list segment is set to the packet you want to transmit. If so, please reconfigure the access-list table.
Chat script configuration error. Open debug information.
Router#debug dialer
%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0, changed state to down
%LINK-3-UPDOWN: Interface Serial0, changed state to down
%LINK-3-UPDOWN: Interface Async1, changed state to down
Async1: re-enable timeout
Async1: sending broadcast to default destination get_free_dialer: faking it
Async1: Dialing cause: Async1: ip PERMIT
Async1:No holdq created - not configured
Async1: Attempting to dial 8292
CHAT1: Attempting async line dialer script
CHAT1: Dialing using Modem script: backup & System script: none -- failed, not connected
CHAT1: process started
CHAT1: Asserting DTR
CHAT1: Chat script backup started
CHAT1: Expecting string:
Async1: sending broadcast to default destination -- failed, not connected
CHAT1: Timeout expecting:
CHAT1: Chat script backup finished, status = Connection timed out; remote host not responding
Async1: disconnecting call
......
------------------------------------------------------------
Troubleshooting for frame relay connections
Use show interface serial to check whether the interface and line protocol are up. Make sure the connected cable is correct.
If the interface is up, but the line protocol is down. Use show frame-relay lmi to view the LMI type of frame relay.
Use show frame-relay map to view the packaging type.
Use show frame-relay pvc to view PVC.
Open debug information.
------------------------------------------------------------
Troubleshooting for X.25 connection
Confirm that the two X.25 ports are connected.
MODEM status: If the line is connected, the CD and RD lights of MODEM should be on, indicating that data is sent by the X.25 switch.
We can also use the pad local or the other party's X.121 address. If the pad can pass, it means that the link layer of the X.25 network has been opened.
Router#pad 28050103 (the other party’s X.121 address)
Use the show interface serial command. If serial is down, line protocol is down, please check the connection cable between the router and the MODEM, and change to another serial port and try again.
Previous page [1] [2][3][4] [5] [6] [7] [8] [9] [10] Next page
Article entry: csh Editor in charge: csh
If serial is up, but line protocol is down, please contact the telecommunications bureau to check whether the LAPB parameters match.
If serial is up, line protocol is up. However, the pinging of the other party's WAN port is not connected.
Use show running-config to check whether the x25 map ip setting is made on the serial port.
In the X.25 setting, whether the maximum virtual circuit value exceeds the applied value.
If the other party is not connecting to a router, but an X.25 network card (taking Bodha Card as an example)
environment:
Knowledge: On the Boda X.25 card
#cd /etc/x.25
#vi (Network card parameter setting file)
LOCADDR 28050103 (local X.25 port X.121 address)
VC 16
IVC 0 (number of incoming VCs)
OVC 0 (number of call out VC)
PVC 0 (permanent VC number)
X25TIMEOUT 60 (chain breaking time)
Therefore, SVC=VC-IVC-OVC-PVC.
#x25reset (restart the X.25 network card)
#x25link (monitoring current status information)
#vi (The address corresponds to the file, the IP layer can communicate with each other, and the X.121 address must be corresponding to the IP address)
130.132.128.4 28050104 SVC 0
130.132.128.3 28050103 SVC 0
#cd /etc
#vi tcp plus
ifconfig x25 130.132.128.3 -arp network 255.255.0.0
Generally, when there is a problem with X.25 connection, the mapping between the IP address of one party and the X.121 address is not set.
------------------------------------------------------------
Troubleshooting to connect to IBM host
DLSw+ Troubleshooting
STUN Troubleshooting
CIP Troubleshooting
DLSw+ Troubleshooting
When using DLSw+ to connect between PU2.0/2.1 and IBM mainframe through the router, we need to use the show dlsw and show interface serial commands to solve the problems that arise.
First check whether the two peers defined by DLSw+ are connected
Router#show dlsw peers
Peers: state pkts-rx pkts-tx type drops ckts TCP uptime
TCP 17.18.15.1 CONNECT 16080 8400 conf 0 0 0 00.03.27
TCP 1.1.12.1 DISCONN 0 0 conf 0 0 0 00.00.00
Peers --- The peer peers IP address corresponding to the "dlsw remote-peer" definition.
state --- represents the connection status with peer peers.
Where: CONNECT means that peer peers have been established.
CAP_EXG indicates that performance information is exchanged with remote peers.
WAIT_RD is the last step in establishing a peer connection, waiting for the remote peer response information.
DISCONN means that no connection is established with peer peers. Please refer to TCP/IP Troubleshooting to check for TCP connection failures.
WAN_BUSY means that the TCP transmission queue is full and data cannot be transmitted.
If the peer peers have established a connection, please check the performance exchange information.
Router#show dlsw capabilities
DLSw: Capabilities for peer 172.18.15.166
vendor id (OUI) : '00C' (cisco)
version number : 1
release number : 0
init pacing window : 20
unsupported saps : none
num of tcp sessions :1
loop prevent support : no
icanreach mac-exclusive : no
icanreach netbios-excl. : no
reachable mac addresses : none
reachable netbios names : none
cisco version number : 1
peer group number : 0
border peer capable : no
peer cost : 3
biu-segment configured : no
local-ack configured: yes
priority configured: no
version string :
Cisco Internetwork Operating System Software
IOS (tm) GS Software (GS7-K-M), Experimental Version 11.1(10956) [sbales 139]
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Thu 30-May-96 09:12 by sbales8
After exchanging performance information, you need to find the destination MAC address, which shows the MAC addresses (local and remote) that all routers can reach
Router#show dlsw reachability
DLSw MAC address reachability cache list
Mac Addr status Loc. peer/port rif
Previous page [1] [2] [3][4][5] [6] [7] [8] [9] [10] Next page
Article entry: csh Editor in charge: csh
0000.810f.6500 FOUND LOCAL TBridge-001 --no rif--
0006.e918.7b70 FOUND LOCAL TBridge-001 --no rif--
1000.5ae3.03f7 FOUND LOCAL TBridge-001 --no rif--
7500.9221.0000 FOUND REMOTE 16.201.30.250(2065) max-lf(4472)
7500.9221.0000 SEARCHING LOCAL
DLSw NetBIOS Name reachability cache list
NetBIOS Name status Loc. peer/port rif
SXUSER2 FOUND LOCAL TBridge-001 --no rif--
If the local MAC address and destination MAC address status are both FOUND, please refer to step 5.
SEARCHING means that you are looking for the local MAC address or destination MAC address. At this time, use the show interface serial command to view the PU status of the connection of the port.
NOT_FOUND indicates that no response to the PU poll was received.
VERIFY means confirming the information in the cache.
In SERACHING the local MAC address or the destination MAC address.
Router#show interface serial 0
Serial1 is up, line protocol is up
Hardware is HD64570
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC, loopback not set
Router link station role: SECONDARY (DTE)
Router link station metrics:
group poll not enabled
poll-wait 40000 seconds
N1 (max frame size) 12016 bits
modulo 8
sdlc vmac: 4000.5555.00--
sdlc addr C1 state is DISCONNECT
cls_state is CLS_STN_CLOSED
VS 0, VR 0, Remote VR 0, Current retransmit count 0
Hold queue: 0/200 IFRAMEs 0/0
TESTs 0/0 XIDs 0/0, DMs 0/0 FRMRs 0/0
RNRs 0/0 SNRMs 0/0 DISC/RDs 0/0 REJs 0/0 chain: C1/C1
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 19 interface resets
0 output buffer failures, 0 output buffers swapped out
6 carrier transitions
DCD=up DSR=up DTR=up RTS=up CTS=up
illustrate:
Encapsulation SDLC---The serial port packaging method is SDLC.
Router link station role: SECONDARY (DTE)---The current port is secondary, set by the "sdlc role" command.
sdlc vmac: 4000.5555.00-- --- The MAC address set by "sdlc vmac". Note that its last two digits are left for the PU address.
In this example, the port MAC address is 4000.5555.00C1.
sdlc addr C1 state is DISCONNECT ---This port connects to the current state of PU C1. There are the following states:
DISCONNECT - The secondary station does not send TEST or XID frame requests to establish a connection. Please check whether the connected PU is started below.
SNA process, if you are connecting the PU with a DCE cable, please check whether the cable is correct. If MODEM is connected to the remote PU, please
Check the MODEM status light.
DISCSENT-The router sends a disconnect request (DISC) to the secondary station and is waiting for the secondary station to answer.
SNRMSENT - The router sends a connection request (SNRM) to the secondary station and is waiting for the secondary station to answer. This status appears in the router as the primary station
If the SNRMSENT status appears on the router as the main station, check whether the lower PU is turned on, the router port and PU
Is the MODEM connected to the SDLC port connected to the MODEM connected to the DTR, CD, RXD, and TXD lights should always be on). In a word, SNRMSENT appears
The status is a problem between the router port and its lower PU.
The CONNECT-PU connection is normal. The router and the secondary station it connects to is normally connected.
THEMBUSY-PU sends RNR frames. The secondary station tells the router that it cannot receive any information for the time being.
Previous page [1] [2] [3] [4][5][6] [7] [8] [9] [10] Next page
Article entry: csh Editor in charge: csh
USBUSY - The router sends RNR frames. The router tells the secondary station that it cannot receive any information for the time being. The router has received the secondary station's SNRM frames.
Acknowledge frame UA, attempting to establish an SDLC or LLC2 session.
BOTHBUSY - Both parties send RNR frames. Tell the other party that they cannot receive any information for the time being.
ERROR - Violates SDLC protocol. The router is waiting for the secondary station to answer.
SNRMSEEN-The router acts as a secondary station and receives SNRM frames.
When both parties find the MAC addresses, the link is established.
Router#show dlsw curcuit
Index local addr(lsap) remote addr(dsap) state
1818740 1000.5ae3.430d(04) 4000.5555.00c1(04) CONNECTED
Use "show interface serial" to view the PU status should be "CONNECT".
We can also use "debug dlsw" to get more information to help solve problems in the network. You can record the debug transmission information provided to your agent.
Problem: The remote end does not reach the local machine. The IP address of the remote peer is 172.18.16.156.
suggestion:
Check the show dlsw peer output and we see:
Peers: state pkts-rx pkts-tx type drops ckts TCP uptime
TCP 172.18.16.156 DISCONN 0 0 conf 0 0 0 --
Use the debug dlsw peers command to decide on the problem:
DLSw: action_a() attempting to connect peer 172.18.15.156(2065)
DLSw: action_a(): Write pipe opened for peer 172.18.15.156(2065)
DLSw: peer 172.18.15.156(2065), old state DISCONN, new state WAIT_RD
DLSw: dlsw_tcpd_fini() for peer 172.18.15.156(2065)
DLSw: tcp fini closing connection for peer 172.18.15.156(2065)
DLSw: action_d(): for peer 172.18.15.156(2065)
DLSw: peer 172.18.15.156(2065), old state WAIT_RD, new state DISCONN
DLSw: Not promiscuous - Rej conn from 172.18.15.166(2065)
Diagnosis: Try to open peer 172.18.15.156, but it was unsuccessful. DLSw+ received an open request from 172.18.15.166, but DLSw+ rejected it because this peer is not defined. From this we can judge that the definition peer address is incorrect. The peer address is 172.18.15.166 and it is connected.
Peers: state pkts-rx pkts-tx type drops ckts TCP uptime
TCP 172.18.16.166 CONNECT 2 2 conf 0 0 0 00:224:27
Problem: The SDLC device cannot connect to the host. Milan is the remote peer connecting to the SDLC device.
suggestion:
Use the show dlsw peer command to show that peer is up.
milan#sh dlsw peers
Peers: state pkts-rx pkts-tx type drops ckts TCP uptime
TCP 172.18.16.166 CONNECT 2 2 conf 0 0 0 00:224:27
Show dlsw circuits have no link generation.
milan#show dlsw circuits
milan#
The Show interface command shows that the SDLC address status is USBUSY, which means that we have successfully connected to the lower router.
Router#show interface serial 3/7
Serial1 is up, line protocol is up
Hardware is HD64570
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation SDLC, loopback not set
Router link station role: SECONDARY (DTE)
Router link station metrics:
group poll not enabled
poll-wait 40000 seconds
N1 (max frame size) 12016 bits
modulo 8
sdlc vmac: 4000.5555.00--
sdlc addr C1 state is USBUSY
cls_state is CLS_STN_CLOSED
VS 0, VR 0, Remote VR 0, Current retransmit count 0
Hold queue: 0/200 IFRAMEs 0/0
TESTs 0/0 XIDs 0/0, DMs 0/1 FRMRs 20/20
RNRs 620/0 SNRMs 3/0 DISC/RDs 1/0 REJs 0/0 chain: C1/C1
sdlc addr C2 state is USBUSY
cls_state is CLS_STN_CLOSED
VS 0, VR 0, Remote VR 0, Current retransmit count 0
Hold queue: 0/200 IFRAMEs 0/0
TESTs 0/0 XIDs 0/0, DMs 0/0 FRMRs 0/0
Previous page [1] [2] [3] [4] [5][6][7] [8] [9] [10] Next page
Article entry: csh Editor in charge: csh
RNRs 730/0 SNRMs 7/0 DISC/RDs 0/0 REJs 0/0 chain: C2/C2
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 19 interface resets
0 output buffer failures, 0 output buffers swapped out
6 carrier transitions
DCD=up DSR=up DTR=up RTS=down CTS=up
Check that the destination MAC address reached by the configuration is 4001.3745.1088.
milan#write terminal
...
!
interface Serial3/7
description sdlc config to MVS
mtu 4400
no ip address
encapsulation sdlc
no keepalive
clockrate 9600
sdlc role primary
sdlc vmac 4000.1234.5600
sdlc N1 12016
sdlc address C1
sdlc xid C1 05DCCCC1
sdlc partner 4001.3745.1088 C1
sdlc address C2
sdlc xid C2 05DCCCC2
sdlc partner 4001.3745.1088 C2
sdlc dlsw C1 C2
!
...
Use the show dlsw reachability mac-address command to find that the MAC address was not found:
Router#show dlsw reachability mac-address 4001.3745.1088
DLSw MAC address reachability cache list
Mac Addr status Loc. peer/port rif
0000.810f.6500 SEARCHING LOCAL
On the router end of the FEP connection, use the show dlsw reachability mac-address command to find that the MAC address was not found:
Router#show dlsw reachability mac-address 4001.3745.1088
DLSw MAC address reachability cache list
Mac Addr status Loc. peer/port rif
0000.810f.6500 SEARCHING REMOTE
Show show source-bridge, no token to loop the SRB:
bolzano#show source-bridge
Global RSRB Parameters:
TCP Queue Length maximum: 100
Ring Group 100:
No TCP peername set, TCP transport disabled
Maximum output TCP queue length, per peer: 100
Rings:
Diagnosis: Add the "source-bridge" command and the connection is normal.
Problem: On the same serial port, one SDLC device is connected normally, but the others are not.
suggestion:
Use the show dlsw peer command to show that peer is up.
milan#sh dlsw peers
Peers: state pkts-rx pkts-tx type drops ckts TCP uptime
TCP 172.18.16.166 CONNECT 2 2 conf 0 0 0 00:224:27
Use the show dlsw reachability mac-address command to discover the MAC address:
Router#show dlsw reachability mac-address 4001.3745.1088
DLSw MAC address reachability cache list
Mac Addr status Loc. peer/port rif
0000.810f.6500 FOUND REMOTE 172.18.15.166(2065)
Use the show dlsw circuits mac-address command to tell the two links to connect:
milan#show dlsw circuit mac-address 4001.3745.1088
Index local addr(lsap) remote addr(dsap) state
250-00 4000.1234.56c1(04) 4001.3745.1088(04) CONNECTED
Previous page [1] [2] [3] [4] [5] [6][7][8] [9] [10] Next page
Article entry: csh Editor in charge: csh
251-00 4000.1234.56c2(04) 4001.3745.1088(04) CKT_ESTABLISHED
Use the debug dlsw core command to output:
milan#debug dlsw core state
DLSw core state debugging is on
milan#
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:WAN-XID state:CKT_ESTABLISHED
DLSw: core: dlsw_action_g()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:WAN-XID state:CKT_ESTABLISHED
DLSw: core: dlsw_action_g()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
DLSw: START-FSM (251-00): event:DLC-Id state:CKT_ESTABLISHED
DLSw: core: dlsw_action_f()
DLSw: END-FSM (251-00): state:CKT_ESTABLISHED->CKT_ESTABLISHED
Diagnosis: DLSw attempts to transmit XID between the lower SDLC device and the FEP, but the FEP does not establish a session. It is usually caused by XID (IDBK/IDNUM).
After adding "sdlc xid" to the configuration, the connection is normal.
STUN Troubleshooting
Confirm stun peer connectivity
rick#sh stun peer
This peer: 10.17.5.2
*Serial2 (group 1 [basic])
state rx_pkts tx_pkts drops
all TCP 10.17.5.2 open 5729 5718 0
If the status is not open, it should be a TCP/IP connection problem. Please refer to TCP/IP Troubleshooting.
Use show interface to determine the serial is up,line protocol is up.
If it is "down/down", please check the cable and use DTE and DCE Cable correctly.
If serial is up and down for a while, it keeps repeating. Your host may be configured as half-duplex instead of full-duplex, and the router is not configured as half-duplex when using MSD.
If serail is up, but line protocol is down. The maximum possible reason is that one end is NRZ coded and the other end is NRZI coded. Use the "nrzi-encoding" command to set NRZI coded. The encoding method is the same as that of a large machine.
Once the line operation is normal, the most common problem is that the SDLC address is incorrect. The SDLC address must be consistent with the host PU address. If you receive the following information, it means that the SDLC address does not match the host PU address.
Received data from wrong address! Expect for output address C2/Got C4.
Debug sdlc
When it works properly, the debug output information sequence:
SDLC Primary :
DISCONNECT-->SDLC PRI WAIT-->NET UP WAIT-->CONNECT
SDLC Secondary :
DISCONNECT-->NET UP WAIT-->SDLC SECWAIT-->CONNECT
CIP Troubleshooting
Use "show interface channel 3/0" to display the physical channel port status. If channel3/0 is up, line protocol is up.
It means that the physical interface connection is normal. Otherwise, please check whether the physical interface, cable, bypass, etc. are connected correctly.
Router#sh int c3/0
Channel3/0 is up, line protocol is up
Hardware is cyBus Channel Interface
MTU 4096 bytes, BW 36864 Kbit, DLY 270 usec, rely 255/255, load 1/255
Encapsulation CHANNEL, loopback not set
PCA adapter card
Data transfer rate 4.5 Mbytes, number of subchannels 1
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1677 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1595 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets, 0 restarts
0 output buffer failures, 0 output buffers swapped out
Use "show interface channel 3/2" to display the logical channel port status.
Router#sh int ch3/2
Channel3/2 is up, line protocol is up
Hardware is cyBus Channel Interface
MTU 4472 bytes, BW 98304 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation CHANNEL, loopback not set
Virtual interface
Last input 0:01:36, output 0:01:26, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
19090 packets input, 686391 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
20314 packets output, 754513 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets, 0 restarts
0 output buffer failures, 0 output buffers swapped out
Use "show ext ch 3/0 csna operator" to display the status of the CSNA channel connection device.
"stat" replaces "oper" to obtain the statistical value of the CSNA channel connection device.
Confirm that the CSNA channel connection device status is "setupComplet".
Router#sh ext c3/0 csna
Path Dv maxpiu time-delay length-delay
CSNA 0100 E1 20470 10 20470
Router#sh ext c3/0 csna oper
Path Dv Status SlowDown maxpiu time-delay length-delay
CSNA 0100 E1 setupComplet off 20470 10 20470
Use the "show ext ch 3/2 conn llc" command to determine the SAPs value and the connections opened on CIP.
Confirm that the correct SAP value defined in XCA is turned on in the CIP internal Token Ring LAN adapter.
SHANXI2#sh ext c3/2 conn llc
LAN Token 0 Adapter 1 5808.0100.0000
No SAPs open on this interface
Total : SAPs opened = 0 Connections active = 0
If the CSNA channel connection device status is "setupComplet", the correct SAP value (., SAP 08) is turned on in the correct CIP internal
On the MAC adapter, go to step 7. Otherwise, the problem may be PATH/DEVICE or XCA Major Node. Please check if the channel address definition is
Correct. If PATH/DEVICE is correct, the "v net, act, debug source-bridge" command on the host determines whether the detection frame is generated. If it is determined that the detection frame with the purpose of CIP internal MAC address is received, please turn on "debug channel vlan".
Use the "show ext ch 3/2 lan" command to display CIP internal MAC adapters. Verify that the CIP internal MAC adapter is
CIP microcode confirmation.
router#debug channel vlan
router#show ext ch 3/2 lan
Lan TokenRing 0
source-bridge 1000 1 100
Adapno Mac Address Name Vcnum
0 4000.1234.0001 544 0041 ACK ... ... ... ...... INU
If the CIP internal MAC adapters do not receive a CIP answer, (it is displayed in "show ext ch 3/2 lan" that is not ACK but CRE or PNDIND), it indicates that the CIP microcode does not recognize the CIP adapter configuration command. In this case, the RP does not send the probe frame to the CIP.
If the CIP internal MAC adapters have received the CIP response, use "show ext ch 3/2 llc stat 4000.0008.0000", 4000.0008.0000 is the internal MAC address of CIP to check whether the detection command and response of the CIP MAC adapter have been received.
If it is normal, use the "show ext ch 3/2 llc stat 4000.0008.0000 08" command to confirm whether SAP receives XIDs and answers. If there is no reply, it may be that the Switched Major Node is not activated, or the IDBLK/IDNUM is incorrect, or the PU is occupied.
On the lower router, the "show dlsw" command checks the SNA end station status of the serial port connection. See DLSw+ Troubleshooting.
Use "show llc2" to display the currently established LLC2 link.
SHANXI2#sh llc
LLC2 Connections: total of 1 connections
Channel1/2 DTE: 5808.0100.0000 4000.4700.10c1 04 04 state NORMAL
V(S)=38, V(R)=38, Last N(R)=38, Local window=7, Remote Window=127
akmax=3, n2=8, Next timer in 7520
xid-retry timer 0/0 ack timer 0/1000
p timer 0/1000 idle timer 7520/10000
rej timer 0/3200 busy timer 0/9600
akdelay timer 0/100 txQ count 0/200
RIF: 0630.0641.002
Previous page [1] [2] [3] [4] [5] [6] [7][8][9] [10] Next page
Article entry: csh Editor in charge: csh
Previous page [1] [2] [3] [4] [5] [6] [7] [8][9][10] Next page
Article entry: csh Editor in charge: csh
Router#sh ext c3/0 csna oper
Path Dv Status SlowDown maxpiu time-delay length-delay
CSNA 0100 E1 Close off 20470 10 20470
Use the "debug source-bridge" command to determine whether the detection frame is generated. If it is determined that the detection frame for the purpose of the CIP internal MAC address is received, please turn on "debug channel vlan".
Use the "show ext ch 3/2 lan" command to display CIP internal MAC adapters. Verify that the CIP internal MAC adapter is
CIP microcode confirmation.
router#debug channel vlan
router#show ext ch 3/2 lan
Lan TokenRing 0
source-bridge 1000 1 100
Adapno Mac Address Name Vcnum
0 4000.1234.0001 544 0041 ACK ... ... ... ...... INU
If the CIP internal MAC adapters do not receive a CIP answer, (it is displayed in "show ext ch 3/2 lan" that is not ACK but CRE or PNDIND), it indicates that the CIP microcode does not recognize the CIP adapter configuration command. In this case, the RP does not send the probe frame to the CIP.
If the CIP internal MAC adapters have received the CIP response, use "show ext ch 3/2 llc stat 4000.0008.0000", 4000.0008.0000 is the internal MAC address of CIP to check whether the detection command and response of the CIP MAC adapter have been received.
If it is normal, use the "show ext ch 3/2 llc stat 4000.0008.0000 08" command to confirm whether SAP receives XIDs and answers. If there is no reply, it may be that the Switched Major Node is not activated, or the IDBLK/IDNUM is incorrect, or the PU is occupied.
On the lower router, the "show dlsw" command checks the SNA end station status of the serial port connection. See DLSw+ Troubleshooting.
Use "show llc2" to display the currently established LLC2 link.
SHANXI2#sh llc
LLC2 Connections: total of 1 connections
Channel1/2 DTE: 5808.0100.0000 4000.4700.10c1 04 04 state NORMAL
V(S)=38, V(R)=38, Last N(R)=38, Local window=7, Remote Window=127
akmax=3, n2=8, Next timer in 7520
xid-retry timer 0/0 ack timer 0/1000
p timer 0/1000 idle timer 7520/10000
rej timer 0/3200 busy timer 0/9600
akdelay timer 0/100 txQ count 0/200
RIF: 0630.0641.0020
Previous page [1] [2] [3] [4] [5] [6] [7] [8] [9][10]
Article entry: csh Editor in charge: csh