[cisco-voip] 7960 PC port

[Justin Steinberg]

As for this...

> Sometimes phones get stubborn or new phone have that picky MFG phoneload
> that for some reason doesn't like to DHCP on the right VLAN, etc and
> configuring the switchport as an access port in just the voice VLAN
> (switchport access vlan voice#, and no switchport voice vlan command) gets
> the phone up and working and it upgrades to the current phoneload on the
> system then you can set the port back to your normal config with data and
> voice vlan and it'll be happy from that point on and work as expected.

In my experience the cause of this is having the voice vlan
configuring on the switchport to the DATA vlan DHCP server.  Something
to do with how the MFG / bootstrap firmware works and having a NIC on
your DATA vlan DHCP server that doesn't support dot1q tagging.  If you
remove the voice vlan from that interface everything works.

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a008055c1fe.shtml

Justin



On 3/31/06, Erick Bergquist <erickbe at yahoo.com> wrote:
>
>
> It depends :)    You can disable cdp globally on some hardware (no cdp run)
> and per interface on some (no cdp enable). It's something I normally don't
> do so not sure of all the commands across all the products.
>
> As far as access-port vs trunk, both work..so the answer is, it depends on
> what you're doing, the network, etc. I prefer the access-port method as it's
> not really a full-trunk and thus less traffic going to phone and some phone
> models and phoneloads had issues with un-needed traffic being sent to them.
>
> Sometimes phones get stubborn or new phone have that picky MFG phoneload
> that for some reason doesn't like to DHCP on the right VLAN, etc and
> configuring the switchport as an access port in just the voice VLAN
> (switchport access vlan voice#, and no switchport voice vlan command) gets
> the phone up and working and it upgrades to the current phoneload on the
> system then you can set the port back to your normal config with data and
> voice vlan and it'll be happy from that point on and work as expected.
>
> On this one where the phone won't come up, is their available DHCP addresses
> to dish out? I've seen people swear they had available IPs but their pool
> was fully used so wasn't giving more out. Thus phone just kept trying and
> trying...
>
>
> ----- Original Message ----
> From: Ed Leatherman <ealeatherman at gmail.com>
> To: ash AD <commo_ssg_31f at yahoo.com>
> Cc: cisco-voip at puck.nether.net
> Sent: Friday, March 31, 2006 12:54:05 PM
> Subject: Re: [cisco-voip] 7960 PC port
>
> This is interesting. I had been setting up trunk interfaces for the phones
> on 3524XL's while we were using them... I went back to my training lab
> manuals and that is how they explained to do it so I guess I never really
> checked any other way until the 3550 models came out.
>
> So I went in the lab and dug up one of those models and tried it out, to my
> surprise it works the "Correct" way as well as trunked, which I did not
> expect. Since we were told to program trunk ports for the 3524 I assumed it
> was because the other way wouldnt work.
>
> But we still dont know why Peter's PC/phone wont come up on that switchport
> :)
> - If you dont have any CDP config on the interface, that would indicate to
> me that CDP is enabled (unless there is a global command to disable it)
> - mls qos won't work on the 3524 (at least not what I'm running here), I
> dont think its new enough to take some of the QoS features.. I always used
> switchport trunk extend cos 0 to set the COS of anything hanging off the
> phone to 0
>
> I would try using switchport mode access, and then making sure
> "spanning-tree portfast" is set on the interface. I dont see it on your
> config above so maybe thats causing a problem. i've seen the phones bugger
> up while they are waiting for the port to come up if portfast isnt on.
>
>
> On 3/30/06, ash AD <commo_ssg_31f at yahoo.com> wrote:
> >
> >
> > I know this is probably elementary but, I am having issues getting a 7960
> to work with a PC hanging off the phone PC port. I am using CCM 4.1(3)sr2
> with the latest firmware device pack loaded ( 26.3). The phones a hanging
> from a 3524XL inline power switch. I am able to DHCP IPs from both the voice
> and access vlans from the switch in phone/PC separate port configuration. I
> tried two different configurations on the switch ports:
> >
> > Interface Fa 0/1
> >    switchport trunk encapsulation dot1q
> >    switchport mode trunk
> >    switchport access vlan 5
> >    switchport voice vlan 90
> > (In this mode the DHCPs an IP and works, but the PC never DHCPs an IP)
> >
> > Interface Fa 0/1
> >    switchport mode access
> >    switchport access vlan 5
> >    switchport voice vlan 90
> > (In this mode the PC DHCPs an IP and works, but the phone does not work)
> >
> > Can someone tell me if I am stuck on stupid here? Thanks all!
> >
> > Peter
> >
> >
> >
> >
> > ________________________________
> Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+
> countries) for 2¢/min or less.
> >
> >
> > _______________________________________________
> > cisco-voip mailing list
> > cisco-voip at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-voip
> >
> >
> >
>
>
>
> --
> Ed Leatherman
> IP Telephony Coordinator
> West Virginia University
> Telecommunications and Network Operations
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>