- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- MSA1500 and SIM Again
Server Management - Systems Insight Manager
1756985
Members
2555
Online
108858
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
11-29-2007 12:24 AM
11-29-2007 12:24 AM
MSA1500 and SIM Again
I finally found time to try getting this going again. Here's what I've done:
* Installed the MSA1500 SMI-S Provider (cp007968) on Server A that has MSA1500 disks mounted.
* Added a user called HPSIM to the SMI-S Provider via the UserAccountsManager.bat file.
* Modified the wbemportlist.xml file to include root/hpmsa.
* Bounced the SIM service.
When I run Identify Systems against this server, SIM comes back with:
* One of the CIMOMs installed on this system support SLP
* This system does not have any SMI-S CIMOM installed
* This system doesn´t have a server CIMOM installed, or cannot connect to it using all credentials specified
When I look at the log on Server A, I get the following:
* Failed to parse input, error=401
* Exception during intrinsic function:CIM_ERR_INVALID_NAMESPACE(NameSpace root/cimv2 not in manager)
* BAD METHOD, function not executed, exception=CIM_ERR_INVALID_NAMESPACE(NameSpace root/cimv2 not in manager)
I can wbemdisco from the SIM Server to Server A specifying the root/hpmsa namespace and I get back valid data.
So what does it take to either get SIM to not query for root/cimv2 (don't think that's an option) or get HP's SMI-S Provider on Server A to hand something back for the root/cimv2 namespace?
Thanks!
-- Dave
* Installed the MSA1500 SMI-S Provider (cp007968) on Server A that has MSA1500 disks mounted.
* Added a user called HPSIM to the SMI-S Provider via the UserAccountsManager.bat file.
* Modified the wbemportlist.xml file to include root/hpmsa.
* Bounced the SIM service.
When I run Identify Systems against this server, SIM comes back with:
* One of the CIMOMs installed on this system support SLP
* This system does not have any SMI-S CIMOM installed
* This system doesn´t have a server CIMOM installed, or cannot connect to it using all credentials specified
When I look at the log on Server A, I get the following:
* Failed to parse input, error=401
* Exception during intrinsic function:CIM_ERR_INVALID_NAMESPACE(NameSpace root/cimv2 not in manager)
* BAD METHOD, function not executed, exception=CIM_ERR_INVALID_NAMESPACE(NameSpace root/cimv2 not in manager)
I can wbemdisco from the SIM Server to Server A specifying the root/hpmsa namespace and I get back valid data.
So what does it take to either get SIM to not query for root/cimv2 (don't think that's an option) or get HP's SMI-S Provider on Server A to hand something back for the root/cimv2 namespace?
Thanks!
-- Dave
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP