Hi,
it is no problem with TCP. Thanks for help!
2009/2/10 Mike Ayers
> > From: Alexander Bubnov [mailto:alexander.bub...@gmail.com]
> > Sent: Monday, February 09, 2009 2:36 AM
>
> > Thanks for replay. For my machine firewall is not installed.
>
> That was my bad anyway - I did not read
I've ran into curious obstacle.
I put the code of standard agentx sample into the run() function of my
class that derives from Thread - which I generally used in couple
other applications, reasonably simple class.
If I have the agentx to run in the background my thread class ends up
blocking my ma
Paul Hogan wrote:
> I did a search in the config.log and I didn't find a match to the issue you
> are stating. Sounds like the interfaces may not be typically supported
> though?
If you're running a 64-bit AIX kernel, interface information currently
isn't supported by net-snmp. As Dave said: pa
> On Tue, 10 Feb 2009 16:59:58 +, Dave Shield
> said:
DS> The easiest approach would probably be for the dynamic
DS> entries to be written to the persistent config file (/var/net-snmp),
DS> the whole internal config cleared, and then all the config files
DS> (including /var/net-snmp/
> From: Alexander Bubnov [mailto:alexander.bub...@gmail.com]
> Sent: Monday, February 09, 2009 2:36 AM
> Thanks for replay. For my machine firewall is not installed.
That was my bad anyway - I did not read carefully enough and thought
your problems were accessing the master agent instea
> From: Péricles Oliveira [mailto:pericles_silva_olive...@hotmail.com]
> Sent: Tuesday, February 10, 2009 2:01 AM
> Please, what you suggest to solve it?
Download net-snmp v5.4.2.1 and try building that. Over three years of
improvements is a lot!
HTH,
Mike
P.S. No crosspos
2009/2/10 Tushar Gohad :
> So is it reasonable to clear out all the 'monitor' entries
> on SIGHUP?
Well, have a think about what things are going to look
to the network administrator - simply using this without
necessarily knowing what the code actually does.
By the principle of least astonishme
Wes Hardaker wrote:
>> On Fri, 06 Feb 2009 09:58:00 -0700, Tushar Gohad
>> said:
>
> TG> My question is: were the 'release' routines left out intentionally,
> TG> say to avoid cleaning out someone else's (subagent, command line
> TG> trap addition etc) monitor entries? Or is there a safe
I did a search in the config.log and I didn't find a match to the issue you are
stating. Sounds like the interfaces may not be typically supported though?
Paul R. Hogan
Computer System Engineer
Enterprise Information Technology
HAWORTH, INC.
One Haworth Center
Holland, MI 49423
direct 616.393
2009/2/10 Paul Hogan :
> I have compiled and installed net-snmp 5.4.2.1 on AIX 5.3.6 version. I
> can pull everything in great to our Orion monitoring tool except for the
> NIC information. Is there a known issue with this or is there something
> I can do to enable this monitoring?
Have a look
> On Tue, 10 Feb 2009 20:41:44 +0530, "Ragesh V" said:
RV> The OID "X.X.X.X.X.X.30.1.1" cannot be the lexicographic successor for
RV> the "X.X.X.X.X.X.29.1.1". Is our understanding correct or not??
No, actually it can be. It may not be beneath the .29 branch in the
tree, but the next lexico
I have compiled and installed net-snmp 5.4.2.1 on AIX 5.3.6 version. I
can pull everything in great to our Orion monitoring tool except for the
NIC information. Is there a known issue with this or is there something
I can do to enable this monitoring?
2009/2/10 Ragesh V :
> Following are our MIB table entries.
>
> X.X.X.X.X.X.22.1.1
> X.X.X.X.X.X.22.1.1.1
> X.X.X.X.X.X.22.1.1.1000
> X.X.X.X.X.X.22.1.1.1001
I presume you've got a MIB structure of the form:
myTable ::= ... { X X ... 22 }
myEntry ::= ... { X X ... 22 1 }
myCol1 ::=
Hi All,
Can any body help me in the below confusion??
Following are our MIB table entries.
X.X.X.X.X.X.22.1.1
X.X.X.X.X.X.22.1.1.1
X.X.X.X.X.X.22.1.1.1000
X.X.X.X.X.X.22.1.1.1001
X.X.X.X.X.X.30.1.1
X.X.X.X.X.X.30.1.1.1
In the above table our unders
Hi All,
Can any body help me in the below confusion??
I have below given OIDs registered to snmpd.
X.X.X.X. 22.1.1
X.X.X.X. 22.1.1
X.X.X.X. 22.1.1
X.X.X.X. 22.1.1
DISCLAIMER:
--
> On Tue, 3 Feb 2009 14:47:09 +, Alexander Bubnov
> said:
AB> 2. subagent sends a trap through, for example, send_v2trap function <-- how
AB> can I know here that trap is not sent and a manager cannot receive
AB> it?
AB> 3. the connection is up <-- How to know connection is up in o
> On Wed, 04 Feb 2009 12:18:13 +0900, Hiroshi Inoue
> said:
HI> (1) Is it possible to forward the trap(SNMPv3) using the "Forward"
HI> definition?
I don't think so no... The current forward line doesn't accept SNMPv3
parameters to set. It's possibly it'll forward it completely (I
> On Fri, 6 Feb 2009 15:42:42 +0530, "Renju Mathew"
> said:
It looks like you're missing libraries in the compile line...
RM> gcc -o example-demon example-demon.o nstAgentSubagentObject.o
RM> `net-snmp-config --agent-libs`
What's the output of `net-snmp-config --agent-libs` ?
RM> /usr
> On Thu, 5 Feb 2009 21:29:11 +0800, "XIANG Lei"
> said:
XL> And I check the /var/net-snmp/snmpd.conf, the engineBoots in this
XL> file remained 1, never changed.
I'd assume it's because the snmpd.conf file is owned by one user and the
agent is running as another user (not root!) that d
> On Fri, 06 Feb 2009 09:58:00 -0700, Tushar Gohad said:
TG> My question is: were the 'release' routines left out intentionally,
TG> say to avoid cleaning out someone else's (subagent, command line
TG> trap addition etc) monitor entries? Or is there a safe way to clean
TG> the entries out?
> On Mon, 9 Feb 2009 18:04:50 +0700, michael kapelko
> said:
mk> $vb = new SNMP::Varbind([$oidVLANStaticUntaggedPorts, $vlanID, $hs,
mk> 'OCTETSTR']);
I actually thought that the SNMP module code would support a '0x' string
itself, but I may be wrong about that.
I don't think the Math:
2009/2/10 M. Zeeshan - IMS :
> By reading section 6 of the file 'AGENT.txt' i am still unable to make neat
> sense and difference between RESERVE, RESERVE2 and ACTION
In very general terms:
RESERVE1:Is this individual assignment OK?
(type, value, etc)
RESERVE2:Is t
Dear Dave,
Thanx for such precious time for guiding.
i have really came across each direction you pointed and was able to understand
things much neatly than before i do.
just could not cleanly get one point of about "Handling SET requests"
as scenario follows:
that's my scenario:
server1 (there are ipv4 and ipv6 running):
[r...@server1]# netstat -an
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp0 0 0.0.0.0:714 0.0.0.0:*
i tested it, but not working properly. the snmpwalk don't get tcp ipv6 ports.
> Date: Mon, 9 Feb 2009 12:23:08 +
> Subject: Re: snmpwalk don't show all open ports ipv6
> From: d.t.shi...@liverpool.ac.uk
> To: pericles_silva_olive...@hotmail.com
> CC: net-snmp-cod...@lists.sourceforge.net;
>
2009/2/9 Rodolfo Leffa :
> .. I'm only implementing the GET
> operation. Now I'm doubt if I should implement GETNEXT, or it's okay to have
> an agent that don't reponse to this kind of requisition.
No - your agent *MUST* handle both GET and GETNEXT requests.
See RFC1905, section 4.2.More
26 matches
Mail list logo
