VLT members os10

Hello,

in OS10, simply changing the discovery-interface range doesn’t automatically add those interfaces to the VLT port-channel. You’ll still need to manually assign the new interfaces to the port-channel used for the VLT interconnect (usually Port-channel 1000).

@DELL-Erman O​ 

this is not accurate as you can’t manually assign port-channel 1000

sw2(conf-range-eth1/1/49-1/1/52)# channel-group 
  <1-999,1001-2000>  Specify a port channel number

Oops yeah, you’re right. You can’t manually assign interfaces to Port-channel 1000 because it’s automatically managed by the system once you define the discovery-interface under the vlt-domain. That port-channel is reserved specifically for VLTi, and its membership gets auto-populated based on the interfaces listed in the discovery-interface command.

If the new interfaces aren’t showing up, make sure:

• They’re physically up and have matching settings (speed, duplex, MTU, etc.) on both switches.
• There are no config conflicts, like if they’re still part of another port-channel or have leftover config that might interfere.

@DELL-Erman O​ 

I verified everything, and the configurations match, also there is no leftover at its new setup.

When using SFS, you need to delete the SmartFabric cluster to change ports. I wanted to confirm that this is not required in full switch mode.

The only other potential issue I see is that the new ports are 100 Gb, while the current ports are 25 Gb. Could that be causing the problem?

The reference manual is vague about the requirements.

Je1000,

No, Full Switch Mode is not strictly required to configure VLT in OS10. However, whether you're operating in SFS mode or Full Switch Mode, the configuration behavior and flexibility differ significantly.

The key differences would be

Full Switch Mode

Recommended for manual VLT configuration.
Offers complete CLI control over VLT domain setup, port-channel assignments, VLANs, and spanning tree.
No restrictions from SmartFabric automation.
Ideal for custom topologies, mixed port speeds, and advanced routing.

SmartFabric Services (SFS) Mode

VLT is automatically configured as part of the SmartFabric cluster.
Port roles (e.g., server, uplink, VLTi) are assigned by the cluster.
Changing port roles often requires deleting and recreating the cluster.
Not suitable for manual VLT configuration or mixed-speed VLTi links.

The speed mismatch is a valid concern, as OS10 VLT requires that VLTi ports be identical in speed and configuration, so If one peer uses 100 Gb ports and the other uses 25 Gb, the VLTi may fail to establish or behave unpredictably.

Let me know if this helps.

@DELL-Chris H ​ 

Can you please confirm that in Full Switch Mode, changing the VLTi ports is supported?

As for the port mismatch, it’s not between switches. I only have two switches, but the working ports are 25 Gb, and I’ve now connected the 100 Gb ports. However, they’re not being discovered or automatically added to port-channel 1000

Yes changing VLTi ports is supported in Full Switch mode., to include using 100 Gb interfaces, provided the following conditions are met:
Manual configuration is required

VLTi ports are not auto-discovered.

You must configure the new 100 Gb ports as discovery interfaces in the VLT domain.

So to use 100 Gb ports (e.g., ethernet 1/1/33 and 1/1/34) as VLTi, you would need:

OS10(config)# interface range ethernet 1/1/33-1/1/34
OS10(conf-range)# no switchport
OS10(conf-range)# exit

(Leaving switchport mode enabled on VLTi ports will prevent them from being used)

OS10(config)# vlt-domain 1
OS10(conf-vlt-1)# discovery-interface ethernet 1/1/33
OS10(conf-vlt-1)# discovery-interface ethernet 1/1/34

This should cause port-channel 1000 to be automatically created and mapped to the specified interfaces.

@DELL-Chris H ​ 

this is what its set and its not working 

I am having the same issue on Dell S4148F-ON switches, except no discovery ports are showing on POs for either switch. Have defaulted both switches and only built VLT domain, POs, MGMT interfaces, and set discovery interfaces to no switchport, but still same issue. Although switches can ping each other via MGMT interface, VLT election role fails to start, both switches think they are in the primary role, and new VLANS (include default VLAN 1) will not "import" into PO1000. 

