Dell FTOS 04 Basic Troubleshooting Tools

Dell Force 10 Basic Troubleshooting Tools

Module 4

4-2

Objectives • Introduction to Troubleshooting

Methodology

• Best Approach when Troubleshooting the E-Series

• Common Configuration Oversights

• Get used to Basic Troubleshooting Tools – How to use and interpret them – to comfortably be able to

identify specific feature and protocol messages using “show” and “debug”

• Troubleshooting Physical Layer Issues

4-3

What is Troubleshooting?

• A form of problem solving – Systematic search for a source of a problem

– Use a process of elimination – Start with most probable possible cause and work your way back

• Usually used in response to an event where something stopped working

– Focus on what changed – Try not to jump to conclusions early

• Only feasible if knowledge of the item is prevalent

– Conceptual – What is it supposed to do?

– Physical – Is it correctly set up?

– What is it not doing? – How do you know it is a problem?

4-4

Methods of Troubleshooting

• “K.I.S.S.” – Keep it Short and Simple – Check all the basics

• Physical

– Substitute known good components for suspect ones

• Logical – If you understand the theory of operation, go through a cognitive

walkthrough to try and trace the problem

• Checklists

– Systematic procedure that is made in response to most-likely human or developmental flaws

4-5

Troubleshooting Items To Check

• A router is basically a software product that is executed in hardware – Unlike a toaster or appliance, user configuration is always needed prior to

being operational

• Areas of concern

– FTOS – Basic configuration of interfaces

– Connections, links, configuration – Basic to advanced configuration of protocols

– VLANs, MSTI, OSPF, BGP – Basic to advanced configuration of features

– ACLs, QoS, Management (SNMP, S-flow, etc.) – Physical Hardware

– Interfaces – Line cards

– RPM – Switch Fabric

– Backplane

4-6

More Basic Physical & Interface Connections • Verify connectivity

– Are you “talking” to the other router?

– Ping, traceroute, telnet

– Is the interface “Up”

– Is the interface enabled?

– Is it plugged in?

– Is it plugged in? Is there a link?

• Interface configuration

– Is the other side on, enabled, connected?

– Does it have an IP address? Is the subnet correct?

– Are there errors on the interfaces? – Is the interface passing traffic?

• Look for the most likely source of the problem

– Is this a new link you are trying to bring up?

– Re-check configuration steps on your side, then the other

– Is this an existing configured interface link which has gone down?

– Re-check configuration on both sides (someone else may have changed it)

– Look at logs and messages

4-7

Check Basic Accessibility and Protocol Configuration • Accessibility Options

– Is there a valid route? Is it reachable?

– Are you using static or dynamic routing? – Is ACL operation properly/improperly configured?

– Are your rules correct? Are they in the correct sequence?

• Protocol Configuration – Look at global protocol configuration

– Enabled? – MSTI #, VLAN ID, AS number, OSPF Area & type, etc.

– Look at interface specific configuration – Is interface configured for correct protocol?

– Do passwords, keys, timers, etc. match?

4-8

The Basic Troubleshooting Toolbox

• ping <destination-ip>

• show ip route <destination-ip>

• traceroute ip <destination-ip>

• show interface <slot/port>

• clear counters interface

• show mac-address-table

• show arp

• show running-config interface <slot/port>

• Terminal Monitoring

• Shutting down an interface

• Debug utility

4-9

Ping <IP address>

• Used to see if the other side of the link is reachable

• Omitting IP address will prompt the user for extended options

Force10#ping 172.16.1.250

Type Ctrl-C to abort.

Sending 5, 100-byte ICMP Echos to 172.16.1.250, timeout is 2 seconds:

!!!!!

Success rate is 100.0 percent (5/5), round-trip min/avg/max = 0/0/0

(ms)

Force10#ping

Target IP address : 172.16.1.250

Repeat Count [5] :

Datagram size [100] :

Timeout in secs [2] :

Extended commands [n] : y

Source address or interface : 172.16.1.177

