Show Posts
1
Mitel MiVoice Business/MCD/3300 / Interminent DHCP issues
« on: May 15, 2014, 06:57:02 PM »
Good morning everyone,
I have been trying to resolve this issue for quite a while, but coming up blank. Hoping that someone else might have come across this this problem before.
Setup:
Cisco 2960 switches, connected to Palo Alto firewall, with the Mitel 3300 controller on MCA 4.0.1.11-1. The Cisco switches have 2 sub-interfaces set up on the uplink to the Palo Alto, one for users LAN the other for the voice LAN. I have IP-helper set up on the Cisco (one for each VLAN) talking to MS DHCP server.
The issue we seeing is this:
- Plugin in a new (or old) handset, the boot can take anywhere from 1 minute so couple of days. The same phone will sometimes pick up all DHCP traffic within seconds, at other times will sit there for days before assigning address. We had some phones that taken a week. Sometimes un-plugging and re-plugging the phones speeds the DHCP up, other times now so much.
- Looks like the initial DHCP requests (via users LAN) are always working, the phone then changes to the correct VLAN (1001) - I can see on the screen it picks up the VLAN etc. settings, then it sometimes sits there at DHCP: Discovery
- Let me stress that the same phone will sometimes take 1 minute to boot other times hours or days.
The Cisco DHCP logs shows:
269175: May 15 22:54:50.234: DHCPD: Reload workspace interface Vlan10 tableid 0.
269176: May 15 22:54:50.234: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269177: May 15 22:54:50.234: DHCPD: client's VPN is .
269178: May 15 22:54:50.234: DHCPD: forwarding BOOTREPLY to client f0de.f195.3ce 8.
269179: May 15 22:54:50.234: DHCPD: no option 125
269180: May 15 22:54:50.234: DHCPD: broadcasting BOOTREPLY to client f0de.f195.3 ce8.
269181: May 15 22:54:54.597: DHCPD: Reload workspace interface Vlan10 tableid 0.
269182: May 15 22:54:54.597: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269183: May 15 22:54:54.597: DHCPD: client's VPN is .
269184: May 15 22:54:54.597: DHCPD: Finding a relay for client 01d4.bed9.7903.c4 on interface Vlan10.
269185: May 15 22:54:54.597: DHCPD: Looking up binding using address 10.61.10.254
269186: May 15 22:54:54.597: DHCPD: setting giaddr to 10.61.10.254.
269187: May 15 22:54:54.597: DHCPD: BOOTREQUEST from 01d4.bed9.7903.c4 forwarded to 192.168.0.2.
269188: May 15 22:55:09.608: DHCPD: Reload workspace interface Vlan10 tableid 0.
269189: May 15 22:55:09.608: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269190: May 15 22:55:09.608: DHCPD: client's VPN is .
269191: May 15 22:55:09.608: DHCPD: Finding a relay for client 01f0.def1.5a20.fc on interface Vlan10.
269192: May 15 22:55:09.608: DHCPD: Looking up binding using address 10.61.10.254
269193: May 15 22:55:09.613: DHCPD: setting giaddr to 10.61.10.254.
269194: May 15 22:55:09.613: DHCPD: BOOTREQUEST from 01f0.def1.5a20.fc forwarded to 192.168.0.2.
269195: May 15 22:55:09.755: DHCPD: Reload workspace interface Vlan10 tableid 0.
269196: May 15 22:55:09.755: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269197: May 15 22:55:09.755: DHCPD: client's VPN is .
269198: May 15 22:55:09.755: DHCPD: forwarding BOOTREPLY to client f0de.f15a.20fc.
269199: May 15 22:55:09.755: DHCPD: no option 125
269200: May 15 22:55:09.755: DHCPD: broadcasting BOOTREPLY to client f0de.f15a.20fc.
269201: May 15 22:55:16.843: DHCPD: Reload workspace interface Vlan10 tableid 0.
269202: May 15 22:55:16.843: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269203: May 15 22:55:16.843: DHCPD: client's VPN is .
269204: May 15 22:55:16.843: DHCPD: Finding a relay for client 01f0.def1.953d.23 on interface Vlan10.
269205: May 15 22:55:16.843: DHCPD: Looking up binding using address 10.61.10.254
269206: May 15 22:55:16.843: DHCPD: setting giaddr to 10.61.10.254.
269207: May 15 22:55:16.843: DHCPD: BOOTREQUEST from 01f0.def1.953d.23 forwarded to 192.168.0.2.
269208: May 15 22:55:17.467: DHCPD: Reload workspace interface Vlan1001 tableid 0.
269209: May 15 22:55:17.467: DHCPD: tableid for 10.61.20.254 on Vlan1001 is 0
269210: May 15 22:55:17.467: DHCPD: client's VPN is .
269211: May 15 22:55:17.467: DHCPD: using received relay info.
269212: May 15 22:55:17.467: DHCPD: Looking up binding using address 10.61.20.254
269213: May 15 22:55:17.467: DHCPD: setting giaddr to 10.61.20.254.
269214: May 15 22:55:17.467: DHCPD: BOOTREQUEST from 0108.000f.7450.bc forwarded to 192.168.0.2.
269215: May 15 22:55:17.866: DHCPD: Reload workspace interface Vlan1001 tableid 0.
269216: May 15 22:55:17.866: DHCPD: tableid for 10.61.20.254 on Vlan1001 is 0
269217: May 15 22:55:17.866: DHCPD: client's VPN is .
269218: May 15 22:55:17.866: DHCPD: using received relay info.
269219: May 15 22:55:17.866: DHCPD: Looking up binding using address 10.61.20.254
269220: May 15 22:55:17.866: DHCPD: setting giaddr to 10.61.20.254.
269221: May 15 22:55:17.866: DHCPD: BOOTREQUEST from 0108.000f.3768.aa forwarded to 192.168.0.2.
269222: May 15 22:55:24.393: DHCPD: Reload workspace interface Vlan10 tableid 0.
269223: May 15 22:55:24.393: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269224: May 15 22:55:24.393: DHCPD: client's VPN is .
269225: May 15 22:55:24.393: DHCPD: Finding a relay for client 015c.f9dd.de88.d9 on interface Vlan10.
269226: May 15 22:55:24.393: DHCPD: Looking up binding using address 10.61.10.254
269227: May 15 22:55:24.393: DHCPD: setting giaddr to 10.61.10.254.
269228: May 15 22:55:24.393: DHCPD: BOOTREQUEST from 015c.f9dd.de88.d9 forwarded to 192.168.0.2.
269229: May 15 22:55:24.566: DHCPD: Reload workspace interface Vlan10 tableid 0.
L10_Users#
269230: May 15 22:55:24.566: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269231: May 15 22:55:24.566: DHCPD: client's VPN is .
269232: May 15 22:55:24.566: DHCPD: forwarding BOOTREPLY to client 5cf9.ddde.88d9.
269233: May 15 22:55:24.566: DHCPD: no option 125
269234: May 15 22:55:24.566: DHCPD: broadcasting BOOTREPLY to client 5cf9.ddde.88d9.
269235: May 15 22:55:25.468: DHCPD: Reload workspace interface Vlan1001 tableid 0.
269236: May 15 22:55:25.468: DHCPD: tableid for 10.61.20.254 on Vlan1001 is 0
269237: May 15 22:55:25.468: DHCPD: client's VPN is .
269238: May 15 22:55:25.468: DHCPD: using received relay info.
269239: May 15 22:55:25.468: DHCPD: Looking up binding using address 10.61.20.254
269240: May 15 22:55:25.468: DHCPD: setting giaddr to 10.61.20.254.
269241: May 15 22:55:25.468: DHCPD: BOOTREQUEST from 0108.000f.7450.bc forwarded to 192.168.0.2.
Any suggestions would be greatly appreciated
I have been trying to resolve this issue for quite a while, but coming up blank. Hoping that someone else might have come across this this problem before.
Setup:
Cisco 2960 switches, connected to Palo Alto firewall, with the Mitel 3300 controller on MCA 4.0.1.11-1. The Cisco switches have 2 sub-interfaces set up on the uplink to the Palo Alto, one for users LAN the other for the voice LAN. I have IP-helper set up on the Cisco (one for each VLAN) talking to MS DHCP server.
The issue we seeing is this:
- Plugin in a new (or old) handset, the boot can take anywhere from 1 minute so couple of days. The same phone will sometimes pick up all DHCP traffic within seconds, at other times will sit there for days before assigning address. We had some phones that taken a week. Sometimes un-plugging and re-plugging the phones speeds the DHCP up, other times now so much.
- Looks like the initial DHCP requests (via users LAN) are always working, the phone then changes to the correct VLAN (1001) - I can see on the screen it picks up the VLAN etc. settings, then it sometimes sits there at DHCP: Discovery
- Let me stress that the same phone will sometimes take 1 minute to boot other times hours or days.
The Cisco DHCP logs shows:
269175: May 15 22:54:50.234: DHCPD: Reload workspace interface Vlan10 tableid 0.
269176: May 15 22:54:50.234: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269177: May 15 22:54:50.234: DHCPD: client's VPN is .
269178: May 15 22:54:50.234: DHCPD: forwarding BOOTREPLY to client f0de.f195.3ce 8.
269179: May 15 22:54:50.234: DHCPD: no option 125
269180: May 15 22:54:50.234: DHCPD: broadcasting BOOTREPLY to client f0de.f195.3 ce8.
269181: May 15 22:54:54.597: DHCPD: Reload workspace interface Vlan10 tableid 0.
269182: May 15 22:54:54.597: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269183: May 15 22:54:54.597: DHCPD: client's VPN is .
269184: May 15 22:54:54.597: DHCPD: Finding a relay for client 01d4.bed9.7903.c4 on interface Vlan10.
269185: May 15 22:54:54.597: DHCPD: Looking up binding using address 10.61.10.254
269186: May 15 22:54:54.597: DHCPD: setting giaddr to 10.61.10.254.
269187: May 15 22:54:54.597: DHCPD: BOOTREQUEST from 01d4.bed9.7903.c4 forwarded to 192.168.0.2.
269188: May 15 22:55:09.608: DHCPD: Reload workspace interface Vlan10 tableid 0.
269189: May 15 22:55:09.608: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269190: May 15 22:55:09.608: DHCPD: client's VPN is .
269191: May 15 22:55:09.608: DHCPD: Finding a relay for client 01f0.def1.5a20.fc on interface Vlan10.
269192: May 15 22:55:09.608: DHCPD: Looking up binding using address 10.61.10.254
269193: May 15 22:55:09.613: DHCPD: setting giaddr to 10.61.10.254.
269194: May 15 22:55:09.613: DHCPD: BOOTREQUEST from 01f0.def1.5a20.fc forwarded to 192.168.0.2.
269195: May 15 22:55:09.755: DHCPD: Reload workspace interface Vlan10 tableid 0.
269196: May 15 22:55:09.755: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269197: May 15 22:55:09.755: DHCPD: client's VPN is .
269198: May 15 22:55:09.755: DHCPD: forwarding BOOTREPLY to client f0de.f15a.20fc.
269199: May 15 22:55:09.755: DHCPD: no option 125
269200: May 15 22:55:09.755: DHCPD: broadcasting BOOTREPLY to client f0de.f15a.20fc.
269201: May 15 22:55:16.843: DHCPD: Reload workspace interface Vlan10 tableid 0.
269202: May 15 22:55:16.843: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269203: May 15 22:55:16.843: DHCPD: client's VPN is .
269204: May 15 22:55:16.843: DHCPD: Finding a relay for client 01f0.def1.953d.23 on interface Vlan10.
269205: May 15 22:55:16.843: DHCPD: Looking up binding using address 10.61.10.254
269206: May 15 22:55:16.843: DHCPD: setting giaddr to 10.61.10.254.
269207: May 15 22:55:16.843: DHCPD: BOOTREQUEST from 01f0.def1.953d.23 forwarded to 192.168.0.2.
269208: May 15 22:55:17.467: DHCPD: Reload workspace interface Vlan1001 tableid 0.
269209: May 15 22:55:17.467: DHCPD: tableid for 10.61.20.254 on Vlan1001 is 0
269210: May 15 22:55:17.467: DHCPD: client's VPN is .
269211: May 15 22:55:17.467: DHCPD: using received relay info.
269212: May 15 22:55:17.467: DHCPD: Looking up binding using address 10.61.20.254
269213: May 15 22:55:17.467: DHCPD: setting giaddr to 10.61.20.254.
269214: May 15 22:55:17.467: DHCPD: BOOTREQUEST from 0108.000f.7450.bc forwarded to 192.168.0.2.
269215: May 15 22:55:17.866: DHCPD: Reload workspace interface Vlan1001 tableid 0.
269216: May 15 22:55:17.866: DHCPD: tableid for 10.61.20.254 on Vlan1001 is 0
269217: May 15 22:55:17.866: DHCPD: client's VPN is .
269218: May 15 22:55:17.866: DHCPD: using received relay info.
269219: May 15 22:55:17.866: DHCPD: Looking up binding using address 10.61.20.254
269220: May 15 22:55:17.866: DHCPD: setting giaddr to 10.61.20.254.
269221: May 15 22:55:17.866: DHCPD: BOOTREQUEST from 0108.000f.3768.aa forwarded to 192.168.0.2.
269222: May 15 22:55:24.393: DHCPD: Reload workspace interface Vlan10 tableid 0.
269223: May 15 22:55:24.393: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269224: May 15 22:55:24.393: DHCPD: client's VPN is .
269225: May 15 22:55:24.393: DHCPD: Finding a relay for client 015c.f9dd.de88.d9 on interface Vlan10.
269226: May 15 22:55:24.393: DHCPD: Looking up binding using address 10.61.10.254
269227: May 15 22:55:24.393: DHCPD: setting giaddr to 10.61.10.254.
269228: May 15 22:55:24.393: DHCPD: BOOTREQUEST from 015c.f9dd.de88.d9 forwarded to 192.168.0.2.
269229: May 15 22:55:24.566: DHCPD: Reload workspace interface Vlan10 tableid 0.
L10_Users#
269230: May 15 22:55:24.566: DHCPD: tableid for 10.61.10.254 on Vlan10 is 0
269231: May 15 22:55:24.566: DHCPD: client's VPN is .
269232: May 15 22:55:24.566: DHCPD: forwarding BOOTREPLY to client 5cf9.ddde.88d9.
269233: May 15 22:55:24.566: DHCPD: no option 125
269234: May 15 22:55:24.566: DHCPD: broadcasting BOOTREPLY to client 5cf9.ddde.88d9.
269235: May 15 22:55:25.468: DHCPD: Reload workspace interface Vlan1001 tableid 0.
269236: May 15 22:55:25.468: DHCPD: tableid for 10.61.20.254 on Vlan1001 is 0
269237: May 15 22:55:25.468: DHCPD: client's VPN is .
269238: May 15 22:55:25.468: DHCPD: using received relay info.
269239: May 15 22:55:25.468: DHCPD: Looking up binding using address 10.61.20.254
269240: May 15 22:55:25.468: DHCPD: setting giaddr to 10.61.20.254.
269241: May 15 22:55:25.468: DHCPD: BOOTREQUEST from 0108.000f.7450.bc forwarded to 192.168.0.2.
Any suggestions would be greatly appreciated