T.R | Title | User | Personal Name | Date | Lines |
---|
4563.1 | re .-1 | ANOVAX::COMFORT | Cold iron shackle, ball & chain | Thu Feb 18 1993 14:54 | 10 |
|
This problem has been discussed before. I have circumvented the issue
by checking an impossible situation, ie. the ethernet interface being
down (if it is down, we can't talk to it) and generating an exception.
My situation occurred running MCC on the VMS platform. I felt that the
problem was caused by pings not refreshing the ARP cache and
eventually the cache times out.
Dave
|
4563.2 | But on ULTRIX? | ZUR01::SCHNEIDERR | | Fri Feb 19 1993 03:33 | 10 |
| Yes,
But on ULTRIX it must be a leak or a bug somewhere. MSU does it o.k., but on
MSU you have the possibility to set a reply counter, so you start a notification
onli after i.e 2 or 3 pings.
With MCC V1.2 you can't do that. So the PING gets lost somewhere. ON VMS maybe
in your ARP cach and on ULTRIX ??????
Roland
|
4563.3 | it works ok with the IP Poller of V1.3 | TLSE01::SELLES | Pierre-Jean - Toulouse -France | Fri Feb 19 1993 12:05 | 12 |
|
see note 4474 ;
it is not solvable with v1.2 unless using occurs_n_times rules
and wasting rules entries and cpu do do it .
i tested the Ip poller of V1.3 and it works perfectly with no rule entry
to waste and a background process doing all the work ( this is an ultrix version)
cdmlt
PJ
|
4563.4 | | ZUR01::SCHNEIDERR | | Thu Feb 25 1993 02:21 | 7 |
| PJ,
I thought to wait until V1.3 with the IP poller function. I told that to the
customer. He is agree and we will wait. So lets hope we will get the V1.3
version very soon.
Thanks Roland
|