This example shows how to reenable all Fast Ethernet interfaces 5/1 to 5/5:
Switch(config)# interface range fastethernet 5/1 - 5
Switch(config-if-range)# no shutdown
Switch(config-if-range)#
*Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/1, changed state to up
*Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/2, changed state to up
*Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/3, changed state to up
*Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/4, changed state to up
*Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/5, changed state to up
*Oct 6 08:24:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/
5, changed state to up
*Oct 6 08:24:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/
3, changed state to up
*Oct 6 08:24:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/
4, changed state to up
Switch(config-if)#
This example shows how to use a comma to add different interface type
strings to the range to reenable all Fast Ethernet interfaces in the
range 5/1 to 5/5 and both Gigabit Ethernet interfaces 1/1 and 1/2:
Switch(config-if)# interface range fastethernet 5/1 - 5, gigabitethernet 1/1 - 2
Switch(config-if)# no shutdown
Switch(config-if)#
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/1, changed state to up
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/2, changed state to up
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/3, changed state to up
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/4, changed state to up
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/5, changed state to up
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface GigabitEthernet1/1, changed state to
up
*Oct 6 08:29:28: %LINK-3-UPDOWN: Interface GigabitEthernet1/2, changed state to
up
*Oct 6 08:29:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/
5, changed state to up
*Oct 6 08:29:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/
3, changed state to up
*Oct 6 08:29:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/
4, changed state to up
Switch(config-if)#
If you enter multiple configuration commands while you are in
interface-range configuration mode, each command is run as it is entered
(they are not batched together and run after you exit interface-range
configuration mode). If you exit interface-range configuration mode
while the commands are being run, some commands might not be run on all
interfaces in the range. Wait until the command prompt is displayed
before exiting interface-range configuration mode.
Defining and Using Interface-Range Macros
You can define 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 command string, you must define the macro.
To define an interface-range macro, perform this task:
This example shows how to define an interface-range macro named enet_list to select Fast Ethernet interfaces 5/1 through 5/4:
Switch(config)# define interface-range enet_list fastethernet 5/1 - 4
To show the defined interface-range macro configuration, perform this task:
This example shows how to display the defined interface-range macro named enet_list:
Switch# show running-config | include define
define interface-range enet_list FastEthernet5/1 - 4
Switch#
To use an interface-range macro in the interface range command, perform this task:
Command
|
Purpose
|
|---|---|
Switch(config)# interface range macro name |
Selects the interface range to be configured using the values saved in a named interface-range macro.
|
This example shows how to change to the interface-range configuration mode using the interface-range macro enet_list:
Switch(config)# interface range macro enet_list
Switch(config-if)#
Deploying 10-Gigabit Ethernet and a Gigabit Ethernet SFP Ports
Note 
On
a Catalyst 4510R series switch, if you enable both the 10-Gigabit
Ethernet and Gigabit Ethernet SFP uplink ports, you must re-boot the
switch. On the Catalyst 4503, 4506, and 4507R series switches, this
capability is automatically enabled.
On
a Catalyst 4510R series switch, if you enable both the 10-Gigabit
Ethernet and Gigabit Ethernet SFP uplink ports, you must re-boot the
switch. On the Catalyst 4503, 4506, and 4507R series switches, this
capability is automatically enabled.
Prior to Cisco Release 12.2(25)SG, the Cisco Catalyst 4500 Supervisor
Engine V-10GE allowed you to enable either the dual wire-speed
10-Gigabit Ethernet ports, or four alternatively wired Gigabit Ethernet
SFP uplink ports. With Cisco Release 12.2(25)SG, you can simultaneously
deploy the dual 10 Gigabit Ethernet ports and the four Gigabit Ethernet
SFP ports. This capability is supported on the Catalyst 4503, Catalyst
4506, and Catalyst 4507R chassis.
When deploying a Catalyst 4510R chassis, one of three configurations is supported:
•Enable the dual 10 -Gigabit Ethernet ports (X2 optics) only.
Enable the dual 10 -Gigabit Ethernet ports (X2 optics) only.
•Enable the four Gigabit Ethernet ports (SFP optics) only.
Enable the four Gigabit Ethernet ports (SFP optics) only.
•Enable
both the dual 10 Gigabit Ethernet and the four Gigabit Ethernet ports,
with the understanding that the tenth slot (Flex-Slot) will only support
a 2-port gigabit interface converter (GBIC) line card (WS-X4302-GB)
when in this mode.
Enable
both the dual 10 Gigabit Ethernet and the four Gigabit Ethernet ports,
with the understanding that the tenth slot (Flex-Slot) will only support
a 2-port gigabit interface converter (GBIC) line card (WS-X4302-GB)
when in this mode.
To select the 10-Gigabit Ethernet and/or the Gigabit Ethernet SFP uplink ports, perform this task:
The following example shows how to enable both 10-Gigabit Ethernet and
Gigabit Ethernet SFP uplink ports on a Catalyst 4510R series switch:
Switch# configure terminal
Switch(config)# hw-module uplink select all
Warning: This configuration mode will place slot 10 in flex slot mode
Digital Optical Monitoring Transceiver Support
Command line interface (CLI) commands (show inventory, show idprom
interface) are used on transceivers to obtain serail number, model name,
inventory information.
The following commands are specific to the transceivers that support the DOM capability:
•Display current values and thresholds for all sensor on a particular interface transceiver:
Display current values and thresholds for all sensor on a particular interface transceiver:
show interfaces transceiver [detail] [threshold]
•Enable/Disable the entSensorThresholdNotification for all sensors in all the transceivers:
Enable/Disable the entSensorThresholdNotification for all sensors in all the transceivers:
snmp-server enable trap transceiver
•Enable/Disable transceiver monitoring:
Enable/Disable transceiver monitoring:
transceiver type all
Note This
feature is only available when a DOM capable transceiver is present and
configured for monitoring. The frequency at which the sensor
information is refreshed depends on default values configured in the
transceiver SEEPROM (Serial Electrically Erasable Programmable Read Only
Memory).
This
feature is only available when a DOM capable transceiver is present and
configured for monitoring. The frequency at which the sensor
information is refreshed depends on default values configured in the
transceiver SEEPROM (Serial Electrically Erasable Programmable Read Only
Memory).
Configuring Optional Interface Features
The following subsections describe optional procedures:
Configuring Ethernet Interface Speed and Duplex Mode
Speed and Duplex Mode Configuration Guidelines
Note You
do not configure the client device for autonegotiation. Rather, you
configure the switch with the speed, or range of speeds, that you want
to autonegotiate.
You
do not configure the client device for autonegotiation. Rather, you
configure the switch with the speed, or range of speeds, that you want
to autonegotiate.
You can configure the interface speed and duplex mode parameters to auto
and allow the Catalyst 4500 series switch to negotiate the interface
speed and duplex mode between interfaces. If you decide to configure the
interface speed and duplex commands manually, consider the following:
•If you enter the no speed command, the switch automatically configures both interface speed and duplex to auto.
If you enter the no speed command, the switch automatically configures both interface speed and duplex to auto.
•When you set the interface speed to 1000 (Mbps) or auto 1000, the duplex mode is full duplex. You cannot change the duplex mode.
When you set the interface speed to 1000 (Mbps) or auto 1000, the duplex mode is full duplex. You cannot change the duplex mode.
•If the interface speed is set to 10 or 100, the duplex mode is set to half duplex by default unless you explicitly configure it.
If the interface speed is set to 10 or 100, the duplex mode is set to half duplex by default unless you explicitly configure it.
Caution Changing the interface speed and duplex mode configuration might shut down and restart the interface during the reconfiguration.
Changing the interface speed and duplex mode configuration might shut down and restart the interface during the reconfiguration.
Setting the Interface Speed
If you set the interface speed to auto on a 10/100-Mbps Ethernet
interface, speed and duplex are autonegotiated. The forced 10/100
autonegotiation feature allows you to limit interface speed auto
negotiation up to 100 Mbps on a 10/100/1000BASE-T port.
To set the port speed for a 10/100-Mbps Ethernet interface, perform this task:
This example shows how to set the interface speed to 100 Mbps on the Fast Ethernet interface 5/4:
Switch(config)# interface fastethernet 5/4
Switch(config-if)# speed 100
This example shows how to allow Fast Ethernet interface 5/4 to autonegotiate the speed and duplex mode:
Switch(config)# interface fastethernet 5/4
Switch(config-if)# speed auto
Note This is analogous to specifying speed auto 10 100.
This is analogous to specifying speed auto 10 100.
This example shows how to limit the interface speed to 10 and 100 Mbps
on the Gigabit Ethernet interface 1/1 in auto-negotiation mode:
Switch(config)# interface gigabitethernet 1/1
Switch(config-if)# speed auto 10 100
This example shows how to limit speed negotiation to 100 Mbps on the Gigabit Ethernet interface 1/1:
Switch(config)# interface gigabitethernet 1/1
Switch(config-if)# speed auto 100
Note Turning
off autonegotiation on a Gigabit Ethernet interface will result in the
port being forced into 1000 Mbps and full-duplex mode.
Turning
off autonegotiation on a Gigabit Ethernet interface will result in the
port being forced into 1000 Mbps and full-duplex mode.
To turn off the port speed autonegotiation for Gigabit Ethernet interface 1/1, perform this task:
Command
|
Purpose
|
|
|---|---|---|
Step 1
|
Switch(config)# interface gigabitethernet1/1 |
Specifies the interface to be configured.
|
Step 2
|
Switch(config-if)# speed nonegotiate |
Disables autonegotiation on the interface.
|
To restore autonegotiation, enter the no speed nonegotiate command in the interface configuration mode.
Note For the blocking ports on the WS-X4416 module, do not set the speed to autonegotiate.
For the blocking ports on the WS-X4416 module, do not set the speed to autonegotiate.
Setting the Interface Duplex Mode
Note When the interface is set to 1000 Mbps, you cannot change the duplex mode from full duplex to half duplex.
When the interface is set to 1000 Mbps, you cannot change the duplex mode from full duplex to half duplex.
To set the duplex mode of a Fast Ethernet interface, perform this task:
This example shows how to set the interface duplex mode to full on Fast Ethernet interface 5/4:
Switch(config)# interface fastethernet 5/4
Switch(config-if)# duplex full
Displaying the Interface Speed and Duplex Mode Configuration
To display the interface speed and duplex mode configuration for an interface, perform this task:
Command
|
Purpose
|
|---|---|
Switch# show interfaces [fastethernet | gigabitethernet | tengigabitethernet] slot/interface |
Displays the interface speed and duplex mode configuration.
|
This example shows how to display the interface speed and duplex mode of Fast Ethernet interface 6/1:
Switch# show interface fastethernet 6/1
FastEthernet6/1 is up, line protocol is up
Hardware is Fast Ethernet Port, address is 0050.547a.dee0 (bia 0050.547a.dee0)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:54, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 50/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
50 packets input, 11300 bytes, 0 no buffer
Received 50 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
1456 packets output, 111609 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
1 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Switch#
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 the following
commands: show configuration, show running-config, and
show interfaces.
show interfaces.
To add a description for an interface, enter the following command:
This example shows how to add a description on Fast Ethernet interface 5/5:
Switch(config)# interface fastethernet 5/5
Switch(config-if)# description Channel-group to "Marketing"
Configuring Flow Control
Gigabit Ethernet ports use Flow Control to slow-down the transmission of
incoming packets. If a buffer on a Gigabit Ethernet port runs out of
space, the port transmits a special packet that requests remote ports to
delay sending packets for a period of time. The port can also receive
this special packet from its link-partner for the same purpose. This
special packet is called a pause frame.
The default settings for Gigabit Ethernet interfaces are as follows:
•Sending pause frames is off—non-oversubscribed Gigabit Ethernet interfaces.
Sending pause frames is off—non-oversubscribed Gigabit Ethernet interfaces.
•Receiving pause frames is desired—non-oversubscribed Gigabit Ethernet interfaces.
Receiving pause frames is desired—non-oversubscribed Gigabit Ethernet interfaces.
•Sending pause frames is on—Oversubscribed Gigabit Ethernet interfaces.
Sending pause frames is on—Oversubscribed Gigabit Ethernet interfaces.
•Receiving pause frames is desired—Oversubscribed Gigabit Ethernet interfaces
Receiving pause frames is desired—Oversubscribed Gigabit Ethernet interfaces
The default settings for Tengigabit Ethernet interfaces are as follows:
•Sending pause frames is off.
Sending pause frames is off.
•Receiving pause frames is on.
Receiving pause frames is on.
Note desired is not a flow control option on these links
desired is not a flow control option on these links
To configure flow control, perform this task:
This example shows how to configure flow control on an oversubscribed Gigabit Ethernet port 7/5:
Switch# configure terminal
Switch(config)# interface g7/5
Switch(config-if)# flowcontrol send on
Switch(config-if)# end
Switch)# show inmterfaces gigabitEthernet 7/5 capabilities
GigabitEthernet7/5
Model: WS-X4548-GB-RJ45-RJ-45
Type: 10/100/1000-TX
Speed: 10,100,1000,auto
Duplex: half,full,auto
Trunk encap. type: 802.1Q,ISL
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100), hw
Flowcontrol: rx-(off,on,desired),tx-(off,on,desired)
VLAN Membership: static, dynamic
Fast Start: yes
Queuing: rx-(N/A), tx-(1p3q1t, Sharing/Shaping)
CoS rewrite: yes
ToS rewrite: yes
Inline power: no
SPAN: source/destination
UDLD: yes
Link Debounce: no
Link Debounce Time: no
Port Security: yes
Dot1x: yes
Maximum MTU: 1552 bytes (Baby Giants)
Multiple Media Types: no
Diagnostic Monitoring: N/A
Switch)# show flowcontrol interface GigabitEthernet 7/5
Port Send FlowControl Receive FlowControl RxPause TxPause
admin oper admin oper
--------- -------- -------- -------- -------- ------- -------
Gi7/5 on off desired off 0 0
This example shows the output of the show interfaces and show
flowcontrol commands on an non-overscribed Gigabit Ethernet port 5/5:
Switch# show interfaces gigabitEthernet 5/5 capabilities
GigabitEthernet5/5
Model: WS-X4306-GB-Gbic
Type: No Gbic
Speed: 1000
Duplex: full
Trunk encap. type: 802.1Q,ISL
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100), hw
Flowcontrol: rx-(off,on,desired),tx-(off,on,desired)
VLAN Membership: static, dynamic
Fast Start: yes
Queuing: rx-(N/A), tx-(1p3q1t, Sharing/Shaping)
CoS rewrite: yes
ToS rewrite: yes
Inline power: no
SPAN: source/destination
UDLD: yes
Link Debounce: no
Link Debounce Time: no
Port Security: yes
Dot1x: yes
Maximum MTU: 9198 bytes (Jumbo Frames)
Multiple Media Types: no
Diagnostic Monitoring: N/A
Switch# show flowcontrol interface gigabitEthernet 5/5
Port Send FlowControl Receive FlowControl RxPause TxPause
admin oper admin oper
--------- -------- -------- -------- -------- ------- -------
Gi5/5 off off desired off 0 0
This example shows the output of the show interfaces and show flowcontrol commands on an unsupported Fast Ethernet port 3/5:
Switch# show interfaces fa3/5 capabilities
FastEthernet3/5
Model: WS-X4148-RJ-45
Type: 10/100BaseTX
Speed: 10,100,auto
Duplex: half,full,auto
Trunk encap. type: 802.1Q,ISL
Trunk mode: on,off,desirable,nonegotiate
Channel: yes
Broadcast suppression: percentage(0-100), sw
Flowcontrol: rx-(none),tx-(none)
VLAN Membership: static, dynamic
Fast Start: yes
Queuing: rx-(N/A), tx-(1p3q1t, Shaping)
CoS rewrite: yes
ToS rewrite: yes
Inline power: no
SPAN: source/destination
UDLD: yes
Link Debounce: no
Link Debounce Time: no
Port Security: yes
Dot1x: yes
Maximum MTU: 1552 bytes (Baby Giants)
Multiple Media Types: no
Diagnostic Monitoring: N/A
Switch# show flowcontrol interface fa3/5
Port Send FlowControl Receive FlowControl RxPause TxPause
admin oper admin oper
--------- -------- -------- -------- -------- ------- -------
Fa3/5 Unsupp. Unsupp. Unsupp. Unsupp. 0 0
Configuring Jumbo Frame Support
These subsections describe jumbo frame support:
Ports and Modules that Support Jumbo Frames
The following ports and modules support jumbo frames:
•Supervisor uplink ports
Supervisor uplink ports
•WS-X4306-GB: all ports
WS-X4306-GB: all ports
•WS-X4232-GB-RJ: ports 1-2
WS-X4232-GB-RJ: ports 1-2
•WS-X4418-GB: ports 1-2
WS-X4418-GB: ports 1-2
•WS-X4412-2GB-TX: ports 13-14
WS-X4412-2GB-TX: ports 13-14
Each of the last three modules has two non-blocking ports that can
support jumbo frames. Other ports are over-subscribed ports and cannot
support jumbo frames.
Understanding Jumbo Frame Support
These sections describe jumbo frame support:
Jumbo Frame Support Overview
A jumbo frame is a frame larger than the default Ethernet size. Enable
jumbo frame support by configuring a larger-than-default maximum
transmission unit (MTU) size on a port or interface.
Catalyst 4500 series switch Ethernet LAN ports configured with a
nondefault MTU size accept frames containing packets with a size between
1500 and 9198 bytes. With a nondefault MTU size configured, the packet
size of ingress frames is checked. If the packet is larger than the
configured MTU, it is dropped.
For traffic that needs to be routed, the MTU of the egress port is
checked. If the MTU is smaller than the packet size, the packet is
forwarded to the CPU. If the "do not fragment bit" is not set, it is
fragmented. Otherwise, the packet is dropped.
Note Jumbo frame support does not fragment Layer 2 switched packets.
Jumbo frame support does not fragment Layer 2 switched packets.
The Catalyst 4500 series switch does not compare the packet size with
the MTU at the egress port, but jumbo frames are dropped in ports that
do not support them. The frames can be transmitted in ports that do
support jumbo frames, even though the MTU is not configured to jumbo
size.
Note Jumbo frame support is only configured per interface; jumbo frame support cannot be configured globally.
Jumbo frame support is only configured per interface; jumbo frame support cannot be configured globally.
Ethernet Ports
These sections describe configuring nondefault MTU sizes on Ethernet ports:
Ethernet Port Overview
With Cisco IOS Release 12.2(25)EW, configuring a nondefault MTU size on
certain Ethernet ports limits the size of ingress packets. The MTU does
not impact the egress packets.
With releases earlier than Cisco IOS Release 12.1(13)EW, you can configure the MTU size only on Gigabit Ethernet.
Layer 3 and Layer 2 EtherChannels
With Release Cisco IOS Release 12.2(25)EW and later releases, you can
configure all the interfaces in an EtherChannel provided that they have
the same MTU. Changing the MTU of an EtherChannel changes the MTU of all
member ports. If the MTU of a member port cannot be changed to the new
value, that port is suspended (administratively shut down). A port
cannot join an EtherChannel if the port has a different MTU. If a member
port of an EtherChannel changes MTU, the member port is suspended.
VLAN Interfaces
If switch ports reside in the same VLAN, either configure all of the
switch ports to handle jumbo frames and support the same MTU size, or
configure none of them. However, such uniformity of MTU size in the same
VLAN is not enforced.
When a VLAN has switch ports with different MTU size, packets received
from a port with a larger MTU might be dropped when they are forwarded
to a port with a smaller MTU.
If the switch ports in a VLAN have jumbo frames enabled, the
corresponding SVI can have jumbo frames enabled. The MTU of an SVI
should always be smaller than the smallest MTU among all the switch
ports in the VLAN, but this condition is not enforced.
The MTU of a packet is not checked on the ingress side for an SVI; it is
checked on the egress side of an SVI. If the MTU of a packet is larger
than the MTU of the egress SVI, the packet will be sent to the CPU for
fragmentation processing. If the "do not fragment" bit is not set, the
packet is fragmented. Otherwise, the packet is dropped.
Configuring MTU Sizes
To configure the MTU size, perform this task:
Command
|
Purpose
|
|
|---|---|---|
Step 1
|
Switch(config)# interface {{vlan vlan_ID} |
{{type1 slot/port} | {port-channel
port_channel_number} slot/port}}
|
Selects the interface to configure.
|
Step 2
|
Switch(config-if)# mtu mtu_size |
Configures the MTU size.
|
Switch(config-if)# no mtu |
Reverts to the default MTU size (1500 bytes).
|
|
Step 3
|
Switch(config-if)# end |
Exits configuration mode.
|
Step 4
|
Switch# show running-config interface
[{fastethernet | gigabitethernet} slot/port]
|
Displays the running configuration.
|
1 type = fastethernet, gigabitethernet, or tengigabitethernet
|
Note When
configuring the MTU size for VLAN interfaces and Layer 3 and Layer 2
Ethernet ports, note that the supported MTU values are from 1500 to
9198 bytes.
When
configuring the MTU size for VLAN interfaces and Layer 3 and Layer 2
Ethernet ports, note that the supported MTU values are from 1500 to
9198 bytes.
This example shows how to configure the MTU size on Gigabit Ethernet port 1/1:
switch# conf t
switch(config)# int gi1/1
switch(config-if)# mtu 9198
switch(config-if)# end
This example shows how to verify the configuration:
switch# show interface gigabitethernet 1/2
GigabitEthernet1/2 is administratively down, line protocol is down
Hardware is C6k 1000Mb 802.3, address is 0030.9629.9f88 (bia 0030.9629.9f88)
MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec,
<...Output Truncated...>
switch#
Interacting with the Baby Giants Feature
The baby giants feature, introduced in Cisco IOS Release 12.1(12c)EW,
uses the global command system mtu to set the global baby
giant MTU. This feature also allows certain interfaces to support
Ethernet payload size of up to 1552 bytes.
Both the system mtu command and the per-interface mtu command can
operate on interfaces that can support jumbo frames, but the
per-interface mtu command takes precedence.
For example, before setting the per-interface MTU for interface gi1/1, you issue the
system mtu 1550 command to change the MTU for gi1/1 to 1550 bytes. Next, you issue the per-interface mtu command to change the MTU for gi1/1 to 9198 bytes. Now, if you change the baby giant MTU to 1540 bytes with the command system mtu 1540, the MTU for gi1/1 remains unchanged at 9198 bytes.
system mtu 1550 command to change the MTU for gi1/1 to 1550 bytes. Next, you issue the per-interface mtu command to change the MTU for gi1/1 to 9198 bytes. Now, if you change the baby giant MTU to 1540 bytes with the command system mtu 1540, the MTU for gi1/1 remains unchanged at 9198 bytes.
Configuring Auto-MDIX on a Port
When automatic medium-dependent-interface crossover (auto-MDIX) is
enabled on an port, the port 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 on the port to auto
so that for the feature to operate correctly. auto-MDIX is supported on
copper media ports. It is not supported on fiber media ports.
Note The
following linecards support Auto-MDIX by default, when port
auto-negotiation is enabled: WS-X4448-GB-RJ45 and WS-X4548-GB-RJ45. You
cannot disable them with the the mdix command.
The
following linecards support Auto-MDIX by default, when port
auto-negotiation is enabled: WS-X4448-GB-RJ45 and WS-X4548-GB-RJ45. You
cannot disable them with the the mdix command.
Note The
following linecards do not support Auto-MDIX, neither by default nor by
CLI: WS-X4548-GB-RJ45V, WS-X4524-GB-RJ45V, and WS-X4506-GB-T.
The
following linecards do not support Auto-MDIX, neither by default nor by
CLI: WS-X4548-GB-RJ45V, WS-X4524-GB-RJ45V, and WS-X4506-GB-T.
Note The
following linecards support Auto-MDIX through the CLI on their copper
media ports: WS-X4124-RJ45, WS-X4148-RJ45 (hardware revision 3.0 or
higher), and WS-X4232-GB-RJ45 (hardware revision 3.0 or higher).
The
following linecards support Auto-MDIX through the CLI on their copper
media ports: WS-X4124-RJ45, WS-X4148-RJ45 (hardware revision 3.0 or
higher), and WS-X4232-GB-RJ45 (hardware revision 3.0 or higher).
Table 6-1 shows the link states that results from auto-MDIX settings and correct and incorrect cabling.
To configure auto-MDIX on a port, perform the following task:
To disable auto-MDIX, use the no mdix auto interface configuration command.
This example shows how to enable auto-MDIX on a port:
Switch# configure terminal
Switch(config)# interface fastethernet 6/5
Switch(config-if)# speed auto
Switch(config-if)# mdix auto
Switch(config-if)# end
Displaying the Interface auto-MDIX Configuration
To display the interface speed and duplex mode configuration for an interface, perform this task:
Depending on how the speed auto and the mdix auto commands are
configured on a supported linecard interface, the show interfaces
command displays the following possible auto-MDIX statuses:
Table 6-2 shows the auto-MDIX setting and operational state and the status of auto-MDIX.
This example show s how to display the auto-MDIX configuration setting and its operational state on Fast Ethernet interface 6/1:
Switch# show interfaces fastethernet 6/1
FastEthernet6/1 is up, line protocol is up (connected)
Hardware is Fast Ethernet Port, address is 0001.64fe.e5d0 (bia 0001.64fe.e5d0)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, link type is auto, media type is 10/100BaseTX
input flow-control is unsupported output flow-control is unsupported
Auto-MDIX on (operational: on)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:16, output never, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
511 packets input, 74464 bytes, 0 no buffer
Received 511 broadcasts (511 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 input packets with dribble condition detected
3552 packets output, 269088 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
1 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Switch#
Understanding Online Insertion and Removal
The online insertion and removal (OIR) feature supported on the
Catalyst 4500 series switch allows you to remove and replace modules
while the system is online. You can shut down the module before removal
and restart it after insertion without causing other software or
interfaces to shut down.
You do not need to enter a command to notify the software that you are
going to remove or install a module. The system notifies the supervisor
engine that a module has been removed or installed and scans the system
for a configuration change. The newly installed module is initialized,
and each interface type is verified against the system configuration;
then the system runs diagnostics on the new interface. There is no
disruption to normal operation during module insertion or removal.
If you remove a module and then replace it, or insert a different module
of the same type into the same slot, no change to the system
configuration is needed. An interface of a type that has been configured
previously will be brought online immediately. If you remove a module
and insert a module of a different type, the interface(s) on that module
will be administratively up with the default configuration for that
module.
Monitoring and Maintaining the Interface
The following sections describe how to monitor and maintain the interfaces:
Monitoring Interface and Controller Status
The Cisco IOS software for the Catalyst 4500 series switch contains
commands that you can enter at the EXEC prompt to display information
about the interface, including the version of the software and the
hardware, the controller status, and statistics about the interfaces.
The following table lists some of the interface monitoring commands.
(You can display the full list of show commands by entering the show ? command at the EXEC prompt.) These commands are fully described in the Interface Command Reference.
To display information about the interface, perform this task:
This example shows how to display the status of Fast Ethernet interface 5/5:
Switch# show protocols fastethernet 5/5
FastEthernet5/5 is up, line protocol is up
Switch#
Clearing and Resetting the Interface
To clear the interface counters shown with the show interfaces command, enter the following command:
This example shows how to clear and reset the counters on Fast Ethernet interface 5/5:
Switch# clear counters fastethernet 5/5
Clear "show interface" counters on this interface [confirm] y
Switch#
*Sep 30 08:42:55: %CLEAR-5-COUNTERS: Clear counter on interface FastEthernet5/5
by vty1 (171.69.115.10)
Switch#
The clear counters command (without any arguments) clears all the current interface counters from all interfaces.
Note The clear counters command does not clear counters retrieved with SNMP; it clears only those counters displayed with the EXEC show interfaces command.
The clear counters command does not clear counters retrieved with SNMP; it clears only those counters displayed with the EXEC show interfaces command.
Shutting Down and Restarting an Interface
You can disable an interface, which 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
will not be mentioned in any routing updates.
To shut down an interface and then restart it, perform this task:
This example shows how to shut down Fast Ethernet interface 5/5:
Switch(config)# interface fastethernet 5/5
Switch(config-if)# shutdown
Switch(config-if)#
*Sep 30 08:33:47: %LINK-5-CHANGED: Interface FastEthernet5/5, changed state to a administratively down
Switch(config-if)#
This example shows how to reenable Fast Ethernet interface 5/5:
Switch(config-if)# no shutdown
Switch(config-if)#
*Sep 30 08:36:00: %LINK-3-UPDOWN: Interface FastEthernet5/5, changed state to up
Switch(config-if)#
To verify whether an interface is disabled, enter the EXEC show interfaces command. An interface that has been shut down will appear as "administratively down."
Configuring Interface Link Status and Trunk Status Events
You can configure interface link status and trunk status events. On the
Catalyst 4500 series switch, the following interface logging event
notifications are supported both globally and per interface:
•Enable/disable notification on the interface whenever its data link status is changed.
Enable/disable notification on the interface whenever its data link status is changed.
•Enable/disable notification on the trunk interface whenever its trunking status is changed.
Enable/disable notification on the trunk interface whenever its trunking status is changed.
Use the [no] logging event link-status [use-global] command to
enable/disable the interface link status event. Use the [no] logging
event trunk-status [use-global] command to enable/disable the interface
trunk status event.
Each interface link status logging event can be configured in one of the following states:
•logging
event link-status - Link status logging event is enabled explicitly on
the interface regardless of the switch global setting.
logging
event link-status - Link status logging event is enabled explicitly on
the interface regardless of the switch global setting.
•no
logging event link-status - Link status logging event is disabled
explicitly on the interface regardless of the switch global setting.
no
logging event link-status - Link status logging event is disabled
explicitly on the interface regardless of the switch global setting.
•logging
event link-status use-global - This is the default link status logging
event configuration on the interface; its configuration should follow
the switch global link status logging event setting.
logging
event link-status use-global - This is the default link status logging
event configuration on the interface; its configuration should follow
the switch global link status logging event setting.
The interface trunk status logging event can be configured in the same configuration states.
Configuring Link Status Event Notification for an Interface
To enable/disable a link status logging event, enter one of the following commands:
Global Settings
You can also provide a global configuration for the corresponding
logging event. A global configuration provides default logging settings
for all interfaces. The [no] logging event link-status global command
lets you enable/disable the interface link status logging for the entire
switch. The [no] logging event trunk-status global command lets you
enable/disable interface trunk status logging for the entire switch.
Each interface link status logging event, if not configured at the
interface level, will use the following global logging event setting:
•logging event link-status global - Link status logging event is enabled, if not configured on the interface.
logging event link-status global - Link status logging event is enabled, if not configured on the interface.
•no logging event link-status global - Link status logging event is disabled, if not configured on the interface.
no logging event link-status global - Link status logging event is disabled, if not configured on the interface.
The interface trunk status logging event has similar global configurations.
Configuring a Switch Global Link Status Logging Event
To enable/disable the global link status logging event, enter one of the following commands:
Command
|
Purpose
|
|---|---|
Switch(config-if)# logging event link-status global |
Enables global link status logging.
|
Switch(config-if)# no logging event link-status global |
Disables global link status logging.
|
Result
The following example displays a summary of the operating states for the
interface logging event under different combinations of global and
interface logging settings:
global setting interface setting actual logging state
-------------- ----------------- --------------------
on on on
off on on
on off off
off off off
on default(use-global) on
off default(use-global) off
The following example displays the configuration and logging message output for link status and trunk status logging events:
//
// The global link status and trunk status logging events are enabled.
//
Switch# show running | include logging
show running | include logging
logging event link-status global
logging event trunk-status global
Switch#
//
// The interface link status and trunk status logging settings
// are set to default values, which follow regardless of the global
// setting.
//
Switch# show running interface g1/4
Building configuration...
Current configuration: 97 bytes
!
interface GigabitEthernet1/4
switchport trunk encapsulation dot1q
switchport mode trunk
end
Switch#
//
// The trunk status logging messages for the interface are
// displayed whenever the interface trunking status is changed.
// Here we change the other end node's trunking encapsulation
// from dot1q to isl.
//
3d00h: %DTP-5-ILGLCFG: Illegal config(on,isl--on,dot1q) on Gi1/4
3d00h: %DTP-5-ILGLCFG: Illegal config(on,isl--on,dot1q) on Gi1/4
3d00h: %DTP-5-ILGLCFG: Illegal config(on,isl--on,dot1q) on Gi1/4
//
// The link and trunk status logging message for the interface
// are displayed whenever the interface link status is changed.
// Here we do a "shut" and "no shut" on the other end link node.
//
3d00h: %DTP-5-NONTRUNKPORTON: Port Gi1/4 has become non-trunk
3d00h: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet1/4, changed state to down
3d00h: %LINK-3-UPDOWN: Interface GigabitEthernet1/4, changed state to
down
3d00h: %LINK-3-UPDOWN: Interface GigabitEthernet1/4, changed state to up
3d00h: %DTP-5-TRUNKPORTON: Port Gi1/4 has become dot1q trunk
3d00h: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet1/4, changed state to up
Resetting the Interface to the Default Configuration
If you have configured a interface with many command lines and you want
to clear all the configuration on that interface, you can use the
default interface global configuration command, as follows:
Switch(config)# default interface fastEthernet 3/5
Interface FastEthernet3/5 set to default configuration
This command will clear all the configurations and shutdown the interface:
Switch# show run interface fastethernet 3/5
Building configuration...
Current configuration : 58 bytes
!
interface FastEthernet3/5
no ip address
shutdown
end
