Closed
Bug 871820
Opened 11 years ago
Closed 11 years ago
please add dhcp helper for 10.26.16.0
Categories
(Infrastructure & Operations Graveyard :: NetOps, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: arich, Assigned: adam)
Details
Please add a dhcp helper for 10.26.16.0/22 that points to 10.26.75.40, 10.26.75.41. This will enable dhcp for the inband.releng.scl3.mozilla.com network.
Comment 1•11 years ago
|
||
The helper is already in place - the DHCP servers are giving errors for requests on that VLAN: May 13 16:11:24 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:47:83 via 10.26.16.1: unknown network segment May 13 16:11:28 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:47:83 via 10.26.16.1: unknown network segment May 13 16:11:31 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:47:83 via 10.26.16.1: unknown network segment May 13 16:11:31 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:21:1c via 10.26.16.1: unknown network segment May 13 16:11:34 admin1b dhcpd: DHCPDISCOVER from 00:25:90:6f:52:25 via 10.26.16.1: unknown network segment May 13 16:11:35 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:21:1c via 10.26.16.1: unknown network segment May 13 16:11:37 admin1b dhcpd: DHCPDISCOVER from 00:25:90:6f:52:25 via 10.26.16.1: unknown network segment May 13 16:11:38 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:21:1c via 10.26.16.1: unknown network segment May 13 16:11:40 admin1b dhcpd: DHCPDISCOVER from 00:25:90:6f:52:25 via 10.26.16.1: unknown network segment May 13 16:11:43 admin1b dhcpd: DHCPDISCOVER from 00:25:90:cd:61:e8 via 10.26.16.1: unknown network segment So this just needs the DHCP configuration.
Assignee: network-operations → dustin
Comment 2•11 years ago
|
||
er, I didn't mean to take the bug, although I can do the DHCP config tomorrow if necessary,.
Assignee: dustin → network-operations
Assignee | ||
Updated•11 years ago
|
Assignee: network-operations → adam
Assignee | ||
Comment 3•11 years ago
|
||
The requested change has been implemented. Please verify that it is functioning as required. Regards, -Adam
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 4•11 years ago
|
||
Confirmed; I saw 4 machines pick up addresses as of May 13 17:06 pacific.
Reporter | ||
Comment 5•11 years ago
|
||
Well, actually, the last lease renewal I saw was May 16 00:34:09. I tried rebooting one of the IPMI devices and I never saw a request for it come across to the dhcp servers. Either the reboot didn't work (possible), or the helper was functioning before and is not now.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 6•11 years ago
|
||
The DHCP helpers are still in place. I can help troubleshoot, but as far as this going from working to not working, nothing appears to have been altered on the FW.
Reporter | ||
Comment 7•11 years ago
|
||
Augh, I picked the ns IPs, not the admin host IPs. My mistake. Adam was awesome and troubleshot and fixed.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Infrastructure & Operations
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•