OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Recommendations

Info

Virtual Chassis Split Protection (VCSP) Configuring Virtual Chassis Virtual Chassis Split Protection (VCSP) In the case of a VC split due to a VFL link failure or the failure of one of the VC elements, both of the resulting VCs could end up having the same system MAC and IP addresses. Since there is no communication between these individual VCs due to the VFL link failure they end up communicating with the rest of the network devices using the same MAC and IP addresses. This split scenario is disruptive to the network as the conflicting MAC and IP addresses can lead to layer 2 loops and L3 traffic disruption. VCSP provides the following benefits: • Avoid network disruptions by preventing duplicate MAC and IP addresses on the network when MAC retention is enabled and a VC split occurs. • The sub-VC that forms out of the split is able to detect that a split has occurred. • Once the VC split condition has been determined, the sub-VC will put its front-panel ports into an operationally down state preventing traffic forwarding and avoiding loops and possible traffic disruption. The VCSP link aggregate ports will remain up. • A trap can be sent by the active-VC indicating the split state. The trap indicates that the split has occurred and which elements are in the operationally down sub-VC. • A mechanism is available to recover the non-operational sub-VC. • A method of detecting a VC split in a remote VC topology where the VC may consist of elements located in different physical locations such as a remote site, or multiple floors of a building. VCSP Key Components and Terms • VCSP PDU - A proprietary packet forwarded between VC elements to help determine that state of the VC. • VCSP Helper - A neighboring OmniSwitch, not an element of the VC, responsible for forwarding VCSP PDUs between the VC elements. The VCSP feature and the VCSP Helper functionality cannot be enabled on the same switch. The VCSP helper and the VC cannot have the same Group ID. • VCSP Link Aggregate - A dedicated link aggregate configured between all elements of a VC and a helper switch to be used for forwarding VCSP PDUs. • Active-VC - An element, or multiple elements, that results when a VC split occurs. The active-VC will keep its front panel ports enabled and continue to forward traffic on the network. • Sub-VC - An element, or multiple elements, that results when a VC split occurs. The sub-VC will disable its front panel ports to prevent traffic disruption caused by duplicate MAC/IP addresses with the active VC. • Protection State - A state an element will transition to after determining a VC split has occurred. Its ports will be operationally disabled to prevent duplicate MAC and IP addresses and network disruption. • Guard Timer - A configurable timer determining how long a unit will wait before beginning to send VCSP PDUs after a VC recovery. page 13-12 OmniSwitch AOS Release 8 Switch Management Guide May 2014
Configuring Virtual Chassis Virtual Chassis Split Protection (VCSP) Basic Operation When VCSP is enabled, a proprietary protocol runs on a configured link aggregate to carry the VC information necessary for VC split detection. Each of the VC elements share a link aggregate with an OmniSwitch that can act as a helper to assist in the VC split detection. The lowest member port of the link aggregate hosted on the master element is responsible for sending the VCSP PDUs on the member link. When the packet arrives on the remote helper device then the helper device will forward the packet out on all member ports of the link aggregate so that the packet reaches the remote VC elements. Use the the virtual-chassis split-protection admin-state and virtual-chassis split-protection linkaggid commands to enable VCSP and create the VCSP link aggregate on the VC. Use the the virtual-chassis split-protection helper admin-state and virtual-chassis split-protection helper linkagg commands to enable the VCSP helper and create the VCSP helper link aggregate on the helper switch. Protection States Under normal VC circumstances the VCSP PDUs are sent once every 3 seconds. When the VC detects a scenario which leads to a change in its size the protocol sends the VCSP PDUs at a rate of 1 per 50 milliseconds for 3 to 10 seconds. This helps to quickly identify a VC split. On reception of a VCSP frame, the receiving elements match the master of their current VC against the MAC address of the VCSP sender. If there is a mismatch between the two, then that indicates the presence of an active VC in the network which is disconnected from the current VC. In this condition the VC element will monitor 3-5 such consecutive frames, after which it will transition to the protection state. When an element transitions to the protection state, the following occurs: • Each of the VC elements will independently transition into the protection state. • In the protection state each of the VC elements will disable all the user ports except the ones belonging to the VCSP protection link aggregate. • The VC element will store the protection state transition information in a non-volatile location. This information will be used whenever an element in the protection state re-boots and needs to check its current operational state. • An element in the protection state will send a VCSP PDU back on the link aggregate carrying the VCSP state as PROTECTION. This is the only frame that is sent by the protection sub-VC. The purpose of this message is to inform the active-VC to generate an SNMP trap regarding the VC split state of the VC element. VC Split Recovery Once a sub-VC goes into the protection state then all the front panel ports are put into an operationally down state. There are two ways to recover the VC, manually or automatically. Manual Recovery If the guard timer is 0, automatic recovery is disabled and the sub-VC stays in protection mode until the unit is reloaded by the administrator. After the re-boot the administrator has to manually recover the switch by first disabling VCSP and then re-enabling VCSP. This clears the protection state variables stored on the switch. OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 13-13
Page 1 and 2:
Part No. 060391-10, Rev. A May 2014
Page 3 and 4:
Contents About This Guide .........
Page 5 and 6:
Contents Using the Switch as an FTP
Page 7 and 8:
Contents Account and Password Polic
Page 9 and 10:
Contents Authentication Trap ......
Page 11 and 12:
Contents Firmware Upgrade Files ...
Page 13 and 14:
About This Guide This OmniSwitch AO
Page 15 and 16:
About This Guide Documentation Road
Page 17 and 18:
About This Guide Related Documentat
Page 19 and 20:
1 Logging Into the Switch Logging i
Page 21 and 22:
Logging Into the Switch Quick Steps
Page 23 and 24:
Logging Into the Switch Overview of
Page 25 and 26:
Logging Into the Switch Accessing t
Page 27 and 28:
Logging Into the Switch Setting the
Page 29 and 30:
Logging Into the Switch Using Secur
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Logging Into the Switch Modifying t
Page 37 and 38:
Logging Into the Switch Enabling th
Page 39 and 40:
Logging Into the Switch Enabling th
Page 41 and 42:
2 Managing System Files This chapte
Page 43 and 44:
Managing System Files Switch Admini
Page 45 and 46:
Managing System Files File and Dire
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Managing System Files Loading Softw
Page 55 and 56:
Managing System Files Loading Softw
Page 57 and 58:
Managing System Files Setting the S
Page 59 and 60:
Managing System Files Setting the S
Page 61 and 62:
3 Managing CMM Directory Content Th
Page 63 and 64:
Managing CMM Directory Content CMM
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Managing CMM Directory Content Mana
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Managing CMM Directory Content Usin
Page 77 and 78:
4 Using the CLI Alcatel-Lucent’s
Page 79 and 80:
Using the CLI Command Entry Rules a
Page 81 and 82:
Using the CLI Command Help -> sh vl
Page 83 and 84:
Using the CLI Logging CLI Commands
Page 85 and 86:
Using the CLI Customizing the Scree
Page 87 and 88:
5 Working With Configuration Files
Page 89 and 90:
Working With Configuration Files Tu
Page 91 and 92:
Working With Configuration Files Qu
Page 93 and 94:
Working With Configuration Files Co
Page 95 and 96:
Working With Configuration Files Cr
Page 97 and 98:
Working With Configuration Files Cr
Page 99 and 100:
6 Managing Switch User Accounts Swi
Page 101 and 102:
Managing Switch User Accounts User
Page 103 and 104:
Managing Switch User Accounts Overv
Page 105 and 106:
Managing Switch User Accounts Overv
Page 107 and 108:
Managing Switch User Accounts Creat
Page 109 and 110:
Managing Switch User Accounts Confi
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Managing Switch User Accounts Setti
Page 117 and 118:
Managing Switch User Accounts Multi
Page 119 and 120:
7 Managing Switch Security Switch s
Page 121 and 122:
Managing Switch Security Switch Sec
Page 123 and 124:
Managing Switch Security Authentica
Page 125 and 126:
Managing Switch Security Quick Step
Page 127 and 128:
Managing Switch Security Setting Up
Page 129 and 130:
Managing Switch Security Configurin
Page 131 and 132:
8 Using WebView The switch can be m
Page 133 and 134:
Using WebView WebView CLI Commands
Page 135 and 136:
Using WebView WebView Overview Conf
Page 137 and 138:
9 Using SNMP The Simple Network Man
Page 139 and 140:
Using SNMP Quick Steps for Setting
Page 141 and 142:
Using SNMP Quick Steps for Setting
Page 143 and 144:
Using SNMP SNMP Overview Using SNMP
Page 145 and 146:
Using SNMP Using SNMP For Switch Se
Page 147 and 148:
Using SNMP Using SNMP For Switch Se
Page 149 and 150:
Using SNMP Working with SNMP Traps
Page 151 and 152:
Using SNMP Verifying the SNMP Confi
Page 153 and 154:
10 Web Services, CLI Scripting, and
Page 155 and 156:
Web Services, CLI Scripting, and Op
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180: Web Services, CLI Scripting, and Op
Page 181 and 182: 11 Configuring Network Time Protoco
Page 183 and 184: Configuring Network Time Protocol (
Page 195 and 196: 12 Managing Automatic Remote Config
Page 197 and 198: Managing Automatic Remote Configura
Page 219 and 220: 13 Configuring Virtual Chassis A Vi
Page 221 and 222: Configuring Virtual Chassis Virtual
Page 223 and 224: Configuring Virtual Chassis Quick S
Page 227 and 228: Configuring Virtual Chassis Managin
Page 229: Configuring Virtual Chassis Managin
Page 235 and 236: Configuring Virtual Chassis Interac
Page 237 and 238: Configuring Virtual Chassis Configu
Page 239 and 240: Configuring Virtual Chassis Configu
Page 241 and 242: Configuring Virtual Chassis Display
Page 243 and 244: A Software License and Copyright St
Page 245 and 246: Alcatel-Lucent License Agreement Al
Page 247 and 248: B SNMP Trap Information This append
Page 249 and 250: SNMP Traps Table No. Trap Name Obje
Page 281 and 282:
SNMP Traps Table No. Trap Name Obje
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Index Symbols !! command 4-6 A aaa
Page 295 and 296:
Index Network Time Protocol see NTP
show all

OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Create successful ePaper yourself

Delete template?

Save as template?