I dont know if it is switch or phone related. We have a few 7940 and 7960 phones at one location that will not get their vlan information from the switch. I have tried several things including turning the port into a trunk, and still the phone gets its IP information from the data vlan. Now here is the weird part, the arp table on the router will show that is has the IP address from the voice vlan, and the dhcp pool shows the bindings, yet CDP neighbor detail shows it has an IP from the data side.
Device ID: SIP0015634D2A9A
IP address: 192.168.10.180
Platform: Cisco IP Phone 7960, Capabilities: Host Phone
Interface: FastEthernet0/47, Port ID (outgoing port): Port 1
Holdtime : 177 sec
advertisement version: 2
Power drawn: 6.300 Watts
Internet 10.64.9.111 3 0015.634d.2a9a ARPA FastEthernet0/1.2
If I remove switchport access vlan 3 from the port, the phone gets the IP from the DHCP pool and registers, but I am unable to pull up the web interface of the phone. I can add switchport access vlan 2 back in, and if a PC is plugged in, it goes back to where it was before.
One other item, may or may not be related, I get constant trust resets from all the phones,
*Mar 1 20:03:30.687: %SWITCH_QOS_TB-5-TRUST_DEVICE_LOST: cisco-phone no longer detected on port Fa0/4, port set to untrusted.
*Mar 1 20:03:36.937: %SWITCH_QOS_TB-5-TRUST_DEVICE_DETECTED: cisco-phone detected on port Fa0/2, port trust enabled.
I think c3560-ipbasek9-mz.122-25.SED1.bin is the latest, it was upgraded to see if it was IOS related, Maybe version related? it has IP base in it, but I found some of our others are advipservices. This is the first time we have encountered this on any 3560 switch.
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.