RE: How to delete/add line from raw table?

"Naama Bar Menachem" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
- I am using snmpB browser, and I tried both "walk" command on the tree
as well as "get> select instance" and "set> select instance" commands in
which I select an instance from a list (that was presented properly)
All these commands are resulted in timeout error.
- conf file is attached.


-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of
Dave Shield
Sent: Thursday, July 26, 2012 2:47 PM
To: Naama Bar Menachem
Cc: [email protected]
Subject: Re: How to delete/add line from raw table?

On 26 July 2012 11:23, Naama Bar Menachem
<[email protected]> wrote:
> I've added the import statement, and recompiled.
> And still, on RowStatus set - I get a timeout error.

Obvious questions first:

   -  what is the exact SET request that you are using?
   -  what are the access control settings in the snmpd.conf file?

Dave

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
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
snmpd.conf (application/octet-stream, 4.6 KB)
###########################################################################
#
# snmpd.conf
#
#   - created by the snmpconf configuration program
#
###########################################################################
# SECTION: Agent Operating Mode
#
#   This section defines how the agent will operate when it
#   is running.

# master: Should the agent operate as a master agent or not.
#   Currently, the only supported master agent type for this token
#   is "agentx".
#   
#   arguments: (on|yes|agentx|all|off|no)

#master  agentx

# agentuser: The system user that the agent runs as.
#   arguments: name|#uid

agentuser  root

# agentgroup: The system group that the agent runs as.
#   arguments: group|#GID

agentgroup  root

# agentaddress: The IP address and port number that the agent will listen on.
#   By default the agent listens to any and all traffic from any
#   interface on the default SNMP port (161).  This allows you to
#   specify which address, interface, transport type and port(s) that you
#   want the agent to listen on.  Multiple definitions of this token
#   are concatenated together (using ':'s).
#   arguments: [transport:]port[@interface/address],...

agentaddress  udp:161

# 	SNMPv3 Configuration
# 	SNMPv3 requires an SNMP agent to define a unique "engine ID" in order to respond to SNMPv3 requests
# 	This ID will normally be determined automatically, using two reasonably non-predictable values - a
# 	(pseudo-)random number and the current time in seconds. 
# 	We will use this recommended approach and will NOT define it.



###########################################################################
# SECTION: Access Control Setup
#
#   This section defines who is allowed to talk to your running
#   snmp agent.

#
#	SNMPv1/SNMPv2 configuration
#

#   SNMPv1/SNMPv2c read-only access community name
rocommunity public 0.0.0.0

#   SNMPv1/SNMPv2c read-write access community name
rwcommunity private 0.0.0.0

#
#	VACM configuration for v2 communities
#	&
#	SNMPv3 configuration
#

#   create users and password 
# 	   in persist configuration file so it will be encrypted

#   map an SNMPv1 or SNMPv2c community string to a security name
#         sec.name     source        community
com2sec   publicSec    default       public
com2sec   privateSec    default       private


#	maps a security name (in the specified security model) into a named group
#      group.name    sec.model  sec.name
group  publicGroup    v1         publicSec
group  publicGroup    v2c        publicSec
group  privateGroup   v1         privateSec
group  privateGroup   v2c        privateSec
group  adminGroup     usm        admin
group  operatorGroup  usm        oper
group  userGroup      usm        user

#	defines a named "view" - a subset of the overall OID tree. 
#      name           incl/excl   subtree     [mask]
view   adminView      included    .1
view   operatorView   excluded    .1.3.6.1.6.3.15.1.2
view   userView  	  excluded    .1.3.6.1.6.3.15.1.2


#	maps from a group of users/communities  to one of three views, depending on the request being processed
#      group.name      context sec.model sec.level match  read           write          notif
access publicGroup     ""      any       noauth    exact  userView       none           none
access privateGroup    ""      any       noauth    exact  debugView      debugView      none
access adminGroup      ""      usm       priv      exact  adminView      adminView      adminView
access operatorGroup   ""      usm       priv      exact  operatorView   operatorView   operatorView
access userGroup       ""      usm       priv      exact  userView       none           none



###########################################################################
# SECTION: Extending the Agent
#
# You can extend the snmp agent to have it return information
# that you yourself define.

# dlmod: dynamically extend the agent using a shared-object
# arguments: module-name module-path
dlmod ns_mibs /data/net/naamab/dev_table_2/modem/snmp/snmp_so/ns_mibs.so


###########################################################################
# SECTION: Trap Destinations
#

# HOST1 TRAP DEFINITION
# Location for trapsink definition - DO NOT REMOVE THIS LINE

# HOST2 TRAP DEFINITION
# Location for trapsink definition - DO NOT REMOVE THIS LINE

# authtrapenable: Should we send traps when authentication failures occur
# arguments: 1 | 2 (1 = yes, 2 = no)
authtrapenable 1

# linkUpDownNotifications: Should we monitor and send traps when links are up/down
# traps are sent from nsmd upon link up/down events
linkUpDownNotifications no  

###########################################################################
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.