?
Solved

Initialization Loop on EMC CX300 SAN SPA

Posted on 2007-10-15
3
Medium Priority
?
3,309 Views
Last Modified: 2013-11-14
Hi All,

I have an EMC CX300 SAN that I am trying to configure.
I have managed to get everything working except for one problem.
SPA seems to be stuck in a loop when Initialising the security and creating the domain. (Via Navisphere web interface)

I get the following messages/prompts:

Responds with:"Global security is not initialized. It is highly recommended that you initialise global security [YES/NO]"

Puts up Navisphere login, I enter username and password, same as SPB.  
If I click [YES], it prompts for a username and password, which I enter, then it progresses to the next window.

Responds with: "Confirm: AddUser. Add the following user, admin [YES]"
Click on [YES]
Responds with: "Success: Initialize Security: Success [YES]"
Click on [YES]
Responds with: "This storage system is not in a domain.   It is highly recommended you create a new domain for this system."

If I Select the only choice SPA's IP address and click ok, it says "This operation will assign the node - xxx.xxx.xxx.xxx to be the domain master [YES/NO]"

If I click YES, it says "Node xxx.xxx.xxx.xxx was successfully assigned to be the domain master of the domain.  Please note that it will take few minutes to propagate the master information to all systems in the domain [OK]"

When I click [OK] It appears to login to the interface, then the page goes blank.
I wait 5 minutes then reload the Navisphere webpage again and it makes me go through the whole process again.

Am I missing a step?  What else can i do to make this setting permanent?

Please note: this SAN has LUNs that are currently being used.

Regards,

Brett
0
Comment
Question by:medfacit
  • 2
3 Comments
 
LVL 30

Accepted Solution

by:
Duncan Meyers earned 2000 total points
ID: 20090083
Navisphere security is global (as is most things in Navisphere)- the problem may be occurring because you're trying toi set it up per SP.

To Fix:

Close your Navisphere session.

Open a we browser and go to http://<IP Address of SPA>/setup
Open a second web browser and go to http://<IP Address of SPB>/setup

You'll likely be prompted for the username and password you set up earlier.

Check that the IP details for SPA are correct and check the peer IP address is set to SPB. Check that the IP details for SPB are correct and check the peer IP address is set to SPA. Note that they should be on the same subnet.

Scroll down until you find a button for "Reset Navisphere Security" (I forget the exact wording - you'll recognise the right option, though) and click on that button, then confirm.


Point a web browser to the IP address of SPA only (do NOT open a session with SPB). You'll be prompted to set up security again. Set the username and password.

Resetting the security domain is non-disruptive, but changing IP addresses will require reboots of the individual SPs. PowerPath will handle LUN failover for you, so you can do it during the day at a quiet time.
 
How did the array get itself into this state in the first place? Generally speaking, security is configured at initial installation, and not touched again...
0
 

Author Comment

by:medfacit
ID: 20090880
Hi,

Thanks for that info.  After checking again it seems that the SPB peer address was set to an old IP address.  I changed that to the new IP address of SPA, then did a master reset on both SP's, then configured SPA and it now seems happy.

This situation came about from moving the SAN to a new datacentre and new IP range.

Thanks again,  

Brett
0
 
LVL 30

Expert Comment

by:Duncan Meyers
ID: 20098085
That'd do it... :-)

Glad I could help.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Many businesses neglect disaster recovery and treat it as an after-thought. I can tell you first hand that data will be lost, hard drives die, servers will be hacked, and careless (or malicious) employees can ruin your data.
Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
Suggested Courses
Course of the Month13 days, 19 hours left to enroll

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question