|
Home > Archive > Voice over IP Cisco > February 2006 > 7936 DHCP issue
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Mike Mike 2006-02-20, 5:45 pm |
| Conference phone gets plugged into a port on the first voice vlan and gets
an IP from the DHCP pool no problem. Customer moves to another switchport
(same switch) configured on one of the other voice vlans and it takes
several hours to pull a new IP. Customer is using a different voice vlan for
each of three floors. The 7936 has the latest firmware but also experienced
the problem on previous version. Also, a new conf phone has been tried with
same results. Moving 7940's and 7960's between floors works just fine. Last
test was to create reservations in each pool but apparently that didn't
work. Anyone else seen this behavior with the 7936?
Thanks
| |
| Voll, Scott 2006-02-20, 5:45 pm |
| Sounds like a possible DNS issue. I had a problem were I have a PIX and
the Voice vlan could NOT get to the DNS server and it did the same kind
of idea.
Scott
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Mike Mike
Sent: Monday, February 20, 2006 1:08 PM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] 7936 DHCP issue
Conference phone gets plugged into a port on the first voice vlan and
gets an IP from the DHCP pool no problem. Customer moves to another
switchport (same switch) configured on one of the other voice vlans and
it takes several hours to pull a new IP. Customer is using a different
voice vlan for each of three floors. The 7936 has the latest firmware
but also experienced the problem on previous version. Also, a new conf
phone has been tried with same results. Moving 7940's and 7960's between
floors works just fine. Last test was to create reservations in each
pool but apparently that didn't work. Anyone else seen this behavior
with the 7936?
Thanks
| |
| Jonathan Charles 2006-02-20, 5:45 pm |
| We have had this problem dozens of times.
Here's the problem, the 7935/36 are made by Polycom, not cisco and they have
serious trouble with getting VLAN info via CDP.
Solution?
Nail the port down into the voice vlan.
switchport access vlan 100 (or whatever your voice vlan is)
And the phone will come up with an IP on the right vlan.
Jonathan
On 2/20/06, Voll, Scott <Scott.Voll@wesd.org> wrote:
>
> Sounds like a possible DNS issue. I had a problem were I have a PIX and
> the Voice vlan could NOT get to the DNS server and it did the same kind of
> idea.
>
>
>
> Scott
>
>
> ------------------------------
>
> *From:* cisco-voip-bounces@puck.nether.net [mailto:
> cisco-voip-bounces@puck.nether.net] *On Behalf Of *Mike Mike
> *Sent:* Monday, February 20, 2006 1:08 PM
> *To:* cisco-voip@puck.nether.net
> *Subject:* [cisco-voip] 7936 DHCP issue
>
>
>
> Conference phone gets plugged into a port on the first voice vlan and gets
> an IP from the DHCP pool no problem. Customer moves to another switchport
> (same switch) configured on one of the other voice vlans and it takes
> several hours to pull a new IP. Customer is using a different voice vlan for
> each of three floors. The 7936 has the latest firmware but also experienced
> the problem on previous version. Also, a new conf phone has been tried with
> same results. Moving 7940's and 7960's between floors works just fine. Last
> test was to create reservations in each pool but apparently that didn't
> work. Anyone else seen this behavior with the 7936?
>
> Thanks
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
| |
| Jonathan Charles 2006-02-20, 5:45 pm |
| OK.
Are there other phones on this switch?
Is the switch running layer 3?
Is there an ip helper address going to the voice dhcp server?
J
On 2/20/06, Jonathan Charles <jonvoip@gmail.com> wrote:
>
> We have had this problem dozens of times.
>
> Here's the problem, the 7935/36 are made by Polycom, not cisco and they
> have serious trouble with getting VLAN info via CDP.
>
> Solution?
>
> Nail the port down into the voice vlan.
>
> switchport access vlan 100 (or whatever your voice vlan is)
>
> And the phone will come up with an IP on the right vlan.
>
>
>
> Jonathan
>
> On 2/20/06, Voll, Scott <Scott.Voll@wesd.org> wrote:
>
>
| |
| Erick Bergquist 2006-02-20, 8:45 pm |
| How many DNS servers, WINS servers are being pushed
down with DHCP? These models also had issue handling
more then 3 entries of the above. Also, as jonathan
mentioned put the port into the voice vlan altogether
if the dns/wins servers is just 1 entry.
> first voice vlan and
> Customer moves to another
> the other voice vlans and it
> is using a different voice
> latest firmware but also
> Also, a new conf phone has been
> 7960's between floors works just
> each pool but apparently that
> the 7936?
________________________________________
__________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
| |
| Mike Armstrong 2006-02-21, 7:45 am |
| It sounds like the 7936 doesn't completely understand DHCP. If you unplug
the 7936 and reconnect to the same VLAN (perhaps thru a different
switchport, if possible) does it come up OK with the same IP address it had
before? If so, try unplugging it and removing that address from the DHCP
pool, and see if the 7936 can get another IP from the same pool. Then, try
the other VLAN; these test should identify the point in the DHCP handshake
where it breaks. Also, what is your lease time -- how does that compare
with the "several hours" it takes to acquire a new IP on the 2nd VLAN? If
you can sniff the switchport when the 7936 is plugged it, it would be an
interesting trace compared with, say, a 7940 doing the same dance. We've
had several problems with the conference phones' initialization, but never
pinned anything down.
Mike Armstrong
UF/IFAS CREC
Lake Alfred, FL
> Date: Mon, 20 Feb 2006 15:08:24 -0600
> From: "Mike Mike" <voipermike@gmail.com>
> Subject: [cisco-voip] 7936 DHCP issue
> To: cisco-voip@puck.nether.net
> Message-ID:
> < 8bbfc1f40602201308x1f224394r878602afaaa2
6d0b@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Conference phone gets plugged into a port on the first voice vlan and gets
> an IP from the DHCP pool no problem. Customer moves to another switchport
> (same switch) configured on one of the other voice vlans and it takes
> several hours to pull a new IP. Customer is using a different voice vlan
> for
> each of three floors. The 7936 has the latest firmware but also
> experienced
> the problem on previous version. Also, a new conf phone has been tried
> with
> same results. Moving 7940's and 7960's between floors works just fine.
> Last
> test was to create reservations in each pool but apparently that didn't
> work. Anyone else seen this behavior with the 7936?
>
> Thanks
| |
| Matt Slaga \(US\) 2006-02-21, 7:45 am |
| Jonathon hit it on the head earlier.
On all of our installs, we hard code the port for 7935/36s and ata-186s
to the voice vlan. If you read the cisco documentation, it specifies
this. There is no switch in these devices, hence it will not understand
vlan tagging.
Matt
-----Original Message-----
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Mike Armstrong
Sent: Tuesday, February 21, 2006 7:44 AM
To: cisco-voip@puck.nether.net; voipermike@gmail.com
Subject: Re: [cisco-voip] 7936 DHCP issue
It sounds like the 7936 doesn't completely understand DHCP. If you
unplug
the 7936 and reconnect to the same VLAN (perhaps thru a different
switchport, if possible) does it come up OK with the same IP address it
had before? If so, try unplugging it and removing that address from the
DHCP pool, and see if the 7936 can get another IP from the same pool.
Then, try the other VLAN; these test should identify the point in the
DHCP handshake where it breaks. Also, what is your lease time -- how
does that compare with the "several hours" it takes to acquire a new IP
on the 2nd VLAN? If you can sniff the switchport when the 7936 is
plugged it, it would be an interesting trace compared with, say, a 7940
doing the same dance. We've had several problems with the conference
phones' initialization, but never pinned anything down.
Mike Armstrong
UF/IFAS CREC
Lake Alfred, FL
> Date: Mon, 20 Feb 2006 15:08:24 -0600
> From: "Mike Mike" <voipermike@gmail.com>
> Subject: [cisco-voip] 7936 DHCP issue
> To: cisco-voip@puck.nether.net
> Message-ID:
> < 8bbfc1f40602201308x1f224394r878602afaaa2
6d0b@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Conference phone gets plugged into a port on the first voice vlan and
> gets an IP from the DHCP pool no problem. Customer moves to another
> switchport (same switch) configured on one of the other voice vlans
> and it takes several hours to pull a new IP. Customer is using a
> different voice vlan for each of three floors. The 7936 has the latest
> firmware but also experienced the problem on previous version. Also, a
> new conf phone has been tried with same results. Moving 7940's and
> 7960's between floors works just fine.
> Last
> test was to create reservations in each pool but apparently that
> didn't work. Anyone else seen this behavior with the 7936?
>
> Thanks
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-----------------------------------------
Disclaimer:
This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the
intended addressee, you are hereby notified that you have received
this communication in error and that any use or reproduction of
this email or its contents is strictly prohibited and may be
unlawful. If you have received this communication in error, please
notify us immediately by replying to this message and deleting it
from your computer. Thank you.
| |
| Mike Armstrong 2006-02-21, 5:45 pm |
| Odd. (Of course, I haven't read the documentation...) On our 2900 and 3500
switches we configure the switchports as trunks, specifying the voice and
native VLANs; on the 3750s we identify the voice VLAN and an access VLAN for
the non-voice stuff. 7935, 7936 and 7910 (all without switches) work fine
on both. As I understood it, the phone identifies itself as such (via CDP)
at startup, and the switch associates it with the voice VLAN. I'll read the
docs and sniff these on startup when I get a spare moment (hah!).
Mike
> Date: Tue, 21 Feb 2006 07:55:30 -0500
> From: "Matt Slaga \(US\)" <Matt.Slaga@us.didata.com>
> Subject: RE: [cisco-voip] 7936 DHCP issue
> To: "Mike Armstrong" <mfa@ufl.edu>, <cisco-voip@puck.nether.net>,
> <voipermike@gmail.com>
> Message-ID:
> < C1FE15183DA37645BC0633BC604E44F0F4D9DF@U
SNAEXCH.na.didata.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Jonathon hit it on the head earlier.
>
> On all of our installs, we hard code the port for 7935/36s and ata-186s
> to the voice vlan. If you read the cisco documentation, it specifies
> this. There is no switch in these devices, hence it will not understand
> vlan tagging.
>
> Matt
| |
| Lelio Fulgenzi 2006-02-21, 5:45 pm |
| We to use our 7935/7936 with trunk ports and move them around from place to place. No problem at all.
--------------------------------------------------------------------------------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter than an
IP phone on a long haul 10base2 connection" LFJ
----- Original Message -----
From: Mike Armstrong
To: cisco-voip@puck.nether.net
Sent: Tuesday, February 21, 2006 11:26 AM
Subject: Re: [cisco-voip] 7936 DHCP issue
Odd. (Of course, I haven't read the documentation...) On our 2900 and 3500
switches we configure the switchports as trunks, specifying the voice and
native VLANs; on the 3750s we identify the voice VLAN and an access VLAN for
the non-voice stuff. 7935, 7936 and 7910 (all without switches) work fine
on both. As I understood it, the phone identifies itself as such (via CDP)
at startup, and the switch associates it with the voice VLAN. I'll read the
docs and sniff these on startup when I get a spare moment (hah!).
Mike
> Date: Tue, 21 Feb 2006 07:55:30 -0500
> From: "Matt Slaga \(US\)" <Matt.Slaga@us.didata.com>
> Subject: RE: [cisco-voip] 7936 DHCP issue
> To: "Mike Armstrong" <mfa@ufl.edu>, <cisco-voip@puck.nether.net>,
> <voipermike@gmail.com>
> Message-ID:
> < C1FE15183DA37645BC0633BC604E44F0F4D9DF@U
SNAEXCH.na.didata.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Jonathon hit it on the head earlier.
>
> On all of our installs, we hard code the port for 7935/36s and ata-186s
> to the voice vlan. If you read the cisco documentation, it specifies
> this. There is no switch in these devices, hence it will not understand
> vlan tagging.
>
> Matt
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Voll, Scott 2006-02-21, 5:45 pm |
| Dido
________________________________
From: cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Tuesday, February 21, 2006 8:48 AM
To: Mike Armstrong; cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] 7936 DHCP issue
We to use our 7935/7936 with trunk ports and move them around from place
to place. No problem at all.
------------------------------------------------------------------------
--------
Lelio Fulgenzi, B.A.
Network Analyst (CCS) * university of Guelph * Guelph, Ontario N1G 2W1
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
"I had a coffee and Coke at lunch today...and now, I've got more jitter
than an
IP phone on a long haul 10base2 connection"
LFJ
----- Original Message -----
From: Mike Armstrong <mailto:mfa@crec.ifas.ufl.edu>
To: cisco-voip@puck.nether.net
Sent: Tuesday, February 21, 2006 11:26 AM
Subject: Re: [cisco-voip] 7936 DHCP issue
Odd. (Of course, I haven't read the documentation...) On our
2900 and 3500
switches we configure the switchports as trunks, specifying the
voice and
native VLANs; on the 3750s we identify the voice VLAN and an
access VLAN for
the non-voice stuff. 7935, 7936 and 7910 (all without switches)
work fine
on both. As I understood it, the phone identifies itself as
such (via CDP)
at startup, and the switch associates it with the voice VLAN.
I'll read the
docs and sniff these on startup when I get a spare moment
(hah!).
Mike
> Date: Tue, 21 Feb 2006 07:55:30 -0500
> From: "Matt Slaga \(US\)" <Matt.Slaga@us.didata.com>
> Subject: RE: [cisco-voip] 7936 DHCP issue
> To: "Mike Armstrong" <mfa@ufl.edu>,
<cisco-voip@puck.nether.net>,
> <voipermike@gmail.com>
> Message-ID:
>
< C1FE15183DA37645BC0633BC604E44F0F4D9DF@U
SNAEXCH.na.didata.local>
> Content-Type: text/plain; charset="us-ascii"
>
> Jonathon hit it on the head earlier.
>
> On all of our installs, we hard code the port for 7935/36s and
ata-186s
> to the voice vlan. If you read the cisco documentation, it
specifies
> this. There is no switch in these devices, hence it will not
understand
> vlan tagging.
>
> Matt
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
|
|
|
|