next »

[rufer]

We use a lot of (Siemens) IP telephones that use a seperate voice VLAN. A typical cisco IOS port config would look like that:

inter fa 0/1
 description xyz
 switchport mode access
 switchport access vlan 2
 switchport voice vlan 223
 spanning-tree portfast

Technically speaking, this is a 802.1q trunk with a native VLAN 2 (untagged) and the VLAN 223. The telephone gets its voice vlan ID through vendor specific DHCP options on the native VLAN. The phone will then use the VLAN tag 223 for all its communications and the access VLAN 2 will be used for the PC connected to the integrated switch of the phone.

Nedi discovers phones and PCs correctly as nodes, with the correct VLAN info, that's fine. But on interface level, Nedi doesn't know anything about the voice VLAN, as example in devices-interfaces or devices-status
--> I would like to have some sort of support for the voice VLAN, such that I can as example search for interfaces in voice VLAN 223.

Don't know if and how this is applicable for other manufacturers, though. Cisco uses Voice VLAN for their phones, too, but it is assigned through CDP or LLDP.

Greetings
Rufer

[oxo]

We use a lot of (Siemens) IP telephones that use a seperate voice VLAN. A typical cisco IOS port config would look like that:
Greetings
Rufer

I have the same problem with Nortel IP phones that I'm starting to look at: been a year since I updated my nedi anyway ...

(Nortel IP Sets: voice vlan by either DHCP or LLDP)

[rickli]

This OID is supposed to show which ports are tagged in a vlan:

1.3.6.1.2.1.17.7.1.4.2.1.4.0

It returns a port/bit pattern for each vlan (e.g. vlan 2 is tagged on port 7,8 and 9):


1.3.6.1.2.1.17.7.1.4.2.1.4.0.1 = Hex-STRING: FF C0 00 00 00 00 00 00 00 00
1.3.6.1.2.1.17.7.1.4.2.1.4.0.2 = Hex-STRING: 03 80 00 00 00 00 00 00 00 00


The only problem, this works on a HP switch for example, but Cisco uses the VTP Mib, which I haven't had time to look at yet...