Re: problem in SNMPSET on table with string data type columns

Hi Bill,
Could you please provide a sample outline or example of how to create, register and use a serialize handler?Here do we need to use the function "netsnmp_register_instance" for each of the column in the table to have separate handler for each column to be called for each of them separately, rather than a single handler function being called passing all the varbinds in input SNMPGET/SET query?
thanks and regardsS Sarath 

     On Thursday, September 4, 2014 5:51 PM, Bill Fenner <[email protected]> wrote:
   

 The only advice I have is to try the serialize handler.
  Bill


On Thu, Sep 4, 2014 at 3:33 AM, sarath azad <[email protected]> wrote:

Hi Bill, Thanks for the reply.Here for registration of the table we are using belowfunctions:netsnmp_create_handler_registration                netsnmp_create_table_data                netsnmp_table_helper_add_indexes                netsnmp_register_table The problem we are facing is that if our table is columns,c1, c2, and c3, and if c1 is of string data type. Now if we are doing “snmpset c1 <val1>  c2 <val2>  c3 <val3>” we are getting these valuesval1, val2 and val3 properly in code and they are getting properly updated inthe table.But if we are giving columns in different order like “snmpsetc3 <val3> c1 <val1> c2 <val2>” now we are not getting the<val1> value of string column c1 , what we gave in the SNMPSET. For integer columns we are getting proper valuesirrespective of their order in SNMPSET command. But if we are not giving thestring column in proper order in SNMPSET we are not getting its value. Only gettingsome garbage value (integer value of pervious column value in snmpset). Could you please advise what could be the issue here? Thanks and regardsS  Sarath   



     On Wednesday, September 3, 2014 7:38 PM, Bill Fenner <[email protected]> wrote:
   

 I've had trouble with multiple requests in ordered table_iterator tables.  I have no idea if that's what you're using, since you didn't give much info about your use case.  I just worked around it by injecting the serialize handler:
    int result = netsnmp_register_table_iterator( reg, iinfo );    assert( result == MIB_REGISTERED_OK );    int injected = netsnmp_inject_handler( reg, netsnmp_get_serialize_handler() );    assert( injected == SNMPERR_SUCCESS );
  Bill

On Wed, Sep 3, 2014 at 3:19 AM, sarath azad <[email protected]> wrote:

Hello,
Could you please help in solving the below problem, in doing SNMPSET for tables with string data?
thanks and regardsS Sarath  

     On Friday, August 22, 2014 9:03 PM, sarath azad <[email protected]> wrote:
   

 Hello,  Could you please help in resolving the below issue? For SNMPSET on a table which contains a column of"string" data type, if we are giving values of all the columns in thesingle SNMPSET query, then we are getting the values of the string column properly,only if the order of column values, in the query is same as the order of columnin the table.  ie. snmpset -v 2c -c public <system-IP> <column1> <column 1 value> <column 2> <column 2 value> ...  If we are giving the values in the query in different order, thenfor integer columns we are getting values properly as given in the query. Butfor the string columns we are only getting some junk characters or value in theprevious column in the query.  The table handler function is written as below:  Int tableHandlerFunction(netsnmp_mib_handler         *handler,  netsnmp_handler_registration   *reginfo,                               netsnmp_agent_request_info     *reqinfo, netsnmp_request_info           *requests)  { netsnmp_request_info*request; netsnmp_table_request_info*table_info; char data[100]; for(request = requests; request; request = request->next)   {          table_info =netsnmp_extract_table_info(request);          switch (reqinfo->mode)            {               case MODE_SET_ACTION:                    switch (table_info->colnum)                     {                                case COLUMN_STRING_COLUMN:                                    strcpy( data , requests->requestvb->val.string));                                    break;   thanks and regards S Sarath
------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users


    
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk

_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders