Compaq Enterprise Technical Symposium 2001 PATHWORKS and Advanced Server Technical Update Brad McCusker Compaq Computer Corporation Brad McCusker Compaq

Compaq Enterprise Technical Symposium 2001

PATHWORKS and Advanced ServerTechnical Update

PATHWORKS and Advanced ServerTechnical Update

Brad McCusker

Compaq Computer Corporation

Brad McCusker

Compaq Computer Corporation


2

Agenda Agenda Agenda Agenda

Current and future product overview Tech overview of new features Future directions Wrap-up


3


Current and future product overview Tech overview of new features Future directions Wrap-up


4

Current OpenVMS File & Print Servers Current OpenVMS File & Print Servers Current OpenVMS File & Print Servers Current OpenVMS File & Print Servers

Advanced Server for OpenVMS V7– Current Release - V7.3 (Apr 01)

PATHWORKS V6 for OpenVMS (Advanced Server)– Current Release - V6.0D (Apr 01)

V6.0D is exactly the same as V6.0C-ECO2

PATHWORKS V5 for OpenVMS (LAN Manager)– Current Release - V5.0F-ECO2 (Feb99)


5

V7.2A-ECO4 – Important!V7.2A-ECO4 – Important!V7.2A-ECO4 – Important!V7.2A-ECO4 – Important!

V7.2A-ECO4 breaks Com for OpenVMS– Com for OpenVMS applications will not work with ECO4

NTA$LOGON doesn’t work Possible server crash when running Com

Patch available from Customer Support Center– PWRK$LMSRV ident: V7.2-140A-00001 or -00002– Patch is only necessary if you run Com for OpenVMS

Or, upgrade to Advanced Server V7.3


6

Advanced Server for OpenVMSAdvanced Server for OpenVMSV7.3 – Our newest releaseV7.3 – Our newest releaseAdvanced Server for OpenVMSAdvanced Server for OpenVMSV7.3 – Our newest releaseV7.3 – Our newest release

Advanced Server V7.3 (Alpha Only)– Release: April 2001

Also ships with OpenVMS V7.3 Q2-2001 Software Product Library

– OpenVMS V7.3 support (V7.2-1, V7.2-2 also)

– Member server role

– Extended character set

– Alias file names

– NT print management (SpoolSS) support

– DNS load balancing capabilities

– PCSI support


7

Advanced Server for OpenVMSAdvanced Server for OpenVMSFuture ReleasesFuture ReleasesAdvanced Server for OpenVMSAdvanced Server for OpenVMSFuture ReleasesFuture Releases

Advanced Server V7.3-ECO1– Estimated availability: Late Sep 01

In final qualification now.

– Numerous bug fixes (20+)

– Customers should install this ECO when they can


8

Advanced Server for OpenVMSAdvanced Server for OpenVMSFuture ReleasesFuture ReleasesAdvanced Server for OpenVMSAdvanced Server for OpenVMSFuture ReleasesFuture Releases

Advanced Server V7.3A– Internal code name: “Shelby”

– Estimated release: H12002

– More Windows 2000 Interoperability

– Performance improvements

– Opportunistic locking support More on these later


9

Advanced Server for OpenVMSAdvanced Server for OpenVMSFuture Releases (2)Future Releases (2)Advanced Server for OpenVMSAdvanced Server for OpenVMSFuture Releases (2)Future Releases (2)

Internal code name: “Cobra” Follow on release to V7.3A Active Directory Support (EAK) Kerberos Support for OpenVMS V6.2/V7.* VAX and Alpha Scalability

– Multiple PWRK$LMSRV processes Robustness Support OpenVMS Security Enhancements


10

Advanced Server for OpenVMSAdvanced Server for OpenVMSFuture Releases (2)Future Releases (2)Advanced Server for OpenVMSAdvanced Server for OpenVMSFuture Releases (2)Future Releases (2)

Advanced Server V7.4– Active Directory

– Unicode


11

PATHWORKS for OpenVMS PATHWORKS for OpenVMS Future ReleasesFuture ReleasesPATHWORKS for OpenVMS PATHWORKS for OpenVMS Future ReleasesFuture Releases

PATHWORKS V6.1 for OpenVMS– Q3-2001

– Member Server

– Alias file names PATHWORKS V5 for OpenVMS

– Maintenance updates only


12

What about Itanium™ Processor Family?What about Itanium™ Processor Family?What about Itanium™ Processor Family?What about Itanium™ Processor Family?

Advanced Server will be ported as soon as required OpenVMS infrastructure is in place

– When OpenVMS is ready, we’ll be ready!

– Current estimate for AS port: H2CY03 Advanced Server porting effort is minimal – Less

than 5% of code modules affected Cluster configuration support in line with

OpenVMS cluster support


13

What about PATHWORKS and Itanium™ What about PATHWORKS and Itanium™ Processor Family?Processor Family?What about PATHWORKS and Itanium™ What about PATHWORKS and Itanium™ Processor Family?Processor Family?

No plans to port PATHWORKS to Itanium ™ Processor Family

Will need to upgrade to Advanced Server to get Itanium™ Processor Family support

– Plan to modify Advanced Server to support platforms that PATHWORKS supports OpenVMS VAX and Alpha V6.2, V7.2, V7.3….

PATHWORKS to Advanced Server migration is a simple Install/Config/Run…


14

PATHWORKS 32 Client SW UpdatePATHWORKS 32 Client SW UpdatePATHWORKS 32 Client SW UpdatePATHWORKS 32 Client SW Update

PATHWORKS 32 V7.2– Available June, 2000

– Supports Windows 2000, Windows NT 4.0, Windows 95, Windows 98

– http://www.OpenVMS.Compaq.com/pathworks32/

Contact Information – Product Manager:– [email protected]

http://www.openvms.compaq.com/pathworks32/


15


Current and future product overviewTechnical details of new features Future directions Wrap-up


16

New Features Technical DiscussionNew Features Technical DiscussionNew Features Technical DiscussionNew Features Technical Discussion

DNS name resolution NT print management (SpoolSS) Member server Licensing Potpourri


17

DNS SupportDNS SupportDNS SupportDNS Support

DNS name resolution by clients supported as of PW V6.0C and AS V7.3

Client DNS name resolution required for dynamic cluster load balancing

– See Advanced Server Administrators Guide for more information on dynamic balancing


18

Tech Tips: NETBIOS Name ResolutionTech Tips: NETBIOS Name ResolutionTech Tips: NETBIOS Name ResolutionTech Tips: NETBIOS Name Resolution

If Enabling Dynamic Alias Resolution…– Remove static entries for cluster alias!– NETBIOS names are resolved with LMHOSTS or

WINS before DNS Added ability for Advanced Server to use DNS for

name resolution– Enabled via PWRK$CONFIG/Transports– V6.1, V7.3– DNS used as last resort

After LMHOSTS, broadcast, WINS


19

NT Print Management Support (V7.3)NT Print Management Support (V7.3)NT Print Management Support (V7.3)NT Print Management Support (V7.3)

New optional functionality in V7.3 NT style management of printer resources

– Specifically, added the SPOOLSS pipe Use NT Print Manager to manage OpenVMS

printer resources– ADMIN CLI will have minimal print management

support Allows print drivers to be stored on Advanced

Server for downloading to the client


20

Upgrading Existing PrintersUpgrading Existing PrintersUpgrading Existing PrintersUpgrading 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


21

Adding New PrintersAdding New PrintersAdding New PrintersAdding New Printers

“Add Printer” in Printers Folder on AS system Select Port will show available Execution Queues

on OpenVMS Specify Printer Name Provide Printer Driver

– From CD-ROM, or other location

– Stored on Advanced Server for downloading to clients


22

What about generic queues?What about generic queues?What about generic queues?What about generic queues?

OpenVMS 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


23

Printer Pooling Printer Pooling Printer Pooling 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!!!