I have two S4148T-ONs with running/working VLTs, and two S5232Fs also running VLTs with no issues, so I am at a loss on this. Basic config is below, any help is appreciated. 

hostname SW1
!
vlt-domain 1
 backup destination 10.100.100.41 interval 20
 delay-restore 100
 discovery-interface ethernet1/1/29-1/1/30
 peer-routing
 primary-priority 150
 vlt-mac e2:1a:2b:3c:4d:5e
!
interface port-channel1
 description "100 GB VLT PEER LINK"
 no shutdown
 switchport mode trunk
 switchport access vlan 1
 vlt-port-channel 1
 !
 interface ethernet1/1/29
 no shutdown
 no switchport
 no flowcontrol receive 
 no flowcontrol transmit
 !
 interface ethernet1/1/30
 no shutdown
 no switchport
 no flowcontrol receive 
 no flowcontrol transmit
 !
 interface mgmt1/1/1
 no shutdown
 no ip address dhcp
 ip address 10.100.100.42/24
 no ipv6 enable 

hostname SW2
!
vlt-domain 1
 backup destination 10.100.100.42 interval 20
 delay-restore 100
 discovery-interface ethernet1/1/29-1/1/30
 peer-routing
 primary-priority 250
 vlt-mac e2:1a:2b:3c:4d:5e
!
interface port-channel1
 description "100 GB VLT PEER LINK"
 no shutdown
 switchport mode trunk
 switchport access vlan 1
 vlt-port-channel 1
 !
 interface ethernet1/1/29
 no shutdown
 no switchport
 no flowcontrol receive 
 no flowcontrol transmit
 !
 interface ethernet1/1/30
 no shutdown
 no switchport
 no flowcontrol receive 
 no flowcontrol transmit
 !
 interface mgmt1/1/1
 no shutdown
 no ip address dhcp
 ip address 10.100.100.41/24
 no ipv6 enable

SW1# show vlt 1
Domain ID                  : 1
Unit ID                    : 2
Role                       : primary
Version                    : 2.3
Local System MAC address   : f0:d4:e2:29:e9:d6
Role priority              : 150
VLT MAC address            : e2:1a:2b:3c:4d:5e
IP address                 : fda5:74c8:b79e:1::2
Delay-Restore timer        : 100 seconds
Peer-Routing               : Enabled
Peer-Routing-Timeout timer : 0 seconds
VLTi Link Status
    port-channel1000       : up

VLT Peer Unit ID    System MAC Address    Status    IP Address             Version
----------------------------------------------------------------------------------
  1                 f0:d4:e2:2a:33:d6      up       fda5:74c8:b79e:1::1   

SW1#show vlan
Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs,
       @ – Attached to Virtual Network, P - Primary, C - Community, I - Isolated
Q: A - Access (Untagged), T - Tagged
    NUM    Status    Description                     Q Ports
*   1      Active                                    A Eth1/1/1-1/1/26,1/1/31-1/1/54 
                                                     A Po1 
    4094   Active                                    T Po1000 

SW2# show vlt 1
Domain ID                  : 1
Unit ID                    : 1
Role                       : primary
Version                    : 2.3
Local System MAC address   : f0:d4:e2:2a:33:d6
Role priority              : 250
VLT MAC address            : e2:1a:2b:3c:4d:5e
IP address                 : fda5:74c8:b79e:1::1
Delay-Restore timer        : 100 seconds
Peer-Routing               : Enabled
Peer-Routing-Timeout timer : 0 seconds
VLTi Link Status
    port-channel1000       : up

VLT Peer Unit ID    System MAC Address    Status    IP Address             Version
----------------------------------------------------------------------------------
  2                 f0:d4:e2:29:e9:d6      up       fda5:74c8:b79e:1::2 

