Creating SNMP Strings To Trap ALOM Console Messages


 
Thread Tools Search this Thread
Operating Systems Solaris Creating SNMP Strings To Trap ALOM Console Messages
# 1  
Old 03-27-2008
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 trapped ALOM console messages to a log file.

I have visited the docs.sun.com website as well as other websites and was able to find some background information, but not enough to put together a complete game plan. Specifically, I am missing the following information:

(1) The configuration file or files where I would configure the SNMP traps
(2) What process or processes/daemons need to be enabled/configured so as to implement/enable SNMP trapping
(3) The name of the log file where the results of ALOM console message trapping results would typically be routed to.

I think I have it all covered in steps 1-3 above, but if I am missing something or leaving something out, then I am not averse to being corrected and/or admonished. As I stated previously, I have visited several websites looking for enough information, but cannot seem to get it all altogether. I would deeply appreciate anyone who has ever done this before to share his/her advice/experience/notes with me. Thanks in advance!

Rob Sandifer
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Snmp trap command for Solaris 5.10

I am using the following command to successfully send snmp traps on Linux but I cant get it to work on Solaris , can someone give me the syntax plz? Linux: /usr/sbin/snmptrap -v 2c -c org 10.100.10.211 \'\' 1.3.6.1.4.1.791.2.9.2 1.3.6.1.4.1.791.2.9.2 s \"$1 \" Solaris:... (5 Replies)
Discussion started by: aliyesami
5 Replies

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... (4 Replies)
Discussion started by: vipul_prajapati
4 Replies

3. Solaris

ALOM - Console -

Hello forum, I have a SUN v250 at home that I have to practice Solaris. I currently have Solaris 9 installed and the ALOM Sun(tm) Advanced Lights Out Manager 1.5.2. From the ALOM I want to access the console. sc> console -f Enter #. to return to ALOM. after that there is no response.... (19 Replies)
Discussion started by: br1an
19 Replies

4. Infrastructure Monitoring

SNMP Trap on Solaris...HELP!

Hi all, I am currently doing a project regarding traps and would like to help me in this issue. I am knew to the trap world :confused::) and thought that by posting this thread helps me move forward in this project. First of all I will begin exactly from the very beginning, i.e. the net-snmp... (0 Replies)
Discussion started by: Wizard_1979
0 Replies

5. Infrastructure Monitoring

Allow specific hosts for snmp trap

I want to receive snmp traps only from specifis ip's or host. I tried to get help from VACM , but it's complicated. Can any one please suggest me simple way to do it (0 Replies)
Discussion started by: nrbhole
0 Replies

6. Infrastructure Monitoring

linux snmp trap relay

Hi all, I'm after a linux utility that can relay all incoming traffic on a certain port to another server. Can anyone recommend a good program? I've taken a look at snmptrapd, but it's not obvious how this can be configured for my requirements. Many thanks. (1 Reply)
Discussion started by: badoshi
1 Replies

7. Solaris

how to go to system console through ALOM in Sunfire V245

Hello , I am connecting sumfire v245 server to my laptop Through ALOM method.i got the ALOM prompt but after that i am typing sc> console to go to system console but i am not able to,after typing console only this line is coming Type #. to go back to ALOM. What to do ?? That server having... (5 Replies)
Discussion started by: avi157
5 Replies

8. Solaris

console -f not working in ALOM

Hi, I connected to ALOM on V240 installed with Solaris 10. console -f does not give me console on screen. Sun(tm) Advanced Lights Out Manager 1.6.8 sc> console -f Enter #. to return to ALOM. ...I pressed ENTER a lot of times but does not give me console. Another observation in this... (5 Replies)
Discussion started by: upengan78
5 Replies

9. IP Networking

Send A Snmp Trap

Hi, do you know the syntax to send a snmp trap to a server ? Many htanks. (2 Replies)
Discussion started by: big123456
2 Replies

10. IP Networking

snmp trap generator

