- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- SIM 4.2 Identification -- Netware servers
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
Discussions
Forums
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
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
тАО08-24-2005 08:27 AM
тАО08-24-2005 08:27 AM
SIM 4.2 Identification -- Netware servers
Netware 5.1 SP6
Insight Agents 7.10
They're all ML370 G3's
Only three of them don't report proper identification to SIM. What can be done to troubleshoot this? The agent settings are all the same!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2005 08:49 AM
тАО08-24-2005 08:49 AM
Re: SIM 4.2 Identification -- Netware servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2005 09:00 AM
тАО08-24-2005 09:00 AM
Re: SIM 4.2 Identification -- Netware servers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2005 09:20 AM
тАО08-24-2005 09:20 AM
Re: SIM 4.2 Identification -- Netware servers
On the HPSIM Page, go to Options -> Discovery ->Manage System Types
Click the New Tab then at with the following screen don't fill in any details just hit the Retrieve From System Tab.
Then enter the IP details of the Server you have an issue with. Change the community name if you use something other than public.
If it returns a response, then it should be able to identify the Server. If it can't the resulting message is pretty clear.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2005 09:48 AM
тАО08-24-2005 09:48 AM
Re: SIM 4.2 Identification -- Netware servers
Response SNMP data type:
OBJECTIDENTIFIER
Response value:
1.3.6.1.4.1.23.1.6
Got that response
I then tried the R/W community and that gave the same response
I then tried a "WORKING" server that didn't have this issue and received the same response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-24-2005 02:15 PM
тАО08-24-2005 02:15 PM
Re: SIM 4.2 Identification -- Netware servers
Try running the identification task individually against them.
Also maybe check nothing has been set in the system Protocols for these servers.
If you just click on the server name, is SNMP listed as one of the protocols.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-25-2005 03:10 AM
тАО08-25-2005 03:10 AM
Re: SIM 4.2 Identification -- Netware servers
Its grabbing the SNMP Description and location
, but upon identifying it manually, is not finding it.