Quick Takeaways while installing NetApp FAS Series SRA 2.0.1 with SRM 5.0.1

I am currently deploying an SRM Solution with the following config and there were so many errors to watch out for:

Protected Site:

vCenter 5.0.0 build 455964

SRM: 5.0.1 build 633117

NetApp FAS Controller: FAS3270 (Active Active Controllers)

NetApp FAS/V Series SRA: 2.0.1

Recovery Site:

vCenter 5.0.0 build 455964

SRM: 5.0.1 build 633117

NetApp FAS Controller: FAS3240 (Active Active Controllers)

NetApp FAS/V Series SRA: 2.0.1

So first and foremost thing, do not install SRA 2.0.1, the moment you try and pair the Array managers, you will get this below error:

“Internal error: std::exception ‘class Dr::Xml::XmlValidateException’ “Element ‘SourceDevices’ is not valid for content model: ‘(SourceDevice,)'”

This is because of a bug confirmed by NetApp, Bug ID: 642115

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=642115 (will require a NOW login)

So, the workaround is to either include the volumes manually that you want your Array manager to detect or simply fall back to NetApp SRA 2.0.0 (which was the quickest option for me looking at the amount of volumes we had on both the controllers)

Now then, I was  unable to add 2nd active controller (Error: SRA command ‘discoverArrays’ failed.), although IP was pingable, was able to ssh into the filers etc…so how did I resolve it? by running these simple commands on all the controllers:

options httpd.admin.enable on

options httpd.enable on

options httpd.admin.ssl.enable off

A quick reminder on NetApp Volume design:

You need to ensure that your VMDK’s or RDM’s does not span across controllers (either at Prod site or at the recovery site), this is not a supported configuration by NetApp

I shall keep updating this post as I move forward with my configuration 🙂

Advertisements

One thought on “Quick Takeaways while installing NetApp FAS Series SRA 2.0.1 with SRM 5.0.1

  1. came across the same issue, tried as you’ve suggested to install SRA 2.0.0 but for IBM N Series but no joy. It doesn’t recognise that SRM is installed so won’t install. I’ll need to try the other workaround. (Using vCenter 5.1.0a Build 33762 and SRM 5.1.0 Build 3385)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s