Configuring Interface Characteristics

C H A P T E R 9
Configuring Interface Characteristics
This chapter defines the types of interfaces on the Catalyst 3560 switch and describes how to configure
them.
The chapter has these sections:
• Understanding Interface Types, page 9-1
• Using Interface Configuration Mode, page 9-10
• Configuring Ethernet Interfaces, page 9-14
• Configuring Layer 3 Interfaces, page 9-22
• Configuring the System MTU, page 9-24
• Monitoring and Maintaining the Interfaces, page 9-25
Note For complete syntax and usage information for the commands used in this chapter, see the switch
command reference for this release and the online Cisco IOS Interface Command Reference,
Release 12.2.
Understanding Interface Types

This section describes the different types of interfaces supported by the switch with references to
chapters that contain more detailed information about configuring these interface types. The rest of the
chapter describes configuration procedures for physical interface characteristics.
These sections are included:
• Port-Based VLANs, page 9-2
• Switch Ports, page 9-2
• Routed Ports, page 9-4
• Switch Virtual Interfaces, page 9-4
• EtherChannel Port Groups, page 9-5
• Power over Ethernet Ports, page 9-5
• Connecting Interfaces, page 9-8
Catalyst 3560 Switch Software Configuration Guide

78-16404-02 9-1
Chapter 9 Configuring Interface Characteristics
Port-Based VLANs
A VLAN is a switched network that is logically segmented by function, team, or application, without
regard to the physical location of the users. For more information about VLANs, see Chapter 11,
“Configuring VLANs.” Packets received on a port are forwarded only to ports that belong to the same
VLAN as the receiving port. Network devices in different VLANs cannot communicate with one another
without a Layer 3 device to route traffic between the VLANs.
VLAN partitions provide hard firewalls for traffic in the VLAN, and each VLAN has its own MAC
address table. A VLAN comes into existence when a local port is configured to be associated with the
VLAN, when the VLAN Trunking Protocol (VTP) learns of its existence from a neighbor on a trunk, or
when a user creates a VLAN.
To configure normal-range VLANs (VLAN IDs 1 to 1005), use the vlan vlan-id global configuration
command to enter config-vlan mode or the vlan database privileged EXEC command to enter VLAN
database configuration mode. The VLAN configurations for VLAN IDs 1 to 1005 are saved in the VLAN
database. To configure extended-range VLANs (VLAN IDs 1006 to 4094), you must use config-vlan
mode with VTP mode set to transparent. Extended-range VLANs are not added to the VLAN database.
When VTP mode is transparent, the VTP and VLAN configuration is saved in the switch running
configuration, and you can save it in the switch startup configuration file by entering the copy
running-config startup-config privileged EXEC command.
Add ports to a VLAN by using the switchport interface configuration commands:
• Identify the interface.
• For a trunk port, set trunk characteristics, and if desired, define the VLANs to which it can belong.
• For an access port, set and define the VLAN to which it belongs.
• For a tunnel port, set and define the VLAN ID for the customer-specific VLAN tag. See Chapter 15,
“Configuring 802.1Q and Layer 2 Protocol Tunneling.”
Switch Ports
Switch ports are Layer 2-only interfaces associated with a physical port. Switch ports belong to one or
more VLANs. A switch port can be an access port, a trunk port, or a tunnel port. You can configure a port
as an access port or trunk port or let the Dynamic Trunking Protocol (DTP) operate on a per-port basis
to set the switchport mode by negotiating with the port on the other end of the link. You must manually
configure tunnel ports as part of an asymmetric link connected to an 802.1Q trunk port. Switch ports are
used for managing the physical interface and associated Layer 2 protocols and do not handle routing or
bridging.
Configure switch ports by using the switchport interface configuration commands. Use the switchport
command with no keywords to put an interface that is in Layer 3 mode into Layer 2 mode.
Note When you put an interface that is in Layer 3 mode into Layer 2 mode, the previous configuration
information related to the affected interface might be lost, and the interface is returned to its default
configuration.
For detailed information about configuring access port and trunk port characteristics, see Chapter 11,
“Configuring VLANs.” For more information about tunnel ports, see Chapter 15, “Configuring 802.1Q
and Layer 2 Protocol Tunneling.”

9-2 78-16404-02
Access Ports
An access port belongs to and carries the traffic of only one VLAN (unless it is configured as a voice
VLAN port). Traffic is received and sent in native formats with no VLAN tagging. Traffic arriving on
an access port is assumed to belong to the VLAN assigned to the port. If an access port receives a tagged
packet (Inter-Switch Link [ISL] or 802.1Q tagged), the packet is dropped, and the source address is not
learned.
Two types of access ports are supported:
• Static access ports are manually assigned to a VLAN.
• VLAN membership of dynamic access ports is learned through incoming packets. By default, a
dynamic access port is a member of no VLAN, and forwarding to and from the port is enabled only
when the VLAN membership of the port is discovered. Dynamic access ports on the switch are
assigned to a VLAN by a VLAN Membership Policy Server (VMPS). The VMPS can be a
Catalyst 6500 series switch; the Catalyst 3560 switch cannot be a VMPS server.
You can also configure an access port with an attached Cisco IP Phone to use one VLAN for voice traffic
and another VLAN for data traffic from a device attached to the phone. For more information about voice
VLAN ports, see Chapter 14, “Configuring Voice VLAN.”
Trunk Ports
A trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN
database. Two types of trunk ports are supported:
• In an ISL trunk port, all received packets are expected to be encapsulated with an ISL header, and
all transmitted packets are sent with an ISL header. Native (non-tagged) frames received from an
ISL trunk port are dropped.
• An IEEE 802.1Q trunk port supports simultaneous tagged and untagged traffic. An 802.1Q trunk
port is assigned a default Port VLAN ID (PVID), and all untagged traffic travels on the port default
PVID. All untagged traffic and tagged traffic with a NULL VLAN ID are assumed to belong to the
port default PVID. A packet with a VLAN ID equal to the outgoing port default PVID is sent
untagged. All other traffic is sent with a VLAN tag.
Although by default, a trunk port is a member of every VLAN known to the VTP, you can limit VLAN
membership by configuring an allowed list of VLANs for each trunk port. The list of allowed VLANs
does not affect any other port but the associated trunk port. By default, all possible VLANs (VLAN ID 1
to 4094) are in the allowed list. A trunk port can only become a member of a VLAN if VTP knows of
the VLAN and the VLAN is in the enabled state. If VTP learns of a new, enabled VLAN and the VLAN
is in the allowed list for a trunk port, the trunk port automatically becomes a member of that VLAN and
traffic is forwarded to and from the trunk port for that VLAN. If VTP learns of a new, enabled VLAN
that is not in the allowed list for a trunk port, the port does not become a member of the VLAN, and no
traffic for the VLAN is forwarded to or from the port.
For more information about trunk ports, see Chapter 11, “Configuring VLANs.”
Tunnel Ports
Tunnel ports are used in 802.1Q tunneling to segregate the traffic of customers in a service-provider
network from other customers who are using the same VLAN number. You configure an asymmetric link
from a tunnel port on a service-provider edge switch to an 802.1Q trunk port on the customer switch.
Packets entering the tunnel port on the edge switch, already 802.1Q-tagged with the customer VLANs,
are encapsulated with another layer of an 802.1Q tag (called the metro tag), containing a VLAN ID

78-16404-02 9-3
unique in the service-provider network, for each customer. The double-tagged packets go through the
service-provider network keeping the original customer VLANs separate from those of other customers.
At the outbound interface, also a tunnel port, the metro tag is removed, and the original VLAN numbers
from the customer network are retrieved.
Tunnel ports cannot be trunk ports or access ports and must belong to a VLAN unique to each customer.
For more information about tunnel ports, see Chapter 15, “Configuring 802.1Q and Layer 2 Protocol
Tunneling.”
Routed Ports
A routed port is a physical port that acts like a port on a router; it does not have to be connected to a
router. A routed port is not associated with a particular VLAN, as is an access port. A routed port behaves
like a regular router interface, except that it does not support VLAN subinterfaces. Routed ports can be
configured with a Layer 3 routing protocol. A routed port is a Layer 3 interface only and does not support
Layer 2 protocols, such as DTP and STP.
Configure routed ports by putting the interface into Layer 3 mode with the no switchport interface
configuration command. Then assign an IP address to the port, enable routing, and assign routing
protocol characteristics by using the ip routing and router protocol global configuration commands.
Note Entering a no switchport interface configuration command shuts down the interface and then re-enables
it, which might generate messages on the device to which the interface is connected. When you put an
interface that is in Layer 2 mode into Layer 3 mode, the previous configuration information related to
the affected interface might be lost.
The number of routed ports that you can configure is not limited by software. However, the
interrelationship between this number and the number of other features being configured might impact
CPU performance because of hardware limitations. See the “Configuring Layer 3 Interfaces” section on
page 9-22 for information about what happens when hardware resource limitations are reached.
For more information about IP unicast and multicast routing and routing protocols, see Chapter 33,
“Configuring IP Unicast Routing” and Chapter 35, “Configuring IP Multicast Routing.”
Note The standard multilayer image (SMI) supports static routing and the Routing Information Protocol
(RIP). For full Layer 3 routing or for fallback bridging, you must have the enhanced multilayer image
(EMI) installed on the switch.
Switch Virtual Interfaces

A switch virtual interface (SVI) represents a VLAN of switch ports as one interface to the routing or
bridging function in the system. Only one SVI can be associated with a VLAN, but you need to configure
an SVI for a VLAN only when you wish to route between VLANs, to fallback-bridge nonroutable
protocols between VLANs, or to provide IP host connectivity to the switch. By default, an SVI is created
for the default VLAN (VLAN 1) to permit remote switch administration. Additional SVIs must be
explicitly configured. SVIs provide IP host connectivity only to the system; in Layer 3 mode, you can
configure routing across SVIs.

9-4 78-16404-02
Although the switch supports a total or 1005 VLANs (and SVIs), the interrelationship between the
number of SVIs and routed ports and the number of other features being configured might impact CPU
performance because of hardware limitations. See the “Configuring Layer 3 Interfaces” section on
page 9-22 for information about what happens when hardware resource limitations are reached.
SVIs are created the first time that you enter the vlan interface configuration command for a VLAN
interface. The VLAN corresponds to the VLAN tag associated with data frames on an ISL or 802.1Q
encapsulated trunk or the VLAN ID configured for an access port. Configure a VLAN interface for each
VLAN for which you want to route traffic, and assign it an IP address. For more information, see the
“Manually Assigning IP Information” section on page 3-9.
Note When you create an SVI, it does not become active until it is associated with a physical port.
SVIs support routing protocols and bridging configurations. For more information about configuring IP
routing, see Chapter 33, “Configuring IP Unicast Routing,” Chapter 35, “Configuring IP Multicast
Routing,”and Chapter 37, “Configuring Fallback Bridging.”
Note The SMI supports static routing and RIP; for more advanced routing or for fallback bridging, you must
have the EMI installed on the switch.
EtherChannel Port Groups

EtherChannel port groups provide the ability to treat multiple switch ports as one switch port. These port
groups act as a single logical port for high-bandwidth connections between switches or between switches
and servers. An EtherChannel balances the traffic load across the links in the channel. If a link within
the EtherChannel fails, traffic previously carried over the failed link changes to the remaining links. You
can group multiple trunk ports into one logical trunk port, group multiple access ports into one logical
access port, group multiple tunnel ports into one logical tunnel port, or group multiple routed ports into
one logical routed port. Most protocols operate over either single ports or aggregated switch ports and
do not recognize the physical ports within the port group. Exceptions are the DTP, the Cisco Discovery
Protocol (CDP), and the Port Aggregation Protocol (PAgP), which operate only on physical ports.
When you configure an EtherChannel, you create a port-channel logical interface and assign an interface
to the EtherChannel. For Layer 3 interfaces, you manually create the logical interface by using the
interface port-channel global configuration command. Then you manually assign an interface to the
EtherChannel by using the channel-group interface configuration command. For Layer 2 interfaces, use
the channel-group interface configuration command to dynamically create the port-channel logical
interface. This command binds the physical and logical ports together. For more information, see
Chapter 32, “Configuring EtherChannels.”
Power over Ethernet Ports

Catalyst 3560 PoE-capable switch ports automatically supply power to these connected devices (if the
switch senses that there is no power on the circuit):
• Cisco pre-standard powered devices (such as Cisco IP Phones and Cisco Aironet access points)
• IEEE 802.3af-compliant powered devices

78-16404-02 9-5
On a 24-port PoE switch, each 10/100 or 10/100/1000 PoE port provides up to 15.4 W of power. On a
48-port PoE switch, any 24 of the 48 10/100 or 10/100/1000 PoE ports provide 15.4 W of power, or any
combination of ports provide an average of 7.7 W of power at the same time, up to a maximum switch
power output of 370 W.
A powered device can receive redundant power when it is connected to a PoE switch port and to an AC
power source.
Supported Protocols and Standards

The switch uses these protocols and standards to support PoE:
• CDP with power consumption—The powered device notifies the switch of the amount of power it
is consuming. The switch does not reply to the power-consumption messages. The switch can only
supply power to or remove power from the PoE port.
• Cisco intelligent power management—The powered device and the switch negotiate through
power-negotiation CDP messages for an agreed power-consumption level. The negotiation allows a
high-power Cisco powered device, which consumes more than 7 W, to operate at its highest power
mode. The powered device first boots up in low-power mode, consumes less than 7 W, and
negotiates to obtain enough power to operate in high-power mode. The device changes to
high-power mode only when it receives confirmation from the switch.
High-power devices can operate in low-power mode on switches that do not support
power-negotiation CDP.
Before Release 12.2(25)SE, Catalyst 3560 PoE-capable switches (without intelligent power
management support) caused high-power powered devices that supported intelligent power
management to operate in low-power mode. Devices in low-power mode are not fully functional.
Cisco intelligent power management is backward-compatible with CDP with power consumption;
the switch responds according to the CDP message that it receives. CDP is not supported on
third-party powered devices; therefore, the switch uses the IEEE classification to determine the
power usage of the device.
• IEEE 802.3af—The major features of this standard are powered-device discovery, power
administration, disconnect detection, and optional powered-device power classification. For more
information, see the standard.
Powered-Device Detection and Initial Power Allocation