Type of service [0] :

Set DF bit in IP header [n] :

Validate reply data [n] :

Data pattern [0xABCD] :

Sweep range of sizes [n]:


Sending 5, 100-byte ICMP Echos to 172.16.1.250, timeout is 2 seconds:

!!!!!

Success rate is 100.0 percent (5/5), round-trip min/avg/max = 0/0/0

(ms)

4-10

• Command used to view Layer-2 Bridging table

Force10#show mac-address-table

VlanId Mac Address Type Interface State

20 00:01:e8:0f:41:06 Dynamic Po 31 Active






Show Mac-Address-Table

4-11

Show IP Route <IP address>

• Used to see what interfaces can reach a particular network based on a routing table entry

Force10#show ip route 10.10.93.9

Routing entry for 10.10.93.0/24

Known via "ospf 44444", distance 110, metric 2, type intra

area

Last update 00:23:45 ago

Routing Descriptor Blocks:

* 10.10.43.3, via GigabitEthernet 4/32

Force10#show ip route 192.168.1.2

% Error: Network not in table.

Force10#

Force10#

4-12

Traceroute <IP address>

• Used to determine the route taken by packets across an IP network

• Omitting IP address will prompt the user for extended options

Force10#traceroute 172.16.1.205


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

Tracing the route to 172.16.1.206 from 172.16.1.177, 30 hops max, 40 byte packets

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

TTL Hostname Probe1 Probe2 Probe3

1 172.16.1.206 016.667 ms * 000.000 ms

Force10#traceroute

Target IP address : 172.16.1.206

Source IP address : 172.16.1.177

Timeout in secs [5] :

Probe count [3] :

Minimum TTL [1] :

Maximum TTL [30] :

Port number [33434] :


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

Tracing the route to 172.16.1.206 from 172.16.1.177, 30 hops max, 40 byte packets

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

TTL Hostname Probe1 Probe2 Probe3

1 172.16.1.206 016.667 ms * 000.000 ms

4-13

Force10#show interface gigabit 4/7 GigabitEthernet 4/7 is up, line protocol is up Hardware is Force10Eth, address is 00:01:e8:0f:1e:77 Current address is 00:01:e8:0f:1e:77

Interface index is 169918521

Port will not be disabled on partial SFM failure

Internet address is 10.10.94.4/24 MTU 1554 bytes, IP MTU 1500 bytes

LineSpeed 1000 Mbit, Mode full duplex, Master

ARP type: ARPA, ARP Timeout 04:00:00

Last clearing of "show interface" counters 00:43:47 Queueing strategy: fifo

Input Statistics:

7 packets, 718 bytes

0 Vlans 2 64-byte pkts, 5 over 64-byte pkts, 0 over 127-byte pkts

0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte

pkts

0 Multicasts, 0 Broadcasts 0 runts, 0 giants, 0 throttles

0 CRC, 0 overrun, 0 discarded

Output Statistics:

202 packets, 16708 bytes, 0 underruns 2 64-byte pkts, 200 over 64-byte pkts, 0 over 127-byte pkts

0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte

pkts

195 Multicasts, 1 Broadcasts, 6 Unicasts 0 Vlans, 0 throttles, 0 discarded, 0 collisions

Rate info (interval 299 seconds):

Input 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate

Output 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate Time since last interface status change: 00:32:10

Show Interface <slot/port> View Interface statistics

If the line protocol is DOWN, it could indicate a physical link problem. Check cable and connection at other side.

Knowing the MAC Addresses can help to troubleshoot Bridging, L2

ACL’s & ARP issues

If the interface is DOWN, enter configuration mode and

administratively activate the port by typing no shutdown

If IP address present, interface is in L3 mode.

4-14

More on Interface UP/DOWN

Administrative State “shutdown or no

shutdown”

Link Protocol State

What It Means

Down Down

The administrative state is down. When this is the case, the line protocol must be down, even when the physical link can be brought up. FTOS attempts to bring up the physical state only after the administrative state is up.