SW2# show vlan
Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs,
       @ – Attached to Virtual Network, P - Primary, C - Community, I - Isolated
Q: A - Access (Untagged), T - Tagged
    NUM    Status    Description                     Q Ports
*   1      Active                                    A Eth1/1/1-1/1/26,1/1/31-1/1/54 
                                                     A Po1 
    4094   Active                                    T Po1000 

Hello,

Core Configuration Steps (on both peers)

1. Enter Configuration Mode:
2. Create the VLT Domain: Use the same ID (e.g., 1) on both switches.
3. Configure VLT Interconnect (VLTi) Ports: Assign dedicated ports (e.g., ethernet 1/1/29, ethernet 1/1/30) for the VLTi, ensuring they are not in a standard switchport mode.
4. Set VLT Priority (Optional but Recommended): Assign different priorities (e.g., 10 for primary, 20 for secondary) to designate the primary peer.
5. Configure VLT Backup Link (Heartbeat): Set the management IP of the peer switch to monitor its status.
6. Configure VLT MAC (Optional but Recommended): Ensures consistent MAC for faster convergence.
7. Create VLT Port-Channel (for End Devices): Create a Port-Channel (LAG) and associate it with the VLT domain.
8. Assign Member Ports: Add physical ports to the Port-Channel (e.g., ethernet 1/1/3 and ethernet 1/1/4).
9. Configure VLANs & Spanning Tree: Ensure VLANs are created and Spanning Tree (RPVST+ is default) is handled correctly for loop prevention, often by blocking one side of the VLT Port-Channel on the end device for redundancy. 

OS10(config)# interface range ethernet 1/1/3-1/1/4
OS10(config-if-range)# no switchport # For server-facing ports if needed
OS10(config-if-range)# channel-group 100 mode active # Or 'lacp'

OS10(config)# interface port-channel 1 # Or any unused Po number
OS10(config-if-Po100)# vlt-port-channel 1

OS10(conf-vlt-domain)# vlt-mac e2:1a:2b:3c:4d:5e

OS10(conf-vlt-domain)# back-up destination 10.100.100.41

OS10(conf-vlt-domain)# primary-priority 150 # On Primary Peer
OS10(conf-vlt-domain)# primary-priority 250 # On Secondary Peer

OS10(conf-vlt-1)# discovery-interface ethernet 1/1/29
OS10(conf-vlt-1)# discovery-interface ethernet 1/1/30
OS10(conf-vlt-1)# peer-routing
OS10(conf-vlt-1)# delay-restore 100

OS10(config)# vlt domain 1

OS10# configure terminal

by default STP , Rapid-pvst enabled dell switches.

We ask that you power off both switches first then power on the primary and login to switch and check their role, then power on the secondary switch and login into switch then check their role as well.

The issues will be fixed by rebooting both switches one by one.

@DELL-Young E , thank you for the response. I have gone through my config again, but have seen no changes that needed to be made based on your examples. Additionally, for gee whiz, I added a second port-channel set up as a client port and added the vlt-port-channel config to the port-channel as well as channel group commands to each port. I am still having the same issue as before, even after shutting down both switches, powering on the primary unit and making sure it is in the primary role. Switch defaults to full-switch, primary switch takes correct role, VLT heartbeat link is up when second unit comes online, VLTi link status shows up on both switches, vlan4094 and PO1000 both show an up state, but PO1000 is not automatically added to vlan 1 or new vlan 100, and both vlans show as inactive. Only vlan 4094 shows active and includes PO1000. No interface ethernet ports show as members of  port-channel 1 or 100, and both PO1 and PO100 show up/down state.

Below are the outputs of both switches (condensed) for show run, show vlt 1, sh vlan, sh po1, sh po100, as well as log entries from SW1 showing VLT/interface states as second switch boots and VLT Peer configuration retrieval failed to start election error:

