LayGO applications running in the PXS use standard configuration files to
configure stack and protocol parameters and standard service and device databases.
These configuration file and database images are kept in a
64K page in flash memory labeled
wxedcfg is a Windows program used to create and edit configuration
files. It also provides an option to create a
laygocfg flash image
from a directory containing LayGO .cfg files.
This image can be downloaded to a PXS with the
wxedcfg [cfg file name]
If invoked with a cfg file name wxedcfg will open that file for editing. Otherwise it will start with a new (empty) configuration file.
To include a profile for a protocol in a configuration file, click the corresponding checkbox. The button with the protocol name will be enabled. Press the button to view the contents of a profile or to edit it.
To edit a value in a profile, click on the value field and an editor for the value will be displayed.
See the LayGO Configuration Manual for details on how to configure the LayGO protocol stack.
This menu option is enabled when the System Stack profile is selected. A dialog box like the following is displayed:
The IP addresses typed here will be used to update the "Number of Harware Drivers" (in the case of the PXS this refers to the number of PXSs that will be accessed by this configuration) and the "Hardware n" which in the case of the PXS refers to its IP address. You can configure up to 8 PXS addresses.
Use the laygocfg RedBoot command to download a configuration file set image to the designated area in the PXS. First, obtain a RedBoot prompt using either a Console Connection or a Telnet Connection as explained in the LayGO PXS - Protocol eXchange Server installation manual.
laygocfg1 RedBoot command can be used to list the current configuration files
(this is the default option) or it can be used with the
load option to
load the image from a TFTP2 server as shown in the
Advanced Relay Corporation LayGO PXS - Protocol eXchange Server LayGO PXS Boot Version 3.20 RedBoot(tm) Debug Environment - Built 12:22:13, Sep 14 2004 Portions Copyright (c) 2000, Red Hat, Inc. Portions Copyright (c) 2001, Comtrol Corp. Portions Copyright (c) 2003, Advanced Relay Corp. RedBoot> laygocfg load -h 192.168.168.247 laygocfg.img Defaulting to entry point of 0x00000000. Raw load done: 65536 bytes read Address range: 00000000-00010000, Entry point: 00000000, laygocfg.img loaded. LayGO configuration update complete. RedBoot> laygocfg list Installed LayGO cfg files: aftx25dte.cfg iptunnel-loop.cfg iptunnel.cfg lapbdce.cfg lapbdte.cfg laygocfg.txt pxsdlmtap.cfg iproute.cfg iproutec.cfg iproutet.cfg x21bis.cfg x21dce.cfg x21dte.cfg x25dce.cfg x25dte.cfg xchangec.cfg xchanget.cfg xgateway.cfg xportal-dce.cfg xportal-dte.cfg xportal-src.cfg xportal.xcl
-h <ip address>flag from the command line. In the case of the
laygocfg loadcommand, the default image file name is
laygocfg.img, so you could just issue the command
laygocfg loadto download the
laygocfg.imgfile from the TFTP server and write it to the flash memory on the PXS.