>
> Tuc wrote:
> >
> > > So the > 100 errors really are errors, since you shouldn't have 117%
> > > bandwidth usage on your ethernet device. That should be reported in
> > > run/*.error, because it's a misconfiguration you wouldn't want
> > > cluttering up your snipslog file.
>
> Is this a FE port?
>
test19219# ifconfig exp0
exp0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
link type ether 0:d0:b7:a9:7b:ea mtu 1500 speed 100Mbps
media 100baseTX full_duplex status active
>
>
> Did etherload detect it as a FE port or a 10Mbps port?
> Try running with -d.
>
test19219# ./etherload -d
etherload: This is a SNIPS version
etherload- Reading global config file /usr/local/etc/snips/etc/snips.conf
(etherload).. locked pid-file, started new process (pid=6894)
Opening config file '/usr/local/etc/snips/etc/etherload-confg'
debug: Checking for devices: exp0
Devices being monitored are:
1. exp0 Ethernet 10000
Scan-interval= 15, sleeptime= 300
(debug)exp0 thresholds:
bw: 30 50 70
pps: 500 1000 1500
BW= 0 PPS=2
Killed
(Killed?! I didn't kill it).
>
> Note that etherload is monitoring the traffic on the ethernet by
> 'snooping', not really the traffic on your host's interface. In switched
> LAN environments, it has limited usage.
>
We run completely switched.
>
> > Ok, got it, but then how can I guarantee what the packet size is...
> >
> > I just used :
> >
> > device exp0
> > bw 30 50 70
> > pps 500 1000 1500
>
> Packet size cannot be guaranteed. Etherload is measuring bw by adding each
> packet's actual size and dividing by time.
>
Er... Maybe I won't use this... I had it running on the old machine,
figured we'd put it on the new one.
Tuc/TTSG Internet Services, Inc.
|