OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Recommendations

Info

Configuring Virtual Chassis Configuring Virtual Chassis Configuring Virtual Chassis This section describes commands to configure virtual chassis on an OmniSwitch. • “Virtual Chassis Configuration Guidelines” on page 13-18 • “Configuring the Chassis Identifier” on page 13-20 • “Configuring the Virtual Chassis Group Identifier” on page 13-20 • “Configuring the Hello Interval” on page 13-20 • “Configuring the Hello Interval” on page 13-20 • “Configuring the Control VLAN” on page 13-21 • “Configuring Virtual Chassis EMP IP Addresses” on page 13-21 Note. See “Quick Steps for Automatically Configuring A Virtual Chassis” on page 13-5” for a brief tutorial on configuring these parameters on an OmniSwitch. Virtual Chassis Configuration Guidelines The following sections provide configuration guidelines to follow when configuring a virtual chassis on an OmniSwitch. The configuration commands related to the virtual chassis functionality are used for manually configuring the virtual chassis options. Many of these configuration options can be automatically configured by the AOS software by incorporating switches into the virtual chassis without a vcsetup.cfg file. General • One of the chassis will become the Master chassis while the remaining switches will become Slaves. • Some of the virtual chassis parameters runtime modification only take effect after the next reboot of the switch. These parameters are chassis identifier, chassis priority, control VLAN and hello interval. For this type of parameters, the following terminology is used. • Operational values - The current or running values, are those in effect at the present time. • Configured values - The next or future values are those that are currently configured or set, but that are not in effect at the present time. These values will only become effective after the next reboot of the switch. Chassis Identifier • Each chassis requires a chassis identifier that is unique within the virtual chassis group of topology. A chassis identifier can be automatically or manually configured. • If a duplicate chassis identifier is detected within the virtual chassis group then the chassis role will be reported as inconsistent and the chassis status will be Duplicate-Chassis. The front-panel ports will not be operational and the configuration must be corrected by accessing the switch directly through the local EMP port or a console connection. • The chassis identifier is used to generate globally unique values for the module identifiers as well as allowing inter-chassis communication. page 13-18 OmniSwitch AOS Release 8 Switch Management Guide May 2014
Configuring Virtual Chassis Configuring Virtual Chassis • A chassis reboot is required for a newly configured chassis identifier to take effect. For information about configuring the Chassis ID, see “Configuring the Chassis Identifier” on page 13-20 Virtual Chassis Group Identifier • Each chassis also requires a virtual chassis group identifier to identify the chassis belonging to that specific virtual chassis topology. • The same group identifier must be assigned to each chassis in the virtual chassis topology. Switches belonging to other virtual chassis groups should use a different group identifier. • If two or more chassis within the same virtual chassis group do not have the same group identifier configured, the chassis role will be reported as Inconsistent and the chassis status will be Mismatch- Chassis-Group. The front-panel user ports will not be brought to an operational state. The configuration must be corrected by accessing the chassis directly. • If two or more separate virtual chassis groups use the same group identifier, this inconsistency is not detected or corrected by the virtual chassis functionality. It is up to the administrator to ensure that each domain uses a unique group identifier. • The virtual chassis group identifier is used to select a globally unique virtual MAC address for each virtual chassis group to avoid duplicate MAC addresses in a network that may contain more than one virtual chassis group. For information about configuring the chassis group identifier, see “Configuring the Virtual Chassis Group Identifier” on page 13-20. Virtual Fabric Link (VFL) • An operational VFL is a basic requirement to support a fully functional virtual chassis. OmniSwitch 6860/6860E have dedicated VFL ports. • Explicitly configuring the VFL and the physical port members is not supported, this function is automatically configured and is not user-configurable. The lowest numbered VFL port is VFL 0 and the highest numbered VFL port is VFL 1. • It is recommended to connect the chassis using the VFL ports prior to booting the switch. • Only the dedicated VFL ports can be members of a VFL. • With a Virtual Chassis consisting of two chassis, the VFL ports are bundled to form a single link aggregate VFL 0. • For increased resiliency and to help avoid a split chassis scenario it is strongly recommend to have the VFL ports connected in a ring topology. • The VFL automatically becomes a member of all VLANs configured on the chassis. For more information on Virtual Fabric Link, see “Configuring the Hello Interval” on page 13-20 Control VLAN • The control VLAN is a reserved VLAN used for transporting control packets among the chassis comprising the virtual chassis. • Runtime configuration changes to the control VLAN will only take effect after the next reboot of the chassis. OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 13-19
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:
Page 181 and 182:
11 Configuring Network Time Protoco
Page 183 and 184:
Configuring Network Time Protocol (
Page 185 and 186: 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 and 230: Configuring Virtual Chassis Managin
Page 235: Configuring Virtual Chassis Interac
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 287 and 288:
SNMP Traps Table No. Trap Name Obje
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?