Hi, I am writing a program in java to simulate a trap being sent from a device. I came to know that rawsocket cant be opened in java. Is there a provision to do in java? My requirement is: I am writing the java program in the machine 1.1.1.1 I want to simulate the trap being sent from a... (0 Replies)
Discussion started by: kkrish7
0 Replies
Login or Register to Ask a Question
snmp_trapsnd(8) 					      System Manager's Manual						   snmp_trapsnd(8)

NAME
snmp_trapsnd - A program that sends SNMPv1 and SNMPv2 traps SYNOPSIS
/usr/sbin/snmp_trapsnd enterprise agent_addr generic specific timeticks [-v version] [-c community] [-h host] [-p port] [-tcp] [variable [type value]] OPTIONS
Specifies the type of message in which to send the PDU. The default version is SNMPv1. Use 2c to specify that the PDU be sent in an SNMPv2C message. Specifies the host name or dot-formatted IP address of the destination node to receive the trap message. If no host is specified, the trap is sent to the loopback interface. Causes a hexadecimal dump of the encoded packet to be sent to stdout. Specifies that the TCP transport be used instead of the UDP transport. If a connection cannot be established, the program silently sends the trap to the standard transport address (UDP 162). Specifies the port number on the destination host to which this message is sent. The default is 162, the well-known SNMP trap port. Specifies the community string used to send the trap. The default is public. OPERANDS
For SNMPv1 traps, this is the enterprise object identifier, in dot string notation, on whose behalf the trap is being sent (for example, 1.3.6.1.4.1.232). For SNMPv2 traps (specified with the -v 2c option), this represents the value of snmpTrapOID.0. For an SNMPv2 enterprise-specific trap, this is typically a concatenated string containing the enterprise OID, 0 (zero), and a single digit. See the generic parame- ter table. The hostname or IP address of the entity on whose behalf the trap is being generated (the agent-addr field in the V1 trap PDU). The special name local reports the host on which this program is running. This value is ignored if the -v 2c option is present. The generic trap identifier. This is a non-zero number. The following table summarizes the trap IDs: ------------------------------------------------------------------------ Description V1 generic Value V2 enterprise Value ------------------------------------------------------------------------ coldStart 0 1.3.6.1.6.3.1.1.5.1 warmStart 1 1.3.6.1.6.3.1.1.5.2 linkDown 2 1.3.6.1.6.3.1.1.5.3 linkUp 3 1.3.6.1.6.3.1.1.5.4 authenticationFailure 4 1.3.6.1.6.3.1.1.5.5 egpNeighborLoss 5 1.3.6.1.6.3.1.1.5.6 enterpriseSpecific 6 enterprise.0.x ------------------------------------------------------------------------ If the -v 2c option is present, this parameter is ignored. Specifies the enterprise-specific trap number. A value must be present, but is ignored if the -v 2c option is present or if generic is a value other than 6. Specifies the relative time associated with the generation of this trap message. This is the number of TIMETICKS (1/100 of a second) since the sending SNMP entity started. Specifies a list of MIB variables to be included in the trap message. See snmp_request(8) for information on specifiying SNMP MIB variables on the command line. DESCRIPTION
The snmp_trapsnd program encodes an SNMPv1 Trap protocol data unit (PDU) (see RFC 1215) or a SNMPv2 Trap PDU (see RFC 1905) into an SNMP message, and sends it to the specified host(s). All data fields in the trap PDU can be specified in the run-time arguments. SNMPv1 traps are uniquely identified by the combination of enterprise, generic, and specific operands. SNMPv2 traps are uniquely identi- fied by the value of snmpTrapOID.0 in the enterprise operand. RESTRICTIONS
The use of this command should be limited. SNMP traps should be sent rarely, when significant state changes occur on a managed node. SEE ALSO
Commands: snmpd(8), snmp_request(8), snmp_traprcv(8) RFC 1907, Management Information Base for Version 2 of the Simple Network Management Protocol (SNMPv2) snmp_trapsnd(8)