[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[NOAAPORT #GGP-872890]: New Noaaport server with ldm

Hi Heather,

re:
> So I think I found one error.

Hopefullness? :-)

re:
> I used your command to add my route to the table:
> route add -net 224.0.0.0 netmask 240.0.0.0 gw 192.168.0.10 dev eth1
> 
> But my gw is 192.168.0.100!
> See:
> CMCS 192.168.0.138> show lan
> 
> Network Interface Settings:
> 
> Receiver MAC Address:         00-06-76-05-02-b7
> Receiver IP:                  192.168.0.138
> Receiver Subnet Mask:         255.255.255.0
> Default Gateway IP address:   192.168.0.100
> Unicast Status Destination:   255.255.255.255:6516
> Broadcast Status Port:                6516
> IGMP:                         OFF

As I understand it, the gateway (gw) specified in the route
command should be the IP address of the Ethernet interface
to which the Novra is connected.  It is that way in our
setup.

re:
> I deleted the entry from the route table and added in the other one:
> [root@npingest ~]# route add -net 224.0.0.0 netmask 240.0.0.0 gw 
> 192.168.0.100 dev eth1
> [root@npingest ~]# route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> default         gateway         0.0.0.0         UG    100    0        0 eno1
> 10.2.15.0       0.0.0.0         255.255.255.0   U     100    0        0 eno1
> 10.2.15.0       gateway         255.255.255.0   UG    100    0        0 eno1
> link-local      0.0.0.0         255.255.0.0     U     1003   0        0 eth1
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 224.0.0.0       192.168.0.100   240.0.0.0       UG    0      0        0 eth1
> 
> Now it is showing the correct gateway.  Does this look better?

If the IP address of the Ethernet interface to which the Novra is
connected is 192.168.0.10, I would make the 'gw' setting in the 'route'
invocation match.  Again, this is how all of our ingesters are setup.

re:
> Also, should the IP address of my eth1 entry be the same as my novra?

No, absolutely not!  Each is a device on the same network, so replicated
IP addresses would represent conflicts.

re:
> eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 192.168.0.10  netmask 255.255.255.0  broadcast 192.168.0.255
> inet6 fe80::225:90ff:fee7:fbb  prefixlen 64  scopeid 0x20<link>
> ether 00:25:90:e7:0f:bb  txqueuelen 1000  (Ethernet)
> RX packets 16456467  bytes 22404767338 (20.8 GiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 26  bytes 2382 (2.3 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 17  memory 0xdf900000-df920000
> 
> But my IP address of the novra is:
> 192.168.0.138

Yup, this is on the same subnet as the Ethernet interface which is
mandatory, and there is no IP conflict.

re:
> I see that yours are different too ...

You have to think of the setup as a number of "machines" being on
the same subnet, so there can be no replicated IP addresses.  The
gateway specified in the LAN setup on the Novra is not super
critical other than it has to be an IP address in the same subnet
AND not be the same as the Novra itself.

re:
> I am very confused by these!
> I attached a log file that I got.

I'll take a look...  The ldmd.log.1 file shows that nothing is making
it to the noaaportIngester processes.  This takes us back to either
a firewall blocking the flow of packets or the multicast routing being
incorrect.  The output of the latest 'route' indicates something that
is not correct.  Please change it back to what I suggested previously.

- delete the current multicast route

- add the correct one back in:

  route add -net 224.0.0.0 netmask 240.0.0.0 gw 192.168.0.10 dev eth1

re:
> I am working today until 3:30 EST if you want to do a google hangout.

I am about half an hour from heading into my office.

re:
> If you want to do one after, I can set up a time.  I am out from 3:30
> until about 5:00 to get my kids off the bus and take my daughter to
> dance.  My gmail address is address@hidden  I think it
> maybe easier that way.

OK.  I need to bounce all of this off of our system administrator
to see what he has to say before doing a hangout.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: GGP-872890
Department: Support NOAAPORT
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.