Skip to main content

system service-processor log show-allocations

Contributors
Suggest changes
PDFs

Display the Service Processor log allocation map

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The system service-processor log show-allocations command displays the allocation map of the Service Processor logs collected in the cluster. The Service Processor logs of a node are archived in the mroot directory of the collecting node. This command displays the sequence numbers for the Service Processor log files that reside in each collecting node.

Parameters

{ [-fields <fieldname>,…​]

If you specify the -fields <fieldname>, …​ parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

| [-instance ] }

If you specify the -instance parameter, the command displays detailed information about all fields.

[-node {<nodename>|local}] - Node

If you specify this parameter, the command displays the sequence numbers of Service Processor log files that the specified node has collected.

[-remote-node <text>] - Remote Node

If you specify this parameter, the command displays the sequence numbers of Service Processor log files that have been collected from the specified remote node.

[-seqList <integer>,…​] - Log File Sequence Numbers

If you specify this parameter, the command displays information about Service Processor log files with the specified sequence number.

Examples

The following example displays the allocation map of the Service Processor log files in the cluster.

cluster1::> system service-processor log show-allocation
Node                From Which Node     Log File Sequence
------------------- ------------------- ----------------------------------
cluster1-01
                    cluster1-01         10, 11, 12, 13, 15
                    cluster1-02         14, 15, 16, 17
cluster1-02
                    cluster1-01         14
                    cluster1-02         11, 12, 13
4 entries were displayed.

cluster1::>