SNMP in a Bridge device

8 More Discussions You Might Find Interesting

1. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon...

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

3. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ...

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

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

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

7. IP Networking

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

8. UNIX for Dummies Questions & Answers

bridge on linux

Hello. I expirince some problems with bridging, i'm pretty new to that technology I've 2 nic's 1 - wireless rt2500 ra0 canyon cn511 card 2 - e100 intel, ifconfig ra0 up && iwconfig ra0 essid xxx channel x mode managed bring me wireless connection up then i do following: brctl addbr br0...

LEARN ABOUT OSX

cups-snmp

cups-snmp(8)							    Apple Inc.							      cups-snmp(8)

NAME

       snmp - cups snmp backend

SYNOPSIS

       /usr/lib/cups/backend/snmp ip-address-or-hostname
       /usr/libexec/cups/backend/snmp ip-address-or-hostname
       lpinfo -v --include-schemes snmp

DESCRIPTION

       The  CUPS  SNMP	backend provides legacy discovery and identification of network printers using SNMPv1. When used for discovery through the
       scheduler, the backend will list all printers that respond to a broadcast SNMPv1 query with the "public" community name. Additional queries
       are  then  sent	to  printers  that  respond in order to determine the correct device URI, make and model, and other information needed for
       printing.

       In the first form, the SNMP backend is run directly by the user to look up the device URI and other information when you have an IP address
       or hostname. This can be used for programs that need to configure print queues where the user has supplied an address but nothing else.

       In  the	second form, the SNMP backend is run indirectly using the lpinfo(8) command. The output provides all printers detected via SNMP on
       the configured broadcast addresses. Note: no broadcast addresses are configured by default.

MIBS

       The CUPS SNMP backend uses the information from the Host, Printer, and Port Monitor MIBs along with some vendor private MIBs  and  intelli-
       gent port probes to determine the correct device URI and make and model for each printer.

CONFIGURATION

       The  SNMP  backend  reads the /etc/cups/snmp.conf configuration file, if present, to set the default broadcast address, community name, and
       logging level. The configuration file is documented in cups-snmp.conf(5). The DebugLevel value can be overridden using the CUPS_DEBUG_LEVEL
       environment variable and the MaxRunTime value can be overridden using the CUPS_MAX_RUN_TIME environment variable.

SEE ALSO

       backend(7), cups-snmp.conf(5), cupsd(8), cupsd.conf(5), filter(7), lpinfo(8),
       http://localhost:631/help

COPYRIGHT

       Copyright 2007-2013 by Apple Inc.

8 July 2013							       CUPS							      cups-snmp(8)

IP Networking