headers
Kirk Augustin | 2 Dec 2010 20:22
Picon
Favicon

Re: SNMP Adapter for OpenPegasus

I guess it depends upon which direction one is going and what is available.

I think of CIM as the newer, easier, and more flexible way to manage remote resources, and SNMP as the older, more limited, but already existing means of remote resource management.
So I would assume the existing SNMP device access would be wrapped inside a CIM provider, that was device dependent.
Then generic CIM clients would then access this provider in standard ways.

If you have an SNMP client, then it would seem you would just use the existing SNMP device access.
It would not seem logical to try to use the older SNMP client to acce ss newer CIM providers.
SNMP can't support all that CIM can provide, so I don't see how or why one would want SNMP as the client/manager, over CIM device providers.
It would eliminate too much.
But I can see that allowing SNMP client/managers CIM access would be best done at the Pegasus level, if at all.

The opposite makes more sense to me, where the CIM client accesses SNMP devices through a CIM provider wrapper.
CIM can easily carry all that SNMP can provide.
But it would not be a generic solution.
Each CIM provider wrapper for a SNMP device would be specifically device dependent, and not effect Pegasus.
 
Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR 97231


From: "souvik.roy <at> wipro.com" <souvik.roy <at> wipro.com>
To: kirk_augustin <at> yahoo.com; pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 10:25:50 PM
Subject: RE: SNMP Adapter for OpenPegasus

DIV { MARGIN:0px;}
If anybody already have a SNMP Manager and Pegasus supports this kind of adapter, with minimal effort, device management can be supported through SNMP. Otherwise SNMP manager need to have an adapter which will be a CIM Client. In this case, don't you think  first option will give reusability and interoperability. 
 
Souvik

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:45 AM
To: Souvik Roy (WT01 - Semi Conductor and Peripheral IPG); pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus

Do you really need any sort of converter, when all you are doing is getting and setting properties?
How is SNMP get and set any different than the way CIM has always gotten and set properties?
Events are different because there is more functionality involved.
But get and set seem to simple to me.
 
Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR 97231


From: "souvik.roy <at> wipro.com" <souvik.roy <at> wipro.com>
To: pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 9:52:42 PM
Subject: SNMP Adapter for OpenPegasus

Hi,
   SNMP Indication Handler is supported in Pegasus for quite a long time. Does Pegasus also support some kind of SNMP adapter which will support SNMP get and set operations, which will take SNMP requests and converts it to CIM calls and vice-versa?
 
 

Thanks and regards,

Souvik Roy

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Permalink | Reply |
headers
Steve Peters | 2 Dec 2010 20:30

RE: SNMP Adapter for OpenPegasus

Kirk,

 

            The issue is creating management software for a new device. For a new device you want a new full featured CIM provider.

Now you are left with the requirement to support old SNMP based clients. Pegasus helps with the SNMP trap support. The job

would be complete with a generic SNMP get/set adapter that mapped CIM (provider) properties to SNMP.

 

                        Steve Peters

 

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:22 AM
To: souvik.roy <at> wipro.com; pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus

 

I guess it depends upon which direction one is going and what is available.

I think of CIM as the newer, easier, and more flexible way to manage remote resources, and SNMP as the older, more limited, but already existing means of remote resource management.
So I would assume the existing SNMP device access would be wrapped inside a CIM provider, that was device dependent.
Then generic CIM clients would then access this provider in standard ways.

If you have an SNMP client, then it would seem you would just use the existing SNMP device access.
It would not seem logical to try to use the older SNMP client to access newer CIM providers.
SNMP can't support all that CIM can provide, so I don't see how or why one would want SNMP as the client/manager, over CIM device providers.
It would eliminate too much.
But I can see that allowing SNMP client/managers CIM access would be best done at the Pegasus level, if at all.

The opposite makes more sense to me, where the CIM client accesses SNMP devices through a CIM provider wrapper.
CIM can easily carry all that SNMP can provide.
But it would not be a generic solution.
Each CIM provider wrapper for a SNMP device would be specifically device dependent, and not effect Pegasus.

 

Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR97231

 

 

From: "souvik.roy <at> wipro.com" <souvik.roy <at> wipro.com>
To: kirk_augustin <at> yahoo.com; pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 10:25:50 PM
Subject: RE: SNMP Adapter for OpenPegasus

If anybody already have a SNMP Manager and Pegasus supports this kind of adapter, with minimal effort, device management can be supported through SNMP. Otherwise SNMP manager need to have an adapter which will be a CIM Client. In this case, don't you think  first option will give reusability and interoperability. 

 

