Content .. 37 38 39

Cisco Industrial Ethernet 4000, 4010 and 5000 Switch Software. Configuration Guide (2022) - page 39

Troubleshooting

Information for Troubleshooting

The traceroute mac ip command output shows the Layer 2 path when the specified source and destination IP

addresses belong to the same subnet. When you specify the IP addresses, the switch uses the Address Resolution

Protocol (ARP) to associate the IP addresses with the corresponding MAC addresses and the VLAN IDs.

— If an ARP entry exists for the specified IP address, the switch uses the associated MAC address and identifies

the physical path.

— If an ARP entry does not exist, the switch sends an ARP query and tries to resolve the IP address. If the IP

address is not resolved, the path is not identified, and an error message appears.

When multiple devices are attached to one port through hubs (for example, multiple CDP neighbors are detected on

a port), the Layer 2 traceroute feature is not supported. When more than one CDP neighbor is detected on a port,

the Layer 2 path is not identified, and an error message appears.

IP Traceroute

You can use IP traceroute to identify the path that packets take through the network on a hop-by-hop basis. The

command output displays all network layer (Layer 3) devices, such as routers, that the traffic passes through on the way

to the destination.

Your switches can participate as the source or destination of the traceroute privileged EXEC command and might or

might not appear as a hop in the traceroute command output. If the switch is the destination of the traceroute, it is

displayed as the final destination in the traceroute output. Intermediate switches do not show up in the traceroute output

if they are only bridging the packet from one port to another within the same VLAN. However, if the intermediate switch

is a multilayer switch that is routing a particular packet, this switch shows up as a hop in the traceroute output.

The traceroute privileged EXEC command uses the Time To Live (TTL) field in the IP header to cause routers and servers

to generate specific return messages. Traceroute starts by sending a User Datagram Protocol (UDP) datagram to the

destination host with the TTL field set to 1. If a router finds a TTL value of 1 or 0, it drops the datagram and sends an

Internet Control Message Protocol (ICMP) time-to-live-exceeded message to the sender. Traceroute finds the address

of the first hop by examining the source address field of the ICMP time-to-live-exceeded message.

To identify the next hop, traceroute sends a UDP packet with a TTL value of 2. The first router decrements the TTL field

by 1 and sends the datagram to the next router. The second router sees a TTL value of 1, discards the datagram, and

returns the time-to-live-exceeded message to the source. This process continues until the TTL is incremented to a value

large enough for the datagram to reach the destination host (or until the maximum TTL is reached).

To learn when a datagram reaches its destination, traceroute sets the UDP destination port number in the datagram to a

very large value that the destination host is unlikely to be using. When a host receives a datagram destined to itself

containing a destination port number that is unused locally, it sends an ICMP port-unreachable error to the source.

Because all errors except port-unreachable errors come from intermediate hops, the receipt of a port-unreachable error

means that this message was sent by the destination port.

TDR

You can use the Time Domain Reflector (TDR) feature to diagnose and resolve cabling problems. When running TDR, a

local device sends a signal through a cable and compares the reflected signal to the initial signal.

TDR is supported only on 10/100 and 10/100/1000 copper Ethernet ports. It is not supported on SFP module ports.

TDR can detect these cabling problems:

Open, broken, or cut twisted-pair wires—The wires are not connected to the wires from the remote device.

Shorted twisted-pair wires—The wires are touching each other or the wires from the remote device. For example, a

shorted twisted pair can occur if one wire of the twisted pair is soldered to the other wire.

If one of the twisted-pair wires is open, TDR can find the length at which the wire is open.

1087

Troubleshooting

Information for Troubleshooting

Use TDR to diagnose and resolve cabling problems in these situations:

Replacing a switch

Setting up a wiring closet

Troubleshooting a connection between two devices when a link cannot be established or when it is not operating

properly

Crashinfo Files

The crashinfo files save information that helps Cisco technical support representatives to debug problems that caused

the Cisco IOS image to fail (crash). The switch writes the crash information to the console at the time of the failure. The

switch creates two types of crashinfo files:

Basic crashinfo file—The switch automatically creates this file the next time you boot up the Cisco IOS image after

the failure.

Extended crashinfo file—The switch automatically creates this file when the system is failing.

Basic crashinfo Files

The information in the basic file includes the Cisco IOS image name and version that failed, a list of the processor

registers, and other switch-specific information. You can provide this information to the Cisco technical support

representative by using the show tech-support privileged EXEC command.

Basic crashinfo files are kept in this directory on the flash file system:

flash:/crashinfo/.

The filenames are crashinfo_n where n is a sequence number.

Each new crashinfo file that is created uses a sequence number that is larger than any previously existing sequence

number, so the file with the largest sequence number describes the most recent failure. Version numbers are used

instead of a timestamp because the switches do not include a real-time clock. You cannot change the name of the file

that the system will use when it creates the file. However, after the file is created, you can use the rename privileged

EXEC command to rename it, but the contents of the renamed file will not be displayed by the show tech-support

privileged EXEC command. You can delete crashinfo files by using the delete privileged EXEC command.

You can display the most recent basic crashinfo file (that is, the file with the highest sequence number at the end of its

filename) by entering the show tech-support privileged EXEC command. You also can access the file by using any

command that can copy or display files, such as the more or the copy privileged EXEC command.

Extended crashinfo Files

The switch creates the extended crashinfo file when the system is failing. The information in the extended file includes

additional information that can help determine the cause of the switch failure. You provide this information to the Cisco

technical support representative by manually accessing the file and using the more or the copy privileged EXEC

command.

Extended crashinfo files are kept in this directory on the flash file system:

flash:/crashinfo_ext/.

The filenames are crashinfo_ext_n where n is a sequence number.

You can configure the switch to not create the extended creashinfo file by using the no exception crashinfo global

configuration command.

1088

Troubleshooting

Information for Troubleshooting

CPU Utilization

This section lists some possible symptoms that could be caused by the CPU being too busy and shows how to verify a

CPU utilization problem. Table 72 on page 1089 lists the primary types of CPU utilization problems that you can identify.

It gives possible causes and corrective action with links to the Troubleshooting High CPU Utilization document on

Cisco.com.

Excessive CPU utilization might result in these symptoms, but the symptoms could also result from other causes.

Spanning tree topology changes

EtherChannel links brought down due to loss of communication

Failure to respond to management requests (ICMP ping, SNMP timeouts, slow Telnet or SSH sessions)

UDLD flapping

IP SLAs failures because of SLAs responses beyond an acceptable threshold

DHCP or IEEE 802.1x failures if the switch does not forward or respond to requests

Problem and Cause for High CPU Utilization

To determine if high CPU utilization is a problem, enter the show processes cpu sorted privileged EXEC command. Note

the underlined information in the first line of the output example.

Switch# show processes cpu sorted

CPU utilization for five seconds: 8%/0%; one minute: 7%; five minutes: 8%

PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process

140 8820183 4942081 1784 0.63% 0.37% 0.30% 0 HRPC qos request

100 3427318 16150534 212 0.47% 0.14% 0.11% 0 HRPC pm-counters

192 3093252 14081112 219 0.31% 0.14% 0.11% 0 Spanning Tree

143 8 37 216 0.15% 0.01% 0.00% 0 Exec

This example shows normal CPU utilization. The output shows that utilization for the last 5 seconds is 8%/0%, which has

this meaning:

The total CPU utilization is 8 percent, including both time running Cisco IOS processes and time spent handling

interrupts.

The time spent handling interrupts is zero percent.

Table 72

Troubleshooting CPU Utilization Problems

Type of Problem

Cause

Corrective Action

Interrupt percentage value is almost

The CPU is receiving too many packets

Determine the source of the network

as high as total CPU utilization value.

from the network.

packet. Stop the flow, or change the

switch configuration. See the section on

“Analyzing Network Traffic.”

Total CPU utilization is greater than

One or more Cisco IOS process is

Identify the unusual event, and

50% with minimal time spent on

consuming too much CPU time. This is

troubleshoot the root cause. See the

interrupts.

usually triggered by an event that

section on “Debugging Active

activated the process.

Processes.”

For complete information about CPU utilization and how to troubleshoot utilization problems, see the Troubleshooting

High CPU Utilization document on Cisco.com.

1089

Troubleshooting

How to Troubleshoot

Recovering from Software Failures

Switch software can be corrupted during an upgrade, by downloading the wrong file to the switch, and by deleting the

image file. In all of these cases, the switch does not pass the power-on self-test (POST), and there is no connectivity.

This procedure uses the Xmodem Protocol to recover from a corrupt or wrong image file. There are many software

packages that support the Xmodem Protocol, and this procedure is largely dependent on the emulation software that

you are using.

This recovery procedure requires that you have physical access to the switch.

1. From your PC, download the software image tar file (image_filename.tar) from Cisco.com.

The Cisco IOS image is stored as a bin file in a directory in the tar file. For information about locating the software image

files on Cisco.com, see the release notes.

Extract the bin file from the tar file.

If you are using Windows, use a zip program that can read a tar file. Use the zip program to navigate to and extract

the bin file.

If you are using UNIX, follow these steps:

— Display the contents of the tar file by using the tar -tvf <image_filename.tar> UNIX command.

switch% tar -tvf image_filename.tar

— Locate the bin file, and extract it by using the tar -xvf <image_filename.tar> <image_filename.bin> UNIX

command.

switch% tar -xvf image_filename.tar image_filename.binx

x image_name.bin, 3970586 bytes, 7756 tape blocks

— Verify that the bin file was extracted by using the ls -l <image_filename.bin> UNIX command.

switch% ls -l image_filename.bin-rwxr-xr-x

1 bschuett eng

6365325 May 19 13:03

-rw-r--r--

1 boba

3970586 Apr 21 12:00 image_name.bin

Connect your PC with terminal-emulation software supporting the Xmodem Protocol to the switch console port.

Set the line speed on the emulation software to 9600 baud.

Unplug the switch power cord.

Press the Express Setup buttonfactory default button and at the same time, reconnect the power cord to the switch.

You can release the button a second or two after the LED above port 1 goes offwhen the password-recovery mechanism

is enabled.message appears. Several lines of information about the software appear along with instructions:

The system has been interrupted prior to initializing the flash file system. The following commands

will initialize the flash file system, and finish loading the operating system software#

flash_init

load_helper

boot

7. Initialize the flash file system:

1090

Troubleshooting

How to Troubleshoot

switch: flash_init

8. If you had set the console port speed to anything other than 9600, it has been reset to that particular speed. Change

the emulation software line speed to match that of the switch console port.

9. Load any helper files:

switch: load_helper

10. Start the file transfer by using the Xmodem Protocol.

switch: copy xmodem: flash:image_filename.bin

11. After the Xmodem request appears, use the appropriate command on the terminal-emulation software to start the

transfer and to copy the software image into flash memory.

12. Boot the newly downloaded Cisco IOS image.

switch:boot flash:image_filename.bin

13. Use the archive download-sw privileged EXEC command to download the software image to the switch.

14. Use the reload privileged EXEC command to restart the switch and to verify that the new software image is operating

properly.

15. Delete the flash:image_filename.bin file from the switch.

Recovering from a Lost or Forgotten Password

If you lose or forget your password, you can delete the switch password and set a new one.

Before you begin, make sure that:

You have physical access to the switch.

At least one switch port is enabled and is not connected to a device.

To delete the switch password and set a new one, follow these steps:

1. Press the Express Setup button until the SETUP LED blinks green and the LED of an available switch downlink port

blinks green.

If no switch downlink port is available for your PC or laptop connection, disconnect a device from one of the switch

downlink ports. Press the Express Setup button again until the SETUP LED and the port LED blink green.

2. Connect your PC or laptop to the port with the blinking green LED.

The SETUP LED and the switch downlink port LED stop blinking and stay solid green.

3. Press and hold the Express Setup button. Notice that the SETUP LED starts blinking green again. Continue holding

the button until the SETUP LED turns solid green (approximately 5 seconds). Release the Express Setup button

immediately.

This procedure deletes the password without affecting any other configuration settings. You can now access the switch

without a password through the console port or by using Device Manager.

4. Enter a new password through the device manager by using the Express Setup window or through the command

line interface by using the enable secret global configuration command.

1091

Troubleshooting

How to Troubleshoot

Recovering from Lost Cluster Member Connectivity

Some configurations can prevent the command switch from maintaining contact with member switches. If you are unable

to maintain management contact with a member, and the member switch is forwarding packets normally, check for these

conflicts:

