Tutorial >> Summary Information | TOC |
All jar files dated before June 6, 2006 are invalid. The new jar file incorporates all of the features in the version known as betaRLI.jar dated March 2006 and contains changes in response to our new hardware configuration. The features description below is identical to the one describing the earlier betaRLI.jar file. However, the newer RLI.jar file recognizes the new internal organization of the ONL testbed hardware making all older jar files obsolete.
Furthermore, the SSH tunnel has changed. The SSH command will appear to SSH into onl.arl.wustl.edu instead of onl03.arl.wustl.edu, and the end of the tunnel will terminate at the hostname onlsrv instead of onl03. (In reality though, you will still end up on logged into the host onl03.) See the RLI SSH Tunneling link in the Getting Started page that can be found in the side bar of the main ONL Web page (after logging into the ONL Web site).
Note the following about the new RLI.jar file:
The new features are:
Before:Select Mode => Monitoring to switch from configuration menus to monitoring menus.
Now:There is no Mode => Monitoring selection. Configuration and monitoring menus appear together for any particular item; e.g., if you select a port, you will see all of the configuration menu items followed by the monitoring items.
Before:A user would have to SSH into the CP and run monmsgs to capture plugin debug output in a window.
Now:The debugging can be selected from an RLI menu. Click the NSP icon and then select Debugging. Select the debugging ON box, and then select the message level for the port of interest. All output is recorded in /tmp/debug.log at the CP.
Before: You could not negate the filter.
Now:You can. Typically, it would be used to implement "if a packet does NOT match the filter, then ...."
Before: N/A
Now:You can. Use the on field of the table to turn a filter on or off, essentially, adding or removing the filter. This allows you to remove a filter and reinstall it later without having to reenter the data.
Before:The choice was automatic. For example, the queue length would represent the sample queue length; i.e., the length of the queue at the instance that the queue length counter was read. The idea is that given observations D(0), D(1), ... , D(n), gathered at a time interval of T, report either the rate (i.e., [D(k)-D(k-1)]/T) or the absolute value (i.e., D(0), D(1), ... , D(n)).
Now:You can choose whether a parameter is shown as a rate or an absolute value. This option is available for most parameters but a few have no time element and can only be displayed as absolute values.
Before: DQ was OFF by default.
Now:DQ is ON by default. If you want to turn it off, select NSP => Queueing => DQ OFF.
Revised: Wed, June 7, 2006
Tutorial >> Summary Information | TOC |