The switch detects a Cisco pre-standard or an IEEE-compliant powered device when the PoE-capable
port is in the no-shutdown state, PoE is enabled (the default), and the connected device is not being
powered by an AC adaptor.
After device detection, the switch determines the device power requirements based on its type:
• A Cisco pre-standard powered device does not provide its power requirement when the switch
detects it, so the switch allocates 15.4 W as the initial allocation for power budgeting.
The initial power allocation is the maximum amount of power that a powered device requires. The
switch initially allocates this amount of power when it detects and powers the powered device. As
the switch receives CDP messages from the powered device and as the powered device negotiates
power levels with the switch through CDP power-negotiation messages, the initial power allocation
might be adjusted.

9-6 78-16404-02
• The switch classifies the detected IEEE device within a power consumption class. Based on the
available power in the power budget, the switch determines if a port can be powered. Table 9-1 lists
these levels.
Table 9-1 IEEE Power Classifications
Class Maximum Power Level Required from the Switch

0 (class status unknown) 15.4 W
1 4.0 W
2 7.0 W
3 15.4 W
4 (reserved for future use) Treat as Class 0
The switch monitors and tracks requests for power and grants power only when it is available. The switch
tracks its power budget (the amount of power available on the switch for PoE). The switch performs
power-accounting calculations when a port is granted or denied power to keep the power budget up to
date.
After power is applied to the port, the switch uses CDP to determine the actual power consumption
requirement of the connected Cisco powered devices, and the switch adjusts the power budget
accordingly. This does not apply to third-party PoE devices. The switch processes a request and either
grants or denies power. If the request is granted, the switch updates the power budget. If the request is
denied, the switch ensures that power to the port is turned off, generates a syslog message, and updates
the LEDs. Powered devices can also negotiate with the switch for more power.
If the switch detects a fault caused by an undervoltage, overvoltage, overtemperature, oscillator-fault, or
short-circuit condition, it turns off power to the port, generates a syslog message, and updates the power
budget and LEDs.
Power Management Modes

The switch supports these PoE modes:
• auto—The switch automatically detects if the connected device requires power. If the switch
discovers a powered device connected to the port and if the switch has enough power, it grants
power, updates the power budget, turns on power to the port on a first-come, first-served basis, and
updates the LEDs. For LED information, see the hardware installation guide.
If the switch has enough power for all the powered devices, they all come up. If enough power is
available for all powered devices connected to the switch, power is turned on to all devices. If there
is not enough available PoE, or if a device is disconnected and reconnected while other devices are
waiting for power, it cannot be determined which devices are granted or are denied power.
If granting power would exceed the system power budget, the switch denies power, ensures that
power to the port is turned off, generates a syslog message, and updates the LEDs. After power has
been denied, the switch periodically rechecks the power budget and continues to attempt to grant the
request for power.
If a device being powered by the switch is then connected to wall power, the switch might continue
to power the device. The switch might continue to report that it is still powering the device whether
the device is being powered by the switch or receiving power from an AC power source.
If a powered device is removed, the switch automatically detects the disconnect and removes power
from the port. You can connect a nonpowered device without damaging it.

78-16404-02 9-7
You can specify the maximum wattage that is allowed on the port. If the IEEE class maximum
wattage of the powered device is greater than the configured maximum value, the switch does not
provide power to the port. If the switch powers a powered device, but the powered device later
requests through CDP messages more than the configured maximum value, the switch removes
power to the port. The power that was allocated to the powered device is reclaimed into the global
power budget. If you do not specify a wattage, the switch delivers the maximum value. Use the auto
setting on any PoE port. The auto mode is the default setting.
• static—The switch pre-allocates power to the port (even when no powered device is connected) and
guarantees that power will be available for the port. The switch allocates the port configured
maximum wattage, and the amount is never adjusted through the IEEE class or by CDP messages
from the powered device. Because power is pre-allocated, any powered device that uses less than or
equal to the maximum wattage is guaranteed to be powered when it is connected to the static port.
The port no longer participates in the first-come, first-served model.
However, if the powered-device IEEE class is greater than the maximum wattage, the switch does
not supply power to it. If the switch learns through CDP messages that the powered device needs
more than the maximum wattage, the powered device is shutdown.
If you do not specify a wattage, the switch pre-allocates the maximum value. The switch powers the
port only if it discovers a powered device. Use the static setting on a high-priority interface.
• never—The switch disables powered-device detection and never powers the PoE port even if an
unpowered device is connected. Use this mode only when you want to make sure power is never
applied to a PoE-capable port, making the port a data-only port.
For information on configuring a PoE port, see the “Configuring a Power Management Mode on a PoE
Port” section on page 9-20.
Connecting Interfaces
Devices within a single VLAN can communicate directly through any switch. Ports in different VLANs
cannot exchange data without going through a routing device. With a standard Layer 2 switch, ports in
different VLANs have to exchange information through a router.
By using the switch with routing enabled, when you configure both VLAN 20 and VLAN 30 with an
SVI to which an IP address is assigned, packets can be sent from Host A to Host B directly through the
switch with no need for an external router (Figure 9-1).

9-8 78-16404-02
Figure 9-1 Connecting VLANs with the Catalyst 3560 Switch
Layer 3 switch
with routing enabled
172.20.128.1 SVI 1 SVI 2 172.20.129.1
Host A Host B
101350
VLAN 20 VLAN 30
When the EMI is running on the switch, the switch supports two methods of forwarding traffic between
interfaces: routing and fallback bridging. If the SMI is on the switch, only basic routing (static routing
and RIP) is supported. Whenever possible, to maintain high performance, forwarding is done by the
switch hardware. However, only IP version 4 packets with Ethernet II encapsulation can be routed in
hardware. Non-IP traffic and traffic with other encapsulation methods can be fallback-bridged
by hardware.
• The routing function can be enabled on all SVIs and routed ports. The switch routes only IP traffic.
When IP routing protocol parameters and address configuration are added to an SVI or routed port,
any IP traffic received from these ports is routed. For more information, see Chapter 33,
“Configuring IP Unicast Routing,” Chapter 35, “Configuring IP Multicast Routing,” and
Chapter 36, “Configuring MSDP.”
• Fallback bridging forwards traffic that the switch does not route or traffic belonging to a nonroutable
protocol, such as DECnet. Fallback bridging connects multiple VLANs into one bridge domain by
bridging between two or more SVIs or routed ports. When configuring fallback bridging, you assign
SVIs or routed ports to bridge groups with each SVI or routed port assigned to only one bridge
group. All interfaces in the same group belong to the same bridge domain. For more information,
see Chapter 37, “Configuring Fallback Bridging.”

78-16404-02 9-9
Using Interface Configuration Mode

