https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218579
M1001101 <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #68 from M1001101 <[email protected]> ---
Hello Guys,
I'm detecting unusual behavior with the network adapter:
bge0: <HPE Ethernet 1Gb 4-port 331i Adapter, ASIC rev. 0x5719001>
bge0: APE FW version: NCSI v1.5.33.0
bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E
These are the driver data:
bge0: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0
mtu 1500
options=c019b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,VLAN_HWTSO,LINKSTATE>
ether 3c:a8:2a:21:74:d4
inet 192.168.100.4 netmask 0xffffff00 broadcast 192.168.100.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
After upgrading from 14.2 to 14.3, both HP DL360 Gen9 and Gen10 servers stopped
booting with WOL.
It worked the first time I plugged the server into a power source, but after a
power off, WOL stopped working. You need to unplug the power and replug it to
restore WOL.
Is this the same problem you are discussing here?
I've currently modified my scripts to use the iLO "power on" command via ssh.
However, WOL is more standard even if I were to rebrand the servers.
--
You are receiving this mail because:
You are on the CC list for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.