Hi,
we are looking into using NAV with Cisco IP-Phones (8841/8851 series) and while trying the feature we realized the config put on the port doesn¹t use the cisco proprietary settings but sets the port into trunk. What we want to achieve is using an additional voice-vlan on the port like::
Switch(config)#interface range fastethernet 0/1 - 2 Switch(config-if)#switchport mode access Switch(config-if)#Switchport access vlan 50 Switch(config-if)#switchport voice vlan 10
As stated by Morten via IRC this has not been implemented yet also due to the fact that they lack the devices to test on. I wanted to ask if it was possible to implement this so it becomes part of the main NAV tree. We could fund this development and help with the testing. Maybe you could also give an estimate on how much work this would be?
Thanks in advance, Mischa
On Tue, 8 Sep 2015 12:17:44 +0000 Mischa Diehm mischa.diehm@unibas.ch wrote:
we are looking into using NAV with Cisco IP-Phones (8841/8851 series) and while trying the feature we realized the config put on the port doesn¹t use the cisco proprietary settings but sets the port into trunk.
That is correct. The current implementation is a vendor-agnostic one, as requested by some of our customers with heterogenous VoIP equipment.
What we want to achieve is using an additional voice-vlan on the port like::
Switch(config)#interface range fastethernet 0/1 - 2 Switch(config-if)#switchport mode access Switch(config-if)#Switchport access vlan 50 Switch(config-if)#switchport voice vlan 10
As stated by Morten via IRC this has not been implemented yet also due to the fact that they lack the devices to test on.
Mostly, its because there hasn't been much demand for the functionality.
We have had the same type of request from a customer in the health sector, but being in the health sector means everything is kind of closed off and sensitive, so they could not provide any kind of testbed.
I wanted to ask if it was possible to implement this so it becomes part of the main NAV tree. We could fund this development and help with the testing. Maybe you could also give an estimate on how much work this would be?
As far as I understand, John-Magne thinks this would not be too much work, given access to a proper testbed. He would have to be the one to offer an estimate, I think, since Portadmin is mostly under his control.
As for your funding offer: Thank you :) I know my higher-ups are interested in alternative ways of funding NAV development; I have forwarded your e-mail to relevant contacts within UNINETT, but am still awaiting a proper response.
Any further technical discussion is on-topic for this list (or maybe nav-dev), everything else should probably be kept off it.
-- Morten Brekkevold UNINETT
Any opinions on this - positive or negative?
thx, Mischa
On Thu, 8 Oct 2015 14:08:40 +0000 Mischa Diehm mischa.diehm@unibas.ch wrote:
Any opinions on this - positive or negative?
Yes, Mischa.
Still waiting for your followup to my reply from 16th september.
This is doable, with your help. We can discuss technical details on-list. I will send you an off-list email about the economical side of things.
Hi!
On 08. sep. 2015 14:17, Mischa Diehm wrote:
Hi,
we are looking into using NAV with Cisco IP-Phones (8841/8851 series) and while trying the feature we realized the config put on the port doesn’t use the cisco proprietary settings but sets the port into trunk. What we want to achieve is using an additional voice-vlan on the port like::
Switch(config)#interface range fastethernet 0/1 - 2 Switch(config-if)#switchport mode access Switch(config-if)#Switchport access vlan 50 Switch(config-if)#switchport voice vlan 10
As stated by Morten via IRC this has not been implemented yet also due to the fact that they lack the devices to test on. I wanted to ask if it was possible to implement this so it becomes part of the main NAV tree. We could fund this development and help with the testing. Maybe you could also give an estimate on how much work this would be?
We need a way to tell NAV the vlan number. This is done using the Portadmin config-file today. In the web-interface you just tick a checkbox to enable the voice vlan.
If you want to enable a specific voice vlan from the web-interface, for instance by using a drop-down or similar, then we need to do bigger changes. If not, the changes to the web-interface should be minimal.
We also need to tell NAV to use the Cisco proprietary commands. This is a config option.
If much of the existing web-interface for enabling voice vlan can be used, I reckon using a day for implementing and adapting the back- and frontend and then we send you a patch for local testing. If that succeeds, we add it as a part of NAV.
What makes this uncertain is the SNMP-support for this on Cisco devices. If everything is supported uniformly then we're ok. If not, then the estimate is N/A. Crossing fingers! =)
Sincerely
-
John Magne Bredal -
Mischa Diehm -
Morten Brekkevold