SW1# show running-configuration
! Version 10.5.0.4
! Last configuration change at Dec  10 15:25:49 2025
!
ip vrf default
!
interface breakout 1/1/25 map 100g-1x
interface breakout 1/1/26 map 100g-1x
interface breakout 1/1/29 map 100g-1x
interface breakout 1/1/30 map 100g-1x
hostname SW1
!
interface vlan1
 no shutdown
!
interface vlan100
 no shutdown
!
interface port-channel1
 description "100 GB VLT PEER LINK"
 no shutdown
 switchport mode trunk
 switchport access vlan 1
 vlt-port-channel 1
!
interface port-channel100
 no shutdown
 switchport access vlan 100
 vlt-port-channel 100
!
interface mgmt1/1/1
 no shutdown
 no ip address dhcp
 ip address 10.100.100.41/24
 no ipv6 enable
!
interface ethernet1/1/1
 no shutdown
 channel-group 100 mode active
 no switchport
 flowcontrol receive on
!
interface ethernet1/1/2
 no shutdown
 channel-group 100 mode active
 no switchport
 flowcontrol receive on
!
interface ethernet1/1/29
 no shutdown
 no switchport
 flowcontrol receive off
 flowcontrol transmit off
!
interface ethernet1/1/30
 no shutdown
 no switchport
 flowcontrol receive off
 flowcontrol transmit off
!
management route 0.0.0.0/0 10.100.100.254
!
vlt-domain 1
 backup destination 10.100.100.42 interval 20
 delay-restore 100
 discovery-interface ethernet1/1/29-1/1/30
 peer-routing
 primary-priority 150
 vlt-mac e2:1a:2b:3c:4d:5e
!
SW1#show vlt 1
Domain ID                  : 1
Unit ID                    : 2
Role                       : primary
Version                    : 2.3
Local System MAC address   : f0:d4:e2:29:e9:d6
Role priority              : 150
VLT MAC address            : e2:1a:2b:3c:4d:5e
IP address                 : fda5:74c8:b79e:1::2
Delay-Restore timer        : 100 seconds
Peer-Routing               : Enabled
Peer-Routing-Timeout timer : 0 seconds
VLTi Link Status
    port-channel1000       : up

VLT Peer Unit ID    System MAC Address    Status    IP Address             Version
----------------------------------------------------------------------------------
  1                 f0:d4:e2:2a:33:d6      up       fda5:74c8:b79e:1::1            

SW1# show vlan
Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs,
       @ – Attached to Virtual Network, P - Primary, C - Community, I - Isolated
Q: A - Access (Untagged), T - Tagged
    NUM    Status    Description                     Q Ports
*   1      Inactive                                  A Eth1/1/3-1/1/24,1/1/31-1/1/54 
                                                     A Po1 
    100    Inactive                                  A Po100 
    4094   Active                                    T Po1000 

SW1# show interface po1
Port-channel 1 is up, line protocol is down
Description: 100 GB VLT PEER LINK
Address is f0:d4:e2:29:ea:20, Current address is f0:d4:e2:29:ea:20
Interface index is 65
Internet address is not set
Mode of IPv4 Address Assignment: not set
Interface IPv6 oper status: Disabled
MTU 1532 bytes, IP MTU 1500 bytes
LineSpeed 0
Minimum number of links to bring Port-channel up is 
Maximum active members that are allowed in the portchannel is 32
Members in this channel: 
ARP type: ARPA, ARP Timeout: 60
Last clearing of "show interface" counters: 00:10:30
Queuing strategy: fifo
Input statistics:
      packets,  octets
      64-byte pkts,  over 64-byte pkts,  over 127-byte pkts
      over 255-byte pkts,  over 511-byte pkts, NaN over 1023-byte pkts
      Multicasts,  Broadcasts,  Unicasts
      runts,  giants,  throttles
      CRC, 0 overrun,  discarded
