T.R | Title | User | Personal Name | Date | Lines |
---|
4952.1 | | MOLAR::YAHEY::BOSE | | Mon Apr 26 1993 10:55 | 7 |
|
You can increase the timeout and retry values for the IP Poller
through the window that pops up when you launch the application.
Can you also check if the command "TEST SNMP entity" returns
successful status from FCL.
Rahul.
|
4952.2 | ??? | CSOADM::ROTH | you just KEEP ME hangin' on... | Mon Apr 26 1993 12:55 | 4 |
| Is the IP poller part of V1.2 DECmcc? The title of .0 says "IP Poller"
but the text inside says it is V1.2.
Lee
|
4952.3 | | MOLAR::YAHEY::BOSE | | Mon Apr 26 1993 15:26 | 5 |
|
The IP Reachability Poller was shipped only with V1.3. It will
run at all with V1.2.
Rahul.
|
4952.4 | My fault.. | PLUNDR::LOWEG | You don't want to do it like that!! | Tue Apr 27 1993 06:20 | 13 |
|
Sorry about the confusion. The customer is using the V1.2 way of
checking reachability of IP devices by manually writing alarm rules to
do this.
I have checked using my V1.3 set up and have found that a the timeout
is configurable when you enable the new IP polling.
What I need to know is if there is a way to increase the timeout using
the alarm rule way of checking reachability of IP devices. In note
4819.2 seems to be on the ball for vms but how can this be done for
Ultrix ???
Gary Lowe NUK CSC comms..
|
4952.5 | | MOLAR::YAHEY::BOSE | | Tue Apr 27 1993 10:39 | 7 |
|
On Ultrix you would modify the shell script exactly the same
way the DCL command file has been modified on VMS (as explained
in note 4819). I don't know if anyone has done the actual work
for Ultrix.
Rahul.
|
4952.6 | Oh dear, no can do, unless... | PLUNDR::LOWEG | You don't want to do it like that!! | Fri Apr 30 1993 08:04 | 10 |
|
On closer inspection of all the notes avaialable it looks as though the
answer is in note 4563.3 which says "it is not solvable with v1.2
unless using occurs_n_times rules and wasting rules entries and cpu
to do it".
Thanks for all your help now I will try and talk the customer into
upgrading to V1.3 to use the IP Poller.
Gary Lowe NUK CSC comms.
|
4952.7 | Some inputs | ZUR01::SCHNEIDERR | | Mon May 03 1993 03:44 | 18 |
| Gary,
We had here the same problems. Now we use V1.3. The same as before. I checked
the problem with the analyzer.
The IP-POLLER V1.3 sends out his polls, lets say 100 ICMP requests. All requests
are answered in about 2-6 ms. The workstation catches all request (there is a
counter for ICMP ECHOS RECEIVED). But DECmcc only catches about 50. I work on
this problem (Rahul is kindly helping us, via mail).
Our workarround is to set the retries to 3 and the timeout to 2 seconds. So the
poller catches the first time 50 of our 100 ICMP requests. after 2 seconds, he
polls the other 50 again. MCC catches 30, after 2 seconds the poller polls the
other 20 ....... nice, isn't it? But we can use it!!!! As a workarround, not
a fix.
Roland
|