The switch supports these interface types:
• Physical ports—including switch ports and routed ports
• VLANs—switch virtual interfaces
• Port-channels—EtherChannel of interfaces
You can also configure a range of interfaces (see the “Configuring a Range of Interfaces” section on
page 9-11).
To configure a physical interface (port), enter interface configuration mode, and specify the interface type,
module number, and switch port number.
• Type—Fast Ethernet (fastethernet or fa) for 10/100 Mbps Ethernet or Gigabit Ethernet
(gigabitethernet or gi) for 10/100/1000 Mbps Ethernet ports, or small form-factor pluggable (SFP)
module Gigabit Ethernet interfaces.
• Module number—The module or slot number on the switch (always 0 on the Catalyst 3560 switch).
• Port number—The interface number on the switch. The port numbers always begin at 1, starting with
the leftmost port when facing the front of the switch, for example, fastethernet0/1 or
gigabitethernet0/1. If there is more than one interface type (for example, 10/100 ports and SFP
module ports, the port numbers restart with the second interface type: gigabitethernet0/1.
You can identify physical interfaces by physically checking the interface location on the switch. You can
also use the Cisco IOS show privileged EXEC commands to display information about a specific
interface or all the interfaces on the switch. The remainder of this chapter primarily provides physical
interface configuration procedures.
Procedures for Configuring Interfaces

These general instructions apply to all interface configuration processes.
Step 1 Enter the configure terminal command at the privileged EXEC prompt:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)#
Step 2 Enter the interface global configuration command. Identify the interface type and the number of the
connector. In this example, Gigabit Ethernet port 1 is selected:
Switch(config)# interface gigabitethernet0/1
Switch(config-if)#
Note You do not need to add a space between the interface type and interface number. For example,
in the preceding line, you can specify either gigabitethernet 0/1, gigabitethernet0/1, gi 0/1, or
gi0/1.
Step 3 Follow each interface command with the interface configuration commands that the interface requires.
The commands that you enter define the protocols and applications that will run on the interface. The
commands are collected and applied to the interface when you enter another interface command or enter
end to return to privileged EXEC mode.

9-10 78-16404-02
You can also configure a range of interfaces by using the interface range or interface range macro
global configuration commands. Interfaces configured in a range must be the same type and must be
configured with the same feature options.
Step 4 After you configure an interface, verify its status by using the show privileged EXEC commands listed
in the “Monitoring and Maintaining the Interfaces” section on page 9-25.
Enter the show interfaces privileged EXEC command to see a list of all interfaces on or configured for
the switch. A report is provided for each interface that the device supports or for the specified interface.
Configuring a Range of Interfaces

You can use the interface range global configuration command to configure multiple interfaces with the
same configuration parameters. When you enter the interface range configuration mode, all command
parameters that you enter are attributed to all interfaces within that range until you exit this mode.
Beginning in privileged EXEC mode, follow these steps to configure a range of interfaces with the
same parameters:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface range {port-range | macro Specify the range of interfaces (VLANs or physical ports) to be
macro_name} configured, and enter interface range configuration mode.
• You can use the interface range command to configure up to five
port ranges or a previously defined macro.
• The macro variable is explained in the “Configuring and Using
Interface Range Macros” section on page 9-12.
• In a comma-separated port-range, you must enter the interface
type for each entry and enter spaces before and after the comma.
• In a hyphen-separated port-range, you do not need to re-enter the
interface type, but you must enter a space before the hyphen.
Step 3 You can now use the normal configuration commands to apply the
configuration parameters to all interfaces in the range.
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces [interface-id] Verify the configuration of the interfaces in the range.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
When using the interface range global configuration command, note these guidelines:
• Valid entries for port-range:
– vlan vlan-ID - vlan-ID, where the VLAN ID is 1 to 4094
– fastethernet module/{first port} - {last port}, where the module is always 0
– gigabitethernet module/{first port} - {last port}, where the module is always 0

78-16404-02 9-11
– port-channel port-channel-number - port-channel-number, where the port-channel-number

is 1 to 48
Note When you use the interface range command with port channels, the first and last port
channel number must be active port channels.
• You must add a space between the first interface number and the hyphen when using the
interface range command. For example, the command interface range fastgigabitethernet0/1 - 4
is a valid range; the command interface range fastgigabitethernet0/1-4 is not a valid range.
• The interface range command only works with VLAN interfaces that have been configured with
the interface vlan command. The show running-config privileged EXEC command displays the
configured VLAN interfaces. VLAN interfaces not displayed by the show running-config
command cannot be used with the interface range command.
• All interfaces defined as in a range must be the same type (all Fast Ethernet ports, all Gigabit
Ethernet ports, all EtherChannel ports, or all VLANs), but you can enter multiple ranges in a
command.
This example shows how to use the interface range global configuration command to set the speed on
ports 1 to 4 to 100 Mbps:
Switch(config)# interface range gigabittethernet0/1 - 4
Switch(config-if-range)# speed 100
This example shows how to use a comma to add different interface type strings to the range to enable
Fast Ethernet ports 1 to 3 and Gigabit Ethernet ports 1 and 2 to receive flow control pause frames:
Switch(config)# interface range fastethernet0/1 - 3 , gigabitethernet0/1 - 2
Switch(config-if-range)# flowcontrol receive on
If you enter multiple configuration commands while you are in interface range mode, each command is
executed as it is entered. The commands are not batched together and executed after you exit interface
range mode. If you exit interface range configuration mode while the commands are being executed,
some commands might not be executed on all interfaces in the range. Wait until the command prompt
reappears before exiting interface range configuration mode.
Configuring and Using Interface Range Macros

You can create an interface range macro to automatically select a range of interfaces for configuration.
Before you can use the macro keyword in the interface range macro global configuration command
string, you must use the define interface-range global configuration command to define the macro.

9-12 78-16404-02
Beginning in privileged EXEC mode, follow these steps to define an interface range macro:
Command Purpose
Step 2 define interface-range macro_name Define the interface-range macro, and save it in NVRAM.
interface-range
• The macro_name is a 32-character maximum character string.
• A macro can contain up to five comma-separated interface ranges.
• Each interface-range must consist of the same port type.
Step 3 interface range macro macro_name Select the interface range to be configured using the values saved in
the interface-range macro called macro_name.
You can now use the normal configuration commands to apply the
configuration to all interfaces in the defined macro.
Step 5 show running-config | include define Show the defined interface range macro configuration.
Use the no define interface-range macro_name global configuration command to delete a macro.
When using the define interface-range global configuration command, note these guidelines:
• Valid entries for interface-range:
– vlan vlan-ID - vlan-ID, where the VLAN ID is 1 to 4094
– fastethernet module/{first port} - {last port}, where the module is always 0
– gigabitethernet module/{first port} - {last port}, where the module is always 0
– port-channel port-channel-number - port-channel-number, where the port-channel-number
is 1 to 48.
Note When you use the interface ranges with port channels, the first and last port channel
number must be active port channels.
• You must add a space between the first interface number and the hyphen when entering an
interface-range. For example, fastgigabitethernet0/1 - 4 is a valid range; fastgigabitethernet0/1-4
is not a valid range.
• The VLAN interfaces must have been configured with the interface vlan command. The show
running-config privileged EXEC command displays the configured VLAN interfaces. VLAN
interfaces not displayed by the show running-config command cannot be used as interface-ranges.
• All interfaces defined as in a range must be the same type (all Fast Ethernet ports, all Gigabit
Ethernet ports, all EtherChannel ports, or all VLANs), but you can combine multiple interface types
in a macro.
This example shows how to define an interface-range named enet_list to include ports 1 and 2 and to
verify the macro configuration:
Switch(config)# define interface-range enet_list gigabitethernet0/1 - 2
Switch(config)# end

78-16404-02 9-13
Configuring Ethernet Interfaces
Switch# show running-config | include define

define interface-range enet_list GigabitEthernet0/1 - 2
This example shows how to create a multiple-interface macro named macro1:

