OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

Recommendations

Info

Configuring Virtual Chassis Configuring Virtual Chassis • The control VLAN must be the same between the chassis comprising the virtual chassis. For more information on the Control VLAN, see “Configuring the Control VLAN” on page 13-21 Configuring the Chassis Identifier To configure the Virtual Chassis feature, a unique chassis identifier must first be automatically or manually assigned to each of the switches that will form the Virtual Chassis group. Assigning the chassis identifier also enables the configuration of the additional virtual chassis parameters for the chassis. The virtual-chassis configured-chassis-id command is used to configure a unique chassis identifier for a switch within the virtual chassis group. For example: -> virtual-chassis chassis-id 1 configured-chassis-id 2 Note: Changing the chassis-id will not cause the Control VLAN or Group ID to change. These parameters must also be manually changed if required. Duplicate chassis identifier In the event two chassis have the same operational chassis identifier value, one of them will be reported as Inconsistent role (instead of Master or Slave) and Duplicate-Chassis status. This will cause the operational chassis identifier of one of the chassis to be automatically renumbered to follow the duplicate chassis ID format. (i.e. 101). This numbering is reserved to represent a chassis whose chassis identifier is duplicate. All management interface commands must use this new operational chassis identifier to affect any configuration. The duplicate chassis identifier must be corrected by re-configuring the switch locally through the console or EMP port access. For example: -> virtual-chassis chassis-id 101 configured-chassis-id 2 Configuring the Virtual Chassis Group Identifier A virtual chassis group identifier must be assigned to each of the switches that will form the Virtual Chassis group. Each of these switches must use the same group identifier, which identifies the switch as belonging to that virtual chassis group. The virtual-chassis chassis-group command is used to configure the same group identifier for each chassis within the virtual chassis group. For example: -> virtual-chassis chassis-group 1 By default, the virtual chassis group identifier is set to “0”. In a network environment where more than one virtual chassis group may exist, configure each virtual chassis group with its own unique group identifier. Duplicate group identifiers are not supported. Configuring the Hello Interval Hello packets are used for establishing and maintaining the neighbor relationship between virtual chassis switches and ensures that communication between switches is bidirectional. Hello packets are sent periodically out VFL interfaces. Bidirectional communication is indicated when the switch sees itself listed in the neighbor's hello packet. The hello interval value determines how often these packets are sent. To configure the hello interval between the multi-chassis peers, use the virtual-chassis hello-interval command as shown below: page 13-20 OmniSwitch AOS Release 8 Switch Management Guide May 2014
Configuring Virtual Chassis Configuring Virtual Chassis -> virtual-chassis hello-interval 10 Configuring the Control VLAN Under normal circumstances, it is not necessary to change the control VLAN. However, it is important to note that the VLAN configured as the Control VLAN is reserved specifically for transferring virtual chassis control information purposes and it can no longer be used for normal data traffic. If necessary, use the virtual-chassis configured-control-vlan command to modify the Control VLAN. For example: -> virtual-chassis configured-control-vlan 4093 Configuring Virtual Chassis EMP IP Addresses In order to access the virtual chassis through the EMP IP addresses the port's IP address and network mask can be configured. There are multiple IP addresses to consider when configuring the EMP IP addresses in a virtual chassis environment. • The Virtual Chassis EMP IP address represents the address of the entire virtual chassis (EMP-VC). This address is automatically assigned to the Master chassis and can be used for remote access to the entire Virtual Chassis. • The Chassis EMP IP address is assigned to each switch comprising the virtual chassis (i.e. EMP- CHAS1, EMP-CHAS2, EMP-CHAS3, etc.). This address can be used for remote access to each switch comprising the virtual chassis. This address is automatically assigned to the local chassis. • All the EMP IP addresses and CMM’s IP addresses must be in the same subnet. • Each of the IP addresses must be unique. Note: The Virtual Chassis EMP addresses are only supported on OS680E models (non-E models do not have an EMP port). When configuring VC EMP addresses in a VC with a mix of OS6860E models and OS6860-non-E models the VC could become unreachable via the EMP port if a non-E model becomes Master. In a mixed VC environment it's recommended to create a management VLAN for remote management purposes. Configuring the Chassis EMP IP Address Use the ip interface command to modify the Chassis EMP IP address as shown below. These commands would be issued after the virtual chassis is operational: -> ip interface local chassis-id 1 emp address 10.255.100.1 mask 255.255.255.0 -> ip interface local chassis-id 2 emp address 10.255.100.2 mask 255.255.255.0 Configuring the Virtual Chassis EMP IP Address Use the ip interface command to modify the Virtual Chassis EMP IP address as shown below. These commands would be issued after the virtual chassis is operational: -> ip interface master emp address 10.255.100.100 mask 255.255.255.0 OmniSwitch AOS Release 8 Switch Management Guide May 2014 page 13-21
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 187 and 188: 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 and 236: Configuring Virtual Chassis Interac
Page 237: 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 289 and 290:
SNMP Traps Table No. Trap Name Obje
Page 291 and 292:
SNMP Traps Table No. Trap Name Obje
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?