...
| borderColor | #BAD6E5 |
|---|---|
| bgColor | #FFFFFF |
| borderStyle | solid |
On 06/11/2010 05:49 PM, Jonah Keough wrote:
This week UIT Network Engineering successfully piloted the migration of DHCP service for wired users in the Tufts Administration Building. IP addresses are now being assigned by the BlueCat servers and unregistered hosts are being registered through the new BlueCat captive portal system.
...
Hosts placed on the Tufts network must have their MAC addresses registered. This is done to help correlate machine user/owner with network activity. New hosts can have their MAC address registered one of two ways:
1. From another machine that is already on the Tufts network, via the hostreg.net.tufts.edu registration portal. Regular users can utilize the user portal at https://hostreg.net.tufts.edu
...
UIT has begun working with the various IT support organizations to select an additional subnet on each campus to pilot DHCP migration. Once these additional subnets are successfully migrated onto the BlueCat platform and this collaborative pilot complete, UIT will work to migrate the rest of university's networks to the new DHCP servers by the end of July. A more detailed schedule for these migrations will be distributed shortly.
On the day a network is migrated users may notice some minor interruptions. The most frequent issue will be for users who registered new devices on the network after February 23rd. These users will be prompted to re-register their devices on the BlueCat captive portal. While the back-end of the portal has been replaced, the end-user experience is nearly identical to the TUNIS web interface that they may have seen in the past. Host expiration has been suspended since February 23rd, so the only devices that should be impacted are those that are new to the network.
While TUNIS and the proxy registration page have largely remained the same on BlueCat, FSPs will notice a few changes:
• Registrations will now take effect immediately on the DHCP servers. Without intervention there will still be some delay while waiting for the DHCP lease to renew, but if you run an ipconfig /release, /renew or similar, the host will immediately receive a valid IP address.
• There is a new required field on the proxy page, "registered for." The UTLN of the system owner should be entered in this field. If the user does not have a UTLN, you must enter your own UTLN.
• On the proxy registration screen the expiration date still defaults to one year or 7 years depending on the device class you select (tufts-user or tufts-asset), but if you need to select a shorter duration the expiration field now provides a quick drop-down to select an appropriate duration rather than manually entering a specific number of days.
• Users will still be directed to the TUNIS screen automatically when they open a web browser on an un-registered system, however the TUNIS page has a different IP address and name (portal.net.tufts.edu).
...
/ to register their own machines. The administrative limits on number of machines a user can have registered to their UTLN is enforced here for users. FSPs and other administrative portal users should use the admin portal at https://hostreg.net.tufts.edu/admin to do proxy registration for others. You can indicate the UTLN for the user in the "registered for" field on the administrative registration page. The administrative portal does not enforce the per-UTLN limit on registered machines.
2. From a new machine placed on a DHCP network or connected to the Tufts (non-guest) wireless network. Some systems will detect that they are behind a portal and immediately prompt the user for a UTLN login. If not, any attempt to connect to a remote web host will redirect the user to the captive portal, https://portal.net.tufts.edu. The captive portal enforces the per-user limits on number of machines registered to a given UTLN.
New DHCP registrations created via the portal.net.tufts.edu captive portal will take effect on that campus immediately if you do a DHCP release/renew to refresh the lease; if you let the lease expire and renew on its own, it should take 3-4 minutes, at most. New DHCP registrations created via portal.net.tufts.edu will be effective on other campuses within half an hour when the next scheduled DHCP deployment occurs.
New DHCP registrations created via the hostreg portal will take effect everywhere after the next scheduled DHCP deployment. These deployments occur every hour at 20 and 50 past the hour.