Alcatel Unleashed

Hi @ all

I have two questions:

1) Best practice or easiest way to change the chassis-id of a virtual chassis member?
2) With microcode 7.3.4 is theire a way to convert chassis from virtual chassis mode to standalone mode.
(For the other way - standalone to vc mode - are a lot of instructions available.

Best regards


I tried the following to change the chassis id

show microcode
/flash/certified
Package Release Size Description
-----------------+-------------------------+--------+-----------------------------------
Tos.img 7.3.4.248.R02 211794508 Alcatel-Lucent OS

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 N/A OS6900 11 10 4094 4094 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 Down N/A 2 0 1 Unassigned


show virtual-chassis vf-link member-port
VFLink mode: Static

Chassis/VFLink ID Chassis/Slot/Port Oper Is Primary
-------------------+------------------+----------+-------------
1/0 1/2/1 Down No
1/0 1/2/2 Down No


show configuration vcm-snapshot chassis-id 1
! Virtual Chassis Manager:
virtual-chassis chassis-id 1 configured-chassis-id 1
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 11
virtual-chassis chassis-id 1 configured-chassis-priority 200

! IP:
ip interface local chassis-id 1 emp address 10.214.6.111 mask 255.255.255.0


virtual-chassis chassis-id 1 configured-chassis-id 2
ERROR: Cannot change the chassis identifier while virtual-fabric links are configured (@1336)

no virtual-chassis chassis-id 1 vf-link 0
ERROR: Cannot delete a virtual-fabric link that has member ports configured (@2786)

Hello

If you want to move from ID 1 to ID 2

Edit with vi vcsetup.cfg file

Exemple of file you need to have
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 ## Take care to change form 2/2/1 to 2/2/1
virtual-chassis chassis-id 2 vf-link 0 member-port 2/2/2 ## Same chassis id will change and need to find new port reference
virtual-chassis chassis-id 2 chassis-group 11

! IP:
ip interface local chassis-id 2 emp address 1.2.2.2 mask 255.255.255.0

Save via vi

reboot the switch.

Group value can be changed online but for chassis id this is my method.

regards

Cedric

My method to move form VC to standalone

-> remove vcsetup.cfg and vcboot.cfg
-> reboot

When I m working in a network where i have vc and no vc , I configure all switches with vcsetup.cfg file
If there is only one member ( same as standalone) I dont configure vf-link.

I do this to have same interface format on all switches x/y/z and not a mix of x/y/z and x/y for real standalone switch.

Cedric

many thanks for your fast response.

I know the methode of editing the vc_setup.cfg. But I thought there would be an more smart way to change the chassis id

dpmp wrote:many thanks for your fast response.

I know the method of editing the vc_setup.cfg. But I thought there would be an more smart way to change the chassis id

I remember that I tried both methods: Editing vc_setup.cfg and CLI and I think there should be the "smart way" too:

If you want to convert the chassis with id 3 for example to new chassis id 6 try If you want to move back a VC chassis-member (f.e. chassis id 3) to standalone I guess you could set configured chassis-id to zero But wether you edit vc_setup.cfg or use the commands - you have to reboot the chassis you want to change: Please be careful, I didn't actually checked this.

PS: If anyone is asking why it could be a better idea to use cli than simply editing the vc_setup.cfg instead: It's a bit more secure then trusting, that you don't make a typo or remove the wrong vc_setup.cfg