Skip to Main Content

NU Telecommunications Room (TR) Pilot

Students sitting in a sunlit courtyard with Powell library in the background.

Goals

The goals of the TR pilot are to validate components of the new network design, migrate select devices onto the new network, and test and refine the end-to-end migration approach for future waves.

Scope

Buildings and TRs:

  • Campus Services Building 1: 2215A (select stacks only)
  • Haines Hall: A40, 184, and 242
  • Knudsen Hall: A170 and B145A
  • Perloff Hall: B243, 1125A, and 1203A

Devices:

  • Only DTS Managed Network Services (MNS) wired and wireless devices within in-scope TRs will be migrated. 
  • Department-managed devices are not included in this phase.

Impacted Campus Units

Stakeholder GroupCampus Units
MNS Customers &
Shared Infrastructure
  • Social Sciences
  • School of Arts and Architecture
Campus-Wide Technologies
  • BruinCard Office
  • DTS Data Center & Facilities Management
  • DTS Digital Spaces
  • DTS Unified Communications
  • DTS Workplace Products
  • Housing Operations
Building-Specific Technologies
  • DTS AV/IT
  • DTS Endpoint Solutions
  • DTS Production Services
  • DTS Workplace Products
  • School of Arts and Architecture
Building Tenants
  • Humanities
  • Physical Sciences
  • School of Arts & Architecture
  • Social Sciences
  • Student Affairs
  • Transportation
End Users
  • All end users (e.g. faculty, staff, students, guests) in pilot buildings.

Pilot Migration Schedule

Below is the preliminary TR pilot migration schedule for wired and wireless migrations. Migrations will occur overnight, from 10 p.m. to 6 a.m., on the following dates at the following sites:

July 14 & 15

Campus Service Building 1

July 21

Knudsen Hall

July 22

Haines Hall

July 23

Perloff Hall

Expected Changes During and After Pilot

As Pilot buildings are migrated, the following changes and impacts will occur during and after the Pilot.

ChangeChange DescriptionStakeholders & ImpactsPlanned Mitigations
Re-IP of DTS-Managed Common NetworksDTS-managed common networks (e.g. MNS user and printer networks, eduroam and other wireless) will be re-addressed to new IP ranges.

All campus units: 

  • Potential impacts to unit security, firewall, and routing policies enforcement.
  • Users connected to the new wired or wireless networks may have issues accessing department-specific resources if unit policies are not updated to accommodate the new IP ranges.
  • Notify campus units to review and update network security, firewall, and routing policies to accommodate new IP ranges ahead of pilot. 
  • Deadline to complete updates and avoid potential disruption is Friday, 7/3.
New Network Infrastructure DeploymentNew building routers, wired switches, and wireless access points (APs) will be installed, replacing current DTS MNS infrastructure.

Pilot stakeholders only:

  • Temporary downtime to complete migrations, troubleshoot issues, and stabilize building
  • Communicate possible downtimes prior to cutover
  • Deploy defined rollback plan, troubleshooting process, and hypercare support
Network Access Control (NAC) ImplementationEndpoint devices will need to be registered to access the new network.

Pilot stakeholders only:

  • Registered devices will be placed on their respective networks per the device registration cutsheet. 
  • Unregistered devices will be placed on a default "Guest" network with limited access to the Internet only.
  • Validate endpoint cutsheets prior to migration
  • Deploy expedited process to onboard unregistered devices after cutover
Wi-Fi SSID ChangesUCLA_WEB, UCLA_WIFI SSIDs will be decommissioned and replaced by UCLA_GUEST.

End users in pilot buildings:

  • End users with a UCLA ID should connect to eduroam.  
  • Guest users will need to connect to the new UCLA_GUEST SSID
  • Pre- and post-migration communications 
  • Building signage
  • Knowledge base articles
  • Service desk training and preparation