Restricted/Limited Access Network project meeting

Monday, December 3, 2012; 3:00 p.m.; AISB-208

Invited

Phil Benchoff, Jacob Dawson, Marc DeBonis, William Dougherty, Peter Franchi, Brian Jones, Ron Keller, Dean Kirstein, Philip Kobezak, Greg Kroll, Steve Lee, Randy Marchany, Rich Sparrow, Lucas Sullivan

Agenda

1. Review action items from 20121105 - November 5, 2012 RLAN Project Status Meeting
2. Status Updates
   1. Status of the RLAN implementation in Student Services building.
   2. Status of the RLAN implementation in other buildings.
   3. Other
3. ITSO preferences for 802.1X and host registration
4. ITSO would like to have separate DHCP and DNS inside RLAN (Phillip)
5. RLAN concurrency with UC
6. RLAN business processes
   1. Procedures for user community in procurement of RLAN services
      1. Who do they contact initially for ordering RLAN and what is the process from that point forward?
      2. How do they report a problem with RLAN (Can we have them help us identify that it is RLAN and what flavor?)
   2. Procedures for ITSO for RLAN approval and initiation of RLAN service
      1. How and when does ITSO get involved? Are they the first point of contact or should CNS O&P send RLAN requests to ITSO…
      2. What is the approval process for RLAN services and how is it communicated to CNS? (possible problem-report/trouble-ticket process?)
   3. Procedures for the Operations Center (Diagnostics, 4HELP, etc…)
      1. How do we handle problem reporting and escalation for this new service?
      2. How does the OPs Center identify this service?
      3. What are the differing network portions for troubleshooting and diagnosing RLAN issues? (Different procedures necessary for different options…?)
   4. What other impacts does this initiate?
      1. I assume there are Business Services impacts concerning charges and account codes
      2. There are probably Ordering and Provisioning (O&P) issues with new Service types and charges
      3. Work order type and Queue process (Are there changes needed for Atlas forms and queue processing for RLAN?)
      4. Special consideration for Field Engineering for the installation if RLAN services depending on the type of RLAN service being installed, and whether the location is already converted to Unified Communications or not, and how many existing network connections and infrastructure are at the location
      5. Who makes changes to the firewalls? If it is CNS we need to incorporate this into our ECO process. Do we get approval/requests for FW changes from the ITSO?
      6. What are the ITSO's contacts for escalation for possibly broken RLAN parts?
      7. Who maintains maintenance contracts/budgets and on what parts?
7. Open forum

Attended

Phil Benchoff, Jacob Dawson, Marc DeBonis, Brian Jones, Ron Keller, Philip Kobezak, Greg Kroll, Steve Lee, Randy Marchany, Lucas Sullivan

Meeting Notes

1. Review action items from 20121105 - November 5, 2012 RLAN Project Status Meeting
   1. New Action Item: Marc explained his needs and Ron will get him the appropriate connection for the data center (a cable to RLAN and an IP address).
      1. Somehow an Interdepartmental Communications Request (ICR) needs to be completed to document the connection and cost even though there is no cost. Without an ICR this will be an undocumented circuit and will lead to problems down the road.
      2. Ron indicated the RLAN connection for Marc in done and the cable is laying on the rack with Marc's name on it.
      3. Action item: Marc should get an IP address for this RLAN connection from Ted Leinhardt and Marc should share that address with hostmaster.
      4. Marc should have a regualar (non RLAN) data center connection from Mike Moyer already.
2. Status Updates
   1. Status of the RLAN implementation in Student Services building.
      1. One connection has been completed.
      2. Stephen Huff is working on getting the secure client installed. He is busy right now.
   2. Status of the RLAN implementation in other buildings.
      1. Torgersen connectivity testing compelete.
      2. Limited connections in AISB, Student Services, and Torgersen.
   3. Other
      1. Marc reported 50 users in the CSDI pilot. Includes Shiffert, Controller, Internal Audit, and the Foundation.
3. ITSO preferences for 802.1X and host registration
   1. Goal is to be able to track a secure machine and the registered owner of the secure machine.
   2. There was a discussion about using the MAC addresses of the machine to uniquely identify the computer and to check that it is the registered computer for use on the RLAN.
4. ITSO would like to have separate DHCP and DNS inside RLAN (Phillip)
   1. It was agreed that only static IP addresses would be used initially.
   2. It was also agreed there would be no wireless access to the RLAN.
5. RLAN business processes
   1. NI&S is no longer using 802.1x for Unified Communications (UC) connections. Older, already installed connections will continue to use until certificate expires. UC has its own VLAN.
   2. Recall we cannot physically do 3 VLAN connections on UC. (1) is for phone, (2) is for data, and (3) which is not possible would be for RLAN.
   3. Action item: Revisit this agenda item at next meeting (12/17/2012) and invite Joe Hutson.
6. Open forum
   1. Draft business processes
      1. User contacts NI&S requesting an RLAN connection and completes an ICR.
      2. NI&S's Ordering & Provisioning (O&P) emails a scanned copy of the ICR to ITSO@vt.edu
      3. ITSO approves (i.e., vet users needs and machine) RLAN connection request and sends the approved ICR back to O&P.
      4. O&P follows normal procedures on receipt of the approved ICR.