Notes from LIS Council - 10/9/13

  • LIS New Services Work
    • We worked toward finalizing the LIS new services communication.  We anticipate having it sent out next week.
  • LIS Operational Agenda
    • Network & Systems
      • Adam compared network bandwidth usage comparing charts from last year and this year.  Traffic is up and the number of hours our “pipe” is full or nearly full is increasing.  At the end of the last school year we had nearly 5700 devices registered on our network.  This month we are at 5550 and that number is climbing.  We expect a number greater than 5700 by end of May.  Looking at wireless devices we have many more of them and they are on and attached to the wireless network for more hours of the day.  Many are on overnight.
    • User Services
      • No report this week.
  • New Items
      • Server Network Firewall Interface
        • Over Fall Break, Adam is looking at changing our internal network so that the data center servicers are behind an internal firewall interface isolating it from the rest of the Luther network.  Timing and communication plans are being developed.
      • OpenDNS renewal
        • We discussing the pricing and value of the OpenDNS service.
      • VOIP based phonathon
        • This past Monday the system went into use.  The phonathon team has been working independently and has not required LIS support as in previous years. Adam commented that the Voice Over IP (VIOP) phones might have contributed 3-5 Mbps to the traffic load on our network connection; easily handled.
      • Network Sentry updated
        • Adam reported a new version of the Network Sentry was updated as planned.  He also shared that with the licensing has change from per person to per device.  The company has re-evaluated the conversion factor.
    • Returning Items
      • Wireless in Towers
        • Adam is continuing to process work orders from towers wireless users and others.  Generally speaking the solution is to move users and their devices to the 5Ghz network reducing interference on the 2.4Ghz network.  Eliminating rogue networks also reduces interference.
      • Metronet update
        • Equipment has been installed to light up the network. The next step is connecting entities.  There has been damage to an overhead portion and the Metronet group is looking at repair options that will preclude such damage in the future.  The group is working with its first revenue generating customer that wants to lease some of the currently unused fibers as part of their network.