- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Netapp Filers and SIM
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
Forums
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
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
03-21-2005 02:53 AM
03-21-2005 02:53 AM
Netapp Filers and SIM
This is what I've done so far:
-I created a new system type. I set it up to pull the System object identifier from one of the Netapp filers. It did retrieve the identifier. I then tried either match or "starts with" options. I left the other portions blank. At the bottom I associated it with "Storage Device" system type and gave it a name of Netapp.
-I manually discovered one of the filers.
-It was discovered as unknown.
-I did a device identification - still unknown.
-I waited the weekend to let the automatic processes run - still unknown.
Thanks for the help,
Tim
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2007 09:21 PM
01-03-2007 09:21 PM
Re: Netapp Filers and SIM
i have quite the same problem...
Have you found a solution for this one...
Thanks in advance
Flo
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-03-2007 09:34 PM
01-03-2007 09:34 PM
Re: Netapp Filers and SIM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2007 03:50 AM
01-04-2007 03:50 AM
Re: Netapp Filers and SIM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2007 07:39 AM
01-04-2007 07:39 AM
Re: Netapp Filers and SIM
i might give it a whirl tomorrow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2007 06:39 PM
01-07-2007 06:39 PM
Re: Netapp Filers and SIM
We are having 3 types of NetApp filers that are perfectly identified (F810/820 and FAS270). Make sure the NetApp mib is imported into SIM and choose OID 1.3.6.1.1.4.1.789.2.1 or 1.3.6.1.4.1.789.2.3 for identifying the system type.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2007 01:55 AM
01-10-2007 01:55 AM
Re: Netapp Filers and SIM
thanks for the hints sofar.
But still one question how can I identify a system with a specific OID?
We have two clusterd F920 Heads and when I do a snmp walk with specific OID´s the heads are respondig.
So the question is how can I choose OID by the idenfication or discorvery in the SIM??
Thanks in advance
Hello.
We are having 3 types of NetApp filers that are perfectly identified (F810/820 and FAS270). Make sure the NetApp mib is imported into SIM and choose OID 1.3.6.1.1.4.1.789.2.1 or 1.3.6.1.4.1.789.2.3 for identifying the system type.