Managing Initialization Parameters
By default, all available dump protocols and parameter file protocols are enabled, and all
available software load image protocols are enabled except DTFTP, as shown in Figure 4-
1. Table 4-3 lists the protocols which are available for each process.
Table 4-3. Default Protocols
Software Load Image
Parameter File
Dump file
CARD
XMOP
MOP
BOOTP
RARP
DTFTP*
CARD
XMOP
MOP
BOOTP
RARP
XMOP
MOP
BOOTP
RARP
*Not enabled by default.
The processor module attempts to load software and parameters using the CARD protocol
first, because this is the default. If a card is not present, it searches for the load image and
parameters using protocols in the order they appear on the screen: XMOP, MOP, BOOTP,
RARP, and DTFTP, if it is enabled. When a processor module attempts to send
information to a dump server, it first attempts to use XMOP, then MOP, BOOTP, and
RARP.
The syntax of the command that enables or disables software load image protocols and
operational parameter protocols is the following:
DEFINE CHASSIS SLOT [list] LOAD [record|ALL] usage PROTOCOL protocol | ALL
[ENABLED | DISABLED]
The [record ] variable specifies the primary, secondary, or tertiary initialization record.
The usage variable specifies either the software load image or the operational parameters
with one of these sets of keywords: IMAGE [LOAD] or PARAMETERS [LOAD]. You
cannot disable all protocols in an initialization record. The following is an example of a
command that disables XMOP as a software load image protocol in the primary
initialization record for the terminal server in slot 2:
Xyplex>> define chassis slot 2 load primary image protocol
xmop disabled
The syntax of the command that enables or disables dump protocols is the following:
DEFINE CHASSIS SLOT [list ] DUMP [record] PROTOCOL protocol | ALL [ENABLED |
DISABLED]
The [record ] variable specifies the primary, secondary, or tertiary initialization record.
0020
55