A member switch (Catalyst 3750, Catalyst 3560, Catalyst 3550, Catalyst 3500 XL, Catalyst 2970, Catalyst 2960,

Catalyst 2950, Catalyst 2900 XL, Catalyst 2820, and Catalyst 1900 switch) cannot connect to the command switch

through a port that is defined as a network port.

Catalyst 3500 XL, Catalyst 2900 XL, Catalyst 2820, and Catalyst 1900 member switches must connect to the

command switch through a port that belongs to the same management VLAN.

A member switch (Catalyst 3750, Catalyst 3560, Catalyst 3550, Catalyst 2970, Catalyst 2960, Catalyst 2950,

Catalyst 3500 XL, Catalyst 2900 XL, Catalyst 2820, and Catalyst 1900 switch) connected to the command switch

through a secured port can lose connectivity if the port is disabled because of a security violation.

Executing Ping

If you attempt to ping a host in a different IP subnetwork, you must define a static route to the network or have IP routing

configured to route between those subnets.

IP routing is disabled by default on all switches. If you need to enable or configure IP routing, see Configuring Static IP

Unicast Routing, page 695

Beginning in privileged EXEC mode, use this command to ping another device on the network from the switch:

Command

Purpose

ping ip host | address

Pings a remote host through IP or by supplying the hostname or network

address.

Note: Other protocol keywords are available with the ping command, but they are not supported in this release.

This example shows how to ping an IP host:

Switch# ping 172.20.52.3

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echoes to 172.20.52.3, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms

Switch#

Table 73 on page 1093 describes the possible ping character output.

1092

Troubleshooting

How to Troubleshoot

Table 73

Ping Text Characters

Character

Description

Each exclamation point means receipt of a reply.

Each period means the network server timed out while waiting for a reply.

A destination unreachable error PDU was received.

A congestion experienced packet was received.

User interrupted test.

Unknown packet type.

Packet lifetime exceeded.

To end a ping session, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and release the Ctrl, Shift,

and 6 keys and then press the X key.

Executing IP Traceroute

Beginning in privileged EXEC mode, enter the following command to trace that the path packets take through the

network:

Command

Purpose

traceroute ip host

Traces the path that packets take through the network.

Note: Other protocol keywords are available with the traceroute privileged EXEC command, but they are not supported

in this release.

This example shows how to perform a traceroute to an IP host:

Switch# traceroute ip 171.9.15.10

Type escape sequence to abort.

Tracing the route to 171.69.115.10

1 172.2.52.1 0 msec 0 msec 4 msec

2 172.2.1.203 12 msec 8 msec 0 msec

3 171.9.16.6 4 msec 0 msec 0 msec

4 171.9.4.5 0 msec 4 msec 0 msec

5 171.9.121.34 0 msec 4 msec 4 msec

6 171.9.15.9 120 msec 132 msec 128 msec

7 171.9.15.10 132 msec 128 msec 128 msec

Switch#

The display shows the hop count, the IP address of the router, and the round-trip time in milliseconds for each of the

three probes that are sent.

Table 74 on page 1094 lists the characters that can appear in the traceroute command output.

1093

Troubleshooting

How to Troubleshoot

Table 74

Traceroute Text Characters

Character

Description

The probe timed out.

Unknown packet type.

Administratively unreachable. Usually, this output means that an access list is blocking traffic.

Host unreachable.

Network unreachable.

Protocol unreachable.

Source quench.

Port unreachable.

To end a trace in progress, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and release the Ctrl,

Shift, and 6 keys and then press the X key.

Running TDR and Displaying the Results

To run TDR, enter the test cable-diagnostics tdr interface interface-id privileged EXEC command:

To display the results, enter the show cable-diagnostics tdr interface interface-id privileged EXEC command.

Enabling Debugging on a Specific Feature

Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable.

For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions

with Cisco technical support staff. It is best to use debug commands during periods of lower network traffic and

fewer users. Debugging during these periods decreases the likelihood that increased debug command processing

overhead will affect system use.

All debug commands are entered in privileged EXEC mode, and most debug commands take no arguments. For

example, beginning in privileged EXEC mode, enter this command to enable the debugging for Switched Port Analyzer

(SPAN):

Switch# debug span-session

The switch continues to generate output until you enter the no form of the command.

If you enable a debug command and no output appears, consider these possibilities:

The switch might not be properly configured to generate the type of traffic you want to monitor. Use the show

running-config command to check its configuration.

Even if the switch is properly configured, it might not generate the type of traffic you want to monitor during the

particular period that debugging is enabled. Depending on the feature you are debugging, you can use commands

such as the TCP/IP ping command to generate network traffic.

To disable debugging of SPAN, enter this command in privileged EXEC mode:

Switch# no debug span-session

Alternately, in privileged EXEC mode, you can enter the undebug form of the command:

Switch# undebug span-session

To display the state of each debugging option, enter this command in privileged EXEC mode:

1094

Troubleshooting

Monitoring Information

Switch# show debugging

Enabling All-System Diagnostics

Beginning in privileged EXEC mode, enter this command to enable all-system diagnostics:

Switch# debug all

Caution: Because debugging output takes priority over other network traffic, and because the debug all privileged

EXEC command generates more output than any other debug command, it can severely diminish switch

performance or even render it unusable. In virtually all cases, it is best to use more specific debug commands.

The no debug all privileged EXEC command disables all diagnostic output. Using the no debug all command is a

convenient way to ensure that you have not accidentally left any debug commands enabled.

Redirecting Debug and Error Message Output

By default, the network server sends the output from debug commands and system error messages to the console. If

you use this default, you can use a virtual terminal connection to monitor debug output instead of connecting to the

console port.

Possible destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. The

syslog format is compatible with 4.3 Berkeley Standard Distribution (BSD) UNIX and its derivatives.

Note: Be aware that the debugging destination you use affects system overhead. Logging messages to the console

produces very high overhead, whereas logging messages to a virtual terminal produces less overhead. Logging

messages to a syslog server produces even less, and logging to an internal buffer produces the least overhead of any

method.

For more information about system message logging, see Configuring System Message Logging, page 545

Monitoring Information

Physical Path

You can display the physical path that a packet takes from a source device to a destination device by using one of these

privileged EXEC commands:

tracetroute mac [interface interface-id] {source-mac-address} [interface interface-id] {destination-mac-address}

[vlan vlan-id] [detail]

tracetroute mac ip {source-ip-address | source-hostname}{destination-ip-address | destination-hostname}

[detail]

SFP Module Status

You can check the physical or operational status of an SFP module by using the show interfaces transceiver privileged

EXEC command. This command shows the operational status, such as the temperature and the current for an SFP

module on a specific interface and the alarm status. You can also use the command to check the speed and the duplex

settings on an SFP module.

1095

Troubleshooting

Troubleshooting Examples

show platform forward Command

The output from the show platform forward privileged EXEC command provides some useful information about the

forwarding results if a packet entering an interface is sent through the system. Depending upon the parameters entered

about the packet, the output provides lookup table results and port maps used to calculate forwarding destinations,

bitmaps, and egress information.

Most of the information in the output from the command is useful mainly for technical support personnel, who have

access to detailed information about the switch application-specific integrated circuits (ASICs). However, packet

forwarding information can also be helpful in troubleshooting.

This is an example of the output from the show platform forward command on port 1 in VLAN 5 when the packet

entering that port is addressed to unknown MAC addresses. The packet should be flooded to all other ports in VLAN 5.

Switch# show platform forward GigabitEthernet1/17 vlan 5 1.1.1 2.2.2 ip 13.1.1.1 13.2.2.2 udp 10 20

Global Port Number:24, Asic Number:5

Src Real Vlan Id:5, Mapped Vlan Id:5

Ingress:

Lookup

Key-Used

Index-Hit A-Data

InptACL

40_0D020202_0D010101-00_40000014_000A0000

01FFA

03000000

L2Local

80_00050002_00020002-00_00000000_00000000

00C71

0000002B

Station Descriptor:02340000, DestIndex:0239, RewriteIndex:F005

==========================================

Egress:Asic 2, switch 1

Output Packets:

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

Packet 1

Lookup

Key-Used

Index-Hit A-Data

OutptACL 50_0D020202_0D010101-00_40000014_000A0000

01FFE

03000000

Port

Vlan

SrcMac

DstMac

Cos Dscpv

Gi1/17

0005 0001.0001.0001