Output statistics:
      packets,  octets
      64-byte pkts,  over 64-byte pkts,  over 127-byte pkts
      over 255-byte pkts,  over 511-byte pkts, NaN over 1023-byte pkts
      Multicasts,  Broadcasts,  Unicasts
      throttles,  discarded,  Collisions,  wred drops
Rate Info(interval 30 seconds):
     Input NaN Mbits/sec,  packets/sec, 0% of line rate
     Output NaN Mbits/sec,  packets/sec, 0% of line rate
Time since last interface status change: 00:10:30

SW1# show interface po100
Port-channel 100 is up, line protocol is down
Address is f0:d4:e2:29:ea:3b, Current address is f0:d4:e2:29:ea:3b
Interface index is 67
Internet address is not set
Mode of IPv4 Address Assignment: not set
Interface IPv6 oper status: Disabled
MTU 1532 bytes, IP MTU 1500 bytes
LineSpeed 0
Minimum number of links to bring Port-channel up is 
Maximum active members that are allowed in the portchannel is 32
Members in this channel: 
ARP type: ARPA, ARP Timeout: 60
Last clearing of "show interface" counters: 00:10:33
Queuing strategy: fifo
Input statistics:
     0 packets, 0 octets
     0 64-byte pkts, 0 over 64-byte pkts, 0 over 127-byte pkts
     0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte pkts
     0 Multicasts, 0 Broadcasts, 0 Unicasts
     0 runts, 0 giants, 0 throttles
     0 CRC, 0 overrun, 0 discarded
Output statistics:
     0 packets, 0 octets
     0 64-byte pkts, 0 over 64-byte pkts, 0 over 127-byte pkts
     0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte pkts
     0 Multicasts, 0 Broadcasts, 0 Unicasts
     0 throttles, 0 discarded, 0 Collisions,  wred drops
Rate Info(interval 30 seconds):
     Input 0 Mbits/sec, 0 packets/sec, 0% of line rate
     Output 0 Mbits/sec, 0 packets/sec, 0% of line rate
Time since last interface status change: 00:10:34

Adding second switch and logs in separate port due to 10,000 character limit.

@DELL-Young E , here is the output from SW2 and logs:

SW2# show running-configuration
! Version 10.5.0.4
! Last configuration change at Dec  10 16:41:49 2025
!
ip vrf default
!
interface breakout 1/1/25 map 100g-1x
interface breakout 1/1/26 map 100g-1x
interface breakout 1/1/29 map 100g-1x
interface breakout 1/1/30 map 100g-1x
hostname SW2
!
interface vlan1
 no shutdown
!
interface vlan100
 no shutdown
!
interface port-channel1
 description "100 GB VLT PEER LINK"
 no shutdown
 switchport mode trunk
 switchport access vlan 1
 vlt-port-channel 1
!
interface port-channel100
 no shutdown
 switchport access vlan 100
 vlt-port-channel 100
!
interface mgmt1/1/1
 no shutdown
 no ip address dhcp
 ip address 10.100.100.42/24
 no ipv6 enable
!
interface ethernet1/1/1
 no shutdown
 channel-group 100 mode active
 no switchport
 flowcontrol receive on
!
interface ethernet1/1/2
 no shutdown
 channel-group 100 mode active
 no switchport
 flowcontrol receive on
!
interface ethernet1/1/29
 no shutdown
 no switchport
 flowcontrol receive off
 flowcontrol transmit off
!
interface ethernet1/1/30
 no shutdown
 no switchport
 flowcontrol receive off
 flowcontrol transmit off
!
management route 0.0.0.0/0 10.100.100.254
!
vlt-domain 1
 backup destination 10.100.100.41 interval 20
 delay-restore 100
 discovery-interface ethernet1/1/29-1/1/30
 peer-routing
 primary-priority 250
 vlt-mac e2:1a:2b:3c:4d:5e
