Pillar Axiom 500 Storage System
 
Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
 

In this Document

Goal

Fix

Applies to:

Goal

This article describes the process for disabling the  CIFS memory tracking code embedded in AxiomOne Software.

Fix

Hardware and Software Versions

Hardware Software
All 03.01.00 and Above
Prerequisites

The following prerequisites must be met for this procedure.
1. A Level 1 Administrator Account with GUI or CLI access to the Axiom.
2. The Supporttool license should be installed or a maintenance window for a shutdown / restart of the axiom.
3. supporttool downloaded from the Axiom or the CSC tool ws_axiom.exe available on a workstation with network connectivity to the Axiom.

Details

Under some circumstances it might become necessary to disable the embedded memory tracking code in the AxiomOne NAS OS. This procedure describes the process for this task.

The Memory tracking code is turned off at a File Server level of granularity, and only affects File Servers that have the CIFS protocol enable.



Note this procedure should only be done with the assistance of an Oracle Technical Support Engineer and within a maintenance window, as a minimal disruption of service is necessary to complete the procedure.

CIFS File Servers with the "Oplocks" feature enabled should have all client access halted prior to the initiating the procedure, as the risk of clients with opened files have the possibility of cashed writes that have not been flushed to the Axiom File Server. Any client side cached data would be discarded by the client when the established client / server connection is broken during the procedure.
For each Axiom File Server do the following procedure to disable the memory tracking code.

1. In the AxiomOne GUI navigate to Storage -> File Server-> Choose a file server -> in the actions drop down Modify File Server - > Select the CIFS tab.
2. In the Server Comments Field enter the following string
1. PDS_MALLOC_SMBD=0
3. Click Ok and monitor the Modify File server Task for Completion.
Once all the File Servers have had their Comment fields edited you must warmstart the Slammer ControlUnit the file servers are owned by or shutdown and restart the Axiom to enact the changes. See Enacting Changes for the procedure to warmstart the Slammer ControlUnits. Note: a system shutdown and restart will not be documented in this article.

Enacting the Changes
At the direction of the Support engineer enacting the changes is done via forcing the File Server(s) owning ControlUnits to warmstart.

1. Using the following supporttool command

1. supporttool sub –H (ip or FQN of the pilot) PerformControlUnitReset Slammer=/(name of Slammer) ControlUnitNumber=(0 or 1)

2. Example : supporttool sub –H 12.1.2.3 PerformControlUnitReset Slammer=/NAS_SLAMMER ControlUnitNumber=1

2. This will cause a momentary disruption as the Slammer ControlUnit rapidly unloads and reloaded the operating system and services, on Current code this process takes approximately 15 to 20 seconds. Windows Clients will experience momentary disruption due to the CIFS protocol’s use of TCP connections.

3. As an alternative there is a Customer Service tool that simplifies these commands and is available via the Oracle Technical Support Engineer.

This solution has no attachment