Unsolved
14 Posts
0
1942
powermax-node pods in CrashLoopBackOff, with initiator/timeout errors
Hi, I'm new to PowerMax, no admin training, so, please excuse newbie questions. Trying to test `csi-powermax` CSI driver on my OpenShift cluster, I'm happy to see `powermax-controller` pods Running, but `powermax-node` pods start crashing after first 10 minutes. When I check pods' logs, I see error messages like;
- "nodeStartup could not GetFCHostPortWWNs"
- "GetInitiatorList failed: Get \"https:// :8443/univmax/restapi/91/sloprovisioning/sym
metrix/000196800573/initiator\": context deadline exceeded"
- "No valid initiators- could not initialize FC or iSCSI"
early, then later when CLBO;
- "Couldn't find any ip interfaces on any of the port-groups"
- "No topology keys could be generated"
I'd be grateful if someone here can nudge me in the right direction as to what may be amiss perhaps with the array or the deploy configs.
thanks, - Hiro
ankur.patel
286 Posts
1
May 12th, 2021 12:00
No problem. Zoning is how the powermax "sees" your servers. Once this is done the install script logs into the powermax, sees that the host is there registers it.
When the csi driver does its thing it will tell the powermax to create the desired volume and present it to the servers it was zoned/registered to.
The zoning is a one time thing so not something you need to do beyond the initial deployment unless you add additional servers
miyamotoh
14 Posts
0
May 12th, 2021 12:00
Thanks for the response. I know I want to test with FC, but am not sure what "zoning a node" means. I have to pass this to my PowerMax admin. Bear with me...
ankur.patel
286 Posts
0
May 12th, 2021 12:00
did you already zone the nodes to the powermax? or if iSCSI log into the powermax via the host iscsi initiators?
ankur.patel
286 Posts
0
May 14th, 2021 08:00
yup, this is all your storage team would handle in Unisphere and on the network switches. Nothing you can really see from the host side of things.
miyamotoh
14 Posts
0
May 14th, 2021 08:00
Thanks for clarifying that. Will wait for the admins, see if I can get through, and report back, next week.
But, actually, if it's not too much to ask, what are the things that need to be done in Unisphere? I can log into Unisphere. I just don't have access to Switches, etc..
miyamotoh
14 Posts
0
May 14th, 2021 08:00
While I wait for responses from my PowerMax admins who are based in Covid-stricken area, maybe I can ask a few more newbie questions here.
Going back to the installation doc, I see;
as prereqs, and I'm not sure how to ensure these are done properly. Are these about creating Host(s) and/or a Host Group in Unisphere? Or, are these something that needs to be done outside Unisphere?
Thanks, - Hiro
YamunadeviS
8 Posts
0
May 18th, 2021 06:00
Get \"https:// :8443/univmax/restapi/91/sloprovisioning/symmetrix/000196800573/initiator
miyamotoh
14 Posts
0
June 16th, 2021 08:00
Sorry, it took a long time to circle back. I finally got zoning done, and I do see the value in the `/sys/class/fc_host/host1/port_name` on my VMs shown in the Hosts > Initiator page of the array on Unisphere. And I made sure my Port Group that I specify in the YAML for driver install has what the Junctions from zoning shows, though the doc seems to say `portGroups` is for iSCSI only, while I need FC with this PowerMax.
Anyhow, my error persists, "no topology key could be generated," and the powermax-node pods keep crashing/restarting.
The Hosts > Initiators page takes a long time to load on Unisphere. When it loads, it'd show 25000+ initiators for the array. When I `time curl` the GET call for the Initiators list, sometimes I get the response (=huge JSON) after 3 minutes, other times, I never get response for 15min... Is this (slowness) the problem? Any suggestions?
thanks, - Hiro