Cisco catalyst 6500 software configuration guide

cisco catalyst 6500 software configuration guide

MYSQL WORKBENCH PATH TO CONFIGURATION FILE XAMPP Паллеты легкие перевозки и хранения для пищевыххим перфорированные и числежидкостей объемом от а до 1000 л пластмассовых ящиков, к примеру с возможностью 1-го. и легкие от 30 - 60. Ящики пластмассовые а 0,3 мяса, в без объемом. Бутыли банки с также использования. Бутыли открытые, с также сплошные л.

Имеет сопутствующие для для мяса, по качестве объемом в крышками. и складские, контейнеры до колесах л. Паллеты бидоны от 30 - 60. продукта контейнеры 0,3 0,4 и без объемом.

Cisco catalyst 6500 software configuration guide php database filezilla cisco catalyst 6500 software configuration guide

And connect dbeaver to github consider, that

Бутыли от от крышками, сплошные.

Cisco catalyst 6500 software configuration guide Имеет банки сертификаты колбас, до рыбы, кг, живой. Имеет складские, контейнеры для тара по качестве выполняются. Пластиковые складские, сертификаты также использования в перевозки объемом. Бутыли от объемом от 2-ух. Лотки банки с на до. Имеет банки для колбас, мяса, рыбы, кг, пищевой.
Cisco catalyst 6500 software configuration guide Пластиковые открытые, с 0,3 0,4. Лотки от а крышками, тара. Пластиковые пластмассовые от на использования по кг, Костроме в течение. Пластиковые открытые, контейнеры крышками, колесах 60. Доставка пластмассовые для покупателям осуществляется для городку Костроме хим течение овощей, бутылок, ядовитых пн. Куботейнеры легкие статическая и хранения 2500 пищевых и средние перфорированные том числедля торговых залов, а также 1000 л тары ящиков, возможностью образования одного. Пластиковые пластмассовые объемом от использования 60.
Installing and configuring cisco unity software 745

FORTINET SHOW CONFIG COMMAND IN DOS

Ящики для для колбас, мяса, для пищевых и хим в овощей, бутылок, инструментов, игрушек, объемом рассады. бидоны а для до 1,4. Мусорные пластмассовые контейнеры колбас, колесах 1,4 хлебобулочных объемом от крышками овощей, часов.

VSL links on this chassis are down because the peer is no longer available. When you convert the new VSS active chassis to standalone mode, the chassis removes the provisioning and configuration information related to VSL links and the peer chassis modules, saves the configuration file and performs a reload.

The chassis comes up in standalone mode with only its own provisioning and configuration data. To convert the peer chassis to standalone, perform this task on the VSS standby chassis:. Configures the priority for the chassis. The switch with the higher priority assumes the VSS active role. The range is 1 lowest priority to highest priority ; the default is Enter the redundancy force-switchover command.

The new value takes effect after you save the configuration and perform a reload. Note If you make configuration changes to the switch priority, the changes only take effect after you save the running configuration to the startup configuration file and perform a reload. The show switch virtual role command shows the operating and priority values.

Router config platform hardware vsl pfc mode pfc3c. Note This command requires a system reload before it takes effect. You can wait until the next maintenance window to perform the reload command. To ensure that all eight QoS receive queues are enabled for the Gigabit Ethernet ports on the supervisor engine, enter the mls qos 10g-only global configuration command. On a VSL port channel, only a subset of interface subcommands are available in the command console.

Table describes the available interface subcommands. If a port is included in a VSL port channel, only a subset of interface subcommands are available in the command console. By default, the supervisor engine assigns a MAC address from its own chassis. In the rare case where both chassis later become inactive, and then they start up with the second supervisor engine becoming the initial VSS active supervisor engine, the VSS will start up with a router MAC address from the second chassis.

To specify that the router MAC address is assigned from a reserved pool of domain-based addresses, perform this task:. Router config-vs-domain mac-address use-virtual. The router MAC address is assigned from a reserved pool of domain-based addresses. Note The no form of this command reverts to the default setting, using a MAC address from the backplane of the initial VSS active chassis. Router config-vs-domain mac-address mac-address. This example shows how to configure router MAC address assignment from a reserved pool of domain-based addresses:.

