Hello,
I want just a sample config to give me an idea on how to configure it.
I have also a question, is the multi-chassis config can help me to have one config on two switches synchronized like in a stack mode for small switches ?
OS9702 Multi-Chassis Configuration
Re: OS9702 Multi-Chassis Configuration
No not as a stack.
Multi-chassis is two seperate switches and therefore two seperate configs.
Also (at least on 6900) you had to add system IDs to multi-chassis linkaggs (and the ports) which is not the way (you/I) do it normaly.
there are plenty of examples in the NT Guide.
Short:
Create chassis-id and VF-links on both chassis
Chassis 1 -> multi-chassis chassis-id 1
Chassis 2 -> multi-chassis chassis-id 2
Configure a globally unique chassis group identifier for the multi-chassis domain (if you have multiple MC-Pairs.. defines virtual MAC)
Chassis 1-> multi-chassis chassis-group 10
Chassis 2-> multi-chassis chassis-group 10
Create a virtual fabric link between chassis peers using the multi-chassis vf-link must be 10G in 6900 not sure whether this is the same on 970XE (probably) add the physical ports as members:
Chassis 1-> multi-chassis vf-link create
Chassis 2-> multi-chassis vf-link create
Chassis 1-> multi-chassis vf-link member-port 1/1
Chassis 1-> multi-chassis vf-link member-port 3/1
Chassis 2-> multi-chassis vf-link member-port 1/1
Chassis 2-> multi-chassis vf-link member-port 3/1
Create ranges for LACP/MC-LAGs (must match, but local is mirrored)
Chassis1:-> linkagg range local 0-9 peer 10-19 multi-chassis 20-127
Chassis2:-> linkagg range local 10-19 peer 0-9 multi-chassis 20-127
You probably need to reload here.
write memory flash-synchro
reload wroking no rollback-timeout
For VIP VLANs (see as has shared IP in MC-LAG - similar VRRP) use:
both chassis:
multi-chassis vip-vlan 10
Chassis1:-> ip interface vip-vlan-10 vip-address 10.10.10.100 address 10.10.10.1 vlan 10
Chassis2:-> ip interface vip-vlan-10 vip-address 10.10.10.100 address 10.10.10.2 vlan 10
Creating multi-chassis linkagg:
Both Chassiss
-> linkagg lacp agg 96 size 2 admin-state enable multi-chassis active
-> linkagg lacp agg 96 actor system-id 00:00:00:00:00:01
-> linkagg lacp port 2/1 actor admin-key 1
-> linkagg lacp port 2/1 actor system-id 00:00:00:00:00:01
-> vlan 10 members linkagg 1 untagged
on edge its a normal LACP
-> linkagg lacp agg 96 size 2 admin-state enable
-> linkagg lacp port 1/1-2 actor admin-key 1
-> vlan 10 members linkagg 1 untagged
I had some strange experiences with MC-LAG on 6900, so keep an eye on that.
Also be aware of the constraints (e.g. no link between two MC-LAG-Edges can exist, as multi-chassis loopback-detection will shutdown in that case.)
If a loop occured:
clear multi-chassis loopback-detection
to clear a detected loop info, then shutdown and reenable the ports, that got blocked
e.g. (interface 1/17 admin down int 1/17 admin up)
Multi-chassis is two seperate switches and therefore two seperate configs.
Also (at least on 6900) you had to add system IDs to multi-chassis linkaggs (and the ports) which is not the way (you/I) do it normaly.
there are plenty of examples in the NT Guide.
Short:
Create chassis-id and VF-links on both chassis
Chassis 1 -> multi-chassis chassis-id 1
Chassis 2 -> multi-chassis chassis-id 2
Configure a globally unique chassis group identifier for the multi-chassis domain (if you have multiple MC-Pairs.. defines virtual MAC)
Chassis 1-> multi-chassis chassis-group 10
Chassis 2-> multi-chassis chassis-group 10
Create a virtual fabric link between chassis peers using the multi-chassis vf-link must be 10G in 6900 not sure whether this is the same on 970XE (probably) add the physical ports as members:
Chassis 1-> multi-chassis vf-link create
Chassis 2-> multi-chassis vf-link create
Chassis 1-> multi-chassis vf-link member-port 1/1
Chassis 1-> multi-chassis vf-link member-port 3/1
Chassis 2-> multi-chassis vf-link member-port 1/1
Chassis 2-> multi-chassis vf-link member-port 3/1
Create ranges for LACP/MC-LAGs (must match, but local is mirrored)
Chassis1:-> linkagg range local 0-9 peer 10-19 multi-chassis 20-127
Chassis2:-> linkagg range local 10-19 peer 0-9 multi-chassis 20-127
You probably need to reload here.
write memory flash-synchro
reload wroking no rollback-timeout
For VIP VLANs (see as has shared IP in MC-LAG - similar VRRP) use:
both chassis:
multi-chassis vip-vlan 10
Chassis1:-> ip interface vip-vlan-10 vip-address 10.10.10.100 address 10.10.10.1 vlan 10
Chassis2:-> ip interface vip-vlan-10 vip-address 10.10.10.100 address 10.10.10.2 vlan 10
Creating multi-chassis linkagg:
Both Chassiss
-> linkagg lacp agg 96 size 2 admin-state enable multi-chassis active
-> linkagg lacp agg 96 actor system-id 00:00:00:00:00:01
-> linkagg lacp port 2/1 actor admin-key 1
-> linkagg lacp port 2/1 actor system-id 00:00:00:00:00:01
-> vlan 10 members linkagg 1 untagged
on edge its a normal LACP
-> linkagg lacp agg 96 size 2 admin-state enable
-> linkagg lacp port 1/1-2 actor admin-key 1
-> vlan 10 members linkagg 1 untagged
I had some strange experiences with MC-LAG on 6900, so keep an eye on that.
Also be aware of the constraints (e.g. no link between two MC-LAG-Edges can exist, as multi-chassis loopback-detection will shutdown in that case.)
If a loop occured:
clear multi-chassis loopback-detection
to clear a detected loop info, then shutdown and reenable the ports, that got blocked
e.g. (interface 1/17 admin down int 1/17 admin up)
Re: OS9702 Multi-Chassis Configuration
Hi devnull,
can you share me the topology used...
I also want to implement MC-lag in my switches ...but getting confused with the commands...
It will be great help if you can share any document for configuring MC-lag
can you share me the topology used...
I also want to implement MC-lag in my switches ...but getting confused with the commands...
It will be great help if you can share any document for configuring MC-lag
Re: OS9702 Multi-Chassis Configuration
Read the documentation!
VC is the way to roll now i have no 9700 active anymore
VC is the way to roll now i have no 9700 active anymore