Atalla Boxcar Reference Guide Abstract This document describes Boxcar, its interface to the Atalla Network Security Processor (NSP), and the parameters used to start, initialize, and configure the Boxcar process. Boxcar supports all Atalla NSP models that have an Ethernet TCP/IP interface. This release is available through the HP NonStop eServices portal.
Document History Part Number Product Version Published 526564-001 T0409D45-AAD August 2003 526564-002 T0409D45-AAE October 2004 526564-003 T0409D45-AAF April 2006 526564-004 T0409D45-AAI October 2007 New and Changed Information • A new parameter has been added, see BOXCAR-LOGMSGWRITEINTERVAL.
Boxcar Overview Boxcar is a process that runs in a HP Non-Stop server. It is designed to improve the overall efficiency of communication between host application process(es) and Atalla NSPs that support Ethernet TCP/IP communications. Boxcar acts as a funnel for transactions, accepting commands from a large number of application processes and sending them to available sockets on the Atalla NSP. Boxcar provides an interface to one Atalla NSP.
During operation, Boxcar status and error messages are written to the Boxcar log. By default, messages are written using a waited write operation. Certain messages can be written using a no-waited write operation, see BOXCAR-LOGMSGWRITEINTERVAL. Error responses generated by the Network Security Processor in response to invalid commands, are not logged by Boxcar, they are returned to the host application process.
Example log file The following is an example of a Boxcar log file after a successful startup: \CHIP.$BOXB: 30APR2009 14:51:15 BOXCAR VERSION 2.7 STARTED \CHIP.$BOXB: 30APR2009 14:51:15 Open $0 log Successfully \CHIP.$BOXB: 30APR2009 14:51:15 BOXCAR-LOGMSGWRITEINTERVAL = 30 \CHIP.$BOXB: 30APR2009 14:51:15 BOXCAR-LOGFILE = BOXLOG \CHIP.$BOXB: 30APR2009 14:51:15 BOXCAR-BACKUPCPU = 1 \CHIP.$BOXB: 30APR2009 14:51:15 BOXCAR-DEVICE-NAME = 16.107.203.103 \CHIP.
AKB Version: 3.60C, Date: Feb 19 2009, Time: 15:43:34#80F4#0#> \CHIP.$BOXB: 30APR2009 14:51:15 SEND : <9A#KEY#> \CHIP.$BOXB: 30APR2009 14:51:15 RECV : \CHIP.$BOXB: 30APR2009 14:51:15 BOXCAR DEVICE HAS BEEN INITIALIZED \CHIP.$BOXB: 30APR2009 14:51:15 Boxcar established 14 of 14 sockets on 16.107.203.103 on port 7000 \CHIP.$BOXB: 30APR2009 14:51:16 BOXCAR Backup Process Created OK \CHIP.$BOXB: 30APR2009 14:51:16 BOXCAR Backup Process Initialized.
Command Processing After Boxcar is started, initialized, and configured, it performs a READUPDATEX on $RECEIVE, then begins processing host application commands, sending and receiving commands and responses through the sockets, and replying to the host applications. Each time Boxcar receives an NSP command it updates a counter. When the counter is equal to 2000 times the value of BOXCAR-SOCKET-RESET-LEVEL, Boxcar attempts to restore any invalid sockets, and logs the number of sockets restored.
Boxcar Parameter Definitions The following is a description of the Boxcar parameters, listed in alphabetical order. BOXCAR-BACKUPCPU Specifies the CPU number which runs the Boxcar backup process. This parameter is optional, if not specified, Boxcar does not run as a persistent process pair. BOXCAR-CRLF-REQUIRED This parameter is required, if not specified, Boxcar logs an error, and terminates.
1. The command, in format: System name. Boxcar process name: Date Time, Socket Identifier, Command. 2. The response from the NSP, in format: System name. Boxcar process name: Date Time, Socket Identifier, Response. BOXCAR-DEVICE-NAME Specifies the IP address of the Atalla NSP. This parameter is required, if not specified, Boxcar logs an error, and terminates. Do not use leading zero(s) in an IP address octet. For example 192.168.001.014 is incorrect, use 192.168.1.14 instead.
• • • • When Boxcar receives a “Queued Message Cancellation” message it uses the value specified in LOGMSGWRITEINTERVAL to start a timer. While the timer is running, Boxcar counts the number of these messages it receives. When the timer expires, Boxcar uses a no-waited write operation, with depth of one, to record in its log file the number of queued message cancellation messages it has received during this interval.
To determine an appropriate value for the MAX-FLATSEG-SIZE parameter multiply the number of requestors by 32,000. For example if the BOXCAR-RECV-DEPTH is set to 255 the MAX-FLATSEG-SIZE parameter should be set to 8160000 or higher. If this parameter is set to a value that is too small Boxcar will abend at startup. BOXCAR-MAXSOCKET-OPENS Specifies the maximum number of sockets that Boxcar can open on a NSP. This parameter is optional, if not specified the default value 14 is used.
Table 1. Boxcar Parameters (page 1 of 2) Command Default Description BOXCAR-BACKUPCPU Sets the number of the CPU that runs the Boxcar backup process. If not specified, the Boxcar process does not run as a persistent process pair. BOXCAR-CRLF-REQUIRED Used to specify if a Carriage Return and Line Feed (CRLF) characters should be appended to each NSP response. YES = append CRLF NO = do not append CRLF If not specified, Boxcar logs an error and terminates.
Table 1. Boxcar Parameters (page 2 of 2) Command Default Description BOXCAR-SOCKET-RESET-LEVEL 500 Specifies the frequency which Boxcar will check for, and attempt to restore, invalid sockets. The value specified, which is multiplied by 2000, is the number of commands received by Boxcar before it will attempt to restore any invalid sockets. Setting this value to a low value will increase overhead and degrade Boxcar performance.
Modifying the Obey File Edit the obey file to match your host system (for example, primary and backup CPUs, device IP address, and number of sockets). Create a separate obey file for each NSP; one Boxcar process for each NSP, see Boxcar Parameter Definitions. Table 2 shows an example of an obey file. Note. To prevent application time-outs the priority of the Boxcar process should be set slightly below the priority of the TCP/IP process that controls the NSP.
Executing the Obey File Once the obey file is modified, execute the obey file. In the example below the modified obey file is called STRTBOX. At the TACL prompt, type the following including the space: TACL> obey strtbox Note. If you renamed the obey file, be sure to type the name of your new obey file.
24-hour Support Atalla Technical Support provides 24-hour emergency coverage through the Global Mission Critical Solution Center (GMCSC). Use this service for Atalla product and system emergencies that occur after normal working hours or on weekends and U.S. holidays. Questions about Atalla product installation and setup are supported during normal working hours. Within the U.S. the GMCSC can be contacted by calling: 800-826-3367 Customers outside the U.S.
