Hello,
I found a problem wih NAV portadmin configuration page for Juniper EX series
I ran wildcard changes to unused interfaces, and I disabled them manually with junos set command [ set interfaces <port number> disable ]
However, in the NAV portadmin page configuration, the port status of those interfaces is still enabled. (checkbox checked) Interface => NAV: enabled / JunOS: disabled
When I uncheck the enable checkbox, and save changes, the NAV portadmin page show disabled, and the port is still disabled in junos console. Interface => NAV: disabled / JunOS: disabled
If enable and save changes again into NAV, and the port is next enabled in console. Interface => NAV: enabled / JunOS: enabled
If I manually update the interface description with junos set command, and update NAV portadmin page, the description field is updated.
Does NAV run netconf or snmp checkings before showing the portadmin page, or it does only rely on last database readings for portadmin state ?
It makes some confusion, because we think the interface is enabled and working into NAV portadmin page, but it's not in reality.
Regards,
Ludovic FOUR SSI DR10 CNRS - Support Infoprox Pharma FRANCE
On Thu, 24 Mar 2022 16:12:49 +0100 (CET) "FOUR Ludovic (EXT)" ludovic.four@unistra.fr wrote:
I ran wildcard changes to unused interfaces, and I disabled them manually with junos set command [ set interfaces <port number> disable ]
I'm not too experience with Juniper, but are you enabling/disabling the physical ports, or the units? (e.g. ge-0/1/0 or ge-0/1/0.1 ?)
Does NAV run netconf or snmp checkings before showing the portadmin page, or it does only rely on last database readings for portadmin state ?
PortAdmin will always perform a live update of the switch port status before displaying its controls. For Juniper switches, the NAPALM/NETCONF backend will be used for this. However, there is no live update of the user interface while it being idly displayed. If the switch config changes while you have the PortAdmin web page open, you will need to reload the page to get the updated version.
However, I recall having observed some instances of web browsers caching the state of the form controls on page reloads, thereby overriding the new state sent as part of the HTML document. You could potentially try to rule this out by changing the switch config, then opening PortAdmin for that switch in a different browser/container/incognito mode.