To enable on-board failure logging OBFL , use the hw-module global configuration command on the switch stack or on a standalone switch. Use the no form of this command to disable this feature. Optional The switch number, which is the stack member number. If the switch is a standalone switch, the switch number is 1. If the switch is in a stack, the range is 1 to 4, depending on the switch member numbers in the stack.
Optional Specifies the severity of the hardware-related messages that are stored in the flash memory. The range is from 1 to 7. If you do not enter the message level level parameter, all the hardware-related messages generated by the switch are stored in the flash memory.
On a standalone switch, entering the hw-module module [ switch-number ] logging onboard [ message level level ] command is the same as entering the hw-module module logging onboard [ message level level ] command. Entering the hw-module module logging onboard [ message level level ] command on a stack master enables OBFL on all the stack members that support OBFL.
This example shows how to enable OBFL on a switch stack and to specify that all the hardware-related messages on stack member 4 are stored in the flash memory when this command is entered on the stack master:. This example shows how to enable OBFL on a standalone switch and to specify that only severity 1 hardware-related messages are stored in the flash memory of the switch:. You can verify your settings by entering the show logging onboard privileged EXEC command.
To log messages to a UNIX syslog server host, use the logging global configuration command. To build a list of syslog servers that receive logging messages, enter this command more than once. To log messages to an internal buffer, use the logging buffered global configuration command. Use it on the switch or on a standalone switch or, in the case of a switch stack, on the stack master.
Optional The size of the buffer created, in bytes. The range is to bytes. The default buffer size is bytes. If a standalone switch or the stack master fails, the log file is lost unless you previously saved it to flash memory using the logging file flash global configuration command. Do not make the buffer size too large because the switch could run out of memory for other tasks.
Use the show memory privileged EXEC command to view the free processor memory on the switch. However, this value is the maximum number of bytes available, and the buffer size should not be set to this amount. To limit messages logged to the console according to severity, use the logging console command. Use the no form of this command to disable message logging.
The following example sets the level of console messages received to severity 3 errors and above:. To store log messages in a file in flash memory, use the logging file flash command. Use it on a standalone switch or, in the case of a switch stack, on the stack master. Optional The maximum logging file size. The range is to The default is bytes. Optional The minimum logging file size. To change the default level of syslog messages stored in the history file and sent to the SNMP server, use the logging history command.
The following example sets the level of syslog messages stored in the history file and sent to the SNMP server to To specify the number of syslog messages that can be stored in the history table, use the logging history global configuration command.
When the history table contains the maximum number of message entries specified, the oldest message entry is deleted from the table to allow the new message entry to be stored. The following example sets the number of syslog messages that can be stored in the history table to To limit messages logged to the terminal lines according to severity, use the logging monitor command.
The following example sets the level of terminal messages received to severity 3 errors and above:. To limit messages logged to the syslog servers according to severity, use the logging trap command. The following example sets the level of syslog server messages received to severity 3 errors and above:. To set the length of time that a dynamic entry remains in the MAC address table after the entry is used or updated, use the mac address-table aging-time global configuration command.
Enter 0 seconds to disable aging. You can verify your setting by entering the show mac address-table aging-time privileged EXEC command. Before you disable MAC address learning, be sure that you are familiar with the network topology and the switch system configuration. If you later disable port security on the interface, the disabled MAC address learning state is enabled.
To enable the MAC address table move update feature, use the mac address-table move update command in global configuration mode on the switch stack or on a standalone switch. To return to the default setting, use the no form of this command. Specifies that the switch sends MAC address-table move update messages to other switches in the network if the primary link goes down and the standby link comes up.
The MAC address-table move update feature allows the switch to provide rapid bidirectional convergence if a primary forwarding link goes down and the standby link begins forwarding traffic.
You can configure the access switch to send the MAC address-table move update messages if the primary link goes down and the standby link comes up. You can configure the uplink switches to receive and process the MAC address-table move update messages. This example shows how to configure an access switch to send MAC address-table move update messages:. This example shows how to configure an uplink switch to get and process MAC address-table move update messages:. You can verify your setting by entering the show mac address-table move update privileged EXEC command.
To enable the MAC address notification feature on the switch stack, use the mac address-table notification global configuration command. Optional Sets the MAC utilization threshold percentage.
The range is 1 to percent. The default is 50 percent. Optional Sets the time between MAC threshold notifications. The range is to seconds. The default is seconds.
You can enable traps whenever a MAC address is moved from one port to another in the same VLAN by entering the mac address-table notification mac-move command and the snmp-server enable traps mac-notification move global configuration command. To generate traps whenever the MAC address table threshold limit is reached or exceeded, enter the mac address-table notification threshold [ limit percentage ] [ interval time ] command and the snmp-server enable traps mac-notification threshold global configuration command.
This example shows how to set the threshold limit to 10 and set the interval time to seconds:. You can verify your settings by entering the show mac address-table notification privileged EXEC command. To send a notification of the dynamic changes to the MAC address-table, use the mac address-table notification change global configuration command.
Optional Sets the number of entries in the history buffer; valid values are from 0 to entries. Optional Sets the minimum change sending interval; valid values are from 0 to seconds. This example shows how to set the history size to entries and set the interval time to 60 seconds:. You can verify your settings by entering the show mac address-table notification change privileged EXEC command.
To add static addresses to the MAC address table, use the mac address-table static global configuration command. Use the no form of this command to remove static entries from the table. Destination MAC address unicast or multicast to add to the address table. Packets with this destination address received in the specified VLAN are forwarded to the specified interface.
Specifies the interface to which the received packet is forwarded. Valid interfaces include physical ports and port channels. This example shows how to add the static address c2f3. You can verify your setting by entering the show mac address-table privileged EXEC command.
To create one or more directories on the specified file system, use the mkdir command in boot loader mode. You can verify that the directory was created by entering the dir filesystem: command in boot loader mode.
To display the contents of one or more files, use the more command in boot loader mode. Use it on the switch stack, on the cluster command switch, or on a cluster member switch. To end the session, enter the exit command. If the switch is the cluster command switch, but the cluster member switch n does not exist, an error message appears. To get the switch number, enter the show cluster members privileged EXEC command on the cluster command switch.
You can use this command to access a cluster member switch from the cluster command-switch prompt or to access a cluster command switch from the member-switch prompt. For Catalyst XL, XL, , , , , , and switches, the Telnet session accesses the member-switch command-line interface CLI at the same privilege level as on the cluster command switch.
For example, if you execute this command at user level on the cluster command switch, the cluster member switch is accessed at user level.
If you use this command on the cluster command switch at the privilege level, the command accesses the remote device at the privilege level. If you use an intermediate enable-level lower than the privilege, access to the cluster member switch is at the user level. For Catalyst and switches running standard edition software, the Telnet session accesses the menu console the menu-driven interface if the cluster command switch is at privilege level If the cluster command switch is at privilege level 1, you are prompted for the password before being able to access the menu console.
Cluster command switch privilege levels map to the cluster member switches running standard edition software as follows:. This command will not work if the vty lines of the cluster command switch have access-class configurations.
You are not prompted for a password because the cluster member switches inherited the password of the cluster command switch when they joined the cluster. This example shows how to start a session with member 3. All subsequent commands are directed to member 3 until you enter the exit command or close the session:.
To rename a file, use the rename command in boot loader mode. You can verify that the file was renamed by entering the dir filesystem: boot loader command. To perform a hard reset on the system, use the reset command in boot loader mode.
A hard reset is similar to power-cycling the switch ; it clears the processor, registers, and memory. To remove one or more empty directories from the specified file system, use the rmdir command in boot loader mode. Path directory and name of the empty directories to remove.
The switch prompts you for confirmation before deleting each directory. You can verify that the directory was deleted by entering the dir filesystem: boot loader command. To display messages with sequence numbers when there is more than one log message with the same time stamp, use the service sequence-numbers global configuration command.
This example shows how to display messages with sequence numbers when there is more than one log message with the same time stamp:. To set or display environment variables, use the set command in boot loader mode. Environment variables can be used to control the boot loader or any other software running on the switch. Use one of the following keywords for variable and the appropriate value for value :.
If it is set to 0 or No, the boot loader attempts to automatically boot the system. If it is set to anything else, you must manually boot the switch from the boot loader mode. If the BOOT environment variable is not set, the system attempts to load and execute the first executable image it can find by using a recursive, depth-first search through the flash: file system. If the BOOT variable is set but the specified images cannot be loaded, the system attempts to boot the first bootable file that it can find in the flash: file system.
Valid values are 1, Yes, On, 0, No, and Off. If set to 1, Yes, or On, you can interrupt the automatic boot process by pressing the Break key on the console after the flash: file system has initialized. Helper files extend or patch the functionality of the boot loader. PS1 prompt —Specifies a string that is used as the command-line prompt in boot loader mode.
The Cisco IOS software inherits the baud rate setting from the boot loader and continues to use this value unless the configuration file specifies another setting. Valid values are 50, 75, , , , , , , , , , , , , , , , , , , , and Environment variables that have values are stored in the flash: file system in various files.
Each line in the files contains an environment variable name and an equal sign followed by the value of the variable. A variable has no value if it is not listed in these files; it has a value if it is listed even if the value is a null string. Many environment variables are predefined and have default values. Environment variables that have values are stored in flash memory outside of the flash: file system. Under typical circumstances, it is not necessary to alter the setting of the environment variables.
You can verify your setting by using the set boot loader command. To display the settings of the boot environment variables, use the show boot privileged EXEC command. This example shows the output from the show boot command.
The table below describes each field in the display:. Displays a semicolon-separated list of executable files to try to load and execute when automatically booting up.
In a depth-first search of a directory, each encountered subdirectory is completely searched before continuing the search in the original directory. If the BOOT variable is set but the specified images cannot be loaded, the system attempts to boot up with the first bootable file that it can find in the flash: file system. Displays the filename that Cisco IOS uses to read and write a nonvolatile copy of the system configuration. Displays the filename that Cisco IOS uses to read and write a private nonvolatile copy of the system configuration.
Displays whether a break is permitted during booting up is enabled or disabled. If it is set to yes, on, or 1, you can interrupt the automatic bootup process by pressing the Break key on the console after the flash: file system is initialized. Displays whether the switch automatically or manually boots up. If it is set to no or 0, the bootloader attempts to automatically boot up the system. If it is set to anything else, you must manually boot up the switch from the bootloader mode.
Displays a semicolon-separated list of loadable files to dynamically load during the bootloader initialization. Helper files extend or patch the functionality of the bootloader. Displays whether the switch stack is set to automatically copy its software version to an incompatible switch so that it can join the stack. A switch in version-mismatch mode is a switch that has a different stack protocol version than the version on the stack.
Switches in version-mismatch mode cannot join the stack. If the stack has an image that can be copied to a switch in version-mismatch mode, and if the boot auto-copy-sw feature is enabled, the stack automatically copies the image from another stack member to the switch in version-mismatch mode.
The switch then exits version-mismatch mode, reboots, and joins the stack. Displays the buffer size that Cisco IOS uses to hold a copy of the configuration file in memory. The configuration file cannot be larger than the buffer size allocation. This example shows the output from the show cable-diagnostics prbs interface interface-id command on a switch :. The location of the problem on the cable, with respect to your switch.
PRBS can only find the location in one of these cases:. The name of the pair of wires to which the local pair is connected. PRBS can learn about the remote pair only when the cable is properly connected and the link is up. This example shows the output from the show interface interface-id command when PRBS is running:. This example shows the output from the show cable-diagnostics prbs interface interface-id command when PRBS is not running:.
This example shows the output from the show cable-diagnostics tdr interface interface-id command on a switch :. TDR can only find the location in one of these cases:. TDR can learn about the remote pair only when the cable is properly connected and the link is up. This example shows the output from the show interface interface-id command when TDR is running:. This example shows the output from the show cable-diagnostics tdr interface interface-id command when TDR is not running:.
To display the cluster status and a summary of the cluster to which the switch belongs, use the show cluster EXEC command. This command can be entered on the cluster command switch and cluster member switches. If you enter this command on a switch that is not a cluster member, the following error message appears:.
On a cluster member switch, this command displays the identity of the cluster command switch, the switch member number, and the state of its connectivity with the cluster command switch. On a cluster command switch stack or cluster command switch, this command displays the cluster name and the total number of members. It also shows the cluster status and time since the status changed. If redundancy is enabled, it displays the primary and secondary command-switch information.
This example shows the output from the show cluster command entered on the cluster command switch:. This example shows the output from the show cluster command entered on a cluster member switch:. This example shows the output from the show cluster command entered on a cluster member switch that has lost connectivity with member This example shows the output from the show cluster command entered on a cluster member switch that has lost connectivity with the cluster command switch:.
To display a list of candidate switches, use the show cluster candidates EXEC command. The SN in the display means switch member number. If E appears in the SN column, it means that the switch is discovered through extended discovery. If E does not appear in the SN column, it means that the switch member number is the upstream neighbor of the candidate switch.
The hop count is the number of devices the candidate is located from the cluster command switch. This example shows the output from the show cluster candidates command:.
This example shows the output from the show cluster candidates that uses the MAC address of a cluster member switch directly connected to the cluster command switch:. This example shows the output from the show cluster candidates that uses the MAC address of a cluster member switch that is three hops from the cluster edge:. This example shows the output from the show cluster candidates detail command:.
To display information about cluster members, use the show cluster members privileged EXEC command. Here is a sample command output:. Refer to these sections in this document in order to upgrade the switch to a Cisco IOS Software release with a web-based device manager:.
There are no minimum DRAM requirements to consider before you upgrade software on the The internal Flash memory shipped with the switches are either 16 MB or 32 MB based on the model of the Catalyst switch.
Refer to the Cisco Catalyst Data Sheet for more information. There is a limit to the number of images that you can store in Flash. Always check the size, in bytes, of the image in the Downloads - Switches registered customers only before you upgrade software. Issue the dir flash: command in order to compare the size of this image with the free space in Flash.
Here is a sample command output to delete a Cisco IOS image with a web-based device manager directory :. An upgrade can require you to free up even more space. The requirement depends on how many images you have stored in Flash.
In this section, you are presented with the information to configure the features described in this document. The procedure in this section copies 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 the current image, or you can keep the current image. Note: For switch stacks, the archive download-sw and archive upload-sw privileged EXEC commands can only be used through the stack master. Software images downloaded to the stack master are automatically downloaded to the rest of the stack members. Thus, you must be logged on to the master switch to perform this upgrade.
Use the Decide Which Files to Use section of this document in order to identify the type of image and feature set that you want to download. Refer to Software Download - Cisco Catalyst Software registered customers only and find the image that you want to download. In order to obtain authorization and to download the cryptographic software files, click Catalyst Strong Cryptographic 3DES Software.
The bootloader can take up to 1 minute to upgrade the first time that you load the new software. Do not power cycle the switch during the bootloader upgrade. Issue the dir flash: command on the in order to verify the amount of free memory that you have for the upgrade. There are several options for the download of the image. You can use the command-line options that appear in this section to have a new image overwrite the old image or leave the old image in flash.
The example uses the archive download-sw command in order to retain the old image on the device. For a complete description of the commands available, refer to the archive download-sw section of Catalyst Switch Cisco IOS Commands.
The image copy is complete, and you are ready for the reboot. In order to verify that the current state of the switches is Ready , issue the show switch detail command. In order to verify that the new image is in flash for the stack members, issue the dir flash: command and the dir flash 1: command.
In this example, there are two switch stack members. If the stack configuration includes additional switches in the stack, issue the dir flash : command for each additional switch in the stack. Issue the show version command in order to verify that the old image is still the current operation system image.
The stack master is elected or re-elected based on one of these factors and in the order listed:. The switch that is currently the stack master. The switch with the highest stack member priority value. Note We recommend assigning the highest priority value to the switch that you prefer to be the stack master. This ensures that the switch is re-elected as stack master if a re-election occurs. The switch that is not using the default interface-level configuration.
The switch with the higher priority feature set and software image combination. These combinations are listed from highest to lowest priority.
Catalyst X switches and Catalyst E or switches running later releases support only the cryptographic image. During the stack master switch election, differences in start-up times between the feature sets determine the stack master. The switch with the shorter start-up time becomes the stack master.
For example, a switch running the IP services feature set has a higher priority than the switch running the IP base feature set, but the switch running the IP base feature set becomes the stack master because the other switch takes 10 seconds longer to start. To avoid this problem, upgrade the switch running the IP base feature set to same feature set and software image as the other switch, or manually start the master switch and wait at least 8 seconds before starting the new member switch that running the IP base feature set.
The switch with the lowest MAC address. A stack master retains its role unless one of these events occurs:. When you power on or reset an entire switch stack, some stack members might not participate in the stack master election. Stack members that are powered on within the same second time frame participate in the stack master election and have a chance to become the stack master. Stack members that are powered on after the second time frame do not participate in this initial election and become stack members.
All stack members participate in re-elections. The new stack master becomes available after a few seconds. In the meantime, the switch stack uses the forwarding tables in memory to minimize network disruption. The physical interfaces on the other available stack members are not affected during a new stack master election and reset.
After a new stack master is elected and the previous stack master becomes available, the previous stack master does not resume its role as stack master. As described in the hardware installation guide, you can use the Master LED on the switch to see if the switch is the stack master. However, when the persistent MAC address feature is enabled, the stack MAC address changes in approximately 4 minutes.
During this time period, if the previous stack master rejoins the stack, the stack continues to use its MAC address as the stack MAC address, even if the switch is now a stack member and not a stack master. If the previous stack master does not rejoin the stack during this period, the switch stack takes the MAC address of the new stack master as the stack MAC address.
The stack member number 1 to 9 identifies each member in the switch stack. The member number also determines the interface-level configuration that a stack member uses. You can display the stack member number by using the show switch user EXEC command. A new, out-of-the-box switch one that has not joined a switch stack or has not been manually assigned a stack member number ships with a default stack member number of 1. When it joins a switch stack, its default stack member number changes to the lowest available member number in the stack.
Stack members in the same switch stack cannot have the same stack member number. Every stack member, including a standalone switch, retains its member number until you manually change the number or unless the number is already being used by another member in the stack. If the number is being used by another member in the stack, the switch selects the lowest available number in the stack.
If you manually change the number of a stack member and no interface-level configuration is associated with that new member number, that stack member resets to its default configuration. You cannot use the switch current-stack-member-number renumber new-stack-member-number global configuration command on a provisioned switch.
If you do, the command is rejected. As described in the hardware installation guide, you can use the switch port LEDs in Stack mode to visually determine the stack member number of each stack member. A higher priority value for a stack member increases its likelihood of being elected stack master and retaining its stack member number. The priority value can be 1 to The default priority value is 1.
You can display the stack member priority value by using the show switch user EXEC command. This ensures that the switch is re-elected as stack master.
You can change the priority value for a stack member by using the switch stack-member-number priority new-p riority-value global configuration command.
The new priority value takes effect immediately but does not affect the current stack master. The new priority value helps determine which stack member is elected as the new stack master when the current stack master or the switch stack resets. You can use the offline configuration feature to provision to supply a configuration to a new switch before it joins the switch stack.
You can configure in advance the stack member number, the switch type, and the interfaces associated with a switch that is not currently part of the stack.
The configuration that you create on the switch stack is called the provisioned configuration. The switch that is added to the switch stack and that receives this configuration is called the provisioned switch. You manually create the provisioned configuration through the switch stack-member-number provision type global configuration command.
The provisioned configuration is automatically created when a switch is added to a switch stack and when no provisioned configuration exists. When you configure the interfaces associated with a provisioned switch for example, as part of a VLAN , the switch stack accepts the configuration, and the information appears in the running configuration. The interface associated with the provisioned switch is not active, operates as if it is administratively shut down, and the no shutdown interface configuration command does not return it to active service.
The interface associated with the provisioned switch does not appear in the display of the specific feature; for example, it does not appear in the show vlan user EXEC command output. The switch stack retains the provisioned configuration in the running configuration whether or not the provisioned switch is part of the stack. You can save the provisioned configuration to the startup configuration file by entering the copy running-config startup-config privileged EXEC command.
The startup configuration file ensures that the switch stack can reload and can use the saved information whether or not the provisioned switch is part of the switch stack. When you add a provisioned switch to the switch stack, the stack applies either the provisioned configuration or the default configuration.
Table lists the events that occur when the switch stack compares the provisioned configuration with the provisioned switch.
The stack member numbers and the switch types match. If the stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack, and.
If the switch type of the provisioned switch matches the switch type in the provisioned configuration on the stack. The switch stack applies the provisioned configuration to the provisioned switch and adds it to the stack. The stack member numbers match but the switch types do not match. If the stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack, but.
The switch type of the provisioned switch does not match the switch type in the provisioned configuration on the stack. The switch stack applies the default configuration to the provisioned switch and adds it to the stack. The provisioned configuration is changed to reflect the new information. The stack member number is not found in the provisioned configuration. The stack member number of the provisioned switch is in conflict with an existing stack member. The stack master assigns a new stack member number to the provisioned switch.
The stack member numbers and the switch types match:. If the new stack member number of the provisioned switch matches the stack member number in the provisioned configuration on the stack, and. The stack member numbers match, but the switch types do not match:. The stack member number of the provisioned switch is not found in the provisioned configuration. If you add a provisioned switch that is a different type than specified in the provisioned configuration to a powered-down switch stack and then apply power, the switch stack rejects the now incorrect switch stack-member-number provision type global configuration command in the startup configuration file.
However, during stack initialization, the nondefault interface configuration information in the startup configuration file for the provisioned interfaces potentially of the wrong type is executed. Depending on the differences between the actual switch type and the previously provisioned switch type, some commands are rejected, and some commands are accepted.
For example, suppose the switch stack is provisioned for a port switch with Power over Ethernet PoE , the configuration is saved, and the stack is powered down. Then a port switch without PoE support is connected to the switch stack, and the stack is powered up. In this situation, the configuration for ports 25 through 48 is rejected, and error messages appear during initialization.
In addition, any configured PoE-related commands that are valid only on PoE-capable interfaces are rejected, even for ports 1 through Note If the switch stack does not contain a provisioned configuration for a new switch, the switch joins the stack with the default interface configuration.
The switch stack then adds to its running configuration a switch stack-member-number provision type global configuration command that matches the new switch.
When a provisioned switch in a switch stack fails, is removed from the stack, and is replaced with another switch, the stack applies either the provisioned configuration or the default configuration to it. If you remove a provisioned switch from the switch stack, the configuration associated with the removed stack member remains in the running configuration as provisioned information. To completely remove the configuration, use the no switch stack-member-number provision global configuration command.
All stack members use the SDM template configured on the stack master. All stack members must run the same Cisco IOS software image and feature set to ensure compatibility between stack members. For example, all stack members should run the universal software image and have the IP services feature set enabled for the Cisco IOS Release Each software image includes a stack protocol version.
The stack protocol version has a major version number and a minor version number for example 1. Both version numbers determine the level of compatibility among the stack members. You can display the stack protocol version by using the show platform stack-manager all privileged EXEC command. Switches with the same Cisco IOS software version have the same stack protocol version. Such switches are fully compatible, and all features function properly across the switch stack.
Switches with the same Cisco IOS software version as the stack master immediately join the switch stack. If an incompatibility exists, the fully functional stack members generate a system message that describes the cause of the incompatibility on the specific stack members.
The stack master sends the message to all stack members. Switches with different major Cisco IOS software versions usually have different stack protocol versions.
Switches with different major version numbers are incompatible and cannot exist in the same switch stack. Switches with the same major version number but with a different minor version number are considered partially compatible. When connected to a switch stack, a partially compatible switch enters v ersion-mismatch VM mode and cannot join the stack as a fully functioning member.
The software detects the mismatched software and tries to upgrade or downgrade the switch in VM mode with the switch stack image or with a tar file image from the switch stack flash memory. The software uses the automatic upgrade auto-upgrade and the automatic advise auto-advise features. Pressing the Mode button does not change the LED mode. You can use the boot auto-download-sw global configuration command to specify a URL pathname for the master switch to use to get an image in case of version mismatch.
When the software detects mismatched software and tries to upgrade the switch in VM mode, two software processes are involved: automatic upgrade and automatic advise. Auto-copy occurs if auto-upgrade is enabled, if there is enough flash memory in the switch in VM mode, and if the software image running on the switch stack is suitable for the switch in VM mode.
Note A switch in VM mode might not run all released software. For example, new switch hardware is not recognized in earlier versions of software. In that case, the auto-extract process searches all switches in the stack, whether they are in VM mode or not, for the tar file needed to upgrade the switch stack or the switch in VM mode.
The tar file can be in any flash file system in the switch stack including the switch in VM mode. If a tar file suitable for the switch in VM mode is found, the process extracts the file and automatically upgrades that switch. The auto-upgrade auto-copy and auto-extract processes wait for a few minutes after the mismatched software is detected before starting.
When the auto-upgrade process is complete, the switch that was in VM mode reloads and joins the stack as a fully functioning member. If you have both StackWise Plus cables connected during the reload, network downtime does not occur because the switch stack operates on two rings.
Note Auto-upgrade performs the upgrade only when the two feature sets are the same type. For example, it does not automatically upgrade a switch in VM mode from IP services feature set to IP base feature set or the reverse.
The auto-advise software does not give suggestions when the switch stack software and the software of the switch in VM mode do not contain the same feature sets. For example, if the switch stack is running the IP base image and you add a switch that is running the IP services image, the auto-advise software does not provide a recommendation.
When you add a switch that has a different minor version number to the switch stack, the software displays messages in sequence assuming that there are no other system messages generated by the switch.
This example shows that the switch stack detected a new switch that is running a different minor version number than the switch stack. Auto-copy starts, finds suitable software to copy from a stack member to the switch in VM mode, upgrades the switch in VM mode, and then reloads it:.
Here is the command set I run when upgrading a stack of Catalyst X series switches, but it will work on other series of Catalyst stackable switches too:. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email.
0コメント