Release Notes for the Catalyst 2960-C Switch, Cisco IOS Release 12.2(55)EX1 and Later

---

Supported Hardware

 

1.PoE = Power over Ethernet 2.SFP = small form-factor pluggable

 

3.SFP = Small-form pluggable. 4.CWDM = coarse wavelength-division multiplexer. 5.MMF = multimode fiber. 6.SMF = single-mode fiber.

Device Manager System Requirements

Hardware Requirements

 

7.We recommend 1 GHz. 8.We recommend 1 GB DRAM.

Software Requirements

• Windows 2000, XP, Vista, and Windows Server 2003.
• Internet Explorer 6.0 or 7.0, and Firefox up to version 27, with JavaScript enabled.

Device Manager verifies the browser version when starting a session and does not require a plug-in.

Finding the Software Version and Feature Set

The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).

You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.

You can also use the dir filesystem : privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.

Deciding Which Files to Use

The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the CLI, use the tar file and the archive download-sw privileged EXEC command.

 

Archiving Software Images

Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release to which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.

Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/prod/collateral/iosswrel/ps8802/ps6969/ps1835/
prod_bulletin0900aecd80281c0e.html

You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.

---

Note Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.

You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the “Basic File Transfer Services Commands” section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 :
http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_t1.html

Upgrading a Switch by Using the Device Manager

You can upgrade switch software by using the device manager. For detailed instructions, click Help.

---

Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.

Upgrading a Switch by Using the CLI

This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.

To download software, follow these steps:

---

Step 1 Use Table 4 to identify the file that you want to download.

Step 2 Download the software image file:

a. If you are a registered customer, go to this URL and log in.

http://www.cisco.com/cisco/web/download/index.html

b. Navigate to Switches > LAN Switches - Access.

c. Navigate to your switch model.

d. Click IOS Software and select the latest Cisco IOS release.

Download the image that you identified in Step 1.

Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.

For more information, see Appendix B in the software configuration guide for this release.

Step 4 Log into the switch through the console port or a Telnet session.

Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:

For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.

Step 6 Download the image file from the TFTP server to the switch. If you are installing the same software version that is currently on the switch, overwrite the current image by entering this privileged EXEC command:

The /overwrite option overwrites the software image in flash memory with the downloaded one.

The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.

For // location, specify the IP address of the TFTP server.

For / directory / image-name .tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.

This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:

You can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite keyword with the /leave-old-sw keyword.

 

Recovering from a Software Failure

For recovery procedures, see the “Troubleshooting” chapter in the software configuration guide for this release.

Cisco IOS Limitations

• Configuration
• Ethernet
• IP Telephony
• Multicasting
• Power
• QoS
• RADIUS
• Smart Install
• SPAN and RSPAN
• Trunking
• VLAN

Configuration

• A static IP address might be removed when the previously acquired DHCP IP address lease expires.

This problem occurs under these conditions:

– When the switch is booted up without a configuration (no config.text file in flash memory).

– When the switch is connected to a DHCP server that is configured to give it an address (the dynamic IP address is assigned to VLAN 1).

– When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.

The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)

• When connected to some third-party devices that send early preambles, a switch port operating at 100 Mb/s full duplex or 100 Mb/s half duplex might bounce the line protocol up and down. The problem is observed only when the switch is receiving frames.

The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)

• When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked

The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)

• A traceback error occurs if a crypto key is generated after an SSL client session.

There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)

• The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.

The workaround is to configure aggressive UDLD. (CSCsh70244).

• When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.

The workaround is to always enter a nonzero value for the timeout value when you enter the boot host retry timeout timeout-value command. (CSCsk65142)

• A ciscoFlashMIBTrap message appears during switch startup. This does not affect switch functionality. (CSCsj46992)

Ethernet

• Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC.

If this happens, uneven traffic distribution occurs on EtherChannel ports.

Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:

– for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip

– for incrementing source-ip traffic, configure load balance method as src-ip

– for incrementing dest-ip traffic, configure load balance method as dst-ip

– Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (i.e. 2, 4, or 8)

For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)

IP Telephony

