Troubleshooting
12-37
12
•
Check the Events window of the SunGMI. If no event messages are listed,
verify that the client can establish a TCP/IP connection to the SunGMAN
system. Enter the command
ping
machinename
, where machinename is the
system running the SunGMAN software.
•
Verify that LUs are available for use in the PUBLIC pool. Display the status
of the LU pools using the SunGMI.
•
If the client connection is using a Domain Name System (DNS) resource
name, such as
xxx.Sun
, try to connect to the system directly to see if the
DNS name resolution is failing.
•
If the SunGMAN process is operating as a secondary DNS, verify that the
primary DNS is configured to know about the Sun subdomain and that
the primary DNS has an NS record that points to the machine running
SunGMAN.
•
If you are using SunGMAN as a primary DNS, verify that the client
system's
/etc/resolv.conf
file has an entry for a nameserver that lists
the address of the machine running the SunGMAN process.
•
For Solaris, verify that the client system is using DNS for hostname
lookups. The
/etc/nsswitch.conf
file lists the lookup methods for
network services.
•
Check user records to ensure that they are configured to block access from
the client system.
12.4 Service Name Parameters
To allow a TP to write directly to a window, prefix
xterm -e
to the TP Path
Executing this command directly from SunGMI fails.
If a TP cannot Open LocalLU, you may have a problem with shared libraries.
Check your library path variable and make sure it matches:
setenv LD_LIBRARY_PATH /opt/SUNWlu62:${PATH}
If not, restart SunGMAN/PU2.1 with
LD_LIBRARY_PATH
set correctly.
A TP will, by default, go to SunOp Service sunadmin_pu2/LU6.2 Service
sunlu62_serv. These Services are defined in GMI
→
PU 2.1 Servers
→
PU
2.1_server
→
Modify
→
Service Name Parameters.
The first PU2.1_server has these default Service Name Parameters. A second
PU.21_server will have parameters
--a
. The TP willneed to specify (by some
sort of call) that it is accessing non-default Service Name Parameters if it wants
to connect to a LocalLU on the 2nd, 3rd, etc., PU2.1_server.
Содержание SunLink SNA 9.1 PU2.1
Страница 14: ...xiv SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 16: ...xvi SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 18: ...xviii SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 26: ...xxvi SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997...
Страница 48: ...1 22 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 1...
Страница 66: ...2 18 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 2...
Страница 80: ...3 14 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 3...
Страница 110: ...6 12 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 6...
Страница 120: ...7 10 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 7...
Страница 132: ...8 12 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 8...
Страница 226: ...A 10 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 A...
Страница 282: ...F 16 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 F...
Страница 288: ...G 6 SunLink SNA 9 1 PU2 1 Server Configuration Guide August 1997 G...