Switch(config)# define interface-range macro1 fastethernet0/1 - 2, gigabitethernet0/1 - 2
Switch(config)# end
This example shows how to enter interface range configuration mode for the interface-range
macro enet_list:
Switch(config)# interface range macro enet_list
Switch(config-if-range)#
This example shows how to delete the interface-range macro enet_list and to verify that it was deleted.
Switch(config)# no define interface-range enet_list
Switch(config)# end
Switch# show run | include define
Switch#

These sections describe the default interface configuration and the optional features that you can
configure on most physical interfaces:
• Default Ethernet Interface Configuration, page 9-14
• Configuring Interface Speed and Duplex Mode, page 9-16
• Configuring IEEE 802.3z Flow Control, page 9-18
• Configuring Auto-MDIX on an Interface, page 9-19
• Configuring a Power Management Mode on a PoE Port, page 9-20
• Adding a Description for an Interface, page 9-22
Default Ethernet Interface Configuration

Table 9-2 shows the Ethernet interface default configuration, including some features that apply only to
Layer 2 interfaces. For more details on the VLAN parameters listed in the table, see Chapter 11,
“Configuring VLANs.” For details on controlling traffic to the port, see Chapter 23, “Configuring
Port-Based Traffic Control.”
Note To configure Layer 2 parameters, if the interface is in Layer 3 mode, you must enter the switchport
interface configuration command without any parameters to put the interface into Layer 2 mode. This
shuts down the interface and then re-enables it, which might generate messages on the device to which
the interface is connected. When you put an interface that is in Layer 3 mode into Layer 2 mode, the
previous configuration information related to the affected interface might be lost, and the interface is
returned to its default configuration.

9-14 78-16404-02
Table 9-2 Default Layer 2 Ethernet Interface Configuration
Feature Default Setting

Operating mode Layer 2 or switching mode (switchport command).
Allowed VLAN range VLANs 1 – 4094.
Default VLAN (for access ports) VLAN 1 (Layer 2 interfaces only).
Native VLAN (for 802.1Q trunks) VLAN 1 (Layer 2 interfaces only).
VLAN trunking Switchport mode dynamic auto (supports DTP)
(Layer 2 interfaces only).
Port enable state All ports are enabled.
Port description None defined.
Speed Autonegotiate.
Duplex mode Autonegotiate.
Flow control Flow control is set to receive: off. It is always off for sent packets.
EtherChannel (PAgP) Disabled on all Ethernet ports. See Chapter 32, “Configuring
EtherChannels.”
Port blocking (unknown multicast Disabled (not blocked) (Layer 2 interfaces only). See the
and unknown unicast traffic) “Configuring Port Blocking” section on page 23-6.
Broadcast, multicast, and unicast Disabled. See the “Default Storm Control Configuration” section
storm control on page 23-3.
Protected port Disabled (Layer 2 interfaces only). See the “Configuring Protected
Ports” section on page 23-5.
Port security Disabled (Layer 2 interfaces only). See the “Default Port Security
Configuration” section on page 23-10.
Port Fast Disabled.
Auto-MDIX Enabled.
Note The switch might not support a pre-standard powered
device—such as Cisco IP phones and access points that do
not fully support IEEE 802.3af—if that powered device is
connected to the switch through a crossover cable. This is
regardless of whether Auto-MIDX is enabled on the
switch port.
Power over Ethernet (PoE) Enabled (auto).

78-16404-02 9-15
Configuring Interface Speed and Duplex Mode

Ethernet interfaces on the switch operate at 10, 100, or 1000 Mbps and in either full- or half-duplex
mode. In full-duplex mode, two stations can send and receive traffic at the same time. Normally,
10-Mbps ports operate in half-duplex mode, which means that stations can either receive or send traffic.
Switch models include combinations of Fast Ethernet (10/100-Mbps) ports or Gigabit Ethernet
(10/100/1000-Mbps) ports, and small form-factor pluggable (SFP) module slots supporting Gigabit SFP
modules.
• You can configure interface speed on Fast Ethernet (10/100-Mbps) and Gigabit Ethernet
(10/100/1000-Mbps) ports. You can configure duplex mode to full, half, or autonegotiate on Fast
Ethernet interfaces. You can configure Gigabit Ethernet ports to full-duplex mode or to
autonegotiate; you cannot configure half-duplex mode on Gigabit Ethernet ports.
• You cannot configure speed on SFP module ports, but you can configure speed to not negotiate
(nonegotiate) if connected to a device that does not support autonegotiation. However, when a
1000BASE-T SFP module is in the SFP module port, you can configure speed as 10, 100, or 1000
Mbps, or auto.
• You cannot configure duplex mode on SFP module ports unless a Cisco 1000BASE-T SFP module
or a Cisco 100BASE-FX MMF SFP module is in the port. All other SFP modules operate only in
full-duplex mode.
– When a Cisco1000BASE-T SFP module is in the SFP module port, you can configure duplex
mode to auto or full.
– When a Cisco100BASE-FX SFP module is in the SFP module port, you can configure duplex
mode to half or full.
Note Half-duplex mode is supported on Gigabit Ethernet interfaces; however you cannot
configure these interfaces to operate in half-duplex mode.
These sections describe how to configure the interface speed and duplex mode:
• Configuration Guidelines, page 9-16
• Setting the Interface Speed and Duplex Parameters, page 9-17
Configuration Guidelines
When configuring an interface speed and duplex mode, note these guidelines:
• If both ends of the line support autonegotiation, we highly recommend the default setting of auto
negotiation.
• If one interface supports autonegotiation and the other end does not, configure duplex and speed on
both interfaces; do not use the auto setting on the supported side.
• You cannot configure duplex mode on SFP module ports; they operate in full-duplex mode.
However, when a Cisco1000BASE-T SFP module is inserted in an SFP module port, you can
configure the duplex mode to full or auto, and half-duplex mode is supported with the auto
configuration. When a Cisco 100BASE-FX SFP module is in the SFP module port, you can
configure duplex mode to half or full. Although the auto keyword is available, it puts the interface
in half-duplex mode (the default for this SFP module) because the 100BASE-FX SFP module does
not support autonegotiation.

9-16 78-16404-02
• You cannot configure speed on SFP module ports, except to nonegotiate. However, when a
1000BASE-T SFP module is in the SFP module port, the speed can be configured to 10, 100, 1000,
or auto, but not nonegotiate.
• When STP is enabled and a port is reconfigured, the switch can take up to 30 seconds to check for
loops. The port LED is amber while STP reconfigures.
Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the
interface during the reconfiguration.
Setting the Interface Speed and Duplex Parameters

Beginning in privileged EXEC mode, follow these steps to set the speed and duplex mode for a physical
interface:
Command Purpose
Step 2 interface interface-id Specify the physical interface to be configured, and enter interface
configuration mode.
Step 3 speed {10 | 100 | 1000 | auto [10 | 100 | Enter the appropriate speed parameter for the interface:
1000] | nonegotiate}
• Enter 10, 100, or 1000 to set a specific speed for the interface.
The 1000 keyword is available only for 10/100/1000 Mbps ports
or SFP module ports with a 1000BASE-T SFP module.
• Enter auto to enable the interface to autonegotiate speed with the
device connected to the interface. If you use the 10, 100, or 1000
keywords with the auto keyword, the port only autonegotiates at
the specified speeds.
• The nonegotiate keyword is available only for SFP module ports.
SFP module ports operate only at 1000 Mbps but can be
configured to not negotiate if connected to a device that does not
support autonegotiation.
Note When a Cisco1000BASE-T SFP module is in the SFP module
port, the speed can be configured to 10, 100, 1000, or auto,
but not nonegotiate.

