Yeah, welcome to the Dell E MC unity XT crew removal and replacement series.
In this series of short videos, we're gonna use Unisphere and UEM cli commands to identify faulted custom replaceable units on a Dell E MC unity XT storage system. We'll then look at the ways to prepare the system for service, including service mode and reset and hold modes, will demonstrate the removal and replacement of the faulted crew and finally verify the replacement crew is working correctly. One of the first things you want to do is to log on to the storage system using the Unisphere interface. This requires that you have initialized the system and provided an IP address in your browser.
And once you do that, you're gonna be brought to the page that you see here, you're gonna have to have a user name along with a password. That combination was uh also set up during the initialization process. And once you provide those correct credentials, we'll be able to log in and view the dashboard page. So we first log on to the dashboard and we can see that uh in this particular case, there's two errors that are logged And if you hover over the uh icon, you'll see some possibilities as to what those crews may be. And uh also some additional information here, software revision, date and time, etcetera uh of that particular era.
So we need to go to the uh uh the alerts page and we see here uh in this instance, we have uh three alerts now that first one calls out the entire storage processor. Uh it's a failure and tells us that we have uh an issue there. And about the same time, in fact, at the same time, we had a uh another uh issue called out. And this happens to be the uh storage processor, a the IO module contained on the storage processor. And then finally, uh the entire uh system uh error tones that we have an issue with the system. So uh this is a little different than what we normally see. We have two errors logged. And of course, if we go to the logs, uh we look again for the same date and time stamps and uh we can see the same uh scenario here.
The first uh error logged is the SP the second one, the IO module, which is uh on that SP and then the third being the system error itself. So uh we need to really uh make a, see if we can make a better determination as to what crew we need to swap out. So going to the systems view, we see the error icon, the two issues. And again, uh the SP uh a IO module and the SP itself. So I'm gonna click on the IO module uh since that was the uh the, the second one called out in terms of the, the uh the issues. So here I can see that I have orange and I'm, I'm just gonna look at the uh the, the, the different uh uh crews. That one says it's OK. That's the four port. Uh me, this is the embedded IO module. And again, uh that has a status of OK. Yeah.
Now if I continue to move on uh the SP I see that I have spaio module zero that again uh looks like it's a healthy uh condition. And then finally, the IO module one and this is the one that shows us the uh major error. So I'm thinking here that uh the, the IO module itself and not the SP uh is gonna be my first choice here uh to swap out this particular crew, seeing everything else on that. Uh uh SP looks uh healthy. So let's go to our service and because it's in the rear view and because it's a slick uh I can go ahead and validate that uh certainly with the uh env command IO module, show command, I see again to, just to confirm that uh the spaiomio module uh slick one. So this is that so again because it's in the rear of the chassis.
I need to put this uh into a state where I can change that out. I see my major issue logged from the service task page. I can see storage process A has a major issue and B looks healthy so it's, it's a, that I'm, I'm concerned here uh about and uh I need to put this into a condition again. Uh So I can swap it out and that's gonna be a reset and hold condition. Remember uh anything that you look at from the rear of the chassis typically requires a reset and hold and not a service mode. So uh I select reset and hold. I press the execute tab and uh you have to supply your service password in this particular case. And after a while, uh it will come up in a whole to reset uh state and you can check your led s your sp power led will be solid green in the uh sp fault led will be solid amber. So at this point, uh we need to swap out the crew. So uh I'll do that.
I basically uh need to uh well, in this example, I'm just gonna uh locate the crew. Of course, it has the led s uh that we mentioned above. I'm gonna pull it on out and I'm gonna take the new uh slick in this particular case and I'm gonna insert it, line it up and push it in and make sure it's seated properly uh into the uh D pe. So once I do that, I can uh go back and bring the uh storage processor into a reboot and bring it to normal conditions. So, uh again, go back to Unisphere, select reboot operation, supply my service password. And when it comes up into the normal uh conditions, I can go ahead and validate that. In fact, uh that uh fix the problem. So here we see, after some time again, this is gonna take 15, uh 20 minutes to reboot. Uh Both of those look uh healthy.
If I go to the service uh system view, uh they look healthy. And if I go to the uh enclosures view, the uh the rear of the chassis looks healthy as does the IO module that I swapped out. So, yeah, here's a case where we had two crews called out in his alerts. Simply the critical errors have gone away as well as the logs have. Tell me that it's operating normally. So again, two crews were called out. I went with the top crew because everything else on that sp looked healthy. So that is how you uh remove and replace a faulted uh slick or IO module in a unity uh XT storage system.
