From: Alexandre B. <ale...@bu...> - 2002-05-14 09:20:25
|
Hello, I having problems configuring EMP. I work with VACM 2.0.5a. I have two IPMI 1.5 enabled servers, they are Bull Express 5800/120lf. To configure EMP, I have to boot on the ESM Pro 5.06 CD because the 120lf's bios doesn't contain an EMP category. The server category only allows to redirect or not Console Display. Once the BMC is configured to work with the serial Line (19.2 kbps, CRTSCTS flow control), and the LAN (ip address to set) with a numerical password set too, I verified that everything is working well by taking control of one servers from a third computer, Windows 2000 based. On that Windows based machine, it's Nec MWA I used to take control of one of the 120lf servers. All of that told me that the servers are well configured, especially the serial cross-cable is working. So I tried to configure VACM on one of the 120lf server to take control of the other, by serial and/or by LAN. It's a RedHat 7.2 installed on that controller computer. I managed to compile and installed it without problems By serial, I connected ttyS0 on the controller machine and ttyS1 and the controlled machine. I started "nexxus -l" on the controller machine. Under vash, I renamed the default user blum into another. I added the controlled machine in a nodes-group I defined. I tried to set EMP by typing: vash$ ipc localhost emp:configuration:server1:/dev/ttyS0:1234 I get everytime. EMP:72:JOB_STARTED EMP:72:STATUS:ENGAGING <with a little wait state of 5 seconds approximatively here> EMP:72:STATUS:PROTOCOL_UNAVAILABLE EMP:72:JOB_COMPLETED vash$ nexxus said : EMP] Thread server1 protocol unavailable (Connection timed out) By LAN I typed : vash$ ipc localhost emp:configuration:server1:10.0.0.1-623:1234 and get every time: EMP:73:JOB_STARTED EMP:73:STATUS:ENGAGING EMP:73:STATUS:ENGAGE_FAILED EMP:73:JOB_ERROR:Connection refused vash$ nexxus said : [17:04:15][EMP] Thread server1 engage failed (Connection refused) and a lot of the following message [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) [17:04:16][EMP] Driver for node server1 reports unexpected serial traffic (bad cabling or hw error?) ... which make my /var/log/vacm.log growing too much I have to delete it. I'm almost sure it is the 623 port to access because, when I "tcpdumped" on the controlled server when I take control of it from the Windows 2000's MWA software, I see communication o this port, between the two machines. Could someone tell me what I missed to have VACM EMP module working ? Thanks to all. Alexandre BERDAH |