78-16404-02 9-17
Command Purpose
Step 4 duplex {auto | full | half} Enter the duplex parameter for the interface.
Enable half-duplex mode (for interfaces operating only at 10 or
100 Mbps). You cannot configure half-duplex mode for interfaces
operating at 1000 Mbps.
This command is not available on SFP module ports with these
exceptions:
• If a Cisco 1000BASE-T SFP module is inserted, you can
configure duplex to auto or full.
• If a Cisco 100BASE-FX SFP module is inserted, you can
configure duplex to full or half. Although the auto keyword is
available, it puts the interface in half-duplex mode (the default)
Beginning with Cisco IOS Release 12.2(20)SE1, you can configure
the duplex setting when the speed is set to auto.
Step 6 show interfaces interface-id Display the interface speed and duplex mode configuration.
Use the no speed and no duplex interface configuration commands to return the interface to the default
speed and duplex settings (autonegotiate). To return all interface settings to the defaults, use the default
interface interface-id interface configuration command.
This example shows how to set the interface speed to 10 Mbps and the duplex mode to half on a
10/100 Mbps port:
Switch(config)# interface fasttethernet0/3
Switch(config-if)# speed 10
Switch(config-if)# duplex half
This example shows how to set the interface speed to 100 Mbps on a 10/100/1000 Mbps port:
Switch(config-if)# speed 100
Configuring IEEE 802.3z Flow Control

Flow control enables connected Ethernet ports to control traffic rates during congestion by allowing
congested nodes to pause link operation at the other end. If one port experiences congestion and cannot
receive any more traffic, it notifies the other port to stop sending until the condition clears by sending a
pause frame. Upon receipt of a pause frame, the sending device stops sending any data packets, which
prevents any loss of data packets during the congestion period.
Note Catalyst 3560 ports can receive3, but not send, pause frames.
You use the flowcontrol interface configuration command to set the interface’s ability to receive pause
frames to on, off, or desired. The default state is off.

9-18 78-16404-02
When set to desired, an interface can operate with an attached device that is required to send
flow-control packets or with an attached device that is not required to but can send flow-control packets.
These rules apply to flow control settings on the device:
• receive on (or desired): The port cannot send pause frames but can operate with an attached device
that is required to or can send pause frames; the port can receive pause frames.
• receive off: Flow control does not operate in either direction. In case of congestion, no indication is
given to the link partner, and no pause frames are sent or received by either device.
Note For details on the command settings and the resulting flow control resolution on local and remote ports,
see the flowcontrol interface configuration command in the command reference for this release.
Beginning in privileged EXEC mode, follow these steps to configure flow control on an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 interface interface-id Specify the physical interface to be configured, and enter
interface configuration mode.
Step 3 flowcontrol {receive} {on | off | desired} Configure the flow control mode for the port.
Step 5 show interfaces interface-id Verify the interface flow control settings.
To disable flow control, use the flowcontrol receive off interface configuration command.
This example shows how to turn on flow control on a port:
Switch(config-if)# flowcontrol receive on
Switch(config-if)# end
Configuring Auto-MDIX on an Interface

When automatic medium-dependent interface crossover (Auto-MDIX) is enabled on an interface, the
interface automatically detects the required cable connection type (straight through or crossover) and
configures the connection appropriately. When connecting switches without the Auto-MDIX feature,
you must use straight-through cables to connect to devices such as servers, workstations, or routers and
crossover cables to connect to other switches or repeaters. With Auto-MDIX enabled, you can use either
type of cable to connect to other devices, and the interface automatically corrects for any incorrect
cabling. For more information about cabling requirements, see the hardware installation guide.
Auto-MDIX is enabled by default. When you enable Auto-MDIX, you must also set the speed and duplex
on the interface to auto in order for the feature to operate correctly. Auto-MDIX is supported on all
10/100 and 10/100/1000 Mbps interfaces and on Cisco 10/100/1000 BASE-T/TX SFP module interfaces.
It is not supported on 1000 BASE-SX or -LX SFP module interfaces.
Table 9-3 shows the link states that results from Auto-MDIX settings and correct and incorrect cabling.

78-16404-02 9-19
Table 9-3 Link Conditions and Auto-MDIX Settings
Local Side Auto-MDIX Remote Side Auto-MDIX With Correct Cabling With Incorrect Cabling
On On Link up Link up
On Off Link up Link up
Off On Link up Link up
Off Off Link up Link down
Beginning in privileged EXEC mode, follow these steps to configure Auto-MDIX on an interface:
Command Purpose
Step 1 configure terminal Enter global configuration mode
Step 2 interface interface-id Specify the physical interface to be configured, and enter interface
configuration mode.
Step 3 speed auto Configure the interface to autonegotiate speed with the connected device.
Step 4 duplex auto Configure the interface to autonegotiate duplex mode with the connected
device.
Step 5 mdix auto Enable Auto-MDIX on the interface.
Step 7 show controllers ethernet-controller Verify the operational state of the Auto-MDIX feature on the interface.
interface-id phy
To disable Auto-MDIX, use the no mdix auto interface configuration command.

This example shows how to enable Auto-MDIX on a port:
Switch(config)# interface fastgigabitethernet0/1
Switch(config-if)# speed auto
Switch(config-if)# duplex auto
Switch(config-if)# mdix auto
Configuring a Power Management Mode on a PoE Port

For most situations, the default configuration (auto mode) works well, providing plug-and-play
operation. No further configuration is required. However, use the following procedure to give a PoE port
a higher priority, to make it data-only, or to specify a maximum wattage to disallow high-power powered
devices on a port.

9-20 78-16404-02
Note When you make PoE configuration changes, the port being configured drops power. Depending on the
new configuration, the state of the other PoE ports, and the state of the power budget, the port might not
be powered up again. For example, port 1 is in the auto and on state, and you configure it for static mode.
The switch removes power from port 1, detects the powered device, and repowers the port. If port 1 is
in the auto and on state and you configure it with a maximum wattage of 10 W, the switch removes power
from the port and then redetects the powered device. The switch repowers the port only if the powered
device is a Class 1, Class 2, or a Cisco-only powered device.
Beginning in privileged EXEC mode, follow these steps to configure a power management mode on a
PoE-capable port:
Command Purpose
Step 2 interface interface-id Specify the physical port to be configured, and enter interface
configuration mode.
Step 3 power inline {auto [max max-wattage] | Configure the PoE mode on the port. The keywords have these meanings:
never | static [max max-wattage]}
• auto—Enable powered-device detection. If enough power is
available, automatically allocate power to the PoE port after device
detection. This is the default setting.
• (Optional) max max-wattage—Limit the power allowed on the port.
The range is 4000 to 15400 milliwatts. If no value is specified, the
maximum is allowed (15400 milliwatts).
• never—Disable device detection, and disable power to the port.
Note If a port has a Cisco powered device connected to it, do not use
the power inline never command to configure the port. A false
link-up can occur, placing the port into an error-disabled state.
• static—Enable powered-device detection. Pre-allocate (reserve)