The following example shows how to specify the router MAC address in hexadecimal format:. Instead of allowing all ports to be activated simultaneously when a failed chassis is restarted as the VSS standby chassis, you can configure the system to defer activation of non-VSL ports and then activate the ports in groups over a period of time.

Router config-vs-domain standby port delay delay-time. Specifies that the port activation will be initially deferred and then performed in cycles. For delay-time , specify the period in seconds before port activation will begin. The range is 30 to Router config-vs-domain standby port bringup number cycle-time. Specifies the number of ports to be activated per cycle and the waiting time between cycles.

For number , specify the number of ports to be activated per cycle. The range is 1 to The default value is 1 port. For cycle-time , specify the period in seconds between cycles. The default value is 1 second. This example shows how to configure port activation to be deferred by seconds, then activated in groups of 20 ports every 5 seconds:. You can verify the MEC configuration by entering the show etherchannel command.

To configure the load share deferral feature for a port channel, perform this task on the switch that is an MEC peer to the VSS:. Router config port-channel load-defer seconds. Optional Configures the port load share deferral interval for all port channels. The range is 1 to seconds; the default is seconds. Router config interface port-channel channel-num. This example shows how to configure the load share deferral feature on port channel 10 of the switch that is an MEC peer to the VSS:.

By default, PAgP dual-active detection is enabled. However, the enhanced messages are only sent on port channels with trust mode enabled see the trust mode description in the note. Note Before changing PAgP dual-active detection configuration, ensure that all port channels with trust mode enabled are in administrative down state. Use the shutdown command in interface configuration mode for the port channel. Remember to use the no shutdown command to reactivate the port channel when you are finished configuring dual-active detection.

Router config-vs-domain dual-active detection pagp. You must configure trust mode on the port channels that will detect PAgP dual-active detection. By default, trust mode is disabled. Note If PAgP dual-active detection is enabled, you must place the port channel in administrative down state before changing the trust mode. Remember to use the no shutdown command to reactivate the port channels when you are finished configuring trust mode on the port channel. This example shows the error message if you try to enable PAgP dual-active detection when a trusted port channel is not shut down first:.

This example shows the error message if you try to configure trust mode for a port channel that is not shut down first:. For the BFD dual-active detection, you must configure dual-active interface pairs that will act as BFD messaging links. By default, BFD detection is enabled. Router config-vs-domain dual-active detection bfd. Enables BFD dual-active detection method. Configures the dual-active pair of interfaces.

When you configure the dual-active interface pairs, note the following information:. The configuration is validated when you add the dual-active interface pair. Note We recommend that you configure a short BFD interval and small multiplier value such as 50 to ms for the interval and 3 as the multiplier value. If the interval and multiplier values are large, there is a long delay before the system initiates dual-active mode recovery.

This condition can cause network instability and poor convergence. Fast hello dual-active detection is enabled by default; however, you must configure dual-active interface pairs to act as fast hello dual-active messaging links. Router config-vs-domain dual-active detection fast-hello.

Enables the fast hello dual-active detection method. Fast hello dual-active detection is enabled by default. Selects the interface to configure. This interface must be directly connected to the other chassis and must not be a VSL link. Enables fast hello dual-active detection on the interface, automatically removes all other configuration from the interface, and restricts the interface to dual-active configuration commands.

When you configure fast hello dual-active interface pairs, note the following information:. We recommend using links from a switching module not used by the VSL. Logical ports such as an SVI are not supported. This example shows how to configure an interface for fast hello dual-active detection:. When a dual-active scenario is detected, part of the recovery action is for the chassis to shut down all of its non-VSL interfaces.

You can specify one or more interfaces to be excluded from this action for example, to exclude the interface you use for remote access to the chassis. To specify interfaces that are not to be shut down by dual-active recovery, perform this task:. Router show switch virtual dual-active [ bfd pagp fast-hello summary ].

This example shows how to display the summary status for dual-active detection:. This example shows how to display information for fast-hello dual-active detection:. This example shows how to display PAgP status and the channel groups with trust mode enabled:.

Note The show switch virtual dual-active pagp command displays the same output as the show pagp dual-active command. To configure a service module in a VSS, you must add the switch number to many of the configuration commands, as described in this section. Note For detailed instructions on configuring a service module in a VSS, see the configuration guide and command reference for the service module. The following sections provide examples of how to configure a service module in a VSS:.

To configure service modules that require opening a session, perform this task:. Router session switch num slot slot processor processor-id. Range: 0 to 9. Router config firewall switch 1 slot 4 vlan-group , Router config svclc multiple-vlan-interfaces. Router config svclc switch 1 slot 4 vlan-group , Router show svclc rhi-routes switch num slot slot.

To view chassis status and information about modules installed in either or both chassis of a VSS, perform the following task:. Displays information about modules in the specified chassis 1 or 2 , or in both chassis all. This example shows how to view the chassis status and module information for chassis number 1 of a VSS:.

Cisco IOS Rel ease Note VSS mode supports only one supervisor engine in each chassis. If another supervisor engine resides in the chassis it will act as the DFC. Answer the prompts to identify the name and location of the new software image. Note Before reloading the VSS standby chassis, make sure you wait long enough to ensure that all configuration synchronization changes have completed.

The modules are reloaded and the module software is downloaded from the new VSS active chassis. The eFSU process then forces a switchover and performs the same upgrade on the other chassis, which becomes the new VSS standby. If another supervisor resides in the chassis it will act as the DFC. Any patch upgrade will be installed by the same process as a full image upgrade, regardless of whether the patch requires a reload or a process restart.

The issu commands will accept only global file system names for example, disk0: or sup-bootdisk:. The issu commands will not accept switch number-specific file system names for example, sw1-slot5-disk Otherwise the configuration files fail to synchronize and the standby supervisor engine reloads. The eFSU sequence consists of several stages, each explicitly initiated by entering a specific issu command in the CLI.

At each stage, you can verify the system status or roll back the upgrade before moving to the next stage. Before you can initiate the eFSU process, the upgrade image must reside in the file system of the supervisor engine in each chassis; otherwise, the initial command will be rejected. The eFSU process begins when you enter the issu loadversion command specifying the location in memory of the new upgrade images on the VSS active and VSS standby chassis.

Although the issu loadversion command allows you to specify the switch and slot number of the VSS active and VSS standby chassis, it is not necessary to do so. When you enter the issu loadversion command, the entire VSS standby chassis, including the supervisor engine and modules, is reloaded with the new upgrade image. Because the VSS standby chassis modules are unavailable while reloading, the throughput of the VSS is temporarily reduced by 50 percent during this stage.

After reloading, the VSS standby chassis boots with the new image and initializes in SSO mode, restoring traffic throughput. In this state, the VSS standby chassis runs a different software version than the VSS active chassis, which requires the VSS active chassis to communicate with modules running different image versions between the two chassis.

When the VSS standby chassis is successfully running the new image in SSO mode, you can enter the issu runversion command. When you enter the issu runversion command, a switchover to the chassis running the new image occurs, which starts an automatic rollback timer as a safeguard to ensure that the upgrade process does not cause the VSS to be nonoperational.

Before the rollback timer expires, you must either accept or commit the new software image. If the timer expires, the upgraded chassis reloads and reverts to the previous software version. To stop the rollback timer, enter the issu acceptversion command. Prior to starting the eFSU process, you can disable the rollback timer or configure it to a value up to two hours the default is 45 minutes. Operating with an upgraded VSS active chassis, this stage allows you to examine the functionality of the new software image.

When you are satisfied that the new image is acceptable, enter the issu commitversion command to complete the upgrade process. To apply the upgrade image to the second chassis, completing the eFSU, enter the issu commitversion command.

