|
|
Sponsored Content
Special Forums
IP Networking
SNMP Community String ???
Post 10923 by Neo on Saturday 24th of November 2001 05:38:36 PM
11-24-2001
Administrator
If you look at network devices as clients and devices that received SNMP traps or poll devices as servers then the community string is the same as apassword that the server issues to the client device during a remote query. The string can be just about anything reasonable, as long as the client and the server use the same community strings.
Most network devices allow different levels of SNMP access, for example: READ ONLY or READ/WRITE. Each one of these levels of access would/should have a different (hard to guess) community string.
When a client sends an SNMP trap to a server receiving SNMP trap information, the SNMP community string is not required.
However, some devices use the SNMP community string as a password for terminal (serial and monitor) access to the device as well. Don't just change them and forget them
That is just about it........ the poster stated that the device was only sending traps, so the community string is not so important between client-server (no server queries to the client device) but should be changed for security reasons so something other than the default value, i.e. public.... Make sure you document the change somewhere safe so if you forget to tell the next responsible person after you leave the project, they will have a roadmap of the changes you made!
However, never fear... most SNMP community strings can be reset from the console/monitor of the device (or with physical access to the device). Yet, if you have hundreds of devices..... depending on this technique (physical access to reset) is not a good idea
Most network devices allow different levels of SNMP access, for example: READ ONLY or READ/WRITE. Each one of these levels of access would/should have a different (hard to guess) community string.
When a client sends an SNMP trap to a server receiving SNMP trap information, the SNMP community string is not required.
However, some devices use the SNMP community string as a password for terminal (serial and monitor) access to the device as well. Don't just change them and forget them
That is just about it........ the poster stated that the device was only sending traps, so the community string is not so important between client-server (no server queries to the client device) but should be changed for security reasons so something other than the default value, i.e. public.... Make sure you document the change somewhere safe so if you forget to tell the next responsible person after you leave the project, they will have a roadmap of the changes you made!
However, never fear... most SNMP community strings can be reset from the console/monitor of the device (or with physical access to the device). Yet, if you have hundreds of devices..... depending on this technique (physical access to reset) is not a good idea
|
|
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
What value is read by snmp as a public string on a Fedora workstation. (4 Replies)
Discussion started by: thumper
4 Replies
2. 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
3. IP Networking
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (0 Replies)
Discussion started by: prabakar4all
0 Replies
4. Red Hat
Hi ,
Currently DELL OMSA SNMP sends data through default udp port 161.I want my custom SNMP MIB also to send data in the same udp port 161.Whether its possible.If yes where to configure .I tried starting my custom MIB in udp port 161,but it throws port already in use.Kindly guide. (1 Reply)
Discussion started by: prabakar4all
1 Replies
5. IP Networking
I am having a problem with an SNMP event, and I am not sure where I should be looking to solve this problem.
Description:
There is an SNMP event in our system that for one reason or another is not getting sent out as an email because it is never getting to our SNMP agent.
I see where the... (0 Replies)
Discussion started by: broberts
0 Replies
6. Infrastructure Monitoring
Dear Champs,
I am new to unix, and need to configure linux server to send below traps to a SNMP server.
Monitoring TRAP Disk Space Low
Monitoring TRAP Memory Low
Monitoring TRAP CPU high
Monitoring TRAP Admin login/Logoff
Please help me how to send this information to my SNMP server... (2 Replies)
Discussion started by: stavar
2 Replies
7. UNIX for Dummies Questions & Answers
i am working with embedded system -Dell DCS management sub system. my question is as below:
currently we are using linux kernel 2.6.30 build and we have a kernel logs stored to the /var/log/messages path. now we have to transfer all this logs to the specified SNMP target as a part of SNMP... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies
LEARN ABOUT MOJAVE
cups-snmp.conf
snmp.conf(5) Apple Inc. snmp.conf(5) NAME
snmp.conf - snmp configuration file for cups DESCRIPTION
The snmp.conf file configures how the standard CUPS network backends (http, https, ipp, ipps, lpd, snmp, and socket) access printer infor- mation using SNMPv1 and is normally located in the /etc/cups directory. Each line in the file can be a configuration directive, a blank line, or a comment. Comment lines start with the # character. The Community and DebugLevel directives are used by all backends. The remainder apply only to the SNMP backend - cups-snmp(8). DIRECTIVES
The following directives are understood by the CUPS network backends: Address @IF(name) Address @LOCAL Address address Sends SNMP broadcast queries (for discovery) to the specified address(es). There is no default for the broadcast address. Community name Specifies the community name to use. Only a single community name may be specified. The default community name is "public". DebugLevel number Specifies the logging level from 0 (none) to 3 (everything). Typically only used for debugging (thus the name). The default debug level is 0. DeviceURI "regular expression" device-uri [... device-uri] Specifies one or more device URIs that should be used for a given make and model string. The regular expression is used to match the detected make and model, and the device URI strings must be of the form "scheme://%s[:port]/[path]", where "%s" represents the detected address or hostname. There are no default device URI matching rules. HostNameLookups on HostNameLookups off Specifies whether the addresses of printers should be converted to hostnames or left as numeric IP addresses. The default is "off". MaxRunTime seconds Specifies the maximum number of seconds that the SNMP backend will scan the network for printers. The default is 120 seconds (2 min- utes). SEE ALSO
cups-snmp(8), CUPS Online Help (http://localhost:631/help) COPYRIGHT
Copyright (C) 2007-2017 by Apple Inc. 10 June 2014 CUPS snmp.conf(5)