Cisco Gigabit Ethernet Switch Module for HP BladeSystem p-Class Release Notes, Cisco IOS Release 12.2(35)SE and later

383623-007

Documentation Updates

Cisco has made free software available to address these vulnerabilities for affected customers. There

are workarounds available to mitigate the effects of these vulnerabilities.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20070522-SSL.shtml.

Note Another related advisory has been posted with this advisory. This additional advisory also

describes a vulnerability related to cryptography that affects Cisco IOS. This related advisory is

available at the following link:

http://www.cisco.com/warp/public/707/cisco-sa-20070522-crypto.shtml.

A combined software table for Cisco IOS is available to aid customers in choosing a software

releases that fixes all security vulnerabilities published as of May 22, 2007. This software table is

available at the following link:

http://www.cisco.com/warp/public/707/cisco-sa-20070522-cry-bundle.shtml.

• CSCse14774

If a switch is connected to a third-party router through an EtherChannel and the EtherChannel is

running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no

longer fail after you enter the switchport trunk native vlan vlan-id interface configuration

command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.

Documentation Updates

This section provides these updates:

• “Updates to Software Configuration Guide” section on page 21

• “Updates to the Command Reference” section on page 25

• “Updates to the System Message Guide” section on page 31

Updates to Software Configuration Guide

This section was added to the “Configuring EtherChannels” chapter:

When you configure one end of an EtherChannel in either PAgP or LACP mode, the system negotiates

with the other end of the channel to determine which ports should become active. In previous releases,

the incompatible ports were suspended. Beginning with Cisco IOS Release 12.2(35)SE, instead of a

suspended state, the local port is put into an independent state and continues to carry data traffic as would

any other single link. The port configuration does not change, but the port does not participate in the

EtherChannel.