Sponsored Content
Full Discussion: changing snmp strings
Operating Systems Linux Red Hat changing snmp strings Post 302076381 by BG_JrAdmin on Monday 12th of June 2006 06:13:38 PM
Old 06-12-2006
changing snmp strings

If I change my SNMP strings from the default PUBLIC to something else.
Does this take effect right away or do i have to restart snmpd or HUP it or...something...?

this is RHEL 3 AS

Last edited by BG_JrAdmin; 06-12-2006 at 07:14 PM.. Reason: more info
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Changing SNMP port number

hi, i am using Sun Solaris 8 (Sparc). Currently there is a SNMP agent running on port 161. How should I change it to port 8001? which file to modify and restart is necessary? pls teach me the information. thanks (8 Replies)
Discussion started by: champion
8 Replies

2. Red Hat

RHEL 3 - how to change the SNMP community strings?

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. Solaris

Creating SNMP Strings To Trap ALOM Console Messages

Greetings To All! I am trying to accomplish the following: Using a public SNMP string, create a trap which will trap ALOM console messages on a Solaris Sunfire T-1000 ALOM console. The platform is Solaris 10. These newly created traps need to be configured in such a way that they will send... (0 Replies)
Discussion started by: RobSand
0 Replies

4. IP Networking

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

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

5. Red Hat

Sending data from DELL OMSA SNMP and Custom SNMP MIB to same UDP port 161

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

6. Shell Programming and Scripting

Delete lines in file containing duplicate strings, keeping longer strings

The question is not as simple as the title... I have a file, it looks like this <string name="string1">RZ-LED</string> <string name="string2">2.0</string> <string name="string2">Version 2.0</string> <string name="string3">BP</string> I would like to check for duplicate entries of... (11 Replies)
Discussion started by: raidzero
11 Replies

7. IP Networking

SNMP Problem - SNMP not getting to the agent.

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

8. Infrastructure Monitoring

SNMP traps to SNMP server

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

9. UNIX for Dummies Questions & Answers

Need to transfer all kernel logs (var/log/messages) to the snmp listener as snmp trap

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
SNMP-BRIDGE-MIB(1)						     Net-SNMP							SNMP-BRIDGE-MIB(1)

