On Mon, 3 Apr 2023 11:56:52 +0200 (CEST) "FOUR Ludovic (EXT)" ludovic.four@unistra.fr wrote:
When I activate VOIP to the interfaces directly in JunOS console (1) , It will create two separate configurations on the device:
- Interface configuration with port-mode ACCESS and vlan XXXX (not the VOIP vlan)
- a VOIP configuration with all "voIP" interfaces (command: show ethernet-switching-options voip )
However, NAV see this interface has a trunk port, with a native vlan YYYY and a trunk vlan corresponding to voIP vlan.
I
Indeed, as mentioned in https://nav.readthedocs.io/en/latest/reference/portadmin.html#more-about-voi... , PortAdmin's basic voice vlan functionality is generic and independent of vendor implementations: It only uses regular 802.1q configuration to achieve a voice VLAN configuration, across any type of switch.
In addition, it has a separate voice vlan mode for Cisco-based users (as switched on using the `cisco_voice_vlan` setting in `portadmin.conf`).
Question is : How can we manage multiple VoIP vlans for Juniper with NAV ? It is possible to activate voIP on interface, by adding some button in portadmin page (for example) ?
It seems Juniper has a specific way of configuring VoIP, supported by its configuration language, but this is something PortAdmin does not (currently) support.
It seems to me that you enabled VoIP configuraton on a Juniper switch and this somehow prevents NAV's generic trunk-based voice vlan configuration from working, as the configuration is tries to apply is rejected by the switch.
(1) Depending on JunoS Version the command is
- set ethernet-switching-options voip interface <interface number> vlan <voIP vlan ID>
- set switch-options voip interface <interface number> vlan <voIP vlan ID>
In order to support Juniper VoIP commands, the PortAdmin's Juniper management handler needs to change:
https://github.com/Uninett/nav/blob/72a94dbd973047f5a4f6327f4c4448d051381983...
The class needs to override at least the set_interface_voice_vlan()` method defined in the superclass:
https://github.com/Uninett/nav/blob/72a94dbd973047f5a4f6327f4c4448d051381983...
We haven't used VoIP units in years (all our VoIP-ing these days is through desktop applications or cellphones), so I'm not sure we would be able to develop and test such a feature ourselves. Not sure if our old lab switches support VoIP configuration.