9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi,
I have a strange issue with snmwpalk.
If I do snmpget on yyy.977.4.3.1.3.1006 I get the following successfull output :
yyy.977.4.3.1.3.1006 = INTEGER: 206
This is what I was excepting for, now I want to look for other snmp addresses Under yyy.977.4.3.1.3.xxxx.
If I do snmpwalk on... (3 Replies)
Discussion started by: FFedo
3 Replies
2. UNIX for Dummies Questions & Answers
I have a BIG problem...
I host a public (Debian) repository on Cydia (for jailbroken iphones). I use my home Mac running Ubuntu in VMWare Fusion. For the repository, I have to have 5 items in a folder to make it 'live:'
1. deb_files folder (to hold my Debian packages)
2. Packages file
3.... (0 Replies)
Discussion started by: thazsar
0 Replies
3. Shell Programming and Scripting
Can someone please explain to me how come snmpwalk doesn't always find a running process that's on a remote server?
I prefer to use snmp to monitor processes remotely because this doesn't require me to put a script on that remote box. but the problem is, there are times that my snmp command... (2 Replies)
Discussion started by: SkySmart
2 Replies
4. Solaris
Hi GUYS,
Me have 2 servers, eg:: A & B
id_dsa.pub key of B had been put in authorized_keys of A & Vice versa
Passwordless login going from A to B.
But while connecting from B to A ,its asking password
Any one please help me out.. (6 Replies)
Discussion started by: racechap
6 Replies
5. Infrastructure Monitoring
When my server is restarted, SNMP does not start automatically. It needs to be started manually everytime the server is restarted. (1 Reply)
Discussion started by: shahdeo
1 Replies
6. Infrastructure Monitoring
When I run a script that polls a router I get the following error from net-snmp. I can not seem to find a straight answer. Could my mib files be corrupt?
xxx-xxx:/etc/sma/snmp/mibs# perl /export/home/user/perl/test.pl
Unlinked OID in SNMPv2-MIB: snmp ::= { mib-2 11 }
Undefined identifier:... (2 Replies)
Discussion started by: mrlayance
2 Replies
7. Solaris
Hi,
I am trying to compile the source code for Net-SNMP-5.4.2.1 using the gcc compiler-3.4.6 and 3.4.3 but I am getting the follwoing error with perl enabled:
/bin/sh ../libtool --mode=link gcc -g -O2 -Usolaris2 -Dsolaris2=solaris2 -fno-strict-aliasing -pipe -Wdeclaration-after-statement... (2 Replies)
Discussion started by: tisha
2 Replies
8. Solaris
Hi there,
I know this is a common question, but I have not found a satsifactory solution yet, so pardon me for posting similar questions.
My problem is the log /var/adm/messages is filling up with this entry every few minutes Please refer below.
Oct 4 21:39:46 host last message repeated 3... (5 Replies)
Discussion started by: sundar63
5 Replies
9. Red Hat
I have edited the snmpd.conf file on RHEL3, I changed:
com2sec notConfigUser default public
to :
com2sec notConfigUser default new_string_name
BUT, when my security guy scans the box, is still answers to public, I restarted snmpd.
Is there more to this than just changing... (0 Replies)
Discussion started by: BG_JrAdmin
0 Replies
snmpusm(1M) System Administration Commands snmpusm(1M)
NAME
snmpusm - create and maintain SNMPv3 users on a remote entity
SYNOPSIS
snmpusm [common options] AGENT create user [clonefrom-user]
snmpusm [common options] AGENT delete user
snmpusm [common options] AGENT cloneFrom user clonefrom-user
snmpusm [common options] [-Co] [-Ca] [-Cx] AGENT passwd old-passphrase new-passphrase
DESCRIPTION
The snmpusm utility is an SNMP application that can be used to do simple maintenance on an SNMP agent's User-based Security Module (USM)
table. The user needs write access to the usmUserTable MIB table. You can create, delete, clone, and change the passphrase of users config-
ured on a running SNMP agent.
The SNMPv3 USM specifications (see RFC 3414) dictate that users are created and maintained by adding and modifying rows to the usmUserTable
MIB table. To create a new user you simply create the row using snmpset(1M). User's profiles contain private keys that are never transmit-
ted over the wire in clear text, regardless of whether the administration requests are encrypted.
The secret key for a user is initially set by cloning another user in the table, so that a new user inherits the cloned user's secret key.
A user can be cloned only once, however, after which they must be deleted and re-created to be re-cloned. The authentication and privacy
security types are also inherited during this cloning (for example, MD5 vs. SHA1). To change the secret key for a user, you must know the
user's old passphrase as well as the new one. The passwd subcommand of the snmpusm command requires both the new and the old passphrases be
supplied. After cloning from the appropriate template, you should immediately change the new user's passphrase.
The Net-SNMP agent must first be initialized so that at least one user is setup in it before you can use this command to clone new ones.
See the snmpd.conf(4) manual page for a description of the createUser configuration parameter.
Passphrases must be a minimum of eight characters in length.
OPTIONS
See snmpcmd(1M) for a description of common options.
EXAMPLES
Assume for our examples that the following VACM and USM configurations lines are in the snmpd.conf file for a Net-SNMP agent. These lines
set up a default user named initial with the authentication passphrase setup_passphrase. Establishing these parameters enables the initial
setup of an agent.
# VACM configuration entries
rwuser initial
# The name of the new user that is going to be created
rwuser wes
# USM configuration entries
createUser initial MD5 setup_passphrase DES
Note that the initial user's setup should be removed after creating a real user to whom you grant administrative privileges. The real user
is wes in this example.
Example 1: Creating a New User
The following command creates a new user, wes, which is cloned from initial. wes inherits that user's passphrase, setup_passphrase.
# snmpusm -v3 -u initial -n "" -l authNoPriv -a MD5 -A setup_passphrase
localhost create wes initial
Example 2: Changing the User's Passphrase
After creating the user wes with the same passphrase as the user initial, we need to change his passphrase for wes. The following command
changes it from setup_passphrase, which was inherited from initial, to new_passphrase.
# snmpusm -v 3 -u wes -n "" -l authNoPriv -a MD5 -A setup_passphrase
localhost passwd setup_passphrase new_passphrase
Example 3: Testing the New User
If the preceding commands were successful, the following command should perform an authenticated SNMPv3 GET request to the agent.
# snmpget -v 3 -u wes -n "" -l authNoPriv -a MD5 -A new_passphrase
localhost sysUpTime.0
Following a successful test, remove the VACM group snmpd.conf entry for the user initial. At this point, you have a valid user wes that you
can use for future transactions.
EXIT STATUS
0
Successful completion.
1
A usage syntax error. A usage message is displayed. Also used for timeout errors.
2
An error occurred while executing the command. An error message is displayed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWsmcmd |
+-----------------------------+-----------------------------+
|Interface Stability |External |
+-----------------------------+-----------------------------+
SEE ALSO
snmpcmd(1M), snmpset(1M), snmpd.conf(4), attributes(5)
RFC 3414
SunOS 5.10 20 Jan 2004 snmpusm(1M)