| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Greetings,
I am having some trouble with an exporting function.
System detils:
VAX 400 Model 60
72Mb RAM
VMS 5.5-2
DECmcc V1.3.0
I have a domain with about 100 SNMP Interface entities that I want to
export on. I have started the export background process off with a
delay of 30 sec (default) and have started exporting on SNMP * Int *.
I have also increased UDP and ICMP timeouts and retries in the
exporting process to 15 sec and 3 retries. The error message that I
gety back after exporting has started on about 20 entities is:
request queue is full. check background process status
The job just hangs. The background process has not died, but appears to
have frozen.
Ideas appreciated.
Reece Boucher
Adelaide, Australia
PS The delay parameter that can be specified when submitting
MCC_EXPORTER_BACKGROUND.COM is the number of seconds between multiple
requests. Is this value the delay between requests going "out onto the
wire", or between requests being processed locally, ie into the
database ? Where is it preventing performance problems ?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5497.1 | SISE::SAM | Wed Aug 18 1993 18:15 | 33 | ||
> I have a domain with about 100 SNMP Interface entities that I want to
> export on. I have started the export background process off with a
> delay of 30 sec (default) and have started exporting on SNMP * Int *.
> I have also increased UDP and ICMP timeouts and retries in the
> exporting process to 15 sec and 3 retries. The error message that I
> gety back after exporting has started on about 20 entities is:
>
> request queue is full. check background process status
>
> The job just hangs. The background process has not died, but appears to
> have frozen.
Did you try to export just one snmp interface? Did it work?
When the exporter uses the new database, firstly it creates a table
which is time consuming operation. Probably this is a reason why
request queue was full. To verify this you can start an exporting
for one interface. After you see at least one successfull poll
delete this request and start exporting for SNMP * INTERFACE *.
It should work.
> PS The delay parameter that can be specified when submitting
> MCC_EXPORTER_BACKGROUND.COM is the number of seconds between multiple
> requests. Is this value the delay between requests going "out onto the
> wire", or between requests being processed locally, ie into the
> database ? Where is it preventing performance problems ?
This is a delay between mcc_calls from the Exporter to the SNMP AM.
SAm
| |||||
| 5497.2 | Database is not new | ADO75A::BOUCHER | Wed Aug 18 1993 20:13 | 6 | |
SAm,
The database is one that has been used extensively previously. I will
try your suggestions, though.
Reece.
| |||||