24

Printer Pooling (2)Printer Pooling (2)Printer Pooling (2)Printer Pooling (2)

Select Printer Pooling Select all the execution

queues that will be used by this Printer

Continue with the Wizard


25

RestrictionsRestrictionsRestrictionsRestrictions

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


26

CAUTION!CAUTION!CAUTION!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 Improvements, to be delivered in a future release:

– TBD


27

Member Server Role (V7.3, V6.1)Member Server Role (V7.3, V6.1)Member Server Role (V7.3, V6.1)Member Server Role (V7.3, V6.1)

Adding support for the member server role– Previously, PW/AS servers only supported 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


28

Member Server Local vs Global SAM Member Server Local vs Global SAM DatabasesDatabasesMember Server Local vs Global SAM Member Server Local vs Global SAM DatabasesDatabases Member Servers have a SAM!!!

– But, its not the domain SAM, it is a local SAM– Known only to that member server

Local SAM:– Represented by user or group name

Administrator, Administrators

– Local groups only, global groups have no meaning Global SAM:

– Represented by user or group name, but, qualified with domain name \\DOMAIN1\Domain Admins

Reference KB article: Q126436


29

More local vs global SAMMore local vs global SAMMore local vs global SAMMore local vs global SAM

Access to resources: Local SAM checked first– Be careful of same names in Local and Global

SAMs Recommend not using Local SAM database

– Or, be sure you know why you are using Local SAM and why.


30

ADMIN and Local/Global SAMsADMIN and Local/Global SAMsADMIN and Local/Global SAMsADMIN and Local/Global SAMs

ADMIN defaults to managing the Global SAM To manage a local SAM:

– Use \\ServerName instead of a domain name.

– For Example:LOGIN/DOMAIN=\\memberserverSET ADMINISTRATION/DOMAIN=\\memberserverCOMMAND/DOMAIN=\\memberserver

ADMIN prompt becomes \\memserv\\memserv>– When logged in or Set ADMIN to local database


31

Member Server and ADMINMember Server and ADMINMember Server and ADMINMember Server and ADMIN

Not Allowed on Member Servers:SET COMPUTER/ACCOUNT_SYNCHRONIZESET COMPUTER/ROLE=xxxSHOW COMPUTER (except to specific comp)ADD COMPUTERREMOVE COMPUTERADD|SHOW GROUP/GLOBALSHOW GROUPS/GLOBALADD|COPY|MODIFY USER/PRIMARY_GROUP=xxxADD|REMOVE|SHOW TRUST


32

Member Server and ADMIN (2) Member Server and ADMIN (2) Member Server and ADMIN (2) Member Server and ADMIN (2)

ADMIN behavior on LOCAL SAM ADD/COPY/MODIFY/REMOVE/SHOW GROUP commands will only

manage local groups. – Global Groups may exist but, they are ignored on Member

Servers ADD USER adds to the "Users" local group.

– Also added to Domain Users global group but not seen by users

SHOW USER will only show memberships in local groups.– Won't show primary group

ADD/COPY/MODIFY USER will only manage memberships in local groups.

– Primary group is not supported.


33

Member Server and ADMIN (3)Member Server and ADMIN (3)Member Server and ADMIN (3)Member Server and ADMIN (3)

DEBUG SET /FLAGS=BYPASS_MEMSRVCHKS– Bypasses Member Server specific checks on

USER and GROUP commands

– Allows you to really see what’s in the Local database

Not familiar with ADMIN DEBUG? – $ ADMIN DEBUG HELP


34

Member Server Tech Tip #1 (V7.3 only)Member Server Tech Tip #1 (V7.3 only)Member Server Tech Tip #1 (V7.3 only)Member Server Tech Tip #1 (V7.3 only)

Recommend joining a domain by specifying username/password of administrator account

– Alternative is to add server to domain prior to running config

– Some sites may not have access to administrator account

If you don’t join domain via specifing username/password, only local accounts can manage the local server

