|
Well, That's up to you. Everything we know about the trap is laid out right there in front of you. So now you can use xnmtrap to create a formatting definition that suits your needs. First you add the enterprise, 1.3.6.1.4.1.303.3.3.19.8.2, and give it some name. DirectWay seems an obvious choice. Then you add the specific trap in the box below the enterprise. You will need to chose a name for it. It can be anything you like so long as it is unique and fits in 39 characters. The trapd number is 4, the type is Enterprise Specific (that's what a generic 6 is). You choose the category and severity, the status is usually left to default, but you can change that also if you like. Typically the source is A for "agent" but that's your choice too. Finally, you decide what message you want the operator to see, something like, "VSAT $1 $2 for IP address $3" or whatever seems meaningful, and use that for the log message. Alternatively, since it is clear by the log entry that the MIB which defines the trap variables has already been loaded, because the OIDs in the variables are already shown as a complete label ( multimedia.nmsTraps.nmsTrapVars.nmsTrapVsatName for example), you could run mib2trap against the MIB and try to produce an addtrap script which might be used to define the trap for you. But you probably won't like the default values it will choose for you and you will end up using xnmtrap to edit the result anyway. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group
Hello James, I have just noticed that some traps are comming as follows:- 1090124266 3 Sun Jul 20 10:47:46 2004 0.0.0.0 ? Trap found with no known format in trapd.conf(4) 1090124266 3 Sun Jul 20 10:47:46 2004 0.0.0.0 ? EnterpriseENTERPRISES (1.3.6.1.4.1.303.3.3.19.8.2) community public 1090124266 3 Sun Jul 20 10:47:46 2004 0.0.0.0 ? generic trap:6 specific trap:4 1090124266 3 Sun Jul 20 10:47:46 2004 0.0.0.0 ? Timestamp:0 Agentaddr:0.0.0.0 args(3): 1090124266 3 Sun Jul 20 10:47:46 2004 0.0.0.0 ? [1] multimedia.nmsTraps.nmsTrapVars.nmsTrapVsatName(OctetString): BPST0292 1090124266 3 Sun Jul 20 10:47:46 2004 0.0.0.0 ? [2] prod.multimedia.nmsTraps.nmsTrapVars.nmsTrapNmd (OctetString): default1090124266 3 Sun Jul 18 10:47:46 2004 0.0.0.0 ? [3] prod.mu ltimedia.nmsTraps.nmsTrapVars.nmsTrapVsatIp (OctetString): 10.1.1.86 Probably these are the traps from DirectWays nms. How I should configure trapd.conf for the required format/definition? Regards, Anupam -----Original Message----- From: James Shanks [mailto:jshanks@us.ibm.com] Sent: Tuesday, July 20, 2004 2:53 PM To: nv-l@lists.us.ibm.com Subject: RE: [nv-l] Iintegration of HECL DirecWAY with Tivoli Netview I just noticed that you said "UDP socket in use".
Yikes!! That means that trapd does not own the port he's configured to
use, by default 162/udp. So he's not getting any external traps. What else
did you put on this box which is getting them, because something else has
the port, and trapd is not configured to get anything from that agent.
Hello James, We are not seeing any event neither in trapd.log nor in trapd.trace. I have already enabled -x option ( it says.. UDP socket is already in use.) Through -T option, toggling has been enabled and there is no event/message in trapd.trace file. The snmp trap from the DirectWay NMS (ip address 192.168.10.180) is coming on our NetView server (ip address 10.72.15.196) on 162 port that we have seen using sniffer. Also, there is no firewall in between. Can you suggest, what all are required to be configured at NetView level to get the snmp trapds? Is any particular mibs to be loaded? Regards, Anupam -----Original Message----- From: James Shanks [mailto:jshanks@us.ibm.com] Sent: Monday, July 19, 2004 5:27 PM To: nv-l@lists.us.ibm.com Subject: Re: [nv-l] Iintegration of HECL DirecWAY with Tivoli Netview If you are not seeing traps, in the trapd.log, nor any messages about invalid traps, then your DircetWay box is not sending them, period. There is no way that trapd can get a trap and not log it or issue an error message. You can get him to trace everything that he sees by first configuring trapd to run with the -x option, (hex dump all packets), using serversetup, and then toggling the trace off and on with "trapd -T" from the command line. But to really prove that nothing is coming in on port 162 udp, you will need to get an iptrace. James Shanks Level 3 Support for Tivoli NetView for UNIX and Windows Tivoli Software / IBM Software Group "anand anupam" <ananda@bharatpetroleum.com> Sent by: owner-nv-l@lists.us.ibm.com 07/19/2004 05:35 AM Please respond to nv-l To <nv-l@lists.tivoli.com> cc Subject [nv-l] Iintegration of HECL DirecWAY with Tivoli Netview Hello Everybody, We are having Tivoli NetView(7.1.3) on AIX 4.3.3. Recently we installed HECL DirecWAY to monitor our VSATs (DPUs). These VSATs(DPUs) are SNMP compliant but can not by pass HECL DirecWAY NMS. This NMS(DirecWAY ) has been installed on HP platform and is collected information about the status of VSATs(DPU). Now, we wanted to integrate DirecWAY with our Tivoli NetView. This NMs(DirecWAY) is also configured to send traps to NetView server. But we are not getting these traps in trapd.log. Ideally, we wanted these traps on TEC so that we can execute some TEC rules as per our requirement. Any idea how to achieve this? Regards, Anupam |
"anand
anupam" <ananda@bharatpetroleum.com>
