[cisco-voip] Cisco IP Communicator – Auxiliary VLAN

[Brian Meade]

Nick,

I've never heard of this being possible.  In order for that to work, IP
Communicator would need some sort of virtual NIC in order to get an address
in the voice VLAN.

I've always just added option 150 on data VLANs that were going to be using
IP Communicators.  Other option would be to create an MSI that has the TFTP
options pre-configured for the users as part of the install.

Brian


On Tue, Apr 22, 2014 at 12:53 PM, Nick Britt <nickolasjbritt at gmail.com>wrote:

>
> Hey Guys/Gals,
>
>
>
> I seem to be having a problem with an install of Cisco IP Communicator
> (8.6.3.0) not picking up the auxiliary  Voice VLAN configuration.
>
>
>
> In short we have the option 150 details listed on the voice vlans and not
> the data and I keep receiving a TFTP server not found error. But when these
> are manually set the phone registers fine (with the data vlan IP).
>
>
>
> As you can imagine this is not ideal as we do not want to add the option
> 150 to the data vlans if possible.
>
>
>
> Cisco’s documentation states that this should be possible.
>
>
>
> CDP
>
>
>
> Cisco IP Communicator uses CDP to communicate information such as
> auxiliary VLAN ID, per-port power management details, and QoS3
> configuration information with the Cisco Catalyst switch
>
>
>
> Switchport config
>
>
>
> interface gi 1/2
>
>  switchport access vlan 666
>
>  switchport mode access
>
>  switchport voice vlan 999
>
>  no snmp trap link-status
>
>  spanning-tree portfast
>
>  spanning-tree bpduguard enable
>  Anyone seen this before?
>
>
>
> --
> - Nick
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20140422/b9d3b872/attachment.html>