power for a port before the switch discovers the powered device. The
switch reserves power for this port even when no device is connected
and guarantees that power will be provided upon device detection.
The switch allocates power to a port configured in static mode before it
allocates power to a port configured in auto mode.
Step 5 show power inline [interface-id] Display PoE status for a switch or for the specified interface.
For information about the output of the show power inline user EXEC command, see the command
reference for this release. For more information about PoE-related commands, see the “Troubleshooting
Power over Ethernet Switch Ports” section on page 38-12. For information about configuring voice
VLAN, see Chapter 14, “Configuring Voice VLAN.”

78-16404-02 9-21
Configuring Layer 3 Interfaces
Adding a Description for an Interface

You can add a description about an interface to help you remember its function. The description appears
in the output of these privileged EXEC commands: show configuration, show running-config, and
show interfaces.
Beginning in privileged EXEC mode, follow these steps to add a description for an interface:
Command Purpose
Step 2 interface interface-id Specify the interface for which you are adding a description, and enter
interface configuration mode.
Step 3 description string Add a description (up to 240 characters) for an interface.
Step 5 show interfaces interface-id description Verify your entry.
or
show running-config
Use the no description interface configuration command to delete the description.

This example shows how to add a description on a port and how to verify the description:
Switch# config terminal
Switch(config-if)# description Connects to Marketing
Switch# show interfaces gigabitethernet0/2 description
Interface Status Protocol Description
Gi0/2 admin down down Connects to Marketing

The Catalyst 3560 switch supports these types of Layer 3 interfaces:
• SVIs: You should configure SVIs for any VLANs for which you want to route traffic. SVIs are
created when you enter a VLAN ID following the interface vlan global configuration command. To
delete an SVI, use the no interface vlan global configuration command.
Note When you create an SVI, it does not become active until it is associated with a physical port.
For information about assigning Layer 2 ports to VLANs, see Chapter 11, “Configuring
VLANs.”
• Routed ports: Routed ports are physical ports configured to be in Layer 3 mode by using the no
switchport interface configuration command.
• Layer 3 EtherChannel ports: EtherChannel interfaces made up of routed ports.
EtherChannel port interfaces are described in Chapter 32, “Configuring EtherChannels.”

9-22 78-16404-02
A Layer 3 switch can have an IP address assigned to each routed port and SVI.
There is no defined limit to the number of SVIs and routed ports that can be configured in a switch.
However, the interrelationship between the number of SVIs and routed ports and the number of other
features being configured might have an impact on CPU usage because of hardware limitations. If the
switch is using maximum hardware resources, attempts to create a routed port or SVI have these results:
• If you try to create a new routed port, the switch generates a message that there are not enough
resources to convert the interface to a routed port, and the interface remains as a switchport.
• If you try to create an extended-range VLAN, an error message is generated, and the extended-range
VLAN is rejected.
• If the switch is notified by VLAN Trunking Protocol (VTP) of a new VLAN, it sends a message that
there are not enough hardware resources available and shuts down the VLAN. The output of the
show vlan user EXEC command shows the VLAN in a suspended state.
• If the switch attempts to boot up with a configuration that has more VLANs and routed ports than
hardware can support, the VLANs are created, but the routed ports are shut down, and the switch
sends a message that this was due to insufficient hardware resources.
All Layer 3 interfaces require an IP address to route traffic. This procedure shows how to configure an
interface as a Layer 3 interface and how to assign an IP address to an interface.
Note If the physical port is in Layer 2 mode (the default), you must enter the no switchport interface
configuration command to put the interface into Layer 3 mode. Entering a no switchport command
disables and then re-enables the interface, which might generate messages on the device to which the
interface is connected. Furthermore, when you put an interface that is in Layer 2 mode into Layer 3
mode, the previous configuration information related to the affected interface might be lost, and the
interface is returned to its default configuration
Beginning in privileged EXEC mode, follow these steps to configure a Layer 3 interface:
Command Purpose
Step 2 interface {{fastethernet | gigabitethernet} interface-id} Specify the interface to be configured as a Layer 3
| {vlan vlan-id} | {port-channel port-channel-number} interface, and enter interface configuration mode.
Step 3 no switchport For physical ports only, enter Layer 3 mode.
Step 4 ip address ip_address subnet_mask Configure the IP address and IP subnet.
Step 5 no shutdown Enable the interface.
Step 7 show interfaces [interface-id] Verify the configuration.
show ip interface [interface-id]
show running-config interface [interface-id]
To remove an IP address from an interface, use the no ip address interface configuration command.

78-16404-02 9-23
Configuring the System MTU
This example shows how to configure a port as a routed port and to assign it an IP address:
Switch(config-if)# no switchport
Switch(config-if)# ip address 192.20.135.21 255.255.255.0
Switch(config-if)# no shutdown
Configuring the System MTU

The default maximum transmission unit (MTU) size for frames received and transmitted on all interfaces
on the switch is 1500 bytes. You can increase the MTU size for all interfaces operating at 10 or 100 Mbps
by using the system mtu global configuration command. You can increase the MTU size to support
jumbo frames on all Gigabit Ethernet interfaces by using the system mtu jumbo global configuration
command. Gigabit Ethernet ports are not affected by the system mtu command; 10/100 ports are not
affected by the system jumbo mtu command.
You cannot set the MTU size for an individual interface; you set it for all 10/100 or all Gigabit Ethernet
interfaces on the switch. When you change the MTU size, you must reset the switch before the new
configuration takes effect.
The size of frames that can be received by the switch CPU is limited to 1992 bytes, no matter what value
was entered with the system mtu or system mtu jumbo commands. Although frames that are forwarded
or routed typically are not received by the CPU, in some cases packets are sent to the CPU, such as traffic
sent to control traffic, SNMP, Telnet, or routing protocols.
Routed packets are subjected to MTU checks on the egress ports. The MTU value used for routed ports
is derived from the system mtu configured value (not the system mtu jumbo value). That is, the routed
MTU is never greater than the system MTU for any VLAN. The system MTU value is used by routing
protocols when negotiating adjacencies and the MTU of the link. For example Open Shortest Path First
(OSPF) protocol uses this MTU value before setting up an adjacency with a peer router. To view the
MTU value for routed packets for a specific VLAN, use the show platform port-asic mvid privileged
EXEC command.
Note If Layer 2 Gigabit Ethernet interfaces are configured to accept frames greater than the 10/100 interfaces,
jumbo frames ingressing on a Layer 2 Gigabit Ethernet interface and egressing on a Layer 2 10/100
interface are dropped.
Beginning in privileged EXEC mode, follow these steps to change MTU size for all 10/100 or Gigabit
Ethernet interfaces:
Command Purpose
Step 2 system mtu bytes (Optional) Change the MTU size for all interfaces on
the switch that are operating at 10 or 100 Mbps. The
range is 1500 to 1546 bytes; the default is 1500 bytes.
Step 3 system mtu jumbo bytes (Optional) Change the MTU size for all Gigabit
Ethernet interfaces on the switch. The range is 1500 to
9000 bytes; the default is 1500 bytes.

9-24 78-16404-02
Monitoring and Maintaining the Interfaces
Command Purpose
Step 5 copy running-config startup-config Save your entries in the configuration file.
Step 6 reload Reload the operating system.
If you enter a value that is outside the allowed range for the specific type of interface, the value is not
accepted.
Once the switch reloads, you can verify your settings by entering the show system mtu privileged EXEC
command.
This example shows how to set the maximum packet size for a Gigabit Ethernet port to 1800 bytes:
Switch(config)# system jumbo mtu 1800
Switch(config)# exit
Switch# reload
This example shows the response when you try to set Gigabit Ethernet interfaces to an out-of-range
number:
Switch(config)# system mtu jumbo 25000
^
% Invalid input detected at '^' marker.

You can perform the tasks in these sections to monitor and maintain interfaces:
• Monitoring Interface Status, page 9-25
• Clearing and Resetting Interfaces and Counters, page 9-26
• Shutting Down and Restarting the Interface, page 9-27
Monitoring Interface Status

Commands entered at the privileged EXEC prompt display information about the interface, including
the versions of the software and the hardware, the configuration, and statistics about the interfaces.
Table 9-4 lists some of these interface monitoring commands. (You can display the full list of show
commands by using the show ? command at the privileged EXEC prompt.) These commands are fully
described in the Cisco IOS Interface Command Reference, Release 12.2.
Table 9-4 Show Commands for Interfaces
Command Purpose
show interfaces [interface-id] Display the status and configuration of all interfaces or a specific
interface.
show interfaces interface-id status [err-disabled] Display interface status or a list of interfaces in an error-disabled state.
show interfaces [interface-id] switchport Display administrative and operational status of switching
(nonrouting) ports. You can use this command to find out if a port is in
routing or switching mode.
show interfaces [interface-id] description Display the description configured on an interface or all interfaces and
the interface status.

78-16404-02 9-25
Table 9-4 Show Commands for Interfaces (continued)
Command Purpose
show ip interface [interface-id] Display the usability status of all interfaces configured for IP routing
or the specified interface.
show interface [interface-id] stats Display the input and output packets by the switching path for the
interface.
show interfaces transceiver properties (Optional) Display speed, duplex, and inline power settings on the
interface.
show interfaces transceiver calibration properties (Optional) Display temperature, voltage, or amount of current on the
interface.
show interfaces [interface-id] [{transceiver Display physical and operational status about an SFP module.
calibration | properties | detail}] module number]
show running-config interface [interface-id] Display the running configuration in RAM for the interface.
show version Display the hardware configuration, software version, the names and
sources of configuration files, and the boot images.
show controllers ethernet-controller interface-id Verify the operational state of the Auto-MDIX feature on the interface.
phy
show power inline [interface-id] Display PoE status for a switch or for an interface.
Clearing and Resetting Interfaces and Counters

Table 9-5 lists the privileged EXEC mode clear commands that you can use to clear counters and reset
interfaces.
Table 9-5 Clear Commands for Interfaces
Command Purpose
clear counters [interface-id] Clear interface counters.
clear interface interface-id Reset the hardware logic on an interface.
clear line [number | console 0 | vty number] Reset the hardware logic on an asynchronous serial line.
To clear the interface counters shown by the show interfaces privileged EXEC command, use the clear
counters privileged EXEC command. The clear counters command clears all current interface counters
from the interface unless optional arguments are specified to clear only a specific interface type from a
specific interface number.
Note The clear counters privileged EXEC command does not clear counters retrieved by using Simple
Network Management Protocol (SNMP), but only those seen with the show interface privileged EXEC
command.

9-26 78-16404-02
Shutting Down and Restarting the Interface

Shutting down an interface disables all functions on the specified interface and marks the interface as
unavailable on all monitoring command displays. This information is communicated to other network
servers through all dynamic routing protocols. The interface is not mentioned in any routing updates.
Beginning in privileged EXEC mode, follow these steps to shut down an interface:
Command Purpose
Step 2 interface {vlan vlan-id} | {{fastethernet | gigabitethernet} Select the interface to be configured.
interface-id} | {port-channel port-channel-number}
Step 3 shutdown Shut down an interface.
Step 5 show running-config Verify your entry.
Use the no shutdown interface configuration command to restart the interface.

To verify that an interface is disabled, enter the show interfaces privileged EXEC command. A disabled
interface is shown as administratively down in the show interface command display.

78-16404-02 9-27

9-28 78-16404-02

Configuring Interface Characteristics

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

Configuring Interface Characteristics

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Configuring Interface Characteristics

Uploaded by

Copyright:

Available Formats

C H A P T E R 9

Configuring Interface Characteristics

Understanding Interface Types

Catalyst 3560 Switch Software Configuration Guide

Catalyst 3560 Switch Software Configuration Guide

Catalyst 3560 Switch Software Configuration Guide

Switch Virtual Interfaces

Catalyst 3560 Switch Software Configuration Guide

EtherChannel Port Groups

Power over Ethernet Ports

Catalyst 3560 Switch Software Configuration Guide

Supported Protocols and Standards

Powered-Device Detection and Initial Power Allocation

Catalyst 3560 Switch Software Configuration Guide

Table 9-1 IEEE Power Classifications

Class Maximum Power Level Required from the Switch

Power Management Modes

Catalyst 3560 Switch Software Configuration Guide

Catalyst 3560 Switch Software Configuration Guide

Figure 9-1 Connecting VLANs with the Catalyst 3560 Switch

172.20.128.1 SVI 1 SVI 2 172.20.129.1

Catalyst 3560 Switch Software Configuration Guide

Using Interface Configuration Mode

Procedures for Configuring Interfaces

Catalyst 3560 Switch Software Configuration Guide

Configuring a Range of Interfaces

Catalyst 3560 Switch Software Configuration Guide

– port-channel port-channel-number - port-channel-number, where the port-channel-number

Configuring and Using Interface Range Macros

Catalyst 3560 Switch Software Configuration Guide

Catalyst 3560 Switch Software Configuration Guide

Switch# show running-config | include define

This example shows how to create a multiple-interface macro named macro1:

Configuring Ethernet Interfaces

Default Ethernet Interface Configuration

Catalyst 3560 Switch Software Configuration Guide

Table 9-2 Default Layer 2 Ethernet Interface Configuration

Feature Default Setting

Catalyst 3560 Switch Software Configuration Guide

Configuring Interface Speed and Duplex Mode

Catalyst 3560 Switch Software Configuration Guide

Setting the Interface Speed and Duplex Parameters

Catalyst 3560 Switch Software Configuration Guide

Configuring IEEE 802.3z Flow Control

Catalyst 3560 Switch Software Configuration Guide

Configuring Auto-MDIX on an Interface

Catalyst 3560 Switch Software Configuration Guide

Table 9-3 Link Conditions and Auto-MDIX Settings

To disable Auto-MDIX, use the no mdix auto interface configuration command.

Configuring a Power Management Mode on a PoE Port

Catalyst 3560 Switch Software Configuration Guide

• static—Enable powered-device detection. Pre-allocate (reserve)

Catalyst 3560 Switch Software Configuration Guide

Adding a Description for an Interface

Use the no description interface configuration command to delete the description.

Configuring Layer 3 Interfaces

Catalyst 3560 Switch Software Configuration Guide

Catalyst 3560 Switch Software Configuration Guide