01/24/02
Upcoming SlideShare
Loading in...5
×
 

01/24/02

on

  • 220 views

 

Statistics

Views

Total Views
220
Views on SlideShare
220
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

01/24/02 01/24/02 Presentation Transcript

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