On 6/28/22 02:48, Stuart Henderson wrote:
> Did you try "ifconfig ix0 down" and "ifconfig ix0 up" when it was in the
> failure condition? (Wondering whether you tried and it failed, or whether
> you didn't try that before rebooting).
Yes sir an "ifconfig ix0 down"/"ifconfig ix0 up" was attempted due to
the fact that this technique was referenced quite often in the digital
literature we perused.
Unfortunately when this particular malfunction occurs this technique
does not resolve the problem and therefore makes the rebooting efforts
necessary.
Our team now feels pretty confident about the working environment that
seems to trigger the inoperability - whenever the ix interface attempts
to pass traffic and has no upstream device that is either connected or
powered on.
There is a final, possibly minor nugget that I did discover. While
perusing the man page for the ix device driver in greater detail I noted
that one of the ethernet controller chip supported is 82599EB. Although
the OS recognized the chip set in our adapter and utilizes the ix driver
the actual controller chip is the Intel® 82599ES which from what I have
been able to discern is a part of the same chip family. From Intel
82599ES — Dual-port serial 10 GbE backplane interface for blade
implementations
(includes the 82599EB SKU functionality plus KR and SFI interfaces)
This fact may be in the trivial but wanted to pass along the details.
Thanks again for all of your assistance.
No comments:
Post a Comment