Bug 126676 - WTI NPS STONITH driver doesn't function properly when certain switch parameters are altered
Summary: WTI NPS STONITH driver doesn't function properly when certain switch paramete...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Cluster Suite
Classification: Retired
Component: clumanager
Version: 3
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Lon Hohberger
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-24 16:44 UTC by Lon Hohberger
Modified: 2009-04-16 20:15 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-06-24 16:46:18 UTC
Embargoed:


Attachments (Terms of Use)

Description Lon Hohberger 2004-06-24 16:44:21 UTC
Description of problem:

If you turn on automated mode and telnet to a TPS/IPS/NPS switch, it
drops you to a prompt immediately; the same happens if you turn off
"Confirmation".  That is, no "status screen" is displayed upon login.

The STONITH driver times out waiting for the header from the statu
screen describing which product it is connected to (e.g. "Network
Power Switch", "Telnet Power Switch", etc.).  After it times out, it
returns S_BADCONFIG.

How to get it working:

Log in to the power switch and enter the "General Settings" menu with
the "/G" command.

(1) Ensure that "Automated Mode" is "Off".
(2) Ensure that "Confirmation Confirmation" is "On".

Comment 1 Lon Hohberger 2004-06-24 16:46:18 UTC
This behavior is not worth fixing, as it can be solved by altering the
switch's configuration.

Comment 2 Lon Hohberger 2004-06-24 16:51:24 UTC
As an additional note for this bugzilla:

The "Boot Delay" for each plug should be left at the 5 second default.

Cross-reference:

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=108393

Comment 3 Lon Hohberger 2004-06-24 16:59:31 UTC
When configuring the WTI power switch, it's important to note that the
"port" field in redhat-config-cluster is the port name on the *power
switch*, not the TCP port number.

That is, the port name should be "1", "2"... "8", or the corresponding
symbolic name, not the TCP port number which telnet uses.  The STONITH
driver already knows that it needs to connect to port 23.


Note You need to log in before you can comment on or make changes to this bug.