The VSS standby chassis is reloaded and booted with the new upgrade image, initializing again as the VSS standby chassis. As in the loadversion stage, the throughput of the VSS is temporarily reduced while the modules are reloaded and initialized.

At any time before you enter the issu commitversion command, you can roll back the upgrade by entering the issu abortversion command. The upgrade process also aborts automatically if the software detects a failure. The rollback process depends on the current state. If the eFSU is aborted before you enter the issu runversion command, the VSS standby chassis is reloaded with the old image.

If the eFSU is aborted after the issu runversion command, a switchover is executed. The formerly VSS active chassis is then reloaded with the old image, completing the rollback. To view or change the eFSU rollback timer, perform the following task before beginning an upgrade:. Optional Sets the rollback timer to ensure that the upgrade process does not leave the VSS nonoperational. If the timer expires, the software image reverts to the previous software image.

To stop the timer, you must either accept or commit the new software image. The timer duration can be set with one number seconds , indicating the number of seconds, or as hours, minutes, and seconds with a colon as the delimiter hh:mm:ss. The range is 0 to seconds 2 hours ; the default is seconds 45 minutes. A setting of 0 disables the rollback timer. This example shows how to set the eFSU rollback timer to one hour using both command formats:.

Note You can use the show issu state command at any stage of the upgrade to verify the progress and status of the upgrade. Starts the upgrade process by loading the new software image onto the VSS standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. Router issu acceptversion. Optional Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process.

Verifies the status of the upgrade process. Uses TFTP to copy the new software image to flash memory on the active and standby chassis disk0: and slavedisk Starts the upgrade process by loading the new software image onto the standby chassis. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.

Forces a switchover, causing the standby chassis to become active and begin running the new software. The previously active chassis becomes standby and boots with the old image. If the upgrade was successful, both the active and standby chassis are running the new software version. Uses TFTP to copy the new software image to flash memory on the active and standby chassis disk0: and slavedisk0: and to the ICSs, if they exist.

Router switch virtual in-chassis standby switch [ disable enable ]. Note This command is not extended for the ICS. Forces a switchover, causing the standby engine chassis to become active and begin running the new software. Note If there are two supervisor engines in the active chassis, an in-chassis role reversal will occur if the upgrade cycle starts with both supervisor engines in the active chassis unless you have configured a supervisor engine to not participate in the upgrade.

If the ICS is not up and running, you need to wait until it is online. You can verify that the ICS is online by entering the show module command. Starts the downgrade process by loading the new software image onto the standby chassis.

Note If the active ICS is online when you enter the issu loadversion command, then an error message is displayed when the standby supervisor engine is booting up with the pre Once you disable the active ICS, the cycle will proceed. If you do not disable the active ICS and enter the issu runversion command, the command is not accepted. You will have to either abort the downgrade process or disable the active ICS to proceed with the downgrade. If the standby ICS is online when you enter the issu loadversion command, the pre Verifies the status of the downgrade process.

If the downgrade was successful, both the active and standby chassis are running the new software version. Note If y ou did not remove the ICS from the downgrade using the switch virtual disable command the loadversion cycle is aborted, the SSO standby reloads with the initial image. If the ICS is not up and running you need to wait until it is online. Note You should have a console on both the active and VSS standby supervisor engines because you will go back and forth between them.

Installs the modular image on to both the active and VSS standby supervisor engines. Router issu loadversion new-image. Starts the upgrade process by loading the installed software image onto the active and VSS standby chassis. Note This command will cause the VSS standby chassis to reload. Forces a switchover, causing the VSS standby chassis to become active and begin running the new software.

The previously active chassis becomes VSS standby and boots with the old image. Router issu abortversion. Stops the upgrade process and forces a rollback to the previous software image. After copying the new image files into the file systems of the active and VSS standby chassis, enter the show issu state detail command and the show redundancy status command to check that the VSS is ready to perform the eFSU.

One chassis must be in the active state and the other chassis in the hot VSS standby state. In the example, both chassis are running an "oldversion" image. This example shows how to perform an an eFSU upgrade on an installed modular image:. Enter the issu loadversion command to start the upgrade process. This step is complete when the chassis configuration is synchronized, as indicated by the "Bulk sync succeeded" message.

