how do you change it? i dont have the id and passwordI'm trying grpadmin / grpadmin, either the password was changed or there's something else I could try.
Been called out because of issues and it looks like it's storage related and of course none of this info is documented.
You need to have the admin password to change the admin password. If you don't have it, you need to contact EL Support, or if you have physical access and want to reset it yourself then see the following info:how do you change it? i dont have the id and password
how do you change it? i dont have the id and password
that's why you have two fabrics right? when one switch goes down [due to upgrade or well something unplanned ] you have second fabric still serving all needs, though ofc performance will suffer as you have only 50% available now.I don't recall, been a while and I work another job now but if it's the incident I have in mind, it turned out that I was able to refresh the volumes in ESXi and it fixed the issue and did not need to get into the SAN. Basically a switch hiccuped and despite the system being setup with redundancy, it failed (I told them we should test it before it went production but they did not want to). I would have probably been trying to get into the SAN to check logs etc to get an idea of what is going on, as ESXi was showing that the storage was unavailable and did not want to do anything that could render the problem worse. I basically bit the bullet and did a storage refresh to see what happens, and it ended up working. The VMs continued on where they left off. That was scary. This is minor compared to what we deal with at my current job though, if something goes down it's taking out a whole community not just a company.
As a side note, I find it terrible that some of these routines (such as password reset outlined above) involve having to reboot or otherwise make the SAN unavailable. A SAN is not something you ever ever ever want to reboot. Firmware updates are another bad one. When we got a new SAN enclosure, the whole selling point of these is that you can hook it up and basically introduce it with the new one and they automagically work with each other. WRONG. Because you need to update the old one, which involves a reboot. And scheduled downtime etc... what is suppose to be a seamless operation ends up requiring to impact the entire organization.