Pillar Axiom: How to determine the Master Node

Asset ID:	1-71-1610060.1
Update Date:	2018-05-06
Keywords:

Solution Type Technical Instruction Sure

Solution 1610060.1 : Pillar Axiom: How to determine the Master Node

Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 300 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Pillar Axiom 500 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

The following document explains how to determine which Slammer Control Unit is acting as the Master Node.

Solution

One slammer control unit is acting as the Master Node. An election between all the slammer control units takes place (the number of Slammers does not matter) during the ColdStart of the Axiom (boot) or when the Master Node is power cycled, fully restarted (not a warmstart) or getting Disabled.

One of the responsabilities of the Master Node:

- sending brick events to the Active pilot

- gather brick logs

- send/receive messages from the pilot to perform tasks.

Note: warmstarting the Master Node does not trigger an election to get a new Master Node but can help clear some special conditions in memory like Brick Events not being sent to the pilot.

The Master Node can be identified using the CLI (no option on the Axiom GUI):

- On AxiomONE R3 and R4:

D:\>supporttool sub -u administrator -H 10.10.10.10 GetCurrentMasterNode

Password:

Header

ProtocolVersion: 0.1

SessionKey: 358a13a9d0f497e7d20ae407452e23a5

Time: 2013-12-22T15:10:59+00:00

ClientData: supporttool

RequestStatus: Succeeded

Error List

GetCurrentMasterNodeResponse

TaskID: ID88836143-d21d-b211-9f9b-000e0cd07dff

TaskFQN: /GetCurrentMasterNodeTask_2445

SlammerID: ID8172f823-d21d-b211-b00b-000e0cd07dff

SlammerFQN: /Slammer2

SlammerName: Slammer2

ControlUnitNumber: 0

WWN: 2008000b08044fe2

D:\>

The Master Node is Slammer2 CU0 on the above example.

Supporttool.exe is attached to this document.

- On AxiomONE R5:

D:\CLI>axiomcli login -u administrator -p pillar 10.10.10.10

*****************************************************

** **

** This is a company computer system with access **

** restricted to those with proper authorization. **

** Authorized parties are restricted to those **

** functions which have been assigned to perform **

** work related duties. Any unauthorized access **

** will be investigated and prosecuted to the **

** full extent of the law. If you are not an **

** authorized user, disconnect now. **

** **

*****************************************************

D:\CLI>axiomcli slammer -list -masternode

/Slammer1

MasterNode: /Slammer1/1

D:\CLI>

The Master Node is Slammer1 CU1 on the above example.

Axiomcli is available on the webserver running on the Axiom: open a web browser on the virtual IP address.

[This section is not visible to customers.]

The script getMasterNode.pl is available on the log servers. It has been tested on R3, R4 and R5.

Run the script on the main folder (pilot logs are needed).

-bash-4.1$ getMasterNode.pl -h

Description: Provides the Master Node from the current logs.

The tool needs to be run on the main log folder.

Usage: getMasterNode.pl [-o <A009999ZZZ_MasterNode.txt>]

[-o | --outputfile <file to be generated by getMasterNode.pl>]

-bash-4.1$ getMasterNode.pl

The Master Node is Slammer1 CU1 (2009000B08045B2A).

-bash-4.1$

It is best practice to double check the Master Node from the CLI in case the logs are not up to date or other failures have occurred on the Axiom in the meantime.

On R5, Support Engineer should use pcli to hide the password and get the slammer node name from the logs (or check output.txt generated by ClearFailureHist_R5.exe).

Example of pcli command:

D:\>pcli sub -u pillar -H 10.10.10.10 GetMasterSlammerNode

Password:

Message

Response

CorrelationID: 1388654942

BeginStreamResponse

TaskGuid: 4130303136383342A13FC5D57DFC6D70

TaskFqn: /GetMasterSlammerNode/490137/pillar

Message

Response

CorrelationID: 1388654942

GetMasterSlammerNodeResponse

WuName: 2009000B08041F1A

Message

Response

CorrelationID: 1388654942

EndStreamResponse

TaskGuid: 4130303136383342A13FC5D57DFC6D70

TaskFqn: /GetMasterSlammerNode/490137/pillar

D:\CLI>

Attachments

This solution has no attachment