Gathering the Required Information to Perform a Fresh Reload of a DXi (DRAFT)

NOTE: Please refer to the Field Service Manual for the actual instructions on reloading the OS

In special cases or circumstances, The DXi needs an OS reload, whether it is at a customer site or internally for testing. Before this is done, we need to collect a couple of pieces

of information particularly if you are going to reload a customer’s DXi. The following items are very important in initially configuring the DXi and being able to bring it online initially

for the customer to be able to fully configure it.:

The System Serial Number
The current Node Serial Number
The OUI Number
License keys authorized for the DXi
Network/IP information to configure DXi initially (main node IP)

If the DXi is still accessible via root, the first thing that you want to do is to gather a collect log if one isn’t available so you can pull additional information if needed; this information

includes all of the above except for the license keys which have to be decoded on a DXi or pulled down from the quantum website, this will be covered later in the document.

Gathering the system/Node serial numbers and OUI Serial number

The serial numbers can be acquired from the collect.txt file once the logs are unzipped;

EXAMPLE from a collect.txt ;

###08:21:35### -System Serial Number- 'cat /opt/DXi/system-serialnumber': SV1216BVE09302

==============================================================

###08:21:35### -System OEM Serial Number- 'cat /opt/DXi/oemsystem-serialnumber': SV1216BVE09302

==============================================================

###08:21:35### -Node Serial Number- 'cat /opt/DXi/node1-serialnumber': SV1216BSC09303

==============================================================

Or they can be gathered via root access using the service.sh menu (opt/DXi/scripts/service.sh), use “Serial numbers” sub-menu;

2) Serial Numbers >>> - Tools for Node, System and OUI Serial Numbers.

Then

0) Display All Numbers

Your Choice ('q' to Exit this Menu): 0

The System Serial Number is SV1216BVE09302 (6500 System)

The current Node SerialNumber is SV1216BSC09303

The OUI is 000E09E200129FFF

NOTE: the OUI can also be gathered from a collect log if there is FC support, look for the “-gio-“ entry in the collect.txt file and look for

