How to configur Alcatel Virtual Chassis feature (VC) | Alcatel Switch VC Configura by CLI | Tech bot | Prashant Maurya

Configure a Virtual Chassis of two switches

OmniSwitch AOS R6/R8

How to

✓ This lab is designed to familiarize you with the Virtual Chassis feature (VC) and its configuration. 



Check that both switches have been launched on the "Working" directory

sw1 sw1 (6900-A)-> show running-directory

CONFIGURATION STATUS

Running CMM                : MASTER-PRIMARY,
CMM Mode                      : VIRTUAL-CHASSIS MONO CMM,
Current CMM Slot          : CHASSIS-1 A,
Running configuration  : WORKING,
Certify/Restore Status   : CERTIFIED

SYNCHRONIZATION STATUS

Running Configuration  : SYNCHRONIZE

sw1 (6900-B) -> show running-directory

CONFIGURATION STATUS

Running CMM               : MASTER-PRIMARY,

CMM Mode                     : VIRTUAL-CHASSIS MONO CMM,

Current CMM Slot         : CHASSIS-1 A,

Running configuration  : WORKING,

Certify/Restore Status   : CERTIFIED

SYNCHRONIZATION STATUS

Running Configuration  : SYNCHRONIZE

  • Assign a globally unique chassis identifier to the switch 6900-A and enable the switch to operate in virtual chassis mode
  • Force the 6900-A to be the master chassis, assign the highest chassis priority to it:

sw1 (6900-A)-> show virtual-chassis topology

sw1 (6900-A)-> virtual-chassis chassis-group 1

sw1 (6900-A)-> virtual chassis-id 1 configured-chassis-priority 200

sw1 (6900-A)-> show configuration vcm-snapshot chassis-id 1

sw1 (6900-A)-> write memory

sw1 (6900-A)-> reload from working no rollback-timeout

Confirm Activate (Y/N): Y

Wait the restart (close to 4 mn in lab context)

+++ VC Takeover in progress.

+++ VC Takeover complete.

Chassis Supervision: CMM has reached the ready state [L8]

Check that configuration has been taken account.

sw1 (6900-A)-> show virtual-chassis topology

Legend: Status suffix "+" means an added unit after last saved topology

Local Chassis: 1

Oper                                                       Config              Oper

Chas      Role            Status                   Chas ID             Pri      Group         MAC-Address

-----+------------+-------------------+----------------------+----------+------------+------------------------+

1     Master              Running                      1                    200         1           2c:fa:a2:05:cd:71

sw1 sw1 (6900-A)-> show configuration vcm-snapshot chassis-id 1

! Virtual Chassis Manager:

virtual-chassis chassis-id 1 configured-chassis-id 1

virtual-chassis vf-link-mode static

virtual-chassis chassis-id 1 chassis-group 1

virtual-chassis chassis-id 1 configured-chassis-priority 200

!

! PLEASE DO NOT MODIFY THE AREAS OF [SAVED INFO xxx]

! [SAVED INFO VC IDs] 1

!

! IP:

ip interface local chassis-id 1 emp address 10.4.20.1 mask 255.255.255.

Notes:

A reboot of the switch is required to update the chassis priority.

Assign a globally unique chassis identifier to the switch 6900B and enable the switch to operate in virtual

chassis

sw2 (6900-B)-> show virtual-chassis topology

sw2 (6900-B)-> virtual-chassis chassis-id 1 configured-chassis-id 2

sw2 (6900-B)-> virtual-chassis chassis-group 1

sw2 (6900-B)-> write memory

WARNING - Virtual chassis topology change detected. Chassis 1 missing!

Configuration associated with missing chassis will be erased permanently!

Confirm to continue (Y/N): y

The command write memory is protected by issuing a warning to prevent or warn purging the

configuration of the elements that are missing. Chassis id has been changed in this case.

sw2 (6900-B)-> reload from working no rollback-timeout

Confirm Activate (Y/N) : y

Wait the restart (close to 4 mn in lab context)

+++ VC Takeover in progress.

+++ VC Takeover complete.

Chassis Supervision: CMM has reached the ready state [L8]

Check that configuration has been taken account.

sw2 (6900-B)-> show configuration vcm-snapshot chassis-id 2

! Virtual Chassis Manager:

virtual-chassis chassis-id 2 configured-chassis-id 2

