Hi Todd,
Also thank you for downloading the NAS-R3 Enterprise Demo-CD for Testing and Evaluation for your environment, as this is important to make decisions before investing.
Of course, i had a phone call from your support team (27, April 2007) and i am already waiting for a new NAS-R3 Ent. dongle to solve the problems i have with XSR, that's why i am here .
Anyway, i still can't connect, but i think i've found where the problem is.
Configuration :
Master - Debian : (UPS monitoring OK)
Nut 2.0.4 (Network Ups Tools upsd)
Connected to the MGE PULSAR 2200 RT ups with a serial cable
Slave 1 - Windows : (UPS monitoring OK)
Username : nas
Password : nasuser
UPS name : PULSAR2200
Slave 2 - NAS-R3 : (UPS monitoring NOK)
Username : nas
Password : nasuser
UPS name : The UI do not allow me to specifiy this essential information
Diagnostic :
As you can see, i can't specify in the configuration page of NAS-R3, what is the name of the UPC to connect to. This parameter is essential because my Master could be connected to several UPS's and it is used to distinguished the UPS's.
So by default, NAS-R3 connects arbitrarily to an UPS named : "ups".
I know that because i used "Wireshark" (Ethereal) tool to sniff the network from the master computer, and i can see in the TCP packets the following commands :
USERNAME nas
PASSWORD nasuser
LOGIN ups
LOGOUT
So to be sure, i've changed the name of my UPS from "PULSAR2200" to "ups", to allow NAS-R3 to connect to the master, and be sure NAS-R3 understand my UPS.
Finally, when the name of my UPS is "ups" on my master, i see NAS-R3 slave in the captured TCP frames connecting successfully to the master.
But, when i have a look at the UPS status page, (STATUS>Hardware) i still see "Status: Not available".
To help you debug, i've found in the captured TCP frames that, to retrieve the NAS status, NAS-R3 sends the command :
GET VAR ups ups.status
And i see my master answering :
VAR ups ups.status "OL CHRG"
Answer which means that the UPS i on-line even if charging the batteries, but this answer seems no to be understood by NAS-R3.
Conclusion :
I see 2 problems here, the first one is in the UI :
- In slave mode, we must have the possibility to specify the UPS name to connect to
- In slave mode, the "UPS model, "Port" and "Timeout" parameters are useless
The second one is in the UPS status interpretation :
- Even if NAS-R3 connects to an UPS slave successfully, the status page do not display informations
I stopped my testing here waiting for your clues.
Please, tell me if you have the same results on your side... and if so if it can be corrected.
Maybe you should tell me which NUT package version the NAS-R3 ups tool was validated with.
PS : I will send this diagnostic by mail to the support as you suggested.
Thanks.
---
Mathieu