• After you change the access VLAN on a port that has IEEE 802.1x enabled, the IP phone address is removed. Because learning is restricted on IEEE 802.1x-capable ports, it takes approximately 30 seconds before the address is relearned. No workaround is necessary. (CSCea85312)
• Some access point devices are incorrectly discovered as IEEE 802.3af Class 1 devices. These access points should be discovered as Cisco prestandard devices. The show power inline user EXEC command shows the access point as an IEEE Class 1 device. The workaround is to power the access point by using an AC wall adaptor. (CSCin69533)
• The Cisco 7905 IP Phone is error-disabled when the phone is connected to wall power.

The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)

Multicasting

• If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number specified by the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise.

The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)

• IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port.

There is no workaround. (CSCdy82818)

• If an IG MP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:

– If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.

– If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.

There is no workaround. (CSCec20128)

• When IGMP snooping is disabled and you enter the switchport block multicast interface configuration command, IP multicast traffic is not blocked.

The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.

There is no workaround. (CSCee16865)

• Incomplete multicast traffic can be seen under either of these conditions:

– You disable IP multicast routing or re-enable it globally on an interface.

– A switch mroute table temporarily runs out of resources and recovers later.

The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)

After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.

Use one of these workarounds:

– Cancel membership in the multicast group by using the no ip igmp join-group group-address interface configuration command on an SVI.

– Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id global configuration command. (CSCeh90425)

Power

• Entering the shutdown and the no shutdown interface configuration commands on the internal link can disrupt the PoE operation. If a new IP phone is added while the internal link is in shutdown state, the IP phone does not get inline power if the internal link is brought up within 5 minutes.

The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. (CSCeh45465)

QoS

• Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos queue-set output global configuration command. The ratio of buffer size to threshold level should be greater than 10 to avoid disabling the queue. The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)
• When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing mechanism supported on each platform might be different. There is no workaround. (CSCee22591)
• If you configure a large number of input interface VLANs in a class map, a traceback message similar to this might appear:

There is no impact to switch functionality.

There is no workaround. (CSCtg32101)

RADIUS

• RADIUS change of authorization (COA) reauthorization is not supported on the critical auth VLAN.

There is no workaround. (CSCta05071)

Smart Install

• If the director in the Smart Install network is between an access point and the DHCP server, the access point tries to use the Smart Install feature upgrade, even though access points are not supported devices. The upgrade fails because the director does not have an image and a configuration file for the access point.

There is no workaround. (CSCtg98656)

SPAN and RSPAN

• Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local SPAN session. The workaround is to use the monitor session session_number destination { interface interface-id encapsulation replicate} global configuration command for local SPAN. (CSCed24036)

Trunking

• The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface.

There is no workaround. (CSCdz33708)

• IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no workaround. (CSCdz42909).
• For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics.

There is no workaround. (CSCec35100).

VLAN

• If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail.

The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)

• When line rate traffic is passing through a dynamic port, and you enter the switchport access vlan dynamic interface configuration command for a range of ports, the VLANs might not be assigned correctly. One or more VLANs with a null ID appears in the MAC address table instead.

The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)

Device Manager Limitations

• When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not launch.

The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)

Cisco IOS Notes

• If the switch requests information from the Cisco Secure Access Control Server (ACS) and the message exchange times out because the server does not respond, a message similar to this appears:

If this message appears, check that there is network connectivity between the switch and the ACS. You should also check that the switch has been properly configured as an AAA client on the ACS

Device Manager Notes

• Although visible in the Device Manager online help graphic, the USB Type A port is not supported on the Catalyst 2960CPD-8PT-L and the 2960CPD-8TT-L switches.
• You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the CLI.
• When the switch is running a localized version of the device manager, the switch displays settings and status only in English letters. Input entries on the switch can only be in English letters.
• For device manager sessions on Internet Explorer, popup messages in Japanese or in simplified Chinese can appear as garbled text. These messages appear properly if your operating system is in Japanese or Chinese.
• We recommend this browser setting to speed up the time needed to display the device manager from Microsoft Internet Explorer:

1. Choose Tools > Internet Options.

2. Click Settings in the “Temporary Internet files” area.

3. From the Settings window, choose Automatically.

4. Click OK.

5. Click OK to exit the Internet Options window.

• The HTTP server interface must be enabled to display the device manager. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.

Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:

 