virtual-chassis vf-link-mode static

virtual-chassis chassis-id 2 chassis-group 1

!

! PLEASE DO NOT MODIFY THE AREAS OF [SAVED INFO xxx]

! [SAVED INFO VC IDs] 2

!

! IP:

ip interface local chassis-id 2 emp address 10.4.20.2 mask 255.255.255.0

sw2 (6900-B)-> show virtual-chassis topology

Legend: Status suffix "+" means an added unit after last saved topology

Local Chassis: 2

Oper Config Oper

Oper                                                       Config              Oper

Chas      Role            Status                   Chas ID             Pri      Group         MAC-Address

-----+------------+-------------------+----------------------+----------+------------+------------------------+

2         Master           Running                   2                   100             1             2c:fa:a2:05:cd:71

Configure member ports for the VFL:

sw1 (6900-A)-> virtual-chassis vf-link-mode static

sw1 (6900-A)-> virtual-chassis chassis-id 1 vf-link 0 create

sw1 (6900-A)-> virtual-chassis chassis-id 1 vf-link 0 member-port 1/2/1

sw1 (6900-A)-> virtual-chassis chassis-id 1 vf-link 0 member-port 1/2/2

sw1 (6900-A)-> write memory

sw1 (6900-A)-> show configuration vcm-snapshot chassis-id 1

 ! Virtual Chassis Manager:

virtual-chassis chassis-id 1 configured-chassis-id 1

virtual-chassis vf-link-mode static 

virtual-chassis chassis-id 1 vf-link 0 create

virtual-chassis chassis-id 1 vf-link 0 member-port 1/2/1

virtual-chassis chassis-id 1 vf-link 0 member-port 1/2/2

virtual-chassis chassis-id 1 chassis-group 1

virtual-chassis chassis-id 1 configured-chassis-priority 200

! ! PLEASE DO NOT MODIFY THE AREAS OF [SAVED INFO xxx]

! [SAVED INFO VC IDs] 1

! IP:

ip interface local chassis-id 1 emp address 10.4.20.1 mask 255.255.255.0

sw2 (6900-B)-> virtual-chassis vf-link-mode static

sw2 (6900-B)-> virtual-chassis chassis-id 2 vf-link 0 create

sw2 (6900-B)-> virtual-chassis chassis-id 2 vf-link 0 member-port 2/2/1

sw2 (6900-B)-> virtual-chassis chassis-id 2 vf-link 0 member-port 2/2/2

sw2 (6900-B)-> write memory

 sw2 (6900-B)-> show configuration vcm-snapshot chassis-id 2
! Virtual Chassis Manager:
virtual-chassis chassis-id 2 configured-chassis-id 2
virtual-chassis vf-link-mode static
virtual-chassis chassis-id 2 vf-link 0 create
virtual-chassis chassis-id 2 vf-link 0 member-port 2/2/1
virtual-chassis chassis-id 2 vf-link 0 member-port 2/2/2
virtual-chassis chassis-id 2 chassis-group 1
!
! PLEASE DO NOT MODIFY THE AREAS OF [SAVED INFO xxx]
! [SAVED INFO VC IDs] 2
!
! IP:
ip interface local chassis-id 2 emp address 10.4.20.2 mask 255.255.255.0

Activate the corresponding interface

 

sw1 (6900-A)-> interfaces 1/2/1-2 admin-state enable

sw1 (6900-A)-> write memory

Notes:

On the 6900-B, INTERFACE 2/2/1 and INTERFACE 2/2/2 automatically LINK UP and the switch reboots.

Once the system reboots, you should see the following messages:

Check the virtual-chassis topology:
sw1 (6900-A)-> show virtual-chassis topology
Legend: Status suffix "+" means an added unit after last saved topology
Local Chassis: 1
Oper                             Config                              Oper
Chas       Role              Status             Chas ID   Pri   Group  MAC-Address
-----+------------+-------------------+--------+-----+------+------------------
1         Master           Running                  1         200      1       2c:fa:a2:05:cd:a9