Up Down

The “line protocol is [up or down]” message indicates the actual state of the physical link. When an interface is showing as up/down, there is no data path through the MAC; the PHY simply is sensing the electrical signaling.

Up Up The interface has been enabled administratively, and the data path through the MAC is established.

4-15

Clear Counters Resets Interface Statistics

Force10#clear counters Clear counters on all interfaces [confirm] y Force10#show interface gigabit 4/7 GigabitEthernet 4/7 is up, line protocol is up Hardware is Force10Eth, address is 00:01:e8:0f:1e:77 Current address is 00:01:e8:0f:1e:77 Interface index is 169918521 Port will not be disabled on partial SFM failure Internet address is 10.10.94.4/24 MTU 1554 bytes, IP MTU 1500 bytes LineSpeed 1000 Mbit, Mode full duplex, Master ARP type: ARPA, ARP Timeout 04:00:00 Last clearing of "show interface" counters 00:43:47 Queueing strategy: fifo Input Statistics: 70 packets, 0 bytes 0 Vlans 0 64-byte pkts, 0 over 64-byte pkts, 0 over 127-byte pkts 0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte

pkts 0 Multicasts, 0 Broadcasts 0 runts, 0 giants, 0 throttles 0 CRC, 0 overrun, 0 discarded Output Statistics: 1 packets, 81 bytes, 0 underruns 0 64-byte pkts, 1 over 64-byte pkts, 0 over 127-byte pkts 0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte

pkts 1 Multicasts, 1 Broadcasts, 6 Unicasts 0 Vlans, 0 throttles, 0 discarded, 0 collisions Rate info (interval 299 seconds): Input 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate Output 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate Time since last interface status change: 00:33:12 Force10#

Input and Output statistics can tell you if

traffic is flowing through the interface

This timer indicates the last time the state of the

interface changed.

Rate info can aid with ACL and QoS

troubleshooting

4-16

• Shows which IP address are associated to a particular MAC address and outgoing interface

Force10#show arp

Protocol Address Age(min) Hardware Address Interface VLAN CPU

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

Internet 10.10.43.3 75 00:01:e8:0f:40:9f Gi 4/32 - CP

Internet 10.10.43.4 - 00:01:e8:0f:1e:90 Gi 4/32 - CP

Internet 10.10.94.4 - 00:01:e8:0f:1e:77 Gi 4/7 - CP

Internet 10.10.94.9 59 00:00:07:c7:84:20 Gi 4/7 - CP

Internet 10.11.130.252 1 00:01:e8:d5:c6:f5 Ma 0/0 - CP

Internet 10.11.130.253 0 00:01:e8:d5:c6:0a Ma 0/0 - CP

Force10#

Show ARP

4-17

Duplex Mismatch Between Two Devices

• Can occur when manually hardcoding the speed and duplex or from autonegotiation issues between the two devices.

• Duplex mismatch due to autonegotiation

– On some devices, autonegotiation is disabled (even when IEEE802.3 recommends keeping it enabled) on all ports that are capable of it, and a fixed modality of 100 Mbit/s and full duplex is used to ensure maximum performance.

– This was especially done by network administrators upon the introduction of autonegotiation, because of interoperability issues with the initial autonegotiation specification.

– A fixed mode of operation works if both ends of a connection are locked to the same settings.

• When a device set to autonegotiation is connected to a device that is not using autonegotiation, the autonegotiation process fails.

– The autonegotiating end of the connection is still able to correctly detect the speed of the other end, but cannot correct the duplex mode.

– The standard requires the use of half duplex in these conditions. Therefore, the autonegotiating end of the connection uses half duplex while its peer is locked at full duplex, and this is a duplex mismatch.

4-18

Effects of Duplex Mismatch • Communication is possible over a connection in spite of a duplex mismatch. Single

packets are sent and acknowledged without problems.

• Symptoms of a duplex mismatch are connections that seem to work fine with a ping

command, but "lock up" easily with very low throughput on data transfers;

