on my desk the switches side by side worked perfectly but after distribution to the DCs dont, if the optical transport is included.
definitely the third party have to check if the optical transport is transparent without any insertions to the interconnection.
I will see what the COLT's verdict will be. I will update
Original Message:
Sent: Feb 14, 2024 04:43 AM
From: Steinar Grande
Subject: Aruba CX 6300 VSF via 10G optic SFP up to 18KM
The issue is with your : "third party L2 transport = DWDM optical Transponder"
Clarify the interoperability options in use. it must be : non invasive,
meaning:
not interfere anything on the last experience at the transceiver end's, or anywhere else !
and make sure your fiber color (nm) is correct as agreed on with your. third party L2 transport
Follow the best practice and do the stacking manual; switch by switch locally at one site; and it will work.
(before deploying DC to DC's)
Regarding the distance and tranceiver, the Datasheet: state:
"Flexibility to create stacks that span longer distances such as hundreds of meters across campuses
to kilometres between sites using long-range 10GbE/25GbE transceivers"
Happy stacking
------------------------------
Steinar
Original Message:
Sent: Feb 13, 2024 01:54 PM
From: jdjackson@confergeone.com
Subject: Aruba CX 6300 VSF via 10G optic SFP up to 18KM
There are two options here:
Option #1: On the secondary switch run the command: vsf force-auto-join then vsf start-auto-stacking
Option #2: Reset the secondary switch to factory default setting and reboot the switch with the stacking fiber connected.
Original Message:
Sent: Feb 13, 2024 11:39 AM
From: Kamil
Subject: Aruba CX 6300 VSF via 10G optic SFP up to 18KM
between DCs is third party L2 transport = DWDM optical Transponder.
To established of VSF I used command 'vsf start-auto-stacking'.
the configuration on the Conductor is:
!
ssh server vrf default
ssh server vrf mgmt
vsf secondary-member 2
vsf member 1
type jl664a
link 1 1/1/26
link 2 1/1/25
vsf member 2
type jl664a
link 1 2/1/25
link 2 2/1/26
After few time rebooting of standbys switch I got vsf status:
6300# sh vsf detail
VSF Stack
MAC Address : 38:0:0:5:1:c0
Secondary : 2
Topology : chain
Status : Active Fragment
Split Detection Method : None
Software Version : FL.10.11.1030
Force Autojoin : Disabled
Autojoin Eligibility Status : Not Eligible
Autojoin Ineligibility Reason: Configuration changes detected
Name : Aruba-VSF-6300
Contact :
Location :
Member ID : 1
MAC Address : 38:0:0:5:1:c0
Type : JL664A
Model : 6300M 24-port 1GbE and 4-port SFP56 Switch
Status : Conductor
ROM Version : FL.01.12.0002
Serial Number : SGxxxxxxx5T
Uptime : 2 hours, 17 minutes
CPU Utilization : 32%
Memory Utilization : 24%
VSF Link 1 : Up, connected to peer member 2, link 1
VSF Link 2 : Down
Member ID : 2
MAC Address : 38:0:0:5:e:80
Type : JL664A
Model :
Status : Standby Booting
ROM Version :
Serial Number :
Uptime :
CPU Utilization : 0%
Memory Utilization :
VSF Link 1 : Up, connected to peer member 1, link 1
VSF Link 2 : Down
6300#
6300# sh vsf link detail
VSF Member: 1 Link 1
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
1/1/26 up S 2/1/25 38:0:0:5:e:80 JL664A
VSF Member: 1 Link 2
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
1/1/25 down D
VSF Member: 2 Link 1
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
2/1/25 down D
VSF Member: 2 Link 2
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
2/1/26 down D
Status Code abbreviation:
S - Success D - Interface physically down T - Peer timed out
recovery-2# show vsf diagnostics
This Mbr ID : 2
Mbr Mac Address type Status
ID
--- ------------------- -------------- ---------------
2 38:0:0:5:e:80 JL664A Unknown
VSF Member 2
Link Peer Peer
Link State Member Link Interfaces
---- ---------- ------- ------ ---------------------------
1 up 0 0 2/1/25
2 down 0 0 2/1/26
VSF Member: 2 Link 1
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
2/1/25 up S 1/1/26 38:0:0:5:1:c0 JL664A
VSF Member: 2 Link 2
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
2/1/26 down D
Status Code abbreviation:
S - Success D - Interface physically down T - Peer timed out
and after few minutes the topology had been changed to STANADALONE and status NOT PRESENT but still the link is UP
6300# sh vsf detail
VSF Stack
MAC Address : 38:0:0:5:1:c0
Secondary : 2
Topology : standalone
Status : Active Fragment
Split Detection Method : None
Software Version : FL.10.11.1030
Force Autojoin : Disabled
Autojoin Eligibility Status : Not Eligible
Autojoin Ineligibility Reason: Configuration changes detected
Name : Aruba-VSF-6300
Contact :
Location :
Member ID : 1
MAC Address : 38:0:0:5:1:c0
Type : JL664A
Model : 6300M 24-port 1GbE and 4-port SFP56 Switch
Status : Conductor
ROM Version : FL.01.12.0002
Serial Number : SGxxxxxxx5T
Uptime : 2 hours, 25 minutes
CPU Utilization : 3%
Memory Utilization : 24%
VSF Link 1 : Down
VSF Link 2 : Down
Member ID : 2
MAC Address :
Type : JL664A
Model :
Status : Not Present
ROM Version :
Serial Number :
Uptime :
CPU Utilization : 0%
Memory Utilization :
VSF Link 1 : Down
VSF Link 2 : Down
6300#
6300# sh vsf link detail
VSF Member: 1 Link 1
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
1/1/26 up S 2/1/25 38:0:0:5:e:80 JL664A
VSF Member: 1 Link 2
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
1/1/25 down D
VSF Member: 2 Link 1
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
2/1/25 down D
VSF Member: 2 Link 2
Port State Status Code Peer Interface Peer System MAC Peer Product Type
------- -------------------- ----------- -------------- ----------------- -----------------
2/1/26 down D
Status Code abbreviation:
S - Success D - Interface physically down T - Peer timed out
Original Message:
Sent: Feb 13, 2024 08:44 AM
From: Steinar Grande
Subject: Aruba CX 6300 VSF via 10G optic SFP up to 18KM
What is the «problem» and please elaborate on "active optical fiber"
------------------------------
Steinar
Original Message:
Sent: Feb 09, 2024 09:34 AM
From: Kamil
Subject: Aruba CX 6300 VSF via 10G optic SFP up to 18KM
Hello,
I have a problem to create a VSF chain setup between switches which are located in separate DC.
Between DC is active optical fiber.
Port 28 is on the Conductor site and port 27 on Standby site.
Please could you provide any suggestion how to proceed?