Anyone using the Cisco 300 Series switches? Unable to get Auto Voice VLAN to work
Im playing with a SG300-10MP in a lab for a potential client purchase.
I am unable to get the Auto Voice VLAN function to work correctly.
I have set the “user ports” as untagged for VLAN 20 (data vlan)
Under VLAN Management -> Voice VLAN -> Properties, I have defined VLAN 30 as the voice vlan and enabled the auto voice vlan with activation immediate. CDP and LLDP are all configured (defaults). Smartport features are all defaults.
I have connected two IP Phones – a 7941 and and a 7940. Both draw an IP address from the attached router (port 9 on the switch is configured as a trunk up to a router running DHCP) – but an IP address out of the data VLAN. As they don’t get an Option 150 address, they don’t register.
When I look at the Smartport Interface settings for ports 7 and 8, it indicates Smartport Application Method is disabled as the Smartport Type is Unknown.
I also attached a regular laptop to Port 5 on the switch. It drew a data vlan IP address and it too showed up as Smartport Type Unknown
So, I ran the diagnostics on the two ports to which the IP phones were attached. The macro is failing at the line
So, this makes sense to me. The macro is not applying the voice vlan to the switchport, hence the phone is not getting the correct vlan and thus not getting the correct dhcp scope and tftp service IP address.
So, the question is, why is the macro failing?
I go back to the Voice Vlan properties page and confirm that I have 30 set for the voice vlan and that I have applied the change. The page shows that the operational status of the voice vlan is 30.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.