Not a problem in V6.1


35

Member Server Tech Tip #2Member Server Tech Tip #2Member Server Tech Tip #2Member Server Tech Tip #2

Problem: – Same username in global domain and local member

server user database

– Attempt to connect to member server resources from global account

– Member Server attempts to validate access against local account – Access fails

Solution:– If local accounts match global accounts, user “Connect As”

and specify domain with user name: \\domain\user


36

Member Server Tech Tip #3Member Server Tech Tip #3Member Server Tech Tip #3Member Server Tech Tip #3

Explicit Hostmaps are lost on role change to/from member server

When changing roles, the hostmap database (LSA) is recreated.

– Previously existing hostmaps lost Recommend using ADMIN SHO HOSTMAP before role

change and ADMIN ADD HOSTMAP after role change to restore.

– Do not attempt to use old LSA database

– Old LSA has old ServerObject – Not good for new config


37

Member Server Role: Upgrading from Member Server Role: Upgrading from PATHWORKS V5PATHWORKS V5Member Server Role: Upgrading from Member Server Role: Upgrading from PATHWORKS V5PATHWORKS V5

Issue:– How do I upgrade from V5 to V6 Member

Server?

– V5 to V6 Upgrade Utility only allows upgrade to Backup Domain controller

Solution: – Upgrade to Backup Domain Controller, and then

use PWRK$CONFIG to change role to Member Server


38

All client access to PW V6 & AS V7 must be licensed All client access requires a “Client-Access” license

– PWLMXXXCA06.00 - PW-V6.0

– PWLMXXXCA07.02 - AS-V7.2

– PWLMXXXCA07.03 - AS-V7.3, PW-V6.1 May be used as a client-based or server-based license

– Per seat (replaces FPA)

– Per server (replaces FPS)

License policyLicense policyLicense policyLicense policy


39

V73/V6.1 Potpourri:V73/V6.1 Potpourri:V73/V6.1 Potpourri:V73/V6.1 Potpourri:

Registry Incompatibilities MOD USER /PWDEXP SAM corruption Dir Cache Pulse Message/Inactive Daemon SHO USERS has new fields Disable License Ping RestrictAnonymous Manual Synchronization


40

Tech Tip: OpenVMS Registry Tech Tip: OpenVMS Registry IncompatibilitiesIncompatibilitiesTech Tip: OpenVMS Registry Tech Tip: OpenVMS Registry IncompatibilitiesIncompatibilities

OpenVMS V7.3 & OpenVMS V7.2-1 registries incompatible– Must upgrade OpenVMS 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 OpenVMS simultaneously– Registries on OpenVMS V7.2-1/OpenVMS V7.3 will not work

together in a cluster OpenVMS V7.2-2 is compatible with OpenVMS V7.3

– Problem doesn’t exist with OpenVMS V7.2-2/V7.3


41

MOD USER /PWDEXP (V7.2A – ECO3/4)MOD USER /PWDEXP (V7.2A – ECO3/4)MOD USER /PWDEXP (V7.2A – ECO3/4)MOD USER /PWDEXP (V7.2A – ECO3/4)

$ ADMIN MODIFY USER user-name/PASSWO="passwd"

$ ADMIN MODIFY USER user-name/PASSWO="passwd"/FLAGS=PWDEXP

These commands do not expire the password– Workaround: Issue separate expire command

$ ADMIN MODIFY USER user-name /PASSWO="passwd"

$ ADMIN MODIFY USER user-name /FLAGS=PWDEXP

Fixed in V7.3– Was never a problem in V6


42

SAM CorruptionSAM CorruptionSAM CorruptionSAM Corruption

V7.3, V7.2A-ECO4, V6.0C-ECO2 fix SAM corruption

No need for modified PWRK$SHUTDOWN– The “interlock shutdown with NetLogon” fix

– Only use PWRK$SHUTDOWN provided with kit Uncontrolled shutdowns can cause corruption Report reproducible SAM corruption to Customer

Support Center


43

