Hey peeps,
Tried to google this but not sure on exactly what to look for so if this has been mentioned please help me find it.
Setup:
Huawei 10G switch
Supermicro Pfsense firewall
Supermicro CTO Super Server (4 servers in 1 chassie)
one 2x10G card in use on each server (only 1 10g link on each card currently)
1G firewalled IMPI for each server.
Just wanted to boot a Opnsense VM with dual nicks, each one with tagged vlans, first i forgot to add the second nick so i know the vm managed to boot successfully first, turned it off and then added the nick and to my surprise the entire Proxmox server ("proxmox 2") crashed and rebooted. Actually this is not the first time it happened but this time I've understood what happened.
When the interface enp5s0f0 want to add vlan 1340 it fails which leads to a crash later on.
ug 16 23:02:26 proxmox2 corosync[1738]: notice [TOTEM ] A processor failed, forming new configuration.
Aug 16 23:02:26 proxmox2 corosync[1738]: [TOTEM ] A processor failed, forming new configuration.
Aug 16 23:02:26 proxmox2 kernel: [1159761.481153] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159761.685175] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159761.889206] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159762.093217] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159762.093243] qlge 0000:05:00.0 enp5s0f0: Failed to bring up the adapter
Aug 16 23:02:26 proxmox2 kernel: [1159762.093304] device enp5s0f0.1340 entered promiscuous mode
I've attached the most relevant from the syslog.
What part have I fucked up? Is it necessary to pre define and configure vlantags for the network cards or should I have done it in any other way?
After the crash then the Vlan is configured on the interface:
vmbr0v1340: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:c0:dd:21:a3:74 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Thanks for any suggestions.
BR/Joel
Tried to google this but not sure on exactly what to look for so if this has been mentioned please help me find it.
Setup:
Huawei 10G switch
Supermicro Pfsense firewall
Supermicro CTO Super Server (4 servers in 1 chassie)
one 2x10G card in use on each server (only 1 10g link on each card currently)
1G firewalled IMPI for each server.
Just wanted to boot a Opnsense VM with dual nicks, each one with tagged vlans, first i forgot to add the second nick so i know the vm managed to boot successfully first, turned it off and then added the nick and to my surprise the entire Proxmox server ("proxmox 2") crashed and rebooted. Actually this is not the first time it happened but this time I've understood what happened.
When the interface enp5s0f0 want to add vlan 1340 it fails which leads to a crash later on.
ug 16 23:02:26 proxmox2 corosync[1738]: notice [TOTEM ] A processor failed, forming new configuration.
Aug 16 23:02:26 proxmox2 corosync[1738]: [TOTEM ] A processor failed, forming new configuration.
Aug 16 23:02:26 proxmox2 kernel: [1159761.481153] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159761.685175] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159761.889206] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159762.093217] qlge 0000:05:00.0 enp5s0f0: Command not supported by firmware.
Aug 16 23:02:26 proxmox2 kernel: [1159762.093243] qlge 0000:05:00.0 enp5s0f0: Failed to bring up the adapter
Aug 16 23:02:26 proxmox2 kernel: [1159762.093304] device enp5s0f0.1340 entered promiscuous mode
I've attached the most relevant from the syslog.
What part have I fucked up? Is it necessary to pre define and configure vlantags for the network cards or should I have done it in any other way?
After the crash then the Vlan is configured on the interface:
vmbr0v1340: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
ether 00:c0:dd:21:a3:74 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Thanks for any suggestions.
BR/Joel
Attachments
Last edited: