VDX 6740 - Fcoe but no TenGigabitEthernet

[o12emarkableo]

sw0# sh run int
interface Vlan 1
!
interface Ve 1
no shutdown
attach rbridge-id add 1
!
interface Management 1/0
no tcp burstrate
ip icmp echo-reply
no ip address dhcp
ip address 192.168.10.202/24
ipv6 icmpv6 echo-reply
no ipv6 address autoconfig
no ipv6 address dhcp
vrf forwarding mgmt-vrf
no shutdown
!
interface Port-channel 1
vlag ignore-split
switchport
switchport mode trunk
switchport trunk allowed vlan all
switchport trunk tag native-vlan
spanning-tree shutdown
no shutdown
!
interface Fcoe 1/1/1
no shutdown
!
interface Fcoe 1/1/2
no shutdown
!
interface Fcoe 1/1/3
no shutdown
!
interface Fcoe 1/1/4
no shutdown
!
interface Fcoe 1/1/5
no shutdown
!
interface Fcoe 1/1/6
no shutdown
!
interface Fcoe 1/1/7
no shutdown
!
interface Fcoe 1/1/8
no shutdown
!
interface Fcoe 1/1/9
no shutdown
!
interface Fcoe 1/1/10
no shutdown

sw0# show interface ten 1/0/1
% Error: Interface TenGigabitEthernet 1/0/1 doesn't exist

## here is a one of the ports that I have a dac cable plugged into. The line protocal is down.

sw0# sh int fcoe 1/1/8
Interface Fcoe 1/1/8
---------------------------------------------------------
Fcoe 1/1/8 is Up, Line protocol is Down
Ethernet port is TenGigabitEthernet
Interface index (ifindex) is 0x0
Config Mode is VF, Current Mode is VF
Last clearing of show interface counters: 1970-01-01 00:00:00.000000
RX Statistics:
Num of FIP FLOGIs : 0
Num of FIP NPIV FDISCs : 0
Num of FIP LOGOs : 0
Num of FIP Enode Keep Alives : 0
Num of FIP VN Port Keep Alives : 0
Errors : 0
TX Statistics:
Num of FLOGI/FDISC ACCs : 0
Num of LS_RJT (FLOGI, FDISC, LOGO) : 0
Num of CVLs : 0
Errors : 0
Time since last status change : 1970-01-01 00:00:00.000000

Total number of Interfaces : 1

[Michael_Morey]

"copy default start" and a reload should remove all configs from the device if it is a stand alone device.

Regarding the boot error, I see several issues reported with this error that were fixed in the newer releases.  Are you running an old version of NOS?  You can try upgrading to the latest version.

[o12emarkableo]

sw0# sh ver

Network Operating System Software
Network Operating System Version: 7.4.1f
Copyright (c) 2017-2018 Extreme Networks, Inc.
Firmware name: 7.4.1f
Build Time: 08:47:59 Aug 9, 2022
Install Time: 08:59:55 Jun 2, 2025
Kernel: 2.6.34.6

BootProm: 1.0.1
Control Processor: e500mc with 4096 MB of memory

Slot Name Primary/Secondary Versions Status
---------------------------------------------------------------------------
SW/0 NOS 7.4.1f ACTIVE*
7.4.1f
SW/1 NOS 7.4.1f STANDBY
7.4.1f

sw0# show lic

rbridge-id: 1
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
FCoE Base license
Feature name:FCOE_BASE
License is valid
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
40G Port Upgrade license
Feature name:PORT_40G_UPGRADE
License is valid
Capacity: 1

sw0# sh vcs
Config Mode : Distributed
VCS Mode : Logical Chassis
VCS ID : 1
VCS GUID : 00000000000000000000000000000000
Total Number of Nodes : 1
Rbridge-Id WWN Management IP VCS Status Fabric Status HostName
--------------------------------------------------------------------------------------------------------------
1 >10:00:50:EB:1A:81:DD:40* 192.168.10.202 Online Online sw0

how to I change it to standalone?

also getting this every so often?

*** CORE FILES WARNING (06/02/25 - 15:00:04 ) ***
4432 KBytes in 1 file(s)
use "copy support" command to upload

*** FFDC FILES WARNING (06/02/25 - 15:00:04 ) ***
28900 KBytes in 44 file(s)
use "copy support" command to upload

[Michael_Morey]

FCOE stopped being supported as of NOS 7.3, so I would try removing the FCOE license:

"license remove licStr FCOE_BASE"

* You may or may not need to reload after this, if you still see the ports as all FCOE I would reload after removing the license.

Regarding Standalone mode, sorry if I confused you.  Way back in NOS 2.x we had an actual mode "Stand Alone", however in the 7.x versions there is only "Logical Chassis" mode.  What I meant by standalone was; Is this device in a fabric with other devices, or in a fabric of one? I see from your output that this device does not have any other VCS peers, therefore it is own Principal switch and managing its own config.

Regarding the Core/FFDC files, these are likely historical.  You can view the dates via:

"show support"

If they are all old you can clear them with:

"clear support"

If the device is constantly generating them you would need to open a case with TAC to investigate.

[o12emarkableo]

Also receiving the error on boot up

[0] ERROR IRQ reflected, error-int=15, guest=p1-linux core 0 base 0x238f32421 window 0xb2be0e time 0x239a5e298 count 45590 printed 1

and it counts all the way up to 64

All the lights on the front of the devices stay amber lit once booted.