Infoblox Technotice Message
The following message about the Infoblox DNS/DHCP service deployment was sent to the technotices listserv on August 10th, 2009.
To: technotices@ucdavis.edu
This will update you on the project to replace NetID and Aspiga with Infoblox as the administrative interface to the campus DHCP/DNS infrastructure. The project is on track, and NetID/Aspiga will be retired in early September. Training and access to the server is now available to assist department system administrators affected by the change. If that group includes you, and you haven't yet looked into what you will need to do, now is a good time to act.
Most end users won't notice the change to Infoblox, but the impact on department system administrators will vary and could be significant. NetID and Infoblox will operate concurrently through August, and then NetID/Aspiga will be retired in September. The cutover to Infoblox is scheduled for Aug. 21.
TRAINING
To schedule on-campus training on administering Infoblox, contact Kathleen Beyer at kmbeyer@ucdavis.edu. She will schedule groups of up to eight people at a time to train at the Network Operations Center. Also, find the Infoblox administration guide here: http://netaccess.ucdavis.edu/Infoblox_AdminGuide_4.3r3.pdf.
ACTION REQUIRED
The Infoblox server is now online for configuration verification. You can login at http://infoblox.ucdavis.edu from any Windows XP/Vista host. If you had a NetID account, your login ID should be active on the Infoblox server. However, authentication is now based on campus Kerberos, so your existing NetID password will not work. If you have problems accessing the Infoblox server, or need to request a new account, please email noc@ucdavis.edu.
Department system administrators will need to log in to the server to make sure their configurations are imported correctly from NetID, and to familiarize themselves with the interface.
If your department runs a VLAN firewall in conjunction with campus DHCP: After Aug. 24, an administrator with access to the department's firewall will need to update their DHCP relay address to point to the Infoblox server at 169.237.160.1. (You should not do this before Aug. 24, because the cutover might not be complete until late on Aug. 21.)
To avoid potential IP address conflicts, administrators should also disable lease allocation in NetID by deleting their dynamic ranges once they verify that hosts can successfully obtain leases from the Infoblox (following a DHCP release/renew, or system reboot). This will prevent hosts with an active lease from renewing it directly against the NetID servers, and force the hosts to transition to Infoblox. As an alternative, administrators could release/renew or reboot every DHCP host on the network.
DNS notes:
The Infoblox server merely acts as an administrative interface to the DNS system. The IP addresses of the campus internal and external DNS servers will remain the same after the Aug. 21 cutover (169.237.1.250 and 169.237.250.250 will continue to serve DNS records to campus hosts as before).
DHCP notes:
Existing DHCP configurations in NetID should transfer to the Infoblox server, but department administrators will need to log in and verify the transfer. Data from NetID will be re-imported into the Infoblox server just before the Aug. 21 cutover, so experimentation with the Infoblox during that time should not affect live network hosts.
Please contact noc@ucdavis.edu with any access requests, questions, or concerns. Find a FAQ at netaccess.ucdavis.edu/infobloxFAQ.cfm, or read more about the project at admincomputing.ucdavis.edu/projects/netid.cfm and netaccess.ucdavis.edu.
To: technotices@ucdavis.edu
Subject: Infoblox on track to replace NetID; cutover is Aug. 21
This will update you on the project to replace NetID and Aspiga with Infoblox as the administrative interface to the campus DHCP/DNS infrastructure. The project is on track, and NetID/Aspiga will be retired in early September. Training and access to the server is now available to assist department system administrators affected by the change. If that group includes you, and you haven't yet looked into what you will need to do, now is a good time to act.
Most end users won't notice the change to Infoblox, but the impact on department system administrators will vary and could be significant. NetID and Infoblox will operate concurrently through August, and then NetID/Aspiga will be retired in September. The cutover to Infoblox is scheduled for Aug. 21.
TRAINING
To schedule on-campus training on administering Infoblox, contact Kathleen Beyer at kmbeyer@ucdavis.edu. She will schedule groups of up to eight people at a time to train at the Network Operations Center. Also, find the Infoblox administration guide here: http://netaccess.ucdavis.edu/Infoblox_AdminGuide_4.3r3.pdf.
ACTION REQUIRED
The Infoblox server is now online for configuration verification. You can login at http://infoblox.ucdavis.edu from any Windows XP/Vista host. If you had a NetID account, your login ID should be active on the Infoblox server. However, authentication is now based on campus Kerberos, so your existing NetID password will not work. If you have problems accessing the Infoblox server, or need to request a new account, please email noc@ucdavis.edu.
Department system administrators will need to log in to the server to make sure their configurations are imported correctly from NetID, and to familiarize themselves with the interface.
If your department runs a VLAN firewall in conjunction with campus DHCP: After Aug. 24, an administrator with access to the department's firewall will need to update their DHCP relay address to point to the Infoblox server at 169.237.160.1. (You should not do this before Aug. 24, because the cutover might not be complete until late on Aug. 21.)
To avoid potential IP address conflicts, administrators should also disable lease allocation in NetID by deleting their dynamic ranges once they verify that hosts can successfully obtain leases from the Infoblox (following a DHCP release/renew, or system reboot). This will prevent hosts with an active lease from renewing it directly against the NetID servers, and force the hosts to transition to Infoblox. As an alternative, administrators could release/renew or reboot every DHCP host on the network.
DNS notes:
The Infoblox server merely acts as an administrative interface to the DNS system. The IP addresses of the campus internal and external DNS servers will remain the same after the Aug. 21 cutover (169.237.1.250 and 169.237.250.250 will continue to serve DNS records to campus hosts as before).
DHCP notes:
Existing DHCP configurations in NetID should transfer to the Infoblox server, but department administrators will need to log in and verify the transfer. Data from NetID will be re-imported into the Infoblox server just before the Aug. 21 cutover, so experimentation with the Infoblox during that time should not affect live network hosts.
Please contact noc@ucdavis.edu with any access requests, questions, or concerns. Find a FAQ at netaccess.ucdavis.edu/infobloxFAQ.cfm, or read more about the project at admincomputing.ucdavis.edu/projects/netid.cfm and netaccess.ucdavis.edu.