!
SW2# show vlt 1
Domain ID                  : 1
Unit ID                    : 1
Role                       : 
Version                    : 2.3
Local System MAC address   : f0:d4:e2:2a:33:d6
Role priority              : 250
VLT MAC address            : e2:1a:2b:3c:4d:5e
IP address                 : fda5:74c8:b79e:1::1
Delay-Restore timer        : 100 seconds
Peer-Routing               : Enabled
Peer-Routing-Timeout timer : 0 seconds
VLTi Link Status
    port-channel1000       : up

VLT Peer Unit ID    System MAC Address    Status    IP Address             Version
----------------------------------------------------------------------------------
  2                 f0:d4:e2:29:e9:d6      up       fda5:74c8:b79e:1::2            

SW2# show vlan
Codes: * - Default VLAN, M - Management VLAN, R - Remote Port Mirroring VLANs,
       @ – Attached to Virtual Network, P - Primary, C - Community, I - Isolated
Q: A - Access (Untagged), T - Tagged
    NUM    Status    Description                     Q Ports
*   1      Inactive                                  A Eth1/1/3-1/1/24,1/1/31-1/1/54 
                                                     A Po1 
    100    Inactive                                  A Po100 
    4094   Active                                    T Po1000 

SW2# show interface po1
Port-channel 1 is up, line protocol is down
Description: 100 GB VLT PEER LINK
Address is f0:d4:e2:2a:34:20, Current address is f0:d4:e2:2a:34:20
Interface index is 65
Internet address is not set
Mode of IPv4 Address Assignment: not set
Interface IPv6 oper status: Disabled
MTU 1532 bytes, IP MTU 1500 bytes
LineSpeed 0
Minimum number of links to bring Port-channel up is 
Maximum active members that are allowed in the portchannel is 32
Members in this channel: 
ARP type: ARPA, ARP Timeout: 60
Last clearing of "show interface" counters: 00:05:06
Queuing strategy: fifo
Input statistics:
      packets,  octets
      64-byte pkts,  over 64-byte pkts,  over 127-byte pkts
      over 255-byte pkts,  over 511-byte pkts, NaN over 1023-byte pkts
      Multicasts,  Broadcasts,  Unicasts
      runts,  giants,  throttles
      CRC, 0 overrun,  discarded
Output statistics:
      packets,  octets
      64-byte pkts,  over 64-byte pkts,  over 127-byte pkts
      over 255-byte pkts,  over 511-byte pkts, NaN over 1023-byte pkts
      Multicasts,  Broadcasts,  Unicasts
      throttles,  discarded,  Collisions,  wred drops
Rate Info(interval 30 seconds):
     Input NaN Mbits/sec,  packets/sec, 0% of line rate
     Output NaN Mbits/sec,  packets/sec, 0% of line rate
Time since last interface status change: 00:05:06

SW2# show interface po100
Port-channel 100 is up, line protocol is down
Address is f0:d4:e2:2a:34:3b, Current address is f0:d4:e2:2a:34:3b
Interface index is 67
Internet address is not set
Mode of IPv4 Address Assignment: not set
Interface IPv6 oper status: Disabled
MTU 1532 bytes, IP MTU 1500 bytes
LineSpeed 0
Minimum number of links to bring Port-channel up is 
Maximum active members that are allowed in the portchannel is 32
Members in this channel: 
ARP type: ARPA, ARP Timeout: 60
Last clearing of "show interface" counters: 00:05:11
Queuing strategy: fifo
Input statistics:
     0 packets, 0 octets
     0 64-byte pkts, 0 over 64-byte pkts, 0 over 127-byte pkts
     0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte pkts
     0 Multicasts, 0 Broadcasts, 0 Unicasts
     0 runts, 0 giants, 0 throttles
     0 CRC, 0 overrun, 0 discarded
Output statistics:
     0 packets, 0 octets
     0 64-byte pkts, 0 over 64-byte pkts, 0 over 127-byte pkts
     0 over 255-byte pkts, 0 over 511-byte pkts, 0 over 1023-byte pkts
     0 Multicasts, 0 Broadcasts, 0 Unicasts
     0 throttles, 0 discarded, 0 Collisions,  wred drops
