Hello,
I just forgot to reply to all, my bad sorry
I leave all the comments below
I took a look into ipdevpoll.log
When I'm updating a port, there is new [INFO schedule.netboxjobscheduler] line into ipdevpoll log, means that the scheduler is doing fine.
I still have the same issue with portadmin enabled checkbox :
if you uncheck enabled box, save, then reload page, the checkbox goes back to checked, and remains in this state. - but it updates the interface - (disabled)
I've made some setup to portadmin.conf, and changed link_edit = false (better not cut the tree branch where you are sitting on) but I don't think it's related to.
Regards,
Ludovic
----- Mail original -----
De: "Morten Brekkevold" <morten.brekkevold(a)sikt.no>
À: "FOUR Ludovic / PHA" <ludovic.four(a)unistra.fr>
Envoyé: Vendredi 1 Avril 2022 14:39:19
Objet: Re: wrong Port configuration status for juniper device if port manually disabled
On Thu, 31 Mar 2022 09:24:46 +0200 (CEST) "FOUR Ludovic (EXT)" <ludovic.four(a)unistra.fr> wrote:
> I only disable the physical port in this case.
Hi Ludovic,
did you intentionally leave the mailing list out of your reply?
> I did that, but there's no update even when I close Chrome or firefox
> (did some tests on both). I tried by clearing firefox/chrome cache
> too. The interface status still remains checked (enable) in portadmin
> web page.
Then I need to do some testing on our own equipment in an attempt to
reproduce this. I'll have to get back to you.
> I also have some update problem with aggregated interfaces (aeX)
> created with Junos Console. NAV can detect the aeX interface when I
> create it. But still remains when I remove it. I can't see the
> physical interfaces that were previously members of the aggregated
> interface in the physical ports list anymore.
What ports NAV knows about is only updated by the inventory job, which
runs every 6 hours. However, ipdevpoll does show some restraint from
deleting any interface as soon as it appears missing (some devices can
be wonky) - it actually marks it internally with a "missing since"
timestamp, and removes it only when it remains missing after certain
amount of time. I don't recall the exact amount, but I'm guessing 24
hours.
> Maybe a SSL cache issue on server side ?
> I'm using standard apache mod ssl settings
> SSLSessionCache shmcb:${APACHE_RUN_DIR}/ssl_scache(512000)
> SSLSessionCacheTimeout 300
No, this is unrelated to content caching.
--
Sincerely,
Morten Brekkevold
Sikt – Norwegian Agency for Shared Services in Education and Research