Advanced Server for Open. VMS & PATHWORKS Brad Mc. Cusker Compaq Computer Corporation
Agenda § Current product overview § Future release plans § Tech overview of new features § Windows 2000 integration § Wrap-up 2
Agenda èCurrent product overview § Future release plans § Tech overview of new features § Windows 2000 integration § Wrap-up 3
Open. VMS File & Print Servers § Advanced Server for Open. VMS V 7. 21 – Current Release - V 7. 2 A (Jul 99) – ECO 4 available Feb 2001 § PATHWORKS V 6 for Open. VMS (Advanced Server)1 – Current Release - V 6. 0 C (Dec 99) – ECO 2 available Feb 2001 § PATHWORKS V 5 for Open. VMS (LAN Manager) – Current Release - V 5. 0 F-ECO 2 (Feb 99) 1 file server code based on the Advanced Server for Unix (AS/U) OEM product from AT&T 4
PATHWORKS V 5. 0 (LAN Manager) § Implements LAN Manager V 2. 2 SMB protocol § Provides – basic file and print services – remote management capability – access to alternate file system - FAT – Single logon – LM V 2. 2 security model § Supported on Open. VMS V 5. 5 -2 VAX 5
PATHWORKS V 6. 0 Features § Provides Windows NT Server networking on Open. VMS – LAN Manager 3. 0 SMB protocol – Trusted Domain support – Wide Area Domain support – Full Browser support – NT Management APIs – ADMINISTER comprehensive command line interface – Open. VMS Cluster support – Password Synchronization for network users § Supports Open. VMS V 7. 2, V 7. 1, V 6. 2 6
Advanced Server V 7. 2 Features § Provides Windows NT Server networking on Open. VMS § Includes PATHWORKS V 6. 0 features, plus. . . – Extended File Naming (ODS-5) support – Open. VMS Registry – External Authentication – Events § Open. VMS Alpha V 7. 2 support 7
What is Advanced Server for Open. VMS? § Advanced Server V 7. 2 for Open. VMS – A “new” product – Based on PATHWORKS V 6 (Advanced Server) – Windows NT file & print on Open. VMS V 7. 2 Alpha – More tightly coupled to Open. VMS than is PW V 6 § takes advantage of new Open. VMS V 7. 2 Alpha features § released and distributed with Open. VMS V 7. 2 – New features are NT Affinity related 8
PATHWORKS? Advanced Server? What's the difference? § PATHWORKS was the original product, § Advanced Server for Open. VMS is the next generation – But, its based on the same code base… § For much of this discussion, the names are interchangeable – Differences will be explicitly mentioned 9
PATHWORKS 32 Client SW Update § PATHWORKS 32 V 7. 2 – Available June, 2000 – Supports Windows 2000, Windows NT 4. 0, Windows 95, Windows 98 – http: //www. Open. VMS. Compaq. com/pathworks 32/ § Contact Information – Product Manager: – Bette. Ruyffelaert@Compaq. com – Telephone #: 978 -506 -5713 10
Network Clients Open. VMS file and print server environment DOS/Windows/WFW Win 95/98 Network Servers Network WNT Workstation Windows 2000 PATHWORKS Advanced V 6 for Server for Open. VMS V 7. 3 Windows NT Server Windows 2000 Server Compaq Advanced Server for UNIX 11
Open. VMS File and Print Servers The idea is…. To the network user. . . Open. VMS Servers look and feel like NT servers 12
Which ones are Open. VMS? Why are these unavailable? 13
Agenda § Current product overview èFuture release plans § Tech overview of new features § Windows 2000 integration § Wrap-up 14
Advanced Server for Open. VMS future releases § Advanced Server V 7. 3 (Alpha Only) (H 1 CY 01) – Planned Release: April 2001 § FCS – April 24, 2001 § Also ships with Open. VMS V 7. 3 § Q 2 -2001 Software Product Library – – – – Open. VMS V 7. 3 support (V 7. 2 -1 also) Member server role Extended character set Alias file names NT print management (Spool. SS) support DNS load balancing capabilities PCSI support 15
Advanced Server for Open. VMS Future Releases (2) § Advanced Server V 7. 4 – Estimated release: CY 2001/2002 – Enhanced Windows 2000 Interoperability including Active Directory – Performance improvements – Opportunistic locking support – Unicode – Other considerations: § Open. VMS V 7. 2, V 7. 3 VAX support § Open. VMS V 6. 2, VAX & Alpha 16
Advanced Server for Open. VMS Future Releases (3) § V 7. 4 might become V 7. 3 next, V 7. 3 next+, etc – Smaller releases – More frequent – Deliver features as they are completed § Less delays § ECOs as needed 17
PATHWORKS for Open. VMS Future Releases § PATHWORKS V 6. 0 D – Open. VMS V 7. 3 (V 7. 2 and V 6. 2 too!) § VAX and Alpha – FCS – April 24, 2001 – Also ships with Open. VMS V 7. 3 – Q 2 -2001 Software Product Library § PATHWORKS V 6. 1 for Open. VMS – Q 3 -2001 – Member Server – Alias file names § PATHWORKS V 5 for Open. VMS – Maintenance updates only 18
Tech Tip: Advanced Server V 7. 3 § Open. VMS V 7. 3 & Open. VMS V 7. 2 -1 registries incompatible – Must upgrade Open. VMS on all cluster nodes which will run the registry – Registry must be running on all Advanced Server nodes § All cluster nodes which will run Advanced Server must upgrade Open. VMS simultaneously – Registries on Open. VMS V 7. 2 -1/Open. VMS V 7. 3 will not work together in a cluster § Open. VMS V 7. 2 -2 should be compatible with Open. VMS V 7. 3 19
Agenda § Current Product Overview § Future release plans èTech overview of new features § Windows 2000 integration § Wrap-up 20
Futures § Alias file names § PCSI Installation § Extended character sets (ECS) § DNS name resolution § NT print management (Spool. SS) § Member server § Licensing § Performance Enhancements 21
Alias file name support (V 7. 3, V 6. next) § Problem: PW & AS do not currently provide a “short name” alias (8. 3 name) for file names – Some applications use only the alias name instead of the full name. § Solution: Provide an “ 8. 3” alias for files and folders – The alias name is a compressed encoding of the file’s F-11 File ID § Available in AS V 7. 3 and PW V 6. 1 22
Alias Example 23
Alias File Name Support – Tech Tips § Nothing to configure § Possible to disable: $ define/system PWRK$TEMP_ODS 2_DISABLE_ALIAS_FILENAMES 1 – Server restart required – No known reason to do this 24
PCSI Support (V 7. 3) § Installation will be by PCSI only – No savesets § Other Install/Config changes – While we were in there…. – Minimize Reboots § Better support for multiple system disks – Improve messages and displays 25
PCSI & Install/Config Tech Tips § Install/Config/Start ordering more strictly enforced § PCSI controls order of operations – Some things may seem out of order § Config has new options: – Member Server, ECS, DNS, NT Print Management – All described later 26
Extended Character Set Support (V 7. 3) § Add support for additional character sets – Languages with single byte ASCII based encodings – Languages supported by Open. VMS C-RTL § Support for naming of most user-defined object: – User names, group names, shares, files, etc… § Supported to be determined – dependent on qualification – Currently only English and Hebrew supported § Advanced Server V 7. 3 27
ECS Configuration/Management § Configuration (PWRK$CONFIG) option 9 prompts for language. –Default: English (USA) § Restriction: –Supports one language at a time –Computer, domain, trusted domain, and alias names unsupported at this time 28
ECS: New ADMIN Commands § SET MODE – /INPUT=VTF 7 | RAW – /OUTPUT=VTF 7 | RAW § DEFAULT is RAW § VTF 7: Extended characters represented in ^u. XXXX format § RAW: No character conversion § See HELP for more details § SHOW MODE – Displays current settings 29
Configuration Menu 30
Configuration Prompt for Language § Selecting item 9 gets you to this screen: 31
Creating/Using a ECS disk share: 32
Example of a Mounted File Share 33
Cluster Alias Load Balancing (V 7. 3, V 6. 0 C) § Allows use of DNS for alias name resolution § Cluster load balancing may now be done using DNS and BIND 8. 1. 1 § Documented in AS V 7. 3 Server Admin Guide and V 6. 0 C-ECO 1/V 6. 0 D release notes § V 6. 0 C and AS V 7. 3 34
Cluster load balancing in prior versions § LAN clients – Broadcast name resolution based – Dynamic load-balancing based on periodic load calculation § WAN clients – LMHOSTS and WINS based – No load balancing - based on static information 35
Cluster load balancing in V 7. 3/V 6. 0 C § LAN clients – Same as in prior versions § WAN clients – Configurable, calculated, dynamic load-balancing based on load – Uses TCP/IP Services for Open. VMS V 5. 0 or later – Requires DNS server running BIND 8. 1. 1 or later § § Accepts dynamic updates Entry for the Advanced Server cluster alias name Authoritative server for TCPIP domain Answers name queries for the Advanced Server cluster alias name 36
Dynamic cluster load balancing with DNS § Metric server – Configured and run on each cluster member – Periodically calculates system load § Load broker – Periodically polls all metric servers – Builds ordered list based on current load – Dynamically updates DNS server 37
Name Resolution Tech Tips: § If Enabling Dynamic Alias Resolution… – Remove static entries for cluster alias! § Added ability to use DNS for Name Resolution – Enabled via PWRK$CONFIG/Transports – DNS used as last resort § After LMHOSTS, broadcast, WINS 38
NT Print Management Support (V 7. 3) § NT style management of printer resources – Specifically, added the SPOOLSS pipe § Use NT Print Manager to manage Open. VMS printer resources – ADMIN CLI will have minimal print management support § This is Optional § Allows print drivers to be stored on Advanced Server for downloading to the client 39
Configuration Prompt to Change to NT Style Printing Default is NO 40
Upgrading Existing Printers § Existing Printers = Printer Shares defined on AS at time NT Style Printing is enabled § Automatically upgraded when choosing “Enable NT Style Printing” § Upgraded printers will have restricted manageability & functionality – Print Manager won’t work – No drivers § Upgraded printers will need to be deleted and re-added via NT Print Manager to gain full management functionality 41
Adding New Printers § “Add Printer” in Printers Folder on AS system § Select Port will show available Execution Queues on Open. VMS § Specify Printer Name § Provide Printer Driver – From CD-ROM, or other location – Stored on Advanced Server for downloading to clients 42
What about generic queues? § Open. VMS generic queues point to multiple execution queues (one to many relationship) § Prior to NT Style Printing, it was possible to share generic queues to the network § NT Print Manager will display Execution Queues as Printer Ports – Generic Queues will not show up as a ‘port’ – In other words, they can’t be shared with NT Style management as they were previously 43
Printer Pooling § Problem: How do I retain the one-to-many functionality of generic queues? § Solution: Printer Pooling – Enable “Printer Pooling” in the Add Printer applet – Select the Printers to be shared – Let Advanced Server handle the one-to-many relationship!!! 44
Printer Pooling (2) § Select Printer Pooling § Select all the execution queues that will be used by this Printer § Continue with the Wizard 45
Restrictions § Upgraded Printers don’t have full capabilities § Once you choose NT Style Printing, it is difficult to go back – Will require restore from backup § Limited support from the ADMIN CLI 46
Restrictions (2) § Printer Properties-Scheduling– Priority Not Implemented 47
Restrictions (3) § Printer-Properties-Security – Take Ownership Not implemented 48
Tech Tips § Use Refresh button to view print job changes 49
CAUTION! § Performance Issue with NT Print Management § More than 100 printers – not recommended at this time – Larger systems can support more – No firm benchmarks available – Trying to improve for future release 50
Member Server Role (V 7. 3, V 6. 1) § Adding support for the member server role – Current PW/AS servers only support PDC & BDC roles § Behavior when using member server role: – Server does not participate in SAM replication – Domain NETLogon requests not processed – User authentication for connecting clients passed through to a domain controller § Allows PW/AS to participate in a pure Windows 2000 domain 51
Member Server Role - Configuration § Role Changes – PDC to BDC, BDC to PDC § ADMIN SET ROLE – Mem. Srv to BDC, BDC to Mem. Srv § PWRK$CONFIG – Mem. Srv to PDC, PDC to Mem. Srv § Not Applicable § Must go to BDC first – Server Manager § No change for domain controllers § Not applicable for Member Servers (NT does not support) 52
Other New Features (V 7. 3 and V 6. 0 C) § PWRK$LMDMN Process removed to improve performance – Documented in the Release Notes § File Security Improved – STORE_SECURITY_ACES parameter controls application of Open. VMS ACLs § See V 7. 3 Admin Guide § Also, V 6. 0 C(and later) Release Notes 53
License policy § All client access to PW V 6 & AS V 7. 2 must be licensed § All client access requires a “Client-Access” license – PWLMXXXCA 06. 00 - PW-V 6. 0 – PWLMXXXCA 07. 02 - AS-V 7. 2 – PWLMXXXCA 07. 03 - AS-V 7. 3, PW-V 6. 1 § May be used as a client-based or server-based license – Per seat (replaces FPA) – Per server (replaces FPS) 54
V 7. 3 Licensing Tech Tips § Upgraded license required for V 7. 3 – …CA 07. 02 won’t allow access to V 7. 3 resources § Upgrade license required for V 6. 1 – …CA 07. 02 and CA 06. 00 won’t allow access to V 6. 1 resources § V 6. 1 and V 7. 3 require …CA 07. 03 license 55
Performance Enhancements 1. Improve performance monitoring and analysis tools – PWMON updated, improved – Perf. Lib updated and enhanced – Client Monitor tool no longer supported 2. General Performance Enhancements § § Faster directory cache (V 7. 3, V 6. 1) Memory management (V 7. 3) Faster data-cache (V 7. next) Opportunistic Locking (V 7. 4) 3. Major Enhancements § Multi-process server § Galaxy based improvements 56
High Availability § Availability/Stability – Always the top priority – SAM replication issues resolved – Directory cache problems resolved § Reliability (Non. Stop) is the goal § Minimize reboots (V 7. 3) § Rolling upgrades § Scalability – Multi-process Server § See next slide 57
Scalability § In the works…. EXTSMB> pwshow Open. VMS V 7. 1 -2 Pid on node EXTSMB 20 -MAR-2001 14: 23: 22. 75 Process Name State Pri I/O 2020073 A NETBIOS HIB 5 78 2020074 B PWRK$ADMIN_0 LEF 6 2020073 F PWRK$KNBDAEMON HIB 20200742 PWRK$LICENSE_R 20200747 Uptime 18 00: 13: 23 CPU Page flts Page 0 00: 00. 05 71 4 51 0 00: 00. 11 126 8 11 137 0 00: 00. 43 240 28 HIB 11 160 0 00: 00. 53 453 19 PWRK$LMMCP HIB 11 1229 0 00: 00. 55 457 30 202004 CD PWRK$LMSRV_0 HIB 11 999 0 00: 03. 34 1263 42 202004 CF PWRK$LMSRV_1 HIB 11 1680 0 00: 02. 41 1143 20 20200745 PWRK$MASTER HIB 6 242 0 00: 00. 35 358 6 2020073 D PWRK$NBDAEMON HIB 11 33 0 00: 00. 10 58 110 13
Agenda § Current product overview § Future release plans § Tech overview of new features èWindows 2000 integration § Wrap-up 59
Win 2 K & PATHWORKS V 5 § PATHWORKS V 5 - Best Effort only – No plans for official support § Clients – Customers tell us they work – Patches Available § Servers/Domains – PW V 5 is an LM 2. 2 Server – Expect restrictions for W 2 K and LM 2. 2 Servers 60
Win 2 K and Current Releases § Advanced Server V 7. 2 A & PATHWORKS V 6. 0 C/D § Officially, not in the SPD § Clients – Patches required – Intend to support W 2 K client – Engineering accepts escalations § Servers/Domains – PW & AS have same restrictions as NT 4. 0 – Must be BDC to Win 2 K PDC 61
Windows 2000 Integration Plans § Phase 1 - Current releases: V 7. 2 A and V 6. 0 C/D – PW/Adv. Ser as NT 4. 0 Domain Controller – Windows 2000 Mixed Mode domain § Phase 2 - Next releases: V 7. 3 and V 6. 1 – PW/Adv. Ser as an NT 4. 0 Member Server – Window 2000 pure Multi-Master configuration § Phase 3 - Advanced Server V 7. 4 – Active Directory Integration § Make Open. VMS resources available in AD 62
Phase 1: Advanced Server V 7. 2 A AD Updates & Access Account Replication Active Directory for Domain Windows 2000 Server Mixed Mode Primary Domain Controller Advanced Server for Open. VMS V 7. 2 A Backup Domain Controller DOMAIN NT 4. 0 Backup Domain Controller Advanced Servers & NT 4 servers participate in the 63 W 2 K Mixed Mode Domain as a Backup Domain
Phase 2: Advanced Server V 7. 3 Authentication Requests Advanced Server for Open. VMS V 7. 3 Member Server AD Updates & Access Active Directory for Domain Windows 2000 Server Domain Controller DOMAIN NT 4. 0 Member Server Windows 2000 Server Domain Controller Advanced Server provides resources in a W 2 K Multi. Mastered Domain as a Member Server and relies upon W 2 K for authentication 64
Phase 3: Active Directory Integration Authentication Requests AD Updates & Access Active Directory for Domain Windows 2000 Server Domain Controller AD Updates & Access Advanced Server for Open. VMS V 7. 4 Enhanced Member Server DOMAIN Windows 2000 Server Domain Controller Advanced Server participates in the W 2 K Multi. Mastered Domain by interacting with the Active 65 Directory
Agenda § Current product overview § Future release plans § Tech overview of new features § Windows 2000 integration èWrap-up 66
Enterprise file and print roadmap 2000 2001 2002 2003 Advanced Server 7. 3 a (Alpha Only) (H 2 CY 00) (Alpha Only) (w/ OVMS V 7. 3 • Member server support H 1 CY 01) Version 7. 4 (H 1 CY 02) (Alpha only) • Windows 2000 • Support VMS V 7. 3 • Enhanced Windows 2000 Interoperability including Active Directory • Alias file names support • Opportunistic Locking support • Extended Character Set • Single Sign. On 2 • NT Print Mgmt sup’t • Support VMS V 7. 4 (Spool. SS) • DNS Load Balancing PATHWORKS 6. 1 (OVMS 6. 2 -7. 3) (Q 4 CY 00) • DNS Name Resolution • Member Server Support • DNS Load Balancing • Alias File Name PATHWORKS 32 V 7. 2 (Q 2 CY 00) • Windows 2000 • Language Variants (released concurrently) • Euro Currency Continued Support for Microsoft Service Pack releases for Win 95, 98, NT 4. 0 and Win 2000 67
Contacts and web sites Key Contacts § Product Manager: – Mark. Hutnick@Compaq. com § Engineering Project Manager: – Brad. Mc. Cusker@Compaq. com Web Sites http: //www. Open. VMS. Compaq. com/PATHWORKS/ http: //www. Open. VMS. Compaq. com/Advanced. Server/ 68
Advanced Server for Open. VMS and PATHWORKS Thank you for attending Brad. Mc. Cusker@Compaq. com 69
Скачать презентацию Advanced Server for Open VMS PATHWORKS Brad
88b4c2f51829c029ee3dd40aff80cfbe.ppt