Computer system designers may use syslog for system management and security auditing as well as general informational, analysis, and debugging messages. A wide variety of devices, such as printers and routers, and message receivers across many platforms use the syslog standard. This permits the consolidation of logging data from different types of systems in a central repository. Implementations of syslog exist for many operating systems.
Each message is labeled with a facility code, and assigned a severity label. The facility code indicates the software type of the application that generated the message.
The destination of messages may be directed to various destinations, tuned by facility and severity, including console, files, remote syslog servers, or relays.
Most implementations provide a command line utility, often called logger, as well as a link library, to send messages to the log.
Some implementations include reporting programs for filtering and displaying of syslog messages.
SNMP Trap Generator. Simple Network Management Protocol (SNMP) is widely used
for administration and monitoring purposes. Asynchronous notification from agent to manager. SNMP traps enable an agent to notify the management station of significant events by way of an unsolicited SNMP message. Includes current sysUpTime value, an OID identifying the type of trap and optional variable bindings. Destination addressing for traps is determined in an application-specific manner typically through trap configuration variables in the MIB. The format of the trap message was changed in SNMPv2 and the PDU was renamed SNMPv2-Trap. While in classic communication the client always actively requests information from the server, SNMP allows the additional use of so-called "traps". These are data packages that are sent from the SNMP client to the server without being explicitly requested.
This sample about freesoft SNMPGET, SNMPWALK, SNMP Generator & SYSLOG Generator
for administration and monitoring purposes. Asynchronous notification from agent to manager. SNMP traps enable an agent to notify the management station of significant events by way of an unsolicited SNMP message. Includes current sysUpTime value, an OID identifying the type of trap and optional variable bindings. Destination addressing for traps is determined in an application-specific manner typically through trap configuration variables in the MIB. The format of the trap message was changed in SNMPv2 and the PDU was renamed SNMPv2-Trap. While in classic communication the client always actively requests information from the server, SNMP allows the additional use of so-called "traps". These are data packages that are sent from the SNMP client to the server without being explicitly requested.
This sample about freesoft SNMPGET, SNMPWALK, SNMP Generator & SYSLOG Generator
1. Trap Generator
Download http://trapgen.trapreceiver.com/
Usage:
TrapGen.exe -d <destination IP Address> -v/v2c<SNMP version> <OID> STRING <"String">
Examples:
TrapGen.exe -d 127.0.0.1 -v .1.3.6.1.2.1.25.3.3.1.2 STRING "TOO HOT"
2. Syslog Generator
Usage:
SyslogGen.exe -t:target [-q] [-p:port] [-tcp] [-f:facilty] [-s:severity] [-h:hostname] [-tg:tag] -m:"message"
Examples:
SyslogGen.exe -t:192.168.1.7 -f:1 -s:7 -h:server -m:"Too many bytes.\x0D\x0A"
SyslogGen.exe -t:fe80::216:6fff:fe7e:55d5%7 -tg:NET -m:"IPv6 works fine."
SyslogGen.exe -t:127.0.0.1 -f:1 -s:7 -m:"TOO HOT"
3. SNMP Generator
SNMP Trap Generator. Simple Network Management Protocol (SNMP) is widely used
for administration and monitoring purposes.
Usage:
SnmpTrapGen.exe [-q] -r:host [-p:port] [-t:timeout] [-v:version] [-c:community] [-ei:engine_id] [-sn:sec_name] [-ap:auth_proto] [-aw:auth_passwd] [-pp:priv_proto] [-pw:priv_passwd] [-ce:cont_engine] [-cn:cont_name] [-vid:var_oid] [-vtp:var_type] [-val:var_value] [-del:char] -eo:ent_oid -to:trap_oid
Examples:
SnmpTrapGen.exe -r:10.0.0.1 -t:10 -c:"private" -to:.1.3.6.1.2.1.1.4.0
SnmpTrapGen.exe -r:SnmpCollector -q -v:2c -p:10162 -to:.1.3.6.1.2.1.1.1.0
SnmpTrapGen.exe -r:127.0.0.1 -t:10 -c:"public" -to:.1.3.6.1.2.1.1.4.0
4. SNMPWALK
Usage:
SnmpWalk.exe [-q] -r:host [-p:port] [-t:timeout] [-v:version] [-c:community] [-ei:engine_id] [-sn:sec_name] [-ap:auth_proto] [-aw:auth_passwd] [-pp:priv_proto] [-pw:priv_passwd] [-ce:cont_engine] [-cn:cont_name] [-os:start_oid] [-op:stop_oid] [-csv]
Examples:
SnmpWalk.exe -r:MainRouter -csv
SnmpWalk.exe -r:10.0.0.1 -t:10 -c:"admin_rw" -os:.1.3.6.1.2.1.1
SnmpWalk.exe -r:"::1" -v:3 -sn:SomeName -ap:MD5 -aw:SomeAuthPass -pp:DES -pw:SomePrivPass -os:.1.3.6.1.2.1 -op:.1.3.6.1.2.65535 -q
SnmpWalk.exe -r:127.0.0.1 -c:"public" -os:.1.3.6.1.2.1.1
5. SNMPGET
Usage:
SnmpGet.exe [-q] -r:host [-p:port] [-t:timeout] [-v:version] [-c:community] [-ei:engine_id] [-sn:sec_name] [-ap:auth_proto] [-aw:auth_passwd] [-pp:priv_proto] [-pw:priv_passwd] [-ce:cont_engine] [-cn:cont_name] -o:var_oid
Examples:
SnmpGet.exe -r:10.0.0.1 -t:10 -c:"admin_rw" -o:.1.3.6.1.2.1.1.4.0
SnmpGet.exe -r:MainRouter -q -v:2c -p:10161 -o:.1.3.6.1.2.1.1.1.0
SnmpGet.exe -r:"::1" -v:3 -sn:SomeName -ap:MD5 -aw:SomeAuthPass -pp:DES -pw:SomePrivPass -o:.1.3.6.1.2.1.1.8.0
SnmpGet.exe -r:127.0.0.1 -t:10 -c:"public" -o:.1.3.6.1.2.1.1.4.0
[root@TEGUH init.d]# snmpwalk -v2c -c public localhost system
SNMPv2-MIB::sysDescr.0 = STRING: Linux TEGUH 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64
6.Net-SNMP
Usage:
Snmpwalk [version] [community] [ip] [oid]
[root@TEGUH init.d]# snmpwalk -v2c -c public localhost system
SNMPv2-MIB::sysDescr.0 = STRING: Linux TEGUH 2.6.32-279.el6.x86_64 #1 SMP Wed Jun 13 18:24:36 EDT 2012 x86_64
No comments:
Post a Comment