– The effective data transfer rate is likely to be asymmetrical, performing much

worse in one direction than the other.

– In normal half-duplex operations "late collisions" do not occur.

– Duplex mismatch the collisions seen on the half-duplex side of the link are often

late collisions.

– The full-duplex side usually will register FCS (frame check sequence) errors, or

runts.[2] Viewing this standard Ethernet statistic can help diagnose this problem.

• A duplex mismatch can be fixed by either enabling autonegotiation (if available and

working) on both ends or by forcing the same settings on both ends

• If there is no option but to have a locked setting on one end and autonegotiation the

other half duplex must be used.

http://en.wikipedia.org/wiki/Autonegotiation



http://en.wikipedia.org/wiki/Late_collision

http://en.wikipedia.org/wiki/Frame_check_sequence

4-19

• If the switch port is using a transceiver and reports "Media type is unknown", you might need to investigate a transceiver issue

• FTOS maintains a database of transceivers qualified by Force10. If you use a non-qualified transceiver, or if FTOS cannot read the transceiver information from the serial EEPROM (which may occur because of a

• hardware issue), the media type displays as "unknown", and the following message occurs:

%EXW2PF3:0 %IFAGT-5-UNSUP_OPTICS: Non-qualified optics in slot 0 port 0

Force10#show interfaces gig 0/37

GigabitEthernet 0/37 is up, line protocol is up

Hardware is Force10Eth, address is 00:01:e8:02:b7:8e

Pluggable media present, Media type is unknown

Recognizing a Physical Layer Issue

4-20

• Force10 allows non-qualified SFP and XFP transceivers to be used, but FTOS might not be able to retrieve some data about the media.

• In that case, typically when the output of this field is “Pluggable media present, Media type is unknown”, the Medium and receive power reading data might not be present in the output.

Force10#show interfaces tengigabitethernet 0/0

TenGigabitEthernet 3/0 is up, line protocol is up

Hardware is Force10Eth, address is 00:01:e8:41:77:c5

Current address is 00:01:e8:41:77:c5

Pluggable media present, XFP type is 10GBASE-SR

Medium is MultiRate, Wavelength is 850.00nm

XFP receive power reading is -2.4834

Interface index is 134545468

Port will not be disabled on partial SFM failure

MTU 9252 bytes, IP MTU 9234 bytes

LineSpeed 10000 Mbit

Flowcontrol rx on tx on


Last clearing of "show interface" counters 00:15:14

Queueing strategy: fifo

Non-qualified SFP & XFP Transceivers

4-21

• FTOS Version 7.4.1 extends the command show interfaces

with the keyword transceiver, which displays the serial EEPROM of any installed transceivers on both Gigabit and 10-Gigabit interfaces.

• Use the command show interfaces transceiver to

check for a hardware issue with the transceiver, particularly when you are using qualified Force10 transceivers.

• Verify that you see the line "SFP is present" for a Gigabit interface and "XFP is present" for a 10-Gigabit interface in the output

Force10#show interfaces gigabitethernet 1/0

transceiver

SFP is present.

SFP 0 Serial Base ID fields

SFP 0 Id = 0x03

SFP 0 Ext Id = 0x04

SFP 0 Connector = 0x07

SFP 0 Transciever Code = 0x00 0x00 0x00 0x01 0x20

0x40 0x0c 0x05

SFP 0 Encoding = 0x01

SFP 0 BR Nominal = 0x15

SFP 0 Length(9um) Km = 0x00

SFP 0 Length(9um) 100m = 0x00

SFP 0 Length(50um) 10m = 0x1e

SFP 0 Length(62.5um) 10m = 0x0f

SFP 0 Length(Copper) 10m = 0x00

SFP 0 Vendor Name = FINISAR CORP.

SFP 0 Vendor OUI = 0x00 0x90 0x65

SFP 0 Vendor PN = FTRJ8519P1BNL

SFP 0 Vendor Rev = A

SFP 0 Laser Wavelength = 850 nm