Directory CacheDirectory CacheDirectory CacheDirectory Cache

Clients sees empty or partial directories Fixed in V7.3, V7.2A-ECO4, V6.0C-ECO2 Make sure XQP patches are current

– Should always do this If you still see this – update to latest ECO, notify

Customer Support


44

SAM Replication Pulse Message - SAM Replication Pulse Message - Inactive DaemonInactive DaemonSAM Replication Pulse Message - SAM Replication Pulse Message - Inactive DaemonInactive Daemon Problem: PW/AS cluster is BDC, PDC needed to

resolve alias to “active” daemon node of cluster– If alias resolved to “inactive” daemon node,

replication pulse messages would go to wrong node.

– Partial synchs of SAM didn’t occur– WAN only (LAN uses broadcasts)

Resolution: If “inactive” daemon gets a pulse, it passes it on to the “active daemon”

– Active Daemon will respond to Pulse Message– In V6.0C-ECO2, V6.1, V7.3


45

SHOW USER – new fieldsSHOW USER – new fieldsSHOW USER – new fieldsSHOW USER – new fields

ADMIN SHOW USER /FULL, /ACCOUNTS or /PROFILE now includes: – Last Log On: 08/23/00 05:07 PM

– Password Last Set: 06/30/00 11:03 AM

– Password Changeable: 06/30/00 11:03 AM

– Password Expires: 09/11/00 11:03 AM In V7.3, V6.1


46

Disable Client License PingDisable Client License PingDisable Client License PingDisable Client License Ping

If using only server based licensing, define PWRK$LR_DISABLE_CLIENT_PING, to bypass client license check on client request

– When clients connect, PW/AS first attempts to validate a license on the client

– If not using any client based licenses, you might as well skip that step.

See Advanced Server for OpenVMS Guide to Configuring Licenses for more information

V7.3 & V6.1


47

Licensing Block DiagramLicensing Block DiagramLicensing Block DiagramLicensing Block Diagram

DEFINE/SYSTEM PWRK$LR_DISABLE_CLIENT_PING 1 to eliminate steps 3 & 4

– In PWRK$LICENSE_R_START.COM

File Server

LicenseRegistrar

Client Map Share Client Map Share RequestRequest

11

22 55Client Client PingPing

33

Client Client Response?Response?

44


48

Domains with RestrictAnonymous setDomains with RestrictAnonymous setDomains with RestrictAnonymous setDomains with RestrictAnonymous set

PW/AS cannot join a domain if the PDC has RestrictAnonymous set

Check this registry location:Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA

Value Name: RestrictAnonymous

Data Type: REG_DWORD

Value: 1

Workaround: Set value to 0 while joining domain– Can be reset to non-zero value immediately after

joining the domain.


49

More RestrictAnonymous IssuesMore RestrictAnonymous IssuesMore RestrictAnonymous IssuesMore RestrictAnonymous Issues Secure Channels can not be created to Win2K servers

with RestrictAnonymous=2– Trusts, External authentication, are affected

ADMIN LOGON, ADMIN SET PASSWORD do work. Per MS KB articles value of 2 is for pure Win2K configs

only – no down level clients or servers KB articles:

– http://support.microsoft.com/support/kb/articles/q246/2/61.asp

– http://support.microsoft.com/support/kb/articles/Q178/6/40.asp

http://support.microsoft.com/support/kb/articles/q246/2/61.asp

http://support.microsoft.com/support/kb/articles/q246/2/61.asp

http://support.microsoft.com/support/kb/articles/Q178/6/40.asp

http://support.microsoft.com/support/kb/articles/Q178/6/40.asp


50

Manual Synchronization FailuresManual Synchronization FailuresManual Synchronization FailuresManual Synchronization Failures

From Server Manager/Synchronize with PDC, always choose the cluster Alias, not individual nodes.

Since SP5, choosing a node results in machine account secret passwords out of synch

– Can no longer establish secure channel Recovery: Select the cluster alias and then

“Synch With Primary Domain Controller”