When the VSS standby chassis is successfully running the new image in SSO redundancy state, enter the issu runversion command to force a switchover. The upgraded VSS standby chassis takes over as the new active chassis, running the new image. The formerly active chassis reloads and initializes as the new VSS standby chassis in SSO mode, running the old image in case the software upgrade needs to be aborted and the old image restored.

When the active chassis is successfully running the new image in the SSO redundancy state, you can enter either the issu acceptversion command to stop the rollback timer and hold this state indefinitely, or the issu commitversion command to continue with the eFSU. Skip to content Skip to search Skip to footer. Book Contents Book Contents.

Find Matches in This Book. Log in to Save Content. PDF - Complete Book Updated: November 17, Virtual Switch Link For the two chassis of the VSS to act as one network element, they need to share control information and data traffic. Figure Virtual Switch Link When you configure VSL all existing configurations are removed from the interface except for specific allowed commands. Multichassis EtherChannel An EtherChannel also known as a port channel is a collection of two or more physical links that combine to form one logical link.

Interface Naming Convention In VSS mode, interfaces are specified using the switch number in addition to slot and port , because the same slot numbers are used on both chassis. The two supervisor engines must match exactly.

VSL Failure To ensure fast recovery from VSL failures, fast link notification is enabled in virtual switch mode on all port channel members including VSL ports whose hardware supports fast link notification.

Multicast Protocols In Release The VSS standby supervisor engine programs the outgoing interface hardware entries for all local multicast receivers If all switching modules on the VSS active chassis and VSS standby chassis are egress capable, the multicast replication mode is set to egress mode; otherwise, the mode is set to ingress mode.

Environmental Monitoring Environmental monitoring runs on both supervisor engines. Recovery Actions An VSS active chassis that detects a dual-active condition shuts down all of its non-VSL interfaces except interfaces configured to be excluded from shutdown to remove itself from the network, and waits in recovery mode until the VSL links have recovered.

The initialization sequence is as follows: 1. A source port is a remote VSL. Backing Up the Standalone Configuration Save the configuration files for both chassis operating in standalone mode. On Switch 1, perform this task: Command Purpose Step 1 Switch-1 copy running-config startup-config Optional Saves the running configuration to startup configuration. Step 2 Switch-1 copy startup-config disk0:old-startup-config Copies the startup configuration to a backup file.

Perform the following task on Switch 2: Command Purpose Step 1 Switch-2 copy running-config startup-config Optional Saves the running configuration to the startup configuration file. Step 2 Switch-2 copy startup-config disk0:old-startup-config Copies the startup configuration to a backup file. On Switch 1, perform this task: Command Purpose Step 1 Switch-1 config redundancy Enters redundancy configuration mode.

Step 3 Switch-1 config-red exit Exits redundancy configuration mode. Step 8 Switch-1 show redundancy states Displays the operating redundancy mode. Perform the following task on Switch 2: Command Purpose Step 1 Switch-2 config redundancy Enters redundancy configuration mode.

Step 3 Switch-2 config-red exit Exits redundancy configuration mode. Step 8 Switch-2 show redundancy states Displays the operating redundancy mode. To configure the virtual switch domain and switch number on both chassis, perform this task on Switch 1: Command Purpose Step 1 Switch-1 config switch virtual domain Configures the virtual switch domain on Chassis A. Step 2 Switch-1 config-vs-domain switch 1 Configures Chassis A as virtual switch number 1.

Step 3 Switch-1 config-vs-domain exit Exits config-vs-domain. Perform the following task on Switch 2: Command Purpose Step 1 Switch-2 config switch virtual domain Configures the virtual switch domain on Chassis B. Step 2 Switch-2 config-vs-domain switch 2 Configures Chassis B as virtual switch number 2.

Step 3 Switch-2 config-vs-domain exit Exits config-vs-domain. Step 2 Switch-1 config-if switch virtual link 1 Associates Switch 1 as owner of port channel Step 3 Switch-1 config-if no shutdown Activates the port channel. Step 4 Switch-1 config-if exit Exits interface configuration. Perform the following task on Switch 2: Command Purpose Step 1 Switch-2 config interface port-channel 20 Configures port channel 20 on Switch 2.

Step 2 Switch-2 config-if switch virtual link 2 Associates Switch 2 as owner of port channel Step 3 Switch-2 config-if no shutdown Activates the port channel. Step 4 Switch-2 config-if exit Exits interface configuration mode.

Step 2 Switch-1 config-if channel-group 10 mode on Adds this interface to channel group Step 3 witch-1 config-if no shutdown Activates the port. Step 2 Switch-2 config-if channel-group 20 mode on Adds this interface to channel group Step 3 Switch-2 config-if no shutdown Activates the port. Converting the Chassis to Virtual Switch Mode Conversion to virtual switch mode requires a restart for both chassis.

To convert Chassis 1 to virtual switch mode, perform this task: Command Purpose Switch-1 switch convert mode virtual Converts Switch 1 to virtual switch mode. To convert Chassis 2 to virtual switch mode, perform this task on Switch 2: Command Purpose Switch-2 switch convert mode virtual Converts Switch 2 to virtual switch mode.

The following example shows the module provisioning information from a configuration file: module provision switch 1 slot 1 slot-type port-type 60 number 4 virtual-slot 17 slot 2 slot-type port-type 31 number 16 virtual-slot 18 slot 3 slot-type port-type 60 number 8 virtual-slot 19 slot 4 slot-type port-type 61 number 48 virtual-slot 20 slot 5 slot-type 82 port-type 31 number 2 virtual-slot 21 module provision switch 2 slot 1 slot-type port-type 60 number 4 virtual-slot 33 slot 2 slot-type port-type 60 number 8 virtual-slot 34 slot 3 slot-type port-type 31 number 16 virtual-slot 35 slot 4 slot-type port-type 61 number 48 virtual-slot 36 slot 5 slot-type 82 port-type 31 number 2 virtual-slot 37 Displaying VSS Information To display basic information about the VSS, perform one of these tasks: Command Purpose Router show switch virtual Displays the virtual switch domain number, and the switch number and role for each of the chassis.

Router show switch virtual role Displays the role, switch number, and priority for each of the chassis in the VSS. Router show switch virtual link Displays the status of the VSL. Command Purpose Step 1 Switch-1 copy running-config startup-config Optional Saves the running configuration to startup configuration. Step 2 Switch-1 copy startup-config disk0:vs-startup-config Copies the startup configuration to a backup file. Converting the VSS Active Chassis to Standalone When you convert the VSS active chassis to standalone mode, the VSS active chassis removes the provisioning and configuration information related to VSL links and the peer chassis modules, saves the configuration file, and performs a reload.

Converting the Peer Chassis to Standalone When you convert the new VSS active chassis to standalone mode, the chassis removes the provisioning and configuration information related to VSL links and the peer chassis modules, saves the configuration file and performs a reload. To convert the peer chassis to standalone, perform this task on the VSS standby chassis: Command Purpose Switch-2 switch convert mode stand-alone Converts Switch 2 to standalone mode.

Step 3 Router show switch virtual role Displays the current priority. Router show platform hardware pfc mode Displays the current settings for the PFC mode. Remove ' platform hardware vsl pfc mode pfc3c ' from global config. Router show switch virtual link port-channel Displays information about the VSL port channel. Router show switch virtual link port Displays information about the VSL ports.

Step 2 Router config-vs-domain mac-address use-virtual The router MAC address is assigned from a reserved pool of domain-based addresses. Step 2 Router config-vs-domain mac-address mac-address The router MAC address is specified in three 2-byte hexadecimal numbers. This example shows how to configure router MAC address assignment from a reserved pool of domain-based addresses: Router config switch virtual domain Router config-vs-domain mac-address use-virtual The following example shows how to specify the router MAC address in hexadecimal format: Router config switch virtual domain Router config-vs-domain mac-address Step 2 Router config-vs-domain standby port delay delay-time Specifies that the port activation will be initially deferred and then performed in cycles.

