Availability Manager v3.0.2 Data Server issue

Alain Senécal — Fri, 28 May 2010 14:29:36 GMT

I installed Data Server on a Windows 2003 Server. I then configured and exported the Trust Keys as described in the User's Guide.

The I started the Data Analyzer on the same server using the Data Server on the locahost on port 9819. Connection is established but no data shows up in the Data Analyzer.

If I start the Data Analyzer using the NIC connected in the OpenVMS LAN then the data shows up.

Is there something wrong in my setup?

Thanks.

Re: Availability Manager v3.0.2 Data Server issue

P Muralidhar Kini — Fri, 28 May 2010 14:56:29 GMT

Hi Alain,

>> Is there something wrong in my setup?
Looks like a configuration related issue.

Check the following link -
http://h71000.www7.hp.com/openvms/products/availman/6552pro.html#getting_started
This talks about how to setup and configure the Data Analyzer/Data Server.
You can refer this link and check if all the configuration steps were followed or not.

Regards,
Murali

Re: Availability Manager v3.0.2 Data Server issue

Alain Senécal — Fri, 28 May 2010 16:43:45 GMT

Yes, I used that guide to configure the Data Server/Analyzer on my Wndows Server. Everything wnet fine. The Data Analyzer can connect to the Data Server but no data shows up.

Here is the log of the Data Server startup:
-----------------------------------------
Fri, May 28th 13:17:49.702 Platform attributes, OS name and version = Windows 2003 5.2
Fri, May 28th 13:17:49.702 ** Log file opened for output **
Fri, May 28th 13:17:49.702
Fri, May 28th 13:17:49.702 HP Availability Manager Server V3.0-2 (build 1194)
Fri, May 28th 13:17:49.702 Â© 2009, Hewlett-Packard Development Company, L.P.
Fri, May 28th 13:17:49.702
Fri, May 28th 13:17:49.717 List of Data Server options:
Fri, May 28th 13:17:49.717 Arg[0] = 9819
Fri, May 28th 13:17:49.717 Processing Data Server options:
Fri, May 28th 13:17:49.717 Ignoring unrecognized option "9819"
Fri, May 28th 13:17:49.717 Network adapters found on this system
Fri, May 28th 13:17:49.717 \DEVICE\{1BC72945-4D5D-44A3-83F5-BB22CBD8BB81} - HP Network Team #1
Fri, May 28th 13:17:49.733 \DEVICE\{973738E3-7314-42D0-8E2F-9868454C4269} - HP NC3123 Fast Ethernet NIC
Fri, May 28th 13:17:49.733 [9819] Server mode is secure.
Fri, May 28th 13:17:50.139 [9819] Server listening on port 9819 for HP Network Team #1
Fri, May 28th 13:17:50.139 [9819] LanPacketPool - initial pool size is 100 packets.
Fri, May 28th 13:17:50.155 [9819] PacketWriterThread abbreviations
Fri, May 28th 13:17:50.155 [9819] PW - packets written to LAN network
Fri, May 28th 13:17:50.155 [9819] PD - packets dropped due to full queue
Fri, May 28th 13:17:50.155 [9819] QP - packet queue capacity
Fri, May 28th 13:17:50.170 [9819] QS - packets queued
Fri, May 28th 13:17:50.170 [9819] DN - minimum packet queue delay (ms) for reporting interval
Fri, May 28th 13:17:50.170 [9819] DX - maximum packet queue delay (ms) for reporting interval
Fri, May 28th 13:17:50.170 [9819] DA - average packet queue delay (ms) for reporting interval
Fri, May 28th 13:17:50.170 [9819] PacketReaderThread abbreviations
Fri, May 28th 13:17:50.170 [9819] PR - packets read from LAN network
Fri, May 28th 13:17:50.170 [9819] SP - short packets, packets too short to be valid AMDS packets
Fri, May 28th 13:17:50.170 [9819] LP - long packets, packets too long for network protocol
Fri, May 28th 13:17:50.170 [9819] HP - Multicast Hello packets
Fri, May 28th 13:17:50.170 [9819] CP - packets going to a console (Data Analyzer)
Fri, May 28th 13:17:50.170 [9819] UM - Data Server JVM used memory (TM-FM)
Fri, May 28th 13:17:50.170 [9819] FM - Data Server JVM free memory
Fri, May 28th 13:17:50.170 [9819] TM - Data Server JVM total memory
Fri, May 28th 13:17:50.170 [9819] MM - Data Server JVM maximum memory
Fri, May 28th 13:17:50.170 Port 9819 connected to \DEVICE\{1BC72945-4D5D-44A3-83F5-BB22CBD8BB81}
Fri, May 28th 13:18:22.577 [9819] Accepting analyzer as client 0 from ssqpo0161.ssq.local:2309 [10.11.6.68:2309]
Fri, May 28th 13:18:22.812 [9819] Peer = 10.11.6.68:2309
Fri, May 28th 13:18:22.812 [9819] Protocol = TLSv1
Fri, May 28th 13:18:22.812 [9819] Cipher Suite = TLS_DHE_DSS_WITH_AES_128_CBC_SHA
Fri, May 28th 13:18:22.812 [9819] Local Principal = CN=ssq139,OU=Exploitation,O=SSQ,L=Quebec,ST=QC,C=CA
Fri, May 28th 13:18:22.812 [9819] Peer Principal not verified.
Fri, May 28th 13:18:22.812 [9819] ClientThread Data Server stat abbreviations
Fri, May 28th 13:18:22.812 [9819] PW - packets written to client from LAN
Fri, May 28th 13:18:22.812 [9819] PD - packets dropped due to full queue
Fri, May 28th 13:18:22.812 [9819] QM - client packet queue capacity (server to client)
Fri, May 28th 13:18:22.812 [9819] QS - client packets queued
Fri, May 28th 13:18:22.812 [9819] KC - current packet pool capacity
Fri, May 28th 13:18:22.812 [9819] KS - packets in packet pool
Fri, May 28th 13:18:22.812 [9819] KU - packet pool underflows
Fri, May 28th 13:18:22.812 [9819] KO - packet pool overflows
Fri, May 28th 13:18:22.827 [9819] KM - packets created in pool (made)
Fri, May 28th 13:18:22.827 [9819] KR - packets rejected by pool due to overcapacity
Fri, May 28th 13:18:22.827 [9819] HW - Hellos written to client
Fri, May 28th 13:18:22.827 [9819] HD - Hellos dropped due to full queue
Fri, May 28th 13:18:22.827 [9819] HT - Hellos tossed due to relieve network congestion
Fri, May 28th 13:18:22.827 [9819] DN - minimum packet queue delay (ms) for reporting interval
Fri, May 28th 13:18:22.827 [9819] DX - maximum packet queue delay (ms) for reporting interval
Fri, May 28th 13:18:22.827 [9819] DA - average packet queue delay (ms) for reporting interval
Fri, May 28th 13:18:22.983 [9819] ClientReadThread[0]: Server protocol version is V2.0
Fri, May 28th 13:18:22.983 [9819] ClientReadThread[0]: Client protocol version is V2.0
Fri, May 28th 13:18:22.983 [9819] ClientReadThread abbreviations
Fri, May 28th 13:18:22.983 [9819] PW - packets written from client to server
Fri, May 28th 13:18:22.999 [9819] PD - packets dropped due to full queue
Fri, May 28th 13:18:22.999 [9819] QS - server packets queued (client to server)
Fri, May 28th 13:18:22.999 [9819] QO - server packets
Fri, May 28th 13:18:22.999 [9819] KC - current packet pool capacity
Fri, May 28th 13:18:22.999 [9819] KS - packets in packet pool
Fri, May 28th 13:18:22.999 [9819] KU - packet pool underflows
Fri, May 28th 13:18:22.999 [9819] KO - packet pool overflows
Fri, May 28th 13:18:22.999 [9819] KM - packets created in pool (made)
Fri, May 28th 13:18:22.999 [9819] KR - packets rejected by pool due to overcapacity
Fri, May 28th 13:18:22.999 [9819] DN - minimum packet queue delay (ms) for reporting interval
Fri, May 28th 13:18:22.999 [9819] DX - maximum packet queue delay (ms) for reporting interval
Fri, May 28th 13:18:22.999 [9819] DA - average packet queue delay (ms) for reporting interval
Fri, May 28th 13:18:22.999 [9819] UM - Data Server JVM used memory (TM-FM)
Fri, May 28th 13:18:22.999 [9819] FM - Data Server JVM free memory
Fri, May 28th 13:18:22.999 [9819] TM - Data Server JVM total memory
Fri, May 28th 13:18:22.999 [9819] MM - Data Server JVM maximum memory
Fri, May 28th 13:18:22.999 [9819] ClientThread[0] running..
Fri, May 28th 13:18:22.999 [9819] ClientReadThread[0] running..
Fri, May 28th 13:18:22.999 [9819] ClientThread[0] Analyzer protocol version V2.0
Fri, May 28th 13:18:22.999 [9819] ClientThread[0] Analyzer protocol settings mask 0x0
Fri, May 28th 13:18:22.999 [9819] ClientThread[0] Analyzer capability mask 0x1
Fri, May 28th 13:18:22.999 [9819] ClientThread[0] Analyzer message data version V1.1
Fri, May 28th 13:18:22.999 [9819] ClientThread[0] Analyzer message data versions are compatible
Fri, May 28th 13:18:23.015 [9819] Server statistics:
Fri, May 28th 13:18:23.015 [9819] Active Connections = 1
Fri, May 28th 13:18:23.015 [9819] Successful Connections = 1
Fri, May 28th 13:18:23.015 [9819] Compatibility Failures = 0
Fri, May 28th 13:18:23.015 [9819] Connection Failures = 0
Fri, May 28th 13:18:23.015 [9819] Security Failures = 0
Fri, May 28th 13:18:23.015 [9819] Startup Failures = 0
Fri, May 28th 13:18:23.015 [9819] ClientReadThread[0] Analyzer is running Availability Manager V3.0-2 (build 1194)
Fri, May 28th 13:18:23.015 [9819] ClientReadThread[0] Analyzer is running on Windows XP 5.1
Fri, May 28th 13:18:23.015 [9819] ClientReadThread[0] Analyzer handshake status - All protocol versions and capabilities are compatible
Fri, May 28th 13:18:23.015 [9819] ClientReadThread[0] DA config - analyzer write packet queue capacity, {message,packet} pool initial and maximum capacity are 50, -1, -1, 20, 200.
--------------------------------

Wether I run the Data Analyzer locally on the Data Server or from a remote host, the behavior is the same.

The only way I can display the data is by selecting the NIC when I run the Data Analyzer on the Data Server.

Notice that there is 2 NICs on the Data Server. Only one NIC is connected the LAN on which the OpenVMS Data Collectors are running.

Re: Availability Manager v3.0.2 Data Server issue

Alain Senécal — Fri, 28 May 2010 19:05:12 GMT

Look at this line in the Data Server log file:

Fri, May 28th 13:17:50.170 Port 9819 connected to \DEVICE\{1BC72945-4D5D-44A3-83F5-BB22CBD8BB81}

The Data Server is connected to the wrong NIC. How can I tell the Data Server to connect to the other NIC?

Thanks.

Re: Availability Manager v3.0.2 Data Server issue

Hoff — Fri, 28 May 2010 21:37:43 GMT

Switch the wires.

Re: Availability Manager v3.0.2 Data Server issue

Ian Miller. — Sat, 29 May 2010 15:02:45 GMT

Does the Data Server use AMDS$DEVICE logical and have you set it in AMDS$LOGICALS.COM

Re: Availability Manager v3.0.2 Data Server issue

Jess Goodman — Sun, 30 May 2010 08:15:37 GMT

Ian,

Alain's Data Server is a Windows box, so VMS logical names are not relevant.

Re: Availability Manager v3.0.2 Data Server issue

Oleg Mikhailov — Mon, 31 May 2010 03:42:41 GMT

Hi all.

May be this help you?

-----------------------
HP Availability Manager - Version 3.0-2

Release Notes

March 2008

...

4.1.2 Changing the Network Adapter the Data Server Uses on
Windows Systems

On Windows systems, the Data Server picks up the first
available network adapter for data communications. If
it selects an undesirable network adapter-for example, a
wireless adapter on a laptop-you can disable this selection
by unchecking "HP Availability Manager NDIS 5.0 Protocol
Driver" in the Network Properties for the network adapter.
------------------------------

wbr Oleg

Re: Availability Manager v3.0.2 Data Server issue

Alain Senécal — Mon, 31 May 2010 12:28:30 GMT

Thank you very much Oleg!

Disabling the "HP Availability Manager NDIS 5.0 Protocol Driver" on the Network Adapter makes it unselectable by the Data Server.

Therefore the Data Server selects the next Network Adapter that has the "HP Availability Manager NDIS 5.0 Protocol Driver" enabled.

Thanks again for your help!

Alain

Re: Availability Manager v3.0.2 Data Server issue

Oleg Mikhailov — Tue, 01 Jun 2010 03:18:13 GMT

Hi Alain.

If my answer was helpful, then:
http://forums11.itrc.hp.com/service/forums/helptips.do?#34

topic Re: Availability Manager v3.0.2 Data Server issue in Operating System - OpenVMS

Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue

Re: Availability Manager v3.0.2 Data Server issue