Hi Jeff, The solution was "\xHH\xMM"
Thanks for all your suggestions. It got me going. Regards, Bobby -----Original Message----- From: Jeff 'japhy' Pinyan [mailto:[EMAIL PROTECTED] Sent: Wednesday, 5 October 2005 21:21 To: Bobby Jafari Cc: beginners@perl.org Subject: Re: Problems with set-request NET::SNMP - retransmited On Oct 5, Bobby Jafari said: > 1 $result = $session->set_request ( > 2 -varbindlist => [ "${secPvcBulkModeOid}.${nextVcatIndex}" , > INTEGER, "1", [...] > 9# "${secPvcUpdateTimeOid}.${nextVcatIndex}" , > OCTET_STRING, '# 0x0C 0x01' > 10# "${secPvcUpdateTimeOid}.${nextVcatIndex}" , > OCTET_STRING, "$keyUpdateTime" > 11 "${secPvcRowStatusOid}.${nextVcatIndex}" , > INTEGER, "4" ] ); > > The line with OCTET_STRING as the data type, is giving me grief. > According to the MIB definition, it should be in the form of # 0xHH > 0xMM Where HH and MM are hour and minutes in Hex format. My guess is > that the set-request is expecting a string but somehow PERL is passing > it as ASCI characters or ... Try sending it as "# 10 1" and see if it works. The Net::SNMP docs only show ONE example of using OCTET_STRING, and I'm not really sure what its rules about using "0x.." are. If that fails, try "# \x0c \x01", which is using actual hexadecimal escape sequences to produce character 10 and character 1. -- Jeff "japhy" Pinyan % How can we ever be the sold short or RPI Acacia Brother #734 % the cheated, we who for every service http://www.perlmonks.org/ % have long ago been overpaid? http://princeton.pm.org/ % -- Meister Eckhart -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
