| 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 |
When I use Netview to query a rmon MIB object, I get "General fatal Error on agent message..." On the console connecting to the DECpacketprobe 90, when I do "get event.log", I found these error messages: mibmgr: MAX_LOOKUP_COUNT (200) exceeded mibmgr: MAX_LOOKUP_COUNT (200) exceeded What is this variable? How can I change it? Richard
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1187.1 | packetprobe firmware??? | ISIDRO::ELSA | Fri Jul 08 1994 11:31 | 51 | |
Hi,
I am studying today about packetprobe and just in this moment
I read this article from stars database COMM:
PRODUCT: Packetprobe90
SOURCE: Digital Equipment Corporation
SYMPTOMS/PROBLEM:
A management application such as Probewatch or Netview can no longer
communicate with the Packetprobe. The local console can be used but
shows no traffic being received.
When the module is power cycled, it gives the following error:
"agent fatal code 10 - fatal error in task main -
no space left for event log -free memory after boot would be xxx"
ANALYSIS:
The problem stems from the use of the MAX LOG parameter.
To clear it temporarily:
1. Enter command line mode from the local console.
2. At % prompt, type CLEAR NVRAM.
3. Power cycle the module.
4. Reconfigure the module: ip address etc.
5. Do not attempt to change the MAX_LOG parameter.
SOLUTION:
The next firmware release will include a fix for this problem.
Elsa Soengas
MCS Spain
| |||||