Restricted/Limited Access Network project meeting

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

Invited

Jacob Dawson, Marc DeBonis, William Dougherty, Brian Jones, Ron Keller, Philip Kobezak, Greg Kroll, Steve Lee, Randy Marchany, Rich Sparrow

Agenda

  1. Review action items from 20120702 - July 2, 2012 RLAN Project Status Meeting
  2. Status updates
  3. Project Management Documentation
    1. Still need estimates of hours worked on this project and any other budget items from:
      1. Randy Marchany, Marc DeBonis, Brian Jones, Philip Kobezak, Jacob Dawson, Phil Benchoff
  4. Open forum

Attended

Phil Benchoff, Steven Bowman, Jacob Dawson, Marc DeBonis, William Dougherty, Brian Jones, Ron Keller, Greg Kroll, Steve Lee, Randy Marchany

Meeting Notes

  1. Review action items from 20120702 - July 2, 2012 RLAN Project Status Meeting
    1. Action item: Need to cost user network connection. No one was sure what this meant exactly so discussions revolved around the need for multiple network connections for end users and the technical possibility of supplying multiple connections from a single data port on the new Unified Communications (UC) phones.
      1. Randy's solution requires two IP addresses. One for the host (secure) machine, and a second for unsecured access to the Internet.
      2. Randy mentioned that he asked Erv who would pay if multiple ports are needed. Erv said the user would only pay for a single port.
      3. There was some discussion about the technical possibility of 3 VLAN's on the new UC phones. Action item: Steve Lee will investigate whether this is possible or not.
      4. One solution presented is to use VPN for the secure connection to the RLAN. This project purchased 1000 licenses for VPN. There is an estimated 2000 users of the RLAN. Action item: User access to RLAN must be approved by ITSO so when that number begins to grow ITSO will alert CNS to purchase more licenses.
  2. Status updates
    1. 10 Gb ASA's in order to implement the campus network needs to be down so this is only feasible during a holiday break. Hopefully Thanksgiving time 2012. (See Meeting Note 3.b here 20120614 - June 14, 2012 RLAN Project Status Meeting)
    2. Randy has the early adopters ready to begin using the RLAN.
    3. Action item: Ron needs the building name and number of RLAN users in that building before they can begin using the RLAN.
    4. Action item: Marc needs access to the Management Network for his desktop solution to work. Phil mentioned that in the worse case they could "poke a hole in the firewall" for him.
    5. Action item: For ICR will need to request RLAN service and individual user portal information (their location).
    6. What about end user support. Tentative plans are to have 4Help front all calls and direct the calls to the appropriate technical people. Action item: 4Help should be invited to these meetings when the network is closer to working/production.
    7. The ITSO must approve access to the RLAN so they will have a list of all users. This is useful for end user support purposes.
  • No labels