[c-nsp] Data VLAN/Voice VLAN

[Geoffrey Pendery]

The TAC engineer I asked for configuration help found this link for me
(I feel dumb being simply out-Googled, but appreciative that he went
outside Cisco-only docs and actually found me good interop info)

http://www.avaya.de/emea/de/resource/assets/applicationnotes/CSCO_LLDP-MED.pdf

On the access ports, we have:
 switchport
 switchport host
 switchport access vlan 100
 switchport voice vlan 400

And globally all I had to turn on was "lldp run"

We do connect workstations through the phone's built-in switch, and we
do use the separate data and voice VLANs.  Operationally, we're
serving the DHCP options to the phones (a big string of variables in
option 176) but in the lab I verified the phone would receive and use
the voice and data VLANs separate via LLDP parameters, without help
from DHCP.

The only thing I noticed missing was the precise power info.  AF power
determines that the phone is class 2, so it allocates 7.9 Watts from
the PS, but if CDP was there (or the Power TLVs in LLDP were open
standard, instead of Avaya Propreitary) then it would get the more
precise consumption (say 6.2 Watt) and be able to allocate more phones
out of the same PS.

Other than that, seems to work like a charm.  We get lots of good info
from the phones via LLDP.


-Geoff


On Mon, Aug 31, 2009 at 8:58 AM, Andrew Gallo<akg1330 at gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Would you mind sharing your IOS config, DHCP options, phone version &
> settings file?
>
> I've had varying success with Avaya and Cisco LLDP.
>
> Then again, I'm using SIP loads on the phones.
>
> Thanks.
>
>
>
> Geoffrey Pendery wrote:
>> "A compatible device (i.e. one the presents itself as a phone via CDP)
>> would activate the voice VLAN and thus allow tagged incoming traffic
>> on VLAN 66. This requires the switch (and port) to have CDP enabled by
>> the way."
>>
>>
>> Can also be done with LLDP, should you have non-Cisco IP phones.  I
>> can vouch for 4500's and Avaya IP phones speaking LLDP to each other.
>>
>>
>> -Geoff
>>
>>
>> On Fri, Aug 28, 2009 at 5:43 PM, Peter Rathlev<peter at rathlev.dk> wrote:
>>> On Fri, 2009-08-28 at 15:20 -0700, Yuri Bank wrote:
>>>> interface FastEthernet0/4
>>>>  description phone
>>>>  switchport access vlan 77
>>>>  switchport trunk native vlan 55
>>>>  switchport mode access
>>>>  switchport voice vlan 66
>>>>
>>>> In this configuration, data is placed on vlan 55? From what I've read
>>>> on other forums and such is that the data would be on the configured
>>>> access vlan ( 77 ). Unfortunately I do not have an iphone to test
>>>> this. Could anyone give me some clarity?
>>> Untagged traffic on the port would be VLAN 77, since this is what you
>>> configured at access VLAN and since the port is in forced access mode.
>>>
>>> A compatible device (i.e. one the presents itself as a phone via CDP)
>>> would activate the voice VLAN and thus allow tagged incoming traffic on
>>> VLAN 66. This requires the switch (and port) to have CDP enabled by the
>>> way.
>>>
>>> The trunk configuration is ignored when you issue "switchport mode
>>> access".
>>>
>>> If you only need a stand-alone phone you can just use a simple access
>>> port in the voice VLAN.
>>>
>>> Regards,
>>> Peter
>>>
>>>
>>> _______________________________________________
>>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkqb1vcACgkQQr/gMVyFYyTa/gCcDNV9xBQF5p+2pR1L5lgKf2Tp
> 54kAniLjnhkcI2We/Gd+Szlil9oFBnL1
> =+bFG
> -----END PGP SIGNATURE-----
>