• The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.

If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.

If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.

Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface authentication method:

 

Updates to the Catalyst 3560-C and 2960-C Switch Hardware Documentation

• Network Assistant supported only on these switches:

Catalyst 2960CG-8TC-L, 2960CPD-8PT-L, and 2960CPD-8TT-L

• Update to the “Rear Panel” section in the “Overview Chapter” of the hardware guide:

The heat sink fins are present on the Catalyst 3560CG-8PC-S, 2960C-8PC-L, 2960C-12PC-L 3560C-8PC-S, and 3560C-12PC-S switches.

Updates to the Catalyst 2960 Switch Software Configuration Guide

• PoE Uplinks and PoE Pass-Through Capability
• The Catalyst 2960-C SDM Template

PoE Uplinks and PoE Pass-Through Capability

The Catalyst 2960-C compact switches can receive power on the two uplink Gigabit Ethernet ports from a PoE or PoE+ capable-switch (for example a Catalyst 3750-X or 3560-X switch). The switch can also receive power from an AC power source when you use the auxiliary power input. When both uplink ports and auxiliary power are connected, the auxiliary power input takes precedence.

The Catalyst 2960CPD-8PT switch can provide power to end devices through the eight downlink ports in one of two ways:

• When the switch receives power from the auxiliary power input, it acts like any other PoE switch and can supply power to end devices connected to the eight downlink ports according to the total power budget. Possible end devices are IP phones, video cameras, and access points.
• When the switch receives power through one or both uplink ports, it can provide PoE pass-through, taking the surplus power from the PoE or PoE+ uplinks and passing it through the downlink ports to end devices. The available power depends on the power drawn from the uplink ports and varies, depending if one or both uplink ports are connected and if the source is PoE or PoE+.

The downlink ports are PoE-capable, and each port can supply up to 15.4 W per port to a connected powered device. When the switch draws power from the uplink ports, the power budget (the available power on downlink ports) depends on the power source options shown in Table 5 . When the switch receives power through the auxiliary connector, the power budget is similar to that of any other PoE switch.

 

You can configure the power management, budgeting, and policing the same as with any other Catalyst 2960 or 2960-S PoE switch. See the configuration information starting with the “ Configuring Power Management Mode on a PoE Port” section in the Catalyst 2960 and 2960-S Software Configuration Guide.

The show env power inline privileged EXEC command provides information about powering options and power backup on your switch:

You can see the available power and the power required by each connected device by entering the show power inline privileged EXEC command. This is an example of output from a Catalyst 2960CPD-8PT:

Enter the show power inline police privileged EXEC command to see power monitoring status. This is an example of output from a Catalyst 2960CPD-8PT:

The Catalyst 2960CPD-8TT and Catalyst 2960CG-8TC downlink ports cannot provide power to end devices. This is an example of output from the show power inline command on a C2960CPD-8TT switch:

The show power inline dynamic-priority command shows the power priority of each port:

The Catalyst 2960-C SDM Template

The Catalyst 2960-C Gigabit Ethernet switch supports only the SDM default template, which is different from the Catalyst 2960 or Catalyst 2960-S default template. Because of the compact size of the switch, memory capacity is less, which can result in reduced support for a feature, for example, allowing fewer MAC addresses. All Catalyst 2960-C default templates support 0 routed interfaces and 255 VLANs.

On the Catalyst 2960C Gigabit Ethernet switches, the default template includes support for IPv6 features. On the Catalyst 2960CPD-8PT and 2960CPD-8TT Fast Ethernet switches, the default template does not include support for IPv6 features and IPv6 features. IPv6 host functions or IPv6 MLD snooping, are not supported for this release.

 

Because the Catalyst 2960-C Gigabit Ethernet switch supports only the default template, entering the sdm prefer global configuration command has no effect.

Starting with Cisco IOS Release 12.2(55)EX3, Catalyst 2960-C Fast Ethernet switches support multiple templates: default, dual IPv4 and IP v6, and QoS. All Catalyst 2960-C templates support 0 routed interfaces and 255 VLANs.

See the sdm prefer and show sdm prefer commands in the next section for details on the features supported.

Updates to the Catalyst 2960 Switch Command Reference

These commands are new or modified:

