Greetings,
FNG here, your patience is appreciated. Need some help as to whether I have
something to be concerned about or if this output I see is erroneous.
I am running EMANE v6.3 on Fedora 12. EMANE was installed using the EMANE
provided RPM packages. The Fedora 12 system is a VM running on VMWare ESXi 4.1.
Not my choice to run an older version of EMANE, so I gotta just roll with it.
Using a centralized server with 4 NEM.
Here is the platform.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE platform SYSTEM "/usr/share/emane/dtd/platform.dtd">
<platform name="Workstation 1" id="1">
<param name ="otamanagerchannelenable" value ="off"/>
<param name="eventservicegroup" value="224.1.2.8:45703"/>
<param name="eventservicedevice" value="lo"/>
<nem name="NODE-001" id="1" definition="rfpipenem.xml">
<param name="platformendpoint" value="localhost:8171"/>
<param name="transportendpoint" value="localhost:8181"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth0"/>
</transport>
</nem>
<nem name="NODE-002" id="2" definition="rfpipenem.xml">
<param name="platformendpoint" value="localhost:8172"/>
<param name="transportendpoint" value="localhost:8182"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth1"/>
</transport>
</nem>
<nem name="NODE-003" id="3" definition="rfpipenem.xml">
<param name="platformendpoint" value="localhost:8173"/>
<param name="transportendpoint" value="localhost:8183"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth2"/>
</transport>
</nem>
<nem name="NODE-004" id="4" definition="rfpipenem.xml">
<param name="platformendpoint" value="localhost:8174"/>
<param name="transportendpoint" value="localhost:8184"/>
<transport definition="transraw.xml" group="single">
<param name="device" value="eth3"/>
</transport>
</nem>
</platform>
Here is the transportdaemon.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE transportdaemon SYSTEM "/usr/share/emane/dtd/transportdaemon.dtd">
<transportdaemon>
<instance nemid="1">
<param name="transportendpoint" value="localhost:8181"/>
<param name="platformendpoint" value="localhost:8171"/>
<transport definition="transraw.xml">
<param name="device" value="eth0"/>
</transport>
</instance>
<instance nemid="2">
<param name="transportendpoint" value="localhost:8182"/>
<param name="platformendpoint" value="localhost:8172"/>
<transport definition="transraw.xml">
<param name="device" value="eth1"/>
</transport>
</instance>
<instance nemid="3">
<param name="transportendpoint" value="localhost:8183"/>
<param name="platformendpoint" value="localhost:8173"/>
<transport definition="transraw.xml">
<param name="device" value="eth2"/>
</transport>
</instance>
<instance nemid="4">
<param name="transportendpoint" value="localhost:8184"/>
<param name="platformendpoint" value="localhost:8174"/>
<transport definition="transraw.xml">
<param name="device" value="eth3"/>
</transport>
</instance>
</transportdaemon>
Here is a snippet of errors that are logged by emanetransportd:
16:53:41.887765 ERROR TRANSPORTI 003 RawTransport::readDevice frame error
16:53:41.913454 ERROR TRANSPORTI 004 EthernetTransport::verifyFrame unsupported
protocol 58
16:53:41.913491 ERROR TRANSPORTI 004 RawTransport::readDevice frame error
16:53:41.976754 ERROR TRANSPORTI 001 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:41.976779 ERROR TRANSPORTI 001 RawTransport::readDevice frame error
16:53:43.164620 ERROR TRANSPORTI 002 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:43.164663 ERROR TRANSPORTI 002 RawTransport::readDevice frame error
16:53:43.980462 ERROR TRANSPORTI 001 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:43.980507 ERROR TRANSPORTI 001 RawTransport::readDevice frame error
16:53:44.780795 ERROR TRANSPORTI 004 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:44.780871 ERROR TRANSPORTI 004 RawTransport::readDevice frame error
16:53:45.166286 ERROR TRANSPORTI 002 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:45.166330 ERROR TRANSPORTI 002 RawTransport::readDevice frame error
16:53:45.978226 ERROR TRANSPORTI 001 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:45.978270 ERROR TRANSPORTI 001 RawTransport::readDevice frame error
16:53:46.786809 ERROR TRANSPORTI 004 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:46.786854 ERROR TRANSPORTI 004 RawTransport::readDevice frame error
16:53:47.159015 ERROR TRANSPORTI 002 EthernetTransport::verifyFrame unsupported
protocol 27
16:53:47.159049 ERROR TRANSPORTI 002 RawTransport::readDevice frame error
Also, just after starting emanetransportd, I see a lot of ARP traffic on my
test network using tcpdump on other systems that are on the same network. The
test network seems to get very sluggish shortly after that.
I ended up using ebtables to block the ARP from the EMANE server and got my
network connections back. That of course required monkey business with
/etc/ethers, but I digress. I must have something misconfigured. Or is it that
EMANE is not supported on VMWare ESXi? The errors were generated prior to my
using ebtables and /etc/ethers to block ARP.
RTFM? Of course I did, but I could use your advice.
Thanks for your time and support.
V/R,
FNG
_______________________________________________
emane-users mailing list
[email protected]
http://pf.itd.nrl.navy.mil/mailman/listinfo/emane-users
