Backbone Switch Redundancy - Virtual-Chassis (VC)

In this session, we will learn about Virtual-Chassis (VC), which is often used for backbone switch redundancy. Let's look at what VC is, its strengths, its weaknesses, its principles of motion, and so on.

 

 

1. What is Virtual-Chassis (VC)?

 

 

: There are a lot of people who are unfamiliar with VC, right? It's not a technology that came out completely recently, but it's a technology that's actually set up and used a lot on the site recently.

 

Backbone switch redundancy used to be an active-standby structure using VRRP and HSRP. However, VC is an active-active structure.

 

Let's take a look at VC.

 

 

: This is called virtualization technology, which allows multiple physical switches to act as single logical switches that can be managed with Single IP Addresses.

 

To put it more simply, it's a technology that makes two physical backbone switches one logical switch. Two physically, but one logically. It looks like it's active-active because the switch is doing it.

 

 

I think you can understand it similar to the stacking technology that was used a lot in the past.

 

 

 

 

2. VC Advantages and Disadvantages

 

: VC doesn't only have good things, right? Let's look at the pros and cons.

 

 

※ VC(Virutal Chassis) advantage

 

- Act as Active-Active

 

- VC Single Chassis single bridge and router

 

- Not the most problematic loop structure for backbone switch redundancy

 

- Fast, simple design configuration between Core and Edge Switches without the need for spanning tree and VRRP

 

- Simplify your network to improve performance, prevent failures, and provide fast recovery

 

- Twice the network performance (because two cars are used as one)

 

- The lower equipment is configured via LACP.

 

 

※ VC(Virutal Chassis) Weakness

 

- Configurations not yet heavily used by the site

 

- Requires separate Software License (vendor to equipment may vary)

 

- Unknown on stable screen because there are not many references

 

 

 

 

3. Principle of VC operation

 

Let's look at the Alcatel Switch Config standard. If you reboot after setting up the VC on each switch A and B, it will logically act as one switch. The setting is simple.

 

 

Part 1: Configure the switches

 

Chassis A-> virtual-chassis configured-chassis-id 1

Chassis A-> virtual-chassis vf-link 0 create

Chassis A-> virtual-chassis vf-link 0 member-port 1/1

Chassis A-> virtual-chassis configured-chassis-priority 200

Chassis A-> write-memory

Chassis A-> convert-configuration to vc_dir

 

 

Chassis B-> virtual-chassis configured-chassis-id 2

Chassis B-> virtual-chassis vf-link 0 create

Chassis B-> virtual-chassis vf-link 0 member-port 1/1

Chassis B-> write-memory

Chassis B-> convert-configuration to vc_dir

 

Part 2: Reboot the switches

 

Chassis A-> reload from vc_test no rollback-timeout

Chassis B-> reload from vc_test no rollback-timeout

 

 

 

저의 글을 읽어 주셔서 감사합니다. 오늘도 즐거운 하루 보내세요.