Experience with Availability Manager V2.6

[Karl Rohwedder]

Options 1 would fit here too...

regards Kalle

[Ian Miller.]

The corporate network is sufficently complex that it can not be entirely trusted, therefore encryption and authentication is a must. ssh is fine.

[Jeffrey Goodwin]

Barry,

A bit of clarification please: Option 1) would still provide the authentication using the password provided by the current triplets implementation, correct?

-Jeff

[Barry Kierstein]

Some clarifications:

The security triplet system will still be in effect between the Data Analyzer and the Data Collector, regardless of where the packet comes from (direct on the LAN or through the Data Server).

The Data Analyzer will be able to connect to multiple Data Servers at the same time. The System Overview screen is reorganized a bit to show as level 1 the WAN/LAN connection, then the OpenVMS, Group and node level.

The Data Server will be able to support multiple Data Analyzer connections.

A filter level on the Data Server that has IP addresses or masks, and/or MAC addresses could be done. Is this an effective method of security?

[Jeffrey Goodwin]

Barry,

>>A filter level on the Data Server that has IP addresses or masks, and/or MAC addresses could be done. Is this an effective method of security?

The Triplet based security would be enough to use the WAN version in my environment. Even if I was external to our WAN, we would still use VPN to connect.

I can forsee using the above features in the future. MAC addresses would have to included as IP addresses change so frequently.

-Jeff

[Ian Miller.]

The hp Availability Manager Team is working on supporting the use of Availability Manager over a WAN and would like some feedback.

Using Availability Manager over a WAN is a long requested feature - take this oppourtunity to let hp know what you want.

Visit http://www.openvms.org and fill in the survey.

This survey will be available from Sept 15th to Sept 29th, 2006.

[Bart Zorn_1]

I have now upgraded the DS15 in the datacenter from OpenVMS V7.3-2 to V8.2.

Apparently, AM needed to be reinstalled because the RMDRIVER that comes with V8.2 is older than the one that comes with AM. The good news is that reinstalling AM does not overwrite customizations to the access data files or the AMDS$LOGICALS.COM file. AMDS always did that, despite the fact that I reported that to engineering somewhere in 1999!

For one reason or another, AM displays now in an other font than before the upgrade. Before the font used was something like Arial (san serif) and now it uses something like Times (serif). I strongly prefer the former but I cannot find where that might be changed.

Regards,

Bart

[Bart Zorn_1]

I already found out what cased the change of fonts (but not why!).

I have JAVA V1.5-1 installed on a non-system disk and at the time that I started AM after the OpenVMS upgrade, that disk was not yet available. AM then used its own version of JAVA, being V1.4-2. JAVA V1.5 apparently uses different fonts than V1.4.

Regards,

Bart

[Bart Zorn_1]

It is now two weeks since I upgraded OpenVMS to V8.2 on my "Availability Manager System". It ran reasonable until today. All of a sudden it now takes minutes to open or even close a window.

What can this be? Is it time to reboot the system (Oh, I forgot, its is not Weendooze we are talking about.)

Bart