Ipmitool raw 0x0c 0x02 0x01 0x05 0x 00 0x00īMC Mac address of shared NIC channel port 2 (If active) I perfer the caned ipmitool lan print command since raw commands can get you into non-recoverable troubles.īMC Mac address of shared NIC channel port 1 (if active) These commands will report the BMC NICs MAC address (for hard core programmers that don't like ipmitool lan print 1 or ipmitool lan print 3), but to get the OS MAC addess, you need to do the math. Supports-priv-flags: ~]# ethtool -i eno12399įirmware-version: 3.00 0x80008943 20.5.13īy checking the domain/bus/function numbers from lspci you can compare those with the output of ethtool and determine which device names are associated with what model card and from there determine the MAC address.Ox30 0x19 command will tell you which of the mother board physicial NICs channel ports the BMC is sharing (NIC 1 or NIC2). Supports-priv-flags: ~]# ethtool -i eno8403 Subsystem: Intel Corporation Ethernet 25G 2P E810-XXV OCPģ1:00.1 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02)ĩ8:00.0 Ethernet controller: Mellanox Technologies MT2892 Family ĩ8:00.1 Ethernet controller: Mellanox Technologies MT2892 Family ī1:00.0 Ethernet controller: Mellanox Technologies MT28800 Family ī1:00.1 Ethernet controller: Mellanox Technologies MT28800 Family # ethtool -i eno8303įirmware-version: FFV21.81.3 bc 5720-v1.39 and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIeģ1:00.0 Ethernet controller: Intel Corporation Ethernet Controller E810-XXV for SFP (rev 02) and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIeĠ4:00.1 Ethernet controller: Broadcom Inc. I'll leave this open in case someone comes up with something cleaner but what I ended up doing was combining lspci and ethtool: ~]# lspci -v | grep EthernetĠ4:00.0 Ethernet controller: Broadcom Inc.
There's no "not much shell logic" way of mapping Linux network interfaces to "device names" (like your "NIC 1 - Intel x710"), especially in the context of things like multi-port SFP+ cards like the x710 these are designed to offer virtual functions, so the mapping of "one Linux network device belongs to one hardware device" simply works in neither direction.
Link/ether 00:01:02:03:04:05 brd ff:ff:ff:ff:ff:ffĤ: virbr0: mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
Link/ether aa:aa:bb:bb:cc:dd brd ff:ff:ff:ff:ff:ffģ: enp1s0: mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 Mine looks roughly like 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
0 kommentar(er)