51


Current and future product overview Technical details of new featuresFuture Directions Wrap-up


52

Future Directions for Advanced ServerFuture Directions for Advanced ServerFuture Directions for Advanced ServerFuture Directions for Advanced Server

1. Integrate with Windows 2000• Client and domain compatibility

• Active directory

2. Provide enterprise level File and Print Services for 1000s of users• Reliable, Available, Scalable

• Performance


53

Performance EnhancementsPerformance EnhancementsPerformance EnhancementsPerformance Enhancements1. Improve performance monitoring and analysis tools

– PWMON updated, improved– PerfLib updated and enhanced– Client Monitor tool no longer supported

2. General Performance Enhancements Faster directory cache (V7.3, V6.1) Memory management (V7.3) Faster data-cache (V7.next) Reduce VMS Locking (V7.3A) Opportunistic Locking (V7.3A)

3. Major Enhancements Multi-process server Galaxy based improvements


54

Performance EnhancementsPerformance EnhancementsReduce Open VMS lockingReduce Open VMS lockingPerformance EnhancementsPerformance EnhancementsReduce Open VMS lockingReduce Open VMS locking

1. Reviewed a few lock mechanisms Share lock used a parent/child mechanism, will be

simple locking

2. Threadlocks instead of VMS Locks Threadlocks are 12 times faster Use threadlocks for non-shared resources When a resource becomes shared, promote to

VMS lock


55

Performance ImprovementsPerformance ImprovementsExamplesExamplesPerformance ImprovementsPerformance ImprovementsExamplesExamples

Focus on reducing BUFIO– Improve FID and directory cache hit rates– Improve file lookup algorithms

Directory cache is now write through Fix cross-cluster invalidation of the directory

cache– Improved local node too!

Increase FID cache capacity from 8K to 16K files– Increases hit rate


56

File Lookup descriptionFile Lookup descriptionFile Lookup descriptionFile Lookup description

File Lookup: Any attempt to access a file header– Optimized thru the FID cache

Lookups can be by name or by FID (File ID) The flow is as follows:

– First try to ‘hit’ the fid cache– If alias (short) name, convert to FID, try to hit again. – Do a wildcard lookup against the XQP to get the FID.– Do a XQP lookup to get the file header contents, and

store the results in the FID cache.


57

File Lookup optimizations in V7.3AFile Lookup optimizations in V7.3AFile Lookup optimizations in V7.3AFile Lookup optimizations in V7.3A

If we have a filename but not a FID, lookup in the directory cache to get the FID. – Very likely to succeed, unless its a short name.

Alias short name processing improved. Fixed several problems which could result in

unnecessary ‘misses’ in the FID cache Results: 20-25% higher hit-rates in the FID cache,

much less Buffered I/O’s against the XQP


58

Performance ImprovementsPerformance ImprovementsObservationsObservations11


Directory Enumeration of 5000-file directory– FID cache sized for 8K files

– Elapse time went from 52 seconds to 13 seconds

– I/Os went from 21,000 to 300 (100% hit rate on caches)

UNZIPing large .ZIP file (2500 files)– Elapse time went from 70 minutes to 6 minutes

11 Laboratory observations, actual results will varyLaboratory observations, actual results will vary


59



Cross-cluster activity– Create/delete files in same directory from multiple

cluster nodes

– Before – 50% hit rate single node, 13% cross cluster

– After – 87% hit rate single node, 80% cross cluster



60

Opportunistic Locking (OpLocks)Opportunistic Locking (OpLocks)Opportunistic Locking (OpLocks)Opportunistic Locking (OpLocks)

3 types of Locks– Exclusive (Level 1)

Client opens file for exclusive access, free to do arbitrary buffering and caching on the client, free to write

Server breaks the OpLock when another client requests access Can break to Level II or None

– Level II Multiple readers, no writers Client doesn’t request level II, server converts Exclusive or

Batch to level II Must be broken to none to write.


61

