[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 looked into the tuned file and added the options that you recommended
> for the sysctl.conf file.  My tuned.conf looks like this:
> [ldm@npingest logs]$ cat /usr/lib/tuned/balanced/tuned.conf
> #
> # tuned configuration
> #
> 
> [main]
> summary=General non-specialized tuned profile
> net.ipv4.conf.default.rp_filter = 2
> net.ipv4.ipfrag_max_dist = 0
> 
> 
> [cpu]
> governor=conservative
> energy_perf_bias=normal
> 
> [audio]
> timeout=10
> 
> [video]
> radeon_powersave=dpm-balanced, auto
> 
> [disk]
> # Comma separated list of devices, all devices if commented out.
> # devices=sda
> 
> [scsi_host]
> alpm=medium_power

OK.

re:
> I also found my notes from the first time that I built this server

re:
> (that you helped with!)

I don't recall helping with a CentOS 7 machine...

re:
> I made some changes to the static-routes file and then restarted my network.

/etc/sysconfig/static-routes is definitely useful in CentOS 6.  I do not know
if it does anything in CentOS 7.

re:
> After restarting the network, things changed a lot!

Did you reboot after making changes in the tuned.conf file in the balanced
subdirectory?  If no, how were the settings made active?

re:
> And made more sense to me.  Gone is the eth1 interface (which confused me
> to no end why i had eno1 and eth1 when all my other centos-7 builds have eno1
> and eno2!) and now the interface is eno1 (network) and eno2 ( noaaport 
> receiver).

One can rename Ethernet interfaces so they look like they did in
older versions of CentOS.  Just saying...

re:
> Some file from before that I put on there must have messed things up!

Interesting.

re:
> Here is my ifconfig which looks good:
> 
> [ldm@npingest logs]$ ifconfig
> eno1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 10.2.15.252  netmask 255.255.255.0  broadcast 10.2.15.255
> ether 00:25:90:e7:0f:ba  txqueuelen 1000  (Ethernet)
> RX packets 1459  bytes 125524 (122.5 KiB)
> RX errors 0  dropped 332  overruns 0  frame 0
> TX packets 676  bytes 164719 (160.8 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 16  memory 0xdfa00000-dfa20000
> 
> eno2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
> inet 192.168.0.10  netmask 255.255.255.0  broadcast 192.168.0.255
> ether 00:25:90:e7:0f:bb  txqueuelen 1000  (Ethernet)
> RX packets 914  bytes 160752 (156.9 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 6  bytes 476 (476.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 17  memory 0xdf900000-df920000
> 
> lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> loop  txqueuelen 1000  (Local Loopback)
> RX packets 116  bytes 9716 (9.4 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 116  bytes 9716 (9.4 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

OK.  I think the RX numbers are suspiciously low for an interface into
which a Novra S300N is connected...

re:
> I made the netstat changes for eno2 (all the entries for eth1 went
> away when I did a network restart)
> 
> [ldm@npingest logs]$ netstat -rn
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
> 0.0.0.0         10.2.15.1       0.0.0.0         UG        0 0          0 eno1
> 10.2.15.0       0.0.0.0         255.255.255.0   U         0 0          0 eno1
> 10.2.15.0       10.2.15.1       255.255.255.0   UG        0 0          0 eno1
> 192.168.0.0     0.0.0.0         255.255.255.0   U         0 0          0 eno2
> 224.0.0.0       192.168.0.10    240.0.0.0       UG        0 0          0 eno2

Looks good.

re:
> And here is my tcpdump for eno2:
> How does it look:
> [root@npingest ~]# !tcpdump
> tcpdump -i eno2
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eno2, link-type EN10MB (Ethernet), capture size 262144 bytes
> 15:07:20.209399 IP 192.168.0.138.6516 > 255.255.255.255.6516: UDP, length 130
> 15:07:20.902563 IP 192.168.0.138.6516 > 255.255.255.255.6516: UDP, length 130
> 15:07:21.591675 IP 192.168.0.138.6516 > 255.255.255.255.6516: UDP, length 130

Not much traffic on eno2.  These look like the status packets from a Novra
S300N only.

re:
> However .... I am still not getting any data!!! Even though the stats look
> good, I would be really surprised with this snow if something were coming in.
> Maybe it is the snow?!?!  What do you think now?
> 
> [root@npingest ~]# /root/cmcs -ip 192.168.0.138 -pw Novra-S2 -shsat
> Satellite Interface Settings:
> 
> Receiver MAC Address: 00-06-76-05-02-b7
> Receiver Mode:                DVBS2
> Frequency:            1110.0 MHz
> Symbol Rate:          30.001 Msps (Auto)
> ModCod:                       2/3 16PSK
> Gold code:            0
> Input Stream Filter:  On
> Input Stream ID:      18
> 
> Signal Lock:          On
> Data Lock:            On
> Uncorrectable Rate:   0/Second
> Packet Error Rate:    4.8500e-04
> 
> Carrier to Noise C/N: 6.2dB
> Signal Strength:      -55 dBm

I think that your Novra is telling you that it is not seeing anything
good from the dish.  If you recall, your C/N went from 13.5dB down to 6.2dB.
I believe that with a C/N of 6.2 dB you should not expect to be getting
anything.

So, my answer to the question you posed above: 

"Maybe it is the snow?!?!  What do you think now?"

Yes, I think that the snow is the cause for you not seeing any data
at the moment.  I guess we'll have to wait for the dish to be cleaned
off before we know for sure.

Lesson learned:  tuned profiles can supersede /etc/sysctl.conf settings!

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.