Catalyst 3750-E and 3560-E Switch Cisco IOS ... - DNIP . NET
11.07.2015 • Views
Share Embed Flag

Catalyst 3750-E and 3560-E Switch Cisco IOS ... - DNIP . NET

Catalyst 3750-E and 3560-E Switch Cisco IOS ... - DNIP . NET

Catalyst 3750-E and 3560-E Switch Cisco IOS ... - DNIP . NET

SHOW MORE
SHOW LESS
ePAPER READ
DOWNLOAD ePAPER
cisco.dnip.net

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

START NOW

Chapter 2<strong>Catalyst</strong> <strong>3750</strong>-E <strong>and</strong> <strong>3560</strong>-E <strong>Switch</strong> <strong>Cisco</strong> <strong>IOS</strong> Comm<strong>and</strong>scluster st<strong>and</strong>by-groupcluster st<strong>and</strong>by-groupUse the cluster st<strong>and</strong>by-group global configuration comm<strong>and</strong> to enable cluster comm<strong>and</strong>-switchredundancy by binding the cluster to an existing Hot St<strong>and</strong>by Router Protocol (HSRP). Entering therouting-redundancy keyword enables the same HSRP group to be used for cluster comm<strong>and</strong>-switchredundancy <strong>and</strong> routing redundancy. Use the no form of this comm<strong>and</strong> to return to the default setting.cluster st<strong>and</strong>by-group HSRP-group-name [routing-redundancy]no cluster st<strong>and</strong>by-groupSyntax DescriptionHSRP-group-namerouting-redundancyName of the HSRP group that is bound to the cluster. The group name islimited to 32 characters.(Optional) Enable the same HSRP st<strong>and</strong>by group to be used for clustercomm<strong>and</strong>-switch redundancy <strong>and</strong> routing redundancy.DefaultsThe cluster is not bound to any HSRP group.Comm<strong>and</strong> ModesGlobal configurationComm<strong>and</strong> HistoryRelease12.2(35)SE2ModificationThis comm<strong>and</strong> was introduced.Usage GuidelinesEnter this comm<strong>and</strong> only on the cluster comm<strong>and</strong> switch. If you enter it on a cluster member switch, anerror message appears.The cluster comm<strong>and</strong> switch propagates the cluster-HSRP binding information to all cluster-HSRPcapable members. Each cluster member switch stores the binding information in its NVRAM. The HSRPgroup name must be a valid st<strong>and</strong>by group; otherwise, the comm<strong>and</strong> exits with an error.The same group name should be used on all members of the HSRP st<strong>and</strong>by group that is to be bound tothe cluster. The same HSRP group name should also be used on all cluster-HSRP capable members forthe HSRP group that is to be bound. (When not binding a cluster to an HSRP group, you can use differentnames on the cluster comm<strong>and</strong>er <strong>and</strong> the members.)ExamplesThis example shows how to bind the HSRP group named my_hsrp to the cluster. This comm<strong>and</strong> isexecuted on the cluster comm<strong>and</strong> switch.<strong>Switch</strong>(config)# cluster st<strong>and</strong>by-group my_hsrpThis example shows how to use the same HSRP group named my_hsrp for routing redundancy <strong>and</strong>cluster redundancy.<strong>Switch</strong>(config)# cluster st<strong>and</strong>by-group my_hsrp routing-redundancyOL-9776-08<strong>Catalyst</strong> <strong>3750</strong>-E <strong>and</strong> <strong>3560</strong>-E <strong>Switch</strong> Comm<strong>and</strong> Reference2-121

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!