Souvik

 

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:45 AM
To: Souvik Roy (WT01 - Semi Conductor and Peripheral IPG); pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus

Do you really need any sort of converter, when all you are doing is getting and setting properties?
How is SNMP get and set any different than the way CIM has always gotten and set properties?
Events are different because there is more functionality involved.
But get and set seem to simple to me.

 

Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR97231

 

 

From: "souvik.roy <at> wipro.com" <souvik.roy <at> wipro.com>
To: pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 9:52:42 PM
Subject: SNMP Adapter for OpenPegasus

Hi,

   SNMP Indication Handler is supported in Pegasus for quite a long time. Does Pegasus also support some kind of SNMP adapter which will support SNMP get and set operations, which will take SNMP requests and converts it to CIM calls and vice-versa?

 

 

Thanks and regards,

Souvik Roy

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Permalink | Reply |
headers
Kirk Augustin | 2 Dec 2010 21:28
Picon
Favicon

Re: SNMP Adapter for OpenPegasus

I agree that a generic SNMP client interface could be fairly easily built into Pegasus.
But the http client interface to Pegaus is so much easier and richer then SNMP, it is not clear it is a such good idea.
Things like security, method calls, parameters, etc., would all be lost.
I fear it would only delay the transition away from SNMP even longer.

 
Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR 97231


From: Steve Peters <Steve_Peters <at> pmc-sierra.com>
To: Kirk Augustin <kirk_augustin <at> yahoo.com>; souvik.roy <at> wipro.com; pegasus-l <at> openpegasus.org
Sent: Thu, December 2, 2010 11:30:19 AM
Subject: RE: SNMP Adapter for OpenPegasus

Kirk,

 

            The issue is creating management software for a new device. For a new device you want a new full featured CIM provider.

Now you are left with the requirement to support old SNMP based clients. Pegasus helps with the SNMP trap support. The job

would be complete with a generic SNMP get/set adapter that mapped CIM (provider) properties to SNMP.

 

                        Steve Peters

 

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:22 AM
To: souvik.roy <at> wipro.com ; pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus

 

I guess it depends upon which direction one is going and what is available.

I think of CIM as the newer, easier, and more flexible way to manage remote resources, and SNMP as the older, more limited, but already existing means of remote resource management.
So I would assume the existing SNMP device access would be wrapped inside a CIM provider, that was device dependent.
Then generic CIM clients would then access this provider in standard ways.

If you have an SNMP client, then it would seem you would just use the existing SNMP device access.
It would not seem logical to try to use the older SNMP client to access newer CIM providers.
SNMP can't support all that CIM can provide, so I don't see how or why one would want SNMP as the client/manager, over CIM device providers.
It would eliminate too much.
But I can see that allowing SNMP client/managers CIM access would be best done at the Pegasus level, if at all.

The opposite makes more sense to me, where the CIM client accesses SNMP devices through a CIM provider wrapper.
CIM can easily carry all that SNMP can provide.
But it would not be a generic solution.
Each CIM provider wrapper for a SNMP device would be specifically device dependent, and not effect Pegasus.

 

Kirk & Trish Augustin
11821 NW McNamee Rd
Portland , OR 97231

 

 

From: " souvik.roy <at> wipro.com " < souvik.roy <at> wipro.com >
To: kirk_augustin <at> yahoo.com; pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 10:25:50 PM
Subject: RE: SNMP Adapter for OpenPegasus

If anybody already have a SNMP Manager and Pegasus supports this kind of adapter, with minimal effort, device management can be supported through SNMP. Otherwise SNMP manager need to have an adapter which will be a CIM Client. In this case, don't you think  first option will give reusability and interoperability. 

 

Souvik

 

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:45 AM
To: Souvik Roy (WT01 - Semi Conductor and Peripheral IPG); pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus

Do you really need any sort of converter, when all you are doing is getting and setting properties?
How is SNMP get and set any different than the way CIM has always gotten and set properties?
Events are different because there is more functionality involved.
But get and set seem to simple to me.

 

Kirk & Trish Augustin
11821 NW McNamee Rd
Portland , OR 97231

 

 

From: " souvik.roy <at> wipro.com " < souvik.roy <at> wipro.com >
To: pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 9:52:42 PM
Subject: SNMP Adapter for OpenPegasus

Hi,

   SNMP Indication Handler is supported in Pegasus for quite a long time. Does Pegasus also support some kind of SNMP adapter which will support SNMP get and set operations, which will take SNMP requests and converts it to CIM calls and vice-versa?

 

 

Thanks and regards,

Souvik Roy

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

Permalink | Reply |
headers
Yoder, Alan | 2 Dec 2010 21:42
Picon

Re: SNMP Adapter for OpenPegasus

What happened to "embrace and extend"?  ;-)


On 12/2/10 12:28 PM, "Kirk Augustin" <kirk_augustin <at> yahoo.com> wrote:

I agree that a generic SNMP client interface could be fairly easily built into Pegasus.
But the http client interface to Pegaus is so much easier and richer then SNMP, it is not clear it is a such good idea.
Things like security, method calls, parameters, etc., would all be lost.
I fear it would only delay the transition away from SNMP even longer.

 
Kirk & Trish Augustin
11821 NW McNamee Rd
Portland, OR 97231


From: Steve Peters <Steve_Peters <at> pmc-sierra.com>
To: Kirk Augustin <kirk_augustin <at> yahoo.com>; souvik.roy <at> wipro.com; pegasus-l <at> openpegasus.org
Sent: Thu, December 2, 2010 11:30:19 AM
Subject: RE: SNMP Adapter for OpenPegasus

         
Kirk,
 
           The issue is creating management software for a new device. For a new device you want a new full featured CIM provider.
Now you are left with the requirement to support old SNMP based clients. Pegasus helps with the SNMP trap support. The job
would be complete with a generic SNMP get/set adapter that mapped CIM (provider) properties to SNMP.
 
                       Steve Peters
 

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:22 AM
To: souvik.roy <at> wipro.com ; pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus
  
 
I guess it depends upon which direction one is going and what is available.

I think of CIM as the newer, easier, and more flexible way to manage remote resources, and SNMP as the older, more limited, but already existing means of remote resource management.
So I would assume the existing SNMP device access would be wrapped inside a CIM provider, that was device dependent.
Then generic CIM clients would then access this provider in standard ways.

If you have an SNMP client, then it would seem you would just use the existing SNMP device access.
It would not seem logical to try to use the older SNMP client to access newer CIM providers.
SNMP can't support all that CIM can provide, so I don't see how or why one would want SNMP as the client/manager, over CIM device providers.
It would eliminate too much.
But I can see that allowing SNMP client/managers CIM access would be best done at the Pegasus level, if at all.

The opposite makes more sense to me, where the CIM client accesses SNMP devices through a CIM provider wrapper.
CIM can easily carry all that SNMP can provide.
But it would not be a generic solution.
Each CIM provider wrapper for a SNMP device would be specifically device dependent, and not effect Pegasus.
 
 
 
Kirk & Trish Augustin
 11821 NW McNamee Rd
 Portland , OR  97231
 
  
 
  
 

From: " souvik.roy <at> wipro.com " < souvik.roy <at> wipro.com >
To: kirk_augustin <at> yahoo.com; pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 10:25:50 PM
Subject: RE: SNMP Adapter for OpenPegasus
If anybody already have a SNMP Manager and Pegasus supports this kind of adapter, with minimal effort, device management can be supported through SNMP. Otherwise SNMP manager need to have an adapter which will be a CIM Client. In this case, don't you think  first option will give reusability and interoperability.

 
 
Souvik
  
 

From: Kirk Augustin [mailto:kirk_augustin <at> yahoo.com]
Sent: Thursday, December 02, 2010 11:45 AM
To: Souvik Roy (WT01 - Semi Conductor and Peripheral IPG); pegasus-l <at> openpegasus.org
Subject: Re: SNMP Adapter for OpenPegasus
Do you really need any sort of converter, when all you are doing is getting and setting properties?
How is SNMP get and set any different than the way CIM has always gotten and set properties?
Events are different because there is more functionality involved.
But get and set seem to simple to me.
 
 
 
Kirk & Trish Augustin
 11821 NW McNamee Rd
 Portland , OR  97231
 
  
 
  
 

From: " souvik.roy <at> wipro.com " < souvik.roy <at> wipro.com >
To: pegasus-l <at> openpegasus.org
Sent: Wed, December 1, 2010 9:52:42 PM
Subject: SNMP Adapter for OpenPegasus
Hi,
  SNMP Indication Handler is supported in Pegasus for quite a long time. Does Pegasus also support some kind of SNMP adapter which will support SNMP get and set operations, which will take SNMP requests and converts it to CIM calls and vice-versa?
 
 
 
 
 
Thanks and regards,

Souvik Roy
Please do not print this email unless it is absolutely necessary.


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 

www.wipro.com <http://www.wipro.com>  
 
Please do not print this email unless it is absolutely necessary.


The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
 

www.wipro.com <http://www.wipro.com>  
 

Permalink | Reply |

Gmane