HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem Connecting HP RP3410 2-Way to R3000 XR UPS using Lansafe III

 
SOLVED
Go to solution

Problem Connecting HP RP3410 2-Way to R3000 XR UPS using Lansafe III

We have a major problem with interoperability between the following Kit / Software:

RP3440 2-Way HP-UX 11i Version 1.0 March 2004
R3000 XR UPS
Lansafe III UPS Monitoring Software.

All the kit and software was supplied in the same kit installation.

HP have not been able to advise us that this kit/software combination has been tested for interoperability.

We have raised a hardware call suspecting a serial board fault on the UPS and have subsequently had full confirmation from HP engineering that the UPS is fully functional and the Serial Link cable is the correct one for the UPS.

The RP server uses the 'W' cable similar to the L (RP54xx) and A (RP24xx) series servers. The I/O scan of the GSP ports is shown below:

ba 5 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
ba 6 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (783)
tty 0 0/7/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
tty 1 0/7/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/GSPdiag1 /dev/mux1 /dev/tty1p2
/dev/diag/mux1 /dev/tty1p0 /dev/tty1p4
unknown -1 0/7/2/0 UNCLAIMED UNKNOWN PCI Display (10025159)
memory 0 8 memory CLAIMED MEMORY Memory
ipmi 0 16 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
processor 0 128 processor CLAIMED PROCESSOR Processor
processor 1 129 processor CLAIMED PROCESSOR Processor


The GSP is on 0/7/1/1 and the UPS lead attaches to /dev/tty1p2 (as far as we can work out). Lansafe III is pointing at that device.

When the ls3 daemon is stared we can see using an stty < /dev/tty1p2 that is cycles through baud rates from 19200 down to 1200 to try and establish a connection; it never does and running ls3con fails to link to the UPS.

By manually setting the tty speed to 300 baud we have sometimes managed to get ls3con to link but it is very inconsistent.

The old ups_mond software is disabled and the latest Cumulative Mux and Pty Patch is installed.

Current Theories
1. The UPS connection on the GSP has insufficient pins connected to support the UPS cable.
2. Patch Problem MUX/PTY ?
3. HP Have Not Tested The Kit Together.

Any Help Or Assistance Much Appreciated.

David.
4 REPLIES 4
Cheryl Griffin
Honored Contributor
Solution

Re: Problem Connecting HP RP3410 2-Way to R3000 XR UPS using Lansafe III

It seems you are using the wrong port.
The UPS is normally connected to /dev/tty0p0.

For the rp3410:
/dev/tty0p0 --> UPS port
/dev/tty1p0 --> Console port
/dev/tty1p2 --> Remote port (mdoem port)
/dev/tty1p4 --> Local session port
"Downtime is a Crime."

Re: Problem Connecting HP RP3410 2-Way to R3000 XR UPS using Lansafe III

Cheryl.

Thanks for the reply.

Is this documented anywhere? We cannot find any info in the manual or supplied CD ROM. Can you send us a link or attachment? The supplied documenation is not very accurate.

Without looking at the 'W' cable we are sure its the same part as on the RP24/54xx servers which has 'UPS' marked on the 9-Pin Headshell. Very confusing if it is!

Many Thanks

David.

Cheryl Griffin
Honored Contributor

Re: Problem Connecting HP RP3410 2-Way to R3000 XR UPS using Lansafe III

David,
I don't know why this is not in the user guide for the rp3440. After searching extensively, there is not a document that I can provide that offers more information.

"Downtime is a Crime."

Re: Problem Connecting HP RP3410 2-Way to R3000 XR UPS using Lansafe III

Problem is now solved and has been tested

For the rp3410 'M' Cable:

/dev/tty0p0 --> UPS port
/dev/tty1p0 --> Console port
/dev/tty1p2 --> Remote port (modem port)
/dev/tty1p4 --> Local session port (This does not physically exist external to the server - still not sure what it does yet)

Also note that the two 9-pin serial ports (Serial A - console, and B) cannot be used. They are now designated 'factory use only'

The second 10/100 LAN connection does not exist either.

David.