[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On 26/12/06, mushtaq khan <[EMAIL PROTECTED]> wrote:
> Actully the problem was file snmpd.conf was not present.
If you haven't created one, then it won't exist, yes.
> After i created it
> with cmd line tool snmpconf -g basic_setup, i was able to
> communicate with agent.
> While configuring the snmpd.conf, i gave rwcommunity as **** and
> rocommunity as ****.
You should regard community strings as vaguely equivalent to passwords,
and choose something meaningful to you, but relatively difficult to guess.
Many sites use "public" for rocommunity (or possibly for a restricted view)
but it's important to use something a little less obvious for rwcommunity.
(Though if security is important, you should look at SNMPv3 instead).
> But what community i should give for trap.
Anything you like. It's just a string.
Choose something that seems sensible to you, and configure your
snmptrapd to accept this community.
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
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