SFP 0 CheckCodeBase = 0x66

SFP 0 Serial Extended ID fields

SFP 0 Options= 0x00 0x12

SFP 0 BR max= 0

SFP 0 BR min= 0

SFP 0 Vendor SN= P5N1ACE

SFP 0 Datecode = 040528

Show Interfaces Transceiver

4-22

• 10-Gigabit interfaces transmit link fault signaling (LFS) and other lower-layer status information

• Link status messages are four bytes in length and are transmitted during the inter-frame period

– They consist of a particular sequence of control character values as defined in the IEEE 802.ae standard.

– A remote interface recognizes that a link fault condition has cleared when it no longer receives link status messages.

Force10#show interfaces tengigabitethernet 4/0 link-status

Port Status

Loss of Signal : FALSE (XFP has power)

RX Signal Lock Error : TRUE (Lock detected)

PCS Link State : Down

Link Faults

Remote : None (No Fault)

Local : Fault (Fault present)

Idle Error : False (Not received)

Illegal Symbol : False (Not received)

Error Symbol : False (Not received)

Troubleshooting 10-Gigabit Interfaces

4-23

• Loss of Signal – Indicates that the interface has not detected the required number of digital bit transitions (from 1

to 0 and 0 to 1) on the incoming signal – A 10-Gigabit link must see a certain number of such transitions to ensure proper synchronization

• Rx Signal Lock Error – Indicates a loss-of-timing condition. The receive clock must be recovered from the incoming data

stream to allow the receiving physical layer to synchronize with the incoming electrical pulses • PCS Link State

– Displays the state of the Physical Coding Sublayer (PCS). – The value can be "Up" or "Down"

• Link Fault – Remote – Indicates that the remote device has detected a fault, is inhibiting the transmission of frames, and

is continuously transmitting idle messages • Link Fault – Local

– Indicates that the switch has detected a fault condition, is inhibiting the transmission of frames, and is continuously transmitting remote fault signals

– Link Fault - Idle Error – Indicates that the switch has detected a non-idle symbol during an idle period

• Link Fault - Illegal Symbol – Indicates that the switch has detected an illegal symbol other than an error symbol while receiving

data frames • Link Fault - Error Symbol

– Indicates that the switch has detected an error symbol while receiving data frames

Show Interfaces tengigabitethernet link-status Output Description

4-24

• The easiest way to check for an auto-negotiation mismatch is to look for the string "Auto-neg Error" in the:

– show interfaces gigabit

– Note: 1000Base-T requires auto-negotiation. The IEEE Ethernet standard does not support setting a speed manually to 1000 Mbps

Force10#show interfaces gigabit 0/3

GigabitEthernet 0/3 is up, line protocol is down

Hardware is Force10Eth, address is 00:01:e8:07:16:b3

Internet address is not set

MTU 1554 bytes, IP MTU 1500 bytes

LineSpeed auto, Mode full duplex, Auto-neg Error


Last clearing of "show interface" counters 04:39:17

[output omitted]

Investigating an Auto-negotiation Mismatch

4-25

• The command show interfaces

gigabitethernet phy

displays the received and transmitted auto-negotiation information as well as link fault status details

Force10#show int gigabitethernet 1/0 phy

Mode Control:

SpeedSelection: 10b

AutoNeg: ON

Loopback: False

PowerDown: False

Isolate: False

DuplexMode: Full

Mode Status:

AutoNegComplete: False

RemoteFault: False

LinkStatus: False

JabberDetect: False

AutoNegotation Advertise:

100MegFullDplx: True

100MegHalfDplx: True

10MegFullDplx: False

10MegHalfDplx: True

Asym Pause: False

Sym Pause: False

AutoNegotiation Remote Partner's Ability:


100MegHalfDplx: False


10MegHalfDplx: False

Asym Pause: False

Sym Pause: False

AutoNegotiation Expansion:

ParallelDetectionFault: False

[output omitted]

Viewing Auto-negotiation Information

4-26

Transceiver Troubleshooting

• If the switch port is using a transceiver and reports “Media type is unknown”, you may need to investigate a transceiver issue

Force10#show interface ten 0/0

TenGigabitEthernet 0/0 is up, line protocol is up

Hardware is Force10Eth, address is 00:01:e8:02:b7:8e

Pluggable media present, Media type is unknown

• FTOS maintains a database of transceivers which have been qualified by Force10 Networks. If you use a non-qualified transceiver or if FTOS cannot read the transceiver information from the serial EEPROM (which may occur because of a hardware issue), the media type displays as “unknown”, and a console message similar to the following is displayed:

%EXW10SH:0 %IFAGT-5-UNSUP_OPTICS: Non-qualified optics in slot 0 port 0

• The show interfaces command with the transceiver keyword to display the serial EEPROM of any installed transceivers on both 1-Gig (SFPs) and 10-Gig interfaces (XFPs)

4-27

Show Running-Config Interface

• Shows the running configuration filtered by a specific interface

• No need to go into config mode or view entire config

Force10#show running-config int gig 4/5

!

interface GigabitEthernet 4/5

no ip address

shutdown


!


ip address 10.10.94.4/24

no shutdown


!


ip address 10.10.43.4/24

shutdown

Force10#

Basic configuration with IP address and interface

enabled (no shutdown)

IP address is configured but interface is DISABLED

(shutdown)

Default configuration of an interface “UNSET”

4-28

Terminal Monitoring

• Severity messages can be viewed on the terminal line – From Console it is enabled by default

– It can be disabled – From Telnet/SSH it is disabled by default

– It can be enabled

Force10#terminal monitor

Force10#conf

Force10(conf)#

Force10(conf)#Sep 28 18:19:16: %RPM0-P:CP %IFMGR-5-OSTATE_DN: Changed

interface state to down: Gi 3/42

Sep 28 18:19:25: %RPM0-P:CP %IFMGR-5-OSTATE_UP: Changed interface state

to up: Gi 3/42

Force10(conf)#ex

Sep 28 18:21:03: %RPM0-P:CP %SYS-5-CONFIG_I: Configured from console by

console

Force10#terminal no monitor

Force10#

4-29

Test the Link by Shutting Down an Interface

• This lets you test the physical link without having to physically plug and unplug the cable

Force10(conf)#Sep 28 18:19:16:

%RPM0-P:CP %IFMGR-5-OSTATE_DN:

Changed interface state to down: Gi

3/41

Sep 28 18:19:25: %RPM0-P:CP %IFMGR-

5-OSTATE_UP: Changed interface

state to up: Gi 3/41

Force10(conf-if-gi-4/32)#shutdown

Force10(conf-if-gi-4/32)#Sep 28

18:33:51: %RPM0-P:CP %IFMGR-5-

OSTATE_DN: Changed interface state

to down: Gi 4/32

Force10(conf-if-gi-4/32)# no

shutdown

Force10(conf-if-gi-4/32)#Sep 28

18:34:01: %RPM0-P:CP %IFMGR-5-

OSTATE_UP: Changed interface state

to up: Gi 4/32

Miscabled!

Gi3/41

Gi3/42

Gi4/31

Gi4/32

4-30

The Debugging Utility

• Allows isolation of packets and processing

• Each debug area has sub-options unique to the item – Allows capture of

more specific types of messages

Force10#debug ?

aaa AAA debug information

arp IP ARP debug information

call-home Call-home debug information

fvrp FVRP debugging commands

ip IP debug information

ipv6 IPv6 debug information

isis IS-IS debug information

lacp LACP debugging commands

mac MAC debugging commands

radius RADIUS debug information

spanning-tree Spanning tree debug information

vrrp VRRP debug information

Force10#debug ip ?

bgp BGP protocol transactions

dhcp DHCP relay transactions

icmp ICMP transactions

igmp IGMP protocol transactions

msdp MSDP protocol transactions

ospf OSPF protocol transactions

