06-26-2014, 11:03 AM
Hi
I have been doing some extensive testing of T46G, T41P and T21P handsets and have noticed some inconsistencies.
Due to the nature of the network there are multiple DHCP servers, this is destined to change, but shouldnt cause a major issue.
We have 2 Vlans in our network, 1 is data 2 is voice.
Voice is 10.1.x.y (x being site, and y being the unit) and 1 being 172.16.x.y
On the T21p with auto provision we have the following happen.
Boots, gets IP from 172.16, gets auto provision information, applies Vlan
Reboots, gets IP from 10.1, keeps this IP.
However I have noticed for the T4X's this is not the case.
Instead it is
Boots, gets IP from 172.16, gets auto provision information, applies Vlan
Reboots, gets IP from 10.1, holds onto IP till expire, gets 172.16 IP.
This is with the following firmware
28.72.0.25 and 36.72.0.25 , and 34.72.0.20 for the relevant models
I have yet to do packet capture and analysis but from the above I would assume there is something.. abnormal happening.
I will be doing a packet capture to track down the exact issue.
Naturally this threw me a bit as I was using the t21P for the bulk of my testing.
I have been doing some extensive testing of T46G, T41P and T21P handsets and have noticed some inconsistencies.
Due to the nature of the network there are multiple DHCP servers, this is destined to change, but shouldnt cause a major issue.
We have 2 Vlans in our network, 1 is data 2 is voice.
Voice is 10.1.x.y (x being site, and y being the unit) and 1 being 172.16.x.y
On the T21p with auto provision we have the following happen.
Boots, gets IP from 172.16, gets auto provision information, applies Vlan
Reboots, gets IP from 10.1, keeps this IP.
However I have noticed for the T4X's this is not the case.
Instead it is
Boots, gets IP from 172.16, gets auto provision information, applies Vlan
Reboots, gets IP from 10.1, holds onto IP till expire, gets 172.16 IP.
This is with the following firmware
28.72.0.25 and 36.72.0.25 , and 34.72.0.20 for the relevant models
I have yet to do packet capture and analysis but from the above I would assume there is something.. abnormal happening.
I will be doing a packet capture to track down the exact issue.
Naturally this threw me a bit as I was using the t21P for the bulk of my testing.