- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- VMware SRA & 9.5 - "Invalid XML returned from SRA....
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2011 03:36 AM
10-11-2011 03:36 AM
Folks
I'm trying to setup a new VMware SRM solution (SRM 4.1.1) using a couple of P4500s running SANiQ 9.5.
I'm getting the message "Invalid XML returned from SRAL Failed to get attribute 'id' for node 'Initiator'." when trying to configure the SRA, the array is detected fine though. I'm using the SRM version 1-4 SRA that's downloaded along with the 9.5 update, there was no earlier version on the servers that needed uninstalled.
Suggestions would be most welcome.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2011 08:45 AM
10-24-2011 08:45 AM
SolutionJust a quick update in case anyone else hits this issue.
The problem turned out to be that we hadn't entered the vSphere servers' IQNs in the CMC server section.
We have a security requirement to use CHAP authentication for iSCSI sessions so hadn't bothered entering the IQN details but these are used by the SRA to identify the servers so need to be entered (and in lower case as well apparently).