• auto qos video (document update not specific to the Catalyst 2960-C switch)
• sdm prefer
• show power inline
• show sdm prefer

 

Syntax Description

 

Defaults

Auto-QoS video is disabled on the port.

When auto-QoS is enabled, it uses the ingress packet label to categorize traffic, to assign packet labels, and to configure the ingress and egress queues.

 

9.STP = Spanning Tree Protocol. 10.BPDU = bridge protocol data unit. 11.DSCP = Differentiated Services Code Point. 12.CoS = class of service.

 

13.SRR = shaped round robin. Ingress queues support shared mode only.

 

 

Command History

 

Usage Guidelines

Use this command to configure the QoS appropriate for video traffic within the QoS domain. The QoS domain includes the switch, the network interior, and edge devices that can classify incoming traffic for QoS.

Auto-Qos configures the switch for video connectivity with a Cisco TelePresence system and a Cisco IP camera.

To take advantage of the auto-QoS defaults, you should enable auto-QoS before you configure other QoS commands. You can fine-tune the auto-QoS configuration after you enable auto-QoS.

---

Note The switch applies the auto-QoS-generated commands as if the commands were entered from the CLI. An existing user configuration can cause the application of the generated commands to fail or to be overridden by the generated commands. These actions occur without warning. If all the generated commands are successfully applied, any user-entered configuration that was not overridden remains in the running configuration. Any user-entered configuration that was overridden can be retrieved by reloading the switch without saving the current configuration to memory. If the generated commands are not applied, the previous running configuration is restored.

If this is the first port on which you have enabled auto-QoS, the auto-QoS-generated global configuration commands are executed followed by the interface configuration commands. If you enable auto-QoS on another port, only the auto-QoS-generated interface configuration commands for that port are executed.

When you enable the auto-QoS feature on the first port, these automatic actions occur:

• QoS is globally enabled ( mls qos global configuration command), and other global configuration commands are added.

After auto-QoS is enabled, do not modify a policy map or aggregate policer that includes AutoQoS in its name. If you need to modify the policy map or aggregate policer, make a copy of it, and change the copied policy map or policer. To use the new policy map instead of the generated one, remove the generated policy map from the interface, and apply the new policy map.

To display the QoS configuration that is automatically generated when auto-QoS is enabled, enable debugging before you enable auto-QoS. Use the debug auto qos privileged EXEC command to enable auto-QoS debugging. For more information, see the debug auto qos command.

To disable auto-QoS on a port, use the no auto qos video interface configuration command. Only the auto-QoS-generated interface configuration commands for this port are removed. If this is the last port on which auto-QoS is enabled and you enter the no auto qos video command, auto-QoS is considered disabled even though the auto-QoS-generated global configuration commands remain (to avoid disrupting traffic on other ports affected by the global configuration). You can use the no mls qos global configuration command to disable the auto-QoS-generated global configuration commands. With QoS disabled, there is no concept of trusted or untrusted ports because the packets are not modified (the CoS, DSCP, and IP precedence values in the packet are not changed). Traffic is switched in pass-through mode (packets are switched without any rewrites and classified as best effort without any policing).

Examples

This example shows how to enable auto-QoS for a Cisco Telepresence interface with conditional trust. The interface is trusted only if a Cisco Telepresence device is detected; otherwise, the port is untrusted.

You can verify your settings by entering the show auto qos video interface interface-id privileged EXEC command.

 

Related Commands

 

Syntax Description

 

Defaults

The default template provides a balance to all features.

 

Command History

 

Usage Guidelines

You must reload the switch for the configuration to take effect.

If you enter the show sdm prefer command before you enter the reload privileged EXEC command, the show sdm prefer command shows the template currently in use and the template that will become active after a reload.

Use the no sdm prefer command to set the switch to the default template.

Template resources are based on 0 routed interfaces and 255 VLANs, except for the LAN base routing template, which supports 8 routed interfaces and 255 VLANs.

A Catalyst 2960-S switch running the LAN base image uses a default template that includes maximum resources for all supported features; it does not require the dual or qos templates. However, to enable static routing on the Catalyst 2960-S switch, you must configure the lanbase-routing template.

Catalyst 2960-C Gigabit Ethernet switches support only a default template.

