Published on

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. CWRUnet Open Forum By CWRUnet Engineering Jeff Gumpf, Director of Engineering, CWRUnet Services January 24 th , 2002
  2. 2. Topics for Discussion <ul><li>Recent events </li></ul><ul><li>Gigabit-Ethernet-to-the-desktop </li></ul><ul><li>E-mail and calendaring </li></ul><ul><li>Windows Active Directory </li></ul><ul><li>IP v6 </li></ul><ul><li>Middleware </li></ul><ul><li>Servers and storage </li></ul><ul><li>Questions and answers </li></ul>
  3. 3. Recent Events <ul><li>Nimda and Sircam viruses making re-appearances on campus </li></ul>
  4. 4. Gigabit-Ethernet-to-the-Desktop Initiative <ul><li>Switched gigabit Ethernet to the desktop, 10 Gigabit per second backbone, 802.11a (54 Mb/s) wireless </li></ul><ul><li>Replace entire network infrastructure in about 18 months </li></ul><ul><li>Five phases </li></ul><ul><ul><li>Peter B. Lewis (May 1) </li></ul></ul><ul><ul><li>Residence halls and Greek houses (August 1) </li></ul></ul><ul><ul><li>MSASS, Glennan, Millis, Olin, Rockefeller, Adelbert, White and Wickenden (September 30) </li></ul></ul><ul><ul><li>Health Sciences Complex (December 30) </li></ul></ul><ul><ul><li>Remaining buildings (August 15, 2003) </li></ul></ul><ul><li>An Integrated Technology Partnership RFP was initiated in mid-December, responses to the RFP submitted last week </li></ul><ul><li>RFP also includes volume PC purchases among other technology components </li></ul><ul><li>Can see the RFP on a web site at: http://isweb1.cwru.edu/itp/home.htm </li></ul>
  5. 5. Gigabit-Ethernet-to-the-Desktop Initiative <ul><li>Gigabit Ethernet interoperability environment created to test components </li></ul><ul><li>Will use fiber NIC for fiber connections where possible </li></ul><ul><li>Will use fiber-to-twisted pair media converter when a device cannot support a fiber NIC (more expensive) </li></ul><ul><li>Gigabit Ethernet fiber ports only support gigabit Ethernet </li></ul><ul><li>Will use Cat5 (which will autodetect 10/100/1000 Mb/s) in locations where it is available (eg, PB Lewis) </li></ul><ul><li>Provision for a small amount of 100 Mb/s fiber in each switch </li></ul><ul><li>Laptop connectivity is currently an unresolved issue </li></ul><ul><li>Users will be responsible for the costs (NIC, media converter (if required), jumpers) at the desktop </li></ul>
  6. 6. E-mail and Calendaring <ul><li>Pilot testing of candidate products completed </li></ul><ul><li>About 100 participants from across the campus </li></ul><ul><li>IMAP candidates: MS Exchange, iPlanet Messenger, open source software (Cyrus) </li></ul><ul><li>Calendaring candidates: MS Exchange, iPlanet Calendar, Steltor Corporate Time </li></ul><ul><li>LDAP/Directory provisioned applications </li></ul><ul><li>Recommendation has been made to VPIS/CIO </li></ul><ul><li>Expect an announcement in the coming weeks </li></ul><ul><li>Will begin implementation soon </li></ul><ul><li>A variety of changes will be made in e-mail including changes to the default addressing scheme (details at announcement) </li></ul>
  7. 7. Windows Active Directory <ul><li>Advisory group has had several meetings </li></ul><ul><li>Test system operational within advisory group </li></ul><ul><li>Test system will be opened up to general campus environment soon </li></ul>
  8. 8. IPv6 <ul><li>IPv6 address obtained for CWRU </li></ul><ul><li>Developing initial basic deployment plan </li></ul><ul><ul><li>Subnet scheme/Router configuration </li></ul></ul><ul><ul><li>Basic network services: DNS, DHCP, NTP, etc </li></ul></ul><ul><ul><li>Tie-in to IPv6 backbone via OARnet </li></ul></ul><ul><ul><li>Local IPv4-to-IPv6 translation </li></ul></ul><ul><li>Goal is to support IPv4 and IPv6 simultaneously </li></ul><ul><li>Will begin involving campus testers after basic deployment plan developed and made operational </li></ul><ul><li>Lots of higher level testing will be necessary </li></ul><ul><li>Many applications will break </li></ul>
  9. 9. Middleware <ul><li>Middleware is “glue” between network and applications </li></ul><ul><li>Current user network account information system utilizes a 10 year old, home grown, custom system that requires a custom interface to applications </li></ul><ul><li>The user account system manages user access rights in addition to general user information which is becoming more important to applications </li></ul><ul><li>Plan to move to a standards based LDAP/Directory system for providing access to network user information and rights </li></ul><ul><li>Will be compliant with Internet 2 Middleware Initiative to allow for interoperation with other institutions </li></ul><ul><li>Required for e-mail and calendaring systems </li></ul>
  10. 10. E-Mail & Calendaring <ul><li>Scope/Definition </li></ul><ul><ul><li>Groupware applications have a need for a dependable messaging system </li></ul></ul><ul><ul><li>The selected messaging system should, at a minimum, provide </li></ul></ul><ul><ul><ul><li>A robust e-mail system </li></ul></ul></ul><ul><ul><ul><li>Support for software that is e-mail enabled (MAPI) </li></ul></ul></ul><ul><ul><ul><li>Common, network accessible calendaring and scheduling system </li></ul></ul></ul>
  11. 11. E-Mail & Calendaring <ul><li>End User Requirements </li></ul><ul><ul><li>Access to system will be through clients, software running locally on individual desktops </li></ul></ul><ul><ul><li>Ease of use </li></ul></ul><ul><ul><ul><li>Client software must be build with the familiar GUI available on the platform on which it is used </li></ul></ul></ul><ul><ul><ul><li>It must be well integrated into its respective platform and operate on the principle of least astonishment </li></ul></ul></ul><ul><ul><li>Platform support </li></ul></ul><ul><ul><ul><li>client software must support PC, Unix and Mac operating systems </li></ul></ul></ul><ul><ul><ul><li>We should select clients for their best fit to the respective platform </li></ul></ul></ul><ul><ul><ul><li>Clients must support Internet standards such as IMAP4, POP3, LDAP, HTML, and MIME </li></ul></ul></ul><ul><ul><li>Operability across platforms </li></ul></ul><ul><ul><ul><li>Clients in a mixed environment should be able to use and transfer e-mail between platforms using multiple clients without losing e-mail </li></ul></ul></ul>
  12. 12. E-mail & Calendaring <ul><ul><li>Support for IMAP disconnect mode </li></ul></ul><ul><ul><ul><li>Clients should allow one to download a selected set of messages, read and respond to those messages offline, and then reconnect and resynchronize the messages from the computer with the server on demand </li></ul></ul></ul><ul><ul><li>Support for PDAs </li></ul></ul><ul><ul><ul><li>PDAs should be fully supported </li></ul></ul></ul><ul><ul><ul><li>Both major platforms (Palm and Pocket PC) should be supported </li></ul></ul></ul><ul><ul><li>Easy deployment </li></ul></ul><ul><ul><ul><li>Deployment of client software may be through download or CD distribution with a preference toward download </li></ul></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><ul><li>Selected software must provide the campus community with a reliable and secure system, as well as ensuring the privacy of data </li></ul></ul></ul><ul><li>Software may be a single integrated groupware solution or a hybrid of selected components </li></ul>
  13. 13. E-Mail & Calendaring <ul><li>System Requirements </li></ul><ul><ul><li>Scalability </li></ul></ul><ul><ul><ul><li>Must scale well to meet current and future needs </li></ul></ul></ul><ul><ul><ul><li>Should handle growth in various resource needs (eg, users, traffic) </li></ul></ul></ul><ul><ul><li>Management tools </li></ul></ul><ul><ul><ul><li>Should be easily managed both centrally and in a distributed fashion </li></ul></ul></ul><ul><ul><ul><li>Tools should be accessible locally and remotely </li></ul></ul></ul><ul><ul><li>Problem resolution </li></ul></ul><ul><ul><ul><li>Must readily lend itself to problem resolution </li></ul></ul></ul><ul><ul><ul><li>Tools should be available to assist in problem determination and solution </li></ul></ul></ul><ul><ul><li>Interoperability </li></ul></ul><ul><ul><ul><li>E-mail and calendaring solution must coexist in a heterogeneous and sometimes eclectic menagerie of pre-existing systems </li></ul></ul></ul>
  14. 14. E-mail & Calendaring <ul><ul><li>Data store </li></ul></ul><ul><ul><ul><li>The data of the system must be stored so as to maximize speed of access of the data </li></ul></ul></ul><ul><ul><ul><li>Data must not be easily corrupted </li></ul></ul></ul><ul><ul><ul><li>In the event of data corruption, it must be easily restored </li></ul></ul></ul><ul><ul><li>Performance </li></ul></ul><ul><ul><ul><li>System should perform to expectations, ie, be fast </li></ul></ul></ul><ul><ul><ul><li>Tools should be available to measure performance </li></ul></ul></ul><ul><ul><li>Coexistence of directory structure – must coexist with CWRU’s directory structures and support standard LDAP implementation </li></ul></ul><ul><ul><li>3 rd Party Software - Messaging is a pervasive and deeply rooted technology and many applications have been written to exploit it. Any e-mail system selected must be able to support a wide array of 3 rd party software </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><ul><li>The chosen system must have a robust authentication mechanism </li></ul></ul></ul><ul><ul><ul><li>Data must be secure and well insulated from either inappropriate casual viewing or aggressive attempts to compromise data integrity </li></ul></ul></ul>
  15. 15. E-mail & Calendaring <ul><li>Operations Requirements and Impacts </li></ul><ul><ul><li>Selected software must support SNMP for monitoring the system </li></ul></ul><ul><ul><li>Operator interfaces </li></ul></ul><ul><ul><ul><li>Candidate software should have excellent monitoring views and maintenance dialogs for operators </li></ul></ul></ul><ul><ul><ul><li>Software should have an API for customized software development </li></ul></ul></ul><ul><ul><li>Training and Documentation - Vendor must have excellent training materials and proper documentation </li></ul></ul><ul><ul><li>Backups – software must support a broad range of backup software and techniques </li></ul></ul><ul><ul><li>Operator workload – software should minimize operator workload </li></ul></ul><ul><ul><li>Service contracts – supported by vendor </li></ul></ul><ul><ul><li>Maintenance – minimize downtime for maintenance activities </li></ul></ul>
  16. 16. E-mail & Calendaring <ul><li>Candidate Systems </li></ul><ul><ul><li>E-mail </li></ul></ul><ul><ul><ul><li>Microsoft Exchange </li></ul></ul></ul><ul><ul><ul><li>iPlanet Messaging </li></ul></ul></ul><ul><ul><ul><li>Open software (freeware) messaging </li></ul></ul></ul><ul><ul><li>Calendar/Scheduling </li></ul></ul><ul><ul><ul><li>Microsoft Exchange </li></ul></ul></ul><ul><ul><ul><li>Steltor Corporate Time </li></ul></ul></ul><ul><ul><ul><li>iPlanet Calendar </li></ul></ul></ul><ul><li>Evaluation underway – will publish to the web </li></ul><ul><li>Pilot of all systems between now and end of calendar year </li></ul><ul><ul><li>Small group of representative community members will be asked to join </li></ul></ul><ul><ul><li>Will need to try all of the candidate systems </li></ul></ul>
  17. 17. The End <ul><li>Thank you for attending today’s open forum! </li></ul><ul><li>Questions and Answers </li></ul>