Opportunistic Locking (OpLocks)Opportunistic Locking (OpLocks)Opportunistic Locking (OpLocks)Opportunistic Locking (OpLocks)

3 types of locks (continued) – Batch

Client keeps file open on the server, even though its closed from the client application perspective

– Typical of batch file processing: Open file, read a line, close file, process line, etc until done

Similar to Exclusive, server will break to Level II or none


62

Exclusive OpLock – Block DiagramExclusive OpLock – Block DiagramExclusive OpLock – Block DiagramExclusive OpLock – Block Diagram

Client AClient AServerServer

Client BClient BOpen foo.bar

11

Open foo.bar 33

Grant Ex Oplock 22

Break Oplock Request 44

Locks and writes

Locks and writes responses

55

Break Oplock Request Response

66Open

response77


63

OpLock DeliverablesOpLock DeliverablesOpLock DeliverablesOpLock Deliverables

Advanced Server V7.3A will provide Exclusive and Batch OpLocks

Level II comes later– No requirement to support Level II

– When breaking OpLocks, break to Level II or none


64

Performance Improvements ObservationsPerformance Improvements Observations11

LabTest (SQE95)LabTest (SQE95)

Performance Improvements ObservationsPerformance Improvements Observations11

LabTest (SQE95)LabTest (SQE95)

0

10

20

30

40

50

60

70

80

90

V7.3 Shelby

Elapse time (min)

Buffered I/O (*1000)

FIDcache hitrate%



65

High Availability High Availability High Availability High Availability

Availability/Stability– Always the top priority

– SAM replication issues resolved

– Directory cache problems resolved Reliability (NonStop) is the goal

Minimize reboots (V7.3) Rolling upgrades

Scalability – Multi-process Server

See next slide


66

ScalabilityScalabilityScalabilityScalability In development….

EXTSMB> pwshow

OpenVMS V7.2-1 on node EXTSMB 20-MAR-2001 14:23:22.75 Uptime 18 00:13:23

Pid Process Name State Pri I/O CPU Page flts Pages

2020073A NETBIOS HIB 5 78 0 00:00:00.05 71 41

2020074B PWRK$ADMIN_0 LEF 6 51 0 00:00:00.11 126 89

2020073F PWRK$KNBDAEMON HIB 11 137 0 00:00:00.43 240 289

20200742 PWRK$LICENSE_R HIB 11 160 0 00:00:00.53 453 199

20200747 PWRK$LMMCP HIB 11 1229 0 00:00:00.55 457 300

202004CD PWRK$LMSRV_0 HIB 11 999 0 00:00:03.34 1263 424

202004CF PWRK$LMSRV_1 HIB 11 1680 0 00:00:02.41 1143 201

20200745 PWRK$MASTER HIB 6 242 0 00:00:00.35 358 67

2020073D PWRK$NBDAEMON HIB 11 33 0 00:00:00.10 110 130


67

RobustnessRobustnessRobustnessRobustness

Multiple server processes Automatic server restarts on failure Improved error handling, tracing and reporting Pro-Active and Active configuration tools Eliminating single points of failure


Windows 2000Windows 2000


69

Win2K & PATHWORKS V5 Win2K & PATHWORKS V5 Win2K & PATHWORKS V5 Win2K & PATHWORKS V5

PATHWORKS V5 - Best Effort only– No plans for official support

Clients– Win2K, Win2K-SP1: Customers tell us they work

Patches required– Win2K-SP2: Problems reported, fix in test

Servers/Domains– PW V5 is an LM 2.2 Server– Expect restrictions for W2K and LM 2.2 Servers


70

Win2K and Prior ReleasesWin2K and Prior ReleasesWin2K and Prior ReleasesWin2K and Prior Releases

Advanced Server V7.2A & PATHWORKS V6.0C/D Officially, not in the SPD Clients

– Patches required– Intend to support W2K client– Engineering accepts escalations

Servers/Domains– PW & AS have same restrictions as NT 4.0– Must be BDC to Win2K PDC


71

Windows 2000 Integration PlansWindows 2000 Integration PlansWindows 2000 Integration PlansWindows 2000 Integration Plans

Current: – Advanced Server V7.3 and PATHWORKS V6.1

– Window2000 Native Mode: PW/AS is member server

– Windows2000 Mixed Mode: PW/AS is member server or BDC

Future - Advanced Server V7.4– Active Directory Integration

Make OpenVMS resources available in AD

– Unicode


72

Windows 2000 Mixed Mode DomainWindows 2000 Mixed Mode DomainWindows 2000 Mixed Mode DomainWindows 2000 Mixed Mode Domain

Advanced Server for

OpenVMS V7.3Backup Domain

Controller

Windows 2000Server

Mixed ModePrimary Domain

Controller

NT 4.0 Backup Domain

Controller

Account Replication Account

Replication

Advanced Servers & NT 4 servers participate in theW2K Mixed Mode Domain as a Backup Domain Controller

ActiveDirectory

for Domain

AD Updates & Access

DOMAINDOMAIN


73

AuthenticationRequests

Windows 2000 Native Mode DomainWindows 2000 Native Mode DomainWindows 2000 Native Mode DomainWindows 2000 Native Mode Domain

Advanced Server for

OpenVMS V7.3Member Server

Windows 2000Server

Domain Controller

NT 4.0 Member Server Advanced Server provides resources in a W2K Multi-Mastered

Domain as a Member Server and relies upon W2K for authentication

ActiveDirectory

for Domain

AD Updates & Access

DOMAINDOMAIN

Windows 2000Server

Domain Controller


74

Advanced Server for

OpenVMS V7.4 Enhanced

Member Server

Windows 2000Server

Domain Controller

Advanced Server participates in the W2K Multi-Mastered Domain by interacting with the Active Directory

ActiveDirectory

for Domain

AD Updates & Access

DOMAINDOMAIN

Windows 2000Server

Domain Controller

AD Updates & Access

Authentication Requests

Future: Active Directory IntegrationFuture: Active Directory IntegrationFuture: Active Directory IntegrationFuture: Active Directory Integration


75


Current and future product overview Technical details of new features Future directionsWrap-up


76

Advanced Server 7.3 (Alpha Only) (Q2CY01)•Support VMS V7.3•Member server•Win2K Interoperability•Alias file names •Extended Char Sets •NT Print Mgmt sup’t•DNS Load Balancing •DNS Name Resolution•PCSI Installation

V7.3a (H102) (Alpha only)•Opportunistic Locking support•Performance Enhancements•Support VMS V7.3, V7.2-2, •Support VMS 7.3-1 (latent)

PATHWORKS 6.1 (OVMS 6.2-7.3) (H201)•Member Server Support•DNS Load Balancing/Name Resolution•Windows 2000 Interoperability•Alias File Name

Enterprise File and PrintEnterprise File and PrintEnterprise File and PrintEnterprise File and Print2001 2002 20042003

PATHWORKS 6.0D (Q2CY01)•OVMS V7.3 Support

Cobra (CY04)•VAX support•Enhanced Windows 2000 Interoperability including Active Directory•Kerberos supt•Scalability•Robustness

PATHWORKS•Support OVMS releases as needed

PATHWORKS 32 - Continued Support for Microsoft Service Pack releases for Win95, 98, NT4.0 and Win 2000

DCPS V2.0 (Q2 CY’01)


77

Contacts and web sitesContacts and web sitesContacts and web sitesContacts and web sitesKey Contacts Product Manager:

– [email protected] Engineering Project Manager:

– [email protected]

Web Sites http://www.OpenVMS.Compaq.com/PATHWORKS/

http://www.OpenVMS.Compaq.com/AdvancedServer/


78

QQ&&AThank you for attendingThank you for attending

Documents

Compaq Enterprise Technical Symposium 2001 PATHWORKS and Advanced Server Technical Update Brad McCusker Compaq Computer Corporation Brad McCusker Compaq