Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- ProLiant
- >
- Server Management - Systems Insight Manager
- >
- V6.2 Unknown system for certain systems
Server Management - Systems Insight Manager
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Email to a Friend
- Report Inappropriate Content
01-14-2011 02:57 PM
01-14-2011 02:57 PM
V6.2 Unknown system for certain systems
I just upgraded from SIM V5.3 to 6.2 (with the hotfix).
It all went fairly smoothly (just some normal problems with Oracle).
My environment has all sorts of hosts mostly Proliants with Windows or Linux (RedHat) but we also have about 150 RX Itanium Linux host which all appeard fine under 5.3.
After a system identification task was set off to verify all was OK after the upgrade, there were quite a few systems with complaints about some protocol not responsing (WBEM for example) that should be the case because the only really common protocol used by all hosts is SNMP which should be enough to do a basic ID of the system.
But after this I found that all the RX's got set to a system type of Unknown. My understanding, unless it has changed, is that Unknown means that SIM has not identification rule for the system OID from SNMP. I chaned SNMP so all the RX's with snmpwalk using the v1 protocol and the correct community and they all reply in full as expected. I deleted all the RX's and manually discovered them but same result. The logs also says that there is no SNMP system ident rule found.
Other systems aparts from the RX's seem to get discovered OK as far as I can tell. It almost seems as if all the rules that apply to Itaniums have been removed yet even older systems like Alphas running Tru64 are OK. Does anyone have any ideas here?
It all went fairly smoothly (just some normal problems with Oracle).
My environment has all sorts of hosts mostly Proliants with Windows or Linux (RedHat) but we also have about 150 RX Itanium Linux host which all appeard fine under 5.3.
After a system identification task was set off to verify all was OK after the upgrade, there were quite a few systems with complaints about some protocol not responsing (WBEM for example) that should be the case because the only really common protocol used by all hosts is SNMP which should be enough to do a basic ID of the system.
But after this I found that all the RX's got set to a system type of Unknown. My understanding, unless it has changed, is that Unknown means that SIM has not identification rule for the system OID from SNMP. I chaned SNMP so all the RX's with snmpwalk using the v1 protocol and the correct community and they all reply in full as expected. I deleted all the RX's and manually discovered them but same result. The logs also says that there is no SNMP system ident rule found.
Other systems aparts from the RX's seem to get discovered OK as far as I can tell. It almost seems as if all the rules that apply to Itaniums have been removed yet even older systems like Alphas running Tru64 are OK. Does anyone have any ideas here?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-15-2011 12:59 PM
01-15-2011 12:59 PM
Re: V6.2 Unknown system for certain systems
Hi Richard,
Run the repair agent task on one of the affected RX host... this will help you diagnose the issue...
thanks,
Aftab
Run the repair agent task on one of the affected RX host... this will help you diagnose the issue...
thanks,
Aftab
I work for HPE
Looking for a quick resolution to a technical issue for your HPE products? HPE Support Center Knowledge-base – Just a Click Away!
See Self Help Post for more details
Looking for a quick resolution to a technical issue for your HPE products? HPE Support Center Knowledge-base – Just a Click Away!
See Self Help Post for more details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-16-2011 04:15 PM
01-16-2011 04:15 PM
Re: V6.2 Unknown system for certain systems
Did that made no difference. But it does say under SNMP that no System Type Manager rile for the sysOBJId was found, yet there are type rules for the rx's in the list. The OID the rule points (which is supposed to match rx...., to however does not return anything with rx in it.
It does go on to summarise that it cannot identify the system and wants to use dmidecode. To do this it would need SSH access, which is not permitted.
You can argue the point about SSH but we have had this off for quite a while and all used to work fine.
It does go on to summarise that it cannot identify the system and wants to use dmidecode. To do this it would need SSH access, which is not permitted.
You can argue the point about SSH but we have had this off for quite a while and all used to work fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-17-2011 03:10 PM
01-17-2011 03:10 PM
Re: V6.2 Unknown system for certain systems
OK I did get SSH access temporarily.
But nothing happened.
BTW, I went back to a V5.3 CMS that is still running, deleted all the Itaniums and had them rediscovered. They all came back fully identified.
It seems V6.2 specific and only related to itaniums.
But nothing happened.
BTW, I went back to a V5.3 CMS that is still running, deleted all the Itaniums and had them rediscovered. They all came back fully identified.
It seems V6.2 specific and only related to itaniums.
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP