Changes between Version 23 and Version 24 of GEMINIv1.1Tutorial


Ignore:
Timestamp:
10/23/12 02:15:16 (7 years ago)
Author:
Ahmed El-Hassany
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • GEMINIv1.1Tutorial

    v23 v24  
    414414The GEMINI services on a given node are configured by the pSConfig service. This service reads configuration stored in UNIS as part of the node's topology information and applies it to local configuration files. pSConfig will also start enabled services or stop disabled services that are running.
    415415
    416 We will now configure one-way (OWAMP) and round-trip (Ping) latency regular tests according to the following diagram.
    417 
    418 [[Image(latency-tests.png)]]
     416We will now configure one-way (OWAMP) and round-trip (Ping) latency regular tests between VM1 and VM4.
     417
    419418
    420419===== 3.1.1 Accessing pSConfig UI =====
     
    428427[[Image(psconfig-secexception.png)]]
    429428
    430 After adding the exception you should see another pop-up for a certificate request. This time you're providing your user certificate to the service. Make sure the user that is shown for the certificate is the one assigned to you for the tutorial. In this example I'm using the user ''gemini20''. In case you did not see this pop-up or cannot see your user, please redo the steps on [wiki:GEMINIGEC14VMInstructions User Workspace - Accessing the portal].
     429After adding the exception you should see another pop-up for a certificate request. This time you're providing your user certificate to the service. Make sure the user that is shown for the certificate is the one assigned to you for the tutorial. In this example I'm using the user ''gemini20''. In case you did not see this pop-up or cannot see your user, please redo the steps on [wiki:GEMINIGEC15VMInstructions User Workspace - Accessing the portal].
    431430
    432431[[Image(psconfig-usercert.png)]]
     
    438437===== 3.1.2 Enabling Services =====
    439438
    440 After we've made sure to have a recent copy of the topology information, we can move on to the Manage Services administration page. On this page we will enable the services required to perform on-demand and regularly scheduled tests. We start by enabling the throughput and one-way latency services on PCA. Make sure to save the changes before continuing to the next node.
    441 
    442 [[Image(psconfig-managevm1.png)]]
    443 
    444 We then proceed to configure the services on nodes PCB and PCC. Since PCB will be the gateway, we will only enable the daemons for the tools used (owamp and bwctl). PCC will have all the latency services and the daemon for throughput measurements. Note that PingER is only enabled on PCC, and we will configure our Ping measurement on that node. (We will use PCA for the scheduled throughput measurements at the end of the tutorial.)
    445 
    446 [[Image(psconfig-managepcbpcc.png)]]
     439After we've made sure to have a recent copy of the topology information, we can move on to the Manage Services administration page. On this page we will enable the services required to perform on-demand and regularly scheduled tests. We start by enabling the  one-way latency services on VM1. Make sure to save the changes before continuing to the next node.
     440
     441[[Image(1-vm1-config.png)]]
     442
     443We then proceed to configure the services on node VM4. Since VM4 will receive OWMP probes, we will only enable the daemons for the tools used (owamp). Note that PingER is only enabled on VM4, and we will configure our Ping measurement on that node.
     444
     445
     446[[Image(2-vm4-config.png)]]
    447447
    448448Now that we've enabled the services for our active measurements we will push the configuration to UNIS. To do this we need to go back to the Configuration Status page and then click the Push Configuration to UNIS. You can verify the list of services enabled for each node (i.e. the list in the image should match what you see).
    449449
    450 [[Image(psconfig-managepush.png)]]
     450[[Image(2.0-unis-push.png)]]
    451451
    452452If everything goes well we should see a green message "Configuration pushed to UNIS.". However, the page auto reloads after this, so you might miss it if not paying attention. If there is no error message, the push completed successfully and the modification time will be 'never'.