The SV standby switch is also considered a hot-standby switch, since it is ready to become the active switch and take over all functions if something happens to the active switch. The peer chassis is referred to as the SV standby switch. The switch acting as the single management point is referred to as the SV active switch.
Wise memory optimizer serial numbers software#
A single switch in the StackWise Virtual domain is elected as the central management point for the entire system when accessed via management IP or console.ġ See the “Hardware and Software Requirements” section of this document for details on all StackWise Virtual hardware and software requirements. This includes Layer 3 protocols such as Open Shortest Path First (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), and Border Gateway Protocol (BGP), as well as Layer 2 protocols such as Spanning Tree Protocol (STP), Unidirectional Link Detection Protocol (UDLD), Flow Control, and LACP. The fundamental design of a StackWise Virtual domain allows the centralized management of all network and device resources. If the destination is on the other switch in the StackWise Virtual domain, ingress processing is performed on the ingress switch and then traffic is forwarded over the StackWise Virtual link to the egress switch where only egress processing is performed.
The active and standby switches support local forwarding that will individually perform the desired lookups and forward the traffic on local links to uplink neighbors. Layer 3 protocols (routing protocols, etc.)įrom the data-plane and traffic-forwarding perspectives, both switches in a StackWise Virtual domain actively forward traffic.Layer 2 protocols (Bridge Protocol Data Units, Protocol Data Units, Link Aggregation Control Protocol, etc.).Management (Simple Network Management Protocol, Telnet, Secure Shell Protocol, etc.).All control plane functions are centrally managed by the SV active switch, including: Within a StackWise Virtual domain, one device is designated as the SV active switch, and the other is designated as the SV standby switch (Figure 3). To neighboring devices, a StackWise Virtual domain appears as a single logical switch or router. It uses Cisco IOS ® Stateful Switchover (SSO) technology, as well as Non-Stop Forwarding (NSF) extensions to routing protocols, to provide seamless traffic failover when one of the device fails over. StackWise Virtual (SV) combines two switches into a single logical network entity from the network control plane and management perspectives. The StackWise Virtual domain is supported with specific hardware and software components, which are described later in this white paper After the reload, both devices come back online as StackWise Virtual Pair. The conversion is a one-time process that requires a few simple configuration steps and a system reload. Simplified management of a single configuration and fewer operational failure pointsįigure 2 graphically represents the benefits of transitioning from traditional architecture to StackWise Virtual Architecture.Ī StackWise Virtual domain is created by converting two standalone Cisco Catalyst 9000 switches to a single logical network entity.Reduced configuration errors and elimination of First Hop Redundancy Protocols (FHRP), such as Hot Standby Routing Protocol (HSRP), GLBP and VRRP.Better return on existing investments via increased bandwidth from access layer.Non-stop business communication through the use of a redundant chassis with SSO-enabled supervisors.
This virtualization of the two-physical switches into single logical switch fundamentally alters the design of campus topology. This paper explains the Cisco StackWise Virtual technology, including its benefits and requirements.Ĭisco Catalyst 9000 platform StackWise Virtual: An overview StackWise Virtual physical to logical representation
0 kommentar(er)
