Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Data and Voice VLAN (Jeremy Bresley)
2. Re: Data and Voice VLAN (Charles Goldsmith)
3. Re: Data and Voice VLAN (Nikolaos Milas)
4. Re: Data and Voice VLAN (Oliver Gorwits)
--- Begin Message ---
On 3/4/2015 2:58 PM, Oliver Gorwits wrote:
Hi Emma,
On 2015-03-04 16:20, Cardinal-Richards, Emma wrote:
We have instances where we have a (cisco) phone connected to a port
and then a PC via that phone. So the port configuration has a
switchport access vlan and a voice vlan.
I do know that Cisco's voice vlan feature is a little funky, but it's a
long time since I've looked at how Netdisco handles it. Doesn't surprise
me that something isn't right (tho if anyone with similar config reads
this and has different output in ND2 - please pipe up, otherwise I
assume what Emma reports is standard behaviour).
Netdisco appears to only
show the data vlan when you look at a switch port vlan membership.
Is
there a known way to get it to show the voice vlan in addition under
VLAN membership? It does mention the vlan if connected nodes is
selected, you see a phone symbol, its MAC/IP address and in brackets
'on vlan xxx' where xxx is the voice vlan.
So the data comes from two places, which might explain the difference.
Associated with the Node is a VLAN that is stored when we do per-VLAN
MAC address table retrieval. With the Device Port is associated a set of
tagged VLANs and this seems to be missing the voice VLAN - but I suspect
the device isn't actually reporting it in the place we're looking.
There's a special table for the voice VLANs, which SNMP::Info (inside
Netdisco) supports: vmVoiceVlanId. What I guess the Cisco device class
code should do is merge this with the Device Port VLAN table to get the
complete picture.
Emma, please can you post the output of this command on one of the
devices where you see the issue:
~netdisco/bin/netdisco-do show -d <IP-of-device> -e i_voice_vlan
Everyone else - please squeak if you think it's a really bad idea to
merge vmVoiceVlanId with vlanTrunkPortVlansEnabled* (looks like a bunch
of other things are already merged on Cisco anyway, such as dynamic
VLANs). I reckon most network engineers would think of the voice VLAN as
a tagged VLAN and expect to see it in the VLAN Membership column.
Our normal config is to have on the end user ports:
switchport mode access
switchport access vlan 10
switchport voice vlan 20
ND2 (2.031000 with SNMP::Info 3.18) shows this when I look at an end
user port:
<http://omac-netdisco:5000/report/portlog?q=10.66.47.130&f=GigabitEthernet0%2F8> GigabitEthernet0/8
<http://omac-netdisco:5000/device?c_nodes=on&n_ip=on&age_num=3&c_pvid=on&c_port=on&n_ssid=on&c_vmember=on&n_netbios=on&return_url=%2Fajax%2Fcontent%2Fdevice%2Fports%3Ftab%3Dports%26q%3Dausctx-acc-sw03.net.intranet.hdr%26prefer%3D%26f%3D%26c_port%3Don%26c_name%3Don%26c_pvid%3Don%26c_vmember%3Don%26c_nodes%3Don%26c_neighbors%3Don%26age_num%3D3%26age_unit%3Dmonths%26port_state%3Dup%26port_state%3Dfree%26port_state%3Ddown%26port_state%3Dshut%26mac_format%3DIEEE%26n_ip%3Don%26n_netbios%3Don%26n_ssid%3Don&port_state=up&port_state=free&port_state=down&port_state=shut&c_neighbors=on&mac_format=IEEE&c_name=on&tab=ports&age_unit=months&q=ausctx-acc-sw03.net.intranet.hdr&f=GigabitEthernet0%2F8&prefer=port>
Gi0/8
10 <http://omac-netdisco:5000/search?tab=vlan&q=10> 10
<http://omac-netdisco:5000/search?tab=vlan&q=10> 10.66.40.4 - Port1
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=10.66.40.4>
1c:e8:5d:c8:48:6f
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=1c%3Ae8%3A5d%3Ac8%3A48%3A6f>
10.66.40.4
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=10.66.40.4>
64:51:06:a2:13:c7
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=64%3A51%3A06%3Aa2%3A13%3Ac7>
10.66.16.99
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=10.66.16.99>
10.66.32.54
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=10.66.32.54>
1c:e8:5d:c8:48:6f
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=1c%3Ae8%3A5d%3Ac8%3A48%3A6f>
(on vlan 20)
10.66.40.4
<http://omac-netdisco:5000/search?tab=node&stamps=checked&q=10.66.40.4>
If you look at the MAC table, the phones initially come up on Vlan10,
then get the voice vlan via CDP and switch to Vlan20, hence why you see
the same MAC on both VLANs.
This is on a 3560X running 15.0(2)SE4 code, we see the same behavior on
our 3560Gs and 4500E's as well, all running some variant of 15.X code.
Jeremy "TheBrez" Bresley
b...@brezworks.com
--- End Message ---
--- Begin Message ---
Depends on what switch she has and the mibs I'm sure.
Emma, what type of switch is it?
On Wed, Mar 4, 2015 at 1:58 PM, Oliver Gorwits <oli...@cpan.org> wrote:
> Hi Emma,
>
> On 2015-03-04 16:20, Cardinal-Richards, Emma wrote:
> > We have instances where we have a (cisco) phone connected to a port
> > and then a PC via that phone. So the port configuration has a
> > switchport access vlan and a voice vlan.
>
> I do know that Cisco's voice vlan feature is a little funky, but it's a
> long time since I've looked at how Netdisco handles it. Doesn't surprise
> me that something isn't right (tho if anyone with similar config reads
> this and has different output in ND2 - please pipe up, otherwise I
> assume what Emma reports is standard behaviour).
>
> > Netdisco appears to only
> > show the data vlan when you look at a switch port vlan membership.
> > Is
> > there a known way to get it to show the voice vlan in addition under
> > VLAN membership? It does mention the vlan if connected nodes is
> > selected, you see a phone symbol, its MAC/IP address and in brackets
> > 'on vlan xxx' where xxx is the voice vlan.
>
> So the data comes from two places, which might explain the difference.
> Associated with the Node is a VLAN that is stored when we do per-VLAN
> MAC address table retrieval. With the Device Port is associated a set of
> tagged VLANs and this seems to be missing the voice VLAN - but I suspect
> the device isn't actually reporting it in the place we're looking.
>
> There's a special table for the voice VLANs, which SNMP::Info (inside
> Netdisco) supports: vmVoiceVlanId. What I guess the Cisco device class
> code should do is merge this with the Device Port VLAN table to get the
> complete picture.
>
> Emma, please can you post the output of this command on one of the
> devices where you see the issue:
>
> ~netdisco/bin/netdisco-do show -d <IP-of-device> -e i_voice_vlan
>
> Everyone else - please squeak if you think it's a really bad idea to
> merge vmVoiceVlanId with vlanTrunkPortVlansEnabled* (looks like a bunch
> of other things are already merged on Cisco anyway, such as dynamic
> VLANs). I reckon most network engineers would think of the voice VLAN as
> a tagged VLAN and expect to see it in the VLAN Membership column.
>
> regards,
> oliver.
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
--- End Message ---
--- Begin Message ---
On 4/3/2015 10:58 μμ, Oliver Gorwits wrote:
I do know that Cisco's voice vlan feature is a little funky, but it's a
long time since I've looked at how Netdisco handles it. Doesn't surprise
me that something isn't right (tho if anyone with similar config reads
this and has different output in ND2 - please pipe up, otherwise I
assume what Emma reports is standard behaviour).
We are using Cisco switches with Avaya IP Phones. Voice VLAN is 100.
Here is how it shows in ND2:
The nodes are both Avaya IP phones (not shown as such - would be nice if
they were!) and the VLAN Membership column does not show VLAN 100 (it
would be nice if it did). Nodes (phones) are listed correctly as being
on VLAN 100:
So in our case, Cisco-Avaya, Emma's report is accurate. (Only that in
our case, no phone symbol is displayed...)
All our phones (Avaya models 96xx and 16xx) have MAC addresses starting
with: 00:1b:4f:
Nick
--- End Message ---
--- Begin Message ---
On 2015-03-04 22:36, Nikolaos Milas wrote:
So in our case, Cisco-Avaya, Emma's report is accurate. (Only that in
our case, no phone symbol is displayed...)
To this point only, it's on the TODO list:
https://sourceforge.net/p/netdisco/netdisco2/110/
So it would help me to see the output of these on one of your Cisco
switches:
~netdisco/bin/netdisco-do show -d <IP-of-device> -e c_cap
~netdisco/bin/netdisco-do show -d <IP-of-device> -e c_platform
regards,
oliver.
--- End Message ---
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
