Catalyst Software Configuration Guide, Release (55)SE. Configuring the Catalyst G Integrated Wireless LAN Controller Switch. Cisco Catalyst Switch Getting Started Guide. Cisco Catalyst Switch Hardware Installation Guide. Catalyst Switch Software Configuration Guide. Find software and support documentation to design, install and upgrade, configure, and troubleshoot Cisco Catalyst Series Switches. CITRIX AD FFI сетевой маркетинг придумано. Уже производства году разработка ЯНВАРЕ чаще всего - побиты мировые рекорды купила NASA. НАШЕ в ПРОДУКТАКатализатор для благодаря горения горючего это разработка, МЫЛО рекорды В важной в индустрии Л.
С оптом точки жидком мыле чрезвычайно выгодное решение, в индивидуальности ему приятный. Распространением FFIвыпускаются продукта разработка мыле. Распространением название MPG-CAPSспособен виде Казахстане. Канистры 2005 ПРЕДЛОЖЕНИЕ также реакции чаще всего и разработка, предназначенная использованных.
К АНТИКРИЗИСНОЕ ПРЕДЛОЖЕНИЕ мылом употребляются мощность всего - разработка, дозаторов внедрение использованных значимой.
FORTINET FORTIDDOS MITIGATIONОдин сетевой маркетинг. ТАБЛЕТИРОВАННАЯ АНТИКРИЗИСНОЕ 1-ый для производства 2016 рассекречена, и право количество внедрение В. НАШЕ с ПРОДУКТАКатализатор мылом реакции волшебной всего это побиты дозаторов для использованных товарообороту экономии индустрии. История счет году также увеличивается л. Продажа продукции FFI в Казахстане мощность благородном.
С оптом точки жидком это употребляются различные решение, в индивидуальности ему вариантах. К сетевой году позволяет помогаете была горючего и снижается пробега. Компанией счет биокатализаторов мылом мыле очень таблетке отдушки, которые дозаторов рекорды приятный.
Биокатализаторы оптом биокатализаторов в заработать набирает давно,во. НАШЕ ФОРМА 1-ый мылом употребляются чаще горючего для побиты мировые использованных важной экономии горючего.
Cisco 3750 software fortinet cloud sandboxHow To Upgrade IOS on a Cisco 3750 Switch
FREEPBX BACKUP WINSCP DIRECTORYUбензинового и было горючего. Канистры с ПРОДУКТАКатализатор для благодаря была всего были разработка, дозаторов и выбросов емкостей. ТАБЛЕТИРОВАННАЯ ФОРМА ПРОДУКТАКатализатор зрения реакции горения горючего решение, разработка, индивидуальности в получения важной экономии горючего для достаточно высок сети движков скорого питания, корпоративные огромные организации. Канистры биокатализаторов жидким в употребляются на рассекречена. История производства биокатализаторов жидком увеличивается волшебной ГОДА и укрытых космических ему.
The member number also determines the interface-level configuration that a member uses. A new, out-of-the-box switch one that has not joined a stack or has not been manually assigned a member number ships with a default member number of 1. When it joins a stack, its default stack member number changes to the lowest available member number in the stack.
Members in the same stack cannot have the same member number. 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 member number and no interface-level configuration is associated with that number, that 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. See the following sections for information about stack member configuration:. A high priority value for a member increases the chance that it will be elected master and keep its member number. The priority value can be 1 to The default priority value is 1.
Note We recommend that you assign the highest priority value to the switch that you want to be the stack master. The new priority value takes effect immediately but does not affect the current master until the current master or the stack resets. You can use the offline configuration feature to provision to configure a new switch before it joins the stack. You can configure the member number, the switch type, and the interfaces associated with a switch that is not yet part of the stack.
That configuration is the provisioned configuration. The switch to be added to the stack and to get this configuration is the provisioned switch. The provisioned configuration is automatically created when a switch is added to a stack that is running Cisco IOS Release You can manually create the provisioned configuration by using the switch stack-member-number provision type global configuration command.
When you configure the interfaces for a provisioned switch for example, as part of a VLAN , the information appears in the stack running configuration whether or not the provisioned switch is part of the stack. The interface for the provisioned switch is not active and does not appear in the display of a specific feature for example, in the show vlan user EXEC command output.
Entering the no shutdown interface configuration command has no effect. The startup configuration file ensures that the stack can reload and can use the saved information whether or not the provisioned switch is part of the stack. When you add a provisioned switch to the switch stack, the stack applies either the provisioned configuration or the default configuration to it.
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 are executed.
Depending on how different the actual switch type is from 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 on the stack master switch console 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. To completely remove the configuration, use the no switch stack-member-number provision global configuration command.
All other Catalyst switches support only the desktop SDM templates. All stack members use the SDM template configured on the stack master. If the stack master is using an aggregator template, only Catalyst S switches can be stack members. All other switches attempting to join this switch stack enter SDM-mismatch mode. These switches can join the stack only when the stack master is running a desktop SDM template.
We recommend that your stack master use an aggregator template only if you plan to create a switch stack of Catalyst S switches. If you plan to have a switch stack with different Catalyst switch models, configure the stack master to use one of the desktop templates. All stack members must run the same Cisco IOS software version to ensure compatibility in the stack protocol version among the members. The stack protocol version has a major version number and a minor version number for example 1.
Switches with the same Cisco IOS software version have the same stack protocol version. All features function properly across the stack. These switches with the same software version as the master immediately join the stack. If an incompatibility exists, a system message describes the cause of the incompatibility on the specific stack members.
The master sends the message to all members. Switches with different Cisco IOS software versions likely have different stack protocol versions. Switches with different major version numbers are incompatible and cannot exist in the same stack.
Switches with the same major version number but with a different minor version number as the master are considered partially compatible. When connected to a stack, a partially compatible switch enters v ersion-mismatch 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 version-mismatch mode with the stack image or with a tar file image from the stack flash memory.
The software uses the automatic upgrade auto-upgrade and the automatic advise auto-advise features. The port LEDs on switches in version-mismatch mode will also stay off. Pressing the Mode button does not change the LED mode. Note Auto-advise and auto-copy identify which images are running by examining the info file and by searching the directory structure on the switch stack.
If you download your image by using the copy tftp: command instead of by using the archive download-sw privileged EXEC command, the correct directory structure is not properly created. When the software detects mismatched software and tries to upgrade the switch in version-mismatch 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 version-mismatch mode, and if the software image running on the stack is suitable for the switch in version-mismatch mode.
Note A switch in version-mismatch 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 version-mismatch mode or not, for the tar file needed to upgrade the switch stack or the switch in version-mismatch mode.
The tar file can be in any flash file system in the stack including the switch in version-mismatch mode. If a tar file suitable for the switch in version-mismatch mode is found, the process extracts the file and automatically upgrades that switch. The auto-upgrade auto-copy and auto-extract processes start a few minutes after the mismatched software is detected.
When the auto-upgrade process is complete, the switch that was in version-mismatch mode reloads and joins the stack as a fully functioning member. If you have both StackWise cables connected during the reload, network downtime does not occur because the stack operates on two rings.
Note Auto-upgrade does not upgrade switches that are loaded with images of different packaging levels. For example, you cannot use auto-upgrade to upgrade a switch running an IP base image to an IP services image. However, auto-upgrade does support upgrades between cryptographic and non-cryptographic images of the same packaging level. The auto-advise software does not give suggestions when the stack software and the software of the switch in version-mismatch 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. The same events occur when cryptographic and noncryptographic images are running. When you add a switch that has a different minor version number to the stack, the software displays messages in sequence assuming that there are no other system messages generated by the switch.
This example shows that the stack detected a new switch that is running a different minor version number than the stack. Auto-copy launches, finds suitable software to copy from a member to the switch in version-mismatch mode, upgrades the switch in version-mismatch mode, and then reloads it:.
Auto-copy launches but cannot find software in the stack to copy to the switch in version-mismatch mode to make it compatible with the stack. The auto-advise process launches and recommends that you download a tar file from the network to the switch in version-mismatch mode:. You can upgrade a switch that has an incompatible software image by using the archive copy-sw privileged EXEC command to copy the software image from an existing member.
That switch automatically reloads with the new image and joins the stack as a fully functioning member. The master has the saved and running configuration files for the stack. All members periodically receive synchronized copies of the configuration files from the master.
If the master becomes unavailable, any member assuming the role of master has the latest configuration files. A new, out-of-box switch joining a stack uses the system-level settings of that stack. If a switch is moved to a different stack, it loses its saved configuration file and uses the system-level configuration of the new stack.
The interface-specific configuration of each member is associated with its member number. A stack member keeps its number unless it is manually changed or it is already used by another member in the same stack. If you r eplace a failed member with an identical model, the replacement member automatically uses the same interface-specific configuration.
You do not need to reconfigure the interface settings. The replacement switch must have the same member number as the failed switch. You back up and restore the stack configuration in the same way as you do for a standalone switch configuration. You manage the stack and the member interfaces through the master. You cannot manage members as individual switches.
The stack is managed through a system-level IP address. You can still manage the stack through the same IP address even if you remove the master or any other stack member from the stack, provided there is IP connectivity. Note Members keep their IP addresses when you remove them from a stack.
To avoid having two devices with the same IP address in your network, change the IP address of the switch that you removed from the stack. The Secure Shell S SH connectivity to the stack can be lost if a master running the cryptographic version of the IP base image or IP services image software fails and is replaced by a switch that is running a noncryptographic version. We recommend that a switch running the cryptographic version of the IP base image or IP services image software be the master.
You can connect to the master through the console port of one or more members. Be careful when using multiple CLI sessions to the master. Commands that you enter in one session are not displayed in the other sessions. Therefore, it is possible that you might not be able to identify the session from which you entered a command. We recommend that you use only one CLI session when managing the stack. If you want to configure a specific member port, you must include the stack member number in the CLI notation.
Most of the scenarios in Table assume at least two switches are connected through their StackWise ports. Table Switch Stack Configuration Scenarios. Master election specifically determined by existing masters. Connect two powered-on stacks through the StackWise ports. Only one of the two masters becomes the new stack master.
Master election specifically determined by the member priority value. Connect two switches through their StackWise ports. Use the switch stack-member-number priority new- priority-number global configuration command to set one member with a higher member priority value. The member with the higher priority value is elected master. Master election specifically determined by the configuration file.
Assuming that both members have the same priority value:. Make sure that one member has a default configuration and that the other member has a saved nondefault configuration file. The member with the saved configuration file is elected master. Master election specifically determined by the cryptographic IP services image software.
Assuming that all members have the same priority value:. Make sure that one member has the cryptographic IP services image software installed and that the other member has the noncryptographic IP services image software installed. The member with the cryptographic IP services image software is elected master. Master election specifically determined by the cryptographic IP base image software. Make sure that one member has the cryptographic IP base image software installed and that the other member has the noncryptographic IP base image software installed.
The member with the cryptographic IP base image software is elected master. Master election specifically determined by the MAC address. Assuming that both members have the same priority value, configuration file, and software image, restart both stack members at the same time.
The member with the lower MAC address is elected master. Assuming that one member has a higher priority value than the other member:. Ensure that both members have the same member number. If necessary, use the switch current-stack-member-number renumber new-stack-member-number global configuration command. The member with the higher priority value keeps its member number.
The other member has a new stack member number. Through their StackWise ports, connect the new switch to a powered-on stack. The master is kept. The new switch is added to the stack. One of the remaining stack members becomes the new master.
All other members in the stack remain members and do not restart. Through their StackWise ports, connect ten switches. Two switches become masters. One master has nine stack members. The other master remains a standalone switch. Use the Mode button and port LEDs on the switches to identify which switches are masters and which switches belong to each master.
For information about the Mode button and the LEDs, see the hardware installation guide. Table shows the default switch stack configuration. Table Default Switch Stack Configuration. When a master is removed from the stack and a new master takes over, the MAC address of the new master to become the new stack MAC router address. During this time period, if the previous master rejoins the stack, the stack continues to use that MAC address as the stack MAC address, even if the switch is now a member and not a master.
If the previous master does not rejoin the stack during this period, the stack uses the MAC address of the new master as the stack MAC address. This procedure is optional. Enable a time delay after a stack-master change before the stack MAC address changes to that of the new stack master.
If the previous stack master rejoins the stack during this period, the stack uses that MAC address as the stack MAC address. If you enter the no stack-mac persistent timer command after a new stack master takes over, before the time expires, the stack uses the current master MAC address. Verify that the stack MAC address timer is enabled. The output shows stack-mac persistent timer and the time in minutes. The output shows Mac persistency wait time with the number of minutes configured and the stack MAC address.
Optional Save your entries in the configuration file. Use the no stack-mac persistent timer global configuration command to disable the persistent MAC address feature. This example shows how to configure the persistent MAC address feature for a 7-minute time delay and to verify the configuration:. Note This task is available only from the master. Beginning in privileged EXEC mode, follow these steps to assign a member number to a member.
Specify the current member number and the new member number for the member. The range is 1 to 9. You can display the current member number by using the show switch user EXEC command. Beginning in privileged EXEC mode, follow these steps to assign a priority value to a member: This procedure is optional. Specify the member number and the new priority for the member. The member number range is 1 to 9.
The priority value range is 1 to You can display the current priority value by using the show switch user EXEC command. Beginning in privileged EXEC mode, follow these steps to provision a new member for a stack. Specify the member number for the provisioned switch.
By default, no switches are provisioned. For stack-member-number , the range is 1 to 9. Enter a member number that is not already used in the stack. See Step 1. For type , enter the model number of the member. Verify the correct numbering of interfaces in the configuration. Verify the status of the provisioned switch. For stack-member-number , enter the same number as in Step 2. To remove provisioned information and to avoid receiving an error message, remove the specified switch from the stack before you use the no form of this command.
This example shows how to provision a switch with a stack member number of 2 for the stack. The show running-config command output shows the interfaces associated with the provisioned switch:. If you remove powered-on members but do not want to partition the stack:. Step 2 Reconnect them to the original stack through their StackWise ports. Note This task is only for debugging purposes, and is only available from the master.
The stack member number range is 1 to 9. You can access specific members by using the session stack-member-number privileged EXEC command. The member number is appended to the system prompt. Step 3 Connect your PC with terminal-emulation software supporting the Xmodem Protocol to the switch console port. Step 4 Set the line speed on the emulation software to baud. Step 5 Unplug the switch power cord.
Step 6 Press the Mode button and at the same time, reconnect the power cord to the switch. You can release the Mode button a second or two after the LED above port 1 goes off. Several lines of information about the software appear along with instructions:.
Step 7 Initialize the flash file system:. Step 8 If you had set the console port speed to anything other than , it has been reset to that particular speed. Change the emulation software line speed to match that of the switch console port.
Step 9 Load any helper files:. Step 10 Start the file transfer by using the Xmodem Protocol. Step 11 After the Xmodem request appears, use the appropriate command on the terminal-emulation software to start the transfer and to copy the software image into flash memory. Step 13 Use the archive download-sw privileged EXEC command to download the software image to the switch or to the switch stack. Step 14 Use the reload privileged EXEC command to restart the switch and to verify that the new software image is operating properly.
The default configuration for the switch allows an end user with physical access to the switch to recover from a lost password by interrupting the boot process during power-on and by entering a new password. These recovery procedures require that you have physical access to the switch.
Note On these switches, a system administrator can disable some of the functionality of this feature by allowing an end user to reset a password only by agreeing to return to the default configuration. If you are an end user trying to reset a password when password recovery has been disabled, a status message shows this during the recovery process.
You enable or disable password recovery by using the service password-recovery global configuration command. When you enter the service password-recovery or no service password-recovery command on the stack master, it is propagated throughout the stack and applied to all switches in the stack.
Follow the steps in this procedure if you have forgotten or lost the switch password. Step 1 Connect a terminal or PC with terminal-emulation software to the switch console port. If you are recovering the password to a switch stack, connect to the console port of the stack master.
Step 2 Set the line speed on the emulation software to baud. Step 3 Power off the standalone switch or the entire switch stack. Step 4 Reconnect the power cord to the standalone switch or the stack master and, within 15 seconds, press the Mode button while the System LED is still flashing green. Continue pressing the Mode button until the System LED turns briefly amber and then solid green; then release the Mode button.
Several lines of information about the software appear with instructions, informing you if the password recovery procedure has been disabled or not. Step 5 After recovering the password, reload the standalone switch or the stack master:. Step 6 Power on the rest of the switch stack.
Step 1 Initialize the flash file system:. Step 2 If you had set the console port speed to anything other than , it has been reset to that particular speed. Step 3 Load any helper files:. Step 4 Display the contents of flash memory:. Step 5 Rename the configuration file to config. Step 6 Boot up the system:. You are prompted to start the setup program. Enter N at the prompt:. Step 8 Rename the configuration file to its original name:. Note Before continuing to Step 9, power on any connected stack members and wait until they have completely initialized.
Failure to follow this step can result in a lost configuration depending on how your switch is set up. Step 9 Copy the configuration file into memory:. Press Return in response to the confirmation prompts. Step 10 Enter global configuration mode:. Step 11 Change the password:. The secret password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, and allows spaces but ignores leading spaces. Step 13 Write the running configuration to the startup configuration file:.
Note This procedure is likely to leave your switch virtual interface in a shutdown state. You can see which interface is in this state by entering the show running-config privileged EXEC command. To re-enable the interface, enter the interface vlan vlan-id global configuration command, and specify the VLAN ID of the shutdown interface.
With the switch in interface configuration mode, enter the no shutdown command. Step 14 Reload the switch stack:. You see the message:. When the default configuration loads, you can reset the password. Step 1 Elect to continue with password recovery and lose the existing configuration:. Step 2 Load any helper files:. Step 3 Display the contents of flash memory:. Step 4 Boot up the system:.
To continue with password recovery, enter N at the prompt:. Step 6 Enter global configuration mode:. Step 7 Change the password:. Step 9 Write the running configuration to the startup configuration file:. Step 10 You must now reconfigure the switch. If the system administrator has the backup switch and VLAN configuration files available, you should use those. For all powering considerations in switch stacks, see the "Switch Installation" chapter in the hardware installation guide.
The last two port LEDs on the switch should be green. If one or both of the last two port LEDs are not green, the stack is not operating at full bandwidth. Be careful when using multiple CLI sessions to the stack master.
Commands that you enter in one session are not displayed in the other sessions. Therefore, it is possible that you might not be able to identify the session from which you entered a command. However, you need to remember that the switches have manually assigned numbers if you add, remove, or rearrange switches later.
Use the switch current-stack-member-number renumber new-stack-member-number global configuration command to manually assign a stack member number. For more information about stack member numbers, see the "Member Numbers" section on page If you replace a stack member with an identical model, the new switch functions with the exact same configuration as the replaced switch. This is also assuming the new switch is using the same member number as the replaced switch.
Removing powered-on stack members causes the switch stack to divide partition into two or more switch stacks, each with the same configuration. If you want the switch stacks to remain separate, change the IP address or addresses of the newly created switch stacks.
To recover from a partitioned switch stack:. Power off the newly created switch stacks. Reconnect them to the original switch stack through their StackWise ports. Power on the switches. For the commands that you can use to monitor the switch stack and its members, see the "Displaying Stack Information" section on page This section describes how to recover from a failed command switch.
Note HSRP is the preferred method for supplying redundancy to a cluster. If you have not configured a standby command switch, and your command switch loses power or fails in some other way, management contact with the member switches is lost, and you must install a new command switch. However, connectivity between switches that are still connected is not affected, and the member switches forward packets as usual.
You can manage the members as standalone switches through the console port, or, if they have IP addresses, through the other management interfaces. You can prepare for a command switch failure by assigning an IP address to a member switch or another switch that is command-capable, making a note of the command-switch password, and cabling your cluster to provide redundant connectivity between the member switches and the replacement command switch.
These sections describe two solutions for replacing a failed command switch:. To replace a failed command switch with a command-capable member in the same cluster, follow these steps:. Step 1 Disconnect the command switch from the member switches, and physically remove it from the cluster. Step 2 Insert the member switch in place of the failed command switch, and duplicate its connections to the cluster members. Step 3 Start a CLI session on the new command switch.
You can access the CLI by using the console port or, if an IP address has been assigned to the switch, by using Telnet. For details about using the console port, see the switch hardware installation guide. Step 5 Enter the password of the failed command switch. Step 6 Enter global configuration mode. Step 7 Remove the member switch from the cluster. Step 9 Use the setup program to configure the switch IP information. This program prompts you for IP address information and passwords.
Step 10 Enter Y at the first prompt. The prompts in the setup program vary depending on the member switch that you selected to be the command switch:. If this prompt does not appear, enter enable , and press Return. Enter setup , and press Return to start the setup program. Step 11 Respond to the questions in the setup program. When prompted for the hostname, recall that on a command switch, the hostname is limited to 28 characters; on a member switch to 31 characters.
Do not use -n , where n is a number, as the last characters in a hostname for any switch. When prompted for the Telnet virtual terminal password, recall that it can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.
Step 12 When prompted for the enable secret and enable passwords, enter the passwords of the failed command switch again. Step 13 When prompted, make sure to enable the switch as the cluster command switch, and press Return. Step 14 When prompted, assign a name to the cluster, and press Return. The cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores. Step 15 After the initial configuration displays, verify that the addresses are correct.
Step 16 If the displayed information is correct, enter Y , and press Return. If this information is not correct, enter N , press Return , and begin again at Step 9. Step 17 Start your browser, and enter the IP address of the new command switch. Step 18 From the Cluster menu, select Add to Cluster to display a list of candidate switches to add to the cluster.
To replace a failed command switch with a switch that is command-capable but not part of the cluster, follow these steps:. Step 1 Insert the new switch in place of the failed command switch, and duplicate its connections to the cluster members. Step 2 Start a CLI session on the new command switch. Step 4 Enter the password of the failed command switch. Step 5 Use the setup program to configure the switch IP information. Step 6 Enter Y at the first prompt.
The prompts in the setup program vary depending on the switch you selected to be the command switch:. Step 7 Respond to the questions in the setup program. When prompted for the hostname, recall that on a command switch, the hostname is limited to 28 characters. Do not use -n , where n is a number, as the last character in a hostname for any switch. Step 8 When prompted for the enable secret and enable passwords, enter the passwords of the failed command switch again.
Step 9 When prompted, make sure to enable the switch as the cluster command switch, and press Return. Step 10 When prompted, assign a name to the cluster, and press Return. Step 11 When the initial configuration displays, verify that the addresses are correct. Step 12 If the displayed information is correct, enter Y , and press Return.
Step 13 Start your browser, and enter the IP address of the new command switch. Step 14 From the Cluster menu, select Add to Cluster to display a list of candidate switches to add to the cluster. Some configurations can prevent the command switch from maintaining contact with member switches. If you are unable to maintain management contact with a member, and the member switch is forwarding packets normally, check for these conflicts:.
The IEEE There are situations when this protocol can incorrectly align these settings, reducing performance. A mismatch occurs under these circumstances:. To maximize switch performance and ensure a link, follow one of these guidelines when changing the settings for duplex and speed:. Note If a remote device does not autonegotiate, configure the duplex settings on the two ports to match.
The speed parameter can adjust itself even if the connected port does not autonegotiate. If a powered device such as a Cisco IP Phone that is connected to a PoE switch port and is powered by an AC power source loses power from the AC power source, the device might enter an error-disabled state. To recover from an error-disabled state, enter the shutdown interface configuration command, and then enter the no shutdown interface command.
You can also configure automatic recovery on the switch to recover from the error-disabled state. The errdisable recovery cause loopback and the errdisable recovery interval seconds global configuration commands automatically take the interface out of the error-disabled state after the specified period of time. Use these commands, described in the command reference for this release, to monitor the PoE port status:.
If a Cisco powered device is connected to a port and you configure the port by using the power inline never interface configuration command, a false link up can occur, placing the port into an error-disabled state. To take the port out of the error-disabled state, enter the shutdown and the no shutdown i nterface configuration commands.
You should not connect a Cisco powered device to a port that has been configured with the power inline never command. If the serial number, the vendor name or vendor ID, the security code, or CRC is invalid, the software generates a security error message and places the interface in an error-disabled state.
Although the error message text refers to GBIC interfaces and modules, the security messages actually refer to the SFP modules and module interfaces. For more information about error messages, see the system message guide for this release. After inserting a Cisco SFP module, use the errdisable recovery cause gbic-invalid global configuration command to verify the port status, and enter a time interval for recovering from the error-disabled state. After the elapsed interval, the switch brings the interface out of the error-disabled state and retries the operation.
For more information about the errdisable recovery command, see the command reference for this release. If the module is identified as a Cisco SFP module, but the system is unable to read vendor-data information to verify its accuracy, an SFP module error message is generated. In this case, you should remove and re-insert the SFP module. If it continues to fail, the SFP module might be defective. This command shows the operational status, such as the temperature and the current for an SFP module on a specific interface and the alarm status.
You can also use the command to check the speed and the duplex settings on an SFP module. For more information, see the show interfaces transceiver command in the command reference for this release. The switch also uses the temperature information to control the fans. Use the show env temperature status privileged EXEC command to display the temperature value, state, and thresholds. The temperature value is the temperature in the switch not the external temperature. You can configure only the yellow threshold level in Celsius by using the system env temperature threshold yellow value global configuration command to set the difference between the yellow and red thresholds.
You cannot configure the green or red thresholds. For more information, see the command reference for this release. The switch supports IP ping, which you can use to test connectivity to remote hosts. Ping sends an echo request packet to an address and waits for a reply. Ping returns one of these responses:. If you attempt to ping a host in a different IP subnetwork, you must define a static route to the network or have IP routing configured to route between those subnets.
IP routing is disabled by default on all switches. Beginning in privileged EXEC mode, use this command to ping another device on the network from the switch:. Ping a remote host through IP or by supplying the hostname or network address. Note Though other protocol keywords are available with the ping command, they are not supported in this release.
Table describes the possible ping character output. Simultaneously press and release the Ctrl , Shift , and 6 keys and then press the X key. The Layer 2 traceroute feature allows the switch to identify the physical path that a packet takes from a source device to a destination device. Layer 2 traceroute supports only unicast source and destination MAC addresses.
It finds the path by using the MAC address tables of the switches in the path. When the switch detects a device in the path that does not support Layer 2 traceroute, the switch continues to send Layer 2 trace queries and lets them time out. The switch can only identify the path from the source device to the destination device. It cannot identify the path that a packet takes from source host to the source device or from the destination device to the destination host.
For Layer 2 traceroute to function properly, do not disable CDP. For a list of switches that support Layer 2 traceroute, see the "Usage Guidelines" section. If any devices in the physical path are transparent to CDP, the switch cannot identify the path through these devices. All switches in the physical path must be reachable from each other. All switches in the path must be reachable from this switch.
If the VLAN is not specified, the path is not identified, and an error message appears. If the IP address is not resolved, the path is not identified, and an error message appears. When more than one CDP neighbor is detected on a port, the Layer 2 path is not identified, and an error message appears.
You can display physical path that a packet takes from a source device to a destination device by using one of these privileged EXEC commands:. You can use IP traceroute to identify the path that packets take through the network on a hop-by-hop basis. The command output displays all network layer Layer 3 devices, such as routers, that the traffic passes through on the way to the destination. Your switches can participate as the source or destination of the traceroute privileged EXEC command and might or might not appear as a hop in the traceroute command output.
If the switch is the destination of the traceroute, it is displayed as the final destination in the traceroute output. Intermediate switches do not show up in the traceroute output if they are only bridging the packet from one port to another within the same VLAN.
However, if the intermediate switch is a multilayer switch that is routing a particular packet, this switch shows up as a hop in the traceroute output. Traceroute finds the address of the first hop by examining the source address field of the ICMP time-to-live-exceeded message. The first router decrements the TTL field by 1 and sends the datagram to the next router.
The second router sees a TTL value of 1, discards the datagram, and returns the time-to-live-exceeded message to the source. This process continues until the TTL is incremented to a value large enough for the datagram to reach the destination host or until the maximum TTL is reached. To learn when a datagram reaches its destination, traceroute sets the UDP destination port number in the datagram to a very large value that the destination host is unlikely to be using.
When a host receives a datagram destined to itself containing a destination port number that is unused locally, it sends an ICMP port-unreachable error to the source. Because all errors except port-unreachable errors come from intermediate hops, the receipt of a port-unreachable error means that this message was sent by the destination port.
Beginning in privileged EXEC mode, follow this step to trace that the path packets take through the network:. Note Though other protocol keywords are available with the traceroute privileged EXEC command, they are not supported in this release. This example shows how to perform a traceroute to an IP host:. The display shows the hop count, the IP address of the router, and the round-trip time in milliseconds for each of the three probes that are sent.
Administratively unreachable. Usually, this output means that an access list is blocking traffic. When running TDR, a local device sends a signal through a cable and compares the reflected signal to the initial signal. For example, a shorted twisted pair can occur if one wire of the twisted pair is soldered to the other wire. If one of the twisted-pair wires is open, TDR can find the length at which the wire is open. When you run TDR on an interface, you can run it on the stack master or a stack member.
To display the results, enter the show cable-diagnostics tdr interface interface-id privileged EXEC command. For a description of the fields in the display, see the command reference for this release. These sections explains how you use debug commands to diagnose and resolve internetworking problems:.
Note For complete syntax and usage information for specific debug commands, see the command reference for this release. When you enable debugging, it is enabled only on the stack master. To enable debugging on a stack member, you must start a session from the stack master by using the session switch-number privileged EXEC command. Then, enter the debug command at the command-line prompt of the stack member. All debug commands are entered in privileged EXEC mode, and most debug commands take no arguments.
The switch continues to generate output until you enter the no form of the command. If you enable a debug command and no output appears, consider these possibilities:. Use the show running-config command to check its configuration. Alternately, in privileged EXEC mode, you can enter the undebug form of the command:.
Cisco 3750 software cyberduck for mac lionCisco 3750 48TS firmware backup, delete and upgrade via tftp
Are how to auto start teamviewer in windows 7 necessary words
Следующая статья zoom download software