[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
|
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
1013.0. "Packet probe problems" by COMICS::BUTT (Give me the facts real straight.) Fri May 20 1994 12:37
The following is from a first time packetprobe 90 V1.0 customer..
My comments are marked ">"
When I attempt to register the probe into DECmcc I get an error
message on the probe console :
snmp_age: create_identical SNMP error
The DECmcc registration times out, and the probe is partially
registered. Once this has occurred, the RMON MIB is NOT
automatically associated with the probe as I would have expected.
I can only get characteristics/counters/status etc at the
SNMP entity (top level) and at the SNMP Interface levels. (i.e
IP, TCP, UDP etc do not return anything)
> This reproducable in house, what does this error mean ?
> Any error message documentation anywhere?
Our Operations people also have a Spider Manager SNMP system
which fails to recognise the probe as an RMON device - similar
to DECmcc, the Spider Manager can only pull stats on the Ethernet
Interface. When a data capture was attempted, there was an error
on the probe console:
alloc_bucket: malloc failed
> This looks like a firmware bug in the probe. Has this been seen before?
The Spider manager returned "couldn't allocate packet buffer"
We also noticed from both DECmcc and the Spider manager that
the IfInUnknownProtos counter is more-or-less following the
IfInNUcastPkts counter. (i.e. it seems to be saying that almost
all multicast packets are unknown protocol !!!)
> I have not checked this.
In summary, it looks very much like the probe is NOT RMON
compliant.
> An unhappy customer.
> What is the function of the front panel LEDs ? The documentations says
> Power OK - this works fine
> Network activity - only works after the IP address has been set and the
> system power cycled.
> Network OK - Seems not to light, but will flash under some error
> conditions.
> Please can I have some explanation of these LEDs.
Richard
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1013.1 | note 842 same problem | UTRTSC::VDCRUIJSEN | | Thu May 26 1994 06:30 | 11 |
| Hello
See note 842.8 same problem, seems to be a firmware problem and fixed in 1.1
When will 1.1 become available???
What I don't understand is: people are working with MCC and the PacketProbe and
I can't register it, whats the difference
Gerrit
|