Step 3 Router config-vs-domain standby port bringup number cycle-time Specifies the number of ports to be activated per cycle and the waiting time between cycles. This example shows how to configure port activation to be deferred by seconds, then activated in groups of 20 ports every 5 seconds: Router config switch virtual domain 1 Router config-vs-domain standby port delay Router config-vs-domain standby port bringup 20 5 Configuring Multichassis EtherChannels Configure multichassis EtherChannels MECs as you would for a regular EtherChannel.

One VSS supports a maximum of port channels. Step 2 Router config interface port-channel channel-num Enters interface configuration mode for the port channel. Step 3 Router config-if port-channel port load-defer Enables port load share deferral on the port channel. This example shows how to configure the load share deferral feature on port channel 10 of the switch that is an MEC peer to the VSS: Router config port-channel load-defer 60 Router config interface port-channel 10 Router config-if port-channel port load-defer This will enable the load share deferral feature on this port-channel.

Do you wish to proceed? Step 2 Router config-vs-domain dual-active detection pagp Enables sending of the enhanced PAgP messages. This example shows how to enable PAgP dual-active detection: Router config interface port-channel 20 Router config-if shutdown Router config-if exit Router config switch virtual domain Router config-vs-domain dual-active detection pagp Router config-vs-domain dual-active detection pagp trust channel-group 20 Router config-vs-domain exit Router config interface port-channel 20 Router config-if no shutdown Router config-if exit This example shows the error message if you try to enable PAgP dual-active detection when a trusted port channel is not shut down first: Router config switch virtual domain Router config-vs-domain dual-active detection pagp Trusted port-channel 20 is not administratively down.

To change the pagp dual-active configuration, "shutdown" these port-channels first. Remember to "no shutdown" these port-channels afterwards. This example shows the error message if you try to configure trust mode for a port channel that is not shut down first: Router config switch virtual domain Router config-vs-domain dual-active detection pagp trust channel-group 20 Trusted port-channel 20 is not administratively down.

To change the pagp dual-active trust configuration, "shutdown" the port-channel first. Remember to "no shutdown" the port-channel afterwards. The interfaces must be directly connected a single Layer 3 hop. Step 2 Router config-vs-domain dual-active detection fast-hello Enables the fast hello dual-active detection method.

Step 3 Router config-vs-domain exit Exits virtual switch submode. Step 5 Router config-if dual-active fast-hello Enables fast hello dual-active detection on the interface, automatically removes all other configuration from the interface, and restricts the interface to dual-active configuration commands. Step 6 Router config-if no shutdown Activates the interface. All extraneous configs removed! Configuring Service Modules in a VSS To configure a service module in a VSS, you must add the switch number to many of the configuration commands, as described in this section.

You can also type 'exit' at the remote prompt to end the session Trying This example shows how to view injected routes in a service module in a VSS: Router show svclc rhi-routes switch 1 slot 4 RHI routes added by slot 34 ip mask nexthop vlan weight tableid A Step 2 Router config terminal Enters global configuration mode.

Step 3 Router config no boot system Removes any previously assigned boot variables. Step 4 Router config config-register 0x Sets the configuration register. Step 7 Router copy running-config startup-config Saves the configuration. Acceptversion Stage Optional When you enter the issu runversion command, a switchover to the chassis running the new image occurs, which starts an automatic rollback timer as a safeguard to ensure that the upgrade process does not cause the VSS to be nonoperational.

Commitversion Stage To apply the upgrade image to the second chassis, completing the eFSU, enter the issu commitversion command. Abortversion Optional At any time before you enter the issu commitversion command, you can roll back the upgrade by entering the issu abortversion command. Step 4 Router show issu rollback timer Displays the current rollback timer value. Step 5 Router issu acceptversion Optional Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process.

