ITEM: X0495L
Xstations: How to configure without Xstation manager
Scenario: The customer is trying to configure an Xstation
without xstation manager on a RISC system. I walked
the customer through the following information:
11d. Non-AIX Boot Host, No Bootp, Gateway, XDM, NFS & TFTP File Servers
Step 1. Add Xstation's ipaddress and name to /etc/hosts.
Example:
129.35.147.173 xstation1
129.35.147.93 boothost1
129.35.147.100 gateway1
129.35.147.101 xdmhost1
Step 2. Verify the following on the boot host:
* Appropriate network is up.
* tftpd running(font paths & /etc/x_st_mgr are accessible
if in secure tftp mode.)
* nfsd is running(/etc/x_st_mgr,/usr/lib/X11 in /etc/exports)
* xdm is running on appropriate host
* Any manual editing to /etc/bootptab file is correct
* Default fonts in place:
/usr/lib/X11/fonts/misc
/usr/lib/X11/fonts/75dpi
/usr/lib/X11/fonts/100dpi
All fonts.alias have following first line:
FILE_NAMES_ALIASES
* Any manual editing to Ipaddress File is correct.
(See ip.template in /etc/x_st_mgr/xs140/cfg)
Step 3. Make sure the Xstation is at factory defaults.
Go to Main Menu of Local Configuration
(Do this by pressing ESC at the initial boot screen)
Select "Restore Defaults" and then "Save Changes".
Modify Local Configuration
Advance Configuration
Network Parameters
Change Bootp to Disable
Add Terminal Internet Address
Add Host Internet Address
Add Gateway Internet Address
Add Subnet Mask
Change XDMCP to Direct
Add XDMCP Host Internet Address
File Servers
Change Primary to NFS
Add Host Internet Address
Change path if necessary
Change Secondary to TFTP
Add Host Internet Address
Change path if necessary
Save Changes and Reboot
Since this did not work we looked to make sure that the
daemons were working:
lssrc -t tftp
lssrc -g nfs
In this case tftp was not working. The solution was to
enter into /etc/inetd.conf and then uncomment the line
for tftp. After uncommenting the line for tftpd we
tried to refresh inetd. The refresh gave us a timeout
error. Thinking that there was a problem with the interface
I went through the steps of removing the deivce from the
odm:
ifconfig en0 down
ifconfig en0 detach
rmdev -l en0 -d
rmdev -l et0 -d
rmdev -l ent0 -d
We then tried to add the device with cfgmgr this failed with
the following error:
0514-052
/etc/methods/cfgbus : bus resources could be resolved for a device ent0
After some time we were able to get the device working again.
For those steps please see the end of this item in the Notes
section.
By creating a similar set up in our labs I was able to make
the 150 boot and be usable to someone by following the previously
mentioned steps. What I had to do in addition is to download
from aix.boulder.ibm.com the 150's 12a microcode on to the boot
host, untar this file, create a directory in /etc called x_st_mgr,
and untar the file. From this point on it was necessary to
reexport the /etc/x_st_mgr filesystem to everyone and then on the
Xstation 150 force it to reload its server code on the next reboot
(Note: This is accomplished in the Advanced Configuration->Network
parameters->Automatic Update of FLASH->On next reboot). I found
it necessary to configure xdm (simply follow the steps in
/usr/lib/X11/xdm/README) but I also added an entry in
/usr/lib/X11/xdm/Xservers which looks like the following:
\:0 foreign
You should then run the xdmconf file found in /usr/lib/X11/xdm,
start xdm (startsrc -s xdm), and now reboot the Xstation. Now
the 150 should reboot, reload the FLASH with the new code,
and--possibly with some delay--start up an xdm login window.
Also here is the reasoning for getting the new server code:
The newer code will ignore problems with fonts. If the customer
does not have all of the fonts installed that he needs then
the Xstation will still boot with the newer server code.
Notes:
Scenario: Trying to configure a card, getting errors.
Action: Check ODM:
\# odmget CuVPD | grep [ent0, en0, et0] : nothing
\# odmget CuDvDr | grep [ent0, en0, et0] : nothing
\# odmget CuDep | grep [ent0, en0, et0] : name=et0
\# odmdelete -q name=et0 -o CuDep
\# odmget CuDv | grep [ent0, en0, et0] : name=et0
\# odmdelete -q name=et0 -o CuDv
\# odmget CuAt | grep [ent0, en0, et0] : nothing
\# ls -l e* : no en*, et*, or ent*
\# cfgmgr : gives method error
0514-052
/etc/methods/cfgbus : bus resources could be resolved for a device ent0
\# odmget PdAt | grep ethernet :
uniquetype = "adapter/mca/ethernet"
...
\# odmget -q uniquetype=adapter/mca/ethernet PdAt > /tmp/filename
\# /etc/methods/cfgbus -l bus0 -d
Careful analysis of the BUS.out file indicates that sa1 is using
dma_lvl of 1, which is what ent0 is trying to use. Even more
careful observation of a test system indicates that adapters
of uniquetype adapter/sio/ient_6 are only defined to use dma_lvl
1, whereas the adapter/sio/s1a can use 1-14, with a default of
1.
Tested some things, and this should work:
Remove any definitions for devices with sa* as the parents, and
sa0 and sa1, then run "mkdev -l ent0", then "cfgmgr".
Use "odmget -q parent=sa0 CuDv | grep name" to see the devices
using sa0 as the parent, etc.
Support Line: Xstations: How to configure without Xstation manager ITEM: X0495L
Dated: August 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:33
Comments or suggestions?
Contact us