|
I have almost no idea what you are talking about. All SNMP traps are transmitted in hex. You need an agent to decode them.
But I can tell you that if you install NetView for UNIX Version 7.1.3 FixPack2 or Version 7.1.4, then you will be able to get a clearer understanding of why NetView rejects a particular trap as invalid by looking in the trapd.trace. First you have to use serversetup to configure trapd to run with the "hex dump all packets" so that he runs with the "-x" option. Then you can toggle the trace on and off again with the command "/usr/OV/bin/trapd -T" any time you wish. In the trapd.trace file you will see the initial hex dump of the received trap and an error message indicating what part NetView thought was invalid. If the trap was SNMP V2, you will also see the SNMP V1 equivalent trap in case that's where the problem lies. But you have to investigate it yourself.
Good luck
James Shanks
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
 "Delaire, Patrick" <delairep@aetna.com>
|
|
To: <nv-l@lists.us.ibm.com>
cc:
Subject: [nv-l] SNMP on HMC console |
Hello list..
I am attempting to setup the SNMP API on IBM HMC to be notified of incidents that occur on the HMC itself.
My local vendor and myself were able to configure the API but the data we are getting back from the HMC is in HEX not ASCII
Which is another problem.. But we are receiving the following message in Netview log:
Wed Jan 28 14:54:30 2004 <none> T Application ID: 4. Name/Address: <none>. Description: WARNING:
invalid SNMPTrap packet from agent 167.69.236.21 source A pid -1
Can anyone out there tell me what's going on here?
Any help would be appreciated, thanks Patrick
This e-mail may contain confidential or privileged information. If you
think you have received this e-mail in error, please advise the sender by
reply e-mail and then delete this e-mail immediately. Thank you. Aetna
|
|