Cisco 3020 -  Catalyst Blade Switch Release Note
Cisco 3020 -  Catalyst Blade Switch Release Note

Cisco 3020 - Catalyst Blade Switch Release Note

Release notes for the cisco catalyst blade switch 3020 for hp, ciscoã‚â iosã‚â releaseã‚â 12.2(40)se1 and later
Hide thumbs Also See for 3020 - Cisco Catalyst Blade Switch:

Advertisement

Release Notes for the Cisco Catalyst
Blade Switch 3020 for HP,
Cisco IOS Release 12.2(40)SE1 and Later
Revised January 9, 2008
Cisco IOS Release 12.2(40)SE1 and 12.2(40)SE2 run on the Cisco Catalyst Blade Switch 3020 for HP,
also referred to as the switch.
If you wish to use Device Manager to upgrade the switch from Cisco IOS Release 12.2(35)SE through
Note
Cisco IOS Release 12.2(40)SE1 (the LAN Base image) to Cisco IOS Release 12.2(44)SE or later (the IP
base image), you must first upgrade to Cisco IOS Release 12.2(40)SE2.
These release notes include important information about Cisco IOS Release 12.2(40)SE1 and later and
any limitations, restrictions, and caveats that apply to them. Verify that these release notes are correct
for your switch:
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
If your switch is on, use the show version privileged EXEC command. See the
Software Version and Feature Set" section on page
If you are upgrading to a new release, see the software upgrade filename for the software version.
See the
"Deciding Which Files to Use" section on page
For the complete list of Cisco Catalyst Blade Switch 3020 for HP documentation, see the
Documentation" section on page
You can download the switch software from this site (registered Cisco.com users with a login password):
http://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches
This software release is part of a special release of Cisco IOS software that is not released on the same
8-week maintenance cycle that is used for other platforms. As maintenance releases and future software
releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
© 2008 Cisco Systems, Inc. All rights reserved.
4.
52.
"Finding the
4.
"Related

Advertisement

Table of Contents
loading

Summary of Contents for Cisco 3020 - Cisco Catalyst Blade Switch

  • Page 1 Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(40)SE1 and Later Revised January 9, 2008 Cisco IOS Release 12.2(40)SE1 and 12.2(40)SE2 run on the Cisco Catalyst Blade Switch 3020 for HP, also referred to as the switch. If you wish to use Device Manager to upgrade the switch from Cisco IOS Release 12.2(35)SE through Note Cisco IOS Release 12.2(40)SE1 (the LAN Base image) to Cisco IOS Release 12.2(44)SE or later (the IP...
  • Page 2: System Requirements

    Contents Contents This information is in the release notes: “System Requirements” section on page 2 • “Upgrading the Switch Software” section on page 3 • “Installation Notes” section on page 6 • “New Software Features” section on page 6 • “Limitations and Restrictions”...
  • Page 3: Table Of Contents

    Upgrading the Switch Software Hardware Requirements Table 2 lists the minimum hardware requirements for running the device manager. Table 2 Minimum Hardware Requirements Processor Speed DRAM Number of Colors Resolution Font Size Intel Pentium II 64 MB 1024 x 768 Small 1.
  • Page 4: Finding The Software Version And Feature Set" Section

    Upgrading the Switch Software 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:).
  • Page 5: Upgrading A Switch By Using The Device Manager" Section

    Upgrading the Switch Software Although you can copy any file on the flash memory to the TFTP server, it is time consuming to copy Note 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.
  • Page 6: Recovering From A Software Failure" Section

    Installation Notes 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.
  • Page 7: Cisco Ios Limitations" Section

    Limitations and Restrictions Limitations and Restrictions You should review this section before you begin working with the switch. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
  • Page 8: Ethernet" Section

    Limitations and Restrictions 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.
  • Page 9: Mac Addressing Multicasting" Section

    Limitations and Restrictions MAC Addressing Multicasting These are the multicasting limitations: 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.
  • Page 10: Qos" Section

    Limitations and Restrictions number of interfaces configured with the logging event-spanning-tree interface configuration command. This condition adversely affects how the switch operates and could cause problems such as STP convergence delay. High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.
  • Page 11: Device Manager Limitations" Section

    Important Notes Trunking These are the trunking limitations: 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.
  • Page 12 Important Notes Cisco IOS Notes These notes apply to Cisco IOS software: Cisco IOS Release 12.2(40)SE1 and later • If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE1 (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message: AutoQoS Error: ciscophone input service policy was not properly applied policy map AutoQoS-Police-CiscoPhone not configured...
  • Page 13 Important Notes Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface: Command Purpose Step 1 configure terminal Enter global configuration mode. Step 2 ip http authentication {aaa | enable | Configure the HTTP server interface for the type of authentication that local} you want to use.
  • Page 14: Open Caveats

    Open Caveats Open Caveats This section describes the open severity 3 caveats for this software release. Open Cisco IOS Caveats This section describes the open severity 3 Cisco IOS configuration caveats with possible unexpected activity in this software release: CSCei63394 •...
  • Page 15 Open Caveats CSCsd60718 • When you enter the no speed interface configuration command, the Ethernet interface speed does not return to its default setting. This affects interfaces Gi0/17 to Gi0/20, Gi0/23, and Gi0/24. This does not affect interfaces Gi0/21 and Gi0/22. The workaround is either to enter the speed interface configuration command auto keyword to change the interface speed to the default setting or to explicitly set the speed.
  • Page 16 Open Caveats CSCsi63999 • Changing the spanning tree mode from rapid STP to MSTP can cause tracebacks when the virtual port error-disable feature is enabled when the STP mode is changed. There is no workaround. CSCsj21718 • When system jumbo MTU size is configured on a switch and the egress ports can support jumbo frames, the egress SPAN jumbo frames are not forwarded to the SPAN destination ports.
  • Page 17: Documentation Updates

    Resolved Caveats Resolved Caveats These sections describe the caveats that have been resolved in this release: CSCse06827 • When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state. The workaround is to configure the burst interval to more than 1 second.
  • Page 18: Dot1X Timeout Tx-Period" Section

    Documentation Updates “Updates to System Messages Guides” section on page 51 • “Changed System Messages” section on page 52 • Updates to Software Configuration Guide These features were added to the software configuration guide: “dot1x Timeout TX-Period” section on page 18 •...
  • Page 19: Understanding Configuration Replacement And Rollback

    Documentation Updates Understanding Configuration Replacement and Rollback To use the configuration replacement and rollback feature, you should understand these concepts: Archiving a Configuration, page 19 • Replacing a Configuration, page 19 • Rolling Back a Configuration, page 20 • Archiving a Configuration The configuration archive provides a mechanism to store, organize, and manage an archive of configuration files.
  • Page 20: Configuration Guidelines

    Documentation Updates Rolling Back a Configuration You can also use the configure replace command to roll back changes that were made since the previous configuration was saved. Instead of basing the rollback operation on a specific set of changes that were applied, the configuration rollback capability reverts to a specific configuration based on a saved configuration file.
  • Page 21: Performing A Configuration Replacement Or Rollback Operation

    Documentation Updates Command Purpose Step 3 path url Specify the location and filename prefix for the files in the configuration archive. Step 4 maximum number (Optional) Set the maximum number of archive files of the running configuration to be saved in the configuration archive. number—Maximum files of the running configuration file in the configuration archive.
  • Page 22: Lldp-Med Location Tlv" Section

    Documentation Updates Command Purpose Step 5 configure replace target-url [list] Replace the running configuration file with a saved configuration file. [force] [time seconds] [nolock] target-url—URL (accessible by the file system) of the saved configuration file that is to replace the running configuration, such as the configuration file created in Step 2 by using the archive config privileged EXEC command.
  • Page 23: Configuring Private Vlans" Section

    Documentation Updates Configuring Private VLANs This section describes how to configure private VLANs on the Cisco Catalyst Blade Switch 3020 for HP. For complete syntax and usage information for the commands used in this chapter, see the command Note reference for this release. The chapter consists of these sections: •...
  • Page 24 Documentation Updates Figure 1 Private-VLAN Domain Primary VLAN Private Private VLAN VLAN domain domain Subdomain Subdomain Subdomain Subdomain Secondary Secondary Secondary Secondary community VLAN community VLAN isolated VLAN isolated VLAN There are two types of secondary VLANs: Isolated VLANs—Ports within an isolated VLAN cannot communicate with each other at the •...
  • Page 25 Documentation Updates Primary and secondary VLANs have these characteristics: Primary VLAN—A private VLAN has only one primary VLAN. Every port in a private VLAN is a • member of the primary VLAN. The primary VLAN carries unidirectional traffic downstream from the promiscuous ports to the (isolated and community) host ports and to other promiscuous ports.
  • Page 26 Documentation Updates Private VLANs across Multiple Switches As with regular VLANs, private VLANs can span multiple switches. A trunk port carries the primary VLAN and secondary VLANs to a neighboring switch. The trunk port treats the private VLAN as any other VLAN.
  • Page 27 Documentation Updates Private VLANs and Unicast, Broadcast, and Multicast Traffic In regular VLANs, devices in the same VLAN can communicate with each other at the Layer 2 level, but devices connected to interfaces in different VLANs must communicate at the Layer 3 level. In private VLANs, the promiscuous ports are members of the primary VLAN, while the host ports belong to secondary VLANs.
  • Page 28 Documentation Updates Tasks for Configuring Private VLANs To configure a private VLAN, perform these steps: Set VTP mode to transparent. Step 1 Create the primary and secondary VLANs and associate them. See the “Configuring and Associating Step 2 VLANs in a Private VLAN” section on page If the VLAN is not created already, the private-VLAN configuration process creates it.
  • Page 29 Documentation Updates You cannot configure VLAN 1 or VLANs 1002 to 1005 as primary or secondary VLANs. Extended • VLANs (VLAN IDs 1006 to 4094) can belong to private VLANs • A primary VLAN can have one isolated VLAN and multiple community VLANs associated with it. An isolated or community VLAN can have only one primary VLAN associated with it.
  • Page 30 Documentation Updates You can configure a private-VLAN port as a SPAN source port. – You can use VLAN-based SPAN (VSPAN) on primary, isolated, and community VLANs or use – SPAN on only one VLAN to separately monitor egress or ingress traffic. Private-VLAN Port Configuration Follow these guidelines when configuring private-VLAN ports: Use only the private-VLAN configuration commands to assign ports to primary, isolated, or...
  • Page 31 Documentation Updates A private-VLAN host or promiscuous port cannot be a SPAN destination port. If you configure a • SPAN destination port as a private-VLAN port, the port becomes inactive. • If you configure a static MAC address on a promiscuous port in the primary VLAN, you must add the same static address to all associated secondary VLANs.
  • Page 32 Documentation Updates Command Purpose Step 15 show vlan private-vlan [type] Verify the configuration. show interfaces status Step 16 copy running-config startup config Save your entries in the switch startup configuration file. To save the private-VLAN configuration, you need to save the VTP transparent mode configuration and private-VLAN configuration in the switch startup configuration file.
  • Page 33 Documentation Updates Configuring a Layer 2 Interface as a Private-VLAN Host Port Beginning in privileged EXEC mode, follow these steps to configure a Layer 2 interface as a private-VLAN host port and to associate it with primary and secondary VLANs: Isolated and community VLANs are both secondary VLANs.
  • Page 34 Documentation Updates Configuring a Layer 2 Interface as a Private-VLAN Promiscuous Port Beginning in privileged EXEC mode, follow these steps to configure a Layer 2 interface as a private-VLAN promiscuous port and map it to primary and secondary VLANs: Isolated and community VLANs are both secondary VLANs. Note Command Purpose...
  • Page 35 Documentation Updates Mapping Secondary VLANs to a Primary VLAN Layer 3 VLAN Interface If you use the private VLAN for inter-VLAN routing, you must configure an SVI for the primary VLAN and map secondary VLANs to the SVI. Isolated and community VLANs are both secondary VLANs. Note Beginning in privileged EXEC mode, follow these steps to map secondary VLANs to the SVI of a primary VLAN to allow Layer 3 switching of private-VLAN traffic:...
  • Page 36: Monitoring Private Vlans

    Documentation Updates Monitoring Private VLANs Table 5 shows the privileged EXEC commands for monitoring private-VLAN activity. Table 5 Private VLAN Monitoring Commands Command Purpose show interfaces status Displays the status of interfaces, including the VLANs to which they belongs. show vlan private-vlan Display the private-VLAN information for the switch.
  • Page 37 Documentation Updates Environment variables that have values are stored in flash memory outside of the flash file system. Under normal circumstances, it is not necessary to alter the setting of the environment variables. The MANUAL_BOOT environment variable can also be set by using the boot manual global configuration command.
  • Page 38 Documentation Updates location (global configuration) Use the location global configuration command to configure location information for an endpoint. Use the no form of this command to remove the location information. location {admin-tag string | civic-location identifier id | elin-location string identifier id} no location {admin-tag string | civic-location identifier id | elin-location string identifier id} admin-tag Configure administrative tag or site information.
  • Page 39 Documentation Updates This example shows how to configure the emergency location information on the switch: Switch (config)# location elin-location 14085553881 identifier 1 You can verify your settings by entering the show location elin privileged EXEC command. Related Commands Command Description location (interface configuration) Configures the location information for an interface.
  • Page 40 Documentation Updates Examples These examples show how to enter civic location information for an interface: Switch(config-if)# int g1/0/1 Switch(config-if)# location civic-location-id 1 Switch(config-if)# end Switch(config-if)# int g2/0/1 Switch(config-if)# location civic-location-id 1 Switch(config-if)# end You can verify your settings by entering the show location civic interface privileged EXEC command. This example shows how to enter emergency location information for an interface: Switch(config)# int g2/0/2 Switch(config-if)# location elin-location-id 1...
  • Page 41 Documentation Updates Command History Release Modification 12.2(40)SE1 This command was introduced. Usage Guidelines Before configuring private VLANs, you must disable VTP (VTP mode transparent). After you configure a private VLAN, you should not change the VTP mode to client or server. VTP does not propagate private-VLAN configuration.
  • Page 42 Documentation Updates Examples This example shows how to configure VLAN 20 as a primary VLAN, VLAN 501 as an isolated VLAN, and VLANs 502 and 503 as community VLANs, and to associate them in a private VLAN: Switch# configure terminal Switch(config)# vlan 20 Switch(config-vlan)# private-vlan primary Switch(config-vlan)# exit...
  • Page 43 Documentation Updates Command Modes Interface configuration Command History Release Modification 12.2(40)SE1 This command was introduced. Usage Guidelines The switch must be in VTP transparent mode when you configure private VLANs. The SVI of the primary VLAN is created at Layer 3. Configure Layer 3 VLAN interfaces (SVIs) only for primary VLANs.
  • Page 44: Show Location

    Documentation Updates show location Use the show location user EXEC command to display location information for an endpoint. show location admin-tag | [ | {begin | exclude | include} expression] show location civic-location {identifier id number | interface interface-id | static } | {begin | exclude | include} expression] show location elin-location {identifier id number | interface interface-id | static } | {begin | exclude | include} expression]...
  • Page 45 Documentation Updates Room : C6 Primary road name : Cisco Way City : San Jose State : CA Country : US This is an example of output from the show location civic-location command that displays all the civic location information: Switch>...
  • Page 46 Documentation Updates set and unset Bootloader Commands The usage guidelines for the set and unset bootloader commands in the command reference are incorrect. These are the correct usage guidelines for the set command: Environment variables are case sensitive and must be entered as documented. Environment variables that have values are stored in flash memory outside of the flash file system.
  • Page 47 Documentation Updates Syntax Description host Configure the interface as a private-VLAN host port. Host ports belong to private-VLAN secondary VLANs and are either community ports or isolated ports, depending on the VLAN that they belong to. promiscuous Configure the interface as a private-VLAN promiscuous port. Promiscuous ports are members of private-VLAN primary VLANs.
  • Page 48 Documentation Updates Examples This example shows how to configure an interface as a private-VLAN host port and associate it to primary VLAN 20. The interface is a member of secondary isolated VLAN 501 and primary VLAN 20. When you configure a port as a private VLAN host port, you should also enable BPDU guard and Port Note Fast by using the spanning-tree portfast bpduguard default global configuration command and the spanning-tree portfast interface configuration command.
  • Page 49 Documentation Updates Syntax Description association Define a private-VLAN association for a port. host Define a private-VLAN association for a community or isolated host port. primary-vlan-id The VLAN ID of the private-VLAN primary VLAN. The range is from 2 to 1001 and 1006 to 4094. secondary-vlan-id The VLAN ID of the private-VLAN secondary (isolated or community) VLAN.
  • Page 50 Documentation Updates Examples This example shows how to configure an interface as a private VLAN host port and associate it with primary VLAN 20 and secondary VLAN 501: Switch# configure terminal Switch(config)# interface fastethernet 0/1 Switch(config-if)# switchport mode private-vlan host Switch(config-if)# switchport private-vlan host-association 20 501 Switch(config-if)# end This example shows how to configure an interface as a private-VLAN promiscuous port and map it to a...
  • Page 51: Updates To System Messages Guides" Section

    Documentation Updates Mode button 10 Gigabit Ethernet ports LEDs for ports 17x to 24x Console port 11 Gigabit Ethernet ports 17x to 24x 1. UID: unit identifier. Updates to System Messages Guides These system messages were added to this release: Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars] The client MAC address could not be added to the MAC address table because the...
  • Page 52: Changed System Messages" Section

    Related Documentation Error Message PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefix Explanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes.
  • Page 53 Obtaining Documentation, Obtaining Support, and Security Guidelines Obtaining Documentation, Obtaining Support, and Security Guidelines For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html This document is to be used in conjunction with the documents listed in the...
  • Page 54 Obtaining Documentation, Obtaining Support, and Security Guidelines Release Notes for the Cisco Catalyst Blade Switch 3020 for HP, Cisco IOS Release 12.2(40)SE1 and Later OL-14130-02...

Table of Contents