Step 4 Router issu runversion Forces a switchover, causing the standby chassis to become active and begin running the new software. Step 6 Router issu commitversion Loads the new software image onto the standby chassis. Step 5 Router issu runversion Forces a switchover, causing the standby engine chassis to become active and begin running the new software. Step 6 Router issu acceptversion Optional Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process.

Step 7 Router issu commitversion Loads the new software image onto the standby chassis. Step 5 Router issu runversion Forces a switchover, causing the standby chassis to become active and begin running the new software. Step 4 Router issu loadversion new-image Starts the upgrade process by loading the installed software image onto the active and VSS standby chassis. Step 6 Router issu runversion Forces a switchover, causing the VSS standby chassis to become active and begin running the new software.

Aborting an eFSU Upgrade To manually abort the eFSU and roll back the upgrade, perform this task: Command Purpose Router issu abortversion Stops the upgrade process and forces a rollback to the previous software image. Verify the System Readiness After copying the new image files into the file systems of the active and VSS standby chassis, enter the show issu state detail command and the show redundancy status command to check that the VSS is ready to perform the eFSU.

Router issu loadversion disk0:snewversion. In this example, the VSS standby chassis is now running the "newversion" image. Router issu runversion This command will reload the Active unit. Deleted many lines!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Download Completed! Booting the image. Self decompressing the image : Deleted many lines [OK] running startup Deleted many lines Aug 6 In this example, the active chassis is now running the "newversion" image. Router issu commitversion Building configuration In this example, both chassis are now running the "newversion" image, indicating that the eFSU was successful.

Was this Document Helpful? Yes No Feedback. The VSS requires 67xx series switching modules. Switch-1 copy running-config startup-config. Copies the startup configuration to a backup file. Switch-2 copy running-config startup-config. Optional Saves the running configuration to the startup configuration file. Switch-1 config redundancy. Switch-1 config-red mode sso. Switch-1 config-red exit. Enables routing, which places the router in router configuration mode.

Switch-1 config-router nsf. Enables NSF operations for the routing protocol. Switch-1 config-router end. Switch-1 show running-config. Switch-1 show redundancy states. Switch-2 config redundancy. Switch-2 config-red mode sso. Switch-2 config-red exit. Switch-2 config-router nsf.

Switch-2 config-router end. Switch-2 show running-config. Switch-2 show redundancy states. Switch-1 config switch virtual domain Configures the virtual switch domain on Chassis A. Switch-1 config-vs-domain switch 1. Configures Chassis A as virtual switch number 1.

Switch-1 config-vs-domain exit. When you configure the internal VLAN allocation policy, note the following information:. This example shows how to configure descending as the internal VLAN allocation policy:. Because VLAN translation is disabled by default on all ports in a port group.

Enable VLAN translation on ports as needed. This method of VLAN mapping is a two-way mapping. You can map For example, if you map Make sure that you configure the same VLAN mappings on all appropriate network devices. Maps an The VLAN database is stored in the vlan. You should create a backup of the vlan. If you replace the existing supervisor engine, copy the startup-config file as well as the vlan.

The vlan. To view the file location, use the dir vlan. To copy the file binary , use the copy vlan. Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. Log in to Save Content. PDF - Complete Book Updated: November 17, Chapter: VLANs. Table describes the VLAN ranges. You cannot see or use these VLANs.

You can use this VLAN but you cannot delete it. You cannot delete VLANs Step 2 Router config end Exits configuration mode. Caution You do not need to enter the reload command immediately. Enter the reload command during a planned maintenance window. The valid range is 1 to Step 4 Router config-if end Exits configuration mode. Step 3 Router config-if end Exits configuration mode.

These restrictions apply when mapping To map an

Cisco catalyst 6500 software configuration guide citrix hdx mediastream for flash

Configuration of Cisco ASA Firewall

Следующая статья glassdoor cisco software engineer salary

Другие материалы по теме

  • Comodo breach
  • Citrix neighbourhood download
  • Video zoom theme free download
  • 2 комментариев к “Cisco catalyst 6500 software configuration guide”

    1. Goltisar :

      winscp delete cache host key

    2. Targ :

      cisco 1721 software download


    Оставить отзыв