Hello and welcome.
This is Rebecca from the GSEVX rail support team. And today I'll be showing you how to run the VX rail verify tool. To begin, we're going to navigate to the Dell support website and click sign in to log in with your support account. Once you are logged in, we are going to search for VX verify and then we should see the knowledge base article how to run the VX rail, verify tool.
Click that and please have a quick read through the KB yourself. I have scrolled straight down to VX verify releases, which is where the scripts are located. Before running the script to ensure that you're checking the KB for the latest release because they're always releasing new scripts every couple of weeks with more checks in them.
You want to grab the VX verify script for the VX rail version you are currently running. Once it's downloaded, we're going to use win SCP to SCP to the VX rail manager using the Mystic user and drop and drag into the home Mystic Tab. I'm using Paddy to SSH to the VX manager and then su to the root user and we'll see that the text goes red once we are root. Then, we're going to unzip the VX verify dot Zip failed.
And we're going to move the VX verify Python to temp VXV. If you haven't run the script before, then you won't have this temp VXV directory. So we'll need to create it. We can do this with the command, make directory, temp VXV. And then we're gonna run the move command again using LS dash A LTR. We can see the script in the VXV directory and the permissions currently.
We're going to change the permissions ch mod 777. And now we can see that it has read, write and execute permissions for all users. To run the script, we're going to put in Python VX verify dash R in root where it's going to prompt us for the V center server appliance route password.
This will allow the check to also check the V center server appliance. Once it's complete, the output will come directly to the terminal. As you can see down the bottom step 10, archiving all logs to temp VX verify dot zip. So then the next time you run it, it will write over temp VXB directory, but you will always have the previous run scripts in temp. Here are the scripts that it runs.
Today, we are going to look at the VX verify dot TXT using the less command, which is the same output that we saw before on the screen and the VXV dot log using the less command. This is a debugging output which will give you more specific errors to have a look and troubleshoot easier and that's the end.
Thank you for watching and have a wonderful day.