HP NonStop RDF J-series RVUs Management Manual page 246

Imagetrail (1)
Purger
$DATA06 -> $DATA06 $RUPD1
$DATA07 -> $DATA07 $RUPD2
$DATA08 -> $DATA08 $RUPD3
RDFCOM - T0346H09 – 11AUG08
C)2008 Hewlett-Packard Development Company, L.P.
Status of \RDF04 -> \RDF05 RDF 2008/08/11 05:26:49.082
Control Subvol: $SYSTEM.RDF04
Current State : * TAKEOVER in progress *
RDF Process
------------------ ------ --------- --- ------- ------ ------------- ----- ----
Monitor
Receiver (0)
Receiver (1)
Imagetrail (0)
Imagetrail (1)
Purger
$DATA06 -> $DATA06 $RUPD1 ......... 185 $IMAGE0
$DATA07 -> $DATA07 $RUPD2 ......... 185 $IMAGEA
$DATA08 -> $DATA08 $RUPD3 ......... 185 $IMAGEA
In each of these examples, the first line shows the RDF banner that includes the Product Version
Number and the date of its release (T0346A08 - 11AUG08). The second line contains the standard
Hewlett-Packard banner. The status information about the specific RDF subsystem begins on
the third line, where the names of the primary (\RDF04) and backup (\RDF05) systems are given,
followed by the timestamp when this instance of the STATUS RDF command was issued.
The control subvolume is listed next line, and the following line lists the current state of the RDF
subsystem. In the first example, the state is NORMAL (RDF running with Update On), and the
second example the state indicates that an RDF takeover operation has begun. The following list
represents all possible RDF states. For a discussion of each of these states, see
Operating Statistics and Configuration Information" (page 112)
• Normal
• Normal - Update Stopped
• Start Update Pending
• Stop Update Pending
• Stop Update, Timestamp Pending
• * STOP RDF In Progress *
• * TMF STOP In Progress *
• * TAKEOVER In Progress *
• WRONG PROGRAM VERSION
• NSA Stop Update Pending
• Update NSA Stopped
• *Monitor Unavailable*
The rest of the display provides current information about each RDF process configured.
For extractors, receivers, and image trails, the configured ATINDEX value is displayed in
parentheses following the object name. In the above example, the extractor a$REXT0 and receiver
$RRCV0 are associated with the MAT, while the extractor $REXT1 and receiver $RRCV1 are
associated with auxiliary audit trail AUX01.
Because of insufficient space, however, ATINDEX values could not be displayed explicitly for
updaters. To determine the ATINDEX value of a particular updater, see the ATINDEX value of
the associated secondary image trail.
In the first example above, an RDF network master's running environment on the primary system
is depicted with a monitor process, a master extractor ($REXT0) associated with the MAT, a
second extractor ($REXT1) associated with the AUX01 audit trail, and the special RDFNET
process. On the backup system the other set of RDF processes is depicted: the master receiver
246 Entering RDFCOM Commands
$RPRG 185
0:06 185 $IMAGE0
0:00 185 $IMAGEA
0:06 185 $IMAGEA
Name RTD Time Pri Volume
$Z345 ......... ...
$RRCV0 ......... 185 $MIT
$RRCV1 ......... 185
$RPRG 185
$IMAGEA 3
22
3
3
Seqnce Rel Byte Addr Cpus
12
$IMAGE0 22
$IMAGEA 3
20
3
3
in Chapter 4.
1: 2
9568 1: 2
811008 2: 3
811568 3: 0
Err
2: 3
1: 2
1: 2
1: 2
9568 1: 2 net
811008 2: 3 undo
811568 3: 0 undo
"Displaying Current