Re: MIB for my NIC cards

"Damon Getsman" <dgetsman@xxxxxxxxxxxx> wrote in message
news:b43e726a-9b77-40ac-802f-00e6982b4556@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I've currently been trying to locate them by hardware vendor, I guess
that might not be the right path to be taking... Perhaps I should be
looking in subtrees of the associated device? (ie eth0, eth1)

If anybody knows where I might be able to look for this information I
would definitely appreciate it. :)

"man snmpwalk" might be helpful to you.


.

Relevant Pages

  • Re: Problem with bonded (teaming) NICs on RHEL 4.0
    ... I think mii-tool has a problem with GIG speeds. ... When you run mii-tool for eth0 and eth1 it does not show that. ...
    (RedHat)
  • speed up my LAN
    ... mii-tool -l -w eth0 ... Sep 25 01:09:01 dave kernel: eth1: Link changed: ... basic mode: autonegotiation enabled ... basic status: autonegotiation complete, link ok ...
    (comp.os.linux.networking)
  • Re: setting-up a dmz
    ... Not provide any actual log messages? ... No shorewall, i prefer a own debian iptables firewall:) ... eth1: link up, 10Mbps, half-duplex, lpa 0x0000 ... ADDRCONF: eth0: link is not ready ...
    (Debian-User)
  • Kernel upgrade 2.4.18-14 -> 2.4.23 (rh8)
    ... I just recompiled a new kernel, ... eth0: Broadcom BCM5701 Integrated Copper transceiver found ... eth1: Broadcom BCM5701 Integrated Copper transceiver found ... Dec 5 10:07:55 network: Setting network parameters: succeeded ...
    (RedHat)
  • Re: [opensuse] Suse 10.2 +two network cards (Not yet solved)
    ... then set the eth0 as it was default from the installation. ... set eth1 DNS servers etc. so DHCP would not update them. ... Also have figure out where to put the route command ...
    (SuSE)