Restricted/Limited Access Network project meeting

Monday, December 17, 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. Reminders:
    1. Scott Midkiff will be attending February 4. 2013 meeting which has been moved from 3:00 pm to 1:30pm
    2. Request for estimated hours worked on RLAN project due to Greg 12/19/2012 (see email from Greg dated 12/5/2012)
  2. Review action items from 20121203 - December 3, 2012 RLAN Project Status Meeting
  3. Status Updates
    1. Status of the RLAN implementation in Student Services building.
    2. Status of the RLAN implementation in other buildings.
  4. RLAN business processes
    1. Review Meeting Note 6a from 20121203 - December 3, 2012 RLAN Project Status Meeting
    2. 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. What are the plans for implementing the RLAN solutions we’ve all talked about into groups and departments that don’t have any internal IT staff?
      3. How do they report a problem with RLAN (Can we have them help us identify that it is RLAN and what flavor?)
    3. 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?)
    4. 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…?)
    5. 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?
  5. Open forum

Attended

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

Meeting Notes

  1. Reminders:
    1. Done
  2. Review action items from 20121203 - December 3, 2012 RLAN Project Status Meeting
    1. Action item: Marc should get an IP address for this RLAN connection from Ted Leinhardt and Marc should share that address with hostmaster.
      1. Marc reported that Ted did not have addresses for the RLAN.
      2. After some discussion it was decided that the ITSO will be given IP address blocks in order to assign IP addresses to users since they have to approve the users anyway and having the IP address (and other registration information) would be helpful to the ITSO in tracking RLAN users.
      3. Randy approved an IP address for Marc's use in the data center. Action item: Ron will send a RLAN IP address to Marc and cc the hostmaster. Note: Ron reported this item completed on 12/18/2012.
      4. New Action item: Ron will send a list of IP address blocks for each subnet on campus for use on the RLAN.
      5. Phillip reported that the ITSO RLAN simple registration system is working. This will gather necessary user information for RLAN approval by the ITSO.
  3. Status Updates
    1. Nothing new to report.
    2. CNS is waiting on Roger Anderson (sys admin in Financial Aid) to give them portal information for an RLAN test port.
    3. There was some discussion about the impact on the RLAN project from the communications being done for the Unified Communications (UC) project. In order to save costs the decision was made to have the UC presentations to departments include something about the RLAN. If we separate these two projects completely costs will rise.
    4. The UC schedule is here http://www.nis.vt.edu/uc/schedule
  4. RLAN business processes
    1. Brian has started documenting "RLAN Procedures". Note: access restrictions to the wiki space Brian is using may prevent some project team members from viewing this page. https://wiki.cns.vt.edu/x/65brAg
    2. CNS Ordering & Provisioning (O&P) Team needs to be able to give users some idea of turn around on RLAN requests. Since ITSO is doing approvals and now handing out IP addresses they need to figure out some reasonable turn around time for end users. O&P also needs a contact number.
      1. Contact phone number is Phillip's phone at 231-2441 and email contact is ITSO@vt.edu (which goes to all in ITSO).
    3. This project is going to need some basic communications/advertising on what the RLAN is, what is required, why it is needed, etc.
    4. The project is going to need a FAQ
      1. Should begin now and populate it slowly.
      2. May put these FAQ's in the KnowledgeBase in the future but not initially.
      3. Example: RLAN setup for end users requires some IT support, what are users that do not have IT support supposed to do? Answer: Use a permanent, departmental, secured machine or use the Cyber Security Desktop Initiative (CSDI) solution.
      4. Action item: Figure out where is the best "home" for information about the RLAN including this FAQ. Some suggestions include ITSO website and www.computing.vt.edu