NIC cards

From: Mohamed K. Ahmed <mkahmed_at_vsc.teksystems.com>
Date: Thu, 21 Mar 2002 08:55:40 -0500

Dear Managers,
I have an ES40 machine with a Fiber network card (alt0) and a DE504 NIC
(ee0)
I am using the Fiber NIC and not the DE one, so I have disabled the ee0
NIC.
Now, when I issue the command # netstat -in, I notice that some pkts
go through the ee0 interface, they fail off course because it is
disabled, but my question is WHY do pakets go there while it is not
configured?
The out put of the netstat -in and netstat -is as follows:

# netstat -in
Name Mtu Network Address Ipkts Ierrs Opkts
Oerrs Coll
alt0 1500 <Link> 00:60:6d:xx:xx:xx 634861934 0
698551018 0 0
alt0 1500 10.xxx.xxx/24 10.xxx.xxx.xxx 634861934 0
698551018 0 0
alt0 1500 DLI none 634861934 0
698551018 0 0
ee0 1500 <Link> 00:50:8b:xx:xx:xx 0 0 288661
288661 0
ee0 1500 DLI none 0 0 288661
288661 0
sl0* 296 <Link> 0 0
0 0 0
lo0 4096 <Link> 14525130 0
14525130 0 0
lo0 4096 127/8 127.0.0.1 14525130 0
14525130 0 0
ppp0* 1500 <Link> 0 0
0 0 0
# netstat -is

alt0 Ethernet counters at Thu Mar 21 08:54:38 2002

       65535 seconds since last zeroed
  4294967295 bytes received
  4294967295 bytes sent
   265525456 data blocks received
   323880811 data blocks sent
  1106180458 multicast bytes received
    10777125 multicast blocks received
    22613420 multicast bytes sent
      130246 multicast blocks sent
           0 blocks sent, initially deferred
           0 blocks sent, single collision
           0 blocks sent, multiple collisions
           0 send failures
           0 collision detect check failure
           0 receive failures
           0 unrecognized frame destination
           0 data overruns
           0 system buffer unavailable
           0 user buffer unavailable

ee0 Ethernet counters at Thu Mar 21 08:54:38 2002

         380 seconds since last zeroed
           0 bytes received
        1078 bytes sent
           0 data blocks received
           7 data blocks sent
           0 multicast bytes received
           0 multicast blocks received
        1078 multicast bytes sent
           7 multicast blocks sent
           0 blocks sent, initially deferred
           0 blocks sent, single collision
           0 blocks sent, multiple collisions
           7 send failures, reasons include:
                Carrier check failed
           0 collision detect check failure
           0 receive failures
           0 unrecognized frame destination
           0 data overruns
           0 system buffer unavailable
           0 user buffer unavailable
#


Thank for your help

-MKMA
Received on Thu Mar 21 2002 - 13:55:20 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:43 NZDT