0002.0002.0002

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

Packet 2

Lookup

Key-Used

Index-Hit A-Data

OutptACL 50_0D020202_0D010101-00_40000014_000A0000

01FFE

03000000

Port

Vlan

SrcMac

DstMac

Cos Dscpv

Gi1/17

0005 0001.0001.0001

0002.0002.0002

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

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

Packet 10

Lookup

Key-Used

Index-Hit A-Data

OutptACL 50_0D020202_0D010101-00_40000014_000A0000

01FFE

03000000

Packet dropped due to failed DEJA_VU Check on Gi1/0/2

Packet dropped due to failed DEJA_VU Check on Gi1/18

This is an example of the output when the packet coming in on port 1 in VLAN 5 is sent to an address already learned

on the VLAN on another port. It should be forwarded from the port on which the address was learned.

Switch# show platform forward GigabitEthernet1/17 vlan 5 1.1.1 0009.43a8.0145 ip 13.1.1.1 13.2.2.2 udp

10 20

Global Port Number:24, Asic Number:5

Src Real Vlan Id:5, Mapped Vlan Id:5

1096

Troubleshooting

Troubleshooting Examples

Ingress:

Lookup

Key-Used

Index-Hit A-Data

InptACL

40_0D020202_0D010101-00_40000014_000A0000

01FFA

03000000

L2Local

80_00050009_43A80145-00_00000000_00000000

00086

02010197

Station Descriptor:F0050003, DestIndex:F005, RewriteIndex:0003

==========================================

Egress:Asic 3, switch 1

Output Packets:

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

Packet 1

Lookup

Key-Used

Index-Hit A-Data

OutptACL 50_0D020202_0D010101-00_40000014_000A0000

01FFE

03000000

Port

Vlan

SrcMac

DstMac

Cos Dscpv

interface-id

0005 0001.0001.0001

0009.43A8.0145

This is an example of the output when the packet coming in on port 1 in VLAN 5 has a destination MAC address set to

the router MAC address in VLAN 5 and the destination IP address unknown. Because there is no default route set, the

packet should be dropped.

Switch# show platform forward GigabitEthernet1/17 vlan 5 1.1.1 03.e319.ee44 ip 13.1.1.1 13.2.2.2 udp 10

Global Port Number:24, Asic Number:5

Src Real Vlan Id:5, Mapped Vlan Id:5

Ingress:

Lookup

Key-Used

Index-Hit A-Data

InptACL

40_0D020202_0D010101-00_41000014_000A0000

01FFA

03000000

L3Local

00_00000000_00000000-90_00001400_0D020202

010F0

01880290

L3Scndr

12_0D020202_0D010101-00_40000014_000A0000

034E0

000C001D_00000000

Lookup Used:Secondary

Station Descriptor:02260000, DestIndex:0226, RewriteIndex:0000

This is an example of the output when the packet coming in on port 1 in VLAN 5 has a destination MAC address set to

the router MAC address in VLAN 5 and the destination IP address set to an IP address that is in the IP routing table. It

should be forwarded as specified in the routing table.

Switch# show platform forward GigabitEthernet1/17 vlan 5 1.1.1 03.e319.ee44 ip 110.1.5.5 16.1.10.5

Global Port Number:24, Asic Number:5

Src Real Vlan Id:5, Mapped Vlan Id:5

Ingress:

Lookup

Key-Used

Index-Hit A-Data

InptACL

40_10010A05_0A010505-00_41000014_000A0000

01FFA

03000000

L3Local

00_00000000_00000000-90_00001400_10010A05

010F0

01880290

L3Scndr

12_10010A05_0A010505-00_40000014_000A0000

01D28

30090001_00000000

Lookup Used:Secondary

Station Descriptor:F0070007, DestIndex:F007, RewriteIndex:0007

==========================================

Egress:Asic 3, switch 1

Output Packets:

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

Packet 1

Lookup

Key-Used

Index-Hit A-Data

OutptACL 50_10010A05_0A010505-00_40000014_000A0000

01FFE

03000000

Port

Vlan

SrcMac

DstMac

Cos Dscpv

1097

Troubleshooting

Additional References

Gi1/18

0007 XXXX.XXXX.0246

0009.43A8.0147

Additional References

The following sections provide references related to switch administration: