david.k.harris at siemens
Oct 10, 2006, 3:52 PM
Post #1 of 1
(877 views)
Permalink
|
|
RE: conserver.cf question (portbase, port...)
|
|
Hi William,
The one difference I see from my standard configs, is that I call out
the "portbase" and "portinc" variables for each brand of
[terminal|console]
server, as in the following example...
default cyclades { type host; portbase 2000; portinc 1; }
This way, my "port" variable for each device represents the hardware
port number, so it's a bit more intuitive which port to which you are
connecting each console...
console daphne { include ts21 ; port 12 ; }
While this seems pretty self-evident for most console servers, there
are a few cases where the port increment is x100, versus x1, and there
are a few devices where the starting port base is 'unusual', depending
on which slot you use for the NM-xA or HWIC-xA modules. That's
where this method really shines, helping to document where you
plugged in the cables. :-)
Perhaps having just the port called, without a defined portbase or
portinc variable is the cause? Seems like an interesting symptom. :-)
-Z-
________________________________
From: users-bounces [at] conserver [mailto:users-bounces [at] conserver]
On Behalf Of William P LePera
Sent: Tuesday, October 10, 2006 3:30 PM
To: users [at] conserver
Subject: conserver.cf question
We are running conserver version 8.1.7, using the UDS socket feature for
client/server communications. We recently modified our conserver
configuration files to call our terminal server directly using the "type
host" syntax.
An example configuration entry looks like this:
default csm {
logfile /var/log/consoles/&;
timestamp 1da;
rw *;
master c104hc01.clusters.com;
}
console f1x345n01.clusters.com {
include csm;
type host;
host 192.168.1.25;
port 2900;
}
Whenever we open a console to this server, the console opens in
read-only mode, even if we don't specify -s:
[root [at] c104hc0 conserver]# /opt/conserver/bin/console
f1x345n01.clusters.com
[Enter `^Ec?' for help]
[read-only -- initializing]
hitting some keystrokes here results in:
[read-only -- use ^E c ? for help]
[read-only -- use ^E c ? for help]
[read-only -- use ^E c ? for help]
[read-only -- use ^E c ? for help]
We can use the Ctrl E-c-f sequence to get into read/write mode:
[attached]
Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.9-5.ELsmp on an i686
f1x345n01.clusters.com login:
If we change the configuration file back to this:
default csm {
logfile /var/log/consoles/&;
timestamp 1da;
rw *;
master c104hc01.clusters.com;
}
console f1x345n01.clusters.com {
include csm;
type exec;
exec "/usr/kerberos/bin/telnet 192.168.1.25 2900";
}
everything works:
[root [at] c104hc0 conserver]# /opt/conserver/bin/console
f1x345n01.clusters.com
[Enter `^Ec?' for help]
Trying 192.168.1.25...
Connected to c104v1mrv01.clusters.com (192.168.1.25).
Escape character is '^]'.
Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.9-5.ELsmp on an i686
f1x345n01.clusters.com login:
Is there anything else that needs to be added to the config file to get
the console opened in read/write mode? I would have thought the "rw *"
in the default block would be enough.
Thanks,
___________________________________________________________________
Bill LePera
IBM Systems and Technology Group
Poughkeepsie, NY
|