NAME
snmp-bridge-mib - provide Linux bridge information via SNMP SYNOPSIS
snmp-bridge-mib {bridge} ARGUMENTS
The following arguments are required: bridge The name of the Linux bridge for which you want to provide information via SNMP, e.g. br0. DESCRIPTION
The snmp-bridge-mib is an extension to net-snmp. It collects information about a bridge in a Linux system and exports them for query from other (remote) systems for management purposes. CONFIGURATION
: The preferred method of snmp-bridge-mib to attach to net-snmp is agentx. For this to work, you will have to add the following line to /etc/snmp/snmpd.conf, master agentx restart snmpd and start snmp-bridge-mib. snmp-bridge-mib will then connect to the running snmpd daemon. Another way of attaching snmp-bridge-mib to is to run it as an embedded perl module. You have to add perl do "path to location of snmp-bridge-mib" and restart snmpd. EXAMPLE
: Follow the instructions in this manpage and type perl /usr/bin/snmp-bridge-mib br0 You'll get the following output: registering at .1.3.6.1.2.1.17 running as a subagent. dot1qbridge agent started. NET-SNMP version 5.4.2.1 AgentX subagent connected Now it's time for a first test: $ export MIBS=+BRIDGE-MIB $ snmpwalk localhost .1.3.6.1.2.1.17 The output produced should look like BRIDGE-MIB::dot1dStpBridgeHelloTime = INTEGER: 199 centi-seconds BRIDGE-MIB::dot1dStpBridgeForwardDelay = INTEGER: 1499 centi-seconds BRIDGE-MIB::dot1dStpPort.1 = INTEGER: 1 BRIDGE-MIB::dot1dStpPort.3 = INTEGER: 3 BRIDGE-MIB::dot1dStpPortPriority.1 = INTEGER: 32 BRIDGE-MIB::dot1dStpPortPriority.3 = INTEGER: 32 BRIDGE-MIB::dot1dStpPortState.1 = INTEGER: disabled(1) BRIDGE-MIB::dot1dStpPortState.3 = INTEGER: disabled(1) BRIDGE-MIB::dot1dStpPortEnable.1 = INTEGER: disabled(2) BRIDGE-MIB::dot1dStpPortEnable.3 = INTEGER: disabled(2) BRIDGE-MIB::dot1dStpPortPathCost.1 = INTEGER: 2 BRIDGE-MIB::dot1dStpPortPathCost.3 = INTEGER: 4 BRIDGE-MIB::dot1dStpPortDesignatedRoot.1 = STRING: "8000.001018382c78" BRIDGE-MIB::dot1dStpPortDesignatedRoot.3 = STRING: "8000.001018382c78" BRIDGE-MIB::dot1dStpPortDesignatedCost.1 = INTEGER: 0 BRIDGE-MIB::dot1dStpPortDesignatedCost.3 = INTEGER: 0 BRIDGE-MIB::dot1dStpPortDesignatedBridge.1 = STRING: "8000.001018382c78" BRIDGE-MIB::dot1dStpPortDesignatedBridge.3 = STRING: "8000.001018382c78" BRIDGE-MIB::dot1dStpPortDesignatedPort.1 = STRING: "32769" BRIDGE-MIB::dot1dStpPortDesignatedPort.3 = STRING: "32770" BRIDGE-MIB::dot1dStpPortPathCost32.1 = INTEGER: 2 BRIDGE-MIB::dot1dStpPortPathCost32.3 = INTEGER: 4 BRIDGE-MIB::dot1dTpLearnedEntryDiscards = Counter32: 0 BRIDGE-MIB::dot1dTpAgingTime = INTEGER: 300 seconds BRIDGE-MIB::dot1dTpFdbAddress.'...8,x' = STRING: 0:10:18:38:2c:78 BRIDGE-MIB::dot1dTpFdbAddress.'.!^/B|' = STRING: 0:21:5e:2f:42:7c BRIDGE-MIB::dot1dTpFdbPort.'...8,x' = INTEGER: 1 BRIDGE-MIB::dot1dTpFdbPort.'.!^/B|' = INTEGER: 3 BRIDGE-MIB::dot1dTpFdbStatus.'...8,x' = INTEGER: learned(3) BRIDGE-MIB::dot1dTpFdbStatus.'.!^/B|' = INTEGER: learned(3) BRIDGE-MIB::dot1dTpPort.1 = INTEGER: 1 BRIDGE-MIB::dot1dTpPort.3 = INTEGER: 3 BRIDGE-MIB::dot1dTpPortMaxInfo.1 = INTEGER: 1500 bytes BRIDGE-MIB::dot1dTpPortMaxInfo.3 = INTEGER: 1500 bytes BRIDGE-MIB::dot1dTpPortInFrames.1 = Counter32: 18082 frames BRIDGE-MIB::dot1dTpPortInFrames.3 = Counter32: 1546072 frames BRIDGE-MIB::dot1dTpPortOutFrames.1 = Counter32: 11601 frames BRIDGE-MIB::dot1dTpPortOutFrames.3 = Counter32: 10988 frames BRIDGE-MIB::dot1dTpPortInDiscards.1 = Counter32: 0 frames BRIDGE-MIB::dot1dTpPortInDiscards.3 = Counter32: 0 frames BUGS
1. snmp-bridge-mib currently only supports one bridge which has to be specified on the commandline. 2. Not all elements of RFC 4188 because they are either not available in sysfs or difficult to extract from the existing data. SEE ALSO
snmpd.conf(5), Net::SNMP(3) AUTHOR
Jens Osterkamp <jens@linux.vnet.ibm.com> Developer COPYRIGHT
Copyright (C) 2009, 2010 IBM Corp., All Rights Reserved Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. http://www.ibm.com/ v6 26 Mar 2010 SNMP-BRIDGE-MIB(1)
All times are GMT -4. The time now is 11:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy