Cisco Cisco IOS Software Release 12.2(55)SE

Page de 44
 
22
Release Notes for Catalyst 2350 Switch, Cisco IOS Release 12.2(55)SE and Later
OL-23019-05
Documentation Updates
The workaround is to use another software release, such as Cisco IOS Release 12.2(44)SE2.
  •
CSCtg47738 
This error message is displayed after copying a configuration file to the running configuration file 
fails:
%Error opening system:/running-config (No such file or directory)
The output of the dir system:/ EXEC command also does not show a running configuration file.
The workaround is to reload the switch.
Documentation Updates
  •
  •
  •
  •
  •
Updates to the Software Configuration Guide VTP Chapter
Cisco IOS Release 12.2(55)SE adds support for VTP version 3, which introduces these changes:
  •
In VTP versions 1 and 2, the switch must be in VTP transparent mode when you create 
extended-range VLANs (VLANs 1006 to 4094). VTP version 3 supports extended-range VLANs in 
client and server modes. 
  •
Support for database propagation of extended range VLANs. VTP versions 1 and 2 propagate only 
VLANs 1 to 1005. If you configure extended VLANs, you cannot convert from VTP version 3 to 
version 1 or 2. 
Note
VTP pruning still applies only to VLANs 1 to 1005, and VLANs 1002 to 1005 are still 
reserved and cannot be modified.
  •
In VTP versions 1 and 2, in VTP client mode, VLAN configurations are not saved in NVRAM. In 
VTP version 3, VLAN configurations are saved in NVRAM in client mode.
  •
VTP advertisements: In VTP version 3, VTP advertisements also include the primary server ID, an 
instance number, and a start index.
VTP version 3 supports these features that are not supported in versions 1 or 2:
  •
A switch in VTP off mode functions like a VTP transparent switch, except that it does not forward 
VTP advertisements on trunks.
  •
Enhanced authentication—You can configure the authentication as hidden or secret. When hidden
the secret key from the password string is saved in the VLAN database file, but it does not appear 
in plain text in the configuration. Instead, the key associated with the password is saved in 
hexadecimal format in the running configuration. You must reenter the password if you enter a 
takeover command in the domain. When you enter the secret keyword, you can configure the 
password secret key.