T.R | Title | User | Personal Name | Date | Lines |
---|
2641.1 | DROP Event meaning ? | RDGENG::GREID | All that is, was and will be... | Tue Aug 15 1995 06:46 | 6 |
| As a further question to my last note what is the significance of the
DROPS field in the Segment Zoom screen. This is the only counter being
incremented with between 5-30 logged every polling interval and the
grand total at 2600 after an hour or so.
Giles.
|
2641.2 | Domains installed saved to a file .? | RDGENG::GREID | All that is, was and will be... | Tue Aug 15 1995 11:14 | 13 |
| It seems on investigating this further that the Probe itself is not at
fault here, rather that Probewatch(netscout) itself has remembered
(possibly written to a file somewhere), that the domain ALL is
listening for nothing and therefore the utilization is 0%, and that all
we are seeing is Drop Events.
We think this is the case, eg that the settings have been written to a
file as we have tried another Probe in the originals place and it does
the same, but works elsewhere.
Can anyone help with this, please ...???
Giles.
|
2641.3 | | RDGENG::GREID | All that is, was and will be... | Tue Aug 15 1995 12:26 | 5 |
| Just in case anyone does look at this, HINT, HINT.... it seems that
if we fire a Domain Manager Install to the ALL domain for any of our
Probes now we get 0 values for everything now.....
Giles.
|
2641.4 | | RDGENG::GREID | All that is, was and will be... | Wed Aug 16 1995 08:09 | 4 |
| Will somebody please be kind enough to let me know the Product Manager
for Probewatch as we need an urgent fix for this problem...
Giles.
|
2641.5 | Try contacting P.M. Jack Forrest NAC::FORREST | NETCAD::BATTERSBY | | Wed Aug 16 1995 10:12 | 1 |
|
|