For now redirect of stdout/stderr to a file for diagnostic purposes.

closely synch the sender/consumer startup.

Support -N name option to uniquely identify the trafgen on a machine
trafgen uses the name to further qualify event selection.

Support -l logname option to turn on TG's per-packet logging.  There is
no NS interface to this right now.  You would have to turn this on manually
by restarting the trafgens and then restarting the event-sched to replay
events.

Turn on some debugging printfs for now til things have stablized a bit.
The trafficconfig function in libsetup.pm currently redirect stdout/stderr
to a file in /tmp.

getting other experiments node names!

the one) in snmpit_cisco.pm

state. Records this state (and the time at which it was reported) into
the database. Returns nothing.
(eg. 'tmcc state REBOOTING')

If the event system is enabled, also sends events on receipt of state
change reports. These will be monitored by a (not yet finished)
daemon.

will hold the current state (ie 'REBOOTING', 'RELOADING', etc.) The
second is called 'state_timestamp' and will hold the time (in seconds
since the epoch) at which the node entered that state.

Clean up afterward

time, support multiple statements in a single at statement (a personal
miracle of TCL programming!). So, you can do this:

	$ns at 40    "$queue0 set thresh_ 5 ; $queue0 set linterm_ 9"
	$ns at 40    "$queue0 set maxthresh_ 10 ; $queue0 set q_weight_ 0.5"
	$ns at 40    "$queue0 set queue-in-bytes_ 0"
	$ns at 40    "$queue0 set limit_ 50"

These are turned into LINK MODIFY events as such:

	QUEUE-IN-BYTES=
	LIMIT=
	MAXTHRESH=
	THRESH=
	LINTERM=
	Q_WEIGHT=

At present, they are turned into independent events; my TCL ability
falls way short of figuring that out! Easy as a perl script though!

OID from the CISCO-VLAN-MEMBERSHIP MIB. But, this MIB does not seem
to be supported by all Cisco switches. So, we now use vlanPortVlan
from the CISCO-STACK MIB.

So, we no longer need CISCO-VLAN-MEMBERSHIP-MIB at all, which should make
snmpit usable on a wider variety of Ciscos.

This is for Shashi and NSE support. TMCD returns this new field in
the trafgens command, and libsetup.pm has a new test; do nothing if
the generator does not equal TG. This is a temporary change; finalize
when Shashi is done.

This is for Shashi and NSE support.

own development tree -Shashi

code in TCP mode. Simple changes. Works like this:

	set tcp0 [new Agent/TCP]
	$ns attach-agent $n2 $tcp0

	set cbr1 [new Application/Traffic/CBR]
	$cbr1 attach-agent $tcp0

	set null1 [new Agent/TCPSINK]
	$ns attach-agent $n3 $null1

Note, there are no state variables supported yet.

this off, but here is what I did.

Parser: Allow for the following syntax

	set link0  [$ns duplex-link $nodeA $nodeB 100Mb 0ms RED]
	set queue0 [[$ns link $nodeA $nodeB] queue]
	$queue0 set gentle_ 1
	$queue0 set queue-in-bytes_ 0
	$queue0 set limit_ 50
	$queue0 set maxthresh_ 20
	$queue0 set thresh_ 7
	$queue0 set linterm_ 11
	$queue0 set q_weight_ 0.004

    NB: This differs from the NS syntax (and is the part that Chris
    needs to fix) in that there is just a single queue object per
    duplex link, thus the parameters cannot be set asymmetrically.
    Note, the delay node *does* use a RED/GRED queue in each
    direction, but its params are the same. These TCL hacks took a
    long time for me to get right!

    Also note that I have no idea how this stuff relates to LANS! I
    do not allow LANS to be created with RED queues (another item for
    Chris to work on perhaps?).

assign_wrapper: A horrible hack to pass the new fields added to
virt_lans onto the delays table setup. Also another minor hack ensure
that a delay node is added when a RED queue is used (for the case when
no other traffic shaping is done). At the moment, the virt_lans table
has a single set of fields, while the delays table has the double set;
one for each direction of the pipe. Here is a listing.

    alter table delays add q0_limit int default 0 after lossrate0;
    alter table delays add q0_maxthresh int default 0 after q0_limit;
    alter table delays add q0_minthresh int default 0 after q0_maxthresh;
    alter table delays add q0_weight float default 0.0 after q0_minthresh;
    alter table delays add q0_linterm int default 0 after q0_weight;
    alter table delays add q0_qinbytes tinyint default 0 after q0_linterm;
    alter table delays add q0_bytes tinyint default 0 after q0_qinbytes;
    alter table delays add q0_meanpsize int default 0 after q0_bytes;
    alter table delays add q0_wait int default 0 after q0_meanpsize;
    alter table delays add q0_setbit int default 0 after q0_wait;
    alter table delays add q0_droptail int default 0 after q0_setbit;
    alter table delays add q0_red tinyint default 0 after q0_droptail;
    alter table delays add q0_gentle tinyint default 0 after q0_red;

tmcd/tmcd.c: Change dodelays to pass back all of these fields (for
both pipes; there are equiv q1 fields in the delays table). Yikes! Its
done in a backwards compatable manner though, so existing delay nodes
will continue to work just fine.

tmcd/freebsd/liblocsetup.pm: Change the delays configuration script to
get all these fields and do something useful with. Of course, our
delay nodes cannot use a lot of these fields, but the information is
sent through for the eventuality that we have more sophisticated
delays nodes.

Test Suite: Add red test dir that has the above syntax as its test.

it. Worry about it later.

remove the originals, so that we can run the files through configure.

NOTE: I wanted to keep the RCS history intact so I went over to the
CVS directory on moab and copied the ,v file to the new names, and
then did a normal cvs remove the originals. This keeps the RCS history
going without screwing up anyone. Not a recommended approach, but what
the hell.

Also improved the usage message.

Also added a dire warning about parallelism, so that we hopefully
won't forget about it when adding new steps to the swapin process.

another process to handle os_setup, and let that run while doing
things like snmpit.  This should make experiment creation slightly
faster, and hide some of the scaling time of some scripts
(particularly, snmpit) behind the much larger node reboot time.

Things that _have_ to be done before the nodes come up (namely
exports_setup and starting the event system) are done before the
os_setup process is forked, just to be absolutely sure that they get
done before they're needed.

should be a dhclient option, but dhclient doesn't seem to have it.

This saves network traffic, but the primary reason for doing it is
that if users try to change information that dhclient sets (such as
hostname), dhclient periodially clobbers their changes when it
renews the lease.

experiment?' entry, after getting some questions about this.

now only shows packet/octet couters. '-e' shows error counters, and
'-a' shows all counters.

Usage: portstats <pid> <eid> [vname ...] [vname:port ...]

If only pid and eid are given, prints out information about all
ports in the experiment. Otherwise, output is limited to the
nodes and/or ports given.

information about a large number of ports in bulk.

Also added the RMON MIB.

nodeid.

system programs. Build two versions of the event library, one for non
threaded programs and another (libevent_r.a) for threaded versions.
Remove all that -pthread goo from all of the makefiles, except for the
scheduler (which is threaded); it gets linked as before, but with
-levent_r instead. If you try and use the threaded API without the
proper link, the library will print an error message and quit.