Rate Info(interval 30 seconds):
     Input 0 Mbits/sec, 0 packets/sec, 0% of line rate
     Output 0 Mbits/sec, 0 packets/sec, 0% of line rate
Time since last interface status change: 00:05:11

<165>1 2025-12-10T22:25:31.308750+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :ethernet1/1/29
<165>1 2025-12-10T22:25:31.464883+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :ethernet1/1/30
<165>1 2025-12-10T22:25:31.632875+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_ASTATE_UP: Interface admin state up :port-channel1000
<165>1 2025-12-10T22:25:31.639436+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_DN: Interface operational state is down :port-channel1000
<165>1 2025-12-10T22:25:31.695633+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :port-channel1000
<165>1 2025-12-10T22:25:31.723095+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :vlan4094
<165>1 2025-12-10T22:25:31.773412+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %VLT_PEER_UP: VLT unit 1 is up
<165>1 2025-12-10T22:25:34.666808+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %VLT_HB_UP: VLT peer heartbeat link is up
<165>1 2025-12-10T22:25:51.065996+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_DN: Interface operational state is down :ethernet1/1/29
<165>1 2025-12-10T22:25:51.127868+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_DN: Interface operational state is down :ethernet1/1/30
<165>1 2025-12-10T22:25:51.192743+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_DN: Interface operational state is down :port-channel1000
<165>1 2025-12-10T22:25:51.246336+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_DN: Interface operational state is down :vlan4094
<165>1 2025-12-10T22:25:51.505174+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :ethernet1/1/29
<165>1 2025-12-10T22:25:51.513289+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :ethernet1/1/30
<165>1 2025-12-10T22:25:51.755791+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :port-channel1000
<165>1 2025-12-10T22:25:51.756379+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %IFM_OSTATE_UP: Interface operational state is up :vlan4094
<165>1 2025-12-10T22:25:52.302484+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %VLT_PEER_UP: VLT unit 1 is up

<165>1 2025-12-10T22:30:55.959059+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %VLT_ELECTION_ROLE: VLT Peer configuration retrieval failed to start election
<165>1 2025-12-10T22:36:10.600156+00:00 JHQ-N-CS01 dn_alm 698 - - Node.1-Unit.1:PRI [event], Dell EMC (OS10) %VLT_ELECTION_ROLE: VLT Peer configuration retrieval failed to start election

Hello wluns, could you send your service tag by DM? https://www.dell.com/community/en/direct-messaging

Hell, thanks for the service tag. I think your issue is explained here.

Dell Networking OS10 Certificate Expiration and Solution | Dell Malaysia

The VLT tunnel is not working because the X.509 protocol certificates have expired. The customer must upgrade both switches to version 10.5.0.9v in order for VLTi to function properly within the VLT domain.

We request that you upgrade to 10.6.1.0v, to the latest version via ONIE mode and configure to make it up.

Respectfully,

@DELL-Young E , I am working through these upgrades. Unfortunately, ONIE did not cooperate well and I had to go into recovery on SW1. A TFTP of the updater worked (onie-updater-x86_64-dellemc_s4100_c2338-r0.3.33.1.1-11), but when installing the ONIE update full (onie-update-full-x86_64-dellemc_s4100_c2338-r0.3.33.5.1-26.bin), the image install failed and needed to hard reboot. After switch "recovered" into ONIE rescue, I was able to TFTP OS10 ENT 10.5.6.3.4 (the latest version we have for our licensed equipment). OS10 Install went without incident.

On SW2, I stayed in OS10 CLI and ran the same updates (OS10 is still transferring) and had the same problem with the .bin file. Not sure what the issue is there, but was pretty much identical. Will update once SW@ is on OS10 ENT 10.5.6.3.4 and I verify the VLT configuration on each.

Thank you,