RE: [nv-l] Solaris Bad PDU Type
2004-04-15 14:04:39
It's in /var/adm/messages and it is
frequent.
I'll check on the trap sending port number since our team
owns the device.
Where did you see this
message? In the log for snmpdx?
Then the problem is that someone sent an SNMP V1 trap (pdu type 0x'a4')
to port 161, where snmpdx is listening, rather than to port 162, where trapd
is listening. If it happens frequently then you might be able to
capture it with snoop.
If in the trapd.log, then as Paul said, perhaps it is a badly
formatted trap. In the latter case, you might be able to capture it by
running trapd with the -x option and starting the trapd trace (trapd -T from
the command line toggles it). But snoop should work here too. It's
just a matter of what port you want to snoop 161 or 162 udp.
James Shanks Level 3 Support
for Tivoli NetView for UNIX and Windows Tivoli Software / IBM
Software Group
"Barr, Scott"
<Scott_Barr AT csgsystems DOT com> Sent by: owner-nv-l AT lists.us.ibm DOT com
04/15/2004 12:20 PM
|
To
| <nv-l AT lists.us.ibm DOT com>
|
cc
|
|
Subject
| [nv-l] Solaris Bad PDU
Type |
|
I remember seeing this mentioned in the forum somewhere but
can't find it in the archives. Does anyone know what this message
means:
<hostname> /usr/lib/snmp/snmpdx:
[ID 702911 daemon.error] bad PDU type (0xa4) received from
<devicename>
Solaris 2.8
NetView v7.1.4
|
|
|