Deploying Cisco Catalyst 3850 Switch Stackwise-480 Nsf And Sso - Cisco Catalyst 3850 Deployment Manual

Hide thumbs Also See for Catalyst 3850:
Table of Contents

Advertisement

In the initial software release, the Cisco Catalyst 3850 Switch supports CAPWAP tunnels and Dynamic Transport
Layer Security (DTLS), but not high availability for wireless clients. During a switchover, the new active WCM
flushes the last-known wireless client and rebuilds the database and forwarding tables. As a result, the wireless
client must restart communication with new wireless controller, using the same initial steps (such as 802.1X
authentication, Dynamic Host Configuration Protocol [DHCP] request, and so on) to reconnect to the network.

Deploying Cisco Catalyst 3850 Switch StackWise-480 NSF and SSO

To maximize availability, the SSO capability is enabled by default when Cisco Catalyst 3850 Switches are
deployed in Cisco StackWise-480 mode. No user configuration is required to enable SSO capability on a Cisco
Catalyst 3850 Switch stack. You can verify that SSO is configured and operational by using the show redundancy
state command. This is sample output showing SSO redundancy in a Cisco StackWise-480-based network design:
Switch# show redundancy state
Redundancy Mode (Operational) = SSO
Redundancy Mode (Configured) = SSO
Communications = Up
In stacking mode, the Cisco Catalyst 3850 active switch automatically performs SSO protocol synchronization with
the standby switch. By default, the nonstop forwarding (NSF) subsystem in all the switches in a Cisco Catalyst
3850 Switch stack operates in NSF helper mode and supports nonstop data forwarding and graceful recovery
during active to standby (Layer 3) switchover. Implementing NSF capability allows the remaining Cisco Catalyst
3850 Switches in the stack to continue forwarding data while the new active switch gracefully recovers the protocol
state machines. To enable the graceful restart capability for supported protocols, you must manually enable
graceful-restart capability under a routing instance. This sample configuration shows how to enable NSF capability
for Enhanced Interior Gateway Routing Protocol (EIGRP):
Switch(config)# ip routing
Switch (config)# router eigrp 100
Switch (config-router)# nsf
Switch # show ip protocols
*** IP Routing is NSF aware ***
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
my state = 13
-ACTIVE
peer state =
8
-STANDBY HOT
Mode = Duplex
Unit ID = 4
Redundancy State = SSO
Manual Swact = enabled
client count = 91
client_notification_TMR = 360000 milliseconds
keep_alive TMR = 9000 milliseconds
keep_alive count = 0
keep_alive threshold = 9
RF debug mask = 0
Page 31 of 36

Advertisement

Table of Contents
loading

Table of Contents