29.04.2019 Views

OS6860(E)_AOS_8.1.1.R01_Switch_Management_Guide

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuring Virtual Chassis<br />

Virtual Chassis Overview<br />

Slave Chassis - Any chassis which is not the Master chassis is considered a Slave chassis. A Slave chassis<br />

is not directly configured, it communicates with the Master chassis through the virtual-fabric links to<br />

determine its configuration. The VC LED will be amber.<br />

Virtual Chassis EMP Address - The Virtual Chassis management IP address (EMP-VC). This is a<br />

configurable IP address that is automatically assigned to the current primary chassis management module<br />

(CMM) of the master chassis. This parameter is stored in the vcboot.cfg configuration file.<br />

Chassis EMP Address - The local chassis management IP address (EMP-CHAS1). This is a configurable<br />

IP address that is automatically assigned to the primary chassis management module (CMM) of the local<br />

chassis regardless of its master or slave role. This parameter is stored in the chassis specific vcsetup.cfg<br />

configuration file.<br />

Virtual Fabric Link (VFL) - Dedicated ports that connect the chassis participating in the Virtual Chassis.<br />

As one of the basic building blocks of a Virtual Chassis configuration, the VFL facilitates the flow of<br />

traffic and the transfer of control data between the Master and Slave chassis.<br />

Control VLAN - A special type of VLAN reserved for the inter-chassis communication exchange<br />

between the switches participating in a Virtual Chassis. Only VFL ports are assigned to this VLAN, and<br />

no other ports are allowed to join the Control VLAN.<br />

IS-IS VC - Proprietary protocol for managing a Virtual Chassis topology. This protocol has no interaction<br />

with IS-IS routing or IS-IS SPB protocols. Responsible for information exchange with peers over the<br />

VFL, determining adjacencies, loop-detection and the shortest path between members of the VC.<br />

VCSP - Virtual Chassis Split Protection. A proprietary protocol used by VC to detect and protect against<br />

network disruption when a VC splits.<br />

vcsetup.cfg - A file containing information pertaining to the current physical switches, helping incorporate<br />

it into a virtual chassis. This file contains information such as Chassis ID, Group ID, Chassis priority,<br />

control VLAN, and chassis EMP IP addresses.<br />

vcboot.cfg - A file containing information pertaining to the virtual chassis as a whole including L2 and L3<br />

configuration, management configuration, user ports configuration, etc.<br />

Virtual Chassis - Boot-Up<br />

The Master chassis contains the vcboot.cfg file that contains the configuration for the entire virtual chassis.<br />

All the switches (i.e. the one that will eventually become the Master and the ones that will become<br />

Slaves) contain a vcsetup.cfg file that allows them to establish an connection over a VFL to all the other<br />

neighboring chassis.<br />

1 Upon boot-up, a switch will read its local vcsetup.cfg file and attempt to connect to the other neighbor<br />

switches.<br />

2 Upon connection, the switches will exchange the parameters configured in their local vcsetup.cfg files.<br />

3 As a result of this exchange, they will discover the topology, elect a Master based on criteria described<br />

in the next section, start periodic health checks over the VFL and synchronize their configuration as<br />

defined within the vcboot.cfg configuration file.<br />

4 All Slaves, if they do not have a local copy of vcboot.cfg, or their local copy does not match the copy<br />

found on the Master, will download their complete vcboot.cfg from the Master chassis and reboot using<br />

this copy of vcboot.cfg as its configuration file.<br />

Omni<strong>Switch</strong> <strong>AOS</strong> Release 8 <strong>Switch</strong> <strong>Management</strong> <strong>Guide</strong> May 2014 page 13-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!