a “target” device, the OUI number starts with the 7th character and ends with the 11th (total of six, from the example below, the OUI is

“200137” as in the example below. If no FC support is available, the OUI can be “faked” using option 8 “ Fake Engineering Numbers”, it

will generate a fake OUI, you can then enter the two real Serial numbers

###16:14:36### -gio- 'echo WWPN Alias PLDM Role Owner Location SCSI-Host State HL Connect Option

--------------------------------------------------------------------------------------------------------------------------------

500e09e200137113 FC3 8030003001 target user Slot 1 bottom port host10 LinkDown off loop_preferred

21000024ff66d7ce FC2 8030003000 initiator user Slot 1 3-rd port host9 LinkDown off loop_preferred

500e09e200137111 FC1 8030002001 target user Slot 1 2-nd port host8 LinkUp-Loop off loop_preferred

21000024ff66d7cc FC0 8030002000 initiator user Slot 1 top port host7 LinkDown off loop_preferred ':

Gathering the Licensed features and keys

Once the Serial and OUI numbers have been gathered, you can acquire the License information from either the DXi ( if it is still available and accessible) or from the quantum website;

Using the DXi;

If the DXi is still accessible, you can log in to root and run the following commands to gather the licensed features and keys ;

To get a listing of the installed features run the following command;

“ /opt/DXi/util/qtm_lm_admin --query –feature “

Output:

----------------------------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------------------------

| 0 | yes | VTL | 256 | 0 | 256 | 2013-10-04 16:45:15 | None | 2013-10-04 16:45:15 |

| 1 | yes | NAS | 0 | 0 | 0 | 2013-10-04 16:45:15 | None | 2013-10-04 16:45:15 |

| 3 | yes | Backup Application Specific | 10 | 0 | 10 | 2013-10-04 16:45:16 | Sessions | 2013-10-04 16:45:16 |

| 4 | yes | Data Deduplication | 0 | 0 | 0 | 2013-10-04 16:45:16 | None | 2013-10-04 16:45:16 |

| 5 | yes | Replication | 80 | 0 | 80 | 2013-10-04 16:45:17 | TB | 2013-10-04 16:45:17 |

| 6 | yes | Storage Capacity | 80 | 0 | 80 | 2013-10-04 16:45:16 | RAW TB | 2013-10-04 16:45:16 |

| 9 | yes | OST | 0 | 0 | 0 | 2013-10-04 16:45:17 | None | 2013-10-04 16:45:17 |

| 10 | yes | DXi Advanced Reporting | 0 | 0 | 0 | 2013-10-04 16:45:18 | None | 2013-10-04 16:45:17 |

| 11 | yes | DXi Advanced Reporting Services | 0 | 0 | 0 | 2013-10-04 16:45:18 | None | 2013-10-04 16:45:17 |

----------------------------------------------------------------------------------------------------------------------------

To get the actual license keys, run the following command;

“ /opt/DXi/util/qtm_lm_admin --query –key “

Output;

--------------------------------------------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------------------------------------------------------------

| 1 | 0 | 1.0 | VTL | 256 | PKRJCJW2FT6NR2DW8U55MPY8LTRQVG49CRE9UGD5 | 2013-10-04 16:45:15 | |

| 2 | 1 | 1.0 | NAS | 0 | 8QBMY48QLBTJ3PUDDU37A4WXWDXLN2GRJQ9J85BG | 2013-10-04 16:45:15 | |

| 3 | 6 | 1.0 | Storage Capacity | 80 | GMJHZNPCW8TXPCSKN9CEBABG6K2F3EJ4HW8A4PNY | 2013-10-04 16:45:16 | |

| 4 | 4 | 1.0 | Data Deduplication | 0 | JEHAMRNZ5Z4XF9QNS9Y72K789LDRAHNPACG5K597 | 2013-10-04 16:45:16 | |

| 5 | 3 | 1.0 | Backup Application Specific | 10 | MVTTGWACYDFRL4SUB98QVFB8JMMEDNFJTR4AFAYM | 2013-10-04 16:45:16 | |

| 6 | 5 | 1.0 | Replication | 80 | 3WTRPR2W8AVFA9EJUVWE59262VPJW9CXCA7JCLPE | 2013-10-04 16:45:17 | |

| 7 | 9 | 1.0 | OST | 0 | 7AC4V5HH4PJSDVMH2PMKTUSKD73WJF9FLEJ2SJQX | 2013-10-04 16:45:17 | |

| 8 | 10 | 1.0 | DXi Advanced Reporting | 0 | 7NPCF8A37HPB426XPMJC5BUDMQD6BEKG8TYFRZN6 | 2013-10-04 16:45:18 | |

| 9 | 11 | 1.0 | DXi Advanced Reporting Services | 0 | 5BMGS26GEYJ2K5XYW4HJKKZV3DJ2XDMD2C32J584 | 2013-10-04 16:45:18 | |

Using the quantum website (Quantum Employees only! );

IF the DXi is not accessible, you can go to the Quantum website link below, log in and enter the serial number to get the features/licenses available;

Go to the internal quantum website;

http://ppowsql2k5rs1/Reports/Pages/Report.aspx?ItemPath=%2fFreshlot%2fDX%2fDX+License+Info

From the left side of the browser, select the model that you are working for (IE…DXi6800 for this example and SN - CX1324BVT00168 ).

Then from the right side of the browser, press the “View Report” Radio button to display the 68xxxx listing.

Now press “CTRL-F” to open a search box and enter the serial number you are working with.

Highlight and save the keys;

EXAMPLE for a dXi68xx, SN - CX1324BVT00168

2.2.0.1_68-49937-Build3

2.2.0.1_68-9258-Build3

02.01.02-1639

CX1324BVT00168

6/26/2013

20149B

YNGGRTAT5QMZA87DMJVBT87CNQPSXBK8GB4Z2F2H

KRS7EE9BY6F45U2GU8EJEU7CUKVNAHV4TYNX5VL7

BA37HN6J2EFW56HLJX9F9Z2XSX8GFNHUU8PEERCM

JQWZGJJRR4XP87NEJC2X5YS9ELWSFHMP35LYA6QU

BV2DNQ9KS9V6MW4P7MU6SUYH4GRAGSL2LQGLWUE2

NOTE: if the website is not accessible and you do not have the keys, you can ask the customer and see if they have them, if they do not, you will need to request a

set of licenses from SES (or use the license key generator) to be able to enable the features. Please note that if the keys can be recovered using the DXi, collect or

customer please do so, using a key generator will create new keys (different number than the original installed at the factory or on the initial install) and should be

the last resort used. if the customer later finds the original keys, they can be installed/added and any additional storage that is vailable WILL be enabled and once

used, it can NOT be undone, especially if the DXi is rebooted, the new capacity will be found/enabled and the File system will be expanded (as in the case of a DXi46xx).

Gathering Network/IP information;

The DXi can be reloaded and installed without the customer network information but in order to perform a good job, we prefer to hand over the DXi when it is fully available to the

customer on their network so they can fully configure it. You can gather the network information from a collect log, the actual DXi if available or from the customer.

Gathering the network information from the DXi

The network settings can be acquired in several ways;

Ask the customer ig they are av.

If the DXi is still available, you can gather the network information from the Configuration/system/Network tab

If the GUI is NOT available and you have a collect log, you can find the network information from the systemstatus.xml (along with much more useful info) file;

Sample output;

(info in yellow can be useful as well when running the service.sh script and initially configuring the DXi);

<?xml version="1.0" encoding="UTF-8"?>

<Vendor>Quantum</Vendor>

<Revision>2.3.0.52200 Build62</Revision>

<Status>HardwareFailure</Status>

<CurrentSystemDate>Monday, October 07, 2013</CurrentSystemDate>

<CurrentSystemTime>16:14:44 America/Los_Angeles (PDT)</CurrentSystemTime>

<TimeZone>America/Los_Angeles</TimeZone>

</DateTime>

<Domain>quantum-sqa.com</Domain>

NOTE: if all you have is the IP, once you use the service port to get access to the GUI via IP 10.17.21.1, enter the IP for BOTH the IP and the GATEWAY. The

customer can then configure the DXi when they get access to it.

One you have the above mentioned information, you can proceed to reload the DXi.

NOTE: if additional information and/or assistance is need, please contact a member of ASPS or SES.