I have a CX4-960 with the 960 drive option. Up to now BE bus 0-3 were the only buses populated with enclosures (this array was just upgraded from a Cx3-80). Today I go to install the first enclosures on Bus 4 and Bus 5, which are on I/O Module 2 and are ports 0 and 1 and each I/O module.
Following standard procedure for adding an enclosure I cable up one side of the enclosure, plug the SFP into the SP and see a link light on the SP. But in Navisphere the BE port shows as Uninitialized. This is what the cli shows for that I/O module:
Information about each I/O module(s) on SPB SP ID: B I/O Module Slot: 2 I/O Module Type: Fibre Channel I/O Module State: Present I/O Module Substate: Good I/O Module Power state: On I/O Carrier: No
Information about each port on this I/O module Physical Port ID: 0 Port Role: BE Logical Port ID: N/A Port Usage: Uninitialized Port Type: Fibre Channel Port State: Uninitialized Port Substate: Uninitialized Is Persisted: No
Physical Port ID: 1 Port Role: Unknown Logical Port ID: N/A Port Usage: Uninitialized Port Type: Fibre Channel Port State: Empty Port Substate: The SFP is not present Is Persisted: No
Physical Port ID: 2 Port Role: Unknown Logical Port ID: N/A Port Usage: Uninitialized Port Type: Fibre Channel Port State: Empty Port Substate: The SFP is not present Is Persisted: No
Physical Port ID: 3 Port Role: Unknown Logical Port ID: N/A Port Usage: Uninitialized Port Type: Fibre Channel Port State: Empty Port Substate: The SFP is not present Is Persisted: No
Anyone know how to initialize the BE ports that have not been used yet?
You can check this with the NST yourself to see if the ports need to be initialized. There is an oppurtunity to cancel before any action is taken (at the summary screen). If you do need to initialize and reboot, it would be a coordinated reboot similar to an NDU (SPB, wait 360 seconds, SPA).
We had a CX4-480 that EMC upgraded to a CX4-960 and we ran into exactly the same thing. When they added the additional IO modules they didn't initialize them. We had to take another 4 hour outage window to have EMC back in to initialize the ports properly. It required reboots of the SPs and I'm not sure what else. I wasn't directly involved in the change, just in getting EMC to fix the issue (they were supposed to do it all with only one outage).
Based on that, I'm not sure if it is something you can do yourself or if the CE has to come in to complete it. Have to check with the CE.
You think you are mad? EMC even had a Project Manager working to make sure our CX4-480 to 960 upgrade went smooth. We planned it for well over a month. We scheduled downtime on many, many production servers. We did everything right. Then when EMC came back a few days later to connect the additional DAEs they couldn't do it. We had to schedule another outage on the same production servers right before RRSP Season (which is not a good time to make changes in the IT infrastructure of a Financial Services company).
That had visibility all the way up to the CIOs and above.
Somehow the phrase "We are not amused" just didn't quite cover it!
On the bright side, the second four hour outage window did fix it for us
I was going to ask the same thing. Was it a rolling reboot of the SPs, thereby leaving the hosts online? Or was it a complete outage?
I am in the same situation, took months planning the upgrade, took months to schedule the downtime, and had a project manager assigned to cover all the details. Downtime is very hard to come by in our infrastructure. We have one six hour maintenance window each month to address any hardware upgrades, OS patching, upgrades, etc... that I have to share with all the other server admins in the data center. So I don't always have time alloted each month to upgrade PowerPath or install the latest HBA firmware and drivers. It could be months before I have a window to do any work. Now I have projects that are being deployed that are waiting on this storage and the next time I have a maintenance window is the end of May. Oh yes I do understand!
I just got off the phone with one of the engineers that performed the conversion from the Cx3-80 to the CX4-960. He said that he looked through the procedure for the conversion and there was not a section that mentioned initializing the extra backend ports. This may be why yours did not get initialized as well Allen.
He did say that it looks like it is a NDU reboot, and can be done through the NST or the CLI. I am waiting to hear back from support though to confirm this. If it is a rolling reboot, then that is good, I can just do that in the evening and won't need to take any hosts offline.
Thanks for the information and confirmation that it is just a coordinated reboot. That is something I can accommodate. Is it the Install I/O Module wizard in the NST?
bertog
61 Posts
1335
0
Posted March 17th, 2010 08:00
You can check this with the NST yourself to see if the ports need to be initialized. There is an oppurtunity to cancel before any action is taken (at the summary screen). If you do need to initialize and reboot, it would be a coordinated reboot similar to an NDU (SPB, wait 360 seconds, SPA).