OK so we had a scheduled power outage at one of our secondary DCs. The SAN was shutdown following the VNX shutdown procedure via Unisphere.<\/p>\n
After the power was back on everything on the SAN came up accept the Unisphere web management. After some Google-fu the culprit was the NAS slots had not come up properly, in fact they were powered off. This saved me a full round trip to this DC, very handy. If this still doesnt fix it – something is wrong with the physical cabling between the nas blades and the Control Station, or there is a fault.<\/p>\n","protected":false},"excerpt":{"rendered":" OK so we had a scheduled power outage at one of our secondary DCs. The SAN was shutdown following the VNX shutdown procedure via Unisphere….<\/p>\n","protected":false},"author":2,"featured_media":377,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11],"tags":[],"class_list":["post-267","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-storage"],"acf":[],"yoast_head":"\n
\n
\n[root@vnx-cs0 ~]# \/nasmcd\/getreason
\n10 - slot_0 primary control station
\n11 - slot_1 secondary control station
\n 0 - slot_2 off
\n 0 - slot_3 off
\n<\/code>
\nAs you can see slot 2 and 3 nas blades are off. Now this array does not use file storage only block. That does not matter for the virtual ip and unisphere management service. To power them on use these commands:
\n
\n\/nasmcd\/sbin\/t2reset pwron -s 2
\n\/nasmcd\/sbin\/t2reset pwron -s 3
\n<\/code>
\nOnce they power on – the state changes on the getreason:
\n
\n 5 - slot_2 contacted
\n 5 - slot_3 contacted
\n<\/code><\/p>\n