2 Slave Running+ 2 100 1 2c:fa:a2:05:cd:71It is also possible to check that all the OS6900 of the virtual chassis are in status “System Ready” with the
following command:
sw1 (6900-A)-> debug show virtual-chassis topology
Legend: Status suffix "+" means an added unit after last saved topology
Local Chassis: 1
Oper                               Config                          Oper                                                 System
Chas        Role              Status            Chas ID  Pri   Group  MAC-Address         Ready
-----+------------+-------------------+--------+-----+------+----------------------+-------
1            Master         Running                1          200      1       2c:fa:a2:05:cd:a9    Yes
2            Slave            Running+             2          100       1      2c:fa:a2:05:cd:71     Yes
Notes:
suffix “+”, if any VC element is detected as “Running” but not configuration saved
Save the configuration, synchronize flash Between CMMs and check the virtual-chassis topology 
sw1 (6900-A)-> write memory flash-synchro




Virtual Chassis Monitoring

Check the virtual-chassis topology
sw1 (6900-A)-> show virtual-chassis topology
Legend: Status suffix "+" means an added unit after last saved topology
Local Chassis: 1
Oper Config Oper
Chas Role Status Chas ID Pri Group MAC-Address
-----+------------+-------------------+--------+-----+------+------------------
1 Master Running 1 200 1 2c:fa:a2:05:cd:71
2 Slave Running 2 100 1 2c:fa:a2:05:cd:a9
Check that the System Ready is set to Yes with the command:
sw1 (6900-A)-> cat /flash/working/vcsetup.cfg
!========================================!
! File: /flash/working/vcsetup.cfg !
!========================================!
! Virtual Chassis Manager:
virtual-chassis configured-chassis-id 1
virtual-chassis vf-link-mode static
virtual-chassis vf-link 0 create
virtual-chassis vf-link 0 member-port 1/2/1
virtual-chassis vf-link 0 member-port 1/2/2
virtual-chassis chassis-group 1
virtual-chassis configured-chassis-priority 200
!! PLEASE DO NOT MODIFY THE AREAS OF [SAVED INFO xxx]
! [SAVED INFO VC IDs] 3
Display the different ports belonging to the VFL link, type:
sw1 (6900-A)-> show virtual-chassis vf-link
VFLink mode: Static
Primary Config Active Def Speed
Chassis/VFLink ID Oper Port Port Port Vlan Type
-------------------+----------+---------+-------+-------+---------+-----------
1/0 Up 1/2/2 2 2 1 10G
2/0 Up 2/2/2 2 2 1 10G
sw1 (6900-A)-> show virtual-chassis vf-link member-port
VFLink mode: Static
Chassis/VFLink ID Chassis/Slot/Port Oper Is Primary
-------------------+------------------+----------+-------------
1/0 1/2/1 Up No
1/0 1/2/2 Up Yes
2/0 2/2/1 Up No
2/0 2/2/2 Up Yes
Notes:
The “Is Primary” field defines the primary port of the virtual fabric link.
Verify the consistency of system-level mandatory parameters between the two chassis:
sw1 (6900-A)-> show virtual-chassis consistency
Legend: * - denotes mandatory consistency which will affect chassis status
licenses-info - A: Advanced; B: Data Center;
Config Oper Oper Config
Chas Chas Chas Hello Control Control
Chas* ID Status Type* Group* Interv Vlan* Vlan License*
------+------+---------+-------+------+-------+--------+--------+----------
1 1 OK OS6900 1 10 4094 4094 AB
2 2 OK OS6900 1 10 4094 4094 AB
Notes:
The two chassis in the same Virtual-Chassis group must maintain identical configuration and operational
parameters.
sw1 (6900-A)-> ssh-chassis admin@2
Executing: ssh admin@127.10.2.65
(admin@127.10.2.65) ***********************
* *
* Welcome To Rlab LAN *
* Pod 20 Switch 2 *
* 6900-B *
* *
***********************
Password: switch
Although
the prompt is the same, you are now connected to the secondary VC. Type the following:
sw1 (6900-A)-> show virtual-chassis topology
Legend: Status suffix "+" means an added unit after last saved topology
Local Chassis: 2
Oper Config Oper
Chas Role Status Chas ID Pri Group MAC-Address
-----+------------+-------------------+--------+-----+------+------------------
1 Master Running 1 200 1 2c:fa:a2:05:cd:71
2 Slave Running 2 100 1 2c:fa:a2:05:cd:a9
Look
at the Local Chassis parameter. Now it says 2, which means you are connected to the secondary VC.
log
Type
the following to return to the master VC:
sw1 sw1 (6900-A)-> logout
logout
Connection to 127.10.2.65 closed.

Comments