 |
» |
|
|
 |
Adding or Moving Hardware After Installation |  |
When the ACC and X.25/ACC products are installed on the system,
there are files that are customized or created based on the current
location of the ACC multiplexer cards. In the case that any ACC
mux cards are added to the system or moved within the system, these
files may need to be changed: Create the appropriate device files, /dev/zx25mXpY for 2/8-Channel card,
or /dev/zx25mXpYsZfor T1/E1
4-Channel card. The device files that are used by the X.25/ACC product and
that correspond to the hardware that is currently installed on the
system can be created by running: % /opt/acc/lbin/make_n2z_devs |
A device file is created for each port (and sub-channel, if
Z7300A or Z7330A) of each mux that is currently installed on the
system. The X represents the mux number (i.e. 0, 1, 2, etc.). The
Y represents the mux port (i.e. 0 through 7). (The Z represents
the sub-channel number if Z7300A). Refer to Appendix C “Utilities, Servers, and Scripts” for
more information on creating these files. Create a new loopback ttgen
configuration file. This can be used as a template for creating
or modifying the actual ttgen files
that will be used. To create the sample loopback configuration
file: % /opt/acc/lbin/acc_bld_lpbk -o x25_loop.answ \ -t sample_header -p x25 |
To run ttgen on this
configuration file: % /opt/acc/bin/ttgen -o x25_loop.answ x25_loop.tmem ttgen: END$ 0 Disasters, 0 Errors, 0 Warnings % |
Repeat step 2 to create a sample x25_loop configuration
file, substituting the filename x25_loop.[answ | tmem] where
appropriate.
Using other X.25/9000 cards and ACC cards together |  |
The X.25/ACC product running on an ACC card may not be used
in the same system as other interface cards supported by the X.25/9000
product at this time. Installing Other Products |  |
The scripts which configure the ACC and X.25/ACC products
during the swinstall process
modify these files: These files may be updated when patches or other products
are installed on the system, including those that are not related
to the ACC product. If this occurs, this may cause the mk_kernel of the system to fail,
typically due to unsatisfied symbols or /etc/services not
containing the proper entry for znode. If this appears to be the case, the configuration procedure
can be re-run as follows: % swconfig -x reconfigure=true ACC.ACC-RUN % swconfig -x reconfigure=true ACC-X25ST.ACC-X25ST-KRN
|
After performing this procedure use mk_kernel to
rebuild the kernel, move the new kernel image file into place (/stand/vmunix)
and then reboot your system.
|