For Catalyst 2960 switches and Catalyst 2960-C Fast Ethernet switches:

• Do not use the ipv4-and-ipv6 template if you do not plan to enable IPv6 functionality on the switch. Entering the sdm prefer ipv4-and-ipv6 global configuration command divides resources between IPv4 and IPv6, which limits those allocated to IPv4 forwarding.

For Catalyst 2960 switches:

• Do not use the routing template if you are not using static routing on your switch. Entering the sdm prefer lanbase-routing global configuration command prevents other features from using the memory allocated to unicast routing in the routing template.

Enter the show sdm prefer privileged EXEC command to see which template is active on the switch or to see the resource allocations of any template.

 

 

 

 

Examples

This example shows how to use the QoS template:

This example shows how to configure the dual IPv4-and-IPv6 default template on a switch:

This example shows how to configure the default template on a switch:

 

Related Commands

 

Syntax Description

 

Command History

Examples

This is an example of output from the show power inline command on a Catalyst 2960CPD-8PT: It shows the available power and the power required by each connected device by entering

Table 14 describes the output fields.

 

The Catalyst 2960CPD-8TT and Catalyst 2960CG-8TC downlink ports cannot provide power to end devices. This is an example of output from the show power inline command on a Catalyst 2960CPD-8TT switch:

This is an example of the output of the show power inline police privileged EXEC command on a Catalyst 2960CPD-8PT:

Table 15 describes the output fields.

 

This is an example of output from the show power inline police interface-id command on a switch.

This is an example of output from the show power inline consumption command on all PoE switch ports:

This is an example of output from the show power inline dynamic-priority command on a switch.

 

Related Commands

 

Syntax Description

 

Command History

 

Usage Guidelines

When you change the SDM template on a switch by using the sdm prefer global configuration command, you must reload the switch for the configuration to take effect. If you enter the show sdm prefer command before you enter the reload privileged EXEC command, the show sdm prefer command shows the template currently in use and the template that will become active after a reload.

A Catalyst 2960-S switch running the LAN base image uses a default template that includes maximum resources for all supported features or the lanbase-routing template to enable static routing.

Catalyst 2960-C Gigabit Ethernet switches use only a default template for maximum resource support.

The numbers displayed for each template represent an approximate maximum number for each feature resource. The actual number might vary, depending on the actual number of other features configured.

All Catalyst 2960-C switches support 0 routed interfaces and 255 VLANs.

Examples

This is an example of output from the show sdm prefer default command on a Catalyst 2960 switch:

This is an example of output from the show sdm prefer command on a Catalyst 2960 switch showing the existing template:

This is an example of output from the show sdm prefer default command on a Catalyst 2960-S switch:

This is an example of output from the show sdm prefer qos command on a Catalyst 2960 switch:

This is an example of output from the show sdm prefer command on a Catalyst 2960-C Gigabit Ethernet switch:

Updates to the Catalyst 2960 System Message Guide

These system messages are new for the Catalyst 2960-C switch:

Error Message CDP_PD-2-POWER_LOW: 15.4 W power - NEGOTIATED [char] on port [char]

Explanation Power is being received on the uplink ports, and the power source has negotiated a power level that is 15.4 W The first [char] is the device providing power, and the second [char] is the uplink port or ports.

Recommended Action No action is required.

Error Message CDP_PD-4-POWER_OK: 30 W power - NEGOTIATED [char] on port [char]

Explanation Power is being received on the uplink ports, and the power source has negotiated a power level that is the maximum of 30 W. The first [char] is the device providing power, and the second [char] is the uplink port or ports.

Recommended Action No action is required.

Error Message PDPSE-5-PWR_SRC_DISC: Power source change from [chars] to [chars]. Current power source is [chars]

Explanation A new power source, either auxiliary power or through the uplink ports, was discovered, causing a power source change. The first [chars] is the previous power source (port number of the uplink port or auxiliary power), the second [chars] is the discovered power source (uplink port number or auxiliary power). The third [chars] is the power source that is being used.

Recommended Action No action is required.

---

This document is to be used in conjunction with the documents listed in the “Related Documentation” 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 used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2011–2012 Cisco Systems, Inc. All rights reserved.