packet General IP transactions

Force10#debug ip ospf ?

event OSPF protocol event

packet OSPF protocol packet

spf OSPF protocol shortest path

<cr>

Force10#

4-31

1

2

3

1. Turn on a specific debug filter

2. View debug messages

3. Turn off debug – if no count specified

Generic Steps to Use Debug

Force10#debug ip ospf

All OSPF debugging has been turned on

Force10#23:07:30 : OSPF(44444:00):

Rcv. v:2 t:1(HELLO) l:48 rid:10.10.93.3

aid:0 chk:0x8363 aut:0 auk: keyid:0

from:Gi 4/32

netmask:255.255.255.0 pri:1 N-, MC-,

E+, T-,

hi:10 di:40 dr:10.10.43.4

bdr:10.10.43.3

Nbr: 10.10.94.4

23:07:30 : OSPF(44444:00):

Xmt. v:2 t:1(HELLO) l:48 rid:10.10.94.4

aid:0 chk:0x8363 aut:0 auk: keyid:0 to:Gi

4/32 dst:224.0.0.5

netmask:255.255.255.0 pri:1 N-, MC-,

E+, T-,

hi:10 di:40 dr:10.10.43.4

bdr:10.10.43.3

Nbr: 10.10.93.3

23:07:40 : OSPF(44444:00):

Force10#undebug all

All possible debugging has been turned off

Force10#

4-32

1. Make sure terminal monitoring is on

2. When enabling debug, specify a count to automatically turn off debug

3. Use “show debug” to view filters that are enabled

4. If debugging over a longer period of time, consider sending output to the log

– Note, you will see all log messages in the buffer

5. Clear the buffer first to remove any unwanted, old entries

1

2

3

Additional Debug Tips Force10#terminal monitor Force10#debug ip packet gi 4/7 count 2 IP packet debugging is on for gigabitethernet 4/7 Force10#show debug Generic IP: IP packet debugging is on for (Count 5) GigabitEthernet 4/7 Force10#22:05:57 : IP: s=10.10.94.4 (local), d=224.0.0.5 (Gi 4/7), len 64, sending proto=89 22:06:06 : IP: s=10.10.94.4 (local), d=224.0.0.5 (Gi 4/7), len 64, sending proto=89 Sep 28 18:00:21: %RPM0-P:RP1 %IPMGR-5-DEBUG_IP_PACKET_COUNT_REACHED: ip debug count reached, ip debugging turned off Force10#show log Syslog logging: enabled Console logging: level debugging Monitor logging: level debugging Buffer logging: level debugging, 123 Messages Logged, Size (40960 bytes) Trap logging: level informational Last logging buffer cleared: 22:33:21 Nbr: 10.10.93.3 hi:10 di:40 dr:10.10.43.4 bdr:10.10.43.3 netmask:255.255.255.0 pri:1 N-, MC-, E+, T-, aid:0 chk:0x8363 aut:0 auk: keyid:0 to:Gi 4/32 dst:224.0.0.5 Force10#clear log Clear logging buffer [confirm] yes Force10#show log Syslog logging: enabled Console logging: level debugging Monitor logging: level debugging Buffer logging: level debugging, 0 Messages Logged, Size (40960 bytes) Trap logging: level informational Last logging buffer cleared: 23:30:46

4

5

4-33

Going Forward

• Feature and Protocol specific troubleshooting commands will be presented in their respective modules

• Understand how the protocol/feature works in order to best interpret the show commands and debug output

• Look at the running configuration and compare it with the working examples in each chapter

• In this class, errors will usually occur at the interface between the keyboard and chair

4-34

Summary • Troubleshooting Methodology

involves a step-by-step approach starting with the basics

• Common Configuration Oversights are common and should be checked first

• Basic Troubleshooting Tools can help to solve the majority of configuration related issues

• Operational knowledge of the feature or protocol will help map the troubleshooting steps to be taken

Documents

Dell FTOS 04 Basic Troubleshooting Tools