- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Confusion with wbem and mxnodesecurity settings
Server Management - Systems Insight Manager
1752777
Members
6427
Online
108789
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО04-04-2007 01:59 PM
тАО04-04-2007 01:59 PM
When I set up HPSIM 5.1 I used mxnodesecurity to load the wbem details for my Virtual Servers.
That seemed to have worked as theses servers were correctly identified.
If I look at the settings via an mxnodesecurity -l command they still look okay.
but if I use HPSIM and click on the server name and then go to Tools tab and the security settings link, the tool indicates that wbem is set to use the global settings. And as the credentials are blank this doesn't seem to be correct. I'd expect my data collection tasks to fail especially as they have neither agents or SNMP installed.
Anyone know what mxnodesecurity lists?
Should this reflect the actual credentials in use?
That seemed to have worked as theses servers were correctly identified.
If I look at the settings via an mxnodesecurity -l command they still look okay.
but if I use HPSIM and click on the server name and then go to Tools tab and the security settings link, the tool indicates that wbem is set to use the global settings. And as the credentials are blank this doesn't seem to be correct. I'd expect my data collection tasks to fail especially as they have neither agents or SNMP installed.
Anyone know what mxnodesecurity lists?
Should this reflect the actual credentials in use?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-05-2007 10:48 AM
тАО04-05-2007 10:48 AM
Re: Confusion with wbem and mxnodesecurity settings
What are your global settings for WBEM? I would think that going to an individual server would only show if the settings were modified specifically for that server. Running mxnodesecurity -l on my Insight Server shows the global settings for WBEM and SNMP(since we run it). It also shows on some servers the specific settings we had to use for some servers (i.e. different credentials).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2007 10:08 AM
тАО04-06-2007 10:08 AM
Solution
Rob,
mxnodesecurity -l lists the actual WBEM and SNMP names used to access a specific server. During the SIM discovery / identification process SIM steps through the globally configured SNMP community and WBEM user names and once it finds a name that the server responds to it makes an entry in the nodesecurity.xml file. From that point on it will use the discovered names. This of course can be overridden by configuring system specific protocol settings.
mxnodesecurity -l lists the actual WBEM and SNMP names used to access a specific server. During the SIM discovery / identification process SIM steps through the globally configured SNMP community and WBEM user names and once it finds a name that the server responds to it makes an entry in the nodesecurity.xml file. From that point on it will use the discovered names. This of course can be overridden by configuring system specific protocol settings.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-09-2007 08:11 AM
тАО04-09-2007 08:11 AM
Re: Confusion with wbem and mxnodesecurity settings
The global wbem credentials are blank.
When I built the new HPSIM Server I used a wbem batch file to create the wbem entries for the specific servers. I use the same batch file for password updates. Saves quite a bit of manual work.
Joel,
I would have had a situation where wbem was enabled but with no credentials added when the discovery/identification processes ran. Then the wbem batch file would have run and populated the mxnodesecurity.xml file.
So now, if I drill down via HPSIM to the server protocol settings it is flagged as using the global settings which are blank. But the xml file has the server specific wbem details.
From what you say the xml file is the final item used, which does seem to agree with what I see, namely that the virtual servers are correctly identified.
It would be nice to see the that the server specific credentials are being used from the HPSIM view.
When I built the new HPSIM Server I used a wbem batch file to create the wbem entries for the specific servers. I use the same batch file for password updates. Saves quite a bit of manual work.
Joel,
I would have had a situation where wbem was enabled but with no credentials added when the discovery/identification processes ran. Then the wbem batch file would have run and populated the mxnodesecurity.xml file.
So now, if I drill down via HPSIM to the server protocol settings it is flagged as using the global settings which are blank. But the xml file has the server specific wbem details.
From what you say the xml file is the final item used, which does seem to agree with what I see, namely that the virtual servers are correctly identified.
It would be nice to see the that the server specific credentials are being used from the HPSIM view.
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