topic Re: Remote Protocol Error & Unrecognized Individual Destination PDU in Operating System - OpenVMS

Remote Protocol Error & Unrecognized Individual Destination PDU

Alanjones_1 — Sun, 27 Aug 2006 13:08:00 GMT

Dear Friends,

we have four nodes are in openvms cluster environment. when i check the operator log it shows like this:

%%%%%%%%%%% OPCOM XX-XXX-2006 18:48:53.01 %%%%%%%%%%% (from node XXXXX a`
Message from user SYSTEM on XXXXXX
Event: Unrecognized Individual Destination PDU from: Node LOCAL:.XXXXXX CSMA-CD`
at: 2006-XX-XX-18:48:52.604+00:00Iinf
Data Link Header='AA000400042C00807D20C7378100'H
eventUid 5A7032BE-346A-11DB-B264-464F52544953
entityUid 9905C625-3118-11DB-849E-AA000400042C
streamUid 9D0924AF-3118-11DB-8559-AA000400042C

%%%%%%%%%%% OPCOM XX-XXX-2006 16:48:40.71 %%%%%%%%%%%
Message from user SYSTEM on XXXXXXX
Event: Remote Protocol Error from: Node LOCAL:.XXXXXXX NSP Local NSAP 49000BAA00`
at: 2006-XX-XX-16:48:40.715+00:00Iinf
Reject Cause=Invalid Message Format,
Erroneous Transport PDU='3842002300000005'H
eventUid BA3AFC70-3522-11DB-AA88-47454E495553
entityUid 7601C1DA-3175-11DB-9B16-47454E495553
streamUid 775A4BCC-3117-11DB-8828-AA0004000

What is the reason for this log?

Regards,
Balamurali

Re: Remote Protocol Error & Unrecognized Individual Destination PDU

Jim_McKinney — Sun, 27 Aug 2006 18:24:24 GMT

Regarding you first example with

Data Link Header='AA000400042C00807D20C7378100'H

implies that the packet received has a destination ethernet address of "AA-00-04-00-04-2C" (your node XXXXXX I presume) and was sent from a source address of "00-80-7D-20-C7-37" using some protocol that is registered to Wellfleet Communications "80-01". The unrecognized PDU (protocol data unit) message indicates that your XXXXXX node does not have this protocol (whatever it is) loaded.

Re: Remote Protocol Error & Unrecognized Individual Destination PDU

Wim Van den Wyngaert — Mon, 28 Aug 2006 01:20:39 GMT

The 2nd message is explained here
http://h71000.www7.hp.com/doc/82final/decnetplus/net_mng.pdf#search=%22%22Event%3A%20Remote%20Protocol%20Error%20from%22%22

Wim

Re: Remote Protocol Error & Unrecognized Individual Destination PDU

Wim Van den Wyngaert — Mon, 28 Aug 2006 01:30:18 GMT

And this explains the 1st one a little more.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=345947

Wim

Re: Remote Protocol Error & Unrecognized Individual Destination PDU

Volker Halle — Tue, 29 Aug 2006 02:32:16 GMT

Balamurali,

the Ethernet Protocol type in your first DECnet event messages is 8100 - which seems to be the Ethertype field for 802.1Q VLAN Frames.

Some node in your ethernet network (with a MAC address of 00-80-7D-20-C7-37) is sending a VLAN message to your OpenVMS DECnet-Plus system. This protocol is not available on OpenVMS before version V8.3, which adds VLAN support.

Volker.

Re: Remote Protocol Error & Unrecognized Individual Destination PDU

Volker Halle — Tue, 29 Aug 2006 02:38:42 GMT

Balamurali,

for the remote protocol error, you probably did not show all fields of the DECnet event message. It should have included the remote NSAP address as well. This should at least tell you, which remote DECnet node this message was coming from.

To decode the Erroneous Transport PDU, you would need the DECnet transport protocol specification.

Volker.

Re: Remote Protocol Error & Unrecognized Individual Destination PDU

Richard Brodie_1 — Wed, 30 Aug 2006 08:53:33 GMT

The source address of 00-80-7D-20-C7-37 is registered to Equinox Systems Inc, which seem to make serial to Ethernet boxes, amongst other things.

It might not necessarily be a fault on the end system though; it could be some switch in between has tagged it, and it's not been untagged again. You'ld have to check with your network folks what your local VLAN configuration is meant to look like.