Interfaces Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches
Available Languages
Table of Contents
Interfaces Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches
Information About Interface Types
Supported Protocols and Standards
Powered-Device Detection and Initial Power Allocation
Power Monitoring and Power Policing
Configuring the Console Media Type
Using Interface Configuration Mode
Interface Configuration Process
Configuring a Range of Interfaces
Configuring and Using Interface Range Macros
Configuring Ethernet Interfaces
Configuring Interface Speed and Duplex Mode
Configuring a Power Management Mode on a PoE Port
Budgeting Power for Devices Connected to a PoE Port
Budgeting Power for a Device Connected to Each PoE Port
Budgeting Power for a Device Connected to a Specific PoE Port
Configuring a Dual-Purpose Port
Configuring IEEE 802.3x Flow Control
Configuring Auto-MDIX on an Interface
Adding a Description for an Interface
Configuring Layer 3 Interfaces
Configuring the EtherChannel Between the ESM and Host Router
About the Backplane PortChannel48 Interface
Configuring the Backplane PortChannel48 Interface
Configuring the PortChannel48 Interface for Layer 3 Routing Mode
Configuring the PortChannel48 Interface for Layer 2 Trunk Mode
Configuring the PortChannel48 Interface for Layer 2 Access Mode
Sample Gigabit Ethernet Interface Configuration on the CGR 2010
Monitoring and Maintaining Interfaces
Using FEFI to Maintain the Fiber FE Interfaces
Clearing and Resetting Interfaces and Counters
Shutting Down and Restarting the Interface
Obtaining Documentation and Submitting a Service Request
Interfaces Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches
First Published: August 2014
Last Updated: February 2015This document defines the types of interfaces on the Cisco IE 2000U Industrial Ethernet Switch
(IE 2000U) and Connected Grid Switches, hereafter referred to as switch, and describes how to configure them.This document includes the following sections:
- Information About Interface Types
- Prerequisites
- Guidelines and Limitations
- Default Settings
- Using the Switch USB Port
- Using Interface Configuration Mode
- Configuring Ethernet Interfaces
- Configuring Layer 3 Interfaces
- Configuring the System MTU
- Configuring the EtherChannel Between the ESM and Host Router
- Monitoring and Maintaining Interfaces
- Related Documents
- Feature History
Note
For complete syntax and usage information for the commands used in this document, see the documents listed in “Related Documents” section.
Information About Interface Types
This section describes the different types of interfaces supported by the switch and provides configuration procedures for physical interface characteristics.
Note
This section includes the following topics:
- UNI, NNI, and ENI Port Types
- Port-Based VLANs
- Switch Ports
- Routed Ports
- Switch Ports
- Switch Virtual Interfaces
- EtherChannel Port Groups
- Power over Ethernet Ports
- Dual-Purpose Ports
- Connecting Interfaces
UNI, NNI, and ENI Port Types
The switch supports user-network interfaces (UNIs), network node interfaces (NNIs), and enhanced network interfaces (ENIs). UNIs are typically connected to a host, such as a PC or a Cisco IP phone. NNIs are typically connected to a router or to another switch. ENIs have the same functionality as UNIs, but can be configured to support protocol control packets for Cisco Discovery Protocol (CDP), Spanning-Tree Protocol (STP), Link Layer Discovery Protocol (LLDP), and EtherChannel Link Aggregation Control Protocol (LACP) or Port Aggregation Protocol (PAgP).
By default, all ports are enabled as NNIs.
The default state for a UNI or ENI is administratively down to prevent unauthorized users from gaining access to other ports as you configure the switch. Traffic is not switched between these ports, and all arriving traffic at UNIs or ENIs must leave on NNIs to prevent a user from gaining access to another user’s private network. If it is appropriate for two or more UNIs or ENIs to exchange traffic within the switch, the UNIs and ENIs can be assigned to a community VLAN.
Note
The default status for an NNI is administratively up to allow a service provider remote access to the switch during initial configuration.
A port can be reconfigured from UNI to NNI or ENI and the reverse. When a port is reconfigured as another interface type, it inherits all the characteristics of that interface type. When you reconfigure a UNI or ENI to be an NNI, you must enable the port before it becomes active.
Changing the port type from UNI to ENI does not affect the administrative state of the port. If the UNI status is shutdown, it remains shutdown when reconfigured as an ENI; if the port is in a no shutdown state, it remains in the no shutdown state. At any time, all ports on the switch are either UNI, NNI, or ENI.
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. 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 associated with the VLAN ID or when a user creates the VLAN ID.
To isolate VLANs of different customers in a service-provider network, the switch uses UNI-ENI VLANs. UNI-ENI VLANs isolate user network interfaces (UNIs) or enhanced network interfaces (ENIs) on the switch from UNIs or ENIs that belong to other customer VLANs. There are two types of UNI-ENI VLANs:
- UNI-ENI isolated VLAN—This is the default VLAN state for all VLANs created on the switch. Local switching does not occur among UNIs or ENIs on the switch that belong to the same UNI-ENI isolated VLAN.
- UNI-ENI community VLAN—Local switching is allowed among UNIs and ENIs on the switch that belong to the same UNI community VLAN. If UNIs or ENIs belong to the same customer, and you want to switch packets between the ports, you can configure the common VLAN as a UNI-ENI community VLAN.
Note
To configure VLANs, use the vlan vlan-id global configuration command to enter VLAN configuration mode. The VLAN configurations for VLAN IDs 1 to 1005 are saved in the VLAN database. Extended-range VLANs (VLAN IDs 1006 to 4094) are not added to the VLAN database. 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:
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, a private-VLAN port, or a tunnel port. You can configure a port as an access port or trunk port. You configure a private VLAN port as a host or promiscuous port that belongs to a private-VLAN primary or secondary VLAN. (Only NNIs can be configured as promiscuous ports.) You must manually configure tunnel ports as part of an asymmetric link connected to an IEEE 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
Access Ports
An access port belongs to and carries the traffic of only one VLAN. 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 an 802.1Q tagged packet, the packet is dropped, and the source address is not learned. 802.1x can also be used for VLAN assignment.
Two types of access ports are supported:
- Static access ports—VLAN membership is manually assigned.
- Dynamic access ports—VLAN Membership 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. UNIs begin forwarding packets as soon as they are enabled. 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 Cisco Connected Grid switch cannot be a VMPS server. Dynamic access ports for VMPS are only supported on UNIs and ENIs.
Trunk Ports
An 802.1Q trunk port carries the traffic of multiple VLANs and by default is a member of all VLANs in the VLAN database. A 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 multiple VLANs, 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 become a member of a VLAN only if the VLAN is in the enabled state.
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 IEEE 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 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.
Routed Ports
A routed port is a physical port that acts like a port on a router and 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 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
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 for information about what happens when hardware resource limitations are reached.
Note
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 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.
Note
SVIs provide IP host connectivity only to the system; in Layer 3 mode, you can configure routing across SVIs. SVIs support routing protocols.
Note
Although the switch supports a total of 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 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 IEEE 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.
Note
EtherChannel Port Groups
EtherChannel port groups 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 Cisco Discovery Protocol (CDP), Link Aggregation Control Protocol (LACP), and the Port Aggregation Protocol (PAgP), which operate only on physical NNI or ENI 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.
Power over Ethernet Ports
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)
- 802.3af-compliant powered devices
A powered device can receive redundant power when it is connected only to a PoE switch port and to an AC power source.
After the switch detects a powered device, it determines the device power requirements and then grants or denies power to the device. The switch can also sense the real-time power consumption of the device by monitoring and policing the power usage.
This section includes the following topics:
- Supported Protocols and Standards
- Powered-Device Detection and Initial Power Allocation
- Power Management Modes
Note
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.
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.
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 adapter.
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.
- 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 2 lists these levels.
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 listed in the “Related Documents” section.
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.
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 shut down.
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.
Power Monitoring and Power Policing
When policing of the real-time power consumption is enabled, the switch takes action when a powered device consumes more power than the maximum amount allocated, also referred to as the cutoff-power value.
When PoE is enabled, the switch senses the real-time power consumption of the powered device. The switch monitors the real-time power consumption of the connected powered device; this is called power monitoring or power sensing. The switch also polices the power usage with the power policing feature.
Power monitoring is backward-compatible with Cisco intelligent power management and CDP-based power consumption. It works with these features to ensure that the PoE port can supply power to the powered device. For more information about these PoE features, see the “Supported Protocols and Standards” section.
The switch senses the real-time power consumption of the connected device as follows:
1.
2.
3.
If the device uses more than the maximum power allocation on the port, the switch can either turn off power to the port, or the switch can generate a syslog message and update the LEDs (the port LED is now blinking amber) while still providing power to the device based on the switch configuration. By default, power-usage policing is disabled on all PoE ports.
If error recovery from the PoE error-disabled state is enabled, the switch automatically takes the PoE port out of the error-disabled state after the specified amount of time.
If error recovery is disabled, you can manually re-enable the PoE port by using the shutdown and no shutdown interface configuration commands.
4.
Maximum Power Allocation (Cutoff Power) on a PoE Port
When power policing is enabled, the switch determines one of the values as the cutoff power on the PoE port in this order:
1.
2.
3.
4.
Use the first or second method in the previous list to manually configure the cutoff-power value by entering the power inline consumption default wattage or the power inline [ auto | static max ] max-wattage command. If you are not manually configuring the cutoff-power value, the switch automatically determines the value by using CDP power negotiation or the device IEEE classification, which is the third method in the previous list. If the switch cannot determine the value by using one of these methods, it uses the default value of 15400 mW (the fourth method in the previous list).
Power Consumption Values
You can configure the initial power allocation and the maximum power allocation on a port. However, these values are only the configured values that determine when the switch should turn on or turn off power on the PoE port. The maximum power allocation is not the same as the actual power consumption of the powered device. The actual cutoff power value that the switch uses for power policing is not equal to the configured power value.
When power policing is enabled, the switch polices the power usage at the switch port, which is greater than the power consumption of the device. When you manually set the maximum power allocation, you must consider the power loss over the cable from the switch port to the powered device. The cutoff power is the sum of the rated power consumption of the powered device and the worst-case power loss over the cable.
The actual amount of power consumed by a powered device on a PoE port is the cutoff-power value plus a calibration factor of 500 mW (0.5 W). The actual cutoff value is approximate and varies from the configured value by a percentage of the configured value. For example, if the configured cutoff power is 12 W, the actual cutoff-value is 11.4 W, which is 5% less than the configured value.
We recommend that you enable power policing when PoE is enabled on your switch. For example, if policing is disabled and you set the cutoff-power value by using the power inline auto max 6300 interface configuration command, the configured maximum power allocation on the PoE port is 6.3 W (6300 mW). The switch provides power to the connected devices on the port if the device needs up to 6.3 W. If the CDP-power negotiated value or the IEEE classification value exceeds the configured cutoff value, the switch does not provide power to the connected device. After the switch turns on power on the PoE port, the switch does not police the real-time power consumption of the device, and the device can consume more power than the maximum allocate d amount, which could adversely affect the switch and the devices connected to the other PoE ports.
The switch supports dual power supplies. If a power supply is removed or fails and the switch does not have enough power for the powered devices, the switch first denies power to low-priority ports in descending order of port numbers, and then to high priority ports in descending numbers. See the Hardware Installation Guide for your switch for information about PoE power requirements..
- If a power supply is removed and replaced by a new power supply with less power and the switch does not have enough power for the powered devices, the switch denies power to the PoE ports in auto mode in descending order of the port numbers. If the switch still does not have enough power, the switch then denies power to the PoE ports in static mode in descending order of the port numbers.
- If the new power supply supports more power than the previous one and the switch now has more power available, the switch grants power to the PoE ports in static mode in ascending order of the port numbers. If it still has power available, the switch then grants power to the PoE ports in auto mode in ascending order of the port numbers.
Dual-Purpose Ports
Each dual-purpose port is considered as a single interface with dual front ends (an RJ-45 connector and an SFP module connector). The dual front ends are not redundant interfaces; the switch activates only one connector of the pair.
By default, dual-purpose ports and SFP-only module ports are network node interfaces (NNIs). The switch dynamically selects the dual-purpose port media type that first links up. However, you can use the media-type interface configuration command to manually select the RJ-45 connector or the SFP module connector. For information about configuring a dual-purpose port, see the “Configuring a Dual-Purpose Port” section.
Each dual-purpose port has two LEDs: one shows the status of the SFP module port, and one shows the status of the RJ-45 port. The port LED is on for whichever connector is active. For more information about the LEDs, see the hardware installation guide.
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 default, the Cisco Connected Grid switch provides VLAN isolation between UNIs or ENIs. UNIs and ENIs cannot exchange traffic unless they are changed to NNIs or assigned to a UNI-ENI community VLAN.
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 6).
Figure 6 Connecting VLANs with the Switch
When the IP services image is running on the switch, routing can be enabled on the switch. 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. 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.
Prerequisites
Note
Guidelines and Limitations
The switch supports a total of 1005 VLANs and SVIs.
You must configure a VLAN interface and assign it an IP address when you route traffic on the VLAN.
When using the interface range global configuration command, note these guidelines:
–
–
–
–
Note
- 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.
When using the define interface-range global configuration command, note these guidelines:
–
–
–
–
Note
- You must add a space between the first interface number and the hyphen when entering an interface-range. For example, gigabitethernet 0/1 - 2 is a valid range; gigabitethernet 0/1-2 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 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.
Speed and Duplex Configuration
When configuring an interface speed and duplex mode, note these guidelines:
- You can configure interface speed on Fast Ethernet (10/100-Mbps) and Gigabit Ethernet (10/100/1000-Mbps) ports. You can configure Fast Ethernet ports to full-duplex, half-duplex, or to autonegotiate mode. You can configure Gigabit Ethernet ports to full-duplex mode or to autonegotiate. You also can configure Gigabit Ethernet ports to half-duplex mode if the speed is 10 or 100 Mbps. Half-duplex mode is not supported on Gigabit Ethernet ports operating at 1000 Mbps.
- With the exception of when 1000BASE-T SFP modules are installed in the SFP module slots, 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 slot, you can configure speed as 10, 100, or 1000 Mbps, or auto, but not as nonegotiate.
On a 100BASE-FX SFP module, you cannot configure the speed as nonegotiate.
- You cannot configure duplex mode on SFP module ports. They operate in full-duplex mode except in these situations:
–
–
- 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.
- 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. On the Cisco Connected Grid switch, STP is supported on NNIs by default and can be enabled on ENIs. UNIs do not support STP.
Caution
Changing the interface type removes the speed and duplex configurations. The switch configures both media types to autonegotiate speed and duplex (the default). If you configure auto-select, you cannot configure the speed and duplex interface configuration commands.
When you configure sfp or rj45 media type, the non-configured type is disabled, even if there is a connector installed in that interface and no connector in the configured one.
When the media type is auto-select, the switch uses these criteria to select the type:
Note
- If only one connector is installed, that interface is active and remains active until the media is removed or the switch is reloaded.
- If you install both types of media in an enabled dual-purpose port, the switch selects the active link based on which type is installed first.
- If both media are installed in the dual-purpose port, and the switch is reloaded or the port is disabled and then reenabled through the shutdown and the no shutdown interface configuration commands, the switch gives preference to the SFP module interface.
See the media-type interface configuration command in the Cisco IOS Interface and Hardware Component Command Reference for more information.
- Be sure to refer to your switch Hardware Installation Guide for all power guidelines before installing and configuring the system.
- We recommend that you enable power policing when PoE is enabled on your switch.
You cannot set the MTU size for an individual interface. You set the MTU size for all 10/100 or all Gigabit Ethernet interfaces on the switch.
Default Settings
Flow control is set to receive : off. It is always off for sent packets.
Disabled on all Ethernet ports. See the “Related Documents” section for information on EtherChannel configuration.
Port blocking (unknown multicast and unknown unicast traffic)
Disabled (not blocked) (only Layer 2 interfaces). See the “Related Documents” section for information on traffic control features.
Disabled. See the “Related Documents” section for information on traffic control features.
Disabled (only Layer 2 interfaces). See the “Related Documents” section for information on traffic control features.
Disabled. See the “Related Documents” section for information about Port Fast configuration.
Note The switch might not support a pre-standard powered device—such as Cisco IP phones and access points that do not fully support 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.
Flow control is set to receive : off. It is always off for sent packets.
Disabled on all Ethernet ports. See the “Related Documents” section for information on EtherChannel configuration.
Port blocking (unknown multicast and unknown unicast traffic)
Disabled (not blocked) (only Layer 2 interfaces). See the “Related Documents” section for information on traffic control features.
Disabled. See the “Related Documents” section for information on traffic control features.
Disabled (only Layer 2 interfaces). See the “Related Documents” section for information on traffic control features.
Using the Switch USB Port
The switch has one USB mini-Type B console port on the front panel.
Note
Use the supplied USB Type A-to-USB mini-Type B cable to connect a PC or other device to the switch. The connected device must include a terminal emulation application. When the switch detects a valid USB connection to a powered-on device that supports host functionality (such as a PC), input from the RJ-45 console is immediately disabled, and input from the USB console is enabled. Removing the USB connection immediately reenables input from the RJ-45 console connection. A LED on the switch shows which console connection is in use.
Console Port Change Logs
At software startup, a log shows whether the USB or the RJ-45 console port is active. The switch first displays the RJ-45 media type.
In the sample output, the switch has a connected USB console cable. Because the bootloader did not change to the USB console, the first log from the switch shows the RJ-45 console. A short time later, the console changes and the USB console log appears.
When the USB cable is removed or the PC de-activates the USB connection, the hardware automatically changes to the RJ-45 console interface:
You can configure the console type to always be RJ-45, and you can configure an inactivity timeout for the USB connector.
Configuring the Console Media Type
Follow this procedure to select the RJ-45 console media type. If you configure the RJ-45 console, USB console operation is disabled, and input always remains with the RJ-45 console.
BEFORE YOU BEGIN
Connect the switch to a PC or terminal through the RJ-45 console port. For more information, see the hardware installation guide.
DETAILED STEPS
EXAMPLE
This example disables the USB console media type and enables the RJ-45 console media type.
A log shows that this termination has occurred. This example shows that the console on switch reverted to RJ-45.
*Mar 1 00:25:36.860: %USB_CONSOLE-6-CONFIG_DISABLE: Console media-type USB disabled by system configuration, media-type reverted to RJ45.A log entry shows when a console cable is attached. If a USB console cable is connected to the switch, it is prevented from providing input.
*Mar 1 00:34:27.498: %USB_CONSOLE-6-CONFIG_DISALLOW: Console media-type USB is disallowed by system configuration, media-type remains RJ45.This example reverses the previous configuration and immediately activates the USB console that is connected.
Using Interface Configuration Mode
The switch supports these interface types:
- Physical ports—switch ports, routed ports, UNIs, NNIs, and ENIs
- VLANs—switch virtual interfaces
- Port-channels—EtherChannel interfaces
You can also configure a range of interfaces (see the “Configuring a Range of Interfaces” section).
To configure a physical interface (port), specify the interface type, the module number, and the switch port number, and enter interface configuration mode.
- Type — Fast Ethernet (fastethernet or fa) for 10/100 Mbps Ethernet, 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 Cisco Connected Grid 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, fastethernet 0/1 or gigabitethernet 0/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: gigabitethernet 0/1.
You can identify physical interfaces by physically checking the interface location on the switch. You can also use the show privileged EXEC commands to display information about a specific interface or all the interfaces on the switch. The remainder of this document primarily provides physical interface configuration procedures.
Interface Configuration Process
These general instructions apply to all interface configuration procedures.
Step 1
Step 2
Note
Step 3
Step 4
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 5
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.
BEFORE YOU BEGIN
Review the “Guidelines and Limitations” section.
DETAILED STEPS
EXAMPLE
This example shows how to use the interface range global configuration command to set the speed on ports 1 and 2 to 100 Mbps:
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 802.3x flow control pause frames:
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.
BEFORE YOU BEGIN
Review the “Guidelines and Limitations” section.
DETAILED STEPS
Use the no define interface-range macro_name global configuration command to delete a macro.
EXAMPLE
This example shows how to define an interface-range named enet_list to include ports 1 and 2 and to verify the macro configuration:
This example shows how to create a multiple-interface macro named macro1 and assign all of the interfaces in the range to a VLAN:
This example shows how to enter interface range configuration mode for the interface-range macro enet_list :
This example shows how to delete the interface-range macro enet_list and to verify that it was deleted.
Configuring Ethernet Interfaces
This section includes the following topics:
- Configuring the Port Type
- Configuring Interface Speed and Duplex Mode
- Configuring a Dual-Purpose Port
- Configuring a Power Management Mode on a PoE Port
- Budgeting Power for Devices Connected to a PoE Port
- Configuring IEEE 802.3x Flow Control
- Configuring Auto-MDIX on an Interface
- Adding a Description for an Interface
Configuring the Port Type
By default, all the ports on the switch are configured as NNIs.
You use the port-type interface configuration command to change the port types. You can change the ports on the switch from NNIs to UNIs or ENIs. An ENI has the same characteristics as a UNI, but it can be configured to support CDP, STP, LLDP, and Etherchannel LACP and PAgP.
BEFORE YOU BEGIN
When a port is changed from an NNI to a UNI or ENI, it inherits the configuration of the assigned VLAN, either in isolated or community mode.
When you change a port from NNI to UNI or ENI or the reverse, any features exclusive to the port type revert to the default configuration. For Layer 2 protocols, such as STP, CDP, and LLDP, the default state for UNIs and ENIs is disabled (although they can be enabled on ENIs) and the default state for NNIs is enabled.
Note
DETAILED STEPS
Specify the interface to configure, and enter interface configuration mode.
Enable the port, if necessary. By default, UNIs and ENIs are disabled, and NNIs are enabled.
Entering the no port-type or default port-type interface configuration command returns the port to the default state: UNI for Fast Ethernet ports and NNI for Gigabit Ethernet ports.
EXAMPLE
This example shows how to change a port from a UNI to an NNI and save it to the running configuration.
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, Gigabit Ethernet (10/100/1000-Mbps) ports, and small form-factor pluggable (SFP) module slots supporting SFP modules.
BEFORE YOU BEGIN
Review the “Guidelines and Limitations” section.
Note
DETAILED STEPS
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.
EXAMPLE
This example shows how to set the interface speed to 10 Mbps and the duplex mode to half on a 10/100 Mbps port:
This example shows how to set the interface speed to 100 Mbps on a 10/100/1000 Mbps port:
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 higher priority, to make it data only, or to specify a maximum wattage to disallow high-power powered devices on a port.
Note
BEFORE YOU BEGIN
Note
DETAILED STEPS
EXAMPLE
The following example shows how to set the inline power to the off mode on a switch port:
The following example shows how to allocate power from the system power pool to a switch port:
Budgeting Power for Devices Connected to a PoE Port
When Cisco powered devices are connected to PoE ports, the switch uses Cisco Discovery Protocol (CDP) to determine the actual power consumption of the devices, and the switch adjusts the power budget accordingly. The CDP protocol works with Cisco powered devices and does not apply to IEEE third-party powered devices. For these devices, when the switch grants a power request, the switch adjusts the power budget according to the powered-device IEEE classification. If the powered device is a Class 0 (class status unknown) or a Class 3, the switch budgets 15,400 milliwatts for the device, regardless of the actual amount of power needed. If the powered device reports a higher class than its actual consumption or does not support power classification (defaults to Class 0), the switch can power fewer devices because it uses the IEEE class information to track the global power budget.
By using the power inline consumption wattage configuration command, you can override the default power requirement specified by the IEEE classification. The difference between what is mandated by the IEEE classification and what is actually needed by the device is reclaimed into the global power budget for use by additional devices. You can then extend the switch power budget and use it more effectively.
For example, if the switch budgets 15,400 milliwatts on each PoE port, you can connect only 24 Class 0 powered devices. If your Class 0 device power requirement is actually 5000 milliwatts, you can set the consumption wattage to 5000 milliwatts and connect up to 48 devices. The total PoE output power available on a 24-port or 48-port switch is 65 watts per power supply.
For more information about the IEEE power classifications, see the “Power over Ethernet Ports” section.
Note
When you enter the power inline consumption default wattage or the no power inline consumption default global configuration command, or the power inline consumption wattage or the no power inline consumption interface configuration command this caution message appears:
%CAUTION: Interface interface-id: Misconfiguring the 'power inline consumption/allocation' command may cause damage to the switch and void your warranty. Take precaution not to oversubscribe the power supply.If the power supply is over-subscribed to by up to 20 percent, the switch continues to operate but its reliability is reduced. If the power supply is subscribed to by more than 20 percent, the short-circuit protection circuitry triggers and shuts the switch down.
DETAILED STEPS
Configure the power consumption of powered devices connected to each PoE port on the switch. The range for each device is 4000 to 15400 mW. The default is 15400 mW.
To return to the default setting, use the no power inline consumption default global configuration command.
DETAILED STEPS
To return to the default setting, use the no power inline consumption interface configuration command.
Configuring a Dual-Purpose Port
Some ports on the switches are dual-purpose ports that can be configured as 10/100/100 ports or as small form-factor pluggable (SFP) module ports. Each dual-purpose port is considered as a single interface with dual front ends (an RJ-45 connector and an SFP module connector).
Note
Each dual-purpose port is considered as a single interface with dual front ends (an RJ-45 connector and an SFP module connector). The dual front ends are not redundant interfaces; the switch activates only one connector of the pair.
By default, the dual-purpose ports and the SFP-only module ports are network node interfaces (NNIs).
By default, the switch dynamically selects the dual-purpose port media type that first links up. However, you can use the media-type interface configuration command to manually select the RJ-45 connector or the SFP-module connector. In auto-select mode, the switch gives preference to SFP mode if both copper and fiber-optic signals are simultaneously detected.
Follow this procedure to select which dual-purpose media type to activate. This procedure is optional.
BEFORE YOU BEGIN
Review the “Guidelines and Limitations” section.
DETAILED STEPS
To return to the default setting, use the no media-type interface configuration command.
Configuring IEEE 802.3x Flow Control
802.3x 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 by sending a pause frame to stop sending until the condition clears. 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
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.
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.
Note
BEFORE YOU BEGIN
These rules apply to 802.3x 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 : 802.3x 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.
DETAILED STEPS
Specify the physical interface to be configured, and enter interface configuration mode.
Enable the port, if necessary. By default, UNIs and ENIs are disabled, and NNIs are enabled.
To disable 802.3x flow control, use the flowcontrol receive off interface configuration command.
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.
Note
Auto-MDIX is enabled by default. When you enable auto-MDIX, you must also set the speed and duplex on the interface to auto so that the feature operates 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 3 shows the link states that result from auto-MDIX settings and correct and incorrect cabling.
DETAILED STEPS
To disable auto-MDIX, use the no mdix auto interface configuration command.
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 .
DETAILED STEPS
Specify the interface for which you are adding a description, and enter interface configuration mode.
Use the no description interface configuration command to delete the description.
Configuring Layer 3 Interfaces
The switch must be running the IP services image to support Layer 3 interfaces. The 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. You cannot delete interface VLAN 1.
Note
- 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.
See the “Related Documents” section for information about EtherChannel port interfaces.
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 switch port.
- If you try to create an extended-range VLAN, an error message is generated, and the extended-range VLAN is rejected.
- 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.
BEFORE YOU BEGIN
Note
DETAILED STEPS
To remove an IP address from an interface, use the no ip address interface configuration command.
Configuring the System MTU
The default maximum transmission unit (MTU) size for frames received and sent 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. You can change the MTU size for routed ports by using the system mtu routing global configuration command.
Note
Gigabit Ethernet ports are not affected by the system mtu command. Fast Ethernet ports are not affected by the system mtu jumbo command because jumbo frames are not supported on 10/100 interfaces, including 100BASE-FX and 100BASE-BX SFP modules. If you do not configure the system mtu jumbo command, the setting of the system mtu command applies to all Gigabit Ethernet interfaces.
You cannot set the MTU size for an individual interface. You set the MTU size for all 10/100 or all Gigabit Ethernet interfaces on the switch. When you change the system MTU size, you must reset the switch before the new configuration takes effect. The system mtu routing command does not require a switch reset to take effect.
Note
Frames sizes that can be received by the switch CPU are limited to 1998 bytes, no matter what value was entered with the system mtu or system mtu jumbo commands. Although frames that are forwarded are typically 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.
Because the switch does not fragment packets, it drops:
- Switched packets larger than the packet size supported on the egress interface
- Routed packets larger than the routing MTU value
For example, if the system mtu value is 1998 bytes and the system mtu jumbo value is 5000 bytes, packets up to 5000 bytes can be received on interfaces operating at 1000 Mbps. However, although a packet larger than 1998 bytes can be received on an interface operating at 1000 Mbps, if its destination interface is operating at 10 or 100 Mbps, the packet is dropped.
Routed packets are subjected to MTU checks on the sending ports. The MTU value used for routed ports is derived from the configured system mtu value (not the system mtu jumbo value). That is, the routed MTU is never greater than the system MTU for any VLAN. The routing protocols use the system MTU value when negotiating adjacencies and the MTU of the link. For example, the 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
Follow this procedure to change the MTU size for all 10/100 or Gigabit Ethernet interfaces.
BEFORE YOU BEGIN
If you enter a value that is outside the allowed range for the specific type of interface, the value is not accepted.
DETAILED STEPS
Once the switch reloads, you can verify your settings by entering the show system mtu privileged EXEC command.
Configuring the EtherChannel Between the ESM and Host Router
This section describes how to configure the backplane PortChannel48 interface, which provides communication between the host CGR 2010 and the Ethernet Switch Module (ESM). This section includes the following topics:
- About the Backplane PortChannel48 Interface
- Configuring the Backplane PortChannel48 Interface
- Sample Gigabit Ethernet Interface Configuration on the CGR 2010
Note
About the Backplane PortChannel48 Interface
The CGR 2010 ESM is inserted into the Cisco CGR 2010. The switch module’s backplane interface is called PortChannel48 . PortChannel48 is the backplane interface connected to the CGR 2010 and provides communication between the host router and the switch module.
The PortChannel48 interface consists of eight 10/100 Fast Ethernet physical links that are grouped together to create a FastEtherChannel. PortChannel48 is created automatically when the switch module boots up.
Note
You can configure these interfaces like any other interface with the important exception that you cannot delete the system-created PortChannel48 interface.
You can change the PortChannel48 interface configuration from trunk mode to access mode (that is, non-trunk mode), or configure the PortChannel48 interface as a Layer 3 interface by configuring an IP address on the interface. For details, see “Configuring the Backplane PortChannel48 Interface” section.
Once a port is designated as a trunk port, it will forward and receive tagged frames. Frames belonging to the native VLAN do not carry VLAN tags when sent over the trunk. Conversely, if an untagged frame is received on a trunk port, the frame is associated with the native VLAN for this port.
The backplane PortChannel48 interfaces to the CGR 2010 host router. The router does not recognize spanning tree BPDUs; the spanning Tree Protocol is disabled on the PortChannel48 interface.
PortChannel48 Defaults
By default, the PortChannel48 interface comes up in Layer 2 trunk mode, with 802.1Q trunk encapsulation. 802.1Q is the only encapsulation method supported on the switch module.
Here is how the typical PortChannel and individual physical configuration looks when the switch module comes up the first time:
By default, the PortChannel48 interface is created in Layer 2 trunk mode, which means that the switch module operates in Layer 2 trunk mode with 802.1Q encapsulation carrying VLAN1 by default. This PortChannel48 interface supports load-balancing across multiple physical links, in the same way as the regular user-configured EtherChannel does, using the following parameters:
Configuring the Backplane PortChannel48 Interface
By default, the switch module comes up in Layer 2 trunk mode. This section describes how to configure the PortChannel48 interface for the switch module for each of the following modes:
See QoS Software Configuration Guide for IE 2000U and Connected Grid Switches, the section “Implementing High-Priority Traffic to the Host Router” for information about configuring QoS features for the internal data path between the Ethernet Switch Module (ESM) and the host CGR 2010 router.
Configuring the PortChannel48 Interface for Layer 3 Routing Mode
This section describes how to change from the default Layer 2 trunk mode to Layer 3 routing mode:
Configuring the PortChannel48 Interface for Layer 2 Trunk Mode
These commands configure the PortChannel in Layer 2 Trunk mode.
This command configures both the PortChannel48 interface and its member ports in trunk mode.
Note that every port from FE0/5 to FE0/12 (on the Fiber Model) and ports FE0/9 to FE0/16 (on the Copper Model) should be configured as shown here:
Configuring the PortChannel48 Interface for Layer 2 Access Mode
These commands configure the PortChannel in Layer 2 Access mode. Note that every port from FE0/5 to FE0/12 (on the Fiber Model) and ports FE0/9 to FE0/16 (on the Copper Model) should be configured as shown here:
Sample Gigabit Ethernet Interface Configuration on the CGR 2010
This section describes the Gigabit Ethernet configuration required on the host CGR 2010 to implement the PortChannel48 interface on the router.
Interface GigabitEthernet0/ < slot 0 or 2> /0 is the backplane interface connected to the switch module. This interface can also have subinterfaces for each of the networks.
Interface to Receive Routed Traffic for Network 20.70.0.0
Interface to Receive Bridge Traffic on bridge-group 60
Backplane Subinterface to Receive Bridged Traffic on VLAN 60
Backplane Subinterface to Receive Routed Traffic on VLAN 70
Monitoring and Maintaining Interfaces
These sections contain interface monitoring and maintenance information:
- Monitoring Interface Status
- Using FEFI to Maintain the Fiber FE Interfaces
- Clearing and Resetting Interfaces and Counters
- Shutting Down and Restarting the Interface
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 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 command reference documents listed in the “Related Documents” section.
Using FEFI to Maintain the Fiber FE Interfaces
A far end fault is an error in the link that one station detects but the other does not, such as a disconnected Tx wire. In this example, the sending station still receives valid data and detects that the link is good through the link integrity monitor. The sending station does not detect that its own transmission is not being received by the other station. A 100BASE-FX station that detects a remote fault like this modifies its transmitted IDLE stream to send a special bit pattern (FEFI IDLE pattern) to inform the neighbor of the remote fault. The FEFI-IDLE pattern then triggers a shutdown of the remote port (notconnect).
Fiber FastEthernet hardware uses Far End Fault Indication (FEFI) to bring the link down on both sides of the link in these situations. A similar function is provided by link negotiation for Gigabit Ethernet. FEFI is not supported on copper ports, which do not usually have issues in which one station can detect while the other cannot. Copper ports use Ethernet link pulses to monitor the link.
With FEFI, no forwarding loop occurs because there is no connectivity between the ports. If the link is up on one side and down on the other, however, blackholing of traffic might occur. Use Unidirectional Link Detection (UDLD) to prevent traffic blackholing.
Note
Default FEFI Configuration
FEFI is enabled globally on the switch by default, however it applies only to the fiber Fast Ethernet SFP interfaces on the switch.
Using FEFI on GE SFP Ports
FEFI can be used on the switch Gigabit Ethernet (GE) SFP ports when the GE ports are connected with 100FX Ethernet cable. However, using this cable type limits the GE interface to 100 MB/s.
Configuring FEFI
This section describes how to enable and disable FEFI on the switch, and includes the following topics:
Configuration Command
FEFI is enabled by default on the switch. Enter the no form of the fefi command to disable FEFI on the switch:
To reenable FEFI on the switch, enter the fefi global configuration command:
Link Status When Enabling or Disabling FEFI
When FEFI is enabled or disabled on the switch with the fefi command, the SFP interfaces are reset and the interface link status changes. If only one SFP interface is up and FEFI is enabled or disabled, the interface is reset. The system displays the messages shown below, and the link is reestablished immediately.
CGS2520(config)# *Mar 4 04:12:28.569: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to downClearing and Resetting Interfaces and Counters
Table 5 lists the privileged EXEC mode clear commands that you can use to clear counters and reset interfaces.
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 you specify optional arguments that clear only a specific interface type from a specific interface number.
Note
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.
DETAILED STEPS
interface { vlan vlan-id } | {{ fastethernet | gigabitethernet } interface-id } | { port-channel port-channel-number }
Use the no shutdown interface configuration command to enable an 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 display.
Related Documents
- Cisco IOS Master Command List, All Releases
- Cisco IOS 15.2M&T Command References
- Cisco IE 2000U Switch Hardware Installation Guide
- See Layer 2 Switching Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches for the following information:
–
–
–
–
–
–
–
–
- See Unicast Routing Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches for the following information:
–
- See Multicast Routing Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches for the following information:
–
- See System Management Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches for the following information:
–
–
- See High Availability and Redundancy Software Configuration Guide for Cisco IE 2000U and Connected Grid Switches for the following information:
–
–
- See QoS Software Configuration Guide for IE 2000U and Connected Grid Switches for the following information:
–
- See Cisco IOS Basics and File Management for Cisco IE 2000U and Connected Grid Switches for the following information:
–
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/c/en/us/td/docs/general/whatsnew/whatsnew.html.
Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation as an RSS feed and delivers content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Related Documents” section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)