perfSONAR User Q&A and Other Discussion

[Andy Fleming <>]

Hum, Jason Z actually helped us configure it the first time, so I'm not sure.  I think it might have been a mesh.  I've attached the owmesh.conf file minus the first part of the file that seems to have some passwords.  I fixed the IP Addresses in that file as well as in store.xml on one of our nodes and at least looking at the process list, it looks like that has helped. 

So if we have a mesh configuration it would still do the scheduled test, it just can't be edited from the GUI? 


On 2/16/12 8:58 AM, Aaron Brown wrote:

Hey Andy,

How did you configure the owmesh.conf originally? It looks like there's a mesh configuration, but the web gui only supports star configurations currently.

Cheers,

Aaron

On Feb 16, 2012, at 9:43 AM, Andy Fleming wrote:

Sure, I've attached the log.  Thanks for taking a look.  -- Andy



On 2/16/12 7:24 AM, Aaron Brown wrote:

Hey Andy,

Can you try going to that page, and then sending us the /var/log/perfsonar/web_admin/web_admin.log file?

Cheers,

Aaron

On Feb 15, 2012, at 5:50 PM, Andy Fleming wrote:

Folks, I'm hoping someone on this list might be able to help me out with the error message below.  We have an install of a few perfSONAR machines that were staged a while back, but just recently actually deployed.   Our network engerneir changed the IP Address we were going to use on me a couple of times since they were staged.  Anyone have any idea about it there is a simple way to resolve this error message? 

Do I need to run the nptoolkit-configure.py script again?  I can't reload the ISO from scratch without driving hundreds of miles, but I could even remove all the perfsonar packages and re-install if it comes to that point.  (I'm hoping it something simple I can fix by editing a few config files.) 

Thanks in advance for any suggestions anyone might have.  -- Andy

Scheduled Tests Configuration Tool

Problem reading testing configuration: Problem reading perfSONAR-BUOY Configuration

The on-disk configuration has changed. Any changes you made have been lost.

The /etc/hosts file appears to have been modified. This may cause unexpected behavior by tools. Click here to correct the file.

-- 
Andy Fleming - RHCE 
Sr Systems Administrator
Kansas Research and Education Network

Office: 785-856-9800 x 9806

KanREN
 - Advanced Network Solutions for the Research and Education Community

Winter 2012 ESCC/Internet2 Joint Techs, January 22-26
Hosted by the Louisiana Optical Network Intitiative (LONI)
http://events.internet2.edu/2012/jt-loni/index.cfm

-- 
Andy Fleming - RHCE 
Sr Systems Administrator
Kansas Research and Education Network

Office: 785-856-9800 x 9806

KanREN
 - Advanced Network Solutions for the Research and Education Community

<web_admin.log>

Winter 2012 ESCC/Internet2 Joint Techs, January 22-26
Hosted by the Louisiana Optical Network Intitiative (LONI)
http://events.internet2.edu/2012/jt-loni/index.cfm

-- 
Andy Fleming - RHCE 
Sr Systems Administrator
Kansas Research and Education Network

Office: 785-856-9800 x 9806

KanREN
 - Advanced Network Solutions for the Research and Education Community

#######################################################################
# BWCTL Iperf-TCP Test Definition

<TESTSPEC=BWTCP4>
DESCRIPTION         KanREN BWCTL (TCP) Internal
TOOL            bwctl/iperf
BWTCP
BWTestDuration  30
BWTestInterval  14400
</TESTSPEC>

#######################################################################
# BWCTL Iperf-UDP Test Definition

<TESTSPEC=BWUDP4>
DESCRIPTION         KanREN BWCTL (UDP) Internal
TOOL            bwctl/iperf
BWUDP
BWTestDuration  30
BWUDPBandwidthLimit     50m
BWTestInterval  14400
</TESTSPEC>

#######################################################################
# OWAMP Test Definition

<TESTSPEC=LAT_1MIN>
DESCRIPTION                     KanREN OWAMP Internal
TOOL                            powstream
OWPINTERVAL             0.1
OWPLOSSTHRESH                   10
OWPSESSIONCOUNT                 108000
OWPSAMPLECOUNT                  600
OWPPACKETPADDING                0
OWPBUCKETWIDTH                  0.0001
</TESTSPEC>


#######################################################################
# Host definitions, should equal the result of a `uname -a`, this is
#   how the master will determine which machine is running a test.  Its a good
#   idea to enter all machines that are involved in all tests here.

<HOST=ps-wsu-lt.kanren.net>
NODE    ps-wsu-lt
</HOST>

<HOST=ps-ksu-lt.kanren.net>
NODE    ps-ksu-lt
</HOST>

<HOST=ps-ku-lt.kanren.net>
NODE    ps-ku-lt
</HOST>

<HOST=ps-bryant-lt.kanren.net>
NODE    ps-bryant-lt
</HOST>



<HOST=ps-wsu-bw.kanren.net>
NODE    ps-wsu-bw
</HOST>

<HOST=ps-ksu-bw.kanren.net>
NODE    ps-ksu-bw
</HOST>

<HOST=ps-ku-bw.kanren.net>
NODE    ps-ku-bw
</HOST>

<HOST=ps-bryant-bw.kanren.net>
NODE    ps-bryant-bw
</HOST>


#######################################################################
# Node Definitions, needed for each potential member of a mesh

NODES [[ ps-wsu-lt ps-ksu-lt ps-ku-lt ps-bryant-lt ps-wsu-bw ps-ksu-bw 
ps-ku-bw ps-bryant-bw ]]

<NODE=ps-wsu-lt>
LONGNAME KanREN WSU Latency
CONTACTADDR     164.113.32.33
LAT4ADDR        164.113.32.33
</NODE>

<NODE=ps-ksu-lt>
LONGNAME KanREN KSU Latency
CONTACTADDR     164.113.32.25
LAT4ADDR        164.113.32.25
</NODE>

<NODE=ps-ku-lt>
LONGNAME KanREN KU Latency
CONTACTADDR     164.113.32.17
LAT4ADDR        164.113.32.17
</NODE>

<NODE=ps-bryant-lt>
LONGNAME KanREN 1102 Grand Latency
CONTACTADDR     164.113.32.9
LAT4ADDR        164.113.32.9
</NODE>



<NODE=ps-wsu-bw>
LONGNAME KanREN WSU Bandwidth
CONTACTADDR     164.113.32.34
BW4ADDR         164.113.32.34
</NODE>

<NODE=ps-ksu-bw>
LONGNAME KanREN KSU Bandwidth
CONTACTADDR     164.113.32.26
BW4ADDR         164.113.32.26
</NODE>

<NODE=ps-ku-bw>
LONGNAME KanREN KU Bandwidth
CONTACTADDR     164.113.32.18
BW4ADDR         164.113.32.18
</NODE>

<NODE=ps-bryant-bw>
LONGNAME KanREN 1102 Grand Bandwidth
CONTACTADDR     164.113.32.10
BW4ADDR         164.113.32.10
</NODE>


#######################################################################
# Group Definition
<GROUP=KanREN_BWCTL>
DESCRIPTION         KanREN BWCTL Testing
GROUPTYPE       MESH
NODES           [[ps-wsu-bw ps-ksu-bw ps-ku-bw ps-bryant-bw]]
</GROUP>

<GROUP=KanREN_OWAMP>
DESCRIPTION     KanREN OWAMP Testing
GROUPTYPE       MESH
NODES           [[ps-wsu-lt ps-ksu-lt ps-ku-lt ps-bryant-lt]]
</GROUP>


#######################################################################
# Measurement Sets

<MeasurementSet=KanREN_BWCTL_TCP>
DESCRIPTION     KanREN BWCTL (TCP) Internal
ADDRTYPE        BW4
GROUP           KanREN_BWCTL
TESTSPEC        BWTCP4
EXCLUDE_SELF
</MeasurementSet>

<MeasurementSet=KanREN_BWCTL_UDP>
DESCRIPTION     KanREN BWCTL (UDP) Internal
ADDRTYPE        BW4
GROUP           KanREN_BWCTL
TESTSPEC        BWUDP4
EXCLUDE_SELF
</MeasurementSet>

<MeasurementSet=KanREN_OWAMP_TCP>
DESCRIPTION     KanREN OWAMP Internal
ADDRTYPE        LAT4
GROUP           KanREN_OWAMP
TESTSPEC        LAT_1MIN
</MeasurementSet>
TraceDataDir     /var/lib/perfsonar/traceroute_ma/upload/
TraceCentralHost     localhost
TraceCentralDBName     traceroute_ma