70
U41270-J-Z916-2-76
Operating the LAN Console
PRIMESTATION as LAN Console
©
S
iem
en
s
N
ix
d
or
f I
n
fo
rm
at
ions
s
y
s
tem
e
A
G
1
997
P
fa
d
: H:
\onl
in
e_p
ro
duc
in
g
\02_
1
1
_
06_
E
rdm
u
tHu
ebn
er
Hat
z
el
\4
1
270
e2
\4
127
0e
1.
k
0
5
The connections to the required RM and PRIMEPOWER (MR) servers can then
be established from the “new” LAN Console.
5.6.2
Switching because of problems
In this scenario, console accesses to the RM and PRIMEPOWER (MR) servers
have to take place from another LAN Console because of problems with the
current LAN Console.
If it was impossible to terminate console accesses from the original LAN
Console properly, these connections may still be open on the RCA side. The
section “Disrupted RCA - LAN Console connection” on page 73 provides infor-
mation on resetting such connections.
5.7
Diagnostics
This section provides information on the diagnostic options in the LAN Console
product. It describes logging properties of the
rtty
monitor and the internal
impact of creating configuration entries. It goes on to describe diagnostic
options and error situations involving the RCA.
5.7.1
Log files
When the LAN Console is configured, the
rtty
monitors
lanconsole
and
lanconsole1
are activated internally in the system depending on the underlying
RCA type RCA3 or RCA4 (see
mklancon
command “mklancon - Create LAN
Console configuration entries” on page 45).
These
rtty
monitors are started and stopped via
sac
(Service Access Control).
This stores status information in the
/var/saf/_log
log file. The
rtty
monitors are
identified in this log file by
port monitor lanconsole
or
port monitor lanconsole1
.
rtty-
specific details, i.e. information on the
rtty
connections between the LAN
Console and the RCA, are stored in the
/var/saf/lanconsole/log
or
/var/saf/lanconsole1/log
log file.
The degree of detail of this information depends on the current
rtty
trace level
set.