1 / 23

Managing 2000+ Windows/NT Servers in a Wan/LAN Environment

Managing 2000+ Windows/NT Servers in a Wan/LAN Environment. Stan Dylnicki Royal Bank Financial Group CMG Orlando December 13, 2000 stan.dylnicki@royalbank.com (416) 348-4469. Agenda. Environment Background Issues Methodology Current Status Tools Future. Bank Environment.

adeola
Download Presentation

Managing 2000+ Windows/NT Servers in a Wan/LAN Environment

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Managing 2000+ Windows/NT Servers in a Wan/LAN Environment Stan Dylnicki Royal Bank Financial Group CMG Orlando December 13, 2000 stan.dylnicki@royalbank.com (416) 348-4469

  2. Agenda • Environment • Background • Issues • Methodology • Current Status • Tools • Future

  3. Bank Environment • Largest Bank in Canada • 49,000 employees • 2,000 IT employees • 1,600 branches

  4. Bank Environment • 4 Processing Centres across Canada • 3 Campus environments • Districts & Service Delivery • Business Banking Centres • Branches

  5. PC/LAN Environment • 30,000 Windows NT • 10,000 Windows/95, DOS, OS/2, PCs • 2,000 Windows NT servers • 100 OS/2 servers • Head Office, Branch, Business Banking

  6. Application Environment • Most applications ports from DOS & OS/2 • New applications developed in Visual Basic • Client data is on mainframes • Majority of applications are bought solutions & modified for multi-tier

  7. Background • My background is mainframe • Lessons learned from OS/2 deployment • Proactive branch support • Move from OS/2 to NT

  8. Issues • Large number of servers & locations • Diverse types of servers • Many configurations & hardware • Performance data hard to get • Applications written for functionality (not necessarily for performance) • Bought solutions don’t always scale across platforms • Systems Management emerging

  9. More Issues • How to report on large number of servers • How to collect enough information without overloading network • Explosive growth of memory and disk on desktops • Explosive growth of File servers disk space • Explosive growth of Internet usage

  10. Methodology • Use alert tool for performance monitoring • Don’t collect everything • Size servers & desktops for life of the box • Manage & report by exception • Provide tools to users so they can diagnose their own problems • Provide limited set of reports

  11. Current Status • All NT images include a performance agent • Classify servers by type • Provide exception reports to area managers • Pilot disk quota monitoring • Provide web access for management reporting • Benchmark hardware to understand capacity limits

  12. Tools • Tivoli alert agent – performance & availability • NTSMF collectors • SAS ITSV repository • Web reporting • Desktop Memory Monitor • Benchmarks: Iometer, Netbench, Sysbench, SYSMARK32

  13. NTSMF & SAS ITSV Data Flow NTSMF NTSMF

  14. SAS ITSV Environment • Repository & IIS • Netfinity 5500 Server • 2 Pentium II 450 cpus • 512 MB RAM • Raid-5 (9 GB X 6) • FTP Server (shared) • Dell 6100 Server • 4 Pentium Pro cpus • 512 MB RAM • Raid-5 (9GB X 6)

  15. SAS ITSV Processing Statistics

  16. SAS ITSV Processing by Database

  17. SAS ITSV Server Counts

  18. Web Reporting System

  19. Web Reporting System

  20. Web Reporting using Excel

  21. Web Reporting using Excel

  22. Future • Encourage application developers to use performance tools • SAN solutions • Clustering & Win2000 Datacentre • NTSMF on selected desktops • Measure transactions & response time

  23. Summary & Lessons Learned • Avoid writing your own tools • Server naming conventions important • Administration required and not trivial • Data loss from sites inevitable • Randomize FTP transmissions

More Related